Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 813693 (katello-foreman) - RFE: Integrate Foreman
Summary: RFE: Integrate Foreman
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: katello-foreman
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-18 08:42 UTC by Lukas Zapletal
Modified: 2019-09-26 13:33 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 19:44:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lukas Zapletal 2012-04-18 08:42:51 UTC
This is a feature tracker bug that shows progress of foreman integration and also link other feature requests on the foreman side that needs to be done to fully integrate it.

Comment 1 Lukas Zapletal 2012-04-18 08:46:11 UTC
To fully integrate Katello, Foreman API must be accessible with oauth. Once oauth is enabled in the Foreman configuration and secret and token is given, Foreman should authenticate all requests with valid oauth and automatically authorize those requests as "admin". Separate role can be used for this, but all permission must be given. Katello is expected to be able to do anything.

http://theforeman.org/issues/1576

Comment 2 Lukas Zapletal 2012-04-18 08:48:54 UTC
Katello and Foreman is expected to run on the same server. Since default ports HTTP and HTTPS are already used by Katello and its backend engines, Foreman will need to be working with a prefix. Since Anaconda installer have problems with kickstarting from different ports than standard 80 and 443, this configuration variable will be likely necessary to support Katello/Foreman kickstarting.

http://theforeman.org/issues/1577

Comment 3 Lukas Zapletal 2012-04-18 11:36:12 UTC
Katello is multi-tenant system and it supports organizations and environments. Typically, every resource belongs to an organization and a environment. Foreman already supports environments for hosts (I am not sure if they can be assigned across whole Foreman) and we could use them for this purpose. It would be good idea to implement also organizations, so we would have direct mapping between Katello and Foreman.

From the history, Candlepin did support only organizations (called owners there), Pulp does not support either orgs or envs. In Candlepin it was tricky to work without environments and some time ago we have decided to implement environments in Candlepin. In Pulp there is no support for them, so resources have very long and ugly names like:

Organization_Name-environment_name-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_5_Server_RPMs_x86_64_5Server

We would need to do the same for Foreman. Each resource (like operating system, installation media etc) would need to have similar name. But with organizations and environments extended for all resources (or at least installation media, operating systems and templates) we could only use the Candlepin product name which is shorter (Red_Hat_Enterprise...).

From our experiences I think it would be better to implement this into the Foreman than to use the string-concatenating approach. Please consider this feature.

http://theforeman.org/issues/1578

Comment 4 Bryan Kearney 2014-01-21 19:07:45 UTC
Moving to Sat6 to be tracked there. Upstream bugs are moving to redmine.


Note You need to log in before you can comment on or make changes to this bug.