[chef] Re: Re: Push Jobs Questions

[Bryan Baugher < >]

Great, thanks for the links. Somehow google wasn't being helpful.

My use case is fairly simple. I want to run chef-client on my nodes in a particular environment but I want to ensure that,

 * I don't end up restarting all the services at once

 * A bad config doesn't take out the whole service

The simplest version of this would just be to group the nodes into X number of groups and run chef-client one group at a time. Knife ssh has a concurrency option which limits the number of ssh connections which would also achieve the same goal.

On Fri Nov 21 2014 at 1:45:45 PM AJ Christensen < > wrote:

https://github.com/opscode/omnibus-pushy
https://github.com/opscode/oc-pushy-pedant
https://github.com/opscode/omnibus-push-jobs-client
https://github.com/opscode/opscode-pushy-server
https://github.com/opscode/opscode-pushy-simulator
https://github.com/opscode/pushy_common
https://github.com/opscode/knife-push
https://github.com/opscode/opscode-pushy-client

Try searching through the issues, or logging an issue or feature
request or RFC. "don't run command X on all nodes at the same time"
sounds a little hard to implement. Do you mean mutually exclusive,
configurable contention, locking of commands?

Can you describe your use-case? An independent team of Chef operators
has been evaluating use cases and building tests/example cases for
Pushy and tools in the same field (our cases thus far have been around
Cassandra ring bootstrap, expansion and contraction)

cheers,

--aj

On Sat, Nov 22, 2014 at 8:39 AM, Bryan Baugher < " target="_blank"> > wrote:
> Hello everyone,
>
> Is the push jobs code available on github anywhere? Also are there any plans
> to add a kind of concurrency option (i.e. don't run command X on all nodes
> at the same time)?
>
> Bryan