Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 67 Next »


Introduction

By sending requests to the Virtual Machine endpoint /v2/vm you can list, create, update or delete VMs. The Virtual Machine endpoint has the following methods available:

ResourceURIDescriptionGETPOSTPUTDELETE
Virtual Machine/vmVirtual Machine management resource. Read, update, delete, create virtual machines.(tick)(tick)(tick)(tick)

OPTIONS HTTP method

Remember, you can also show what methods are allowed and method description, parameters, etc. by making a GET HTTP request to /v2/vm.

http OPTIONS "https://vss-api.eis.utoronto.ca/v2/vm"
curl -X OPTIONS "https://vss-api.eis.utoronto.ca/v2/vm"

On this page:

Create

Single Virtual Machine

To create a new Virtual Machine, send a POST request to /v2/vm. The attribute values that must be set to successfully create a Virtual Machine are marked with a (tick) in the following table:

AttributeDescriptionTypeRef URIOptionsDefaultRequired
admin_emailAdministrator's emailstring--User's email number submitting the request-
admin_nameAdministrator's namestring--User's name number submitting the request-
admin_phoneAdministrator's phone numberstring--User's phone number submitting the request-
clientClient Departmentstring---(tick)
built_from

Build process. If you are installing OS from scratch use os_install.

Clone when deploying a VM from a running or powered off virtual Machine.

Template gives the ability to deploy multiple VMs at the same time.

string-

os_install

clone

template

image

contentlib

-(tick)
cpuCPU countinteger--1-
descriptionShort description of the service or application. This will be part of the annotations field.string---(tick)
disksDisks in GigaBytes.array or array of objects--

[40]

[

{"capacity_gb": 40,

"backing_mode": "persistent",

"backing_sharing": "nosharing"}

]

-
high_io

If set to true,VM will be created with a VMware Paravirtual SCSIController.

PVSCSI controllers are best suited for environments, especially SAN environments, running I/O-intensive applications.

boolean-

True

False

False-
domainFault domain moId (Managed Object Identifier)string/v2/domain-Fault Domain -
folderFolder moId (Managed Object Identifier)string/v2/folder--(tick)
informInformational comma separated emails or list of email addresses.string or list of strings--User's email submitting the request-
isoISO image path to be mounted after creationstring/v2/iso-None-
memoryMemory in GBinteger--1-
nameHuman readable name without the VSS Prefix. This prefix will be added before creation.string--Randomly generated-
networks

Network interface controller object.

[{"network": "moref-or-name", "type": "valid-type"}]

Each network will be attached to a NIC type specified or if not, vmxnet3, the most recent virtual network device from VMware, and was designed from scratch for high performance and to support new features.

array/v2/network-Unaccessible VLAN-
os

Supported guest operating system identifier.

string/v2/os--(tick)
usageVirtual Machine usage. Prod for Production, Test for testing, QA for Quality Assurance, and Dev for Development.string-

Prod

Test

QA

Dev

Test-
notesClient notes to be stored in the annotation field.string----
source_vmSource Virtual Machine Moref or Uuid.string

/v2/vm


--

(tick) only with clone

source_vm_snap_idClone virtual machine from source snapshotinteger/v2/vm/<id>/snapshot--(tick) only with clone
source_clibSource Deployable (VM or OVF) Content Library item name or ID.string/v2/contentlib/item

(tick) only with contentlib
source_templateSource Virtual Machine Template Moref or UUID.string/v2/template--(tick) only with template
source_imageSource OVA/OVF Virtual Machine file stored in VSKEY-STORstring/v2/image--(tick) only with image
user_dataCloud-init user_data to preconfigure the guest os upon first boot. Note: Experimental feature and currently tested with Ubuntu Cloud Images and VMware Photon OS. Only supported on OVA/OVF deployments.string----
extra_configAllows to Set VMware guestinfo interface properties which are available to the VM guest operating system via VMware Tools. These properties are stored in the VMX file prefixed with "guestinfo.".array of objects----
custom_specCustomize a guest operating system to prevent conflicts if virtual machines are identical after deployed. To customize the guest operating system, you must configure the virtual machine and guest to meet VMware Tools and virtual disk requirements.dict---recommended with clone and template deployment







power_onPower on virtual machine after successful deploymentboolean-False--
ha_groupCreate high availability group metadata (based on morefs)array or string/v2/vm---
vss_optionsSets available VSS Options to virtual machine metadata.array or string/v2/vss/options---
vss_serviceTags Virtual Machine with a specific predefined service.string/v2/vss/service--(tick) only for ITS users
retirement

Create a Retirement request for the virtual machine. The retirement request allows to set a retirement date for a virtual machine.

There are currently two types:

  • timedelta: days, months and hours from now until retirement.
  • datetime: specific timestamp to retire vm.


