----- Original Message ----- > From: "Christopher Wood" <[email protected]> > To: "mcollective-users" <[email protected]> > Sent: Wednesday, 5 October, 2016 22:19:50 > Subject: Re: [mcollective-users] translate activemq subcollectives to nats.io
> Subcollectives indeed work fine. So far I have things running on a single host > and the setup was much easier than doing something similar with activemq > several years ago. Everything I could think to try works the same. > > Next to fully puppetize the setup and persuade the security department to open > another port for nats (oh dear). Did you use the module the wiki recommend? It's simple but does what you want including clustering > Mild nitpick: there doesn't seem to be a client config file option for cert > and > key. I know there are environment variable options but enough people will > forget to set those on every login (environment with no persistent > .bash_profile or similar, yes indeed). My workaround will be to provide a > short > puppet manifest to reshape their client config since any shuffling errors will > be obvious when mailed back. It would definitely be easier to have people copy > activemq cert params into choria cert params. why do you wish to change these paths? It defaults to the same ones puppet use for a reason - you should not need to make any client configuration at all, just put the certs in the puppet location - which 'mco choria request_cert' does for you -- --- You received this message because you are subscribed to the Google Groups "mcollective-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
