Awesome! Please, add me as reviewer of your commit. Edgar
On 2/19/16, 7:21 AM, "Kevin Bringard (kevinbri)" <[email protected]> wrote: >Ah, thanks Rob, I misunderstood the purpose for the repo. > >Once I get everything tidied up and complete I'll work on getting a PR into >contrib. > > > > >On 2/18/16, 7:42 PM, "Robert Starmer" <[email protected]> wrote: > >>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. >> >> >>Robert >> >> >>On Wed, Feb 17, 2016 at 8:42 PM, Kevin Bringard (kevinbri) >><[email protected]> wrote: >> >> >> >> >> >>On 2/17/16, 1:31 PM, "Shamail" <[email protected]> wrote: >> >>>Sorry for the top posting... I wanted to make a suggestion: >>> >>> >>>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. >>> >> >>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. >> >>At least that's my thought, but maybe I overestimate the effort involved in >>generalizing it. >> >>> >>>[1] >>https://wiki.openstack.org/wiki/Osops <https://wiki.openstack.org/wiki/Osops> >>> >>> >>>Thanks, >>>Shamail >>> >>>On Feb 17, 2016, at 4:29 PM, Matt Kassawara <[email protected]> wrote: >>> >>> >>> >>>Cool! I'd like to see this stuff in the networking guide... or at least a >>>link to it for now. >>> >>>On Wed, Feb 17, 2016 at 8:14 AM, Kevin Bringard (kevinbri) >>><[email protected]> wrote: >>> >>>Hey All! >>> >>>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 >>> migrating real workloads. >>> >>>I forked Sam's stuff and modified it to work in icehouse with tenants nets: >>>https://github.com/kevinbringard/novanet2neutron/tree/icehouse >>><https://github.com/kevinbringard/novanet2neutron/tree/icehouse>. >> 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). >>> >>>If this is something folks are interested in I proposed a talk to go over >>>the process and our various use cases in Austin: >>> >>>https://www.openstack.org/summit/austin-2016/vote-for-speakers/presentation/7045 >>> >>><https://www.openstack.org/summit/austin-2016/vote-for-speakers/presentation/7045> >>> >>>-- Kevin >>> >>> >>> >>>On 12/9/15, 12:49 PM, "Kevin Bringard (kevinbri)" <[email protected]> wrote: >>> >>>>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 >>> the default_security_group table, which was introduced in Kilo. >>>> >>>>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. >>>> >>>>-- Kevin >>>> >>>> >>>> >>>>On 12/9/15, 10:00 AM, "Edgar Magana" <[email protected]> wrote: >>>> >>>>>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 >>>>> make the migration in multiple steps, maybe we could use this as a good >>>>> step 0. >>>>> >>>>> >>>>>Edgar >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>From: "Kris G. Lindgren" >>>>>Date: Wednesday, December 9, 2015 at 8:57 AM >>>>>To: Edgar Magana, Matt Kassawara, "Kevin Bringard (kevinbri)" >>>>>Cc: OpenStack Operators >>>>>Subject: Re: [Openstack-operators] Nova-network -> Neutron Migration >>>>> >>>>> >>>>> >>>>>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? >>>>> >>>>> >>>>>___________________________________________________________________ >>>>>Kris Lindgren >>>>>Senior Linux Systems Engineer >>>>>GoDaddy >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>From: Edgar Magana <[email protected]> >>>>>Date: Wednesday, December 9, 2015 at 9:54 AM >>>>>To: Matt Kassawara <[email protected]>, "Kevin Bringard (kevinbri)" >>>>><[email protected]> >>>>>Cc: OpenStack Operators <[email protected]> >>>>>Subject: Re: [Openstack-operators] Nova-network -> Neutron Migration >>>>> >>>>> >>>>> >>>>>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. >>>>> >>>>> >>>>>Edgar >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>From: Matt Kassawara >>>>>Date: Wednesday, December 9, 2015 at 8:52 AM >>>>>To: "Kevin Bringard (kevinbri)" >>>>>Cc: Edgar Magana, Tom Fifield, OpenStack Operators >>>>>Subject: Re: [Openstack-operators] Nova-network -> Neutron Migration >>>>> >>>>> >>>>> >>>>>Anyone think we should make this script a bit more "official" ... perhaps >>>>>in the networking guide? >>>>> >>>>>On Wed, Dec 9, 2015 at 9:01 AM, Kevin Bringard (kevinbri) >>>>><[email protected]> wrote: >>>>> >>>>>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. >>>>> >>>>> >>>>> >>>>>On 12/8/15, 10:37 PM, "Edgar Magana" <[email protected]> wrote: >>>>> >>>>>>Awesome code! I just did a small testbed test and it worked nicely! >>>>>> >>>>>>Edgar >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>On 12/8/15, 7:16 PM, "Tom Fifield" <[email protected]> wrote: >>>>>> >>>>>>>On 09/12/15 06:32, Kevin Bringard (kevinbri) wrote: >>>>>>>> Hey fellow oppers! >>>>>>>> >>>>>>>> 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 >>>>>>>> >>>>>>>> I came across a couple of things in my search: >>>>>>>> >>>>>>>> >>>>>https://wiki.openstack.org/wiki/Neutron/MigrationFromNovaNetwork/HowTo >>>>><https://wiki.openstack.org/wiki/Neutron/MigrationFromNovaNetwork/HowTo> >>>>>>>> >>>>>http://docs.openstack.org/networking-guide/migration_nova_network_to_neutron.html >>>>> >>>>><http://docs.openstack.org/networking-guide/migration_nova_network_to_neutron.html> >>>>>>>> >>>>>>>> But neither of them have much in the way of details. >>>>>>>> >>>>>>>> Looking to disrupt as little as possible, but of course with something >>>>>>>> like this there's going to be an interruption. >>>>>>>> >>>>>>>> If anyone has any experience, pointers, or thoughts I'd love to hear >>>>>>>> about it. >>>>>>>> >>>>>>>> Thanks! >>>>>>>> >>>>>>>> -- Kevin >>>>>>> >>>>>>>NeCTAR used this script (https://github.com/NeCTAR-RC/novanet2neutron ) >>>>>>>with success to do a live nova-net to neutron using Juno. >>>>>>> >>>>>>> >>>>>>> >>>>>>>_______________________________________________ >>>>>>>OpenStack-operators mailing list >>>>>>>[email protected] >>>>>>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>>>>>_______________________________________________ >>>>>>OpenStack-operators mailing list >>>>>>[email protected] >>>>>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>>>>_______________________________________________ >>>>>OpenStack-operators mailing list >>>>>[email protected] >>>>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>_______________________________________________ >>>>OpenStack-operators mailing list >>>>[email protected] >>>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>>_______________________________________________ >>>OpenStack-operators mailing list >>>[email protected] >>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>>_______________________________________________ >>>OpenStack-operators mailing list >>>[email protected] >>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>> >>> >>> >>_______________________________________________ >>OpenStack-operators mailing list >>[email protected] >>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >> >> >> >> >> >> >_______________________________________________ >OpenStack-operators mailing list >[email protected] >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
