If you use any external LB device, we cannot configure the cidr. -----Original Message----- From: Francois Gaudreault [mailto:fgaudrea...@cloudops.com] Sent: Thursday, May 28, 2015 4:56 AM To: dev@cloudstack.apache.org Subject: Re: External LB integration
I dont think its configurable, maybe have a look in global settings? We are using netscalers but in a VPC model. So we dont have to deal with networkguru at all :) FG On May 27, 2015 5:57 PM, "Erik Weber" <terbol...@gmail.com> wrote: > Thank you Francois, > > Do you know if the subnets it considers are customizable somehow? > As far as I could see it chose something completely random, which > might not be a good thing. > > -- > Erik > > > On Wed, May 27, 2015 at 11:17 PM, Francois Gaudreault < > fgaudrea...@cloudops.com> wrote: > > > Erik, > > > > Thats correct. Its called NetworkGuru. This is to avoid overlapping > subnets > > on a shared netscaler. Pretty sure if you use a dedicated one, youll > > have more flexibility. > > > > FG > > On May 27, 2015 4:30 PM, "Erik Weber" <terbol...@gmail.com> wrote: > > > > > Doing some tests with Netscaler at the moment (input welcome!), > > > and discovered that if you have a network offering with external > > > LB, you're > > not > > > allowed to specify the CIDR later when you add a network. > > > > > > Instead it seems to randomly pick a range, from I don't know > > > where, and > > use > > > that. > > > > > > Does anyone know where this behaviour comes from? Why does > > > CloudStack > > think > > > it is better at specifying a proper CIDR than me? Where is it > > > getting > > it's > > > range from? > > > > > > The saga continues > > > > > > -- > > > Erik > > > > > >
