x/valence
Code Issues Proposed changes

Fix minor mistake in README.rst file

Browse Source 
In valence README.rst file, Under "components" section there
is small mistake, which states valence api is pecan based daemon.
Now this has been changed to flask based daemon.

Change-Id: I308b623ab6061d5b94689e31863a70d626f15d28
Closes-Bug: #1651397
This commit is contained in:
praveenraj 2016-12-20 16:30:56 +05:30
parent af61ee043a
commit bf2a283f85
1 changed files with 7 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
README.rst
View File

@ -78,17 +78,16 @@ below:
valence-api
-----------
A pecan based daemon to expose Valence REST APIs. The api service communicates
to the controller through AMQP.
valence-controller
--------------
The controller implements all the handlers for valence-api. It reads requests
from the AMQP queue, process it and send the reponse back to the caller.
A python based daemon based on Flask framework to expose Valence REST APIs.
The api service communicates to the PODM through REST interface using Redfish(TM) specification.
For adding new api please refer https://github.com/openstack/valence/blob/master/doc/source/developer-guide/add_new_api.rst
valence-ui
--------
valence-ui provides a GUI interface to invoke Valence APIs.
valence-ui provides a Web based GUI interface that can be used to explore
Rack Scale Design (RSD) artifacts and compose/disassemble nodes.
valence-ui is implemented using Node.js runtime environment and hosted through apache.
valence-ui makes us of React.js javascript libaray and invoke Valence REST APIs through ajax REST calls.
==========
Features