The Infrastructure as a Service (IaaS Framework), http://www.iaasframework.com is,
A generalized approach to the outcome of years of research under the UCLP Research programs funded by CANARIE
A set of software resources used to administer a domain from user workspaces, to resource exchanges, permissions and security
A list of operation providers that can be used to quickly provide functionalities like permissions/security, reservation, topology and allow them to seamlessly integrate in the Resource Management Centre (RMC)
Libraries and tools to manage persistence or communication with the hardware devices
The enabling technology for upcoming products and R&D initiatives
IaaS Framework, Products and Research Projects Architecture Device Controller Services Device Virtualization Services Network Virtualization Services IP Network Resources WDM Resources Application Services MANTICORE (IP Research Project) Framework (Open Source) Ether™ (Product) (Ethernet Networks) Argia™ (Product) (Optical Networks) Resource Management Centre and User Web Portal. WS GRIM (Virtual Instruments Research) GRIM Resources Instrument Resources Support Services Unless specified otherwise the development is being performed in partnership by i2CAT, CRC and Inocybe Technologies. RCP WEB (Development) . . . Optical Switch Resources Router Resources Scenarios Resources Ethernet Switch Resources TDM Timeslot Resources Ethernet Port Resources Connections Resources VLAN Resources Physical Network Resources Resource List Resources WS WS WS WS Appliance Resource User Workspace Resources
Physical Network Administrator: Owners of physical infrastructure. He can virtualize (create a software object that represents all or a part of a physical infrastructure) the physical infrastructure and give permissions to users (=export virtual resources) so they can have limited control over the resources.
APN (or Virtual Network) Administrator: He gathers resources from one or more physical network administrators or other APN Administrators (by asking them or through resource brokers). He also assigns the resources he’s harvested to different services (for instance, he could assign a set of ethernet port resources to the VLAN Service, or a set of logical routers to the IP Network Service).
End User: Just uses the services provided by the software. For instance, if there is a reservation service, the user can ask for network reservations; if there is an IP Network Service, the user can configure its IP Network; if there is a VLAN Service, the user can ask for an end to end VLAN, and so on (this type of user JUST SEES THE SERVICE INTERFACE, he cannot collect or trade virtual resources, it is the traditional end user).
Resource Trading User A Provider 1 User B Provider 2 User C Resource List Resource List Resource List Resource List
They offer a service to the end user on top of the virtual resources. The following could be examples of network virtualization services:
Reservation Service Creates point to point connections (inmediate or in advance) over SONET/SDH resources (withVCAT, LCAS, GFP) IP Network Service Creates an IP network Service where the user can configure internal routing protocols, external peering, … … Other.. (put the service that you want here) GMPLS Service Has the functionalities of a GMPLS node (Connection Controller, Routing Controller, …) Speaks GMPLS Protocols (OSPF, RSVP), and can be seen as a GMPLS domain by external entities
MANTICORE Software Architecture Router-WS Virtual Resource Services Ethernet Resource WS TDM Resource WS . . . IP Network WS GUI client(s) RPSL may be used to let the GUI specify high level routing policies (internal as well as external) to the IP Network WS Transforms the routing configuration abstract description in high level operations that will be invoked in the Router WS over one or more virtual resources Represent the physical (ports) or logical interfaces (VLANs, TDM Channels) that users can access. Transforms the high level operations over one or more virtual resources into specific commands that each particular routing device can understand Netconf Juniper device Protocol X Other vendor device Protocol Y Software router User Workspace WS Manage user accounts, get user credentials, authenticate
The user can configure the IP address, the NETMASK, the status (up or down) and other general parameters of the interface.
Add/Delete static route
The user applies a static entry to the routing table. This static entry can be for one or more source interfaces.
Configure an IGP on a interface or the whole network
The user of an IP Network can apply a dynamic routing protocol (initially OSPF and RIP) to every interface inside it, and modify the IGP parameters.
Configure an EGP on an interface or the whole network
The user can decide to what other IP Networks he wants to peer with, and choose what routes are advertised to external networks. Simple BGP configurations will be generated (iBGP will also be configured between BGP nodes of the same AS)
Language used to describe the routing policies of an AS. E.g.
davew@byron:~$ whois as1213 aut-num: AS1213 as-name: HEANET import: from AS3549 # Global Crossing action pref=100; accept ANY import: from AS2850 # UCD action pref=50; accept AS2850 export: to AS3549 # Global Crossing announce AS-HEANET export: to AS2850 # UCD [client] announce ANY ...but just send you ours Transit provider We'll take entire internet's routes Client - we only want to see your own network ...we'll send you all we've got
RPSL can be used as a means of describing the external routing policies as well as the IGP configurations (with minor extensions).
These RPSL descriptions can be taken as an input by the IP Network WS and then generate the high level operations to invoke at the Router WS (remember the architecture picture).
Implementation status: RPSL RFCs (2622, RPSL and 4012, RPSLng) have been studied, and some preliminary RPSL descriptions for the MANTICORE use cases have been generated. Not implemented yet due to time constraints.
Router-WS Virtual Resource Services Ethernet Resource WS TDM Resource WS . . . IP Network WS GUI client(s) RPSL may be used to let the GUI specify high level routing policies (internal as well as external) to the IP Network WS Transforms the routing configuration abstract description in high level operations that will be invoked in the Router WS over one or more virtual resources Represent the physical (ports) or logical interfaces (VLANs, TDM Channels) that users can access. Transforms the high level operations over one or more virtual resources into specific commands that each particular routing device can understand Netconf Juniper device Protocol X Other vendor device Protocol Y Software router User Workspace WS Manage user accounts, get user credentials, authenticate
FEDERICA e-Infrastructure What : 7 th FP project in the area “ Capacities - Research Infrastructures” 3.7 MEuro EC contribution, 5.2 ME budget, 20 partners , 461 Person Months When : 1 st January 2008 - 30 June 2010 ( 30 months ) Virtualization infrastructure, a “ Network Factory ” to provide “slices” to researchers in Future Internet, where a slice is a mix of network circuits and computing elements . Built using resources (Gb Ethernet circuits) from G ÉANT2 and NRENs as contributions to the project. Open to interconnect other Infrastructures Connected to Internet (through NRENs)
Act as a forum and support for researchers/projects on “Future Internet”. Support of experimental activities to validate theoretical concepts, scenarios, architectures, control and management solutions. Users have full control of their slice
Provide on European scale network and system agnostic e-infrastructure to be deployed in phases. Provide its operation, maintenance and on-demand configuration
Validate and gather experimental information for the next generation of research networking also through basic tool validation
Dissemination and cooperation between NRENs and researchers’ community
Contribution to standards in form of requirements and experience
Internal extended research , e.g. advanced optical technology