<html><head><title></title></head><body><!-- rte-version 0.2 9947551637294008b77bce25eb683dac --><div class="rte-style-maintainer" style="white-space: pre-wrap; font-size: small; font-family: 'Courier New', Courier; color: rgb(0, 0, 0);"data-color="global-default" bbg-color="default" data-bb-font-size="medium" bbg-font-size="medium" bbg-font-family="fixed-width">We're in mostly the same boat; using nova-network with VLAN segmentation and looking at a Neutron migration (though ours may take a more drastic path and take us to Neutron+Calico). One question I have for you: the largest issue and conceptual leap we had when initially prototyping Neutron+linuxbridge was that our current model only has controllers and work nodes, with no provisions for dedicated network nodes to route in/out of the cluster. All our work nodes can route by themselves, which would have steered us towards a DVR model, but that seems to have its own issues as well as mandating OVS.<div><br></div><div>Since your branch indicates you're using linuxbridge on Icehouse, are you provisioning network nodes as part of your migration, or are you avoiding needing to provision network nodes in a different fashion?<br><div><br><div class="rte-style-maintainer" style="font-size: small; font-family: 'Courier New', Courier; color: rgb(0, 0, 0);"data-color="global-default" bbg-color="default" data-bb-font-size="medium" bbg-font-size="medium" bbg-font-family="fixed-width"><div class="bbg-rte-fold-content" data-header="From: kevinbri@cisco.com" data-digest="From: kevinbri@cisco.com"style=""><div class="bbg-rte-fold-summary">From: kevinbri@cisco.com </div><div>Subject: Re: [Openstack-operators] Nova-network -> Neutron Migration<br></div></div><blockquote>Definitely, I can work on that. I need to get the migration done first, but once I do I plan to open source our plays and whatever else to help people perform the migration themselves. At that point I can work on adding some stuff to the networking guide as well. Probably will be a few months from now, though.<br><br><br><br><br>On 2/17/16, 9:29 AM, "Matt Kassawara" <<a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:mkassawara@gmail.com" data-destination="mailto:rte:bind">mkassawara@gmail.com</a>> wrote:<br><br>>Cool! I'd like to see this stuff in the networking guide... or at least a link to it for now.<br>><br>>On Wed, Feb 17, 2016 at 8:14 AM, Kevin Bringard (kevinbri)<br>><<a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:kevinbri@cisco.com"data-destination="mailto:rte:bind">kevinbri@cisco.com</a>> wrote:<br>><br>>Hey All!<br>><br>>I wanted to follow up on this. We've managed successfully migrated Icehouse with per tenant networks (non overlapping, obviously) and L3 services from nova-networking to neutron in the lab. I'm working on the automation bits, but once that is done we'll start<br>> migrating real workloads.<br>><br>>I forked Sam's stuff and modified it to work in icehouse with tenants nets: <br>>https://github.com/kevinbringard/novanet2neutron/tree/icehouse <<a spellcheck="false"bbg-destination="rte:bind" href="https://github.com/kevinbringard/novanet2neutron/tree/icehouse"data-destination="rte:bind">https://github.com/kevinbringard/novanet2neutron/tree/icehouse</a>>. I need to update the README to succinctly reflect the steps, but the code is there (I'm going to work on the README today).<br>><br>>If this is something folks are interested in I proposed a talk to go over the process and our various use cases in Austin:<br>><br>>https://<a spellcheck="false"bbg-destination="rte:bind" href="http://www.openstack.org/summit/austin-2016/vote-for-speakers/presentation/7045"data-destination="rte:bind">www.openstack.org/summit/austin-2016/vote-for-speakers/presentation/7045</a> <<a spellcheck="false"bbg-destination="rte:bind" href="https://www.openstack.org/summit/austin-2016/vote-for-speakers/presentation/7045"data-destination="rte:bind">https://www.openstack.org/summit/austin-2016/vote-for-speakers/presentation/7045</a>><br>><br>>-- Kevin<br>><br>><br>><br>>On 12/9/15, 12:49 PM, "Kevin Bringard (kevinbri)" <<a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:kevinbri@cisco.com"data-destination="mailto:rte:bind">kevinbri@cisco.com</a>> wrote:<br>><br>>>It's worth pointing out, it looks like this only works in Kilo+, as it's written. Sam pointed out earlier that this was what they'd run it on, but I verified it won't work on earlier versions because, specifically, in the migrate-secgroups.py it inserts into<br>> the default_security_group table, which was introduced in Kilo.<br>>><br>>>I'm working on modifying it. If I manage to get it working properly I'll commit my changes to my fork and send it out.<br>>><br>>>-- Kevin<br>>><br>>><br>>><br>>>On 12/9/15, 10:00 AM, "Edgar Magana" <<a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:edgar.magana@workday.com" data-destination="mailto:rte:bind">edgar.magana@workday.com</a>> wrote:<br>>><br>>>>I did not but more advanced could mean a lot of things for Neutron. There are so many possible scenarios that expecting to have a “script” to cover all of them is a whole new project. Not sure we want to explore than. In the past we were recommending to<br>>>> make the migration in multiple steps, maybe we could use this as a good step 0.<br>>>><br>>>><br>>>>Edgar<br>>>><br>>>><br>>>><br>>>><br>>>><br>>>>From: "Kris G. Lindgren"<br>>>>Date: Wednesday, December 9, 2015 at 8:57 AM<br>>>>To: Edgar Magana, Matt Kassawara, "Kevin Bringard (kevinbri)"<br>>>>Cc: OpenStack Operators<br>>>>Subject: Re: [Openstack-operators] Nova-network -> Neutron Migration<br>>>><br>>>><br>>>><br>>>>Doesn't this script only solve the case of going from flatdhcp networks in nova-network to same dchp/provider networks in neutron. Did anyone test to see if it also works for doing more advanced nova-network configs?<br>>>><br>>>><br>>>>___________________________________________________________________<br>>>>Kris Lindgren<br>>>>Senior Linux Systems Engineer<br>>>>GoDaddy<br>>>><br>>>><br>>>><br>>>><br>>>><br>>>><br>>>>From: Edgar Magana <<a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:edgar.magana@workday.com" data-destination="mailto:rte:bind">edgar.magana@workday.com</a>><br>>>>Date: Wednesday, December 9, 2015 at 9:54 AM<br>>>>To: Matt Kassawara <<a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:mkassawara@gmail.com" data-destination="mailto:rte:bind">mkassawara@gmail.com</a>>, "Kevin Bringard (kevinbri)" <<a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:kevinbri@cisco.com"data-destination="mailto:rte:bind">kevinbri@cisco.com</a>><br>>>>Cc: OpenStack Operators <<a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:openstack-operators@lists.openstack.org" data-destination="mailto:rte:bind">openstack-operators@lists.openstack.org</a>><br>>>>Subject: Re: [Openstack-operators] Nova-network -> Neutron Migration<br>>>><br>>>><br>>>><br>>>>Yes! We should but with a huge caveat that is not not supported officially by the OpenStack community. At least the author wants to make a move with the Neutron team to make it part of the tree.<br>>>><br>>>><br>>>>Edgar<br>>>><br>>>><br>>>><br>>>><br>>>><br>>>>From: Matt Kassawara<br>>>>Date: Wednesday, December 9, 2015 at 8:52 AM<br>>>>To: "Kevin Bringard (kevinbri)"<br>>>>Cc: Edgar Magana, Tom Fifield, OpenStack Operators<br>>>>Subject: Re: [Openstack-operators] Nova-network -> Neutron Migration<br>>>><br>>>><br>>>><br>>>>Anyone think we should make this script a bit more "official" ... perhaps in the networking guide?<br>>>><br>>>>On Wed, Dec 9, 2015 at 9:01 AM, Kevin Bringard (kevinbri)<br>>>><<a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:kevinbri@cisco.com"data-destination="mailto:rte:bind">kevinbri@cisco.com</a>> wrote:<br>>>><br>>>>Thanks, Tom, Sam, and Edgar, that's really good info. If nothing else it'll give me a good blueprint for what to look for and where to start.<br>>>><br>>>><br>>>><br>>>>On 12/8/15, 10:37 PM, "Edgar Magana" <<a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:edgar.magana@workday.com" data-destination="mailto:rte:bind">edgar.magana@workday.com</a>> wrote:<br>>>><br>>>>>Awesome code! I just did a small testbed test and it worked nicely!<br>>>>><br>>>>>Edgar<br>>>>><br>>>>><br>>>>><br>>>>><br>>>>>On 12/8/15, 7:16 PM, "Tom Fifield" <<a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:tom@openstack.org"data-destination="mailto:rte:bind">tom@openstack.org</a>> wrote:<br>>>>><br>>>>>>On 09/12/15 06:32, Kevin Bringard (kevinbri) wrote:<br>>>>>>> Hey fellow oppers!<br>>>>>>><br>>>>>>> I was wondering if anyone has any experience doing a migration from nova-network to neutron. We're looking at an in place swap, on an Icehouse deployment. I don't have parallel<br>>>>>>><br>>>>>>> I came across a couple of things in my search:<br>>>>>>><br>>>>>>><br>>>>https://wiki.openstack.org/wiki/Neutron/MigrationFromNovaNetwork/HowTo <<a spellcheck="false"bbg-destination="rte:bind" href="https://wiki.openstack.org/wiki/Neutron/MigrationFromNovaNetwork/HowTo"data-destination="rte:bind">https://wiki.openstack.org/wiki/Neutron/MigrationFromNovaNetwork/HowTo</a>><br>>>>>>><br>>>>http://docs.openstack.org/networking-guide/migration_nova_network_to_neutron.html <<a spellcheck="false"bbg-destination="rte:bind" href="http://docs.openstack.org/networking-guide/migration_nova_network_to_neutron.html"data-destination="rte:bind">http://docs.openstack.org/networking-guide/migration_nova_network_to_neutron.html</a>><br>>>>>>><br>>>>>>> But neither of them have much in the way of details.<br>>>>>>><br>>>>>>> Looking to disrupt as little as possible, but of course with something like this there's going to be an interruption.<br>>>>>>><br>>>>>>> If anyone has any experience, pointers, or thoughts I'd love to hear about it.<br>>>>>>><br>>>>>>> Thanks!<br>>>>>>><br>>>>>>> -- Kevin<br>>>>>><br>>>>>>NeCTAR used this script (<a spellcheck="false"bbg-destination="rte:bind" href="https://github.com/NeCTAR-RC/novanet2neutron" data-destination="rte:bind">https://github.com/NeCTAR-RC/novanet2neutron</a> )<br>>>>>>with success to do a live nova-net to neutron using Juno.<br>>>>>><br>>>>>><br>>>>>><br>>>>>>_______________________________________________<br>>>>>>OpenStack-operators mailing list<br>>>>>><a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:OpenStack-operators@lists.openstack.org" data-destination="mailto:rte:bind">OpenStack-operators@lists.openstack.org</a><br>>>>>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators<br>>>>>_______________________________________________<br>>>>>OpenStack-operators mailing list<br>>>>><a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:OpenStack-operators@lists.openstack.org" data-destination="mailto:rte:bind">OpenStack-operators@lists.openstack.org</a><br>>>>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators<br>>>>_______________________________________________<br>>>>OpenStack-operators mailing list<br>>>><a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:OpenStack-operators@lists.openstack.org" data-destination="mailto:rte:bind">OpenStack-operators@lists.openstack.org</a><br>>>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators<br>>>><br>>>><br>>>><br>>>><br>>>><br>>>><br>>>><br>>>><br>>>><br>>>><br>>>><br>>>><br>>>><br>>>_______________________________________________<br>>>OpenStack-operators mailing list<br>>><a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:OpenStack-operators@lists.openstack.org" data-destination="mailto:rte:bind">OpenStack-operators@lists.openstack.org</a><br>>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators<br>>_______________________________________________<br>>OpenStack-operators mailing list<br>><a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:OpenStack-operators@lists.openstack.org" data-destination="mailto:rte:bind">OpenStack-operators@lists.openstack.org</a><br>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators<br>><br>><br>><br>><br>><br>><br>><br>_______________________________________________<br>OpenStack-operators mailing list<br><a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:OpenStack-operators@lists.openstack.org" data-destination="mailto:rte:bind">OpenStack-operators@lists.openstack.org</a><br><a spellcheck="false"bbg-destination="rte:bind" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators"data-destination="rte:bind">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br></blockquote><br></div></div></div></div></body></html>