[
https://issues.apache.org/jira/browse/CLOUDSTACK-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle resolved CLOUDSTACK-2056.
--------------------------------------
Resolution: Fixed
> DeploymentPlanner choice via ServiceOffering
> ---------------------------------------------
>
> Key: CLOUDSTACK-2056
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2056
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Reporter: Prachi Damle
> Assignee: Prachi Damle
> Fix For: 4.2.0
>
>
> Currently in a CloudStack deployment, only one of these planners can be used
> for all VM deployments. The global parameter 'vm.allocation.algorithm'
> decides which planner will be used.
> However there could be a need to be able to choose different planning
> strategies within a single CS deployment. So letting Admin choose a
> deployment planner for a set of VMs will be helpful.
> To enable this, proposal is:
> 1) Expose deployment planner as part of a ServiceOffering API. By
> default, the value can be set to the default CS FirstFitPlanner, but admin
> can override it and set some other strategy as per needs.
> 2) Add a resource reservation mechanism to let deployment planners co-exist
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
