mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-29 21:41:00 +08:00
85 lines
7.3 KiB
Markdown
85 lines
7.3 KiB
Markdown
|
13 tools to measure DevOps success
|
||
|
|
======
|
||
|
|
How's your DevOps initiative really going? Find out with open source tools
|
||
|
|
|
||
|
|
|
||
|
|
In today's enterprise, business disruption is all about agility with quality. Traditional processes and methods of developing software are challenged to keep up with the complexities that come with these new environments. Modern DevOps initiatives aim to help organizations use collaborations among different IT teams to increase agility and accelerate software application deployment.
|
||
|
|
|
||
|
|
How is the DevOps initiative going in your organization? Whether or not it's going as well as you expected, you need to do assessments to verify your impressions. Measuring DevOps success is very important because these initiatives target the very processes that determine how IT works. DevOps also values measuring behavior, although measurements are more about your business processes and less about your development and IT systems.
|
||
|
|
|
||
|
|
A metrics-oriented mindset is critical to ensuring DevOps initiatives deliver the intended results. Data-driven decisions and focused improvement activities lead to increased quality and efficiency. Also, the use of feedback to accelerate delivery is one reason DevOps creates a successful IT culture.
|
||
|
|
|
||
|
|
With DevOps, as with any IT initiative, knowing what to measure is always the first step. Let's examine how to use continuous delivery improvement and open source tools to assess your DevOps program on three key metrics: team efficiency, business agility, and security. These will also help you identify what challenges your organization has and what problems you are trying to solve with DevOps.
|
||
|
|
|
||
|
|
### 3 tools for measuring team efficiency
|
||
|
|
|
||
|
|
Measuring team efficiency—in terms of how the DevOps initiative fits into your organization and how well it works for cultural innovation—is the hardest area to measure. The key metrics that enable the DevOps team to work more effectively on culture and organization are all about agile software development, such as knowledge sharing, prioritizing tasks, resource utilization, issue tracking, cross-functional teams, and collaboration. The following open source tools can help you improve and measure team efficiency:
|
||
|
|
|
||
|
|
* [FunRetro][1] is a simple, intuitive tool that helps you collaborate across teams and improve what you do.
|
||
|
|
* [Kanboard][2] is a [kanban][3] board that helps you visualize your work in progress to focus on your goal.
|
||
|
|
* [Bugzilla][4] is a popular development tool with issue-tracking capabilities.
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
### 6 tools for measuring business agility
|
||
|
|
|
||
|
|
Speed is all that matters for accelerating business agility. Because DevOps gives organizations capabilities to deliver software faster with fewer failures, it's fast gaining acceptance. The key metrics are deployment time, change lead time, release frequency, and failover time. Puppet's [2017 State of DevOps Report][5] shows that high-performing DevOps practitioners deploy code updates 46x more frequently and high performers experience change lead times of under an hour, or 440x faster than average. Following are some open source tools to help you measure business agility:
|
||
|
|
|
||
|
|
* [Kubernetes][6] is a container-orchestration system for automating deployment, scaling, and management of containerized applications. (Read more about [Kubernetes][7] on Opensource.com.)
|
||
|
|
* [CRI-O][8] is a Kubernetes orchestrator used to manage and launch containerized workloads without relying on a traditional container engine.
|
||
|
|
* [Ansible][9] is a popular automation engine used to automate apps and IT infrastructure and run tasks including installing and configuring applications.
|
||
|
|
* [Jenkins][10] is an automation tool used to automate the software development process with continuous integration. It facilitates the technical aspects of continuous delivery.
|
||
|
|
* [Spinnaker][11] is a multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers.
|
||
|
|
* [Istio][12] is a service mesh that helps reduce the complexity of deployments and eases the strain on your development teams.
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
### 4 tools for measuring security
|
||
|
|
|
||
|
|
Security is always the last phase of measuring your DevOps initiative's success. Enterprises that have combined development and operations teams under a DevOps model are generally successful in releasing code at a much faster rate. But this has increased the need for integrating security in the DevOps process (this is known as DevSecOps), because the faster you release code, the faster you release any vulnerabilities in it.
|
||
|
|
|
||
|
|
Measuring security vulnerabilities early ensures that builds are stable before they pass to the next stage in the release pipeline. In addition, measuring security can help overcome resistance to DevOps adoption. You need tools that can help your dev and ops teams identify and prioritize vulnerabilities as they are using software, and teams must ensure they don't introduce vulnerabilities when making changes. These open source tools can help you measure security:
|
||
|
|
|
||
|
|
* [Gauntlt][13] is a ruggedization framework that enables security testing by devs, ops, and security.
|
||
|
|
* [Vault][14] securely manages secrets and encrypts data in transit, including storing credentials and API keys and encrypting passwords for user signups.
|
||
|
|
* [Clair][15] is a project for static analysis of vulnerabilities in appc and Docker containers.
|
||
|
|
* [SonarQube][16] is a platform for continuous inspection of code quality. It performs automatic reviews with static analysis of code to detect bugs, code smells, and security vulnerabilities.
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
**[See our related security article,[7 open source tools for rugged DevOps][17].]**
|
||
|
|
|
||
|
|
Many DevOps initiatives start small. DevOps requires a commitment to a new culture and process rather than new technologies. That's why organizations looking to implement DevOps will likely need to adopt open source tools for collecting data and using it to optimize business success. In that case, highly visible, useful measurements will become an essential part of every DevOps initiative's success
|
||
|
|
|
||
|
|
### What to read next
|
||
|
|
|
||
|
|
--------------------------------------------------------------------------------
|
||
|
|
|
||
|
|
via: https://opensource.com/article/18/10/devops-measurement-tools
|
||
|
|
|
||
|
|
作者：[Daniel Oh][a]
|
||
|
|
选题：[lujun9972](https://github.com/lujun9972)
|
||
|
|
译者：[译者ID](https://github.com/译者ID)
|
||
|
|
校对：[校对者ID](https://github.com/校对者ID)
|
||
|
|
|
||
|
|
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||
|
|
|
||
|
|
[a]: https://opensource.com/users/daniel-oh
|
||
|
|
[1]: https://funretro.io/
|
||
|
|
[2]: http://kanboard.net/
|
||
|
|
[3]: https://en.wikipedia.org/wiki/Kanban
|
||
|
|
[4]: https://www.bugzilla.org/
|
||
|
|
[5]: https://puppet.com/resources/whitepaper/state-of-devops-report
|
||
|
|
[6]: https://kubernetes.io/
|
||
|
|
[7]: https://opensource.com/resources/what-is-kubernetes
|
||
|
|
[8]: https://github.com/kubernetes-incubator/cri-o
|
||
|
|
[9]: https://github.com/ansible
|
||
|
|
[10]: https://jenkins.io/
|
||
|
|
[11]: https://www.spinnaker.io/
|
||
|
|
[12]: https://istio.io/
|
||
|
|
[13]: http://gauntlt.org/
|
||
|
|
[14]: https://www.hashicorp.com/blog/vault.html
|
||
|
|
[15]: https://github.com/coreos/clair
|
||
|
|
[16]: https://www.sonarqube.org/
|
||
|
|
[17]: https://opensource.com/article/18/9/open-source-tools-rugged-devops
|