Age | Commit message (Collapse) | Author | Files | Lines |
|
Adding elasticsearch deployment artifact to POMBA charts
Change-Id: I5d1d5675ca610315f6dd91caab5920edf3ff9318
Issue-ID: LOG-573
Signed-off-by: Geora Barsky <georab@amdocs.com>
Add pomba kibana chart for POMBA deployment
Adding new kibana deployment artifacts for pomba
Issue-ID: LOG-573
Change-Id: I1137fb9f2930933a5f47c839d110f61b69e761ef
Signed-off-by: Geora Barsky <georab@amdocs.com>
Use elasticsearch dump tool
Use elasticsearch dump tool to import index-patterns
Change-Id: I1137fb9f2930933a5f47c839d110f61b69e761ef
Issue-ID: LOG-573
Signed-off-by: Geora Barsky <georab@amdocs.com>
|
|
PS-3 MK: the sample value for openStackVNFTenantId is being
interpolated as a number because it is all numeric.
Going with the quoting it at the template level.
Changing the value to 12345abcde probably would work too.
Change-Id: I2f81430e56f465543d3701a2d8cd4b562e7e987d
Issue-ID: OOM-1116
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
Change-Id: I8bfbaaad6ab5842cca6feb746e38830a5cd5c1f1
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: SDNC-330
|
|
NBI (North Bound Interface) is one of the new project added for Beijing
release.
Features added
==============
MongoDB common chart
--------------------
Ability to start a mongo container, with a chart consistent with other
common charts (readiness, liveness, persistence, resources, nfs,
service, ...).
Specific configuration:
* name of the db to create if needed
NBI chart
---------
Ability to start a mariadb container, with a chart consistent with other
common charts (readiness, liveness, persistence, resources, nfs,
service, ...).
Specific configuration:
* name of the db to create if needed
* name of the user that has access to the db
* password of the user that has access to the db
* root password of the database
Ability to start a NBI container, with a chart consistent with other
common charts (readiness, liveness, persistence, resources, nfs,
service, ...).
Specific configuration:
* log level
* cloudOwner
* ecompInstanceId
* openStackRegion
* openStackServiceTenantName
* sdc_authorization
* aai_authorization
* so_authorization
ONAP chart
----------
Added a requirement on NBI chart, possibility to enable/disable and
configuration to push to the chart.
Current Status
==============
- [*] adding a common chart for mongodb
- [*] make mongo chart compiling
- [*] testing the mongodb common role
- [*] creating a mariadb chart inside nbi helm
- [*] testing the mariadb chart
- [*] make mariadb chart compiling
- [*] make nbi use these charts
- [*] make nbi chart compiling
- [*] test the whole solution
- [*] create a service for nbi
Change-Id: I8dd3e79768c83b1553a05c892cf418f840931255
Issue-ID: EXTAPI-54
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Issue-ID: SDNC-290
Change-Id: I68776259f5950d07e3b2c76b046d2b8b596bbc34
Signed-off-by: Trevor Tait <rtait@amdocs.com>
|
|
This task also includes renaming of mock project into sniro-emulator
Issue-ID: OOM-741
Change-Id: Ib0352f7ecb10019f940c571de073dc0af7056ee5
Signed-off-by: vaibhav <vaibhav.chopra@amdocs.com>
|
|
Change-Id: I2d1ff878c215becc9856af184eb0b11defd75e1d
Issue-ID: OOM-1064
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
Borislav: Fixed Makefile and renamed charts.
Also cosmetic fixes.
Includes corrections for the service name of MR used by dbc to
be "message-router", which matches the message-router chart
Patchset 2: standardize abbreviation for bus-controller to be "dbc"
Patchset 3: correct references in README to match what is deployed
Patchset 4: blew previous commit. Also added dmaap/Makefile lint step
Change-Id: I36c07c7c1200f8e23ae12bd7357a5626346dcccd
Signed-off-by: Dominic Lunanuova <dgl@research.att.com>
Issue-ID: DMAAP-386
Signed-off-by: Dominic Lunanuova <dgl@research.att.com>
|
|
Thank you for the very detailed Review Boris.
All changes you had asked have been incorported.
Please take a look and let me know.
Few important points.
All components excep API and Music are services
that do not expose any TCP or HTTP ports. All the NodePort
and serices section areas in each of these component's
values.yaml file have been cleaned. Actually, the service
section do not make sense of these components at all.
They use Music as a distributed Q to receive and push their
tasks/changes.
These include a). Controller b). Data c). Solver and 4). Reservation.
This is why you didn't see any service.yaml files for these.
-------------------------------
Made a single configuration based setup.
All HAS components are now configured through
a single configmap and a single set of configuration
files.
All oof-has components share configurations.
Restructured the charts so that theere is
one parent for oof-has from where properties
can be inherited.
Removed other issues like the make was failing.
All PODs are coming up except data - which depends
on AAI certs - team is looking for that side.
Issue-ID: OPTFRA-22
Change-Id: I4bf36a68fc3636c822f33f55da70ace577c64ac0
Signed-off-by: Ikram Ikramullah <ikram@research.att.com>
Signed-off-by: Anaƫl Closson <ac2550@intl.att.com>
Removed Urls not needed
Issue-ID: OPTFRA-22
Change-Id: I270de9cbed5f25dd971f40477fb95385a57fba5c
Signed-off-by: Ikram Ikramullah <ikram@research.att.com>
Removed Music IPs
MK:
PS-14: fixing robot testcase by forking the testcase until it is fixed in robot
adding target port to osdf service. required to map port 8698:8699
Issue-ID: INT-444
Change-Id: I150e3389aece7fae3b0685647af3a787cc9f267d
Signed-off-by: Ikram Ikramullah <ikram@research.att.com>
Signed-off-by: ac2550 <ac2550@intl.att.com>
Signed-off-by: Ikram Ikramullah <ikram@research.att.com>
Signed-off-by: = <=>
Signed-off-by: Ikram Ikramullah <ikram@research.att.com>
Signed-off-by: Ankitkumar Patel <ankit@research.att.com>
Signed-off-by: Thomas Nelson <tn1381@att.com>
Signed-off-by: Ikram Ikramullah <ikram@research.att.com>
Signed-off-by: Ankitkumar Patel <ankit@research.att.com>
Signed-off-by: Thomas Nelson <tn1381@att.com>
Signed-off-by: Ikram Ikramullah <ikram@research.att.com>
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
|
|
Updated installation scripts based on changes to ccsdk.
Updated properties file to support Nitrogen ODL.
Change-Id: Ib714fe0fc4a2adec839dc573700338db4129eeb5
Issue-ID: OOM-1021
Signed-off-by: Aaron Hay <ah415j@att.com>
|
|
DMaaP listener was not trying to connect to the right service name, so
it was failing.
In addition, the pod doesn't wait for the dmaap pod to be up and running
before starting, so I've added that dependency.
Lastly, I removed the config of the DMaaP port from the top level values.yaml
files, as out of the box it's very unlikely this would be changed.
Change-Id: I5a190b39f4f163b020189ac9dd178040f80125cd
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: SDNC-293
|
|
change in common/mysql/templates/pvc.yaml to allow pvc use
when persistence is required
change in common/mysql/templates/storageclass.yaml to be
led by the disableNfsprovisioner variable
change in appc/values to default the disableNfsprovisioner
to false as it is in sdnc
changing the default disableNfsprovisioner to true for both appc and sdnc
changing the stateful set avoid volumeclaimtemplates.
When used in helm, the volumeclaimtemplates is causing pvc to be left
after the helm delete --purge. I guess this is due to the fact the pvc
are not directly created by the helm install by indirectly by kubernetes
Now the tests are working in both cases (nfsprovisioner disabled or not)
The only piece remaining after a helm delete is pv in released state
in case we are using nfsprovisioner. That makes sense again because this
are objects created by the provisioner and not by helm.
removed some leftover
Issue-ID: OOM-787
Change-Id: Ieb1f1c482217aeb1b89be39a437bb891a299db71
Signed-off-by: Jerome Doucerain <jerome.doucerain@bell.ca>
|
|
Change-Id: Ieccbd863e45bb68d76f4f1f066433276c9adf3cd
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: OOM-945
|
|
Change-Id: I26e27cfb3b973bbffd0a94e3ec8411f5218cdf4f
Issue-ID: OOM-804
Signed-off-by: mahendrr <mahendra.raghuwanshi@amdocs.com>
|
|
Change-Id: Ie7064b59032c6cd81ee37466c89a5dee74530939
Issue-ID: OOM-750
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
Issue-ID: OOM-731
Change-Id: I2137b9dbe7c7a320094c13779e8e43dadef964c7
Signed-off-by: pramod <pramod.kumarsharma@amdocs.com>
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
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
|
|
Change-Id: Ic9f0eb567716224893955d9379e9ed9308b9ea79
Issue-ID: OOM-740
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
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>
|
|
Issue-ID: OOM-728
Change-Id: I2e6b298a78e7d10c47ce1d531bf089c928a40284
Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com>
|
|
Issue-ID: OOM-280
Deploy kube2msb along with msb contianers, so the ONAP services can be sync to MSB after MSB is restarted
Change-Id: I408e27c72c4b2169c0babe2562e74d4a645683de
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|
|
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 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>
|