summaryrefslogtreecommitdiffstats
path: root/docs/release/userguide/UC01-feature.userguide.rst
blob: 5cf38e11c0895146f4ee6521785acb589652753a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
.. 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) Open Platform for NFV Project, Inc. and its contributors


======================================
Auto User Guide: Use Case 1 Edge Cloud
======================================

This document provides the user guide for Fraser release of Auto,
specifically for Use Case 1: Edge Cloud.


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.

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.


Preconditions:

#. hardware environment in which Edge cloud may be deployed
#. an Edge cloud has been deployed and is ready for operation
#. ONAP has been deployed onto a Cloud, and is interfaced (i.e. provisioned for API access) to the Edge cloud



Main Success Scenarios:

* lifecycle management - stop, stop, scale (dependent upon telemetry)

* recovering from faults (detect, determine appropriate response, act); i.e. exercise closed-loop policy engine in ONAP

  * verify mechanics of control plane interaction

* collection of telemetry for machine learning


Details on the test cases corresponding to this use case:

* Environment check

  * Basic environment check: Create test script to check basic VIM (OpenStack), ONAP, and VNF are up and running

* VNF lifecycle management

  * VNF Instance Management: Validation of VNF Instance Management which includes VNF instantiation, VNF State Management and termination

  * Tacker Monitoring Driver (VNFMonitorPing):

    * Write Tacker Monitor driver to handle monitor_call and based on return state value create custom events
    * If Ping to VNF fails, trigger below events

      * Event 1 : Collect failure logs from VNF
      * Event 2 : Soft restart/respawn the VNF

  * Integrate with Telemetry

    * Create TOSCA template policies to implement ceilometer  data collection service
    * Collect CPU utilization data, compare with threshold, and perform action accordingly (respawn, scale-in/scale-out)



Test execution high-level description
=====================================

<TBC>