60 likes | 184 Vues
This outline presents a comprehensive review of Colin's HostTracker porting proposal discussed on May 20th, 2013. It delves into the functionality of the code, intended deployment, and the critical coupling between HostTracker, Topology, and Forwarding components. Key points include the role of IStorageSource for inter-controller communication, identifying big open questions, and illustrating the topology's implications with various networking setups. Insights into Phase 1 achievements and a roadmap for Phase 2+ reinforce the need to address complexities such as virtualization and broadcast domain management.
E N D
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 • Big Open Questions • Lots of pictures – fewer slides
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
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)
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
Big Open Questions • Do we support both interfaces? • IDeviceManager and SAL’s HostTracker? • Gets back to event ordering