From 7126df41ed4ad3cdddcc05844609dab340210af4 Mon Sep 17 00:00:00 2001
From: Gerard Damm <gerard.damm@wipro.com>
Date: Fri, 16 Mar 2018 15:31:41 -0500
Subject: cosmetic fixes (numbering, bulleting, TOC, section levels, ...)

JIRA: AUTO-26

edited files for better HTML rendering (especially, added missing blank lines to ensure proper bulleting)

Change-Id: I8165363f15f26bab2e3f72cc1435c4acf32f618b
Signed-off-by: Gerard Damm <gerard.damm@wipro.com>
---
 docs/release/release-notes/Auto-release-notes.rst | 42 +++++++++++------------
 1 file changed, 21 insertions(+), 21 deletions(-)

(limited to 'docs/release/release-notes/Auto-release-notes.rst')

diff --git a/docs/release/release-notes/Auto-release-notes.rst b/docs/release/release-notes/Auto-release-notes.rst
index 18dee5c..84665cd 100644
--- a/docs/release/release-notes/Auto-release-notes.rst
+++ b/docs/release/release-notes/Auto-release-notes.rst
@@ -1,11 +1,7 @@
 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
 .. http://creativecommons.org/licenses/by/4.0
 .. SPDX-License-Identifier CC-BY-4.0
-.. (c) optionally add copywriters name
-
-.. contents::
-   :depth: 3
-   :local:
+.. (c) Open Platform for NFV Project, Inc. and its contributors
 
 
 ==================
@@ -29,14 +25,14 @@ OPNFV is a SDNFV system integration project for open-source components, which so
 In particular, OPNFV has yet to integrate higher-level automation features for VNFs and end-to-end Services.
 
 Auto ("ONAP-Automated OPNFV") will focus on ONAP component integration and verification with OPNFV reference platforms/scenarios, through primarily a post-install process in order to avoid impact to OPNFV installer projects. As much as possible, this will use a generic installation/integration process (not specific to any OPNFV installer's technology).
-* `ONAP <https://www.onap.org/`_, a Linux Foundation Project, is an open source software platform that delivers robust capabilities for the design, creation, orchestration, monitoring, and life cycle management of Software-Defined Networks (SDNs).
+
+* `ONAP <https://www.onap.org/`_ (a Linux Foundation Project) is an open source software platform that delivers robust capabilities for the design, creation, orchestration, monitoring, and life cycle management of Software-Defined Networks (SDNs).
 
 While all of ONAP is in scope, as it proceeds, the project will focus on specific aspects of this integration and verification in each release. Some example topics and work items include:
 
 * How ONAP meets VNFM standards, and interacts with VNFs from different vendors
 * How ONAP SDN-C uses OPNFV existing features, e.g. NetReady, in a two-layer controller architecture in which the upper layer (global controller) is replaceable, and the lower layer can use different vendor’s local controller to interact with SDN-C
-* What data collection interface VNF and controllers provide to ONAP DCAE, and (through DCAE), to closed-loop control functions such as Policy
-Tests which verify interoperability of ONAP automation/lifecycle features with specific NFVI and VIM features, as prioritized by the project with technical community and EUAG input. Examples include:
+* What data collection interface VNF and controllers provide to ONAP DCAE, and (through DCAE), to closed-loop control functions such as Policy Tests which verify interoperability of ONAP automation/lifecycle features with specific NFVI and VIM features, as prioritized by the project with technical community and EUAG input. Examples include:
 
   * Abstraction of networking tech/features e.g. through NetReady/Gluon
   * Blueprint-based VNF deployment (HOT, TOSCA, YANG)
@@ -44,8 +40,8 @@ Tests which verify interoperability of ONAP automation/lifecycle features with s
   * Policy (through DCAE)
   * Telemetry (through VES/DCAE)
 
-Initial areas of focus for Auto (in orange dotted lines; this scope can be expanded for future releases)
-It is understood that:
+Initial areas of focus for Auto (in orange dotted lines; this scope can be expanded for future releases). It is understood that:
+
 * ONAP scope extends beyond the lines drawn below
 * ONAP architecture does not necessarily align with the ETSI NFV inspired diagrams this is based upon
 
@@ -53,12 +49,14 @@ It is understood that:
 
 
 Testability:
+
 * Tests will be developed for use cases within the project scope.
 * In future releases, tests will be added to Functest runs for supporting scenarios.
 
 Auto’s goals include the standup and tests for integrated ONAP-Cloud platforms (“Cloud” here being OPNFV “scenarios” or other cloud environments). Thus, the artifacts would be tools to deploy ONAP (leveraging OOM whenever possible (starting with Beijing release of ONAP), and a preference for the containerized version of ONAP), to integrate it with clouds, to onboard and deploy test VNFs, to configure policies and closed-loop controls, and to run use-case defined tests against that integrated environment. OPNFV scenarios would be a possible component in the above.
 
 Auto currently defines three use cases: Edge Cloud, Resiliency Improvements, and Enterprise vCPE. These use cases aim to show:
+
 * increased autonomy of Edge Cloud management (automation, catalog-based deployment)
 * increased resilience (i.e. fast VNF recovery in case of failure or problem, thanks to closed-loop control)
 * enterprise-grade performance of vCPEs (certification during onboarding, then real-time performance assurance with SLAs and HA).
@@ -73,9 +71,11 @@ An ONAP instance (without DCAE) has been installed over Kubernetes on bare metal
 Onboarding of 2 VNFs is in progress: a vCPE and a vFW.
 
 Integration with Arm servers has started (exploring binary compatibility):
+
 * Openstack is currently installed on a 6-server pod of Arm servers
 * a Kubernetes cluster is installed there as well, for another instance of ONAP on Arm servers
 * An additional set of 14 Arm servers is in the process of being deployed at UNH, for increased capacity
+* LaaS (Lab as a Service) resources are also used (hpe16, hpe17, hpe19)
 
 Test case implementation for the three use cases has started.
 
@@ -109,14 +109,14 @@ Module version changes
 
 
 Document version changes
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~
 - There have been no version changes.
 
 
 Reason for version
-^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^
 Feature additions
-~~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~
 
 Initial release, with use case descriptions, release plan, and in-progress test cases and ONAP installations.
 
@@ -144,9 +144,8 @@ Initial release, with use case descriptions, release plan, and in-progress test
 +--------------------------------------+--------------------------------------+
 
 
-
 Bug corrections
-~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~
 
 **JIRA TICKETS:**
 
@@ -162,18 +161,19 @@ Bug corrections
 +--------------------------------------+--------------------------------------+
 
 Deliverables
-----------------
+============
 
 Software deliverables
-^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^
 
 Initial release: in-progress install scripts and test case implementations.
 
 
 Documentation deliverables
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Initial versions of:
+
 * User guide `OPNFV User and Configuration Guide <http://docs.opnfv.org/en/latest/release/userguide.introduction.html>`_
 * Release notes (this document)
 
@@ -183,7 +183,7 @@ Known Limitations, Issues and Workarounds
 =========================================
 
 System Limitations
-^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^
 
 * ONAP still to be validated for Arm servers
 * DCAE still to be validated for Kubernetes
@@ -191,7 +191,7 @@ System Limitations
 
 
 Known issues
-^^^^^^^^^^^^^^^
+^^^^^^^^^^^^
 
 None at this point.
 
@@ -210,7 +210,7 @@ None at this point.
 +--------------------------------------+--------------------------------------+
 
 Workarounds
-^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^
 
 None at this point.
 
-- 
cgit 1.2.3-korg