Age | Commit message (Collapse) | Author | Files | Lines |
|
There are x86 specific build items that can't be used when building on
aarch64. Adding conditionals so that the items only get built in when
building on x86_64.
There are aarch64 specific settings that need to be set for deployment.
JIRA: APEX-381
Change-Id: I63e1c99d5d22bbb523c88be7e973a6c834a38b01
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
- power management updated to virtualbmc, pxe_ssh is deprecated
- removing custom tacker build
- removing custom congress build
- disabling yum update in undercloud on the cli instead of in a patch
- Undercloud is direct kernel booted now, there are no kernel and initrd
in the disk image from upstream
- remove OpenDaylight previous to Carbon
JIRA: APEX-433
JIRA: APEX-432
JIRA: APEX-431
Change-Id: I6963f16e65eacade5607a3082b58b6150331406c
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Currently we allow specifying ram per Overcloud VM. If the node is
detected as ODL, we bump the RAM to a minimum of 10GB. There is a need
to be able to specify the RAM per compute node in cases where we need
controller RAM to be high, but want compute nodes to be low (like CSIT)
- in order to keep the memory footprint as small as possible.
Changes Include:
- Adds '--virtual-compute-ram' argument that will override the
'--virtual-ram' param for compute nodes
- Fixes a bug where if ODL is used and RAM is overridden to 10GB for
Control nodes, it was also accidentally being set for compute nodes
- Modifies '--virtual-ram' to be '--virtual-default-ram' in order to
clarify this parameter sets the default amount of RAM for all
overcloud nodes which may be overridden by a role specific arg
Change-Id: Ia36082aa2167d9897f3ec6753d08804352301c63
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
- 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>
|
|
Change-Id: I602279b30b035cfc667e4ee9b83905a638440abb
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Change-Id: Ib03728e8ffe9c65044b32b4348e9c1c88862c6e3
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Defaults for virtual deployments was not correct, there were three baremetal
nodes being created by default for a noha deployment.
JIRA: APEX-221
Change-Id: I8b13ffb620d8ebaed4308725edbc7e84279872dd
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
JIRA: APEX-234
Change-Id: Ieb055d5de33177dd6f6b5286f3ff1608d62fbf60
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Changes include:
- RPM build for congress moved into Apex
- Fixes missing log dir for congress in spec
- Adds missing API network definition for Congress
- Fixes URL for getting doctor driver
- Increases controller default RAM to 10GB due to resource contention
with ODL
- Fixes Congress service config/db sync in THT to be in step 3
opnfv-tht-pr: 51
JIRA: APEX-212
Change-Id: I4a55646e7ef851782ae0d1963f7b479086958365
Signed-off-by: Carlos Goncalves <carlos.goncalves@neclab.eu>
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
trying to reduce the monolith deploy.sh to smaller parts
Change-Id: Ic40a7327d95a290d83f9c0b18ad87a280b0da3c4
Signed-off-by: Dan Radez <dradez@redhat.com>
|