[openstack-dev] [Neutron][L3] Representing a networks connected by routers

Kevin Benton blak111 at gmail.com
Tue Jul 28 23:44:53 UTC 2015

We need to work on that code quite a bit anyway for other features (get me
a network, VLAN trunk ports) so adding a different parameter shouldn't be
bad. Even if Nova doesn't initially buy in, we can always pre-create the
port and pass it to Nova boot as a UUID.

On Tue, Jul 28, 2015 at 6:15 AM, Ryan Moats <rmoats at us.ibm.com> wrote:

> Kevin, doesn't this in itself create technical debt on the nova side in
> the sense of what an instance attaches to?
> I agree that it looks like less technical debt than conditionally
> redefining a network, but without nova buy-in, it looks
> like a non-starter...
> Ryan
> Kevin Benton <blak111 at gmail.com> wrote on 07/28/2015 02:15:13 AM:
> [snip]
> > I would rather see something to reference a group of subnets that
> > can be used for floating IP allocation and port creation in lieu of
> > a network ID than the technical debt that conditionally redefining a
> > network will bring.
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Kevin Benton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150728/dedd1351/attachment.html>

More information about the OpenStack-dev mailing list