diff options
Diffstat (limited to 'docs/sections/guides/development_guides')
3 files changed, 5 insertions, 5 deletions
diff --git a/docs/sections/guides/development_guides/oom_dev_config_management.rst b/docs/sections/guides/development_guides/oom_dev_config_management.rst index 36a02dc85d..c6f1c4735d 100644 --- a/docs/sections/guides/development_guides/oom_dev_config_management.rst +++ b/docs/sections/guides/development_guides/oom_dev_config_management.rst @@ -441,4 +441,4 @@ SO deployment specification excerpt: - --container-name - so-mariadb env: - ...
\ No newline at end of file + ... diff --git a/docs/sections/guides/development_guides/oom_dev_container_orchestration.rst b/docs/sections/guides/development_guides/oom_dev_container_orchestration.rst index b137bff8b6..ecbaabd7be 100644 --- a/docs/sections/guides/development_guides/oom_dev_container_orchestration.rst +++ b/docs/sections/guides/development_guides/oom_dev_container_orchestration.rst @@ -363,4 +363,4 @@ containers and any state information within it. To avoid a loss of state, a persistent volume should be used to store all data that needs to be persisted over the re-creation of a container. Persistent volumes have been created for the database components of each of the projects and the same technique can be -used for all persistent state information.
\ No newline at end of file +used for all persistent state information. diff --git a/docs/sections/guides/development_guides/oom_dev_helm_chart_info.rst b/docs/sections/guides/development_guides/oom_dev_helm_chart_info.rst index 533f60e29b..0299c9579f 100644 --- a/docs/sections/guides/development_guides/oom_dev_helm_chart_info.rst +++ b/docs/sections/guides/development_guides/oom_dev_helm_chart_info.rst @@ -22,9 +22,9 @@ in a hierarchy as found in the `aai`_ ONAP component. Charts are created as files laid out in a particular directory tree, then they can be packaged into versioned archives to be deployed. There is a public -archive of `Helm Charts`_ on ArtifactHUB that includes many technologies applicable -to ONAP. Some of these charts have been used in ONAP and all of the ONAP charts -have been created following the guidelines provided. +archive of `Helm Charts`_ on ArtifactHUB that includes many technologies +applicable to ONAP. Some of these charts have been used in ONAP and all of the +ONAP charts have been created following the guidelines provided. An example structure of the OOM common helm charts is shown below: |