Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-users@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of sowmya.krishnan@citrix.com
 designates 203.166.19.134 as permitted sender)
From: Sowmya Krishnan <sowmya.krishnan@citrix.com>
To: "cloudstack-users@incubator.apache.org"
	<cloudstack-users@incubator.apache.org>
Date: Thu, 14 Feb 2013 19:52:14 +0530
Subject: RE: DHCP IP range in the isolated network
Thread-Topic: DHCP IP range in the isolated network
Thread-Index: Ac4KtCnN3WkNSd6eQAW0ZVOPwMBPbAACmaVA
Message-ID: 
 <97F4356AEA71904482CD192135C038F9011CC1390D33@BANPMAILBOX01.citrite.net>
References: <da2cde0683579bb365953f0de5389916@mail.gmail.com>
In-Reply-To: <da2cde0683579bb365953f0de5389916@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Option of specifying custom dhcp range is available while creating a new gu=
est network - You can specify custom guest gateway and network during netwo=
rk creation that would override the default zone level CIDR. But this is no=
t allowed if you choose a network offering that uses external devices (like=
 Netscaler for example). The CIDR is generated by CloudStack in that case.

For existing network, I think updateNetwork API does provide an option to c=
hange cidr. But if you already have running VMs in the network, I am not ve=
ry sure of the behavior in that case.

-----Original Message-----
From: Fabrice Brazier [mailto:fabrice.brazier@apalia.net]=20
Sent: Thursday, February 14, 2013 6:41 PM
To: cloudstack-users@incubator.apache.org
Subject: DHCP IP range in the isolated network

Hi Folks,


By default the guest CIDR for the advanced zone is 10.1.1.0/24 and the dhcp=
 ip range is on the entire subnet.

Does it possible to modify the default dhcp ip range in this isolated netwo=
rk ?


Thanks,

Fabrice