Bug 1186419

Summary:	[RFE] Option to hide Content View from selection by user
Product:	Red Hat Satellite	Reporter:	Peter Vreman <peter.vreman>
Component:	Content Views	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WORKSFORME	QA Contact:	Jameer Pathan <jpathan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0.7	CC:	bbuckingham, bkearney, brubisch, dhaval.joshi, jsherril, mmccune, sreber, xdmoon
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-10 16:38:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1122832, 1316897

Description Peter Vreman 2015-01-27 16:11:54 UTC

Description of problem:
We are using product Content Views to store RPM and Puppet modules together and freeze those per product release. The product Content Views are then bundled in Composite Content Views per hostgroup. The users shall only use the Composite Content Views.

Please add an option to Hide Content Views from host/hostgroup assignment boxes.

E.g. this can also be used to prepare a Content View without it being directly visible for all users.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Justin Sherrill 2015-01-27 16:17:47 UTC

In addition we shouldn't publish a puppet environment for content views that have no puppet environments

Comment 7 Peter Vreman 2015-07-30 16:21:51 UTC

Having this option to have a content view only for use by composite content views also can have a huge performance improvement.
- publishing the repo for consumers is not require anymore
- capsule synchronization is not required anymore for those content views

Comment 8 Dhaval 2016-01-21 09:00:15 UTC

I am looking for feature where, if I have setup some filters in "roles", so when user is creating new hostgroup or modifying existing Host, he should only see contentviews with matching criteria in selection tab.

Comment 9 Peter Vreman 2016-10-13 12:11:28 UTC

We have implemented a solution with using a separate Lifecycle environment for the compositecontentviews that shall be visible for the users. The library is then used for the building-block contentviews. The only downside is that we need to do 2 steps, a Publish and aPromote. To remvoe this inefficience there is a request to publuish directly to any lifeccle without the Library, see https://bugzilla.redhat.com/show_bug.cgi?id=1376474

Comment 10 Peter Vreman 2017-05-10 16:38:39 UTC

Closing this RFE as original requester. The lifecycle environments fullfill this.