EC (EU), MIC & NICT (JP) collaborative project Project running from April 2013 till March 2016 302 PMs of effort PL BE NL DE IT ES JP EU coordinator JP.

  • Published on

  • View

  • Download



FELIX components and APIs

Bartosz Belter, Poznan Supercomputing and Networking CenterFIRE-GENI MeetingWashington D.C., September 2015FELIX in a NutshellEC (EU), MIC & NICT (JP) collaborative projectProject running from April 2013 till March 2016302 PMs of effort


EU coordinatorJP coordinatorTo create a large-scale testbed federated across two continents

To define a common software architecture for testbedsFacts


FELIX ConceptsThe slice concept is adopted in FELIX Experimental facilities to be provided dynamically on top of the FELIX physical infrastructure (federated testbeds)All the experimental facilities are controlled programmatically Facilities are composed of computing and network resources (CR and NR) belonging to distributed SDN islands in FELIX infrastructureOrchestrate resources in a multi-domain environment In a slice, facilities are interconnected via TN service-controlled domains (transit network)User has access and control of a provided slice

A user-defined subset of virtual networking and computing resources, created from the physical resources available in federated testbeds. A slice has the basic property of being isolated from other slices defined over thesame physical resources

3FELIX Architecture Overview

Request configurationof slice(s)Control sliceManage sliceUsersThe FELIX Space provides users with slices for their own use. Users request slices to an RO.RO: Resource OrchestratorRM: Resource ManagerPHY RES: physical resources (testbed)

The User Space consists of any tools and applications that a user wants to deploy to control a slice or execute particular operationsResource controllers in User Space may communicate with FELIX Space components

Refer to overall project objectives of the project (from PPR2) explain the WP positioning towards them

4FELIX Architecture

FELIX technical documents/deliverables and architecture whitepaper available at www.ict-felix.euTransport Network Resource Manager (TNRM)

TNRMFeaturesAllocation (reservation), provisioning (generation), (re)creation, deletion of inter-domain links between STPs of remote networksProxy between RO and NSI agent to set up connectivity between different domainsAccess and interfaces:Standard northbound API (GENIv3) for federation with multiple clientsMakes FELIX transit network technology agnostic (e.g. NSI, GRE, etc.)GENI/NSI translations: state mapping

GENI/NSI translationsGENINSI AllocateReserve + CommitDelete/shutdownTerminateProvision-PerformOperationalAction startprovision (link up)PerformOperationalAction stoprelease (link down)Inter-domain Networking > TNRM > InternalsData model: GENI RSpec adopted by TNRM. RSpec and NSI messages are translated to each other.Base tools: Existing eiSoil framework (Python) used as base server. Jython (Java-interoperable Python) used to communicate calls from NSI (Java) with those from eiSoil (Python).TNRMROeiSoil serversrc/main.pyeiSoilvendor/tnrm_delegate.pySimpleXMLRPCServervendor/nsi2interface.pyNSI CS2.0 Providers / AggregatorNSIv2 Requesting Agent InterfaceNSI2Interface.javaNSI messages(JAVA method call with NSI parameters)(Python RPCWith GENI RSpec)TNRM topology configvendor/config.pyproxy.pyConvert FELIX to NSIv2reservation.pyGENI v3RPCMRO10CLIROGENIv3 APITNRMGENIv3 APINSIThe TNRM DemoAIST NSI AggregatorAIST NSI uPAJGN-X NSI uPAiCAIR NSI uPANL NSI uPAPSNC NSI uPANetherLight NSIAggregatorAISTIslandPSNCIslandFELIX domainNSI domainTN Request RSpec


View more >