If I have 8 brokers (amq) and the server configuration on each of my agents contains the 8 brokers, with the plugin.activemq.randomize set to true, would it be reasonable to expect that I should see all of my connections distributed somewhat evenly between all 8 brokers?
_rc
assuming they
assuming they're all reachable by all the nodes, sure
esbe
Ok, thanks.
Right now I'm seeing only the first 2 in my pool being used. I end up with ~2500 per broker and not nothing on the other 6. If I change the order in my pool to have other servers be the first and second entries in the pool, they seem to work.
This would be an issue with STOMP gem and not so much MCO, correct?
_rc
assuming your configuration is good and isn't saying anything odd like plugin.activemq.pool.size = 2, yeah
esbe
Perfect. Thank you!
_rc
the gem will select a broker to connect to and stay connected until there's something to trigger a failover
the mcollective logs should show it connecting to brokers in the pool until it finds one
SOLDIERz__ joined the channel
SOLDIERz__ joined the channel
straylen has quit
ddevon joined the channel
straylen joined the channel
straylen has left the channel
piavlo joined the channel
inecas has quit
stresler has quit
stresler joined the channel
cat_pants
Has anyone successfully installed the "shell" agent?
torrancew
cat_pants: yes, but I had to back it out due to a conflict with the nrpe agent (patched upstream, just not sure if there's a packaged release for it yet)
cat_pants
Ah, I'm not using the nrpe agent afaik
I installed by doing a git clone in /root, then doing "rsync -av /root/mcollective-shell-agent/lib/mcollective /usr/libexec/mcollective/"
Which looks like it merges the directories properly
stresler has quit
Restarted mcollective on the client and server
Trying to do "mco shell run dir" but it gives me "undefined method `sort_by!' for #<Array:0x7f3c8fc79ac0>"
torrancew
nrpe is in our critical path (our custom deploy agent/app call out to it), so I didn't get to do much fiddling :/
stresler joined the channel
cat_pants
Ah no worries
fiddyspence has quit
ramindk has quit
ramindk joined the channel
jantman has quit
Bdawk joined the channel
Anyone else using the shell agent?
ramindk has quit
jobewan joined the channel
ramindk joined the channel
frozenfoxx joined the channel
frozenfoxx
I have a kinda dumb question about mcollective.
I know that normally you have to establish ssh key exchange with a master server, is there any way to configure mcollective to allow any system in a specified subnet or domain to automatically register, even if it overwrites a pre-existing completed chain?
for an example of what I'm talking about, I've got three systems, one server and two clients.
ramindk has quit
Is there a way to configure mcollective on the server to register client1, then if it receives a registration from client2 CLAIMING it's client1 to automatically revoke the old trust for client1 and replace it with client2?
This is coming up because I'm building an environment that has many rapidly built-and-destroyed machines, so the generated keys for each hostname on a domain are going to change rapidly.
As a side note, yes I'm aware this means that any system on a subnet could man-in-the-middle any other system, but that's a totally different concern.