The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Step 1 | In Rackspace, create a public cloud account. |
Step 2 | Note down the following information about the Rackspace account: |
Step 3 | In Rackspace, add the desired operating system images to the account. |
Step 4 | If you connect through a proxy server, configure the proxy server settings in the run.sh file in the Cisco UCS Director VM. |
Step 5 | In Cisco UCS Director, create a virtual account for the Rackspace cloud account. |
Step 6 | Create a Rackspace deployment policy. |
Step 7 | (Optional)If you want to
set up a chargeback for end-users, define a public cloud cost model in the
Cisco UCS Director chargeback module.
For more information, see the Cisco UCS Director Administration Guide. |
Step 8 | Create a virtual
data center (vDC) for the Rackspace cloud account.
For more information, see the Cisco UCS Director Administration Guide. |
Step 9 | Add a catalog
for each operating system image that you want to make available to end users.
For more information, see the Cisco UCS Director Administration Guide. |
Step 10 | In the
Self-Service Portal,
provision a VM through a service request.
For more information, see the Cisco UCS Director Administration Guide or the Cisco UCS Director Self-Service Portal Guide. |
Cisco UCS Director tests the connection to the Rackspace cloud. If that test is successful, it adds the Rackspace cloud account. This discovery process and inventory may take a few minutes.
The Rackspace deployment policy determines the actions that are performed when a user creates a VM in the cloud through the Self-Service Portal.
Create a Rackspace cloud account.
Cisco UCS Director does not host operating system images for a Rackspace cloud account. The images must already exist in Rackspace. Then Cisco UCS Director performs an inventory collection from the Rackspace account to make them available for catalogs.
Step 1 | On the menu bar, choose . | ||||||||||||||||
Step 2 | In the left pane, expand the pod and then click the Rackspace cloud account. | ||||||||||||||||
Step 3 | In the right
pane, click one of the following tabs to monitor the account:
| ||||||||||||||||
Step 4 | If desired, you
can click the icons on the table bar to customize the table columns, filter the
results, or export a report of the current table contents.
For more information, see the Cisco UCS Director Administration Guide. |
In addition to these reports, you can also create Cloudsense Analytics for VMs and other items, as described in the Cisco UCS Director Administration Guide.
Step 1 | On the menu bar, choose . | ||||||||||
Step 2 | In the left pane, expand the pod and then click the Rackspace cloud account. | ||||||||||
Step 3 | In the right
pane, click one of the following tabs to view reports about the account:
| ||||||||||
Step 4 | For some
reports, you can click the icons on the table bar to customize the table
columns, filter the results, or export a report of the current table contents.
For more information, see the Cisco UCS Director Administration Guide. |