From 3c78ff4776a98ef9f69bdcbe506c56d4a456a80c Mon Sep 17 00:00:00 2001 From: Viktor Tikkanen Date: Thu, 17 Dec 2015 10:50:06 +0200 Subject: Added node role configuration If there are dedicated HW nodes for controller and compute nodes, it should be possible to define node roles in configuration files. This patch introduces "capabilities" property into pod_example_settings.yaml so as adds needed flavor definitions and overcloud deploy parameters into opnfv-deploy script. Change-Id: Ie62d3fa215aa168390d074c73fdb2fa03ecc67f5 Signed-off-by: Viktor Tikkanen --- docs/installation-instructions/installation-instructions.rst | 1 + 1 file changed, 1 insertion(+) (limited to 'docs/installation-instructions') diff --git a/docs/installation-instructions/installation-instructions.rst b/docs/installation-instructions/installation-instructions.rst index 72a7bb22..8703fdd3 100644 --- a/docs/installation-instructions/installation-instructions.rst +++ b/docs/installation-instructions/installation-instructions.rst @@ -288,6 +288,7 @@ IPMI configuration information gathered in section `Execution Requirements (Bare - ``pm_addr``: IPMI IP Address - ``pm_user``: IPMI username - ``pm_password``: IPMI password + - ``capabilities``: Intended node role (profile:control or profile:compute) - ``cpu``: CPU cores available - ``memory``: Memory available in Mib - ``disk``: Disk space available in Gb -- cgit 1.2.3-korg