This module provides a generic quantum plugin 'QuantumRestProxy' that translates quantum function calls to authenticated REST request to a set of redundant external network controllers.
This allows the network controller specific code to be decoupled from this plugin. This allows for:
- independent authentication and redundancy solutions for quantum and the network controller since they are now decoupled.
- independent upgrade/development cycles for quantum and network controller since it limits the proxy code upgrade requirement to quantum release cycle (and the network controller specific code upgrade requirement to network controller release cycle).
It also keeps a local persistent store of quantum state that has been setup using that API. This allows us to:
- independently update/recover the external network controller(s) as their state can now be updated to be in sync with the state previously programmed via the API.
- provide local response for query operations and fail-fast when it can be determined based on previously configured state.
Downstream REST API used by this proxy is almost same as the API as defined for quantum itself (more specifically, the JSON subset with some additional parameters, e.g. gateway on network-create request and macaddr on port-attach request). In addition, it also requires support for an additional PUT to do a bulk dump of all persistent data; this is used for state synchronization (if supported).
- FloodLight Openflow Controller
Floodlight controller uses this plugin to provide openflow/VLAN based virtual networks. Four components will be needed:
- An openstack controller running the nova and quantum services
- A Floodlight Controller running the Virtual Network Filter
- This plugin, which translates nova/quantum api to REST requests to Virtual Network Filter
- And an OpenVswitch (OVS) running on each of the the nova-compute nodes
For details on how to configure FloodLight, please check:
For Quantum Folsom please use the following instructions: