Hello Complementing, you can automate this process via
// SW - config channel // Outside SW - ansible - puppet ______________ Best Waldirio Skype: waldirio Site: www.waldirio.com.br LinkedIn: https://www.linkedin.com/in/waldirio On Wed, Mar 6, 2019 at 12:43 PM Steve Meier <em...@steve-meier.de> wrote: > Hi Jody, > > Am 2019-03-06 18:47, schrieb Jody McIvor: > > Hi All, > > > > I first stopped into the IRC but it was a ghost town. Hopefully not > > so, here > > this mailing-list is quite active ;-) > > > In SCCM (Its been a while), if I added a package/app/etc, any asset > > subscribed to the parent of that package would eventually > > automatically receive it. My question about Spacewalk is, if I put an > > app on spacewalk under a main software channel, will it eventually > > force that app to all subscribed systems, or will they only receive > > once I schedule it to be pushed to selected systems (SSM)? Basically > > wondering if its safe/normal practice to have two systems subscribed > > to one channel, adding an app to that channel and having it only > > installed onto one of said two systems. > > Channels in Spacewalk work like normal repositories do. They make > software > packages available to the clients that are subscribed to them. > > There is no such thing as an automatic package installation with > Spacewalk. > So you can put new packages and even multiple versions of the same > package > into a channel. These will become available to the client(s) but you > have to > trigger the installation. > > Kind regards, > Steve > > _______________________________________________ > 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
