X-Git-Url: https://gerrit.onap.org/r/gitweb?a=blobdiff_plain;f=docs%2Frelease-notes.rst;h=77929b7ff44ccfe96d4498d44365104be02aaf66;hb=a4007dd6135b3d2fe02d5ce7e88ded68155403cd;hp=3cb547cce3b96d46926517bd9ae34a6b017c880b;hpb=af4183e1284e5592a4359a4d2a9000ee2feafda7;p=oom.git

diff --git a/docs/release-notes.rst b/docs/release-notes.rst
index 3cb547cce3..77929b7ff4 100644
--- a/docs/release-notes.rst
+++ b/docs/release-notes.rst
@@ -8,6 +8,46 @@
 Release Notes
 =============
 
+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 cluster
+  - postgres cluster
+  - cassandra
+  - mysql
+  - mongodb
+- 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:
+	- `OOM project page <https://wiki.onap.org/display/DW/ONAP+Operations+Manager+Project>`_
+
+	- `Passing Badge information for OOM <https://bestpractices.coreinfrastructure.org/en/projects/1631>`_
+
+
+**Known Issues**
+
+Problem:        kubectl connections to pods (kubectl exec|logs) will fail after a while due to a known bug in Kubernetes
+Workaround:     Restart of the kubelet daemons on the k8s hosts
+Fix:            Will be delivered in the next release via a new Kubernetes version
+- `OOM-1532 <https://jira.onap.org/browse/OOM-1532>`_
+
+
 Version 2.0.0 Beijing Release
 -----------------------------
 
@@ -425,7 +465,7 @@ 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 OMAP components - on any type of environment.
+    - 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.