10分でわかるDevOps
Upcoming SlideShare
Loading in...5
×
 

10分でわかるDevOps

on

  • 11,203 views

http://togetter.com/li/153695 も併せてご覧下さい。

http://togetter.com/li/153695 も併せてご覧下さい。

Statistics

Views

Total Views
11,203
Views on SlideShare
7,567
Embed Views
3,636

Actions

Likes
5
Downloads
34
Comments
1

17 Embeds 3,636

http://d.hatena.ne.jp 3331
http://marqs.hatenablog.com 148
http://coderwall.com 90
http://infra.rrdtool.net 16
url_unknown 14
http://webcache.googleusercontent.com 9
http://www.slideshare.net 7
http://paper.li 7
https://twitter.com 4
http://twitter.com 3
http://news.taaza.com 1
http://rss.ameba.jp 1
http://translate.googleusercontent.com 1
http://cc.bingj.com 1
http://www.freerss.net 1
https://twimg0-a.akamaihd.net 1
http://blog.akuwano.net 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

10分でわかるDevOps 10分でわかるDevOps Presentation Transcript

  • 10分でわかるDevOps
    2011/6/24
    (株)paperboy&co.
    宮下 剛輔
  • DevOps?
    なにそれという人?
  • Devな人?
  • Opsな人?
  • DevでもOpsでも
    ある人?
  • DevでもOpsでも
    ない人?
  • DevOps?
  • 2009年始め頃
  • Patrick Debois氏
  • Agile InfrastructureAgile Operations
    からの流れ
  • 2009年後半のDevOps Days in Ghentで広まる
  • Velocity 2009での
    JohnAllspaw氏の
    プレゼン
  • 10+ Deploys Per Day:
    Dev and Ops Cooperation at Flickr
  • DevOpsの解釈は
    いくつかありそう
  • Infrastructure as Code
  • 仮想化
    IaaS
    PaaS
  • NoOps
  • DevOpsとは?
  • 開発者と運用者の
    より良い関係
  • Dev vs. Ops
  • 守備範囲の違い
  • 方向性の違い
  • こういった境界線で
    対立が生まれる
  • exclusive
  • inclusive
  • John Allspaw氏の
    コメントから引用
  • It's not abstraction.
  • It's not even "infrastructure as code".
  • It's not any single tool.
  • It's not about provisioning.
  • It's not about deployment.
  • It's not about a job description or position.
  • It's also not about
    the cloud
  • It *is* about the collaborative and communicative culture
  • and the tools and process that arise from that culture.
  • Nothing more.