Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

RSS

forkable_client (1) Versions 0.0.1

Provides forked chef-client runs

Berkshelf/Librarian
Policyfile
Knife
cookbook 'forkable_client', '~> 0.0.1'
cookbook 'forkable_client', '~> 0.0.1', :supermarket
knife cookbook site install forkable_client
knife cookbook site download forkable_client
README
Dependencies
Quality

ForkableClient

Like modifying code on the fly? Like reworking internals of running code to do interesting things? Like not losing a huge chunk of memory because some jerk cookbook decided to load a 100M json file just for the hell of it? Then this cookbook is for you!

What's it do?

This cookbook adds forking support to chef-client runs. It is based on the work within this ticket. After this cookbook has loaded, client runs will fork themselves and then converge. What this provides is less worry about what cookbooks may be doing (and loading) that is going to bloat out the memory of the process. It's just that simple.

How do I use it?

Just add it to your node's run list (and probabably restart your daemon if it's currently running)

knife node run_list add my.amazing.node recipe[forkable_client]

Single runs

This cookbook does not work for single runs. It requires an interval based run (daemonized if you'd like), as the first run will fail by design. The reason for the failure is that we need to adjust how the client performs the run, and we don't want it to attempt to converge the node before we get the modifications applied. So a first run will end with something like this:

ERROR: Running exception handlers
FATAL: Saving node information to /var/cache/chef/failed-run-data.json
ERROR: Exception handlers complete
ERROR: ForkedClientInsertion: Chef client is now forkable. This is a non-fatal error.
FATAL: Stacktrace dumped to /var/cache/chef/chef-stacktrace.out
ERROR: Sleeping for 5 seconds before trying again

But the next run will show the new functionality at work:

INFO: Forking chef instance to converge...
INFO: Fork successful. Waiting for new chef pid: 16231
INFO: Forked instance now converging
INFO: *** Chef 0.10.10 ***
...
INFO: Chef Run complete in 4.34858479 seconds
INFO: Running report handlers
INFO: Report handlers complete
INFO: Forked instance completed. Exiting.
INFO: Forked converge complete

References

Repo: https://github.com/chrisroberts/cookbook-forkable_client

<small> * http://tickets.opscode.com/browse/CHEF-3104 * https://github.com/opscode/chef/pull/291 </small>

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric
            

0.0.1 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric
            

0.0.1 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

0.0.1 failed this metric

FC064: Ensure issues_url is set in metadata: forkable_client/metadata.rb:1
FC065: Ensure source_url is set in metadata: forkable_client/metadata.rb:1
FC066: Ensure chef_version is set in metadata: forkable_client/metadata.rb:1
FC067: Ensure at least one platform supported in metadata: forkable_client/metadata.rb:1
FC069: Ensure standardized license defined in metadata: forkable_client/metadata.rb:1
Run with Foodcritic Version 11.1.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

0.0.1 passed this metric

No Binaries Metric
            

0.0.1 passed this metric

Publish Metric
            

0.0.1 passed this metric

Supported Platforms Metric
            

0.0.1 failed this metric

forkable_client should declare what platform(s) it supports.

Testing File Metric
            

0.0.1 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

0.0.1 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must include a tag that matches this cookbook version number