Installing And Configuring VCloud Connector - VCloud .

2y ago
50 Views
2 Downloads
1.25 MB
94 Pages
Last View : 2d ago
Last Download : 9m ago
Upload by : Halle Mcleod
Transcription

Installing and Configuring vCloudConnectorvCloud Connector 2.5.0This document supports the version of each product listed andsupports all subsequent versions until the document isreplaced by a new edition. To check for more recent editionsof this document, see http://www.vmware.com/support/pubs.EN-001127-02

Installing and Configuring vCloud ConnectorYou can find the most up-to-date technical documentation on the VMware Web site at:http://www.vmware.com/support/The VMware Web site also provides the latest product updates.If you have comments about this documentation, submit your feedback to:docfeedback@vmware.comCopyright 2011–2013 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright andintellectual property laws. VMware products are covered by one or more patents listed athttp://www.vmware.com/go/patents.VMware is a registered trademark or trademark of VMware, Inc. in the United States and other jurisdictions. All other marksand names mentioned herein may be trademarks of their respective companies.VMware, Inc.3401 Hillview Ave.Palo Alto, CA 94304www.vmware.com2VMware, Inc.

ContentsInstalling and Configuring vCloud Connector 51 vCloud Connector Editions 72 vCloud Connector Overview 9vCloud Connector 9Planning Your vCloud Connector Installation 103 Installing vCloud Connector 13Collect Necessary Information 14Check System Requirements 16Download the vCloud Connector Virtual Appliances 18Install vCloud Connector Server 18Configure vCloud Connector Server 29Install vCloud Connector Nodes 32Register vCloud Connector Nodes with Clouds 43Configure vCloud Connector Nodes 44Register vCloud Connector Nodes with vCloud Connector Server 49Register the vCloud Connector UI 504 Entering the License Key for vCloud Connector Advanced Edition 535 Deploying Multi-tenant Nodes as a vCloud Service Provider 556 Using Service Provider Multi-tenant Nodes 57Use Service Provider Nodes 57Use vCloud Hybrid Service Multi-tenant Nodes 57Accessing Log Files for Multi-tenant Nodes 607 Selecting Copy Options 61About vCloud Connector Copy 61Compatibility with Earlier Versions of vCloud Connector 62Data Transfer Protocols for Copy 62Data Encryption 64Set UDT Properties 66Using Proxy Servers 66Firewall Rules for UDT Copy Between Private and Public Clouds698 Preparing vCloud Connector for Production Use 71Add Valid SSL Certificates 71Upload Certificates from the Command Line 74VMware, Inc.3

Installing and Configuring vCloud ConnectorAdd CA Root Certificate to Trusted Keystore 75Configure vCloud Connector Node Allocated Storage 76Increase Maximum Concurrent Tasks 779 Cross-Cloud Data Transfer and Network Connectivity 7910 Uninstalling vCloud Connector 81Uninstall a vCloud Connector Server 81Uninstall vCloud Connector Nodes 8211 Upgrading to vCloud Connector 2.5 85Use the Admin Web Console to Upgrade to vCloud Connector 2.5 85Update Registration with vSphere Client 8612 Troubleshooting vCloud Connector 87Troubleshooting Storage 87Troubleshooting Connectivity 88Accessing Log Files from the UI 88Accessing Log Files from the Console 89Accessing Log Files for Multi-tenant Nodes 90Troubleshooting Log File Size 90Using Fully Qualified Domain Names (FQDNs) 91Index493VMware, Inc.

Installing and Configuring vCloud Connector Installing and Configuring vCloud Connector provides a brief overview of VMware vCloud Connector . Italso provides detailed information on installing and configuring vCloud Connector server and vCloudConnector nodes and setting up the vCloud Connector UI .Intended AudienceThis information is intended for anyone who wants to set up vCloud Connector. You should be familiar with VMware vSphere Client , VMware vCloud Director , and deploying virtual appliances.VMware, Inc.5

Installing and Configuring vCloud Connector6VMware, Inc.