Timedelta
{
 "value": {"type": "timedelta", "days": 4, "months": 6, "hours": 0},
 "warning": {"days": 15}
}
Datetime
{
 "value": {"type": "datetime", "datetime": "2021-10-20 10:00"},
 "warning": {"days": 15}
}

warning is optional but if not set, no notification will be sent to confirm or cancel retirement.

object----

A new virtual machine can be created with as few as the following attributes in JSON format:

Request Body
{"usage": "Prod",
 "os": "ubuntu64Guest",
 "built_from": "os_install",
 "client": "EIS",
 "description": "Java web application.",
 "folder": "group-v4122",
 "networks": [{"network": "dvportgroup-95", "type": "e1000"}, {"network": "dvportgroup-92"}],
 "disks": [40, 100],
 "power_on": true
}

HTTPie

http POST "https://vss-api.eis.utoronto.ca/v2/vm" "Authorization: Bearer $TK" usage='Prod' os='ubuntu64Guest' built_from='os_install' client='EIS' description='Java web application.' folder='group-v4122' networks:='[{"network": "dvportgroup-95", "type": "e1000"}, {"network": "dvportgroup-92"}]' disks:='[40, 20]' power_on:=true

CURL

curl -H "Content-Type: application/json" -H "Authorization: Bearer $TK" -X POST "https://vss-api.eis.utoronto.ca/v2/vm" -d '{"usage": "Prod", "os": "ubuntu64Guest", "built_from": "os_install", "client": "EIS", "description": "Java web application.", "folder": "group-v4122", "networks": [{"network": "dvportgroup-95", "type": "e1000"}, {"network": "dvportgroup-92"}], "disks": [40, 100], "power_on": true}'

If the request was successfully submitted and all parameters were accepted, the following Response Status, Headers and body will be received:

Response Headers
HTTP/1.0 202 ACCEPTED
Allow: HEAD, POST, OPTIONS, GET
Content-Length: 364
Content-Type: application/json
Date: Tue, 26 Apr 2016 18:24:23 GMT
Location: https://vss-api.eis.utoronto.ca/v2/request/task/fa276e28-a876-477a-ab40-0d2d84df9234
X-RateLimit-Limit: 7200
X-RateLimit-Remaining: 7190
X-RateLimit-Reset: 1461697200
Response Body
{
   "data": {
    "_links": {
        "request": "https://vss-api.eis.utoronto.ca/v2/request/new/8",
        "task": "https://vss-api.eis.utoronto.ca/v2/request/task/fa276e28-a876-477a-ab40-0d2d84df9234"
    },
    "message": "Request has been accepted for processing",
    "name": "Accepted",
    "request": {
        "id": 8,
        "status": "Submitted",
        "task_id": "fa276e28-a876-477a-ab40-0d2d84df9234"
    },
    "status": 202
    }
}

Note that you will receive as well additional Hypermedia links contained in the _links attribute. Request object is the new virtual machine creation request which stores all parameters previously submitted and Task, is the unique task in charged of processing your request. Request and Task are both related, in terms of status, errors and warnings. Request will store any status or errors caught by the task, also it will pass the recently created VM Uuid.

Task

Request processing is almost instantaneous, however you could check the task progress by making a HTTP GET request to any given /v2/request/task/<task_id> endpoint.

Response Body
 {
    "_links": {
        "request": "https://vss-api.eis.utoronto.ca/v2/request", 
        "self": "https://vss-api.eis.utoronto.ca/v2/request/task/a57a3d4a-9e94-4822-a1d3-f99db1005dbd"
    }, 
    "data": {
        "result": {
            "current": 100, 
            "result": {
                "errors": [], 
                "warnings": [
                    "Fault Domain: FD3 ", 
                    "Created in: VSS > Sandbox > jm", 
                    "Network adapter 1: 00:50:56:92:50:6d: VL-1102-UTCS", 
                    "Network adapter 2: 00:50:56:92:3f:91: VL-1072-VSGAN"
                ]
            }, 
            "status": "1604P-desperate_thompson Processed", 
            "total": 100
        }, 
        "status": "SUCCESS"
    }, 
    "meta": {
        "count": 2, 
        "time": "0.00028s", 
        "user": "jm"
    }
}

Request 

Checking the overall status of the request and also the resulting Uuid can be done by making a HTTP GET request to /v2/request/new/8 endpoint:

