1. SDN-based Inter-Cloud Federation for OF@TEIN
Asia Pacific Advanced Network (APAN)
Cloud Working Group Meeting 2016
Networked Computing System Laboratory (NetCS Lab)
Electrical Engineering and Computer Science (EECS)
Gwangju Institute of Science and Technology (GIST)
Gwangju, South Korea
Hong Kong, August 3rd 2016
Aris C. Risdianto
PhD Student
2. Agenda
Introduction
Future Internet and Cloud Integration
Multi-site Cloud Deployment
Multi-domain SDN-based Inter-Connection
SDN-based Inter-Cloud Federation
Conclusion and Future Works
8. FIDC Testbeds
• FIDC : Future Internet and Distributed Cloud Testbeds
• The goal is to widely shared the testbeds environment
• The effort is include Federation Policy, Testbeds Control / Data
Plane Federation
• It need to solve the technical challenges as well as human side
challenges
Challenges in Worldwide Federation of
ernet and Distributed Cloud Testbeds
M. Berman, M. Brinn
GENI Project Office
Raytheon BBN Technologies
Cambridge, MA, USA
d distributed cloud (FIDC)
important research and
While FIDC testbeds may be
hare the primary capabilities
configurations of computing,
) and deep programmability
all resources from low level
ents). FIDC testbeds often
ty through software defined
ch researchers employ both to
experiment virtual networks,
ic throughout the virtual
developers and researchers
create federated testbed and
ation holds the promise of
nd technical diversity, while
uired to create and maintain
an endeavor. In the case of
ements of trust and resource
cally via trusted identities,
seen strong progress and
g many of the key application
that enable the technical
ds, at both the control plane
and the implementation of the
well-understood and open
ryptography, attribute based
c circuit networking (DCN).
e resulted in a number of
c collaborations. There are a
Some of these are technical,
federated testbeds, federation policy.
I. INTRODUCTION – WHY FIDC TESTBEDS? WHY FEDERATE?
A. Motivation
Future Internet and Distributed Cloud (FIDC) testbeds are
rapidly gaining acceptance within the computer science
research community. These testbeds create opportunities for
experimental research and education that are difficult or
impossible to conduct in individual laboratories, commercial
clouds, or the public Internet. FIDC testbeds, which began with
the Global Environment for Networking Innovation (GENI)
project in the US [1] and the Future Internet Research &
Experimentation (FIRE) project in the EU [2], are gaining
acceptance. There is now a growing number of national and
regional scale FIDC testbeds in use or development worldwide,
as shown in Figure 1.
Figure 1: Worldwide FIDC testbed activity
These testbeds were originally conceived in response to
researchers’ concerns over Internet ossification, a term that
refers to the difficulty of performing innovative research within
the public Internet [3]. For example, novel protocols that do not
9. BonFIRE Testbeds
• BonFIRE: A Multi-cloud Test Facility for Internet of Services
Experimentation
• Offer test infrastructure for distributed applications and services
• Adopt a cloud-based model which familiar for Internet Services
experimenter
• Ability to control network parameters for distributed applications
10. SDN-Cloud Playground in OF@TEIN
o Multi-domain networks Infrastructure and SDN islands
o Multi-site Cloud Deployment Model
o Multi-tenant with separated logical networking inter-
connections
o Workload/applications distribution across the Clouds
12. OpenStack Multi-region for Multi-site Cloud Deployment
Region : A Region : B
Region : C Region : D
Controller/
Compute/Network
Controller/
Compute/Network
Controller/
Compute/Network
Controller/
Compute/Network
13. OpenStack Multi-region for Multi-site Cloud Deployment
o Independent Network Environment such as topology, IP address
range, and different administrative domain
o Central management for authentication/authorization and
accessing the cloud resources
o Most all OpenStack Projects (Nova, Neutron, … ) installed and
ran in each site
o The inter-connections are manually steered, because no tunnel
bridge will be configured
16. ONOS SDN-IP : SDN and IP Seamless Integration
https://wiki.onosproject.org/display/ONOS/SDN-IP+Architecture
17. ONOS SDN-IP : SDN and IP Seamless Integration
https://wiki.onosproject.org/display/ONOS/SDN-IP+Architecture
o BGP protocol is mature to federate inter-domain network (the
example is our current internet)
o BGP Speaker / Route Server used to help communication
between SDN Controller and BGP Router
o BGP as control-plane and OpenFlow SDN as data-plane
o The routing are learned via BGP router, but the forwarding are
decided by SDN Controller
18. Routing-Exchange for Multi-domain SDN
BGP
speaker 2
Route
ReflectorSDN-IP 1
BGP
speaker 1
ONOS-1
SDN Network 1
(Private AS X)
External Network
(Multiple Public AS)
SDN-IP 2
ONOS-2
SDN Network 2
(Private AS Y)
Control-Plane
Data-Plane
BGP Routes
OpenFlow entries
Federated SDN Control Plane
(Private AS Z)
Route
Reflector
BGP Router 1 BGP Router 2
External
Router/Gateway 1
External
Router/Gateway 2
• “Modified” version of ONOS SDN-IP Configuration
• Additional configuration BGP RR and policy-based routing
20. SDN-based Inter-Cloud Federation
o Multi-site distributed SDN-Cloud Testbeds
o Inter-Cloud Federation controlled by SDN
o Inter-Connect between Multi-domain SDN
o SDN Datapath control by BGP Protocol
21. SDN-based Inter-Cloud Federation
TEIN
REN REN
SDN Island
SDN Island
Cloud
Testbed
Cloud
Testbed
SmartX SmartX
Datapath
Inter-Cloud Federation Control-Plane
Inter-Cloud Federation Data-Plane
24. Conclusion and Future Works
SDN can be used for Inter-Cloud Federation in OF@TEIN SDN-
Cloud Playground
BGP is one of option for multi-domain SDN inter-connections
Future Works
o Verify the inter-cloud federation with specific workloads/applications
o Extend the Routing-Exchange approach into SDX approach