1 / 6

Technical Work Stream: HostTracker

Technical Work Stream: HostTracker. May 20th, 2013. Outline. Quickly Review Colin’s HostTracker porting proposal Stepping back – what does this code do? Intended deployment Coupling between HostTracker , Topology, and Forwarding IStorageSource is for inter-controller communication

kuri
Download Presentation

Technical Work Stream: HostTracker

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. Technical Work Stream: HostTracker May 20th, 2013

  2. Outline • Quickly Review Colin’s HostTracker porting proposal • Stepping back – what does this code do? • Intended deployment • Coupling between HostTracker, Topology, and Forwarding • IStorageSource is for inter-controller communication • Big Open Questions • Lots of pictures – fewer slides

  3. Review of Colin’s HostTracker • Great Step for Phase 1 • Create Stubs for Dependencies • TopologyManager • IStorageSource, HA Role Changes • Let’s understand what Phase1 gets us • HostTracker confused by tunnels, Non-OF topologies, virtualization, switch-level HA • Plan Phase 2+ to bring these back in

  4. Intended Deployment Router Disk Router Disk Disk Non-OF Aggregation Network Non-OF ToR Non-OF ToR Non-OF ToR Bcast Pkt Bcast Pkt VSwitch VSwitch VSwitch VSwitch VSwitch VSwitch VSwitch VSwitch VSwitch L2-over-L3 Tunnels between all vswitches (not all shown)

  5. Topology Implications • Multiple paths between all points • Tunnel vs. non-tunnel • Mixed OpenFlow and non-OpenFlow • Multiple broadcast “brains” play together • Requirement: All devices are not VMs • Managing broadcast domains is a pain • Correspondingly, HostTracking is a pain

  6. Big Open Questions • Do we support both interfaces? • IDeviceManager and SAL’s HostTracker? • Gets back to event ordering

More Related