Response Body
{
    "_link": {
        "request": "https://vss-api.eis.utoronto.ca/v2/request/new",
        "self": "https://vss-api.eis.utoronto.ca/v2/request/new/180"
    },
    "data": {
        "_links": {
            "task": "https://vss-api.eis.utoronto.ca/v2/request/task/6f642f4b-6be1-4fba-aabd-eab7f6366912",
            "user_data": "https://vss-api.eis.utoronto.ca/v2/request/new/180/user_data",
            "vm": "https://vss-api.eis.utoronto.ca/v2/vm/501219a5-a563-787c-f334-e7b65e829dca"
        },
        "annotation": [
            "VM Name: 1608T-sw-node2",
            "UTvssAdmin: Jose Manuel Lopez Lujan:416-577-7061:jm.lopez@utoronto.ca",
            "UTvssClient: EIS",
            "UTvssPurpose: Testing",
            "UTvssRequested: 2016-08-26 15:03:50 ",
            "UTvssInform: jm.lopez@utoronto.ca",
            "Description: deploying the new docker swarm cluster",
            ""
        ],
        "built_from": "image",
        "cpu": "1",
        "created_on": "2016-08-26 15:03:50 EDT",
        "disks": [
            10,
            40,
            40,
            40
        ],
        "domain": "domain-c5877",
        "dvd_cd": "",
        "folder": "group-v7505",
        "guest_os": "ubuntu64Guest",
        "high_io": false,
        "id": 180,
        "memory": "1",
        "message": {
            "errors": [],
            "warnings": null
        },
        "networks": [
                 {"network": "dvportgroup-95", "type": "e1000"}, 
                 {"network": "dvportgroup-92", "type": "vmxnet3"}
        ],
        "source_image": "images/wily-server-cloudimg-amd64.ova",
        "status": "Processed",
        "task_id": "6f642f4b-6be1-4fba-aabd-eab7f6366912",
        "updated_on": "2016-08-26 15:04:42 EDT",
        "user": {
            "_links": {
                "self": "https://vss-api.eis.utoronto.ca/v2/user"
            },
            "username": "josem"
        },
        "vm_name": "1608T-sw-node2",
        "vm_uuid": "501219a5-a563-787c-f334-e7b65e829dca",
        "workdir": "/data/imports/5279a6a4-87bc-4d5d-89a6-8458912d1b53"
    },
    "meta": {
        "count": 23,
        "time": "0.00968s",
        "user": "josem"
    }
}

Multiple Virtual Machines

To create multiple Virtual Machines, send a POST request to /v2/vm. Creating multiple VMs is quite similar to creating a single VM, but instead of sending name as a string, send names as an array and select the right built process, either clone or template. The following request body is used to deploy three VM from a VM template:

Request Body
{"": "EIS",
 "built_from": "template",
 "description": "Ubuntu cluster",
 "os": "ubuntu64Guest",
 "folder": "group-v4122",
 "source_template": "50123c4c-c810-5c0f-6203-eac67f0cb7e8",
 "names": ["Ubuntu1", 
           "Ubuntu2", 
           "Ubuntu3"],
 "networks": [
                 {"network": "dvportgroup-95", "type": "e1000"}, 
                 {"network": "dvportgroup-92", "type": "vmxnet3"}
        ],
 "disks": [40, 100]}

The main difference between selecting clone or template as built process is that a source VM Template can deploy multiple instances concurrently, whereas a VM Clone can only be deployed concurrently when the source Virtual Machine is powered off. If VM is powered On, it can only be cloned one at a time.

HTTPie

http POST "https://vss-api.eis.utoronto.ca/v2/vm" "Authorization: Bearer $TK" os='ubuntu64Guest' built_from='template' client='EIS' description='Ubuntu cluster' folder='group-v4122' networks:='[{"network": "dvportgroup-95", "type": "e1000"}, {"network": "dvportgroup-92"}]' disks:='[40, 100]' names:='["Ubuntu1", "Ubuntu2", "Ubuntu3"]' source_template=50123c4c-c810-5c0f-6203-eac67f0cb7e8

CURL

curl -H "Content-Type: application/json" -H "Authorization: Bearer $TK" -X POST "https://vss-api.eis.utoronto.ca/v2/vm" -d '{"client": "EIS", "built_from": "template", "description": "Ubuntu cluster", "os": "ubuntu64Guest", "folder": "group-v4122", "source_template": "50123c4c-c810-5c0f-6203-eac67f0cb7e8", "names": ["Ubuntu1", "Ubuntu2", "Ubuntu3"], "networks": [{"network": "dvportgroup-95", "type": "e1000"}, {"network": "dvportgroup-92"}], "disks": [40, 100]}'
If the request was successfully submitted and all parameters were accepted, the following Response StatusHeaders and body will be received:
Response Headers
HTTP/1.0 202 ACCEPTED
Allow: HEAD, POST, OPTIONS, GET
Content-Length: 682
Content-Type: application/json
Date: Wed, 27 Apr 2016 14:16:42 GMT
X-RateLimit-Limit: 7200
X-RateLimit-Remaining: 7191
X-RateLimit-Reset: 1461769200
Response Body
{
    "data": {
        "_links": {
            "requests": [
                "https://vss-api.eis.utoronto.ca/v2/request/new/26", 
                "https://vss-api.eis.utoronto.ca/v2/request/new/27", 
                "https://vss-api.eis.utoronto.ca/v2/request/new/28"
            ], 
            "tasks": [
                "https://vss-api.eis.utoronto.ca/v2/request/task/aa1cc5fa-94fc-473f-b29c-47f022745eb2", 
                "https://vss-api.eis.utoronto.ca/v2/request/task/97d1f968-dec5-4249-b23c-226b46258483", 
                "https://vss-api.eis.utoronto.ca/v2/request/task/0ec62b83-6c7f-47ae-8670-588449c3a2cb"
            ]
        }, 
        "message": "New VM Requests have been accepted for processing", 
        "name": "Accepted", 
        "status": 202
    }, 
    "meta": {
        "time": "0.10215s", 
        "user": "jm"
    }
}

