Ansible Homebrew



Jeff Geerling (geerlingguy) maintains a large variety of open source Ansible content. This website catalogs it all. About Jeff Geerling (geerlingguy) Jeff Geerling is an author and software developer from St. He started using Ansible in 2013 and maintains numerous Ansible works. # This module was written for Ansible. # It doesn't support all of Homebrew yet. # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version.

Ansible Homebrew Module

Ansible homebrew vs

This command calls ansible and tells it: To use localhost as it's inventory (-i).Inventory is Ansible speak for machine or machines you want to be able to run commands on. To connect (-c) locally (local) instead of over SSH.To run the ping module (-m) to test the connection.; To run the command on all hosts in the inventory (in this case, our inventory is just the localhost). Sudo pip install ansible -quiet; Then, if you would like to update Ansible later, just do: sudo pip install ansible -upgrade; Native Python Install - Full explanation: Ensure Xcode is installed first. Some of Ansible's dependencies need to be compiled, so you'll need the developer tools that come with Xcode. Homebrew - Package manager for Homebrew; homebrewcask - Install/uninstall homebrew casks. Wait for Ansible Tower job to finish. Towerlabel - create, update,.

Chef
Developer(s)Chef
Initial releaseJanuary 2009; 12 years ago[1]
Stable release
Server14.2.2 / March 18, 2021; 32 days ago[2]
Client16.11.7 / March 18, 2021; 32 days ago[3]
Repositorygithub.com/chef/chef
Written inClient: Ruby
Server: Ruby, Erlang
Operating systemGNU/Linux, MSWindows, FreeBSD, macOS, IBM AIX, Solaris
TypeConfiguration management, System administration, Network management, Cloud management, Continuous delivery, DevOps, Infrastructure as Code
LicenseApache License 2.0
Websitewww.chef.io

Chef is a company and the name of a configuration management tool written in Ruby and Erlang. 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, Oracle Cloud, OpenStack, IBM Cloud, Microsoft Azure, and Rackspace 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.

Features[edit]

The user writes 'recipes' that describe how Chef manages server applications and utilities (such as Apache HTTP Server, MySQL, or Hadoop) and how they are to be configured. These recipes (which can be grouped together as a 'cookbook' for easier management) describe a series of resources that should be in a particular state: packages that should be installed, services that should be running, or files that should be written. These various resources can be configured to specific versions of software to run and can ensure that software is installed in the correct order based on dependencies. Chef makes sure each resource is properly configured and corrects any resources that are not in the desired state.[4]

Chef can run in client/server mode, or in a standalone configuration named 'chef-solo'. In client/server mode, the Chef client sends various attributes about the node to the Chef server. The server uses Elasticsearch to index these attributes and provides an API for clients to query this information. Chef recipes can query these attributes and use the resulting data to help configure the node.[citation needed]

Traditionally, Chef was used to manage Linux but later versions support Microsoft Windows as well.[5]

It is one of the major configuration management systems on Linux, along with CFEngine, Ansible and Puppet.[6][7] More than a configuration management tool, Chef, along with Puppet and Ansible, is one of the industry's most notable Infrastructure as Code (IAC) tools.[8]

History[edit]

Ansible

Chef was created by Adam Jacob as a tool for his consulting company, whose business model was to build end-to-end server/deployment tools. Jacob showed Chef to Jesse Robbins, who saw its potential after running operations at Amazon. They founded a new company with Barry Steinglass, Nathen Haneysmith, and Joshua Timberman to turn Chef into a product.[9]

The project was originally named 'marionette', but the word was too long and cumbersome to type; the 'recipe' format that the modules were prepared in led to the project being renamed 'Chef'.[9]

Ansible Homebrew

In February 2013, Opscode released version 11 of Chef. Changes in this release included a complete rewrite of the core API server in Erlang.[10]

On April 2, 2019, the company announced that all their products are now open source under the Apache 2.0 license.[11]

On September 8, 2020, Progress announces the acquisition of Chef.[12]

Platform support[edit]

Chef is supported on multiple platforms according to a supported platforms matrix for client and server products.[13] Major platform support for clients includes AIX, Amazon Linux, Debian, CentOS/RHEL, FreeBSD, macOS, Solaris, SUSE Linux, Microsoft Windows and Ubuntu. Additional client platforms include Arch Linux and Fedora. Chef Server is supported on RHEL/CentOS, Oracle Linux, SUSE Linux and Ubuntu.

Customers[edit]

Chef is used by Facebook,[14]AWS OpsWorks, Prezi,[15] and BlackLine.

See also[edit]

Ansible Homebrew Tap

  • Infrastructure as code (IaC)

Ansible Homebrew App

References[edit]

  1. ^'Announcing Chef'. chef.io. 15 January 2009. Retrieved 2020-11-25.CS1 maint: discouraged parameter (link)
  2. ^'Chef Infra Server 14.2.2 Released! - Chef Release Announcements - Chef Questions'. discourse.chef.io. Retrieved 2021-03-29.
  3. ^'Chef Infra Client 16.11.7 Released! - Chef Release Announcements - Chef Questions'. discourse.chef.io. Retrieved 2021-03-29.
  4. ^Chef - Code Can | Chef, retrieved 2015-07-04CS1 maint: discouraged parameter (link)
  5. ^Cade Metz (2011-10-26), 'The Chef, the Puppet, and the Sexy IT Admin', Wired, retrieved 2015-07-04CS1 maint: discouraged parameter (link)
  6. ^Alan Sharp-Paul (2013-03-04), Puppet vs. Chef - The Battle Wages On, retrieved 2015-07-04CS1 maint: discouraged parameter (link).
  7. ^Lueninghoener, Cory (2011-03-28), 'Getting Started with Configuration Management'(PDF), ;login:, Usenix, 36 (2), retrieved 2015-07-04CS1 maint: discouraged parameter (link)
  8. ^Keiser, John (14 November 2016). 'Chef Provisioning: Infrastructure As Code'.
  9. ^ abHistory of Chef: What's in a Name? on YouTube
  10. ^Bryan McLellan (2013-02-04). 'Chef 11 Released!'. Chef (company). Retrieved 2015-07-04.CS1 maint: discouraged parameter (link)
  11. ^Introducing the New Chef: 100% Open, Always - Chef Blog
  12. ^Corporation, Progress Software (2020-09-08). 'Progress Announces Acquisition of Chef'. GlobeNewswire News Room. Retrieved 2020-09-08.
  13. ^'Platforms — Chef Docs'. chef.io. Retrieved 2 April 2021.CS1 maint: discouraged parameter (link)
  14. ^'Facebook uses a seasoned Chef to keep servers simmering'. pcadvisor.co.uk. Retrieved 6 January 2014.CS1 maint: discouraged parameter (link)
  15. ^How Chef Enables the DevOps Culture at Prezi - Zsolt Dollenstein on YouTube

External links[edit]

Retrieved from 'https://en.wikipedia.org/w/index.php?title=Chef_(software)&oldid=1018778401'