The Nectar Research Cloud allocations system allows you to apply for a variety of resources.  Unfortunately, some of these resources can be difficult for a novice user to understand.  In particular, some combinations of resources do not make sense. In the past we have had many cases where the inconsistencies were not noticed to start with, an the user has had to request a further amendment to fix the problem

Since these apparently inconsistent resource combinations sometimes do make sense, we don't forbid them outright. Instead. the allocation request workflows will warn you of the inconsistency.  You then have two choices:

  • You can adjust the resources you are requesting to resolve the inconsistency, and Submit the request again.  This will recheck the form, and complete the submission if the consistencies are now resolved.
  • You can "Submit ignoring warnings". In this case, the approver will see the same warnings and may query you about them before approving your request.

The purpose of this article is to explain as best we can what the warnings mean, and what you can do to resolve them.   (You probably reached this page by clicking on a "More information" link in the Nectar dashboard.

User warnings.

Requested instances > requested VCPUs

Explanation: This warning relates to the number of instances and VCPUs that you have requested. When you launch a Nectar instance at least 1 VCPU will be allocated, depending on the flavor that you select. When you request quotas for more instances than VCPUs, some of the instance quota will be unusable.

Impact: This is probably harmless since excess instance quotas don't consume a scarce resource. However, if your intention is to actually run the number of instances implied by the instance quota, then you will need more VCPU quota to achieve this.

Remedy: Either decrease the instance quota or increase the VCPU quota.

No VCPUs requested

Explanation: You have requested quota for 1 or more instances, but no quota for VCPUs.

Impact: Without this quota, you will not be able to launch Nectar instances.

Remedy: Either set the instance quota to zero or increase the VCPU quota.

No instances requested

Explanation: You have requested quota for 1 or more VCPUs, but no quota for instance.

Impact: Without instance quota you will not be able to launch Nectar instances.

Remedy: Either set the VCPU quota to zero or increase the instance quota.

Volume storage requested without any instances

Explanation: Volume storage resources can only be accessed when they are attached to an instance in the same project and the same availability zone. You have not requested instance quota, and therefore won't be able to use the volume storage as intended.

Impact: Without instance quota you will not be to create an instance to attach volumes to.

Remedy: Either remove the volume storage quota (set it to zero), or add instance and VCPU quotas so that you can create an instance to attach the volume(s) to.

Use of advanced networking requires at least 1 router

Explanation: All Nectar-supported use-cases for Neutron advanced networking require at least 1 router and 1 private network. You have not requested router quota, and therefore won't be able to use advanced networking.

Impact: Without router quota you will not be to use advanced networking.

Remedy: Either remove all advanced networking quotas, or add quotas for at least 1 router and 1 private network.

Use of advanced networking requires at least 1 network

Explanation: All Nectar-supported use-cases for Neutron advanced networking require at least 1 router and 1 private network. You have not requested network quota, and therefore won't be able to use advanced networking.

Impact: Without router quota you will not be to use advanced networking.

Remedy: Either remove all advanced networking quotas, or add quotas for at least 1 router and 1 private network.

Floating IPs require at least 1 network and 1 router

Explanation: All Nectar-supported use-cases for floating IPs require at least 1 router and 1 private network. You have requested floating IP quota without network and/or router quota, and therefore won't be able to use the floating IPs.

Impact: Without router and private network quota you will not be to use floating IPs.

Remedy: Either remove all advanced networking quotas, or add quotas for at least 1 router and 1 private network.

Load balancers require at least 1 network and 1 router

Explanation: All Nectar-supported use-cases for load balancers require at least 1 router and 1 private network. You have requested load balancer quota without network and/or router quota, and therefore won't be able to use the load balancer.

Impact: Without router and private network quota you will not be to use load balancers.

Remedy: Either remove all advanced networking quotas, or add quotas for at least 1 router and 1 private network.

Approver-only warnings.

These warnings should only be visible to allocation approvers.

Non-default RAM > 4GB per core ratio

A non-default RAM quota has been set for this allocation. Since this may have happened accidentally, it is advisable to check that this is (still) intended.

Note that setting a memory quota greater than the magic ratio will only work if the allocation has access to a "large memory" flavor. Currently none of the public flavors support this.

Non-default RAM < 4GB per core ratio

A non-default RAM quota has been set for this allocation . Since this may have happened accidentally, it is advisable to check that this is (still) intended.

<site>-local allocation requests volume storage in <other-site>

You have classified this allocation as 'local' to your node, but the allocation includes quota for Volume Storage at another Nectar node. The node-local restrictions implemented in July 2019 mean that the project will only be able to launch instances at your node, and will be unable to use the Volume Storage quota.

<site>-local allocation requests shares in <other-site>

You have classified this allocation as 'local' to your node, but the allocation includes quota for File Shares at another Nectar node. The node-local restrictions implemented in July 2019 mean that the project will only be able to launch instances at your node, and will be unable to use the File Share quota.

Quota should be authorized by the other site before approving <site> storage quota

This just is a reminder that you should always get permission from the site where the storage (volume, fileshare) lives before approving AZ specific storage quota. If you have that permission, this warning can be ignored.

Note that applies to 'national' allocations. (For 'local' allocations, zone-specific storage quotas in another AZ won't be usable, and should not be approved; see above.)

Problem with approver registration: contact Core Services

Please raise a support ticket about this with Core Services.