RackConnect v2.0 Compatibility with Cloud Server Images
APPLIES TO: RackConnect v2.0
For the Rackspace Open Cloud offering, the image list for RackConnect customers with Managed Infrastructure has been simplified. As long as your RackConnect implementation is complete, you can select from any of the base images displayed in your image list (via the API, MyRackspace Portal, or the Cloud Control Panel), and we can configure RackConnect on your cloud servers. This is now true for Windows and Linux images, as well as for Managed Operations Service Level and Managed Infrastructure customers.
IMPORTANT NOTE: The MyRackspace Portal and Cloud Control Panel allow you to choose the flavor of server that you want to provision. You can choose from standard and workload-optimized flavors, as shown in the following figure. When creating new Cloud Servers, always be sure to select the region where your RackConnect configuration is located.
Cloud Servers API “access IP”
The access IP is the IP address used by RackConnect Automation to access the server. This value is accessible via the API. It is already part of the MyRackspace Portal and is being added to the Cloud Control Panel soon. At the time a server is built, it is populated with the public IP address of the server. In the case of a Cloud Server connected through RackConnect , the RackConnect automation updates the access IP to reflect the public IP assigned through Network Address Translation (NAT) through the RackConnect Edge Network Device.
Note: There are accessIPv4 and accessIPv6 values in the API. RackConnect continues to be an IPv4-only solution, so only accessIPv4 reflects a value after the RackConnect automation has performed its post-build updates. Because these values can be updated via the public API, it is possible (although not recommended) for you to modify the values.
RackConnect Compatibility with Standard Cloud Server Images <---Previous | Next ---> The RackConnect API
© 2015 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
See license specifics and DISCLAIMER