You can run instances of various sizes on the cloud, from one to 16 cores, and from one instance to hundreds. When you submit a request for a project allocation, you will become the project (or tenant) manager. You will be able to add other users to the project, amend and extend the allocation.

We have a tutorial about how to manage an allocation and please visit the Nectar Tutorial Website.

Project Trials (Automatic, no application required)

When you log into the cloud for the first time, you are automatically granted a Project Trial Research Allocation of two cores for three months. Project Trials have names like pt-2061.

Within your default allocation you can run:

  • a medium (two core) instance, or
  • two small (single core) instances.
  • As you get near the end of your Project Trial, submit a request for more resources.

Submit a Request for more resources

To request access to more Nectar Cloud resources, you fill in a new request or you can amend/extend one of your existing requests. 

To make a new request, follow our tutorial here. 

To amend/extend your project, follow our tutorial here. 

Only a project's manager(s) can request an amendment to the project's resources. Be sure to select the correct project in the Dashboard, otherwise you may not see the corresponding request in the "My Requests" tab. As a rule of thumb, the more resources you ask for, the more detail we require about your research. Requesting a few cores won’t be scrutinised as much as requesting tens or hundreds of cores.

Allocation Request Process

The allocation request process ensures fair access to resources by ensuring the requests are of an appropriate size and provisioned based on merit, to support nationally significant research. The allocation request process is started when an eligible researcher submits a request. When a request is submitted it will be assessed by the Nectar Allocation Committee (NAC) according to the criteria set out in the Research Cloud-National Allocation Scheme (RC-NAS). If the assessment is successful, the allocation request will be approved and the allocation provisioned as a National merit allocation. As part of the approval process, larger allocation requests may be right sized to ensure fairness and for pragmatic reasons. If a request is assessed as not meeting the RC-NAS criteria (refer to section 7.1) it may be rejected with feedback to the applicant on the reasons for rejection. Alternatively, a request may be approved by a Node for provisioning within their discretionary local Node share. While National merit allocations are permitted to use resources at any of the Nectar federation nodes, local allocations can only run at the approving node. If the information provided in the allocation request is not sufficient to make an assessment, the assessor may request further information from the requester, and ask them to resubmit a revised allocation request. This may indicated by rejecting the request, or by creating a support ticket to facilitate a discussion of the issues. When an allocation is approved, it is provisioned automatically and the project owner is notified. A submitted allocation request that is pending approval can be updated and re-submitted. A provisioned allocation's request can also be updated (e.g. to request more resources) and re-submitted. In this scenario the provisioned resources will remain active. Rejected allocation requests and expired allocation requests (prior to final deletion) can be updated and re-submitted. However, the later steps of expiry can result in some data loss that cannot reversed, and the final deletion is irreversible. Caveat: Project owners and their nominees are notified by email each time their request changes status. Allocation expiry notices are also sent by email. Unfortunately, we cannot guarantee that the emails will be delivered to you, or forwarded to your new email address if you change institutions. We rely on the email address provided by your institution via AAF when you login to the Nectar Dashboard.  If you are changing institution, and wish to continue using your allocation, please contact Nectar support.

What happens after you submit a request

When you submit the request, you will receive a confirmation email with all your details. View or edit your request by clicking on the ‘My Requests’ tab at the dashboard.

Your request will be reviewed by your local node (if any) or the Nectar Allocation Committee. This can take up to four weeks to process.

If there are any issues with your request, we will get in touch with you. You may be asked to provide more detail about your research or to clarify your technical requirements.

Approved requests become "Projects"

We create a Research Cloud Project using your project name, for example ‘QCIF DNA Sequencing Project’. You will receive an email confirming everything is ready to go. As the requester, you will automatically be the project manager. You can assign another project manager by contacting the support desk.

As a user, you can be a member of more than one project. You select the current project to access at the dashboard using a drop down menu on the left hand side.

Managing an approved Project (Add.remove users)

Users can be members of multiple Projects sharing each Projects resources with its members. 

If you are a project manager, you can add or remove users from your allocation in the users tab on the nectar dashboard. To add a user, you only need the email address they use to access Nectar via AAF. Note that they must have previously accessed the Nectar Dashboard for this to work.

If you would like to transfer status as "project manager" to another user, request the change by launching a support ticket. It is helpful to do this before your account becomes deactivated if you are leaving your AAF member institution.

How do I increase my existing Projects' resources

As a project manager, you can make changes to your request at any time by clicking on ‘My Requests’ at the dashboard. This will show the requests you have made and you can update them.

If you change and resubmit the request, it will go through the review process as outlined earlier.

This can be used to change the resources allocated, or to extend an allocation prior to its expiry (see Project Allocation and Expiry).