Katello integrates open source systems management tools into a single solution for controlling the lifecycle of your machines.
Ruby JavaScript HTML CSS
Latest commit e5cd23c Nov 29, 2016 @jlsherrill jlsherrill committed with jlsherrill Fixes #17512 - index content in a paged manner
This does two major things:

 1) Centralizes fetching and indexing of content to central places
(pulp_database_unit.rb & pulp_content_unit.rb). This should help making
content units pluggable in the future easier, as all the code is based
around the unit DB class or service class.

 2) Change the indexing so that we only keep a page (default is 500) of
units in memory. Previously we would fetch all units in pages, but then
take the entire list and index that. With this change we actually index
just the page while we have it, and then throw it away to fetch another
page and process that.
Failed to load latest commit information.
.tx fix paths in .tx/config after git reorganization Apr 29, 2013
app Fixes #17512 - index content in a paged manner Dec 8, 2016
bin Fixes #15035 - Adding rails script to katello (#6045) May 13, 2016
ca adding redhat-uep.pem to katello ca Oct 5, 2011
config Fixes #15950 - CV Composite accepts latest version Dec 6, 2016
db Fixes #15950 - CV Composite accepts latest version Dec 6, 2016
engines/bastion_katello Refs #17317 - correctly update docker tags to manifests Dec 8, 2016
lib Fixes #17512 - index content in a paged manner Dec 8, 2016
locale Merge pull request #5760 from bkearney/bkearney/10241 Feb 9, 2016
spec Fixes #16921 - Get candlepin's subs just once when repo enabling Nov 17, 2016
test Fixes #17512 - index content in a paged manner Dec 8, 2016
vendor Fixes #4062: remove jScrollPane and references. Jun 24, 2016
.gitignore Fixes #15042 - Use a single fixture dir (#6309) Sep 13, 2016
.hound.yml Fixes #16242 - Enable HoundCI for ruby linting (#6265) Aug 31, 2016
.mention-bot Fixes #16924 - Add mention-bot config Oct 13, 2016
.rspec initial commit Jun 15, 2011
.rubocop.yml Fixes #16710 - Setting TargetRubyVersion in rubocop (#6350) Sep 29, 2016
.rubocop_todo.yml Fixes #16500 - Support rubocop 0.42 (#6306) Sep 12, 2016
.simplecov Setup simplecov in katello Mar 5, 2013
CONTRIBUTING.md Fixes #15034 - Remove old scripts from katello (#6044) May 13, 2016
CONTRIBUTORS adding myself to contrib Jul 1, 2015
Gemfile Engine: Removing old gem files Dec 6, 2013
LICENSE.txt set Markdown as default markup Jan 16, 2013
README.md Fixes #15669 - Fixing old stuff in README (#6180) Jul 13, 2016
katello.gemspec Fixes #16801 - Move from underscore to lodash Nov 2, 2016



Build Status Code Climate Dependency Status

Full documentation is at http://www.katello.org


Katello is a systems life cycle management plugin to Foreman. Katello allows you to manage thousands of machines with one click. Katello can pull content from remote repositories into isolated environments, and make subscriptions management a breeze.

Currently, it is able to handle Fedora and Red Hat Enterprise Linux based systems.


The most common way to set up Katello for development is to use katello-deploy. This will set up a Vagrant instance with the Katello codebase checked out. You can also run setup.rb directly with katello-deploy if you prefer to not use Vagrant.

There is also katello-devel-installer if you would like to use that.

If you have questions or issues with any of the above methods, feel free to ask for assistance on #theforeman-dev IRC channel or via the foreman-dev mailing list.

Test Run

At this point, the development environment should be completely setup and the Katello engine functionality available. To verify this, go to your Foreman checkout:

  1. Start the development server

    cd $GITDIR/foreman
    rails s
  2. Access Foreman in your browser (e.g. https://<hostname>/). Note that while Rails will listen on port 3000, the dev installer will set up a reverse proxy so HTTPS on port 443 will work.

  3. Login to Foreman (default: admin and changeme)
  4. If you go to https://<hostname>/about and view the "Plugins" tab, you should see a "Katello" plugin listed.

Reset Development Environment

In order to reset the development environment, all backend data and the database needs to be reset. To reiterate, the following will destroy all data in Pulp, Candlepin and your Foreman/Katello database. From the Foreman checkout run:

rake katello:reset

Found a bug?

That's rather unfortunate. But don't worry! We can help. Just file a bug in our project tracker.


See the developer documentation.

Contact & Resources


Most of our documentation (both for users and developers) can be found at Katello.org.