From 802241ababb30a19d8c1b364c7697f991a9b9754 Mon Sep 17 00:00:00 2001 From: ChrisC Date: Mon, 26 Mar 2018 05:21:05 -0700 Subject: [PATCH] Update Release Note Add Beijing Release Note entry for the release. Change-Id: I45bb1e2c31978fb767d2984c88afa75ca858b463 Issue-ID: CLAMP-128 Signed-off-by: ChrisC --- docs/release-notes.rst | 55 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) diff --git a/docs/release-notes.rst b/docs/release-notes.rst index e372c846..a5b92804 100644 --- a/docs/release-notes.rst +++ b/docs/release-notes.rst @@ -5,6 +5,61 @@ Release Notes ============= +Version: 2.0.0 +-------------- + +:Release Date: 2018-03-28 + +**New Features** + +The Beijing release is the second release of the Control Loop Automation Management Platform (CLAMP). + +The main goal of the Beijing release was to: + + - Enhance Platform maturity by improving CLAMP maturity matrix see `Wiki `_ + - Focus CLAMP on Closed loop runtime operations and control - this is reflected by the move of the design part to DCAE-D. + - Introduce CLAMP Dashboard for monitoring of active Closed Loops. + - CLAMP is integrated with MSB + - CLAMP has integrated SWAGGER + - CLAMP main Core has been reworked for improved flexibility + +**Bug Fixes** + + - The full list of implemented user stories and epics is available on `JIRA `_ + This is technically the first release of CLAMP, previous release was the seed code contribution. + As such, the defects fixed in this release were raised during the course of the release. + Anything not closed is captured below under Known Issues. If you want to review the defects fixed in the Amsterdam release, refer to Jira link above. + +**Known Issues** + + - `CLAMP-69 `_ Deploy action does not always work. + + The "Deploy" action does not work directly after submitting it. + + Workaround: + + You have to close the CL and reopen it again. In that case the Deploy action will do something + + +**Security Issues** + CLAMP is following the CII Best Practices Badge Program, results including security assesment can be found on the + `project page `_ + + CLAMP Code is formally scanned during build time, the goal of Beijing Release was to ensure that all Critical items are closed + The remaining security issues and their workarounds are captured `here `_ + +**Upgrade Notes** + + New Docker Containers are avaialble, an ELK stack is also now part of CLAMP deployments + +**Deprecation Notes** + + The CLAMP Designer UI is now deprecated and unavailable, the design time is being onboarded into SDC - DCAE D + +**Other** + + CLAMP Dashboard is now implemented, allows to monitor Closed Loops that are running by retrieving CL events on DMAAP + Version: 1.1.0 -------------- -- 2.16.6