Remove docs directory from policy/clamp

All the documentation from policy-clamp is now moved to policy parent and
the links from the ONAP root documentaiton to CLAMP are now pointing at
the documentation for CLAMP in policy/parent.

This all means that the documentation in policy/clamp can now be removed.

Issue-ID: POLICY-3337
Change-Id: I9bf99b0dc7a8184dc5a972a207e94fad33e507e2
Signed-off-by: liamfallon <liam.fallon@est.tech>

1 files changed, 0 insertions, 48 deletions

diff --git a/docs/architecture.rst b/docs/architecture.rst
deleted file mode 100644
index b65eb1c1d..000000000
--- a/docs/architecture.rst
+++ /dev/null
@@ -1,48 +0,0 @@
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-.. Copyright (c) 2017-2021 AT&T Intellectual Property.  All rights reserved.
-.. _architecture:
-
-Policy/Clamp in ONAP Architecture
----------------------------------
-
-CLAMP platform has been integrated into the Policy framework project, starting as a POC during
-Honolulu release and as a official feature with Istanbul release. So CLAMP must be seen now
-as a function provided by the Policy Framework project.
-
-CLAMP is a function for designing and managing control loops and a UI to manage Policies.
- It is used to visualize a control loop, configure it with specific parameters for a particular network
-service, then deploying and undeploying it.  Once deployed, the user can also
-update the loop with new parameters during runtime, as well as suspending and
-restarting it.
-
-Starting with Istanbul release, CLAMP GUI can also be used to create/read/update/delete/list policies
-outside of a control loop, and therefore CLAMP is also the front-end for Policies management in ONAP.
-
-CLAMP interacts with other systems to deploy and execute the control loop. For
-example, it extracts the control loop blueprint from CSAR distributed by SDC.
-CLAMP also calls the internal Policy framework API to get the Policy Models(Model Driven Control Loop)
-It requests from DCAE the instantiation of microservices.
-to manage the control loop flow. Furthermore, it creates and updates multiple
-policies (for DCAE mS configuration and actual Control Operations) in the Policy Engine
-that define the closed loop flow.
-
-|clamp-flow|
-
-The ONAP CLAMP function abstracts the details of these systems under the concept
-of a control loop model.  The design of a control loop and its management is
-represented by a workflow in which all relevant system interactions take
-place.  This is essential for a self-service model of creating and managing
-control loops, where no low-level user interaction with other components is
-required.
-
-At a higher level, CLAMP is about supporting and managing the broad operational
-life cycle of VNFs/VMs and ultimately ONAP components itself. It will offer the
-ability to design, test, deploy and update control loop automation - both closed
-and open. Automating these functions would represent a significant saving on
-operational costs compared to traditional methods.
-
-|closed-loop|
-
-.. |clamp-flow| image:: images/architecture/distdepl.png
-.. |closed-loop| image:: images/architecture/ONAP-closedloop.png