diff options
| author |   Xuan Jia <jason.jiaxuan@gmail.com> | 2017-10-19 14:17:18 +0800 |
|---|---|---|
| committer | Xuan Jia <jason.jiaxuan@gmail.com> | 2017-10-19 14:30:05 +0800 |
| commit | e5476e92b95b4cca079381ceac7e3a7b147c38a2 (patch) | |
| tree | 663bc80df13a9cd198e6c7a2837f1b916c223204 /docs/development/ngvsrequirements | |
| parent | 4b7b5289169f5790a9cbdd65edf01cd3f372ee99 (diff) | |
E release note
Change-Id: I1b5ecaf5e79df6800fdf44be797dbdbee75631a7
Signed-off-by: Xuan Jia <jason.jiaxuan@gmail.com>
Diffstat (limited to 'docs/development/ngvsrequirements')
| -rw-r--r-- | docs/development/ngvsrequirements/ngvs-requirements-document.rst | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/development/ngvsrequirements/ngvs-requirements-document.rst b/docs/development/ngvsrequirements/ngvs-requirements-document.rst index 878176c..d2c775e 100644 --- a/docs/development/ngvsrequirements/ngvs-requirements-document.rst +++ b/docs/development/ngvsrequirements/ngvs-requirements-document.rst @@ -45,10 +45,12 @@ At a high level, we believe the VIM scheduler must: - By legacy scheduling we mean scheduling without any trigger (see above) i.e. the current technique used by schedulers such as OpenStack Nova. + - By event-driven scheduling we mean scheduling with a trigger (see above). We do not mean that the unikernel or container that is going to run the VNF is already running . The instance is started and torn-down in response to traffic. The two step process is transparent to the user. + - More specialized higher level schedulers and orchestration systems may be run on top e.g. FaaS (similar to AWS Lambda) etc. |