Return-Path: X-Original-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 386BDCE4F for ; Tue, 5 Jun 2012 01:16:12 +0000 (UTC) Received: (qmail 723 invoked by uid 500); 5 Jun 2012 01:16:12 -0000 Delivered-To: apmail-incubator-cloudstack-users-archive@incubator.apache.org Received: (qmail 699 invoked by uid 500); 5 Jun 2012 01:16:12 -0000 Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-users@incubator.apache.org Delivered-To: mailing list cloudstack-users@incubator.apache.org Received: (qmail 691 invoked by uid 99); 5 Jun 2012 01:16:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jun 2012 01:16:12 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Evan.Miller@citrix.com designates 66.165.176.89 as permitted sender) Received: from [66.165.176.89] (HELO SMTP.CITRIX.COM) (66.165.176.89) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jun 2012 01:16:07 +0000 X-IronPort-AV: E=Sophos;i="4.75,716,1330923600"; d="scan'208";a="26835470" Received: from sjcpmailmx02.citrite.net ([10.216.14.75]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Jun 2012 21:15:33 -0400 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.72]) by SJCPMAILMX02.citrite.net ([10.216.14.75]) with mapi; Mon, 4 Jun 2012 18:15:32 -0700 From: Evan Miller To: "cloudstack-users@incubator.apache.org" Date: Mon, 4 Jun 2012 18:15:28 -0700 Subject: RE: What are the steps for effectively shrinking a pod's management ip range? Thread-Topic: What are the steps for effectively shrinking a pod's management ip range? Thread-Index: Ac1Coplq2LgwDeCSSNCBzNV8FfHgCgAFaBSg Message-ID: <93099572B72EB341B81A644E134F240B011CF7695754@SJCPMAILBOX01.citrite.net> References: <93099572B72EB341B81A644E134F240B011CF76956D9@SJCPMAILBOX01.citrite.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org -----Original Message----- From: Alena Prokharchyk [mailto:Alena.Prokharchyk@citrix.com]=20 Sent: Monday, June 04, 2012 3:38 PM To: cloudstack-users@incubator.apache.org Subject: Re: What are the steps for effectively shrinking a pod's managemen= t ip range? On 6/4/12 3:28 PM, "Evan Miller" wrote: >Running CloudStack Management Server v3.0.1 on Centos 6.2. >=20 >Running XenServer v6.0.2. >=20 >There is a single zone, single pod, single > >cluster and (currently) single (XenServer) host. >=20 >I'd like to remove two ip addresses from the current management ip=20 >range for the pod. Then, I'd like to add those two ip addresses to the=20 >new, second pod. >=20 >A set of private and management ip addresses > >currently exists in the existing pod. >=20 >I tried a few thing, but it appears that the fact that I defined a set=20 >of private ips for the pod is preventing me from deleting the pod. >Note: Deleting hosts is no problem. >=20 >I am working in a non-production environment trying to determine=20 >peculiar and particular limits to CloudStack v3.0.1. >=20 >Regards, > =20 >Evan Miller > =20 >Citrix Systems. Inc. >Desktop and Cloud Engineering Infrastructure >4988 Great America Parkway >Santa Clara, CA 95054 >(V) and (F) 408-790-8489 >(C) 925-209-1428 >(Email) =20 >Evan.Miller@citrix.com > >=20 > Management ip addresses are not used by hosts; they are used by the system = vms (SSVM and Console proxy vms). The vms have to be stopped in order to re= lease these Ips. Here are the steps: 1) check which vms are using those ips: select instance_id from nics where id in (select nic_id from op_dc_ip_addre= ss_alloc where taken is not null); 2) put your xen hosts into maintenance mode - this has to be done to ensure= the system won't find a spot to restart SSVM and CPVM > Is the CPVM =3D v-2-VM?=20 > Evan 3) stop SSVM and CPVM having ids that we got on step 1) 4) If private (management) ip addresses you want to remove, are located in = the beginning or at the end of the pod range, you can shrink the Pod range = by editing the pod. If they are not, you have to remove the pod and reconfi= gure it again. -Alena.