Page 34 - Cloud computing: From paradigm to operation
P. 34

1                                    Framework and requirements for cloud computing


            –       Interoperability:  It  is  recommended  that  cloud  service  provided  by  the  CSP  complies  with
                    appropriate specifications and/or standards for allowing these systems to work together;
            –       Portability: It is recommended that cloud service provided by the CSP supports the portability of
                    software assets and the data of cloud service customers (CSCs) with minimum disruption;
            –       Service access: The CSP is recommended to provide CSCs with access to cloud services from a variety
                    of  user  devices.  It  is  recommended  that  CSCs  be  provided  with  a  consistent  experience  when
                    accessing cloud services from different devices;

            –       Service  availability,  service  reliability  and  quality  assurance:  It  is  recommended  that  the  CSP
                    provides end-to-end quality of service assurance, high levels of reliability and continued availability
                    of cloud services according to the service level agreement (SLA) with the CSC.


            7       General requirements for IaaS
            The general requirements for infrastructure as a service (IaaS) derived from the use cases in clause I.2 are as
            follows:
            –       Configuration,  deployment  and  maintenance  of  resources:  The  IaaS  CSP  is  recommended  to
                    configure, deploy and maintain processing, storage and/or networking resources with specific SLAs
                    and charging models to CSCs;
            –       Use and monitoring of resources: The IaaS CSP is recommended to provide the capability for CSCs
                    to use and monitor processing, storage and/or networking resources so that they are able to deploy
                    and run arbitrary software.
            NOTE – Functional requirements for IaaS are provided in [ITU-T Y.3513].


            8       General requirements for NaaS

            The general requirements for network as a service (NaaS) derived from the use cases in clause I.3 are as
            follows:
            –       On-demand  network  configuration:  It  is  required  that  the  NaaS  CSP  provides  the  network
                    capability, which can be configured on demand by the CSC;
            –       Secure connectivity: It is required that the NaaS CSP provides secure connectivity;
            –       QoS-guaranteed  connectivity:  The  NaaS  CSP  is  recommended  to  provide  QoS-guaranteed
                    connectivity according to the negotiated SLA;
            –       Heterogeneous networks compatibility: It is recommended that the NaaS CSP supports network
                    connectivity through heterogeneous networks.
            NOTE – Functional requirements for NaaS are provided in [ITU-T Y.3512].


            9       General requirements for DaaS
            The general requirements for desktop as a service (DaaS) derived from the use cases in clause I.4 are as
            follows:
            –       Configurability of the virtual environment: It is recommended that a user is capable of configuring
                    the  virtual  desktops'  virtual  environment,  such  as  the  central  processing  unit  (CPU),  memory,
                    storage, network, etc.;

            –       Fast boot-up time: DaaS CSP is recommended to provide CSCs with appropriate boot-up time of
                    their virtual desktops;
            –       QoE: DaaS CSP is recommended to provide an acceptable user experience, including the running
                    speed  of  application  programs  and  the  capability  to  select  and  run  various  applications,  when
                    application programs run in their CSC devices;
            –       Single sign-on access control: It is recommended that a CSC is capable to get all DaaS functionality
                    with appropriate security requirements through a single sign-on mechanism.


            26
   29   30   31   32   33   34   35   36   37   38   39