You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by John Kinsella <jl...@stratosec.co> on 2014/03/05 09:22:07 UTC

The global settings beast...

One thing that’s been gnawing on me - we keep shoving more and more stuff into the global settings shortcut instead of creating a proper settings UI. Then some new user comes along all shiny-eyed at the awesomeness of ACS, but wonders why something isn’t working, only to be told that combination of a) it’s in the docs and b) you have to scroll down through 30 items in global settings, then change something, then restart mgmt, then re-login…then it’ll work.

I know the UI is supposed to be a proof of concept, but I’m thinking we need to shed that label and empty out some closeted skeletons such as this.

Am I the only one this bothers, or should we maybe set it as a goal for 4.5 (maybe this is on a feature list and I’ve missed it…)?

John

Re: The global settings beast...

Posted by Mike Tutkowski <mi...@solidfire.com>.
Thanks for the info, Alex.


On Wed, Mar 5, 2014 at 11:14 PM, Alex Huang <Al...@citrix.com> wrote:

> I don't think we will be able to get that until all configs are converted
> to using the ConfigKey.  Today, a lot of components just stores the
> parameter value as a member variable so changes can't be reflected without
> a reboot.  Switching to ConfigKey will force all of those to change.
>
> --Alex
>
> > -----Original Message-----
> > From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> > Sent: Wednesday, March 5, 2014 7:46 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: The global settings beast...
> >
> > Hi Alex,
> >
> > I typically update system.vm.use.local.storage to true before I create
> my first
> > zone in a fresh environment. The GUI tells me I need to reboot the CS
> > Management Server, but I've noticed I don't really have to.
> >
> > Is there a list somewhere that specifies which parameters really require
> a
> > reboot of the CS MS and which ones don't? Also, I wonder if the GUI just
> > says this for all Global Settings that are changed because it has no
> knowledge
> > of which ones really require a reboot. Does that sound correct?
> >
> > Thanks
> >
> >
> > On Wed, Mar 5, 2014 at 6:18 PM, Alex Huang <Al...@citrix.com>
> > wrote:
> >
> > > I added something to address this last year.
> > >
> > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Configuration
> > >
> > > It addresses several problems.
> > >
> > > - Parameter values are not stored in member variables so it's possible
> > > for changed values to take effect without reboot.
> > > - Breaks up the enum so that plugins can have their own config
> > > parameters without changing the Config.java in CloudStack.
> > > - If the default value for a parameter changes, this change
> > > automatically updates a default value field and a timestamp so the
> > > admin can evaluate whether they want to change their current value for
> > the parameter.
> > > - Deleted parameters from the code are marked with an update time
> > > that's null so the admin knows the parameter have been removed after an
> > upgrade.
> > >
> > > There are several todos left.  They are documented in
> > > ConfigDepotImpl.java.  For the important ones, I filed bugs.  If you
> > > have some time, please help work on them.
> > >
> > > - CLOUDSTACK-6206: No UI to reflect these changes.
> > > - CLOUDSTACk-6207: Remove Config.java and move all enums to the new
> > > ConfigKey parameter.
> > > - CLOUDSTACK-6208: Create a per management server properties file that
> > > contains parameters that pertains to each management server node,
> > > instead of globally.
> > >
> > > --Alex
> > >
> > > > -----Original Message-----
> > > > From: Rajesh Battala [mailto:rajesh.battala@citrix.com]
> > > > Sent: Wednesday, March 5, 2014 3:22 AM
> > > > To: dev@cloudstack.apache.org
> > > > Subject: RE: The global settings beast...
> > > >
> > > > The need to restart is, the Managers  have configured with the
> > > > values in Global Settings and running.
> > > >
> > > > -----Original Message-----
> > > > From: Rajani Karuturi [mailto:Rajani.Karuturi@citrix.com]
> > > > Sent: Wednesday, March 5, 2014 3:13 PM
> > > > To: dev@cloudstack.apache.org
> > > > Subject: Re: The global settings beast...
> > > >
> > > > The need to restart the management server for any global
> > > > configuration change is a problem.
> > > > I spent at least a few hours trying to debug an issue only to
> > > > realise
> > > that its not
> > > > an issue but, I have to restart the management server.
> > > >
> > > >
> > > > ~Rajani
> > > >
> > > >
> > > >
> > > > On 05-Mar-2014, at 3:01 pm, Donal Lafferty
> > > > <do...@citrix.com>
> > > > wrote:
> > > >
> > > > > In fairness, the biggest problem is having to reboot.
> > > > >
> > > > > WRT to b), there is a search option that avoids the need to scroll.
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: John Kinsella [mailto:jlk@stratosec.co]
> > > > >> Sent: 05 March 2014 08:22
> > > > >> To: <de...@cloudstack.apache.org>
> > > > >> Subject: The global settings beast...
> > > > >>
> > > > >> One thing that's been gnawing on me - we keep shoving more and
> > > > >> more stuff into the global settings shortcut instead of creating
> > > > >> a proper
> > > settings
> > > > UI.
> > > > >> Then some new user comes along all shiny-eyed at the awesomeness
> > > > >> of ACS, but wonders why something isn't working, only to be told
> > > > >> that combination of a) it's in the docs and b) you have to scroll
> > > > >> down through 30 items in global settings, then change something,
> > > > >> then restart mgmt, then re- login...then it'll work.
> > > > >>
> > > > >> I know the UI is supposed to be a proof of concept, but I'm
> > > > >> thinking we need to shed that label and empty out some closeted
> > > > >> skeletons such
> > > > as this.
> > > > >>
> > > > >> Am I the only one this bothers, or should we maybe set it as a
> > > > >> goal for 4.5 (maybe this is on a feature list and I've missed
> it...)?
> > > > >>
> > > > >> John
> > >
> > >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkowski@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud<http://solidfire.com/solution/overview/?video=play>
> > *(tm)*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*

