Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 409FFCD6A for ; Tue, 16 Jul 2013 18:24:58 +0000 (UTC) Received: (qmail 40755 invoked by uid 500); 16 Jul 2013 18:24:48 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 40705 invoked by uid 500); 16 Jul 2013 18:24:48 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 40698 invoked by uid 500); 16 Jul 2013 18:24:48 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 40694 invoked by uid 99); 16 Jul 2013 18:24:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jul 2013 18:24:48 +0000 Date: Tue, 16 Jul 2013 18:24:48 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-2155) Anti-Affinity -When Vm deployment is done in parallel , anti-affinity rule is not honored. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710043#comment-13710043 ] ASF subversion and git services commented on CLOUDSTACK-2155: ------------------------------------------------------------- Commit fa9ca72f360959d84ea61b341c83bf0a1cd0ae6e in branch refs/heads/master from [~prachidamle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fa9ca72 ] CLOUDSTACK-2155: Anti-Affinity -When Vm deployment is done in parallel , anti-affinity rule is not honored. Changes: - Locking the group and save reservation mechanism done by DPM - Added admin operation to cleanup VM reservations - DPM will also cleanup VM reservations on startup > 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