Bug 1102985 - Technical Review Edits: Satellite 6 Beta Transition Guide
Summary: Technical Review Edits: Satellite 6 Beta Transition Guide
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Transition Guide
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: David O'Brien
QA Contact: Athene Chan
URL:
Whiteboard:
: 1017343 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-30 02:30 UTC by Athene Chan
Modified: 2019-09-25 20:29 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-14 03:10:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Athene Chan 2014-05-30 02:30:58 UTC
>  Documentation Title: Transitioning from Satellite 5 to Satellite 6
> Docbuilder Link: http://docbuilder.usersys.redhat.com/22727/
>
* "Table 2.1. Comparison of Satellite 5 and Satellite 6 concepts"
http://docbuilder.usersys.redhat.com/22727/#chap-Comparing_Satellite_5_and_Satellite_6
-
Nice side-by-side comparison table do we want to go into the feature
comparison at all?  For example the stuff in Todd's Gapstatic document
(e.g., no more Monitoring, Solaris support, ISS, future External
Database support etc.)  I understand these are still under discussion so
probably not, just a thought.

* The doc doesn't actually talk about how to transition or the tools
used yet, but that's because that's still WIP and won't be ready for
Sat6 Beta, right?  Should it give an overall process overview or preview
of pre-requisites and rough process though?

* Maybe reference documentation to explain Classic vs. Certificate-based
Subscription Management, and Sat Certs vs. Manifests.  E.g.,
https://access.redhat.com/site/documentation/en-US/Red_Hat_Subscription_Management/1/html/MigratingRHN/sat-certs.html
or
https://access.redhat.com/site/documentation/en-US/Red_Hat_Subscription_Management/1/html/Subscription_Concepts_and_Workflows/index.html#subscr-legacy

Comment 1 RHEL Program Management 2014-05-30 02:57:03 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 David O'Brien 2014-06-02 00:12:47 UTC
Aren't new books supposed to moving or removing all the Doc Conventions material, How to get Help, and so on? I thought that was either going or being moved somewhere less consipicuous.

Comment 4 David O'Brien 2014-06-02 00:19:46 UTC
(In reply to Athene Chan from comment #0)
> >  Documentation Title: Transitioning from Satellite 5 to Satellite 6
> > Docbuilder Link: http://docbuilder.usersys.redhat.com/22727/
> >
> * "Table 2.1. Comparison of Satellite 5 and Satellite 6 concepts"
> http://docbuilder.usersys.redhat.com/22727/#chap-
> Comparing_Satellite_5_and_Satellite_6
> -
> Nice side-by-side comparison table do we want to go into the feature
> comparison at all?  For example the stuff in Todd's Gapstatic document
> (e.g., no more Monitoring, Solaris support, ISS, future External
> Database support etc.)  I understand these are still under discussion so
> probably not, just a thought.

I'd be disinclined to discuss or mention features that might or might not happen. It could introduce expectations from customers that we're not prepared to address.


> 
> * The doc doesn't actually talk about how to transition or the tools
> used yet, but that's because that's still WIP and won't be ready for
> Sat6 Beta, right?  

Last I heard, correct. The tools weren't available except from the repo; not integrated into the product at all.


> Should it give an overall process overview or preview
> of pre-requisites and rough process though?

I'm guessing that's what Grant's SOE docs do. While going through the Sat5 version it discussed what's required at each end (Sat5 & 6), and a high-level overview of the process. No details, really, because it's not customer-ready.

> 
> * Maybe reference documentation to explain Classic vs. Certificate-based
> Subscription Management, and Sat Certs vs. Manifests.  E.g.,
> https://access.redhat.com/site/documentation/en-US/
> Red_Hat_Subscription_Management/1/html/MigratingRHN/sat-certs.html
> or
> https://access.redhat.com/site/documentation/en-US/
> Red_Hat_Subscription_Management/1/html/Subscription_Concepts_and_Workflows/
> index.html#subscr-legacy


If the above material is accurate and answers the questions, can we just provide links to it, or something similar?

Comment 5 David O'Brien 2014-06-03 05:17:25 UTC
(In reply to David O'Brien from comment #3)
> Aren't new books supposed to moving or removing all the Doc Conventions
> material, How to get Help, and so on? I thought that was either going or
> being moved somewhere less consipicuous.

Apparently this is being trialled on RHEL7 first.

Comment 6 David O'Brien 2014-06-18 02:26:37 UTC
> 
> * Maybe reference documentation to explain Classic vs. Certificate-based
> Subscription Management, and Sat Certs vs. Manifests.  E.g.,
> https://access.redhat.com/site/documentation/en-US/
> Red_Hat_Subscription_Management/1/html/MigratingRHN/sat-certs.html
> or
> https://access.redhat.com/site/documentation/en-US/
> Red_Hat_Subscription_Management/1/html/Subscription_Concepts_and_Workflows/
> index.html#subscr-legacy

Added these links to "Manifest" entry in the Glossary of Terms:
http://docbuilder.usersys.redhat.com/22727/#Definitions1

I don't *think* there's anything else that's ready to go into this version of this book. We need to wait until the tools work and we have time to extract material from the SOE docs and flesh this one out.

Comment 7 David O'Brien 2014-06-24 05:17:02 UTC
*** Bug 1017343 has been marked as a duplicate of this bug. ***

Comment 8 Tazim Kolhar 2014-06-27 07:44:04 UTC
VERIFIED

Comment 9 Tazim Kolhar 2014-06-27 07:45:35 UTC
Already assigned to other QA person

Comment 10 David O'Brien 2014-07-14 03:09:09 UTC
Self-reviewed.

Comment 11 David O'Brien 2014-07-14 03:10:25 UTC
Pushed and public.


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