+5. Information Model and framework utilities continue to evolve to harmonize
+ the topology, workflow, and policy models from a number of SDOs including
+ ETSI NFV MANO, TM Forum SID, ONF Core, OASIS TOSCA, IETF and MEF.
+
+|image2|
+
+**Figure 2. Functional view of the ONAP architecture**
+
+The Casablanca release has a number of important new features in the areas of
+design time and runtime, ONAP installation, and S3P.
+
+Design time: The Service Design and Creation (SDC) project in ONAP has two new
+dashboards—DCAE design studio, SO Workflow Designer—to help designers, product
+managers, TechOps, and VNF owners create artifacts in one unified design
+palette.
+
+Runtime: Service Orchestration (SO) and controllers have new functionality to
+support physical network functions (PNFs), reboot, traffic migration, expanded
+hardware platform awareness (HPA), cloud agnostic intent capabilities, improved
+homing service, SDN geographic redundancy, scale-out and edge cloud onboarding.
+This will expand the actions available to support lifecycle management
+functionality, increase performance and availability, and unlock new edge
+automation and 5G use cases. With support for ETSI NFV-SOL003, the introduction
+of an ETSI compliant VNFM is simplified.
+
+In the area of monitoring, analytics, and service assurance, ONAP has early
+support for the Linux Foundation PNDA project in DCAE as a compliment to CDAP.
+Next, the data collection framework can now collect real-time messages through
+a high-volume collector, handle PNFs, and support SNMP and bulk performance
+management data files. The Policy project supports a new policy engine as well
+as the new Casablanca blueprints and can distribute policies through policy
+design capabilities in SDC, simplifying the design process. Next, the Holmes
+alarm correlation engine features a new GUI and provides richer functionality
+through scripting, again simplifying how rapidly alarm correlation rules can be
+developed.
+
+Moreover, there are new features in A&AI to support audit capabilities by
+providing historical data. ONAP northbound API continues to align better with
+TMForum (around ServiceOrder) and MEF APIs (around Legato and Interlude APIs)
+to simplify integration with OSS/BSS. The VID and UUI operations GUI projects
+can support a larger range of lifecycle management actions through a simple
+point and click interface allowing operators to perform more tasks with ease.
+Furthermore, The CLAMP project offers a new dashboard to view DMaaP and other
+events during design and runtime to ease the debugging of control-loop
+automation. ONAP has experimentally introduced ISTIO in certain components to
+progress the introduction of Service Mesh.
+
+ONAP installation: The ONAP Operations Manager (OOM) continues to make progress
+in streamlining ONAP installation by using Kubernetes (Docker and Helm Chart
+technologies). In Casablanca, OOM supports pluggable persistent storage
+including GlusterFS, providing users with more storage options. In a multi-node
+deployment, OOM allows more control on the placement of services based on
+available resources or node selectors. Finally, OOM now supports backup/restore
+of an entire k8s deployment thus introducing data protection.
+
+Casablanca has introduced the controller design studio, as part of the
+controller framework, which enables a model driven approach for how an ONAP
+controller controls the network resources.
+
+Deployability: Casablanca continued the 7 Dimensions momentum (Stability,
+Security, Scalability, Performance; and Resilience, Manageability, and
+Usability) from the prior to the Beijing release. A new logging project
+initiative called Post Orchestration Model Based Audit (POMBA), can check for
+deviations between design and ops environments thus increasing network service
+reliability. Numerous other projects ranging from Logging, SO, VF-C, A&AI,
+Portal, Policy, CLAMP and MSB have a number of improvements in the areas of
+performance, availability, logging, move to a cloud native architecture,
+authentication, stability, security, and code quality. Finally, versions of
+OpenDaylight and Kafka that are integrated in ONAP were upgraded to the Oxygen
+and v0.11 releases providing new capabilities such as P4 and data routing
+respectively.