ONAP Operations Manager Release Notes

Version 5.0.1 (El Alto Release)

Release Date:2019-10-10

Summary

The focus of this release was on maintanence and as such no new features were delivered. A list of issues resolved in this release can be found here: https://jira.onap.org/projects/OOM/versions/10726

New Features

Bug Fixes

  • 25 defects addressed (see link above)

Known Issues

The following known issues will be addressed in a future release:

  • [OOM-1480] - postgres chart does not set root password when installing on an existing database instances
  • [OOM-1966] - ONAP on HA Kubernetes Cluster - Documentation update
  • [OOM-1995] - Mariadb Galera cluster pods keep failing
  • [OOM-2061] - Details Missing for installing the kubectl section
  • [OOM-2075] - Invalid MTU for Canal CNI interfaces
  • [OOM-2080] - Need for “ReadWriteMany” access on storage when deploying on Kubernetes?
  • [OOM-2091] - incorrect release deployed

Security Notes

Fixed Security Issues

Known Security Issues

  • In default deployment OOM (consul-server-ui) exposes HTTP port 30270 outside of cluster. [OJSI-134]
  • Hard coded password used for all oom deployments [OJSI-188]
  • CVE-2019-12127 - OOM exposes unprotected API/UI on port 30270 [OJSI-202]

Known Vulnerabilities in Used Modules

OOM code has been formally scanned during build time using NexusIQ and no Critical vulnerability was found.

Quick Links:

Version 5.0.0 (El Alto Early Drop)

Release Date:2019-08-19

Summary

Software Requirements

  • Upgraded to Kubernetes 1.15.x and Helm 1.14.x

Version 4.0.0 (Dublin Release)

Release Date:2019-06-26

Summary

Platform Resiliency

  • Documenation of a Highly-Available Kubernetes Cluster Deployment
  • Availability of a Default Storage Class Provisioner for improved Persistent Storage resiliency
  • Availability of a CNI reference integration for Multi-site support
    • applications can take advantage of multi-site by using POD and/or Node (anti)affinity, taints/tolerations, labels per application

Footprint Optimization

  • Shared MariaDB-Galera Cluster - current clients in Dublin: SO, SDNC
  • Shared Cassandra Cluster - current clients in Dublin: AAI, SDC
  • Optional deployment of independent clusters (backward compatibility)

Platform Upgradability

  • Introduction of an Upgrade Framework supporting:
    • Automated rolling upgrades for applications
    • In-place schema and data migrations
    • Blue-Green deployment environment migration (e.g. Pre-prod to Prod)
    • Upgrades from embedded database instance into shared database instance
  • Release-to-release upgrade support delivered for the following projects
    • A&AI
    • SDNC
    • SO

Security Notes

Fixed Security Issues

Known Security Issues

  • In default deployment OOM (consul-server-ui) exposes HTTP port 30270 outside of cluster. [OJSI-134]
  • Hard coded password used for all oom deployments [OJSI-188]
  • CVE-2019-12127 - OOM exposes unprotected API/UI on port 30270 [OJSI-202]

Known Vulnerabilities in Used Modules

OOM code has been formally scanned during build time using NexusIQ and no Critical vulnerability was found.

Quick Links:

Known Issues

Version 3.0.0 Casablanca Release

Release Date:2018-11-30

Summary

The focus of this release was on incremental improvements in the following areas:

  • Pluggable persistent storage with support for GlusterFS as the first storage class provisioner
  • CPU and Memory limits in Helm Charts to improve Pod placement based on resource availablity in Kubernetes Cluster
  • Support of Node Selectors for Pod placement
  • Common “shared” Helm Charts referencing common images
    • mariadb-galera
    • postgres
    • cassandra
    • mysql
    • mongo
  • Integration of ARK Backup and Restore solution
  • Introduction of Helm deploy and undeploy plugins to better manage ONAP deployments

Security Notes

OOM code has been formally scanned during build time using NexusIQ and no Critical vulnerability was found.

Quick Links:

