Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
During our discussions with NRENs and at workshops it became clear that there are OAV terms that are being used in different ways and in some cases with slightly different meaning and understanding. So in order to have a common basis we decided to identify a list of relevant OAV terms and add a short definition with a reference link (source) for each term as well as an acronym table with definitions of abbreviations. We tried to use standard-based definitions whenever we could find them and listed internal definitions in cases where no standard definitions were found.
Internal definitions are based on the consensus of all team members; to come to an agreed definition of all team members a terminology document was created with descriptions of the terms and an internal survey was conducted for final adjustments. Additional comments are welcome!
OAV Common Terms
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Glossary
OAV Terms | Definition and reference |
---|---|
API (Application Programming Interface) | An API is a set of commands, functions, protocols, and objects that programmers can use to create software or interact with an external system. Any data can be shared woth an application program interface. |
Automated service provisioning | Automated service provisioning is the ability to deploy an information technology or telecommunications service by using pre-defined procedures that are carried out electronically without requiring human intervention.
|
Automation | Processing abstracted service objects in a repeatable manner to yield the same result every time without human intervention.
|
Cgroups (control groups) | Cgroups are linux kernel mechanisms to restrict and measure resource allocations to each process group. Using cgroups, you can allocate resources such as CPU time, network, and memory. |
Control plane | The control plane is responsible for processing a number of different control protocols that may affect the forwarding table, depending on the configuration and type of network device. These control protocols are jointly responsible for managing the active topology of the network.
|
Cross-domain data services | Data services that are delivered across multiple administrative, information or technological domains that allow data sharing among authorized consumers in different domains.
|
Data center interconnect (DCI) | Data center interconnect (DCI) is a segment of the networking market that focuses on the technology used to link two or more data centers so the facilities can share resources. |
Data plane | The data plane (sometimes known as the user plane, forwarding plane, carrier plane or bearer plane) is the part of a network that carries user traffic from one interface to another. |
Domain | A collection of network infrastructure under the administrative control of the same organisation.
|
Federated orchestration | Service orchestration performed by multiple autonomous management domains, to effectively allow services to span across several providers.
|
Hierarchical orchestration | Orchestration decomposed into one or more hierarchical interactions where parts of the service are delegated to a subordinate orchestrator.
|
Management | The processes aiming at fulfilment, assurance, and billing of services, network functions, and resources in both physical and virtual infrastructure including compute, storage, and network resources.
|
Management domain | A collection of physical or functional elements under the control of an entity, aiming at fulfilment, assurance, and billing of services, network functions, and resources in both physical and virtual infrastructure.
|
Microservices | Microservices is an approach to software architecture that builds a large, complex application from multiple small components that each perform a single function, such as authentication, notification, or payment processing. Each microservice is a distinct unit within the software development project, with its own code base, infrastructure, and database. The microservices work together, communicating through web APIs or messaging queues to respond to incoming events. |
NFV | Network Function Virtualisation (NFV) is a network architecture concept that uses virtualization to classify entire classes of network node functions into building blocks that may connect, or chain together, to create communication services. More specifically, it is the deployment of software implementations of traditional network functions (e.g. load balancers, firewalls, office switches/routers) on virtualized infrastructure rather than on function-specific specialized hardware devices.
|
NFV-MANOArchitectural Framework(Network Functions Virtualisation Management and Orchestration Architectural Framework) | Management and orchestration (MANO) is a key element of the ETSI network functions virtualization (NFV) architecture. MANO is an architectural framework that coordinates network resources for cloud-based applications and the lifecycle management of virtual network functions (VNFs) and network services. As such, it is crucial for ensuring rapid, reliable NFV deployments at scale. MANO includes the following components: the NFV orchestrator (NFVO), the VNF manager (VNFM), and the virtual infrastructure manager (VIM). Collection of all functional blocks (including those in NFV-MANO category as well as others that interwork with NFV-MANO), data repositories used by these functional blocks, and reference points and interfaces through which these functional blocks exchange information for the purpose of managing and orchestrating NFV.
|
NFVO(Network Functions Virtualisation 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.
|
Network controller | Functional block that centralizes some or all of the control and management functionality of a network domain and may provide an abstract view of its domain to other functional blocks via well-defined interfaces.
|
Network function | Network Function (NF) – a functional building block within a network infrastructure, which has well-defined external interfaces and a well-defined functional behaviour.
|
Network function disaggregation (NFD) | Defines the evolution of switching and routing appliances from proprietary, closed hardware and software sourced from a single vendor, towards totally decoupled, open components which are combined to form a complete switching and routing device. |
Network resource | Physical or logical network component of hardware, software or data in the data, control or management planes.
|
Network slicing | Network slicing is a specific form of virtualisation that allows multiple logical networks to run on top of a shared physical network infrastructure. |
OpenStack | Open source software for creating private and public clouds. OpenStack software controls large pools of compute, storage, and networking resources throughout a data center, managed through a dashboard or via the OpenStack API. |
Open virtual network (OVN) | Open Virtual Network (OVN) is an Open vSwitch-based software-defined networking (SDN) solution for supplying network services to instances. |
Open vSwitch (OVS) | Open source multilayer virtual switch that supports standard interfaces and protocols.
|
SDN | A programmable network approach that supports the separation of control and forwarding planes via standardized interfaces.
|
Self-configuration | A process by which computer systems or networks automatically adapt their own configuration of components without human direct intervention.
|
Service chaining (NFV) | Network service chaining, also known as service function chaining (SFC) is a capability that uses software-defined networking (SDN) capabilities to create a service chain of connected network services (such as L4-7 like firewalls, network address translation [NAT], intrusion protection) and connects them in a virtual chain. This capability can be used by network operators to set up suites or catalogs of connected services that enable the use of a single network connection for many services, with different characteristics. |
Switch abstraction interface (SAI) | Definition of the API to provide a vendor-independent way of controlling forwarding elements, such as a switching ASIC, an NPU or a software switch in a uniform manner.
|
Virtual eXtensible Local Area Network (VXLAN) | Virtual eXtensible Local Area Network (VXLAN) enables the encapsulation of Ethernet frames inside UDP packets with a designated UDP destination port (4789). VXLAN allows users to overlay L2 networks on top of existing L3 networks. In the data center, it is commonly used to stretch an L2 network across multiple racks. |
Virtual routing and forwarding (VRF) | Virtual Routing and Forwarding is a layer 3 abstraction, which provides a separate routing table for each instance, usually this is done by adding some sort of VRFID to the routing table lookup.
|
Virtualisation | Abstraction of service objects to make them appear generic, i.e. disassociated from the underlying hardware implementation specifics.
|
GLOSSARY
Abbreviation/ Acronym | Description/Definition |
---|---|
BSS | Business Support System |
CBP | Ciena Blue Planet |
CNI | Container Network Interface |
CSP | Communications Service Provider |
DC | Data Centre |
DCN | Data Communication Network |
DTN | Data Transfer Node |
ETSI | European Telecommunications Standards Institute |
EVPN | Ethernet VPN |
FRR | Free Range Routing |
Geneve | Generic Network Virtualisation Encapsulation |
GRE | Generic Routing Encapsulation |
GVM | Generalised Virtualisation Model |
IaC | Infrastructure as Code |
IEEE | Institute of Electrical and Electronics Engineers |
IETF | Internet Engineering Task Force |
ITU | International Telecommunication Union |
K8s | Kubernetes |
MANO | Management and Orchestration |
MDSO | Multi-Domain Service Orchestration |
MEF | Metro Ethernet Forum |
NaaS | Network-as-a-Service |
NaC | Network as Code |
NAO | Network Automation and Orchestration |
NCO | Network Controls and Orchestration |
NEP | Network Equipment Providers |
NETCONF | Network Configuration Protocol |
NFV | Network Function Virtualisation |
NFVI | Network Function Virtualisation Infrastructure |
NFV-O | Network Function Virtualisation Orchestrator |
NGN | Next Generation Network |
NREN | National Research and Education Network |
NRO | Network Resource Optimisation |
NS | Network Service |
NSA | Network Service Agent |
NSI | Network Service Interface |
NVGRE | Network Virtualisation over GRE (Generic Routing Encapsulation) |
OAV | Orchestration, Automation and Virtualisation |
OCP | Open Compute Project |
ODL | OpenDaylight |
OESS | Open Exchange Software Suite |
OGF | Open Grid Forum |
ONAP | Open Networking Automation Platform |
ONOS | Open Network Operating System |
OPNFV | Open Platform for NFV Project |
OSM | Open Source MANO |
OSS | Operations Support System |
OVN | Open Virtual Network |
OVS | Open vSwitch |
PaaS | Platform as a Service |
R&D | Research and Development |
R&E | Research & Education |
SAI | Switch Abstraction Interface |
SDDC | Software-Defined Data Center |
SDN | Software Defined Network |
SD-WAN | Software-Defined networking in a Wide Area Network (WAN) |
SDX | Software-Defined Exchange |
SFC | Service Function Chaining (also known as Network Service Chaining) |
SPA | Service Provider Architecture |
STF | Service and Technology Forum |
STT | Stateless Transport Tunneling |
TMF | TM Forum |
VCDN | Virtual Content Delivery Network |
VIM | Virtual Infrastructure Management |
VM | Virtual Machine |
VNF | Virtual Network Function |
VNFM | Virtualised Network Function Manager |
VPN | Virtual Private Network |
VPP | Vector Packet Processing |
VRF | Virtual Routing Function |
VSI | Virtual Switch Instance |
VTEP | Virtual Tunnel End Point |
VXLAN | Virtual Extensible LAN |
XaaS | Anything as a Service |
XDP | eXpress Data Path |
ZTP | Zero Touch Provisioning |