al settings, we can migrate them to use ConfigKey so
> they get created during upgrade/db-migration.
>
>
> Regards.
>
>
> From: Pierre-Luc Dion
> Sent: 02 September 2016 21:28:02
> To: dev@cloudstack.apache.org
> Subject: Re: upgrade
lation. 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
Sent: 02 September 2016 21:28:02
To: dev@cloudstack.apache.org
Subject: Re: upgrade div
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
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 a
