DevOps is the combination of cultural philosophies, technical practices, and tools that fosters integration, collaboration, communication, and automation between technology operations and software development teams in order to improve the quality and speed of software delivery. The common goal of DevOps is to remove friction, risk, and other constraints to enable faster, more successful application production rollouts, as often and as rapidly as the business requires. Most companies that implement DevOps methods today still have a development team and an operations team in place. You can think of DevOps as the processes and individuals that build the bridges between these teams to improve the business and enhance the end-customer experience. Various tools and platforms facilitate the work of DevOps, but they do not define it.

How did DevOps originate?

DevOps was birthed by the practice and propagation of agile software development. Since the agile methodology speeds up the development process and throughput velocity, there was a need to alter the structure of project teams to accommodate this new reality. As agile culture took root, it became clear that having the software development and IT operations teams working separately was counterproductive and inefficient. DevOps practices automate deployment pipelines and produces faster feedback to improve efficiency, predictability, maintainability, and security. It brings developers into the production environment, gives them deeper insights into the infrastructure and gets them more involved in application lifecycle management.

Like all work cultures, DevOps is adopted and applied in different ways from organization to organization. Nevertheless, certain capabilities are common in nearly all DevOps implementations. What are DevOps key characteristics? Collaboration Instead of operations and development teams assuming a defensive or combative stance when engaging one another, they strive to collaborate. The conflicts and rivalry between these teams are one of the principal catalysts for the creation of DevOps. Automation DevOps is geared toward facilitating the speedy delivery of an agile development project. Therefore, it is heavily dependent on automation. That means a reliance on multiple tools that automate the application development and deployment cycle. Continuous Integration Continuous integration is a technique for continually merging software code from all developers in a project into a shared mainline. This ensures that the copy of the project each developer is working on is nearly the same. By compelling developers to integrate their work into the mainline at least daily, DevOps culture reduces the likelihood of disruptive merger conflicts later on. Continuous Testing Software failure is expensive. Unleashing an application release that ruins existing user experience or introduces new risks would be counterproductive. Continuous testing ensures the right balance of software quality and speedy deployment is achieved. In DevOps, software testing isn’t something left to one person or department. Rather, it’s everyone’s responsibility. Developers engineer quality into the code and then avail test data. Quality assurance and operations teams, in turn, configure test cases and the test environment. Since tests must be executed quickly to avoid falling behind new changes being applied in development, the test process must be automated as much as possible. Continuous Delivery Continuous delivery means changes to application code are automatically prepared for release into the live environment. All code changes are deployed into a test environment before they are eventually applied to production. The DevOps team always has a deployment-ready release that has successfully been taken through the standardized and automated test process. Release frequency will vary depending on goals, priority, and urgency. It may be as often as multiple releases per day or as seldom as one release per month or quarter. Continuous Monitoring Given the speed and number of releases, it’s imperative to have a solution in place that provides continuous monitoring to enable faster and better response to changing customer needs. Continuous monitoring allows the DevOps team to track software performance and improve its stability. Problems are identified quickly, and root causes proactively investigated to prevent outages and downtime. Monitoring starts during release development. The same monitoring tools that are applied in the live environment can be leveraged in development to pick up problems before they make their way into production.

Organizations that embrace DevOps might have all IT resources within a traditional data center, all resources in an offsite cloud, or distribute their resources in a hybrid environment. The DevOps movement is not defined, nor led, by traditional IT software, hardware, or management vendors. In addition, there are currently no codified rules or manuals for DevOps, only generally accepted guidelines. With that said, adoption and implementation of DevOps vary greatly from one organization to the next. The learnings of DevOps are primarily evangelized by a passionate grassroots community of IT practitioners, spread across a wide variety of IT disciplines. Most members of the DevOps community have active jobs within various organizations, and they share their learnings in numerous online and in-person forums and gatherings. Depending on the number and maturity of the practitioners in an organization, the benefits of a DevOps implementation can be significant, including: Faster release of apps with automation of integrated build, test and deployment process Increased developer and operational efficiency by managing your infrastructure as code Improved customer experience with immediate feedback loops and continuous improvement

How to Scale DevOps practices across all your environments?

Micro Focus enables you to scale DevOps practices across Hybrid IT , automating and orchestrating continuous delivery pipelines from mainframe to mobile, and providing actionable insight to securely deliver high quality software and services faster. Micro Focus helps its customers scale DevOps practices across traditional and hybrid IT environments. Enterprise DevOps can deliver in-novation by transforming and extending your current IT environments, with quality and security built in, every step of the way. The Micro Focus approach starts with under-standing where you are on your Enterprise DevOps journey. We then provide guidance on scaling your DevOps practices and help you integrate your toolchain from mainframe to mobile. We believe it’s imperative to think big and start small. Look at the system holistically, understand where the constraints are and re-move them one-by-one. We are the only vendor to provide an integrated, end-to-end application lifecycle management solution that is built for any methodology, technology, and delivery model.

什么是 DevOps？ | Micro Focus

‹ Back

应用程序递送管理
‹ Back

应用程序递送管理
加快速度、消除瓶颈，不断提升软件交付能力
应用现代化和连接
‹ Back

应用现代化和连接
实现核心业务系统现代化，以推动业务转型
安全性
‹ Back

安全性
让您的任何工作都以安全为中心；操作、应用程序、身份和数据
信息管理和治理
‹ Back

信息管理和治理
值得信赖和久经考验的合法、合规和隐私解决方案
IT 运营管理
‹ Back

