Age | Commit message (Collapse) | Author | Files | Lines |
|
Its not needed to preserve onap release version in
patch naming.
Change-Id: I8dfaa56d3a74cd5227523c3acd5e31fa540a75a2
Issue-ID: OOM-1869
Signed-off-by: Michal Ptacek <m.ptacek@partner.samsung.com>
|
|
- Adding missing artifacts into onap_3.0.x-http_files.list
- Some fine-tuning of examples in DOCs
Issue-ID: OOM-1805
Change-Id: Ic5a55590a9fa9a244c43aff6a63554aefaea6cc5
Signed-off-by: Michal Ptacek <m.ptacek@partner.samsung.com>
|
|
This is required to align with OOM charts, otherwise
some components like DMAAP might be not initialized
properly. Furthmore removing duplicated files, most
of our data_lists are same for Casablanca MR and
Casablanca base releases.
Change-Id: I376410c7915d8f2682287c31392e2f3796adc990
Issue-ID: OOM-1771
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>
|
|
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>
|