Jump to: navigation, search

Difference between revisions of "QuantumClientGUI"

Line 9: Line 9:
 
* attach/detach those interfaces from networks.  
 
* attach/detach those interfaces from networks.  
  
An example template for this GUI would be the work to modify [[OpenStack]] dashboard for the Quantum demo given at the Diablo summit.   
+
Some representation of additional attributes exposed by [[ QuantumAPIExtensions ]] may be desirable as well (e.g. QoS, ACL's, etc).  An example template for this GUI would be the work to modify [[OpenStack]] dashboard for the Quantum demo given at the Diablo summit.  The bulk of the code can be done in a "django-quantum" module.   
  
 
This work may benefit from shared client library code with the [[ QuantumClientCLI ]] work.
 
This work may benefit from shared client library code with the [[ QuantumClientCLI ]] work.

Revision as of 18:01, 1 July 2011

The Quantum GUI should expose all tenant operations exposed as part of the core Quantum API.

Communication with Quantum should be over the tenant web services API.

Key operations include

  • creation/modify/delete networks
  • view set of available interfaces exposed by "interface services"
  • attach/detach those interfaces from networks.

Some representation of additional attributes exposed by QuantumAPIExtensions may be desirable as well (e.g. QoS, ACL's, etc). An example template for this GUI would be the work to modify OpenStack dashboard for the Quantum demo given at the Diablo summit. The bulk of the code can be done in a "django-quantum" module.

This work may benefit from shared client library code with the QuantumClientCLI work.