ply-To: "dev@cloudstack.apache.org"
> Date: Tuesday, 8 November 2016 at 10:49 PM
> To: "dev@cloudstack.apache.org"
> Subject: Re: Adding a Config value to Cloudstack
>
> Yes init is destructive. Unfortunately it was the only option that I had.
> Since it was a
Please share the code/PR if possible.
From: Syed Ahmed
Reply-To: "dev@cloudstack.apache.org"
Date: Tuesday, 8 November 2016 at 10:49 PM
To: "dev@cloudstack.apache.org"
Subject: Re: Adding a Config value to Cloudstack
Yes init is destructive. Unfortunately it was the on
Yes init is destructive. Unfortunately it was the only option that I had.
Since it was a Dev env it was mostly fine.
On Tue, Nov 8, 2016 at 10:37 AM Linas Žilinskas wrote:
> Be careful with setting the init to false. It does lot more than just
> adding new configs. I've found out that the hard wa
Be careful with setting the init to false. It does lot more than just
adding new configs. I've found out that the hard way.
At least on our multiple deployments, the default networks were
recreated and user_ip_address table had duplicated ips in them, which i
had to remove manually. Not sure i
You pretty much have to insert it manually. You need to either make a
database migration for it, or just run a query for insert. We've run into
similar problems on our own fork, and our solution was to ensure all config
values get created on startup. This is the code we used to do it:
https://githu
Yes, I've done exactly what you've shown here Nicolas, make the class
implement Configurable, add the getConfigKeys and created the Param.
However when I reinstall Cloudstack, the startup does not seem to pick up
the newly added config.
As a workaround, I had to reset the "init" value as "false" i
Hi Syed,
You can do it using ConfigKey class
(org.apache.cloudstack.framework.config.ConfigKey)
like this:
- Define your new configuration as a variable in a class that implements
Configurable (org.apache.cloudstack.framework.config.Configurable) using
ConfigKey constructor in which you
