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 2016/09/01 17:34:35 UTC
upgrade divergence vs/ new install
Hi,
I've observed on few system we've upgrade over the last months that they
don't have the same amount of global settings has opose to a fresh install
of cloudstack.
I have 3 scenarios
4.4.x to 4.7.x (484)
4.4.x to 4.7.x to 4.9.0 (494)
4.2.1 to 4.6.0 to 4.7.0 to 4.9.0 (499)
4.7.x (398)
in all case they have missing settings and don't have the same number of
settings in the configuration table, counts inside ().
for the case of 4.7.x vs 4.4.x to 4.7.x I found that missing settings are
located in the file:
server/src/com/cloud/configuration/Config.java
So, does anyone have the same issue, if you search for "publish" in Global
settings you would have nothing ?
And, How those this Config.java is call, look like it called at the first
boot lf cloudstack or something like that.
Thanks,
Re: upgrade divergence vs/ new install
Posted by Pierre-Luc Dion <pd...@cloudops.com>.
I'll investigate further but setting init to false dynamite my db at the
first try :-S.
I'll continue next week but might be a dangerous path so far :-S
On Fri, Sep 2, 2016 at 2:03 PM, Rohit Yadav <ro...@shapeblue.com>
wrote:
> Hi PL,
>
>
> That's correct, all new global settings should use the ConfigKey class to
> setup new global settings. Any changes that may be done recently (4.6+)
> that added new global settings directly in Config.java won't get added to
> the configuration table unless it's a fresh installation. Can you gather
> the list of such global settings, we can migrate them to use ConfigKey so
> they get created during upgrade/db-migration.
>
>
> Regards.
>
> ________________________________
> From: Pierre-Luc Dion <pd...@cloudops.com>
> Sent: 02 September 2016 21:28:02
> To: dev@cloudstack.apache.org
> Subject: Re: upgrade divergence vs/ new install
>
> Look like anything in Config.java is not applied when upgrading CloudStack,
> so if that file change, we need to update the configuration name="init".
> This is the case for anyone upgrading prior 4.6.
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-9489
>
> I'm not sure how we should proceed with this but basically any upgraded
> CloudStack have 15 missing Global Settings.
> It's easy to replicate event with jetty.
>
>
>
>
>
> rohit.yadav@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
> On Thu, Sep 1, 2016 at 1:34 PM, Pierre-Luc Dion <pd...@cloudops.com>
> wrote:
>
> > Hi,
> >
> > I've observed on few system we've upgrade over the last months that they
> > don't have the same amount of global settings has opose to a fresh
> install
> > of cloudstack.
> >
> > I have 3 scenarios
> >
> > 4.4.x to 4.7.x (484)
> > 4.4.x to 4.7.x to 4.9.0 (494)
> > 4.2.1 to 4.6.0 to 4.7.0 to 4.9.0 (499)
> > 4.7.x (398)
> >
> > in all case they have missing settings and don't have the same number of
> > settings in the configuration table, counts inside ().
> >
> >
> > for the case of 4.7.x vs 4.4.x to 4.7.x I found that missing settings
> are
> > located in the file:
> > server/src/com/cloud/configuration/Config.java
> >
> > So, does anyone have the same issue, if you search for "publish" in
> Global
> > settings you would have nothing ?
> >
> > And, How those this Config.java is call, look like it called at the first
> > boot lf cloudstack or something like that.
> >
> >
> > Thanks,
> >
>
Re: upgrade divergence vs/ new install
Posted by Rohit Yadav <ro...@shapeblue.com>.
Hi PL,
That's correct, all new global settings should use the ConfigKey class to setup new global settings. Any changes that may be done recently (4.6+) that added new global settings directly in Config.java won't get added to the configuration table unless it's a fresh installation. Can you gather the list of such global settings, we can migrate them to use ConfigKey so they get created during upgrade/db-migration.
Regards.
________________________________
From: Pierre-Luc Dion <pd...@cloudops.com>
Sent: 02 September 2016 21:28:02
To: dev@cloudstack.apache.org
Subject: Re: upgrade divergence vs/ new install
Look like anything in Config.java is not applied when upgrading CloudStack,
so if that file change, we need to update the configuration name="init".
This is the case for anyone upgrading prior 4.6.
https://issues.apache.org/jira/browse/CLOUDSTACK-9489
I'm not sure how we should proceed with this but basically any upgraded
CloudStack have 15 missing Global Settings.
It's easy to replicate event with jetty.
rohit.yadav@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
On Thu, Sep 1, 2016 at 1:34 PM, Pierre-Luc Dion <pd...@cloudops.com> wrote:
> Hi,
>
> I've observed on few system we've upgrade over the last months that they
> don't have the same amount of global settings has opose to a fresh install
> of cloudstack.
>
> I have 3 scenarios
>
> 4.4.x to 4.7.x (484)
> 4.4.x to 4.7.x to 4.9.0 (494)
> 4.2.1 to 4.6.0 to 4.7.0 to 4.9.0 (499)
> 4.7.x (398)
>
> in all case they have missing settings and don't have the same number of
> settings in the configuration table, counts inside ().
>
>
> for the case of 4.7.x vs 4.4.x to 4.7.x I found that missing settings are
> located in the file:
> server/src/com/cloud/configuration/Config.java
>
> So, does anyone have the same issue, if you search for "publish" in Global
> settings you would have nothing ?
>
> And, How those this Config.java is call, look like it called at the first
> boot lf cloudstack or something like that.
>
>
> Thanks,
>
Re: upgrade divergence vs/ new install
Posted by Pierre-Luc Dion <pd...@cloudops.com>.
Look like anything in Config.java is not applied when upgrading CloudStack,
so if that file change, we need to update the configuration name="init".
This is the case for anyone upgrading prior 4.6.
https://issues.apache.org/jira/browse/CLOUDSTACK-9489
I'm not sure how we should proceed with this but basically any upgraded
CloudStack have 15 missing Global Settings.
It's easy to replicate event with jetty.
On Thu, Sep 1, 2016 at 1:34 PM, Pierre-Luc Dion <pd...@cloudops.com> wrote:
> Hi,
>
> I've observed on few system we've upgrade over the last months that they
> don't have the same amount of global settings has opose to a fresh install
> of cloudstack.
>
> I have 3 scenarios
>
> 4.4.x to 4.7.x (484)
> 4.4.x to 4.7.x to 4.9.0 (494)
> 4.2.1 to 4.6.0 to 4.7.0 to 4.9.0 (499)
> 4.7.x (398)
>
> in all case they have missing settings and don't have the same number of
> settings in the configuration table, counts inside ().
>
>
> for the case of 4.7.x vs 4.4.x to 4.7.x I found that missing settings are
> located in the file:
> server/src/com/cloud/configuration/Config.java
>
> So, does anyone have the same issue, if you search for "publish" in Global
> settings you would have nothing ?
>
> And, How those this Config.java is call, look like it called at the first
> boot lf cloudstack or something like that.
>
>
> Thanks,
>