Edit Access Control for VPC Server Type

To edit Access Control, use the following request:

1
2
PUT /billing/buckets/:bucket_id/access_controls.xml
PUT /billing/buckets/:bucket_id/access_controls.json

XML Request Example

1
curl -i -X PUT http://onapp.test/billing/buckets/1/access_controls.xml -u user:userpass -H 'Accept: application/xml' -H 'Content-Type: application/xml' -d '<access-control><target_id type="integer">30</target_id><type>compute_zone_resource</type><bucket_id type="integer">1</bucket_id><server_type>vpc</server_type><apply_to_all_resources_in_the_bucket>true</apply_to_all_resources_in_the_bucket><limits><limit_cpu_share>1</limit_cpu_share><limit_cpu_units>1</limit_cpu_units><limit_memory>1</limit_memory><limit_default_cpu>1</limit_default_cpu><limit_min_cpu>1</limit_min_cpu><limit_min_memory>1</limit_min_memory><limit_default_cpu_share>1</limit_default_cpu_share><limit_min_cpu_priority>1</limit_min_cpu_priority><use_cpu_units>1</use_cpu_units><limit_nsxt_edge_gateways type="integer">15</limit_nsxt_edge_gateways></limits></access-control>'

JSON Request Example

1
curl -i -X PUT http://onapp.test/billing/buckets/1/access_controls.json -u user:userpass -H 'Accept: application/json' -H 'Content-Type: application/json' -d '{"target_id":30,"type":"compute_zone_resource","bucket_id":1,"server_type":"vpc","apply_to_all_resources_in_the_bucket":"true","limits":{"limit_cpu_share":1.0,"limit_cpu_units":1.0,"limit_memory":1.0,"limit_default_cpu":1.0,"limit_min_cpu":1.0,"limit_min_memory":1.0,"limit_default_cpu_share":1.0,"limit_min_cpu_priority":1.0,"use_cpu_units":1.0, "limit_nsxt_edge_gateways": 8}}'

Where:

target_id - the ID of the resource for which access control is configured

type* - the type of the resource, it can be one of the following values:

virtual_servers_resource
application_servers_resource
compute_zone_resource
data_store_zone_resource
network_zone_resource

bucket_id* - the ID of the bucket with which this access control is associated

server_type* - the server type this access control is applicable to. For VPS resources, it is VPC .

apply_to_all_resources_in_the_bucket - set to true to apply limits that you pass for a zone resource to all resources of the same type in the bucket. The parameter is applicable to the following recourse types:

compute_zone_resource
data_store_zone_resource
network_zone_resource

limits - the array of limits for a resource. Depending on the type of resource, you can have limits described in the table below.

VPC Server Type
Type	Parameters	Description
virtual_servers_resource	limit	the total amount of VSs the users can create in the cloud (VS/hour)
application_servers_resource	limit	the total amount of application servers that the users can create in the cloud (application VS/hour)
compute_zone_resource	limit_cpu_share	the maximum amount of CPU shares users can request for all their servers in this compute zone under this bucket (CPU share %/hour)
	limit_cpu_units	the maximum amount of CPU units that users can request for all their VSs within this compute zone under the bucket (CPU unit/hour)
	limit_memory	the maximum amount of RAM that users can request for all their VSs within this compute zone under the bucket (Mb/hour)
	limit_default_cpu	the default amount of CPU cores that will be set in the VS creation wizard when the user adds a VS in this compute zone under this bucket (CPU core/hour)
	limit_min_cpu	the minimum amount of CPU cores that can be set in the VS creation wizard when the user adds a VS under this bucket in the compute zone (CPU core/hour)
	limit_min_memory	the minimum amount of RAM that can be set in the VS creation wizard when the user adds a VS under this bucket in the compute zone (Mb/hour)
	limit_default_cpu_share	the default amount of CPU shares that will be set in the VS creation wizard when the user adds a VS in this compute zone under this bucket (CPU share %/hour)
	limit_min_cpu_priority	the minimum amount of CPU priority which can be set in the VS creation wizard when the user adds a VS under this bucket in the compute zone (CPU share %/hour)
	use_cpu_units	set to "1" to use CPU shares instead of CPU priority (CPU unit/hour). Otherwise, set to "0". Set the number of CPU units available to users under this bucket using the limit_cpu_units parameter.
	limit_nsxt_edge_gateways	the maximum number of NSX-T edge gateways that can be created in a compute zone
data_store_zone_resource	limit_min_disk_size	the minimum amount of disk size (users can request for each storage policy (data store) in a provider storage policy (data store zone) (GB/hour)
	limit_disk_size	the maximum amount of disk size users can request for each storage policy (data store) in a provider storage policy (data store zone) (GB/hour)
	limit_vs_disk_size	the maximum amount of disk size that users can request for all VSs totally within the whole data store zone (GB/hour)
network_zone_resource	limit_ip	the maximum number of IP Addresses users can request to deploy Edge Gateways for the whole network zone (IP/hour)
network_zone_resource	limit_vs_ip	the maximum amount of IP addresses that users can allocate to deploy/recompose a vApp within the whole network zone (IP/hour)

Page History

v.6.5 Edge 4

Added limit_nsxt_edge_gateways parameter