Hi all, Thanks for the suggestions, I'm trying to limit the need to invoke anything from the deployed client. This is because:
1. It would save putting in security mechanisms to ensure only the registered client make the call to Spacewalk 2. It would prevent issues where Spacewalk connectivity could be via a proxy with no direct connection back to Spacewalk server (NAT/firewalling etc). So far, the best solution I have come up with is to create a temporary group for deployed servers on Spacewalk server for each activation key, and then add then join the systems to that group when they activate. Then I just just create a cron entry on the spacewalk server to probe member of the group for new clients every minute. Once a new client is found to run a number of required scripts (post validation tests etc) and then to remove the client from that group. It would be nice to be able to trigger such things instead though - this would remove the need for cron and unnecessary load, if there is a need for this and it is not present then perhaps I can put in a feature request? Cheers, Tim On 22 September 2014 14:01, Will D <wil...@nixpeeps.com> wrote: > I had a similar requirement recently and through a little inventiveness, and > some python/cgi scripting we basically create a http cgi call from the newly > built system to the satellite during build time, that passed a few > variables, and executed api calls to move the server to appropriate groups, > configure custom variables and perform other satellite functions > automatically. > > > > > On Sep 22, 2014, at 5:42 AM, Waldirio Manhães Pinheiro <waldi...@gmail.com> > wrote: > > Hello Tim and list, good morning > > Tim when you say "grouped automatically", do you means sign a server in > specific or more then one system group ?? > > I did in a customer some months ago one script where the sysadmin answer > some questions and at the end the client that will be registered did the > download of bootstrap.sh and changed the activation keys accordind choices. > Note, you can combine activation keys so in this case was so easy to do what > you need. > > Let me know if help you. > > B'regards > Waldirio > > Em 19/09/2014 04:25, "Timothy Rees" <reestr...@gmail.com> escreveu: >> >> Hi list, >> >> Is there a builtin way to trigger a script on the spacewalk server to >> run as soon as a new client is registered using an activation key? >> >> I have a requirement where registered clients are grouped >> automatically and the output of a scheduled command is used to >> determine which groups a client should be joined to. Currently I have >> this running out of cron on a schedule, however would like it to be >> triggered when systems are registered, any way to achieve this? >> >> Cheers, >> Tim >> >> _______________________________________________ >> 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 > > > > _______________________________________________ > 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