summaryrefslogtreecommitdiffstats
path: root/config/inventory/pod_example_settings.yaml
AgeCommit message (Collapse)AuthorFilesLines
2016-12-20Adds declaring disk device to use on overcloud nodesTim Rozet1-0/+5
Now in inventory file a user can declare 'disk_device' which will allow the user to specify which disk on their overcloud server to use for installation. The variable can be a comma delimited list, which will search in order post-introspection for the first device on the node that exists. The default disk used will be sda for deployments. Currently defining a per node disk is not supported by OSCLI, so although defined that way in Apex inventory, only the last definition will be used for all nodes. Other changes include: - Various fixes in inventory parsing - Makes bash writing a common function - Introspection now enabled for baremetal deployments JIRA: APEX-296 Change-Id: I330d91eb17408ccfceb7a99c25edbae5ce6d848d Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-02-13Support power management type changesMichael Chapman1-0/+5
JIRA: APEX-95 pm_type is already in the sample instackenv.json but wasn't previously being read. Change-Id: Ia82c5010481d77d142d4fa3ca6e738558e8e9e4e
2016-01-27Fixes various bugs and adds some improvementsTim Rozet1-5/+5
Changes Include: - Disables introspection. We don't currently use introspection for anything other than to just run it. Disabling it to increase deploy speed and reduce pxeboot issues. - Adds timeout to deploy of 90 minutes. Default heat timeout is 3-4 hours. - Fixes OVS bridge attach/detach for users who use PREFIX in their ifcfg instead of NETMASK - Adds nosdn deploy settings file, and allows nosdn deployments - Adds example inventory file to the docs dir Change-Id: Ic13d6c4d5f27bac25365e5951acdd9bd3e641a15 Signed-off-by: Tim Rozet <trozet@redhat.com>
2015-12-21Added node role configurationViktor Tikkanen1-0/+5
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 <viktor.tikkanen@nokia.com>
2015-12-02Adds yaml files to use as input to Apex build/deployTim Rozet1-0/+46
yaml inputs are broken up into: -build settings -deploy options -network definition -pod baremetal information JIRA: APEX-53 Change-Id: Iee85b17beb37ce82bf9312dcce61e09ae924dfc5 Signed-off-by: Tim Rozet <trozet@redhat.com>