> On April 18, 2013, 5:18 p.m., Sateesh Chodapuneedi wrote: > >
Since we are not creating subnets for guest CIDR, there is no need for a separate broadcast IP. The guest Broadcast will be same as the Network Broadcast. Currently this is the behaviour : CIDR 10.1.1.0/26 Network CIDR 10.1.1.0/24 Reserved Range : 10.1.1.63-10.1.1.254 CIDR 10.1.1.224/27 Network CIDR 10.1.1.0/24 Reserved Range : 10.1.1.1-10.1.1.224 CIDR 10.1.1.32/27 Network CIDR 10.1.1.0/24 Reserved Range : 10.1.1.1-10.1.1.32 , 10.1.1.63-10.1.1.254 Since broadcast is an assignable IP so it should be a part of Reserved range. Closing the request. - Saksham ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/10078/#review19395 ----------------------------------------------------------- On March 22, 2013, 10:04 a.m., Saksham Srivastava wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/10078/ > ----------------------------------------------------------- > > (Updated March 22, 2013, 10:04 a.m.) > > > Review request for cloudstack, Murali Reddy and Sateesh Chodapuneedi. > > > Description > ------- > > While reserving IPs, broadcast IPs of guestvmcidr is also getting reserved. > > > Diffs > ----- > > server/src/com/cloud/api/ApiResponseHelper.java 663139d > > Diff: https://reviews.apache.org/r/10078/diff/ > > > Testing > ------- > > CIDR : 10.1.1.0/26 (10.1.1.1-10.1.1.62, Broadcast: 10.1.1.63) > Network CIDR: 10.1.1.0/24 (10.1.1.1-10.1.1.254, Broadcast: 10.1.1.255) > Reserved Range: 10.1.1.64-10.1.1.254 > > > Thanks, > > Saksham Srivastava > >
