Information technology -- Storage management

Technologie de l'information -- Management du stockage

General Information

Status
Published
Current Stage
4020 - DIS ballot initiated: 5 months
Start Date
25-Aug-2020
Completion Date
25-Aug-2020
Ref Project

RELATIONS

Buy Standard

Draft
ISO/IEC DIS 24775-1 - Information technology -- Storage management
English language
40 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

DRAFT INTERNATIONAL STANDARD
ISO/IEC DIS 24775-1
ISO/IEC JTC 1 Secretariat: ANSI
Voting begins on: Voting terminates on:
2020-08-25 2020-11-17
Information technology — Storage management —
Part 1:
Overview
ICS: 35.200
THIS DOCUMENT IS A DRAFT CIRCULATED
This document is circulated as received from the committee secretariat.
FOR COMMENT AND APPROVAL. IT IS
THEREFORE SUBJECT TO CHANGE AND MAY
NOT BE REFERRED TO AS AN INTERNATIONAL
STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS
FAST TRACK PROCEDURE
BEING ACCEPTABLE FOR INDUSTRIAL,
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
Reference number
NATIONAL REGULATIONS.
ISO/IEC DIS 24775-1:2020(E)
RECIPIENTS OF THIS DRAFT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS,
NOTIFICATION OF ANY RELEVANT PATENT
RIGHTS OF WHICH THEY ARE AWARE AND TO
PROVIDE SUPPORTING DOCUMENTATION. ISO/IEC 2020
---------------------- Page: 1 ----------------------
ISO/IEC DIS 24775-1:2020(E)
1 USAGE

2 Copyright © 2018 SNIA. All rights reserved. All other trademarks or registered trademarks are the property of their

3 respective owners.

The SNIA hereby grants permission for individuals to use this document for personal use only, and for corporations

and other business entities to use this document for internal use only (including internal copying, distribution, and

display) provided that:

1) Any text, diagram, chart, table or definition reproduced shall be reproduced in its entirety with no alter-

ation, and,

2) Any document, printed or electronic, in which material from this document (or any portion hereof) is

reproduced shall acknowledge the SNIA copyright on that material, and shall credit the SNIA for granting

permission for its reuse.

Other than as explicitly provided above, you may not make any commercial use of this document or any portion

thereof, or distribute this document to third parties. All rights not explicitly granted are expressly reserved to SNIA.

Permission to use this document for purposes other than those enumerated above may be requested by e-mailing

tcmd@snia.org. Please include the identity of the requesting individual and/or company and a brief description of

the purpose, nature, and scope of the requested use.

All code fragments, scripts, data tables, and sample code in this SNIA document are made available under the

following license:
BSD 3-Clause Software License
Copyright (c) 2018, The Storage Networking Industry Association.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the

following conditions are met:

• Redistributions of source code must retain the above copyright notice, this list of conditions and the following

disclaimer.

• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the

following disclaimer in the documentation and/or other materials provided with the distribution.

• Neither the name of The Storage Networking Industry Association (SNIA) nor the names of its contributors may

be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY

EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL

THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN

CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY

WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2020

All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may

be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting

on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address

below or ISO’s member body in the country of the requester.
SNIA Technical Position 3
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2020 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC DIS 24775-1:2020(E)
1 USAGE

2 Copyright © 2018 SNIA. All rights reserved. All other trademarks or registered trademarks are the property of their

3 respective owners.

The SNIA hereby grants permission for individuals to use this document for personal use only, and for corporations

and other business entities to use this document for internal use only (including internal copying, distribution, and

display) provided that:

1) Any text, diagram, chart, table or definition reproduced shall be reproduced in its entirety with no alter-

ation, and,

2) Any document, printed or electronic, in which material from this document (or any portion hereof) is

reproduced shall acknowledge the SNIA copyright on that material, and shall credit the SNIA for granting

permission for its reuse.

Other than as explicitly provided above, you may not make any commercial use of this document or any portion

