ReleaseEngineering/PuppetAgain/Base Images: Difference between revisions

ReleaseEngineering/PuppetAgain/Base Images (view source)

599 bytes added , 24 June 2014

no edit summary

canmove, Confirmed users

1,394

edits

@@ Line 3: / Line 3: @@
 See [[ReleaseEngineering/PuppetAgain/Puppetization Process|Puppetization Process]] for how a base image becomes a running instance.
-= CentOS 6.2 with Kickstart =
+= CentOS 6.x with Kickstart =
 The bulk of a kickstart script is available in [http://hg.mozilla.org/build/puppet/file/default/setup/ setup].  Run 'make' to create the script.  The top section will need a few site-specific modifications.  Most of the action is in the %post section, which:
@@ Line 9: / Line 9: @@
 * installs minimal packages
 ** Using a possibly site-specific yum-repo location (under <tt><nowiki>http://repos/repos/</nowiki></tt>)
+* installs [http://hg.mozilla.org/build/puppet/file/default/setup/puppetize.sh puppetize.sh] and sets it to run on boot.
+The same script supports both i386 and x86_64 ISAs; the determining factor is the kernel used to run the installer.
+= Ubuntu with Kickstart =
+Ubuntu is very similar to CentOS.  While it doesn't use Anaconda, it reads a kickstart profile similar to, but not exactly like, that for CentOS.  Beyond those minor differences, it does the same things:
+* looks for PUPPET_PASS on the kernel command line, and stores it in /root/deploypass
+* installs some repos and minimal packages
 * installs [http://hg.mozilla.org/build/puppet/file/default/setup/puppetize.sh puppetize.sh] and sets it to run on boot.