[Satellite 6] Content view package deploy during kickstart

Support
1

Hi,
I created distribution based on Centos 6* and to content view connected
with this distro I added multiple products with multiple rpm repositories
(like epel, libreoffice, etc). I want to install packages from those custom
repos during kickstart phase, but problem is, that anaconda can not see
them, because installation media is automatically set to Centos 6 os
repository. What is prefered way to deploy custom packages to managed
system? Should I write puppet module which takes care about software
deployment or should I create new Media which will lead to content view
http repository? Lets say, I want to deploy package HTOP to Centos 6. This
package is not in kickstart repo (os), so during kickstart I can not deploy
it because Anaconda can not see it. After installation and registration to
satellite (with key) I can deploy it because it is in my content view for
rhel 6.

Thanks

2

What I did (after talking to a developer about this) was to simply add repo
definitions to my provisioning template that pointed to the custom view
repos.

Definitely sub-optimal behavior but it can be made to work very quickly.

Regards,
–Tony

··· On Monday, December 29, 2014 2:17:54 AM UTC-5, Jakub Bittner wrote: > > Hi, > I created distribution based on Centos 6* and to content view connected > with this distro I added multiple products with multiple rpm repositories > (like epel, libreoffice, etc). I want to install packages from those custom > repos during kickstart phase, but problem is, that anaconda can not see > them, because installation media is automatically set to Centos 6 os > repository. What is prefered way to deploy custom packages to managed > system? Should I write puppet module which takes care about software > deployment or should I create new Media which will lead to content view > http repository? Lets say, I want to deploy package HTOP to Centos 6. This > package is not in kickstart repo (os), so during kickstart I can not deploy > it because Anaconda can not see it. After installation and registration to > satellite (with key) I can deploy it because it is in my content view for > rhel 6. > > Thanks >
3

I will try it.

Dne pondělí, 29. prosince 2014 14:38:11 UTC+1 Tony Coffman napsal(a):

··· > > What I did (after talking to a developer about this) was to simply add > repo definitions to my provisioning template that pointed to the custom > view repos. > > Definitely sub-optimal behavior but it can be made to work very quickly. > > Regards, > --Tony > > > > On Monday, December 29, 2014 2:17:54 AM UTC-5, Jakub Bittner wrote: >> >> Hi, >> I created distribution based on Centos 6* and to content view connected >> with this distro I added multiple products with multiple rpm repositories >> (like epel, libreoffice, etc). I want to install packages from those custom >> repos during kickstart phase, but problem is, that anaconda can not see >> them, because installation media is automatically set to Centos 6 os >> repository. What is prefered way to deploy custom packages to managed >> system? Should I write puppet module which takes care about software >> deployment or should I create new Media which will lead to content view >> http repository? Lets say, I want to deploy package HTOP to Centos 6. This >> package is not in kickstart repo (os), so during kickstart I can not deploy >> it because Anaconda can not see it. After installation and registration to >> satellite (with key) I can deploy it because it is in my content view for >> rhel 6. >> >> Thanks >> >