Continuous Integration Scripts for Satellite 6

:Author: Nick Strugnell :Email: nstrug@redhat.com :Date: 2014-11-20 :Revision: 0.1

== Introduction Continuous Integration for Infrastructure (CII) is a process by which the Operating System build ("build") component of a Standard Operating Environment (SOE) can be rapidly developed, tested and deployed.

A build is composed of the following components:

• Red Hat provided base packages
• 3rd party and in-house developed packages
• Deployment instructions in the form of kickstart templates
• Configuration instructions in the form of puppet modules
• Test instructions in the form of BATS scripts

The CII system consists of the following components:

• A git repository, containing the 3rd party and in-house packages, kickstarts, puppet modules and BATS scripts. This is where development of the build takes place.
• A Jenkins instance. This is responsible for building artefacts such as RPMs and Puppet modules. Pushing artefacts into the Red Hat Satellite, and orchestrating and reporting tests.
• Red Hat Satellite 6. This acts as the repository for Red Hat-provided and 3rd party packages, kickstarts and puppet modules. The Foreman module is also used to deploy test clients.
• A virtualisation infrastructure to run test clients. I have used KVM/Libvirt as supplied with RHEL 7.

The architecture is shown in https://github.com/RedHatEMEA/soe-ci/blob/master/Engineering%20Platform.graphml[this] YeD diagram.

== Setup The following steps should help you get started with CII.

=== Jenkins Server

NB I have SELinux disabled on the Jenkins server as I ran into too many problems with it enabled and didn't have the time to fix them.

==== Installation

• Install a standard RHEL 7 server with a minimum of 4GB RAM and 50GB availabile in +/var/lib/jenkins+. It's fine to use a VM for this.
• Register the server to RHN RHEL7 base and RHEL7 common repos. You need the RHEL 7 Common repos for puppet.
• Configure the server for access to the http://mirrors.coreix.net/fedora-epel/7/x86_64/repoview/epel-release.html[EPEL] and http://pkg.jenkins-ci.org/redhat/[Jenkins] repos.
• Install httpd, mock, createrepo and puppet on the system. These are available from the standard RHEL repos so should just install with yum. Ensure that httpd is running.
• Configure mock by copying https://github.com/RedHatEMEA/soe-ci/blob/master/rhel-7-x86_64.cfg[this] file to /etc/mock on the jenkins server, and linking ensuring that the link /etc/mock/default.cfg point to it.
• Install jenkins. If you have setup the Jenkins repo correctly you should be able to simply use yum.
• Start Jenkins and browse to the console at http://jenkinsserver:8080/
• Select the 'Manage Jenkins' link, followed by 'Manage Plugins'. You will need to add the following plugins: ** Git Plugin ** Multiple SCMs Plugin ** TAP Plugin
• Restart Jenkins
• Add the jenkins user to the mock group. This will allow Jenkins to build RPMs.
• Create /var/www/html/pub/soe-repo and /var/www/html/pub/soe-puppet and assign their ownership to the jenkins user. These will be used as the upstream repositories to publish artefacts to the satellite.
• su to the jenkins user and use ssh-keygen to create an ssh keypair. These will be used for authentication to both the git repository, and to the satellite server.
• Create a build plan in Jenkins by creating the directory /var/lib/jenkins/jobs/SOE and copying in the file https://github.com/RedHatEMEA/soe-ci/blob/master/config.xml
• Check that the build plan is visible and correct via the Jenkins UI

=== Git Repository

• Clone the following two git repos: ** https://github.com/RedHatEMEA/soe-ci These are the scripts used to by Jenkins to drive CII ** https://github.com/RedHatEMEA/acme-soe This is a demo CI environment
• Push these to a private git remote (or branch on github).
• Edit the build plan on your jenkins instance so that the two SCM checkouts point (one for acme-soe, the other for soe-ci) point to your private git remote (or your branch on github) and not to the master branch - you will need to edit both of these.

=== Satellite 6

