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/userguide/UC01-feature.userguide.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/userguide/UC01-feature.userguide.rst')
| -rw-r--r-- | docs/release/userguide/UC01-feature.userguide.rst | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/docs/release/userguide/UC01-feature.userguide.rst b/docs/release/userguide/UC01-feature.userguide.rst index ea02bad..5b5edb8 100644 --- a/docs/release/userguide/UC01-feature.userguide.rst +++ b/docs/release/userguide/UC01-feature.userguide.rst @@ -17,9 +17,12 @@ Description This use case aims at showcasing the benefits of using ONAP for autonomous Edge Cloud management. -A high level of automation of VNF lifecycle event handling after launch is enabled by ONAP policies and closed-loop controls, which take care of most lifecycle events (start, stop, scale up/down/in/out, recovery/migration for HA) as well as their monitoring and SLA management. +A high level of automation of VNF lifecycle event handling after launch is enabled by ONAP policies and closed-loop +controls, which take care of most lifecycle events (start, stop, scale up/down/in/out, recovery/migration for HA) as +well as their monitoring and SLA management. -Multiple types of VNFs, for different execution environments, are first approved in the catalog thanks to the onboarding process, and then can be deployed and handled by multiple controllers in a systematic way. +Multiple types of VNFs, for different execution environments, are first approved in the catalog thanks to the onboarding +process, and then can be deployed and handled by multiple controllers in a systematic way. This results in management efficiency (lower control/automation overhead) and high degree of autonomy. |