Known Issues

  • Problem: kubectl connections to pods (kubectl exec|logs) will fail after a while due to a known bug in Kubernetes (1.11.2)

    Workaround: Restart of the kubelet daemons on the k8s hosts

    Fix: Will be delivered in the next release via a new Kubernetes version (1.12)

Version 2.0.0 Beijing Release

Release Date:2018-06-07

Epic

  • [OOM-6] - Automated platform deployment on Docker/Kubernetes
  • [OOM-7] - Platform monitoring and auto-healing
  • [OOM-8] - Automated platform scalability
  • [OOM-9] - Platform upgradability & rollbacks
  • [OOM-10] - Platform configuration management
  • [OOM-46] - Platform infrastructure deployment with TOSCA
  • [OOM-109] - Platform Centralized Logging
  • [OOM-138] - Using Optimization framework
  • [OOM-346] - Platform Resiliency (including Recoverability, High-Availability, Backup/Restore, Geo-Redundancy)
  • [OOM-376] - ONAP deployment options standardization
  • [OOM-486] - HELM upgrade from 2.3 to 2.8.0
  • [OOM-535] - Upgrade Kubernetes from 1.8.6 to 1.9.2
  • [OOM-590] - OOM Wiki documentation of deployment options

Story

  • [OOM-11] - Add AAF containers to ONAP Kubernetes
  • [OOM-13] - Add CLI containers to ONAP Kubernetes
  • [OOM-15] - Add DMAAP containers to ONAP Kubernetes
  • [OOM-20] - State Monitoring: MSO/mso
  • [OOM-21] - State Monitoring: A&AI/aai-service
  • [OOM-22] - State Monitoring: SDNC/sdc-be
  • [OOM-24] - State Monitoring: message-router
  • [OOM-25] - State Monitoring: MSB
  • [OOM-29] - State Monitoring: VID
  • [OOM-31] - State Monitoring: APPC/dbhost
  • [OOM-32] - State Monitoring: VFC
  • [OOM-33] - State Monitoring: Multi-VIM
  • [OOM-34] - Auto-Restart on failure: …
  • [OOM-35] - State Monitoring: A&AI/hbase
  • [OOM-36] - State Monitoring: A&AI/model-loader-service
  • [OOM-37] - State Monitoring: APPC/dgbuilder
  • [OOM-38] - State Monitoring: APPC/sdnctldb01
  • [OOM-39] - State Monitoring: APPC/sdnctldb02
  • [OOM-40] - State Monitoring: APPC/sdnhost
  • [OOM-41] - State Monitoring: MSO/mariadb
  • [OOM-42] - State Monitoring: SDNC/dbhost
  • [OOM-43] - State Monitoring: SDNC/sdnc-dgbuilder
  • [OOM-44] - State Monitoring: SDNC/sdnc-portal
  • [OOM-45] - State Monitoring: SDNC/sdnctldb01
  • [OOM-51] - OOM ONAP Configuration Management - Externalize hardwired values
  • [OOM-52] - OOM ONAP Configuration Management - Parameterization of docker images
  • [OOM-53] - OOM ONAP Configuration Management - Parameterization for Sizing
  • [OOM-63] - Kubernetes cluster created by TOSCA description
  • [OOM-85] - Test the code in the “Lab” project environment
  • [OOM-86] - Monitoring the health status of ONAP components
  • [OOM-87] - Configure TOSCA description via dashboard
  • [OOM-88] - Deploy Holmes on K8S cluster by TOSCA description
  • [OOM-89] - Deploy CLAMP on K8S cluster by TOSCA description
  • [OOM-91] - Deploy MSB on K8S cluster by TOSCA description
  • [OOM-92] - Deploy AAF on K8S cluster by TOSCA description
  • [OOM-93] - Deploy VF-C on K8S cluster by TOSCA description
  • [OOM-94] - Deploy Multi-VIM on K8S cluster by TOSCA description
  • [OOM-95] - Deploy DCAEGen2 on K8S cluster by TOSCA description
  • [OOM-96] - Deploy AAI on K8S cluster by TOSCA description
  • [OOM-97] - Deploy APPC on K8S cluster by TOSCA description
  • [OOM-98] - Deploy MSO on K8S cluster by TOSCA description
  • [OOM-99] - Deploy Policy on K8S cluster by TOSCA description
  • [OOM-100] - Deploy SDC on K8S cluster by TOSCA description
  • [OOM-102] - Deploy VID on K8S cluster by TOSCA description
  • [OOM-110] - OOM ONAP Logging - Elastic Stack components deployment
  • [OOM-111] - OOM ONAP Logging - FileBeat deployment aside ONAP components
  • [OOM-112] - OOM ONAP Logging - Configuration of all ONAP components to emit canonical logs
  • [OOM-116] - ignore intellj files
  • [OOM-145] - update directory path from dockerdata-nfs to configured directory name (make it configurable)
  • [OOM-235] - Service endpoint annotation for Usecase UI
  • [OOM-242] - Modify DCAE seed for Helm
  • [OOM-262] - Remove “oneclick” kubectl scripts.
  • [OOM-265] - Top level helm chart for ONAP
  • [OOM-268] - Persist and externalize database directories via persistent volumes
  • [OOM-271] - Copy app config files from source
  • [OOM-272] - Set application environment variables from source
  • [OOM-277] - add automatic ONAP config parameter substitution
  • [OOM-280] - MSB automatically re-synch service data on restart.
  • [OOM-292] - Expose LOG Volume via /dockerdata-nfs
  • [OOM-293] - OOM ONAP Configuration Management - Handling of Secrets
  • [OOM-298] - Provide script to cleanup configuration data created by createConfig.sh
  • [OOM-322] - Clean-up config files that are generated at system startup
  • [OOM-341] - Provide an example of a partial deployment of ONAP components (e.g. no VFC)
  • [OOM-342] - Add pointer to Wiki page on the readme file.
  • [OOM-344] - Break the configuration tarball per appplication
  • [OOM-345] - Re-validate # of containers and configuration for DCAEgen2
  • [OOM-356] - Add ‘Usecase UI’ containers to ONAP Kubernetes
  • [OOM-359] - SDC logback chef failure
  • [OOM-375] - F2F: ONAP/OOM for Developers
  • [OOM-382] - Robot Version 1.1 OpenO tests
  • [OOM-406] - In Kubernetes 1.8, the annotations are no longer supported and must be converted to the PodSpec field.
  • [OOM-457] - In Kubernetes 1.8, init-container annotations to be converted to PodSpec field for aaf, clamp and vfc
  • [OOM-460] - Segregating configuration of ONAP components
  • [OOM-476] - Parameterize values.yaml docker image repos into global config variables
  • [OOM-528] - Confirm k8s context with a prompt for deleteAll.bash
  • [OOM-534] - Need to provide support for creating different sized OOM deployments
  • [OOM-546] - Provide option to collect ONAP env details for issue investigations
  • [OOM-569] - Investigate containerizing Cloudify Manager
  • [OOM-579] - Document a Cloudify deployment of OOM Beijing
  • [OOM-633] - Provide direct access to ONAP Portal without the need to use VNC
  • [OOM-677] - Update all source code files with the Apache 2 License header
  • [OOM-678] - Enforce MSB dockers dependencies using init-container
  • [OOM-681] - updating docker images/components to latest code
  • [OOM-682] - deployment of sdc workflow designer
  • [OOM-695] - Improve Readiness-check prob
  • [OOM-722] - OOM - Run all ONAP components in one namespace
  • [OOM-725] - Use Blueprint to install Helm and k8s dashboard while creating k8s cluster
  • [OOM-727] - Add Standardized Configuration to SO
  • [OOM-728] - Add Standardized Configuration to ROBOT
  • [OOM-729] - Add Standardized Configuration to VID
  • [OOM-730] - Add Standardized Configuration to Consul
  • [OOM-731] - Add Standardized Configuration to DMaaP Message Router
  • [OOM-732] - Add Standardized Configuration to AAF
  • [OOM-733] - Add Standardized Configuration to APPC
  • [OOM-734] - Add Standardized Configuration to AAI
  • [OOM-735] - Add Standardized Configuration to CLAMP
  • [OOM-736] - Add Standardized Configuration to CLI
  • [OOM-737] - Add Standardized Configuration to DCAEGEN2
  • [OOM-738] - Add Standardized Configuration to ESR
  • [OOM-739] - Add Standardized Configuration to KUBE2MSB
  • [OOM-740] - Add Standardized Configuration to LOG
  • [OOM-742] - Add Standardized Configuration to MSB
  • [OOM-743] - Replace deprecated MSO Helm Chart with Standardized SO Helm Chart
  • [OOM-744] - Add Standardized Configuration to MULTICLOUD
  • [OOM-746] - Add Standardized Configuration to PORTAL
  • [OOM-747] - Add Standardized Configuration to SDC
  • [OOM-748] - Add Standardized Configuration to SDNC
  • [OOM-749] - Add Standardized Configuration to UUI
  • [OOM-750] - Add Standardized Configuration to VFC
  • [OOM-751] - Add Standardized Configuration to VNFSDK
  • [OOM-758] - Common Mariadb Galera Helm Chart to be reused by many applications
  • [OOM-771] - OOM - update master with new policy db deployment
  • [OOM-777] - Add Standardized Configuration Helm Starter Chart
  • [OOM-779] - OOM APPC ODL (MDSAL) persistent storage
  • [OOM-780] - Update MSO to latest working version.
  • [OOM-786] - Re-add support for multiple instances of ONAP
  • [OOM-788] - Abstract docker secrets
  • [OOM-789] - Abstract cluster role binding
  • [OOM-811] - Make kube2msb use secret instead of passing token as environment variable
  • [OOM-822] - Update Documentation for the Beijing Release
  • [OOM-823] - Add CDT image to APPC chart
  • [OOM-827] - Add quick start documentation README
  • [OOM-828] - Remove oneclick scripts
  • [OOM-857] - kube2msb fails to start
  • [OOM-914] - Add LOG component robot healthcheck
  • [OOM-960] - OOM Healthcheck lockdown - currently 32/39 : 20180421
  • [OOM-979] - Enhance OOM TOSCA solution to support standardized Helm Chart
  • [OOM-1006] - VNFSDK healthcheck fails
  • [OOM-1073] - Change the Repository location in the image oomk8s/config-init:2.0.0-SNAPSHOT
  • [OOM-1078] - Update Kubectl, docker, helm version

