[chef] Re: Re: Re: Re: Push Jobs Questions

["kritivagop01 ." < >]

hi,

please inform what values to be given for  push jobs

 "package_url": "",

    "package_checksum": ""

.

thanks,

K.Gopalakrishnan

On Sat, Nov 22, 2014 at 1:40 AM, AJ Christensen < " target="_blank"> > wrote:

You may be able to use the Quorum functionality to half-bake this [0]:

```
knife job start --quorum 90% 'chef-client' --search 'role:webapp'
```

The minimum number of nodes that match the search criteria, are
available, and acknowledge the job request. This can be expressed as a
percentage (e.g. 50%) or as an absolute number of nodes (e.g. 145).
Default value: 100%

I'd try values like 50% of your available foobars and see how it works
out for ya.

Good Luck!

cheers,

--aj

[0] https://github.com/opscode/knife-push#examples

On Sat, Nov 22, 2014 at 8:56 AM, Bryan Baugher < "> > wrote:
> 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 < "> > 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