diff options
| author |   Gergely Csatari <gergely.csatari@nokia.com> | 2018-02-01 10:17:12 +0100 |
|---|---|---|
| committer | Gergely Csatari <gergely.csatari@nokia.com> | 2018-02-01 13:27:40 +0100 |
| commit | 0944cc15c038b1c4424bedae581ce40eb4644326 (patch) | |
| tree | eedbe607efa8305a07aa55d1213953f42c0b875d /docs/development/ngvsrequirements | |
| parent | 5ed69809f33e546bf3e06dc285a90e0818c89ceb (diff) | |
Error corrections and architecture option updates
Correction of some errors which are permitting a succesfull build
in the master following these descriptions: http://docs.opnfv.org/en/latest/how-to-use-docs/include-documentation.html#individual-project-documentation
Moving the architecture options to the Container4NFV wiki and
leaving only a reference here.
Change-Id: I7b4debc90997f8812a5681daa8bfa19f90724cef
Signed-off-by: Gergely Csatari <gergely.csatari@nokia.com>
Diffstat (limited to 'docs/development/ngvsrequirements')
| -rw-r--r-- | docs/development/ngvsrequirements/ngvs-requirements-document.rst | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/docs/development/ngvsrequirements/ngvs-requirements-document.rst b/docs/development/ngvsrequirements/ngvs-requirements-document.rst index d2c775e..793708f 100644 --- a/docs/development/ngvsrequirements/ngvs-requirements-document.rst +++ b/docs/development/ngvsrequirements/ngvs-requirements-document.rst @@ -2,7 +2,7 @@ .. License.http://creativecommons.org/licenses/by/4.0 .. (c) Xuan Jia (China Mobile) -========================================================================== +=========================================================================== OpenRetriever Next Gen VIM & Edge Computing Scheduler Requirements Document =========================================================================== @@ -44,15 +44,15 @@ At a high level, we believe the VIM scheduler must: - Support legacy and event-driven scheduling - By legacy scheduling we mean scheduling without any trigger (see above) -i.e. the current technique used by schedulers such as OpenStack Nova. + 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. + 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. + run on top e.g. FaaS (similar to AWS Lambda) etc. +----------------------------------------------------------------------------------------+ | Serverless vs. FaaS vs. Event-Driven Terminology | @@ -257,6 +257,7 @@ Multiple compute types | | - Support shared storage (e.g. OpenStack | | | Cinder, K8s volumes etc.) | +----------------------------------------+-----------------------------------------------+ + .. [1] Intel EPA includes DPDK, SR-IOV, CPU and NUMA pinning, Huge Pages etc. |