diff options
| author |   liamfallon <liam.fallon@est.tech> | 2022-11-01 13:16:21 +0000 |
|---|---|---|
| committer | Liam Fallon <liam.fallon@est.tech> | 2022-11-01 17:00:48 +0000 |
| commit | 688a2dd3a681c28ac48ad737316c2dc1dff08526 (patch) | |
| tree | 2cec8ad6af476f64fdf13f495788a277ee88644b /docs/installation/oom.rst | |
| parent | b0f136169fcf812b4f030a6d0ffe2817977b313c (diff) | |
Fix doc config files and dead links
Documentation config fixed as instructed.
Configuration files have been copied from examples provided by the
documentation project.
Dead links are fixed as well, they cause build fails now.
Issue-ID: POLICY-4426
Change-Id: Ied5ca5e5a24f7a625e5b2d94c46d0c2347c68ace
Signed-off-by: liamfallon <liam.fallon@est.tech>
Diffstat (limited to 'docs/installation/oom.rst')
| -rw-r--r-- | docs/installation/oom.rst | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/docs/installation/oom.rst b/docs/installation/oom.rst index 621df5b7..30efdbe7 100644 --- a/docs/installation/oom.rst +++ b/docs/installation/oom.rst @@ -54,9 +54,8 @@ From your local copy, edit any of the values.yaml files in the policy tree to ma The policy schema will be installed automatically as part of the database configuration using ``db-migrator``. By default the policy schema is upgraded to the latest version. -For more information on how to change the ``db-migrator`` setup please see: `Using Policy DB Migrator`_. - -.. _Using Policy DB Migrator: ../db-migrator/policy-db-migrator.html +For more information on how to change the ``db-migrator`` setup please see +:ref:`Using Policy DB Migrator <policy-db-migrator-label>`. **Step 2** Build the charts @@ -130,7 +129,7 @@ For security reasons, the ports for the policy containers are configured as Clus kubectl -n onap expose service policy-api --port=7171 --target-port=6969 --name=api-public --type=NodePort Overriding certificate stores -******************************* +***************************** Policy components package default key and trust stores that support https based communication with other AAF-enabled ONAP components. Each store can be overridden at installation. @@ -163,7 +162,7 @@ When the keystore passwords are changed, the corresponding component configurati This procedure is applicable to an installation that requires either AAF or non-AAF derived certificates. The reader is refered to the AAF documentation when new AAF-compliant keystores are desired: -* `AAF automated configuration and Certificates <https://docs.onap.org/projects/onap-aaf-authz/en/latest/sections/configuration/AAF_4.1_config.html#typical-onap-entity-info-in-aaf>`_. +* `AAF automated configuration and Certificates <https://wiki.onap.org/display/DW/Application+Authorization+Framework+%28AAF%29+Documentation>`_. * `AAF Certificate Management for Dummies <https://wiki.onap.org/display/DW/AAF+Certificate+Management+for+Dummies>`_. * `Instructional Videos <https://wiki.onap.org/display/DW/Instructional+Videos>`_. |