VM Deploy
Overview
With VMware vCloud Director, it's important to understand the concept of vApp.
A vApp is a container used to bring together one or more VMs in order to manage them more easily.
A VM will automatically be part of a vApp even if it has been deployed autonomously.
There are several ways to deploy a VM :
- From a catalog
- From a vApp
- From a OVF/OVA file
Prerequisite
- You must have enough resources available in your VDC to deploy a new VM.
- How access VM Access
VM Deploiement
There are two ways to deploy a VM from a catalog :
From Add vApp From Catalog or by adding from an Existing vApp.
From a Catalog
By this way, you will create a vApp with a VM
Reminder : You can also access your VMs from a specific vDC : VM Access
|
|
Select a VDC
Reminder: CPU, RAM and storage resources are allocated to a VDC, so it's important to choose your destination VDC. Reminder: You can also choose the VDC rather than using the Applications tab. |
|
Select Template To Import
Different templates provided by Orange and those you have created will be listed. You can apply a filter by name or catalogue to find the template more easily.
|
|
Select a Name
Runtime lease
Storage lease
|
|
Configure Resources
|
|
Compute Policies
the frequency per vCPU is set at the creation of your VDC
|
|
Customize Hardware
|
|
Validation
Check the parameters in the Ready to Complete windows and click on the FINISH button. |
From an Existing vApp
By this way, you will Add a VM into a vApp.
|
|
|
From an OVF/OVA file
Next select the target vDC |
|
Select Source File
|
|
The next part of the procedure is similar to what we see when we add a vApp from a template, except for the following: You may be asked to :
|
|