On Fri, Sep 26, 2014 at 12:54 AM, James Page <james.p...@ubuntu.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 24/09/14 12:09, Andrew Wilkins wrote: > > > > Anyway, normally I think you'd want the primary charm's > > (swift-proxy's) relevant relation-changed hook to do the restart > > itself when the middleware changes (ie. when middleware-changed is > > triggered). This just makes sure that the responsibility and > > knowledge of restarts stays within the charm responsible for the > > service. > > > > > > That makes sense. I was coming from the angle of how to do this > > without touching any existing charms, which is wrong. > > > > I think to do this right I'd need to modify the swift-proxy and > > swift-storage charms, and have them modify their configuration > > files rather than having the subordinate do it. The subordinate > > would effectively just provide configuration parameters and install > > the middleware dependencies. I'll hack around for now, and maybe > > I'll propose something later if anything becomes of my charm. > > That sounds like the best approach - we did something similar for > cinder backends - see the cinder and cinder-ceph or cinder-vmware charms. > Perfect, just what I was after. Thanks James.
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju