| jhh | 27ae347 | 2021-03-25 14:08:45 -0500 | [diff] [blame] | 1 | |
| 2 | .. This work is licensed under a Creative Commons Attribution 4.0 International License. |
| 3 | .. http://creativecommons.org/licenses/by/4.0 |
| 4 | |
| 5 | ******************* |
| 6 | Feature: no locking |
| 7 | ******************* |
| 8 | |
| 9 | .. contents:: |
| 10 | :depth: 3 |
| 11 | |
| 12 | The no-locking feature allows applications to use a Lock Manager that always succeeds. It does not deny |
| 13 | acquiring resource locks. |
| 14 | |
| 15 | To utilize the no-locking feature, first stop policy engine, disable other locking features, and then enable it |
| 16 | using the "*features*" command. |
| 17 | |
| 18 | In an official OOM installation, place a script with a .pre.sh suffix: |
| 19 | |
| 20 | .. code-block:: bash |
| 21 | :caption: features.pre.sh |
| 22 | #!/bin/sh |
| 23 | |
| 24 | sh -c "features disable distributed-locking" |
| 25 | sh -c "features enable no-locking" |
| 26 | |
| 27 | |
| 28 | under the directory: |
| 29 | |
| 30 | .. code-block:: bash |
| 31 | oom/kubernetes/policy/components/policy-drools-pdp/resources/configmaps |
| 32 | |
| 33 | |
| 34 | and rebuild the policy charts. |
| 35 | |
| 36 | At container initialization, the distributed-locking will be disabled, and the no-locking feature will be enabled. |
| 37 | |
| 38 | End of Document |