Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I7a96309d77fd303429f3710d1b919a4f35a52ebc
Issue-ID: OOM-1458
Signed-off-by: root <frank.obrien@amdocs.com>
|
|
Change-Id: I34627212ad2fb3797dd86c1bee1c2883308a3b25
Issue-ID: OOM-1451
Signed-off-by: Ubuntu <frank.obrien@amdocs.com>
|
|
All Chart versions and requirement dependencies have been updated to 3.0 for Casablanca release.
Change-Id: Iea57e5da09ea8a8bac0a415b9a6196151cbea10b
Issue-ID: OOM-1354
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
Change-Id: Ibca20f8ab51cc87458d18b0abf3de9d573895ea9
Issue-ID: CCSDK-366
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
Change-Id: I7aaa10563a9008d4628534159b2064a5f51802ec
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: OOM-1379
|
|
This file contains the added liveliness and readiness timeouts for some
of the components that are stuck in Init state during deployment.
Change-Id: Ia4904b17b2ab64cad9b1511fa21b88b53d1c3a87
Issue-ID: OOM-1327
Signed-off-by: Sudhakar Reddy <Sudhakar.Reddy@amdocs.com>
|
|
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>
|
|
Change-Id: I8e2268ab90bc685e9764daf923cf74f37e0a5477
Issue-ID: OOM-1103
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.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>
|
|
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-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>
|