Using VLSM at the zone creation the admin can create multiple subnets from a parent subnet, but that is not what we are targeting at. CloudStack admin should not be interested to create a subnet for Non CloudStack hosts IMHO. This particular requirement is to only have a definite subnet for CloudStack Guest VMs and all other IPs in the parent subnet can be assigned to non CloudStack purposes.
Thanks, Saksham ________________________________________ From: Kelcey Damage (BT) [kel...@backbonetechnology.com] Sent: Friday, January 04, 2013 11:56 PM To: cloudstack-dev@incubator.apache.org Subject: RE: [DISCUSS] IP Address Reservation within a network So I see this and now wonder why do we even specify the guest CIDR at zone creation? Why not just use VLSM at network creation? Or some other instance in time controlled by the client/admin provisioning process. Thanks -kd >-----Original Message----- >From: Saksham Srivastava [mailto:saksham.srivast...@citrix.com] >Sent: Friday, January 04, 2013 9:41 AM >To: cloudstack-dev@incubator.apache.org >Cc: Manan Shah; Chiradeep Vittal >Subject: RE: [DISCUSS] IP Address Reservation within a network > >The admin can specify the CIDR to be used for guest VMs (Guest CIDR) during >advanced zone creation. > >This CIDR is used by default for the Guest Networks. > >The proposed plan is to have a new parameter say "CS-GuestVM CIDR" which >will be a subset of the Guest CIDR. >For instance at the time of zone creation the Guest CIDR is 10.1.1.0/24 And the >"CS-GuestVM CIDR" is specified as 10.1.1.0/26 So the remaining IPs can now >be used for Non Cloudstack VMs/Physical servers. >The plan is to now use only 10.1.1.0/26 as the CIDR for Cloudstack Guest Vms. > >Currently when the user wants to create a new Guest network , he specifies >the gateway and subnet mask. >The proposal is that he will have additional options to specify the start range >and end range for guest vms. The remaining IPs can then be used for Non >Cloudstack vms. > >Also the ranges will be frozen once the network is created. > >Thanks, >Saksham > >-----Original Message----- >From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] >Sent: Thursday, January 03, 2013 12:59 PM >To: CloudStack DeveloperList >Cc: Manan Shah >Subject: Re: [DISCUSS] IP Address Reservation within a network > >The proposed workflow seems counter-intuitive to me from an end-user >perspective. >How about: reserve a range of *usable* ip addresses. Then the admin is free >to use the remainder of the range. >Questions: >1. Is it one range or multiple? >2. Are there update semantics, or are the ranges frozen once the network is >created? > > >On 12/31/12 2:11 AM, "Saksham Srivastava" <saksham.srivast...@citrix.com> >wrote: > >>Hi all, >> >>I have started looking into this feature and would like to have the >>community feedback/suggestions on it. >> >>I would be sharing the FS shortly. >> >>Thanks, >>Saksham >> >> >> >>On Saturday 22 December 2012 06:51 AM, Manan Shah wrote: >>> Hi, >>> >>> >>> I would like to propose a new feature for IP Reservation within a >>>network. >>> I have created a JIRA ticket and provided the requirements at the >>>following location. Please provide feedback on the requirements. >>> JIRA Ticket: https://issues.apache.org/jira/browse/CLOUDSTACK-705 >>> Requirements: >>> >>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/IP+Range+Res >erv >>>ati >>>on >>> +within+a+Network >>> >>> >>> Regards, >>> Manan Shah >>> >>>
