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

2                                            Cloud Computing management


                                                      Appendix I

                         Metadata applicability in NaaS service lifecycle management
                            (This appendix does not form an integral part of this Recommendation.)


            This appendix aims to provide applicability examples of NaaS service lifecycle management metadata.


            I.1     Virtual private cloud
            The manipulation of the virtual private cloud (VPC) network may also affect the configuration of physical
            networks. For example, when two new virtual machines (VMs) associated to a given VPC are deployed in two
            different data centres (DCs), the VPC control mechanism needs to generate a virtual private network (VPN)
            between these two data centres for the internal VPC communications. Therefore, the control mechanism for
            a VPC should be able to adjust the underlying network at run time when a CSC requests changes to the VPC
            network or service deployment.

            When a CSC moves from one location to another, which is near to another CSP's data centre, and in the case
            where the network load between these two data centres is low, the CSC's VM(s) should be migrated to the
            new data centre to allow for a better user experience.

            As illustrated by Figure I.1, a VPC corresponds to a combination of cloud computing resources with a VPN
            infrastructure  to  give  NaaS  service  CSCs  the  abstraction  of  a  private  set  of  cloud  resources  that  are
            transparently and securely connected to their own infrastructure. VPCs are created by taking dynamically
            configurable pools of cloud resources and connecting them to enterprise sites with VPNs.


















                                        Figure I.1 – Illustration of virtual private cloud

            The NaaS resource data model needs to be used in this scenario for modelling the physical nodes and links.

            The NaaS service data model, specifically for L3VPN, is needed to model the L3VPN attributes, including, but
            not limited to: tenant ID, VPN site IDs, VPN type, access bandwidth.
            Here, the NaaS policy data model can be described as follows, using event, condition and action (ECA) policy.
            –       Event: a VPC user's location is changed (near to another DC)

            –       Condition: network_load(DC_old, DC_new) < threshold
            –       Action:
                    1)  migrate the VM to the new data center (DC_new);
                    2)  update the VPNs connecting the CSC's services.

            I.2     Instant VPN

            Traditionally, when a NaaS CSP needs to deploy VPN services for an enterprise NaaS CSC, the NaaS CSP will
            send service staff to the NaaS CSC site to make the wired connection between the customer edge (CE) and



            522
   525   526   527   528   529   530   531   532   533   534   535