ConVirt EnterpriseMain Page | About | Help | FAQ | Special pages | Log in

Printable version | Disclaimers | Privacy policy

Feature Walkthrough: ConVirt for VMware(vCenter/ESXi)

From ConVirt Enterprise



Contents


1 Introduction

Welcome to ConVirt for VMware(vCenter/ESXi). ConVirt is an enterprise-wide solution for managing your virtualization and cloud infrastructure, including VMware, Hyper-V, KVM, Xen, Amazon Web Services, and OpenStack. For VMware, ConVirt provides full lifecycle management of your open source virtualization infrastructure, including:

This document walks you through many of the key features of ConVirt. The assumption is that you have already installed and setup your ConVirt Management Server, and have a couple of vCenter/ESXi hosts under management. If not, you can walk through these steps. For Standalone ESXi refer Getting Started Guide: ConVirt for VMware(ESXi). For vCenter refer Getting Started Guide: ConVirt for VMware(vCenter).


Note - this guide applies to ConVirt Enterprise 3.x and ConVirt Enterprise Cloud 3.x versions.


2 VM Lifecycle Management

ConVirt provides a toolset for day-to-day VM administration and lifecycle management, including templates-based provisioning, monitoring, configuration management, basic automation, live migration and much more.

2.1 Create A Template

A template is a set of related configuration information from which you can create one or more virtual machines. ConVirt ships with a set of default templates geared towards doing an ISO install, and can be easily customized to your environment.

First, lets create a template - we're going to do this by cloning and modifying an existing template:

  1. Select the Template Library and drill down to the vCenter Templates group and select the vSphere ISO install template.

    VCenter1.png

  2. Right click on the template and select "Create Like":

    VCenter2.png

  3. Enter a name for the new template and click OK.

    VCenter3.png

  4. You should see the new template show up in the Common Templates group.

    VCenter4.png

  5. Right click on the new template, and select Edit Settings.

    VCenter5.png

  6. A Template Settings dialog box should pop up that will guide you through the process of editing the template.

    VCenter6.png

  7. In the General section, change the default values to match your virtual machine template. For example, you can change the memory or change the number of virtual CPUs. The template is now set up to provision new virtual machines. Click OK.

    VCenter7.png

  8. Revise the version if you like, then click Yes.

    VCenter8.png

  9. You have just created a template that is suitable for provisioning multiple virtual machines in your environment.

2.2 Provision A Virtual Machine

Now that you have created your template, you can use it to provision a new virtual machine. There are several ways to provision a VM:

For this example, we will provision a VM on one of our host servers:

  1. Right click on the host and select Provision Virtual Machine.

    VCenter9.png

  2. A dialog box will come up that will guide you through the provisioning process. Select the Template Group and Template Name you just created in the last section, and give the VM a name:

    VCenter10.png

  3. Next we will associate the shared storage with this new VM. Select the Storage tab on the left, click on the ISO file option and select Edit. Click the "shared storage" icon on the right side to select the datastore and then provide the appropriate ISO file path under Location.

    VCenter11.png

  4. After providing the appropriate ISO file path, Click Save.

    VCenter12.png

  5. Select the Networks tab on the left for editing network configuration.

    VCenter13.png

  6. After providing the appropriate network configuration, Click Save.

    VCenter14.png

  7. Click OK to provision the VM.

    VCenter15.png

  8. If the connection is successful, you should see the new VM show up in the Navigation page under your host server.

    VCenter16.png

2.3 Start & Connect To Your Virtual Machine

Now that you have provisioned your VM, you can start it, connect to it, and use it. And you can do all this from the ConVirt console:

  1. Right click on the new VM, and select Start.

    VCenter17.png

  2. When the VM icon turns green, the VM has been started.

    VCenter18.png

  3. Right click on the VM, and select View Console.

    VCenter19.png

  4. ConVirt asks which viewer you want to use to view the console. Please refer vSphere Console Client Support for more details on different console options supported by ConVirt for vCenter.

    VCenter20.png

  5. ConVirt opens a console window to your new virtual machine.

    VCenter21.png

2.4 Manage Virtual Networks

