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

3                                                       XaaS


            There is a need to guarantee the availability, confidentiality and integrity of the logging records held by the
            NS monitoring and reporting functional component. For multi-tenant cloud services, there is also a need to
            design access to the records so that particular tenants can only gain access to information about their own
            tenancy and about no other tenancy.

            8.3.2.4    NS policy management

            The NS policy management functional component provides capabilities to define, store and retrieve policies
            that apply to network services. Policies can include business, technical, security, privacy and certification
            policies that apply to network services and their usage by NaaS CSCs.
            Some policies can be general and apply to a network service irrespective of the customer concerned. Other
            policies can be specific to a particular customer.

            8.3.2.5    NS automation
            The NS automation functional component provides capabilities for network service delivery including the
            management and execution of network service templates and the orchestration of network services. The NS
            automation functional component holds the network service templates which define the cloud computing
            activities and workflows required to provision and deliver a specific entry in the NS catalogue.

            Network service provisioning can be automated in order to support scalable resource operations, including
            configuration and charging.

            Network service administration activities of NaaS CSC can be capable of being automated and need not
            require any intervention by NaaS CSP.

            The NS automation functional component works with the NS provisioning functional component and the
            service integration functional component to achieve its goals.
            8.3.2.6    NS level management
            The NS level management functional component provides capabilities for managing the service levels of a
            particular network service, aiming to ensure that the network service meets the requirements of the SLA
            which applies to the network service.
            The  NS  level  management  functional  component  manages  the  capacity  and  performance  relating  to  a
            network service. This can involve the application of network service policies (e.g., a placement rule which
            aims to avoid single points of failure).
            The NS level management functional component obtains monitoring information from the NS monitoring
            and reporting functional component in order to measure and record key performance indicators (KPIs) for
            the network service. Capacity of network service is allocated or de-allocated based on the basis of these KPIs.
            The  NS  level  management  functional  component  also  keeps  track  of  the  overall  state  of  allocated  and
            available resources. The comparison of allocated capacity against network service performance KPIs can
            assist in the identification of current or potential bottlenecks, in support of capacity planning.

            8.3.2.7    NS incident and problem management
            The NS incident and problem management functional component provides capabilities for the capture of
            network service incident or problem reports and managing those reports through to resolution.
            Network service incidents and problems can be detected and reported by the NaaS CSP's systems, or they
            can be detected and reported by NaaS CSCs.

            8.3.2.8    NS inventory
            The NS inventory functional component holds information of all network service instances. This information
            is updated during the lifecycle of the network service instances, reflecting changes resulting from execution
            of management operations on these network service instances.





            684
   687   688   689   690   691   692   693   694   695   696   697