1vCloud Connector Editions vCloud Connector 2.5 has two editions: VMware vCloud Connector 2.5 Core and VMware vCloudConnector 2.5 Advanced. vCloud Connector 2.5 Advanced requires a valid VMware vCloud Suite 5.1 or 5.5 license key to enable itsfeatures. In addition to vCloud Connector 2.5 Core features, it includes these advanced features.Content SyncnnStretch Deploy (also referred to as Datacenter Extension)See Chapter 4, “Entering the License Key for vCloud Connector Advanced Edition,” on page 53 forinformation on how to assign the license key.VMware, Inc.7

Installing and Configuring vCloud Connector8VMware, Inc.

vCloud Connector Overview2This section provides an overview of vCloud Connector. It describes the functionality of vCloud Connectorand the components that make it up.This chapter includes the following topics:n“vCloud Connector,” on page 9n“Planning Your vCloud Connector Installation,” on page 10vCloud ConnectorvCloud Connector is an enterprise product that provides a single user interface for overseeing multiplepublic and private clouds and for transferring cloud content from one cloud to another. It allows you toconnect multiple clouds, both internal and external, in a single user interface.Using vCloud Connector, you can stop and start virtual machines, check their performance, and transfervirtual machines, vApps, and templates from one cloud to another.Using vCloud Connector Advanced edition, you can also extend your private datacenter to a public vCloudwith Datacenter Extension and set up a Content Library to distribute and synchronize templates acrossclouds.vCloud Connector ComponentsvCloud Connector consists of three distinct components: the vCloud Connector UI, the vCloud Connectorserver, and vCloud Connector nodes.VMware, Inc.9

Installing and Configuring vCloud ConnectorFigure 2‑1. vCloud Connector ComponentsexternalinternalThe vCC UI can be surfaced in vSphere ClientvSphere ClientvCloudConnector UIvCloudConnectorServerA single vCC Servercontrols everything.A vCC node ineach cloudmanages ubliccloudnodepubliccloudvCloud Connector UIvCloud Connector UI is the user interface that the vCloud Connector server produces. It can be surfaced invSphere Client. You decide where to display the UI during the configuration process.vCloud Connector ServerThe vCloud Connector server is a virtual appliance that coordinates the activity of vCloud Connector,controls vCloud Connector nodes, and produces the vCloud Connector UI. Only one vCloud Connectorserver is needed.vCloud Connector NodesvCloud Connector nodes are virtual appliances that handle transferring content from one cloud to another.A vCloud Connector node must be installed in every vSphere or vCloud Director-based cloud that vCloudConnector oversees.On public clouds, the service provider installs a vCloud Connector node as a multi-tenant node for multiplecustomers to use.Planning Your vCloud Connector InstallationBefore you install vCloud Connector, you need to do some basic high-level planning.You need to decide the following.10nWhere you want to install the vCloud Connector servernWhich clouds you want to be able to add to the vCloud Connector UI. You must install a vCloudConnector node in each cloud that you want to add.VMware, Inc.

Chapter 2 vCloud Connector OverviewOn vCloud Director clouds, you do not need to install a node for each organization. vCloud Connectornodes are multi-tenant, that is, one node can be used by multiple organizations to transfer content toand from the cloud. If you are a public vCloud service provider or the system administrator of a privatevCloud Director cloud, you can choose to install one node in the cloud for multiple organizations touse.nIn which vSphere Client you want to surface the UIYou also need to collect specific information to use during the installation and configuration process. Whatyou need to know depends on your specific installation decisions. A detailed description of the informationyou should collect is covered in “Collect Necessary Information,” on page 14.VMware, Inc.11

Installing and Configuring vCloud Connector12VMware, Inc.

3Installing vCloud ConnectorInstalling vCloud Connector is a multi-step process. This section gives you a high-level overview of thesteps you need to take.Figure 3‑1. vCloud Connector Installation and Configuration WorkflowexternalinternalvSphere Client10vCloudConnector UI4 5vCloudConnectorServer9vSpherenodenode6 7 86 7 u install a vCloud Connector node in each cloud that you want to connect. To connect a public cloud, youcan either install your own node in the cloud or ask your service provider to install a multi-tenant node. Youonly need one vCloud Connector server.This figure illustrates all the combinations that you can set up with vCloud Connector. Typically, you use asubset of these. Common installation scenarios include using vCloud Connector to connect the following.nConnect a private vSphere cloud with a public vCloud.nConnect a private vCloud Director cloud with a public vCloud.nConnect a private vSphere cloud with a private vSphere cloud.nConnect a private vCloud Director cloud with a private vCloud Director cloud.nConnect a private vSphere cloud with a private vCloud Director cloud.VMware, Inc.13

