- Release-team - mailman3.cels.anl.gov

Re: [Release-team] magellan
by Robert Olson 04 Sep '14

04 Sep '14

Then this model of upgrading by mass destruction is badly broken. On Sep 4, 2014, at 3:29 PM, Boisvert, Sebastien <boisvert(a)anl.gov> wrote: > I agree. > > But the thing is that both OpenStack deployment basically use the same storage > hardware, so there is basically not a lot of storage right now in the new cloud (that's what Scott > told me). > > > wait-as-a-service^{TM} > ________________________________________ > From: Robert Olson [olson(a)mcs.anl.gov] > Sent: Thursday, September 04, 2014 3:27 PM > To: Boisvert, Sebastien > Cc: release-team(a)lists.kbase.us > Subject: Re: [Release-team] magellan > > That seems like reason to halt any mass migration off essex. If the new volumes can't be available the new system clearly isn't ready to use. > > On Sep 4, 2014, at 3:26 PM, Boisvert, Sebastien <boisvert(a)anl.gov> wrote: > >> >> I think the waste of time is mostly with volumes. >> >> I migrated one instance, but it is still useless because its 400 GiB volume is not migrated yet >> by the Magellan support. >> >> ________________________________________ >> From: Robert Olson [olson(a)mcs.anl.gov] >> Sent: Thursday, September 04, 2014 3:25 PM >> To: Boisvert, Sebastien >> Cc: release-team(a)lists.kbase.us >> Subject: Re: [Release-team] magellan >> >> Thanks. What this means is that we are going to take downtime for this conversion. What a waste of time. >> >> >> On Sep 4, 2014, at 3:21 PM, Boisvert, Sebastien <boisvert(a)anl.gov> wrote: >> >>> You have to: >>> >>> - stop the instance cleanly in the old OpenStack ("halt" in the shell) >>> - create a snapshot of the root volume of the stopped instance >>> - any snapshop and image is synced automatically to the new OpenStack deployment >>> - in the new OpenStack cloud, boot an instance from the snapshot >>> - associate a IP address >>> - update your DNA A record, if any. >>> >>> >>> ________________________________________ >>> From: release-team-bounces(a)lists.kbase.us [release-team-bounces(a)lists.kbase.us] on behalf of Robert Olson [olson(a)mcs.anl.gov] >>> Sent: Thursday, September 04, 2014 3:13 PM >>> To: release-team(a)lists.kbase.us >>> Subject: [Release-team] magellan >>> >>> I understand that the essex instances are all getting killed tomorrow. Does anyone have experience in directly bringing across instances? I think the production genome annotation is still running there so we may lose it for a while. >>> >>> Who knows what else we may lose as well. >>> >>> >>> _______________________________________________ >>> Release-team mailing list >>> Release-team(a)lists.kbase.us >>> https://lists.kbase.us/mailman/listinfo/release-team >>> >> >> > >

1 0

Re: [Release-team] magellan
by Boisvert, Sebastien 04 Sep '14

04 Sep '14

I agree. But the thing is that both OpenStack deployment basically use the same storage hardware, so there is basically not a lot of storage right now in the new cloud (that's what Scott told me). wait-as-a-service^{TM} ________________________________________ From: Robert Olson [olson(a)mcs.anl.gov] Sent: Thursday, September 04, 2014 3:27 PM To: Boisvert, Sebastien Cc: release-team(a)lists.kbase.us Subject: Re: [Release-team] magellan That seems like reason to halt any mass migration off essex. If the new volumes can't be available the new system clearly isn't ready to use. On Sep 4, 2014, at 3:26 PM, Boisvert, Sebastien <boisvert(a)anl.gov> wrote: > > I think the waste of time is mostly with volumes. > > I migrated one instance, but it is still useless because its 400 GiB volume is not migrated yet > by the Magellan support. > > ________________________________________ > From: Robert Olson [olson(a)mcs.anl.gov] > Sent: Thursday, September 04, 2014 3:25 PM > To: Boisvert, Sebastien > Cc: release-team(a)lists.kbase.us > Subject: Re: [Release-team] magellan > > Thanks. What this means is that we are going to take downtime for this conversion. What a waste of time. > > > On Sep 4, 2014, at 3:21 PM, Boisvert, Sebastien <boisvert(a)anl.gov> wrote: > >> You have to: >> >> - stop the instance cleanly in the old OpenStack ("halt" in the shell) >> - create a snapshot of the root volume of the stopped instance >> - any snapshop and image is synced automatically to the new OpenStack deployment >> - in the new OpenStack cloud, boot an instance from the snapshot >> - associate a IP address >> - update your DNA A record, if any. >> >> >> ________________________________________ >> From: release-team-bounces(a)lists.kbase.us [release-team-bounces(a)lists.kbase.us] on behalf of Robert Olson [olson(a)mcs.anl.gov] >> Sent: Thursday, September 04, 2014 3:13 PM >> To: release-team(a)lists.kbase.us >> Subject: [Release-team] magellan >> >> I understand that the essex instances are all getting killed tomorrow. Does anyone have experience in directly bringing across instances? I think the production genome annotation is still running there so we may lose it for a while. >> >> Who knows what else we may lose as well. >> >> >> _______________________________________________ >> Release-team mailing list >> Release-team(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/release-team >> > >

1 0

Re: [Release-team] magellan
by Nomi L. Harris 04 Sep '14

04 Sep '14

Hey, at least they didn't do it right before (or during) the RSV! Nomi Sent from my iPhone > On Sep 4, 2014, at 1:25 PM, Robert Olson <olson(a)mcs.anl.gov> wrote: > > Thanks. What this means is that we are going to take downtime for this conversion. What a waste of time. > > >> On Sep 4, 2014, at 3:21 PM, Boisvert, Sebastien <boisvert(a)anl.gov> wrote: >> >> You have to: >> >> - stop the instance cleanly in the old OpenStack ("halt" in the shell) >> - create a snapshot of the root volume of the stopped instance >> - any snapshop and image is synced automatically to the new OpenStack deployment >> - in the new OpenStack cloud, boot an instance from the snapshot >> - associate a IP address >> - update your DNA A record, if any. >> >> >> ________________________________________ >> From: release-team-bounces(a)lists.kbase.us [release-team-bounces(a)lists.kbase.us] on behalf of Robert Olson [olson(a)mcs.anl.gov] >> Sent: Thursday, September 04, 2014 3:13 PM >> To: release-team(a)lists.kbase.us >> Subject: [Release-team] magellan >> >> I understand that the essex instances are all getting killed tomorrow. Does anyone have experience in directly bringing across instances? I think the production genome annotation is still running there so we may lose it for a while. >> >> Who knows what else we may lose as well. >> >> >> _______________________________________________ >> Release-team mailing list >> Release-team(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/release-team > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team

1 0

Re: [Release-team] magellan
by Robert Olson 04 Sep '14

04 Sep '14

That seems like reason to halt any mass migration off essex. If the new volumes can't be available the new system clearly isn't ready to use. On Sep 4, 2014, at 3:26 PM, Boisvert, Sebastien <boisvert(a)anl.gov> wrote: > > I think the waste of time is mostly with volumes. > > I migrated one instance, but it is still useless because its 400 GiB volume is not migrated yet > by the Magellan support. > > ________________________________________ > From: Robert Olson [olson(a)mcs.anl.gov] > Sent: Thursday, September 04, 2014 3:25 PM > To: Boisvert, Sebastien > Cc: release-team(a)lists.kbase.us > Subject: Re: [Release-team] magellan > > Thanks. What this means is that we are going to take downtime for this conversion. What a waste of time. > > > On Sep 4, 2014, at 3:21 PM, Boisvert, Sebastien <boisvert(a)anl.gov> wrote: > >> You have to: >> >> - stop the instance cleanly in the old OpenStack ("halt" in the shell) >> - create a snapshot of the root volume of the stopped instance >> - any snapshop and image is synced automatically to the new OpenStack deployment >> - in the new OpenStack cloud, boot an instance from the snapshot >> - associate a IP address >> - update your DNA A record, if any. >> >> >> ________________________________________ >> From: release-team-bounces(a)lists.kbase.us [release-team-bounces(a)lists.kbase.us] on behalf of Robert Olson [olson(a)mcs.anl.gov] >> Sent: Thursday, September 04, 2014 3:13 PM >> To: release-team(a)lists.kbase.us >> Subject: [Release-team] magellan >> >> I understand that the essex instances are all getting killed tomorrow. Does anyone have experience in directly bringing across instances? I think the production genome annotation is still running there so we may lose it for a while. >> >> Who knows what else we may lose as well. >> >> >> _______________________________________________ >> Release-team mailing list >> Release-team(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/release-team >> > >

1 0

Re: [Release-team] magellan
by Boisvert, Sebastien 04 Sep '14

04 Sep '14

This is a very clear use case for DNS. But there is no DNS as a Service in Magellan yet. ________________________________________ From: Robert Olson [olson(a)mcs.anl.gov] Sent: Thursday, September 04, 2014 3:26 PM To: Boisvert, Sebastien Cc: release-team(a)lists.kbase.us Subject: Re: [Release-team] magellan This also means that the production services that point to any magellan instances will need to be updated as I suspect I won't be able to reassign to the same IP address. On Sep 4, 2014, at 3:25 PM, Robert Olson <olson(a)mcs.anl.gov> wrote: > Thanks. What this means is that we are going to take downtime for this conversion. What a waste of time. > > > On Sep 4, 2014, at 3:21 PM, Boisvert, Sebastien <boisvert(a)anl.gov> wrote: > >> You have to: >> >> - stop the instance cleanly in the old OpenStack ("halt" in the shell) >> - create a snapshot of the root volume of the stopped instance >> - any snapshop and image is synced automatically to the new OpenStack deployment >> - in the new OpenStack cloud, boot an instance from the snapshot >> - associate a IP address >> - update your DNA A record, if any. >> >> >> ________________________________________ >> From: release-team-bounces(a)lists.kbase.us [release-team-bounces(a)lists.kbase.us] on behalf of Robert Olson [olson(a)mcs.anl.gov] >> Sent: Thursday, September 04, 2014 3:13 PM >> To: release-team(a)lists.kbase.us >> Subject: [Release-team] magellan >> >> I understand that the essex instances are all getting killed tomorrow. Does anyone have experience in directly bringing across instances? I think the production genome annotation is still running there so we may lose it for a while. >> >> Who knows what else we may lose as well. >> >> >> _______________________________________________ >> Release-team mailing list >> Release-team(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/release-team >> > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team

1 0

Re: [Release-team] magellan
by Thomas Brettin 04 Sep '14

04 Sep '14

That’s right, i already checked on the IPs On Sep 4, 2014, at 4:26 PM, Robert Olson <olson(a)mcs.anl.gov> wrote: > This also means that the production services that point to any magellan instances will need to be updated as I suspect I won't be able to reassign to the same IP address. > > On Sep 4, 2014, at 3:25 PM, Robert Olson <olson(a)mcs.anl.gov> wrote: > >> Thanks. What this means is that we are going to take downtime for this conversion. What a waste of time. >> >> >> On Sep 4, 2014, at 3:21 PM, Boisvert, Sebastien <boisvert(a)anl.gov> wrote: >> >>> You have to: >>> >>> - stop the instance cleanly in the old OpenStack ("halt" in the shell) >>> - create a snapshot of the root volume of the stopped instance >>> - any snapshop and image is synced automatically to the new OpenStack deployment >>> - in the new OpenStack cloud, boot an instance from the snapshot >>> - associate a IP address >>> - update your DNA A record, if any. >>> >>> >>> ________________________________________ >>> From: release-team-bounces(a)lists.kbase.us [release-team-bounces(a)lists.kbase.us] on behalf of Robert Olson [olson(a)mcs.anl.gov] >>> Sent: Thursday, September 04, 2014 3:13 PM >>> To: release-team(a)lists.kbase.us >>> Subject: [Release-team] magellan >>> >>> I understand that the essex instances are all getting killed tomorrow. Does anyone have experience in directly bringing across instances? I think the production genome annotation is still running there so we may lose it for a while. >>> >>> Who knows what else we may lose as well. >>> >>> >>> _______________________________________________ >>> Release-team mailing list >>> Release-team(a)lists.kbase.us >>> https://lists.kbase.us/mailman/listinfo/release-team >>> >> >> _______________________________________________ >> Release-team mailing list >> Release-team(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/release-team > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team

1 0

Re: [Release-team] magellan
by Boisvert, Sebastien 04 Sep '14

04 Sep '14

I think the waste of time is mostly with volumes. I migrated one instance, but it is still useless because its 400 GiB volume is not migrated yet by the Magellan support. ________________________________________ From: Robert Olson [olson(a)mcs.anl.gov] Sent: Thursday, September 04, 2014 3:25 PM To: Boisvert, Sebastien Cc: release-team(a)lists.kbase.us Subject: Re: [Release-team] magellan Thanks. What this means is that we are going to take downtime for this conversion. What a waste of time. On Sep 4, 2014, at 3:21 PM, Boisvert, Sebastien <boisvert(a)anl.gov> wrote: > You have to: > > - stop the instance cleanly in the old OpenStack ("halt" in the shell) > - create a snapshot of the root volume of the stopped instance > - any snapshop and image is synced automatically to the new OpenStack deployment > - in the new OpenStack cloud, boot an instance from the snapshot > - associate a IP address > - update your DNA A record, if any. > > > ________________________________________ > From: release-team-bounces(a)lists.kbase.us [release-team-bounces(a)lists.kbase.us] on behalf of Robert Olson [olson(a)mcs.anl.gov] > Sent: Thursday, September 04, 2014 3:13 PM > To: release-team(a)lists.kbase.us > Subject: [Release-team] magellan > > I understand that the essex instances are all getting killed tomorrow. Does anyone have experience in directly bringing across instances? I think the production genome annotation is still running there so we may lose it for a while. > > Who knows what else we may lose as well. > > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team >

1 0

Re: [Release-team] magellan
by Robert Olson 04 Sep '14

04 Sep '14

This also means that the production services that point to any magellan instances will need to be updated as I suspect I won't be able to reassign to the same IP address. On Sep 4, 2014, at 3:25 PM, Robert Olson <olson(a)mcs.anl.gov> wrote: > Thanks. What this means is that we are going to take downtime for this conversion. What a waste of time. > > > On Sep 4, 2014, at 3:21 PM, Boisvert, Sebastien <boisvert(a)anl.gov> wrote: > >> You have to: >> >> - stop the instance cleanly in the old OpenStack ("halt" in the shell) >> - create a snapshot of the root volume of the stopped instance >> - any snapshop and image is synced automatically to the new OpenStack deployment >> - in the new OpenStack cloud, boot an instance from the snapshot >> - associate a IP address >> - update your DNA A record, if any. >> >> >> ________________________________________ >> From: release-team-bounces(a)lists.kbase.us [release-team-bounces(a)lists.kbase.us] on behalf of Robert Olson [olson(a)mcs.anl.gov] >> Sent: Thursday, September 04, 2014 3:13 PM >> To: release-team(a)lists.kbase.us >> Subject: [Release-team] magellan >> >> I understand that the essex instances are all getting killed tomorrow. Does anyone have experience in directly bringing across instances? I think the production genome annotation is still running there so we may lose it for a while. >> >> Who knows what else we may lose as well. >> >> >> _______________________________________________ >> Release-team mailing list >> Release-team(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/release-team >> > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team

1 0

Re: [Release-team] magellan
by Robert Olson 04 Sep '14

04 Sep '14

Thanks. What this means is that we are going to take downtime for this conversion. What a waste of time. On Sep 4, 2014, at 3:21 PM, Boisvert, Sebastien <boisvert(a)anl.gov> wrote: > You have to: > > - stop the instance cleanly in the old OpenStack ("halt" in the shell) > - create a snapshot of the root volume of the stopped instance > - any snapshop and image is synced automatically to the new OpenStack deployment > - in the new OpenStack cloud, boot an instance from the snapshot > - associate a IP address > - update your DNA A record, if any. > > > ________________________________________ > From: release-team-bounces(a)lists.kbase.us [release-team-bounces(a)lists.kbase.us] on behalf of Robert Olson [olson(a)mcs.anl.gov] > Sent: Thursday, September 04, 2014 3:13 PM > To: release-team(a)lists.kbase.us > Subject: [Release-team] magellan > > I understand that the essex instances are all getting killed tomorrow. Does anyone have experience in directly bringing across instances? I think the production genome annotation is still running there so we may lose it for a while. > > Who knows what else we may lose as well. > > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team >

1 0

Re: [Release-team] magellan
by Robert Olson 04 Sep '14

04 Sep '14

And from the source >> From: Scott Devoid <devoid(a)anl.gov> >> Subject: Re: [magellan-support #226803] instances being killed >> Date: September 4, 2014 at 3:22:01 PM CDT >> To: Magellan Support <magellan-support(a)rt.mcs.anl.gov>, Robert Olson <olson(a)mcs.anl.gov> >> >> Hey, >> >> Yes, we're killing off all instances tomorrow (we sent several >> messages since mid-July about impending doom). >> >> We're currently sync-ing snapshots from Essex to Havana every 10 or 15 >> minutes. So if you create a snapshot today, it'll show up on Havana >> pretty quickly. On Sep 4, 2014, at 3:15 PM, Thomas Brettin <brettin(a)anl.gov> wrote: > Where did you learn this from? > > > On Sep 4, 2014, at 4:13 PM, Robert Olson <olson(a)mcs.anl.gov> wrote: > >> I understand that the essex instances are all getting killed tomorrow. Does anyone have experience in directly bringing across instances? I think the production genome annotation is still running there so we may lose it for a while. >> >> Who knows what else we may lose as well. >> >> >> _______________________________________________ >> Release-team mailing list >> Release-team(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/release-team >

1 0