Virtual Appliance Overview
Virtual Appliance Overview
The only way to install the CloudCenter Suite is to use the virtual appliance Installer method. Cisco builds these appliances on CentOS 7.x base images.
Installers are already incorporated in the CloudCenter Suite SaaS offer, see SaaS Access for additional details.
General Virtual Appliance Approach
To prepare infrastructure for the appliance approach, follow this process.
Review and ensure that you have met the requirements to Prepare Infrastructure before installing the CloudCenter Suite.
Review the list of Supported Suite Installers to verify the supported Virtual Appliances.
Navigate to software.cisco.com to download virtual appliances for each supported cloud.
Follow directions as specified in the table below to obtain and import each image.
Shared image (AMI)
Obtain launch permissions for the AWS account. Refer to the AWS documentation for additional context.
Request image sharing for the AWS account by opening a CloudCenter Support case (https://mycase.cloudapps.cisco.com/case or http://www.cisco.com/c/en/us/support/index.html). In your request, specify the following details:
Your AWS account number
Your CloudCenter Suite version
Your Customer ID (CID)
Your customer name
Specify if your setup is in production or for a POC
You Contact Email address
Downloaded Virtual Appliance
(VHD from the ZIP folder)
Create a new Azure image using the provided VHD file provided by Cisco and launch a VM using that image. Refer to the Azure documentation for additional context.
Create a new GCP image using the provided VHD provided by Cisco and launch a VM using that image. Refer to the GCP documentation for additional context
Downloaded Virtual Appliance (QCOW2)
Import the QCOW2 image file using the OpenStack client. Refer to the OpenStack Documentation for additional context.
Downloaded Virtual Appliance (OVA)
Follow this procedure:
- Download the OVA image.
Import the OVA to your vSphere environment by using the vSphere client
- When you import the OVA as a VM, ensure that it is powered off on vSphere.
- If your environment requires a static IP, use a VMware Customization Spec to manually configure the static IP for the installer VM.
A default password is required to ensure access to the VM using the console (in case the SSH has issues).
If you provide a default password or public-key, be aware of the following requirements:
- The login user is the cloud-user.
- If you configure a default password or public key in the VM, you must also configure the default instance ID and hostname fields as they are dependent and required fields.
Use this password to access the VM via vSphere console.
You cannot use this password to SSH into the launched VMs.
- Select the required Network for the interface to be connected.
Convert the VM to a template.
You must convert the VM to template and then create a VM from this template, so that the template can be used when installing a VMware data center. If you do not provide the template name when installing a VMware data center, your installation will fail.
- Select the template created in the previous step and clone to Virtual Machine, to launch the installer VM. This template will also be used as the value for the vSphere Template Name cloud setting, in the installer UI.
- After the VM is created from the template, power it on. To access the UI, go to the newly created VM IP using HTTPS protocol in a supported browser (see Browser Compatibility).
Launch the installer instance using the image.
The per-cloud setup procedures are only listed below to serve as sample setup scenarios.
- No labels