| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 36450.4-2024 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Information technology - Storage management - Part 4: Block devices
| Valid |
GB/T 36450.4-2024
|
PDF similar to GB/T 36450.4-2024
Basic data | Standard ID | GB/T 36450.4-2024 (GB/T36450.4-2024) | | Description (Translated English) | Information technology - Storage management - Part 4: Block devices | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | L77 | | Classification of International Standard | 35.220 | | Word Count Estimation | 915,979 | | Date of Issue | 2024-10-26 | | Date of Implementation | 2025-05-01 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 36450.4-2024: Information technology - Storage management - Part 4: Block devices---This is an excerpt. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.), auto-downloaded/delivered in 9 seconds, can be purchased online: https://www.ChineseStandard.net/PDF.aspx/GBT36450.4-2024
ICS 35.220
CCSL77
National Standard of the People's Republic of China
Information Technology Storage Management
Part 4.Block Devices
(ISO /IEC 24775-4.2021,MOD)
Released on October 26, 2024
Implementation on May 1, 2025
State Administration for Market Regulation
The National Standardization Administration issued
Table of Contents
Preface VII
Introduction VIII
1 Scope 1
2 Normative references 1
3 Terms and Definitions 1
4 Array Configuration File 1
4.1 Description 1
4.2 Health and Fault Management Considerations 6
4.3 Cascading Notes 6
4.4 Configuration File Method 6
4.5 Use Case 6
4.6 CIM Elements 7
4.7 WAN Storage Resource Management 13
5 Service Pack 13
5.1 Description 13
5.2 Health and Fault Management Considerations 35
5.3 Cascading Notes 38
5.4 Configuration File Method 38
5.5 Use Cases 55
5.6 CIM Elements 62
6 Block Storage View Profile 94
6.1 Description 94
6.2 Health and Fault Management Considerations 111
6.3 Cascading Considerations 111
6.4 Configuration File Method 111
6.5 Client Notes and Methods 111
6.6 CIM Elements 115
7.Performance Profiles for Block Services 146
7.1 Description 146
7.2 Implementation 148
7.3 Health and Fault Management Considerations 169
7.4 Cascading Considerations 169
7.5 Configuration File Method 169
7.6 Client Notes and Methods 178
7.7 CIM Elements 183
8 CKD Block Service Profile 211
8.1 Description 211
8.2 Health and Fault Management Considerations 214
8.3 Cascading Considerations 214
8.4 Configuration File Method 214
8.5 Use Cases 214
8.6 CIM Elements 214
9 Copying Service Configuration Files 248
9.1 Description 248
9.2 Health and Fault Management Considerations 282
9.3 Cascading Considerations 284
9.4 Supported Configuration Files and Packages 284
9.5 Configuration File Methods 285
9.6 Client Notes and Method 303
9.7 CIM Elements 315
10 Disk Drive Thin Profile 332
10.1 Summary 332
10.2 Description 332
10.3 Modeling 332
10.4 Health and Fault Management Considerations 334
10.5 Cascading Considerations 337
10.6 Configuration File Method 337
10.7 CIM Elements 338
11 Disk Spare Configuration File 351
11.1 Description 351
11.2 Health and Fault Management Considerations 357
11.3 Cascading Considerations 358
11.4 Configuration File Method 358
11.5 Use Cases 362
11.6 CIM Elements 362
12 Erase configuration file 372
12.1 Description 372
12.2 Health and Fault Management Considerations 374
12.3 Cascading Considerations 374
12.4 Configuration File Method 374
12.5 Use Cases 375
12.6 CIM Elements 375
13 Scope Composition Profile 379
13.1 Description 379
13.2 Health and Fault Management Considerations 395
13.3 Cascading Considerations 395
13.4 Configuration File Methods 395
13.5 Use Cases 395
13.6 CIM Elements 396
14 Masking and Mapping Profiles 405
14.1 Description 405
14.2 Health and Fault Management Considerations 414
14.3 Cascading Considerations 414
14.4 Configuration File Method 414
14.5 Use Cases 426
14.6 CIM Elements 426
15 Asymmetric Configuration Files for Storage Servers 446
15.1 Description 446
15.2 Health and Fault Management Considerations 454
15.3 Cascading Considerations 454
15.4 Configuration File Method 454
15.5 Use Cases 455
15.6 CIM Elements 455
16 Storage Virtualization Device Configuration File 465
16.1 Summary 465
16.2 Description 467
16.3 Example Figure 467
16.4 Health and Fault Management Considerations 472
16.5 Cascaded Storage Virtualization Support 472
16.6 Configuration File Methods 473
16.7 Use Cases 474
16.8 CIM Elements 474
17 Volume Composition Configuration File 491
17.1 Description 491
17.2 Strips and jointed composite volumes 501
17.3 Health and Fault Management Considerations 502
17.4 Cascading Notes 502
17.5 Configuration File Method 502
17.6 Use Cases 514
17.7 CIM Elements 514
18 Volume Management Configuration File 521
19 Protection Profiles for Storage Elements 521
19.1 Description 521
19.2 Health and Fault Management Considerations 532
19.3 Cascading Considerations 532
19.4 Configuration File Methods 532
19.5 Client Notes and Methods 535
19.6 CIM Elements 535
20 Replica Service Profile 539
20.1 Description 539
20.2 Health and Fault Management Considerations 565
20.3 Cascading Considerations 566
20.4 Mapping of Replication and Replica Service Attributes and Methods 568
20.5 Configuration File Methods 569
20.6 Use Case 605
20.7 CIM Element 606
21 Pool Configuration File 641
21.1 Description 641
21.2 Enhanced Block Device Services 645
21.3 Health and Fault Management Considerations 646
21.4 Cascading Considerations 646
21.5 Configuration File Methods 646
21.6 Use Cases 647
21.7 CIM Elements 647
22 sets of masking and mapping profiles 650
22.1 Description 650
22.2 Health and Fault Management Considerations 656
22.3 Cascading Considerations 656
22.4 Configuration File Methods 657
22.5 Use Cases 662
22.6 CIM Elements 663
23 Storage Relocation Configuration File 688
23.1 Description 688
23.2 Health and Fault Management Considerations 693
23.3 Cascading Considerations 693
23.4 Mapping and Masking Considerations 693
23.5 Configuration File Methods 693
23.6 Use Cases 696
23.7 CIM Elements 702
24 Simplified Configuration File 719
24.1 Description 719
24.2 Health and Fault Management Considerations 723
24.3 Cascading Considerations 723
24.4 Configuration File Method 723
24.5 Use Cases 724
24.6 CIM Elements 728
25 Automatic Storage Tiering Profile 764
25.1 Description 764
25.2 Configuration File Methods 774
25.3 Client Notes and Methods 779
25.4 CIM Elements 780
26 Automatic Storage Tiering Policy Profile 802
26.1 Summary 802
26.2 Description 802
26.3 Strategy 802
26.4 Key Components 802
26.5 Implementing 803
26.6 Method 807
26.7 Use Case 812
26.8 CIM Elements 812
27 Storage Pool Diagnostic Configuration File 840
27.1 Summary 840
27.2 Description 841
27.3 Implementing 843
27.4 Method 859
27.5 Use Cases 862
27.6 CIM Elements 869
Appendix A (Informative) SMI-S Information Model 892
Appendix B (Informative) StorageExtent Definition Registry 893
B.1 ExtentDiscriminator Definition 893
B.2 The relevance of different scope definitions 893
B.3 Examples of valid combinations of range definitions 896
B.4 Combinations of scope definitions not defined in this version of the standard 896
Appendix C (Informative) Extensions based on structured peer-to-peer networks 898
C.1 Extension Purpose 898
C.2 Structured Peer-to-Peer Network Extension Experiment 898
C.3 Experimental Summary 902
Reference 903
Preface
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 4.Block devices;
--- Part 5.File system;
--- Part 6.Switching structure;
--- Part 7.Host elements;
---Part 8.Media Library.
This document is modified to adopt ISO /IEC 24775-4.2021 "Information technology storage management - Part 4.Block devices".
The technical differences between this document and ISO /IEC 24775-4.2021 and their reasons are as follows.
--- Add a column to the last part of Table 1 and Table 368 to introduce the published GB/T 36450.1-2018;
---Replace ISO /IEC 24775-7, 1.8.0 Rev 4 in 4.1.2 with GB/T 36450.7-2021 to adapt to my country's technology
Conditions (see Chapter 1) and include normative references;
--- Changed the scope of application of this document from local area network to wide area network to adapt to my country's technical conditions (see Chapter 1);
--- Replaced ISO /IEC 24775-2 (see Chapter 11 and Chapter 14) with the normative reference GB/T 36450.2-2021 to match
The scope of application of this document is extended from local area network to wide area network;
--- Replaced ISO /IEC 24775-3 (see Chapter 5, Chapter 11, Chapter 15,
Chapters 16, 20 and 23) to adapt to my country's technical conditions.
The following editorial changes have been made to this document.
--- The original text does not have Figures 5 and 6.This document adjusts the figure numbers. Figures 5 to 175 in this document correspond to Figures 7 to 176 in the original text.
Figure 177;
--- Added Appendix C (informative) "Extensions based on structured peer-to-peer networks".
Please note that some of the contents of this document may involve patents. The issuing organization of this document does not assume the responsibility for identifying patents.
This document was proposed and coordinated by the National Technical Committee for Information Technology Standardization (SAC/TC28).
This document was drafted by. Huazhong University of Science and Technology, China Electronics Standardization Institute, Shenzhen CESI Information Technology Co., Ltd., Northwestern Polytechnical University
University of Science and Technology, Sichuan Changhong Jiahua Information Products Co., Ltd., Shenzhen Urban Transportation Planning and Design Research Center Co., Ltd., China
University of Geosciences (Wuhan), Shenzhen Kelirui Technology Co., Ltd., Huawei Technologies Co., Ltd., Hangzhou Hikvision Digital Technology Co., Ltd.
Inspur Electronic Information Industry Co., Ltd., Shenzhen Quanxing Technology Co., Ltd., Deyi Microelectronics Co., Ltd., Chengdu Information Industry
Cheng University, Shenzhen Fangyuanbao Information Technology Service Co., Ltd., Shenzhen Yinshan Technology Co., Ltd., Shenzhen Jinsheng Electronic Technology Co., Ltd.,
Beike Data Technology (Shenzhen) Co., Ltd., Beijing Xiaomi Mobile Software Co., Ltd., and Shenzhen Jubang Technology Co., Ltd.
The main drafters of this document are. Feng Dan, Sun Wei, Guo Xiong, Xu Guanglei, Yang Hong, Zhang Xiao, Zhuo Lan, Su Jingru, He Xia, Liu Yang, Deng Ze, Meng Fanhui,
Zhao Xiangyang, Wang Weichun, Liu Tao, Shi Zhan, Zhang Xiaochun, Tong Wei, Tan Zhipeng, Zhang Guiyong, Li Xiaoqiang, Wu Xi, Lin Tao, Zhou Hai, Cheng Fangquan, Sun Chenguang,
Zheng Yuanyuan, Li Xiaolu, Huang Shaowa, Zeng Kun, Wei Xueliang, Shen Jinliang, You Lujin, Tang Zhangjie, Tang Yin, Zhu Yajun, and Li Chulong.
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 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
1 Scope
This document defines a wide area network interface for the security, scalability, and interoperability management of heterogeneous distributed storage systems.
This interface uses an object-oriented, XML-based, S-P2PN-based, information-based protocol design to support management in this environment.
Specific requirements for equipment and subsystems.
This document describes the information available to a WBEMClient for an SMI-S compliant CIM WBEMServer.
This document applies to the design, development, and application of block devices in heterogeneous distributed storage systems.
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.
GB/T 36450.2-2021 Information technology storage management Part 2.Common architecture (ISO /IEC 24775-2.2014,
MOD)
GB/T 36450.3-2024 Information technology storage management Part 3.Common profile (ISO /IEC 24775-3.2021, IDT)
GB/T 36450.7-2021 Information technology storage management Part 7.Host elements (ISO /IEC 24775-7.2014,
MOD)
3 Terms and Definitions
The terms and definitions defined in GB/T 36450.2-2021 apply to this document.
Stable
4 Array Configuration File
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
|