1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. Copyright (c) 2017-2019 AT&T Intellectual Property. All rights reserved.
Release Notes
=============
Version: 4.0.3
--------------
:Release Date: 2019-05-06
**New Features**
The Dublin release is the fourth release of the Control Loop Automation Management Platform (CLAMP).
The main goal of the Dublin release was to:
- Stabilize Platform maturity by stabilizing CLAMP maturity matrix see `Wiki <https://wiki.onap.org/display/DW/Dublin+Release+Platform+Maturity>`_.
- CLAMP supports of Policy-model based Configuration Policy
- CLAMP supports new Policy Engine direct Rest API (no longer based on jar provided by Policy Engine)
- CLAMP main Core/UI have been reworked, removal of security issues reported by Nexus IQ.
**Bug Fixes**
- The full list of implemented user stories and epics is available on `DUBLIN RELEASE <https://jira.onap.org/projects/CLAMP/versions/10427>`_
This includes the list of bugs that were fixed during the course of this release.
**Known Issues**
- `CLAMP-384 <https://jira.onap.org/browse/CLAMP-384>`_ Loop State in UI is not reflecting the current state
**Security Notes**
*Fixed Security Issues*
- `OJSI-128 <https://jira.onap.org/browse/OJSI-128>`_ In default deployment CLAMP (clamp) exposes HTTP port 30258 outside of cluster.
- `OJSI-147 <https://jira.onap.org/browse/OJSI-147>`_ In default deployment CLAMP (cdash-kibana) exposes HTTP port 30290 outside of cluster.
- `OJSI-152 <https://jira.onap.org/browse/OJSI-152>`_ In default deployment CLAMP (clamp) exposes HTTP port 30295 outside of cluster.
*Known Security Issues*
*Known Vulnerabilities in Used Modules*
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.
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=64003444>`_.
Quick Links:
- `CLAMP project page <https://wiki.onap.org/display/DW/CLAMP+Project>`_
- `Passing Badge information for CLAMP <https://bestpractices.coreinfrastructure.org/en/projects/1197>`_
- `Project Vulnerability Review Table for CLAMP <https://wiki.onap.org/pages/viewpage.action?pageId=64003444>`_
**Upgrade Notes**
New Docker Containers are available.
Version: 3.0.4 - maintenance release
------------------------------------
:Release Date: 2019-04-06
**New Features**
none
**Bug Fixes**
none
**Known Issues**
CLAMP certificates have been renewed to extend their expiry dates
- `CLAMP-335 <https://jira.onap.org/browse/CLAMP-335>`_ Update Certificates on Casablanca release.
Version: 3.0.3 - maintenance release
------------------------------------
:Release Date: 2019-02-06
**New Features**
none
**Bug Fixes**
none
**Known Issues**
one documentation issue was fixed, this issue does not require a new docker image:
- `CLAMP-257 <https://jira.onap.org/browse/CLAMP-257>`_ User Manual for CLAMP : nothing on readthedocs.
Version: 3.0.3
--------------
:Release Date: 2018-11-30
**New Features**
The Casablanca release is the third release of the Control Loop Automation Management Platform (CLAMP).
The main goal of the Casablanca release was to:
- Enhance Platform maturity by improving CLAMP maturity matrix see `Wiki <https://wiki.onap.org/display/DW/Casablanca+Release+Platform+Maturity>`_.
- CLAMP Dashboard improvements for the monitoring of active Closed Loops
- CLAMP logs alignment on the ONAP platform.
- CLAMP is now integrated with AAF for authentication and permissions retrieval (AAF server is pre-loaded by default with the required permissions)
- CLAMP improvement for configuring the policies (support of Scale Out use case)
- 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)
- As a POC, the javascript coverage can now be enabled in SONAR (Disabled for now)
**Bug Fixes**
- The full list of implemented user stories and epics is available on `CASABLANCA RELEASE <https://jira.onap.org/projects/CLAMP/versions/10408>`_
This includes the list of bugs that were fixed during the course of this release.
**Known Issues**
- None
**Security Notes**
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.
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>`_.
Quick Links:
- `CLAMP project page <https://wiki.onap.org/display/DW/CLAMP+Project>`_
- `Passing Badge information for CLAMP <https://bestpractices.coreinfrastructure.org/en/projects/1197>`_
- `Project Vulnerability Review Table for CLAMP <https://wiki.onap.org/pages/viewpage.action?pageId=42598587>`_
**Upgrade Notes**
New Docker Containers are available, an ELK stack is also now part of CLAMP deployments.
**Deprecation Notes**
The CLAMP Designer Menu (in CLAMP UI) is deprecated since Beijing, 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.
**How to - Videos**
https://wiki.onap.org/display/DW/CLAMP+videos
Version: 2.0.2
--------------
:Release Date: 2018-06-07
**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 <https://wiki.onap.org/display/DW/Beijing+Release+Platform+Maturity>`_.
- 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 `BEIJING RELEASE <https://jira.onap.org/projects/CLAMP/versions/10314>`_
This includes the list of bugs that were fixed during the course of this release.
**Known Issues**
- `CLAMP-69 <https://jira.onap.org/browse/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 Notes**
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>`_.
Quick Links:
- `CLAMP project page <https://wiki.onap.org/display/DW/CLAMP+Project>`_
- `Passing Badge information for CLAMP <https://bestpractices.coreinfrastructure.org/en/projects/1197>`_
- `Project Vulnerability Review Table for CLAMP <https://wiki.onap.org/pages/viewpage.action?pageId=25440749>`_
**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
--------------
:Release Date: 2017-11-16
**New Features**
The Amsterdam release is the first release of the Control Loop Automation Management Platform (CLAMP).
The main goal of the Amsterdam release was to:
- Support the automation of provisionning for the Closed loops of the vFW, vDNW and vCPE through TCA.
- Support the automation of provisionning for the Closed loops of VVolte (Holmes)
- Demonstrate complete interaction with Policy, DCAE, SDC and Holmes.
**Bug Fixes**
- The full list of implemented user stories and epics is available on `AMSTERDAM RELEASE <https://jira.onap.org/projects/CLAMP/versions/10313>`_
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-68 <https://jira.onap.org/browse/CLAMP-68>`_ ResourceVF not always provisioned.
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.
Workaround:
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.
- `CLAMP-69 <https://jira.onap.org/browse/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 <https://bestpractices.coreinfrastructure.org/projects/1197>`_
**Upgrade Notes**
N/A
**Deprecation Notes**
N/A
**Other**
===========
End of Release Notes
|
