Age | Commit message (Collapse) | Author | Files | Lines |
|
Adds watchdog config and tables, oof configuration, aai athentication, etc.
Change-Id: I43b5432d12c69ef45cdbeff5ab3427fbf5e9d1d0
Issue-ID: OOM-1039
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
Update the docker image versions in the OOM helm charts
with the versions specified in the docker-manifest.csv
in the integration repo.
Change-Id: I38bd9e98ae1b15ed4bbc68051b8516f311aa8db0
Issue-ID: OOM-1053
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Aligned service names (and numerous other minor fixes) with latest best practices
and standard templates.
Change-Id: I740fe299053805df60abcd6a6043031d8beda7e8
Issue-ID: OOM-909
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
Change-Id: Ia742842cf1878c5786f71949013ed8afedd13c39
Issue-ID: OOM-909
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
Readiness check version is not sinchronized in many pods
This causing deployment failures.
Issue-ID: OOM-936
Change-Id: Ieef91df17836adcdf24db536440d0a1624a50591
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
Change-Id: Ic9f0eb567716224893955d9379e9ed9308b9ea79
Issue-ID: OOM-740
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
Issue-ID: OOM-821
Change-Id: I627ac962afe8cd6bf2859a30a0e88f6c9ac89d34
Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com>
|
|
Change-Id: Iec439d1ac774763cfd245ca1f72f1dccd01e764e
Issue-ID: OOM-809
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
with this change we can now do the following:
can deploy umbrella chart with currently working components:
helm install local/onap --name onap --namespace onap-all
helm install local/onap --name onap-2 --namespace onap-all-2 \
--set global.nodePortPrefix=303
- umbrella includes setup chart
can deploy a-la-carte component by component into a single namespace
- Need to deploy a setup chart first. cannot be made a helm dependency
as there will be conflicts if each app chart has the same setup dependency.
helm install local/setup --name onap-setup --namespace onap-apps
helm install local/so --name so1 --namespace onap-apps \
--set global.nodePortPrefix=304
helm list
NAME REVISION STATUS CHART NAMESPACE
onap 1 DEPLOYED onap-2.0.0 onap-all
onap-2 1 DEPLOYED onap-2.0.0 onap-all-2
onap-setup 1 DEPLOYED setup-2.0.0 onap-apps
so1 1 DEPLOYED so-2.0.0 onap-apps
Unfortunately, the config maps all have fixed names, so installing
the same app in the a-la-carte fashion will fail due to a collision.
Not worrying about this as I'm not sure we want to support this.
-made the common and setup charts standalone to remove relative file paths
from requirements.yaml
This will help when there are different levels of subcharts that
need to include common
Issue-ID: OOM-786
Issue-ID: OOM-789
Issue-ID: OOM-788
Change-Id: I20bacae6f0f20e8f3bb1527af1e7e53f187341d5
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
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>
|