[docs] Remove scenarios

For Jerma, a documentation restructure was proposed [1].
THis change removes reference to scenarios in Barometer.

[1] https://wiki.opnfv.org/display/meetings/OPNFV+TSC+Meeting+2020-10-13?preview=/63111416/63111451/OPNFV-docstructure.pdf
Change-Id: Id55e55c3a4ea824c20fcadcfc4716ff8d23cc68f

Change-Id: I135226f7ecc72ee086effede68f92ade0c85d0a2
Signed-off-by: Emma Foley <efoley@redhat.com>

1 files changed, 0 insertions, 61 deletions

diff --git a/docs/release/scenarios/os-nosdn-bar-noha/scenario.description.rst b/docs/release/scenarios/os-nosdn-bar-noha/scenario.description.rst
deleted file mode 100644
index d6a1184a..00000000
--- a/docs/release/scenarios/os-nosdn-bar-noha/scenario.description.rst
+++ /dev/null
@@ -1,61 +0,0 @@
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-.. (c) <optionally add copywriters name>
-
-=================================================
-OPNFV os-nosdn-bar-noha overview and description
-=================================================
-
-This document provides details of the scenario for Euphrates release of Barometer.
-
-.. contents::
-   :depth: 3
-   :local:
-
-Introduction
----------------
-.. In this section explain the purpose of the scenario and the types of
-.. capabilities provided
-
-This scenario has the features from the Barometer project. Collectd (a telemetry agent) is installed
-on compute nodes so that their statistics, events and alarming services can be relayed to Gnoochi and Aodh.
-These are the first steps in paving the way for Platform (NFVI) Monitoring in OPNFV.
-
-Scenario components and composition
--------------------------------------
-.. In this section describe the unique components that make up the scenario,
-.. what each component provides and why it has been included in order
-.. to communicate to the user the capabilities available in this scenario.
-
-This scenario deploys the High Availability OPNFV Cloud based on the
-configurations provided in ``os-nosdn-bar-noha.yaml``.
-This yaml file contains configurations and is passed as an
-argument to ``overcloud-deploy-function.sh`` script.
-This scenario deploys multiple nodes: 1 Controller, 2 Computes.
-
-Collectd is installed on compute nodes and Openstack services runs on the controller node.
-
-os-nosdn-bar-noha scenario is successful when all the nodes are accessible, up and running.
-Also, verify if plugins/services are communicating with Gnocchi and Aodh on the controller nodes.
-
-Scenario usage overview
-----------------------------
-.. Provide a brief overview on how to use the scenario and the features available to the
-.. user.  This should be an "introduction" to the userguide document, and explicitly link to it,
-.. where the specifics of the features are covered including examples and API's
-
-After installation, plugins will be able to read/write the stats on/from the controller node.
-A detailed list of supported plugins along with their sample configuration can be found in the userguide.
-
-Limitations, Issues and Workarounds
----------------------------------------
-.. Explain scenario limitations here, this should be at a design level rather than discussing
-.. faults or bugs.  If the system design only provide some expected functionality then provide
-.. some insight at this point.
-
-None.
-
-References
------------------
-
-