IT 运营管理
使您的 IT Operations 与 DevOps 齐头并进
分析与大数据

DevOps 是文化理念、技术实践和工具的组合，可促进技术运维和软件开发团队之间的集成、协作、沟通和自动化，从而提高软件交付的质量和速度。

DevOps 的共同目标是消除摩擦、风险和其他约束，以实现更快、更成功的应用生产推出，并且频率和速度也达到了业务要求。

目前大多数实施 DevOps 方法的公司仍然有自己的开发团队和运维团队。您可以将 DevOps 看作是进程和个人，用于在这些团队之间构建桥梁以提升业务和增强最终客户体验。各种工具和平台均会促进 DevOps 的工作，但他们并没有对 DevOps 进行说明。

DevOps 的起源是什么？ DevOps 的需求阐释

DevOps 是伴随着敏捷软件开发的实践和传播而诞生的。由于敏捷方法论加快了开发过程和吞吐速度，因此有必要更改项目团队的结构，以适应这一新现实状况。随着敏捷文化不断扎根，很明显，让软件开发团队和 IT 运维团队分开工作会适得其反，致使效率低下。

DevOps 实践使部署管道自动化，更快速地提供反馈，以提高效率、可预测性、可维护性和安全性。它将开发人员引入生产环境，让他们对基础设施有更深入的了解，并使他们更多地参与到应用程序生命周期管理中来。

DevOps 有哪些作用？

像所有工作文化一样，DevOps 的采用和应用方式因组织而异。但是，某些功能在几乎所有 DevOps 安装启用案例中是通用的。 DevOps 有哪些关键特征？

协作

在需要联合作业时，运维团队和开发团队无需箭弩拔张、相互警惕，而是尽力协作。这些团队之间的冲突和竞争是创建 DevOps 的主要催化剂之一。

自动化

DevOps 致力于促进敏捷开发项目的快速交付。因此，它严重依赖自动化。这意味着要依靠多种工具实现应用程序开发和部署周期自动化。

持续集成

持续集成是将项目中所有开发人员的软件代码不断合并到共享主线中的技术。这样可确保各个开发人员处理的项目版本近乎一样。通过迫使开发人员至少每天将其工作集成到主线，DevOps 文化降低了日后产生破坏性合并冲突的可能性。

持续测试

软件故障代价非常高昂。发布会破坏现有用户体验或引入新风险的应用程序会适得其反。持续测试可确保实现软件质量和快速部署的微妙平衡。

在 DevOps 中，软件测试不再只是某个人或某个部门的任务。它是每个人都必须承担的责任。开发人员确保代码质量，然后利用测试数据。质量保证和运维团队则配置测试用例和测试环境。

由于必须快速执行测试以避免落后于开发中应用的新更改，因此测试过程必须尽可能自动化。

持续交付

持续交付意味着自动准备对应用程序代码的更改，以便发布到实时环境中。所有代码更改都要先部署到测试环境中，然后再应用到生产环境中。

DevOps 团队始终具备已成功通过标准化和自动化测试流程的可部署版本。发布频率取决于目标、优先级和紧急程度。它可以是一天发布多次，也可以是每月或每个季度发布一次。

持续监控

考虑到发布的速度和数量，必须实施一个提供持续监控的解决方案，以应对不断变化的客户需求，快速做出优质回应。

持续监控使 DevOps 团队能够跟踪软件性能，并改善其稳定性。快速识别问题，积极调查根本原因，防止设备停开和停机。

在版本开发期间开始监控。可以在开发环节利用实际环境中使用的同款监视工具，以便在版本进入生产环境前发现问题。

为何选择 DevOps？

接受 DevOps 的企业可能拥有一个传统数据中心的所有 IT 资源以及异地云中的所有资源，或者在混合环境中分发他们的资源。

DevOps 活动不是由传统 IT 软件、硬件或管理供应商所定义及主导。此外，目前还没有关于 DevOps 的成文规则或手册，只有一般公认的准则。因此，在不同的企业之中普及和实施 DevOps 会有很大的不同。

DevOps 的相关知识主要是由 IT 各个领域从业者所在的充满激情的基层社区宣传。 DevOps 社区的大多数成员在不同的企业中都有有效职位，他们在许多在线和面对面的论坛和聚会上分享他们的知识。视企业中从业人员的数量和成熟度而定，实现 DevOps 的优势是重要的，包括：

通过自动实现集成化构建、测试和部署流程来加快应用发布速度
通过管理基础设施即代码，提高了开发人员和运维效率
通过即时反馈环路和持续改进，提升了客户体验

跨所有环境扩展 DevOps 实践

Micro Focus 使您能够跨混合 IT 环境扩展 DevOps 实践，自动化和协调从大型机到移动设备的持续交付管道，并提供可行见解，以便快速安全地交付高质量的软件和服务。

Micro Focus 帮助其客户跨传统和混合 IT 环境扩展 DevOps 实践。 Enterprise DevOps 可通过当前 IT 环境的转型和扩展实现创新，同时保证各个环节的质量和安全。

Micro Focus 方法首先要了解您在 Enterprise DevOps 之旅所处的位置。然后，我们会指导您扩展 DevOps 实践，并帮助您将工具链从大型机集成到移动设备。我们坚信大处着眼，小处着手。从整体看系统，了解其限制，然后逐一清除。我们是唯一能够提供集成式端到端应用程序生命周期管理解决方案的供应商，我们的解决方案适用于任意方法、技术和交付模型。

Your browser is not supported