RE: The global settings beast...

Posted by Alex Huang <Al...@citrix.com>.
I don't think we will be able to get that until all configs are converted to using the ConfigKey.  Today, a lot of components just stores the parameter value as a member variable so changes can't be reflected without a reboot.  Switching to ConfigKey will force all of those to change. 

--Alex

> -----Original Message-----
> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> Sent: Wednesday, March 5, 2014 7:46 PM
> To: dev@cloudstack.apache.org
> Subject: Re: The global settings beast...
> 
> Hi Alex,
> 
> I typically update system.vm.use.local.storage to true before I create my first
> zone in a fresh environment. The GUI tells me I need to reboot the CS
> Management Server, but I've noticed I don't really have to.
> 
> Is there a list somewhere that specifies which parameters really require a
> reboot of the CS MS and which ones don't? Also, I wonder if the GUI just
> says this for all Global Settings that are changed because it has no knowledge
> of which ones really require a reboot. Does that sound correct?
> 
> Thanks
> 
> 
> On Wed, Mar 5, 2014 at 6:18 PM, Alex Huang <Al...@citrix.com>
> wrote:
> 
> > I added something to address this last year.
> >
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Configuration
> >
> > It addresses several problems.
> >
> > - Parameter values are not stored in member variables so it's possible
> > for changed values to take effect without reboot.
> > - Breaks up the enum so that plugins can have their own config
> > parameters without changing the Config.java in CloudStack.
> > - If the default value for a parameter changes, this change
> > automatically updates a default value field and a timestamp so the
> > admin can evaluate whether they want to change their current value for
> the parameter.
> > - Deleted parameters from the code are marked with an update time
> > that's null so the admin knows the parameter have been removed after an
> upgrade.
> >
> > There are several todos left.  They are documented in
> > ConfigDepotImpl.java.  For the important ones, I filed bugs.  If you
> > have some time, please help work on them.
> >
> > - CLOUDSTACK-6206: No UI to reflect these changes.
> > - CLOUDSTACk-6207: Remove Config.java and move all enums to the new
> > ConfigKey parameter.
> > - CLOUDSTACK-6208: Create a per management server properties file that
> > contains parameters that pertains to each management server node,
> > instead of globally.
> >
> > --Alex
> >
> > > -----Original Message-----
> > > From: Rajesh Battala [mailto:rajesh.battala@citrix.com]
> > > Sent: Wednesday, March 5, 2014 3:22 AM
> > > To: dev@cloudstack.apache.org
> > > Subject: RE: The global settings beast...
> > >
> > > The need to restart is, the Managers  have configured with the
> > > values in Global Settings and running.
> > >
> > > -----Original Message-----
> > > From: Rajani Karuturi [mailto:Rajani.Karuturi@citrix.com]
> > > Sent: Wednesday, March 5, 2014 3:13 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: The global settings beast...
> > >
> > > The need to restart the management server for any global
> > > configuration change is a problem.
> > > I spent at least a few hours trying to debug an issue only to
> > > realise
> > that its not
> > > an issue but, I have to restart the management server.
> > >
> > >
> > > ~Rajani
> > >
> > >
> > >
> > > On 05-Mar-2014, at 3:01 pm, Donal Lafferty
> > > <do...@citrix.com>
> > > wrote:
> > >
> > > > In fairness, the biggest problem is having to reboot.
> > > >
> > > > WRT to b), there is a search option that avoids the need to scroll.
> > > >
> > > >> -----Original Message-----
> > > >> From: John Kinsella [mailto:jlk@stratosec.co]
> > > >> Sent: 05 March 2014 08:22
> > > >> To: <de...@cloudstack.apache.org>
> > > >> Subject: The global settings beast...
> > > >>
> > > >> One thing that's been gnawing on me - we keep shoving more and
> > > >> more stuff into the global settings shortcut instead of creating
> > > >> a proper
> > settings
> > > UI.
> > > >> Then some new user comes along all shiny-eyed at the awesomeness
> > > >> of ACS, but wonders why something isn't working, only to be told
> > > >> that combination of a) it's in the docs and b) you have to scroll
> > > >> down through 30 items in global settings, then change something,
> > > >> then restart mgmt, then re- login...then it'll work.
> > > >>
> > > >> I know the UI is supposed to be a proof of concept, but I'm
> > > >> thinking we need to shed that label and empty out some closeted
> > > >> skeletons such
> > > as this.
> > > >>
> > > >> Am I the only one this bothers, or should we maybe set it as a
> > > >> goal for 4.5 (maybe this is on a feature list and I've missed it...)?
> > > >>
> > > >> John
> >
> >
> 
> 
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*

Re: The global settings beast...

Posted by Mike Tutkowski <mi...@solidfire.com>.
Ah, interesting - thanks!


On Thu, Mar 6, 2014 at 12:08 AM, Harikrishna Patnala <
harikrishna.patnala@citrix.com> wrote:

> Hi Mike,
>
> As Alex quoted we need to make all the parameters to use ConfigKey.
> Now if you want to check which parameters require reboot or not, there is
> a column 'is_dynamic' in Configuration table.
> If the value is 1 then no need to restart MS for those parameters.
>
> -Harikrishna
>
> On 06-Mar-2014, at 9:16 am, Mike Tutkowski <mi...@solidfire.com>
> wrote:
>
> > Hi Alex,
> >
> > I typically update system.vm.use.local.storage to true before I create my
> > first zone in a fresh environment. The GUI tells me I need to reboot the
> CS
> > Management Server, but I've noticed I don't really have to.
> >
> > Is there a list somewhere that specifies which parameters really require
> a
> > reboot of the CS MS and which ones don't? Also, I wonder if the GUI just
> > says this for all Global Settings that are changed because it has no
> > knowledge of which ones really require a reboot. Does that sound correct?
> >
> > Thanks
> >
> >
> > On Wed, Mar 5, 2014 at 6:18 PM, Alex Huang <Al...@citrix.com>
> wrote:
> >
> >> I added something to address this last year.
> >>
> >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Configuration
> >>
> >> It addresses several problems.
> >>
> >> - Parameter values are not stored in member variables so it's possible
> for
> >> changed values to take effect without reboot.
> >> - Breaks up the enum so that plugins can have their own config
> parameters
> >> without changing the Config.java in CloudStack.
> >> - If the default value for a parameter changes, this change
> automatically
> >> updates a default value field and a timestamp so the admin can evaluate
> >> whether they want to change their current value for the parameter.
> >> - Deleted parameters from the code are marked with an update time that's
> >> null so the admin knows the parameter have been removed after an
> upgrade.
> >>
> >> There are several todos left.  They are documented in
> >> ConfigDepotImpl.java.  For the important ones, I filed bugs.  If you
> have
> >> some time, please help work on them.
> >>
> >> - CLOUDSTACK-6206: No UI to reflect these changes.
> >> - CLOUDSTACk-6207: Remove Config.java and move all enums to the new
> >> ConfigKey parameter.
> >> - CLOUDSTACK-6208: Create a per management server properties file that
> >> contains parameters that pertains to each management server node,
> instead
> >> of globally.
> >>
> >> --Alex
> >>
> >>> -----Original Message-----
> >>> From: Rajesh Battala [mailto:rajesh.battala@citrix.com]
> >>> Sent: Wednesday, March 5, 2014 3:22 AM
> >>> To: dev@cloudstack.apache.org
> >>> Subject: RE: The global settings beast...
> >>>
> >>> The need to restart is, the Managers  have configured with the values
> in
> >>> Global Settings and running.
> >>>
> >>> -----Original Message-----
> >>> From: Rajani Karuturi [mailto:Rajani.Karuturi@citrix.com]
> >>> Sent: Wednesday, March 5, 2014 3:13 PM
> >>> To: dev@cloudstack.apache.org
> >>> Subject: Re: The global settings beast...
> >>>
> >>> The need to restart the management server for any global configuration
> >>> change is a problem.
> >>> I spent at least a few hours trying to debug an issue only to realise
> >> that its not
> >>> an issue but, I have to restart the management server.
> >>>
> >>>
> >>> ~Rajani
> >>>
> >>>
> >>>
> >>> On 05-Mar-2014, at 3:01 pm, Donal Lafferty <do...@citrix.com>
> >>> wrote:
> >>>
> >>>> In fairness, the biggest problem is having to reboot.
> >>>>
> >>>> WRT to b), there is a search option that avoids the need to scroll.
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: John Kinsella [mailto:jlk@stratosec.co]
> >>>>> Sent: 05 March 2014 08:22
> >>>>> To: <de...@cloudstack.apache.org>
> >>>>> Subject: The global settings beast...
> >>>>>
> >>>>> One thing that's been gnawing on me - we keep shoving more and more
> >>>>> stuff into the global settings shortcut instead of creating a proper
> >> settings
> >>> UI.
> >>>>> Then some new user comes along all shiny-eyed at the awesomeness of
> >>>>> ACS, but wonders why something isn't working, only to be told that
> >>>>> combination of a) it's in the docs and b) you have to scroll down
> >>>>> through 30 items in global settings, then change something, then
> >>>>> restart mgmt, then re- login...then it'll work.
> >>>>>
> >>>>> I know the UI is supposed to be a proof of concept, but I'm thinking
> >>>>> we need to shed that label and empty out some closeted skeletons such
> >>> as this.
> >>>>>
> >>>>> Am I the only one this bothers, or should we maybe set it as a goal
> >>>>> for 4.5 (maybe this is on a feature list and I've missed it...)?
> >>>>>
> >>>>> John
> >>
> >>
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkowski@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud<http://solidfire.com/solution/overview/?video=play>
> > *(tm)*
>
>


-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*

Re: The global settings beast...

Posted by Harikrishna Patnala <ha...@citrix.com>.
Hi Mike,

As Alex quoted we need to make all the parameters to use ConfigKey.
Now if you want to check which parameters require reboot or not, there is a column 'is_dynamic' in Configuration table. 
If the value is 1 then no need to restart MS for those parameters.

-Harikrishna
 
On 06-Mar-2014, at 9:16 am, Mike Tutkowski <mi...@solidfire.com> wrote:

> Hi Alex,
> 
> I typically update system.vm.use.local.storage to true before I create my
> first zone in a fresh environment. The GUI tells me I need to reboot the CS
> Management Server, but I've noticed I don't really have to.
> 
> Is there a list somewhere that specifies which parameters really require a
> reboot of the CS MS and which ones don't? Also, I wonder if the GUI just
> says this for all Global Settings that are changed because it has no
> knowledge of which ones really require a reboot. Does that sound correct?
> 
> Thanks
> 
> 
> On Wed, Mar 5, 2014 at 6:18 PM, Alex Huang <Al...@citrix.com> wrote:
> 
>> I added something to address this last year.
>> 
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Configuration
>> 
>> It addresses several problems.
>> 
>> - Parameter values are not stored in member variables so it's possible for
>> changed values to take effect without reboot.
>> - Breaks up the enum so that plugins can have their own config parameters
>> without changing the Config.java in CloudStack.
>> - If the default value for a parameter changes, this change automatically
>> updates a default value field and a timestamp so the admin can evaluate
>> whether they want to change their current value for the parameter.
>> - Deleted parameters from the code are marked with an update time that's
>> null so the admin knows the parameter have been removed after an upgrade.
>> 
>> There are several todos left.  They are documented in
>> ConfigDepotImpl.java.  For the important ones, I filed bugs.  If you have
>> some time, please help work on them.
>> 
>> - CLOUDSTACK-6206: No UI to reflect these changes.
>> - CLOUDSTACk-6207: Remove Config.java and move all enums to the new
>> ConfigKey parameter.
>> - CLOUDSTACK-6208: Create a per management server properties file that
>> contains parameters that pertains to each management server node, instead
>> of globally.
>> 
>> --Alex
>> 
>>> -----Original Message-----
>>> From: Rajesh Battala [mailto:rajesh.battala@citrix.com]
>>> Sent: Wednesday, March 5, 2014 3:22 AM
>>> To: dev@cloudstack.apache.org
>>> Subject: RE: The global settings beast...
>>> 
>>> The need to restart is, the Managers  have configured with the values in
>>> Global Settings and running.
>>> 
>>> -----Original Message-----
>>> From: Rajani Karuturi [mailto:Rajani.Karuturi@citrix.com]
>>> Sent: Wednesday, March 5, 2014 3:13 PM
>>> To: dev@cloudstack.apache.org
>>> Subject: Re: The global settings beast...
>>> 
>>> The need to restart the management server for any global configuration
>>> change is a problem.
>>> I spent at least a few hours trying to debug an issue only to realise
>> that its not
>>> an issue but, I have to restart the management server.
>>> 
>>> 
>>> ~Rajani
>>> 
>>> 
>>> 
>>> On 05-Mar-2014, at 3:01 pm, Donal Lafferty <do...@citrix.com>
>>> wrote:
>>> 
>>>> In fairness, the biggest problem is having to reboot.
>>>> 
>>>> WRT to b), there is a search option that avoids the need to scroll.
>>>> 
>>>>> -----Original Message-----
>>>>> From: John Kinsella [mailto:jlk@stratosec.co]
>>>>> Sent: 05 March 2014 08:22
>>>>> To: <de...@cloudstack.apache.org>
>>>>> Subject: The global settings beast...
>>>>> 
>>>>> One thing that's been gnawing on me - we keep shoving more and more
>>>>> stuff into the global settings shortcut instead of creating a proper
>> settings
>>> UI.
>>>>> Then some new user comes along all shiny-eyed at the awesomeness of
>>>>> ACS, but wonders why something isn't working, only to be told that
>>>>> combination of a) it's in the docs and b) you have to scroll down
>>>>> through 30 items in global settings, then change something, then
>>>>> restart mgmt, then re- login...then it'll work.
>>>>> 
>>>>> I know the UI is supposed to be a proof of concept, but I'm thinking
>>>>> we need to shed that label and empty out some closeted skeletons such
>>> as this.
>>>>> 
>>>>> Am I the only one this bothers, or should we maybe set it as a goal
>>>>> for 4.5 (maybe this is on a feature list and I've missed it...)?
>>>>> 
>>>>> John
>> 
>> 
> 
> 
> -- 
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*


Re: The global settings beast...

Posted by Mike Tutkowski <mi...@solidfire.com>.
Hi Alex,

I typically update system.vm.use.local.storage to true before I create my
first zone in a fresh environment. The GUI tells me I need to reboot the CS
Management Server, but I've noticed I don't really have to.

Is there a list somewhere that specifies which parameters really require a
reboot of the CS MS and which ones don't? Also, I wonder if the GUI just
says this for all Global Settings that are changed because it has no
knowledge of which ones really require a reboot. Does that sound correct?

Thanks


On Wed, Mar 5, 2014 at 6:18 PM, Alex Huang <Al...@citrix.com> wrote:

> I added something to address this last year.
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Configuration
>
> It addresses several problems.
>
> - Parameter values are not stored in member variables so it's possible for
> changed values to take effect without reboot.
> - Breaks up the enum so that plugins can have their own config parameters
> without changing the Config.java in CloudStack.
> - If the default value for a parameter changes, this change automatically
> updates a default value field and a timestamp so the admin can evaluate
> whether they want to change their current value for the parameter.
> - Deleted parameters from the code are marked with an update time that's
> null so the admin knows the parameter have been removed after an upgrade.
>
> There are several todos left.  They are documented in
> ConfigDepotImpl.java.  For the important ones, I filed bugs.  If you have
> some time, please help work on them.
>
> - CLOUDSTACK-6206: No UI to reflect these changes.
> - CLOUDSTACk-6207: Remove Config.java and move all enums to the new
> ConfigKey parameter.
> - CLOUDSTACK-6208: Create a per management server properties file that
> contains parameters that pertains to each management server node, instead
> of globally.
>
> --Alex
>
> > -----Original Message-----
> > From: Rajesh Battala [mailto:rajesh.battala@citrix.com]
> > Sent: Wednesday, March 5, 2014 3:22 AM
> > To: dev@cloudstack.apache.org
> > Subject: RE: The global settings beast...
> >
> > The need to restart is, the Managers  have configured with the values in
> > Global Settings and running.
> >
> > -----Original Message-----
> > From: Rajani Karuturi [mailto:Rajani.Karuturi@citrix.com]
> > Sent: Wednesday, March 5, 2014 3:13 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: The global settings beast...
> >
> > The need to restart the management server for any global configuration
> > change is a problem.
> > I spent at least a few hours trying to debug an issue only to realise
> that its not
> > an issue but, I have to restart the management server.
> >
> >
> > ~Rajani
> >
> >
> >
> > On 05-Mar-2014, at 3:01 pm, Donal Lafferty <do...@citrix.com>
> > wrote:
> >
> > > In fairness, the biggest problem is having to reboot.
> > >
> > > WRT to b), there is a search option that avoids the need to scroll.
> > >
> > >> -----Original Message-----
> > >> From: John Kinsella [mailto:jlk@stratosec.co]
> > >> Sent: 05 March 2014 08:22
> > >> To: <de...@cloudstack.apache.org>
> > >> Subject: The global settings beast...
> > >>
> > >> One thing that's been gnawing on me - we keep shoving more and more
> > >> stuff into the global settings shortcut instead of creating a proper
> settings
> > UI.
> > >> Then some new user comes along all shiny-eyed at the awesomeness of
> > >> ACS, but wonders why something isn't working, only to be told that
> > >> combination of a) it's in the docs and b) you have to scroll down
> > >> through 30 items in global settings, then change something, then
> > >> restart mgmt, then re- login...then it'll work.
> > >>
> > >> I know the UI is supposed to be a proof of concept, but I'm thinking
> > >> we need to shed that label and empty out some closeted skeletons such
> > as this.
> > >>
> > >> Am I the only one this bothers, or should we maybe set it as a goal
> > >> for 4.5 (maybe this is on a feature list and I've missed it...)?
> > >>
> > >> John
>
>


-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*

RE: The global settings beast...

Posted by Alex Huang <Al...@citrix.com>.
I added something to address this last year.  

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Configuration

It addresses several problems.

- Parameter values are not stored in member variables so it's possible for changed values to take effect without reboot.
- Breaks up the enum so that plugins can have their own config parameters without changing the Config.java in CloudStack.
- If the default value for a parameter changes, this change automatically updates a default value field and a timestamp so the admin can evaluate whether they want to change their current value for the parameter. 
- Deleted parameters from the code are marked with an update time that's null so the admin knows the parameter have been removed after an upgrade.

There are several todos left.  They are documented in ConfigDepotImpl.java.  For the important ones, I filed bugs.  If you have some time, please help work on them.

- CLOUDSTACK-6206: No UI to reflect these changes.
- CLOUDSTACk-6207: Remove Config.java and move all enums to the new ConfigKey parameter.
- CLOUDSTACK-6208: Create a per management server properties file that contains parameters that pertains to each management server node, instead of globally.

--Alex

> -----Original Message-----
> From: Rajesh Battala [mailto:rajesh.battala@citrix.com]
> Sent: Wednesday, March 5, 2014 3:22 AM
> To: dev@cloudstack.apache.org
> Subject: RE: The global settings beast...
> 
> The need to restart is, the Managers  have configured with the values in
> Global Settings and running.
> 
> -----Original Message-----
> From: Rajani Karuturi [mailto:Rajani.Karuturi@citrix.com]
> Sent: Wednesday, March 5, 2014 3:13 PM
> To: dev@cloudstack.apache.org
> Subject: Re: The global settings beast...
> 
> The need to restart the management server for any global configuration
> change is a problem.
> I spent at least a few hours trying to debug an issue only to realise that its not
> an issue but, I have to restart the management server.
> 
> 
> ~Rajani
> 
> 
> 
> On 05-Mar-2014, at 3:01 pm, Donal Lafferty <do...@citrix.com>
> wrote:
> 
> > In fairness, the biggest problem is having to reboot.
> >
> > WRT to b), there is a search option that avoids the need to scroll.
> >
> >> -----Original Message-----
> >> From: John Kinsella [mailto:jlk@stratosec.co]
> >> Sent: 05 March 2014 08:22
> >> To: <de...@cloudstack.apache.org>
> >> Subject: The global settings beast...
> >>
> >> One thing that's been gnawing on me - we keep shoving more and more
> >> stuff into the global settings shortcut instead of creating a proper settings
> UI.
> >> Then some new user comes along all shiny-eyed at the awesomeness of
> >> ACS, but wonders why something isn't working, only to be told that
> >> combination of a) it's in the docs and b) you have to scroll down
> >> through 30 items in global settings, then change something, then
> >> restart mgmt, then re- login...then it'll work.
> >>
> >> I know the UI is supposed to be a proof of concept, but I'm thinking
> >> we need to shed that label and empty out some closeted skeletons such
> as this.
> >>
> >> Am I the only one this bothers, or should we maybe set it as a goal
> >> for 4.5 (maybe this is on a feature list and I've missed it...)?
> >>
> >> John


RE: The global settings beast...

Posted by Rajesh Battala <ra...@citrix.com>.
The need to restart is, the Managers  have configured with the values in Global Settings and running.

-----Original Message-----
From: Rajani Karuturi [mailto:Rajani.Karuturi@citrix.com] 
Sent: Wednesday, March 5, 2014 3:13 PM
To: dev@cloudstack.apache.org
Subject: Re: The global settings beast...

The need to restart the management server for any global configuration change is a problem.
I spent at least a few hours trying to debug an issue only to realise that its not an issue but, I have to restart the management server. 


~Rajani



On 05-Mar-2014, at 3:01 pm, Donal Lafferty <do...@citrix.com> wrote:

> In fairness, the biggest problem is having to reboot.
> 
> WRT to b), there is a search option that avoids the need to scroll.
> 
>> -----Original Message-----
>> From: John Kinsella [mailto:jlk@stratosec.co]
>> Sent: 05 March 2014 08:22
>> To: <de...@cloudstack.apache.org>
>> Subject: The global settings beast...
>> 
>> One thing that's been gnawing on me - we keep shoving more and more 
>> stuff into the global settings shortcut instead of creating a proper settings UI.
>> Then some new user comes along all shiny-eyed at the awesomeness of 
>> ACS, but wonders why something isn't working, only to be told that 
>> combination of a) it's in the docs and b) you have to scroll down 
>> through 30 items in global settings, then change something, then 
>> restart mgmt, then re- login...then it'll work.
>> 
>> I know the UI is supposed to be a proof of concept, but I'm thinking 
>> we need to shed that label and empty out some closeted skeletons such as this.
>> 
>> Am I the only one this bothers, or should we maybe set it as a goal 
>> for 4.5 (maybe this is on a feature list and I've missed it...)?
>> 
>> John


Re: The global settings beast...

Posted by Rajani Karuturi <Ra...@citrix.com>.
The need to restart the management server for any global configuration change is a problem.
I spent at least a few hours trying to debug an issue only to realise that its not an issue but, I have to restart the management server. 


~Rajani



On 05-Mar-2014, at 3:01 pm, Donal Lafferty <do...@citrix.com> wrote:

> In fairness, the biggest problem is having to reboot.
> 
> WRT to b), there is a search option that avoids the need to scroll.
> 
>> -----Original Message-----
>> From: John Kinsella [mailto:jlk@stratosec.co]
>> Sent: 05 March 2014 08:22
>> To: <de...@cloudstack.apache.org>
>> Subject: The global settings beast...
>> 
>> One thing that's been gnawing on me - we keep shoving more and more
>> stuff into the global settings shortcut instead of creating a proper settings UI.
>> Then some new user comes along all shiny-eyed at the awesomeness of
>> ACS, but wonders why something isn't working, only to be told that
>> combination of a) it's in the docs and b) you have to scroll down through 30
>> items in global settings, then change something, then restart mgmt, then re-
>> login...then it'll work.
>> 
>> I know the UI is supposed to be a proof of concept, but I'm thinking we need
>> to shed that label and empty out some closeted skeletons such as this.
>> 
>> Am I the only one this bothers, or should we maybe set it as a goal for 4.5
>> (maybe this is on a feature list and I've missed it...)?
>> 
>> John


RE: The global settings beast...

Posted by Donal Lafferty <do...@citrix.com>.
In fairness, the biggest problem is having to reboot.

WRT to b), there is a search option that avoids the need to scroll.

> -----Original Message-----
> From: John Kinsella [mailto:jlk@stratosec.co]
> Sent: 05 March 2014 08:22
> To: <de...@cloudstack.apache.org>
> Subject: The global settings beast...
> 
> One thing that's been gnawing on me - we keep shoving more and more
> stuff into the global settings shortcut instead of creating a proper settings UI.
> Then some new user comes along all shiny-eyed at the awesomeness of
> ACS, but wonders why something isn't working, only to be told that
> combination of a) it's in the docs and b) you have to scroll down through 30
> items in global settings, then change something, then restart mgmt, then re-
> login...then it'll work.
> 
> I know the UI is supposed to be a proof of concept, but I'm thinking we need
> to shed that label and empty out some closeted skeletons such as this.
> 
> Am I the only one this bothers, or should we maybe set it as a goal for 4.5
> (maybe this is on a feature list and I've missed it...)?
> 
> John