Lefteris Mamatas University of Macedonia, Greece * joined work with Stuart Clayman and Alex Galis from UCL, UK

Size: px

Start display at page:

Download "Lefteris Mamatas University of Macedonia, Greece * joined work with Stuart Clayman and Alex Galis from UCL, UK"

Sybil Barnett
5 years ago
Views:

1 Lefteris Mamatas University of Macedonia, Greece * joined work with Stuart Clayman and Alex Galis from UCL, UK

2 } Research challenges in information handling for SDN/NFV environments } The Virtual Infrastructure Information Service (VIS } Representative test-bed results } Our next steps and conclusions 2

technologies } Different Management and Control Entities (MCEs should operate: with a clear,

3 } The Internet is gradually supporting flexibility and programmability: Network Slices / Network Virtualization Network Functions Virtualization Software-Defined Networks Cloud technologies } Different Management and Control Entities (MCEs should operate: with a clear, often global view of the network environment, and exchange management information in alternative ways 3

} This unique flexibility at the network operation and control level: enables management solutions bringing the highlevel service requirements closer to the network results in a

4 } This unique flexibility at the network operation and control level: enables management solutions bringing the highlevel service requirements closer to the network results in a proliferation of new services where traditional services can operate in more predictable environments } We should leverage native service-awareness in the network infrastructure 4

5 } New SDN applications beyond centralized traffic engineering, independent from hardware characteristics virtualization is the enabling technology appropriate abstractions and standardized interfaces } Flexible allocation and utilization of network resources realizing a large number of services efficient, stable and predictable services operation aligned to the requirements of users, service and infrastructure providers 5

6 } New abstractions for sophisticated management features on top of the flexible and programmable network components bringing the gap between local and global viewpoints } A global picture of the network infrastructure should be maintained, using logically-centralized intelligence programmable techniques abstracted design, and being adaptable to the requirements and resource constraints of the involved MCEs 6

} The tailor-made information handling facilities have disadvantages: No adaptability to existing network conditions and MCE QoS requirements No handling of systematic problems through prioritization

7 } The tailor-made information handling facilities have disadvantages: No adaptability to existing network conditions and MCE QoS requirements No handling of systematic problems through prioritization of the required MCEs communication No collective optimization of the different information manipulation processes The collected or processed state may not be available to other MCEs that can benefit from it 7

8 } The introduction of a state information manipulation facility that: abstracts away information handling in a logicallycentralized manner builds the global-picture for the system operates at large Internet scale supports local and domain level views, adaptable to the diverse requirements of the MCEs tuning the involved performance trade-offs at global or local levels is designed considering the characteristics of the SDN/NFV paradigms 8

