From: "Jonathan D. Proulx" <jon@csail.mit.edu>
To: Tommi Virtanen <tv@inktank.com>
Cc: "Sage Weil" <sage@inktank.com>,
loic.dachary@enovance.com, puppet-openstack@puppetlabs.com,
"Teyo Tyree" <teyo@puppetlabs.com>,
"François Charlier" <francois.charlier@enovance.com>,
puppet-users@googlgroups.com, ceph-devel@vger.kernel.org
Subject: Re: Puppet modules for Ceph
Date: Tue, 7 Aug 2012 09:51:44 -0400 [thread overview]
Message-ID: <20120807135144.GA10072@csail.mit.edu> (raw)
In-Reply-To: <CADvuQREVc0gqheYSo89m7cpsdCg02EFkxFJ5LvcMrVLwBMsO7Q@mail.gmail.com>
On Tue, Jul 31, 2012 at 12:09:13PM -0700, Tommi Virtanen wrote:
:Juju seems to provide a real-time notification mechanism between
:peers, using it's <name>-relation-changed hook. Other CM frameworks
:may need to step up their game, or be subject to the "keep re-running
:chef-client until it works" limitation.
Have you lloked at "puppet kick"
puppet-kick(8) -- Remotely control puppet agent
========
SYNOPSIS
--------
Trigger a puppet agent run on a set of hosts.
I'm not using it in my environment and it does require some specific
puppet config on the agent side to make it work so less than ideal,
but might atleast provide a path.
-Jon
next prev parent reply other threads:[~2012-08-07 14:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20120718-152758-+019.59-1@marduk.tchpc.tcd.ie>
2012-07-18 13:58 ` Puppet modules for Ceph François Charlier
2012-07-18 14:41 ` Mark Nelson
2012-08-10 16:21 ` François Charlier
2012-07-18 17:09 ` Tommi Virtanen
[not found] ` <CAKsDvb0Eq0amkEq=+9RrKcBv4RJ0PFwUGpzDpV8CzBHLQpMHtg@mail.gmail.com>
2012-07-18 22:21 ` Tommi Virtanen
[not found] ` <CAKsDvb2d63hDTq0LvmGL0z+yr09cNSr3ythWiqg6WVmzjxy8BA@mail.gmail.com>
2012-07-18 22:31 ` Tommi Virtanen
[not found] ` <5391f2cc-e01f-4cf4-b6cb-b4479bd15df0@puppetlabs.com>
2012-07-31 18:48 ` Tommi Virtanen
2012-07-31 18:51 ` Sage Weil
2012-07-31 19:09 ` Tommi Virtanen
2012-08-07 13:51 ` Jonathan D. Proulx [this message]
2012-08-09 17:04 ` Tommi Virtanen
2012-07-26 15:57 ` Jimmy Tang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120807135144.GA10072@csail.mit.edu \
--to=jon@csail.mit.edu \
--cc=ceph-devel@vger.kernel.org \
--cc=francois.charlier@enovance.com \
--cc=loic.dachary@enovance.com \
--cc=puppet-openstack@puppetlabs.com \
--cc=puppet-users@googlgroups.com \
--cc=sage@inktank.com \
--cc=teyo@puppetlabs.com \
--cc=tv@inktank.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.