Hi,
We use yum wrapped up in a python script that runs from a master server and
uses ssh to log into server/servers and run the requested command (the
script doesn't support all, just most -install, downgrade, upgrade etc)
against either a single rpm or upgrade all rpms. It uses the exit status
from yum to catch errors, log them and either move to the next server or
exit (which is an option to the script).
For the more dangerous yum actions (such as downgrade, remove etc) the
script ask for verification by generating a random number and requesting
you input it (basic yes/no leads to auto typing).
Ideally I'd like this to be a part of dnf or yum suite so that I don't have
to run write a script to perform this. As we look after 100s of servers,
having the ability to do this has saved large amounts of time for us.
Since I wrote the original (a bash script originally) 10 years ago this is
used globally internally and our SAs expect this to be there and can't
imagine managing our server farms without. Therefore I strong believe this
is a typical user case that is currently not covered.
Hope that is what you are looking for.
Regards,
Jon
On Tue Dec 09 2014 at 17:29:04 Radek Holy <rholy(a)redhat.com> wrote:
Dear users of YUM and DNF,
I'm writing to you regarding a request for your feedback. I would be very
grateful if you could send me a brief description of how you use YUM or DNF
currently or how would you like to use it. I am particularly interested in
the occurrences of "dnf/yum install" calls in your scripts. What does these
scripts do and what do they expect when they call the "install" command in
different situations?
Please share with me the use cases, not the description of the "install"
command. Think twice before you share something because I believe it's not
as easy as it might seem. As an example I think it might be something like:
- "I call YUM install, because I want to get given packages into my system
and I don't care whether it requires an upgrade or downgrade or what." or
- "I want to get them there but it should protect me against dangerous
operations like downgrades" or
- "I often make typos, so I expect that the program knows what I mean" or
- "it would be nice if it would literally perform the installation; if any
of the packages cannot be installed because of any reason, it should fail".
Not something like: "that's obvious that the install command should never
downgrade packages".
Please focus on *use cases*. The *real* (non-hypothetical) use cases. Not
on the command's name as it might also result in a new command (while
preserving the well-known install command together with an appropriate
behaviour).
I don't mind if you send it offlist (or to another list). I think there is
no need to comment on anyone's use case. Every case is valid. Just not
every case can be supported.
Thank you very much in advance.
--
Radek Holý
Associate Software Engineer
Software Management Team
Red Hat Czech
--
devel mailing list
devel(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct:
http://fedoraproject.org/code-of-conduct