Copied from RI's https://github.com/ripienaar/mcollective-vagrant
Puppet agent and a PE specific agent
…Puppetd::YAML In the past it was possible for the puppetd agent's #last_run_summary to be reached without yaml being required. Yaml will now always be required when calling #last_run_summary
…n policy directive In the past all Fact and Class lists would apply a logical 'and' to all the given values, limiting the flexibility of the policy. Fact and Class fields can now be defined using the mcollective discovery language inside the policy file. Facts and Classes can be combined by dropping the class field in the policy file and listing both facts and classes as a complex statement in the facts field. The Rakefile has also been updated to include simplerpc_authorization tests.
…ng puppet Puppet 2 requires you to set $puppet_application_name before requiring puppet else the settings/defaults/config classes will assume apply This is unfortunate because there is also no way at all to re-read the config files once its been incorrectly initialized. With this change we catch most of the known cases where we require puppet and make sure they all set the preference to agent which seems to be the most likely section people might want a long running daemon that interact with Puppe to use.
Dsh application was not working because it was looking for the discovery agent which does not have a DDL. After applying this fix, the application now uses rpcutil and no longer fails.
…b installed can use the script
…ames Remove data plugins that were merged to mcollective core and rename data plugins for better packaging
…ames Add a few aggregate summaries and change all the names to single words in the DDLs so that packages built using the plugin packager do not end up with really horrid looking package names.
Support setting a maximum age for a node in the registration database after which they will be considered invalid and not discoverable using the plugin.registration.criticalage setting
values usable by mcollective 2.1.x
and now will just confuse users, removing.
…tus, not as a result The NRPE treated results where the status code was > 0 as OK, this could be in the case where something is majorly wrong with the mcollectived on a node or if the RPC authorization layer denies access to the runcommand actions. We now treat those as UNKNOWN statusses
The DDL has an output value of oudated_packages. The agent expects to populate outdated_packages. This causes Live Management to barf on yum checkupdates.
The package agent was ported from old style agents before the current style of agent development was well established and so it was always a weird fit. This changes the output formats around to be more in line with current design and how the CLI works.
for discovery queries like: mco find -S "resource('File[/srv/www]').managed = true" mco find -S "resource().count > 500"
when selecting hosts, the meta registration agent has been updated to send the collectives a node blong to so this plugin can now restrict results to the requested collective