After adding an NSX VPC in a project, you can add one or multiple quotas to define a maximum limit for the number of objects of a specific type that users can create in the NSX VPC.
When you set a quota for an object type in an NSX VPC, it implies that the total number of user-created objects of that type in the NSX VPC cannot exceed that limit.
For example, assume that you have set a quota for 10 subnets in an NSX VPC. In this case, the total number of subnets that users can add in the NSX VPC cannot exceed 10.
- Scenario: Set a quota for the same object more than once in the same NSX VPC
-
System allows you to set a quota for the same object more than once and apply it to the same NSX VPC. However, in such a situation, the quota with the lower limit is enforced for that object in the NSX VPC. For example, consider the following sequence of events:
- User A creates quota 1 for the group object, and specifies the limit as 100.
- Quota 1 is applied to NSX VPC 1.
- Later, user A creates quota 2 for the group object and specifies the limit as 50.
- Quota 2 is also applied to NSX VPC 1.
In this case, system enforces the limit of 50 on the group object in NSX VPC 1.
The following procedure explains the workflow of adding quota for objects inside an NSX VPC from the project view. If you want to set limits on the total number of objects that users can create in the NSX VPCs across a project, you must switch to the default space. For more information, see Add Quota to an NSX Project.
Prerequisites
- Project Admin
- Enterprise Admin
Procedure
Results
When the number of user-created objects in an NSX VPC reaches the limit that is set for the object, an alarm is triggered in the system when you try to create and save another object of the same type.
Alarms for the Creation Count Limit Reached event are visible to the Project Admin, but not to the VPC Admin.