Systems, Man & Cybernetics - October 2017 - 37

in Figure 2. These modules were designed with a pluggable
architecture so that new resources can be added to the
infrastructure by simply modifying or creating a new module while maintaining various resource management
approaches for different infrastructures. Each module was
described previously [9] and is briefly summarized in the
following sections.
Resource Orchestrator
The resource orchestrator (RO) acts as a broker inside the
FELIX SDI architecture that can proxy requests between
the experimenter and the various resource managers (RM)
in the infrastructure for the allocation and provisioning of
resources according to predefined policies. As shown in
Figure 3, additional abstraction and mapping may take
place at the RO level to complete the experimenter's
request with varying degrees of granularity. All of this is
performed in a technologically agnostic way that is dependent on the configuration and policies defined by the
domain. The RO delegates requests recursively [9] between
the ROs of other federated infrastructures through a hybrid
deployment, combining centralized and distributed ROs. To
properly handle requests, the RO maintains an aggregated
topological view of its managed, underlying infrastructures
and any detected error conditions from the underlying
RMs. This allows the RO to detect where resources can be
provisioned to meet the experimenter's requests.

RMs
All RMs provide control mechanisms for the various
resources in the test bed by advertising the resources
under its control, receiving requests, and informing of success/failure events. The transit network resource manager
(TNRM) provides mechanisms for network connectivity
between particular domains using the NSI-CS protocol for
NSI transport networks and generic routing encapsulation
(GRE) tunneling protocols for connections over the Internet (Figure 4). A single TNRM is responsible for a group of
particular network resources, which belong to a single,
managed network domain. Each domain, however, can use
different L1 and L2 network technologies and may be controlled by specific interfaces, systems, or protocols that are
technology dependent.
The stitching entity resource manager (SERM) controls
the stitching entity, which is a network element that provides necessary translation mechanisms for slice creation
on the L2 protocol stack. This hides the multidomain transport network topology -complexity from the user, allowing
for an easier creation of SDI slices.
The SDNRM provides control of SDN-enabled domains
using programmable, OpenFlow-enabled network devices
to control network behavior through flow rules that are
inserted via a software controller that communicates with
the physical network devices. In shared environments,
such as data centers, proper network isolation is required

User Access

GENIv3 API
MMS

Region
(Europe, Japan, etc.)

MCBAS

MRO
GENIv3 API
RO

GENIv3
API
MS

SNMP

GENIv3
API

SDNRM

CRM

XEN/KVM
API

Single
FELIX
Facility

C-BAS

OpenFlow

GENIv3
API
SERM

OpenFlow

GENIv3
API
TNRM
NSI
OpenFlow/OVSDB

Figure 2. A detail of the FELIX management stack showing interactions between northbound and southbound

interfaces of RMs and physical resources, and side interactions between RO and C-BAS for AAA. MRO: master Ro;
MMS: master monitoring system; MCBAS: master certificate-based AAA for SDN experimental facilities; C-BAS:
certificate-based AAA for SDN experimental facilities; SNMP: simple network management protocol; KVM: kernelbased virtual machine; OVSDB: open vSwitch database management protocol.

	

O c tob e r 2017

IEEE SYSTEMS, MAN, & CYBERNETICS MAGAZINE	

37



Table of Contents for the Digital Edition of Systems, Man & Cybernetics - October 2017

