Release Notes#
Learn about new features, enhancements, known issues, resolved issues, and other important details about Rackspace Cloud Networks API 2.0 service updates.
Note
For information about using the API, see the documentation overview.
API v2.0 updates, February 07, 2017#
What’s new#
The Cloud Networks API v2.0 no longer includes floating IP Address functionality.
Resolved issues#
None for this release
Known issues#
None for this release
API v2.0 updates, August 15, 2016#
What’s new#
The Cloud Networks API v2.0 now includes operations for shared IP addresses. These operations, described in detail in the Cloud Networks API Developer Guide (see Shared IP operations), allow you to manage and associate shared ip addresses. To get started using shared IP addresses, see Sharing IP address between servers. To learn more about shared IP addresses, see Shared IP addresses concepts.
The shared IP address API is currently in Limited Availability. It is available to Managed Infrastructure customers and Managed Operations customers. To use this feature, contact Rackspace Support.
Resolved issues#
None for this release
Known issues#
None for this release
API v2.0 updates, July 25, 2016#
What’s new#
The Cloud Networks API v2.0 now includes operations for floating IP addresses. These operations, described in detail in the Cloud Networks API Developer Guide, allow you to create, read, update, and delete floating ip addresses.
Resolved issues#
None for this release
Known issues#
API v2.0 updates, March 24, 2015#
What’s new#
The Cloud Networks API v2.0 now includes operations for security groups and security group rules. These operations, described in detail in the Cloud Networks API Developer Guide (see Security groups operations ), allow you to create, read, update, and delete security groups and security group rules. You can add rules to the security groups, and, using the port API operations, assign the groups to servers to manage the ingress (inbound) traffic for a port on a server.
Resolved issues#
None for this release
Known issues#
None for this release
API v2.0 updates, March 19, 2015#
What’s new#
The Cloud Networks Getting Started Guide now includes installation instructions and usage examples for the neutron client. The neutron client provides a simple, command-line interface to the Cloud Networks API, similar to the nova client for Cloud Servers and the trove client for Cloud Databases. All these clients are actually executing cURL operations in the background.
Resolved issues#
None for this release
Known issues#
None for this release
API v2.0 release, September 30, 2014#
The Cloud Networks service was originally released using the OpenStack Nova-Network API, and its operations are detailed in the Network extension.
Now Rackspace Cloud Networks has been released using the OpenStack Neutron API v2.0, and its operations are detailed in this guide. We recommend that you use the Neutron API operations even though the Nova-Network API operations still work. For information that helps you determine which method is better for you, see Networking: neutron versus nova-network.
What’s new#
A network is an isolated virtual layer-2 broadcast domain that is typically reserved for the tenant who created it, unless the network is configured to be shared. Tenants can create up to 10 networks per region.
In the Networks API v2.0, the network is the main entity. Ports and subnets are always associated with a network.
A subnet represents an IP address block that can be used to assign IP addresses to virtual instances. Each subnet must have a CIDR and must be associated with a network. IP addresses can be selected either from the whole subnet CIDR or from allocation pools that can be specified by the user.
A subnet can also optionally have a gateway, a list of DNS name servers, and host routes. This information is pushed to the cloud servers whose ports are associated with the subnet, as long as the ports or servers were created after the subnet was created.
A port represents a virtual switch port on a logical network switch. Cloud servers attach their interfaces into ports. The logical port also defines the MAC address and the IP addresses, to be assigned to the interfaces that are plugged into them. When IP addresses are associated with a port, the port is associated with a subnet, because the IP address was taken from the allocation pool for a specific subnet.
Resolved issues#
None for this release
Known issues#
None for this release