Introductory talk about DevOps world and Amazon AWS

1. Devs are from Mars,
Ops are from Venus
Alex Recarey
@alexrecarey
Jose Ignacio Galarza
@igalarzab

2. wtf is devops?

3. collaboration
config management
capacity planning
infrastructure as code
devops
monitoring
cross functional skills
trouble shooting
deployment

4. why?

5. because ops suck...

6. fear of change
risky deployments
dev != ops

7. machine = snowflake
firefighting mentality

8. when did this
start?

9. (33% US internet bandwidth 2012)

10. the same work
has to be done
but it can be done in a
different way

11. the same work
has to be done
e
m
o be done in a
but itecan
s
w
A different way

12. Over the last year a
community
has been formed

13. devopsdays.org
#monitoringsucks
#devops
devopsweekly.com
dev2ops.org
codeascraft.etsy.com

14. Collaboration

15. Not sexy, but
important

16. Dev
Ops

17. DevOps

18. Configuration
Management

19. sexy & important

20. “it works for me”
Hand crafted config
Prehistory
“don’t touch the
production server”
Shell scripts

21. “it works for me”
Hand crafted config
Present day
“don’t touch the
production server”
Shell scripts

22. turning an art
into
an assembly line

23. Infrastructure
as code

24. versioned
+
automated
+
repeatable

25. 10’s to 1,000’s of servers
scale
1 a month to 5 deployments a day

26. nd
ld a n
O e
rov
p
CF Engine
tp
os
M
nd
ip a
H
ool
c
lar
pu
o
Puppet
Salt
Chef
Ansible Juju

27. Choose one,
use it

28. Monitoring

29. Measure everything

30. Monitoring is crucial for ops
Can also be fun
Debugging without logs is hell

31. Logging
Should be centralized
&
Web accessible

32. Self Hosted
rsyslog logstash
aaS
greylog
scalyr papertrail loggly

33. Graphing
Should be centralized,
Web accessible
&
easy to add metrics

34. Self Hosted
graphite statsd
scalyr
aaS
nagios
new relic cloudwatch

35. Alerting
Should be escalating
&
reliable

36. Self Hosted
(don’t)
aaS
opsgenie pingdom cloudwatch

37. Deployment

38. Make the
Feedback Loop
Shorter

39. Artists have a very short
feedback loop

40. programmers, not so much
xkcd.com

41. need
we
to change this

42. are
we
changing this

43. Computer scientists have been
reducing the time to iteration
ny
ago
Rewiring circuits
Punching cards
ror
hor
Waiting for turn at the terminal

44. ble
ara
be
Your own PC!
Compile software
ool
c
Dynamic languages!
Deploy software
a
e!
som
we
Continuous Deployment

45. minimum viable
product
continuous
integration
continuous
deployment

46. Example!

47. How about
Instagram?

48. three dudes and an idea...
hacked over a couple of weeks
BOOM!
Massive growth!

49. Oh oh...
How do you avoid downtime?
How do you continue to deliver features?
How do you keep in front when 200 people
copy your app?

50. DevOps

51. let’s get
practical

53. chef server
nodes
workstation

54. bring your own chef server
nginx
Web UI
Erchef
search index
PostgreSQL
Bookshelf
cookbooks

55. hosted chef...
aka: I’m too lazy to install all that stuff
it’s free up to five machines
all the work is done!

56. first steps...
Register your account in Hosted Chef
Clone the official Opscode Repo (Git)
Download the three magical files
knife.rb, validation-key.pem, USER.pem

57. chef server
nodes
workstation

58. each machine controlled by the
chef server is called
node

59. each node authenticates with the
chef server via RSA keys
after that, the node connects periodically to:
update attributes
execute the run-list
... and other stuff

60. chef server
nodes
workstation

61. each machine with the rights to
control the chef server is a
workstation

62. we use
knife
to give instructions
to the chef server

63. well, it’s more like a...

64. cookbooks
recipes
attributes
roles

65. cookbook
a
is
the fundamental unit of
configuration of chef

66. you can create a new cookbook with knife
$ knife cookbook create ntp
or install one from the community
$ knife cookbook site install nginx

67. $ ls -l cookbooks/ntp
CHANGELOG.md
README.md
attributes/
definitions/
files/
libraries/
metadata.rb
providers/
recipes/
/default.rb
resources/
templates/

68. $ cat metadata.rb
name "Chuck Norris"
maintainer "Chuck Norris"
maintainer_email "chuck@norris.com"
license "WTF Public License"
version "1.0.0"
depends "sudo"

69. after coding, remember
to upload it to the
chef server!
$ knife cookbook upload nginx

70. cookbooks
recipes
attributes
roles

71. a cookbook is divided
into recipes,
these are just Ruby code

72. $ cat ntp/recipes/default.rb
package "ntp" do
action :install
end
template "/etc/ntp.conf" do
source "ntp.conf.erb"
mode 0644
owner "root"
group "root"
notifies :restart, "service[ntpd]")
end
service "ntpd" do
action [:enable, :start]
end

73. $ cat ntp/templates/ntp.conf.erb
# This file was generated by Chef for
# Machine:'<%= node['fqdn'] %>'.
# Do NOT edit this file by hand!
restrict default kod nomodify notrap nopeer noquery
restrict -6 default kod nomodify notrap nopeer
noquery
restrict 127.0.0.1
restrict -6 ::1
server '0.pool.ntp.org'
server 127.127.1.0
driftfile /var/lib/ntp/drift
keys /etc/ntp/keys

74. cookbooks
recipes
attributes
roles

75. an attribute is a piece of data about
the node, such as a network interface or
the IP to bind a service

76. $ cat ntp/attributes/default.rb
default["ntp"]["server1"] = "0.pool.ntp.org"
default["ntp"]["server2"] = "127.127.1.0"
the attributes can be
overridden in multiple levels

77. cookbooks
recipes
attributes
roles

78. collections of
cookbooks to execute
and attributes to apply

79. $ cat ../roles/ntp-server.rb
name "ntp-server"
description "NTP Server"
run_list(
"recipe[ntp]",
"recipe[ntp::default]"
)

80. ok, ok...
but, how can I create
a new node?

81. just create a new clean machine and...
on vagrant/virtualbox/“normal server”/...
$ knife bootstrap localhost
--ssh-user vagrant --ssh-password vagrant
--ssh-port 2222 --sudo --run-list "recipe[ntp]"
on EC2
$ knife ec2 server create -r 'role[ntp-server]'
-I ami-3d4ff254 -x ubuntu -i KEY -g GROUP

82. demooooooooo

83. cloud
services

84. cloud computing is the use of
computing resources that are delivered
as a service over a network (typically
the Internet)
- wikipedia

85. gce
rackspace

87. RDS
EBS
VPC
SNS
CloudFront
CloudWatch
EC2
SQS
SES S3
Elastic Cache
Route53
SWF
ELB
DynamoDB
Glacier
Auto Scaling
Elastic Beanstalk Cloud Formation

88. EC2 is the cloud computing
solution of AWS,
you give them money,
they give you machines

89. S3 is the massive data store
solution of AWS,
you give them money,
they store your files

90. RDS is the relational
database solution of AWS,
you give them money,
they manage your DB

91. ELB is the load balancer
solution of AWS,
you give them money,
they balance your load

92. Auto Scaling is the automatic,
load sensitive machine
provisioning solution of AWS,
you give them money,
they give you machines on load

93. talk is cheap
show me the code

94. questions?

95. thanks for coming