diff options
Diffstat (limited to 'doc/08-Requirements_from_other_OPNFV_Project.rst')
| -rw-r--r-- | doc/08-Requirements_from_other_OPNFV_Project.rst | 40 |
1 files changed, 40 insertions, 0 deletions
diff --git a/doc/08-Requirements_from_other_OPNFV_Project.rst b/doc/08-Requirements_from_other_OPNFV_Project.rst new file mode 100644 index 0000000..62e611f --- /dev/null +++ b/doc/08-Requirements_from_other_OPNFV_Project.rst @@ -0,0 +1,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. |