The main difference between single and multiple vm creation/deployment is the number of requests and tasks returned by the API. In this case, since we required three VMs, we get the same number of requests and tasks as a result of the POST request, which can be queried individually to verify its progress or result.

Task

Request processing is almost instantaneous, however you could check the task progress by making a HTTP GET request to any given /v2/request/task/<task_id> endpoint.

Response Body
 {
    "_links": {
        "request": "https://vss-api.eis.utoronto.ca/v2/request/", 
        "self": "https://vss-api.eis.utoronto.ca/v2/request/task/aa1cc5fa-94fc-473f-b29c-47f022745eb2"
    }, 
    "data": {
        "result": {
            "current": 100, 
            "result": {
                "errors": [], 
                "warnings": [
                    "Hard disk 1 capacity is the same. No change need to be done.", 
                    "Fault Domain: FD3 ", 
                    "Created in: VSS > Sandbox > jm", 
                    "Network adapter 1: 00:50:56:92:08:08: VL-1102-UTCS", 
                    "Network adapter 2: 00:50:56:92:14:fe: VL-1072-VSGAN"
                ]
            }, 
            "status": "1604T-Ubuntu1 Processed", 
            "total": 100
        }, 
        "status": "SUCCESS"
    }, 
    "meta": {
        "count": 2, 
        "time": "0.00597s", 
        "user": "jm"
    }
}

Requests

Checking the overall status of the requests and also the resulting Uuid can be done by making a HTTP GET request to /v2/request/new/26 - 28 endpoint:

Response Body
{
    "_link": {
        "request": "https://vss-api.eis.utoronto.ca/v2/request/new", 
        "self": "https://vss-api.eis.utoronto.ca/v2/request/new/26"
    }, 
    "data": {
        "_links": {
            "task": "https://vss-api.eis.utoronto.ca/v2/request/task/aa1cc5fa-94fc-473f-b29c-47f022745eb2", 
            "vm": "https://vss-api.eis.utoronto.ca/v2/vm/5012826a-6a1a-815a-249d-7d6eb640f020"
        }, 
        "annotation": [
            "VM Name: 1604T-Ubuntu1", 
            "UTvssAdmin: JM Lopez Lujan:416-123-1234:jm.lopez@utoronto.ca", 
            "UTvssClient: EIS", 
            "UTvssPurpose: Test", 
            "UTvssRequested: 2016-04-27 10:16:42 ", 
            "UTvssInform: jm.lopez@utoronto.ca", 
            "Description: Ubuntu cluster", 
            ""
        ], 
        "built_from": "template", 
        "cpu": "1", 
        "created_on": "2016-04-27 10:16:42 EDT", 
        "disks": [
            40, 
            100
        ], 
        "domain": "domain-c5877", 
        "dvd_cd": "", 
        "folder": "group-v4122", 
        "guest_os": "ubuntu64Guest", 
        "high_io": false, 
        "id": 26, 
        "memory": "1", 
        "message": {
            "errors": [], 
            "warnings": [
                "Hard disk 1 capacity is the same. No change need to be done.", 
                "Fault Domain: FD3 ", 
                "Created in: VSS > Sandbox > jm", 
                "Network adapter 1: 00:50:56:92:08:08: VL-1102-UTCS", 
                "Network adapter 2: 00:50:56:92:14:fe: VL-1072-VSGAN"
            ]
        }, 
        "networks": [
            "dvportgroup-95", 
            "dvportgroup-92"
        ], 
        "source_template": "50123c4c-c810-5c0f-6203-eac67f0cb7e8", 
        "source_vm": null, 
        "status": "Processed", 
        "task_id": "aa1cc5fa-94fc-473f-b29c-47f022745eb2", 
        "updated_on": "2016-04-27 10:26:00 EDT", 
        "user": {
            "_links": {
                "self": "https://vss-api.eis.utoronto.ca/v2/user"
            }, 
            "id": 1, 
            "username": "jm"
        }, 
        "vm_name": "1604T-Ubuntu1", 
        "vm_uuid": "5012826a-6a1a-815a-249d-7d6eb640f020"
    }, 
    "meta": {
        "count": 23, 
        "time": "0.00541s", 
        "user": "jm"
    }
}