thereof, or distribute this document to third parties. All rights not explicitly granted are expressly reserved to SNIA.

Permission to use this document for purposes other than those enumerated above may be requested by e-mailing

tcmd@snia.org. Please include the identity of the requesting individual and/or company and a brief description of

the purpose, nature, and scope of the requested use.

All code fragments, scripts, data tables, and sample code in this SNIA document are made available under the

following license:
BSD 3-Clause Software License
Copyright (c) 2018, The Storage Networking Industry Association.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the

following conditions are met:

• Redistributions of source code must retain the above copyright notice, this list of conditions and the following

disclaimer.

• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the

following disclaimer in the documentation and/or other materials provided with the distribution.

• Neither the name of The Storage Networking Industry Association (SNIA) nor the names of its contributors may

be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY

EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL

THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN

CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY

WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

SNIA Technical Position 3
© ISO/IEC 2020 – All rights reserved
---------------------- Page: 3 ----------------------
ISO/IEC DIS 24775-1:2020(E)
DISCLAIMER

The information contained in this publication is subject to change without notice. The SNIA makes no

warranty of any kind with regard to this specification, including, but not limited to, the implied warranties

of merchantability and fitness for a particular purpose. The SNIA shall not be liable for errors contained

herein or for incidental or consequential damages in connection with the furnishing, performance, or use

of this specification.
Suggestions for revisions should be directed to http://www.snia.org/feedback/.

Copyright © 2003-2020 SNIA. All rights reserved. All other trademarks or registered trademarks are the

property of their respective owners.

Portions of the CIM Schema are used in this document with the permission of the Distributed

Management Task Force (DMTF). The CIM classes that are documented have been developed and

reviewed by both the SNIA and DMTF Technical Working Groups. However, the schema is still in

development and review in the DMTF Working Groups and Technical Committee, and subject to change.

© ISO/IEC 2020 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC DIS 24775-1:2020(E)
REVISION HISTORY
Revision 1
Date
April 14, 2017
SCRs Incorporated and other changes
None
Comments
Editorial notes and DRAFT material are displayed.
Revision 2
Date
February 16, 2018
SCRs Incorporated and other changes
None.
Comments
Substantial editorial clean up to align CIM references with existing XML.
Revision 3
Date
August 14, 2018
SCRs Incorporated and other changes
None.
Comments
None.
Revision 4
Date
October 24, 2019
SCRs Incorporated and other changes
None.
Comments
Minor editorial clean up to create corrected technical position.
Revision 5
Date
March 23, 2020
SCRs Incorporated and other changes
None.
© ISO/IEC 2020 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC DIS 24775-1:2020(E)
Comments

Revision number updated to keep all books in sync after a minor update to the architecture book.

Suggestion for changes or modifications to this document should be sent to the SNIA Storage Management

Initiative Technical Work Group (SMI TWG) at http://www.snia.org/feedback/
© ISO/IEC 2020 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC DIS 24775-1:2020(E)
1 INTENDED AUDIENCE

2 This document is intended for use by individuals and companies engaged in developing, deploying, and

3 promoting interoperable multi-vendor SANs through the Storage Networking Industry Association (SNIA)

4 organization.
5 CHANGES TO THE SPECIFICATION

6 Each publication of this specification is uniquely identified by a three-level identifier, comprised of a

7 version number, a release number and an update number. The current identifier for this specification is

8 version 1.8.0. Future publications of this specification are subject to specific constraints on the scope of

9 change that is permissible from one publication to the next and the degree of interoperability and

10 backward compatibility that should be assumed between products designed to different publications of

this standard. The SNIA has defined three levels of change to a specification:

• Major Revision: A major revision of the specification represents a substantial change to the underlying scope

or architecture of the SMI-S API. A major revision results in an increase in the version number of the version

identifier (e.g., from version 1.x.x to version 2.x.x). There is no assurance of interoperability or backward

compatibility between releases with different version numbers.

