yahoo-eng-team team mailing list archive

[Mike Kolesnik <mkolesni@xxxxxxxxxx>]

Public bug reported:

Marking network as external represents a different usage for that specific network than an "ordinary" network.
It doesn't make sense to connect instances directly to the external network (otherwise you'd have used the network directly and not floating IPs).

For that reason, it also doesn't make sense to mark the network as
shared (and vice versa).

Currently it is allowed to mark a network as both shared and external,
this should be prevented to deter misconfiguration and misuse of the
network.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1323267

Title:
  Network shouldn't be shared and external at the same time

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Marking network as external represents a different usage for that specific network than an "ordinary" network.
  It doesn't make sense to connect instances directly to the external network (otherwise you'd have used the network directly and not floating IPs).

  For that reason, it also doesn't make sense to mark the network as
  shared (and vice versa).

  Currently it is allowed to mark a network as both shared and external,
  this should be prevented to deter misconfiguration and misuse of the
  network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1323267/+subscriptions