powellnathanj / mcollective-yum-agent Goto Github PK

Thanks for the yum plugin! Just adding a feature request for yum list or yum list installed so you can discover what package versions are installed.

I know you can do this with mco package status package=foo, but I'd like to be able to disable the mco package plugin altogether since I've got a yum-centric version now, mainly to avoid someone from installing something outside of yum.

Just a question, Is there any benefit for the output on check-update to have three sections which seem somewhat repetitive? I was thinking about modifying this to just keep the Exit code and 'Output' sections for each host, but I was wondering if that might be a mistake I'd regret doing.

This is what I currently get:

       Exit Code: 100

Outdated Packages: nil
outdated_packages: [{:repo=>"DoIT", :package=>"MariaDB-common.x86_64", :version=>"10.0.20-1.el6"},
{:repo=>"DoIT", :package=>"MariaDB-compat.x86_64", :version=>"10.0.20-1.el6"},
{:repo=>"DoIT", :package=>"MariaDB-shared.x86_64", :version=>"10.0.20-1.el6"},
{:repo=>"DoIT", :package=>"db4.x86_64", :version=>"4.7.25-19.el6_6"},
{:repo=>"DoIT", :package=>"db4-utils.x86_64", :version=>"4.7.25-19.el6_6"},
{:repo=>"DoIT", :package=>"dmidecode.x86_64", :version=>"1:2.12-5.el6_6.1"},
{:repo=>"DoIT", :package=>"glibc.x86_64", :version=>"2.12-1.149.el6_6.9"},
{:repo=>"DoIT",
:package=>"glibc-common.x86_64",
:version=>"2.12-1.149.el6_6.9"},
{:repo=>"DoIT", :package=>"htop.x86_64", :version=>"1.0.3-1.el6.rf"},
{:repo=>"DoIT", :package=>"kernel.x86_64", :version=>"2.6.32-504.23.4.el6"},
{:repo=>"DoIT",
:package=>"kernel-firmware.noarch",
:version=>"2.6.32-504.23.4.el6"},
{:repo=>"DoIT", :package=>"openssl.x86_64", :version=>"1.0.1e-30.el6.11"},
{:repo=>"DoIT", :package=>"puppet.noarch", :version=>"3.8.1-1.el6"},
{:repo=>"DoIT", :package=>"rsyslog.x86_64", :version=>"8.10.0.ad1-2.el6"},
{:repo=>"DoIT",
:package=>"rsyslog-gnutls.x86_64",
:version=>"8.10.0.ad1-2.el6"},
{:repo=>"DoIT", :package=>"tzdata.noarch", :version=>"2015e-1.el6"}]
Output:
MariaDB-common.x86_64 10.0.20-1.el6 DoIT
MariaDB-compat.x86_64 10.0.20-1.el6 DoIT
MariaDB-shared.x86_64 10.0.20-1.el6 DoIT
db4.x86_64 4.7.25-19.el6_6 DoIT
db4-utils.x86_64 4.7.25-19.el6_6 DoIT
dmidecode.x86_64 1:2.12-5.el6_6.1 DoIT
glibc.x86_64 2.12-1.149.el6_6.9 DoIT
glibc-common.x86_64 2.12-1.149.el6_6.9 DoIT
htop.x86_64 1.0.3-1.el6.rf DoIT
kernel.x86_64 2.6.32-504.23.4.el6 DoIT
kernel-firmware.noarch 2.6.32-504.23.4.el6 DoIT
openssl.x86_64 1.0.1e-30.el6.11 DoIT
puppet.noarch 3.8.1-1.el6 DoIT
rsyslog.x86_64 8.10.0.ad1-2.el6 DoIT
rsyslog-gnutls.x86_64 8.10.0.ad1-2.el6 DoIT
tzdata.noarch 2015e-1.el6 DoIT

Working on the basis that mco yum command... should, as near as is possible, function the same as yum command... I suggest removing the downloadonly command in favour of using the --downloadonly switch.

The yum command should drop some sort of semaphore to prevent multiple instances of the yum command being launched.

There should also be a command to kill any currently running yum processes (in the event that a yum command hangs or is taking too long to run).

Hi,

It would be nice if the mco rpc yum allows the native yum arguments or at least the exclude option and if possible something like this:
mco yum update-minimal --security -y --disablerepo=${RD_OPTION_DISABLE_REPO} ${RD_OPTION_FQDN}

My goal: update only the security patches from Base/Updates but exclude certain repo's with high impact packages such tomcat, own custom repo's etc.

Is something like this possible to add?

Thanks!

Michiel