k2s Posted July 15, 2015 Report Posted July 15, 2015 In traditional data centers, server configuration and management was the purview of system administrators. They lugged around the servers, hooked them up to power and networking infrastructures, and installed and configured the software and services required of them by clients. For the most part, that’s still how data centers are run, except for the last part of the process: the configuration and management of server operating systems and other software.
k2s Posted July 15, 2015 Author Report Posted July 15, 2015 As companies like Google and Facebook found they needed ever quicker and more agile server provisioning, they automated much of the process, developing programmatic tools that made server configuration more akin to development than traditional server administration. So began the rise of devops, which applies the techniques of development to system administration tasks.
k2s Posted July 15, 2015 Author Report Posted July 15, 2015 Over the last few years, two tools have gained prominence in the devops world: Chef from OpsCode and Puppet. Both are configuration management tools created to allow for the programmatic configuration and management of multiple servers. There are however significant differences between the two. The most obvious difference between Chef and Puppet is one of language. From a certain perspective, Puppet is a language – a declarative language with similarities to JSON – and the tools to implement that language’s instructions. OpsCode Chef on the other hand uses a subset of the popular Ruby language to create a domain specific language. Chef recipes are written in Ruby using helper functions that are part of Chef.
ramudu3 Posted July 15, 2015 Report Posted July 15, 2015 chef antee vantodu , puppet antee kukka pilla ani undee kadaa ninnati daka , marchesaraaa.
k2s Posted July 15, 2015 Author Report Posted July 15, 2015 We use Chef Recipes evvar rasina recipes ? mee own va leda bayata ready made ga untaya ?
k2s Posted July 15, 2015 Author Report Posted July 15, 2015 Infrastructure as Code Chef turns infrastructure into code. With Chef, you can automate how you build, deploy, and manage your infrastructure. Your infrastructure becomes as versionable, testable, and repeatable as application code. Chef server stores your recipes as well as other configuration data. The Chef client is installed on each server, virtual machine, container, or networking device you manage—we’ll call these nodes. The client periodically polls Chef server latest policy and state of your network. If anything on the node is out of date, the client brings it up to date.
k2s Posted July 15, 2015 Author Report Posted July 15, 2015 Chef is a systems and cloud infrastructure automation framework that makes it easy to deploy servers and applications to any physical, virtual, or cloud location, no matter the size of the infrastructure. Each organization is comprised of one (or more) workstations, a single server, and every node that will be configured and maintained by the chef-client. Cookbooks (and recipes) are used to tell the chef-client how each node in your organization should be configured. The chef-client (which is installed on every node) does the actual configuration.
sattipandu Posted July 15, 2015 Report Posted July 15, 2015 evvar rasina recipes ? mee own va leda bayata ready made ga untaya ? woh kaama humaarein DevOps and Infrastructure COE dekh ley te hum tho sirf developer hain,
porsche911 Posted July 15, 2015 Report Posted July 15, 2015 adanta maak telvad.... code rastam ... bug fixing sestham
k2s Posted July 15, 2015 Author Report Posted July 15, 2015 woh kaama humaarein DevOps and Infrastructure COE dekh ley te hum tho sirf developer hain, bye1 adanta maak telvad.... code rastam ... bug fixing sestham :3D_Smiles:
sattipandu Posted July 15, 2015 Report Posted July 15, 2015 evvar rasina recipes ? mee own va leda bayata ready made ga untaya ? woh kaama humaarein DevOps and Infrastructure COE dekh ley te hum tho sirf developer hain, Simple bhayya we release code every 2 weeks sometimes every week, so our program as a whole opted to use Chef with Chef platform, infrastructure can be treated like code, tied to SVN/GitHub and compartmentalized based on environments and much better way of doing CI properties/server credential changes in prod dont need code pushes or hotfixes, Chef deploys any databag changes to any env stealthily based on diff Also with Chef spinning up env's in AWS is just plain simple
k2s Posted July 15, 2015 Author Report Posted July 15, 2015 Chef DK The Chef development kit defines a common workflow for cookbook development, including unit and integration testing, identifying lint-like behavior, dedicated tooling, and more:
k2s Posted July 15, 2015 Author Report Posted July 15, 2015 Simple bhayya we release code every 2 weeks sometimes every week, so our program as a whole opted to use Chef with Chef platform, infrastructure can be treated like code, tied to SVN/GitHub and compartmentalized based on environments and much better way of doing CI properties/server credential changes in prod dont need code pushes or hotfixes, Chef deploys any databag changes to any env stealthily based on diff Also with Chef spinning up env's in AWS is just plain simple +578 gadey sauthunna iffudu...... uses endi anedi....atta saduvukunta ikkada info posting..
.thumb.jpg.ce42bb16ec102475a78c2087ce269c7d.jpg)
Recommended Posts