You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Carlos Reategui <ca...@reategui.com> on 2013/08/08 02:21:08 UTC

Physically moving an installation

This is probably more of a question for the XS forums but thought I'd get
you alls perspective too.
We are moving buildings and need to move our CS + XS hardware.  What it the
recommended way to do that?

I was thinking of the following steps:
1) stop the CS management server
2) pause/stop every VM using XenCenter (CS system VMs last?)
3) shutdown XS hosts
4) shutdown Management Server host (also NFS server)
5) move
On the other end I would:
1) boot Management Server Host (make sure CS Management Server is stopped,
and NFS is up)
2) boot XS hosts
3) Use XenCenter to start all VMs (CS system vms first?)
4) Start CS Management Server

Anything I am missing?

thanks,
Carlos

Re: Physically moving an installation

Posted by Carlos Reategui <ca...@reategui.com>.
Thanks for the suggestions.  Move is not for another month. Going to do a
dry run next week.


On Wed, Aug 7, 2013 at 7:24 PM, Geoff Higginbottom <
geoff.higginbottom@shapeblue.com> wrote:

> Kirk is right, us CS to shutdown all VMs, this will remove any VM to Host
> mapping and ensure all VMs are safely stored on storage.
>
> I would seriously consider taking a backup of storage before moving it as
> you never know someone could drop the chassis etc.
>
> Once all VMs are stopped, place all storage into maintenance mode, then do
> the same with Hosts, this will ensure all System VMs are stopped.
>
> You can then shutdown your CS and DB nodes, hosts and storage.
>
> Once everything is in its new home, bring storage online, then hosts and
> do some basic tests before powering on the DB and CS nodes.
>
> Once DB and CS nodes are online, bring storage and a couple of Hosts out
> of maintenance mode and ensure System VMs come online and function
> correctly.  Test importing / exporting templates etc to test all network
> components.
>
> Once you are happy everything is working OK, bring remaining hosts out of
> maintenance and start to bring your Guest VMs online, but do so in small
> batches and test to make sure everything is performing normally etc.
>
> Regards
>
> Geoff Higginbottom
>
> D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
>
> geoff.higginbottom@shapeblue.com
>
> -----Original Message-----
> From: Kirk Jantzer [mailto:kirk.jantzer@gmail.com]
> Sent: 07 August 2013 20:29
> To: Cloudstack users mailing list
> Subject: Re: Physically moving an installation
>
> I would use CS to shutdown all instances. Then shutdown the management
> server, then hosts, then reverse it on the other end. But wait for others
> to chime in before moving forward.
>
> Regards,
>
> Kirk Jantzer
> http://about.me/kirkjantzer
> On Aug 7, 2013 8:21 PM, "Carlos Reategui" <ca...@reategui.com> wrote:
>
> > This is probably more of a question for the XS forums but thought I'd
> > get you alls perspective too.
> > We are moving buildings and need to move our CS + XS hardware.  What
> > it the recommended way to do that?
> >
> > I was thinking of the following steps:
> > 1) stop the CS management server
> > 2) pause/stop every VM using XenCenter (CS system VMs last?)
> > 3) shutdown XS hosts
> > 4) shutdown Management Server host (also NFS server)
> > 5) move
> > On the other end I would:
> > 1) boot Management Server Host (make sure CS Management Server is
> > stopped, and NFS is up)
> > 2) boot XS hosts
> > 3) Use XenCenter to start all VMs (CS system vms first?)
> > 4) Start CS Management Server
> >
> > Anything I am missing?
> >
> > thanks,
> > Carlos
> >
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is
> operated under license from Shape Blue Ltd. ShapeBlue is a registered
> trademark.
>

RE: Physically moving an installation

Posted by Geoff Higginbottom <ge...@shapeblue.com>.
Kirk is right, us CS to shutdown all VMs, this will remove any VM to Host mapping and ensure all VMs are safely stored on storage.

I would seriously consider taking a backup of storage before moving it as you never know someone could drop the chassis etc.

Once all VMs are stopped, place all storage into maintenance mode, then do the same with Hosts, this will ensure all System VMs are stopped.

You can then shutdown your CS and DB nodes, hosts and storage.

Once everything is in its new home, bring storage online, then hosts and do some basic tests before powering on the DB and CS nodes.

Once DB and CS nodes are online, bring storage and a couple of Hosts out of maintenance mode and ensure System VMs come online and function correctly.  Test importing / exporting templates etc to test all network components.

Once you are happy everything is working OK, bring remaining hosts out of maintenance and start to bring your Guest VMs online, but do so in small batches and test to make sure everything is performing normally etc.

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbottom@shapeblue.com

-----Original Message-----
From: Kirk Jantzer [mailto:kirk.jantzer@gmail.com]
Sent: 07 August 2013 20:29
To: Cloudstack users mailing list
Subject: Re: Physically moving an installation

I would use CS to shutdown all instances. Then shutdown the management server, then hosts, then reverse it on the other end. But wait for others to chime in before moving forward.

Regards,

Kirk Jantzer
http://about.me/kirkjantzer
On Aug 7, 2013 8:21 PM, "Carlos Reategui" <ca...@reategui.com> wrote:

> This is probably more of a question for the XS forums but thought I'd
> get you alls perspective too.
> We are moving buildings and need to move our CS + XS hardware.  What
> it the recommended way to do that?
>
> I was thinking of the following steps:
> 1) stop the CS management server
> 2) pause/stop every VM using XenCenter (CS system VMs last?)
> 3) shutdown XS hosts
> 4) shutdown Management Server host (also NFS server)
> 5) move
> On the other end I would:
> 1) boot Management Server Host (make sure CS Management Server is
> stopped, and NFS is up)
> 2) boot XS hosts
> 3) Use XenCenter to start all VMs (CS system vms first?)
> 4) Start CS Management Server
>
> Anything I am missing?
>
> thanks,
> Carlos
>
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Physically moving an installation

Posted by Kirk Jantzer <ki...@gmail.com>.
I would use CS to shutdown all instances. Then shutdown the management
server, then hosts, then reverse it on the other end. But wait for others
to chime in before moving forward.

Regards,

Kirk Jantzer
http://about.me/kirkjantzer
On Aug 7, 2013 8:21 PM, "Carlos Reategui" <ca...@reategui.com> wrote:

> This is probably more of a question for the XS forums but thought I'd get
> you alls perspective too.
> We are moving buildings and need to move our CS + XS hardware.  What it the
> recommended way to do that?
>
> I was thinking of the following steps:
> 1) stop the CS management server
> 2) pause/stop every VM using XenCenter (CS system VMs last?)
> 3) shutdown XS hosts
> 4) shutdown Management Server host (also NFS server)
> 5) move
> On the other end I would:
> 1) boot Management Server Host (make sure CS Management Server is stopped,
> and NFS is up)
> 2) boot XS hosts
> 3) Use XenCenter to start all VMs (CS system vms first?)
> 4) Start CS Management Server
>
> Anything I am missing?
>
> thanks,
> Carlos
>