Versions Compared

Old Version 6

changes.mady.by.user Unknown User (fay)

Saved on

compared with

New Version 7

changes.mady.by.user Unknown User (fay)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

A&AI: Active and Available Inventory (component of ECOMP 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 (ecompOpenECOMP.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 Systems

BVC: Brocade Vyatta Controller

  • old name of the controller that Brocade now calls Brocade SDN Controller now

CCD: Common Configuration Dashboard (application within ECOMPOpenECOMP)

Chef:

CLAMP: Control Loop Automation Management Platform (ecomp_ugfrom OpenECOMP User Guide)

  • a system to design and execute control loops within ECOMP OpenECOMP that monitor systems, take corrective actions, and inform personnel about malfunctions

CMA: Change Management Application (within ECOMPOpenECOMP)

Congress:

Controller:

  • Manages manages the state of an Application, Infrastructure, or Network resource
  • Single single service/network domain scope

DCAE: Data Collection, Analytics and Events (component of ECOMP OpenECOMP runtime)

Anchor
Drools
Drools
Drools: Red Hat's Business Rules Management System solution https://www.drools.org/

ECOMP: Enhanced Control, Orchestration, Management and Policy (from ecomp.pdf)

  • product/service independent capabilities
    • policy-driven, metadata-driven
    • dynamic capacity
    • consistent failure management
    • near real-time reconfiguration
    • component and workload shaping, placement, execution, and administration
    • for the design, creation and lifecycle management of a cloud environment with network services
    • for carrier-scale, real-time workloads
    • does not directly support legacy physical elements

ECOMP Portal:

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 provides access to design, analytics and operational control/administration via a common role-based menu or dashboard. Includes SDK to drive UI consistency.

EMS: Element Management System

ETSI: European Telecommunications Standards Institute

FCAPS: Fault Configuration Accounting Performance Security

HEAT:

GBP: Group-Based Policy (https://wiki.openstack.org/wiki/GroupBasedPolicy)

Heat:



IAM/IDAM: Identity and Access Management

  •  security security and business discipline that "enables the right individuals to access the right resources at the right times and for the right reasons"

ICE: Incubation and Certification Environment

  • for vendors and 3rd parties to develop solutions using ECOMP OpenECOMP and AIC

IPS: Intrusion Prevention System

Karaf:

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 ECOMP OpenECOMP does
  • ETSI's MANO resource description does not include complete meta-data for lifecycle management of infrastructure as well as VNFs (ECOMP OpenECOMP does)

MD-SAL: Model Driven Service Abstraction Layer

MOP: Method of Procedure

  • a set of deployment instructions

MSO: Master Service Orchestrator (component of ECOMP 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

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 Nonprofit consortium that drives the development, convergence and adoption of open standards for the global information society.

OMF: Operational Management Framework (of ECOMPOpenECOMP)

OpenDaylight: the largest = ODL


...

OpenStack: Open source software for creating private and public clouds

OpenECOMP: Open-source Enhanced Control, Orchestration, Management and Policy

OpenStack:

  • Open source software for creating private and public clouds GBP: Group-Based Policy (https://wikiwww.openstack.org/wiki/GroupBasedPolicy)

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: Operation Support System

OSGI:

POLO: Portal Open Loop operation

  •  a a mechanism within ECOMP 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


SDC: Service Design and Creation (component of ECOMP)OpenECOMP for visual modeling and design)

Anchor
SDN
SDN
SDN: Software-Defined Networking

  • 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
  • creates internal metadata used by all ECOMP applications, both design time and runtime
  • Includes catalog of standard (resource) items
  • Can read Yang, HEAT, TOSCA, YAML, BPMN/BPEL
  • Four asset types: Resource, Service, Product, and Offer
    • Resource: a fundamental capability, either hardware or software
    • Infrastructure (the Cloud resources, e.g., Compute, Storage)
    • Network (network connectivity functions and elements)
    • Application (features and capabilities of a software application)
  • Service: a well-formed object with one or more resources
  • Product: includes one or more services packaged with commercialization attributes for customer ordering and billing of the underlying service(s)
  • Offer: bundling of products with specific Marketing configurations for selling to customers

SDN-C:

  • Proprietary proprietary (non-ECOMP?OpenECOMP) network definition service
  • Its 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 specifies cloud infrastructure

TSC:

VF: Virtual Function

VFC: Virtualized Function Component (draft_ecompOpenECOMP_0_1 p. 45)

  • component of a VSP
  • Examplesexamples: Hypervisor, VM recovery details, and cloning

VID: Virtual Instantiation Deployment

  • instantiate services or components that are required by infrastructure customers (draft_ecompOpenECOMP_u_g p 113)

VIM: Virtualized Infrastructure Manager

  • part of MANO
  • Controls controls and manages the NFVI compute, storage, and network resources

VNF = NFV: Virtual Network Functions

  • applications such as routers, switches, firewalls

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)


SDN-C Specific Terms (not part of OpenECOMP)


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 (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