This pack integrates with vsphere and allows for the creation and management of Virtual Machines.

You will need to specificy the details of the vcenter instance you will be connecting to within the /opt/stackstorm/config/vsphere.yaml file. You can specificy multiple environments using nested values

---
ssl_verify: 
vsphere:
  dev:
    host:
    port:
    user:
    passwd:
  staging:
    host:
    port:
    user:
    passwd:

Note: To ensure backward compatability and ease for single environment use. If no vsphere value is passed to the actions it will look for v0.3 config.yaml structure:

  ssl_verify:
  host:
  port:
  user:
  passwd:

Please Note Configuration validation will raise an exception if config.yaml contains 'vsphere' but no defined endpoints.

This sensor observes TaskInfo which is invoked on the vSphere environment which is specified in the configuration after the TaskInfoSensor is started.

This is the configuration parameters for this.

sensors:
  taskinfo:
    tasknum: # indicates the task numbers to check at once
    vsphere:

These are the each parameters meaning to be set.

• tasknum: The maximum TaskInfo numbers to get from vCenter at once (1 is set as default when setting this value is omitted). When you specify the number of greater than 1 and a number of Tasks which are less than the tasknum are occurred, vCenter returns the actual occurred TaskInfos. And when a number of Tasks which are greater than the tasknum are occurred, TaskInfoSensor dispatches them iteratively until the all TaskInfos is done during a polling interval.

• vsphere: The name of vSphere environment to observe (default is set as default when setting this value is omitted). This value must be same with the value of the name of vSphere environment which is specified in the configuration for connecting (please see Connection Configuration).

This trigger is emitted for every task information that is invoked on the specified vSphere environment in the configuration.

Here is a example of a trigger payload.

{
  queue_time: 2017/03/10 02:08:39,
  start_time: 2017/03/10 02:08:39,
  complete_time: 2017/03/10 02:08:40,
  operation_name: VirtualMachine.destroy,
  task_id: task-5714
}

Each of parameters mean following.

• Create actions for vsphere environment data retrieval. Allowing for integration with external systems for accurate action calls with informed parameter values.
• Review and implement ST2 1.5 config.yaml changes. Review how useable dynamic configuration can be in case of this Packs purpose.
• Expand base test files. Level of mocking required has limited this at present.

This pack requires the python module PYVMOMI. At present the requirements.txt specifies version 5.5.0. The version specification is to ensure compatibility with Python 2.7.6 (standard version with Ubuntu 14.04). PYVMOMI 6.0 requires alternative connection coding and Python 2.7.9 minimum due to elements of the SSL module being used.

• vsphere.get_moid - Returns the MOID of vSphere managed entity corresponding to the specified parameters
• vsphere.get_vmconsole_urls - Retrieves urls of the virtual machines' consoles
• vsphere.get_vms - Retrieves the virtual machines on a vCenter Server system. It computes the union of Virtual Machine sets based on each parameter.
• vsphere.hello_vsphere - Wait for a Task to complete and returns its result.
• vsphere.set_vm - Changes configuration of a Virtual Machine.
• vsphere.vm_check_tools - Wait for a Task to complete and returns its result.
• vsphere.vm_create_from_template - Create a new VM from existing template.
• vsphere.vm_env_items_get - Retrieve list of Objects from VSphere
• vsphere.vm_hw_barebones_create - Create BareBones VM (CPU, Ram, Graphics Only)
• vsphere.vm_hw_basic_build - Minstral Flow to Build Basic Server and power it on.
• vsphere.vm_hw_cpu_mem_edit - Adjust the CPU and RAM values assigned to a Virtual Machine
• vsphere.vm_hw_detail_get - Retrieve Vsphere Data about a virtual machine
• vsphere.vm_hw_hdd_add - Add a HardDrive Object to a Virtual Machine
• vsphere.vm_hw_moid_get - Retrieve VM MOID
• vsphere.vm_hw_nic_add - Add a Network Device to VM and attach to designated network.
• vsphere.vm_hw_nic_edit - Edit Network Device on Virtual machine (V0.2 only allows to switch network)
• vsphere.vm_hw_power_off - Perform VM Power off - Equivilant of Holding power button
• vsphere.vm_hw_power_on - Power on Virtual Machine
• vsphere.vm_hw_remove - Removes the Virtual Machine.
• vsphere.vm_hw_scsi_controller_add - Add SCSI HDD Controller device to VM
• vsphere.vm_hw_uuid_get - Retrieve VM UUID
• vsphere.wait_task - Wait for a Task to complete and returns its result.

• Bug: vm_hw_hdd_add, Specifying datastore does not work. New files will be added to the same datastore as the core VM files. Note. Specifying a Datastore Cluster does still install files to the correct set of datastores.