Managing Allocation Requests

This guide includes instructions for getting a new allocation of cloud resources (project) on the Melbourne Research Cloud, and how to manage those resources after that.

What is an Allocation Request?

The main organisational structure on the Melbourne Research Cloud is the Project. When you create an instance, volume or object store container they belong to a specific Project. Once you have logged into the dashboard, you can change Project in the Projects dropdown in the top-right navigation bar. The selected Project will be what dictates the resource limits and in which subsequent actions are made.

You may submit an Allocation Request to apply for a new Project and request an allocation (quota) of cloud resources. The Allocation Request may also be amended at any time to request more resources, update any details or extend the Project. Resources are allocated for a limited length of time to ensure that the Melbourne Research Cloud is being actively used.

Any user may have, or belong to, any number of Projects.

Where do I create or manage my Allocation Requests?

Allocation Requests are managed in the Melbourne Research Cloud dashboard using the "Allocations" tab on the left-hand navigation panel:

Note: The only user who can see projects under My Requests is the user who created the allocation request. In other words, if a Project needs to be extended or updated in any way, that request needs to come from the Project owner.

Allocation Request Lifecycle

Submission

You can submit a new allocation request at Allocations > New Request.

See the below section Requestable Cloud Resources for help in completing the Cloud Resources section.

Allocation requests can take up to 2 weeks to process.

Your allocation request may be declined. If this occurs you will receive an email with advice regarding the reasons why. You may be asked to amend and resubmit your original allocation request.

Approval

If your allocation request is approved you will receive an email telling you that your project has been provisioned.

The start date will be updated to the date of approval if the approval occurs later than your specified start date.

Expiry

Your project will have an end date. You will be reminded that your project will be expiring two weeks before the end date. You may extend the allocation request at any time in the dashboard.

If you do not submit an extension request:

  1. On the expiry date the allocation quotas will be set to zero. Existing virtual machines and storage resources will continue to be accessible, but no new resources can be created.
  2. Two weeks after expiry, all instances and data in this project allocation will be archived and safely stored.
  3. Three months after expiry, all archived instances and data will be deleted.

Requestable Cloud Resources

Compute Resources

The following flavours can be launched on the Melbourne Research Cloud. Use this table to determine the number of Instances and vCPUs to include in your Allocation Request form. All instances come with a 30 GB disk.

Flavour name vCPUs RAM (GB) Suggested use
uom.general.1c4g 1 4 Simple web hosting
uom.general.2c8g 2 8 Database driven website
uom.general.4c16g 4 16 Data Science using RStudio or JupyterHub
uom.general.8c32g 8 32 Data science on larger data sets
uom.general.12c48g 12 48
uom.general.16c64g 16 64

Note: the General flavors run on oversubscribed hypervisors.

Premium Flavours

If you require servers with higher memory or vCPUs than the general options above, there is an option to select Premium Flavours. You will be asked to justify your request. The Premium Flavours are

Flavour name vCPUs RAM (GB) Notes
uom.bigmem.24c1000g 24 1 TB
uom.bigmem.36c1500g 36 1.5 TB
uom.bigmem.48c2000g 48 2 TB
uom.hicores.8c72g 8 72
uom.hicores.12c108g 12 108
uom.hicores.16c144g 16 144
uom.hicores.20c180g 20 180
uom.hicores.24c216g 24 216
uom.hicores.28c252g 28 252
uom.hicores.32c288g 32 288
uom.hicores.48c432g 48 432
uom.hicores.64c576g 64 576
uom.hicores.80c720g 80 720
uom.vdi.m10-6c30g 6 30 Perfect for Virtual Desktops
uom.gpgpu.k80-6c55g 6 55 General Purpose GPU
uom.gpgpu.2gpu-k80-12c110g 12 110 2 General Purpose GPUs

Note: the Premium flavors run on dedicated hypervisors that are not oversubscribed.

Volume Storage

A persistent volume looks and acts like a hard drive that can be attached to your virtual machine instances. Volumes and their data persist independently of virtual machine instances and volumes can be dynamically attached and detached to/from different virtual machine instances.

Object Storage

Object Storage is a large accessible online storage location that you can reach from most machines with internet connectivity. Object Storage requires cloud native applications for access.

Database Service

The database service provides a simple interface for provisioning and managing database engines supporting MySQL and PostgreSQL, with MongoDB coming soon. You can specify the number of database servers, the total database storage your project would require, or both.

Advanced Networking

Virtual resources for building more advanced network topologies for your instances, including routers, load balancers and private networks.

Previous Next