Bug 1386681 - [Doc RFE] Document how to upgrade CNS deployment from OpenShift Container Platform 3.3 to OpenShift Container Platform 3.4.
Summary: [Doc RFE] Document how to upgrade CNS deployment from OpenShift Container Pl...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: doc-Container_Native_Storage_with_OpenShift
Version: cns-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: CNS 3.4
Assignee: Divya
QA Contact: Apeksha
URL:
Whiteboard:
Depends On:
Blocks: 1385252
TreeView+ depends on / blocked
 
Reported: 2016-10-19 12:37 UTC by Anjana Suparna Sriram
Modified: 2017-01-23 07:22 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-23 07:22:44 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Anjana Suparna Sriram 2016-10-19 12:37:48 UTC
Additional info: This bug tracks the following use case from CNS 3.4 Content Plan: https://docs.google.com/document/d/1SrbUxavmmdbLn7FT2nhOAlX0Q3VTsqPCZyx6wV3gjn0/edit#


Use Case #2: As an administrator, I need to upgrade my CNS deployment from OpenShift Container Platform 3.3 to OpenShift Container Platform 3.4.

- Provide detailed upgrade instructions that are also prefaced with any recommendations/best practices.

Comment 5 Divya 2016-10-24 10:46:50 UTC
[Cancelling the need info in BZ# 1386676 and adding it here. This comment seems more relevant to this bug.]

Anjana,

For upgrade, Ken has added the following note to the Resource List [1] doc:

>>>>

RHGS volmanager (heketi) container image upgrade steps - ownership on QE to test, discover steps and provide to CCS for documentation, Devel to assist QE in process.

<<<<

Could you let me know the QE contact and the timelines of when they would be providing the inputs to the CCS?

Thanks!

[1] https://docs.google.com/document/d/1aixoTr0qI6tNCtX3g7FGHthjcZBxYKgJ9t0A-EXqUyo/edit

Comment 7 Divya 2016-10-25 10:11:57 UTC
Anoop,

Raising an early need info to just let you know that I am waiting for the upgrade information :).

Thanks!

Comment 8 Apeksha 2016-11-14 13:53:54 UTC
Steps:

1. Update the heketi packages. Commands - yum update heketi-templates -y
                                          yum update heketi-client -y
2. Update the heketi pod. Command - oc deploy heketi --latest ( generic ->
     oc deploy <dc-name> --latest )

Comment 9 Divya 2016-11-16 06:23:21 UTC
The draft of the Upgrade chapter is available at: https://docs.google.com/document/d/1SaOgjvjexK_4UyPrnBP2Huw-vLyOkjERqAJSaazkQsk/edit#

Comment 10 Divya 2016-11-17 04:28:44 UTC
The draft of the Upgrade chapter is available at: https://docs.google.com/document/d/1SaOgjvjexK_4UyPrnBP2Huw-vLyOkjERqAJSaazkQsk/edit#

Apeksha, could you please review and let me know if it requires any change?

Thanks!

Comment 11 Divya 2016-11-18 10:25:50 UTC
Apeksha,

I have ported the content of the Upgrade chapter to the CNS guide and is available at: https://doc-stage.usersys.redhat.com/documentation/en/red-hat-gluster-storage/3.1/single/container-native-storage-for-openshift-container-platform/#chap-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-Upgrade 

Please review and let me know if it requires any change. Also, do let me know if there are any recommendations/best practices to be followed during/after/before the upgrade.

Moving the bug ON_QA.

Thanks!

Comment 16 Apeksha 2017-01-10 10:35:12 UTC
1. We need to provide upgrade link of openshift document and not installation guide.
2. step 5- there are 2 examples, just give one with nodename and one generic saying <IP/nodename>
3. step 11- we need to mention that we are deleting service and route as well.
4. step 13- this step is not to deploy deploy-heketi but only heketi. we are not deploying deploy-heketi during upgrade


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