Ryu » History » Version 2

« Previous - Version 2/10 (diff) - Next » - Current version
Thiago Paiva, 23 Sep 2013 11:25


Ryu

About

Network management applications on top of Ryu (inside a controller node)

  • GRE tunneling
  • VLAN support
  • topology discovery
  • MAC based segregation

'Only commodity hardware'

Ryu <--> OpenStack

  • Flat networks regardless of the underlying physical network
  • Scalable multi-tenant isolations
    • tunneling based isolations
    • VLAN does not scale larger than 4096
    • do not need high-end switches
  • Future items:
    • integration with quantum IPAM and L3 API
    • firewall
    • virtual network <--> physical network
    • distributed controllers (redundancy)

Quantum plugin ofr each network technology

Communication

'nova requests quantum-server for network configuragion'

OVS <--> Ryu: openflow

Ryu agent <--> Ryu: REST API

Quantum server <--> Ryu: REST API

Ryu agent <--> Quantum db: db access

VIF driver <--> quantum: Quantum API
linux_net driver <--> server: Quantum API

Network Creation (network-node = nova-network + linux_net driver + OVS)

  1. to nova-network: create netork
  2. nova network --> quantum server: create net
  3. quantum server --> Ryu: network <uuid>, <tunnel key>
  4. quantum server --> nova network: <uuid>
  5. nova network --> linux_net driver: plug
  6. linux_net driver --> OVS: create gw-xxx
  7. linux_net driver --> quantum server: tentant id, network id, dp id, port, mac
  8. quantum server --> Ryu: network id, dp id, port, mac
  9. ryu --> OVS: set flow entryies

Instance creation (compute-node = nova compute + VIF driver + OVS)

  1. to nova compute: create instance
  2. nova compute --> quantum server: create port
  3. quantum server --> nova compute: uuid
  4. nova compute --> VIF driver: plug
  5. VIF driver --> OVS: create tap-xxx
  6. VIF driver --> quantum server: (tenant_id, dp_id, port, mac)
  7. quantum server --> Ryu: (network_id, dp_id, port, mac)
  8. Ryu --> OVS: set flow entryies

Also available in: PDF HTML TXT