Neil, I'm very glad to here of your interest. I have been talking with Kyle Mestery about the rfe you mention [1] since the day he filed it. It relates to a blueprint that I have been trying to get traction on [2] in various forms for a while [*].
The rfe talks about attaching VMs directly to the the L3 routed network. This will require some coordination between ip address assignment and scheduling of the instance to a compatible physical server. My blueprint, on the other hand, tries to maintain IP mobility across the network by relying on the BGP speaker work: another BP we've been trying to get traction on for a while. I also limit the connections to the L3 routed network to virtual routers for now. The two have network segments in common. So, as I proceed on the implementation of my blueprint [2], I will keep in mind the needs of the rfe [1] and build network segments in a way which can be utilized by both. However, I will leave the coordination of VM scheduling and IP address assignment to someone else. Does this all make sense? Currently, I have my development efforts mostly consumed in the address scopes blueprint. However, I would like to find a way to pass that on soon so that I can turn my attention toward the network segments work. Let's find some time to look at what first steps we can get started. Ping me directly on IRC. Carl [1] https://bugs.launchpad.net/neutron/+bug/1458890 [2] https://review.openstack.org/#/c/172244/ [*] You're not the only one having trouble getting traction. Sometimes it takes a while to realize that we're interested in similar things and to find the commonalities and then to get people excited about something. It has been an uphill battle for me until recently. On Thu, Jun 11, 2015 at 6:16 AM, Neil Jerram <neil.jer...@metaswitch.com> wrote: > Hi Carl et al., > > I see from [1] that L3 routed network segments are on the Neutron L3 > subteam's roadmap for Liberty, and I wanted to say that I'm very interested > in this work, and - if there isn't someone else already - happy to take the > lead on making it happen. > > I'm aware already of several parties interested in this work, and discussion > between those parties has been proceeding at [2]. If there is anyone else > interested - i.e. in networks that are predominantly L3 routed, and/or where > L2 broadcast is partitioned into subsets of the overall network - please do > take a look at that bug [2] and add your thoughts there, or comment in > response to this email. > > I'm afraid I've not previously been attending L3 subteam IRC meetings - > something which I now see was a mistake! - but I plan to do that from now > on. For today's meeting, though, I'm afraid I have to leave at the half way > point. Therefore, if you (Carl) think it would be useful to raise or > discuss this during the meeting, I'd appreciate if that could be scheduled > during the first half hour. > > Many thanks, > Neil > > > [1] https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam > [2] https://bugs.launchpad.net/neutron/+bug/1458890 __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev