ZStack 3.10.0>Tutorials>Advanced Features>vCenter Management Tutorial>VM Instance

VM Instance

After you add a vCenter, the vCenter VM instances will be automatically synchronized to ZStack. In addition, you can create vCenter VM instances on your Cloud.

This topic describes how to create vCenter VM instances in ZStack.

On the VM Instance page, check the details about the VM instances synchronized from the vCenter you added to ZStack.

In the navigation pane of the ZStack Private Cloud UI, choose vCenter > VM Instance. Then, the VM Instance page is displayed, as shown in vCenter VM Page.
Figure 1. vCenter VM Page

Note: ZStack allows you to manage resources of multiple vCenters. You can view resources of all vCenters or a vCenter by clicking the vCenter drop-down arrow.
Create a vCenter VM instance on the current Cloud.
Before you create a vCenter VM instance on your current Cloud, you need to set up a vCenter vRouter network or vCenter flat network in advance in ZStack. For more information, see Network.
After you create a vCenter vRouter network or flat network, click Create VM Instance on the VM Instance page of the vCenter. On the displayed Create VM Instance page, set the following parameters:
- Add Type: Select an add type to determine whether to create multiple VM instances at a time. Options: Single | Multiple.
- VM Name: Enter a name for the vCenter VM instance.
  Note: The vCenter VM name cannot be identical with the vCenter image name.
- VM Description: Optional. Enter a description for the vCenter VM instance.
- Instance Offering: Select an instance offering for the vCenter VM instance.
- Image: Select a vCenter image to create the vCenter VM instance.
- Network: Select a vCenter vRouter network or vCenter flat network that you created before.
- Advanced: Optional. Specify resources for the vCenter VM instance. If not specified, the system will automatically specify resources for the vCenter VM instance.
  - Data Disk Offering: Select a data disk offering for the vCenter VM instance.
  - Cluster: Specify a cluster in the vCenter for the vCenter VM instance.
  - Primary Storage: Specify a primary storage in the vCenter for the vCenter VM instance.
  - Host: Specify a host in the vCenter for the vCenter VM instance.
As shown in Create vCenter VM Instance to Your Current Cloud. Click OK. Then, the vCenter VM instance is created.
Figure 2. Create vCenter VM Instance on the Current Cloud

You can perform the following operations on a vCenter VM instance:

Create: Create a vCenter VM instance on the current Cloud.
Start: Start a vCenter VM instance that is in the stopped state.
Stop: Stop the vCenter VM instance.
Reboot: Reboot the vCenter VM instance.
Pause: Pause the vCenter VM instance.
Resume: Resume the vCenter VM instance that is in the paused state.
Migrate: Migrate the vCenter VM instance to the other compute node.
- Currently, only hot migrations are supported.
- Shared storages allow you to perform hot migrations for the vCenter VM instance with data volumes.
- Currently, local storages do not support migrations.
- The migration speed is associated to network configurations of two hosts. If the network configurations are relatively low, the migration speed will probably be slow.
- Before you perform migrations for the vCenter VM instance, make sure that vMotion is enabled.
  - For vCenter 5.5, configure specific VMkernel networks and enable vMotion. In addition, make sure that IP addresses of the vMotion sub-interface for both source VMkernels and destination VMkernels can be intercommunicated.
  - For vCenter 6.0 or later, enable vMotion in management networks.
Clone: Clone a root volume of the vCenter VM instance. According to the instance offering of the vCenter VM instance, the system clones out a VM instance that has the identical system with the current vCenter VM instance.
- The vCenter VM instance supports online cloning and offline cloning.
- The vCenter VM instance with data volumes cannot be cloned with together with its data volumes.
- The vCenter VM instance can be cloned as a VM instance rather than as a template.
Power off: Power off the vCenter VM instance directly.
Change instance offering: Change the CPU or memory offline for the vCenter VM instance.
Change owner: Change the owner of the vCenter VM instance.
Note:
ZStack supports multi-tenant management in the managed vCenter. Normal accounts and project members can perform operations on vCenter VM instances.
Set HA level: Set the high availability (HA) level to NeverStop or None.
- None: Disable the HA feature for the vCenter VM instance.
- NeverStop: Enable the HA feature for the vCenter VM instance.
  If you set the HA level to NeverStop for a VM instances that is running on the LocalStorage primary storage, note that:
  - When the host where the vCenter VM instance is running is in the Enable state and the Connected status, this vCenter VM instance will keep running. Even if this vCenter VM instance is forced to stop, this vCenter VM instance will be rebooted.
    Note:
    If you want a vCenter VM instance with the NeverStop HA level to not be automatically rebooted, select Check the box will make NeverStop VM instance would not start automatically after stop. in the displayed Stop VM Instance dialog box.
  - When the host where the vCenter VM instance is running is powered off or disconnected, this vCenter VM instance will enter the Stopped state.
- If a remote vCenter environment enabled the Distributed Resource Scheduler (DRS) service to provide HA for the vCenter VM instance, the HA setting in ZStack is not affected.
Open console: Open the console of the vCenter VM instance to log in to and control this vCenter VM instance.
Note:
After ZStack takes over a vCenter, you cannot directly open the console of the running VM instances synchronized from the vCenter.
You can directly open the console of the following vCenter VM instances:
- vCenter VM instances that are created in ZStack
- vCenter VM instances that are rebooted in ZStack
- vCenter VM instances that are dynamically migrated via ZStack based on shared storages
Set console password: Set a console password for the vCenter VM instance.
Cancel console password: Cancel a console password for the vCenter VM instance.
Attach volume: Attach an available volume to the current vCenter VM instance.
Detach volume: Detach a volume that you added before from the vCenter VM instance.
Attach NIC: Attach an available NIC to the current vCenter VM instance. Both public network NICs and private network NICs are supported.
Detach NIC: Detach a NIC that you added before from the vCenter VM instance.
Delete: Delete a vCenter VM instance. If you delete a vCenter VM instance, the local records will be deleted as well. Simultaneously, the actual VM instance in the remote vCenter will be stopped.
Recover: Recover a vCenter VM instance that is in the deleted state.
Expunge: Completely delete a vCenter VM instance that is in the deleted state. If you expunge the vCenter VM instance, the local records and the actual VM instance in the remote vCenter will be expunged.
View monitoring data: View the monitoring data of the vCenter VM instance. On the vCenter VM instance details page, click on the Monitoring Data tab page. Then, you can view real-time display of the CPU, memory, disk, virtual disk, and NIC information about the vCenter VM instance.

Next Chapter:Network

VM Instance

Products

Solutions

Help & Support

Contact Us