1 Requirements from other OPNFV projects
2 --------------------------------------
4 | We have created a questionnaire for collecting other projects
6 (https://docs.google.com/forms/d/11o1mt15zcq0WBtXYK0n6lKF8XuIzQTwvv8ePTjmcoF0/viewform?usp=send_form),
8 | ==[hujie] Can we force other OPNFV projects to complete the survey by
9 using JIRA dependence?==
14 | ==Note: This scenario could be out of scope in Escalator project, but
15 having the option to support this should be better to align with
16 Doctor requirements.==
17 | The scope of Doctor project also covers maintenance scenario in which
18 1) the VIM administorator requests host maintenance to VIM, 2) VIM
19 will notifiy it to consumer such as VNFM to trigger application level
20 migration or switching active-standby nodes, and 3) VIM waits responce
21 from the consumer for a short while.
23 - VIM should send out notification of VM migration to consumer (VNFM)
24 as abstracted message like "maintenance".
25 - VIM could wait VM migration until it receives "VM ready to
26 maintenance" message from the owner (VNFM)
34 - Escalator upgrade one site should at least not lead to the other site
35 API token validation failed.