openflow multiple controllers03

1、TOWARDS AN ELASTICDISTRIBUTED SDN CONTROLLERAdvait Dixit, Fang Hao, Sarit Mukherjee, T.V. Lakshman, Ramana KompellaSDN Control PlaneSingle point of failure Performance bottleneckDistributed Control PlanePhysical Network InfrastructureSpatial PartitioningOverloadGrowing the Control PlaneShrinking the

2、 Control PlaneGoals Build a distributed control plane which Load balances Grows Shrinks This requires Load estimation at controllers Switch migration protocolNave Switch MigrationMSALSATVEER MSALSATVEERProblem With Nave Switch MigrationMSALSATVEERMSALSATVEERPacket-Out from Slave is droppedMigration

3、Protocol Requirements Safety: Exactly 1 controller processes every message from the switch Liveness: For each switch, at least 1 controller is active at all times Openflow compliant4-Phase Switch Migration ProtocolMSALSATVEER MESAQLSAUTVAEELRPPPhhhaaassee2341:IFnClsuhesarhnt gainen-d frfroomfmligEvS

4、hqeltaumdvauelemtstoosmaMEygaqefsulotaewlrA Mininet TestbedEmulation HostProblem: Cannot generate sufficient traffic for a large distributed control planeOpenvSwitchOpenvSwitchOpenvSwitchveth PairOpenvSwitchOpenvSwitchOpenvSwitchOpenvSwitchA Multi-Host Mininet TestbedGRE TunnelEmulation HostEmulatio

5、n HostEmulation HostOpenvSwitchOpenvSwitchOpenvSwitchOpenvSwitchOpenvSwitchEvaluationEvaluationNext Step: ElastiConLoadMeasurementsDistributed SDN Control PlaneNode 1Node 2Physical Network InfrastructureDistributed Data Store(e.g., Hazelcast)Core Controller ModuleCore Controller ModuleApplication 2A

6、pplication 1Application 2Application 1Actions: Migrate switch Remove controller Add controllerLoad Adaptation Decisions LoadScale UpBalanceScale DownTHANK YOUDistributed Control Plane in a Datacenter Median flow arrival rate requires 1-5 controllers, peak requires 150* Distributed control plane shou

7、ld grow and shrink Flow arrival rates vary across switches and time Need a switch migration (handover) protocol* Calculations based on Benson et al, IMC 2010Distributed SDN Control PlaneHazelcast Client StubController Node 1Controller Node 2Distributed Data Store (e.g., Hazelcast)Physical Network In

8、frastructureCore Controller ModuleCore Controller ModuleApplication 2Application 1Application 2Application 1Next StepsBuild a control loop and algorithms for dynamically: Changing switch-controller mapping based Growing and shrinking distributed controllerThanks! Questions?EvaluationNeed title for t

9、his slide For a data center with 100K hosts: Peak flow arrival rate = 300M* flows/sec Median flow arrival rate = 1.5-10M* flows/sec Impossible to predict flow arrival rates at a switch Implications: Distributed controller needs to grow and shrink Need a switch migration protocol* From Benson et al,

10、IMC 2010New Problems in Distributed SDN Controllers How to manage distributed state? Where to place controllers? How to write distributed controller applications? How many controllers? Which switch connects to which controller?New Problems in Distributed SDN Controllers How to manage distributed state? Where to place controllers? How to write distributed controller applications? How many controllers? Which switch connects to which controller?Distributed SDN ControllerApplication 1Application 2Application 3Application 4Distributed Global Network StatePhysical Netwo