Working with VMware’s API via Python
(Update – Sept. 2, 2015)
In some of the community samples, someone wrote a nice function to get different objects.
As part of streamlining VM creation, I began working with VMware’s API. The first thing I learned is that there are multiple API implementations. Until recently, while VMware had their own Python API, they kept it private and did not officially support it. That prompted folks to write their own bindings and share them via Google Code in a project called pySphere (https://code.google.com/p/pysphere/). In early 2014, however, VMware did release their bindings to the public (https://github.com/vmware/pyvmomi).
Wanting to go the official route, I downloaded pyVmomi and got to work. From the beginning I noticed that this API is very thorough and robust. The downside of that is that it is also very complex and can sometimes be difficult to know just how to get and do what you need. Fortunately there are many good samples included in the code. So, while it takes a lot of effort to get things just right, once you get the objects and methods sorted out, it works well. And fortunately the documentation (vmware python API doc), if you can stay awake while you wade through it, will tell you what you need.
I won’t go into how I did each and every thing. The goal of this document is to give the reader a decent understanding of how to create and manipulate objects, as well as how to make the method calls.
What to import
The basic script should have the following items.
from pyVmomi import vim– this module contains what we need to create objects and make calls
from tools import tasks– if we’re going to create anything in vCenter, this module allows us to designate the creation process as a task, then wait for it to finish
from pyVim import connect– needed to login
import atexit– this module allows us to specify that, when we logout, certain things should happen (such as logging out)
import argparse– if we’re going to accept command-line input, this module greatly simplifies managing that input
To get information (such as a list of VMs) or do things (such as create a VM), the system requires a session to be established and objects to be passed to the method calls. Establishing a session is as simple as logging in, which is covered in the sample code included in the project, so I won’t cover that here. The samples refer to the session as a service instance, often shortened as “si”. For this document, you will notice the service-instance object referred to as “si”.
A few basic objects
Once we’re logged in we need a few fundamental objects from which we can build others. For my scripts, I use these:
- atexit.register(connect.Disconnect, si)
- content = si.RetrieveContent()
- datacenter = content.rootFolder.childEntity
- hosts = datacenter.hostFolder.childEntity
These are mostly self-explanatory. The second item, “content,” is essentially “all the things” in this vCenter. From those we get access to pretty much any object that the API allows us to reference.
The fun begins
The challenge began when I wanted to create a new VM by cloning a template. While the API is, as I said, very thorough and complex, the documentation is equally so. But it’s also confusing at times. I’ll demonstrate using parts of the cloning process.
While there is a method called CloneVM_Task, that is the wrong call if you want your VM placed in a certain datastore cluster but do not want to specify which store it lands it. CloneVM_Task forces you to specify the specific datastore for your new VM. The proper way to do that is with a combination of RecommendDatastores and ApplyStorageDrsRecommendation_Task.
This method requires one object (called a parameter in the doc). While the documentation page lists two parameters (_this and storageSpec), the first of those is really a parent object against which we run the method. I’ll elaborate on that in a second. But first let me point out that any parameter named “_this” in the documentation means you call the method in question by appending it to an object to which “_this” refers. Demonstration:
RecommendDatastores lists two parameters: _this and storageSpec. We actually call it like so:
storage_rec = content.storageResourceManager.RecommendDatastores(storageSpec=storagespec)
So, “_this” gets translated into ” content.storageResourceManager” and we call the method using storageSpec, which is an object we have to have already built.
Now, how the heck would you have known that? Well, you wouldn’t intrinsically. There are three ways to find that out: either you figure it out from the included samples, you find it from samples in the discussion lists for pysphere (because pysphere is pretty close to pyVmomi), or you catch a clue from the documentation page. In this case, the documentation URL for this method ends with this text:
Additionally, in the left pane of the documentation the method lists its parent namespace in parentheses, i.e. “RecommendDatastores (in StorageResourceManager)”
But you might not have guessed it is called under the “content” object without further digging or experimentation. Plainly put, it just takes some intuition and hacking sometimes to get this right.
And that’s just the tip of the iceberg. You could be forgiven for thinking, “Oh, this only has one object. No worries.” Why? Because “storageSpec” contains a lot of other objects. And many of those contain other objects, etc. And many of those objects must first be instantiated (a decidedly object-oriented programming term) by a method before they can be used.
Ready to quit yet? Don’t. There’s a good payoff to sticking with this stuff. At the least it will stretch your mind and deepen your understanding of how VMware works under the hood. And what bit-head doesn’t want that?
Looking at storageSpec, it wants an object of type “StoragePlacementSpec“. As we drill into that, we see this object consists of several other objects. And, as I said, some of them have many more objects in their definition. Let’s pick a somewhat simple one: podSelectionSpec. This particular data type (StorageDrsPodSelectionSpec) tells VMware which datastore cluster we want to use for the new VM. Of the two objects that this data type uses, we are only interested in the second one, storagePod.
Unfortunately, because these are custom data types, we cannot simply say
storagePod = “MyStoragePod” and expect the API to intuit what we want. In place of “MyStoragePod” we need a data type of StoragePod which points to the pod named “MyStoragePod”. In our case, from the samples I took a bit of code which created a view of the storage pods, then I parsed through that list and compared each pod name to our target (“MyStoragePod”) and, when we got a match, assigned that to a variable named “pod”. So, below, first we create a view, then we destroy the view so we do not consume too many resources in the vHost. And finally we parse through the view until we find a match.
obj_view = content.viewManager.CreateContainerView(content.rootFolder,[vim.StoragePod],True) ds_cluster_list = obj_view.view obj_view.Destroy() for ds in ds_cluster_list: if ds.name == "MyStoragePod": pod = ds break # a blank object of type PodSelectionSpec podsel = vim.storageDrs.PodSelectionSpec() podsel.storagePod = pod
And thus we have our pod selection. To add that to our primary object, a StoragePlacementSpec data type, I create the blank object, then add to it:
# a blank type of StoragePlacementSpec storagespec = vim.storageDrs.StoragePlacementSpec() storagespec.podSelectionSpec = podsel
So, in short, we first create a blank parent object (similar to initializing a variable in other languages), then we assign the child object to be a part of the parent object. Again, the tricky part is finding a way to identify those child objects.
Update – Sept. 2, 2014 –
def get_obj(content, vimtype, name): """ Return an object by name, if name is None the first found object is returned """ obj = None container = content.viewManager.CreateContainerView( content.rootFolder, vimtype, True) for c in container.view: if name: if c.name == name: obj = c break else: obj = c break return obj
Now all you have to do is call that function with the proper “vimtype”. A few that are useful:
# gets a datastore cluster (storage pod) matching "DS-Cluster1" cluster = get_obj(content, [vim.StoragePod], "DS-Cluster1") # gets a host cluster matching "My-Host-Cluster" cluster = get_obj(content, [vim.ClusterComputeResource], "My-Host-Cluster") # gets a resource pool matching "My-Resource-Pool" cluster = get_obj(content, [vim.ResourcePool], "My-Resource-Pool") # gets a datastore matching "Datastore1" cluster = get_obj(content, [vim.Datastore], "Datastore1")
Doing stuff to the objects
Once we have built our objects, we can create the VM. Or, in our case, clone a template into a VM. Before I discuss the methods, here are the steps I used to create the VM object.
template = getTemplate(si, tierdata['template']) if template == None: print "Unable to find template matching %s" % template # make an empty clone spec object, then customize it print("Checkpoint - getting customization data") cloneSpec = vim.vm.CloneSpec() custSpec = content.customizationSpecManager.GetCustomizationSpec(tierdata['customization_spec']) # dev_gold custSpec.spec.nicSettingMap.adapter.ip.ipAddress = VMip custSpec.spec.nicSettingMap.adapter.gateway = gateway cloneSpec.customization = custSpec.spec # make an empty config spec, then customize it config = vim.vm.ConfigSpec() config.name = machine_name cloneSpec.config = config location = vim.vm.RelocateSpec() cloneSpec.location = location # if we cannot find resource pool with name given by user, use default for this vHost print("Checkpoint - getting resource pool data") resourcePool = getResourcePool(hosts,tierdata['resource_pool']) # "MyStoragePod" if resourcePool == None: print("Unable to find resource pool named %s" % tierdata['resource_pool']) # MyStoragePod sys.exit(1) cloneSpec.location.pool = resourcePool cloneSpec.powerOn = powerOn # using name of target cluster (i.e. MyStoragePod), parse thru clusters until we find a match print("Checkpoint - getting datastore cluster data") obj_view = content.viewManager.CreateContainerView(content.rootFolder,[vim.StoragePod],True) ds_cluster_list = obj_view.view obj_view.Destroy() for ds in ds_cluster_list: if ds.name == tierdata['datastore']: # MyStoragePod pod = ds break # set thin provisioning on disks device = vim.vm.device.VirtualDevice() vdisk = vim.vm.device.VirtualDisk() backing = vim.vm.device.VirtualDisk.FlatVer2BackingInfo() vdisk.backing = backing vdisk.backing.thinProvisioned = True vdisk.key = -100 dspec = vim.vm.device.VirtualDeviceSpec() dspec.device = vdisk config.deviceChange = [dspec] # make an empty pod selection spec, then customize it podsel = vim.storageDrs.PodSelectionSpec() podsel.storagePod = pod # make an empty storage placement spec, then customize it storagespec = vim.storageDrs.StoragePlacementSpec() storagespec.podSelectionSpec = podsel storagespec.vm = template storagespec.type = 'clone' print("Checkpoint - getting destination folder data") storagespec.folder = getDestFolder(datacenter, "Development", "Applications") storagespec.cloneSpec = cloneSpec storagespec.cloneName = machine_name storagespec.configSpec = config '''Once that is done, we have built our VM object. The method we use to create the VM is "RecommendDatastores", which we call like so:''' rec = content.storageResourceManager.RecommendDatastores(storageSpec=storagespec) '''This asks vCenter to tell us which datastore within the cluster it prefers to use for this host. That method returns an object, which I chose to call "rec". One of the recommendation objects is a key, which we will use to actually apply the recommendation. Interesting note: when you create a VM from a template within the GUI, you see a similar process. You select a datastore and the GUI returns recommendations. To apply the recommendation, we use another set of objects VMware provided known as tasks. Using that framework, we are able to tell the script to wait until the task finishes before continuing.''' rec_key = rec.recommendations.key task = content.storageResourceManager.ApplyStorageDrsRecommendation_Task(rec_key) tasks.wait_for_tasks(si, [task])
(Note that VMware will proceed with the task whether we execute the last step or not. It is wise and courteous on our part to let it finish each VM creation before proceeding to the next.)
At this point, in the GUI you will see the clone process taking place. It typically finishes within 2-3 minutes. If there are any errors, you will see those in the GUI as well. You can copy the text of them for research. Additionally, the Python code will throw an exception which usually matches the GUI message fairly well.