Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Event posted on 11-20-2009 09:24am EST by RFE-tool
1) Customer Name:
Eidgenossische-Technische Hochschule Zuerich (ETHK)
2) Nature Of Problem:
Configuration Channels in Satellite can not be shared among organisations
like Software Channels
3) Business Requirements Satisfied By Request:
Duplicating configuration channels is not practical.
4) Functional Requirements That Are Not Presently Possible:
A Configuration Channel should be shareable amoung the organisations on a
satellite
5) What Will Success Look Like:
Configuration Channels can be shared like 'normal' Software Channels
6) Desired Release Vehicle:
next release
7) Request Meets The Rhel Inclusion Criteria:
Yes
8) Affected Packages:
rhn-satellite
9) Sales Sponsor:
aflierl as SRM
10) Rh Business Opportunity With Customer:
Big customer with 6500+ system
11) Status And Risk To Contract If Not Satisfied:
little, but customer will contact the spacewalk community about this
12) If this request is vendor specific, has the customer engaged the
partner as well?:
Not Applicable
This event sent from IssueTracker by jwest [SEG - Feature Request]
issue 368163
Customers can try this out with Satellite 6 MDP2, users are able to share puppet configuration across organizations with the ability to pick and choose which organizations can see what configuration modules.
Moving to a future release for consideration.
You can't currently share Content Views between organizations in Satellite 6 so this RFE isn't really satisfied.
This is entirely possible in 6.1:
* Create a Content View in OrgA with various Puppet Classes
* Publish
* go to OrgB under the Organizations list
* ensure the Puppet Environments from OrgA are also added and available in OrgB
* You can then create Host Groups and Hosts with Puppet Classes from OrgA
This can pass as a completed RFE if you can provision a host in OrgB with Puppet Classes in OrgA
VERIFIED
sat 6.2.0 Beta (GA11)
The Puppet Environments can now be shared across organizations (they can be assigned to multiple).
so they also can be used for host provisioning in other Orgs.
[attached screenshots]
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2016:1500