[jira] [Commented] (CLOUDSTACK-2056) DeploymentPlanner choice via ServiceOffering

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660066#comment-13660066 ] 

ASF subversion and git services commented on CLOUDSTACK-2056:
-------------------------------------------------------------

Commit a2eb7bab1ef67de6589053ccd45515cf410d187c in branch refs/heads/master from Prachi Damle <pr...@cloud.com>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a2eb7ba ]

CLOUDSTACK-2056: DeploymentPlanner choice via ServiceOffering

- Changes merged from planner_reserve branch
- Exposing deploymentplanner as an optional parameter while creating a service offering
- changes to DeploymentPlanningManagerImpl to make sure host reserve-release happens between conflicting planner usages.

                
> 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