一千萬個為什麽

搜索

“DevOps轉型”包含什麽?



一些咨詢公司正在推廣名為“DevOps Transformation”的服務。多家大公司在世界各地的會議和聚會上討論這個問題。

這種“DevOps轉型”帶來了什麽? 它是如何以可執行的術語出現的,無論是成功轉型還是失敗。

轉載註明原文: “DevOps轉型”包含什麽?

一共有 2 個回答:

我需要在DevOps的背景下回答這個問題,更具體地說,在我參與的DevOps轉型中,DevOps是完整的軟件開發生命周期的所有權。圖表中的所有實踐都是DevOps的重要組成部分,它們支持和支持兩種方法。系統思考和反饋循環的放大

然而,CI/CD和DevOps之間的關鍵區別在於生產環境中軟件的實際操作,它可以為客戶及其所服務的業務提供價值。

DevOps Lifecycle

作為參與或領導DevOps轉型的顧問,我有以下幾方面的想法:

  • 文化:正如 Dave正確指出 a 持續實驗與學習文化對於任何轉型的成功至關重要。從DevOps的角度來看,這涉及到我們如何創建一種支持所選DevOps模型的文化,這種模式可能是“您構建它,您運行它”,或者它可能更符合Google的 Site Reliability Engineering 練習。

  • 運營模式:這是商業命題的一部分,它闡明了組織如何實現價值,通常通過闡述在較高層次上捆綁在一起的人員,流程和工具。如果沒有運作模式,你就沒有藍圖來說明組織采用文化定義的做法的方式,這反過來又導致了缺乏明確和不同的行為。

    你會打亂人們,有些人不會喜歡這些變化 - 重要的是你要從上面“空中掩蓋”來改變事情並向前發展。

一旦達到最高水平,重要的是要找到你可以切實實現的東西:

  1. Start as small as possible, ideally, once you have some people who understand the culture, a sketch of an operating model and buy-in from the executives create the "Minimum Viable Project", don't attempt to boil the ocean by introducing DevOps to an audience of thousands. Set an achievable goal:
    • Automate the creation of the infrastructure from Product X.
    • Automate the delivery of Product X into Azure across all environments.
    • Hand-back support from outsourcer Y to a development team in London.
    • Create a set of tests around our riskiest feature and run them in continuous integration.
  2. Great you have some success under your belt now it is time to start baking this into more teams, add another couple of teams into the mix and get them up and running. Don't be afraid to offer "White Glove Support" at first to assist them in the transition; they will need a lot of hand-holding over the coming weeks and months.
  3. Now you have several early adopters following a new way of working; you have some critical mass, it is time to start evangelising the work you are doing with a wider audience:
    • Hold regular show-and-tell sessions ask the early adopters to demonstrate how successful they have been.
    • Offer drop-in sessions to allow other parts of the organisation to explore how they can come on board with your team.
    • Enable the creation of Communities of Practice focusing on specific disciplines: Continuous Deployment, Automated Testing, Business Communication, Risk Management, Monitoring and Alerting, etc.
  4. Stay the course and close off the transformation by onboarding the rest of the organisation. Understand the relationship between the Gartner Hype Cycle and the Adoption Lifecycle. Prepare for the Transformation Programme to fall into the "Trough of Disillusionment", stay the course and keep the end goal in sight.

    Gartner Hype Cycle vs. Adoption Curve

想要深入了解最後一點,請閱讀Geoffrey A. Moore的穿越裂縫。我可以毫不誇張地寫一本關於如何實現DevOps轉型的書,但是到我完成它的時候,可能沒有更多的DevOps轉型工作可以做。

DevOps傾向於在三個主要方面分解:

Culture
DevOps culture emphasizes high levels of trust, collaboration and communication between all stakeholders, especially Dev, Ops, and Security. The natural tension and competition between these groups creates friction, and often dysfunction. DevOps is (arguably) first and foremost about aligning efforts between these teams.

Process
DevOps development processes align closely to Agile processes. Ops is encouraged to take up Agile-like practices to better align to Dev efforts. DevOps-aligned processes are designed to support high velocity and fast feedback loops throughout the development/delivery lifecycles. Continuous Integration, Continuous Delivery, and Continuous Improvement (kaizen) are focus areas of DevOps process.

Technology
DevOps isn't a tool, but it is supported by tools. There are whole families of tools supporting a range of areas including Continuous Integration, Source Control, and Application Lifecycle Management.

“DevOps轉型”必須解決所有三個要素,但不一定全部同時處理。有一個自然的進程和轉變的“關鍵路徑”。舉例來說,DevOps依賴於某種形式的敏捷實踐,至少在開發團隊/團隊內部。在進行模具投資之前,可能需要解決文化問題。

References:
Culture: https://www.andykelk.net/devops/using-the-westrum-typology-to-measure-culture
Technology: https://xebialabs.com/periodic-table-of-devops-tools/