Lifecycle management service for pooled bare-metal infrastructure.
Go to file
akhiljain23 cf99ff0165 Updating docs
>> Changed project name from plasma to valence in docs.
>> Fixed docstring indentation.
>> Added features docs.
>> Added driver docs.
>> Hidden licence headers from html files.

Depends-On: Ia02bc00ad168b3c3d01ef6ca9696d43996091070
Change-Id: I1fa382d566165f5e76c84ad864024c0f546ef74c
2018-04-24 19:18:35 +05:30
api-ref/source Updating docs 2018-04-24 19:18:35 +05:30
doc Updating docs 2018-04-24 19:18:35 +05:30
etc Fixing installation for Ubuntu 16.04 2017-05-31 17:44:01 +05:30
releasenotes Updating docs 2018-04-24 19:18:35 +05:30
simulator Updating docs 2018-04-24 19:18:35 +05:30
ui Clean up css styles for each components. 2017-03-01 01:33:58 +00:00
valence Updating docs 2018-04-24 19:18:35 +05:30
.gitignore Clean valence.conf.sample generated by install_valence.sh 2017-06-28 16:47:22 -07:00
.gitreview Update project name setting in .gitreview 2016-11-23 21:44:55 -08:00
.testr.conf Make functional tests out of Jenkin's verification 2017-01-06 14:27:59 +08:00
babel.cfg Initial import from external repository 2016-10-07 08:50:05 +08:00
CONTRIBUTING.rst Update and replace http with https for doc links 2017-09-15 00:07:23 -07:00
HACKING.rst Update the documentation link for doc migration 2017-07-26 07:53:30 +00:00
install_valence.sh Clean valence.conf.sample generated by install_valence.sh 2017-06-28 16:47:22 -07:00
MANIFEST.in Initial import from external repository 2016-10-07 08:50:05 +08:00
README.rst Updating docs 2018-04-24 19:18:35 +05:30
requirements.txt Add async executor 2018-03-26 12:27:13 +05:30
setup.cfg Add ExpEther Driver in Valence 2018-03-28 03:54:34 +00:00
setup.py Update requirements manually 2018-01-31 09:12:45 +01:00
test-requirements.txt Update requirements manually 2018-01-31 09:12:45 +01:00
tox.ini Remove valence.conf.sample 2017-04-10 11:51:37 +05:30

Openstack Valence Project

Overview

Valence is a service for lifecycle management of pooled bare-metal hardware infrastructure. The concept of pooled storage (SSDs or nvmE) disaggregated from compute nodes and network disaggregated from compute and storage provides the flexibility to compose and uses as and when the cloud requires more server resources. Valence provides the capability "compose" hardware nodes and release resources as needed by the overcloud.

Valence supports Redfish as default management protocol to communicate to hardware. It supports Rack Scale Design (RSD), Open architecture for management of disaggregated server hardware resources, which is standardized in Redfish. Valence also provides capability to manage other vendors disaggregated hardware using their respective drivers other than Redfish.

Free software

Apache license

Wiki

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

Source

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

Bugs

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

Feature Highlights

Valence provides the following capabilities for managing disaggregated hardware resources.

Multiple Podmanager Support

Valence provides the capability to manage multiple podmanagers. Each podmanager can be configured to use different driver. By default, redfishv1 driver is used.

Currently supported drivers in Valence are:
  1. redfishv1-driver
  2. expether-driver

Future work include redfish v2 driver support. Other vendors also could implement their own driver to manage their hardware.

This provides uniform interface to manage all the disaggregated hardware in datacentre supporting different protocols.

Device Orchestration framework

Valence provides support for the dynamic management of pooled resources like storage, network and other pci devices which can be connected on demand to a composed node, giving user the ability to attach or detach the devices dynamically based on workload.

Ironic provision driver

Valence supports ironic provision driver to be able to register the valence composed node to ironic. Once the node is registered further operations of provisioning/managing could be directly performed using Ironic.

For more details on Ironic usage: Ironic API guide.

For more features please refer the Valence blueprints for supported and in-the-pipeline features.