Transcript Fabio Farina - TNC2013

Complex federated slices provisioning through SFA
The FEDERICA and NOVI joint experience
Fabio Farina (GARR), Simon Vocella (GARR), Álvaro Monje (UPC),
Celia Velayos (i2Cat), Chrysa Papagianni (NTUA),
Vassilis Maglaris (NTUA) and Mauro Campanella (GARR)
TERENA Conference, Maastricht, 6th June 2013
Outline
 Testbeds, virtual infrastructures and provisioning
 NOVI and the FEDERICA facility
 The provisioning flow in NOVI
 RSpec extensions and development in FEDERICA
 Learned lessons and conclusions
2
Fabio Farina
TNC 2013, Maastricht, 05.06.2013
Virtual testbeds for networking research

Testbeds are a common tool to experiment and assess new ideas


Dedicated testbeds: optical transport, wireless
Flexibly reconfigurable testbeds
 Can benefit of virtualization and cloud concepts
 Less expensive and simpler to manage, almost full control to the users

Minimal terminology




Environments




Substrate: the physical resources in the facility that host virtual resources
Slice: the virtual infrastructure where the user experiments, is made of virtual machines,
virtual topologies and links
Functionalities: direct control of Layer2/3, virtual routers and routers, host VM, last mile
connectivity, etc.
Future Internet Research and Experimentation Initative (FIRE)
Global Environment for Network Innovations (GENI)
AKARI Architecture Design Project (AKARI Project)
One common problem: automate how to map the slices on the substrate
3
Fabio Farina
TNC 2013, Maastricht, 05.06.2013
Automatic slice provisioning

Automatic provisioning of resources
 A quite common feature in modern infrastructures and clouds
 Provisioning homogeneous resources in a single environment is easy (like CPU
slots in a cluster, VPN over a network, … )

Provisioning of complete virtual infrastructures is a complex task for a
facility, Virtual Network Embedding (VNE)

It’s even more complex in federated testbeds
 Different protocols, monitoring, policies and AAI
 Functional (node type, OS), non-functional
(CPU, RAM, bandwidth), virtual topology aspects
 Boundedness of the request and platform dependencies
4
Fabio Farina
TNC 2013, Maastricht, 05.06.2013
NOVI
www.fp7-novi.eu
NOVI = Networking innovations Over Virtualized Infrastructures
STREP project, final review April 17th
 NOVI objectives
 Target innovative research in a bottom-up approach, addressing a
critical area in FI services
 How FI users securely share a multi-domain networking substrate
 Build set of algorithms, methods and services for management of
federated virtual infrastructures
 Provide experimenters the ability to request, use and update
virtualized resources in a federated environment, tailored to their
needs
5
Fabio Farina
TNC 2013, Maastricht, 05.06.2013
NOVI Technical Approach
 Modular data, control and management plane architecture
 An ontology-based Information Model capturing the abstractions of
virtualized resources and services across different platforms
 A framework providing interoperability of monitoring tools across
federated heterogeneous platforms
 A semantic distributed resource discovery and mapping framework
tackling the inter-domain virtual network embedding problem
 A policy-based management framework able to enforce intra and
inter-domain management policies
 Data-plane stitching tool for transparent data-plane connectivity
across dissimilar platforms involved in multi-domain user-slices
6
Fabio Farina
TNC 2013, Maastricht, 05.06.2013
FEDERICA
http://www.fp7-federica.eu
FEDERICA = Federated E-infrastructure Dedicated to European
Researchers Innovating in Computing network Architectures
Phase1: FP7 Project (2007-2011)  Phase2: under GN3 SA1.T3 (2012-2013)
 An e-Infrastructure based on virtualization in both computers and network
elements as a fundamental tool/playground for researchers on current and
Future Internet, its uses and technologies.
 Researchers has complete control
of their set of resources (a “slice”)
with minimal of constraints to enables
disruptive experiments at all
communication layers over
a realistic substrate
Router/Switch
Host for Virtual nodes
Ethernet 1 Gbps
 Focus on reproducibility
of the experiments
7
Fabio Farina
TNC 2013, Maastricht, 05.06.2013
The FEDERICA facility
 Every FEDERICA PoP is equipped with hypervisors and network
devices capable of virtualization
 VMware 5.0 for the hosts, services and pure-software routers/switches
 Juniper MX480 for logical routers
 Circuits between the PoPs
 1Gbps (IP/MPLS)
 Minimal resources in a slice
 Management VLAN
 User Access Gateway VM
 #data VLAN according to
