diff options
author | cristinapauna <cristina.pauna@enea.com> | 2016-11-25 17:06:27 +0200 |
---|---|---|
committer | cristinapauna <cristina.pauna@enea.com> | 2016-11-25 17:52:46 +0200 |
commit | dbc3359d6b8d66549d7975156c42acbdae0d0d5d (patch) | |
tree | fc7b18993b100b23a57a426df2cdf5fbffcfaed3 /patches/fuel-astute | |
parent | 572381de2421d62b14028cf5d4efa721ee434832 (diff) |
Fuel rework for multiple libvirt
The current fuel arhitecture assumes that all the VMs
(Jenkins slave, Fuel master and Target nodes) are all on
the same server. There is code that allows the Fuel master
to be on a different machine, but nothing for the Target nodes.
In Enea-Arm lab we have a different server for each.
This commit also adds specific templates for a virtual pod in
the Enea-Arm lab.
Therefore, the following changes are done:
- The default libvirt URI is the machine on which the Target nodes are
- The parameter libvirtUri was added in the dha.yaml file for fuel master
- All virsh calls have "-c" option to explicitly specify the uri; this parameter
is set only when libvirtUri is explicitly set in the yaml file
- The scenarios dha override now point to the arm template files
- The network templates are not needed for ARM, as the network infra is provided
by the server on which the Target node VMs reside; the folder is added here
just for consistency
- The target nodes are created with virsh rather than quemu when the nodes are
not on the same machine as Jenkins slave (similar logic to what is done for
remote Fuel master)
JIRA: ARMBAND-122
FIXME: remove hardcodes for
- Network bridges from templates
- Default pool
- libvirtUri from scenario overwrite
Change-Id: Ibf4744e5593f5201550115397024fd8311696074
Signed-off-by: cristinapauna <cristina.pauna@enea.com>
Diffstat (limited to 'patches/fuel-astute')
0 files changed, 0 insertions, 0 deletions