Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Ia742842cf1878c5786f71949013ed8afedd13c39
Issue-ID: OOM-909
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
Change-Id: Ic9f0eb567716224893955d9379e9ed9308b9ea79
Issue-ID: OOM-740
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
updated the endpoints and service in a single namespace onap deployment prospective
updated the parameters order for the image source to allow override
Issue-ID: OOM-743
Change-Id: I6a379ec4661d465f95478b383d60c3b2eecc0f72
Signed-off-by: Jerome Doucerain <jerome.doucerain@bell.ca>
|
|
This is a standardization (based on helm community best practices)
of a Helm chart for the Service Orchestrator (so) in ONAP.
How to deploy the so chart (outside of the parent onap chart) from
the local oom/kubernetes codebase.
** need to create/update dependencies defined in the chart's
** requirements.yaml
helm dep update so/
** deploy the so helm chart with the "release" name of 'onap'
helm install so/ -n onap
Change-Id: I22471eb9fe0dec32941e14dc63857222c80ebe20
Issue-ID: OOM-727
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|