User creates virtualAppliances on virtual dataCenter section, when user starts these virtual Appliance, system starts each of the virtual Machines that there are inside. More over addequate physical machine is selected to instantiate the virtual machine. This is the deploy state on the Virtual Machien life cycle.
The resource provisioning mechanism follows these rules:
- Check total allocated resources on infrastructure for the Resource Allocation Limits.
- Only selects physical machines on the datacenter associated to the virtual virtual DataCenter of the Virtual Appliance.
- These only includes physical machines with the appropriate virtualization technology for the provided virtual image.
- Filter the physical machines with enough free resources to fit the virtual machine requirements.
- If more than one physical machine can be selected the one with less capacity is used. These mechanism intend to fully utilize each single physical machine.
- Finally there is a check process that assures that the selected Physical machine is running, if not, it changes its state and starts the process again.
Common deployment errors
From the Virtual Datacenter perspective, when deploying a virtual appliance or a single virtual machine the follow errors can appear to the user related to the scheduler logic.
| Type | Description | Solutions |
|---|---|---|
| Not enought resource | The virtual appliance's data center there isn't a physical machine with enought free resources for the virtual machine requirements. |
|
| Resource allocation limits exceeded (Hard limits) | The configured Resource Allocation Limits on the infraestructure do not allow the total resource utilization after the virtual machine requirements. |
|
| Resource allocation limits exceeded (Soft limits) | The configured Resource Allocation Limits on the infraestructure allow the total resource utilization after the virtual machine requirements but alerts users that their resources are reaching the hard limit |
|
