2. What’s DevOps?
DevOps is … Collaboration of
‘Development’ and ‘operation’.
Philosophy, Policy, the way of
thinking
Dev: Innovative …
Sometimes, it’s disruptive.
Ops: Stable …
Sometimes, it’s conservative.
3. What’s DevOps?
DevOps is … Collaboration of
‘Development’ and ‘operation’.
Philosophy, Policy, the way of
thinking
DevOps is
NOT …
Automation
Build and Release
Infrastructure Development
System Administration
They are only tools for DevOps.
4. (BTW) How to think about XXX?
At first, Think about our problems and cause.
1. What is the problem and what is the goal.
2. Think about the cause of for each
problems.
3. Set priority for each problems.
4. Get solutions for each problems.
5. (BTW) Example for bad case.
We have many problems at release timing..
I found the solution ‘DevOps’
What’s this?
It will make installation / release
operation more easy.
How do we do DevOps?
The way is 1. xxx, 2.xxxx….
It’s NOT clear what is solved by the solution.
They haven’t understood what is the solution itself.
6. What are our problems?
Problems.
Well, It works on my machine..
It’s not server, It’s your code.
Sorry, please see the server setting by
yourself, I don’t know detail.
We should use same environment local and
Live environment, and guarantee easy installation.
7. Goals
We should make environment as…
1. Same environment Live and Local.
2. Auto deployment and test to make
installation more easily.
3. Auto checking status of the system.
8. What’s DevOps? (2)
Selenium
Unit test
TestFlight
Travis CI
jenkins
Capistrano
Ansible
CloudWatch
ELK
Zabbix
MRTG
SNMP
DockerEC2
Fabric
Chef
Vagrant
1
2
32
1
1
Ci
DevOps
Development
Operation
Immutable infrastructure
Infrastructure as Code
Automatic Installation
Auto-testing
Auto build and test report
deployment as Code
log checking and visualization
9. What’s DevOps? (again)
Think again about DevOps..
“DevOps is an approach to bridge the gap between
agile software development and operations.”
Collaboration mindset of Devs and Ops.
C.A.M.S.
Culture
Automation
Metrics
Sharing
10. DevOps: Culture
Relationship and Communication
Bust Silos and stop finger-pointing
Talk directly
Don’t say “No”
Involve all members
11. DevOps: Automation
XXXX as Code
Infrastructure as Code
Deployment as Code
Test as Code
- Machines are good at doing same
things many times.
- Make XXXX clearly.
Make it automatic.
build, deploy, test, report, monitoring..
- Save time and make tasks efficiently.
12. DevOps: Metrics
Monitor/report status
Build/test report, server status.
Find failure
Getting error when it occur.
Improve
Analysis status and make proper
structure.
Make a plan
Find the point to make it better
from status, and make new design.
13. DevOps: Sharing
Share design of infrastructure. (Ops->Dev)
Infrastructure design and
authorization for shell access of
servers.
Share changes and new functions (Dev->Ops)
What is the point of this release and
what kind of technology we use.
Share metrics.
check status and find failure.
15. The scope of this study
1. Same environment Live and Local.
2. Auto deployment and test to make
installation more easily.
3. Auto checking status of the system.
* ’Gray text’ will be next time…
16. Preparation for next study
1. Install applications
2. Download box image
3. research and learn of key technology
in this paper.
• Virtual Box
• Vagrant
• python
• ansible
• fabric
• CentOS6.5 (https://github.com/2creatives/
vagrant-centos/releases/download/v6.5.3/
centos65-x86_64-20140116.box)
c.f. “Instruction” slide
17. References:
• 10 deploys per day
- dev and ops cooperation at flickr -
( http://www.slideshare.net/jallspaw/10-deploys-per-
day-dev-and-ops-cooperation-at-flickr )
• DevOps
( http://www.slideshare.net/geekle/devops-5348895 )
• How to choose tools devops
( http://www.slideshare.net/matthewskelton/how-to-
choose-tools-for-devops )
There are much more information in the Internet.
Special Thanks : following slides.
The great origin.
I borrowed many phrase from them. Please check them out.