[
https://issues.apache.org/jira/browse/CLOUDSTACK-9975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Beims Bräscher updated CLOUDSTACK-9975:
-----------------------------------------------
Description:
Currently, it is only possible to change the template used by virtual routers,
but other system VMs do not have the same feature. The virtual router template
is configured according to the respective global settings parameters:
router.template.hyperv, router.template.kvm, router.template.lxc,
router.template.xenserver, router.template.ovm, router.template.vmware.
This ticket proposes the configuration of templates for storage system VMs
(SSVMs) and console proxy system VMs with parameters similar with the virtual
router template configuration: ssvm.template.<virtualization-tool> and
consoleproxy.template.<virtualization-tool>
If a parameter is null then it keeps the current flow for that scenario
(systemvm/virtualization tool).
This proposal allows users to customize virtual machines templates according to
specific needs of each system VM. This feature was useful in a practical
scenario where it was necessary to perform some changes for the console proxy
system VM template.
was:
Currently, it is only possible to change the template used by virtual routers,
but other system VMs does not have the same feature. The virtual router
template is configured according to the respective global settings parameters:
router.template.hyperv, router.template.kvm, router.template.lxc,
router.template.xenserver, router.template.ovm, router.template.vmware.
This ticket proposes the configuration of templates for storage system VMs
(SSVMs) and console proxy system VMs with parameters similar with the virtual
router template configuration: ssvm.template.<virtualization-tool> and
consoleproxy.template.<virtualization-tool>
If a parameter is null then it keeps the current flow for that scenario
(systemvm/virtualization tool).
This proposal allows users to customize virtual machines templates according to
specific needs of each system VM. This feature was useful in a practical
scenario where it was necessary to perform some changes for the console proxy
system VM template.
> Allow customizing system VM templates for SSVM, VR, and Console Proxy
> ---------------------------------------------------------------------
>
> Key: CLOUDSTACK-9975
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9975
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Gabriel Beims Bräscher
> Assignee: Gabriel Beims Bräscher
> Priority: Minor
>
> Currently, it is only possible to change the template used by virtual
> routers, but other system VMs do not have the same feature. The virtual
> router template is configured according to the respective global settings
> parameters: router.template.hyperv, router.template.kvm, router.template.lxc,
> router.template.xenserver, router.template.ovm, router.template.vmware.
> This ticket proposes the configuration of templates for storage system VMs
> (SSVMs) and console proxy system VMs with parameters similar with the virtual
> router template configuration: ssvm.template.<virtualization-tool> and
> consoleproxy.template.<virtualization-tool>
> If a parameter is null then it keeps the current flow for that scenario
> (systemvm/virtualization tool).
> This proposal allows users to customize virtual machines templates according
> to specific needs of each system VM. This feature was useful in a practical
> scenario where it was necessary to perform some changes for the console proxy
> system VM template.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
