Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue-ID: POLICY-2378
Change-Id: I31d1dabe86f2d7d0466d7e5527de24e4a4b1224e
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Parent released, common and models have fixes.
Issue-ID: POLICY-2486
Change-Id: I9e34b45f23411a4660f015ee6099ad4158eb1c57
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Issue-ID: POLICY-2378
Change-Id: Ie302d4e3f9141004feb7782d5895dda040d7bdfd
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Issue-ID: POLICY-2378
Change-Id: Ie64c246fee536138c179e13d53f1ccfc854c2238
Signed-off-by: Peyton Puckett <peyton.puckett@att.com>
|
|
Issue-ID: POLICY-2378
Change-Id: Ib2ca540fd6b77dbf4dec6e36b8fc75fce8a9d44b
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
2.0.1 is released, bump to next patch.
Also ensure configuration for dependencies is correct.
Issue-ID: POLICY-2378
Change-Id: Ia581392df30614f92d30b52ef4799258991f584b
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
|
|
Issue-ID: POLICY-2330
Signed-off-by: Rashmi Pujar <rashmi.pujar@bell.ca>
Change-Id: Ibb0343ea5446bce4d35905931930fb3de5df0448
|
|
Issue-ID: POLICY-2325
Signed-off-by: Bilal A <bilal@research.att.com>
Change-Id: I6d170616e9e0b9ff0342ef5dba6816207cb73b2e
|
|
Issue-ID: POLICY-1586
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: I122637aec5eb48d6bf2d452167998964f9346211
|
|
Issue-ID: POLICY-2191
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: I8eeb77afe17efefe413bbe6d1b1877c8a884cd6e
|
|
When PDPs register with PAP, they now have to specify their PDP
group. Added the default group to the config file.
Issue-ID: POLICY-2285
Signed-off-by: Jim Hahn <jrh3@att.com>
Change-Id: I1e3928ff17d0d30961a8211b6c7a3c05453558a5
|
|
Issue-ID: POLICY-1945
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: I10885a2eba9a13a454f4ba9922aaf16054b6b015
|
|
Issue-ID: POLICY-2088
Signed-off-by: Rashmi Pujar <rashmi.pujar@bell.ca>
Change-Id: Id06c467923b3df8c7199b349571676958341c2c5
|
|
policy/models: 2.1.1
policy/common: 1.5.1
Change-Id: I703e2fb1c86e84893c8752bee5b8d69ce554baa5
Issue-ID: POLICY-1953
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
|
|
Due to dublin branch.
Also update the configuration for CSIT tests.
Issue-ID: POLICY-1747
Change-Id: Ifb8f89f12b534543a5bded0a6f673c44f857b761
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Released drools-applications and models.
Issue-ID: POLICY-1700
Change-Id: I24b044cfd72a77514e8f07cdd8f61ebee165fc00
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Point to latest drools-applications release
Issue-ID: POLICY-1630
Change-Id: I8732445928530ea6eb70b2465025f713d47f2f6d
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
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>
|
|
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>
|
|
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>
|
|
Change-Id: I233d2da28fea73bd594ee25cba8cd5740aa9236a
Issue-ID: POLICY-1664
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
|
|
Change-Id: I4b237c91b0c7e24804bc7f28af24e1600e2333f6
Issue-ID: POLICY-1551
Signed-off-by: Jorge Hernandez <jorge.hernandez-herrero@att.com>
|
|
Change-Id: I88c4174b0cef304fec125d92b7633475190701a6
Issue-ID: POLICY-1557
Signed-off-by: Jorge Hernandez <jorge.hernandez-herrero@att.com>
|
|
Change-Id: I4ff249d4a74ce808d81420be1b79f6752d1d6e53
Issue-ID: POLICY-1367
Signed-off-by: Jorge Hernandez <jorge.hernandez-herrero@att.com>
|
|
Add CCVPN policy in push-policies.sh script
Issue-ID: POLICY-1356
Change-Id: I36d22904750a4c371e5c404022b7b59d58402eb8
Signed-off-by: Vidyashree Rama <vidyashree.rama@huawei.com>
|
|
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>
|
|
Change-Id: Ie6d4ba979d0608b97a7dfddb41afa33a584fbf1f
Issue-ID: POLICY-1240
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Change-Id: I66a26da2a7b5779d1391d227379fa3ff820a110b
Issue-ID: POLICY-1240
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
|
|
Removed requestParameters and reverted name.
Change-Id: Ife2f6855a1f9977d06a881e9b243226aed99a53d
Issue-ID: POLICY-1240
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Change-Id: I8bac1c98b46cf11cabec4831358a14fe1cc3d7b7
Issue-ID: POLICY-1238
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
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>
|
|
Change-Id: I7efadaf3f8230a8433ea7a6fe8367459581043e5
Issue-ID: POLICY-1194
Signed-off-by: Jorge Hernandez <jh1730@att.com>
|
|
Change-Id: I113094a4357ad1e9678f297054f31d4e02cfffe7
Issue-ID: POLICY-1183
Signed-off-by: Jorge Hernandez <jh1730@att.com>
|
|
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>
|
|
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>
|
|
Change-Id: If5f1344cb0e9468fe8a807bd4dc7cb205d3f1bb1
Signed-off-by: Jorge Hernandez <jh1730@att.com>
Issue-ID: POLICY-1043
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
Change-Id: I5402135e561477522aa23ec0551bcd24dad60120
Issue-ID: POLICY-1057
Signed-off-by: Jorge Hernandez <jh1730@att.com>
|
|
Change-Id: Ia5ae42f19930e34bac49b556e3217988e613bcb0
Issue-ID: POLICY-877
Signed-off-by: Jorge Hernandez <jh1730@att.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|