Resource Driver Overview Brent handles Resource Manager transition and operation requests for Resources using Resource Drivers. The following diagram shows the interactions between Brent and a resource driver Resource Driver is a combination of VIM and Lifecycle drivers of TNC-O version 2.1 into a single driver concept. Unlike in v2.1.0 where a VIM Driver handles infrastructure creation/deletion while Lifecycle Driver executes resource transitions once the resource has been created; a Resource Manager handles both infrastructure and lifecycles by serving Create/Delete as lifecycle requests. »

Onboard Drivers You can onboard drivers with the resourcedriver add command from LMCTL v2.1+. Read more about all the commands from LMCTL resourcedriver command reference Drivers by default run with SSL enabled and need to be onboarded with an SSL certificate that allows Brent to communicate with them. To retrieve the SSL certificate for a deployed driver (in base64-encoded PEM format), run the following command: kubectl get secret <secretName> -o 'go-template={{index . »

Introduction You may create your own resource driver to support integration with virtual infrastructure and to complete transitions and operations with different scripting mechanisms. The driver must fulfill resource driver APIs and be capable of accepting HTTP requests and returning responses asynchronously on Kafka. The programming language used to create the driver is at the discretion of the user. The SOL 003 Lifecycle Driver is a good example of writing a driver with Java. »