6.2
Table Of Contents
- IaaS Configuration for Cloud Platforms
- Contents
- IaaS Configuration for Cloud Platforms
- Configuring IaaS
- Configuring IaaS for Cloud Checklist
- Custom Properties in Machine Provisioning, Blueprints, and Build Profiles
- Bringing Resources Under vRealize Automation Management
- Configure Machine Prefixes
- Create a Business Group
- Managing Key Pairs
- Cloud Reservations
- Optional Configurations
- Preparing for Provisioning
- Choosing a Cloud Provisioning Scenario
- Preparing for Amazon Provisioning
- Preparing for OpenStack Provisioning
- Preparing for Virtual Machine Image Provisioning
- Preparing for Linux Kickstart Provisioning
- Preparing for WIM Provisioning
- Creating a Cloud Blueprint
- Configuring Advanced Blueprint Settings
- Managing Cloud Infrastructure
- Monitoring Workflows and Viewing Logs
- Machine Life Cycle and Workflow States for Cloud Platforms
The elastic IP address is associated with your Amazon Web Services account, not a particular machine.
The address remains associated with your Amazon Web Services account until you choose to release it.
You can release it to map it to a specific machine instance.
An administrator can allocate elastic IP addresses to your Amazon Web Services account by using the
AWS Management Console. One range of addresses is allocated to a non-Amazon VPC region and
another range to a Amazon VPC region.
A tenant administrator or business group manager can use a custom property to assign an elastic IP
address to a machine during provisioning. A machine owner or an administrator with rights to edit the
machine can assign an elastic IP addresses to a machines after it is provisioned. However, if the address
is already associated to a machine instance, and the instance is part of the Amazon Virtual Private Cloud
deployment, Amazon does not assign the address.
A machine owner can view the elastic IP address assigned to that machine. Only one Amazon machine
at a time can use the elastic IP address.
vRealize Automation does not track the cost of using the elastic IP address.
There are two groups of elastic IP addresses in any given a region, one group for non-Amazon VPC
instances and another group for Amazon VPCs. If you allocate addresses in a non-Amazon VPC region
only, the addresses will not be available in an Amazon VPC. The reverse is also true. If you allocate
addresses in an Amazon VPC only, the addresses will not be available in a non-Amazon VPC region.
For more information about creating and using Amazon elastic IP addresses, see Amazon Web Services
documentation.
Using Elastic Block Storage
Amazon elastic block storage provides block level storage volumes to use with an Amazon AWS machine
instance and Amazon Virtual Private Cloud. The storage volume can persist past the life of its associated
Amazon machine instance in the Amazon Web Services cloud environment.
When you use an Amazon elastic block storage volume in conjunction with vRealize Automation, the
following caveats apply:
n
You cannot attach an existing elastic block storage volume when you provision a machine instance.
However, if you create a new volume and request more than one machine at a time, the volume will
be created and attached to each instance. For example, if you create one volume named volume_1
and request three machines, a volume will be created for each machine. Three volumes named
volume_1 will be created and attached to each machine. Each volume will have a unique volume ID.
Each volume will be the same size and in the same location.
n
The volume must be of the same operating system and in the same location as the machine to which
you attach it.
n
vRealize Automation does not track the cost of using an existing elastic block storage volume.
IaaS Configuration for Cloud Platforms
VMware, Inc. 45