User manual VMWARE VCLOUD SDK FOR JAVA 1.0 DEVELOPER S GUIDE

[. . . ] vCloud SDK for Java Developer's Guide vCloud SDK for Java 1. 0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www. vmware. com/support/pubs. EN-000362-00 vCloud SDK for Java Developer's Guide You 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. com Copyright © 2010 VMware, Inc. VMware products are covered by one or more patents listed at http://www. vmware. com/go/patents. [. . . ] These templates can be retrieved from catalogs and transformed into virtual systems, called vApps, through a process called instantiation, which binds a template's abstract resource requirements to resources available in a vDC. A vApp contains one or more individual virtual machines (Vm elements), along with parameters that define operational details such as: How the contained virtual machines are connected to each other and to external networks. Deployment lease terms (typically inherited from the containing organization) that constrain the vApp's consumption of vDC resources Access control information specifying which users and groups can perform operations such as deploy, power on, modify, and suspend on the vApp and the virtual machines it contains. VMware, Inc. 9 vCloud SDK for Java Developer's Guide 10 VMware, Inc. 2 Setting Up for Java Development 2 This chapter includes these topics: "Prerequisites" on page 11 "Download the vCloud SDK for Java Package" on page 11 Prerequisites The vCloud SDK for Java requires JDK 6 or later (the SDK and samples were developed using JDK 1. 6. 0_14b08). This document and the SDK reference documentation assume that you are familiar with the Java programming language and have access to an installation of VMware Cloud Director. In addition, you should consider the following: Although the vCloud SDK for Java javadoc provides information about the vCloud API XML schemas, which define the objects and operations that the SDK supports, familiarity with the details of the underlying objects and operations, as described in the vCloud API Programming Guide, can help you understand the structure of vCloud API objects, and how the methods in this SDK operate on those objects. Before you can run the samples, you must use the Cloud Director web console or the vCloud API to create an organization, catalog, and vDC that the samples can use. Import the contents of the vcloud-java-sdk-all folder into your Java IDE. About SSL Access In the default configuration, VMware Cloud Director requires vCloud API clients to use SSL. To simplify access to Cloud Director, all SDK samples use a FakeSSLSocketFactory class that allows the sample programs to accept all SSL certificates. Because clients that use the FakeSSLSocketFactory class are inherently insecure, you should restrict use of this method to sample applications, and only in trusted environments. Client applications built with this SDK can enable the use of SSL certificates by either importing certificates into a keystore or implementing a custom socket factory that accepts certificates from the server. Client applications should not use the FakeSSLSocketFactory class. 12 VMware, Inc. 3 Hello vCloud: A Structured Java Workflow Example 3 This chapter presents an example of using the vCloud SDK for Java to implement a structured workflow through the lifecycle of a vApp. It contains the following topics. "Running the HellovCloud Sample" on page 13 "Logging In and Getting an Organization List" on page 14 "Getting References to the vDC and Catalog" on page 14 "Upload an OVF Package to Create a vApp Template" on page 15 "Add the vApp Template to a Catalog" on page 16 "Instantiate the vApp Template" on page 16 "Operate the vApp" on page 17 Running the HellovCloud Sample The HellovCloud. java sample, included in the samples folder of vcloud-java-sdk-samples-1. 0-sources. jar, demonstrates a number of the operations supported by the vCloud SDK for Java: Logging in to the vCloud Uploading an OVF package to create a vApp template Adding the vApp template to a catalog Instantiating the vApp template to create a vApp Operating the vApp The file HellovCloud. txt in that folder includes sample input and output. The examples shown in this section are extracted from the HellovCloud. java sample. To run the HellovCloud. java sample, use the following command line. java HellovCloud vCloudApiVersionsURL versionId user@vcloud-organization password orgName vdcName ovfFileLocation vmdkFileLocation vmdkFileName catalogName where: vCloudApiVersionsURL is the base API URL of the vCloud. versionId is the version of the API to use (always 1. 0 for this release). username is the name of a Cloud Director user, in the form user@vcloudorganization, who has rights to upload OVF, create vApp templates, create vApps, and operate vApps. password is the user's password. VMware, Inc. 13 vCloud SDK for Java Developer's Guide orgName is the name of the organization to which the user is authenticating. vdcName is the name of a vDC in that organization where the user can upload the OVF and deploy the vApp. ovfFileLocation is the full pathname to the OVF descriptor on the local disk. vmdkFileLocation is the full pathname to the vmdk file referenced in the OVF descriptor. catalogName is the name of the catalog in which the vApp template will be catalogued. For example: java HellovCloud https://vcloud/api/versions 1. 0 user@SampleOrg Pa55w0rd SampleOrg SampleVdc C:\descriptor. ovf C:\disk. vmdk disk. vmdk SampleCatalog Logging In and Getting an Organization List Most vCloud API requests must be authenticated by a login request that supplies user credentials in the form required by Basic HTTP authentication (MIME Base64 encoding of a string having the form user@vcloudorganization:password). [. . . ] HellovCloud. java implements a newvAppFromTemplate method that has two parameters: vAppTemplateReference: a reference to the template (obtained from the catalog). Vdc: a reference to the vDC in which to instantiate the template. With these inputs, newvAppFromTemplate constructs a simple InstantiateVAppTemplateParams request body, makes the request to the action/instantiateVAppTemplate URL of the vDC, and returns a Vapp helper object that contains (among other things) a reference to the vApp. Instantiating the vApp Template public static Vapp newvAppFromTemplate(ReferenceType vAppTemplateReference, Vdc vdc) throws VCloudException { . . . //get the href of the OrgNetwork to which we can connect the vApp network NetworkConfigurationType networkConfigurationType = new NetworkConfigurationType(); if (vdc. getAvailableNetworkRefs(). size() == 0) { System. out. println("No Networks in vdc to instantiate the vapp"); System. exit(0); } //specify the NetworkConfiguration for the vApp network networkConfigurationType. setParentNetwork(vdc. getAvailableNetworkRefs() . iterator(). next()); networkConfigurationType. setFenceMode(FenceModeValuesType. BRIDGED); VAppNetworkConfigurationType vAppNetworkConfigurationType = new VAppNetworkConfigurationType(); vAppNetworkConfigurationType. setConfiguration(networkConfigurationType); vAppNetworkConfigurationType. setNetworkName("new network"); //fill in the NetworkConfigSection NetworkConfigSectionType networkConfigSectionType = new NetworkConfigSectionType(); MsgType networkInfo = new MsgType(); networkInfo. setMsgid("1"); networkInfo. setValue("network info"); networkConfigSectionType. setInfo(networkInfo); List<VAppNetworkConfigurationType> vAppNetworkConfigs = networkConfigSectionType . getNetworkConfig(); vAppNetworkConfigs. add(vAppNetworkConfigurationType); //fill in remaining InstatiationParams InstantiationParamsType instantiationParamsType = new InstantiationParamsType(); 16 VMware, Inc. Chapter 3 Hello vCloud: A Structured Java Workflow Example List<JAXBElement<? [. . . ]