• Minor Revision: A minor revision of the specification represents a technical change to existing content or an

adjustment to the scope of the SMI-S API. A minor revision results in an increase in the release number of

the specification’s identifier (e.g., from x.1.x to x.2.x). Minor revisions with the same version number preserve

interoperability and backward compatibility.

• Update: An update to the specification is limited to minor corrections or clarifications of existing specification

content. An update will result in an increase in the third component of the release identifier (e.g., from x.x.1 to

x.x.2). Updates with the same version and minor release levels preserve interoperability and backward

compatibility.
TYPOGRAPHICAL CONVENTIONS
Maturity Level

In addition to informative and normative content, this specification includes guidance about the maturity

of emerging material that has completed a rigorous design review but has limited implementation in

commercial products. This material is clearly delineated as described in the following sections. The

typographical convention is intended to provide a sense of the maturity of the affected material, without

29 altering its normative content. By recognizing the relative maturity of different sections of the standard, an

30 implementer should be able to make more informed decisions about the adoption and deployment of

31 different portions of the standard in a commercial product.

This specification has been structured to convey both the formal requirements and assumptions of the

33 SMI-S API and its emerging implementation and deployment lifecycle. Over time, the intent is that all

34 content in the specification will represent a mature and stable design, be verified by extensive

35 implementation experience, assure consistent support for backward compatibility, and rely solely on

36 content material that has reached a similar level of maturity. Unless explicitly labeled with one of the

subordinate maturity levels defined for this specification, content is assumed to satisfy these

37 requirements and is referred to as “Finalized”. Since much of the evolving specification

38 content in any given release will not have matured to that level, this specification defines three

subordinate levels of implementation maturity that identify important aspects of the content’s increasing

maturity and stability. Each subordinate maturity level is defined by its level of implementation

experience, its stability and its reliance on other emerging standards. Each subordinate maturity level is

identified by a unique typographical tagging convention that clearly distinguishes content at one maturity

model from content at another level.
SNIA Technical Position 9
© ISO/IEC 2020 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC DIS 24775-1:2020(E)
46 Experimental Maturity Level

No material is included in this document unless its initial architecture has been completed and reviewed.

Some content included in this document has complete and reviewed design, but lacks implementation

experience and the maturity gained through implementation experience. This content is included in order

to gain wider review and to gain implementation experience. This material is referred to as

“Experimental”. It is presented here as an aid to implementers who are interested in likely future

developments within the SMI specification. The contents of an Experimental profile may change as

implementation experience is gained. There is a high likelihood that the changed content will be included

in an upcoming revision of the specification. Experimental material can advance to a higher maturity level

as soon as implementations are available. Figure 1 is a sample of the typographical convention for

Experimental content.
EXPERIMENTAL
Experimental content appears here.
EXPERIMENTAL
Figure 1 - Experimental Maturity Level Tag
Implemented Maturity Level

Profiles for which initial implementations have been completed are classified as “Implemented”. This

indicates that at least two different vendors have implemented the profile, including at least one provider

implementation. At this maturity level, the underlying architecture and modeling are stable, and changes

in future revisions will be limited to the correction of deficiencies identified through additional

implementation experience. Should the material become obsolete in the future, it must be deprecated in a

minor revision of the specification prior to its removal from subsequent releases. Figure 2 is a sample of

the typographical convention for Implemented content.
IMPLEMENTED
Implemented content appears here.
IMPLEMENTED
Figure 2 - Implemented Maturity Level Tag
Stable Maturity Level

Once content at the Implemented maturity level has garnered additional implementation experience, it

can be tagged at the Stable maturity level. Material at this maturity level has been implemented by three

different vendors, including both a provider and a client. Should material that has reached this maturity

level become obsolete, it may only be deprecated as part of a minor revision to the specification. Material

at this maturity level that has been deprecated may only be removed from the specification as part of a

major revision. A profile that has reached this maturity level is guaranteed to preserve backward

compatibility from one minor specification revision to the next. As a result, Profiles at or above the Stable

