chef-cookbooks | RCB OPS - Chef Cookbooks | DevOps library

by rcbops Ruby Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | chef-cookbooks Summary

chef-cookbooks is a Ruby library typically used in Devops, Chef applications. chef-cookbooks has no bugs, it has no vulnerabilities and it has low support. However chef-cookbooks has a Non-SPDX License. You can download it from GitHub.

This repository contains a collection of chef cookbooks that can be used to deploy, and manage, the suite of OpenStack core projects (nova, glance, keystone, swift, horizon). User documentation is available in our knowledge center! The rest of this documentation is primarily aimed at developers who want to hack on the cookbooks. The cookbooks have been designed and written in such a way that they can be used to deploy individual service components on any of the nodes in the infrastructure; in short they can be used for single node 'all-in-one' installs (for testing), right up to multi/many node production installs. In order to achieve this flexibility, they make use of the chef search functionality, and therefore require that if you are deploying anything larger than a single node deployment, you use chef server to host your cookbooks rather than using chef solo.

Support

Quality

Security

License

Reuse

Support

chef-cookbooks has a low active ecosystem.

It has 116 star(s) with 103 fork(s). There are 107 watchers for this library.

It had no major release in the last 6 months.

There are 99 open issues and 394 have been closed. On average issues are closed in 69 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of chef-cookbooks is current.

Quality

chef-cookbooks has 0 bugs and 0 code smells.

Security

chef-cookbooks has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

chef-cookbooks code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

chef-cookbooks has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

chef-cookbooks releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

chef-cookbooks saves you 280 person hours of effort in developing the same functionality from scratch.

It has 678 lines of code, 0 functions and 76 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of chef-cookbooks

Get all kandi verified functions for this library.

chef-cookbooks Key Features

No Key Features are available at this moment for chef-cookbooks.

chef-cookbooks Examples and Code Snippets

No Code Snippets are available at this moment for chef-cookbooks.

Community Discussions

Trending Discussions on chef-cookbooks

Chef recipe 'include_recipe' takes precedence over other code and resources

How to stage, develop, and test changes to the chef repo

QUESTION

Chef recipe 'include_recipe' takes precedence over other code and resources

Asked 2019-Oct-14 at 23:49

I'm attempting to create a Chef cookbook that, for now, is mostly just a wrapper cookbook for another cookbook (the audit cookbook). I'm still learning Chef, but from what I can gather from the About Recipes documentation and the Resources Reference documentation, Chef recipes should execute in the order that they're defined (via Ruby code and/or Chef resources).

In the About Recipes documentation, it mentions that

When a recipe is included, the resources found in that recipe will be inserted (in the same exact order) at the point where the include_recipe keyword is located.

In the Resources Reference documentation, they have an apt_update resource that presumably executes before the include_recipe method due to the fact that it's defined earlier in the recipe.

My wrapper cookbook has a single recipe, default.rb, which is literally these two lines:

...

ANSWER

Answered 2019-Oct-10 at 04:54

if you would examine the audit::inspec rescipe, you will find that it uses a compile time installation of the inspec rubygem (see the last line)

Source https://stackoverflow.com/questions/58314519

QUESTION

How to stage, develop, and test changes to the chef repo

Asked 2017-Jul-17 at 18:27

I wanted to ask what the best practice, and what is commonly done for testing and developing changes to cookbooks,environments,nodes, essentially the chef repo. Reason I ask this, is the current setup has one chef server. All environments (staging, beta, prod) use this server and have all the relevant info pulled from here.

However, when I want to make a change to a cookbook and test it on one of our staging environments...it pulls from this repo and I either have to make a mess of configuration changes or...upload a cookbook with a different name, test, and then proceed to rename my cookbook back to the original name. Far from efficient, and frustrating even.

I thought maybe I could have different git branches and somehow point them in different directions but it would still be pulling from the same repo I imagine..

My thought then was to simply have an entirely separate chef server dedicated for developing and testing, and point my staging environments to that chef server.

Not sure if there was another more simple way I was missing, thus why I'm asking the community.

This may seem related to another question I asked, but I hope the difference between these two questions is clear (How to update chef cookbooks in a developer workflow)

...

ANSWER

Answered 2017-Jul-17 at 15:17

Chef has the notion of different environments: https://docs.chef.io/environments.html

You can have prod and staging environment files which have all relevant cookbooks pinned to a stable version.

Then when you make a change to your cookbook you should bump the version number and update the staging environment with the new version so you can test the changes there. I.e.

Source https://stackoverflow.com/questions/45147266

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install chef-cookbooks

You can download it from GitHub.
On a UNIX-like operating system, using your system’s package manager is easiest. However, the packaged Ruby version may not be the newest one. There is also an installer for Windows. Managers help you to switch between multiple Ruby versions on your system. Installers can be used to install a specific or multiple Ruby versions. Please refer ruby-lang.org for more information.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: