aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2019-05-31Remove unsupported vagrant and update READMEjhh4-105/+5
Change-Id: I1f2c9723a3dae88da524ff4ec5b2b5c0aad813c5 Issue-ID: POLICY-1816 Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
2019-05-23Update to releasedPamela Dragosh1-2/+2
Released drools-applications and models. Issue-ID: POLICY-1700 Change-Id: I24b044cfd72a77514e8f07cdd8f61ebee165fc00 Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
2019-05-23Update INFO.yamlPamela Dragosh1-1/+17
Add ram and Jim Issue-ID: POLICY-1775 Change-Id: Ia1ef6afb2ad7b901cf0bff849167120af1fa4105 Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
2019-05-15Upgrade to release drools-appsPamela Dragosh1-1/+1
Point to latest drools-applications release Issue-ID: POLICY-1630 Change-Id: I8732445928530ea6eb70b2465025f713d47f2f6d Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
2019-05-15Update to release policy/modelsPamela Dragosh1-1/+1
Point to release version as the SNAPSHOT will disappear in about 2-3 weeks. Issue-ID: POLICY-1630 Change-Id: If1ffa5703b5647588806538609d72bf927c1d7db Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
2019-05-01Upgrade parent and bump snapshotPamela Dragosh6-7/+8
The version for this wasn't quite correct either. Fixed to ensure follows the 1.4.x as defined in version.properties. Updated to point to policy/parent release version and remove warning for relative path. Issue-ID: POLICY-1700 Change-Id: I6772a272f3f291af5fd6ee9efc3f10b0ac3edfd1 Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
2019-04-29No fetching applications loadjhh4-178/+2
drools-pdp in docker when it sees this configuration files, it will try to execute them. Since the alpine common image has an immutable BUILD_VERSION that does not refer to the actual drools build, it will not find it. Two solutions: (a) update the scripts to look for the newly added BUILD_VERSION_DROOLS to counter the presence of that variable, or (b) remove them altogether since the control loop application being the only one that is used will have the control loop applications image cooked. Change-Id: Ie8adb4b50565601b09e1100578458e3071ee6e54 Issue-ID: POLICY-1712 Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
2019-04-29No dependency.json manipulation in brmsgwjhh1-11/+0
There are multiple VERSIONS that make it to the dependency.json since some libraries are coming from models and others from drools-applications. Change-Id: Ide1764962531e09ed5fc733cd18d22550d53c7da Issue-ID: POLICY-1712 Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
2019-04-26Use policy-pdpd-cl image for droolsjhh4-9/+10
Change-Id: I233d2da28fea73bd594ee25cba8cd5740aa9236a Issue-ID: POLICY-1664 Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
2019-04-17Fix pom.xml parent, add artifact version4.0.0-ONAP1.4.0Dmitry Puzikov1-1/+3
Change-Id: Icd321dcc6f2ed3578e63f9712bf8ab923b9b7861 Issue-ID: INT-996 Signed-off-by: Dmitry Puzikov <dmitry.puzikov@tieto.com>
2019-04-15Fix lost version.properties fileDmitry Puzikov1-0/+13
Lost version.properites file causes build failure. Version set for 1.4.0 Change-Id: I58d6150a08da1432c5eca4f66397d7f51f730ca4 Issue-ID: INT-996 Signed-off-by: Dmitry Puzikov <dmitry.puzikov@tieto.com>
2019-04-02Add licence headers, fix notesDmitry Puzikov6-13/+47
Change-Id: I7664605a55554caad347c13d159908537b7c4fb0 Issue-ID: INT-996 Signed-off-by: Dmitry Puzikov <dmitry.puzikov@tieto.com>
2019-03-27Base and common images for Policy appsDmitry Puzikov9-0/+509
Alpine based base and common images to use across Policy project Change-Id: I01d504b48ee361d1751dfa982e1515705b9e343e Issue-ID: INT-996 Signed-off-by: Dmitry Puzikov <dmitry.puzikov@tieto.com>
2019-03-15Update INFO.yaml fileJessica Wagantall1-2/+25
Update missing information blocks and indentation to pass verify job. Change-Id: I5fe22533c9d493e957fc483aa265d0f26acf79df Issue-ID: CIMAN-134 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
2019-03-07Companion changes to Alpine moveJorge Hernandez2-2/+2
Change-Id: I4b237c91b0c7e24804bc7f28af24e1600e2333f6 Issue-ID: POLICY-1551 Signed-off-by: Jorge Hernandez <jorge.hernandez-herrero@att.com>
2019-03-01New install/env variables for docker improvementsJorge Hernandez1-2/+10
Change-Id: I88c4174b0cef304fec125d92b7633475190701a6 Issue-ID: POLICY-1557 Signed-off-by: Jorge Hernandez <jorge.hernandez-herrero@att.com>
2019-02-28Update INFO.yaml Liam's emailPamela Dragosh1-1/+1
est.tech Issue-ID: POLICY-1556 Change-Id: I9a6f52f436102b0c8c596da265918ca12fa591e5 Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
2019-01-07Consistent naming convention of install variablesJorge Hernandez1-10/+10
Change-Id: I4ff249d4a74ce808d81420be1b79f6752d1d6e53 Issue-ID: POLICY-1367 Signed-off-by: Jorge Hernandez <jorge.hernandez-herrero@att.com>
2018-11-29Add CCVPN policy in push-policies.sh scriptVidyashree Rama1-0/+29
Add CCVPN policy in push-policies.sh script Issue-ID: POLICY-1356 Change-Id: I36d22904750a4c371e5c404022b7b59d58402eb8 Signed-off-by: Vidyashree Rama <vidyashree.rama@huawei.com>
2018-11-13Fix bug in Guard policies for DockerMichael Mokry1-6/+6
Modified push-policies.sh to fix pre-loaded guard policies Change-Id: I8716079d6abb0b1ac2872c55b4450bf69842c163 Issue-ID: POLICY-1257 Signed-off-by: Michael Mokry <michael.mokry@att.com>
2018-11-02Re-added requestParams to vDNS policyJim Hahn1-1/+1
Change-Id: Ie6d4ba979d0608b97a7dfddb41afa33a584fbf1f Issue-ID: POLICY-1240 Signed-off-by: Jim Hahn <jrh3@att.com>
2018-10-31Replaced single quotes with %27Jim Hahn1-1/+1
Change-Id: I66a26da2a7b5779d1391d227379fa3ff820a110b Issue-ID: POLICY-1240 Signed-off-by: Jim Hahn <jrh3@att.com>
2018-11-01Merge "Added config params to scale-out policy"Pamela Dragosh1-1/+1
2018-10-31Added config params to scale-out policyJim Hahn1-1/+1
Removed requestParameters and reverted name. Change-Id: Ife2f6855a1f9977d06a881e9b243226aed99a53d Issue-ID: POLICY-1240 Signed-off-by: Jim Hahn <jrh3@att.com>
2018-10-31Replaced /ecomp/mso with /onap/so in URLJim Hahn1-1/+1
Change-Id: I8bac1c98b46cf11cabec4831358a14fe1cc3d7b7 Issue-ID: POLICY-1238 Signed-off-by: Jim Hahn <jrh3@att.com>
2018-10-25AAF Heat installation configuration3.0.0-ONAPJorge Hernandez1-0/+1
The docker repo (for heat) by default will come with AAF configuration flag set to false. An installer could simply set it to true to enable AAF. The main reason for this default in heat installs is to not deal with routinely failures of CSIT tests (as they will need either an AAF running or divergent installations scripts). OOM installations instead will have AAF enabled by default. Change-Id: I2014877285ea776b057b45cf8875d4da6a6730a9 Issue-ID: POLICY-1216 Signed-off-by: Jorge Hernandez <jorge.hernandez-herrero@att.com>
2018-10-09Change DMaaP hostnames1.3.0Jorge Hernandez3-6/+6
Change-Id: I7efadaf3f8230a8433ea7a6fe8367459581043e5 Issue-ID: POLICY-1194 Signed-off-by: Jorge Hernandez <jh1730@att.com>
2018-10-05ONAP Heat Install support for SDNCJorge Hernandez1-0/+6
Change-Id: I113094a4357ad1e9678f297054f31d4e02cfffe7 Issue-ID: POLICY-1183 Signed-off-by: Jorge Hernandez <jh1730@att.com>
2018-09-28default passwords to aaf default oneJorge Hernandez2-5/+5
Default heat installation credentials to be the same regardless aaf is in use or not. This will allow transparent switching from AAF to non-AAF support without requiring clients (robot, consul, etc ..) reconfiguring themselves regardless of what we are using. Change-Id: I2f3c0cbf93d6369168fb0317ff78a13e35c08c12 Signed-off-by: Jorge Hernandez <jh1730@att.com> Issue-ID: POLICY-1156 Signed-off-by: Jorge Hernandez <jh1730@att.com>
2018-09-24CADI AAF changes for policy/dockerMichael Mokry1-0/+3
Added variables for cadi properties Changed property values based on comments and removed resource property Change-Id: I5d7ea2383e306c251f129625b9e9a671c2704ed5 Issue-ID: POLICY-913 Signed-off-by: Michael Mokry <mm117s@att.com>
2018-09-19aaf related install configurationJorge Hernandez1-2/+7
Change-Id: If5f1344cb0e9468fe8a807bd4dc7cb205d3f1bb1 Signed-off-by: Jorge Hernandez <jh1730@att.com> Issue-ID: POLICY-1043
2018-09-19Preload Guard PoliciesMichael Mokry1-130/+195
Modified push_policies.sh to create and push Guard Min/Max and Frequency Limiter policies I also converted tabs to spaces throughout the file while I was in there Change-Id: Idcf5059988c9f291e6be44a069894fd2b864436f Issue-ID: POLICY-968 Signed-off-by: Michael Mokry <mm117s@att.com>
2018-09-19Add Config and CL policies for OOF PCI use caseSaravanan A1-0/+29
Following config policies to be defined for OOF PCI use case for Casablanca: PCI-Handler MS config policy OOF config policy Control loop policy Change-Id: I0e6e0370a875dbd8eb4857d0c15e4219c252efac Issue-ID: POLICY-1086 Signed-off-by: Saravanan A<saravanan.a75@wipro.com>
2018-09-18Add Config and CL policies for OOF PCI use caseSaravanan A1-0/+68
Following config policies to be defined for OOF PCI use case for Casablanca: PCI-Handler MS config policy OOF config policy Control loop policy Change-Id: I2cd0c2221ee0b950463ab939b6426def14c8b69a Issue-ID: POLICY-1086 Signed-off-by: Saravanan A<saravanan.a75@wipro.com>
2018-09-13Provide pre-loaded SDNC Naming policiesMichael Mokry1-0/+54
Added curl commands to created and push SDNC vFW and vPG Naming policies during installation Change-Id: I01b1254199b96dbea5558a31ba8900d76c655ded Issue-ID: POLICY-983 Signed-off-by: Michael Mokry <mm117s@att.com>
2018-08-29Fix cert issue with push-policies scriptMichael Mokry1-17/+17
This should also fix the issues with the CSIT tests. I made changes to the push-policies.sh script to add option -k and bypass certificate errors Change-Id: I5b8bdc1161bc0bc88122884eedd7e63042d9ba42 Issue-ID: POLICY-781 Signed-off-by: Michael Mokry <mm117s@att.com>
2018-08-22policy/docker changes to support PE httpsMichael Mokry7-27/+27
Made changes to conf files and push-policies.sh to set variables and use https in urls Change-Id: I319e800a33756e771f57a8ef8bd611925fdd9299 Issue-ID: POLICY-781 Signed-off-by: Michael Mokry <mm117s@att.com>
2018-08-16default install passwords for Policy keystoresJorge Hernandez2-0/+2
Change-Id: I5402135e561477522aa23ec0551bcd24dad60120 Issue-ID: POLICY-1057 Signed-off-by: Jorge Hernandez <jh1730@att.com>
2018-05-31match brmsgw.conf dependency with dev branchJorge Hernandez1-1/+1
Change-Id: Ia5ae42f19930e34bac49b556e3217988e613bcb0 Issue-ID: POLICY-877 Signed-off-by: Jorge Hernandez <jh1730@att.com>
2018-05-31minor cosmetic tweaks for 1.2.3Jorge Hernandez3-5/+5
The changes are cosmetics to leave the docker repo a bit more tidy for release. The switch from openecom.org to onap.org is functionally noop .conf files as both domain names are supported. The BRMS_DEPENDENCY_VERSION is noop as it will be properly substituted by the underlying docker-install.sh invocation during docker brmsgw container instantation bringup. Change-Id: I154a1e1560dd7083609080d8f56e47e4d62b99eb Issue-ID: POLICY-877 Signed-off-by: Jorge Hernandez <jh1730@att.com>
2018-05-23Adjust conf files for loggerv1.2.32.0.0-ONAP2.0.0-ONAPJim Hahn2-2/+2
Because this shares the log4j.properties embedded within policy/common, the target for the IntegrityMonitor.log cannot be changed. Thus the PARSERLOGPATH was modified to point to that location. Change-Id: Ib68ddb327aa9ef7520314dad354d52c2f409d42e Issue-ID: POLICY-759 Signed-off-by: Jim Hahn <jrh3@att.com>
2018-05-22Use hard-coded path in conf filesJim Hahn2-4/+4
Replace ${{POLICY_LOGS}} with hard-coded path in conf files, as the former does not get expanded. Change-Id: I7686ba75656086ffccb714289b927cf75f8b3e72 Issue-ID: POLICY-759 Signed-off-by: Jim Hahn <jrh3@att.com>
2018-05-22heat install - update to use onap.orgJorge Hernandez1-4/+4
Cosmetic in heat install as openecom.org still works. Better to use onap.org domain moving forward though. Change-Id: Ic3f843beb7c58326c5d6db1d8cba70c6e43a65db Issue-ID: POLICY-853 Signed-off-by: Jorge Hernandez <jh1730@att.com>
2018-05-15Use preinstall hook in docker image to get CL appJorge Hernandez1-0/+52
Change-Id: Id096c43bb3cb7e88ba1ec2e3ca1a788bd01847a4 Issue-ID: POLICY-797 Signed-off-by: Jorge Hernandez <jh1730@att.com>
2018-05-13allow db non-root access toJorge Hernandez1-1/+1
The databases to which the non-root policy user are granted access are: operationshistory10 (guard) and pooling (pooling feature). Change-Id: Id8653e872a7750fe9e037ad2872b5541241ef4e7 Issue-ID: POLICY-788 Signed-off-by: Jorge Hernandez <jh1730@att.com>
2018-05-09allow non-root user to access migration databaseJorge Hernandez1-1/+1
Change-Id: I890daecb9b24bbc21c989f4e3c5fe9c4d1aa2005 Issue-ID: POLICY-788 Signed-off-by: Jorge Hernandez <jh1730@att.com>
2018-05-09Add pooling topicJim Hahn1-0/+14
Added pooling topic for amsterdam-closed-loop feature. Only used when pooling is enabled. Moved property to feature-specific conf file and renamed the property so it isn't specific to amsterdam-cl. Change-Id: I98ad8ca5bbcf910d204b460cadd15345a1d71370 Issue-ID: POLICY-782 Signed-off-by: Jim Hahn <jrh3@att.com>
2018-05-08default dcae consumer group configurationJorge Hernandez1-0/+1
The idea is that by default all pdp-ds will share the same dcae topic, therefore load-balanced in onsets. Change-Id: Id92906f123c4b8b21f84629bdf0a7fe03dc70aa1 Issue-ID: POLICY-766 Signed-off-by: Jorge Hernandez <jh1730@att.com>
2018-05-07fix PE DB transaction lock timeouts.Jorge Hernandez1-2/+2
I hope this fixes all DB related issues that are being seen by integration teams. The failOver jdbc parameters + perhaps some changes in underlying code and persistence libraries may have been causing the PAP to become useless. A thread dump shows that a significant number of threads were in timed-wait state, waiting on a lock trying to acquire a connection. In SB07, the system became useless in terms wouldn't accept any transaction. These changes to the PE provided jdbc parameters seems to be behaving in the expected way, and the expectation is that fixes the problems (behavior is good in own OOM lab). It is thought that this may perhaps solve POLICY-773, POLICY-775, POLICY-779, and perhaps POLICY-776. Change-Id: Ib2319b68b5a503f61c2cb04998c549b7b97f9f31 Issue-ID: POLICY-777 Signed-off-by: Jorge Hernandez <jh1730@att.com>
2018-05-06upgrade mariadb versionJorge Hernandez2-4/+4
this was an exercise to see if it helps with the pessimistic lock exceptions on PE side. The problem still persists, in any case, the database was outdated, and better to run with a more up to date one. Change-Id: I8e51617fde6c1ac9870d1680ebe81e039a333489 Issue-ID: POLICY-777 Signed-off-by: Jorge Hernandez <jh1730@att.com>