Floppy Images

Introduction

In some operating systems, such as the most recent versions of Windows, you need to provide the device drivers to properly recognize basic devices like the VMXNET3 network adapter or Paravirtual SCSi controllers. These drivers are provided by VMware and now, they are available for you to use on demand by the Floppy API resource. 

The Floppy API resource also provides available .flp images from your VSKEY-STOR space, so you are free to upload any custom floppy image and mount it to a Virtual Machine.

On this page:

The following table shows a brief description and HTTP methods allowed to interact with Floppy images available to customers.

ResourceURIDescriptionGETPOSTPUTPATCHOPTIONS
Floppy images/floppyFloppy images available to customers.(tick) 


(tick)

TK stores the Cloud API Token generated as a result of the following POST request to the /auth/request-token resource:

curl -X POST https://vss-api.eis.utoronto.ca/auth/request-token -u <username>

For example, extracting the token with the jq command:

TK=$(curl -X POST https://vss-api.eis.utoronto.ca/auth/request-token -u <username> | jq -r '.token')

List

In order to list available floppy images you should make a GET request to the endpoint /v2/floppy passing your access token. As a result, you will get list of Floppy images in form of JSON objects with the following attributes:

NameTypeDescription
namestringFloppy image file name
pathstringDatastore path location

The following examples implements HTTPie and CURL to list available Floppy images:

http GET "https://vss-api.eis.utoronto.ca/v2/floppy" "Authorization: Bearer $TK"
curl -H "Authorization: Bearer $TK" -X GET "https://vss-api.eis.utoronto.ca/v2/floppy"
Response Body
{
    "_links": {
        "api": "https://vss-api.eis.utoronto.ca/v2/", 
        "self": "https://vss-api.eis.utoronto.ca/v2/floppy"
    },
    "data": [
       {
            "name": "pvscsi-Windows2008.flp",
            "path": "[] /vmimages/floppies/pvscsi-Windows2008.flp"
        },
        {
            "name": "pvscsi-Windows2008.flp",
            "path": "[] /vmimages/floppies/pvscsi-Windows2008.flp"
        },
        {
            "name": "pvscsi-Windows2003.flp",
            "path": "[] /vmimages/floppies/pvscsi-Windows2003.flp"
        },
        {
            "name": "pvscsi-WindowsXP.flp",
            "path": "[] /vmimages/floppies/pvscsi-WindowsXP.flp"
        },
        {
            "name": "pvscsi.flp",
            "path": "[vssUser-xfers] jm/floppies/pvscsi.flp"
        }
    ], 
    "meta": {
        "count": 3, 
        "time": "0.91943s", 
        "user": "jm"
    }
}

Note the last item in the list is coming from jm's personal space in vskey-stor.

Sort

Sorting results has been recently introduced on version 3.2.1:

NameDescription
sortsort results by path or name

The following examples show how to structure a GET request, with sorting:

http GET "https://vss-api.eis.utoronto.ca/v2/floppy?sort=name" "Authorization: Bearer $TK"
http GET "https://vss-api.eis.utoronto.ca/v2/floppy?sort=path" "Authorization: Bearer $TK"

curl -X GET -H "Authorization: Bearer $TK" "https://vss-api.eis.utoronto.ca/v2/floppy?sort=path" 
curl -X GET -H "Authorization: Bearer $TK" "https://vss-api.eis.utoronto.ca/v2/floppy?sort=name" 

Filters

This resource has one filter to narrow down the number of floppy images shown in the result.

NameDescription
nameFloppy image file name

The following examples show how to structure a GET request, with filters:

http GET "https://vss-api.eis.utoronto.ca/v2/floppy?name=ubuntu" "Authorization: Bearer $TK"
http GET "https://vss-api.eis.utoronto.ca/v2/floppy?name=ubuntu-16" "Authorization: Bearer $TK"

curl -X GET -H "Authorization: Bearer $TK" "https://vss-api.eis.utoronto.ca/v2/floppy?name=ubuntu"
curl -X GET -H "Authorization: Bearer $TK" "https://vss-api.eis.utoronto.ca/v2/floppy?name=ubuntu-16"