Revision 90e748b7
Added by Alexis Mousset almost 7 years ago
| 00_introduction/20_key_features.txt | ||
|---|---|---|
|
[TODO]) so that it provides generic, abstract, OS independant primitives to the
|
||
|
user who can:
|
||
|
|
||
|
image::./images/core_techniques.png["Standard Technique Library", float="right"]
|
||
|
image::./images/introduction/core_techniques.png["Standard Technique Library", float="right"]
|
||
|
|
||
|
* install software in OS native packaging system (RPM on RHEL, Windows software
|
||
|
components, or even direct install from sources),
|
||
| 80_extension_and_integration/20_Rudder_plugins.txt | ||
|---|---|---|
|
|
||
|
===== Extending API: rudder-plugin-itop
|
||
|
|
||
|
Link: https://github.com/Normation/rudder-plugin-itop
|
||
|
Link: https://github.com/normation/rudder-plugin-itop
|
||
|
|
||
|
This plugin was used to add new API endpoint dedicated to the integration with
|
||
|
https://www.combodo.com/itop-193[iTop CMDB software].
|
||
| ... | ... | |
|
|
||
|
===== Adding information to node details: rudder-plugin-external-node-information
|
||
|
|
||
|
Link: https://github.com/Normation/rudder-plugin-external-node-information
|
||
|
Link: https://github.com/normation/rudder-plugin-external-node-information
|
||
|
|
||
|
This plugin allows to add new tabs in Rudder "node details" page and display
|
||
|
node specific files, stored in node-dedicated places. It also use a
|
||
| ... | ... | |
|
|
||
|
===== Providing a full new feature: rudder-plugin-datasources
|
||
|
|
||
|
Link: https://github.com/Normation/rudder-plugin-datasources
|
||
|
Link: https://github.com/normation/rudder-plugin-datasources
|
||
|
|
||
|
As we said, Rudder plugins can be quite powerful. For example, the "Data sources
|
||
|
Plugin" brings a completely new feature to Rudder by allowing to configure external
|
||
| ... | ... | |
|
As of Rudder 4.1, there is no dedicated, frozen plugin API for plugins. A plugin
|
||
|
is built in Scala, and the normal starting point is to clone and study the
|
||
|
template plugin project,
|
||
|
https://github.com/Normation/rudder-plugin-helloworld[rudder-plugin-helloworld].
|
||
|
https://github.com/normation/rudder-plugin-helloworld[rudder-plugin-helloworld].
|
||
|
|
||
|
The project code source is documented to be didactic and provides:
|
||
|
|
||
| 80_extension_and_integration/40_Rudder_Integration.txt | ||
|---|---|---|
|
|
||
|
==== Existing third party integration
|
||
|
|
||
|
==== Rundeck
|
||
|
===== Rundeck
|
||
|
|
||
|
http://rundeck.org[Rundeck] is a tool that helps automating infrastructures, by
|
||
|
defining jobs that can be run manually or automatically. There is a
|
||
|
https://github.com/Normation/rundeck-plugin-rudder[plugin] for Rundeck
|
||
|
https://github.com/normation/rundeck-plugin-rudder[plugin] for Rundeck
|
||
|
that allows using Rudder inventory data in Rundeck.
|
||
|
|
||
|
With that plugin, you can execute commands on node registered in Rudder, taking
|
||
|
advantage of the groups defined for you policies.
|
||
|
|
||
|
==== Ansible
|
||
|
===== Ansible
|
||
|
|
||
|
There is an https://github.com/ansible/ansible/blob/devel/contrib/inventory/rudder.py[inventory plugin]
|
||
|
for Ansible that makes possible to use Rudder inventory (including groups, nodes,
|
||
Also available in: Unified diff
Fixes #10687: Broken doc build