1 / 13

Simplified Network Service Interfaces

Simplified Network Service Interfaces. Sept 29 2014 Rex.pugh@hp.com. Outline. Motivations Use-cases API Definitions Design Considerations Q/As. Motivations. Port Existing SDN Apps to OpenDaylight Project Decrease Complexity for “Application” Writers

nolan-wallace
Télécharger la présentation

Simplified Network Service Interfaces

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Simplified Network Service Interfaces Sept 29 2014 Rex.pugh@hp.com

  2. Outline • Motivations • Use-cases • API Definitions • Design Considerations • Q/As

  3. Motivations • Port Existing SDN Apps to OpenDaylight Project • Decrease Complexity for “Application” Writers • Provide Data Model and Infrastructure Independence • Eliminate Code Duplication • Provide an abstraction of Network Services from the underlying Data Model • Applications are burdened with searching, sorting, and filtering model objects in the datastore • Increase Performance for certain frequent data access • .findNode is an O(n) operation • Build a flexible middleware service layer for evolving North-Bound API’s

  4. Network Service API’s Foundation for Evolving NBI’s • Network Services API’s are a library of Data Access methods that allow middleware apps to create action-based semantics • Middleware apps want to interact with the control plane with action-based semantics, not network data semantics • ‘block’, ‘allow’, ‘inspect’, ‘inject’, ‘redirect’, ‘copy’, ‘set quality {latency, bandwidth, loss}’ • Network Middleware Apps: HP Network Optimizer HP Network Protector

  5. Network Service API’sSAL Layering GBP . . . NBI’s Action Semantic API’s ??? Network Service API’s API’s Packet Flow Path Link Host Node Topo Providers Data Access Data Change Notifications MD-SAL Data Store Packet Flow Path Link Host Node Topo Packet Flow Path Link Host Node Topo Suppliers . . . SNMP NETCONF OpenFlow Protocols • Acknowledge that there are many levels at which “Applications” interact with controller functions. • Network Service API’s are at a lower stratum than Intent level or Policy level NBI’s

  6. App Code Example • Getting hosts by IP address On MD-SAL Today: DataBroker broker = session.<DataBroker>getSalService(DataBroker.class); ReadOnlyTransactiontx = broker.newReadOnlyTransaction(); ListenableFuture<Hosts> future = tx.read(LogicalDatastoreType.OPERATIONAL, instanceIdentifier); Hosts hosts = future.get(); List<Host> salHosts = hosts.get(); List<Host> matchingHosts = new ArrayList<Host>(); for(Host host : salHosts ) { //if IP address matches //matchingHosts.add(host); ... with a Simple API HostServicens; IpAddressaddr = IpAddress.valueOf("192.168.100.10"); List<Host> Hosts = ns.getHostsByIpAddress(addr);...

  7. Network Service API’s - Nodes

  8. Network Service API’s - Hosts

  9. Network Service API’s - Links

  10. Network Service API’s – Topology

  11. Network Service API’s - Path

  12. Design Overview & Options • Simple Start • Just write APIs with methods that use MD-SAL directly • Optimize for Performance • Use Hash Maps instead of Tree Data Store • Create Hash Maps to index into Tree Data Store • Store Instance ID’s as keys • Store Object references as keys

  13. Q&A’s • Thanks!

More Related