Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I9b162cd02aa472e16e146518e1294f57de1e306b
Issue-ID: POLICY-959
Signed-off-by: Jorge Hernandez <jh1730@att.com>
|
|
Final Beijing artifact images
Issue-ID: POLICY-844
Change-Id: I7d86c69d23a3c285fc93fa604913e2595e86f00c
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Issue-ID: POLICY-798
Change-Id: If35ad61649daa347118e02de383b6778c4b4472c
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Change-Id: I2d1ff878c215becc9856af184eb0b11defd75e1d
Issue-ID: OOM-1064
Signed-off-by: BorislavG <Borislav.Glozman@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>
|
|
paplp_1 process is unused and causes intermittent bad
behavior when issuing healthchecks. Since it provides
no apparent benefit integrity monitor usage has been
disabled.
preloading policies apis are executed when the PAP come up.
The PDP-Xs take longer to come up, therefore the
push-policies script causes bad interactions. This operation
has to be triggered after all the PDP-Xs are up and properly
running, which is difficult to predict. Therefore, it is moved
to a manual step execution. In the future, we could think of'how
perhaps execute autonomously by some other means. It does not
currently work as is, so it is disabled, at least temporarily,
there were a couple problems with pap.conf, first the pdps hostname
need to be explicitly provided, as PAP keeps a white list of pdp hosts
that can connect to it and be served policies. Another limitation
is the format, note the change to ";" to separate pdps, instead of ",".
Further the automatic configuration sequence is only made for 1 PDP-X,
does not work well when multiple PDP-Xs are provided, so for the first
PDP-X, the credentials need to be explicitly added, otherwise, it
denies access to PDP-Xs.
Change-Id: I5d4a9a39822c036db26e97edb594ecaaa27f80d8
Issue-ID: POLICY-768
Signed-off-by: Jorge Hernandez <jh1730@att.com>
|
|
Issue-ID: OOM-906
Change-Id: Ic65127d3981cb0a696c784392cab59fbf06b1e66
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>
|
|
We have released artifacts and want to test with our
STAGING docker image.
Change-Id: I7885d433dc6c4c9499e90e4a1e7af6cb9e84889d
Issue-ID: POLICY-708
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
removing cli package change from policy patch
Change-Id: I673cfb90f76df877bd9e69f9a185ae7c77ee4b9b
Issue-ID: OOM-844
Signed-off-by: mayankg2703 <mayank.gupta@amdocs.com>
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
Change-Id: Iabdb2bba14b5095c08ff2920aec97a213e0acb30
Issue-ID: OOM-745
Signed-off-by: mayankg2703 <mayank.gupta@amdocs.com>
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
Signed-off-by: Mandeep Khinda <mandeep.khinda@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>
|
|
changes can be seen in reviews: 31743 and 31721
Issue-ID: OOM-514
Change-Id: I001362b65b03137d996e93b1ace64438bcbf2d9c
Signed-off-by: kerenj <keren.joseph@amdocs.com>
|
|
Issue-ID: OOM-689
Change-Id: Iff389af637dec0b85e568dd9b4cfa641f11eb3fc
Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com>
|
|
- remove useless init-check in deployment to match requirement
from policy team: https://gerrit.onap.org/r/gitweb?p=policy/docker.git;a=blob;f=docker-compose.yml;h=96fd5073e9d51908dabd04643aa96b42820ac681;hb=HEAD
- add missing drools port (9696)
- update configuration files to reflect latest
Change-Id: I3399c21a3357b649fdc078a0bd4ba4af1f751a9b
Issue-ID: OOM-490
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
Change-Id: Iac46cbae69404d17e1f4e59f85ed18fc7ecd01dd
Issue-ID: OOM-432
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
(cherry picked from commit f033f949c49cc195be1f3a6bdf79759f7e0983ca)
|
|
Deployment of: filebeat containar for each relevant component
+ chown of log dir to root - prevents filebeat complaining about filebeat file
+ ecomp web app renamed onap - fixed dep-pap.yaml
+ fixed multiple volumeMounts in vid-server
Change-Id: I74f8f2abd5feeba1d37b044d2a023674fd41c994
Issue-ID:OOM-110
Signed-off-by: yuryn <Yury.Novitsky@Amdocs.com>
|
|
Pods aren't starting properly. Let's not take any risk, so reverting.
3m 18s 4 kubelet, kubernetes-5 spec.containers{vid-server} Normal Killing Killing container with id docker://vid-server:FailedPostStartHook
This reverts commit 4ca69ea2b6a2aaaf0974953a3c3dec7694fdfcb0.
Deployment of: filebeat containar for each relevant component Issue-ID:OOM-110
Change-Id: I7953ac3b0e2a4ecbdd1a7d2a48cb9a1964bf08ab
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
Deployment of: filebeat containar for each relevant component
Issue-ID:OOM-110
Change-Id: I3605a975ee9dbe3e34b8fa6b17fef52e9d29b975
Signed-off-by: Itay Hassid <itay.hassid@amdocs.com>
|
|
was the cause of the robot failure for policy in oom
Issue-ID: OOM-297
Change-Id: Iabb24cc7a007ef852cde3ebe2cbb9226bb4153b3
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
Signed-off-by: Ahmed Alabulrahman <ahmed.alabdulrahman@amdocs.com>
|
|
|
|
- up verion containers to use 1.1
- pap and brmsgw report it is waiting for pap 9091 port to be open but pdp and pypdp reports pap 9091 port is open
- removed push-policies.sh from 1.1 due to comment in CR
- removed pypdp container from 1.1 due to comment in CR
- removed pypdp.conf from 1.1 due to comment in CR
- removed ip_addr.txt from 1.1 due to comment in CR
Change-Id: Ibb685ec603a59dba56aa9673044ae1923d993191
Issue-Id: OOM-249
Signed-off-by: Eric Au <kachun.au@amdocs.com>
|
|
parameterization of node ports, and create/delete update to fix multi ONAP instances creation(in diff NS).
Issue-ID: OOM-52
Change-Id: Iaa3f5bc43f70b95cdc349389e25ef8b804a7a329
Signed-off-by: kerenj <keren.joseph@amdocs.com>
|
|
-removed the full namespace from each template. better lets us reuse
variables.
-made secret end up in a configurable namespace
-fixed some bugs where secrets were missing
-updated createAll and delete to make use of namespace prefix
removing the need for seds to replace the word onap.
*** all containers at this point come up in my env. except for
aai model loader which is failing cause its still at 1.0
and its trying to talk to a 1.1 sdc and it doesnt auth properly. ***
Issue-ID:OOM-215
Change-Id: I15815a01469786a391e272fde4bdaa53ff48091c
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
changed policy k8s deployment to support helm parameterization. updated images to 1.1
Issue-ID: OOM-52
Change-Id: I4eb0626c7c00ace2c266d6ddbb1313f3b654d69e
Signed-off-by: kerenj <keren.joseph@amdocs.com>
|