Katello 2.4 Documentation

Transitioning from Katello 1.4 to 2.0

Can I do an in place upgrade?

Due to the evolution of Katello as a standalone application into a plugin to The Foreman, an upgrade is not feasible. We regret that instead of an upgrade you will need to transition to a new server.

Terminology Changes

The following terminology changes have occured between Katello 1.4 and 2.0:

  • Systems are now Content Hosts
  • System Groups are now Host Collections
  • Environments are now Lifecycle Environments

How do I transition?

The general steps for transitioning are:

  1. Standup a new server
  2. Install Katello 2.0
  3. Transition Content
  4. Re-create other entities such as Activation Keys and System Groups
  5. Transition Systems

Installing a new Katello 2.0 Server

Follow the installation instructions for the latest Katello version: Installation

Configuration of the Katello 2.0 Server

If you are using Red Hat Content you will want to import your Subscription Manifest in the same way as you had done on your previous Katello instance. You will likely want to create the same set of Lifecycle Environments.

Transitioning Content

Red Hat Content

For Red Hat repositories that come from your subscription manifest, we recommend to re-enable these and sync them again to the new server.

Custom Content

For custom content you can re-create them with the same upstream url and sync them again. Alternatively you can sync them from your existing Katello server. Assuming the custom repo has been published with ‘HTTP’ enabled, set the url of the repository in the Katello 2.0 server to the repository’s url on the Katello 1.4 Server. It would look something like: http://hostname/pulp/repos/Default_Organization/Library/custom/product_name/repo_name

For custom content that was not published via HTTP, it will not be available for the new Katello Server to easily sync. You can, however, SCP it over to the new server and then manually import it there:

  1. On the Katello 2.0 server, create a directory to hold each repo:

    mkdir -p /repos/my_product/my_repo

    repeat for each product and repo you want to transfer. Note that you cannot use /tmp for this as pulp can not sync from /tmp locally.

  2. On the Katello 1.4 server, copy over each repo:

    scp - r /var/lib/pulp/published/https/repos/ACME_Corporation/Library/custom/my_product/my_repo/      root@KATELLO2.0:/repos/my_product/my_repo

    Replacing ‘KATELLO2.0’ with the hostname or IP address of your Katello 2.0 server. Note that each repo path will follow a similar directory path of /var/lib/pulp/published/https/repos/ORG/Library/custom/PRODUCT/REPO. Repeat for each Repository you want to copy.

  3. On the Katello 2.0 server, ensure the permissions allow apache to read the files: chmod 755 /repos/my_product/my_repo -R
  4. Create a new Repsoitory on the Katello server with a feed of file:///repos/my_product/my_repo
  5. Sync the new Repository
  6. Change the feed on the new Repository to that of the desired upstream url. This will allow future syncs to pull in content from the upstream Repository.

Transitioning other Items

Other items such as:

  • Users
  • Activation Keys
  • Host Collections (formerly System Groups)

Will all need to be recreated manually through the UI or through the Hammer CLI tool. We recommend to create things like Activation Keys and Host Collections prior to transitioning your Systems over to make it easier to re-register them.

Transitioning Systems

In order to move systems to the new Katello server you will need to re-register them. On each system:

  1. Remove the existing bootstrap rpm:

    rpm -e `rpm -qf /etc/rhsm/ca/candlepin-local.pem`
  2. Install the new bootstrap rpm (replacing HOSTNAME with your Katello server’s hostname):

    rpm -Uvh http://HOSTNAME/pub/katello-ca-consumer-latest.noarch.rpm
  3. Register:

    subscription-manager register --user=admin --password=changme --org=Default_Organization --environment=Library

    Or you may create an activation key and register with that:

    subscription-manager register --org=Default_Organization --activationkey=mykey

Foreman 2.0.1 has been released! Follow the quick start to install it.

Foreman 1.24.3 has been released! Follow the quick start to install it.