<div dir="ltr">It still probably fits in OSOps, at least in contrib, as the idea is to capture scripts and code that _may_ help someone, rather than necessarily being 100% fit for any production environment. Of course, any/all documentation available would also be useful.<div><br></div><div>Robert</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 17, 2016 at 8:42 PM, Kevin Bringard (kevinbri) <span dir="ltr"><<a href="mailto:kevinbri@cisco.com" target="_blank">kevinbri@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
<br>
<br>
On 2/17/16, 1:31 PM, "Shamail" <<a href="mailto:itzshamail@gmail.com">itzshamail@gmail.com</a>> wrote:<br>
<br>
>Sorry for the top posting... I wanted to make a suggestion:<br>
><br>
><br>
>Would this script be suited for OSOps[1]? The networking guide could then reference it but we could continue to evolve/maintain it as an operators tool.<br>
><br>
<br>
</span>It could be... The problem is that every deploy is different, and so this isn't so much a one size fits all software, as it is a good reference. By the time we got it to the point where it was a generic migration tool, anyone who'd benefit from it would likely have long moved away from nova-networking.<br>
<br>
At least that's my thought, but maybe I overestimate the effort involved in generalizing it.<br>
<span class=""><br>
><br>
>[1] <a href="https://wiki.openstack.org/wiki/Osops" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Osops</a><br>
><br>
><br>
>Thanks,<br>
>Shamail<br>
><br>
>On Feb 17, 2016, at 4:29 PM, Matt Kassawara <<a href="mailto:mkassawara@gmail.com">mkassawara@gmail.com</a>> wrote:<br>
><br>
><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 href="mailto:kevinbri@cisco.com">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>
</span>><a href="https://github.com/kevinbringard/novanet2neutron/tree/icehouse" rel="noreferrer" target="_blank">https://github.com/kevinbringard/novanet2neutron/tree/icehouse</a> <<a href="https://github.com/kevinbringard/novanet2neutron/tree/icehouse" rel="noreferrer" target="_blank">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>
<span class="">><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>
</span>><a href="https://www.openstack.org/summit/austin-2016/vote-for-speakers/presentation/7045" rel="noreferrer" target="_blank">https://www.openstack.org/summit/austin-2016/vote-for-speakers/presentation/7045</a> <<a href="https://www.openstack.org/summit/austin-2016/vote-for-speakers/presentation/7045" rel="noreferrer" target="_blank">https://www.openstack.org/summit/austin-2016/vote-for-speakers/presentation/7045</a>><br>
<div class="HOEnZb"><div class="h5">><br>
>-- Kevin<br>
><br>
><br>
><br>
>On 12/9/15, 12:49 PM, "Kevin Bringard (kevinbri)" <<a href="mailto:kevinbri@cisco.com">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 href="mailto:edgar.magana@workday.com">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 href="mailto:edgar.magana@workday.com">edgar.magana@workday.com</a>><br>
>>>Date: Wednesday, December 9, 2015 at 9:54 AM<br>
>>>To: Matt Kassawara <<a href="mailto:mkassawara@gmail.com">mkassawara@gmail.com</a>>, "Kevin Bringard (kevinbri)" <<a href="mailto:kevinbri@cisco.com">kevinbri@cisco.com</a>><br>
>>>Cc: OpenStack Operators <<a href="mailto:openstack-operators@lists.openstack.org">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 href="mailto:kevinbri@cisco.com">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 href="mailto:edgar.magana@workday.com">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 href="mailto:tom@openstack.org">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>
>>><a href="https://wiki.openstack.org/wiki/Neutron/MigrationFromNovaNetwork/HowTo" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Neutron/MigrationFromNovaNetwork/HowTo</a> <<a href="https://wiki.openstack.org/wiki/Neutron/MigrationFromNovaNetwork/HowTo" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Neutron/MigrationFromNovaNetwork/HowTo</a>><br>
>>>>>><br>
>>><a href="http://docs.openstack.org/networking-guide/migration_nova_network_to_neutron.html" rel="noreferrer" target="_blank">http://docs.openstack.org/networking-guide/migration_nova_network_to_neutron.html</a> <<a href="http://docs.openstack.org/networking-guide/migration_nova_network_to_neutron.html" rel="noreferrer" target="_blank">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 href="https://github.com/NeCTAR-RC/novanet2neutron" rel="noreferrer" target="_blank">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 href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
>>>>><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
>>>>_______________________________________________<br>
>>>>OpenStack-operators mailing list<br>
>>>><a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
>>>><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
>>>_______________________________________________<br>
>>>OpenStack-operators mailing list<br>
>>><a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
>>><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>_______________________________________________<br>
>>OpenStack-operators mailing list<br>
>><a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
>><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
>_______________________________________________<br>
>OpenStack-operators mailing list<br>
><a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
>_______________________________________________<br>
>OpenStack-operators mailing list<br>
><a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
><br>
><br>
><br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</div></div></blockquote></div><br></div>