Neev Partners with Opscode Inc.

Contributed by Ravi Petlur on 18 Sep 2013

Neev is proud to partner US-based Opscode Inc as a reseller to license and resell its software products and services to our customers. Additionally, Neev is also licensed to provide training on Opscode’s products.

Opscode is a US-based software company founded in the year 2008. Opscode is one of the world’s leading providers of products and services for IT infrastructure automation. Opscode helps enterprises create easily and predictably scalable fully automated server infrastructures. These infrastructures can be rebuilt quickly in any environment. This helps system engineers and developers save time and money. Its flagship product is the Chef Software configuration management tool. Its client list includes Facebook, Prezi, Wharton School, Splunk, Branchout, Get Satisfaction among others.

About Chef:

IT cos who follow the DevOps philosophy of application and infrastructure management have Chef in their kitty for sure. Chef is an automation platform that transforms infrastructure into code. Chef enables conversion of infrastructure into code and helps manage conﬁgurations, put them together in recipes, track it like source code and conﬁgure your servers.

How Chef works:

The following diagram shows the relationships between the various elements of Chef - the nodes, the server, and the workstations. These elements work together to provide the chef-client the information and instruction that it needs so that it can do its job.

Image Source: Opscode

Chef comprises of three main elements: a server, one (or more) nodes, and at least one workstation.

The server acts as a hub that is available to every node in the organization. This ensures that the right cookbooks (and recipes) are available, right policies are applied, the node object used during the previous chef-client run is available to the current chef-client run, and that all of the nodes that will be maintained by the chef-client are registered and known to the server.

The workstation is the location from which cookbooks (and recipes) are authored, policy data (such as roles, environments, and data bags) are defined, data is synchronized with the chef-repo, and data is uploaded to the server.

Each node contains a chef-client that performs the various infrastructure automation tasks that each node requires.

Cookbooks are also a very important element and are treated as a separate component (alongside the server, nodes, and the workstation) across any documentation. In general, cookbooks are authored and managed from the workstation, moved to the server, and then are pulled down to nodes by the chef-client during each chef-client run.

References:

http://www.opscode.com/chef/

http://docs.opscode.com/release/11-4/chef_overview.html

http://devopsangle.com/2013/06/24/ask-devops-nine-top-devops-tools-for-management-of-cloud-applications/

http://docs.opscode.com/chef_overview.html

http://www.slideshare.net/Clogeny/deep-dive-into-opscode-chef-16512960

https://learnchef.opscode.com/starter-use-cases/convert-bash-to-chef/

Visit us at Neevtech.com to know more about our offerings.

Tags: automated server infrastructure, automation platform, Branchout, Chef Software configuration management, chef-client, chef-repo, code, cookbook, developer, DevOps, FaceBook, Get Satisfaction, infrastructure automation, infrastructure management, IT infrastructure automation, license, Neev, nodes, Opscode, policy, Prezi, reseller, server, software products, software services, SPLUNK, system engineer, training, US-based, Wharton School