From bf2a283f85a19c17d8d261210faebe9557ccd8d5 Mon Sep 17 00:00:00 2001 From: praveenraj Date: Tue, 20 Dec 2016 16:30:56 +0530 Subject: [PATCH] Fix minor mistake in README.rst file 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 --- README.rst | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/README.rst b/README.rst index 95c5581..66d227a 100644 --- a/README.rst +++ b/README.rst @@ -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