This is a very clear use case for DNS. But there is no DNS as a Service in Magellan yet. ________________________________________ From: Robert Olson [[email protected]] Sent: Thursday, September 04, 2014 3:26 PM To: Boisvert, Sebastien Cc: [email protected] 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 <[email protected]> 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 <[email protected]> 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: [email protected] [[email protected]] on behalf of Robert Olson [[email protected]] Sent: Thursday, September 04, 2014 3:13 PM To: [email protected] 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 [email protected] https://lists.kbase.us/mailman/listinfo/release-team
_______________________________________________ Release-team mailing list [email protected] https://lists.kbase.us/mailman/listinfo/release-team