blob: 62e611ff01ae9692b9509f0abb1a208c60fb90b2 (
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
|
Requirements from other OPNFV projects
--------------------------------------
We have created a questionnaire_ for collecting other projects requirements.
Please advertise it.
.. _questionnaire: https://docs.google.com/forms/d/11o1mt15zcq0WBtXYK0n6lKF8XuIzQTwvv8ePTjmcoF0/viewform?usp=send_form
Doctor Project
~~~~~~~~~~~~~~
.. <Malla> This scenario could be out of scope in Escalator project, but
having the option to support this should be better to align with
Doctor requirements.
The scope of Doctor project also covers maintenance scenario in which
1. The VIM administrator requests host maintenance to VIM.
2. VIM will notify it to consumer such as VNFM to trigger application level
migration or switching active-standby nodes.
3. VIM waits response from the consumer for a short while.
- VIM should send out notification of VM migration to consumer (VNFM)
as abstracted message like "maintenance".
- VIM could wait VM migration until it receives "VM ready to
maintenance" message from the owner (VNFM)
HA Project
~~~~~~~~~~
Multi-site Project
~~~~~~~~~~~~~~~~~~
- Escalator upgrade one site should at least not lead to the other site
API token validation failed.
|
