1.0
Table Of Contents
- vCloud API Programming Guide
- Contents
- About This Book
- Introducing the VMware vCloud API
- Hello vCloud: A Structured REST Workflow Example
- Logging In and Getting an Organization List
- Browsing an Organization
- Finding a vApp Template
- Getting Information About a vDC
- Instantiating the Template in the vDC
- Deploying and Powering On the vApp
- Getting Information About the vApp
- Displaying the Console
- Deleting the vApp
- Logging Out
- Moving on to Additional Use Cases
- Browsing
- Provisioning
- Summary of Provisioning Requests
- Upload OVF to Create a vApp Template
- View the OVF Descriptor of a vApp Template
- Download a vApp Template as OVF
- Upload a Media Image
- Copying and Moving
- Changing a Name or Description
- Delete a vAppTemplate, vApp, or Media Image
- Cataloging vApp Templates and Media Images
- Controlling Access
- Datacenter Operations
- Summary of Datacenter Operations Requests
- vApp Lifecycle
- Instantiate a vApp Template
- Compose a vApp
- Recompose a vApp to Add or Remove Virtual Machines
- Capture a vApp to Create a vApp Template
- Reconfiguring vApps and Virtual Machines
- Deploying and Controlling vApps and Virtual Machines
- Deploy a vApp or Virtual Machine
- Undeploy a vApp or Virtual Machine
- Power On a vApp or Virtual Machine
- Power Off a vApp or Virtual Machine
- Reset a vApp or Virtual Machine
- Suspend a vApp or Virtual Machine
- Discard the Suspended State of a vApp or Virtual Machine
- Shut Down a vApp or Virtual Machine
- Reboot a vApp or Virtual Machine
- List Media Devices of a Virtual Machine
- Insert Media Into a Virtual Machine
- Eject Media from a Virtual Machine
- Get a Screen Thumbnail for a Virtual Machine
- Get a Screen Ticket for a Virtual Machine
- Provide User Input Requested by a Virtual Machine
- Control Access to vApps
- Retrieve a Task
- Administrative Operations
- VMware vSphere Platform Operations
- Summary of vSphere Platform Operations Requests
- List vSphere Platform Operations and Objects for a vCloud
- List Provider vDCs in a vCloud
- List External Networks in a vCloud
- List Network Pools in a vCloud
- List vCenter Servers Registered to a vCloud
- List ESX/ESXi Hosts in a vCloud
- Create a Provider vDC
- Create an External Network
- Create a Network Pool
- Import a Virtual Machine from vCenter
- XML Representations in the vCloud API
- User API Reference
- Request Parameters Reference
- Administrative API Reference
- vSphere Platform Extensions Reference
- OVF and the vCloud API
- An Introduction to REST for vCloud API Users
- Index
vCloud API Programming Guide
72 VMware, Inc.
AsetofFirewallRulesthatallowTCPtraffictoports21and22.Becausetheserulesrequireyouto
specifyasingleIPaddressontheinsideofthefirewall,theIpScopeelementismodifiedtolimittherange
ofIPaddressesavailableonthevAppnetworktoasingleaddress.
AnyVmthatconnectstothevApp
networkdefinedinthisNetworkConfigSectionisgiventhisaddress.
ANatServiceelementthatmapsaroutableexternalIPaddresstotheinternalIPaddressallocatedtothe
VmbythevAppnetwork.TheVAppScopedVmIdvalueinthiselementistakenfromthe
VAppScopedLocalIdelementoftheVmandtheVmNicIdvalueistakenfromits
PrimaryNetworkConnectionIndex.SeeExample 5‐12
onpage 75.
WheneveryoumodifyavAppnetwork,aswedointhisexample,youmustbesurethatthemodificationsare
consistentwiththenetworkconnectionrequirementsofthevirtualmachinesthatconnecttothenetwork.The
vAppinthisexamplecontainsasingleVm.AsshowninExample 5‐12
onpage 75,thatvirtualmachine’s
NetworkConnectionelementspecifiesanIPaddressthatwillnotbeavailableafterthevAppnetworkhas
beenreconfiguredasshowninExample 5‐11.Example 5‐14onpage 77correctsthisproblem.While
Example 5‐11usestheIpScopeelementtorestricttheIPaddressesavailableon
avAppnetwork,itisusually
morepracticaltokeeptherangeofaddressesavailableonavAppnetworksomewhatwider,andapplyany
firewall‐relatedIPaddressrestrictionsbymodifyingtheNetworkConnection oftheVmtowhichthe
FirewallRulesapply,aswedoinExample 5‐14.Awiderrangeof
IPaddresseswouldallowthisvApptobe
modifiedtoincludeadditionalvirtualmachines,andtheIPaddressrestrictionappliedinExample 5‐14would
allowtheFirewallRulesinExample 5‐14toremainvalid.
Thisrequest,likeallrequestbodiesderivedfromaresponse,omitstheLinkelementsandhrefattributesthat
werepartoftheresponse.ItalsoomitstheIsDeployedelementoftheNetworkConfig.Theseelementsand
attributesarecreatedbytheserverandareread‐only.Theyareignoredifyouincludetheminarequest.
Example 5-11. Modify vApp Network Configuration
Request:
PUT http://vcloud.example.com/api/v1.0/vApp/vapp-7/networkConfigSection/
Content-type: application/vnd.vmware.vcloud.networkConfigSection+xml
...
<NetworkConfigSection>
<ovf:Info>Configuration parameters for logical networks</ovf:Info>
<NetworkConfig networkName="vAppNetwork">
<Configuration>
<IpScope>
<IsInherited>false</IsInherited>
<Gateway>10.147.56.253</Gateway>
<Netmask>255.255.255.0</Netmask>
<Dns1>10.147.115.1</Dns1>
<Dns2>10.147.115.2</Dns2>
<DnsSuffix>example.com</DnsSuffix>
<IpRanges>
<IpRange>
<StartAddress>10.147.56.1</StartAddress>
<EndAddress>10.147.56.1</EndAddress>
</IpRange>
</IpRanges>
</IpScope>
<ParentNetwork type="application/vnd.vmware.vcloud.network+xml" name="Internet"
href="http://vcloud.example.com/api/v1.0/network/54"/>
<FenceMode>natRouted</FenceMode>
<Features>
<FirewallService>
<IsEnabled>true</IsEnabled>
<FirewallRule>
<IsEnabled>true</IsEnabled>
<Description>FTP Rule</Description>
<Policy>allow</Policy>
<Protocols>
<Tcp>true</Tcp>
</Protocols>
<Port>21</Port>