You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Pierre-Luc Dion <pd...@cloudops.com> on 2014/07/17 18:41:50 UTC
changing cpu.overprovisioning.factor
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_
Re: changing cpu.overprovisioning.factor
Posted by Pierre-Luc Dion <pd...@cloudops.com>.
https://issues.apache.org/jira/browse/CLOUDSTACK-7120
updated.
*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 2:35 PM, Harikrishna Patnala <
harikrishna.patnala@citrix.com> wrote:
> Please create a doc bug only for two parameters cpu and memory
> overprovisioning factors.
>
> Because for the remaining parameters till the value is defined at granular
> level, CS uses the value at global level.
>
> So in your case if it would have some parameter other than cpu and memory
> over provisioning factors, then changing the value at global level should
> affect at cluster level also.
>
>
> Thanks,
> Harikrishna
>
>
> On 17-Jul-2014, at 10:38 pm, Pierre-Luc Dion <pd...@cloudops.com> wrote:
>
> > good idea, doing it now ...
> >
> >
> > *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:57 PM, Nitin Mehta <Ni...@citrix.com>
> > wrote:
> >
> >> Thanks for confirming. Could you please create a bug at JIRA for adding
> >> this into documentation ?
> >>
> >> -Nitin
> >>
> >> On 17/07/14 9:53 AM, "Pierre-Luc Dion" <pd...@cloudops.com> wrote:
> >>
> >>> 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 <Ni...@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_
> >>>>
> >>>>
> >>
> >>
>
>
Re: changing cpu.overprovisioning.factor
Posted by Harikrishna Patnala <ha...@citrix.com>.
Please create a doc bug only for two parameters cpu and memory overprovisioning factors.
Because for the remaining parameters till the value is defined at granular level, CS uses the value at global level.
So in your case if it would have some parameter other than cpu and memory over provisioning factors, then changing the value at global level should affect at cluster level also.
Thanks,
Harikrishna
On 17-Jul-2014, at 10:38 pm, Pierre-Luc Dion <pd...@cloudops.com> wrote:
> good idea, doing it now ...
>
>
> *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:57 PM, Nitin Mehta <Ni...@citrix.com>
> wrote:
>
>> Thanks for confirming. Could you please create a bug at JIRA for adding
>> this into documentation ?
>>
>> -Nitin
>>
>> On 17/07/14 9:53 AM, "Pierre-Luc Dion" <pd...@cloudops.com> wrote:
>>
>>> 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 <Ni...@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_
>>>>
>>>>
>>
>>
Re: changing cpu.overprovisioning.factor
Posted by Pierre-Luc Dion <pd...@cloudops.com>.
good idea, doing it now ...
*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:57 PM, Nitin Mehta <Ni...@citrix.com>
wrote:
> Thanks for confirming. Could you please create a bug at JIRA for adding
> this into documentation ?
>
> -Nitin
>
> On 17/07/14 9:53 AM, "Pierre-Luc Dion" <pd...@cloudops.com> wrote:
>
> >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 <Ni...@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_
> >>
> >>
>
>
Re: changing cpu.overprovisioning.factor
Posted by Nitin Mehta <Ni...@citrix.com>.
Thanks for confirming. Could you please create a bug at JIRA for adding
this into documentation ?
-Nitin
On 17/07/14 9:53 AM, "Pierre-Luc Dion" <pd...@cloudops.com> wrote:
>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 <Ni...@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_
>>
>>
Re: changing cpu.overprovisioning.factor
Posted by Pierre-Luc Dion <pd...@cloudops.com>.
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 <Ni...@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_
>
>
Re: changing cpu.overprovisioning.factor
Posted by Nitin Mehta <Ni...@citrix.com>.
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_