blob: 57c899ec97b0b1331ec1af85f1eeaac9e82e05ab [file] [log] [blame]
Rich Bennettc58f8462017-10-24 08:26:42 -04001.. This work is licensed under a Creative Commons Attribution 4.0 International License.
ChrisCba72d202017-11-07 06:44:18 -08002.. http://creativecommons.org/licenses/by/4.0
ChrisC8ec1b912018-03-27 03:12:59 -07003.. Copyright (c) 2017-2018 AT&T Intellectual Property. All rights reserved.
Rich Bennettc58f8462017-10-24 08:26:42 -04004
5Release Notes
6=============
7
sebdet4d1e6b92018-10-23 16:54:02 +02008Version: 3.0.1
9--------------
10
11:Release Date: 2018-10-25
12
13**New Features**
14
15The Casablanca release is the third release of the Control Loop Automation Management Platform (CLAMP).
16
17The main goal of the Casablanca release was to:
18
19 - Enhance Platform maturity by improving CLAMP maturity matrix see `Wiki <https://wiki.onap.org/display/DW/Casablanca+Release+Platform+Maturity>`_.
20 - CLAMP Dashboard improvements for the monitoring of active Closed Loops
21 - CLAMP logs alignment on the ONAP platform.
22 - CLAMP is now integrated with AAF for authentication and permissions retrieval (AAF server is pre-loaded by default with the required permissions)
23 - CLAMP improvement for configuring the policies (support of Scale Out use case)
24 - 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)
25 - As a POC, the javascript coverage can now be enabled in SONAR (Disabled for now)
26
27**Bug Fixes**
28
29 - The full list of implemented user stories and epics is available on `CASABLANCA RELEASE <https://jira.onap.org/projects/CLAMP/versions/10408>`_
30 This includes the list of bugs that were fixed during the course of this release.
31
32**Known Issues**
33
34 - None
35
36**Security Notes**
37
38CLAMP 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.
39The CLAMP open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/display/DW/CLAMP+R3+-+Vulnerability+Threat>`_.
40
41Quick Links:
42 - `CLAMP project page <https://wiki.onap.org/display/DW/CLAMP+Project>`_
43
44 - `Passing Badge information for CLAMP <https://bestpractices.coreinfrastructure.org/en/projects/1197>`_
45
46 - `Project Vulnerability Review Table for CLAMP <https://wiki.onap.org/display/DW/CLAMP+R3+-+Vulnerability+Threat>`_
47
48**Upgrade Notes**
49
50 New Docker Containers are available, an ELK stack is also now part of CLAMP deployments.
51
52**Deprecation Notes**
53
54 The CLAMP Designer Menu (in CLAMP UI) is deprecated since Beijing, the design time is being onboarded into SDC - DCAE D.
55
56**Other**
57
58 CLAMP Dashboard is now implemented, allows to monitor Closed Loops that are running by retrieving CL events on DMAAP.
59
60**How to - Videos**
61
62 https://wiki.onap.org/display/DW/CLAMP+videos
63
Determe, Sebastien (sd378r)64221d32018-05-30 18:16:31 +020064Version: 2.0.2
ChrisC802241a2018-03-26 05:21:05 -070065--------------
66
Gildas Lanilis6b6521b2018-05-30 12:11:25 -070067:Release Date: 2018-06-07
ChrisC802241a2018-03-26 05:21:05 -070068
69**New Features**
70
71The Beijing release is the second release of the Control Loop Automation Management Platform (CLAMP).
72
73The main goal of the Beijing release was to:
74
ChrisC8ec1b912018-03-27 03:12:59 -070075 - Enhance Platform maturity by improving CLAMP maturity matrix see `Wiki <https://wiki.onap.org/display/DW/Beijing+Release+Platform+Maturity>`_.
ChrisC802241a2018-03-26 05:21:05 -070076 - Focus CLAMP on Closed loop runtime operations and control - this is reflected by the move of the design part to DCAE-D.
77 - Introduce CLAMP Dashboard for monitoring of active Closed Loops.
ChrisC8ec1b912018-03-27 03:12:59 -070078 - CLAMP is integrated with MSB.
79 - CLAMP has integrated SWAGGER.
80 - CLAMP main Core has been reworked for improved flexibility.
ChrisC802241a2018-03-26 05:21:05 -070081
82**Bug Fixes**
83
ChrisC8ec1b912018-03-27 03:12:59 -070084 - The full list of implemented user stories and epics is available on `BEIJING RELEASE <https://jira.onap.org/projects/CLAMP/versions/10314>`_
85 This includes the list of bugs that were fixed during the course of this release.
ChrisC802241a2018-03-26 05:21:05 -070086
87**Known Issues**
88
89 - `CLAMP-69 <https://jira.onap.org/browse/CLAMP-69>`_ Deploy action does not always work.
90
91 The "Deploy" action does not work directly after submitting it.
92
93 Workaround:
94
ChrisC8ec1b912018-03-27 03:12:59 -070095 You have to close the CL and reopen it again. In that case the Deploy action will do something.
ChrisC802241a2018-03-26 05:21:05 -070096
Gildas Lanilis6b6521b2018-05-30 12:11:25 -070097**Security Notes**
ChrisC802241a2018-03-26 05:21:05 -070098
Gildas Lanilis6b6521b2018-05-30 12:11:25 -070099CLAMP 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>`_.
ChrisC802241a2018-03-26 05:21:05 -0700100
Gildas Lanilis6b6521b2018-05-30 12:11:25 -0700101Quick Links:
102 - `CLAMP project page <https://wiki.onap.org/display/DW/CLAMP+Project>`_
103
104 - `Passing Badge information for CLAMP <https://bestpractices.coreinfrastructure.org/en/projects/1197>`_
105
106 - `Project Vulnerability Review Table for CLAMP <https://wiki.onap.org/pages/viewpage.action?pageId=25440749>`_
ChrisC802241a2018-03-26 05:21:05 -0700107
108**Upgrade Notes**
109
ChrisC8ec1b912018-03-27 03:12:59 -0700110 New Docker Containers are avaialble, an ELK stack is also now part of CLAMP deployments.
ChrisC802241a2018-03-26 05:21:05 -0700111
112**Deprecation Notes**
113
ChrisC8ec1b912018-03-27 03:12:59 -0700114 The CLAMP Designer UI is now deprecated and unavailable, the design time is being onboarded into SDC - DCAE D.
ChrisC802241a2018-03-26 05:21:05 -0700115
116**Other**
117
ChrisC8ec1b912018-03-27 03:12:59 -0700118 CLAMP Dashboard is now implemented, allows to monitor Closed Loops that are running by retrieving CL events on DMAAP.
ChrisC802241a2018-03-26 05:21:05 -0700119
ChrisCba72d202017-11-07 06:44:18 -0800120Version: 1.1.0
Rich Bennettc58f8462017-10-24 08:26:42 -0400121--------------
122
ChrisCba72d202017-11-07 06:44:18 -0800123:Release Date: 2017-11-16
Rich Bennettc58f8462017-10-24 08:26:42 -0400124
125**New Features**
126
ChrisCba72d202017-11-07 06:44:18 -0800127The Amsterdam release is the first release of the Control Loop Automation Management Platform (CLAMP).
128
129The main goal of the Amsterdam release was to:
130
131 - Support the automation of provisionning for the Closed loops of the vFW, vDNW and vCPE through TCA.
132 - Support the automation of provisionning for the Closed loops of VVolte (Holmes)
133 - Demonstrate complete interaction with Policy, DCAE, SDC and Holmes.
Rich Bennettc58f8462017-10-24 08:26:42 -0400134
135**Bug Fixes**
ChrisCba72d202017-11-07 06:44:18 -0800136
ChrisC8ec1b912018-03-27 03:12:59 -0700137 - The full list of implemented user stories and epics is available on `AMSTERDAM RELEASE <https://jira.onap.org/projects/CLAMP/versions/10313>`_
ChrisCba72d202017-11-07 06:44:18 -0800138 This is technically the first release of CLAMP, previous release was the seed code contribution.
139 As such, the defects fixed in this release were raised during the course of the release.
140 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.
141
Rich Bennettc58f8462017-10-24 08:26:42 -0400142**Known Issues**
ChrisCba72d202017-11-07 06:44:18 -0800143 - `CLAMP-68 <https://jira.onap.org/browse/CLAMP-68>`_ ResourceVF not always provisioned.
144
145 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.
146
147 Workaround:
148
149 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.
ChrisC8ec1b912018-03-27 03:12:59 -0700150
ChrisCba72d202017-11-07 06:44:18 -0800151 - `CLAMP-69 <https://jira.onap.org/browse/CLAMP-69>`_ Deploy action does not always work.
152
153 The "Deploy" action does not work directly after submitting it.
154
155 Workaround:
156
157 You have to close the CL and reopen it again. In that case the Deploy action will do something
158
Rich Bennettc58f8462017-10-24 08:26:42 -0400159
160**Security Issues**
ChrisCba72d202017-11-07 06:44:18 -0800161 CLAMP is following the CII Best Practices Badge Program, results including security assesment can be found on the
162 `project page <https://bestpractices.coreinfrastructure.org/projects/1197>`_
Rich Bennettc58f8462017-10-24 08:26:42 -0400163
164
165**Upgrade Notes**
166
ChrisCba72d202017-11-07 06:44:18 -0800167 N/A
168
Rich Bennettc58f8462017-10-24 08:26:42 -0400169**Deprecation Notes**
170
ChrisCba72d202017-11-07 06:44:18 -0800171 N/A
172
Rich Bennettc58f8462017-10-24 08:26:42 -0400173**Other**
174
ChrisCba72d202017-11-07 06:44:18 -0800175
176
Rich Bennettc58f8462017-10-24 08:26:42 -0400177===========
178
179End of Release Notes