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.3522 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (09/2016) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES Cloud Computing End-t
2、o-end cloud service lifecycle management requirements Recommendation ITU-T Y.3522 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Service
3、s, applications and middleware Y.200Y.299 Network aspects Y.300Y.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 Service
4、s and applications Y.1100Y.1199 Architecture, access, network 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 Char
5、ging Y.1800Y.1899 IPTV over NGN Y.1900Y.1999 NEXT GENERATION NETWORKS 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 a
6、nd networks in NGN Y.2250Y.2299 Enhancements to NGN Y.2300Y.2399 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 NETW
7、ORKS Y.3000Y.3499 CLOUD COMPUTING Y.3500Y.3999 INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES General Y.4000Y.4049 Definitions and terminologies Y.4050Y.4099 Requirements and use cases Y.4100Y.4249 Infrastructure, connectivity and networks Y.4250Y.4399 Frameworks, architectures and protocols Y.
8、4400Y.4549 Services, applications, computation and data processing Y.4550Y.4699 Management, control and performance Y.4700Y.4799 Identification and security Y.4800Y.4899 Evaluation and assessment Y.4900Y.4999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.3522 (
9、09/2016) i Recommendation ITU-T Y.3522 End-to-end cloud service lifecycle management requirements Summary Recommendation ITU-T Y.3522 provides an overview of end-to-end (E2E) cloud service lifecycle management by specifying cloud service lifecycle metadata, the cloud service lifecycle management fra
10、mework, cloud service lifecycle management stages and the relationship with cloud computing reference architecture. This Recommendation also provides E2E cloud service lifecycle management functional requirements derived from the corresponding typical use cases. History Edition Recommendation Approv
11、al Study Group Unique ID* 1.0 ITU-T Y.3522 2016-09-29 13 11.1002/1000/13020 Keywords Cloud service lifecycle management, end-to-end, functional requirements, metadata, model, stage. * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed
12、by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Y.3522 (09/2016) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (
13、ICTs). The 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 Telecommunicati
14、on Standardization 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 inf
15、ormation technology 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 ag
16、ency. Compliance 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 so
17、me other obligatory 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
18、implementation 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 pr
19、ocess. As 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 stron
20、gly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2016 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.3522 (09/2016) iii Table of Contents Page 1 Scope . 1 2 Refere
21、nces . 1 3 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 Overview of E2E cloud service lifecycle management 3 6.1 Cloud service lifecycle metadata 4 6.2 Cloud service lifecycle management framework . 4 6.3 Cl
22、oud service lifecycle management stages . 6 6.4 Relationship with cloud computing reference architecture 7 7 E2E cloud service lifecycle management functional requirements 8 7.1 Service management interface 8 7.2 Self-service . 8 7.3 Service maintenance . 8 7.4 Reporting 8 7.5 Composite applications
23、 or mash-ups 8 7.6 Traditional business processes . 9 7.7 Decommissioning . 9 7.8 Policy 9 7.9 Lifecycle stage management 9 7.10 Service automation and continuous delivery 9 7.11 Metadata management 9 8 Security considerations . 9 Appendix I E2E cloud service lifecycle management use cases 10 I.1 Se
24、rvice management interface 10 I.2 Self-service use case . 12 I.3 Service maintenance use case . 12 I.4 Composite applications or mash-ups use case 12 I.5 Traditional business processes use case . 13 I.6 Decommissioning use case . 13 I.7 Policy use case 14 I.8 Lifecycle stage management use case 14 I
25、.9 Service automation and continuous delivery use case . 15 I.10 Metadata management use case 15 Bibliography. 16 Rec. ITU-T Y.3522 (09/2016) 1 Recommendation ITU-T Y.3522 End-to-end cloud service lifecycle management requirements 1 Scope This Recommendation specifies the functional requirements of
26、end-to-end (E2E) cloud service lifecycle management. This Recommendation comprises the following: cloud service lifecycle metadata; cloud service lifecycle management framework; cloud service lifecycle management stages; relationship with cloud computing reference architecture; functional requiremen
27、ts and typical use cases of cloud service lifecycle management. 2 References The following 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.
28、 All Recommendations and other references are subject to revision; users of this Recommendation 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
29、 regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T M.3030 Recommendation ITU-T M.3030 (2002), Telecommunications Markup Language (tML) framework. ITU-T X.1601 Recommendation ITU-T X.1601 (201
30、5), Security framework for cloud computing. ITU-T Y.3500 Recommendation ITU-T Y.3500 (2014) | ISO/IEC 17788:2014, Information technology Cloud computing Overview and vocabulary. ITU-T Y.3502 Recommendation ITU-T Y.3502 (2014) | ISO/IEC 17789:2014, Information technology Cloud computing Reference arc
31、hitecture. ITU-T Y.3511 Recommendation ITU-T Y.3511 (2014), Framework of inter-cloud computing. ITU-T Y.3520 Recommendation ITU-T Y.3520 (2015), Cloud computing framework for end to end resource management. ITU-T Y.3521 Recommendation ITU-T Y.3521/M.3070 (2016), Overview of end-to-end cloud computin
32、g management. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 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 an
33、d administration on-demand. NOTE Examples of resources include servers, operating systems, networks, software, applications and storage equipment. 2 Rec. ITU-T Y.3522 (09/2016) 3.1.2 cloud service ITU-T Y.3500: One or more capabilities offered via cloud computing invoked using a defined interface. 3
34、.1.3 cloud service customer ITU-T Y.3500: Party which is in a business relationship for the purpose of using cloud services. NOTE A business relationship does not necessarily imply financial agreements. 3.1.4 cloud service partner ITU-T Y.3500: Party which is engaged in support of, or auxiliary to,
35、activities of either the cloud service provider or the cloud service customer, or both. 3.1.5 cloud service provider ITU-T Y.3500: Party which makes cloud services available. 3.1.6 inter-cloud computing ITU-T Y.3511: The paradigm for enabling the interworking between two or more cloud service provid
36、ers. NOTE Inter-cloud computing is also referred as inter-cloud. 3.1.7 metadata ITU-T M.3030: Data that describes other data. 3.1.8 role ITU-T Y.3502: A set of activities that serves a common purpose. 3.1.9 product catalogue ITU-T Y.3502: A listing of all the cloud service products which cloud servi
37、ce providers make available to cloud service customers. 3.1.10 service catalogue ITU-T Y.3502: A listing of all the cloud services of a particular cloud service provider. 3.1.11 service management interface (SMI) ITU T Y.3521: Interface that provides a set of management capabilities exposed by a clo
38、ud service through which the cloud service can be managed. NOTE For additional details of SMI concepts, see ITU T Y.3520 and b-TMF TR198. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 functional interface: Interface that provides a set of functional
39、capabilities exposed by a cloud service through which the cloud service can be consumed. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: CSC Cloud Service Customer CSN Cloud Service Partner CSP Cloud Service Provider CSU Cloud Service User CT Communica
40、tions Technology E2E End-to-End FI Functional Interface IT Information Technology OSS Operational Support Systems QoS Quality of Service SMI Service Management Interface WSDL Web Services Description Language Rec. ITU-T Y.3522 (09/2016) 3 5 Conventions The keywords “is required to“ indicate a requir
41、ement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. The keywords “is recommended“ indicate a requirement which is recommended but which is not absolutely required. Thus this requirement need not be present to claim conforma
42、nce. In the body of this Recommendation and its appendixes, the words shall, shall not, should, and may sometimes appear, in which case they are to be interpreted, respectively, as is required to, is prohibited from, is recommended, and can optionally. The appearance of such phrases or keywords in a
43、n appendix or in material explicitly marked as informative are to be interpreted as having no normative intent. 6 Overview of E2E cloud service lifecycle management Nowadays, cloud computing technologies are widely used in both information technology (IT) and communications technology (CT) industrie
44、s. Telecommunication operators use cloud-based technologies to deliver cloud services to their users as well as to leverage their telecommunication services and network. This allows for automation and acceleration provisioning of cloud services across cloud and non-cloud facilities. Therefore, effec
45、tive cloud service lifecycle management becomes one of the most important challenges from telecommunication operators perspectives. Cloud service lifecycle management integrates and optimizes processes such as service provisioning, service assurance, service fulfilment, service charging and service
46、change management for particular workloads respecting relevant governance and polices. In both telecommunication and cloud computing environments, cloud service lifecycle management has to be considered in an E2E manner which means service lifecycle management chains across cloud and non-cloud facil
47、ities. In practice, cloud service lifecycle management could be achieved by using a service management interface (SMI) based common model for E2E cloud computing management supported by operational support systems (OSS), see ITU-T Y.3521. The OSS encompass the set of operational related management c
48、apabilities, including service catalogue, provisioning, monitoring and reporting, service policy management, service automation, etc., in order to manage and control cloud services offered to cloud service customers (CSCs), see ITU-T Y.3502. OSS realize the required E2E cloud service lifecycle manag
49、ement functionalities by using service management interfaces (SMIs). These operational related management capabilities can help to achieve the service lifecycle management objective with the pre-defined distributed metadata in each stage. The consistent approach to service lifecycle management includes representative definitions for the particular stages which cloud services pass through. This is based on a lifecycle management metadata model, which can
