TANGO Cloud Virtual Machines (VMs) are created and managed using the TANGO Cloud dashboard. Once a VM has been deployed, the hardware configuration can be reconfigured if required.
You may also like to refer to the TANGO Cloud Quick Access Guide here.
1. Logging in
2. The "Home" page
At the top right of the page, use the "Preferences" button to:
- "Assign Delegates" (this feature is for admins and relates to "Approvals")
- Set the TANGO Cloud dashboard language
- Enable/disable email notifications
Use the pencil icon in the upper right corner to change the layout of the Home page and add additional information using "Portlets".
The other tabs at the top of the page:
Catalog: This is where you browse available VMS and request new deployments.
Requests: A log of all requests (such as create, destroy, modify a VM) is stored here
Items: Your VM deployments are listed here.
3. Deploying a Virtual Machine
To deploy a VM, browse the Service Catalog and request the type of VM you'd like.
Enter a description and the reason for your request. By default this will deploy one VM, however, you can deploy multiple instances of the same machine by increasing the number of deployments. Note that some management operations (including "Destroy") will apply to all VMs in the same deployment.
To configure the VM, select the "vSphere_Machine_1" menu item. Configure the number of CPUs and memory as required- the possible values are shown to the right. The disk drive for the operating system cannot be configured by the user, however, additional disks can be added in the next step or after the initial deployment.
Click "New" and enter the capacity of the drive, 100 GB in this case. Optionally, for Windows, add a drive letter (e.g. "D") or, for Linux, you must mount the additional storage from within the VM once it is provisioned. For Windows machines, The values "A" and "B" are reserved and cannot be used here, whilst for Linux machines, the value "/root" is reserved. A hard disk label may also be optionally added.
Be sure to press "OK" once the additional disk(s) have been configured.
Once submitted, the request will appear in the "Requests" tab. If you saved your configured VM to be deployed later, this is where you continue to configure it and eventually submit it (using the "Edit" button which is displayed for saved request). Notice also, the "Status" of the deployment- it will appear as "In progress" for around 10 minutes for a new deployment of a single VM.
You may need to refresh your browser to see the change in status (to "Successful").
- Expanding the deployment in the "Deployments" page.
- Selecting the "Machines" page
4. Managing a VM
Clicking the VM name will load the management interface for the VM.
Change Lease: by default the VM will not expire, however, if you wish to schedule a time for all VMs related to this deployment to be automatically destroyed you can do so here. CAUTION! All data on configured disk drives will be lost.
Connect to Remote Console: Opens a remote console session in a new window in a web browser.
Connect using RDP: Use the RDP protocol and client (built-in client on Windows) (MAKE SURE TO USE PORT 32189).
Connect using VMRC: Uses VMware client to open a remote console session (for eRSA administrators).
Create Snapshot: Creating a snapshot saves the present state of the virtual machine. Snapshots can be reloaded at a later point in time to return the VM to it’s previous state. If the VM is powered on it is recommended to include the memory in the snapshot. The availability of the create snapshot option is limited by the allowed number of snapshots. If you are allowed two snapshots and you used them, the option is not available until you delete a snapshot. For performance reasons, VMware recommends that snapshots are not kept longer than 3 days and are not intended as long-term VM backups.
Revert Snapshot: revert to a previous snapshot of the machine. You must have an existing snapshot to use this action.
Destroy: immediately destroy all VMs related to this deployment. CAUTION! All data on configured disk drives will be lost.
Expire: immediately expire and destroy all VMs related to this deployment. CAUTION! All data on configured disk drives will be lost.
Install Tools: installs the VMware tools. By default these have already been installed.
Power Cycle: only recommended if a VM becomes unresponsive and does not respond to a reboot command. You can force a shutdown and reboot; analogous to turning the power off at the switch on a physical machine and pressing the power switch to start it.
Power Off: only recommended if a VM becomes unresponsive and does not respond to a reboot command. Similar to "Power Cycle", however, the VM will not be restarted.
Power On: start the VM (only appears if VM is powered off).
Reboot: Sends a reboot command to the operating system. This (and rebooting from within the VM) is the preferred method of rebooting as the operating system is able to cleanly shutdown.
Reconfigure: Change the following properties of a VM: CPU, memory, network, disk settings, and description. There is a known issue whereby the network adapters are named differently to the initial VM deployment. The adapter named "Red-Client-Public-01-V393" is equivalent to "Public Network-01", whilst the adapter named "Blue-Client-Mgmt-01-V305" is equivalent to "Private Network-01".
Reprovision: Destroys the machine, then initiates the provisioning workflow to create a machine with the same name. When you request that a machine be reprovisioned, a known issue might cause vRealize Automation to display the reprovisioning status as Complete in the catalog, when the actual state is In Progress. After you submit a request to reprovision a machine, you can use any of the following sequences to check the status of the reprovisioned machine:
- Infrastructure > Managed Machines
- Items > Item Details
- Administration > Events > Event Logs
Shutdown: Sends a shutdown command to the operating system. This (and shutting down from within the VM) is the preferred method of shutting down as the operating system is able to do so cleanly.
Suspend: Sends a suspend command to the operating system, effectively placing it in a paused state- only the storage resource will continue to be used. The status will be "Off", however. To resume the machine, use the "Power On" function (you may need to refresh your browser to see the new state).