• Install and register a Red Hat Satellite 6 as per the instructions at https://access.redhat.com/site/documentation/en-US/Red_Hat_Satellite/6.0/html/Installation_Guide/index.html I would recommend doing this on a RHEL6 server rather than RHEL7.
• Enable the following repos: RHEL 7 Server Kickstart 7Server, RHEL 7 Server RPMs 7Server, RHEL 7 Server - RH Common RPMs 7 Server
• Create a sync plan that does a daily sync of the RHEL product
• Do an initial sync
• Create a product called 'ACME SOE'
• Create a puppet repository called 'Puppet' with an upstream repo of http://jenkinsserver/pub/soe-puppet
• Create an RPM repository called 'RPMs' with an upstream repo of http://jenkinsserver/pub/soe-ci
• Do NOT create a sync plan for the ACME SOE product. This will be synced by Jenkins when needed.
• Take a note of the repo IDs for the Puppet and RPMs repos. You can find these by hovering over the repository names in the Products view on the Repositories tab. The digits at the end of the URL are the repo IDs.
• Configure hammer for passwordless usage by creating a /etc/hammer/cli_config.yml file. More details http://blog.theforeman.org/2013/11/hammer-cli-for-foreman-part-i-setup.html[here].
• Create a jenkins user on the satellite.
• Copy over the public key of the jenkins user on the Jenkins server to the jenkins user on the satellite and ensure that jenkins on the jenkins server can do passwordless ssh to the satellite.
• Configure a Compute Resource on the satellite - I use libvirt, but most people are using VMWare. This will be used to deploy test machines.

=== Bootstrapping In order to create a Content View on the satellite, you need some initial content, so manually trigger a build on Jenkins. This will fail, however it will create some content in the output directories by building the demo RPMs and Puppet modules. Check that these are available then do the following tasks:

• On the satellite, do a manual sync of your ACME SOE product. Check that it syncs correctly and you have got the RPMs and puppet modules that Jenkins built for you.
• Create a Content View (I called mine 'acme-7.0.0') that contains the 3 Red Hat repos, and the two repos (Puppet and RPMs) that you created. Grab the ID of the content view using the same hover over trick as described before.
• Publish the Content View - ensure that it contains your RPMs and puppet modules.
• Create a lifecycle environment that your test clients will live in. I called mine 'Crash' you will need to get the ID of this environment, most likely it will be 2 or you can find it with 'hammer lifecycle-environment list --organization="Default_Organization"'
• Create an activation key that provides access to the RHEL 7 RPMs, RHEL 7 Common, RPMS, and Puppet repos. (you don't need access to the kickstart repo after installation)
• Create a hostgroup (I called mine 'Test Servers') that deploys machines on to the Compute Resource that you configured earlier, and uses the activation key that you created. Create a default root password and make a note of it.
• Create a couple of initial test servers and deploy them. Ensure that they can see your private RPM and puppet repositories.
• In your checkout of acme-soe, edit common.sh and update the following: ** REPO_ID (this is the ID of the RPM repo) ** PUPPET_REPO_ID (this is the ID of the puppet repo) ** TESTVM_HOSTGROUP (this is the name of your test server hostgroup) ** TESTVM_ENV (this is environmnt that your test servers live in) ** TEST_ROOT (this is the root password for your test servers) ** CV (this is the name of your content view)
• Commit common.sh and then push it to your remote - the one that Jenkins is watching.

=== Getting Started At this point, you should be good to go. In fact Jenkins may have already kicked off a build for you when you pushed common.sh.

Develop your build in your checkout of acme-soe. Software that you want packaging goes in 'rpms', puppet modules in 'puppet' and BATS tests in 'tests'. You MUST update versions (in specfiles and metadata.json files) whenever you make a change, otherwise satellite6 will not pick up that you have new versions, even though Jenkins will have repackaged them.

== COMING SOON

• Kickstart files (currently doesn't do anything)
• Hiera usage
• Selective BATS tests - currently all tests run on all test servers, irrespective of whether the puppet module that they are testing is installed