Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Issue-ID: POLICY-4295
Change-Id: I50d0cf45c4b5bf0a30aa522a97e902775c982602
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-4211
Change-Id: I03def43ec2f027f276674af00d749018a951a05f
Signed-off-by: pdragosh <pd1248@att.com>
|
|
More details can be found here:
https://wiki.onap.org/display/DW/JSON+Schema+support+in+APEX-PDP
A separate review will be raised as part of POLICY-4292 with a reference
example on how to use the JSON Schema.
Change-Id: I903d48969c6c5a24c63b8465b2412ed0b75b9351
Issue-ID: POLICY-4291
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
(cherry picked from commit c354fba3fb87ebe21a7fbb2a15268ccc9d033fbd)
|
|
The issue was observed when APEX fails to consume events from
a Kafka topic when message compression is used specifically snappy.
APEX KafkaConsumer uses snappy-java library (transitive
dependency from kafka-clients) to consume events with snappy
compression. The snappy-java jar packages the native
library (built against glibc) which can be overwritten
to use alpine compatible native library (built using musl).
This means we will need to install the java-snappy-package in apex-pdp
which is also added to the commit as an option.
Alternatively, in later version of snappy-java dependency (1.1.8)
there is an option to use Java implementation instead of native
library as per:
https://github.com/xerial/snappy-java#using-pure-java-snappy-implementation.
This is a cleaner solution to fix the issue.
Issue-ID: POLICY-4310
Signed-off-by: Rashmi Pujar <rashmi.pujar1@bell.ca>
Change-Id: Ic92b1d429ca3ca0cd1cd7070cd8d102df58b1420
|
|
updated policy models references
*** This commit is generated by a PF release script ***
Issue-ID: POLICY-4233
Signed-off-by: liamfallon <liam.fallon@est.tech>
Change-Id: I51c7d75c98643cf582c9723f2f1c0d75714890ea
|
|
apex-pdp was using a very old version of commons-codec. This change
enables it to use the version of commons-codec managed from policy
parent.
Issue-ID: POLICY-3590
Change-Id: Ic29e46b61107719df5aaad00ee923de056fe7bac
Signed-off-by: liamfallon <liam.fallon@est.tech>
(cherry picked from commit a45cf053402a862dbbb1b17cb4a1f974b1f53edc)
|
|
Issue-ID: POLICY-3329
Change-Id: Iae6b3d356483398740da602d950879cf21d28a34
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-3329
Change-Id: Ibf33e52ba0583c1e21ffd0dc37c6c777c8adb8b5
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-3329
Change-Id: I1752a2cd0270f7eecfe5e8da8a395c82bd54c8c2
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-3329
Change-Id: I6866b9bef2f3dbf712780b7d1161126f716521c5
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
When multiple policies are expecting event on the same topic/endpoint,
a lot of event parsing failure log messages are generated
unnecessarily. With this change, only a 1 line message will
be printed if an event cannot be parsed, and the detailed messages
will be available at debug level.
Change-Id: If1e7460ef5ed86fd470396f1e2ed8cc3c8af70c4
Issue-ID: POLICY-3499
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
(cherry picked from commit 1036206455218a4722079b749e628ca96825418d)
|
|
Issue-ID: POLICY-3507
Change-Id: Ie30a1b289fea24b641495148f371e16b1ea06690
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-3329
Change-Id: I86c81ddb4ba8e5961690c451e1dd5185ecf20d3b
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-3329
Change-Id: I0735113a8b0731850bbdd57a9b24680a8daa4b55
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-3329
Change-Id: I05879dc7f9aabcdcb8fae1f9888d6be856435137
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-3329
Change-Id: I18687d4e36a47372ddafe29b3294f9d692f1e0cb
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Similar to '.' (_DoT_) and '-' (_Dash_), the ':' (_ColoN_) character
can now be used in Apex Event Field names specified using Avro Schema
Change-Id: I320058441a1a1a544b9f1619e45c96e71e5aa9e3
Signed-off-by: JohnKeeney <john.keeney@est.tech>
Issue-ID: POLICY-3301
Signed-off-by: JohnKeeney <john.keeney@est.tech>
(cherry picked from commit fe40844bba4a94e26efc0f1c57d62c97e35bfc79)
|
|
The csit test files for all repos have been consolidated in policy/docker to maintain them at single place and allow us to trigger verify jobs in gerrit reviews.
Issue-ID: POLICY-3257
Change-Id: I26d281b75d91e7bf1250e97b22d0e7a303815ed6
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
(cherry picked from commit c70c2179f1555e356794145956cbe32a3407e622)
|
|
Adding testcases to validate policy status and pdp statistics api's.
Issue-ID: POLICY-3257
Change-Id: I730451c4abb19bab6ddf10cba58f63ab5ca3a11a
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
(cherry picked from commit 27d086bfa7a72f761204ad7a76068687f6f36f89)
|
|
context handling" into honolulu
|
|
into honolulu
|
|
Change-Id: I11668e9222dd9c61cc3096fa5c754c8702a781bf
Issue-ID: POLICY-3227
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
(cherry picked from commit 7bcbd221e350e45db5be0c4f1ceb2e4e1a418f63)
|
|
The Kafka plugin in APEX-PDP already has a field "kafkaProperties" that
can take in any properties required for the Kafka client. This is apt to
store the SSL related properties as they could change based on the
server implementation.
To make the communication possible, the only change required in APEX is
to allow a property to have an empty value.
For e.g., to disable the server host name verification, ssl.endpoint.identification.algorithm must to be explicitly set to an empty string on the client.
Change-Id: If3adaeaf11e5fbbd2aff582b5d4ba7824017ea8a
Issue-ID: POLICY-3194
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
(cherry picked from commit bd21c78ed6953de4e8f9fd43311fd22bee7a5472)
|
|
The stackoverflow issue is happening only in standalone mode when
RestManager class is called from APEX Javascript logic to post a
JSON body, that too 6-7 out of 10 times.
To identify the exact root cause may need more investigation,
but changing the base image from policy-jre-alpine to policy-jdk-alpine
seems to have fixed the issue during local testing.
(Issue didn't happen 10 out of 10 times)
Change-Id: Ibe718294ff9ab04c70349b3bc52c3c66619f2093
Issue-ID: POLICY-3066
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
(cherry picked from commit f19e437f71b82507e406e96b99b56bb9fbb02b56)
|
|
- Update performance test file
- Update stability test file
Issue-ID: POLICY-3109
Signed-off-by: arkadiusz.adamski <aadamski@est.tech>
Change-Id: Ibcab9cd012ed9ea50cb389f45ae7d8149b850a2d
(cherry picked from commit 4daab4def85bf5de00fb3d4cd01ebb38b61760be)
|
|
Change-Id: I2fbf0303805b4c5feead522ad78fd4ef518659af
Issue-ID: POLICY-3173
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
(cherry picked from commit ae01c8d07c3b62dd9b06958a62702816e2f7bfc1)
|
|
Issue-ID: POLICY-3093
Signed-off-by: arkadiusz.adamski <aadamski@est.tech>
Change-Id: If9600785d46bed5596847991690fe1631b97bbf3
(cherry picked from commit 31a94576b1a60be11120deb202475850b8f83d3d)
|
|
Overriding to default entry point (/bin/sh) in apex-pdp docker file to support stand alone installations of docker image.
Issue-ID: POLICY-3062
Change-Id: I100674cedf78f7221128bc87dd562835f297e0dd
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
(cherry picked from commit 4d967d61cfb83802b5426d5fd818bcecf144d6e1)
|
|
Issue-ID: POLICY-3150
Change-Id: I563f3f4f2d0d3355b6f683db5904bd2d339f6623
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-3150
Change-Id: Ic146feb53bfe042f2ba213a01279b8878f4f37c2
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-3150
Change-Id: I27c09b2cc644937fc7812ee0bbbb6cf9b9784a78
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-3150
Change-Id: I92dd8dd234820daa78de25c85276bb079282811c
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Deploying invalid APEX policies with duplicate concepts resulting in
corrupting all the policies in memory. This is fixed here.
This entire functionality handling multiple policies will be
revisited as part of https://jira.onap.org/browse/POLICY-3018
Change-Id: I751102d5dddcb92cdcede8222855e2f467bb724d
Issue-ID: POLICY-3141
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
(cherry picked from commit e3f1349915f425c2f0c09688a2cc6d8d246f4110)
|
|
Parallel event execution in APEX was resulting in incorrect dynamic REST url. This issue is fixed in this review.
Change-Id: Id8a28c001a7fd7915df1f5909109bb369667ab40
Issue-ID: POLICY-3019
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
(cherry picked from commit 369a94a9fd626b35d52c2e7ee5f19e6ff6e1b9d8)
|
|
Issue-ID: POLICY-3139
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: Ia67cb1486a5625385a710c5f6c2b4325ca108820
|
|
Issue-ID: POLICY-3105
Change-Id: I49d5c47b029d95664409f785dc3ed2e1229e9ed9
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Change-Id: I291f968367b1f864bb417a72fd0bdb22a07ba0f7
Issue-ID: POLICY-3127
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
Change-Id: I9b5ee20c4760d4f9adcc28c708af62922d6952fa
Issue-ID: POLICY-3127
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
Change-Id: Ib32e0a9dc3d3b9a27f712a02c0317bf7640bc12d
Issue-ID: POLICY-3127
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
Change-Id: I142f196ddcd71048b6812af2d6af014ca42aa5a9
Issue-ID: POLICY-3127
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
Issue-ID: POLICY-3028
Change-Id: Icf1319122ed19a0ba36b148bab7d77be626ba20e
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Change-Id: I761ded255a97128f858d3a7ce95f2479b6208a4e
Issue-ID: POLICY-3088
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
Issue-ID: POLICY-3088
Change-Id: Id5754dac1e8bab68cdb280800750ad98f14c76b1
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
|
|
Issue-ID: POLICY-3088
Change-Id: Ifa746c534623e43f883f9101c4beb0f34dffbaac
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
This review should fix the intermittent test failures in
TestExecutionPropertyRest class in APEX.
Change-Id: I1871a3ac1a40985ad44bbd1433c54930793c7b3c
Issue-ID: POLICY-3096
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
Change-Id: I17e2e093421733fc94a3de8f5946b867b3b73ba9
Issue-ID: POLICY-3088
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
Issue-ID: POLICY-3069
Change-Id: Ib30782485652ec693d2dbea79514183c7cfbb0c4
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
|