Chef

  • Chef is a configuration management tool written in Ruby and Erlang

• Was written to manage Linux but later versions also support Microsoft Windows

• In February 2013, Opscode released version 11 of Chef

• It uses a pure-Ruby to write system configuration "recipes"

• Integrates with cloud-based platforms such as Internap, Amazon EC2, Google Cloud Platform, OpenStack, SoftLayer, Microsoft Azure and Rackspace

• Support for includes AIX, RHEL/CentOS, FreeBSD, OS X, Solaris, Microsoft Windows and Ubuntu platforms

• Additional client platforms supported include Arch Linux, Debian and Fedora

• Chef Server can be on RHEL/CentOS, Oracle Linux, and Ubuntu

• Chef can run in client/server mode or standalone configuration named "chef-solo"


Chef Architecture

• Chef Development Kit has tools to develop and test your infrastructure automation code

• Infrastructure as code automation code is developed locally on workstation and then deployed in production

• Chef Server is a central repository for Chef cookbooks and have information about every node being managed

• Chef client runs on each node and securely communicates with the Chef server to get the latest configuration instructions for that node

• Chef cookbooks have code for desired state of infrastructure

• Chef node is a physical machine or virtual machine in network being managed by the Chef server




We will define the following in context of Chef:

• Server
• Node
• Resource
• Recipe
• Cookbook
• Run List
• Roles
• Search

Chef Organization

• An organization is the top-level entity for role-based access control in the Chef server
• Each organization contains the default groups (admins, clients, and users, plus billing_admins for the hosted Chef server), at least one user and at least one node (on which the chef-client is installed)
• The Chef server supports multiple organizations
• Organizations are completely independent tenants of Enterprise Chef
• Share nothing with other organizations
• May represent different
• Companies
• Business units
• Departments

Chef Node

• Nodes represent the servers in your infrastructure
• Could be physical servers or virtual servers
• May represent hardware that you own or compute instances in a public or private cloud
• Could also be network hardware – switches, routers etc.

Chef Resources

• A Resource represents a piece of the system and its desired state
• A package that should be installed
• A service that should be running
• A file that should be generated
• A cron job that should be configured
• A user that should be managed
• And more

Chef Recipe

• Configuration files that describe the resource and their desired state

• Recipes can :

Install and configure software components
Mange files
Deploy applications
Execute other recipes
And more

Chef Cookbooks

• Recipes are stored in Cookbooks
• Cookbooks contain recipes, templates, files, custom resources, etc
• Code re-use and modularity

Chef Run List

• A run-list defines all of the information necessary for Chef to configure a node into the desired state
• A run-list is:
• An ordered list of roles and/or recipes that are run in the exact order defined in the run-list; if a recipe appears more than once in the run-list, the chef-client will not run it twice
• Always specific to the node on which it runs; nodes may have a run-list that is identical to the run-list used by other nodes
• Stored as part of the node object on the Chef server
• Maintained using knife and then uploaded from the workstation to the Chef server, or maintained using Chef Automate

Chef Roles

• A role is a way to define certain patterns and processes that exist across nodes in an organization as belonging to a single job function
• Each role consists of zero (or more) attributes and a run-list
• Each node can have zero (or more) roles assigned to it
• When a role is run against a node, the configuration details of that node are compared against the attributes of the role, and then the contents of that role’s run-list are applied to the node’s configuration details
• When a chef-client runs, it merges its own attributes and run-lists with those contained within each assigned role

Roles represent the types of server in your infrastructure

• Load Balancer
• Application Server
• Database Cache
• Database
• Monitoring


learn more about chef here :

Installation on Node

CookBook

Knife


Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources...
Read more

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed withou...
Read more