Age | Commit message (Collapse) | Author | Files | Lines |
|
OOF component recently introduced new internet dependency
and it's downloading flask and requests pip packages.
This patch is needed for fixing this in offline platform.
Change-Id: I5bb707bf13af30f6df5cfd42cee75e2d1839821e
Issue-ID: OPTFRA-509
Signed-off-by: Michal Ptacek <m.ptacek@partner.samsung.com>
|
|
some oom helm charts patching from Casablanca is not needed,
this is the rest we need to keep eye on.
Change-Id: I0011d2bfdb4552c08745822989f830969f46ab9a
Issue-ID: OOM-1869
Signed-off-by: Michal Ptacek <m.ptacek@partner.samsung.com>
|
|
Casablanca policy is using different file as its keystore.
We need to adjust our patch accordingly
Issue-ID: OOM-1727
Change-Id: I67cb3f098a8e56467594832050dbc2c66dbe124c
Signed-off-by: Michal Ptacek <m.ptacek@partner.samsung.com>
|
|
|
|
In some deployments not all chart files might be present.
We should not fail if some components are not deployed.
Issue-ID: OOM-1691
Change-Id: I6a0ae05e753a2de6301ee0188022a958868776ad
Signed-off-by: Michal Ptacek <m.ptacek@partner.samsung.com>
|
|
Since there is no difference in patching between 3.0.0 and 3.0.1
release there name of patchfile that includes this tag
is unnecessary and confusing.
Issue-ID: OOM-1687
Change-Id: I751398f15c38dab83e36ed0b8f555533497291f8
Signed-off-by: Milan Verespej <m.verespej@partner.samsung.com>
|
|
To avoid dependency on patch utility and to have standardized look
of patch file this change uses git-format and git-apply to patch
charts.
Change-Id: I1c63334619bf6091b5ab50a4eebfadb3c28a2616
Issue-ID: OOM-1634
Signed-off-by: Milan Verespej <m.verespej@partner.samsung.com>
|
|
These pods are installing packages from apt and pypi repositroies
during runtime.
This change creates patch and makes necessary modifications
for packages being installed from offline repositories.
Change-Id: Id71f40f94c8641ad0c9d1ba4c87d3daea70c828e
Issue-ID: OOM-1619
Signed-off-by: Milan Verespej <m.verespej@partner.samsung.com>
|
|
This commits introduced another bunch of patches for OOM charts
we need in Casablanca to be able to get our certificate trusted
by policy pods which are collecting maven artifacts from our
nexus during runtime.
Change-Id: I8289b155970e57059bccb5dfe09231e28bf27a32
Issue-ID: OOM-1609
Signed-off-by: Michal Ptacek <m.ptacek@partner.samsung.com>
|
|
DCAE bootstraping require that bootstrap/cloudify-manager pods has
to trust our certificate. We are mounting path to this certificate
to respective pod.
Change-Id: Ie2ea796851e6def52d4ec556c9d5b19633e8a743
Issue-ID: OOM-1618
Signed-off-by: Michal Ptacek <m.ptacek@partner.samsung.com>
|
|
This commit is showing-up how OOM patches must be handled in casablanca
release. In Dublin we would like to avoid this completely OOM-1610
so here we are just reproducing the same logic which was already
implemented in Beijing for bash offline installer.
In general it works in a way that OOM charts are patched during
offline platform build and values are configured in install time using
pre-install application role/hook.
Change-Id: I1a2425ef63edd6bc08dcecf0fcae7fd6e553d0ed
Issue-ID: OOM-1616
Signed-off-by: Michal Ptacek <m.ptacek@partner.samsung.com>
|
|
For old bash solution how it got working with Beijing release of
ONAP, some of the Helm charts needs to be patched to work offline.
This file is tracking what changes are done and these changes are
applied by installer on top of cloned Helm charts.
Change-Id: Ic2265773de3bcfdb9d6aca19c2bcb4b5852966ba
Issue-ID: OOM-1551
Signed-off-by: Samuli Silvius <s.silvius@partner.samsung.com>
|