I am (finally*) digging into nats as a broker.
I think I need help figuring out how to translate an activemq authorizationMap
specifying all the collectives into a set of nats.io routes. Are subcollectives
specified in the broker config still a thing with nats? The idea is to preserve
the same set of subcollectives for group convenience.
Details:
For instance, here's the default "mcollective" collective in activemq:
<authorizationMap>
<authorizationEntries>
<authorizationEntry topic="mcollective.>" write="mcollective"
read="mcollective" admin="mcollective" />
<authorizationEntry queue="mcollective.>" write="mcollective"
read="mcollective" admin="mcollective" />
</authorizationEntries>
</authorizationMap>
Going by the example (https://github.com/ripienaar/puppet-nats) it doesn't look
like there's a similar construct in nats. So maybe not a thing?
(*Why now? Two days ago one of the activemq daemons here helped up achieve our
monthly clustering failure by crashing, and the clustering stayed dead even
when monit brought the daemon up, again. I'm feeling the glimmer of a scintilla
of irritation here.)
--
---
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.
