summaryrefslogtreecommitdiffstats
path: root/docs/release-notes-amsterdam.rst
blob: 79d2e302f4f0ee6e3fa9d5c904e86fc1981efe5c (plain)
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
.. This work is licensed under a Creative Commons Attribution 4.0 International
.. License.
.. http://creativecommons.org/licenses/by/4.0
.. Copyright 2017 Bell Canada & Amdocs Intellectual Property.  All rights
.. reserved.
.. _release_notes_amsterdam:

ONAP Operations Manager Release Notes
=====================================

Version: 1.1.0
--------------

:Release Date: 2017-11-16

**New Features**

The Amsterdam release is the first release of the ONAP Operations Manager
(OOM).

The main goal of the Amsterdam release was to:

    - Support Flexible Platform Deployment via Kubernetes of fully
      containerized ONAP components - on any type of environment.
    - Support State Management of ONAP platform components.
    - Support full production ONAP deployment and any variation of component
      level deployment for development.
    - Platform Operations Orchestration / Control Loop Actions.
    - Platform centralized logging with ELK stack.

**Bug Fixes**

    The full list of implemented user stories and epics is available on
    `JIRA <https://jira.onap.org/secure/RapidBoard.jspa?rapidView=41&view=planning.nodetail&epics=visible>`_
    This is the first release of OOM, 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**
    - `OOM-6 <https://jira.onap.org/browse/OOM-6>`_ Automated platform deployment on Docker/Kubernetes

        VFC, AAF, MSB minor issues.

        Workaround: Manual configuration changes - however the reference
        vFirewall use case does not currently require these components.

    - `OOM-10 <https://jira.onap.org/browse/OOM-10>`_ Platform configuration management.

        OOM ONAP Configuration Management - Handling of Secrets.

        Workaround: Automated workaround to be able to pull from protected
        docker repositories.


**Security Issues**
    N/A


**Upgrade Notes**

    N/A

**Deprecation Notes**

    N/A

**Other**

    N/A

End of Release Notes
span class="k">then echo "MVN_VERSION is empty" exit 1 fi if [[ -z $MVN_MAJMIN_VERSION ]] then echo "MVN_MAJMIN_VERSION is empty" exit 1 fi if [[ $MVN_VERSION == *"SNAPSHOT"* ]] then MVN_MAJMIN_VERSION="${MVN_MAJMIN_VERSION}-SNAPSHOT" else MVN_MAJMIN_VERSION="${MVN_MAJMIN_VERSION}-STAGING" fi echo $MVN_MAJMIN_VERSION echo "Building $IMAGE" # # This is the local latest tagged image. The Dockerfile's need this to build images # TAGS="--tag onap/${IMAGE}:latest" # # This has the nexus repo prepended and only major/minor version with latest # TAGS="${TAGS} --tag ${DOCKER_REPOSITORY}/onap/${IMAGE}:${MVN_MAJMIN_VERSION}-latest" # # This has the nexus repo prepended and major/minor/patch version with timestamp # TAGS="${TAGS} --tag ${DOCKER_REPOSITORY}/onap/${IMAGE}:${MVN_VERSION}-${TIMESTAMP}Z" echo $TAGS docker build --quiet ${BUILD_ARGS} $TAGS packages/docker/target/$IMAGE if [ $? -ne 0 ] then echo "Docker build failed" docker images exit 1 fi docker images # # Push image # echo "Pushing $IMAGE" docker push ${DOCKER_REPOSITORY}/onap/$IMAGE:${MVN_MAJMIN_VERSION}-latest if [ $? -ne 0 ] then echo "Docker push failed" exit 1 fi docker push ${DOCKER_REPOSITORY}/onap/$IMAGE:${MVN_VERSION}-${TIMESTAMP}Z if [ $? -ne 0 ] then echo "Docker push failed" exit 1 fi