summaryrefslogtreecommitdiffstats
path: root/lib/python/apex_python_utils.py
AgeCommit message (Collapse)AuthorFilesLines
2016-12-20Adds declaring disk device to use on overcloud nodesTim Rozet1-2/+9
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-09-27Removing --flat and network_isolation variablesDan Radez1-12/+2
VLAN support allows a set of nodes with a single nic to deploy removing the need for --flat. flat was not well maintained or tested. Change-Id: Ieae1c2350c83544ce50048b44300fa0b8e68dd43 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-09-22migrating to proposed common network settings fileDan Radez1-16/+3
- proposed in genesis https://wiki.opnfv.org/display/genesis/Common+Network+Settings - This patch updates the network_settings files in the config/network dir and updates the associated bash, python and python tests relative to the new yaml structure and nomenclature used in the proposed settings file JIRA: APEX-262 Change-Id: Ib0dc9d0f21465b38f2a53cff20f71fb9230bfc48 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-09-20Handling file loads and tmp dirs differentlyDan Radez1-2/+9
Change-Id: I602279b30b035cfc667e4ee9b83905a638440abb Signed-off-by: Dan Radez <dradez@redhat.com>
2016-09-07moving inventory file parsing to pythonDan Radez1-4/+25
Change-Id: Ib03728e8ffe9c65044b32b4348e9c1c88862c6e3 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-08-30Adds ability to power off nodes in cleanTim Rozet1-0/+11
Now if an inventory file is provided to clean, those nodes will be powered off. JIRA: APEX-250 Change-Id: I2d78285717726c3d1c9d7d88c38e706d4617e337 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-08-22removing enabled_network_list as an argument to network envDan Radez1-9/+6
NetworkSettings Object is being rendered and passed to net env object already. We can get the enabled network list from the network settings object instead of passing it in as an arg. Basically just removing duplicate arguments to the network env object. Change-Id: I828c60878a0432cae2b37c08ae1896dce49071d0 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-08-11Making NetworkEnvironment a dictDan Radez1-1/+1
Change-Id: I983f4483b328268413d4ec66c753f1219d59fd27 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-08-10Merge "Making NetworkSettings a dict"Dan Radez1-2/+1
2016-08-09Making NetworkSettings a dictDan Radez1-2/+1
Change-Id: Ib7fc4e9ca543a4c678576ea2119fa606ece0095c Signed-off-by: Dan Radez <dradez@redhat.com>
2016-08-04Fix network_isolation argparse issueFeng Pan1-4/+4
JIRA: APEX-222 Change-Id: I435852fbe1597bf03f617dc14a6718de699b648f Signed-off-by: Feng Pan <fpan@redhat.com>
2016-08-03Adds configuring vpp/hc on all nodesTim Rozet1-1/+14
Changes include: - starting vpp with pci addr of tenant nic - setting performance options for fdio scenario - creates nosdn fdio scenario (needs newtorking-vpp, etc) - starts HC if ODL is used opnfv-tht-pr: 46 JIRA: APEX-133 Change-Id: Ie7a7f1418b94dfb82255ec9aebc550a955dd696a Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-07-18Allows specifying nic order for overcloud nodes in network settingsTim Rozet1-4/+6
Currently there is no way to specify logically or physically the nic order to be used on overcloud nodes. We always hardcode to use nic1 for admin network, nic2 for private, etc. This patch allows a user to not only decide which logical nics to use for which network, but also specify physical interface names if they need to. This is done on a per role basis, due to tripleO limitation. So a user is able to specify nic order/names for compute and controller roles separately. If a user specifies nic order, they must specify it for all networks other than admin network. We assume if admin network is unspecified it uses "nic1", so that name is reserved in this case. A user is also allowed to specify a mixture of logical and physical names, for example "nic2" and "eth3" on another network. JIRA: APEX-151 Change-Id: Ie9d4abb463cf8f8788913cb4bcf9486830adc449 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-06-30Syntax updates and new testsDan Radez1-0/+206
- syntax updates to match pep8 standards - tests to cover apex_python_utils.py Change-Id: Ifac06fdbb97266f1b574b20610979b6965d6dd55 Signed-off-by: Dan Radez <dradez@redhat.com>