mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-25 23:11:02 +08:00
TSL
This commit is contained in:
Xiaobin.Liu
parent
7b2768367d
commit
ab58659226
@ -1,109 +0,0 @@
|
||||
[#]: subject: "Open source DevOps tools in a platform future"
|
||||
[#]: via: "https://opensource.com/article/22/10/open-source-devops-tools"
|
||||
[#]: author: "Will Kelly https://opensource.com/users/willkelly"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "lxbwolf "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Open source DevOps tools in a platform future
|
||||
======
|
||||
|
||||
The open source roots of DevOps tools are undeniable, even with a prediction that the global DevOps market will reach $17.8 billion by 2026. The changing world of work, security, and compliance concerns, along with venture capital firms, are pushing the market to DevOps platforms where development teams can access a complete end-to-end DevOps toolchain in the cloud.
|
||||
|
||||
### The current state of open source DevOps tools
|
||||
|
||||
Let's get one thing straight: There's no way open source tools will disappear from the DevOps world. Right now, there's a balance between open source and vendor DevOps tools, with developers using what works for them. Indeed, there are plenty of cases when a development team chooses an open source tool for their DevOps pipeline only to upgrade later to a commercial version.
|
||||
|
||||
### 3 examples of open source DevOps tools
|
||||
|
||||
Here are some examples of open source DevOps tools with a commercial business built around them.
|
||||
|
||||
#### Git
|
||||
|
||||
[Git][1]–the source code management tool–is probably one of the main foundations for DevOps toolchains serving as a source code repository.
|
||||
|
||||
The two best commercial examples of Git are GitLab and GitHub. GitLab [accepts contributions][2] to its open source project. GitHub is embarking on an effort to become a DevOps platform as well with the launch of GitHub Copilot–an AI pair programmer–launching to mixed reviews and criticism from some open source groups.
|
||||
|
||||
#### Jenkins
|
||||
|
||||
An open source automation server, Jenkins is prized for its easy installation, configuration, and extensibility.
|
||||
|
||||
CloudBees offers JenkinsX, an open-source solution that provides automated continuous integration and continuous delivery (CI/CD) and automated testing tools for cloud-native applications on Kubernetes. They also provide commercial support for JenkinsX, including:
|
||||
|
||||
- Access to CloudBees technical expertise
|
||||
- 24x7 technical support
|
||||
- Access to CloudBees documentation and online knowledge base
|
||||
|
||||
#### Kubernetes
|
||||
|
||||
The growth of [Kubernetes][3] is undeniable as more organizations seek an enterprise-grade container orchestration solution. Despite criticisms about its complexity, Kubernetes
|
||||
|
||||
There's an entire burgeoning industry around Kubernetes, and with good reason. According to Allied Market Research, the global container and [Kubernetes security][4] market was valued at $714 million in 2020 and is projected to reach $8242 million by 2030.
|
||||
|
||||
### DevOps toolchains today
|
||||
|
||||
There are still plenty of build-your-own (BYO) CI/CD toolchains in play across industries. The open source projects powering DevOps functions are still prospering,
|
||||
|
||||
BYO toolchains are integration-ready and very extensible, which has always been a strength for organizations continuing to iterate on their DevOps practices. The lack of a standard bill of materials might prove troublesome in enterprises seeking standardization for business, IT, and security reasons.
|
||||
|
||||
While the advent of DevOps platforms isn't going unnoticed, many organizations migrated their CI/CD toolchains to the public cloud well before the pandemic. The security of the toolchain itself has long been a rising concern, and public cloud infrastructure provides Identity Access Management (IAM) and other security features to control access.
|
||||
|
||||
### DevOps platforms: Friend or foe?
|
||||
|
||||
A DevOps platform is an end-to-end solution that places all functions of the CI/CD toolchain into the cloud. Examples of DevOps platforms include GitLab and Harness. GitHub is also making moves to become a DevOps platform in its own right.
|
||||
|
||||
#### Advantages (even if only in the eyes of enterprise buyers)
|
||||
|
||||
DevOps platforms are attractive to enterprise buyers who are already comfortable with the consumption-based and subscription-based pricing of the SaaS and cloud industries. Concerns about maintenance, security, compliance, and developer productivity are certainly at the top of mind for technology leaders in this remote and hybrid work world. Standardizing on a DevOps platform becomes an appealing story to these people.
|
||||
|
||||
#### Disadvantages
|
||||
|
||||
Age-old concerns about vendor lock-in come to mind when depending on a vendor for a DevOps toolchain. The extensibility of development teams building and maintaining their toolchains isn't going to be quite the experience as it was when they made their toolchains from scratch, much less bringing in new tools to improve their workflows.
|
||||
|
||||
There are also potential economic disadvantages with DevOps platform providers. Think what might happen to an overvalued DevOps tools startup that doesn't meet its investors' lofty financial goals. Likewise, there could be smaller startup vendors that may not receive their next round of funding and fade away into irrelevance.
|
||||
|
||||
While the advent of a DevOps platform makes sense in many ways, it does work against the open source ethos that has helped build the DevOps tools we use today.
|
||||
|
||||
### DevOps tools: An inflection point
|
||||
|
||||
Security and compliance concerns for DevOps toolchains continue to mount as working models change. It's only natural.
|
||||
|
||||
#### The changing world of work
|
||||
|
||||
How we work affects DevOps teams just like the rest of the enterprise. Remote and hybrid DevOps teams require secure toolchains. Changing collaboration and reporting requirements across the pipelines are also growing necessities, such as asynchronous work and executives demanding a return to the office.
|
||||
|
||||
#### Software supply chain security market
|
||||
|
||||
The software supply chain security market draws much attention after high-profile attacks and the federal government response. No organization has yet to blame open source for a software supply chain attack, but we're going to see an extension of DevOps/DevSecOps practices and tools to combat this threat. When it's all said and done, though, DevOps/DevSecOps tools and practices will outlast some startups that pivoted to the trend.
|
||||
|
||||
### Final thoughts
|
||||
|
||||
It's far from game over for OSS projects in the DevOps space, but DevOps stakeholders have a right to start asking questions about the toolchains of the future. However, OSS DevOps projects do need to consider their future, especially in light of growing security and compliance concerns that directly impact pipelines.
|
||||
|
||||
There's a future of coopetition where the DevOps platform providers donate time, money, and resources to the open source tools that serve as a foundation for their platforms. An interesting example of a potential future is [OpsVerse][5], which offers a DevOps platform with open source tools they manage for their customers.
|
||||
|
||||
Then again, there's also a future where the open source DevOps tools projects continue to prosper and innovate as more enterprise-built toolchains migrate to the cloud in more significant numbers.
|
||||
|
||||
**[ Kickstart an organizational culture change. Read the first article in a series, [DevSecOps: 5 tips for seeding a culture transformation][6] ]**
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/10/open-source-devops-tools
|
||||
|
||||
作者：[Will Kelly][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者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/willkelly
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/article/22/4/our-favorite-git-commands
|
||||
[2]: https://opensource.com/article/19/9/how-contribute-gitlab
|
||||
[3]: https://opensource.com/resources/what-is-kubernetes
|
||||
[4]: https://enterprisersproject.com/article/2019/1/kubernetes-security-4-tips-manage-risks?intcmp=7013a000002qLH8AAM
|
||||
[5]: https://www.opsverse.io/
|
||||
[6]: https://www.redhat.com/architect/devsecops-culture?intcmp=7013a000002qLH8AAM
|
||||
@ -0,0 +1,109 @@
|
||||
[#]: subject: "Open source DevOps tools in a platform future"
|
||||
[#]: via: "https://opensource.com/article/22/10/open-source-devops-tools"
|
||||
[#]: author: "Will Kelly https://opensource.com/users/willkelly"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "lxbwolf "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
平台化未来的开源DevOps工具
|
||||
======
|
||||
|
||||
DevOps 的开源根基是无法动摇的，即便有预言称全球的 DevOps 市场将在 2026 年之前达到 178 亿美元。不断变化的工作环境、安全和合规性问题，以及风险投资公司等等因素正在将市场推向 DevOps 平台，开发团队可以在云中获得完整的端到端 DevOps 工具链。
|
||||
|
||||
### 开源 DevOps 工具现状
|
||||
|
||||
我们要搞清楚一件事：开源工具不可能从 DevOps 世界中消失。现在，在开源和供应商提供的 DevOps 工具之间存在着一种平衡，开发人员会在两者间选择适合他们的工具。事实上，很多情况下，一个开发团队起初会为他们的 DevOps 流水线选择一个开源工具，后来又升级到商业版本。
|
||||
|
||||
### 三种开源 DevOps 工具实例
|
||||
|
||||
下面我们介绍一些开源 DevOps 工具的例子，每种工具都已经有了围绕其建立的商业化生态。
|
||||
|
||||
#### Git
|
||||
|
||||
[Git][1]——源代码管理工具——可能是作为源代码库的 DevOps 工具链的主要基建之一。
|
||||
|
||||
Git 的两个最佳商业案例是 GitLab 和 GitHub。GitLab [接受开发者对其贡献开源项目][2]。GitHub 也在着手努力成为一个 DevOps 平台，推出了 GitHub Copilot——结对编程的人工智能虚拟版——推出后受到了一些开源团体的褒贬不一的评价。
|
||||
|
||||
#### Jenkins
|
||||
|
||||
作为一个开源的自动化服务，Jenkins 因其易于安装、配置和可扩展性而受到推崇。
|
||||
|
||||
CloudBees 发布了 JenkinsX，JenkinsX 是一套开源的解决方案，可以为 Kubernetes 上的云原生应用提供自动化持续集成和持续交付（CI/CD）以及自动化测试工具。他们还为JenkinsX 提供商业支持，包括：
|
||||
|
||||
- 访问 CloudBees 的专业技术技能
|
||||
- 24x7 技术支持
|
||||
- 访问 CloudBees 的文档和在线知识库
|
||||
|
||||
#### Kubernetes
|
||||
|
||||
随着越来越多的组织寻求企业级的容器编排解决方案，[Kubernetes][3] 的发展成为必然。尽管有人批评其复杂性，但 Kubernetes
|
||||
|
||||
Kubernetes 周边有完整的、蓬勃发展的产业，并且没有消亡理由。根据 Allied 市场调研的数据，全球容器和 [Kubernetes 安全][4]市场在 2020 年的估值为 7.14 亿美元，预计到 2030 年将达到 8.42 亿美元。
|
||||
|
||||
### 目前的 DevOps 工具链
|
||||
|
||||
各个行业仍有很多自建（BYO）的 CI/CD 工具链在发挥作用。支持 DevOps 功能的开源项目仍在蓬勃发展。
|
||||
|
||||
BYO 工具链可以集成其他工具，而且非常具有扩展性，这对于持续迭代其 DevOps 实践的组织来说一直是一个优势。在出于业务、IT 和安全原因寻求标准化的企业中，缺乏标准的材料清单可能是个麻烦。
|
||||
|
||||
虽然 DevOps 平台的出现并没有被忽视，但许多组织早在大流行之前就将他们的 CI/CD 工具链迁移到了公共云。长期以来，工具链本身的安全性一直是一个不断上升的问题，而公共云基础设施提供了身份访问管理（IAM）和其他安全功能来控制访问。
|
||||
|
||||
### DevOps 平台是敌是友？
|
||||
|
||||
DevOps 平台是一个端到端的解决方案，它将 CI/CD 工具链的所有功能放入云中。DevOps 平台的例子包括 GitLab 和 Harness。GitHub 也在采取行动，使自己成为一个 DevOps 平台。
|
||||
|
||||
#### 优势（即便只从企业买家角度考虑）
|
||||
|
||||
DevOps 平台对那些已经适应了 SaaS 和云计算行业的基于消费和订阅的定价的企业买家很有吸引力。在这个远程和混合工作的世界里，对可维护性、安全、合规性和开发人员的生产力的担忧肯定是技术领导者的首要考虑。对这些人来说，在 DevOps 平台上实现标准化是很有吸引力的。
|
||||
|
||||
#### 劣势
|
||||
|
||||
在依赖供应商提供的 DevOps 工具链时，人们会想到对供应商锁定功能的古老担忧。开发团队构建和维护其工具链的可扩展性不会像他们从头开始制作工具链时那样，更不用说引入新的工具来改善他们的工作流程了。
|
||||
|
||||
DevOps 平台供应商也有潜在的经济方面的劣势。想一想，一个被高估的 DevOps 工具初创公司如果没有达到其投资者的高额财务目标，可能会发生什么。同样，也可能有一些较小的初创供应商得不到下一轮的资金，而慢慢消失。
|
||||
|
||||
虽然 DevOps 平台的出现在很多方面都是有意义的，但它确实违背了促成我们今天使用的 DevOps 工具的开源精神。
|
||||
|
||||
### DevOps 工具：一个拐点
|
||||
|
||||
随着工作模式的改变，人们对 DevOps 工具链的安全和合规性的关注必然会增加。
|
||||
|
||||
#### 正在变化的工作环境
|
||||
|
||||
我们的工作方式与企业其他部门一样影响着 DevOps 团队。远程和混合 DevOps 团队需要安全的工具链。整个流水线中不断变化的协作和报告要求，如异步工作和经理要求返回办公室等，也是日益增长的必要条件。
|
||||
|
||||
#### 软件供应链安全市场
|
||||
|
||||
在高调的攻击和联邦政府的回应之后，软件供应链安全市场引起了很多关注。目前还没有组织将软件供应链的攻击归咎于开源，但我们将看到 DevOps/DevSecOps 实践和工具的延伸，以对抗这种威胁。不过，当一切都结束时，DevOps/DevSecOps 的工具和实践将超过一些转向这一趋势的初创公司。
|
||||
|
||||
### 最后的想法
|
||||
|
||||
对于 DevOps 领域的开放源码软件（OSS）项目来说，这还远远没有结束，但 DevOps 利益相关者有权开始询问未来的工具链。然而，OSS DevOps 项目确实需要考虑他们的未来，特别是考虑到日益增长的直接影响流水线的安全和合规性问题。
|
||||
|
||||
DevOps 平台供应商与开源工具的未来趋势是合作性竞争，即 DevOps 平台供应商向作为其平台基础的开源工具贡献时间、金钱和资源。一个有趣的例子就是 [OpsVerse][5]，它用他们为客户管理的开源工具提供了一个 DevOps 平台。
|
||||
|
||||
然后，还有一个未来，随着更多的企业构建的工具链迁移到云端，开源 DevOps 工具项目将继续繁荣和创新。
|
||||
|
||||
**[ Kickstart an organizational culture change. Read the first article in a series, [DevSecOps: 5 tips for seeding a culture transformation][6] ]**
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/10/open-source-devops-tools
|
||||
|
||||
作者：[Will Kelly][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[lxbwolf](https://github.com/lxbwolf)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/willkelly
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/article/22/4/our-favorite-git-commands
|
||||
[2]: https://opensource.com/article/19/9/how-contribute-gitlab
|
||||
[3]: https://opensource.com/resources/what-is-kubernetes
|
||||
[4]: https://enterprisersproject.com/article/2019/1/kubernetes-security-4-tips-manage-risks?intcmp=7013a000002qLH8AAM
|
||||
[5]: https://www.opsverse.io/
|
||||
[6]: https://www.redhat.com/architect/devsecops-culture?intcmp=7013a000002qLH8AAM
|
||||
Loading…
Reference in New Issue
Block a user