Unsubscribe
Sent from my iPhone > On May 21, 2017, at 8:06 AM, [email protected] wrote: > > Send OpenStack-operators mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OpenStack-operators digest..." > > > Today's Topics: > > 1. Successful nova-network to Neutron Migration (Joe Topjian) > 2. Re: Successful nova-network to Neutron Migration (Belmiro Moreira) > 3. Re: Successful nova-network to Neutron Migration (Joe Topjian) > 4. [trove][all] Weekly meeting time change - 1500UTC > #openstack-meeting-alt (Amrith Kumar) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 20 May 2017 10:51:07 -0600 > From: Joe Topjian <[email protected]> > To: "[email protected]" > <[email protected]> > Subject: [Openstack-operators] Successful nova-network to Neutron > Migration > Message-ID: > <CA+y7hvh2099O-ApFJvOsM+=+gVASeK7O7Z5VcpKs=nbs-ya...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi all, > > There probably aren't a lot of people in this situation nowadays, but for > those that are, I wanted to report a successful nova-network to Neutron > migration. > > We used NeCTAR's migration scripts which can be found here: > > https://github.com/NeCTAR-RC/novanet2neutron > > These scripts allowed us to do an in-place upgrade with almost no downtime. > There was probably an hour or two of network downtime, but all instances > stayed up and running. There were also a handful of instances that needed a > hard reboot and some that had to give up their Floating IP to Neutron. All > acceptable, IMO. > > We modified them to suit our environment, specifically by adding support > for IPv6 and Floating IPs. In addition, we leaned on our existing Puppet > environment to deploy certain Nova and Neutron settings in phases. > > But we wouldn't have been able to do this migration without these scripts, > so to Sam and the rest of the NeCTAR crew: thank you all very much! > > Joe > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20170520/e5991ee5/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date: Sat, 20 May 2017 22:54:41 +0200 > From: Belmiro Moreira <[email protected]> > To: Joe Topjian <[email protected]> > Cc: "[email protected]" > <[email protected]> > Subject: Re: [Openstack-operators] Successful nova-network to Neutron > Migration > Message-ID: > <CAPkQhnc40_EXM9TrnDOoVR=_rgan7njl43hxk24oxefnihk...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi Joe, > congrats. > > Can you also make available your scripts changes for IPv6? > The more the better for any site that is still working in the migration, > like us :) > > thanks, > Belmiro > >> On Sat, May 20, 2017 at 6:51 PM, Joe Topjian <[email protected]> wrote: >> >> Hi all, >> >> There probably aren't a lot of people in this situation nowadays, but for >> those that are, I wanted to report a successful nova-network to Neutron >> migration. >> >> We used NeCTAR's migration scripts which can be found here: >> >> https://github.com/NeCTAR-RC/novanet2neutron >> >> These scripts allowed us to do an in-place upgrade with almost no >> downtime. There was probably an hour or two of network downtime, but all >> instances stayed up and running. There were also a handful of instances >> that needed a hard reboot and some that had to give up their Floating IP to >> Neutron. All acceptable, IMO. >> >> We modified them to suit our environment, specifically by adding support >> for IPv6 and Floating IPs. In addition, we leaned on our existing Puppet >> environment to deploy certain Nova and Neutron settings in phases. >> >> But we wouldn't have been able to do this migration without these scripts, >> so to Sam and the rest of the NeCTAR crew: thank you all very much! >> >> Joe >> >> _______________________________________________ >> OpenStack-operators mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20170520/086d573d/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Sat, 20 May 2017 18:24:23 -0600 > From: Joe Topjian <[email protected]> > To: Belmiro Moreira <[email protected]> > Cc: "[email protected]" > <[email protected]> > Subject: Re: [Openstack-operators] Successful nova-network to Neutron > Migration > Message-ID: > <CA+y7hvgLtTHbx=ibrd3pCeFQ=f-+dtj15q2fpcbeyqxxcq4...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Yep, absolutely: > > https://github.com/cybera/novanet2neutron > > The changes are all rolled into one commit: > > https://github.com/cybera/novanet2neutron/commit/31a6ef0eaebb84b94f4cc97d4f0acfffb4eed251 > > Note that we hard-coded the network and subnet names in there, so if you > end up using this, you'll want to change that. > > Thanks, > Joe > > On Sat, May 20, 2017 at 2:54 PM, Belmiro Moreira < > [email protected]> wrote: > >> Hi Joe, >> congrats. >> >> Can you also make available your scripts changes for IPv6? >> The more the better for any site that is still working in the migration, >> like us :) >> >> thanks, >> Belmiro >> >>> On Sat, May 20, 2017 at 6:51 PM, Joe Topjian <[email protected]> wrote: >>> >>> Hi all, >>> >>> There probably aren't a lot of people in this situation nowadays, but for >>> those that are, I wanted to report a successful nova-network to Neutron >>> migration. >>> >>> We used NeCTAR's migration scripts which can be found here: >>> >>> https://github.com/NeCTAR-RC/novanet2neutron >>> >>> These scripts allowed us to do an in-place upgrade with almost no >>> downtime. There was probably an hour or two of network downtime, but all >>> instances stayed up and running. There were also a handful of instances >>> that needed a hard reboot and some that had to give up their Floating IP to >>> Neutron. All acceptable, IMO. >>> >>> We modified them to suit our environment, specifically by adding support >>> for IPv6 and Floating IPs. In addition, we leaned on our existing Puppet >>> environment to deploy certain Nova and Neutron settings in phases. >>> >>> But we wouldn't have been able to do this migration without these >>> scripts, so to Sam and the rest of the NeCTAR crew: thank you all very much! >>> >>> Joe >>> >>> _______________________________________________ >>> OpenStack-operators mailing list >>> [email protected] >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>> >>> >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20170520/1ccd9981/attachment-0001.html> > > ------------------------------ > > Message: 4 > Date: Sun, 21 May 2017 07:08:23 -0400 > From: "Amrith Kumar" <[email protected]> > To: "'OpenStack Development Mailing List \(not for usage questions\)'" > <[email protected]>, > <[email protected]> > Subject: [Openstack-operators] [trove][all] Weekly meeting time change > - 1500UTC #openstack-meeting-alt > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > The Trove weekly meeting time has been changed from 1800UTC on Wednesdays to > 1500UTC on Wednesdays[1]. Thanks to Trevor for following up on this action > item from the discussions we had in the summit in Boston. > > This change has been made to accommodate some new participants to the > community from Europe and China, and advancing the meeting time by three > hours makes the time more convenient for them and not terrible for the rest > of us. > > The first meeting at this new time[2] will be on this coming Wednesday, > 24th. As always, the meeting agenda can be found at [3]. > > Thanks, > > -amrith > > [1] https://review.openstack.org/#/c/466381/ > [2] http://eavesdrop.openstack.org/#Trove_(DBaaS)_Team_Meeting > [3] https://wiki.openstack.org/wiki/Meetings/TroveMeeting > -- > Amrith Kumar > GPG: 0x5e48849a9d21a29b > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: smime.p7s > Type: application/pkcs7-signature > Size: 4815 bytes > Desc: not available > URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20170521/3657182f/attachment-0001.bin> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > OpenStack-operators mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > ------------------------------ > > End of OpenStack-operators Digest, Vol 79, Issue 28 > ***************************************************
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