List

Virtual machines

In order to list all your Virtual Machines you should make a HTTP GET request to the endpoint /v2/vm:

The following examples use HTTPie and CURL to request ALL Virtual Machine managed by given user without filters:

http GET "https://vss-api.eis.utoronto.ca/v2/vm" "Authorization: Bearer $TK"
curl -H "Authorization: Bearer $TK" -X GET "https://vss-api.eis.utoronto.ca/v2/vm"

HTTP response data would look something like:

Response
{
    "_links": {
        "self": "https://vss-api.eis.utoronto.ca/v2/vm?short=1&per_page=5"
    },
    "data": [
        {
            "hostName": "HOTH",
            "ipAddress": "",
            "moref": "vm-4210",
            "name": "1409P-hoth",
            "powerState": "poweredOff",
            "uuid": "50127974-aa4a-c215-f9f0-e1ab8a4ef050"
        },
        {
            "hostName": "glog-app01.eis.utoronto.ca",
            "ipAddress": "192.168.2.222",
            "moref": "vm-12178",
            "name": "1803D-graylog-app-0",
            "powerState": "poweredOn",
            "uuid": "5012f72a-f9c7-366f-5cf0-e1ac6afe4466"
        },
        {
            "hostName": "glog-app02.eis.utoronto.ca",
            "ipAddress": "192.168.2.122",
            "moref": "vm-12075",
            "name": "1803D-graylog-es1",
            "powerState": "poweredOn",
            "uuid": "50129e9f-38c5-ba9a-14d1-a1023fbc3aeb"
        },
        {
            "hostName": "gpu-dh-108",
            "ipAddress": "192.168.1.155",
            "moref": "vm-15854",
            "name": "1811D-ubuntu",
            "powerState": "poweredOn",
            "uuid": "501257e0-81f5-9c2a-84e5-e900212fef76"
        },
        {
            "hostName": "ubuntu",
            "ipAddress": "",
            "moref": "vm-13053",
            "name": "1807P-Ubuntu-18.04-server-tmpl",
            "powerState": "poweredOff",
            "uuid": "50120242-3ea3-d7ba-b6a5-14ffa8565b65"
        }
    ],
    "meta": {
        "count": 5,
        "pages": {
            "first_url": "https://vss-api.eis.utoronto.ca/v2/vm?per_page=5&page=1&expand=True",
            "last_url": "https://vss-api.eis.utoronto.ca/v2/vm?per_page=5&page=5&expand=True",
            "next_url": "https://vss-api.eis.utoronto.ca/v2/vm?per_page=5&page=2&expand=True",
            "page": 1,
            "pages": 5,
            "per_page": 5,
            "prev_url": null,
            "total": 25
        },
        "time": "0.03134s",
        "user": "jm"
    }
}


Included attributes are described in the following table:

NameTypeDescription
uuidstring128-bit UUID of a virtual machine, represented as a hexademical string. This identifier is used by VirtualCenter to uniquely identify all virtual machine instances, including those that may share the same SMBIOS UUID.
morefstringManaged object reference of the vm
namestringVirtual Machine name including VSS prefix.
guest_full_namestringThe full name of the guest operating system for the virtual machine. For example: Windows 2000 Professional.
guest_idstringThe guest operating system identifier.
ip_addressstringPrimary IP address assigned to the guest operating system, if known.
hostnamestringGuest hostname. Provided only when VMware Tools is running.

memoryGB

integerMemory size of the virtual machine, in Gigabytes.

cpu_count

integerNumber of processors in the virtual machine. 

overall_status

string

VM general "health" value:

  • gray: The status is unknown.
  • green: The entity is OK.
  • red: The entity definitely has a problem.
  • yellow: The entity might have a problem.
power_statestringThe current power state of the virtual machine. The state could be: poweredOff or poweredOn
provisioned_gbintegerSum of Committed and Uncommitted storage.
folderobjectFolder object which contains current VM
folder_morefstringFolder managed object reference
tools_running_statusstringVMware Tools running status.
tools_versionstringVMware Tools version.
tools_version_statusstringVMware Tools version status.
versionstringVirtual hardware version.

Paging

All requests to the /vm URL are paginated. The response body includes a 'meta.pages' key with everything to navigate through the results, for instance:

KeyDescription
first_urlContain the URLs to navigate through results.
last_url
prev_url
next_url
pageCurrent page
pagesTotal number of pages
per_pageResults per page. Maximum 250; Default 10.
totalTotal number of results

Results per page can be set by including the parameter in the URL query, so we can get the desired number of elements per page, for example:

http GET "https://vss-api.eis.utoronto.ca/v2/vm?per_page=200" "Authorization: Bearer $TK"
curl -H "Authorization: Bearer $TK" -X GET "https://vss-api.eis.utoronto.ca/v2/vm?per_page=1500"

