GB/T 36450.4-2024Information technology - Storage management - Part 4: Block devices (English PDF)

0.1 Description of the text structure of GB/T 36450

GB/T 36450 "Information Technology Storage Management" is a recommended standard to guide the standardization of storage management in my country.

The standard management interface solves the interoperability of multi-vendor products and the management issues of cross-regional, multi-functional distributed storage systems.

GB/T 36450 "Information Technology Storage Management" is compiled based on ISO/IEC 24775 and is intended to consist of eight parts.

--- Part 1: Overview. The purpose is to provide a high-level introduction to key concepts and is essential for understanding GB/T 36450 "Information Technology it is an important basis for the detailed content of the "Technical Storage Management" standard.

--- Part 2: General architecture. The purpose is to establish a general transmission model to exchange management information between management system components.

The design rules of the general transmission model and the roles and responsibilities of each component using the general transmission model are given.

--- Part 3: Common Profile. The purpose is to establish a unified solution across multiple autonomous management profiles for storage management Other system configuration files are supported.

--- Part 4: Block devices. The purpose is to establish a configuration interface for storage management system security, scalability and interoperability.

The interface is designed through object-oriented, XML-based and information-transfer protocols to support management devices and subsystems in different environments.

System requirements.

--- Part 5: File system. The purpose is to establish the autonomous management configuration files of programs and devices, and to provide support for file data.

Core functional requirements for support and access.

--- Part 6: Switching Fabric. The purpose is to establish the autonomous management configuration of programs and devices that support storage networking document.

--- Part 7: Host Elements. The purpose is to establish autonomous management configuration based on host storage devices, components and abstract configuration files document requirements.

--- Part 8: Media Library. The purpose is to establish the modeling details requirements for monitoring media library objects.

0.2 Typographical Conventions

In addition to informative and normative content, this document contains guidance on emerging materials that have undergone rigorous design review.

However, its implementation in commercial products is limited. The purpose of typographical conventions is to provide corresponding the maturity level of the material. Implementers should make further decisions based on the maturity levels recognized in different parts of this document to determine whether to Adoption and deployment of various parts of this document in commercial products.

This document is organized into a structure that considers the implementation and deployment life cycle of Information Technology Storage Management and its new products, both formally and in summary, the goal is that all the contents of this document will present a mature and stable design that will be accepted by a large number of implementations.

ensure consistent support for backward compatibility and only rely on content material that has reached a similar maturity level.

Mark the sub-level maturity levels defined in this document, and for all other content, assume that they meet these requirements and call them "done" Because much of the evolving standard content falls short of this level of completion in any given implementation, this document defines There are three sub-levels of implementation maturity that identify important aspects of the increasing maturity and stability of the technical content.

Maturity levels are defined by their degree of implementation experience, stability, and dependency on other emerging standards. Each sub-maturity level is defined by A unique labeling convention is used to mark content at one maturity model level so that content at another level is clearly distinguishable.

Experimental Maturity Level. This document contains only technical content for which the initial architecture has been completed and passed design review.

Some of the technical content has been designed and reviewed, but lacks implementation experience and the maturity derived from that experience.

The purpose of this document is to gain wider review and implementation experience. This material will be marked as "experimental".

The contents of the "experimental" profiles may be modified as products are implemented.

The experimental material will be changed as experience is gained. It is likely that the changed content will be included in new versions of this document.

Figure 1 is an example of typographic conventions for experimental content.

Experimental

Experimental content is given here.

Experimental

Figure 1 Experimental maturity level label

Implementation Maturity Level. Profiles that have completed initial implementation are classified as "Implemented". This means that at least two different suppliers have at this maturity level, there is a stable underlying architecture and modeling process.

The changes in future versions are limited to correcting defects found in more implementation experience. If such materials become outdated in the future, they will be removed from subsequent implementations.

This material was discarded when minor revisions were made to this document before it was deleted in the current version. Figure 2 is an example of the typographical conventions of the implemented content.

Implemented

The implementation is given here.

Implemented

Figure 2 Implementation maturity level labels

Stable maturity level. Once content at the Implemented maturity level has gained more implementation experience, it can be marked as Stable.

The material at this maturity level has been implemented by three different suppliers, including a provider and a customer.

If the material that has reached this maturity level becomes outdated, it needs to be discarded when making minor revisions to this document.

When a minor revision is made to a profile to produce the next version, backward compatibility of the profile that has reached that maturity level must be ensured.

Profiles at or above the Stable maturity level do not need to depend on any content at the Experimental maturity level.

Examples of typographical conventions for specified content.

Stable

Here is the stable content.

Stable

Figure 3 Stable maturity level label

Completed maturity level. Content that reaches the highest maturity level is called "completed".

Otherwise, content at the Done level of maturity should only depend on material that has reached Done level or its refinements.

If the external content is not SNIA controlled material and is therefore not subject to its maturity definition, SNIA will evaluate the external content to ensure that it has met If material that has reached this maturity level becomes outdated, significant revisions to this document are required.

The material is deprecated when it is modified. Profiles that reach this maturity level guarantee backward compatibility with each minor revision of this document.

Therefore, for this maturity level, there are no requirements as for other maturity sub-levels.

For content in this document that is not represented using one of the typographical conventions specified for the sub-maturity level, Mark, it should be assumed that it has reached the completion level of maturity.

Deprecated Material. Experimental material is deprecated and will not be included in subsequent revisions of this document.

The material is outdated and is not recommended for use in new development work. Existing and new implementations may still use this material, but should be adopted as soon as possible.

How long newly deprecated material will remain in the standard depends on its maturity level.

Until the next revision of this document, while "stable" and "finished" material needs to be retained until the next major revision of this document.

Providers are required to implement this material as long as it appears in this document to ensure backward compatibility. Clients may rely on deprecated material.

materials, but are encouraged to use non-deprecated alternatives where possible.

Arrange the deprecated clauses by citing the previous version and incorporate the deprecated clauses into the current standard as a replacement for normative material.

Figure 4 is an example of typographical conventions for deprecated content.

Deprecated

Deprecated content is given here.

Deprecated

Figure 4 Deprecation label

Information Technology Storage Management Part 4: Block Devices

4.1 Description

4.1.1 Overview

Configuration file name. array (autonomous configuration file) Version. 1.7.0 Organization.SNIA Core class. ComputerSystem Scope Class.ComputerSystem