1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
3 .. Copyright (c) 2017-2018 AT&T Intellectual Property. All rights reserved.
8 Version: 3.0.4 - maintenance release
9 ------------------------------------
11 :Release Date: 2019-04-06
20 CLAMP certificates have been renewed to extend their expiry dates
21 - `CLAMP-335 <https://jira.onap.org/browse/CLAMP-335>`_ Update Certificates on Casablanca release.
24 Version: 3.0.3 - maintenance release
25 ------------------------------------
27 :Release Date: 2019-02-06
36 one documentation issue was fixed, this issue does not require a new docker image:
37 - `CLAMP-257 <https://jira.onap.org/browse/CLAMP-257>`_ User Manual for CLAMP : nothing on readthedocs.
42 :Release Date: 2018-11-30
46 The Casablanca release is the third release of the Control Loop Automation Management Platform (CLAMP).
48 The main goal of the Casablanca release was to:
50 - Enhance Platform maturity by improving CLAMP maturity matrix see `Wiki <https://wiki.onap.org/display/DW/Casablanca+Release+Platform+Maturity>`_.
51 - CLAMP Dashboard improvements for the monitoring of active Closed Loops
52 - CLAMP logs alignment on the ONAP platform.
53 - CLAMP is now integrated with AAF for authentication and permissions retrieval (AAF server is pre-loaded by default with the required permissions)
54 - CLAMP improvement for configuring the policies (support of Scale Out use case)
55 - CLAMP main Core/UI have been reworked, removal of security issues reported by Nexus IQ on JAVA/JAVASCRIPT code (Libraries upgrade or removal/replacement when possible)
56 - As a POC, the javascript coverage can now be enabled in SONAR (Disabled for now)
60 - The full list of implemented user stories and epics is available on `CASABLANCA RELEASE <https://jira.onap.org/projects/CLAMP/versions/10408>`_
61 This includes the list of bugs that were fixed during the course of this release.
69 CLAMP code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and actions to be taken in future release.
70 The CLAMP open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=42598587>`_.
73 - `CLAMP project page <https://wiki.onap.org/display/DW/CLAMP+Project>`_
75 - `Passing Badge information for CLAMP <https://bestpractices.coreinfrastructure.org/en/projects/1197>`_
77 - `Project Vulnerability Review Table for CLAMP <https://wiki.onap.org/pages/viewpage.action?pageId=42598587>`_
81 New Docker Containers are available, an ELK stack is also now part of CLAMP deployments.
85 The CLAMP Designer Menu (in CLAMP UI) is deprecated since Beijing, the design time is being onboarded into SDC - DCAE D.
89 CLAMP Dashboard is now implemented, allows to monitor Closed Loops that are running by retrieving CL events on DMAAP.
93 https://wiki.onap.org/display/DW/CLAMP+videos
98 :Release Date: 2018-06-07
102 The Beijing release is the second release of the Control Loop Automation Management Platform (CLAMP).
104 The main goal of the Beijing release was to:
106 - Enhance Platform maturity by improving CLAMP maturity matrix see `Wiki <https://wiki.onap.org/display/DW/Beijing+Release+Platform+Maturity>`_.
107 - Focus CLAMP on Closed loop runtime operations and control - this is reflected by the move of the design part to DCAE-D.
108 - Introduce CLAMP Dashboard for monitoring of active Closed Loops.
109 - CLAMP is integrated with MSB.
110 - CLAMP has integrated SWAGGER.
111 - CLAMP main Core has been reworked for improved flexibility.
115 - The full list of implemented user stories and epics is available on `BEIJING RELEASE <https://jira.onap.org/projects/CLAMP/versions/10314>`_
116 This includes the list of bugs that were fixed during the course of this release.
120 - `CLAMP-69 <https://jira.onap.org/browse/CLAMP-69>`_ Deploy action does not always work.
122 The "Deploy" action does not work directly after submitting it.
126 You have to close the CL and reopen it again. In that case the Deploy action will do something.
130 CLAMP code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The CLAMP open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=25440749>`_.
133 - `CLAMP project page <https://wiki.onap.org/display/DW/CLAMP+Project>`_
135 - `Passing Badge information for CLAMP <https://bestpractices.coreinfrastructure.org/en/projects/1197>`_
137 - `Project Vulnerability Review Table for CLAMP <https://wiki.onap.org/pages/viewpage.action?pageId=25440749>`_
141 New Docker Containers are avaialble, an ELK stack is also now part of CLAMP deployments.
143 **Deprecation Notes**
145 The CLAMP Designer UI is now deprecated and unavailable, the design time is being onboarded into SDC - DCAE D.
149 CLAMP Dashboard is now implemented, allows to monitor Closed Loops that are running by retrieving CL events on DMAAP.
154 :Release Date: 2017-11-16
158 The Amsterdam release is the first release of the Control Loop Automation Management Platform (CLAMP).
160 The main goal of the Amsterdam release was to:
162 - Support the automation of provisionning for the Closed loops of the vFW, vDNW and vCPE through TCA.
163 - Support the automation of provisionning for the Closed loops of VVolte (Holmes)
164 - Demonstrate complete interaction with Policy, DCAE, SDC and Holmes.
168 - The full list of implemented user stories and epics is available on `AMSTERDAM RELEASE <https://jira.onap.org/projects/CLAMP/versions/10313>`_
169 This is technically the first release of CLAMP, previous release was the seed code contribution.
170 As such, the defects fixed in this release were raised during the course of the release.
171 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.
174 - `CLAMP-68 <https://jira.onap.org/browse/CLAMP-68>`_ ResourceVF not always provisioned.
176 In Closed Loop -> Properties CL: When opening the popup window, the first service in the list does not show Resource-VF even though in SDC there is a resource instance in the service.
180 If you have multiple service available (if not create a dummy one on SDC), just click on another one and then click back on the first one in the list. The ResourceVF should be provisioned now.
182 - `CLAMP-69 <https://jira.onap.org/browse/CLAMP-69>`_ Deploy action does not always work.
184 The "Deploy" action does not work directly after submitting it.
188 You have to close the CL and reopen it again. In that case the Deploy action will do something
192 CLAMP is following the CII Best Practices Badge Program, results including security assesment can be found on the
193 `project page <https://bestpractices.coreinfrastructure.org/projects/1197>`_
200 **Deprecation Notes**