Katello integrates open source systems management tools into a single solution for controlling the lifecycle of your machines.
Clone or download
johnpmitsch Fixes #25818 - Show virt-who hypervisor type
* Fixes #25818 - Show virt-who hypervisor type

virt-who hypervisors use "hypervisor::type" rather than
"virt::host_type" for type. This commit updates the UI
to check for both.

To review, register a virt-who hypervisor and check
the type field in the content host details page is
filled out.
Latest commit 9b38ba7 Jan 17, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.storybook Fixes #21931 - Add react-storybook to Katello Dec 12, 2017
.tx Fixes #21836 - Add in the string extraction logic Nov 5, 2018
app Fixes #25818 - Show virt-who hypervisor type Jan 17, 2019
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 #25087 - Import module inventory from subman (#7788) Nov 6, 2018
db Fixes #25794 - rename unit uuid to pulp_id Jan 10, 2019
engines/bastion_katello Fixes #25818 - Show virt-who hypervisor type Jan 17, 2019
lib Fixes #25866 - handle missing puppet dist on upgrade task Jan 17, 2019
locale Fixes #21836 - Add in the string extraction logic Nov 5, 2018
spec Fixes #25860 - remove old product init code Jan 15, 2019
test Fixes #25818 - Show virt-who hypervisor type Jan 17, 2019
vendor Fixes #20544 - Make CSS assets findable to sprockets Aug 14, 2017
webpack Fixes #25837 - Change "Red Hat Subscriptions" to "Subscriptions" Jan 11, 2019
.babelrc Fixes #21575 - Use hound to run eslint Nov 16, 2017
.gitignore Fixes #21836 - Add in the string extraction logic Nov 5, 2018
.rspec initial commit Jun 15, 2011
.rubocop.yml Refs #25300 - Update Rubocop config to 0.59.x Oct 30, 2018
.rubocop_todo.yml Refs #25300 - Update Rubocop config to 0.59.x Oct 30, 2018
.simplecov Setup simplecov in katello Mar 5, 2013
.travis.yml Fixes #24960 - Adds tests coverage via coveralls Nov 16, 2018
CONTRIBUTING.md Fixes #23639 - Updated CONTRIBUTING.md May 24, 2018
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 #24327 - Update outdated references in README Jul 20, 2018
katello.gemspec Fixes #25696 - finish migration to concurrent-ruby-1.1 Jan 10, 2019
package.json Fixes #21045 - React components for formatting dates Jan 3, 2019
travis_run_js_tests.sh Fixes #24960 - Adds tests coverage via coveralls Nov 16, 2018



Build Status Code Climate

Full documentation is at https://www.theforeman.org/plugins/katello/


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 forklift. This will set up a virtual machine with the Katello codebase checked out. Please use the forklift documentation found in the repository for how to get started with forklift.

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 on freenode or via the community forum

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.

Annotated Pulp and Candlepin Workflows and test Scenarios

See the annotation docs for more information.

Contact & Resources


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