Sorting

The resource provides also attribute sorting by adding the sort parameter in the URL query string in the following format:

sort=<field_name>,<asc|desc>

For example:

http GET "https://vss-api.eis.utoronto.ca/v2/vm?sort=name,desc" "Authorization: Bearer $TK"
http GET "https://vss-api.eis.utoronto.ca/v2/vm?sort=uuid,asc" "Authorization: Bearer $TK"


Filtering

Virtual Machines can be filtered by adding the filter argument to the query string in the following format:

filter=<field_name>,<operator>,<value>

Operators can be:

OperatorDescription
eqEquals
neNot equal
ltLower than
leLower equal
gtGreater than
geGreater equal
likeMatching pattern
inMatch value in many items separated by commas

Filter Virtual Machine resource by any of the following

AttributeFilter
namename
ipAddressip_address
hostnamehostname
powerStatepower_state
cpuCountcpu_count
overallStatusoverall_status
toolsVersion

tools_version

toolsVersionStatustools_version_status
versionversion

The following examples show how to implement a GET request with the first three parameters shown below. The result is similar to the previous section.

http GET "https://vss-api.eis.utoronto.ca/v2/vm?filter=name,like,%Test%" "Authorization: Bearer $TK"
http GET "https://vss-api.eis.utoronto.ca/v2/vm?filter=ip_address,eq,10.2.1.2" "Authorization: Bearer $TK"
http GET "https://vss-api.eis.utoronto.ca/v2/vm?filter=hostname,like,wiki.eis.utoronto.ca" "Authorization: Bearer $TK"

Filtering by name can be done as follows:

http GET "https://vss-api.eis.utoronto.ca/v2/vm?filter=name,like,%Test%" "Authorization: Bearer $TK"

HTTP response data would look something like:

HTTP Response
{
    "_links": {
        "api": "https://vss-api.eis.utoronto.ca/v2/", 
        "self": "https://vss-api.eis.utoronto.ca/v2/vm"
    }, 
    "data": [
        {
            "_links": {
                "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db"
            }, 
            "name": "1604Q-VMTest_1", 
            "uuid": "5012bd15-c20c-a971-aa68-af1a3cf3d0db"
        }
    ], 
    "meta": {
        "count": 1, 
        "time": "1.86220s", 
        "user": "jm"
    }
}

From now on, you will need the UUID of any virtual machine, provided by the either the uuid attribute or in the "_links" section, to get further information and eventually to modify its configuration.

Specific virtual machine info

Some of the attributes will have an object value. Such is the case of guest, hardware, network, config and vss

NameTypeDescription
uuidstringVirtualCenter-specific 128-bit UUID of a virtual machine, represented as a hexademical string. This identifier is used by VirtualCenter to uniquely identify all virtual machine instances, including those that may share the same SMBIOS UUID.
namestringVirtual Machine name including VSS prefix.
ConfigVM Configuration
boot.delay_msintegerDelay in milliseconds before starting the boot sequence. The boot delay specifies a time interval between virtual machine power on or restart and the beginning of the boot sequence.
os.guest_idstringOperating system configured in the virtual machine
FolderLogical Folder
namestringImmediate folder holding VM
parentstringParent folder holding the VM
pathstringFull path to immediate folder
morefstringManaged object reference to parent folder
GuestGuest status and configuration
guest_full_namestringThis is the full name of the guest operating system for the virtual machine. For example: Windows 2000 Professional.
guest_idstringGuest operating system configured on a virtual machine.
hostnamestringHostname of the guest operating system, if known.
ip_addressstringList of IP address assigned to the guest operating system, if known.
tools_statusstringCurrent running status of VMware Tools in the guest operating system, if known.
NoteVirtual Machine Metadata
notestringVirtual Machine full annotation
clientstringClient notes
Name
full_namestringVM full name including VSS prefix.
HardwareVirtual Machine Hardware configuration
cpu_countintegerNumber of processors in the virtual machine. 
cores_per_socketintegerNumber of cores used to distribute virtual CPUs among sockets in this virtual machine. If the value is unset it implies to numCoresPerSocket = 1.
memory_mbintegerMemory size of the virtual machine, in megabytes.
devicesstringList of strings holding controllers, cd/dvd, disks and nics configured in the VM
versionstringThe version string for this virtual machine.
StorageStorage summary
provisioned_gbinteger

Sum of Committed and Uncommitted storage.

uncommitted_gbintegerAdditional storage space, in bytes, potentially used by this virtual machine on all datastores.
committed_gbintegerTotal storage space, in bytes, committed to this virtual machine across all datastores.
unshared_gbintegerTotal storage space, in bytes, occupied by the virtual machine across all datastores, that is not shared with any other virtual machine.
StateRuntime status related attributes
overall_statusstring