ConVirt significantly streamlines the error-prone and time-consuming tasks of configuring your network resources, providing a centralized interface for managing your virtual networks. With ConVirt, you can centrally define your virtual network, attach it to your host server pools, then ConVirt automates the provisioning of the networks on all the hosts in the pool.

  1. Lets create a new virtual network - we start selecting Manage Virtual Networks at the Data Center level.
    Vcenter-24-1.PNG

  2. This brings up the Manage Virtual Networks dialog - select New.
    Vcenter-24-2.PNG

  3. The New Virtual Network dialog box walks us through the process of configuring a new network resource. Fill in the appropriate network information for your environment. Note that the Ethernet name must be consistent across all machines in the network. Click Save to create the new Virtual Network.
    Vcenter-24-3.PNG

  4. We've now successfully defined our VLAN.
    Vcenter-24-4.PNG

  5. The next step is to attach this VLAN to our server pool. Lets go to the esxi-pool server pool, right click on it, and select Manage Virtual Networks
    Vcenter-24-5.PNG

  6. This brings up the Manage Virtual Networks dialog for the server pool - select Attach.
    Vcenter-24-6.PNG

  7. Select the network we just created and click Attach.
    Vcenter-24-7.PNG

  8. Click on the green status icon to view details about the new VLAN connection.
    Vcenter-24-8-1.PNG

    Vcenter-24-8-2.PNG






3 Self Service

ConVirt makes it easy to give your business unit and customer administrators access to data center virtualization resources with an easy-to-use, lightweight self-service capability that overlays your existing virtualization - no new infrastructure required. You simply delegate compute resources to your business customers, and they provision and manage the compute resources via a web-based self-service console.

3.1 Setup Network Resources

In order to create self-service Virtual Data Centers, ConVirt transforms existing virtualized infrastructure into a cloud by overlaying an Infrastructure-as-a-Service (IaaS) layer. To manage this layer, you need to set up several network resources:

3.1.1 Network Service

Convirt's Network Service connects the following networks:

For larger scale production deployments, these networks would each be set up on their own physical network. For the purposes of this guide, we will use the same physical network to support both the Management and External/Public networks. In addition, while the Network Service can be run on an external server or on a VM, for this guide we will designate one VM to run ConVirt's Network Service.