Installing and Configuring vCloud ConnectorProcedure1Collect Necessary Information on page 14Print this worksheet section to help you collect the information you need to install and configurevCloud Connector.2Check System Requirements on page 16You must ensure that your system meets the minimum requirements before you install vCloudConnector.3Download the vCloud Connector Virtual Appliances on page 18The vCloud Connector server and vCloud Connector node are packaged as virtual appliances. Youdownload the virtual appliances from the vCloud Connector Download page.4Install vCloud Connector Server on page 18You can install a vCloud Connector server in a vSphere cloud or in a vCloud Director cloud.5Configure vCloud Connector Server on page 29You use the vCloud Connector server Admin Web console to do basic configuration tasks, such asdefining your time zone, specifying proxy servers, or setting log levels. What you need to do dependson your particular installation.6Install vCloud Connector Nodes on page 32You can install vCloud Connector nodes in vSphere or vCloud Director clouds.7Register vCloud Connector Nodes with Clouds on page 43After you install a vCloud Connector node for a cloud, you need to associate it with the cloud.8Configure vCloud Connector Nodes on page 44You use the vCloud Connector node Admin Web console for each of your nodes to perform basicconfiguration tasks, such as defining your time zone, specifying proxy servers, or setting log levels.What you need to do depends on your particular installation.9Register vCloud Connector Nodes with vCloud Connector Server on page 49You use the vCloud Connector server Admin Web console to register vCloud Connector nodes withthe vCloud Connector server. The nodes can be installed on vSphere, private vCloud Director clouds,or public vClouds. The registration allows the server to manage the nodes.10Register the vCloud Connector UI on page 50To use the vCloud Connector UI, you register it to a vSphere Client.Collect Necessary InformationPrint this worksheet section to help you collect the information you need to install and configure vCloudConnector.AccountsYou need the following accounts.14VMware, Inc.

Chapter 3 Installing vCloud ConnectorTable 3‑1. Account InformationAccount TypeInformation NeededUsed ForA My Vmware account.You can get an account fromwww.vmware.com.User name and passwordDownloading vCloudConnectorOne of the following: n VMware vCenterServer administratoraccountn VMware vCloudDirector account withat least organizationadministrator statusUser name, password, andURL or IP address for theappropriate entityInstalling vCloudConnector servervCenter Serveradministrator account foreach vSphere cloudUser name, password, andURL or IP addressInstalling vCloudConnector nodevCloud Director accountwith at least organizationadministrator status for eachvCloud Director cloudUser name, password, andURL or IP addressInstalling vCloudConnector nodeProxy ServersYou need the following proxy information.Table 3‑2. Proxy InformationInstall TypeInformation NeededConditionvCloud Connector serverhost:portIf the server needs a proxyto be able to access systemsbeyond the firewall in thelocation in which it isinstalled.vCloud Connector node per nodehost:portIf the node needs a proxyto be able to access systemsbeyond the firewall in thelocation in which it isinstalled.NOTE UDT-based data transfer in vCloud Connector is only compatible with SOCKS5-compliant proxyservers, as these proxy servers support the UDP protocol. You cannot use UDT-based data transfer with anyother types of proxy servers.NetworkIf you are using a static IP address (and not DHCP) for your vCloud Connector server or vCloud Connectornode, you need the following information for each instance.Table 3‑3. Network InformationNetwork InformationAn available static IP addressThe netmask for that addressThe IP address of the gatewayVMware, Inc.15

