Table of Contents | ||
---|---|---|
|
...
Excerpt | ||
---|---|---|
| ||
To You can add variables to a VM template, enter the Key and Value, then click Add. To edit an existing value, click the pencil icon, enter the new Value, then click ok. To save your changes to the template, click Save. The variables will be added automatically to new VMs. Users can VM templates and the platform will automatically add them to new VMs that users create from the templates. Users can then edit the variables when configuring the VMtheir VMs. After the VM deploys, users can then access variables in the guest.
To add variables to a VM template, enter the Key and Value, then click Add. To edit an existing value, click the pencil icon, enter the new Value, then click ok. To save your changes to the template, click Save. |
...
Share VM templates
Excerpt | ||||
---|---|---|---|---|
| ||||
In the Catalogue view, shared templates are marked with the outstretched hand symbol.
By default, templates are local to the tenant that creates them (the "owner" enterprise). To share templates, assign scopes to them.
To share a template with a scope:
For more information, see Manage scopes and Manage resource scopes Screenshot: To share a template with the enterprises in one or more scopes, select template scopes. To remove enterprise access to a template, remove the scope containing the enterprise.
To make a template private to the owner enterprise, unselect all scopes. In private cloud, the instances of shared templates belong to the enterprise that created them. When a template has instances, it is "in use" by the enterprises with instances. This may mean that you cannot delete a template without deleting or promoting the instances first. When you make a shared template unavailable, other enterprises cannot deploy it, but it may not be marked as "unavailable" in the Catalogue of other enterprises until you refresh your Catalogue. |
...
Excerpt | ||
---|---|---|
| ||
Add a bootstrap script to a VM template and the platform will add it to all VMs created from the template to use with the Cloud-init or similar options for Guest setup. Before you begin:
To add a VM bootstrap configuration or script:
Note: when you save VM disks to an instance template, Abiquo copies the VM bootstrap script to the instance template. For details of how to work with bootstrap scripts in a VM, see VM bootstrap script |
...
Excerpt | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
You can also specify some Advanced template values using the OVF and the API. See Extended OVF support and template definition .
|
...
Excerpt | |||||
---|---|---|---|---|---|
| |||||
When you edit a VM template, you can add extra charges for cloud billing.
|
...
Add tags to a VM template
Excerpt | ||
---|---|---|
| ||
When you edit a VM template, you can add tags to group resources and manage them in Control view. To manage tags for a template:
|
...
Manage VM templates with the API
Tip |
---|
API Documentation For the Abiquo API documentation of this feature, see Abiquo API Resources and the page for this resource VirtualMachineTemplatesResource. |
...