To move a Server to a different Deployment.
Table of Contents
Before you move a Server, it's important to fully understand its ramifications. Remember, a Deployment is a RightScale-specific concept. Deployments provide a means of logically grouping a set of Servers together. Typically, you'll create a separate Deployment for each project in your RightScale account. Servers within a Deployment will inherit any input parameters that have been defined at the Deployment level unless they are overwritted at the Server or Server Array levels. As a best practice, we strongly recommend that all inputs be defined at either the ServerTemplate or Depoyments levels. (See Understanding Inputs.) Therefore, due to the laws of input inheritance, when you move a Server from one Deployment to the next, it may inherit different input parameters.
You can move both active and inactive Servers. Remember, you're not physically moving a Server from one cloud to the next. When you move a Server you're only changing the Deployment with which it's associated. In addition, it is possible to move a raw server instance to 'no deployment' which causes the server to be removed from the deployment it is currently associated with.
Moving an Active (Operational) Server
When you move an active, running Server, none of its current configurations will be changed. However, it's important that you understand which of its inputs are being inherited from the Deployment level, because any script that is run after the Server has been moved will get its input parameter(s) from the the new Deployment. Also, if the Server is relaunched, it may be configured completely different the next time it's launched depending on what input parameters are inherited from the Deployment level.
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.