summaryrefslogtreecommitdiffstats
path: root/kubernetes/onap/resources/overrides
AgeCommit message (Collapse)AuthorFilesLines
2020-03-13Add dcaemod chartsJack Lucas1-0/+2
Issue-ID: DCAEGEN2-1866 Change-Id: I0179e1e75529ad8017b1a5c23747dbd80aa6f625 Signed-off-by: Jack Lucas <jflucas@research.att.com> Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2020-03-09add yaml for 5G Network Slicing usecasezhangqingjie1-0/+172
Issue-ID: OOM-2329 supply a ONAP installation config file for 5G Network Slicing usecase, so that the user can easily install a minimum-scope ONAP with as few resources as possible. Signed-off-by: zhangqingjie <zhangqingjie@huawei.com> Change-Id: I728a0229296d62120418f654e4c3f50a2805a69e
2020-02-13[SO] Enable use of Keystone v3Sylvain Desbureaux1-1/+5
SO can handle keystone v3 but override file must be capable to handle this. If openStackKeystoneVersion is set to "KEYSTONE_V3" in so-catalog-db-adapter config part, SO will be able to use keystone v3 for OpenStack Issue-ID: OOM-2221 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I14db318d25842a08ef380f6edb708e26dae050ad
2020-01-17Add VID to onap-vfw overridesBrian Freeman1-1/+3
Issue-ID: OOM-2266 Change-Id: I0c571c765cb099b1f2e7886bc686e24a436f290e Signed-off-by: Brian Freeman <bf1936@att.com>
2019-11-26Example ingress configuration with vhostsLucjan Bryndza1-17/+11
Example ingress configuration with vhosting support. Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com> Issue-ID: OOM-2125 Change-Id: I62c818f8941871cbebdfbf1984e7b6eee7e1180d Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
2019-10-02Increase liness/readiness timeout and periodBrian Freeman1-0/+17
Issue-ID: OOM-2059 Change-Id: I02bbdd5b06e7194434d761bcf1aebbd749c6f1d7 Signed-off-by: Brian Freeman <bf1936@att.com>
2019-10-02Improved nginx configuration overrridesLucjan Bryndza1-1/+18
Nginx ingress controller configuration sample adopted to the new ingress configuration common templates. Issue-ID: OOM-1508 Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com> Change-Id: I1e8f069dbcff8ae3c927bad763d1bc2595cc9311 Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
2019-09-11Add cds to onap-all-ingress-nginx.yamlAbdelmuhaimen Seaudi1-0/+2
Issue-ID: OOM-2085 Signed-off-by: Abdelmuhaimen Seaudi <abdelmuhaimen.seaudi@orange.com> Change-Id: Iaabdf44581c6b0dc5e0600454a5ff9bcaeaba16c
2019-09-10Seperate CDS chart from SDNC in OOMAbdelmuhaimen Seaudi1-0/+2
Issue-ID: OOM-2085 Signed-off-by: Abdelmuhaimen Seaudi <abdelmuhaimen.seaudi@orange.com> Change-Id: I21fed8c9cf33967f62f156cac96deefdcb4f8d47 Signed-off-by: Abdelmuhaimen Seaudi <abdelmuhaimen.seaudi@orange.com>
2019-07-22Add nginx ingress configuration overridesLucjan Bryndza1-0/+80
Add example nginx ingress controller configuration overrides for testing purposes. Change-Id: Ibac181c4e79fab4cd5b63b28bf4f25912bfe4724 Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com> Issue-ID: OOM-1508
2019-07-08Merge "Enabling generic parser in onap-all override file"Yang Xu1-0/+2
2019-07-02Merge integration timing to environment.yamlBrian Freeman1-0/+225
Issue-ID: OOM-1959 Change-Id: I835be9a5eccf72e8e6534da1e5090f21d10c7a5a Signed-off-by: Brian Freeman <bf1936@att.com>
2019-07-01Enabling generic parser in onap-all override fileTomáš Levora1-0/+2
The modeling generic parser needs to be enabled in general override file onap/overrides/onap-all.yaml Issue-ID: MODELING-175 Signed-off-by: Tomáš Levora <t.levora@partner.samsung.com> Change-Id: Ia175145b2c9a3c4ca4da1fe8cbf119b41fc9782a
2019-05-09Add doc guide fixesMike Elliott1-11/+7
Change-Id: Ibe57c857b4d9367b77878757821c2e9c44c61a7b Issue-ID: OOM-1598 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2019-05-08Update overrides to support docsMike Elliott3-2/+126
Change-Id: I2a0428bfec238231b299c9f35364979b116a5d67 Issue-ID: OOM-1598 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2019-03-02Improve override usabilityMike Elliott1-0/+73
Currently when you deploy onap with no override file, the behavior is to deploy everything. In order to deploy a subset of components, an override file must contain all components and then disable the ones you don't want. As we prepare to transfer helm chart ownership to the teams, it will simplify the creation of project specific development override files, if the default behavior for deploying onap was reversed. Allowing override files to only contain the components they care to enable (and configure) and ignore the rest as they would be disabled by default. From this point on, it will be necessary to use an override file (as integration uses for testing) to enable all components. This patch includes an onap-all.yaml override file that may be used for this purpose. helm deploy dev local/onap -f onap/overrides/onap-all.yaml No configuration is part of this override. Its purpose is only to enable the components and is intended to be used in combination with other override files that provide environment specific configuration. Change-Id: I4b74a3a8a35a178298af7205762e2aca7c65dda3 Issue-ID: OOM-1692 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>