[Spacewalk-list] can/cannots of Spacewalk: some questions

[Jason M. Nielsen]

I am not aware of an easy method of backing up the existing file prior 
to deploy. You could push the file back to the SW with rhncfg-manager or 
the like but unfortunately there appears to be no way to submit files 
from the client to the clients "locally managed" config channel. Odd as 
listing the channels out you can see it (its just the systemid). Maybe a 
way to submitting it to a general temp channel, then another process 
moves it to the locally managed, removes and moves on to the next client.

You could use profiles to enforce systems to look a certain way from a 
package perspective.  For instance, set up "foo" to look as you wish. 
Add "bar" to a system group "baz" which is suppose to look like "foo". 
Periodically, cron perhaps, run a job that tells all the nodes in system 
group baz to sync their profiles to the saved foo profile. Number of 
ways you could do this through the basic tools. Might be a better way if 
you look more to the guts of SW though. I frequently use the profile 
sync feature to make machines look the same and it works quite well 
(perfectly thus far).

You should be able to have packages installed on system registration. I 
do this for all the spacewalk and rhn packages as well as a few other 
items. Although I am on version 1.5. Looked into the logs or client 
verbose for errors? What I have found to not work correctly are 
configuration channels. The registration simply crashes and Ive not 
taken any time to look into as of yet.

On 08/10/2012 05:30 AM, Registros Web wrote:
> Hi all,
>
> I'll be grateful if anyone can give an answer to this questions:
>
> - Is it possible to have files removed with SW?. I know files can be
> deployed but is there a way to tell SW to delete arbitrary files in
> case they exists??. And what about move/copy them?. For example I want
> to make a backup of the actual file before deploying a replacement.
>
> - Package installation/removal. I know that you can tell SW to install
> some packages at the moment of a client registration (which BTW
> doesn't work for me) but, is it possible to tell SW which packages you
> want a system (or group) to have installed and NOT installed?. For
> example, I want my systems to have installed package 'telnet' and have
> package 'nfs-common' removed if installed, and I want all that to be
> checked regularly, not only on client registration. Is this possible
> with SW?.
>
> Thanks.
>
> Cheers,
> Fred.
>
>
>
> “Free software” is a matter of liberty, not price. To understand the
> concept, you should think of “free” as in “free speech”, not as in
> “free beer”.
> Free software is a matter of the users' freedom to run, copy,
> distribute, study, change and improve the software.
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>