Task

  • [OOM-57] - Agree on configuration contract/YAML with each of the project teams
  • [OOM-105] - TOSCA based orchestration demo
  • [OOM-257] - DevOps: OOM config reset procedure for new /dockerdata-nfs content
  • [OOM-305] - Rename MSO to SO in OOM
  • [OOM-332] - Add AAI filebeat container - blocked by LOG-67
  • [OOM-428] - Add log container healthcheck to mark failed creations - see OOM-427
  • [OOM-429] - DOC: Document HELM server version 2.7.2 required for tpl usage
  • [OOM-489] - Update values.yaml files for tag name changes for docker images and versions.
  • [OOM-543] - SDNC adjust docker pullPolicy to IfNotPresent to speed up initial deployment slowdown introduced by SDNC-163
  • [OOM-604] - Update OOM and HEAT AAI sparky master from v1.1.0 to v1.1.1 - match INT-288
  • [OOM-614] - SDC, SDNC, AAI Healthcheck failures last 12 hours 20180124:1100EST
  • [OOM-624] - CII security badging: cleartext password for keystone and docker repo creds
  • [OOM-726] - Mirror AAI docker version changes into OOM from AAI-791
  • [OOM-772] - Remove old DCAE from Release
  • [OOM-801] - Policy docker images rename - key off new name in POLICY-674
  • [OOM-810] - Improve emsdriver code
  • [OOM-819] - expose log/logstash 5044 as nodeport for external log producers outside of the kubernetes cluster
  • [OOM-820] - Bypass vnc-portal for ONAP portal access
  • [OOM-943] - Upgrade prepull_docker.sh to work with new helm based master refactor - post OOM-328
  • [OOM-947] - Update AAI to latest images
  • [OOM-975] - Notes are missing in multicloud
  • [OOM-1031] - Config Changes for consul to make vid, so, log health checks pass
  • [OOM-1032] - Making consul Stateful
  • [OOM-1122] - Update APPC OOM chart to use Beijing release artifacts

