Hide Forgot
Document URL: Section Number and Name: Describe the issue: Suggestions for improvement: Additional information:
Issue 1: Directions are confusing for version: User should not be executing both of these commands: Subscribe to the OpenShift Enterprise 3.2 repo This enables you to install the Openshift client packages # subscription-manager repos --enable=rhel-7-server-ose-3.2-rpms # yum install atomic-openshift-clients # yum install atomic-openshift Subscribe to the OpenShift Container Platform 3.3 repo This enables you to install the Openshift client packages # subscription-manager repos --enable=rhel-7-server-ose-3.3-rpms # yum install atomic-openshift-clients # yum install atomic-openshift Issue 2: If router doesn't deploy, user can use port-forwarding but it's finicky. It should remind user to check status of the port forwarding if heketi-cli commands aren't working. This may prevent many users from being stuck. Issue 3: When creating the PV/PVCs it should be done in a consistent manner. Either all yaml or json. It's strange to mix both Issue 4: Selectors: Comments directly in doc: https://docs.google.com/document/d/1CDb35N7N_qIW98ga9967QnCDHTE_dHhKTrNn0CWEJzk/edit?ts=57e38508
(In reply to Erin Boyd from comment #2) > Issue 1: > Directions are confusing for version: > User should not be executing both of these commands: > Subscribe to the OpenShift Enterprise 3.2 repo > This enables you to install the Openshift client packages > > # subscription-manager repos --enable=rhel-7-server-ose-3.2-rpms > > # yum install atomic-openshift-clients > > # yum install atomic-openshift > > Subscribe to the OpenShift Container Platform 3.3 repo > This enables you to install the Openshift client packages > > # subscription-manager repos --enable=rhel-7-server-ose-3.3-rpms > > # yum install atomic-openshift-clients > > # yum install atomic-openshift I have already fixed this issue based on Erin's email on 29/09/2016 Link to the doc: https://doc-stage.usersys.redhat.com/documentation/en/red-hat-gluster-storage/3.1/single/red-hat-gluster-storage-container-native-with-openshift-platform/#idm139904512129824 > > Issue 2: > If router doesn't deploy, user can use port-forwarding but it's finicky. It > should remind user to check status of the port forwarding if heketi-cli > commands aren't working. This may prevent many users from being stuck. > > Issue 3: > When creating the PV/PVCs it should be done in a consistent manner. Either > all yaml or json. It's strange to mix both > > Issue 4: Selectors: > Comments directly in doc: > https://docs.google.com/document/d/ > 1CDb35N7N_qIW98ga9967QnCDHTE_dHhKTrNn0CWEJzk/edit?ts=57e38508
(In reply to Divya from comment #3) > (In reply to Erin Boyd from comment #2) > > Issue 1: > > Directions are confusing for version: > > User should not be executing both of these commands: > > Subscribe to the OpenShift Enterprise 3.2 repo > > This enables you to install the Openshift client packages > > > > # subscription-manager repos --enable=rhel-7-server-ose-3.2-rpms > > > > # yum install atomic-openshift-clients > > > > # yum install atomic-openshift > > > > Subscribe to the OpenShift Container Platform 3.3 repo > > This enables you to install the Openshift client packages > > > > # subscription-manager repos --enable=rhel-7-server-ose-3.3-rpms > > > > # yum install atomic-openshift-clients > > > > # yum install atomic-openshift > > I have already fixed this issue based on Erin's email on 29/09/2016 > > Link to the doc: > https://doc-stage.usersys.redhat.com/documentation/en/red-hat-gluster- > storage/3.1/single/red-hat-gluster-storage-container-native-with-openshift- > platform/#idm139904512129824 > > > > > Issue 2: > > If router doesn't deploy, user can use port-forwarding but it's finicky. It > > should remind user to check status of the port forwarding if heketi-cli > > commands aren't working. This may prevent many users from being stuck. Erin, We have already added the following note in the "4.1. Preparing the Red Hat OpenShift Container Platform Cluster" section : If the router setup fails, use the port forward method as described in Appendix B, Client Configuration using Port Forwarding. Appendix B has information how to configure the client using Port Forwarding Do you want us to add a similar note in any other section? > > Issue 3: > > When creating the PV/PVCs it should be done in a consistent manner. Either > > all yaml or json. It's strange to mix both > > > > Issue 4: Selectors: > > Comments directly in doc: > > https://docs.google.com/document/d/ > > 1CDb35N7N_qIW98ga9967QnCDHTE_dHhKTrNn0CWEJzk/edit?ts=57e38508 I have incorporated the comments listed in the google doc.
The two topology files should match (using 7.1.2.2 as the RIGHT one) 7.1.3.1. Updating Topology file and 7.1.2.2
(In reply to Erin Boyd from comment #6) > The two topology files should match (using 7.1.2.2 as the RIGHT one) > 7.1.3.1. Updating Topology file and 7.1.2.2 I have updated the topology files in "Chapter 7. Managing Clusters" to address the issue wrt hostname and IP address. Link to the doc: https://doc-stage.usersys.redhat.com/documentation/en/red-hat-gluster-storage/3.1/single/red-hat-gluster-storage-container-native-with-openshift-platform#chap-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-Managing_Clusters
Verified.
Verified