Commit 0d47b9d1 by akhiljain23 Committed by Anusha Ramineni

Adding Valence-0.9 relasenotes doc

This commit adds valence-0.9 relasenote which contain following
features:
>> Support for multi-vendors in Valence
>> Device Orchestration
>> ExpEther driver

Change-Id: I13c9b9e7113f432b453cb107b74928933751a9fe
parent cf99ff01
......@@ -42,6 +42,13 @@ Contributors Guide
contributors-guide/*
Release Notes
=============
.. toctree::
:maxdepth: 1
releasenotes/valence-0.9
Indices and tables
==================
......
=========================
Valence 0.9 Release Notes
=========================
*************
Main Features
*************
Multi-Podmanager Support
------------------------
Valence provides the capability to manage multiple podmanagers.
Each podmanager can be configured to use different driver.
By default valence provides redfish driver to manage the hardware.
Also provides framework for other vendors could implement their
own driver to manage their hardware.
More detail refer :ref:`Multi Podmanager Support <multi-podm-support>`.
Device Orchestration
--------------------
Valence supports management of pooled resources and adds
ability to attach/detach dynamically to nodes according
to workload demand. New config option 'enable_periodic_sync'
supported to sync resources from podmanager periodically.
By default, periodic sync is disabled.
More detail about :ref:`Device Orchestration Framework <device-orchestration>`.
Ironic provision driver
-----------------------
Valence supports ironic provision driver to interface with Ironic, 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.
More detail about :ref:`Ironic Provision Driver <ironic-provision-driver>`.
ExpEther driver
---------------
Added ExpEther driver support inside valence to be able to manage
NEC ExpEther hardware.
More detail about :ref:`ExpEther Driver <expether-driver>`.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or sign in to comment