Installing and Configuring vCloud ConnectorTable 3‑3. Network Information (Continued)Network InformationThe IP address of a primary and secondary DNS serverA host name (optional)For information on network paths in data transfers, see Chapter 9, “Cross-Cloud Data Transfer andNetwork Connectivity,” on page 79.Displaying the vCloud Connector UI To set up the vCloud Connector UI in a VMware vSphere Client , you need the following information.Table 3‑4. vCloud Connector UI in vSpherevCloud Connector UI in vSphereThe IP address or fully qualified domain name of thevCenter Server to which you will be connecting.A user name and password for the vCenter Server.The IP address or fully qualified domain name of thedeployed vCloud Connector server. This information isassigned when the vCloud Connector server is firstdeployed.Check System RequirementsYou must ensure that your system meets the minimum requirements before you install vCloud Connector.Product RequirementsTo install and configure a vCloud Connector server and nodes, you need to install the following VMwareproducts.Table 3‑5. VMware Products16ProductSupported VersionNotesvSphere4.0, 4.1, 5.0, 5.1, 5.5Required if you are deploying thevCloud Connector server or vCloudConnector nodes on vSphere.NOTE To use the Stretch Deployfeature (Datacenter Extension), youmust install vSphere 5.1 or later.vCloud Director1.5, 5.1, 5.5Required if you are deploying thevCloud Connector server or vCloudConnector nodes on vCloud Director.NOTE To use the Stretch Deployfeature (Datacenter Extension), youmust install vCloud Director 5.1 orlater.VMware, Inc.

Chapter 3 Installing vCloud ConnectorTable 3‑5. VMware Products (Continued)ProductSupported VersionNotesvShield Manager5.1.2, 5.5Required for the Stretch Deployfeature (Datacenter Extension) only.vSphere Client4.0, 4.1, 5.0, 5.1, 5.5Required as the vCloud Connector UIis registered as a plug-in in vSphereClient.NOTE The Stretch Deploy feature has special system requirements. See System Requirements for StretchDeploy in Using vCloud Connector for more information.Supported BrowsersTo access the vCloud Connector server and node Admin Web consoles, you need a browser.Table 3‑6. Supported BrowsersBrowserSupported VersionInternet Explorer8, 9Firefox15, 16Chrome22, 23The browser must be set to accept third-party cookies.NOTE Do not use Firefox to log in to the vCloud Connector server or node Admin Web console. Some tabs,such as the Server tab in the server Admin Web console and the Node tab in the node Admin Web console,display blank pages on Firefox.Required PortsvCloud Connector uses the following ports to communicate between its various components: server, nodes,and the server and node Admin Web consoles.Table 3‑7. Port InformationPort NumberUse443Used when SSL is enabled.This port is used for communication between the vCloud Connector server andvCloud Connector nodes and between nodes.80Used when SSL is disabled.This port is used for communication between the vCloud Connector server andvCloud Connector nodes and between nodes.8190Required on the destination node for UDT-based data transfer.NOTE When you copy data between a private cloud and a public cloud, port 8190needs to be open on the public cloud.5480This port is used for communication with the vCC server and vCC node AdminWeb consoles.NOTE Ports 80 and 443 are also used for the Local Content Directory node, which is a node that isautomatically installed with the vCloud Connector server and used for the Content Library. Port 80 is usedwhen SSL is disabled and port 443 is used when SSL is enabled.VMware, Inc.17

Installing and Configuring vCloud ConnectorDownload the vCloud Connector Virtual AppliancesThe vCloud Connector server and vCloud Connector node are packaged as virtual appliances. Youdownload the virtual appliances from the vCloud Connector Download page.PrerequisitesYou have collected the information specified in “Collect Necessary Information,” on page 14.Procedure1Go to the vCloud Connector Download page.2Click Download.3Scroll down to the Product Downloads section and download both the vCCServer and vCCNode files.aClick either Download Manager or Manually Download.For information about each method, click the Need help downloading? link at the top of thesection.bLog in with your My VMware account information.cRead and accept the End User License Agreement.A dialog box appears that prompts you to open or save the zip file.d4Download the zip file to your desktop.In separate directories, unzip the vCloud Connector server and vCloud Connector node virtualappliance zip files.Install vCloud Connector ServerYou can install a vCloud Connector server in a vSphere cloud or in a vCloud Director cloud.Only one vCloud Connector server is required for each vCloud Connector installation. Choose one of thefollowing options to install your server.Install vCloud Connector Server in vSphereYou can install a vCloud Connector server in vSphere.For information on installing vCloud Connector in a Linked Mode vCenter server configuration, see“Installing vCloud Connector in Linked Mode vCenter Server Configurations,” on page 19.PrerequisitesYou must have an administrator account for the vSphere instance in which you deploy the vCloudConnector server. You must have the unzipped version of the template you downloaded in “Download thevCloud Connector Virtual Appliances,” on page 18.Procedure181Log in to vSphere Client.2Select File Deploy OVF template.3Click Browse and navigate to the OVF directory of the server zip file you downloaded.4Click Next.VMware, Inc.

