Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 97825110C6 for ; Tue, 15 Apr 2014 23:18:48 +0000 (UTC) Received: (qmail 35175 invoked by uid 500); 15 Apr 2014 23:18:47 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 35107 invoked by uid 500); 15 Apr 2014 23:18:47 -0000 Mailing-List: contact dev-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 dev@cloudstack.apache.org Received: (qmail 35099 invoked by uid 99); 15 Apr 2014 23:18:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Apr 2014 23:18:47 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mike.tutkowski@solidfire.com designates 209.85.219.43 as permitted sender) Received: from [209.85.219.43] (HELO mail-oa0-f43.google.com) (209.85.219.43) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Apr 2014 23:18:43 +0000 Received: by mail-oa0-f43.google.com with SMTP id eb12so11604034oac.2 for ; Tue, 15 Apr 2014 16:18:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=Ax+MySPZXXYqdZxZ0aWH2LPJ7BKene8dwlbA7nsgCAw=; b=LzIRh3Aolct0qBZ6bgP/GylnYm9vizxtdpewE3TApUIA4RqEOJAKQ+nI4RnM3valgG vJ6kR87KO15Jv3kxnmsNMI/gmsS/f21jxK82GTAAiZDw4XFwcN3Zhs+03WI9SXhMXaR2 XuTOOD1NeuaExKbYxhDGL+wQ/Fsb/NvW6TlJUw+glzGzKIOywm4/R1WE5Dl0HT22ajha /oyGCN8IeSWRdkjdTIRi98rKZlNmG8MZvsgb4Nh7m4IWV0g/+qHdnW7UmnE18Zt4ukha oZoW7y49enNd4YBFRX2mTYuKwNikfwhnr5fH78db8V0PZxn45OqL68tTXngWhyoP01xV W/9g== X-Gm-Message-State: ALoCoQnVK48ZYGWHbfMkPQLWszHtvB32/Q64dZpFTUxP/OwmPZLj+7pXh1+KspNoCeM/Er3RG8Eh MIME-Version: 1.0 X-Received: by 10.60.229.228 with SMTP id st4mr3822272oec.16.1397603900000; Tue, 15 Apr 2014 16:18:20 -0700 (PDT) Received: by 10.182.114.164 with HTTP; Tue, 15 Apr 2014 16:18:19 -0700 (PDT) Date: Tue, 15 Apr 2014 17:18:19 -0600 Message-ID: Subject: [ACS4.4, XenServer] Adding a XenServer host to a cluster From: Mike Tutkowski To: "dev@cloudstack.apache.org" Content-Type: multipart/alternative; boundary=001a11362fb0ff1bad04f71d038c X-Virus-Checked: Checked by ClamAV on apache.org --001a11362fb0ff1bad04f71d038c Content-Type: text/plain; charset=ISO-8859-1 Hi, Prior to 4.4, if I built a CS cluster with one XenServer host (that was not in a XenServer resource pool) and then later wanted to add another XenServer host to the CS cluster, CS would put both hosts in a XenServer resource pool automatically and then show them both in the CS cluster. In 4.4, this process fails. What I need to do now is manually create the XenServer resource pool and put my hosts in it, then ask CS to add the second host to the CS cluster. Is this expected behavior for 4.4? Thanks! -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkowski@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud *(tm)* --001a11362fb0ff1bad04f71d038c--