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 1C6F518AB8 for ; Thu, 10 Dec 2015 09:35:10 +0000 (UTC) Received: (qmail 34308 invoked by uid 500); 10 Dec 2015 09:35:09 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 34254 invoked by uid 500); 10 Dec 2015 09:35:09 -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 34239 invoked by uid 99); 10 Dec 2015 09:35:09 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Dec 2015 09:35:09 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 1B1ABE0AC0; Thu, 10 Dec 2015 09:35:09 +0000 (UTC) From: nitin-maharana To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: CLOUDSTACK-8847: ListServiceOfferings is ... Content-Type: text/plain Message-Id: <20151210093509.1B1ABE0AC0@git1-us-west.apache.org> Date: Thu, 10 Dec 2015 09:35:09 +0000 (UTC) Github user nitin-maharana commented on the pull request: https://github.com/apache/cloudstack/pull/823#issuecomment-163550095 @DaanHoogland : No, it needn't not be an exact match but the new one should be a superset of the current one. According to your scenario, as the new one supports (x,y) as well as supports an extra tag (z). The interpretation will be more clear if we think of this in terms of venn diagram. The migration will fail in running mode. Dynamic scaling cannot be done. It will only be done on reboot. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---