What's on this page

Resource Manager

Attach to LM

Prerequisites The Lifecycle Manager communicates with the RM through the RMs published API. Prior to registering it with the LM this must be known. Attaching an RM to LM An RM exists as a standalone entity and when instantiated it is isolated by definition. In order to be used it must first be registered with the LM instance with which it is to be coupled. Permissions This action is performed in LM by a user with the suitable permissions. »


In order for an RM to communicate with a VIM both it and LM must first be aware of it. This allows an deployment location to be selected for during the instantiation of assemblies for each resource. Prerequisites A suitable RM must have been registered with LM prior to adding a VIM to LM An LM user with suitable permission to perform the action in the LM UI Adding a VIM to LM and an RM A VIM exists as a standalone entity totally independent of LM and any RM. »

Resource Manager API Architecture

The Resource Manager API is responsible for defining the interactions between the Stratoss™ Lifecycle Manager (LM) and the Resource Managers (RM) used to manage resources within virtual (or physical) infrastructures. High Level Overview There are four groups of interface endpoints referenced within the Resource Manager API. These groups are responsible for the management or retrieval of different entities from the Resource Managers. The following diagram shows the high-level functional architecture referenced in this interface specification. »

Open Source Resource Manager Projects

A Resource Manager is responsible for managing resources within virtual or physical infrastructures on behalf of an LM. Open Source Service Lifecycle Management Projects The Open Source Service Lifecycle Management - OSSLM project supports the development and maintenance of open-source Resource Manager implementations. The current open source resource manager projects include: Ansible RM Docker RM OpenSource MANO »