Chapter 3 Installing vCloud Connector5Proceed through the wizard.You can either use the Networking Properties step in the wizard to set basic network properties or youcan wait and set those properties when you configure your server.NOTE If you are going to use a static IP address, you need to assign it here. Proxy information is setduring “Configure vCloud Connector Server,” on page 29.6In the vSphere Client, select Inventory VMs and Templates to see the virtual machine that is created.7Right-click the virtual machine and select Power Power on to power it on.8Click the Summary tab and find the vCloud Connector server's IP address in the General section. TheIP address field (not the Host field) displays the IP address of the vCloud Connector server. Make anote of the IP address. You will need it later in the process.Installing vCloud Connector in Linked Mode vCenter Server ConfigurationsvCloud Connector is compatible with Linked Mode vCenter server configurations. You install a vCloudConnector server or vCloud Connector nodes in vCenter server instances in a Linked Mode configuration inthe same way that you install them on single vCenter server instances.For information about Linked Mode vCenter server configurations, see the VMware vSphereDocumentation Center.Installing a vCloud Connector Server in a Linked Mode vCenter ServerConfigurationYou install one vCloud Connector server. You can install it in any of the vCenter server instances in theLinked Mode configuration.Installing vCloud Connector Nodes in a Linked Mode vCenter ServerConfigurationYou install a vCloud Connector node for each vCenter server instance that you want to manage in vCloudConnector. You then register each node with your vCloud Connector server.Registering the vCloud Connector UI with a vSphere Client Associated with aLinked Mode vCenter Server ConfigurationThe vCloud Connector UI appears as a plug-in in vSphere Client. You can register the vCloud Connector UIto any of the vCenter server instances in the Linked Mode configuration.When you register the vCloud Connector UI, specify the IP address or URL of any of the vCenter serverinstances. The UI appears in the vSphere Client for all the vCenter instances.NOTE If the plug-in does not appear in vSphere Client, clear the Internet Explorer cache, then close andrestart vSphere Client.Install vCloud Connector Server in vCloud Director 1.5You can install a vCloud Connector server in vCloud Director 1.5.NOTE If you install a vCloud Connector server in a public cloud, you can only connect to public clouds inyour vCloud Connector UI.PrerequisitesYou must have at least organization administrator access in the vCloud Director cloud in which you installthe vCloud Connector server.VMware, Inc.19

Installing and Configuring vCloud ConnectorProcedure1Add vCloud Connector Server to a vCloud Director 1.5 Catalog as a vApp Template on page 20Before you can deploy a vCloud Connector server in a vCloud Director 1.5 cloud, you must upload thevirtual appliance to a catalog as a vApp template. You do not need to upload an additional template ifa template is already uploaded to a master catalog that multiple organizations share.2Create the vCloud Connector Server from the Template in a vCloud Director 1.5 Cloud on page 21After the vCloud Connector server is added to the vCloud Director 1.5 cloud as a template, you canuse it to create a running instance on that cloud.3Set Up NAT Mapping for vCloud Connector Server in vCloud Director 1.5 on page 22If you select a NAT-based network connection when you deploy your vCloud Connector server, youneed to set up NAT mapping and firewall rules.Add vCloud Connector Server to a vCloud Director 1.5 Catalog as a vAppTemplateBefore you can deploy a vCloud Connector server in a vCloud Director 1.5 cloud, you must upload thevirtual appliance to a catalog as a vApp template. You do not need to upload an additional template if atemplate is already uploaded to a master catalog that multiple organizations share.PrerequisitesYou must have system administrator or organization administrator access in the vCloud Director cloud inwhich you install the vCloud Connector server. You must have the unzipped version of the template youdownloaded in “Download the vCloud Connector Virtual Appliances,” on page 18.Procedure1Log in to the vCloud Director Web console using a supported browser.2Click Catalogs.If you log in as system administrator, select your organization first, then click the Catalogs tab.3Double-click the catalog to which you want to upload the vCloud Connector server, then click the vAppTemplates tab.4Click the Upload icon.5In the Upload OVF package as a vApp Template dialog box, click Browse, accept the security certificateif you are prompted to do so, and select the vCloud Connector server OVF file that you downloaded.6Specify a name and, optionally, a description, for the vApp template.7Select the virtual datacenter and catalog for the template.8Click Upload.The upload process begins. You can monitor the status of the upload in the Transfer Progress popup.NOTE It may take several seconds after the upload itself has finished for the process to be finalized in thecloud.20VMware, Inc.

