You might need to stop a cloud server for multiple reasons, including the following ones:
To test your disaster recovery procedures
To upgrade a server by creating a new server but leaving the old one in a stopped state
To determine whether the server is still actively in use
To assist with data recovery
You can use the Cloud Server Application Programmer Interface (API) by using a cURL® command, a script, or the interactive website application, Pitchfork. To learn more about Pitchfork, see Pitchfork - the Rackspace Cloud API web application to.
To use Pitchfork to stop a server, perform the following steps:
Log in to Pithfork and enter your credentials. If you don’t know how to find your credentials, see View and reset your API key.
Under Available Product, click Cloud Server.
Scroll down to Stop Server in the Server Actions section.
Click on Details.
Insert the server instance UUID, which you can find in the Cloud Control Panel.
Click Mock API Call.
This command stops the server, and the server no longer accepts connections.
Note: Rackspace continues to bill the owner of the server continues even if a server is stopped. To stop getting billed, delete the server.
To reactivate a server in stopped state, contact Rackspace Support, or send us a ticket with the re-activation request.