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

Devdeep Singh commented on CLOUDSTACK-4356:
-------------------------------------------

Explicit and implicit dedication work differently.

Explicit dedication is enforced using pre-processors (explicit dedication 
processor). A user while deploying an instance can choose to deploy it on a 
dedicated resource (zone/pod/cluster/host) by passing the explicit dedication 
processor as a parameter in deployvm command. Currently the processor ignores 
systemvm. This was done so that system vm deployments can work if the entire 
zone is dedicated.

Implicit dedication is achieved by an implicit dedication planner. While 
creating a service offering the administrator can choose to use an implicit 
dedication planner (default is firstfit). If an implicit dedication planner is 
used all the hosts running vms of other accounts (+ few other criterias are 
considered) are placed in avoid set. These hosts then do not get picked up for 
deploying an instance created using the service offering (with implicit 
planner). System vms are not ignored by the implicit planner. Initial 
implmentation used to ignore system vms (like explicit); but since the 
systemvms may consume significant cpu cycles, the behaviour was changed to not 
to ignore them. So, if a host is running systemvms; it'll not be picked up for 
implicit dedication to an account.
                
> [Automation] TestImplicitPlanner test case failed to deploy VM
> --------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4356
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4356
>             Project: CloudStack
>          Issue Type: Test
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Automation
>    Affects Versions: 4.2.0
>         Environment: Automation
>            Reporter: Rayees Namathponnan
>            Assignee: Devdeep Singh
>             Fix For: 4.2.0
>
>
> Test cases 
> integration.component.test_implicit_planner.TestImplicitPlanner.test_01_deploy_vm_with_implicit_planner
>  failed deploy VM
> Looks like test case trying to deploy VM eventhoug not found any host with 
> empty VM,  test case should check for host with empty VM second zone,  if 
> still didnt find any host with empty VM, test case should skip 

--
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

Reply via email to