Deprecated Terms are listed at the bottom of this page.
A&AI: Active and Available Inventory (component of OpenECOMP runtime)
Real-time views of Resources, Services, Products, Customer Subscriptions, and their relationships
Akka: handles clustering (used by Brocade) akka.io
ASTRA: Web application firewall provided by Czar Securities and developed by AT&T
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 (OpenECOMP.pdf)
- graphical representation for specifying business processes
BRMS: Business Rules Management System
Brocade:
- commercial product built on top of OpenDaylight that has additional support and services Jump to Brocade's site
BSS: Business Support System
BVC: Brocade Vyatta Controller
- old name of the controller that Brocade now calls Brocade SDN Controller now
CCD: Common Configuration Dashboard (application within OpenECOMP)
Chef:
- configuration management tool written in Ruby and Erlang. Jump to Wikipedia article
CLAMP: Control Loop Automation Management Platform (from OpenECOMP User Guide)
- system to design and execute control loops within OpenECOMP that monitor systems, take corrective actions, and inform personnel about malfunctions
CMA: Change Management Application (within OpenECOMP)
Congress:
- Policy as a service (https://wiki.openstack.org/wiki/Congress)
- manages the state of an Application, Infrastructure, or Network resource
- single service/network domain scope
DCAE: Data Collection, Analytics and Events (component of OpenECOMP runtime)
DDoS: Distributed Denial-of-Service attack Jump to Wikipedia article
Anchor | ||||
---|---|---|---|---|
|
DLUX: the OpenDaylight community GUI (comes packaged with brocade) Jump to the DLUX documentation
- typically not needed for OpenECOMP development
Disconnect: (Vendor specific)
- disconnecting an existing connection sometimes called a delete
- Total Disconnect- Disconnect all port and Vlan from Database (SDN-C) and Network (NCS)
- Vlan Disconnect- Disconnect an active vlan from Database (SDN-C) and Network (NCS)
- Soft Disconnect - Disable the interface for traffic to flow through without deleting the interface from the network
EMS: Element Management System
ETSI: European Telecommunications Standards Institute
FCAPS: Fault Configuration Accounting Performance Security
GBP: Group-Based Policy (https://wiki.openstack.org/wiki/GroupBasedPolicy)
Heat:
- cloud infrastructure creation template language for Open Stack (https://wiki.openstack.org/wiki/Heat)
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" (https://en.wikipedia.org/wiki/Identity_management)
ICE: Incubation and Certification Environment
- for vendors and 3rd parties to develop solutions using OpenECOMP and AIC
IDS: Intrusion Detection System Jump to Wikipedia article
IKE: Internet Key Exchange Jump to Wikipedia article
IPS: Intrusion Prevention System Jump to Wikipedia article
IPSEC: Internet Protocol Security Jump to Wikipedia article
Karaf:
- a container, sponsored by Apache, fully supporting OSGI with lots of extras Jump to the official Apache page
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
- https://www.sdxcentral.com/nfv/definitions/nfv-mano/
- ETSI's MANO does not include Controller and Policy components, as OpenECOMP does
- ETSI's MANO resource description does not include complete meta-data for lifecycle management of infrastructure as well as VNFs (OpenECOMP does)
MD-SAL: Model Driven Service Abstraction Layer
- OpenDayight derives service abstractions from YANG models using yang tools. read about MD-SAL on github
MOP: Method of Procedure
- set of deployment instructions
MSO: Master Service Orchestrator (component of OpenECOMP runtime)
- automates activities, tasks, rules and policies needed for on-demand creation, modification or removal of network, application or infrastructure services
NEP: Network Equipment Provider
NETCONF: Network Configuration Protocol Jump to Wikipedia article
NFV = VNF: Network Function Virtualization
- https://www.sdxcentral.com/nfv/definitions/virtual-network-function/
- 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/
- applications such as routers, switches, firewalls
NFVI: network functions virtualization infrastructure
Node-RED:
- open-source project by IBM to graphically create flows that configure devices. Projects include managing a raspberry pi. Jump to the 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.
OMF: Operational Management Framework (of OpenECOMP)
OpenDaylight = ODL
- Largest open source SDN controller, written in Java https://www.opendaylight.org/, https://en.wikipedia.org/wiki/OpenDaylight_Project
OpenECOMP: Open-source Enhanced Control, Orchestration, Management and Policy
OpenStack:
- Open source software for creating private and public clouds (https://www.openstack.org/)
OPNFV: Open Platform for NFV Project
- carrier-grade, integrated platform that introduces new products and services to the industry more quickly.
- will work closely with the ETSI and others to press for consistent implementation of open standards.
- https://www.sdxcentral.com/nfv/definitions/opnfv/
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) Jump to Wikipedia article
POLO: Portal Open Loop operation
- a mechanism within OpenECOMP to trigger APP-C functions
Portal:
- OpenECOMP 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.
RCA: Root Cause Analysis
REST: REpresentational State Transfer Jump to Wikipedia article
RESTCONF: REST + NETCONF
- IETF draft that describes how to map a YANG specification to a RESTful interface. Read the IETF draft
RPC: Remote Procedure Call
SDC: Service Design and Creation (component of OpenECOMP for visual modeling and design)
Anchor | ||||
---|---|---|---|---|
|
- separates the control (brains) and forwarding (muscle) planes for a centralized view of the network, for more efficient orchestration and automation of network services.
- https://www.sdxcentral.com/nfv/definitions/virtual-network-function/
- https://www.sdxcentral.com/nfv/definitions/which-is-better-sdn-or-nfv/
- Jump to Wikipedia article
SDN-C:
- proprietary (non-OpenECOMP) network definition service
- its operators accept Comma Separated Value files describing networks
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.
SUPP: (Vendor Specific) short for supplement, changing a connection before activation
TEM: Telecom Electronics Manufacturer
TOSCA: Topology and Orchestration Specification for Cloud Applications (OASIS spec)
- specifies cloud infrastructure
TSC:
VF: Virtual Function
VFC: Virtualized Function Component (draft_OpenECOMP_0_1 p. 45)
- component of a VSP
- examples: Hypervisor, VM recovery details, and cloning
VID: Virtual Instantiation Deployment
- instantiate services or components that are required by infrastructure customers (draft_OpenECOMP_u_g p 113)
VIM: Virtualized Infrastructure Manager
- part of MANO
- controls and manages the NFVI compute, storage, and network resources
VNF = NFV: Virtual Network Functions
VNO: Virtual Network Operator
VSP: Virtual Software Product
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
YANG: A Data Modeling Language for the Network Configuration Protocol (NETCONF)
Anchor | ||||
---|---|---|---|---|
|
DG - short for directed graph. This is the XML output of DG Builder. DGs are meant to encapsulate service-logic.
DG Builder - short for directed graph builder. This is an AT&T customized version of Node-RED. It is a graphic editor used to generate the resulting XML files that are fed into SLI.
DHV - Dynamic Hybrid VPN formerly Hybrid Networking
NFoD - Network Functions on Demand
PLC - Port Level Class of Service
PNC - Private Network Connection
SLI - service logic interpreter, interprets DGs (xml output file)
uCPE - AT&T Universal Customer Premises Equipment read more at the public PDF on the AT&T business site.
VIG - Virtual Interface/Interconnection Gateway
VPE - Virtual Provider Edge
VRF - Virtual Routing & Forwarding
SDN System Acronyms (Deprecated, not part of OpenECOMP)
APP-C - Application Controller
SDN-CP - Software Defined Network - Controller Platform
SDN-GP - Software Defined Network - GUI Portal
SDN-GC - Software Defined Network - Global Controller
SDN-F - Software Defined Network - Fabric
SDN-MLC - Software Defined Network - Multi Layer Controller
SDN-U - Software Defined Network - Uverse
Vendor System Acronyms (Deprecated, not part of OpenECOMP)
These vendor-specific terms should not be used.
NCS - Network Control System
INSTAR (sometimes used interchangeably with LPP) -
LPP - Logical Provisioning Platform consists of INSTAR, ICORE and other sub-components. LPP has no mots id, they use either INSTAR or ICORE.
EIPAM - Enterprise IP Address Management
UEB - Universal Event Broker
C-BUS - Collaboration Bus
VID - Virtual Infrastructure Deployment
PHS - Phone Home Server
AOTS-CM - One Ticket System - Change Management
AOTS-TM - One Ticket System - Trouble Management
CCD - Common Configuration Dashboard <<same as Dashboard? If so, promote>>