Device42 Rundeck Resource plugin allows to collect nodesets from the Device42 instance and set them up as the node sets for particular projects in Rundeck. You can use Device42 filtering option to limit the amount of devices collected for the project. If you wish to use smart filters for the specific jobs feel free to use the default filtering mechanism of the Rundeck - all collected Device42 attributes are stored as Node properties, tags or attributes.
For your convenience, compiled jar file is located at: http://www.device42.com/integrations/rundeck/. You can build per the instructions below, or use the pre-compiled jar file.
The plugin uses gradle build system. To build the plugin execute "gradlew" application
For Windows run
For Linux run
After the build completes, the compiled jar file can be found in the build/libs sub-directory under the plugin directory gradlew was executed from. The pom file is irrelative to the build, maven cannot be used to build the plugin in this version.
Gradle uses the smart versioning system. If you want to change the version - check Axion Release plugin documentation for details.
Installing the plugin is as easy as copying the .jar file to your Rundeck plugins folder. On Ubuntu, the default directory for this is /etc/rundeck/libext. Alternatively you can build the plugin using Gradle by running the gradlew script included in the repository.
To setup the filter, add a new Rundeck resource to the project you are on through Configuration and select “Devices from D42”. Enter your Device42 url and credentials, and then you can enter filter values. We’ve included some common filters: tags, os, service_level, and customer, but you can also enter any Device42 API endpoint as a filter including custom fields. For a full list please visit Device42 API Page.
Working with Device42 nodes in Rundeck
After adding the filters, you will now be able to see which nodes Rundeck is pulling into Device42 by selecting the “Nodes” option in Rundeck. By drilling down to one of the nodes we could also see the synchronized information about node data including building, room and rack information about a device, operating system information, device type, and other information when applicable such as a virtual machine’s host. Now when creating Rundeck jobs you no longer have to worry about tracking down your node data to make sure you run it on the proper systems. Device42 will keep your data up-to-date, eliminating one more hurdle form your devops workflow. Furthermore, if you do not set a cache value, scheduled jobs will refresh the list of nodes to run on at the time they run making sure you have the most up-to-date list of nodes. If you wish to use smart filters for the specific jobs feel free to use the default filtering mechanizm of the Rundesk - all collected Device42 attributes are stored as Node properties, tags or attributes.
Coming soon at http://docs.device42.com
Please reach out to us at support at device42.com or open a support ticket from Device42 Support Page