VM general "health" value:

  • gray: The status is unknown.
  • green: The entity is OK.
  • red: The entity definitely has a problem.
  • yellow: The entity might have a problem.
power_statestringThe current power state of the virtual machine.
alarmsbooleanWhether the VM has triggered alarms.
SnapshotVirtual Machine Snapshot information
existbooleanWhether the current virtual machine has Snapshots
VSSVSS Metadata
adminstringAdmin responsible of this VM.
clientstringCustom client key-value notes.

 The following example, requests information about a particular VM using its base resource /v2/vm and appending the UUID to get the URI /vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/


http GET "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db" "Authorization: Bearer $TK"

HTTP response data would look something like:

Response
  {
    "config": {
      "boot": {
        "_links": {
          "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/boot"
        },
        "delay_ms": 5000
      },
      "os": {
        "_links": {
          "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/os"
        },
        "guest_id": "centos7_64Guest"
      },
      "template": {
        "_links": {
          "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/template"
        },
        "is_template": false
      }
    },
    "folder": {
      "_links": {
        "self": "https://vss-api.eis.utoronto.ca/v2/folder-vc/group-v759"
      },
      "moref": "group-v759",
      "name": "Dev",
      "parent": "Public",
      "path": "Public > Dev"
    },
    "guest": {
      "_links": {
        "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/guest"
      },
      "guest_full_name": "CentOS 6 (64-bit)",
      "guest_id": "centos6_64Guest",
      "hostname": "pi-lab.dcb.eis.utoronto.ca",
      "ip_address": [
        "fe80::1b5b:c11b:dbff:37b8",
        "128.100.111.0",
        "fe80::250:56ff:feb0:3be0"
      ],
      "tools_running_status": "guestToolsRunning",
      "tools_status": "guestToolsUnmanaged",
      "tools_version": "10309"
    },
    "hardware": {
      "cpu": {
        "_links": {
          "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/cpu"
        },
        "cpu_count": 1
      },
      "devices": {
        "cds": [
          {
            "_links": {
              "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/cd/1"
            },
            "backing": "client",
            "unit": 1
          }
        ],
        "disks": [
          {
            "_links": {
              "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/disk/1"
            },
            "capacity_gb": 8.0,
            "unit": 1
          },
          {
            "_links": {
              "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/disk/2"
            },
            "capacity_gb": 1.0,
            "unit": 2
          },
          {
            "_links": {
              "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/disk/3"
            },
            "capacity_gb": 1.0,
            "unit": 3
          }
        ],
        "floppies": [
          {
            "_links": {
              "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/floppy/1"
            },
            "backing": "client",
            "unit": 1
          }
        ],
        "nics": [
          {
            "_links": {
              "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/nic/1"
            },
            "connected": true,
            "mac_address": "00:50:56:b0:3b:e0",
            "network": {
              "_links": {
                "self": "https://vss-api.eis.utoronto.ca/v2/network-vc/dvportgroup-1094"
              },
              "moref": "dvportgroup-1094"
            },
            "type": "vmxnet3",
            "unit": 1
          },
          {
            "_links": {
              "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/nic/2"
            },
            "connected": true,
            "mac_address": "00:50:56:b0:3f:4c",
            "network": {
              "_links": {
                "self": "https://vss-api.eis.utoronto.ca/v2/network-vc/dvportgroup-1083"
              },
              "moref": "dvportgroup-1083"
            },
            "type": "vmxnet3",
            "unit": 2
          }
        ]
      },
      "memory": {
        "_links": {
          "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/memory"
        },
        "memory_gb": 1.0
      },
      "version": "vmx-13"
    },
    "name": {
      "_links": {
        "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/name"
      },
      "full_name": "1904T-Pi-Lab"
    },
    "note": {
      "client": {
        "_links": {
          "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/note/client"
        },
        "value": ""
      },
      "note": {
        "_links": {
          "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/note"
        }
      }
    },
    "permission": {
      "_links": {
        "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/permission"
      }
    },
    "snapshot": {
      "_links": {
        "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/snapshot"
      },
      "exist": true,
      "requireDiskConsolidation": false
    },
    "state": {
      "_links": {
        "alarm": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/alarm",
        "event": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/event",
        "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/state"
      },
      "alarms": false,
      "domain": {
        "_links": {
          "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/domain"
        },
        "moref": "domain-c63",
        "name": "Cluster1"
      },
      "overall_status": "green",
      "power_state": "poweredOn"
    },
    "storage": {
      "committed_gb": 5.65,
      "provisioned_gb": 15.65,
      "uncommitted_gb": 10.0,
      "unshared_gb": 5.53
    },
    "uuid": "5012bd15-c20c-a971-aa68-af1a3cf3d0db",
    "vss": {
      "_links": {
        "self": "https://vss-api.eis.utoronto.ca/v2/vm/5012bd15-c20c-a971-aa68-af1a3cf3d0db/vss"
      },
      "admin": "JM Lopez L:416-577-7062:jm.lopez utoronto.ca",
      "client": "EIS2",
      "description": "This is a test VM",
      "inform": [
        "jm.lopez utoronto.ca"
      ],
      "options": [
        "reset_on_restore",
        "reboot_on_restore"
      ],
      "service": {
        "description": "Not Applicable",
        "id": 112,
        "name": "N/A",
        "service_group_id": 15
      },
      "usage": "Test"
    }
  }