Chapter 3 Installing vCloud ConnectorCreate the vCloud Connector Server from the Template in a vCloud Director 1.5CloudAfter the vCloud Connector server is added to the vCloud Director 1.5 cloud as a template, you can use it tocreate a running instance on that cloud.PrerequisitesYou must have at least organization administrator access in the vCloud Director cloud in which you installthe vCloud Connector server.Procedure1On the vApp Templates tab of the catalog to which you uploaded, right-click the name of your vCloudConnector server template and select Add to My Cloud.The Add to My Cloud popup appears.2Give the server vApp an easily identifiable name and provide a description.3Set the leases for the server vApp and click Next.4Read and accept the EULA, and click Next.5Select an appropriate network from the Network drop-down menu.Unless all your vCloud Connector nodes and the vCloud Connector server are behind the samefirewall, you must select a network that is configured to access the Internet. Ask your service provideror network administrator for more information.NOTE If your provider uses NAT, you will need to set up NAT mapping after your server is deployed.See “Set Up NAT Mapping for vCloud Connector Server in vCloud Director 1.5,” on page 22.6Select the appropriate IP Assignment from the drop-down menu and click Next.If there is a static IP pool, that is probably a reasonable choice. Ask your service provider or networkadministrator for more information.7In the Networking Properties page, use the information you collected before you began installingvCloud Connector to specify the DNS server, IP address, Netmask, and Default Gateway. If you areusing DHCP, leave the fields blank.8In the Configure Networking page, leave both check boxes unselected, and click Next.9In the Ready to Complete page, review the settings and click Finish.10Click the My Cloud tab, then select vApps in the My Cloud panel.You see the vApp being created.11In the My Cloud panel, select VMs, right-click your vCloud Connector server, and select Properties.12In the Virtual Machine Properties window, click the Guest OS Customization tab.13Select Enable guest customization, then click OK.14In the My Cloud panel, select vApps, then right-click the console icon of the vCloud Connector serverand select Start.15When the server on vCloud Director 1.5 is in running state, click VMs in the My Clouds panel andmake a note of the IP address of the server VM.You need the IP address later in the registration process.VMware, Inc.21

Installing and Configuring vCloud ConnectorSet Up NAT Mapping for vCloud Connector Server in vCloud Director 1.5If you select a NAT-based network connection when you deploy your vCloud Connector server, you need toset up NAT mapping and firewall rules.There are multiple approaches to managing this issue. Decide whether you wish to use NAT to forwardonly the ports necessary for vCloud Connector operation or to forward all ports and then set up a firewallrule to filter all but the required ports. See “Check System Requirements,” on page 16 for the list of requiredports.PrerequisitesYour appliance is deployed and you are logged in to the vCloud Director Web console as organizationadministrator or system administrator.Procedure1Click the Administration tab and select Networks in the left panel.2Find the network you are using in the Networks list, right-click, and select Configure Services.3In the Configure Services dialog box, click the NAT Mapping tab and click Add at the bottom of thepopup to create the NAT rule.The Add NAT Rule popup appears.4Select one of the External IP addresses from the drop-down menu.Note this address if you plan to set up a firewall rule.5If you wish to NAT all ports, enter * for the first port entry.If you wish to NAT only the required ports, create a rule for each port.6Enter the internal IP address from your initial setup and match the port entry for this rule.7Click OK and click OK again.8If you are using a firewall rule to control traffic, click the Firewall tab and select the Enable firewallcheck box.9Click Add at the bottom of the pop-up menu to create a new firewall rule.Create a rule for each necessary port.The Add Firewall Rule popup appears.10Give the rule a name and select the Incoming option.11Type the source IP address and the source port.For incoming traffic, the source is the external network. This is the address you selected in Step 4 above.12Type the destination IP address and port.The destination IP address is the internal IP address from your initial setup.2213Select the Allow action.14Select the Enabled check box.15Click OK and click OK again to create the rule.VMware, Inc.

