Bug 1040150 - 5.1. Configuring Broker Host Entitlements
Summary: 5.1. Configuring Broker Host Entitlements
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 2.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Alex Dellapenta
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-10 20:25 UTC by Luke Meyer
Modified: 2017-03-08 17:35 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-09 03:25:46 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Luke Meyer 2013-12-10 20:25:21 UTC
http://documentation-devel.engineering.redhat.com/docs/en-US/OpenShift_Enterprise/2/html-single/Deployment_Guide/index.html#sect-Configuring_Broker_Host_Entitlements

Table 5.1. OpenShift Enterprise Broker Host Channel Options
Client tools - "Required only if you intend to use the client tools on the node host." => should be broker host. Better: "Required only if you intend to use the client tools for testing on the broker host."


5.1.1. Using Red Hat Subscription Management
Procedure 5.1. To Configure Entitlements with RHSM:
Steps 2 & 3 - I don't think in most cases they will want to subscribe to two different pools. I believe typically they'll have one "OpenShift Enterprise" pool for a trial, or one "OSE Broker Infrastructure" pool for a real purchase (as well as others for the node and EAP). Anyway we don't really want to lead them to expect to need two here.
Step 4. - As of 2.0, there won't be any channels enabled aside from RHEL. You could use "subscription-manager repos" instead but that will probably be too much info (with debug and source repos). Rather than say this is the output of "yum repolist" I think it would be best to say that these are the repos you'll need to enable with yum-config-manager --enable.

5.1.2. Using RHN Classic
Procedure 5.2. To Configure Entitlements with RHN Classic:
Step 2. Basically same problem as w/ RHSM - none of these will be enabled (unless they knew to set up and use an activation key) so they'll have to enable them explicitly with "rhn-channel -a -c <channel name>".


5.1.3. Preventing Third-Party Package Conflicts
This section name is kind of misleading... it will give the impression it's not needed if you don't have EPEL/Puppet/something else on this system. This is required setup for avoiding issues with RHEL and JBoss content too. In fact, it may be best to inline the relevant parts of the yum-validator kbase (https://access.redhat.com/site/articles/386273) now that 2.0 has shipped.


More or less the same criticisms apply to http://documentation-devel.engineering.redhat.com/docs/en-US/OpenShift_Enterprise/2/html-single/Deployment_Guide/index.html#sect-Configuring_Node_Host_Entitlements  -- except there are more channels and they really are likely to need two pool ids. Separate bug?

Comment 7 Alex Dellapenta 2014-01-14 23:00:13 UTC
The OSE 1 and OSE 2 Deployment Guides have been updated to address this BZ.


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