As part of infrastructure provision there are times when adding or configuring disks for the template being used is required. There is support for adding new disks to VMware, but this same feature is not supported for RHEV-M VM provision requests.
Two possible ways to support this feature with the exist provisioning state-machines in automate are:
- Follow the same pattern used for VMware provisioning as defined in “Defining new disks during provisioning” from the CFME Integration Services Guide.
- Allow an exit point after the VM has been provisioned but before any additional changes to the VM have been performed. This could be achieve a two ways:
- Always call the automate provisioning profile with a specific message, like what is done for VM naming.
- Honor a new provision options key that would accept an automate URI that would be called.
These two options are not mutually exclusive.
The first is focused purely on disks and requires that the model be updated to support collecting and processing the disk options. While much of this can be handled generically there may be some special processing or checks required, but the caller does not have to be concerned with direct interaction with the provider system.
The second option is more open-ended and the caller would be required to interact and perform task through the RHEV-M Restful API.