puppet-choria
puppet-choria copied to clipboard
choria-io
Module to install and manage Choria
This is a building block that might be used when/if we want to add Bolt tasks / plans to setup Choria on nodes not managed by Puppet, in particular client...
Puppet runs its process under `root`, and in our circumstance, we run our Choria governors under another non-privileged Unix user. Please add the ability to configure which user the governor...
When specifying the `network_peers` parameter to the broker manifest let's automatically assume that the `cluster_peer_port` should be in the broker configuration.
Three new parameters for choria::broker * client_anon_tls * request_signing_certificate * deny_server_connections to set each of * plugin.choria.network.client_anon_tls * plugin.choria.security.request_signing_certificate * plugin.choria.network.deny_server_connections by default there is no change to the broker.conf
This still has a couple of issues, and you'll likely want to change some of the defaults in `.sync.yml` to suit your taste (https://github.com/puppetlabs/pdk-templates#config_default-values- et al.).
There's a few things I want to do - mainly toward getting rid of the `mcollective_agent_bolt_tasks` and `mcollective_choria` modules and trimming down the `mcollective` one. - [x] Move config to...
Or some other static deployment method. We ran into an issue in our environment where certain systems (usually assembly floor gear) does not have internet access, but still needs puppet...
- [ ] An `*.msi` file to install choria ([POC here](https://github.com/smortex/go-choria/commit/a7f06150f2959681a9618abb1a519d0c8a712027)). `PACKAGES=windows_64 rake build` will build for windows now, added in https://github.com/choria-io/go-choria/issues/769 if paths are wrong etc pls fix there...
There's no way to store the results of each iteration for choria::in_groups_of - your suggestion from slack was to add a $memo field to return the result set from.
