AAF: Application Authorization Framework
- fine-grained authorization library and service; one of the ONAP Common Services
AAI = A&AI: Active and Available Inventory (component of ONAP runtime)
Real-time views of Resources, Services, Products, Customer Subscriptions, and their relationships
AID: Architecture Integration Document
Akka: handles clustering (used OpenDaylight controllers) akka.io
AJSC: see JSC
Amsterdam: Code name for the first release of ONAP
APPC (formerly APP-C): Application Controller (part of ONAP)
- handles the life cycle management of Virtual Network Functions (VNFs)
Beijing: Code name for the second release of ONAP
BPEL: Business Process Execution Language (OASIS Standard)
- XML-based language that allows Web services in a service-oriented architecture (SOA) to interconnect and share data.
BPMN: Business Process Model and Notation (Wikipedia) or Business Process Management Notation (ONAP.pdf)
- graphical representation for specifying business processes
BRMS: Business Rules Management System
BSS: Business Support System
CDAP: Cask Data Application Platform
- open source framework to build and deploy data applications on Apache™ Hadoop® (CDAP.io site)
Chef:
CI/CD: Continuous Integration / Continuous Delivery
- continuous integration (CI) is the practice of merging all developer working copies to a shared mainline several times a day (Wikipedia)
- continuous delivery (CD) is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time (Wikipedia)
CLAMP: Closed Loop Automation Management Platform
CMA: Change Management Application (within ONAP)
Congress:
Controller:
- manages the state of an Application, Infrastructure, or Network resource
- single service/network domain scope
CSAR: Cloud Service ARchive (link)
- a package defined by OASIS TOSCA. It is a ZIP file that includes a TOSCA template of a Network Service, and all the scripts or files that a VNF needs for the lifecycle from creation to termination.
DAO: Data Access Object (Wikipedia)
- an object that provides an abstract interface to some type of database or other persistence mechanism
DCAE: Data Collection, Analytics and Events (component of ONAP runtime)
DDoS: Distributed Denial-of-Service attack (Wikipedia)
DG: Directed Graph
- in ONAP, it is the XML output of DG Builder. Directed graphs are used to encapsulate service logic.
DG Builder: Directed Graph Builder
- This is an ONAP-customized version of Node-RED. It is a graphic editor used to generate the resulting XML files that are fed into SLI.
Disconnect: (Vendor specific)
- disconnecting an existing connection sometimes called a delete
- Total Disconnect - Disconnect all ports and VLAN from the Database (SDNC) and Network (NCS)
- VLAN Disconnect - Disconnect an active vlan from Database (SDNC) and Network (NCS)
- Soft Disconnect - Disable the interface for traffic to flow through without deleting the interface from the network
DLUX:
- the OpenDaylight community GUI (DLUX documentation)
- typically not needed for ONAP development
DMaaP: Data Movement as a Platform
- a set of common services provided by ONAP, including a Message Router, Data Router, and a Data Bus Controller
DME: Direct Messaging Engine (common service within ONAP)
DNS: Domain Name System
Docker:
- containerization platform (link)
DPDK: Data Plane Development Kit
- a set of libraries and drivers for fast packet processing (dpdk.org). Its optimizations could be used by VNFs requiring high packet processing speeds.
Drools: Red Hat's Business Rules Management System solution https://www.drools.org/
EELF: Event and Error-Logging Framework (common service within ONAP)
EMS: Element Management System (Wikipedia)
ETSI: European Telecommunications Standards Institute
EUAG: ONAP End User Advisory Group, i.e. telecom operators (https://wiki.lfnetworking.org/pages/viewpage.action?pageId=2916362)
FCAPS: Fault Configuration Accounting Performance Security
GBP: Group-Based Policy (https://wiki.openstack.org/wiki/GroupBasedPolicy)
Heat:
HDFS: Hadoop Distributed File System
Honeycomb:
- Java-based agent that runs on the same host as a Vector Packet Processor (VPP); manages the VPP by translating NETCONF/YANG or RESTCONF (link)
- used by vFirewall demonstration service within ONA
HPA: Hardware Platform Awareness
HTTP: HyperText Transfer Protococol
IAM/IDAM: Identity and Access Management
- security and business discipline that "enables the right individuals to access the right resources at the right times and for the right reasons" (Wikipedia)
ICE: Incubation and Certification Environment
- for vendors and 3rd parties to develop Virtual Network Functions and other Resources using ONAP and a network cloud
IDS: Intrusion Detection System (Wikipedia)
IETF: Internet Engineering Task Force (http://www.ietf.org)
- a standards body that creates the internet protocol standards.
IKE: Internet Key Exchange (Wikipedia)
IPS: Intrusion Prevention System (Wikipedia)
IPSEC: Internet Protocol Security (Wikipedia)
JAR: Java ARchive (Wikipedia)
- a package file format typically used to aggregate many Java class files and associated metadata and resources (text, images, etc.) into one file for distribution. A JAR file is built on the ZIP format and typically has a .jar file extension.
JSC: Java Service Container: (formerly AJSC)
- Service container library and framework that is provided as part of Common Frameworks open source, separately from ONAP
JSON: JavaScript Object Notation
Karaf:
- a container, sponsored by Apache, fully supporting OSGI with lots of extras (Apache page)
LCM: Life Cycle Management
LRM: Local Resource Monitor
M0: Release Kick-off milestone. See also Release Lifecycle
M1: Release Planning milestone. See also Release Lifecycle
M2: Release Functionality Freeze milestone. See also Release Lifecycle
M3: Release API Freeze milestone. See also Release Lifecycle
M4: Release Code Freeze milestone. See also Release Lifecycle
MACD: (Vendor specific) Move Add Change Delete/Disconnect
- an existing connection is being changed; thus, MACDs are also called change orders. The connection will have both operational and configuration data.
MANO: MANagement and Organization of NFV
MD-SAL: Model Driven Service Abstraction Layer
MR: Message Router (a Common Service of ONAP)
MOP: Method of Procedure
- set of deployment instructions
MOTS: Mechanized Operations Tracking System
MSB: Microservice Bus
MSO: Master Service Orchestrator (component of ONAP runtime)
- automates activities, tasks, rules and policies needed for on-demand creation, modification or removal of network, application or infrastructure services
MVP: Minimum Viable Product
NAI: Network Artificial Intelligence
NANCSP: Network Cloud Service Provider
NEP: Network Equipment Provider
NETCONF: Network Configuration Protocol (Wikipedia)
network cloud:
- a compute, storage, and network virtualization environment where the network integration and control scope extends beyond the data center
NFV: Network Function Virtualization (Wikipedia)
- a network architecture concept that uses the technologies of IT virtualization to virtualize entire classes of network node functions into building blocks that may connect, or chain together, to create communication services
- decouples the network functions, such as DNS, Caching, etc., from proprietary hardware appliances, so they can run in software to accelerate service innovation and provisioning, particularly within service provider environments.
- https://www.sdxcentral.com/nfv/definitions/which-is-better-sdn-or-nfv/
NFVI: network functions virtualization infrastructure
NOD: Network On Demand
Node-RED:
- open source project by IBM to graphically create flows that configure devices. Projects include managing a raspberry pi. (official docs)
NS: Network Services
NS: (Vendor Specific) New Start
- a new connection is being setup for the first time. There will only be configuration data until it is activated.
OA&M: Operations, Administration and Management
OASIS:
- Nonprofit consortium that drives the development, convergence and adoption of open standards for the global information society.
Offer:
- in ONAP, a bundling of Products with specific Marketing configurations
OCX/OMX - AT&T system that sends service orders to SO API Handler to trigger its activities
OMF: Operational Management Framework (of ONAP)
OMSA: ONAP Microservice Architecture
OOF: ONAP Optimization Framework
OpenDaylight = ODL
ONAP: Open-source Enhanced Control, Orchestration, Management, and Policy
OpenStack:
- a free and open-source software platform for creating private and public clouds (compute, network, and storage facilities) (https://www.openstack.org/)
- mostly deployed as an infrastructure-as-a-service (IaaS). The software platform consists of interrelated components that control hardware pools of processing, storage, and networking resources throughout a data center. Users either manage it through a web-based dashboard, through command-line tools, or through a RESTful API.
OOM: ONAP Operations Manager
OPNFV: Open Platform for NFV Project
Orchestration:
- the definition and execution of workflows or processes to manage the completion of a task
- will not involve human intervention/decision/guidance in the vast majority of cases
OSS: Operations Support System
OSGI:
- a modular system and a service platform for the Java programming language that implements a complete and dynamic component model (OpenDaylight uses this) (Wikipedia)
PAP: Policy Administration Point (ONAP)
PCE: Path Computation and Element (ONAP)
PDP-x: Policy Decision Point - XACML (ONAP)
PDP-d: Policy Decision Point - Drools (ONAP)
PO: Platform Orchestrator
PNF: Physical Network Function
- a network function that runs in a hardware appliance
Portal:
- ONAP user interface; provides access to design, analytics and operational control/administration via a common role-based menu or dashboard. Includes SDK to drive UI consistency.
Product:
- in ONAP, a composition of Services
RCA: Root Cause Analysis
RCT: Reference Connection Tool
Recipe:
- within Chef, the most fundamental configuration element (see the Style Guide)
Resource:
- in ONAP, a fundamental capability
REST: REpresentational State Transfer (Wikipedia)
RESTCONF: REST + NETCONF
- IETF draft that describes how to map a YANG specification to a RESTful interface. Read the IETF draft and see its current status here or here.
RO: Resource Orchestrator
RPC: Remote Procedure Call
SDC: Service Design and Creation (component of ONAP for visual modeling and design)
SDN: Software-Defined Networking
SDNC (formerly SDN-C): Software Defined Network Controller (part of ONAP)
- its operators accept Comma Separated Value files describing networks
SDN-GP: Software Defined Network - Global Platform
Service:
- in ONAP, a composition of Resources
SLA: Service Level Agreement
- a contract between a service provider (either internal or external) and the end user that defines the level of service expected from the service provider. SLAs are output-based in that their purpose is specifically to define what the customer will receive.
SLI: Service Logic Interpreter
- within the Application Controller (APP-C), executes Directed Graphs (DGs)
SME: Subject Matter Expert
SMTP: Simple Mail Transfer Protocol
SNMP: Simple Network Management Protocol
SO: Service Orchestrator (Project)
SOT: Source Of Truth
- external system where data object originates
SR-IOV: Single-Root Input/Output Virtualization (Wikipedia)
- a network interface that allows the isolation of the PCI Express resources for manageability and performance reasons
SSH: Secure Shell
SSL: Secure Sockets Layer (Wikipedia), precursor to TLS
SUPP: (Vendor Specific) short for supplement, changing a connection before activation
TCP: Transmission Control Protocol
TEM: Telecom Electronics Manufacturer
tenant:
- a group of users who share a common access with specific privileges to a software instance on a server (Wikipedia). This terminology is used in OpenStack
TLS: Transport Layer Security (Wikipedia), standardized replacement for Secure Sockets Layer (SSL)
TOSCA: Topology and Orchestration Specification for Cloud Applications (OASIS spec)
TPS: Transactions Per Second
TSC: Technical Steering Committee. Establishes work flows and procedures, criteria for contributors and committers, and any additional roles and responsibilities required on ONAP projects.
UEB: An event bus interface that has been replaced by DMaaP.
vCE: virtual CE (Customer Edge) router (an example VNF)
vDNS: Virtual Domain Name Server (an example VNF)
VES: Virtual function Event Stream
- OPNFV proposed standard common event data model for telemetry-related data (PowerPoint of proposal)
- used by vFirewall ONAP demonstration VNF to report heartbeats, faults, measurements, etc.
- DCAE has a VES Collector
vF: Virtual Firewall (an example VNF)
VF: Virtual Function
- an entity that may be modeled and subsequently instantiated, which takes on the responsibility of handling a particular function that when instantiated, will run on one or more virtual machines within the cloud.
- in SDC, a VF is equivalent to a Resource
VFC: Virtual Function Controller (the ONAP project)
VFC: Virtual Function Component (Resource Onboarding)
- software component of a VF that is packaged into one or more images and is capable of running in its own container
in SDC, a VFC is configured as a sub-component of a VSP.
the smallest granularity of function visible to ONAP designers
vfModule: Virtual Function Module
- A Heat stack that defines the compute, network, licensing and other Heat resources needed to instantiate one or more VFCs associated with a VNF. In a VNF, one vfModule is typically designated as a base module. Any resources defined in the base module Heat template can be exposed to all other vfModules by declaring their resource UUID as Heat outputs. Beyond the base module, other VNF vfModules are typically referred to as expansion modules.
VID: Virtual Instantiation Deployment
- a Portal GUI to trigger MSO instantiation of services and components
VIM: Virtualized Infrastructure Manager
- part of MANO
- controls and manages the NFVI compute, storage, and network resources
VLAN: Virtual Local Area Network
VM: Virtual Machine
VNF: Virtual Network Function (link)
- a virtualized task formerly carried out by proprietary, dedicated network hardware. (Examples: virtual firewall, virtual DNS.)
- in ONAP, a VNF is a Resource
- a VNF is a specific kind of Vendor Software Product
VNFC: Virtual Network Function Component
- a part of a VNF. It is a stand-alone executable that is loosely-coupled, granular, re-usable, and responsible for a single capability.
VNO: Virtual Network Operator
vPE: virtual PE (Provider Edge) router (an example of a VNF)
VPP: Vector Packet Processing (link)
- open-source version of Cisco's VPP
- a platform that provides switch/router functionality
- used by vPacketGenerator, vFirewall, and vLoadBalancer Virtual Network Functions in ONA
VSP: Vendor Software Product (from SDC Demo Guide)
- example: a VNF
- In ONAP, a VSP is a Resource.
WAR: Web application ARchive (Wikipedia)
- a JAR file used to distribute a collection of JavaServer Pages, Java Servlets, Java classes, XML files, tag libraries, static web pages (HTML and related files) and other resources that together constitute a web application
XACML++: eXtensible Access Control Markup Language (OASIS standard, extended)
- a declarative fine-grained, attribute-based access control policy language, an architecture, and a processing model describing how to evaluate access requests according to the rules defined in policies. It is an Attribute-Based Access Control system (ABAC), where attributes (bits of data) associated with a user or action or resource are inputs into the decision of whether a given user may access a given resource in a particular way.
YAML:
- machine parsable data serialization format designed for human readability and interaction with scripting languages such as Perl and Python (yaml.org) (Wikipedia)
YANG: A Data Modeling Language for the Network Configuration Protocol (NETCONF)