The document discusses how operations teams deliver and operate infrastructures in the real world. It covers topics like provisioning infrastructure using tools like Chef, configuring systems with tools like Puppet and Ansible, implementing automation around areas like monitoring, logging, and testing with tools like Elasticsearch and Test Kitchen. It also discusses concepts like software-defined networking and storage. It emphasizes treating infrastructure as code, building automation pipelines, and integrating operations work with product development.

1. HOW THE OPS TEAMS DELIVERY AND OPERATE
THE INFRASTRUCTURES IN THE REAL WORLD
@mateusprado

2. $ whoami
• Software Engineer
• Co-founder CodeOps
• SRE at Santander Produban
• c, java, ruby, go, python
• <3 storages, servers, distributed systems
• api <3++
• craft beers, bbq
• airplanes

3. Agenda
• Agile?
• Ops work
• Tools
• Agile Infrastructure in the real world

4. “June 2009: At the O'Reilly
Velocity 09 conference”

7. #OLD

11. Your infrastructure is here.

12. Agile Infrastructure
Pero no mucho.

13. [ops-ng]
How the Ops teams delivery
and operate the infrastructures
in the real world

14. OPS WORK

15. DELIVERY

16. KEEP ON

18. DELIVERY

19. Provisioning
Configuration
&

20. provisioning
• bare metal, virtualization
• storage
• network

21. Configuration
• os tuning
• hardening
• compliance rules

22. KEEP ON

23. MONITORING

24. IMPROVEMENTS

25. Metrics
Improvements
Provisioning
Configuration

27. to be Agile
• API
• Code
• API
• Code
• API
• Code

30. AUTOMATION

31. automation
• provisioning: chef, knife bootstrap
• conf management: cfengine, chef, puppet, ansible
• sdn, nfv: openflow
• sds: ceph
• log aggregation: graylog, elk stack
• metrics: libbeat
• qa: kitchen, rubocop, foodcritic

32. provisioning
$ knife vsphere vm clone
--name demoiselle-app-front.qa.chewbacca.local
—template centos7
--datacenter Norte01
--resource-pool QA
--cdomain qa.chewbacca.local
--cvlan hom_10.16.12.0/24
--environment QA
--run_list "role[xemele-app-front]"
--ccpu 4
--cram 4

33. Configuration
Management

34. # chef-recipe
# aws opsworks
directory '/opt/go/bin' do
owner 'demoiselle'
group 'demoiselle'
mode '0644'
action :create
recursive true
end
template '/opt/go/conf/config.toml' do
source 'conf/config.toml.erb'
owner 'demoiselle'
group 'demoiselle'
mode '0644'
action :create
end
package 'demoiselle-front-app' do
action :install
end
package 'nginx' do
action :install
end
service 'nginx' do
action :start
end

35. sdn, nfv

36. software-defined-storage

37. Log Aggregation

41. Metrics

46. QA

48. # .kitchen.yml
driver:
name: vagrant
provisioner:
name: chef_zero
platforms:
- name: ubuntu-12.04
- name: centos-6.4
- name: debian-7.1.0
suites:
- name: default
run_list:
- recipe[demoiselle::frontend]

49. require 'chefspec'
describe 'file::delete' do
let(:chef_run) {
ChefSpec::SoloRunner.new(platform: 'ubuntu',
version: ’16.04’).converge(described_recipe)
}
it 'deletes a file with an explicit action' do
expect(chef_run).to delete_file('/tmp/explicit_action')
expect(chef_run).to_not delete_file('/tmp/not_explicit_action')
end
it 'deletes a file with attributes' do
expect(chef_run).to delete_file('/tmp/with_attributes').with(backup: false)
expect(chef_run).to_not delete_file('/tmp/with_attributes').with(backup:
true)
end
end

51. In the real world
• On demand available whenever
• Ephemeral short periods, disposable, show unused
• Elastic scale, PoC
• Integrate exposed
• Supported owned

52. HIRING

53. Hiring
• Generalists
• Code skill
• Bad apples
• Incentive Transparency
• KPI

54. Tips
• Treat your code as code;
• Build the Ops Pipeline;
• Think about Product and not servers;
• Docs;
• Rollback is a deploy;
• Share the metrics;
• Share the code;

55. Your infrastructure is here.

58. Q&A
Mateus Prado
mateus@codeops.com.br
Twitter: @mateusprado
Slideshare: mateushprado