blob: 79d2e302f4f0ee6e3fa9d5c904e86fc1981efe5c [file] [log] [blame]
Sylvain Desbureauxdd769782020-05-29 11:19:42 +02001.. This work is licensed under a Creative Commons Attribution 4.0 International
2.. License.
3.. http://creativecommons.org/licenses/by/4.0
4.. Copyright 2017 Bell Canada & Amdocs Intellectual Property. All rights
5.. reserved.
6.. _release_notes_amsterdam:
7
8ONAP Operations Manager Release Notes
9=====================================
10
11Version: 1.1.0
12--------------
13
14:Release Date: 2017-11-16
15
16**New Features**
17
18The Amsterdam release is the first release of the ONAP Operations Manager
19(OOM).
20
21The main goal of the Amsterdam release was to:
22
23 - Support Flexible Platform Deployment via Kubernetes of fully
24 containerized ONAP components - on any type of environment.
25 - Support State Management of ONAP platform components.
26 - Support full production ONAP deployment and any variation of component
27 level deployment for development.
28 - Platform Operations Orchestration / Control Loop Actions.
29 - Platform centralized logging with ELK stack.
30
31**Bug Fixes**
32
33 The full list of implemented user stories and epics is available on
34 `JIRA <https://jira.onap.org/secure/RapidBoard.jspa?rapidView=41&view=planning.nodetail&epics=visible>`_
35 This is the first release of OOM, the defects fixed in this release were
36 raised during the course of the release.
37 Anything not closed is captured below under Known Issues. If you want to
38 review the defects fixed in the Amsterdam release, refer to Jira link
39 above.
40
41**Known Issues**
42 - `OOM-6 <https://jira.onap.org/browse/OOM-6>`_ Automated platform deployment on Docker/Kubernetes
43
44 VFC, AAF, MSB minor issues.
45
46 Workaround: Manual configuration changes - however the reference
47 vFirewall use case does not currently require these components.
48
49 - `OOM-10 <https://jira.onap.org/browse/OOM-10>`_ Platform configuration management.
50
51 OOM ONAP Configuration Management - Handling of Secrets.
52
53 Workaround: Automated workaround to be able to pull from protected
54 docker repositories.
55
56
57**Security Issues**
58 N/A
59
60
61**Upgrade Notes**
62
63 N/A
64
65**Deprecation Notes**
66
67 N/A
68
69**Other**
70
71 N/A
72
73End of Release Notes