Page History

...

• introduce new 'Connectivity' service capability 'distributedrouting'. This capability shall indicate 'Connectivity' service providers ability to perform distributed routing.
• createVPCOffering API shall be enhanced to take 'distributedrouting' as capability for 'Connectivity' service. Provider specified for the 'Connectivity' service shall be validated with capabilities declared by the service provider, to ensure provider supports 'distributedrouting' capability.
• listVPCOfferings API shall return VpcOfferingResponse response that shall contain 'Connectivity' service's  'distributedrouting' capability details of the offering if it is configured
• createNetworkOffering API shall throw exception if distributedrouting' capability is specified for 'Connectivity' service. 

OVS

...

Network Element enhancements

• OVS element shall declare 'distributedrouting' as supported capability for 'Connectivity' service.
• OvsElement uses prepare() phase in NIC life cycle to implement tunnels and setup bridges on hypervisors. Following changes shall be needed in nic prepare phase:
  • current logic of preparing a NIC is described as below, if the VM's is first VM from the network being launched on a host.
    • get the list of hosts on which network spans currently
    • create tunnel from the current host on which VM being launched to all the host on which network spans
    • create tunnel from all the host on which network spans to the current host on which VM being launched
  • check shall be made if network is part of VPC, if its part of VPC, and VPC offering does not have 'distributedrouting' capability enabled current flow of actions outlined above shall be performed during the nic prepare phase
  • if network is part of VPC, and VPC offering has 'distributedrouting' capability enabled then following actions shall be performed.
    • if there is VPC VR running on the current host on which VM is being launched then proceed with steps outlined above (i.e setting up tunnels just with the bridge corresponding to network).
    • if VPC VR is running on different host than the current host on which VM is being launched, then following actions shall be performed:
      • for each network in the VPC create a bridged network
      • for each of the bridge created for the tier in the VPC, form full mesh of tunnels with the hosts on which network/tier spans
      • create a bridge that shall act as logical router and connect each bridge created in previous step with patch port to logical router
      • set up flow rules on each bridge to;
        • exclude mac learning and flooding on patch port
        • for traffic destined to other tiers send the traffic on the patch port
        • for the rest of the traffic from VIF's connected to VM, tunnel interface and patch port do normal (L2 switching) processing
      • set up flow rules on logical router bridge to:
        • reflect flows corresponding to current ingress ACL's and egress ACL's set on tier
        • set flows to route traffic on appropriate patch port based on the destination ip's subnet
• OvsElement release() (which handles NIC release) is currently used to destroy tunnels and bridges on hypervisors. Following changes shall be needed in nic release phase:
  • current logic of releasing a NIC is described as below, if the VM's is last VM from the network being deleted on the host.
    • get the list of hosts on which network spans currently
    • delete tunnel from all the hosts on which network spans to the current host on which VM being deleted
    • destroy the bridge
  • check shall be made if network is part of VPC, if its part of VPC, and VPC offering does not have 'distributedrouting' capability enabled current flow of actions outlined above for release phase shall be performed during the nic release
  • if network is part of VPC, and VPC offering has 'distributedrouting' capability enabled & VM is not the LAST vm from VPC then just return
  • if network is part of VPC, and VPC offering has 'distributedrouting' capability enabled & VM is LAST vm from the VPC on the host then following steps shall be performed
    • for each network/tier in the VPC:
      • get the list of hosts on which tier spans
      • delete tunnels from the all the hosts on which tier spans to the current host on which VM is being deleted
      • destroy the bridge for the tier
    • destroy the logical router
• OvsElement implement() that handles implement phase of network shall need following changes to deal with case where a new tier in a VPC is created:
  • check shall be made if network is part of VPC, if its part of VPC, and VPC offering have 'distributedrouting' capability enabled then
    • get the list of hosts on which VPC spans currently excluding host running VPC VR
    • for each host in the list
      • create a bridge for the tier
      • interconnect the bridge and logical router by creating a patch port on the logical router and the created bridge
      • add flow rule to forward packets on the created patch port on the logical router for IP packets destined to subnet corresponding to created tier 
• OvsElement destory() that handles destroy phase of network shall need following changes to deal with case where a tier in a VPC is deleted:
  • check shall be made if network is part of VPC, if its part of VPC, and VPC offering have 'distributedrouting' capability enabled then
    • get the list of hosts on which VPC spans currently excluding host running VPC VR
    • for each host in the list
      • destroy the bridge corresponding to the network
      • destroy the patch port on logical router
      • remove the forwarding entry flow and entries corresponding to ingress, egress ACL's
• VPC VR migration: OvsElement shall implement NetworkMigrationResponder to hook into VM migration. If the VM that is being migrated is VPC VR, and VPC offering have 'distributedrouting' capability enabled then following action shall be performed
  • On the host from which VPC VR is being migrated
    • create a logical router, connect it with the bridges corresponding to tiers with patch ports
    • populate flow rules on logical router to reflect ingress and egress ACL for each tier
    • populate flow rules on logical router to forward packet on destination patch port depending on the destination IP
    • on each bridge establish flow rules to forward inter-tier traffic on to patch port

OVS tunnel manager enhancements

• replaceNetworkACLList enhancements:
  • OvsTunnel manager shall subscribe to replaceNetworkACLList events using in-memory event bus
  • on event trigger, if the VPC offering of the VPC that contains the network, has 'distributedrouting' capability enabled then following actions shall be performed
  • get the list of the hosts on which network spans
  • on each host flush the ingress/egress ACL represented as flows on logical router bridge and apply new flows corresponding to the new ACL list

...