[katello-devel] When does Puppet start

Lukas Zapletal lzap at redhat.com
Mon Oct 29 16:11:27 UTC 2012


I think this is doable with Puppet, Foreman defaults to run Puppet in
the anaconda post-install section too.

I recommend trying Foreman standalone, until we fully integrate it in
Katello.

LZ

On Mon, Oct 29, 2012 at 04:05:54PM -0000, Innes, Duncan wrote:
> Thanks Lukas,
> 
> I thought there was already some integration of Puppet beyond installing
> Katello itself.  It's been a while since I've installed the package to
> test/play around.
> 
> By "install kernel" I meant the ability to run any Puppet stuff during
> the install phase - much like post-installation scripts on the current
> Satellite platform.
> 
> Gives us the ability to harden a server before it first boots, but I can
> see Puppet being too much a nightmare to have running before the first
> boot.
> 
> D
> 
> On Mon, Oct 29, 2012 at 13:53PM, Zapletal Lukas wrote:
> > Katello does not support Foreman yet, therefore our Puppet 
> > codebase is currently only for installing Katello itself.
> > 
> > What you mean by install kernel?
> > 
> > We will use Puppet the way it is integrated in Foreman. Have 
> > a look at www.theforeman.org to see how it works.
> > 
> > Basically, puppet is usually integrated in the kickstart 
> > file. During the first boot, it negotiates SSL certificates 
> > with the puppet master and then makes initial configuration. 
> > Then you run it either from cron or using a daemon to 
> > re-apply the configuration over and over again.
> > 
> > LZ
> > 
> > On Mon, Oct 29, 2012 at 10:53:41AM -0000, Innes, Duncan wrote:
> > > Hi folks,
> > > 
> > > Hopefully this isn't an entirely stupid question. I'm trying to find
> 
> > > out where Puppet will start processing during the whole build phase
> in 
> > > Katello.
> > > 
> > > Is there anything of Puppet running during the install kernel?  It 
> > > would be neat if it does as that would enable machines to be fully 
> > > configured on first boot.  But I can see the scope of Puppet being 
> > > large enough to avoid running it in the install kernel.  What 
> > > direction has Puppet integration taken?
> > > 
> > > If there's any good documentation on the process that I can read,
> I'm 
> > > happy to do that.
> > > 
> > > Cheers
> > > 
> > > Duncan
> > > 
> > > _______________________________________________
> > > katello-devel mailing list
> > > katello-devel at redhat.com
> > > https://www.redhat.com/mailman/listinfo/katello-devel
> > 
> > --
> > Later,
> > 
> >  Lukas "lzap" Zapletal
> >  #katello #systemengine
> > 
> > _______________________________________________
> > katello-devel mailing list
> > katello-devel at redhat.com
> > https://www.redhat.com/mailman/listinfo/katello-devel
> > 
> 
> 
> This e-mail is intended to be confidential to the recipient. If you receive a copy in error, please inform the sender and then delete this message.
> 
> Virgin Money plc - Registered in England and Wales (Company no. 6952311). Registered office - Jubilee House, Gosforth, Newcastle upon Tyne NE3 4PL. Authorised and regulated by the Financial Services Authority.
> 
> The following companies also trade as Virgin Money and are registered in England and Wales and have their registered office at Discovery House, Whiting Road, Norwich NR4 6EJ:
> 
> Virgin Money Personal Financial Service Limited (Company no. 3072766) and Virgin Money Unit Trust Managers Limited (Company no. 3000482) are authorised and regulated by the Financial Services Authority.
> 
> Virgin Money Cards Limited (Company no. 4232392) is introducer appointed representative only of Virgin Money Personal Financial Service Limited.
> 
> For further details of Virgin Money group companies please visit our website at virginmoney.com

-- 
Later,

 Lukas "lzap" Zapletal
 #katello #systemengine




More information about the katello-devel mailing list