Red Hat Bugzilla – Bug 838132
Document subscription-manager registration.
Last modified: 2012-12-04 12:22:44 EST
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@redhat.com 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.
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?
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.
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.
Waiting on Bug # 838136, Bug # 838137 to move to QA.
It wasn't marked correctly but this was a tracker, all tracked bugs are VERIFIED or CLOSED so moving tracker to VERIFIED.