Ask Your Question

Revision history [back]

Hi,

The best approach I'm aware of is to setup a new havana-based cloud right beside the old one (pull nodes off the old one, if needed, to give the new one enough resources) - and then migrate your application workloads over to the new cloud.

This way, you're not really caring about the cloud instances themselves. They were just workers - so you replace them with new workers in the new cloud, doing the same job for your end users that the old workers were doing.

With puppet and friends it's possible to deploy production nodes "hands off" - i.e. no human ever logs in on them. Very possibly you could use the same puppet deployment scripts with Havana that you may have originally targetted to Essex.

Also, LBaaS can help minimize the impact of switchover. Hope this helps!

Hi,

The best approach I'm aware of is to setup a new havana-based cloud right beside the old one (pull nodes off the old one, if needed, to give the new one enough resources) - and then migrate your application workloads over to the new cloud.

This way, you're not really caring about the cloud instances themselves. They were just workers - so you replace them with new workers in the new cloud, doing the same job for your end users that the old workers were doing.

With puppet and friends it's possible to deploy production nodes "hands off" - i.e. no human ever logs in on them. Very possibly you could use the same puppet deployment scripts with Havana that you may have originally targetted to Essex.

Also, LBaaS can help minimize the impact of switchover. Hope this helps!