the experiment needs
8
Fabio Farina
TNC 2013, Maastricht, 05.06.2013
Federated slice provisioning in NOVI
1. User models a slice using the web GUI
2. NOVI-API accepts the authenticated user request
3. Intelligent Resource Mapper (IRM) invokes the local Resources Information
Service (RIS)
4. The local IRM queries RIS/monitoring to partition the request among the
federated platforms
1. Splitting phase: find the portion of request suited for the different testbeds
considering resources functional requirements, then summon their IRM/RIS
2. If platform-bound request, skip
9
Fabio Farina
TNC 2013, Maastricht, 05.06.2013
Federated slice provisioning in NOVI
5. Mapping of the resources on the distributed IRM by local resource discovery
(RIS) according to non-functional requirements (Monitoring) and policies
1. Unbound/semi-bound requests: splitting and distributed mapping, interaction with the
RIS/Monitoring Service/Policy Service
2. Bound requests: references to the physical resources
6. Partial bound requests are aggregated to the IRM, inter-domain connections
are set up by the NSwitch
7. Local and remote RISs drive Request Handlers for actual resources reservation
8. NSwitches coordinate to connect the resources as a unique slice
10
Fabio Farina
TNC 2013, Maastricht, 05.06.2013
Federated slice provisioning in NOVI
 NOVI prototype
 Developed a flexible and expandable architecture for mapping slice
request on federated testbeds
 Rich semantic model to represent common aspects and peculiarities of
each facility
 Developed an algorithm for request splitting among different platforms
 Testbed-specific request handlers, intra-domain mapping algorithms
and monitoring tools
 Slice-based Federation Architecture (SFA) as inter-facility protocol
 FEDERICA and PlanetLab testbeds
 FEDERICA needed for a model representing the testbed and a better API
for virtual resources
11
Fabio Farina
TNC 2013, Maastricht, 05.06.2013
SFA and RSpec
 FEDERICA adopted Generic Slice-based Facility Architecture
 SFA is designed to provide a minimal set of functionalities and API that
enable interoperable federation
 FEDERICA adopted a subset of the components, not the complete
framework
 RSpec to model resources and requests
 Extensible XML data model to
represent the unique features
of the testbed
 FEDERICA introduces various extensions
on the syntax and review of the
semantics
12
Fabio Farina
TNC 2013, Maastricht, 05.06.2013
FEDERICA extensions: RSpec
 Providing three views
 Advertisement – The substrate with available physical capacities
 Vnodes hypervisors, Juniper routers, links capacity and features
supported by the interfaces
 Request – A syntax to model the user’s requests
 VMs characteristic and configurations, logical routers, virtual topology
 Manifest – Instantiated virtual resources
 returned to the user to access the virtual infrastructure
13
Fabio Farina
TNC 2013, Maastricht, 05.06.2013
FEDERICA extensions: RSpec
Advertisement
<node client_id="novi-router4" exclusive="false" component_manager_id="…"
component_id="…+psnc.poz.router1">
Extensions
<hardware_type name="genericNetworkDevice" />
<sliver_type name="router">
<cc:router_configuration method="inline" configuration="
edit routing-options autonomous-system 55;
edit protocols bgp group G1 type external peer-as 44 neighborRequest
192.168.40.1;
edit protocols bgp group G2 type external peer-as 44 neighbor 192.168.40.2;"/>
Extensions
</sliver_type>
<services>
<login authentication="ssh-pap" cc:user= "novi001" cc:key= "my-super-secres-passwd123! " />
</services>
<interface client_id="vImanagement" component_id=«…+psnc.poz.router1.ge-0/1/2" cc:exclusive="false">
<ip address="192.168.40.3" netmask="255.255.255.0" type="ipv4"/>
</interface>
</node>
<link client_id="vlink1">
<interface_ref client_id=“vm1:if0"/> <interface_ref client_id="router1:if0"/>
<fed:vlan id=”auxVLAN2” vlantag=1401 />
</link>
14
Fabio Farina
TNC 2013, Maastricht, 05.06.2013
FEDERICA extensions: the Adapter
 The Adapter converts SFA requests to FEDERICA Web Services
 Based on the Generic SFA architecture
 Aggregate Manager maps the requests
to the FEDERICA model and orchestrates
slice creation
 Router & Server Wrapper Components
bridge between the AM and the FED-WS
 FED-WSs create & configure VMware
VMs, JunOS Logical Routers and
Virtual Switches
15
Fabio Farina
TNC 2013, Maastricht, 05.06.2013
Conclusions
 NOVI shows that full interoperability on federated facilities is a reality
 Pathfinder in best practices for community and federated clouds
 New algorithms, software prototypes and state-of-art modeling
 Technical collaboration and co-evolution between FIRE Projects
 Generic SFA Wrapper enabled automatic provisioning for complex slices
over testbeds PlanetLab and FEDERICA
 Deep extensions to the RSpec data model
 Advantages and fallbacks on other FIRE projects: BonFIRE OCCI
 Sharing of knowledge and efforts on specific tasks should be
supported in liaisons actions more often and more deeply
16
Fabio Farina
TNC 2013, Maastricht, 05.06.2013
The future
 Both NOVI and FEDERICA ended in the last months
 Facilities and architectures are valuable, will do our best to keep them up
& running
 But knowledge and expertize are much more important!
 Know-how will continue by contributing to other projects
 GN3Plus SA2 “TaaS”, federation of the substrate resources and know-how
 GN3Plus SA7 “Support to clouds”, expertise on the standards
 Fed4Fire on modeling
17
Fabio Farina
TNC 2013, Maastricht, 05.06.2013
Thanks
Questions?