- API v2.0 updates, September 15, 2016
- API v2.0 updates, August 15, 2016
- API v2.0 updates, June 2, 2015
- API v2.0 updates, October 30, 2014
- API v2.0 updates, July 24, 2014
- API v2.0 updates, August 21, 2012
- API v2.0 updates, August 15, 2012
- API v2.0 updates, July 9, 2012
- API v2.0 updates, June 13, 2012
- API v2.0 release, May 1, 2012
For information about using the API, see the documentation overview.
First generation servers are officially end-of-life and references are removed from this document. The term "Next Generation" is now used only in a historical context.
Published scheduler hints. Used when creating servers, a scheduler hint allows
a cloud server to be built near to, or far from, an existing server within a
specific zone. Use either the
``public-zone-ip:far parameter and be sure to use the server`s
ID and not
zone when making the request.
See Scheduler hint extension for more information.
XML examples have been removed. The XML serialization format for API request and response bodies is no longer supported by OpenStack. To stay consistent with OpenStack (and industry trends in general), Rackspace has deprecated the use of XML request and response bodies. New code using the Compute API should not use XML, and current programs using XML should prepare for the end of XML support. The date when Rackspace will remove XML support from the Compute API will be announced soon.
The Performance flavor class was renamed to align with the OnMetal naming style (Compute, Memory, and so on). In summary, the following changes have been made to the flavor classes:
- Two new flavor classes have replaced the Performance flavor classes: General Purpose v1 (like Performance 1 but with combined data and system disk) and IO v1 (like Performance 2).
- Two existing flavors classes (Performance 1 and Performance 2) have been removed from the Cloud Control Panel, but they are still visible in the API.
- Two new flavor classes have been added: Compute v1 and Memory v1.
- At a future date, the Standard, Performance 1, and Performance 2 flavor classes will be discontinued.
OnMetal servers have been introduced. OnMetal extends Rackspace Cloud Servers to support single-tenant, bare-metal, high-end hardware specialized to deliver outstanding performance for the key workloads typically seen in web applications. These servers can be provisioned within minutes via the Cloud Servers API, similar to any other cloud instance.
Significant differences between virtual cloud servers and OnMetal cloud servers are as follows:
- OnMetal servers are created using special flavors and images.
- Private networks are not currently available for OnMetal servers.
- OnMetal servers must be created using key pairs, and the admin password provided at creation should be neither used nor modified.
- Some server actions, like rebuild, resize, rescue, and so on, are not applicable to OnMetal servers.
The tables of images and flavors have been updated.
The new extended status extension displays the virtual machine (VM), task, and power statuses for servers. The extension displays these statuses in the following fields in the response bodies for the operations to list servers and get server details:
||The VM status|
||The task status|
||The power status|
A new authentication endpoint has been added.
To authenticate, you issue a request to the Rackspace Identity Service, which is an implementation of the OpenStack Keystone Identity service v2.0. Customers with UK-based accounts can now issue a POST /tokens request to the Rackspace Identity service at the https://lon.identity.api.rackspacecloud.com/v2.0 endpoint to authenticate access to either the first generation Cloud Servers or next generation Cloud Servers services.
In response to valid credentials, an authentication request to the Rackspace Identity service v2 returns an authentication token and a service catalog.
Both first generation and next generation Cloud Servers services now appear in the service catalog.
In the service catalog, the Cloud Servers services are named as follows:
Cloud Servers generation Service name in the catalog First generation
If you use the authentication token to access this service, you can view and perform first generation Cloud Servers API operations against your first generation servers.
If you use the authentication token to access this service, you can view and perform next generation Cloud Servers API operations against your next generation servers.
Next generation servers might show multiple endpoints to enable regional choice. Select the appropriate endpoint for the region that you want to interact with by examining the
For detailed information about authentication through the Identity service v2.0, see the Rackspace Identity Client Developer Guide.
A new authentication endpoint has been added and changes have been made to the service catalog. For detailed information about authentication through the Identity service v2.0, see the Rackspace Identity API Guide.
- The 256 MB flavor has been removed from the next generation Cloud Servers. While these small instances were appropriate in certain cases, they often caused performance problems for applications and placed undue stress on underlying host machines. This change reduces the number of application performance issues and improves the overall Cloud Servers experience.
- Next generation Cloud Servers now implements a single vCPU allocation scheme across all operating systems. Unlike the earlier vCPU allocation scheme, which was optimized for burst on Linux and for CPU consistency on Windows, the new scheme favors consistent CPU performance while retaining some burst potential. The number of vCPUs is reduced for some flavors and increased for others to simplify Cloud Servers while balancing predictability and value.
- OpenStack ready. Rackspace continuously integrates with OpenStack code, which means that you have nearly immediate access to product enhancements from the OpenStack community.
Corrected a hardware problem that affected performance.
- Version 2.0 of the Rackspace Cloud Servers API uses Open Software Foundation (OSF)
Universally Unique Identifiers (UUIDs) instead of integers for object IDs for images,
servers, and so on. The version 1.0 used integer IDs. For example, an ID in version 1.0
2, while in the API v2, the ID might be
- Third-party clients can now access the server directly through a server access IP address.
- The following Rackspace extensions have been added.
- Bandwidth stats extension, which shows bandwidth usage statistics for a given audit period
- Disk configuration extension, which enables control of how the disk is partitioned when a server is created, rebuilt, or resized
- Rescue mode extension, which creates a new server with the file system for the specified version of Cloud Servers mounted to fix file system and configuration errors
- Used limits extension, which returns the amount of absolute limit capacity that is currently used
- Volume attachment extension, which, in conjunction with Cloud Block Storage API operations, enables you to attach a volume to a server instance, list volume attachments for a server instance, get volume details for a volume attachment, and delete a volume attachment
- Image metadata and metadata management operations have been added.
- IPv6 support has been added. When you create a server, an IPv4 address and an IPv6 address block are assigned. The IPv4 address and IPv6 address block are used for the public interface (Internet). The IPv4 address is also used for the private interface.
- Authentication now occurs through the Rackspace Identity service, which integrates with the Rackspace infrastructure and is a modification of the OpenStack Keystone authentication specification.
- The Rackspace Next Generation Cloud Servers API v2.0 is based on the OpenStack Compute API v2, which differs significantly from the Rackspace First Generation Cloud Servers API v1.0.
- The defaults for rate limits have changed. You can request Rackspace to either raise or lower the limits as needed.
- Red Hat images cannot be registered. Red Hat Network (RHN) registration is required for Red Hat.
- The following version 1 API operations are not yet available in the v2.0
- Shared IP addresses
- Backup schedules
- Resize server down (not supported for Windows Cloud Servers)
- Add an IP address to a cloud server