|
Hey guys, I’m looking into creating a strictly client-side
library for controlling func modules that is cross platform (read: windows).
Basically I want to be able to run the func command line tool on a windows box
and nothing else (no windows minions). 1.
I’m reading over the wiki and the source, and am
running into a few sticking points which I don’t understand. First off, the
minions and the overlord communicate using SSL. What sort of authentication
exists between a client and the overlord? Is there any sort of access-control
or encryption with this communication? The Overlord object relies on jobthing and forkbomb, both of
which require unix-only modules (dbm, fnctl, os.fork). 2.
To handle nforks/async calls, I’m thinking about
writing a module that accomplishes the same but uses regular python threads for
windows programs to use. Any reason this wouldn’t work, or things I
should look out for? 3.
Rather than using the UNIX-only dbm module and locking
provided by fnctl.flock, I’ll find some other cross-platform solution.
Seems like the strategy here is for all of the child threads to write into a
shared file, each exclusively locking it in turn, until all of them finish and sys.exit(0).
The parent then reads the shared file to return all of the results. (Please
correct me if this analysis is incorrect!) This can be done using other
methods, perhaps even using traditional python thread locks. Thanks for whatever feedback you may have. --Rob |
_______________________________________________ Func-list mailing list Func-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/func-list
