What's on this page


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.


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. In order to be used it must first be registered with the LM instance with which it is to be coupled and LM during the process LM will register the VIM with the identified RM


This action is performed in LM by a user with the suitable permissions. Specifically the user must have the SLMAdmin role.

  1. Select Deployment Locations from the left hand menu under System
  2. From the resulting page click on the Add button on the right hand side of the screen.
  3. Populate the resulting modal window

Adding an RM

Having navigated to the Add RM modal you should now be at a modal with three data fields

Deployment Location Name

Each deployment location should be registered with LM with a unique and meaningful name. Once added it cannot be edited as it is the routing/selecting parameter for the RM.


The type is a free text field which can be used to assist the user when deploying resources to determine which is the correct location to deploy to.

Resource Manager

Each VIM/deployment location is managed by an RM. That is, when LM wishes to perform an action be it a lifecycle change event, resource operation or a discovery it will do so through the identified RM for that location. The RM is selected from a dropdown of the set of registered RMs


As a managed field LM provides the ability to identify the type of a VIM. This is a drop down list of known VIM types. It is not restrictive, in that if a suitable one is not available it is acceptable to select other.

Infrastructure-specific Properties

Each VIM may have one or more properties which are specific to it. LM provides the ability to enter a list of key value pairs in JSON format. This is not stored in LM. Rather it is passed to the RM and cannot be retrieved. Should it need to be updated this can be achieved with an edit of the Deployment Location with the reentry of the full set of properties.

Once these have been populated and the user has clicked on Save .