Public bug reported:
Neutron and Designate integration covers use cases for ports which are exposed
via floating IPs, or reside on provider networks.
However, the following use cases aren't being covered:
1. Ports reside on a no-NAT network, which is routable from outside the
Openstack deployment.
2. Ports on any network which need exposure via DNS: e.g an app uses FQDNs to
intercommunicate between app components.
As the no-NAT attribute belongs to the router, and not to the network, it might
be tricky to detect port exposure via this attribute: a user could attach a
network with some ports on it to a no-NAT network and so they're exposed even
though they weren't during creation.
Or a router might be changed from NAT to no-NAT and vice versa.
To simplify I would suggest adding an attribute to the network via an
extension, which would indicate that this network's ports should be published
on the DNS.
So for networks which need exposure via DNS, we could flag these networks and
force the DNS publishing.
** 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/1784879
Title:
Neutron doesn't update Designate with some use cases
Status in neutron:
New
Bug description:
Neutron and Designate integration covers use cases for ports which are
exposed via floating IPs, or reside on provider networks.
However, the following use cases aren't being covered:
1. Ports reside on a no-NAT network, which is routable from outside the
Openstack deployment.
2. Ports on any network which need exposure via DNS: e.g an app uses FQDNs to
intercommunicate between app components.
As the no-NAT attribute belongs to the router, and not to the network, it
might be tricky to detect port exposure via this attribute: a user could attach
a network with some ports on it to a no-NAT network and so they're exposed even
though they weren't during creation.
Or a router might be changed from NAT to no-NAT and vice versa.
To simplify I would suggest adding an attribute to the network via an
extension, which would indicate that this network's ports should be published
on the DNS.
So for networks which need exposure via DNS, we could flag these networks and
force the DNS publishing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1784879/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
