3.8.3. Building SIMP From Source¶
126.96.36.199. Getting Started¶
Please have your environment prepared as specified by Environment Preparation before continuing.
Download the CentOS/RedHat installation media:
- Refer to
release_mappings.yamlto determine the distribution ISO compatible with the version of SIMP you want to build.
release_mappings.yamlis maintained the simp-core module in the
- SIMP_5.X: CentOS-7-x86_64-DVD-1611.iso
- SIMP_4.X: DVD1 and DVD2 of the CentOS 6.8 release. For example, CentOS-6.8-x86_64-bin-DVD1.iso
188.8.131.52. Generating The ISO Using Docker (recommended)!¶
$ git clone https://github.com/simp/simp-core $ cd simp-core
Check out your desired branch of SIMP:
- To check out a stable SIMP release, check out a tag (Recommended):
$ git checkout tags/6.1.0-0
- To check out an unstable SIMP release, check out the latest
$ git checkout master
bundle to make sure that all of the build tools and dependencies are
installed and up to date:
$ bundle install
ISO directory, and copy in the CentOS/RHEL installation media:
$ mkdir ISO $ cp </path/to/dvd*.iso> ISO
rpm_docker beaker suite, toggling build options with environment
$ <build ENV vars> bundle exec rake beaker:suites[rpm_docker]
Build ENV vars:
SIMP_BUILD_docs- (yes|no) - Toggle doc builds.
- The docs take a long time to build!
SIMP_ENV_NO_SELINUX_DEPS- (yes|no) - Force the earliest version of
selinux-policy<-devel>for the major EL release.
- In order to maintain the backward compatibility of simp-rsync with each major EL release, we must bring in the selinux policies supplied by the original major EL release being built. SELinux policies are forward compatible during a major release, but not necessarily backwards compatible. If you opt to use repositories that bring in updated selinux policies, you will need to set this to
BEAKER_destroy- (yes|no) - Setting
BEAKER_destroy=nowill preserve the docker container used to build SIMP.
Once the process completes, you should have a bootable SIMP ISO, in:
184.108.40.206. After You Build¶
You may have noticed that a development GPG key has been generated for the build.
This key is only valid for one week from generation and has been specifically generated for your ISO build.
Doing this allows you to have a validly signed set of RPMs while reducing the risk that you will have invalid RPMs distributed around your infrastructure.
If you need to build and sign your RPMs with your own key, you can certainly
do so using the
rpm --resign command.
The new development key will be placed at the root of your ISO and will be
RPM-GPG-KEY-SIMP_dev. This key can be added to your clients, or
served via a web server, if you need to install from a centralized yum
Please see the Red Hat Guide to Configuring YUM and YUM Repositories for additional information.