Current stumbling block is setting the hostname for Puppet. We currently
PXE / Koan profiles in a private VLAN and then move them to a public
VLAN with proper hostname , IP when they are ready for production.
Not sure how to properly setup puppet for our profile based installs
another concern is after pushing to production it would seem that
another puppet / client change would be required.
Going to take a bit to wrap my head around this one :)
On 10/8/2012 5:27 PM, Dan White wrote:
http://watzmann.net/blog/2006/12/kickstarting-into-puppet.html
Basically, install Puppet as part of your list of packages thru Cobbler, and
get it to run once to initiate the certification request.
I found it helps to have the new server defined in Puppet before you begin your
Cobbler run.
Puppet picks up where Cobbler leaves off in terms of configuration and
installation and then maintains.
On Oct 8, 2012, at 4:15 PM, Ronald J Yacketta wrote:
Hello all!
Looking for some decent documentation on setup Cobbler and Puppet. We
currently have a working Cobbler system that has been in place for over a
year now and would like to integrate Pupput into the fold.
Scoured google but found bits and pieces with nothing really going through
a soup to nuts setup / example.
-Ron
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
