x/valence
Code Issues Proposed changes
Lifecycle management service for pooled bare-metal infrastructure.
79 Commits 1 Branch 0 Tags 4.1 MiB
Python 84.6%
JavaScript 8.7%
reStructuredText 4.9%
Shell 0.9%
CSS 0.7%
Other 0.2%
6351e9a727
Go to file
Lin Yang 6351e9a727 Add vlan parameters in compose menu 
This patch adds new dynamic input form in compose menu to support
user specify vlan ID for the ethernet interface. And supoort
multiply ethernet setting in next commit.

Change-Id: Ife0698e599806bf776634080fd4b34725aec4fc6
Closes-Bug: #1634596
2016-11-21 18:23:53 +00:00
api-ref/source Aapi-ref doc, this is converted from Word file to RST format. 2016-10-27 10:44:04 -04:00
doc Migrate to flask 2016-11-04 21:08:06 +05:30
etc/valence Migrate to flask 2016-11-04 21:08:06 +05:30
releasenotes Initial import from external repository 2016-10-07 08:50:05 +08:00
ui Add vlan parameters in compose menu 2016-11-21 18:23:53 +00:00
valence Add initial redfish unit testing 2016-11-18 16:09:08 -08:00
.gitignore Add install_valence.log to gitignore 2016-10-27 12:47:26 -07:00
.gitreview Added .gitreview 2016-09-13 08:21:55 +00:00
.testr.conf Enable tox to run unit tests 2016-10-12 10:25:09 +05:30
babel.cfg Initial import from external repository 2016-10-07 08:50:05 +08:00
CONTRIBUTING.rst Initial import from external repository 2016-10-07 08:50:05 +08:00
HACKING.rst Initial import from external repository 2016-10-07 08:50:05 +08:00
install_valence.sh Fix some issues in Install_valence.sh 2016-11-18 16:40:53 +08:00
MANIFEST.in Initial import from external repository 2016-10-07 08:50:05 +08:00
README.rst Update the link of Valence blueprints in Readme 2016-11-16 15:19:33 +08:00
requirements.txt Use gunicorn instead of werkzeug 2016-11-11 21:40:51 -08:00
setup.cfg Use gunicorn instead of werkzeug 2016-11-11 21:40:51 -08:00
setup.py Initial import from external repository 2016-10-07 08:50:05 +08:00
test-requirements.txt Initial import from external repository 2016-10-07 08:50:05 +08:00
tox.ini Skip flake8 check for local node_modules directory 2016-11-09 10:34:23 -08:00

README.rst

Openstack Valence Project

Valence is a service for lifecycle management of pooled bare-metal hardware infrastructure such as Intel(R) Rack Scale architecture which uses Redfish(TM) as one of the management protocols.

Free software

Apache license

Wiki

https://wiki.openstack.org/wiki/Valence

Source

http://git.openstack.org/cgit/openstack/rsc

Bugs

http://bugs.launchpad.net/openstack-valence

Download and Installation

The following steps capture how to install valence. All installation steps require super user permissions.

Valence installation

  1. Install software dependencies

    $ sudo apt-get install git python-pip

  2. Clone the Valence code from git repo.

    $ git clone https://git.openstack.org/openstack/rsc

3. Execute the 'install_valence.sh' file present in the Valence root directory. The install script will automatically install the dependencies listed in the requirements.txt file.

$ sudo bash install_valence.sh

  1. Check the values in valence.conf located at /etc/valence/valence.conf

    set the ip/credentials of podm for which this Valence will interact

  2. Check the PYTHON_HOME and other variables in /etc/init/valence.conf

  3. Start valence service

    $ sudo service valence start

  4. Logs are located at /var/logs/valence/

GUI installation

Please refer to the installation steps in the ui/README file.

Components

Valence follows the typical OpenStack project setup. The components are listed 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 Plasma-api. It reads requests from the AMQP queue, process it and send the reponse back to the caller.

valence-ui --------valence-ui provides a GUI interface to invoke Valence APIs.

Features

Please refer the Valence blueprints for supported and in-the-pipeline features. https://blueprints.launchpad.net/openstack-valence