| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
to recall.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
non-ssl xmlrpclib.ServerProxy
aka, enabled ssl support
|
|/
|
|
|
|
|
|
| |
return codes assume
the server specification is NOT a glob and return a single value instead of a hash. This minimizes
code when needing to address only one system at a time. The command line will always assume globs are
possible and will not use this shortcut.
|
|
|
|
| |
to some clever magic with getattr. You have one client object that can address multiples and returns a hash with the results for each machine. Second, results are hashes, not lists, and we are a bit more clever in returning a return code the CLI .. the highest int wins if there's an int, for instance. Still, return codes are relatively meaningless for multi-control ... the true power is in scripting things.
|
|
|
|
|
| |
certmaster/funcd to generate certs, you will now need them in order to use the
client for testing.
|
|
that want to script against func. Placeholders are there for globbing
of multiple certs, and places are also marked where we need to add
SSL.
|