summaryrefslogtreecommitdiffstats
path: root/controlloop/common/feature-controlloop-amsterdam/src/main/feature
AgeCommit message (Collapse)AuthorFilesLines
2020-03-12Delete template.demo submodule, amsterdam controllerPeyton Puckett2-132/+0
Issue-ID: POLICY-2421 Change-Id: I0e61e7b3272f5c7babceb41e4e249716af4529cf Signed-off-by: Peyton Puckett <peyton.puckett@att.com>
2019-10-29Update APPC LCM Model referencesDaniel Cruz1-3/+3
Updates to all references of APPC LCM model code based on changes in policy models for APPC LCM. Issue-ID: POLICY-2043 Change-Id: I0102eb27f449578636cfc0bf22124fa863f05724 Signed-off-by: Daniel Cruz <dc443y@att.com>
2019-07-18change json path to delete regex matchingjhh1-2/+2
This is necessary as the explicit "match-all" regular expressions causes events to be accepted in error, even when the json field is not present in the document. Change-Id: Idf4b408850514f49ebe8375d2870e116e793a935 Issue-ID: POLICY-1830 Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
2019-03-04Merge "Add controller logger configurations"Jorge Hernandez1-0/+56
2019-03-01Add controller logger configurationsDaniel Cruz1-0/+56
Logger configurations have been added for each feature that installs a controller. The convention that the controller logging feature looks for in a controller logback config file is "logback-include-.*.xml". Issue-ID: POLICY-1427 Change-Id: Ic37686bf6c1063ba5162fdd494b7465c3a82da01 Signed-off-by: Daniel Cruz <dc443y@att.com>
2019-03-01Replace hard install vars with environment varsJorge Hernandez1-30/+15
Change-Id: Iabff9e820e733a3e9f54018040f87a542a187de3 Issue-ID: POLICY-1543 Signed-off-by: Jorge Hernandez <jorge.hernandez-herrero@att.com>
2019-02-18Change Controller FiltersDaniel Cruz1-5/+5
The controller properties files have been updated to use json-path filters in support of the drools-pdp infrastructure changes. Issue-ID: POLICY-1489 Change-Id: I21a7ff18bc3716bd675a1d740e7acdf971394e92 Signed-off-by: Daniel Cruz <dc443y@att.com>
2018-10-09Add implementation for OOF PCI use caseSaravanan A1-2/+18
Receive DMaaP message from PCI-Handler MS with PCI Config change recommendations through DCAE_CL_OUTPUT topic. Trigger SDN-R (if allowed by policy) by sending DMaaP request through SDNR-CL topic. When the response is received from SDNR through SDNR-CL-RSP topic, just parse and print. Code review comments addressed Added controller changes into amsterdam too. Change-Id: I93e54d3f44b4266092931a5f05b766cc26f2a869 Issue-ID: POLICY-1089 Signed-off-by: Saravanan A<saravanan.a75@wipro.com>
2018-09-11disable http for drools apps using dmaapJorge Hernandez1-6/+6
per security guidelines .. Change-Id: I1db4468f20c3bd22a9e5f27fefcb76b55a3b6d89 Signed-off-by: Jorge Hernandez <jh1730@att.com> Issue-ID: POLICY-1105
2018-07-31https configuration for amsterdam controllerJorge Hernandez1-36/+42
configuration set to false until unblocked by DMAAP-547. Change-Id: I2efdafa8b143725fd73f05ec3d0a6a9ffc3b12c6 Issue-ID: POLICY-941 Signed-off-by: Jorge Hernandez <jh1730@att.com>
2018-05-08allow dcae consumer group configurationv1.2.1Jorge Hernandez1-0/+1
this allows to change the dcase onset processing group behavior across pdp-ds. if installation sets DCAE_CONSUMER_GROUP, all PDP-Ds will share the same consumer group, therefore will have exclussive processing of onsets. Otherwise if installation unsets it (blank), all pdp-d's will process all onsets being placed in dcae topic on dmaap bus Change-Id: I4cc63005402ce66c09617b52dfad9a6094cbcb46 Issue-ID: POLICY-766 Signed-off-by: Jorge Hernandez <jh1730@att.com>
2018-04-03Configure correct classnames for LCM classesJorge Hernandez1-3/+3
Change-Id: I5305e71bb0cc844dd37ff6420cd30012f98c88ed Issue-ID: POLICY-720 Signed-off-by: Jorge Hernandez <jh1730@att.com>
2018-04-02installation enhancementsJorge Hernandez1-0/+68
The following changes aim to have a quicker start of the drools container: 1. For both amsterdam (and the experimental beijing) controllers dependencies are pre-installed, so the loading of 3rd party dependencies are faster. 2. Further enhancements in installation. 3. Make sure that the naming of the generated control loop artifacts have a "control loop" label associated with it, so in the future, if other applications are added (non control loop related) do not conflict and is clear. Change-Id: Iecb84d186fcc34069aa5c4a175a8a4521b38499d Issue-ID: POLICY-534 Signed-off-by: Jorge Hernandez <jh1730@att.com>