Nitin, This is the behaviour I've observe and make sense too. Updating cluster config does work.
I think our documentation need to reflect that behaviour maybe in the admin guide... Thanks ! *Pierre-Luc DION* Architecte de Solution Cloud | Cloud Solutions Architect t 855.652.5683 *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Thu, Jul 17, 2014 at 12:50 PM, Nitin Mehta <nitin.me...@citrix.com> wrote: > Did you change the global config or the cluster config ? > Global config is inherited when a new cluster is created but once the > cluster is created you need to modify it at the cluster for it take > affect. See if that helps. > > Thanks, > -Nitin > > On 17/07/14 9:41 AM, "Pierre-Luc Dion" <pd...@cloudops.com> wrote: > > >I've tried to change the cpu.overprovisioning.factor in Cloudstack 4.3 > >using Global Settings, even after restarting cloudstack-managment server > > GHz available remain the same in the zone. > > > >Turns out that changing the value in the cluster did update value > >automatically without restarts. > > > >Is this a wanted behaviour ? > > > >Thanks, > > > >*Pierre-Luc DION* > >Architecte de Solution Cloud | Cloud Solutions Architect > >t 855.652.5683 > > > >*CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts > >420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 > >w cloudops.com *|* tw @CloudOps_ > >
