diff options
author | Gerald Kunzmann <kunzmann@docomolab-euro.com> | 2017-02-14 15:38:29 +0000 |
---|---|---|
committer | Gerald Kunzmann <kunzmann@docomolab-euro.com> | 2017-02-16 14:41:46 +0000 |
commit | d0b22e1d856cf8f78e152dfb6c150e001e03dd52 (patch) | |
tree | 0c3b7af828967d5014c2272675560410fceb6e4d /docs/requirements/glossary.rst | |
parent | e171b396ce87322f2dc5ef0719419144774e43d7 (diff) |
Update docs structure according to new guidelines in https://wiki.opnfv.org/display/DOC
Change-Id: I1c8c20cf85aa46269c5bc369f17ab0020862ddc5
Signed-off-by: Gerald Kunzmann <kunzmann@docomolab-euro.com>
Diffstat (limited to 'docs/requirements/glossary.rst')
-rw-r--r-- | docs/requirements/glossary.rst | 89 |
1 files changed, 0 insertions, 89 deletions
diff --git a/docs/requirements/glossary.rst b/docs/requirements/glossary.rst deleted file mode 100644 index 2c82b37f..00000000 --- a/docs/requirements/glossary.rst +++ /dev/null @@ -1,89 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 - -**Definition of terms** - -Different SDOs and communities use different terminology related to -NFV/Cloud/SDN. This list tries to define an OPNFV terminology, -mapping/translating the OPNFV terms to terminology used in other contexts. - - -.. glossary:: - - ACT-STBY configuration - Failover configuration common in Telco deployments. It enables the - operator to use a standby (STBY) instance to take over the functionality - of a failed active (ACT) instance. - - Administrator - Administrator of the system, e.g. OAM in Telco context. - - Consumer - User-side Manager; consumer of the interfaces produced by the VIM; VNFM, - NFVO, or Orchestrator in ETSI NFV [ENFV]_ terminology. - - EPC - Evolved Packet Core, the main component of the core network architecture - of 3GPP's LTE communication standard. - - MME - Mobility Management Entity, an entity in the EPC dedicated to mobility - management. - - NFV - Network Function Virtualization - - NFVI - Network Function Virtualization Infrastructure; totality of all hardware - and software components which build up the environment in which VNFs are - deployed. - - S/P-GW - Serving/PDN-Gateway, two entities in the EPC dedicated to routing user - data packets and providing connectivity from the UE to external packet - data networks (PDN), respectively. - - Physical resource - Actual resources in NFVI; not visible to Consumer. - - VNFM - Virtualized Network Function Manager; functional block that is - responsible for the lifecycle management of VNF. - - NFVO - Network Functions Virtualization Orchestrator; functional block that - manages the Network Service (NS) lifecycle and coordinates the - management of NS lifecycle, VNF lifecycle (supported by the VNFM) and - NFVI resources (supported by the VIM) to ensure an optimized allocation - of the necessary resources and connectivity. - - VIM - Virtualized Infrastructure Manager; functional block that is responsible - for controlling and managing the NFVI compute, storage and network - resources, usually within one operator's Infrastructure Domain, e.g. - NFVI Point of Presence (NFVI-PoP). - - Virtual Machine (VM) - Virtualized computation environment that behaves very much like a - physical computer/server. - - Virtual network - Virtual network routes information among the network interfaces of VM - instances and physical network interfaces, providing the necessary - connectivity. - - Virtual resource - A Virtual Machine (VM), a virtual network, or virtualized storage; - Offered resources to "Consumer" as result of infrastructure - virtualization; visible to Consumer. - - Virtual Storage - Virtualized non-volatile storage allocated to a VM. - - VNF - Virtualized Network Function. Implementation of a Network Function that - can be deployed on a Network Function Virtualization Infrastructure - (NFVI). - -.. - vim: set tabstop=4 expandtab textwidth=80: |