返回 ITIL 4理论与实践整体知识体系中文版发布文件汇总

需要下载最新翻译版本请关注微信公众号：ITILXF，并回复“部署”即可。

关于本文件
本文档为部署管理实践提供了实用指南。它分为五个主要部分，内容包括：
●        有关实践的一般信息
●        实践的流程和活动以及它们在服务价值链中的作用
●        实践中涉及的组织和人员
●        支持实践的信息和技术
●        用于实践的用于合作伙伴和供应商的注意事项。
1.1 ITIL®4 鉴证方案

本文的选定内容可以作为以下教学大纲的一部分进行检查：
●        ITIL专家：创建，交付和支持
●        ITIL专家：高速IT
有关详细信息，请参考教学大纲文档。

一般信息
2.1        目的和描述        


关键信息
部署管理实践的目的是将新的或更改的硬件，软件，文档，流程或任何其他组件移到实际环境中。它还可能涉及将组件部署到其他环境以进行测试或登台。
部署管理实践负责将服务或服务组件移入指定的环境。该实践使得部署或从不同环境（包括开发，集成，实时，生产，测试或登台环境）的服务组件或从其中移除。
实践通常应用于组织控制的商定的范围内的数字化和物理IT组件，包括软件，硬件，文档，许可证和数据。
2.2        术语和概念        
2.2.1        环境环境
部署管理实践支持在环境之间移动产品，服务和服务组件。

服务组件的生命周期可能因其类型和发包方法而异。组织中受控环境的数量和用途也可能有所不同。表2.1列出了开发软件的组织的示例环境。

表2.1开发软件的组织的示例环境列表


环境        
目的

开发/集成        
开发和集成软件

测试        
测试服务组件

分期        测试版本，包括产品，服务和其他配置项目

现场/制作        
向服务消费者提供IT服务

对于组织以外的产品和组件，开发环境可能不在组织的控制之内。对于交付给组织以外的服务消费者的产品和服务，可以限制运行环境之上的控制。其他变化是可能的。

2.2.2        持续集成，持续交付和持续部署（CI / CD）
敏捷和DevOps中部署的关键概念是：

●        持续集成在软件开发环境中集成，构建和测试代码。
●        持续交付持续交付意味着内置的软件可以随时发布到生产中。可以进行频繁部署，但是部署的决定要视具体情况而定，通常是因为组织更喜欢部署的速率较低。
●        持续部署更改会通过流水线并自动放入生产环境中，从而每天可以进行多个生产部署。连续
部署依赖持续交付。

软件开发和管理，服务，验证和测试，部署管理，基础设施和平台管理和发布管理实践均支持这些方法。这些实践涉及特定技能，流程，过程，自动化工具以及与第三方的协议。它们为集成，交付和部署启用了连续的流水线。这也会影响其他实践的设计，例如服务配置管理，监控和事态管理，事件管理等。
2.3        范围        
部署管理实践的范围包括：

●        产品，服务和服务组件在受控环境（例如开发，实时，测试和登台环境）之间的有效转移。
●        有效地从指定环境中删除产品，服务和服务组件。
这些添加，修改和删除可以是由以下各项触发的授权更改/发布的一部分：
●        服务的新/变更要求
●        新功能/版本
●        技术和运行的的更改
●        第三方变更要求
●        服务退役和撤职
●        支持/故障排除
●        服务请求。
部署管理实践中未包含几个活动和职责范围，尽管它们仍与部署密切相关。表2.2中列出了这些内容，以及对可以找到它们的实践的引用。重要的是要记住，ITIL实践只是价值流的背景中使用的工具的集合；根据情况，应将它们组合在一起。


About this document
This document provides practical guidance for the deployment management practice. It is split into five main sections, covering:
●        general information about the practice
●        the practice’s processes and activities and their roles in the service value chain
●        the organizations and people involved in the practice
●        the information and technology supporting the practice
●        considerations for partners and suppliers for the practice.
1.1 ITIL® 4 QUALIFICATION SCHEME

Selected content of this document is examinable as a part of the following syllabus:
●        ITIL Specialist: Create, deliver and support
●        ITIL Specialist: High Velocity IT
Please refer to the syllabus documents for details.

General information
2.1        PURPOSE AND DESCRIPTION        


Key message
The purpose of the deployment management practice is to move new or changed hardware, software, documentation, processes, or any other component to live environments. It may also be involved in deploying components to other environments for testing or staging.
The deployment management practice is responsible for moving a service or service component into a designated environment. This practice enables the deployment or removal of service components from or to different environments, including development, integration, live, production, test, or staging environments.
The practice is usually applied to digital and physical IT components, including software, hardware, documentation, licences, and data, within the agreed scope of environments controlled by the organization.
2.2        TERMS AND CONCEPTS        
2.2.1        Environments
The deployment management practice enables the move of products, services, and service components between the environments.

A service component’s lifecycle may vary depending on its type and the sourcing approach. The number and purpose of controlled environments within the organization may also vary. Table 2.1 provides a list of example environments for an organization that develops software.

Table 2.1 List of example environments for an organization that develops software


Environment        
Purpose

Development/Integration        
Developing and integrating software

Test        
Testing service components

Staging        Testing releases including products, services and other configuration items

Live/Production        
Delivering IT services to service consumers

For products and components sourced outside the organization, development environments can be out of the organization’s control. For products and services delivered to service consumers outside of the organization, control over the live environment can be limited. Other variations are possible.

2.2.2        Continuous integration, continuous delivery, and continuous deployment (CI/CD)
The key concepts for deployment in Agile and DevOps are:

●        Continuous integration Integrating, building, and testing code within the software development environment.
●        Continuous delivery Continuous delivery means that built software can be released to production at any time. Frequent deployments are possible, but deployment decisions are taken case by case, usually because organizations prefer a slower rate of deployment.
●        Continuous deployment Changes go through the pipeline and are automatically put into the production environment, enabling multiple production deployments per day. Continuous
deployment relies on continuous delivery.

These approaches are supported by the software development and management, service validation and testing, deployment management, infrastructure and platform management, and release management practices. These practices involve specific skills, processes, procedures, automation tools, and agreements with third parties. They enable the continuous pipeline for integration, delivery, and deployment. This would also affect the design of other practices, such as service configuration management, monitoring and event management, incident management, and others.
2.3        SCOPE        
The scope of the deployment management practice includes:

●        the effective move of products, services, and service components between controlled environments, such as the development, live, test, and staging environments.
●        the effective removal of products, services, and service components from designated environments.
These additions, modifications, and removals can be part of authorized changes/releases triggered by:
●        new/changed service requirements
●        new features/releases
●        technical and operational changes
●        third-party change requirements
●        service retirements and removals
●        support/troubleshooting
●        service requests.
Several activities and areas of responsibility are not included in the deployment management practice, although hey are still closely related to deployment. These are listed in Table 2.2, along with references to the practices in which they can be found. It is important to remember that ITIL practices are merely collections of tools to use in the context of value streams; they should be combined as necessary, depending on the situation.

greet, thx for your share

Practice_Deployment management 部署管理实践ITIL 4中