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 work flows 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.

If you need help or advice on quotas and quota consistency, you can raise a support ticket about this. (When the requested quotas are modest and sensible, your chances of a quick approval are increased.)

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 flavour 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.

Database servers requested without any database storage.

Explanation: The Nectar database service requires both a server and disk storage to hold the database.

Impact: Without database storage quota you will not be able to create a database server.

Remedy: Either remove the database server quota (set it to zero), or add at least 1 GB of database storage. Note that the maximum supported size for a Nectar database is 1 TB.

Database storage requested without any database servers.

Explanation: The Nectar database service requires both a server and disk storage to hold the database.

Impact: Without database server quota you will not be able to create a database server.

Remedy: Either remove the database storage quota (set it to zero), or add at least 1 database server.

Database storage requested without object storage for backup.

Explanation: The Nectar database service uses object storage for backup, and uses your object storage quota for this.

Impact: If you do not have sufficient object storage quota, you will not be able to use the database backup facility. If your database is going to contain valuable information, it ought to be backed up regularly. Note however that there are other ways to backup a database over the network.

Remedy: Request sufficient object storage quota to hold your anticipated database backups.

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.

Openstack clusters require instance quota

Explanation: Kubernetes clusters running under the Openstack Cluster Orchestration Engine service use instances to provide the nodes in the cluster. Your project will require sufficient Openstack compute quota (instance and VCPUs) to allow the nodes to be launched. We recommend quota for at least 2 nodes in each cluster to provide redundancy and to facilitate smooth upgrades.

Impact: Without sufficient instance quota, you may not be able to set up a robust / maintainable Kubernetes cluster.

Remedy: We recommend that you increase the instance quota to at least 2 times the number of clusters that you intend to run, and adjust the VCPU quotas accordingly.

Openstack clusters require network quota

Explanation: Each Kubernetes cluster running under the Openstack Cluster Orchestration Engine service makes use of a private network.

Impact: Without sufficient network quota, you will not be able to launch a Kubernetes cluster.

Remedy: Increase your network quota so that you have one networ for each cluster.

Openstack clusters require floating IP quota

Explanation: Each Kubernetes cluster running under the Openstack Cluster Orchestration Engine service needs one floating IP address for the control infrastructure, and (probably) at least one more for your services.

Impact: Without sufficient floating IP quota, you will not be able to launch a Kubernetes cluster.

Remedy: Increase your floating IP quota so that Kubernetes can use at least two floating IPs for each cluster.

Openstack clusters require load balancer quota

Explanation: Each Kubernetes cluster running under the Openstack Cluster Orchestration Engine service makes use of a two load balancers internally. If you have externally facing services, they will need at least one additional load balancer.

Impact: Without sufficient load balancer quota, you will not be able to launch a Kubernetes cluster.

Remedy: Increase your load balancer quota so that you have three load balancers for each cluster.

Openstack clusters require router quota

Explanation: Each Kubernetes cluster running under the Openstack Cluster Orchestration Engine service makes use of a router for its private network.

Impact: Without router quota, you will not be able to launch a Kubernetes cluster.

Remedy: Increase your router quota so that you have one router for each cluster.

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 4GB per VCPU ratio will only work if the allocation has access to flavors with a higher ratio. 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.