摘要(中) |
因應現今雲端科技,市場快速變化之環境,個案公司面臨不斷新增的業務需求,及 伺服器數目持續增加,面對頻繁上版及精實成本的壓力,提出雲端服務優化專案,期能 提昇軟體發行頻率及軟體開發品質,並能快速的故障復原。
因此本研究由系統和組織二個層面探討個案公司的雲端服務優化專案所面臨的問 題及衝擊與因應方案。本個案研究主要探討以下三個議題:
1. 個案公司面臨的雲端服務營運優化需求及採取的行動方案。
2. 自動化部署系統對個案公司優化目標之預期貢獻及系統架構議題。 3. 個案公司執行雲端服務優化專案組織調整及變革議題。
個案分析顯示,個案公司為優化雲端服務而導入 DevOps 策略,在管理上的建議應 強化人員、組織結構及組織文化等變革的推動,以期能實現快速回應業務需求及提昇整 體生產力之目標。若只改變作業流程及導入工具,並無法實際此目標。本研究發現對於 未來其他要導入的企業,尤其針對非新創公司或全新系統,而是針對現有系統要導入自 動化部署之企業,提供參考價值。 |
摘要(英) |
Due to advances in cloud computing technology and rapid changes in the marketplace, the company described in this case study faces the following challenges: (1) constantly changing business needs, (2) increasing number of servers, (3) frequent software upgrades, and (4) need to reduce costs. Because of these challenges, the company proposed a cloud computing service optimization project with the objectives of increasing software release frequency, increasing software development quality, and quickly recovery from service interruptions.
Therefore this study looks at the challenges faced, their impacts, and the solutions employed by the company during the course of this cloud computing service optimization project from the systematic and organizational levels. This study focuses on following three key topics:
1. The need for the optimization of cloud service operations and the actions the company took to address those needs.
2. Anticipated contribution of the auto-deployment system to the company’s optimization goals and system architectural issues.
3. Organizational change and team structural change issues faced by the company when implementing the cloud service optimization project.
This case study analyzes the company’s introduction of DevOps strategy to optimize its
cloud services and how changing people, structure, and culture are crucial to organizational change. Without organizational change, cloud computing optimization by itself will not achieve its intended goals. Lastly, this study’s finding is of particular value to existing systems seeking to introduce auto-deployment systems, but not of particular value to startups or new systems. |
參考文獻 |
【英文文獻】
1. Allspaw, F. & Hammond, P. (2009). “10 deploys per day - dev & opscooperation at flickr” http://www.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr, Accessed 2014/10/21.
2. Amazon Web Services, Inc. (2013a). Architecting on AWS (課程教材).
3. Amazon Web Services. (2013b). “AWS Security Best Practices” http://media.amazonwebservices.com/AWS_Security_Best_Practices.pdf, Accessed 2014/12/27.
4. Amazon Web Services. (2014). “Scaling Up to Your First 10 Million Users” http://www.slideshare.net/AmazonWebServices/sov204-scaling-up-to-your-first-10-milli on-users-aws-reinvent-2014-41572495, Accessed 2014/12/27.
5. Bernstein, A. (2013). “Puppet - Configuration Management Made Eas(ier)” http://www.slideshare.net/bernstein_aaron/puppet-introduction-26593192, Accessed 2014/10/22.
6. Farroha, B., & Farroha, D. (2014). “A Framework for Managing Mission Needs, Compliance, and Trust in the DevOps Environment.” In 2014 IEEE Military Communications Conference (MILCOM), 288-293.
7. Gartner, Inc. (2014a). “Forecast Overview: Public Cloud Services, Worldwide, 2014 Update” https://www.gartner.com/doc/2842018/forecast-overview-public-cloud-services, Accessed 2014/12/24.
8. Gartner, Inc. (2014b). “Magic Quadrant for Cloud Infrastructure as a Service” http://www.gartner.com/technology/reprints.do?id=1-1UKQQA6&ct=140528&st=sb, Accessed 2014/10/19.
9. Herry, H., Anderson, P., & Wickler, G. (2011). “Automated planning for configuration changes.” In Proceedings of the 2011 LISA Conference.
10. Hou, Z., Tie, J., Zhou, X., Foster, I., & Wilde, M. (2009). “ADEM: automating deployment and management of application software on the open science grid.” In 2009 10th IEEE/ACM International Conference on Grid Computing, 130-137.
11. Hüttermann, M. (2012). DevOps for Developers. United States of America: Appress.
12. Juve, G., & Deelman, E. (2011). “Automating application deployment in infrastructure clouds.” In 2011 IEEE Third International Conference on Cloud Computing Technology and Science (CloudCom), 658-665.
13. Mell, P., & Grance, T. (2011). “The NIST definition of cloud computing.”
14. Puppet Labs. (2013). “Continuous Delivery — What It Is and How to Get Started” http://info.puppetlabs.com/download-free-continuous-delivery-ebook.html, Accessed 2014/10/19.
15. Puppet Labs. (2014a). “What is Puppet?” http://puppetlabs.com/puppet/what-is-puppet, Accessed 2014/05/22.
16. Puppet Labs. (2014b). “Puppet Camp Boston 2014: Keynote” http://www.slideshare.net/PuppetLabs/puppet-camp-intro-keynote-patrickmaddox, Accessed 2014/10/01.
17. Puppet Labs. (2014c). “Puppet Labs Documentation” https://docs.puppetlabs.com/#puppetpuppet, Accessed 2014/10/01.
【中文文獻】
1. 中山大學企業管理學系 (2007),管理學:整合觀點與創新思維,台北:前程文化。
2. 李建興 (2014),「DevOps 將顛覆未來 IT 人角色」http://www.ithome.com.tw/news/87144, Accessed 2014/12/12.
3. 林建煌 (2013),管理學,台北:華泰文化事業股份有限公司。
4. 葉匡時、俞慧芸 (2004),EMBA 的第一門課,台北:臺灣商務。 |