1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T Y.3513 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (08/2014) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Cloud Computing Cloud computing Functional requirements of
2、 Infrastructure as a Service Recommendation ITU-T Y.3513 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Services, applications and middleware Y.200Y.299 Network aspects Y.30
3、0Y.399 Interfaces and protocols Y.400Y.499 Numbering, addressing and naming Y.500Y.599 Operation, administration and maintenance Y.600Y.699 Security Y.700Y.799 Performances Y.800Y.899 INTERNET PROTOCOL ASPECTS General Y.1000Y.1099 Services and applications Y.1100Y.1199 Architecture, access, network
4、capabilities and resource management Y.1200Y.1299 Transport Y.1300Y.1399 Interworking Y.1400Y.1499 Quality of service and network performance Y.1500Y.1599 Signalling Y.1600Y.1699 Operation, administration and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 IPTV over NGN Y.1900Y.1999 NEXT GENERATION N
5、ETWORKS Frameworks and functional architecture models Y.2000Y.2099 Quality of Service and performance Y.2100Y.2199 Service aspects: Service capabilities and service architecture Y.2200Y.2249 Service aspects: Interoperability of services and networks in NGN Y.2250Y.2299 Enhancements to NGN Y.2300Y.23
6、99 Network management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Packet-based Networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carrier grade open environment Y.2900Y.2999 FUTURE NETWORKS Y.3000Y.3499 CLOUD COMPUTING Y.3500Y.3999 For further det
7、ails, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.3513 (08/2014) i Recommendation ITU-T Y.3513 Cloud computing Functional requirements of Infrastructure as a Service Summary Recommendation ITU-T Y.3513 introduces the concept of Infrastructure as a Service (IaaS) and describes its
8、 functional requirements. As one of the cloud computing service categories, Infrastructure as a Service provides cloud service customers with computing, storage and network services by cloud service providers. To derive those requirements, relevant use cases are also presented. History Edition Recom
9、mendation Approval Study Group Unique ID* 1.0 ITU-T Y.3513 2014-08-29 13 11.1002/1000/12286 Keywords Cloud computing, Infrastructure as a Service, IaaS, virtual machine. _ * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Rec
10、ommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Y.3513 (08/2014) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The
11、 ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standar
12、dization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information t
13、echnology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Comp
14、liance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other o
15、bligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibility that the practice or implementa
16、tion of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As
17、of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged
18、to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2014 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.3513 (08/2014) iii Table of Contents Page 1 Scope . 1 2 References . 1 3
19、 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 3 6 General description . 3 7 Functional requirements . 4 7.1 Computing service functional requirements . 5 7.2 Storage service functional requirements 6 7.3 Network
20、 service functional requirements . 7 8 Security considerations . 8 Appendix I Use case of Infrastructure as a Service 9 I.1 Use case template . 9 I.2 IaaS use case on infrastructure level 10 I.3 IaaS computing service use case 11 I.4 IaaS storage service use case 15 I.5 IaaS network service use case
21、 16 Appendix II Methodology of mapping use cases and requirements . 17 Bibliography. 18 Rec. ITU-T Y.3513 (08/2014) 1 Recommendation ITU-T Y.3513 Cloud computing Functional requirements of Infrastructure as a Service 1 Scope This Recommendation provides functional requirements and use cases of Infra
22、structure as a Service (IaaS), one of the representative cloud service categories. This Recommendation covers the following: General description of IaaS; Functional requirements of IaaS; Typical IaaS use cases. NOTE The general requirements of IaaS can be found in ITU-T Y.3501. 2 References The foll
23、owing ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Reco
24、mmendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not
25、 give it, as a stand-alone document, the status of a Recommendation. ITU-T X.1601 Recommendation ITU-T X.1601 (2014), Security framework for cloud computing. ITU-T Y.3500 Recommendation ITU-T Y.3500 (2014), Information technology Cloud computing Overview and vocabulary. ITU-T Y.3501 Recommendation I
26、TU-T Y.3501 (2013), Cloud computing framework and high-level requirements. ITU-T Y.3502 Recommendation ITU-T Y.3502 (2014), Information technology Cloud computing Reference architecture. ITU-T Y.3510 Recommendation ITU-T Y.3510 (2013), Cloud computing infrastructure requirements. 3 Definitions 3.1 T
27、erms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 cloud capabilities type ITU-T Y.3500: Classification of the functionality provided by a cloud service to the cloud service customer, based on resource used. NOTE The cloud capabilities types are application
28、capabilities type, infrastructure capabilities type and platform capabilities type. 3.1.2 cloud computing ITU-T Y.3500: Paradigm for enabling network access to a scalable and elastic pool of shareable physical or virtual resources with self-service provisioning and administration on-demand. NOTE Exa
29、mples of resources include servers, operating systems, networks, software, applications, and storage equipment. 2 Rec. ITU-T Y.3513 (08/2014) 3.1.3 cloud service ITU-T Y.3500: One or more capabilities offered via cloud computing invoked using a defined interface. 3.1.4 cloud service category ITU-T Y
30、.3500: Group of cloud services that possess some common set of qualities. NOTE A cloud service category can include capabilities from one or more cloud capabilities types. 3.1.5 cloud service customer ITU-T Y.3500: Party which is in a business relationship for the purpose of using cloud services. 3.
31、1.6 cloud service customer data ITU-T Y.3500: Class of data objects under the control, by legal or other reasons, of the cloud service customer that were input to the cloud service, or resulted from exercising the capabilities of the cloud service by or on behalf of the cloud service customer via th
32、e published interface of the cloud service. NOTE 1 An example of legal controls is copyright. NOTE 2 It may be that the cloud service contains or operates on data that is not cloud service customer data; this might be data made available by the cloud service providers, or obtained from another sourc
33、e, or it might be publicly available data. However, any output data produced by the actions of the cloud service customer using the capabilities of the cloud service on this data is likely to be cloud service customer data, following the general principles of copyright, unless there are specific pro
34、visions in the cloud service agreement to the contrary. 3.1.7 cloud service provider ITU-T Y.3500: Party which makes cloud services available. 3.1.8 cloud service provider data ITU-T Y.3500: Class of data objects, specific to the operation of the cloud service, under the control of the cloud service
35、 provider. NOTE Cloud service provider data includes but is not limited to resource configuration and utilization information, cloud service specific virtual machine, storage and network resource allocations, overall data centre configuration and utilization, physical and virtual resource failure ra
36、tes, operational costs and so on. 3.1.9 Infrastructure as a Service ITU-T Y.3500: Cloud service category in which the cloud capabilities type provided to the cloud service customer is an infrastructure capabilities type. NOTE The cloud service customer does not manage or control the underlying physi
37、cal and virtual resources, but does have control over operating systems, storage, and deployed applications that use the physical and virtual resources. The cloud service customer may also have limited ability to control certain networking components (e.g., host firewalls). 3.1.10 infrastructure cap
38、abilities type ITU-T Y.3500: Cloud capabilities type in which the cloud service customer can provision and use processing, storage or networking resources. 3.1.11 open virtualization format b-ISO/IEC OVF: An open, secure, portable, efficient and extensible format for the packaging and distribution o
39、f software to be run in virtual machines. 3.1.12 party ITU-T Y.3500: Natural person or legal person, whether or not incorporated, or a group of either. 3.1.13 tenant ITU-T Y.3500: Group of cloud service users sharing access to a set of physical and virtual resources. 3.2 Terms defined in this Recomm
40、endation None. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: CPU Central Processing Unit CSC Cloud Service Customer Rec. ITU-T Y.3513 (08/2014) 3 CSP Cloud Service Provider LUN Logical Unit Number IaaS Infrastructure as a Service IP Internet Protocol
41、 I/O Input/Output NaaS Network as a Service NAT Network Address Translation NIC Network Interface Card OVF Open Virtualization Format QoS Quality of Service SLA Service Level Agreement UML Unified Modelling Language VLAN Virtual Local Area Network VM Virtual Machine 5 Conventions The keywords “is re
42、quired to“ indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. The keywords “is recommended“ indicate a requirement which is recommended but which is not absolutely required. Thus this requirement nee
43、d not be present to claim conformance. The keywords “can optionally“ indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendors implementation must provide the option and the feature can be optionally en
44、abled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. In the body of this Recommendation and its annexes, the words shall, shall not, should, and may sometimes appear, in which case they are
45、to be interpreted, respectively, as is required to, is prohibited from, is recommended, and can optionally. The appearance of such phrases or keywords in an appendix or in material explicitly marked as informative are to be interpreted as having no normative intent. 6 General description Infrastruct
46、ure as a Service (IaaS) is one of the representative categories of cloud services, in which the cloud capabilities type provided to the cloud service customer (CSC) is an infrastructure capabilities type. IaaS allows the CSC to use cloud infrastructure resources (processing, storage or networking).
47、Use of cloud infrastructure resources is supported by service functions, which can include the relevant operations. IaaS provides to the CSC the following service functions: computing service functions allow the CSC to provision and use processing resources. CSC can perform operations relevant to pr
48、ocessing resources including machine (physical or virtual machine) lifecycle operations and functions such as virtual machine (VM) migration, backup, snapshot, clone and reservation; 4 Rec. ITU-T Y.3513 (08/2014) storage service functions allow the CSC to use storage resources. The CSC can perform o
49、perations relevant to storage resources including lifecycle operations and functions such as snapshot, backup, input/output (I/O) performance, load balance and reservation; network service functions allow the CSC to use networking resources. The CSC can integrate infrastructure resources using network relevant functions such as IP address, network isolation (e.g., virtual local area network (VLAN), virtual networking (e.g., virtual sw