Chapter 3 Installing vCloud ConnectorInstall vCloud Connector Server in vCloud Director 5.1You can install a vCloud Connector server in vCloud Director 5.1.You must have at least organization administrator access in the vCloud Director cloud in which you installthe vCloud Connector server.NOTE If you install vCloud Connector server in a public cloud, you can only connect to public clouds inyour vCloud Connector UI.1Add the vCloud Connector Server to a vCloud Director 5.1 Catalog as a vApp Template on page 23Before you can deploy a vCloud Connector server in a vCloud Director 5.1 cloud, you must upload thevirtual appliance to a catalog as a vApp template. You do not need to upload an additional template ifa template is already uploaded to a master catalog that multiple organizations share.2Create the vCloud Connector Server from the Template in a vCloud Director 5.1 Cloud on page 24After the vCloud Connector Server is added to the vCloud Director 5.1 cloud as a template, you canuse it to create a running instance on that cloud.3Set Up NAT Mapping for vCloud Connector Server in vCloud Director 5.1 on page 25If you select a NAT-based network connection when you deploy your vCloud Connector server, youneed to set up NAT mapping and firewall rules.Add the vCloud Connector Server to a vCloud Director 5.1 Catalog as a

Configure vCloud Connector Server 29 Install vCloud Connector Nodes 32 Register vCloud Connector Nodes with Clouds 43 Configure vCloud Connector Nodes 44 Register vCloud Connector Nodes with vCloud Connector Server 49 Register the vCloud Connector UI 50 4 Entering the License Key for vCloud C

Related Documents:

The vCloud API version number is incremented whenever any of its types or operations changes. The vCloud API Programming Guide for Service Providers is revised with each release of VMware vCloud Director. Versions of the vCloud API that were not introduced in a VMware vCloud Director release are documented in the vCloud Air Compute Service .

The following table describes the components that comprise the VMware vCloud Suite. Table 2. vCloud Components vCloud Component Description VMware vCloud Director vCloud API Layer of software that abstracts virtual resources and exposes vCloud components to consumers. Inclu

vCloud Suite API client applications use the Lookup Service to retrieve the vCenter Single Sign-On endpoint, the vCloud Suite Endpoint, and the endpoints of services that are exposed through the vSphere API. To access vCloud Suite services such as Content Library and Tagging, client applications issue requests to the vCloud Suite Endpoint.

vCloud Suite API client applications use the Lookup Service to retrieve the vCenter Single Sign-On endpoint, the vCloud Suite Endpoint, and the endpoints of services that are exposed through the vSphere API. To access vCloud Suite services such as Content Library and Tagging, client applications issue requests to the vCloud Suite Endpoint.

vCloud Suite API client applications use the Lookup Service to retrieve the vCenter Single Sign-On endpoint, the vCloud Suite Endpoint, and the endpoints of services that are exposed through the vSphere API. To access vCloud Suite services such as Content Library and Tagging, client applications issue requests to the vCloud Suite Endpoint.

The vCloud Suite includes the entire set of cloud infrastructure capabilities: virtualization, software-defined datacenter services, policy-based provisioning, disaster recovery, application management, and operations management. The vCloud solution encompasses the vCloud Suite, along with an architecture defined in the VMware vCloud Architecture

VMware vCloud Air User's Guide vCloud Air This document supports the version of each product listed and supports all subsequent versions until the document is . 7 Disaster Recovery in vCloud Air 47 8 Storage in vCloud Air 49 Overview of Storage Tiers 49 Adjust Storage for a Virtual Data Center 53

Illustration by: Steven Birch, Mary Peteranna Date of Fieldwork: 9-18 February 2015 Date of Report: 17th March 2015 Enquiries to: AOC Archaeology Group Shore Street Cromarty Ross-shire IV11 8XL Mob. 07972 259 255 E-mail inverness@aocarchaeology.com This document has been prepared in accordance with AOC standard operating procedures. Author: Mary Peteranna Date: 24/03/2015 Approved by: Martin .