1.5
Table Of Contents
- vCloud API Programming Guide
- Contents
- vCloud API Programming Guide
- About the VMware vCloud API
- Hello vCloud: A Simplified RESTful Workflow
- Exploring a Cloud
- Provisioning an Organization with vApps, Templates, and Media
- Deploying and Operating vApps
- Summary of vCloud API vApp and Virtual Machine Operations Requests
- Create a vApp From a Template
- Compose a vApp From Existing Virtual Machines
- Recompose a vApp to Add or Remove Virtual Machines
- Operate a vApp
- Configuring vApps and Virtual Machines
- Retrieve the Configuration Links for a vApp
- Retrieve the Configuration Links for a Virtual Machine
- Retrieve or Update a Modifiable Section
- Update a vApp Network Configuration
- Update the NetworkConnectionSection of a Virtual Machine
- Retrieve or Modify the CPU Configuration of a Virtual Machine
- Retrieve or Modify the GuestCustomizationSection of a Virtual Machine
- Retrieve or Modify ProductSection Elements
- Retrieve or Modify Groups of Related Sections in a Virtual Machine
- Retrieve or Modify the Hard Disk Configuration of a Virtual Machine
- Creating, Provisioning, and Managing Organizations
- Summary of Administrative Requests
- Administrator Credentials and Privileges
- Organization Administration
- Network Administration
- vDC Administration
- Catalog Administration
- User and Group Administration
- Working With Roles and Rights
- Controlling Access to vApps and Catalogs
- Using vCloud API Extensions to Provision and Manage a Cloud
- Working With Object Metadata
- Using the Query Service
- Configuring and Using Blocking Tasks and Notifications
- XML Representations in the vCloud API
- Index
Rules are applied to packets in the order in which the FirewallRule elements appear in the FirewallService
definition.
<FirewallService>
<IsEnabled>true</IsEnabled>
<DefaultAction>allow</DefaultAction>
<LogDefaultAction>false</LogDefaultAction>
<FirewallRule>
<IsEnabled>true</IsEnabled>
<Description>allow ssh</Description>
<Policy>allow</Policy>
<Protocols>
<Tcp>true</Tcp>
</Protocols>
<Port>22</Port>
<DestinationIp>Any</DestinationIp>
<SourcePort>-1</SourcePort>
<SourceIp>Any</SourceIp>
<Direction>in</Direction>
<EnableLogging>false</EnableLogging>
</FirewallRule>
<FirewallRule>
<IsEnabled>true</IsEnabled>
<Description>deny outgoing rdp</Description>
<Policy>drop</Policy>
<Protocols>
<Tcp>true</Tcp>
</Protocols>
<Port>3389</Port>
<DestinationIp>Any</DestinationIp>
<SourcePort>-1</SourcePort>
<SourceIp>Any</SourceIp>
<Direction>out</Direction>
<EnableLogging>true</EnableLogging>
</FirewallRule>
</FirewallService>
You can see this fragment in the context of an organization network in “Example: Create an Organization
Network With a Routed Connection,” on page 128.
Static Routing Configurations for vCloud Director Networks
A network Configuration element can define a static routing service and specify one or more static routes
between routed vApp or organization networks.
You can create static routes between two routed networks that do not have overlapping IP address spaces.
Static routing service details and routes are defined in a StaticRoutingService element contained by the
Features element of a network's Configuration. A StaticRoutingService element can contain zero or more
StaticRoute elements. Each StaticRoute specification requires the following elements:
Name
A name for the route.
Network
The network specification in CIDR notation.
Chapter 6 Creating, Provisioning, and Managing Organizations
VMware, Inc. 123