From ebc6907968050189688a0b8ccc0e0c42419a9202 Mon Sep 17 00:00:00 2001 From: osgn422w Date: Tue, 16 Mar 2021 16:27:47 +0100 Subject: Policy/Clamp doc update update the documentation to reflect the merge of clamp into Policy framework Issue-ID: REQ-684 Change-Id: I06391cb6468c15aba58bac18a5c042d05b6c8b9f Signed-off-by: osgn422w --- docs/user-guide.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'docs/user-guide.rst') diff --git a/docs/user-guide.rst b/docs/user-guide.rst index b3c1535b2..5cfcf1abd 100644 --- a/docs/user-guide.rst +++ b/docs/user-guide.rst @@ -1,10 +1,10 @@ .. This work is licensed under a Creative Commons Attribution 4.0 International License. .. http://creativecommons.org/licenses/by/4.0 -.. Copyright (c) 2017-2018 AT&T Intellectual Property. All rights reserved. +.. Copyright (c) 2017-2021 AT&T Intellectual Property. All rights reserved. -Control loop in CLAMP ---------------------- -There are 2 control loop levels in CLAMP: +Control loop in Policy/CLAMP +---------------------------- +There are 2 control loop levels in Policy/CLAMP: - Control loop template: This is created from the DCAE blueprint (designed in the DCAE designer), and distributed by SDC to CLAMP. - Control loop instance: Based on the template, it represents a physical control loop in the platform related to a service and a VNF. @@ -116,8 +116,8 @@ In the *Loop Operations* menu, lists the operations to be perform to the loop. |clamp-loop-operation-menu| -Submitting the Control loop to policy -------------------------------------- +Submitting the Control loop to core policy +------------------------------------------ The SUBMIT operation can be used to send the configuration to policy engine. If everything is successful, the status to the policy will become *SENT*. Clamp should also show proper logs in logs view. -- cgit 1.2.3-korg