Provision Network Service VM

  1. Provision a Linux VM on one of your hosts
    • Use ConVirt to provision an Ubuntu 12.04 VM on one of your hosts
    • Provision it with 2 virtual NICs:
    eth0 for the External/Public and Management interfaces, connecting to hv-switch0
    eth1 for the VM Network/Private VLAN interface, connecting to vm-switch0 (note: this network should allow all VLANs!)
    Getting started hyperv5.png
    • Connect to the VM and set up a root password by typing:
    sudo (you'll be prompted for the password that you used at the time of installation)
    su -l root
    passwd (enter the password for the root user)
    • Ensure that you install kvm on this VM.
    sudo apt-get install qemu-kvm libvirt-bin ubuntu-vm-builder bridge-utils
    • Create a kvm directoiry (this allows the CMS to discover the VM as a KVM host):
    mkdir /dev/kvm
  2. Copy convirt-tool tarball from the CMS to the VM
    • Login to CMS server as CMS user account
    • Copy the convirt-tool tarball to the VM
    scp convirture-enterprise-tools-3.4.7.tar.gz root@virtualmachine:/root
  3. On the VM, extract the contents of the archive into a directory. For example:
    tar -xzf convirture-enterprise-tools-3.4.7.tar.gz
  4. Change to the ~/convirture-enterprise-tools/install/managed_server/scripts directory. For example:
    cd ./convirture-enterprise-tools/install/managed_server/scripts
  5. Install required dependencies:
    ./convirt-tool install_dependencies
    If you find this step failing you might consider running sudo apt-get update and re-run installation of dependencies.
  6. Use the convirt-tool command to configure the VM (make sure to include the "--skip_bridge" option as you do not need to create bridges on all interfaces):
    ./convirt-tool --skip_bridge setup
  7. Take note of the details needed to register the VM with ConVirt in the next section
    • Get the IP address of the eth0 interface
    ifconfig eth0

Discover Network Service VM Into ConVirt

  1. Add a new server pool to hold the Network Service host
    • Make sure the type is "KVM"
  2. Add the Network Service virtual machine as a KVM host
    • Right click on the new server pool, and select Add Server
      • Select KVM as the platform type
    • In the Add Server dialog, enter the following info to import the Network Service virtual machine as a host:
      • Host Name - use the IP address of the eth0 interface of the Network Service VM
      • Username/Password - enter the root credentials for the VM that you set up in the previous section
      • Click OK to add the server
  3. You should see the virtual machine added as a host under the new server pool you created.

3.1.2 VLAN ID Pool

ConVirt creates private virtual networks for isolation. One such network is created each time a new self-service Virtual Data Center is provisioned. In addition, ConVirt has the capability to allow users to create their own private networks. To do this, ConVirt requires a VLAN ID when such a private network is created. For convenience, a VLAN ID Pool needs to be declared.

  1. Right click on Data Center and select Manage VLAN ID Pool
    Vcenter-412-1.PNG
  2. Click New on the Manage VLAN ID Pool dialog
    Vcenter-412-2.PNG
  3. In the VLAN ID Pool Detail window on the Definition tab, provide the appropriate details.
    Vcenter-412-3.PNG
  4. In the VLAN ID Pool Detail window on the Server Pools tab, select the server pools for which these VLAN IDs will be available, and click Save.
    Vcenter-412-4.PNG
  5. You've now created a pool of VLAN IDs that you can use to provision self-service Virtual Data Centers.
    Vcenter-412-5.PNG

3.1.3 Public IP Pool

ConVirt enables self-service Virtual Data Centers to optionally make their virtual machines accessible over the Internet by assigning a public IP address. To do this, you define a Public IP pool, and then assign Public IP quotas to Virtual Data Centers. Self-service Virtual Data Center clients can then request a Public IP, assign it to a virtual machine, and release it back into the Public IP pool.

Here's how to set up the Public IP pool:

  1. Right click on Data Center and select Manage Public IP Pool
    Vcenter-313-1.PNG
  2. This brings up the Manage Public IP Pool dialog showing the available pools. Click Add.
    411.png
  3. In the Public IP Pool dialog, specify the name of the pool and the IPs, then click Save.
    412.png
  4. The Manage Public IP Pool dialog is updated to show the new pool.
    413.png

3.2 Create A Local Cloud From Your Virtualized Resources

The first step in adding self service is to convert your virtualization infrastructure into a local cloud. To do this in ConVirt, an IaaS entity needs to be defined. With a few simple clicks, ConVirt’s IaaS wizard allows you to designate which parts of your existing infrastructure (server pools, networks, storage, and templates) should be used for the cloud deployment, then generates the IaaS.

  1. Right click on IaaS and select "Add IaaS" to create a new cloud resource
    Vcenter-32-1.PNG

  2. The type of cloud we're going to create uses "Local Infrastructure"
    Cloud3.png

  3. This brings up the Add Local Infrastructure Iaas dialog - put in a name and description of the cloud you want to create.
    Vcenter-32-3.PNG

  4. Select the server pool (local infrastructure) that you would like to use for the cloud
    Vcenter-32-4.PNG

  5. Select the network(s) you would like to make available to cloud users
    Vcenter-32-5.PNG

  6. Select the templates that you would like to make available to cloud users
    Vcenter-32-6.PNG

  7. Pick the Network Service host you created when you first set up ConVirt, and select the name/IP of the Network Service VM, enter the public (eth0) and private (eth1) interfaces, and click Save.
    • ConVirt will orchestrate your local resources together into an Infrastructure-as-a-Service cloud.
    Vcenter-32-7.PNG

  8. The new cloud should show up in the IaaS area of your navigation pane.
    Vcenter-32-8.PNG

3.3 Delegate Cloud Resources Via A "Virtual Data Center"

The next step in adding self service is to delegate some of these IaaS resources to your business customers. To do this in ConVirt, you create a Virtual Data Center (VDC), which allows customer administrators to use the IaaS cloud capacity without knowing any details about the underlying physical infrastructure. With a few simple clicks, ConVirt’s VDC wizard allows you to define the compute, template, storage and networks resources that will be made available, the quota limit for each resource, and the authorized users/administrators of the VDC. ConVirt automatically assembles the VDC based on your selections.

  1. Right click on Virtual Data Centers, and select Provision Virtual Data Center.
    Vcenter-33-1.PNG

  2. Next you choose the cloud resource you'd like the self-service console to use. Note that you can have multiple Virtual Data Centers utilizing a single IaaS cloud. Select the cloud you just created and click OK.
    Vcenter-33-2.PNG

  3. The Provisioning Virtual Data Center dialog should pop up, to walk you through the self-service definition. Type in an appropriate name and a description.
    Vcenter-33-3.PNG

  4. Select the templates you would like to make available via the self-service console. Note - the templates will be limited to what is available via the cloud resource you are using.
    Vcenter-33-4.PNG

  5. Select the network resources you would like to make available via the self-service console.
    Vcenter-33-5.PNG

  6. Next define the resources quotas for the self-service console. ConVirt enforces these quota limits so that users of the self-service consoles cannot go beyond the limits you set.
    Vcenter-33-6.PNG

  7. And finally, create or assign the administrator(s) for this self-service console. Note that you can assign existing users who were already defined as ConVirt admins, or you can integrate users from your LDAP or Active Directory, or you can create new users.
    Vcenter-33-7.PNG

  8. Click Save to create the self-service Virtual Data Center. You will receive a confirmation alert.
    Vcenter-33-8.PNG

  9. The new self-service console will show up under the Virtual Data Center section of the navigation pane. You can see the quota information in the Summary tab on the right.
    Vcenter-33-9.PNG

3.4 Provision & Manage VMs On A Self-Service Basis

Once the Virtual Data Center (VDC) is created, authorized users/administrators will be able to access and manage the environment from ConVirt's web-based console. Users/administrators are able to do things like create Virtual Machines; create networks (if configured at the time of VDC creation); start, stop and connect to Virtual Machines; delete/destroy Virtual Machines; and reserve a public IP address and associate it to a Virtual Machine.

  1. Open a different browser, and log in to the ConVirt Management Server using the self-service user credentials you just created.
    Vcenter-34-1.PNG

  2. What comes up is a version of ConVirt’s web-based console that shows only the resources that are authorized to be used in this self service environment.
    Vcenter-34-2.PNG

  3. In this self service environment, you have access to all the controls that ConVirt provides - the only limits are on the resources you can access. So lets go ahead and provision a virtual machine - right click on the Virtual Machines folder and select Provision Virtual Machine.
    Vcenter-34-3.PNG

  4. Type in a name for the virtual machine you'd like to create, and select a template to use.
    Vcenter-34-4.PNG

  5. Select the network(s) to use with the new VM...
    Vcenter-34-5.PNG

  6. Select or change the storage resources as appropriate, and click Save.
    Vcenter-34-6.PNG

  7. ConVirt provisions the new VM. Note that in the Summary section, the number of Provisioned Virtual Machines has been incremented by 1.
    Vcenter-34-7.PNG

  8. Next lets start the virtual machine - right click on it and select Start.
    Vcenter-34-8.PNG

  9. ConVirt starts the new VM. Note that in the Summary section, the number of Running Virtual Machines has been incremented by 1.
    Vcenter-34-9.PNG

  10. Now lets view the console for the new VM - right click on the VM and select Connect.
    Vcenter-34-10.PNG

  11. ConVirt prompts you for the local viewer you would like to use to connect to the VM.
    Vcenter-34-11.PNG

  12. The console window opens in a new window and you can get to work on your VM.
    Vcenter-34-12.PNG






4 Conclusion

This concludes our feature walkthrough. Hopefully it has given you a good feel for how ConVirt works, and the depth of functionality available in the product. Please check out some of the following sections of our website for more information:

Retrieved from "http://www.convirture.com/ee_wiki/index.php?title=Feat_vCenter"

This page has been accessed 12,214 times. This page was last modified on 26 February 2016, at 19:00.


Find

Browse
Main page
Installation
Documentation
Forums
Blog
Website
Recent changes
Random page
Help
Edit
View source
Editing help
This page
Discuss this page
New section
Printable version
Context
Page history
What links here
Related changes
My pages
Log in / create account
Special pages
New pages
File list
Statistics
More...