© ISO/IEC 2020 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/IEC DIS 24775-1:2020(E)

76 maturity level shall not rely on any content that is Experimental. Figure 3 is a sample of the typographical

77 convention for Implemented content.
STABLE
Stable content appears here.
STABLE
Figure 3 - Stable Maturity Level Tag
78 Finalized Maturity Level

79 Content that has reached the highest maturity level is referred to as “Finalized.” In addition to satisfying

80 the requirements for the Stable maturity level, content at the Finalized maturity level must solely depend

81 upon or refine material that has also reached the Finalized level. If specification content depends upon

82 material that is not under the control of the SNIA, and therefore not subject to its maturity level

83 definitions, then the external content is evaluated by the SNIA to assure that it has achieved a

84 comparable level of completion, stability, and implementation experience. Should material that has

85 reached this maturity level become obsolete, it may only be deprecated as part of a major revision to the

86 specification. A profile that has reached this maturity level is guaranteed to preserve backward

87 compatibility from one minor specification revision to the next. Over time, it is hoped that all specification

content will attain this maturity level. Accordingly, there is no special typographical convention, as there is

with the other, subordinate maturity levels. Unless content in the specification is marked with one of the

typographical conventions defined for the subordinate maturity levels, it should be assumed to have

reached the Finalized maturity level.
Deprecated Material

Non-Experimental material can be deprecated in a subsequent revision of the specification. Sections

identified as “Deprecated” contain material that is obsolete and not recommended for use in new

development efforts. Existing and new implementations may still use this material, but shall move to the

newer approach as soon as possible. The maturity level of the material being deprecated determines how

long it will continue to appear in the specification. Implemented content shall be retained at least until the

next revision of the specialization, while Stable and Finalized material shall be retained until the next

major revision of the specification. Providers shall implement the deprecated elements as long as it

appears in the specification in order to achieve backward compatibility. Clients may rely on deprecated

elements, but are encouraged to use non-deprecated alternatives when possible.

Deprecated sections are documented with a reference to the last published version to include the

deprecated section as normative material and to the section in the current specification with the

replacement. Figure 4 contains a sample of the typographical convention for deprecated content.

DEPRECATED
Content that has been deprecated appears here.
100
101
DEPRECATED
102
Figure 4 - Deprecated Tag
103
104
105
SNIA Technical Position 11
© ISO/IEC 2020 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC DIS 24775-1:2020(E)
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
© ISO/IEC 2020 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/IEC DIS 24775-1:2020(E)
Contents

Revision History .................................................................................................................................... 5

List of Figures ..................................................................................................................................... 13

List of Tables ....................................................................................................................................... 15

Foreword ............................................................................................................................................. 17

1 Scope ............................................................................................................................................ 19

2 Normative References................................................................................................................... 21

2.1 Overview ............................................................................................................................. 21

2.2 Approved references........................................................................................................... 21

2.3 References under development .......................................................................................... 21

3 Term, Definitions, Symbols, Abbreviations, and Conventions....................................................... 23

4 Introduction.................................................................................................................................... 25

4.1 Preamble............................................................................................................................. 25

4.2 Business Rationale ............................................................................................................. 25

4.3 Interface Definition .............................................................................................................. 26

4.4 Technology Trends ............................................................................................................. 28

4.5 Management Environment .................................................................................................. 29

4.6 Architectural Objectives ...................................................................................................... 30

4.7 Disclaimer ........................................................................................................................... 31

5 Overview........................................................................................................................................ 33

5.1 Base Capabilities ................................................................................................................ 33

5.2 Object Oriented ................................................................................................................... 33

6 Functionality Matrix........................................................................................................................ 37

6.1 Overview ............................................................................................................................. 37

6.2 Multi-Level Model Of Networked Storage Management Functionality ................................ 37

6.3 FCAPS ................................................................................................................................ 38

6.4 Management Functionality Within Each Level Of The Model ............................................. 38

