From 644f51f420a38b494a2c6af60ac5a8134c733931 Mon Sep 17 00:00:00 2001 From: Xuan Jia Date: Thu, 19 Oct 2017 14:17:18 +0800 Subject: E release note Change-Id: I1b5ecaf5e79df6800fdf44be797dbdbee75631a7 Signed-off-by: Xuan Jia (cherry picked from commit e5476e92b95b4cca079381ceac7e3a7b147c38a2) --- docs/development/ngvsrequirements/ngvs-requirements-document.rst | 2 ++ 1 file changed, 2 insertions(+) (limited to 'docs/development') 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. -- cgit 1.2.3-korg