Systems, Man & Cybernetics - October 2017 - Cover1
Systems, Man & Cybernetics - October 2017 - Cover2
Systems, Man & Cybernetics - October 2017 - 1
Systems, Man & Cybernetics - October 2017 - 2
Systems, Man & Cybernetics - October 2017 - 3
Systems, Man & Cybernetics - October 2017 - 4
Systems, Man & Cybernetics - October 2017 - 5
Systems, Man & Cybernetics - October 2017 - 6
Systems, Man & Cybernetics - October 2017 - 7
Systems, Man & Cybernetics - October 2017 - 8
Systems, Man & Cybernetics - October 2017 - 9
Systems, Man & Cybernetics - October 2017 - 10
Systems, Man & Cybernetics - October 2017 - 11
Systems, Man & Cybernetics - October 2017 - 12
Systems, Man & Cybernetics - October 2017 - 13
Systems, Man & Cybernetics - October 2017 - 14
Systems, Man & Cybernetics - October 2017 - 15
Systems, Man & Cybernetics - October 2017 - 16
Systems, Man & Cybernetics - October 2017 - 17
Systems, Man & Cybernetics - October 2017 - 18
Systems, Man & Cybernetics - October 2017 - 19
Systems, Man & Cybernetics - October 2017 - 20
Systems, Man & Cybernetics - October 2017 - 21
Systems, Man & Cybernetics - October 2017 - 22
Systems, Man & Cybernetics - October 2017 - 23
Systems, Man & Cybernetics - October 2017 - 24
Systems, Man & Cybernetics - October 2017 - 25
Systems, Man & Cybernetics - October 2017 - 26
Systems, Man & Cybernetics - October 2017 - 27
Systems, Man & Cybernetics - October 2017 - 28
Systems, Man & Cybernetics - October 2017 - 29
Systems, Man & Cybernetics - October 2017 - 30
Systems, Man & Cybernetics - October 2017 - 31
Systems, Man & Cybernetics - October 2017 - 32
Systems, Man & Cybernetics - October 2017 - 33
Systems, Man & Cybernetics - October 2017 - 34
Systems, Man & Cybernetics - October 2017 - 35
Systems, Man & Cybernetics - October 2017 - 36
Systems, Man & Cybernetics - October 2017 - 37
Systems, Man & Cybernetics - October 2017 - 38
Systems, Man & Cybernetics - October 2017 - 39
Systems, Man & Cybernetics - October 2017 - 40
Systems, Man & Cybernetics - October 2017 - 41
Systems, Man & Cybernetics - October 2017 - 42
Systems, Man & Cybernetics - October 2017 - 43
Systems, Man & Cybernetics - October 2017 - 44
Systems, Man & Cybernetics - October 2017 - Cover3
Systems, Man & Cybernetics - October 2017 - Cover4
https://www.nxtbook.com/nxtbooks/ieee/smc_202310
https://www.nxtbook.com/nxtbooks/ieee/smc_202307
https://www.nxtbook.com/nxtbooks/ieee/smc_202304
https://www.nxtbook.com/nxtbooks/ieee/smc_202301
https://www.nxtbook.com/nxtbooks/ieee/smc_202210
https://www.nxtbook.com/nxtbooks/ieee/smc_202207
https://www.nxtbook.com/nxtbooks/ieee/smc_202204
https://www.nxtbook.com/nxtbooks/ieee/smc_202201
https://www.nxtbook.com/nxtbooks/ieee/smc_202110
https://www.nxtbook.com/nxtbooks/ieee/smc_202107
https://www.nxtbook.com/nxtbooks/ieee/smc_202104
https://www.nxtbook.com/nxtbooks/ieee/smc_202101
https://www.nxtbook.com/nxtbooks/ieee/smc_202010
https://www.nxtbook.com/nxtbooks/ieee/smc_202007
https://www.nxtbook.com/nxtbooks/ieee/smc_202004
https://www.nxtbook.com/nxtbooks/ieee/smc_202001
https://www.nxtbook.com/nxtbooks/ieee/smc_201910
https://www.nxtbook.com/nxtbooks/ieee/smc_201907
https://www.nxtbook.com/nxtbooks/ieee/smc_201904
https://www.nxtbook.com/nxtbooks/ieee/smc_201901
https://www.nxtbook.com/nxtbooks/ieee/smc_201810
https://www.nxtbook.com/nxtbooks/ieee/smc_201807
https://www.nxtbook.com/nxtbooks/ieee/smc_201804
https://www.nxtbook.com/nxtbooks/ieee/smc_201801
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_1017
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0717
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0417
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0117
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_1016
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0716
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0416
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0116
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_1015
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0715
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0415
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0115
https://www.nxtbookmedia.com