Bug

  • [OOM-4] - deleteAll.bash fails to properly delete services and ports
  • [OOM-153] - test - Sample Bug
  • [OOM-212] - deleteAll script does not have an option to delete the services
  • [OOM-215] - configure_app for helm apps is not correct
  • [OOM-218] - createConfig.sh needs a chmod 755 in release-1.0.0 only
  • [OOM-239] - mso.tar created in dockerdatanfs
  • [OOM-258] - AAI logs are not being written outside the pods
  • [OOM-282] - vnc-portal requires /etc/hosts url fix for SDC sdc.ui should be sdc.api
  • [OOM-283] - No longer able to deploy instances in specified namespace
  • [OOM-290] - config_init pod fails when /dockerdata-nfs is nfs-mounted
  • [OOM-300] - cat: /config-init/onap/mso/mso/encryption.key: No such file or directory
  • [OOM-333] - vfc-workflow fails [VFC BUG] - fixed - 20180117 vfc-ztevnfmdriver has docker pull issue
  • [OOM-334] - Change kubernetes startup user
  • [OOM-351] - Apply standard convention across the “template deployment YML” file
  • [OOM-352] - failed to start VFC containers
  • [OOM-363] - DCAE tests NOK with Robot E2E tests
  • [OOM-366] - certificates in consul agent config are not in the right directory
  • [OOM-389] - sdc-be and sdc-fe do not initialize correctly on latest master
  • [OOM-409] - Update Vid yaml file to point to the ONAPPORTAL URL
  • [OOM-413] - In portal VNC pod refresh /etc/hosts entries
  • [OOM-414] - MSB Healtcheck failure on $*_ENDPOINT variables
  • [OOM-424] - DCAE installation is not possible today
  • [OOM-430] - Portal healthcheck passing on vnc-portal down
  • [OOM-467] - Optimize config-init process
  • [OOM-493] - Kubernetes infrastructure for ESR
  • [OOM-496] - Readiness check is marking full availability of some components like SDC and SDNC before they would pass healthcheck
  • [OOM-514] - Readiness prob fails sometimes even though the relevant pods are running
  • [OOM-539] - Kube2MSB registrator doesn’t support https REST service registration
  • [OOM-570] - Wrong value is assigned to kube2msb AUTH_TOKEN environment variable
  • [OOM-574] - OOM configuration for robot doesnt copy heat templatese in dockerdata-nfs
  • [OOM-577] - Incorrect evaluation of bash command in yaml template file (portal-vnc-dep.yaml)
  • [OOM-578] - Hard coded token in oom/kubernetes/kube2msb/values.yaml file
  • [OOM-589] - Can not acces CLI in vnc-portal
  • [OOM-598] - createAll.bash base64: invalid option – d
  • [OOM-600] - Unable to open CLI by clicking CLI application icon
  • [OOM-630] - Red herring config pod deletion error on deleteAll - after we started deleting onap-config automatically
  • [OOM-645] - Kube2MSB RBAC security issues
  • [OOM-653] - sdnc-dbhost-0 deletion failure
  • [OOM-657] - Look into DCAEGEN2 failure on duplicate servicePort
  • [OOM-672] - hardcoded clusterIP for aai breaks auto installation
  • [OOM-680] - ONAP Failure install with kubernetes 1.8+
  • [OOM-687] - Typo in README_HELM
  • [OOM-724] - License Update in TOSCA
  • [OOM-767] - data-router-logs and elasticsearch-data mapped to same folder
  • [OOM-768] - Hardcoded onap in config files
  • [OOM-769] - sdc-es data mapping in sdc-be and sdc-fe redundant
  • [OOM-783] - UUI health check is failing
  • [OOM-784] - make new so chart one namespace compatible
  • [OOM-791] - After OOM-722 merge - docker pulls are timing out - switch to pullPolicy IfNotPresent
  • [OOM-794] - demo-k8s.sh name not modified in the usage string
  • [OOM-795] - HEAT templates for robot instantiateVFW missing
  • [OOM-796] - robot asdc/sdngc interface in synch for Master
  • [OOM-797] - GLOBAL_INJECTED_SCRIPT_VERSION missing from vm_properties.py
  • [OOM-804] - VFC vfc-ztevnfmdriver container failure
  • [OOM-815] - OOM Robot container helm failure after OOM-728 35909 merge
  • [OOM-829] - Can not make multicloud helm chart
  • [OOM-830] - Fix OOM build dependencies
  • [OOM-835] - CLAMP mariadb pv is pointing to a wrong location
  • [OOM-836] - champ and gizmo yaml validation issue
  • [OOM-845] - Global repository should not be set by default
  • [OOM-846] - Add liveness enabled fix to helm starter
  • [OOM-847] - log-elasticsearch external ports are not externally accessible
  • [OOM-848] - log-logstash logstash pipeline fails to start after oom standard config changes
  • [OOM-851] - sdc chart validation error
  • [OOM-856] - appc mysql fails deployment
  • [OOM-858] - Fail to deploy onap chart due to config map size
  • [OOM-870] - Missing CLAMP configuration
  • [OOM-871] - log kibana container fails to start after oom standard config changes
  • [OOM-872] - APPC-helm Still need config pod
  • [OOM-873] - OOM doc typo
  • [OOM-874] - Inconsistent repository references in ONAP charts
  • [OOM-875] - Cannot retrieve robot logs
  • [OOM-876] - Some containers ignore the repository setting
  • [OOM-878] - MySQL slave nodes don’t deploy when mysql.replicaCount > 1
  • [OOM-881] - SDN-C Portal pod fails to come up
  • [OOM-882] - Some SDNC service names should be prefixed with the helm release name
  • [OOM-884] - VID-VID mariadb pv is pointing to a wrong location
  • [OOM-885] - Beijing oom component log messages missing in Elasticsearch
  • [OOM-886] - kube2msb not starting up
  • [OOM-887] - SDN-C db schema and sdnctl db user not reliably being created
  • [OOM-888] - aaf-cs mapping wrong
  • [OOM-889] - restore pv&pvc for mysql when NFS provisioner is disabled
  • [OOM-898] - Multicloud-framework config file is not volume-mounted
  • [OOM-899] - SDNC main pod does not come up
  • [OOM-900] - portal-cassandra missing pv and pvc
  • [OOM-904] - OOM problems bringing up components and passing healthchecks
  • [OOM-905] - Charts use nsPrefix instead of release namespace
  • [OOM-906] - Make all services independent of helm Release.Name
  • [OOM-907] - Make all persistent volume to be mapped to a location defined by helm Release.Name
  • [OOM-908] - Job portal-db-config fails due to missing image config
  • [OOM-909] - SO Health Check fails
  • [OOM-910] - VID Health Check fails
  • [OOM-911] - VFC Health Check fails for 9 components
  • [OOM-912] - Multicloud Health Check fails for 1 of its components
  • [OOM-913] - Consul agent pod is failing
  • [OOM-916] - Used to fix testing issues related to usability
  • [OOM-918] - Policy - incorrect configmap mount causes base.conf to disappear
  • [OOM-920] - Issue with CLAMP configuation
  • [OOM-921] - align onap/values.yaml and onap/resources/environments/dev.yaml - different /dockerdata-nfs
  • [OOM-926] - Disable clustering for APP-C out-of-the-box
  • [OOM-927] - Need a production grade configuration override file of ONAP deployment
  • [OOM-928] - Some charts use /dockerdata-nfs by default
  • [OOM-929] - DMaaP message router docker image fails to pull
  • [OOM-930] - New AAF Helm Charts required
  • [OOM-931] - Reintroduce VNC pod into OOM
  • [OOM-932] - Unblock integration testing
  • [OOM-935] - sdc-cassandra pod fails to delete using helm delete - forced kubectl delete
  • [OOM-936] - Readiness-check prob version is inconsistent across components
  • [OOM-937] - Portal Cassandra config map points to wrong directory
  • [OOM-938] - Can’t install aai alone using helm
  • [OOM-945] - SDNC some bundles failing to start cleanly
  • [OOM-948] - make vfc got an error
  • [OOM-951] - Update APPC charts based on on changes for ccsdk and Nitrogen ODL
  • [OOM-953] - switch aai haproxy/hbase repo from hub.docker.com to nexus3
  • [OOM-958] - SDC-be deployment missing environment paramter
  • [OOM-964] - SDC Healthcheck failure on sdc-be and sdc-kb containers down
  • [OOM-968] - warning on default deployment values.yaml
  • [OOM-969] - oomk8s images have no Dockerfile’s
  • [OOM-971] - Common service name template should allow for chart name override
  • [OOM-974] - Cassandra bootstrap is done incorrectly
  • [OOM-977] - The esr-gui annotations should include a “path” param when register to MSB
  • [OOM-985] - DMAAP Redis fails to start
  • [OOM-986] - SDC BE and FE logs are missing
  • [OOM-989] - Sync ete-k8.sh and ete.sh for new log file numbering
  • [OOM-990] - AUTO.json in SDC has unreachable addresses
  • [OOM-993] - AAI model-loader.properties not in sync with project file
  • [OOM-994] - DCAE cloudify controller docker image 1.1.0 N/A - use 1.2.0/1.3.0
  • [OOM-1003] - dcae-cloudify-manager chart references obsolete image version
  • [OOM-1004] - aai-resources constantly fails due to cassanda hostname
  • [OOM-1005] - AAI Widgets not loading due to duplicate volumes
  • [OOM-1007] - Update dcae robot health check config
  • [OOM-1008] - Set default consul server replica count to 1
  • [OOM-1010] - Fix broken property names in DCAE input files
  • [OOM-1011] - Policy config correction after Service Name changes because of OOM-906
  • [OOM-1013] - Update DCAE container versions
  • [OOM-1014] - Portal login not working due to inconsistent zookeeper naming
  • [OOM-1015] - Champ fails to start
  • [OOM-1016] - DOC-OPS Review: Helm install command is wrong on oom_user_guide - missing namespace
  • [OOM-1017] - DOC-OPS review: Docker/Kubernetes versions wrong for master in oom_cloud_setup_guide
  • [OOM-1018] - DOC-OPS review: global repo override does not match git in oom quick start guide
  • [OOM-1019] - DOC-OPS review: Add Ubuntu 16.04 reference to oom_user_guide to avoid 14/16 confusion
  • [OOM-1021] - Update APPC resources for Nitrogen ODL
  • [OOM-1022] - Fix SDC startup dependencies
  • [OOM-1023] - “spring.datasource.cldsdb.url” in clamp has wrong clampdb name
  • [OOM-1024] - Cassandra data not persisted
  • [OOM-1033] - helm error during deployment 20180501:1900 - all builds under 2.7.2
  • [OOM-1034] - VID Ports incorrect in deployment.yaml
  • [OOM-1037] - Enable CLI health check
  • [OOM-1039] - Service distribution to SO fails
  • [OOM-1041] - aai-service was renamed, but old references remain
  • [OOM-1042] - portalapps service was renamed, but old references remain
  • [OOM-1045] - top level values.yaml missing entry for dmaap chart
  • [OOM-1049] - SDNC_UEB_LISTENER db
  • [OOM-1050] - Impossible to deploy consul using cache docker registry
  • [OOM-1051] - Fix aaf deployment
  • [OOM-1052] - SO cloud config file points to Rackspace cloud
  • [OOM-1054] - Portal LoadBalancer Ingress IP is on the wrong network
  • [OOM-1060] - Incorrect MR Kafka references prevent aai champ from starting
  • [OOM-1061] - ConfigMap size limit exceeded
  • [OOM-1064] - Improve docker registry secret management
  • [OOM-1066] - Updating TOSCA blueprint to sync up with helm configuration changes (add dmaap and oof/delete message-router)
  • [OOM-1068] - Update SO with new AAI cert
  • [OOM-1076] - some charts still using readiness check image from amsterdam 1.x
  • [OOM-1077] - AAI resources and traversal deployment failure on non-rancher envs
  • [OOM-1079] - Robot charts dont allow over ride of pub_key, dcae_collector_ip and dcae_collector_port
  • [OOM-1081] - Remove component ‘mock’ from TOSCA deployment
  • [OOM-1082] - Wrong pv location of dcae postgres
  • [OOM-1085] - appc hostname is incorrect in url
  • [OOM-1086] - clamp deployment changes /dockerdata-nfs/ReleaseName dir permissions
  • [OOM-1088] - APPC returns error for vCPE restart message from Policy
  • [OOM-1089] - DCAE pods are not getting purged
  • [OOM-1093] - Line wrapping issue in redis-cluster-config.sh script
  • [OOM-1094] - Fix postgres startup
  • [OOM-1095] - common makefile builds out of order
  • [OOM-1096] - node port conflict SDNC (Geo enabled) & other charts
  • [OOM-1097] - Nbi needs dep-nbi - crash on make all
  • [OOM-1099] - Add External Interface NBI project into OOM TOSCA
  • [OOM-1102] - Incorrect AAI services
  • [OOM-1103] - Cannot disable NBI
  • [OOM-1104] - Policy DROOLS configuration across container restarts
  • [OOM-1110] - Clamp issue when connecting Policy
  • [OOM-1111] - Please revert to using VNFSDK Postgres container
  • [OOM-1114] - APPC is broken in latest helm chart
  • [OOM-1115] - SDNC DGBuilder cant operate on DGs in database - need NodePort
  • [OOM-1116] - Correct values needed by NBI chart
  • [OOM-1124] - Update OOM APPC chart to enhance AAF support
  • [OOM-1126] - Incorrect Port mapping between CDT Application and APPC main application
  • [OOM-1127] - SO fails healthcheck
  • [OOM-1128] - AAF CS fails to start in OpenLab