6.5 Referring To Levels And Capabilities In The Multi-level Model........................................... 39

6.6 Functionality Descriptions in SMI-S Profiles ....................................................................... 39

6.7 Capabilities of This Version.................................................................................................39

7 Operational Environment............................................................................................................... 43

7.1 General ............................................................................................................................... 43

7.2 Using this Specification ....................................................................................................... 44

7.3 Language Bindings ............................................................................................................. 45

SNIA Technical Position 11
© ISO/IEC 2020 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC DIS 24775-1:2020(E)
© ISO/IEC 2020 – All rights reserved
---------------------- Page: 12 ----------------------
ISO/IEC DIS 24775-1:2020(E)
LIST OF FIGURES

Figure 1 - Experimental Maturity Level Tag ......................................................................................... 8

Figure 2 - Implemented Maturity Level Tag ......................................................................................... 8

Figure 3 - Stable Maturity Level Tag.................................................................................................... 9

Figure 4 - Deprecated Tag................................................................................................................... 9

Figure 5 - Interface Functions ............................................................................................................ 26

Figure 6 - Large SAN Topology ......................................................................................................... 29

Figure 7 - Example Client Server Distribution in a SAN..................................................................... 30

Figure 8 - Object Model/Server Relationship ..................................................................................... 34

Figure 9 - Canonical Inheritance........................................................................................................ 35

Figure 10 - Operational Environment................................................................................................. 44

SNIA Technical Position 13
© ISO/IEC 2020 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/IEC DIS 24775-1:2020(E)
© ISO/IEC 2020 – All rights reserved
---------------------- Page: 14 ----------------------
ISO/IEC DIS 24775-1:2020(E)
LIST OF TABLES

Table 1 - Functionality Matrix..............................................................................................................................37

SNIA Technical Position 15
© ISO/IEC 2020 – All rights reserved
---------------------- Page: 15 ----------------------
ISO/IEC DIS 24775-1:2020(E)
© ISO/IEC 2020 – All rights reserved
---------------------- Page: 16 ----------------------
ISO/IEC DIS 24775-1:2020(E)
FOREWORD

The Overview part of the Storage Management Technical Specification contains informative clauses that

provide an overview of how SMI-S works. It is a useful base for understanding the details of the technical

specification. While the normative information of the specification is contained in other parts, this part

provides high-level introductory material on key concepts of the specification.
Parts of this Standard
This standard is subdivided in the following parts:
• Storage Management Technical Specification, Part 1 Overview, 1.8.0 Rev 4

• Storage Management Technical Specification, Part 2 Common Architecture, 1.8.0 Rev 4

• Storage Management Technical Specification, Part 3 Common Profiles, 1.8.0 Rev 4

• Storage Management Technical Specification, Part 4 Block Devices, 1.8.0 Rev 4
• Storage Management Technical Specification, Part 5 Filesystems, 1.8.0 Rev 4
• Storage Management Technical Specification, Part 6 Fabric, 1.8.0 Rev 4
• Storage Management Technical Specification, Part 7 Host Elements, 1.8.0 Rev 4

• Storage Management Technical Specification, Part 8 Media Libraries, 1.8.0 Rev 4

SNIA Web Site

Current SNIA practice is to make updates and other information available through their web site at

http://www.snia.org
SNIA Address

Requests for interpretation, suggestions for improvement and addenda, or defect reports are welcome. They

should be sent via the SNIA Feedback Portal at http://www.snia.org/feedback/ or by mail to the Storage Networking

Industry Association, 4360 ArrowsWest Drive, Colorado Springs, Colorado 80907, U.S.A.

SNIA Technical Position 17
© ISO/IEC 2020 – All rights reserved
---------------------- Page: 17 ----------------------
ISO/IEC DIS 24775-1:2020(E)
© ISO/IEC 2020 – All rights reserved
---------------------- Page: 18 ----------------------
ISO/IEC DIS 24775-1:2020(E)
1 1 Scope
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.