[
https://issues.apache.org/jira/browse/CLOUDSTACK-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Purushothama closed CLOUDSTACK-2155.
--------------------------------------------
Verified the following scenarios with 4.2 Build.
Used Setup with 3 ESXi 5.0 Update 2 hosts. The three hosts are in three
different clusters.
Scenario 1: Tried to deploy 7 VMs in parallel with one affinity group.
mysql> select id,name,host_id,state,removed from vm_instance where name like
"helloMore%";
+----+-------------+---------+-----------+---------------------+
| id | name | host_id | state | removed |
+----+-------------+---------+-----------+---------------------+
| 19 | helloMore-3 | 6 | Running | NULL |
| 20 | helloMore-1 | 1 | Starting | NULL |
| 21 | helloMore-4 | 3 | Running | NULL |
| 22 | helloMore-5 | NULL | Expunging | 2013-08-09 23:40:01 |
| 23 | helloMore-7 | NULL | Expunging | 2013-08-09 23:40:01 |
| 24 | helloMore-2 | NULL | Expunging | 2013-08-09 23:40:01 |
| 25 | helloMore-6 | NULL | Expunging | 2013-08-09 23:40:01 |
+----+-------------+---------+-----------+---------------------+
7 rows in set (0.00 sec)
mysql> select * from affinity_group_vm_map;
+----+-------------------+-------------+
| id | affinity_group_id | instance_id |
+----+-------------------+-------------+
| 19 | 2 | 19 |
| 20 | 2 | 21 |
| 21 | 2 | 20 |
+----+-------------------+-------------+
3 rows in set (0.00 sec)
mysql>
Scenario 2: Tried to deploy 7 VMs in parallel with two affinity groups.
mysql> select * from affinity_group_vm_map where affinity_group_id in (1,5);
+----+-------------------+-------------+
| id | affinity_group_id | instance_id |
+----+-------------------+-------------+
| 26 | 1 | 26 |
| 27 | 5 | 26 |
| 28 | 1 | 27 |
| 29 | 5 | 27 |
| 30 | 1 | 28 |
| 31 | 5 | 28 |
+----+-------------------+-------------+
6 rows in set (0.00 sec)
mysql> select id,name,host_id,state,removed from vm_instance where name like
"helloLess%";
+----+-------------+---------+----------+---------+
| id | name | host_id | state | removed |
+----+-------------+---------+----------+---------+
| 26 | helloLess-3 | 6 | Starting | NULL |
| 27 | helloLess-6 | 3 | Starting | NULL |
| 28 | helloLess-1 | 1 | Starting | NULL |
| 29 | helloLess-5 | NULL | Error | NULL |
| 30 | helloLess-2 | NULL | Error | NULL |
| 31 | helloLess-7 | NULL | Error | NULL |
| 32 | helloLess-4 | NULL | Error | NULL |
+----+-------------+---------+----------+---------+
7 rows in set (0.00 sec)
mysql> select id,name,host_id,state,removed from vm_instance where name like
"helloLess%";
+----+-------------+---------+-----------+---------------------+
| id | name | host_id | state | removed |
+----+-------------+---------+-----------+---------------------+
| 26 | helloLess-3 | 6 | Running | NULL |
| 27 | helloLess-6 | 3 | Running | NULL |
| 28 | helloLess-1 | 1 | Starting | NULL |
| 29 | helloLess-5 | NULL | Expunging | 2013-08-09 23:51:02 |
| 30 | helloLess-2 | NULL | Expunging | 2013-08-09 23:51:02 |
| 31 | helloLess-7 | NULL | Expunging | 2013-08-09 23:51:02 |
| 32 | helloLess-4 | NULL | Expunging | 2013-08-09 23:51:02 |
+----+-------------+---------+-----------+---------------------+
7 rows in set (0.00 sec)
Closing the bug as verified based on the above Observations made in the two
scenarios.
> Anti-Affinity -When Vm deployment is done in parallel , anti-affinity rule is
> not honored.
> ------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2155
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2155
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Environment: build from master
> Reporter: Sangeetha Hariharan
> Assignee: Prachi Damle
> Priority: Blocker
> Labels: integration-test
> Fix For: 4.2.0
>
> Attachments: management-server.rar
>
>
> Anti-Affinity - When Vm deployment is done in parallel , anti-affinity rule
> is not honored.
> Steps to reproduce the problem:
> Setup:
> Advanced zone with 6 hosts.
> Create a new anti-affnity rule.
> Deploy 5 Vms in this anti-affnity rule.
> We see that some of the vms that belong to the same anti-affinity rules are
> getting deployed on the same host.
> select * from affinity_group_vm_map;
> | 60 | 22 | 63 |
> | 61 | 22 | 65 |
> | 62 | 22 | 64 |
> | 63 | 22 | 66 |
> | 64 | 22 | 67 |
> | 65 | 22 | 68 |
> +----+-------------------+-------------+
> 30 rows in set (0.00 sec)
> mysql> select host_id,id,state from vm_instance where id > 60;
> +---------+----+-----------+
> | host_id | id | state |
> +---------+----+-----------+
> | NULL | 61 | Expunging |
> | 6 | 62 | Running |
> | 9 | 63 | Running |
> | 8 | 64 | Running |
> | 8 | 65 | Running |
> | 8 | 66 | Running |
> | 7 | 67 | Running |
> | 7 | 68 | Running |
> +---------+----+-----------+
> 8 rows in set (0.00 sec)
> Will attach management-server log.
--
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
