| Table of Contents | ||
|---|---|---|
|
...
| Excerpt | ||||
|---|---|---|---|---|
| ||||
Before you begin:
To modify a VM template:
 In private cloud datacenters, standard templates have disks that will deploy to the hypervisor datastore, in contrast to persistent templates that have disks on external storage volumes. This documentation describes standard templates. Edit template general informationEnter the general information about the template as follows: 
|
...
Edit VM template variables
...
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.
The variables will be added automatically to new VMs. Users can edit the variables when configuring the VM.
After the VM deploys, users can then access variables in the guest.
For example, AWS stores the variables in the ~/vm-variables.rc file. Cloud-init may use variables. Remember to check your provider documentation about metadata security.
...
Share VM templates from the scopes tab
...
In the Catalogue view, shared templates are marked with the outstretched hand symbol.
...
| Panel |
|---|
Privileges: Allow user to switch enterprises |
By default, templates are local to the tenant that creates them (the "owner" enterprise). To share templates, assign scopes to them.
| Tip |
|---|
Users who belong to the owner enterprise or enterprises in a template's scopes can display and use the template. |
To share a template with a scope:
Go to Users → Scopes
Create a scope
For enterprises to use the template, select them in the scope
Log in or switch to the enterprise that owns the template
Go to Catalogue → Templates
Edit a template
Go to Scopes
Select the scope
For more information, see Manage scopes and Manage resource scopes
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.
You cannot remove a scope from the template if an enterprise in the scope is using the template, for example, if it has deployed VMs or instances of VMs.
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.
...
Activate hardware profiles for a VM template
...
Activate datastore tiers for a VM template
...
When you edit a VM template in private cloud, you can recommend some datastore tiers for users when they create VMs from this template. You can also restrict users to the recommended tiers.
By default, when users configure VMs, they can access all datastore tiers that are appropriately configured in the infrastructure and allowed for their enterprise.
To activate a set of selected datastore tiers for a template:
Go to Apps library → Private → select region or datacenter → Templates
Edit the template
Go to Recommended
Select the datastore tiers to recommend for this template. The platform will display these datastore tiers in the selection list with (Recommended) beside them. Remember that the administrator must allow the user's tenant to access the datastore tiers
To activate and display the recommended datastore tiers only, select the Enable only recommended DS tiers option
...
...
Add a bootstrap script to a VM template
...
Go to Catalogue → Edit VM template
Go to Bootstrap
Paste your configuration or script in the Bootstrap script text box
Continue to configure the VM template or click Save to finish
...
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
Edit template advanced tab
You can also specify some Advanced template values using the OVF and the API. See Extended OVF support and template definition.
...
Field | Value |
|---|---|
Guest setup | Select Guest setup option of Cloud-init or Hypervisor tools. |
Guest initial password | If Guest setup is selected, select this option to request an initial password |
Cost code |
|
...
. For more details, see Multiple cost codes. | |
Operating system | Sets the VMware guest operating system type. Select from the pull-down list. |
Os Version | OS version is used to:
See Guest operating system definition for VMware and Extended OVF support and template definition for further details. |
User | Default user for a VM created from this template for SSH access.
|
Password | Default password for the default User of a VM created from this template. |
NIC driver |
|
Enable UEFI boot | When selected, disable BIOS boot and enable UEFI boot.
For VMs, the uefiEnabled attribute is read-only and it is available via the API. |
Enable hot add / reconfigure in VM | See separate section |
Creation user | SYSTEM means that the platform created the template, for example, from an OVF file in the NFS repository. |
Creation date | Date and time when the template was created. |
Enable hot add and hot reconfigure for VM templates
To allow users to reconfigure their VMs without powering off, set these values as described on the Advanced tab of the VM edit dialog.
...
Add tags to a VM template
...
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:
Go to Apps library → select a datacenter or public cloud region
Go to Templates
Edit a template
Add tags
For more details see Edit resource tags
...
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. |
...