diff options
| -rw-r--r-- | docs/development/ngvsrequirements/ngvs-requirements-document.rst | 2 | ||||
| -rw-r--r-- | docs/release/release-notes/release-notes.rst | 11 |
2 files changed, 13 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. diff --git a/docs/release/release-notes/release-notes.rst b/docs/release/release-notes/release-notes.rst new file mode 100644 index 0000000..51711f8 --- /dev/null +++ b/docs/release/release-notes/release-notes.rst @@ -0,0 +1,11 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International +.. License. http://creativecommons.org/licenses/by/4.0 +.. (c) Xuan Jia (China Mobile) + +================================== +Container4NFV E release Notes +================================== +1. Gap analysis for openstack,kubernetes,opnfv installer +2. Container architecture options +3. Joid could support Kubernetes +4. Using vagrant tool to setup an env with DPDK enabled. |