Hi Chiradeep, I think you are asking about the changes I am going to make to assign IPs considering the multiple subnets associated to a network. (Earlier i thought you were asking if i provide a way to choose a subnet for allocation.)
So this is how i plan to handle the IP allocation. if user has specified the IP. 1.) If the user specifies the IP, check the cidr to which it belongs if it dose not belong to any existing cidr throw an error. 2.) check if the IP requested is available, exit if not available. 3.) assign the IP. If the user dose not specify any IP. 1.) Allocate form the first subnet which has free IPs. Also we do not allow addition of a subnet which is superset of the existing subnet. Bharat. On Mar 13, 2013, at 11:24 AM, Chiradeep Vittal <chiradeep.vit...@citrix.com> wrote: > > > On 3/11/13 5:13 AM, "Bharat Kumar" <bharat.ku...@citrix.com> wrote: > >> Hi Chiradeep, >> >>> >>> I'm guessing there is some change in the logic for assigning a guest or >>> management ip address (in order to select from the new subnet / range) >> >> In case if the admin wants to specify the ip that will be allotted to a >> guest vm he can mention it as a part of DeployVm API. >> currently we don't have any way to do this for management ip addresses. I >> don't know the use case in which this will be required. > > I refer you to acquireIp4Address in GuestNetworkGuru (method > acquireIp4Address) and PodBasedNetworkGuru (method reserve) where > undoubtedly there are assumptions that are going to be violated by your > changes. >
