Attach to LM
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.
This action is performed in LM by a user with the suitable permissions. Specifically the user must have the SLMAdmin role.
- Select Resource Managers from the left hand menu under System
- From the resulting page click on the Add button on the right hand side of the screen.
- 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
Each RM 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 in identifying the correct RM.
This is the URL at which the Resource Managers API has been published. This will be determined by the install of the RM and must be provided here to allow LM to communicate with the RM over its exposed API
For example: with the Ansible RM (ARM) the default URL is will be;
Note: The port may have been actively changed from the default during the install
Special consideration for Ansible RM
At the present the Ansible RM needs to be added as its internal namespace name and port osslm-ansible-rm. This is reflected in the example above.
Once the set of values have been populated and Createclicked, the user will be provided with an onscreen report on the status of the RM.
With the RM now registered with LM, Deployment Locations/VIMs can be added. We can now proceed to Adding a VIM (deployment location) to a LM and an RM.