Aha! Thanks so much for pointing that out. Although actually it's a reminder,
and I should have known that already, as I now remember your recent thread
about this.
So, 100% understood now that flavors aren't intended for networks.
I hope that the metaplugin removal change might land quickly
As it is a bug fix, perhaps you could add this to the agenda for the next Neutron IRC meeting, in the Bugs section?Regards, Neil
+1 also
Original Message
From: Fox, Kevin M
Sent: Friday, 26 June 2015 21:15
To: OpenStack Development Mailing List (not for usage questions)
Reply To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova] The unbearable lightness of specs
+1
It seems like we're possibly stuck now on the VIF plugin script spec [1];
there being core comments in apparently conflicting directions. I wonder if
it's still feasible for a version of this to land during Liberty?
[1] https://review.openstack.org/#/c/162468/
I plan to reread everyone's
Great initiative, IMO. I favour going directly to openstack-, rather than
stackforge-, for the migration reason that you mention.
Original Message
From: Thomas Goirand
Sent: Wednesday, 27 May 2015 09:17
To: OpenStack Development Mailing List (not for usage questions)
Reply To: OpenStack
How about retaining --dhcp-authoritative when dhcp_agents_per_network = 1? I would guess that that is the 90% case. I suppose that would require passing new information from the Neutron server to the DHCP
Out of interest, have you done this by re-releasing the Ubuntu packaging? Or
have you taken an independent approach?
Regards,
Neil
Original Message
From: Thomas Goirand
Sent: Thursday, 14 May 2015 22:21
To: OpenStack Operators; Openstack; OpenStack Development Mailing List (not for
Thanks Russell and Kyle for explaining. I think I get the picture now, in
particular of how these backend projects are mostly under separate management,
but at the same time subject to PTL oversight and 'part of the wider Neutron
effort'.
May I drill down further on what is anticipated,
Note also, though, that any third party package can add its own mechanism
driver to this list. So the effective complete list is the combination of:
- what you see in Neutron's setup.cfg, under neutron.ml2.mechanism_drivers
- further neutron.ml2.mechanism_drivers entries that are added by
To the extent that it's useful to those suggesting the questions, it feels to me like this could be an ongoing resource rather than a one-off survey.Hence, perhaps a web page that all OpenStack members should
Thanks for your interest; following is a description of what Calico does in this area. Just to be clear, this is for interest and information only and I don't mean to suggest that this has any bearing on the
11 matches
Mail list logo
