Age | Commit message (Collapse) | Author | Files | Lines |
|
This is largely a duplication of what will be in
the offical readthedocs documentation. It is put
here now as part of the README to provide immediate
help to those trying to deploy ONAP using an all
Helm deployment mechanism.
The README will later be amended to simply point to
the offical docs once it has been published for Beijing.
Change-Id: I5e3ec279e19617912d28d482e7818c01620d8945
Issue-ID: OOM-827
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
Moved mysql and dgbuilder under common (built first)
to ensure they are built before appc and sdnc charts
that depend on them.
Change-Id: I2fc28f0537b2639bd2b761c6f115544965a228b1
Issue-ID: OOM-830
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
This is a standardization (based on helm community best practices)
of a Helm chart for the Application Controller (appc) in ONAP.
How to deploy the helm chart (outside of the parent onap chart) from
the local oom/kubernetes codebase.
Run local helm repository in the background:
$ nohup helm serve &
In kubernetes directory run:
$ make all
2 ways to install (--set are for testing purposes)
Full onap:
$ helm install onap --name onap --namespace onap --set global.pullPolicy=Never,mysql.replicaCount=2,appc.replicaCount=2
Appc only:
$ helm install setup --name onap-setup --namespace onap-apps
$ helm install appc --name appc --namespace onap-apps
Change-Id: Ib780f979ad25ecafb08110504b5941e980ca8a95
Issue-ID: OOM-733
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
Signed-off-by: ah415j <ah415j@att.com>
|
|
Moved shared templates into common directory.
This "common" location is where upcoming charts
for mariadb-galera, postgress etc. will reside.
Change-Id: Id2e2ffd3369a3e4d6437c2ca4f04a5f1dceb236a
Issue-ID: OOM-816
Signed-off-by: Mike Elliott <mike.elliott@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>
|
|
Executing 'make' provides:
- linting of all charts
- resolution of chart/subchart dependencies
- creation and deployment of Helm packages to a local Helm repo
Prerequisite:
Start up a local repo and register with Helm as 'local'.
Example:
> helm serve
> helm repo add local http://127.0.0.1:8879
Change-Id: Ie08e8fc2593ac7e67b01f93e266953b962adef5d
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
Issue-ID: OOM-265
|