市場調査レポート

DevOps市場の動向:2011年

DevOps

発行 Ovum, Ltd. 商品コード 139899
出版日 ページ情報 英文 26 Pages
納期: 即日から翌営業日
価格
こちらの商品の販売は終了いたしました。
Back to Top
DevOps市場の動向:2011年 DevOps
出版日: 2010年10月20日 ページ情報: 英文 26 Pages

当商品の販売は、2016年07月01日を持ちまして終了しました。

概要

現在はDevOpsの初期段階であり、その性質、範囲、目的はいまだ流動的なものとなっております。企業やベンダーの注目度が高まっており、DecOpsは徐々に勢いを増すと考えられます。

当レポートでは、DevOpsへの動きの様々な側面について考察するとともに、企業のIT開発や事業活動への関わりについてまとめ、概略下記の構成でお届けいたします。

第1章 サマリー

  • 発展要因
  • OVUMの見解
  • 主なメッセージ

第2章 OpsとDevsの統合

  • 逆機能から連携へ
  • 責任ある連携の構築
  • 連携中心のプロセスとツールの構築

第3章 Devsから取り入れるOps

  • Devsから学ぶOps
  • アジャイルなDevsからアジャイルなOpsへ
  • ALMはDevsからOpsへ
  • DevOpsが企業のOpsに接触するにはメッセージを調整する必要がある

第4章 DevOpsの出現

  • 語弊があるが便利なラベル
  • ボトムアップの動きは加速している

第5章 クラウド・コンピューティングを包含するDevOps

  • クラウド・コンピューティングより前から存在する動向を基にする
  • パブリック・クラウドにより促進されるDevOps
  • プライベート・クラウドを促進するDevOps

第6章 提案

  • 企業への提案
  • ベンダーへの提案

付録

目次
Product Code: OI00005-001

Abstract

Introduction
It is early days for the DevOps movement. Its nature, scope, and ambitions are still in flux. Some of its ideas are old (for example, Ops-Devs collaboration), while others are leading edge (such as cloud-based API-centric Ops). Enterprises and vendors alike should start paying attention to both types of ideas, as we expect the DevOps movement to slowly gain momentum.

Features and benefits
The report provides an overview of the various facets of the DevOps movement and puts these facets in context.
The report enables enterprises to figure out how and to what extent DevOps relates to their own IT development and operations activities.

Highlights
The DevOps movement acknowledges that the relationship between Dev and Ops teams is usually rather dysfunctional. It provides a space where Ops and an increasing number of Devs can provide ideas on how to repair the relationship.

While IBM and Microsoft talk about Dev and Ops collaboration in generic terms and believe that such a collaboration has time to build up, the DevOps message is different in terms of focus (it is largely cloud computing centric) and urgency (it emphasizes the need to start at once).

The DevOps debate talks about the convergence between Devs and Ops from various angles. One of the most important emphasizes the need for production systems (both physical and virtual) to be designed in the context of the infrastructure that underpins them and the Ops tools that manage them.

Your key questions answered
What is the DevOps movement about? What are its strengths and weaknesses?
What are the chances of success for the DevOps movement, and why?
How does DevOps relate to ALM, Agile development, ITSM, and ITIL?

Table of Contents

SUMMARY
Catalyst
Ovum view
Key messages
OPS GETS TOGETHER WITH DEVS
From dysfunction to collaboration
DevOps is about repairing the dysfunctional devs/ops relationship
Many vendors have tried, and so far failed, to repair this relationship
The DevOps movement is trying again
DevOps is about an API- and application-centric view of ops
Building an accountable collaboration
Weaving collaboration at all levels
Making collaboration accountable
DevOps is more than a job description
Multi-skilled individuals might help - within limits
Separation of concerns and division of labor should remain key objectives
DevOps should move beyond sysadmins versus devs
Building collaboration-centric processes and tools
Process-centric collaboration: narrow application delivery/deployment focus
Process-centric collaboration: broad cradle-to-grave focus
Taking into account generic application issues
Tool-centric collaboration
OPS BORROWS FROM DEVS
Ops to learn from devs
Inspiration: Ops to reuse proven devs ideas
Convergence: Ops are becoming more like devs
Ops programming skills to improve
Ops scripts to become business assets as important as application code
Ops scripts becoming policies
From Agile devs to Agile ops
Agile development has become mainstream
DevOps wants Agile operations to become mainstream too
ITIL is less an obstacle than it appears
Focus on metrics needs to increase
ALM from devs to ops
Devs ALM focuses on process automation
Ops ALM focuses on tool integration
Ops ALM focuses on application delivery-centric automation
DevOps needs to move from upfront to retrofitted automation
API-centric ops tools will take time to emerge…
…as will ops ALM metadata management…
…and ops ALM infrastructure services
DevOps needs to calibrate its messages to reach out to enterprise ops
DevOps is about potential, not shortcomings
Ops can teach devs a thing or two
DevOps needs to focus on job evolution
Charity begins at home
DEVOPS IS EMERGING
A misleading but useful label
DevOps is about ops first, devs second
DevOps is about ops learning from, and working with, devs
A useful label
A bottom-up challenged movement gathering pace
Young and attractive
Fledgling, dismissed, worth paying attention to
The confusion that surrounds DevOps will continue but can be reduced
DEVOPS EMBRACES CLOUD COMPUTING
Builds on trends that predate cloud computing
SOA and virtualization have changed IT
IT has become shared and service-centric
Ops have had to adapt
DevOps is driven by public clouds
Inspired by public cloud service providers
Inspiring public cloud service providers
DevOps will drive private clouds…
…for enterprise IT to keep up with the public cloud Jones
…for ops to promote and adapt to API-centric private clouds
…for ops to deliver self-service, on-demand cloud provisioning now
…from a business-centric perspective
RECOMMENDATIONS
Recommendations for enterprises
Reach out to DevOps
Build an accountable, collaborative DevOps team
Be aware of the shortcomings of the DevOps debate
Recommendations for vendors
Clearly identify your approach
Less hype is more
Be bold
APPENDIX
Further reading
Author
Ovum Consulting
Disclaimer

Back to Top