Hi Seth After lots of looking around on the wiki, and many google searches, I still only find information on the delegation feature. In this model, ultimately, there is a single overlord over everything, no matter how many sub-overlords you deploy. - For highly available environments, one should have the ability to have more than one overlord for each minion - Minions support ACL's about what modules an overlord can execute, surely this too should be extended to include multiple overlords ? ie.: overlord1 can execute module a, b and c, overlord2 can execute module c, d and e. Jacques On Mon, 2009-04-20 at 09:01 -0400, Seth Vidal wrote: > > On Mon, 20 Apr 2009, Botha, Jacques (FNB) wrote: > > > Hi Berthe > > > > Thanks for the info, and I read your last post. Interesting > > architecture with lots of possibilities, unfortunately it still has a > > single point of failure, the master overlord above the sub-overlords, > > which is exactly what we are trying to avoid. If the overlord dies, we > > lose control of all the minions, the only way around this would be a > > second overlord to which all of the minions are subscribed. > > > > If anyone has some pointers, please share ! :) > > > > Lookup Minion2Minion in the func trac wiki. > > -sv To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to firstrandbankdisclaimer@xxxxxxxxx and we will send you a copy of the Disclaimer.
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Func-list mailing list Func-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/func-list
