GB/T 36450.3-2024Information technology - Storage management - Part 3: Common profiles (English PDF)

Foreword

This document is in accordance with the provisions of GB/T 1.1-2020 "Guidelines for standardization work Part 1: Structure and drafting rules for standardization documents" Drafting:

This document is Part 3 of GB/T 36450 "Information Technology Storage Management": GB/T 36450 has been published in the following parts:

--- Part 1: Overview;

--- Part 2: General architecture;

--- Part 3: General profile;

--- Part 5: File system;

--- Part 6: Switching structure;

--- Part 7: Host elements;

--- Part 8: Media Library:

This document is equivalent to ISO/IEC 24775-3:2021 "Information technology storage management Part 3: Common profile":

The following minimal editorial changes were made to this document:

--- Corrected the article numbers of 32:6:18~32:6:24 in the international standard;

--- Corrected the numbering of the drawings in the international standards:

Introduction

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 quasi-management interface solves the interoperability of multi-vendor products and the management issues of cross-regional, multi-functional distributed storage systems:

GB/T 36450 is compiled based on ISO/IEC 24775 and consists of eight parts:

--- Part 1: Overview: The purpose is to provide a high-level introduction to key concepts and to understand the details of GB/T 36450:

important foundation:

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

The general transmission model is introduced, and the design rules of the general transmission model are given, as well as the roles and responsibilities of each component using the general transmission model:

--- Part 3: Generic Profile: The purpose is to establish a unified solution across multiple autonomous management profiles for storage management systems Other profiles are supported:

--- Part 4: Block devices: The purpose is to establish a configuration interface for storage management systems that is secure, scalable, and interoperable:

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 profile of programs and equipment, and the support and Access to core functionality requirements:

--- Part 6: Switching structure: The purpose is to establish the autonomous management profile of the programs and devices that provide support for storage networking:

--- Part 7: Host elements: The purpose is to establish autonomous management profiles based on host storage devices, components and abstract profiles Require:

--- 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, implementation in commercial products is limited: The purpose of typographical conventions is to provide appropriate the implementer should make a further decision as to whether to include the material in the Adoption and deployment of various parts of this document in commercial products:

This document is structured to provide both formal requirements and guidance for the implementation and deployment life cycle of GB/T 36450 and its new products:

In summary, all the contents of this document will show a mature and stable design, which will be tested by a large number of implementations to ensure backwards compatible with the same support, and only rely on content material that has reached a similar maturity level:

For all other content, it is assumed that they meet these requirements and are called "complete":

In any implementation of a standard, there is much that does not reach this level of "completion", so this document defines three levels of implementation maturity:

Sub-levels, which identify important aspects of the increasing maturity and stability of the technical content: Each sub-maturity level is actually each sub-maturity level is defined by its degree of experience, stability, and dependency on other emerging standards:

The content of one maturity model level is clearly distinguished from that of another level by means of a signatory agreement:

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

Some of the technical content has been designed and reviewed, but lacks implementation experience and the maturity gained from implementation experience:

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

The content of the "experimental" profile may be modified as products are implemented:

The experimental material will be updated as it is implemented:

Figure 1 is an example of typographical conventions for experimental content:

Figure 1 Experimental maturity level label

Implementation maturity level: Profiles that have completed preliminary implementations are classified as "implemented": This means that at least two different vendors have implemented at this maturity level, the underlying architecture and modeling process are stable and future versions of the this change is limited to correcting defects found in more implementation experience: If such material becomes outdated in the future, it will be removed from subsequent implementation versions:

Before deletion, the material is discarded when minor changes are made to this document: Figure 2 is an example of the typographical conventions of the implemented content:

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 vendors, including a provider and a customer:

If material that has reached this maturity level becomes obsolete, it may be discarded when making minor revisions to this document:

When making minor changes to produce the next version, backward compatibility with profiles that have reached this maturity level is guaranteed:

The outline of the Stable maturity level does not depend on any content in the Experimental maturity level: Figure 3 is a typographical outline of the Stable content:

Set example:

Figure 3 Stable maturity level label

Completed maturity level: Content that reaches the highest maturity level is called "completed": In addition to meeting the requirements of the stable level of maturity Otherwise, content at the Done level of maturity depends only on material that has reached Done level or its refinements:

SNIA controls material that is not subject to its maturity definition, SNIA will evaluate the external content to ensure that it has achieved comparable maturity:

If material that has reached this maturity level becomes outdated, significant revisions may be made to this document:

Profiles reaching this maturity level guarantee backward compatibility with each minor revision of this document:

All contents of this document meet this maturity level: Therefore, there is no special requirement for this maturity level as there is for other maturity sub-levels:

For content in this document that is not marked using one of the typographical conventions specified for the sub-maturity level, it is recommended to assume that it has reached completion level maturity:

Deprecated Material: Experimental material that may be deprecated in subsequent revisions of this document is not included: Sections marked "deprecated" contain 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 updated as soon as possible:

Adopt new approaches: How long newly deprecated material stays in the standard depends on its maturity level:

Deprecated material is reserved for the next major revision of this document, while "stable" and "finished" material is reserved for the next major revision of this document:

Providers are required to implement deprecated material as long as it appears in this document to ensure backward compatibility: Clients may depend on deprecated material, but are encouraged to Encourage the use of non-deprecated alternatives where possible:

The deprecated clauses are arranged by citing the previous version, and the deprecated clauses are included as normative materials in the replacement clauses of the current standard:

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

Figure 4 Deprecation label

Information Technology Storage Management Part 3: General profiles

1 Scope

This document defines the general outline required by other parts of GB/T 36450: The previous clauses provide background information that helps explain the purpose and overview:

The generic port profiles are grouped together because they serve as transmission-specific variations of the generic model: The port profiles are followed by their He has a universal outline:

2 Normative references

The contents of the following documents constitute the essential clauses of this document through normative references in this document:

For referenced documents without a date, only the version corresponding to that date applies to this document; for referenced documents without a date, the latest version (including all amendments) applies to this document:

2.1 Approved References Storage management-Part 2: Common Architecture) Note: GB/T 36450.2-2021 Information technology storage management Part 2: General architecture

2.2 DMTF Reference Document (Final) the DMTF final document is accepted as a standard:

http://www:dmtf:org/sites/default/files/standards/documents/DSP1004_1:0:1:pdf http://www:dmtf:org/sites/default/files/standards/documents/DSP1009_1:1:1:pdf http://www:dmtf:org/standards/published_documents/DSP1011_1:0:2:pdf DMTFDSP1013:2008 Fan Profile (FanProfile1:0:1) http://www:dmtf:org/standards/published_documents/DSP1015_1:1:0:pdf http://www:dmtf:org/standards/published_documents/DSP1023_1:0:1:pdf http://www:dmtf:org/standards/published_documents/DSP1025_1:0:0:pdf http://www:dmtf:org/sites/default/files/standards/documents/DSP1052_1:0:3:pdf http://www:dmtf:org/sites/default/files/standards/documents/DSP1054_1:2:2:pdf