Delete

Single Virtual Machine

To delete an existent Virtual Machine, send a DELETE request to /v2/vm/<vm_uuid> and a change request to decommission requested VM will be submitted.

HTTPie

http DELETE "https://vss-api.eis.utoronto.ca/v2/vm/50125d11-a8d6-2af7-c01e-dc6f6be0e607" "Authorization: Bearer $TK"

CURL

curl -H "Authorization: Bearer $TK" $TK -X DELETE "https://vss-api.eis.utoronto.ca/v2/vm/50125d11-a8d6-2af7-c01e-dc6f6be0e607"
If the request was successfully submitted, the following Response StatusHeaders and body will be received:
Response Headers
HTTP/1.0 202 ACCEPTED
Allow: HEAD, DELETE, OPTIONS, GET
Content-Length: 398
Content-Type: application/json
Date: Thu, 28 Apr 2016 15:32:55 GMT
Location: https://vss-api.eis.utoronto.ca/v2/request/task/7e8e4a7c-7c09-42d2-86e1-41ff5ea530c6
X-RateLimit-Limit: 7200
X-RateLimit-Remaining: 7195
X-RateLimit-Reset: 1461859200
Response Body
{
   "data": {
        "_links": {
            "request": "https://vss-api.eis.utoronto.ca/v2/request/change/12", 
            "task": "https://vss-api.eis.utoronto.ca/v2/request/task/7e8e4a7c-7c09-42d2-86e1-41ff5ea530c6"
        }, 
    	"message": "Request has been accepted for processing",
    	"name": "Accepted",
    	"request": {
    	    "id": 12,
    	    "status": "Submitted",
    	    "task_id": "7e8e4a7c-7c09-42d2-86e1-41ff5ea530c6"
    	},
    	"status": 202
    }
}

Task

Request processing is almost instantaneous, however you could check the task progress by making a HTTP GET request to any given /v2/request/task/<task_id> endpoint.

Response Body
{
    "_links": {
        "request": "https://vss-api.eis.utoronto.ca/v2/request/", 
        "self": "https://vss-api.eis.utoronto.ca/v2/request/task/7e8e4a7c-7c09-42d2-86e1-41ff5ea530c6"
    }, 
    "data": {
        "result": {
            "current": 100, 
            "result": {
                "errors": [], 
                "warnings": [
                    "Virtual Machine 1604T-Ubuntu3 has been deleted."
                ]
            }, 
            "status": "1604T-Ubuntu3 Processed", 
            "total": 100
        }, 
        "status": "SUCCESS"
    }, 
    "meta": {
        "count": 2, 
        "time": "0.00865s", 
        "user": "jm"
    }
}

Requests

Checking the overall status of the requests and also its result can be done by making a HTTP GET request to /v2/request/change/26 - 28 endpoint:

Response Body
{
    "_link": {
        "request": "https://vss-api.eis.utoronto.ca/v2/request/change", 
        "self": "https://vss-api.eis.utoronto.ca/v2/request/change/12"
    }, 
    "data": {
        "_links": {
            "task": "https://vss-api.eis.utoronto.ca/v2/request/task/7e8e4a7c-7c09-42d2-86e1-41ff5ea530c6", 
            "vm": "https://vss-api.eis.utoronto.ca/v2/vm/50125d11-a8d6-2af7-c01e-dc6f6be0e607"
        }, 
        "attribute": "state", 
        "created_on": "2016-04-28 11:32:55 EDT", 
        "id": 12, 
        "message": {
            "errors": [], 
            "warnings": [
                "Virtual Machine 1604T-Ubuntu3 has been deleted."
            ]
        }, 
        "status": "Processed", 
        "task_id": "7e8e4a7c-7c09-42d2-86e1-41ff5ea530c6", 
        "updated_on": "2016-04-28 11:32:56 EDT", 
        "user": {
            "_links": {
                "self": "https://vss-api.eis.utoronto.ca/v2/user"
            }, 
            "id": 1, 
            "username": "jm"
        }, 
        "user_id": 1, 
        "value": {
            "state": "delete"
        }, 
        "vm_name": "1604T-Ubuntu3", 
        "vm_uuid": "50125d11-a8d6-2af7-c01e-dc6f6be0e607"
    }, 
    "meta": {
        "count": 13, 
        "time": "0.00572s", 
        "user": "jm"
    }
}


  • No labels