How To

Deploy Ubuntu 18.04 LTS VM

It is highly recommended that MITA Marketplace templates are used for projects rather than standard Azure templates to make sure that the correct naming convention is applied.

 The following custom templates are available for users:

  • MITA Windows Server Datacentre (Option of Win16 and Win19)
  • MITA Windows SQL Server 2017 on Windows 2016
  • MITA Ubuntu Server 18-04 LTS
  • MITA CentOS Server
  • Virtual Machine OS disk Restore
MITA Ubutnu Server 18-04 LTS

The MITA Ubuntu Server 18.04LTS custom image requests the following parameters:

  • Virtual Machine Name
  • Administrators Username
  • Authentication Type –
    • SSH
    • Password
  • Administrators Password or SSH
  • Windows OS Version
  • Server Size –
    • Small: 2 vCPU 4GB Ram
    • Medium: 4 vCPU 8GB Ram
    • Large: 8 vCPU 16GB Ram
  • Subnet Name
    • FrontEnd
    • BackEnd
  • AvailabilitySetName: This option is not required but recommended if you would like to use a load balancer with the VM. Firstly, you will need to pre-create an Availability Set and once you’re successful, only then can you enter the name of the availability set so that the VM will join it as soon as it is created.
  • Backups are now enforced with all VMs

You can view the deployment progress under Notifications Bell or under the Deployment section of the Resource Group:

Deploying

The deployment for a Linux VM takes approximately 10-20 minutes when backup is selected, and the following resources are created:

  • Ubuntu 18.04 LTS virtual machine
  • Network interface card with a private IP
  • Public IP (only if VM is created in frontend subnet)
  • OS disk of 127GB
  • Storage account to store VM diagnostics (if not already created)

Deleting Resources

When deleting resources make sure you delete all related resources. For example, deleting a virtual machine will not delete the disks, NIC cards and public IPs. Make sure that if these resources are not needed, then they are also removed.

NOTE: You can delete a network interface if it’s not attached to a virtual machine. If a network interface is attached to a virtual machine, you must first place the virtual machine in the stopped (deallocated) state, then detach the network interface from the virtual machine.