summaryrefslogtreecommitdiffstats
path: root/controlloop/common/feature-controlloop-amsterdam/src
AgeCommit message (Collapse)AuthorFilesLines
2018-08-14Fix checkstyle issuesPamela Dragosh1-0/+1
Spacing, missing javadoc Issue-ID: POLICY-883 Change-Id: Ice65c6c1baf0bb7c6273411f078bacfe3496b89b Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
2018-08-13Resolve checkstyle formattingPamela Dragosh1-5/+5
This submission is mostly focused on 120 spacing, missing spaces, rearranged imports, newlines before package and a few other items. Will have to submit further reviews to finish this. Issue-ID: POLICY-883 Change-Id: I772a2077ac97a0cb929810d8afadd2f415fae17b Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
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 Hernandez5-0/+222
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>