Sub-task

  • [OOM-304] - Service endpoint annotation for Data Router
  • [OOM-306] - Handle mariadb secrets
  • [OOM-510] - Increase vm.max_map_count to 262144 when running Rancher 1.6.11+ via helm 2.6+ - for elasticsearch log mem failure
  • [OOM-512] - Push the reviewed and merged ReadMe content to RTD
  • [OOM-641] - Segregating of configuration for SDNC-UEB component
  • [OOM-655] - Create alternate prepull script which provides more user feedback and logging
  • [OOM-753] - Create Helm Sub-Chart for SO’s embedded mariadb
  • [OOM-754] - Create Helm Chart for SO
  • [OOM-774] - Create Helm Sub-Chart for APPC’s embedded mySQL database
  • [OOM-775] - Create Helm Chart for APPC
  • [OOM-778] - Replace NFS Provisioner with configurable PV storage solution
  • [OOM-825] - Apache 2 License updation for All sqls and .js file
  • [OOM-849] - Policy Nexus component needs persistent volume for /sonatype-work
  • [OOM-991] - Adjust SDC-BE init job timing from 10 to 30s to avoid restarts on single node systems
  • [OOM-1036] - update helm from 2.7.2 to 2.8.2 wiki/rtd
  • [OOM-1063] - Document Portal LoadBalancer Ingress IP Settings

Security Notes

OOM code has been formally scanned during build time using NexusIQ and no Critical vulnerability was found.

Quick Links:

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 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 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 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