On Thu, 2008-10-09 at 15:50 +0200, Marco Mornati wrote: > On Thu, 2008-10-09 at 09:40 -0400, seth vidal wrote: > > On Mon, 2008-10-06 at 17:39 -0400, Michael DeHaan wrote: > > > Michael DeHaan wrote: > > > > It would be nice to have a way to issue offline orders to minions so > > > > they could check in when they come online (via XMLRPC) and then see if > > > > they have any orders. > > > > > > > > This is the other mode of communication we would like to support in > > > > order to enable Func to replace OSAD in Spacewalk. > > > > > > > > For example, "this node should yum update the next time I see it" is > > > > different from "this node should update now if it's online". > > > > > > > > Anyone have any thoughts on implementations? > > > > > > > > --Michael > > > > > > > > _______________________________________________ > > > > Func-list mailing list > > > > Func-list@xxxxxxxxxx > > > > https://www.redhat.com/mailman/listinfo/func-list > > > > > > To elaborate, basically with what we have here and also the new cobbler > > > "config file templating" feature, we have the makings of a much easier > > > to understand config management tool, all in Python, and all very easy > > > to understand. This could be the beginings of "RRS" (remote rocket > > > surgery) built on Cobbler+Func. (See also recent Cobbler integration). > > > > > > We just need a way to address offline nodes, basically. > > > > > > > Offline commands are fine if you don't expect some sort of response from > > the command, right? > > > > We'd need something more or less like this: > > > > for each host > > if ping host > > do command > > else > > store command and retry > > > > the retry trick only works well if we have another daemon running that > > stores the commands and the responses, I think, I guess we could do it > > with a regularly scheduled cron job to look for unrun jobs but.... > No I think the better implementation should be: > > for each host > if ping host > do command > else > store command > > And nothing more on "server side" > > When my minion will be "online" it will send to overlord/certmaster a > "return online message" > and then, on my server I've something like > > search for hostname queued_command > for each command > do command > > So I don't need another daemon/thread running that pool all offline This only works if you only have a single overlord. With minion-to-minion communication you want to store it on the side that is trying to send it to you. Think of it like smtp. If the receiving system is down the message waits and queues on the sending system's SMTP server. -sv _______________________________________________ Func-list mailing list Func-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/func-list
