Bug 838132 (RHEV31_SAM_DOC)

Summary:	Document subscription-manager registration.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Stephen Gordon <sgordon>
Component:	Documentation	Assignee:	Stephen Gordon <sgordon>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.1.0	CC:	acathrow, dyasny, jskeoch
Target Milestone:	---	Keywords:	Tracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	838133 838134 838136 838137 (view as bug list)		Environment:
Last Closed:	2012-12-04 17:22:44 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:	838133, 838134, 838136, 838137
Bug Blocks:	815465

Description Stephen Gordon 2012-07-06 18:03:47 UTC

Description of problem:

We need to document the use of subscription-manager to register to RHN and subscribe to the required channels for RHEV. This will need to be done alongside RHN Classic instructions which we already provide.

We should probably concentrate on the command line, as most RHEV-M servers probably wont run a GUI (we can defer to the SAM guides for those that do want to use it though).

# subscription-manager register
Username: sgordon
Password:
The system has been registered with id: <UUID>
# subscription-manager list --available
# subscription-manager subscribe --pool=<POOLID>
Successfully consumed a subscription from the pool with id <UUID>.

Need to work out what the names to grep out of list available are though for RHEV channels, I only have my employee subs which aren't specific enough.

Comment 1 Stephen Gordon 2012-07-06 18:16:04 UTC

Andy, what's the easiest way to add the RHEV subs using the subscription-manager command line tools? Should we be getting users to follow the route I outline in the bug description of specifying the pools (and are the pool ids static such that we could include them in the docs)? 

Or is it better/easier to use the activation key (where does one find this in RHN-land?

Comment 3 Stephen Gordon 2012-07-11 13:24:28 UTC

Andy, I think to document installation of RHEV-M from certificate based RHN using subscription-manager I *think* we will need to know the 'Product Name', and 'Product Id' as they will appear in the output of:

# subscription-manager list --available

We would need these values for all the RHEV channels if we are to update the documentation to cover the use of subscription-manager.

Comment 4 Stephen Gordon 2012-07-11 18:46:17 UTC

Talking further with Jay, RHEV-M boxes need these entitlements:

JBoss Enterprise Application Platform
Red Hat Enterprise Virtualization
Red Hat Enterprise Linux Server

RHEL Hosts will need these entitlements:

Red Hat Enterprise Virtualization
Red Hat Enterprise Linux Server

RHEL Guests will need these entitlements:

Red Hat Enterprise Linux Server

Subscription requirements for RHN Classic boxes remain unchanged, with the exception of the JBoss channel which of course moves from EAP5 to EAP6.

Comment 5 Stephen Gordon 2012-10-26 15:39:48 UTC

Waiting on Bug # 838136, Bug # 838137 to move to QA.

Comment 6 Stephen Gordon 2012-10-30 18:39:56 UTC

It wasn't marked correctly but this was a tracker, all tracked bugs are VERIFIED or CLOSED so moving tracker to VERIFIED.