.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. SPDX-License-Identifier: CC-BY-4.0
-.. Copyright (C) 2019 highstreet technologies GmbH
+.. Copyright (C) 2021 highstreet technologies GmbH
Operation and Maintenance Release Notes
=======================================
-This document provides the release notes for O-RAN-SC Amber release of the Operation and Maintenance (OAM) project.
+This document provides the release notes for O-RAN-SC D-Release of the Operation and Maintenance (OAM) project.
.. contents::
:depth: 3
:local:
+Version 4.0.1, 2021-03-12
+--------------------------
-Version history
----------------
++--------------------------------------------------------+-------------------------------------------------------------+
+| Issue | Summary |
++========================================================+=============================================================+
+| `OAM-180 <https://jira.o-ran-sc.org/browse/OAM-180>`__ | Wrong time format in VES client scripts |
++--------------------------------------------------------+-------------------------------------------------------------+
+| `OAM-176 <https://jira.o-ran-sc.org/browse/OAM-176>`__ | Support of IPv6 by docker-compose |
++--------------------------------------------------------+-------------------------------------------------------------+
+| `OAM-175 <https://jira.o-ran-sc.org/browse/OAM-175>`__ | Update docker-compose and its configurations |
++--------------------------------------------------------+-------------------------------------------------------------+
+| `OAM-174 <https://jira.o-ran-sc.org/browse/OAM-174>`__ | Update VES Client scripts supporting VES 7.2 |
++--------------------------------------------------------+-------------------------------------------------------------+
+| `OAM-173 <https://jira.o-ran-sc.org/browse/OAM-173>`__ | Update VES client scripts supporting https |
++--------------------------------------------------------+-------------------------------------------------------------+
+| `OAM-170 <https://jira.o-ran-sc.org/browse/OAM-170>`__ | Delete folder 'model' from OAM repo' |
++--------------------------------------------------------+-------------------------------------------------------------+
+| `OAM-169 <https://jira.o-ran-sc.org/browse/OAM-169>`__ | Use case driven yang for O-DU |
++--------------------------------------------------------+-------------------------------------------------------------+
+| `OAM-168 <https://jira.o-ran-sc.org/browse/OAM-168>`__ | Update namespace definitions in prototype yangs of O-RAN-SC |
++--------------------------------------------------------+-------------------------------------------------------------+
+| `OAM-164 <https://jira.o-ran-sc.org/browse/OAM-164>`__ | Add WG4 november train yangs modules |
++--------------------------------------------------------+-------------------------------------------------------------+
-+--------------------+--------------------+--------------------+--------------------+
-| **Date** | **Ver.** | **Author** | **Comment** |
-| | | | |
-+--------------------+--------------------+--------------------+--------------------+
-| 2019-09-08 | 0.1.0 | | Initial Version |
-| | | | |
-+--------------------+--------------------+--------------------+--------------------+
-| 2019-09-18 | 0.1.1 | | Initial Version |
-| | | | DEV environment |
-+--------------------+--------------------+--------------------+--------------------+
-| 2019-11-14 | 1.0 | | Docs added |
-| | | | |
-+--------------------+--------------------+--------------------+--------------------+
+Version 2.0.4, 2020-06-13
+--------------------------
-Summary
--------
+* Documentation updated
+* Develop reusable OAM API such that the first consumer being a VTH can query, subscribe or publish on a DMaaP topic Story
+* Create helm deployment for SMO
+* Feature split for starting devicemanagers
+* Seed coder for an YANG linter
+* Please see also Release Notes of `ONAP SDNC, DCAE, DMaaP, OOM <https://onap-doc.readthedocs.io/en/frankfurt/release/index.html>`_
-According to the O-RAN-SC-OAM-Architecture document all ManagedElements
-(near-real-time-RIC, O-CU-CP, O-CU-UP, O-DU and O-RU) implement the O1-interface.
+Version 2.0.3, 2020-04-08
+-------------------------
-The O-RAN-OAM-interface specification defines
+* What is an SMO?
+* Provide xRAN datamodels
+* Provide curl bash scripts for Software Management
+* Add jenkins jobs for oam
+* Add parents to model artifacts
+* Add top level pom file to distribution
+* Wrong image tag in nonrt-o1-controller distribution pom
+* Use ONAP release parents directly
+* Adjust artifact group name to ORAN naming rule
+* Use ORAN parents
+* Add push registry to distribution pom
-a NetConf-Server for Configuration Management (CM) and
-a http-client for Fault Managment (FM), Performance Management (PM) and other events
-on each Management-Service-Provider (MnS-Provider) running on the ManagedElement (ME).
+Version 2.0.2, 2020-03-16
+-------------------------
+* Controller DeviceManager for O-RAN-SC
+* Provide O1 yang modules
+Version 2.0.1, 2020-02-26
+-------------------------
-The O-RAN-SC-OAM project provides reference implementation according to the O-RAN OAM (WG1) documents.
-In addition we provide a common MnS-Consumer for development and module test purposes.
-The assumption is that the projects for the ManagedElements can concentrate on the more important user-plane.
+* Develop VTH for A1 interface
+
+
+Version 1.0.0, 2019-11-14
+-------------------------
+
+* Documentation added
+
+
+Version 0.1.1, 2019-09-18
+-------------------------
+
+* Development environment added
+
+
+Version 0.1.0, 2019-09-08
+-------------------------
+* Initial version
Code Review / oam.git / blobdiff