Add Rudder to Configuration Management #551
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you for taking the time to work on a PR for Awesome-Sysadmin!
To ensure your PR is dealt with swiftly please check the following:
Demo
andClients
are optional.Do not add a duplicate
Source code
link if it is the same as the main link.Keep the short description under 80 characters and use sentence case
for it, even if the project's webpage or readme uses another capitalisation.
Demo
links should only be used for interactive demos, i.e. not video demonstrations.- [Name](http:https://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http:https://url.to/demo), [Source Code](http:https://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`
Language
tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb,
"Remove aaa from bbb" for removing, "Fix license for aaa", etc.
Please take some time to answer the following questions as best you can:
Rudder is, in effect, a pretty CFEngine frontend, and has the ability to interact with the systems it manages on a pull-based system, rather than a push (Though you can push, if you so desire). It's awesome because it scales easily, is extremely reliable (in my experience) and very easily extensible with your own directives, groups, rules and script packages.
Yes, for around 6 years.
Both, I've had it in my lab managing 20+ Linux systems for years, but have also implemented it at scale with multiple relays in a 500+ endpoint environment.
Personally? 23 currently.
Honestly? Ease of use if you're coming from an RMM with agent procedures like Kaseya. Reporting is a piece of cake with the really well documented API, and the agents are extremely reliable being based on CFEngine.
Biggest con is that the server is a bit of a resource hog on larger installations.
Only limitation I can think of is that the automated patch management and compliance modules that have prebuilt scripts for CIS, ISO27k etc have a price tag. This does not mean you can't just build them yourself, though.