vCloud Director - Managing VMs

Before starting this chapter, please make sure you're on My Cloud section of vCloud Director.

My Cloud section welcome screen will look something like this (once you have Virtual Machines).

Managing VMs

The initial view of My Cloud will show you a list of vApps.

To get to a list of Virtual Machines, you can double click the vApp "row" in vCloud Director, or click onto the vApp Name itself.

The initial view of VMs within a vApp will be the vApp Network Diagram.

While it looks cool, it's not the most useful of views, so if you're like us, you will find yourself in the Virtual Machines Tab most of the time.

In this table view, you will get a list of all Virtual Machines within a vApp (very similar to view of all vApps in your Virtual Datacenter) we looked at in previous chapter.

The top menu of VMs section contains a couple of useful options as well:

These will look very familiar, as a few of them ovelap with the vApp options we'e seen earlier, but we'll mention them regardless.

Adding a VM to a vApp

This is one of the most common actions you'll perform on day-to-day basis.

option will open up a New VM Wizard which will guide you through the process of adding a new Virtual Machine to a vApp.

You will have the option to deploying VMs from within Existing vApps in your (or Public) Catalogs:

and to create brand new blank VMs onto which you can install the Operating System after they've been created:

As we have gone through Deploying a vApp from Catalogs in previous chapter (which is quite self explanatory), we will take some space in this chapter to demonstrate how one can create a brand new, fresh VM instead.

After clicking the New Virtual Machine... button, a form will pop-up with a number of options for configuring the new Virtual Machine.

  • Virtual Machine Name is simply the name you want to give to your new VM (say: Web-01).

  • Compter Name is your virtual machine's hostname. This may or may not get passed to Virtual Machine's OS (depending on VMware Tools), but it's recommended to set it to something similar to VM Name (say: web-01).

  • Description is exactly what it says, a short description of what this machine does, or for VMs that will be a part of deployable template in the future, you could put a default Username and Password info here.

  • Unless there is a reason for choosing something less than the highest version offered (in this case HWv10), you should leave it at default. The higher the version, the more advanced Virtual Hardware presented to a VM will be, however, some older Operating Systems may not like this.

  • While OS Family option will not install the selected OS for you, it will present the most compatible hardware for chosen operating system to your VM. It is recommended to match this option, as well as teh Operating System option below it to exactly the OS you will install after creating the VM.

  • This is one of the most important settings for your Virtual Machine. Unless you have a completely valid reason (such as application specs instruct you to do otherwise), you should ony set the # of Virtual CPUs and leave Cores per Socket at default. If you require assistance with this, please feel free to contact Cloud Propeller Support.
  • WARNING: the most common performance issue with Virtual Machines comes from setting too many CPU cores on a VM in hopes of getting higher performance. Best action one can take is to start with just 1 or 2 cores, enable VM's CPU Hot-Add option (as we'll show below), and add extra cores as needed.
  • If you add too many cores, due to the way VM CPU Scheduling works, your machine may experience a syndrom called High CPU Ready Time and it will behave extremely slow and may be quite unresponsive.
  • If you run into any performance issues, contact us and we'll assist. In 9 out of 10 performance related cases, the solution has been to allocate LESS CPU cores to a VM.

results matching ""

    No results matching ""