Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Ieccbd863e45bb68d76f4f1f066433276c9adf3cd
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: OOM-945
|
|
See description in linked issue id.
Change-Id: I3bcec1214875cb318dc45162013aec8957443dc8
Issue-ID: OOM-845
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
Change-Id: I9f4d43c2a3f0766b9c8477a180f5a0bd45fde243
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: OOM-748
|
|
This is as a means towards obsoleting the oneclick scripts
from the Beijing release, in favour of directly using Helm.
From this point on, users of onap should use the follow
command:
helm install local/onap -n onap --namespace onap
Please refer to the official documentation for all the steps
required to deploy onap. Currently as a patched to be
merged: https://gerrit.onap.org/r/#/c/37871/
Change-Id: I75e5dbc9a79fec86a9b7c0cff487b10ec9df9a20
Issue-ID: OOM-816
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
Issue-ID: OOM-821
Change-Id: I627ac962afe8cd6bf2859a30a0e88f6c9ac89d34
Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com>
|
|
This is a top-level parent helm chart which deploys customizations
of the ONAP platform.
The parent ONAP chart represents the start of OOM's move away from
the oneclick bash scripts and towards the direct use of Helm to
manage configuration and deployment of ONAP.
How to deploy onap chart from local oom/kubernetes codebase.
** need to create/update dependencies defined in the chart's
** requirements.yaml
helm dep update onap/
** deploy the onap parent chart (and all referenced subcharts)
** with the "release" name of 'onap'
helm install onap/ -n onap
Change-Id: I71bee25770bdce82a47bfabb04946bb4fad069a2
Issue-ID: OOM-265
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|