Edit Orchestration Model
To edit an orchestration model, use the following request:
| |
XML Request Example
| |
JSON Request Example
| |
Where:
- label - the name of the orchestration model
- hypervisor_id - the ID of the compute resource associated with the orchestration model
- provider_vdc_id - the ID of the provider vDC that will be used when an organization vDC will be deployed from the orchestration model
- vdc_model_type - the resource pool type: allocation, reservation or pay_as_you_go
- cpu_allocation_min - the minimum amount of allocated CPU resources, that can be set during orchestration model deployment
- cpu_allocation_max - the maximum amount of allocated CPU resources, that can be set during orchestration model deployment
- cpu_allocation_default - the default amount of allocated CPU resources, that will be set during orchestration model deployment
- cpu_allocation_customizable - set to “1”, if you want the CPU allocation related parameters to be editable during orchestration model deployment, otherwise set to “0”
- cpu_allocation_visible - set to “1”, if you want the CPU allocation related parameters to be visible during orchestration model deployment, otherwise set to “0”
- cpu_guaranteed_min - the minimum amount of guaranteed CPU, that can be set during orchestration model deployment
- cpu_guaranteed_max - the maximum amount of guaranteed CPU, that can be set during orchestration model deployment
- cpu_guaranteed_default - the default amount of guaranteed CPU, that will be set during orchestration model deployment
- cpu_guaranteed_customizable - set to “1”, if you want the CPU guaranteed related parameters to be editable during orchestration model deployment, otherwise set to “0”
- cpu_guaranteed_visible - set to “1”, if you want the CPU guaranteed related parameters to be visible during orchestration model deployment, otherwise set to “0”
- memory_min - the minimum amount of allocated memory, that can be set during orchestration model deployment
- memory_max - the maximum amount of allocated memory, that can be set during orchestration model deployment
- memory_default - the default amount of allocated memory, that will be set during orchestration model deployment
- memory_customizable - set to “1”, if you want the memory related parameters to be editable during orchestration model deployment, otherwise set to “0”
- memory_visible - set to “1”, if you want the memory related parameters to be visible during orchestration model deployment, otherwise set to “0”
- memory_guaranteed_min - the minimum amount of guaranteed memory allocation, that can be set during orchestration model deployment
- memory_guaranteed_max - the maximum amount of guaranteed memory allocation, that can be set during orchestration model deployment
- memory_guaranteed_default - the default amount of guaranteed memory allocation, that will be set during orchestration model deployment
- memory_guaranteed_customizable - set to “1”, if you want the memory guaranteed related parameters to be editable during orchestration model deployment, otherwise set to “0”
- memory_guaranteed_visible - set to “1”, if you want the memory guaranteed related parameters to be visible during orchestration model deployment, otherwise set to “0”
- vm_number_min - the minimum number of VSs, that will be set during orchestration model deployment
- vm_number_max - the maximum number of VSs, that will be set during orchestration model deployment
- vm_number_default - the default number of VSs, that will be set during orchestration model deployment
- vm_number_customizable - set to “1”, if you want the VS number related parameters to be editable during orchestration model deployment, otherwise set to “0”
- vm_number_visible - set to “1”, if you want the VS number related parameters to visible be during orchestration model deployment, otherwise set to “0”
- default_network_pool - set a network pool
- edge_gateway_name - fill in the label for the new edge gateway. The default name is MyEdgeGateway.
- networks_to_create - the array of parameters related to the networks that will be created when the orchestration model is deployed
- name - the label for the network
- type - the type of the network: routed, isolated or direct
- network_address - fill in the network address
- dns - DNS for the network
- enable_thin_provisioning - set to “1” to enable thin provisioning, otherwise set to “0”
- enable_fast_provisioning - set to “1” to enable fast provisioning, otherwise set to “0”
- data_stores_to_create - the array of parameters related to the data stores that will be created when the orchestration model is deployed
- label - the label of the data store zone in which a data store will be created during orchestration model deployment
- id - the ID of the data store zone in which a data store will be created during orchestration model deployment
- min - the minimum data store size that can be requested during orchestration model deployment
- max - the maximum data store size that can be requested during orchestration model deployment
- default - the default data store size that will be set during orchestration model deployment
- data_store_customizable - set to “true” if you want that the data store size can be altered during orchestration model deployment, otherwise set to “false”
- data_store_visible - set to “true” for the data store to be listed during orchestration model deployment, otherwise set to “false”.If the data store zone is not visible, a data store will still be created in it.
- use_it - set to “true” for the data store to be created during orchestration model deployment, otherwise set to “false”