shared network defined in overcloud

[Andrea Frittoli]

setup-neutron creates a shared network in the overcloud, so that the demo user can than create VM attached to it to verify overcloud creation.

It would be sufficient to create a non-shared network for the demo tenant, as the admin user does not use it.
I'd suggest having an option about this, so that we can have the shared network created or not created.

Several tempest tests rely on only one network being available to the tenant running the test, so the current setup is not compatible with tempest.

It would be interesting for tempest to be able to work in an environment with shared networks defined as well.

[Andrea Frittoli (andrea-frittoli)]

Fixing this on tempest side would be helpful for all scenarios where devstack is not the cloud under tests, e.g. refstack against public cloud.

[Steven Hardy (shardy)]

This bug was reported against an old version of TripleO, and may no longer be valid.

Since it was reported before the start of the liberty cycle (and our oldest stable
branch is stable/liberty), I'm marking this incomplete.

Please reopen this (change the status from incomplete) if the bug is still valid
on a current supported (stable/liberty, stable/mitaka or trunk) version of TripleO,
thanks!

[Andrea Frittoli (andrea-frittoli)]

Tempest has been changed to that a network is specified to servers when servers are created, which avoids issues when a shared network exists.
This has been implemented in various patches over time, to linked to this bug, so I'm marking this as won't fix.

[Launchpad Janitor (janitor)]

[Expired for tripleo because there has been no activity for 60 days.]