x/valence
Code Issues Proposed changes
Lifecycle management service for pooled bare-metal infrastructure.
110 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%
8154e5c072
Go to file
John L. Villalovos 8154e5c072 Remove reference to magnum in .gitignore 
There was a reference to magnum files in .gitignore

Change-Id: Ie3946328373f7f8668c9fdc25028afc40f963a77
2016-12-13 13:22:19 -08:00
api-ref/source rename issue for flavor->flavors 2016-12-06 10:27:40 +08:00
doc Added developer documentation 2016-12-08 05:30:28 +00:00
etc/valence [Trivial] Add placeholder for podm port in config 2016-12-12 19:19:07 -08:00
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 Merge "Revert "Added Error Response"" 2016-12-12 04:22:04 +00:00
.gitignore Remove reference to magnum in .gitignore 2016-12-13 13:22:19 -08:00
.gitreview Update project name setting in .gitreview 2016-11-23 21:44:55 -08:00
.testr.conf Enable Api Functional Test 2016-12-02 09:54:07 +08:00
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 Fix h305 python import order issue 2016-11-22 09:17:33 +05:30
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 RSC to Valence 2016-11-25 09:58:38 +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 fix '#tox -e api-ref' not working for generating Valence API Docs 2016-12-05 16:51:24 +08:00
tox.ini Change py34 to py35 in tox setting 2016-12-07 18:16:22 -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/valence

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/valence

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 valence-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