Frequently Asked Questions
Short list here so far, but we'll add more as we get 'em.
Q.) Does Katello work on CentOS?
A.) Theoretically it will work on CentOS, but we're not officially supporting it yet. Please give it a try, and patches are welcome!
Q.) What about Spacewalk?
A.) The Satellite product will continue to use the upstream Spacewalk project. Similarly the Katello project will be an upstream component of the CloudForms product. We first announced the Katello project and the future of Satellite at the 2011 Red Hat Summit. You can review those presentation slides here:
The Future of Red Hat Network Satellite: A New Architecture Enabling Traditional Datacenters & the Cloud
Q.) How do I get started?
A.) Click here. Do it now!
Q.) How is Katello licensed?
A.) Katello source code is licensed with GPLv2+, you can view a copy of the license here.
Q.) Why does Katello have its own Rubygem repo?
A.) The reason was to keep the gems listed in Gemfile.lock in sync with the gems we had packaged. Generally when you do a bundle install the Gemfile.lock file will be updated with all of the newest gems from the repo. So if rubygems.org releases an updated gem 'foo' with version 1.2, the Gemfile.lock will be updated automatically to use foo-1.2, regardless of whether we have packaged it or not. Basically bundle install will update the Gemfile.lock with the NEWEST versions in the remote gem repo, updating our product dependencies without intention to do so.
So if you were to commit your updated gemfile.lock, the next time the katello rpm was built & installed, rails would refuse to start because we haven't built foo-1.2 as an rpm.
Turns out that this helped a ton with debugging and testing as well.