9 } The Virtual Infrastructure Information Service (VIS supports: information collection, aggregation and dissemination from information sources to sinks information storage, indexing and processing information flow establishment and optimization, supporting both global and local tuning of involved performance trade-offs alternative communication methods between information sources and sinks, i.e. push/pull, pub/sub, direct communication 9

} The Virtual Infrastructure Information Service (VIS supports: logically-centralized path optimization open interfaces for information exchange and information flow management architecture aligned

10 } The Virtual Infrastructure Information Service (VIS supports: logically-centralized path optimization open interfaces for information exchange and information flow management architecture aligned to physical and virtual space, accommodating extensions improving its behavior } We have implemented VIS and integrated it with our SDN/NFV platform: the Very Lightweight Software-Driven Network and Service Platform (VLSP 10

11 11 Informa(onManagement Interface/REST VirtualInfrastructureInforma(onService(VIS Informa(onProcessing& KnowledgeProduc(on Informa(on Aggrega(on Knowledge Produc(on Informa(onStorage&Indexing MCE Registra(on Informa(on Storage Informa(on Loca(on Informa(onFlowEstablishment& Op(miza(on Informa(on Flow Establishment Informa(on Quality Controller Informa(onCollec(on& Dissemina(on Informa(on Retrieval Informa(on Dissemina(on Informa(onExchange Interface/REST Informa(onExchange Interface/REST Informa(onManagement Interface/REST High/LevelManagementApplica(ons DeploymentEnvironment (SDNand/orvirtualizedinfrastructure VISnode VISnode Informa(on Flow Op(miza(on PhysicalMachine MCEs VirtualRouterMCE VirtualRouterMCE

12 12 Lightweight( Network( Hypervisor (LNH Virtual( Infrastructure Management (VIM Informa>on(Exchange( Interface Informa>on(Management Interface LNH(Control Interface LNH(Monitoring Interface Informa>on(Exchange( REST(Interface Informa>on(Management REST(Interface VIM Interface Ingress(Point Egress(Point MCE(Sink MCE(Source Streaming( Applica>on File(Transfer( Applica>on Monitoring( Probe Run>me( Engine Monitoring( Probe Configura>on(and(Monitoring Configurators(/ Configura>on( Actuators Scrip>ng( Engine Monitoring( Engine Host( Controller Informa>on(Processing(&( Knowledge(Produc>on Informa>on( Aggrega>on Knowledge( Produc>on Informa>on(Storage(&(Indexing MCE( Registra>on Informa>on( Storage Informa>on( Loca>on HighNLevel(Services(and(Management(Applica>ons Informa>on(Collec>on(&(Dissemina>on Informa>on( Retrieval Informa>on( Dissemina>on Informa>on( Flow( Controller VIM Interface Infrastructure(Controller Resources( Orchestrator Service( Orchestrator Infrastructure(Op>miser Flow( Controller Placement( Engine VIS Virtual(Infrastructure(Informa>on(Service((VIS Physical(Host(A Physical(Host(B Physical(Host(C Run>me( Engine Host( Controller Run>me( Engine Host( Controller Aggrega>on( Point VLSP

13 } We assume two MCEs: (1 A Virtual Network Management (VNM MCE that provides management & control facilities for virtual infrastructures, including support of traffic monitoring; and (2 An Entity Placement Optimization (EPO MCE that optimizes the data flow over a virtual network, through adapting the positioning of communicating nodes (e.g. data servers, in response to the dynamic network conditions. 13

14 HighKLevel!Management!Applicaons! HighKLevel! Performance!Goals! Global!Picture! Informaon! VNM!MCE! Collect!Data!/!! Informaon! Register!Informaon! Availability! Informaon!Flow!! Configuraon! Share!Informaon! Informaon! Retrieval!!!! Informaon! Disseminaon! Informaon!! Flow!Controller!! Informaon!Collecon!&! Disseminaon! Store!Informaon! Retrieve!Informaon! Register!Informaon! Requirements! Informaon!Flow!! Configuraon! Informaon!Retrieval! using!pull! EPO!MCE! Enforcing! Decision! Network! Informaon!Storage!&!Indexing! Network! 14

15 } Every experiment starts with the creation of a virtual network topology over a physical network of 11 servers, with 4 CPU cores and 8-32GB of physical memory each. } We have created MCEs, with diverse requirements in terms of information handling, including applications collecting information from the virtual routers and applications requesting information from the VIS. supporting various communication methods, i.e. Publish/Subscribe, Push/Pull, and Direct Communication } The MCEs can specify and update their own requirements at any point of the communication, e.g. changing their requested communication method, their local performance goal, or their minimum / maximum data rates etc. this triggers appropriate management information flow negotiations. 15

16 16

17 } Here, we demonstrate the flexibility aspects of the VIS. } For the same global behavior, in terms of memory consumption and CPU load, we can tune the relevant performance trade-offs to meet the needs of the MCEs } If we trigger a change in the global performance goal: this allows a global tuning of the performance of some selected or all established management information flows 17

18 } Examples: Switching from the Pull from Entities method to the Direct Communication method: improves average response time and information freshness, while at the same time it minimizes response time jitter Switching from the Pull from Storage method to the Direct Communication method: we trade average response time for information freshness therefore, we improve the quality of information if we tolerate more delays in order to retrieve the information. } Such performance updates can be maintained by an autonomic control loop at the VIS level 18

19 30 25 Average CPU Load Flows 1 Flows 2 Flows 3 Flows Memory State Flows 1 Flows 2 Flows 3 Flows CPU Load 15 Memory State Time Time 19

20 80 70 Average Response Time Flows 1 Flows 2 Flows 3 Flows Average Information Freshness Flows 1 Flows 2 Flows 3 Flows Response Time Information Freshness Time Time 20

21 80 70 Average Response Time Flows 1 Flows 2 Flows 3 Flows Average Information Freshness Flows 1 Flows 2 Flows 3 Flows Response Time Information Freshness Time Time 21

22 } In the previous example, a change is triggered in the global performance goal that impacts all existing flows. } Our VIS implementation supports changes to the local performance goals at the MCE level, as well as global goal changes that impact a subset of the established management information flows } We show that a particular MCE may request a renegotiation of its own management information flow(s. this may involve a different tuning of the local performance trade-offs (i.e. improving response time in this example, but with a minor or zero impact in the performance of other coexisting management information } Such behaviour can be associated with autonomic control loops at the MCE level. 22

80 70 Average Response Time (Selected Flows Flows 1+1 Flows 1+2 Flows 1+3 Flows 1+4 80 70 Average Response Time Flows 1+1 Flows 1+2

23 80 70 Average Response Time (Selected Flows Flows 1+1 Flows 1+2 Flows 1+3 Flows Average Response Time Flows 1+1 Flows 1+2 Flows 1+3 Flows Response Time Response Time Time Time 23

24 } We identified research challenges for the future evolution of SDN / NFV technologies towards improving service-awareness } We discussed the research problem of information manipulation in such environments } We have introduced the Virtual Infrastructure Information Service, an information orchestration infrastructure for SDN/NFV environments 24

25 } The VIS: resides between the applications & services and the network infrastructure, and is able to orchestrate the management information flows, while balancing the local with the global requirements } Our next steps include: Improving the management information flows negotiation heuristic, to support a wider range of parameters Investigating other local and global performance trade-offs that can be tuned, such as between energy efficiency and QoS Implementing complete autonomic control-loops tackling representative management problems 25

26 } Related References 1. L. Mamatas, S. Clayman and A. Galis, "A Service-Aware Virtualized Software Defined Infrastructure", IEEE Communications Magazine, Feature Topic on Network and Service Virtualization, Part II, Volume 53, Issue 4, Pages , April L. Mamatas, S. Clayman and A. Galis, "Experimenting with Management Information Orchestration for Virtual Software-Defined Networks", submitted. 3. L. Mamatas, S. Clayman and A. Galis, "A Flexible Information Service for Management of Virtualized Software-Defined Infrastructures", submitted. 4. S. Clayman, L. Mamatas and A. Galis, "Very Lightweight Software- Driven Network and Services Platform (VLSP Operations and Evaluation", submitted. } Open-source software The VIS Platform code: The VLSP code + documentation: 26

27 Ques%ons? 27

Information Exchange Management as a Service for Network Function Virtualization Environments

L. MAMATAS ET AL. 1 Information Exchange Management as a Service for Network Function Virtualization Environments Lefteris Mamatas, Member, IEEE, Stuart Clayman, Member, IEEE, and Alex Galis, Member, IEEE.