Welcome to the Linux Foundation Forum!

Need guidance on increase quotas under IAM & admin - not able to find us-central1

Hi there,

I didn't see us-central1 in IAM & admin. Could you please help me here?

Best,

Hale

Comments

  • Hi! I have an update regarding this post. When I select ONAP from the project list, then I tried clicking IAM &Admin --> Quotas and got the following failure, how can I fix it?

    Failed to load.

    There was an error while loading /iam-admin/quotas?folder=&organizationId=&project=onap-177920. Please try again.

    Tracking Number: c5508396542099272

  • Hi, this seems to be an error from the Google cloud account which is either transient or you do not have the permissions to create (or request for increase) the quota). Can you please check with the support team of Google cloud (GCP)?

    Please make sure you login with the appropriate account (in case you have multiple accounts) which you have provided us for image access. As a test, you can try creating a test VM using your account.

    Your id that was given access is: [email protected]

    Please let us know if you still find any issue, or you would like the access on a different account.

  • Hi SriramRupanagunta , I have only 1 gcloud account that I provıded to you. I see 2 projects and I didn2t create those. I am able to see IAM &Admin --> Quotas for My First Project but not able to see for ONAP.

  • vmuthukrishnanvmuthukrishnan Posts: 26
    edited April 14

    Hi Haledonertasli .

    The project **onap-177920 ** is owned by us and you only have read only access to the GCP image to create instances. You can execute the below command to check if you have access to the GCP image.

    $ gcloud compute images list --project onap-177920 | grep 'aarna-aio-openstack-train-centos-7-08062020-00'
    aarna-aio-openstack-train-centos-7-08062020-00 onap-177920 READY

    Also, kindly note that you will have to apply the below workarounds for the respective labs.

    Lab/Exercise 4.1

    Online students should execute the following commands before starting the openstack deployment at Step(5). This is required to pull AIO patches.
        cd $HOME/onap-custom/setup-utils
        git pull -v
        Continue with the LFS263 documented steps.
    

    Lab/Exercise 4.4

    Online students should execute the following commands before starting the ONAP deployment on the ONAP master node at Step(1). This is required to pull ONAP Dublin release latest patches
    
        cd $HOME/onap-custom/
        git pull -v
        Continue with the LFS263 documented steps.
    
  • Hi vmuthukrishnan ,

    I have access to ONAP image. I am stuck at the IAM &Admin --> Quotas step for 2 weeks now. There is no us-central1 in IAM &Admin --> Quotas as instructed in the lab for both ONAP and My First Project. Is the manual getting updated properly? There is no us-central1 in there, instead I see only Compute Engine API and BigQuery API.

    I thinking changing the quotas needs update in ONAP Lab manual. Please advice.

  • HI haledonertasli ,

    Sorry the email notification went to my spam folder and now i fixed it.

    It seems like a quota issue with your Gcloud account. Can you please go to IAM & Admin --> Quota page to verify your CPU, Memory and Disk quota limits.

    If possible we can plan for a meeting tomorrow April/22/2021 between 3:00PM IST and 4:00PM IST. You can send me the Zoom invite to my email [email protected]

    Regards
    Vivek

  • You can also consider using the gcloud CLI to find the quot details for your project.

    $ gcloud projects list
    $ gcloud compute project-info describe --project YOUR_TARGET_PROJECT_NAME

  • I got this:

    gcloud compute project-info describe --project warm-now-309910
    commonInstanceMetadata:
    fingerprint: I1jwEfrgvoQ=
    kind: compute#metadata
    creationTimestamp: '2021-04-16T06:56:02.510-07:00'
    defaultNetworkTier: PREMIUM
    defaultServiceAccount: [email protected]
    id: '4954078533838449053'
    kind: compute#project
    name: warm-now-309910
    quotas:

    • limit: 1000.0
      metric: SNAPSHOTS
      usage: 0.0

    • limit: 5.0
      metric: NETWORKS
      usage: 1.0

    • limit: 100.0
      metric: FIREWALLS
      usage: 5.0

    • limit: 100.0
      metric: IMAGES
      usage: 0.0

    • limit: 8.0
      metric: STATIC_ADDRESSES
      usage: 0.0

    • limit: 200.0
      metric: ROUTES
      usage: 1.0

    • limit: 15.0
      metric: FORWARDING_RULES
      usage: 0.0

    • limit: 50.0
      metric: TARGET_POOLS
      usage: 0.0

    • limit: 50.0
      metric: HEALTH_CHECKS
      usage: 0.0

    • limit: 8.0
      metric: IN_USE_ADDRESSES
      usage: 0.0

    • limit: 50.0
      metric: TARGET_INSTANCES
      usage: 0.0

    • limit: 10.0
      metric: TARGET_HTTP_PROXIES
      usage: 0.0

    • limit: 10.0
      metric: URL_MAPS
      usage: 0.0

    • limit: 5.0
      metric: BACKEND_SERVICES
      usage: 0.0

    • limit: 100.0
      metric: INSTANCE_TEMPLATES
      usage: 0.0

    • limit: 5.0
      metric: TARGET_VPN_GATEWAYS
      usage: 0.0

    • limit: 10.0
      metric: VPN_TUNNELS
      usage: 0.0

    • limit: 3.0
      metric: BACKEND_BUCKETS
      usage: 0.0

    • limit: 10.0
      metric: ROUTERS
      usage: 0.0

    • limit: 10.0
      metric: TARGET_SSL_PROXIES
      usage: 0.0

    • limit: 10.0
      metric: TARGET_HTTPS_PROXIES
      usage: 0.0

    • limit: 10.0
      metric: SSL_CERTIFICATES
      usage: 0.0

    • limit: 100.0
      metric: SUBNETWORKS
      usage: 25.0

    • limit: 10.0
      metric: TARGET_TCP_PROXIES
      usage: 0.0

    • limit: 96.0
      metric: CPUS_ALL_REGIONS
      usage: 0.0

    • limit: 10.0
      metric: SECURITY_POLICIES
      usage: 0.0

    • limit: 100.0
      metric: SECURITY_POLICY_RULES
      usage: 0.0

    • limit: 1000.0
      metric: XPN_SERVICE_PROJECTS
      usage: 0.0

    • limit: 20.0
      metric: PACKET_MIRRORINGS
      usage: 0.0

    • limit: 100.0
      metric: NETWORK_ENDPOINT_GROUPS
      usage: 0.0

    • limit: 6.0
      metric: INTERCONNECTS
      usage: 0.0

    • limit: 5000.0
      metric: GLOBAL_INTERNAL_ADDRESSES
      usage: 0.0

    • limit: 5.0
      metric: VPN_GATEWAYS
      usage: 0.0

    • limit: 100.0
      metric: MACHINE_IMAGES
      usage: 0.0

    • limit: 20.0
      metric: SECURITY_POLICY_CEVAL_RULES
      usage: 0.0

    • limit: 0.0
      metric: GPUS_ALL_REGIONS
      usage: 0.0

    • limit: 5.0
      metric: EXTERNAL_VPN_GATEWAYS
      usage: 0.0

    • limit: 1.0
      metric: PUBLIC_ADVERTISED_PREFIXES
      usage: 0.0

    • limit: 10.0
      metric: PUBLIC_DELEGATED_PREFIXES
      usage: 0.0

    • limit: 128.0
      metric: STATIC_BYOIP_ADDRESSES
      usage: 0.0

    • limit: 15.0
      metric: INTERNAL_TRAFFIC_DIRECTOR_FORWARDING_RULES
      usage: 0.0
      selfLink: https://www.googleapis.com/compute/v1/projects/warm-now-309910
      xpnProjectStatus: UNSPECIFIED_XPN_PROJECT_STATUS

    and I am getting this error

    HALE:~ haleair$ gcloud compute instances create openstack-01 --zone us-central1-f --custom-cpu 32 --custom-memory 72GB --min-cpu-platform "Intel Haswell" --image "https://www.googleapis.com/compute/v1/projects/onap-177920/global/images/aarna-aio-openstack-train-centos-7-08062020-00"
    ERROR: (gcloud.compute.instances.create) Could not fetch resource:
    - Quota 'CPUS' exceeded. Limit: 24.0 in region us-central1.

    But my quota was increased as seen in the picture attached.

  • Hi Haledonertasli,

    Looks like you have the quota to create an instance but for some reason it is failing at the gcloud side. Let me look into google forum and come back to you.

    Regards
    Vivek

  • Hi, looks like there is a per-region limit of 24 due to which it is not allowing you to start the VM with 32 vcpus. I am not sure if this is specific to this region alone (us-central1) or if there is any other limit that exists (which limits the vcpus to per-region). Can you please try from any other region/zone?

    Following is the link to the list of zones. You can probably pick a zone closest to your geographical location.
    https://cloud.google.com/compute/docs/regions-zones

  • You can also try the following command for the per-region limit:
    gcloud compute regions describe

    From GCP documentation:

    Quotas and resource availability
    Resource quotas are the maximum number of resources you can create of that resource type, if those resources are available. Quotas do not guarantee that resources are available at all times. If a resource is not available, or if the region you choose is out of the resource, you can't create new resources of that type, even if you have remaining quota in your region or project. For example, you might still have quota to create external IP addresses in us-central1, but there might not be available IP addresses in that region.

  • Sorry, you need to give the region name - for eg.,
    gcloud compute regions describe us-central1

  • Hi haledonertasli ,

    Let us try reducing the Openstack CPU & Memory resources to verify if you can create an instance. Please use the below command to create a smaller instance.

    $ gcloud compute instances create openstack-01 --zone us-central1-f --custom-cpu 8 --custom-memory 16GB --min-cpu-platform "Intel Haswell" --image "https://www.googleapis.com/compute/v1/projects/onap-177920/global/images/aarna-aio-openstack-train-centos-7-08062020-00"

    Let us know how it goes ?

    Regards
    Vivek

  • vmuthukrishnan, yes it works with the following command but what I must do now? Is it ok to do like this?

    gcloud compute instances create openstack-01 --zone us-central1-f --custom-cpu 8 --custom-memory 16GB --min-cpu-platform "Intel Haswell" --image "https://www.googleapis.com/compute/v1/projects/onap-177920/global/images/aarna-aio-openstack-train-centos-7-08062020-00"
    Created [https://www.googleapis.com/compute/v1/projects/warm-now-309910/zones/us-central1-f/instances/openstack-01].
    NAME ZONE MACHINE_TYPE PREEMPTIBLE INTERNAL_IP EXTERNAL_IP STATUS
    openstack-01 us-central1-f custom-8-16384 10.128.0.2 35.224.84.132 RUNNING

  • SriramRupanagunta , here is the output, what should I do now?

    HALE:~ haleair$ gcloud compute regions describe us-central1
    creationTimestamp: '1969-12-31T16:00:00.000-08:00'
    description: us-central1
    id: '1000'
    kind: compute#region
    name: us-central1
    quotas:

    • limit: 24.0
      metric: CPUS
      usage: 0.0

    • limit: 4096.0
      metric: DISKS_TOTAL_GB
      usage: 0.0

    • limit: 8.0
      metric: STATIC_ADDRESSES
      usage: 0.0

    • limit: 8.0
      metric: IN_USE_ADDRESSES
      usage: 0.0

    • limit: 500.0
      metric: SSD_TOTAL_GB
      usage: 0.0

    • limit: 6000.0
      metric: LOCAL_SSD_TOTAL_GB
      usage: 0.0

    • limit: 100.0
      metric: INSTANCE_GROUPS
      usage: 0.0

    • limit: 50.0
      metric: INSTANCE_GROUP_MANAGERS
      usage: 0.0

    • limit: 24.0
      metric: INSTANCES
      usage: 0.0

    • limit: 50.0
      metric: AUTOSCALERS
      usage: 0.0

    • limit: 20.0
      metric: REGIONAL_AUTOSCALERS
      usage: 0.0

    • limit: 20.0
      metric: REGIONAL_INSTANCE_GROUP_MANAGERS
      usage: 0.0

    • limit: 0.0
      metric: PREEMPTIBLE_CPUS
      usage: 0.0

    • limit: 1.0
      metric: NVIDIA_K80_GPUS
      usage: 0.0

    • limit: 0.0
      metric: COMMITTED_CPUS
      usage: 0.0

    • limit: 0.0
      metric: COMMITTED_LOCAL_SSD_TOTAL_GB
      usage: 0.0

    • limit: 0.0
      metric: COMMITMENTS
      usage: 0.0

    • limit: 100.0
      metric: NETWORK_ENDPOINT_GROUPS
      usage: 0.0

    • limit: 200.0
      metric: INTERNAL_ADDRESSES
      usage: 0.0

    • limit: 1.0
      metric: NVIDIA_P100_GPUS
      usage: 0.0

    • limit: 0.0
      metric: PREEMPTIBLE_LOCAL_SSD_GB
      usage: 0.0

    • limit: 1.0
      metric: PREEMPTIBLE_NVIDIA_K80_GPUS
      usage: 0.0

    • limit: 1.0
      metric: PREEMPTIBLE_NVIDIA_P100_GPUS
      usage: 0.0

    • limit: 1.0
      metric: NVIDIA_P100_VWS_GPUS
      usage: 0.0

    • limit: 1.0
      metric: NVIDIA_V100_GPUS
      usage: 0.0

    • limit: 1.0
      metric: NVIDIA_P4_GPUS
      usage: 0.0

    • limit: 1.0
      metric: NVIDIA_P4_VWS_GPUS
      usage: 0.0

    • limit: 100.0
      metric: NODE_GROUPS
      usage: 0.0

    • limit: 100.0
      metric: NODE_TEMPLATES
      usage: 0.0

    • limit: 1.0
      metric: PREEMPTIBLE_NVIDIA_V100_GPUS
      usage: 0.0

    • limit: 1.0
      metric: PREEMPTIBLE_NVIDIA_P4_GPUS
      usage: 0.0

    • limit: 1.0
      metric: PREEMPTIBLE_NVIDIA_P100_VWS_GPUS
      usage: 0.0

    • limit: 1.0
      metric: PREEMPTIBLE_NVIDIA_P4_VWS_GPUS
      usage: 0.0

    • limit: 16.0
      metric: INTERCONNECT_ATTACHMENTS_PER_REGION
      usage: 0.0

    • limit: 80000.0
      metric: INTERCONNECT_ATTACHMENTS_TOTAL_MBPS
      usage: 0.0

    • limit: 5.0
      metric: RESOURCE_POLICIES
      usage: 0.0

    • limit: 20.0
      metric: IN_USE_SNAPSHOT_SCHEDULES
      usage: 0.0

    • limit: 1.0
      metric: NVIDIA_T4_GPUS
      usage: 0.0

    • limit: 1.0
      metric: NVIDIA_T4_VWS_GPUS
      usage: 0.0

    • limit: 1.0
      metric: PREEMPTIBLE_NVIDIA_T4_GPUS
      usage: 0.0

    • limit: 1.0
      metric: PREEMPTIBLE_NVIDIA_T4_VWS_GPUS
      usage: 0.0

    • limit: 20.0
      metric: IN_USE_BACKUP_SCHEDULES
      usage: 0.0

    • limit: 10.0
      metric: PUBLIC_DELEGATED_PREFIXES
      usage: 0.0

    • limit: 0.0
      metric: COMMITTED_NVIDIA_K80_GPUS
      usage: 0.0

    • limit: 0.0
      metric: COMMITTED_NVIDIA_P100_GPUS
      usage: 0.0

    • limit: 0.0
      metric: COMMITTED_NVIDIA_P4_GPUS
      usage: 0.0

    • limit: 0.0
      metric: COMMITTED_NVIDIA_V100_GPUS
      usage: 0.0

    • limit: 0.0
      metric: COMMITTED_NVIDIA_T4_GPUS
      usage: 0.0

    • limit: 8.0
      metric: C2_CPUS
      usage: 0.0

    • limit: 8.0
      metric: N2_CPUS
      usage: 0.0

    • limit: 0.0
      metric: COMMITTED_N2_CPUS
      usage: 0.0

    • limit: 0.0
      metric: COMMITTED_C2_CPUS
      usage: 0.0

    • limit: 100.0
      metric: RESERVATIONS
      usage: 0.0

    • limit: 0.0
      metric: COMMITTED_LICENSES
      usage: 0.0

    • limit: 8.0
      metric: N2D_CPUS
      usage: 0.0

    • limit: 0.0
      metric: COMMITTED_N2D_CPUS
      usage: 0.0

    • limit: 128.0
      metric: STATIC_BYOIP_ADDRESSES
      usage: 0.0

    • limit: 0.0
      metric: AFFINITY_GROUPS
      usage: 0.0

    • limit: 0.0
      metric: NVIDIA_A100_GPUS
      usage: 0.0

    • limit: 0.0
      metric: PREEMPTIBLE_NVIDIA_A100_GPUS
      usage: 0.0

    • limit: 0.0
      metric: COMMITTED_NVIDIA_A100_GPUS
      usage: 0.0

    • limit: 0.0
      metric: M1_CPUS
      usage: 0.0

    • limit: 0.0
      metric: M2_CPUS
      usage: 0.0

    • limit: 0.0
      metric: A2_CPUS
      usage: 0.0

    • limit: 0.0
      metric: COMMITTED_A2_CPUS
      usage: 0.0

    • limit: 0.0
      metric: COMMITTED_MEMORY_OPTIMIZED_CPUS
      usage: 0.0

    • limit: 15.0
      metric: EXTERNAL_NETWORK_LB_FORWARDING_RULES
      usage: 0.0

    • limit: 15.0
      metric: EXTERNAL_PROTOCOL_FORWARDING_RULES
      usage: 0.0
      selfLink: https://www.googleapis.com/compute/v1/projects/warm-now-309910/regions/us-central1
      status: UP
      supportsPzs: false
      zones:

    • https://www.googleapis.com/compute/v1/projects/warm-now-309910/zones/us-central1-a

    • https://www.googleapis.com/compute/v1/projects/warm-now-309910/zones/us-central1-b
    • https://www.googleapis.com/compute/v1/projects/warm-now-309910/zones/us-central1-c
    • https://www.googleapis.com/compute/v1/projects/warm-now-309910/zones/us-central1-f
      HALE:~ haleair$
  • Hi haledonertasli ,

    Good. This seems to suggest that you do not enough CPU quota to bring up a larger instance. You may want to contact your IT team otherwise you can request Google cloud to increase the CPU & Memory quota for the given region.

    I guess it should help you.

    Regards
    Vivek

  • @haledonertasli said:
    SriramRupanagunta , here is the output, what should I do now?

    HALE:~ haleair$ gcloud compute regions describe us-central1
    creationTimestamp: '1969-12-31T16:00:00.000-08:00'
    description: us-central1
    id: '1000'
    kind: compute#region
    name: us-central1
    quotas:

    > - limit: 24.0

    metric: CPUS
    usage: 0.0

    This confirms that in us-central1, you can only allocate 24 cpus.

    So, you seem to have sufficient resources across all regions, but less resources in a single region. You need to ask them to increase them per-region, since you need one large instance in a single region.

    As Vivek suggested, can you please contact GCP support, and request them to increase the quota "per region"?

    You do need a large instance as documented, since some of the lab exercises will fail with less resources.

  • OK. This problem is resolved. Thank you!

Sign In or Register to comment.