For #1, you can create separate activation key(s) that will place the client in whatever group(s) and assign specific base/child channels, then use --activationkey "<your-key-name>" with rhnreg_ks as appropriate for each client.
On Tue, Aug 13, 2019 at 9:55 AM Ananta Chakravartula < anant...@googlemail.com> wrote: > I created groups dev/stage/prod and assigned nodes to those groups > depending on our chef client environment. > > My questions > > 1) whenever I run `rhnreg_ks` on clients, i want to run a script on the > server to add the node to a certain group and set basechannel depending on > the environment. for example I want all the prod nodes to be set to base > channel prod-xxx. I wrote some code for that, but how can i trigger it on > rhnreg_ks, is it possible? > > 2) I don't see any option in here > <https://spacewalkproject.github.io/documentation/api/2.9/handlers/ServerGroupHandler.html%20.> > to set all the nodes in a group to certain base channel.It will be nice to > add that , is there any space where I can create a PR or suggest? > This > <https://spacewalkproject.github.io/documentation/api/2.9/handlers/SystemHandler.html#setBaseChannel> > takes only systemid, it will be nice if it can take groupname or groupid > > 3) How can i set spacecmd not to cache in config? I run in to many issues > with spacecmd not doing what it is supposed to be even after confirming the > changes in stdout. Some gets cleared vi clear_caches. I also can't > reproduce the issues, so i can't open bug report. It will be nice and handy > if there is any config option not to do caching. > > cheers, > ac > > > _______________________________________________ > Spacewalk-list mailing list > Spacewalk-list@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list