Chef

Chef is a configuration management tool primarily written in Ruby, with an Erlang & Java server. It uses a pure-Ruby, domain-specific language (DSL) for writing system configuration "recipes". Chef is used to streamline the task of configuring and maintaining a company's servers, and can integrate with cloud-based platforms such as Amazon EC2, Google Cloud Platform, OpenStack, SoftLayer, and Microsoft Azure to automatically provision and configure new machines. Chef contains solutions for both small and large scale systems, with features and pricing for the respective ranges.

Chef Workstation

chef-workstation^AUR contains the development and deployment tools for working with the Chef platform. It includes:

Chef Infra Client
Test Kitchen
Cookstyle
Chef InSpec

Chef Infra Client

For the systems being managed, install the chef-client^AUR package. This is the recommend installation method to get chef-client, chef-solo, or chef-zero tools.

Cinc Client

Chef Software changed their licensing for using their packages to require accepting their license, much like Red Hat requires license acceptance to use Red Hat Enterprise Linux. There is a community distribution called Cinc that is working towards providing community-supported packages for Chef Software's products (similar to CentOS as an alternative). The cinc^AUR package provides the alternate cinc-client, cinc-solo, or cinc-zero tools.

Omnibus Chef Installer

The packages provided by Chef Software are built with their dependencies included. This allows them to ship Chef without worrying about the underlying operating systems' support for Ruby, OpenSSL, etc. The chef-workstation^AUR, chef-client^AUR, and cinc^AUR packages are built by re-using these packages.

Installing from Source

If you wish to build your own Omnibus packages:

 $ git clone https://github.com/opscode/omnibus-chef.git
 $ cd omnibus-chef

Wipe out any previous installations and the omnibus cache:

# rm -Rf /opt/chef/* /var/cache/omnibus/*

Set up the directories and change the ownership to yourself so building as root is not required:

# mkdir -p /opt/chef /var/cache/omnibus
# chown -R "$USER:users" /opt/chef
# chown -R "$USER:users" /var/cache/omnibus

Run the following to build:

$ bundle install --binstubs
$ bundle exec omnibus clean chef
$ bundle exec omnibus build chef

After that, you may like to change the ownership of directories back to the system:

# chown -R root:root /opt/chef
# chown -R root:root /var/cache/omnibus

A Makeself portable installer will be created, e.g. chef-11.8.2_0.arch.3.12.6-1-ARCH.sh. Run this executable to install chef.

Uninstallation

Remove all installation files manually:

# rm -Rf /opt/chef

You can also ensure the omnibus cache is removed:

# rm -Rf /var/cache/omnibus

Other Installation Methods

Note: Do not use these methods. It is recommended to install chef-client or use the Omnibus installer method (see above). This section is included only for completeness-sake.

By RubyGem

This is one of easiest ways to install Chef, but it is highly not recommended. If you already have gem versions of the dependencies installed to the system you could run into conflicts.

Ensure you first install the package. This also provides RubyGems.

Next, install the Chef RubyGem:

# gem install chef

gollark: Hmm, for reasons, what would the people of esolangs™ suggest I use for programming web backend stuff?

gollark: Well, it makes XSS attacks pretty easy to do, and it's just weirdly object-oriented and often inconsistent.

gollark: JS's basic DOM API is just kind of awful.

gollark: If you use one of the many virtual DOM-type frameworks, you would have to deliberately *try* to introduce XSS.

gollark: Okay, yes, fair, but JS+frameworks make XSS really hard.

This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.