Add drools no-locking feature documentation

Issue-ID: POLICY-3142
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: I461da8d2b901c38b9bdb9ef2478c474ca96b6691
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>

1 files changed, 38 insertions, 0 deletions

diff --git a/docs/drools/feature_nolocking.rst b/docs/drools/feature_nolocking.rst
new file mode 100644
index 00000000..5399f8b0
--- /dev/null
+++ b/docs/drools/feature_nolocking.rst
@@ -0,0 +1,38 @@
+
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+*******************
+Feature: no locking
+*******************
+
+.. contents::
+    :depth: 3
+
+The no-locking feature allows applications to use a Lock Manager that always succeeds.  It does not deny
+acquiring resource locks.
+
+To utilize the no-locking feature, first stop policy engine, disable other locking features, and then enable it
+using the "*features*" command.
+
+In an official OOM installation, place a script with a .pre.sh suffix:
+
+    .. code-block:: bash
+       :caption: features.pre.sh
+        #!/bin/sh
+
+        sh -c "features disable distributed-locking"
+        sh -c "features enable no-locking"
+
+
+under the directory:
+
+    .. code-block:: bash
+        oom/kubernetes/policy/components/policy-drools-pdp/resources/configmaps
+
+
+and rebuild the policy charts.
+
+At container initialization, the distributed-locking will be disabled, and the no-locking feature will be enabled.
+
+End of Document