II.1 VPC The manipulation of the virtualized VPC network may also affect the configuration of physical networks. For example, when two new VMs associated to a given VPC are deployed in two different data centres, the VPC control mechanism needs to generate a 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 the CSC requests changes to the VPC network or service deployment. When the CSC moves from one location to another, which is near to another data centre, and CSP’s in the case the network load between these two data centres is low, the should be CSC’s VM(s) migrated to the new data centre in order to allow for a better user experience. As illustrated by Figure I.1, a virtual private cloud (VPC) corresponds to a combination of cloud computing resources with a VPN infrastructure to give cloud service customers 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 VPC Network resource data model needs to be used in this scenario for modelling the physical nodes and links. Network 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. Network policy data model here can be described as follows, using 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 user's services. Bibliography _______________________
II.1 VPC The manipulation of the virtualized VPC network may also affect the configuration of physical networks. For example, when two new VMs associated to a given VPC are deployed in two different data centres, the VPC control mechanism needs to generate a 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 the CSC requests changes to the VPC network or service deployment. When the CSC moves from one location to another, which is near to another CSP’s data centre, and in the case the network load between these two data centres is low, the CSC’s VM(s) should be migrated to the new data centre in order to allow for a better user experience. As illustrated by Figure I.1, a virtual private cloud (VPC) corresponds to a combination of cloud computing resources with a VPN infrastructure to give cloud service customers 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 VPC Network resource data model needs to be used in this scenario for modelling the physical nodes and links. Network 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. Network policy data model here can be described as follows, using 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 user's services. Bibliography _______________________