summaryrefslogtreecommitdiffstats
path: root/config
AgeCommit message (Collapse)AuthorFilesLines
2021-03-25Update 'Configuration' chapter of install guideBartek Grzybowski1-2/+2
Change-Id: Iea6e571f2e7c9f4a3f7c54fb5318bb05736cb97a Issue-ID: INT-1893 Signed-off-by: Bartek Grzybowski <b.grzybowski@partner.samsung.com>
2019-11-12Revert "Fix packaging offline-installer"Tomáš Levora1-0/+20
This reverts commit 92477974b68c7638a43ffc869e3ea9fb854b3534. Reason for revert: Not solved handling of application_configuration.yml in package.py Change-Id: I814c01dc1f7334a961e991c42fd485d9af4675a1 Signed-off-by: Tomas Levora <t.levora@partner.samsung.com> Issue-ID: OOM-2201
2019-11-11Fix packaging offline-installerDenis Kasanic1-20/+0
Fix typos in Build and Install documentation Fix using relative paths in args for package.py Fix missing hosts.yml & application_configuration.yml in sw_package Change default build-version of packaging to empty as used in docs Give possibility to specify own inventory file to package in package.py Issue-ID: OOM-1994 Issue-ID: OOM-2197 Issue-ID: OOM-2158 Signed-off-by: Denis Kasanic <d.kasanic@partner.samsung.com> Change-Id: I76598fb71a42ada1a71c9905ef2d32bc03d8f71c
2019-10-11Remove patching from offline-installerTomáš Levora1-2/+1
The patching of OOM should not be necessary to bypass offline state, therefore this custom patching can be removed in offline-installer Issue-ID: OOM-2014 Change-Id: I61b4cd48cfada613a7914ef5001bb64f7584815a Signed-off-by: Tomáš Levora <t.levora@partner.samsung.com>
2019-05-29Changing patchfile naming conventionMichal Ptacek1-2/+2
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>
2019-05-09Updating offline platform with latest 3.0.2Michal Ptacek1-1/+1
- 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>
2019-03-07Refine application_pre_install_role variable usageBartek Grzybowski1-3/+3
As 'application_pre_install_role' variable set in config/application_configuration.yml must stay in sync with patch role directory name defined in package.conf under APP_CONFIGURATION variable, it's name shall stay under complete user control without any variable as part of it's name. App_helm_build_targets list and app_helm_chart_name should default to 'onap' in application_configuration.yml as customizing them isn't supported at the moment. Also fixed some wording in comments/docs in relevant files. Change-Id: I82b6dd519fbc3426739a11fac1e02eb495a668c0 Issue-ID: OOM-1697 Signed-off-by: Bartek Grzybowski <b.grzybowski@partner.samsung.com>
2019-02-13More default values and simplify onap configSamuli Silvius1-84/+10
Populate more default values for ansible all.yml configuration to make it simpler by default for user. Removed project_configuration variable as it caused just confusion. Replaced that mostly by using app_name variable. According to above changed simplified actual configuration config/application_configuration.yml used to install onap. Mostly removed repeation of comments. Also updated ansible/application/README.md that was not updated for a while. Issue-ID: OOM-1633 Change-Id: Idcc4c510b64bb61edd874d0e0616cdb41938f2d3 Signed-off-by: Samuli Silvius <s.silvius@partner.samsung.com>
2019-02-11Change helm plugin install to copy moduleMilan Verespej1-2/+2
Since helm plugin install command is not the most suitable for Ansible and it basically just creates link to plugin original location this change is using Ansible's copy module instead. Plugin is copied from install server because copy module doesn't support recursive directory copying with remote_src option. Issue-ID: OOM-1638 Change-Id: I9e9dcd8d33f8917296f576c2b34c0c576c9c126c Signed-off-by: Milan Verespej <m.verespej@partner.samsung.com>
2019-02-06Setting-up NPM registry for dgbuilderMichal Ptacek1-0/+95
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>