Any reply to my questions is hugely appreciated.. On Tuesday, December 6, 2011 4:19:46 PM UTC+5:30, Jens Braeuer wrote: > > Hi everyone, > > I run MCollective 1.2.1 together with ActiveMQ 5.5 under Scientific Linux > 6.1 on Amazon EC2. Overall it works like a > charm, but sometimes (eg. 1/30) discovery fails. Still the exit-code of > mco will be 0, which is a problem for me as I > use MCollective e.g. to trigger deployments from Jenkins. > > I would like to ask for some feedback on the following ideas, that could > fix this problem. > > a) Increase discovery timeout > mco offers a option to tweak the discovery timeout. What is your > experience with increasing this value? When running > "mco ping", I see ping times of 130ms, so 2 seconds (the default should be > enough), or? > Is there a way to configure is global? > > b) Mco should exit != 0 when no nodes are found > I would like to see a "--batch" or "--non-interactive" mode, where mco has > a exit code different from 0, when no nodes > are found. > > c) Add "expected count" to mco command > I thing there are some situation, where one knows the number of > MCollective nodes. So what about adding a options > "--expect-number" option to mco, where I can either give a count or range > of expected nodes. > > d) Is this normal at all? > I have no experience with MCollective in a datacenter, so: Is this problem > cloud/EC2 related or does it happen in > non-cloud setups too? How could I debug what makes the discovery fail? > > I really appreciate your feedback. You can find me a jbraeuer on #puppet. > Cheers, > Jens > >
-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/7DDpZQq0tRYJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
