| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
JIRA: ARMBAND-173
Currently only ha scenarios were successfully deployed on virtual pods
The default configuration is for ha scenarios and those have 5 target nodes
while on the noha scenarios there are 4. The noha scenarios failed because
it was trying to parse one extra node.
This patch modifies the dea and dha files for each noha scenario so that the
nodes are properly configured.
Change-Id: I360aeaf8dc92e0ff614367d47d74f6fa61ef2268
Signed-off-by: cristinapauna <cristina.pauna@enea.com>
|
|
Some leftover chars in https://gerrit.opnfv.org/gerrit/#/c/24901/
were keeping the deploy to work.
Also, the empty folder networks was added. This folder should contain templates
for virtual network config for the targets. For arm we don't need those so we
leave it empty for consistency with other projects and for avoiding changing
the deploy logic
JIRA: ARMBAND-122
Change-Id: Id33e2efacc3ff8d3754c8b29d4bebefd0b385c41
Signed-off-by: cristinapauna <cristina.pauna@enea.com>
|
|
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>
|
cristinapauna