aboutsummaryrefslogtreecommitdiffstats
path: root/controlloop/templates/archetype-cl-beijing/src
AgeCommit message (Collapse)AuthorFilesLines
2018-04-25Fix NullPointException in SO and VFC.RESPONSEJim Hahn1-3/+3
In the rules, the $manager was missing the condition to match the request id of the manager with the request id of the event. As a result, the completed operation was being applied to an unrelated manager. Change-Id: Icb63c0f151788e7f96450e26853270a7368dfcd8 Issue-ID: POLICY-763 Signed-off-by: Jim Hahn <jrh3@att.com>
2018-04-16Add missing license headersPamela Dragosh4-0/+52
I removed a couple of empty README and added licenses. Issue-ID: POLICY-741 Change-Id: I10aad3536d02b738a1dc606f7311de6b3a2777cd Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
2018-04-02installation enhancementsJorge Hernandez1-2/+2
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>
2018-03-27Removed checkstyle warningsmmis3-71/+71
Removed checkstyle warnings from: policy/drools-applications/controlloop/common/model-impl/appc policy/drools-applications/controlloop/common/model-impl/appclcm policy/drools-applications/controlloop/common/model-impl/events including changes to template files due to renamed methods Issue-ID: POLICY-705 Change-Id: Ieb93baf43268aa608f204eef1a610354f2adec32 Signed-off-by: mmis <michael.morris@ericsson.com>
2018-03-26Create Drools Scripts for BeijingDaniel Cruz17-28/+83
The create-cl-beijing script will now allow the user to create a rules jar that does not need to be expanded and also generate test files that can be used to insert facts for all the supported beijing use cases. The yaml for each policy is provisioned by the user in case custom yaml is desired. In addition to this, a new script is included that will extract the needed data from the controller properties file to insert facts for all the supported use cases. This script can be used to insert ControlLoopParams facts after the create-cl-beijing script is used to generate the rules artifact. No provisioning necessary other than specifying where the controller properties file is located. Issue-ID: POLICY-692 Change-Id: I42f0a08fba133ca36fb1be588a720e4f9598d79f Signed-off-by: Daniel Cruz <dc443y@att.com>
2018-03-26Removed checkstyle warningsmmis1-2/+1
Removed checkstyle warnings from policy/drools-applications/controlloop/common/model-impl/aai including renaming classes: AAI* -> Aai* PNF* -> Pnf* and renaming some methods in those classes Issue-ID: POLICY-705 Change-Id: I2d59a668728aa58a2c9fbe78c44e924e6cfb4531 Signed-off-by: mmis <michael.morris@ericsson.com>
2018-03-23Create archetype for Beijing ReleaseDaniel Cruz20-0/+1898
This new archetype is a proof of concept for removing template expansion from the BRMSGW. The idea is to have a ueb or dmaap topic that the BRMSGW uses to send params json and then the pdp-d will deserialize it into a ControlLoopParams object. The rules engine will then insert that fact in to the working memory which will be used for rules matching between onset events and corresponding policies. Issue-ID: POLICY-692 Change-Id: I4237221c2216dab16160e79a8f2fdcab6571e1eb Signed-off-by: Daniel Cruz <dc443y@att.com>