Short intro what is Chef and how we used in our company: tripsta!

1. What is Chef..
..and how we use it at

2. Who am I?
Giedrius Rimkus
Lithuanian
PHP Developer at tripsta
Ruby enthusiast
Basketball lover
@giedriusr

3. I'll be talking about..
Sentiments
Pain
Solution

4. Back in 2009..

5. Infrastructure
Application

7. Infrastructure
Application

8. Infrastructure
Application Application Database

9. Infrastructure
Application Application Application
Database

10. Infrastructure
Application Application Application
Application Database Application

11. Infrastructure
Application Application Application
Application Database Application
API API
LB LB

12. Complexity

13. Pain
○ Long installation process
○ Hard maintenance
○ Scaling issues
○ Constantly increased load and usage of
resources (no load balancer)

14. Solution

15. CLUSTER

16. WTH IS CLUSTER?

17. What is a Cluster?
It's a group of linked computers, working
together closely thus in many respects forming
a single computer.

18. Cluster categories
High-availability (HA) clusters
High-availability clusters (also known as failover cluster) are implemented
primarily for the purpose of improving the availability of services that the
cluster provides.
Load-balancing clusters
Load-balancing is when multiple computers are linked together to share
computational workload or function as a single virtual computer. Logically,
from the user side, they are multiple machines, but function as a single
virtual machine.
Compute clusters
Somes times called as a “Grid computing”. Basically used for calculating huge
stats, etc.

19. HOW TO BUILD IT?

21. OR

27. What is Chef? What problem does it solve?
Chef is an open-source systems integration
framework built specifically for automating
the cloud / system configuration.

28. Chef types
Chef Solo
Chef client and Chef server
Hosted Chef
Private Chef

29. Chef Solo..
..is an open source standalone version of Chef
that runs locally on your node, detached from
a Chef server.

30. Chef Client and Chef Server
Chef-client connects to a Chef Server to be told what to
do on the node.

31. Hosted Chef
As with Chef-Server, Chef-client connects to Hosted Chef
to be told what to do on the local node.

32. Private Chef..
..is for Enterprises who want the power, flexibility,
availability, and performance of Hosted Chef, but require
that information never leave their private networks.

33. Why it's an issue?
Infrastructure changes all the time.
Different operating systems
Different hardware from different vendors.

34. What exactly can you do with Chef?
● Install Operating Systems on new servers.
● Install application software on servers.
● Have new software automatically configure
itself to match your environment.
● Share recipes (and obtain recipes from)
other people to install and configure
software.

35. Some goodies I like about Chef
"Manage your servers by writing code,
not by running commands."
Chef is idempotent
Built on top of Ruby

36. Chef Server Architecture

37. Architecture visualization

38. Basic structure of Chef
Environments
Nodes
Cookbooks
Recipes
Files / Templates
Attributes
Data Bags
Search

39. What is what?
What is recipe?
What is cookbook?
What is resource?
What is node?
What is chef-client?
What is knife?
What is data bag?
What is template?

40. Modeling your
infrastructure

41. Nodes
A node is a host that runs the Chef client. The
primary features of a node, from Chef's point
of view, are its attributes and its run list.
Nodes are the thing that Recipes and Roles are
applied to.

42. Roles
A role means grouping similar features of
similar nodes.

43. Run list
A list of recipes that a node will run.

44. Configuring Nodes

45. Cookbooks
A cookbook is a collection of recipe, resource
definition, attribute, library, cookbook file
and template files that chef uses to configure
a system. Cookbooks are typically grouped
around configuring a single package or service.
The MySQL cookbook, for example, contains
recipes for both client and server.

47. Recipes
Recipes are the files where you write your
resources (code).

48. Another example
chef/cookbooks/git/recipes/default.rb
package "git-core"
# apt-get install git-core
# yum install git-core
# etc..

49. Another example
directory "/home/new_folder" do
mode 0755
owner "someuser"
group "www"
action :create
end

50. Metadata
Cookbooks often rely on other cookbooks for
pre-requisite functionality. In order for the
server to know which cookbooks to ship to a
client, a cookbook that depends on another
one needs to express that dependency
somewhere. That "somewhere" is in cookbook
metadata.

51. Resources
A resource is usually a cross platform
abstraction of the thing you're configuring on
the host.
Chef's resources are mostly just containers for
data, with some basic validation functionality.

52. Resources
Have a type
Have a name
Have parameters
Take action to put the resource in the
declared state

53. Type

54. Name

55. Parameters

56. Action

57. Providers
The provider is the platform-specific
implementation of the thing a resource
abstracts.
On Red Hat or CentOS - yum
Debian and Ubuntu - apt package manager will
be used

58. Search
Search is built by the Chef Server, and allow
you to query arbitrary data about your
infrastructure

59. Data Bags
Data Bags store nested key–value data on the
chef server. Data Bag data are searchable, and
can also be loaded directly by name in a
recipe. Data Bags are global for your chef-
server installation–you can think of them as
attributes for your whole infrastructure.

60. Environments
Provides a mechanism for managing different
architectural segmented spaces such as
production, staging, development, and
testing, etc with one Chef setup.

61. Chef Workflow

62. Everyday Chef Workflow for developers

63. Developer makes changes to Chef recipes, roles, etc.

64. Developer pushes changes to origin Chef repository

65. Developer uses Knife to push new code to the Chef Server

66. Developer uses Knife to tell Chef-clients to update themselves

67. Chef-client on Chef nodes contact the Chef Server

68. Chef-client pulls latest code from the Chef Server

69. Chef-client on the node updates the system

70. Practical example

71. Update authorized_keys
$ cat cookbooks/bootstrap/files/default/authorized_keys
$ echo 'ssh-rsa dev4-public-key' >> !$

72. Committing and pushing
$ git diff
git add .
git commit -m 'adding new public key'
git push

73. Updating Chef Server
bundle exec knife cookbook upload bootstrap
cap configure:all
or
ssh root@127.0.0.1
$ chef-client

74. How Chef helped us?

75. We don't care that much about
Infrastructure changes all the time
Scalability, because..
- adding new nodes is painless
- it's fast (takes minutes or hours, not days or weeks)
- there is no need in buying more machines with every
new website

76. Clear separation between servers
with roles:
Frontend
Backend
Application
Memcached
Database
other..

77. Chef requirements
Chef-client is supported on the following platforms
● Ubuntu (10.04, 10.10, 11.04, 11.10)
● Debian (5.0, 6.0)
● RHEL & CentOS (5.x, 6.x)
● Fedora 10+
● Mac OS X (10.4, 10.5, 10.6, 10.7)
● Windows 7
● Windows Server 2003 R2, 2008 R2
Ruby
Ruby 1.8.7, 1.9.1 or 1.9.2 with SSL bindings is required.
RubyGems
Version 1.3.7 or greater. On Ubuntu and Debian Rubygems should be installed
from source
Git?

78. Parts I didn't cover
- Setting up and running chef-server / chef-client
- Shef
- Knife plugins
- Chef + capistrano
- All the rest Chef goodies

79. Chef Alternatives
● Puppet
● Sprinkle
● Rubber
● Sunzi

80. Great resources
https://github.com/opscode/cookbooks
http://wiki.opscode.com/display/chef/Home
http://railscasts.com/episodes/339-chef-solo-basics
https://github.com/ctshryock/capistrano-chef

81. Thank You