Professional Documents
Culture Documents
Garg 2021
Garg 2021
They are lightweight and isolated Linux processes present a novel networking architecture that amal-
that deploy and run distributed applications on gamates SDN and NFV paradigms while simulta-
VNF infrastructure at the cost of reduced isola- neously extending their capabilities using an edge
tion. With containerization, an application runs computing platform. Further, it also leverages the
quickly and reliably from one computing environ- concept of mixed VNF deployment using VMs
ment to another. Moreover, it has several benefits and containers. Although similar approaches have
in comparison to VM technology, including low been proposed in the literature, their extension to
resource overhead, agility to launch new service generic platforms/domains limit their adaptability
or upgrade existing service at runtime, resource in the ever growing Energy Internet ecosystem.
scalability according to demands, faster deploy- Further, the proposed work also puts forward the
ment and portability of new services, resiliency concept of mixed VNF deployment, which has
against failures, and so on. Further, applications not been explored to its full potential. Thus, to
like mobile edge computing (MEC), network slic- the best of our knowledge, this is the first initiative
ing, and cloud radio access networks (cRANs) of its kind that achieves network agility and flexi-
also demand containers for highly automated bility in the Energy Internet domain.
deployment of services in the 5G network. How-
ever, their practical deployment is limited by their Research Contributions of This Work
support for VNF deployment on a certain set of In this article, we present a novel architecture for
OSs, namely Linux, Windows, and Solaris. On the SDN integrated with NFV specifically for the Ener-
contrary, there are numerous NFV infrastructures gy Internet ecosystem by leveraging the advantag-
that do not yet support the above mentioned OSs es of edge computing. In the considered setup,
currently. Thus, using container-only deployments the deployment of VNFs is achieved using both
for VNF deployment is not feasible, particularly virtualization and containerization (a lightweight
for the present heterogeneous architecture sur- means to achieve virtualization). The key contri-
faced by the edge and the cloud [10]. butions of the proposed work are summarized as
follows:
Motivation • The designed framework presents an
The growing interconnections in the Energy Inter- enabling network solution to andEnergy
net ecosystem include networks, spanning fleets Internet utility provider with the means of
of EVs, groups of homes, industrial sectors, build- automated provisioning, configuration, and
ings, and so on. Thus, the heterogeneous data optimization of NFVs. In other words, the
generated by these interconnected and complex on-demand provisioning of network func-
networks is growing at an exponential rate. Its tions can be referred to as VNF as a service
real-time processing and transmission to the cen- (VNF-aaS). The proposed framework extends
tralized cloud infrastructure for deep analysis is an the capabilities of the SDN platform along
important research direction. In this vein, here we with NFV to achieve the same.
instances, which otherwise are executed on application programming interface (API). The
hardware elements. NFV also helps in the rapid control plane, on the other hand, incorporates
deployment of network functionalities as software SDN’s controller and NFV manager (details of
components with ease of configuration facility. the NFV manager follow). Its capabilities are
Additionally, it supports elastic scaling of network exposed to the application plane by leveraging
services. Essentially, NFV supports network slic- the northbound API. The uppermost application
ing by logically segregating the network and its plane takes care of different networking services/
resources. This is achieved by virtualization on the applications, each having access to a certain class
physical network; hence, the name NFV. Some of underlying resources.
prominent examples of NFV functions include
TCP optimization, firewall, NAT, load balancing, NFV Management and Orchestration Plane
and so on [11]. The roles and responsibilities of this plane are
On the other hand, the paradigm of SDN aligned to the NFV manager, which allows it to
is characterized by the decoupling of the con- achieve VNF management and orchestration. It
trol plane from the data plane. Further, it is also achieves the same using three significant func-
notable for its ability to centralize its control tional blocks: NFV orchestrator (NFVO), VNF
intelligence. The entity where the central control manager (VNFM), and virtualized infrastructure
rests is referred to as the SDN controller, that is, manager (VIM). Here, the NFVO helps in man-
centralized software to implement the network aging the life cycle activities of network services,
functionality. SDN operates using the OpenFlow while the VNFM coordinates the life cycle of
protocol (OFP) for control information transmis- VNFs. The VIM, on the other hand, manages the
sion from the SDN controller to the forwarding NFV infrastructure resources in order to provide
elements [12]. the required resources for VNF deployment and
Essentially, SDN comprises three important connectivity (details follow).
planes: the data, control, and application planes. It is worth mentioning here that the terms net-
SDN’s data plane comprises the OpenFlow work services and service chains are often inter-
switches and routers (a.k.a., forwarding elements) changeable. However, their respective meanings
that form the backbone of the networking plat- differ a lot. For instance, a network service is
form. The capabilities of this plane are made avail- essentially the final product that is delivered to the
able to the upper plane using the southbound end user and is typically characterized by its func-
160
140
termination.
120
Observation and Analysis
100
In this section, evaluation of the proposed
80 scheme for VNF placement in the hybrid virtual-
60 ized environment over the edge-cloud integration
40 is performed. For performance evaluation, the
20
proposed scheme has been accessed using the
widely used MOEA framework, a Java-based open
0
50 100 150 200 250 300 350 400 450 source platform for evaluating the performance of
Number of VNFs various multi-objective evolutionary algorithms.
(b) The simulation setup considered a total of 20
7500
nDCs and 1 cloud DC with variable configura-
7000
Propsed Scheme tions. In addition to this, we also assumed a total
Existing Scheme
of 150 containers and 150 VMs to be available
Aveage Overhead (ms)
6500
in the considered edge-cloud setup with differ-
6000
ent CPU, memory, and storage characteristics.
5500
The number of VNFs waiting to be deployed was
5000
assumed to be in the range of [20, 450]. Further,
4500
the proposed scheme has been compared with
4000
an existing scheme for VNF placement on VMs.
3500 The obtained results are summarized as follows.
3000 The evaluation results have been outlined on
2500 the basis of three different evaluation criteria: pro-
2000 cessing time, number of migrations, and overhead
50 100 150 200 250 300 350 400 450
analysis. The description is illustrated below.
Number of VNFs Processing Time Analysis: It refers to the total
(c) time for executing a particular VNF on a physical/
virtual machine in addition to the time to wait for
FIGURE 4. An illustrative comparison of the proposed a free virtualized instance for execution. The total
scheme against the existing scheme: a) process-
time is expressed in terms of seconds.
ing time analysis; b) number of migrations;
Number of Migrations: This metric refers to
c) overhead analysis.
the number of VNF requests that need to be
migrated to the core cloud in lieu of insufficient
allows a single VM/container to be allocated to resources at the edge or longer waiting time for
N
a particular VNF. Constraint C 2 (i.e., Sj=1 Xij Pij VNF deployment. A higher number of migrations
≤ PRi) refers to the upper limit on the processing lead to higher overall overhead.
time of a particular VNF across different virtual- Overhead Analysis: This refers to the addition-
ized instances. Here, the variable PRi refers to the al overall associated with the deployment of VNFs
upper limit on the processing time of the ith VNF. on VMs and containers. It refers to the total time
The rest of the constraints (C3, C4, C5) restrict the required for instantiation and booting of VMs and
number of resources (namely CPU cores, main containers. It is expressed in milliseconds.
memory, and storage) allocated for the execution Figure 4a depicts the overall processing time
M
of a particular VNF. Here, C3 = Si=1 Xij Ci ≤ Cj, analysis of the proposed scheme relative to the
M M
C4 = Si=1 Xij Mi ≤ Mj, and C5 = Si=1 Xij Si ≤ Sj; existing scheme. It is evident from the figure that
wherein the variables Ci, M i, and S i refer to the the processing time for both schemes increases
resource requirement of the ith VNF in terms of with increasing VNF requests for deployment.
CPU cores, main memory, and storage, respec- More importantly, the processing time in the
tively. Likewise, the upper limit on these resourc- VM-only execution setup shows enhanced dura-
es with respect to the jth virtualized instance is tions of processing VNF requests relative to the
expressed as Cj, Mj, and Sj. proposed scheme. This can be attributed to lim-