An "inactive" server is a definition of a server that has not been launched. Perhaps the server has never been launched or the previous incarnation of that server was terminated or stopped. Current (active) servers also have the notion of an inactive server, which can be accessed in the history timeline bar under the "Next" server option.
If a server has not been launched you can change all of its configurations because a corresponding virtual instance does not exist. However, if a server is operational and has a virtual instance that's running in the cloud, you are fairly limited in what you can change because a virtual instance has already been launched and configured. See Managing Active (Current) Servers.
The majority of a server's configuration settings can be edited under its Info tab. Remember, most of a server's configuration settings are inherited from either its ServerTemplate or Deployment. However, you do have the flexibility to overwrite any of the settings listed below at the server level. Although the ability to modify a server's configuration at the server level is allowed to give you more design flexibility it should only be used under unique circumstances. If you are following best practices, a server's configuration should always inherit its settings from either the ServerTemplate or Deployment in order to promote consistency and repeatability. You should only update a server's configuration at the server level for development and testing purposes.
You can perform any of these modifications/actions on an inactive server. A server's configuration can be modified under its Info tab. Click Edit. See details below.
* EC2 only
© 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.