Skip to content

Latest commit

 

History

History
100 lines (63 loc) · 5.57 KB

production.md

File metadata and controls

100 lines (63 loc) · 5.57 KB
Raw

Production Environments

This covers how you can use the tooling provided by Forklift to spin up a production environment for real deployments or evaluation purposes. The tooling can spin up deployments automatically using Vagrant or be used on your virtual or bare metal machines.

Vagrant

The Vagrant configuration can currently run pointing at either a Libvirt or Virtualbox setup.

Using VirtualBox (Windows, OS X)

If you're using Linux, we recommend Libvirt. The default setup in the Vagrantfile is for VirtualBox. It has been tested against VirtualBox 4.2.18. To use Install VirtualBox from the 4.2 downloads page. Vagrant 1.6.5+ can be downloaded and installed from Vagrant Downloads

Libvirt (Linux)

The Vagrantfile provides default setup and boxes for use with the vagrant-libvirt provider. To set this up:

  1. Ensure you have Vagrant installed
    • For libvirt:
      1. Ensure you have the prerequisites installed sudo yum install ruby rubygems ruby-devel gcc gcc-c++
  2. Install libvirt. On CentOS/Fedora/RHEL, run sudo yum install @virtualization libvirt-devel
  3. Install the libvirt plugin for Vagrant (see vagrant-libvirt page for more information) vagrant plugin install vagrant-libvirt
  4. Make sure your user is in the qemu group. (e.g. [[ ! "$(groups $(whoami))" =~ "qemu" ]] && sudo usermod -aG qemu $(whoami))
  5. Set the libvirt environment variable in your .bashrc or for your current session - export VAGRANT_DEFAULT_PROVIDER=libvirt
  6. If you are asked to provide your password for every command, follow these policykit steps.

Vagrant Box Installation

The available versions and types of installs varies as new releases are made and older releases are deprecated. The most accurate way to see the list of available installations is to run the status command:

vagrant status

This will show a list of boxes by type and OS. For example, at the time of this documentation both Foreman 1.12 and Katello 3.1 had been released. Thus, when doing a status I see, for example:

centos7-foreman-nightly                 not created (libvirt)
centos7-katello-nightly                 not created (libvirt)
centos7-foreman-proxy-nightly           not created (libvirt)
centos7-foreman-1.16                    not created (libvirt)
centos7-katello-3.4                     not created (libvirt)

This indicates that both Foreman and Katello nightly (our unstable releases) are available as well as production installations on Centos 7 boxes of Foreman, Katello and a Foreman Proxy. To fire up a Katello 3.4:

Start the installation for CentOS 7:

vagrant up centos7-katello-3.4

This will create a libvirt based virtual machine running the Katello server on CentOS.

BYOB

This setup assumes you are either deploying on a non-VM environment or you already have a Virtual machine setup. The deployment can be done either locally on the box or via SSH using an Ansible inventory script with proper access.

Remote Deployment

This use case assumes that you are on a box that has SSH access to the target box for installation and that Ansible can properly realize the target host via an inventory script.

  1. Ensure Ansible is installed
  2. Clone this repository - git clone https://github.com/theforeman/forklift.git
  3. Enter the repository - cd forklift
  4. Create an inventory file with your hosts in the inventories subfolder. You can also pass a different inventory to ansible-playbook using --inventory or -i.
  5. Change the variable remote_user in ./ansible.cfg to the appropriate value (the user that will log into the remote machine)
  6. Determine the compatible versions of Foreman and Katello you want to install based on the Katello install instructions at https://github.com/theforeman/forklift/blob/master/vagrant/config/versions.yaml. Replace the 3.16 in the URL with whatever version of Katello you want to install.

For a release version in production:

ansible-playbook -l <target-host> playbooks/katello.yml -e foreman_repositories_version=WANTED_FOREMAN_VERSION -e katello_repositories_version=WANTED_KATELLO_VERSION

For nightly production:

ansible-playbook -l <target-host> playbooks/katello.yml

After installing a Katello server, you could then spin up a Capsule with the assumption the Katello server can talk to the Capsule and vice versa.

ansible-playbook -l <target-capsule-host> playbooks/capsule_31.yml

Local Deployment

  1. ssh to target machine as root
  2. Install Ansible -- yum install ansible (for example from the EPEL repo)
  3. Clone this repository - git clone https://github.com/theforeman/forklift.git
  4. Enter the repository - cd forklift
  5. Make sure DNS is set up properly. This is a Foreman requirement, not an Ansible requirement.
  6. Determine the compatible versions of Foreman and Katello you want to install based on the Katello install instructions at https://github.com/theforeman/forklift/blob/master/vagrant/config/versions.yaml.

For a release version in production:

ansible-playbook -l localhost playbooks/katello.yml -e foreman_repositories_version=WANTED_FOREMAN_VERSION -e katello_repositories_version=WANTED_KATELLO_VERSION

For nightly production:

ansible-playbook -l localhost playbooks/katello.yml