Overview

A Resource is an abstract term for a leaf level component of an Assembly Service. Resource instances ultimately represent infrastructure and the software running at a location to fulfil a function.

Telco Network Cloud Orchestration (TNC-O) requires a descriptor to identify the properties, transitions, operations, metrics, and the infrastructure available for each resource instance. The Resource can then be added to any number of Assembly designs and instantiated upon creation of an Assembly.

Although TNC-O will determine the transitions and operations performed on a Resource instance as an Assembly instance moves through its lifecycle, it is the role of a Resource Manager to communicate with a target location (VIM) to bring it into service and, under the instruction of the Intent Engine, to perform discrete transitions and operations on it. This relationship with Resource Managers allows TNC-O to abstract both the specifics of communicating with a given VIM and the execution of given tasks to specialised Resource Managers.

Resource Managers

Open source Resource Manager implementations exist and TNC-O is designed to operate with multiple Resource Managers concurrently. TNC-O comes with a carrier-grade Resource Manager out-of-the-box, named Brent. This Resource Manager integrates with Resource Drivers to support managing multiple infrastructure (e.g VIM) types and lifecycle scripting technologies.

The remainder of this guide focuses on how to build Resource packages managed by Brent. Read on to begin creating Resource packages and working with drivers.