Rohit,
Its usually shell scripts that wrap around cloudmonkey. I hit this issue
when i have to run parallel tasks using multiple envs.
One other somewhat ugly work around is to make config file immurable
with chattr command, but then - it prints errors as its unable to write
to config file. Not p
In my case, we have scripts running by Puppet, and crond hourly, and by Nagios
(once every 5 min, I think), all by root user or sudo to root user (in case of
Nagios). In most of our scripts, we call “set display default” first. Only
occasionally , admins would login and manually run cloudmonke
Correction from previous reply:
"I'll see what I can do, in general you should NOT be replacing or changing the
cloudmonkey config file outside of cloudmonkey itself."
Regards,
Rohit Yadav
rohit.ya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapebl
Whenever a set command is called, it would save/update the config file. When
you run set profile xyz; it needs to make that profile the default profile and
update other parameters associated with the profile which may be set as well
(such as url, username, password, apikey, secretkey etc). When
I've seen the similar behaviour.
For some reason cloudmonkey try to persist the configs each time your
run something.
If i open cloudmonkey in multiple terminals and use different profiles
and execute commands in mutliple terminals in parallel - i've seen
cloudmonkey mess up the config for one of
Hi,
We have a few scripts that use cloudmonkey to talk to CloudStack server. The
scripts are invoked by Puppet once per hour.
However, every once a while, the /root/.cloudmonkey/config file would be over
written with default settings. That is, blank apikey/secretkey, default
password, default
