Right, How to you make sure that juju doesn't override my changes? If I had to add another mon node (and remove one of the existing ones) the new config would be overwritten by the default one.
I think the general issue is that I can't tell when particular config files will be re-generated. kind regards Pshem On Wed, 25 Nov 2015 at 21:58 Peter Sabaini <peter.saba...@canonical.com> wrote: > On 24.11.15 23:25, Pshem Kowalczyk wrote: > > Hi, > > > > I'm relatively new to the juju ecosystem. I've built a test/POC > > openstack setup using juju charms. Ceph is used as the backend-storage > > system for the deployment. Since the production deployment of this > > system has to meet some external requirements (particular CRUSH > > settings, recovery times etc) I'll have to tune ceph settings a bit. > > > > The charm itself doesn't seem to have a section to add that information > > (some other charms do have that ability). What's the best way of doing > it? > > > > In general case, I've realised that sometimes it would be useful to > > have ability to run some actions after juju has finished its > > configuration to fine-tune it to particular requirements (without > > losing the advantages of using juju for all the dependencies). Is it > > possible to do something like that without building my own charms? > > We're generally just using "juju ssh", "juju run" and occasionally > "juju scp" > > Caveat: juju ssh doesn't really handle stdin > > cheers, > peter. > > > kind regards > > Pshem > > > > > > > > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju