diff options
| author |   Martin Klozik <martin.klozik@tieto.com> | 2018-05-30 09:48:03 +0200 |
|---|---|---|
| committer | Martin Klozik <martin.klozik@tieto.com> | 2018-05-30 10:22:03 +0200 |
| commit | bf21f3086791419abd713757ec85d0b9a77312d5 (patch) | |
| tree | 99033ca7e184b8698d2f54d508fe54573637ef56 /docs/release/configguide/Auto-featureconfig.rst | |
| parent | f19ad7f768a1fd6f7523a8e418b30bce2088ebce (diff) | |
docs: Fix long lines
OPNFVDOCS scripts set max line length to 240 chars. This patch
shortens long lines to avoid rst validation warnings during Auto
docs generation.
Change-Id: I124e3ea3aa04bc7fc8c2f5cf25ce9c75fdcef330
Signed-off-by: Martin Klozik <martin.klozik@tieto.com>
Diffstat (limited to 'docs/release/configguide/Auto-featureconfig.rst')
| -rw-r--r-- | docs/release/configguide/Auto-featureconfig.rst | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/docs/release/configguide/Auto-featureconfig.rst b/docs/release/configguide/Auto-featureconfig.rst index af16a9b..fe51be3 100644 --- a/docs/release/configguide/Auto-featureconfig.rst +++ b/docs/release/configguide/Auto-featureconfig.rst @@ -55,14 +55,19 @@ server with the OpenStack instance. .. image:: auto-installTarget-initial.jpg -The OpenStack instance running VNFs may need to be configured as per ONAP expectations, for example creating instances of ONAP projects/tenants, users, security groups, networks (private, public), connected to the Internet by a Router, and making sure expected VM images and flavors are present. A script (using OpenStack SDK, or OpenStack CLI, or even OpenStack Heat templates) would populate the OpenStack instance, as illustrated below: +The OpenStack instance running VNFs may need to be configured as per ONAP expectations, for example creating +instances of ONAP projects/tenants, users, security groups, networks (private, public), connected to the +Internet by a Router, and making sure expected VM images and flavors are present. A script (using OpenStack +SDK, or OpenStack CLI, or even OpenStack Heat templates) would populate the OpenStack instance, as illustrated below: .. image:: auto-OS-config4ONAP.png Jenkins (or more precisely JJB: Jenkins Job Builder) will be used for Continuous Integration in OPNFV releases, to ensure that the latest master -branch of Auto is always working. The first 3 tasks in the pipeline would be: install OpenStack instance via OPNFV installer (Fuel/MCP for example), configure the OpenStack instance for ONAP, install ONAP (using the OpenStack instance network IDs in the ONAP YAMP file). +branch of Auto is always working. The first 3 tasks in the pipeline would be: install OpenStack instance via OPNFV +installer (Fuel/MCP for example), configure the OpenStack instance for ONAP, install ONAP (using the OpenStack +instance network IDs in the ONAP YAMP file). Moreover, Auto will offer an API, which can be imported as a module, and can be accessed for example by a web application. The following diagram shows the planned structure for the Auto Git repository, |