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 1156251 - Use Case for Architecture, Deployment, and Environment Setup
Summary: Use Case for Architecture, Deployment, and Environment Setup
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Documentation
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite-doc-list
QA Contact: satellite-doc-list
URL:
Whiteboard:
Depends On:
Blocks: GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker
TreeView+ depends on / blocked
 
Reported: 2014-10-24 02:21 UTC by Dan Macpherson
Modified: 2019-09-26 16:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-13 05:24:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Dan Macpherson 2014-10-24 02:21:25 UTC 
I've been in touch with a customer on the portal regarding a rough guide he's written on creating a patch control environment in Satellite 6:

https://access.redhat.com/discussions/1199583

This would be a good candidate for a possible use case to include in the possible deployment scenario guide we were talking about with TAMs.
Comment 1 RHEL Program Management 2014-10-24 02:22:58 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Athene Chan 2014-10-27 03:14:30 UTC 
Thanks Dan!!

Let's discuss the following at the next Scramble or Monthly Meeting:
1. Where do we want to add this
2. When do we want to create this

I am also needinfo-ing Xixi to provide GSS perspective.

Cheers,
Athene
Comment 4 David O'Brien 2014-10-31 03:20:50 UTC 
(In reply to Athene Chan from comment #3)
> Thanks Dan!!
> 
> Let's discuss the following at the next Scramble or Monthly Meeting:

0. Do we want to add this?

New content of any but minor scope needs planning and approval to make sure it fits in with the direction of the doc in general. Seems like an "ok in principle" case, but we need to make sure it's what we really want.

> 1. Where do we want to add this
> 2. When do we want to create this

If we go ahead, will need to add to list/spreadsheet of BZs for priority, yeah?

> 
> I am also needinfo-ing Xixi to provide GSS perspective.
> 
> Cheers,
> Athene
Comment 5 David O'Brien 2014-10-31 03:26:14 UTC 
We might also want to consider this:

http://post-office.corp.redhat.com/archives/satellite6-list/2014-October/msg00533.html
Comment 6 Xixi 2014-11-14 05:03:01 UTC 
(In reply to David O'Brien from comment #4)
> (In reply to Athene Chan from comment #3)
> > Thanks Dan!!
> > 
> > Let's discuss the following at the next Scramble or Monthly Meeting:
> 
> 0. Do we want to add this?
> 
> New content of any but minor scope needs planning and approval to make sure
> it fits in with the direction of the doc in general. Seems like an "ok in
> principle" case, but we need to make sure it's what we really want.
> 
> > 1. Where do we want to add this
> > 2. When do we want to create this
> 
> If we go ahead, will need to add to list/spreadsheet of BZs for priority,
> yeah?
> 
> > 
> > I am also needinfo-ing Xixi to provide GSS perspective.
> > 
> > Cheers,
> > Athene

Thanks Athene/David,
customers often request specific examples in addition to general documentation which makes this a valuable addition for sure. 

So yes to "Do we want to add this?" and "add to list/spreadsheet of BZs for priority". 

"Where do we want to add this" is trickier though - would this better be a part of docs, or, a kbase for more flexibility (like a Ref Arch perhaps)?  I defer to docs team for props and cons in each,  

Xixi
Comment 7 RHEL Program Management 2015-04-21 16:09:31 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 8 Andrew Dahms 2017-05-24 23:04:51 UTC 
Resetting the QA contact.
Comment 9 Andrew Dahms 2017-06-13 05:24:50 UTC 
Since this bug was raised, we have created a new Quick Start Guide to get an environment up and working, re-structured the Installation Guide, and are now working on a new Errata Management Guide that will cover some patching scenarios.

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