Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1842420

Summary: [DOCS][l10n] Need description about how to create PV for statically provisioning VMware vSphere volumes
Product: OpenShift Container Platform Reporter: Masaki Furuta ( RH ) <mfuruta>
Component: Documentation-l10nAssignee: Localization RH <l10n-bugzilla>
Status: CLOSED ERRATA QA Contact: Vikram Goyal <vigoyal>
Severity: medium Docs Contact: Vikram Goyal <vigoyal>
Priority: high    
Version: 4.4CC: aos-bugs, asasaki, bfuru, gotoutkq, jokerman, piqin, vigoyal, wduan
Target Milestone: ---   
Target Release: 4.2.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1783437 Environment:
Last Closed: 2020-06-04 11:31:52 UTC Type: ---
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: 1783437    
Bug Blocks:    
Attachments:
Description Flags
Japanese doc needs update on the section 2.14.2 none

Description Masaki Furuta ( RH ) 2020-06-01 08:48:40 UTC 
+++ This bug was initially created as a clone of Bug #1783437 +++

Document URL: 
  
  https://docs.openshift.com/container-platform/4.2/storage/persistent-storage/persistent-storage-vsphere.html#vsphere-static-provisioning_persistent-storage-efs

Section Number and Name: 

  Persistent storage using VMware vSphere - Configuring persistent storage | Storage | OpenShift Container Platform 4.2

Describe the issue: 

  In the section "Statically provisioning VMware vSphere volumes", the document currently only describes how to make a PV with pv.yaml without volumeName.
  But it is very confusable for the customer to learn how to create PVC based on this PV from this description.

Suggestions for improvement: 

  Would you please add an example of pvc.yaml with volumeName, as well as adding volumeName to pv.yaml ?

Additional information:

--- Additional comment from Masaki Furuta on 2019-12-20 16:41:13 JST ---

(In reply to Masaki Furuta from comment #0)
...
>   Would you please add an example of pvc.yaml with volumeName, as well as
> adding volumeName to pv.yaml ?

Hi Vikram,

Would you please provide examples (pvc.yaml) for users to have correct understanding, as well as existing pv.yaml ?

I am grateful for your help.

Thank you,

BR,
Masaki

--- Additional comment from Masaki Furuta on 2020-04-06 19:16:13 JST ---

Hello,

Could you please provide a news on this ?

On this BZ, the customer request adding an example of pvc.yaml with volumeName, as well as adding volumeName to pv.yaml for Statically provisioning section [0]. 

   [0] https://docs.openshift.com/container-platform/4.4/storage/persistent_storage/persistent-storage-vsphere.html#vsphere-static-provisioning_persistent-storage-efs

Because, as we have an example of pvc.yaml for Dynamically provisioning section [1] and that's all what we need, but example of pvc.yaml is missing at Statically provisioning [0] . Because both of pvc.yaml and pv.yaml is required for Statically provisioning. That's confusable for customer to know what are needed for Statically provisioning.

    [1] https://docs.openshift.com/container-platform/4.4/storage/persistent_storage/persistent-storage-vsphere.html#vsphere-dynamic-provisioning-cli_persistent-storage-efs

I am grateful for your help.

Thank you,

BR,
Masaki

--- Additional comment from Bob Furu on 2020-05-05 04:51:13 JST ---

Hello Furuta-san,

Thank you for the details. I have created PR 21805: https://github.com/openshift/openshift-docs/pull/21805 to get this info added in OCP 4.2+.

Moving to QA
Liang or Ping - PTAL

Thanks,
Bob

--- Additional comment from Wei Duan on 2020-05-07 18:52:13 JST ---

I reviewed the PR 21805 and LGTM.

--- Additional comment from Bob Furu on 2020-05-07 22:44:16 JST ---

Out for peer review

--- Additional comment from Bob Furu on 2020-05-08 05:56:40 JST ---

PR merged and CP'ed to 4.2-4.5. Verified docs are published and live: https://docs.openshift.com/container-platform/4.4/storage/persistent_storage/persistent-storage-vsphere.html#vsphere-static-provisioning_persistent-storage-efs 
Closing bug.
Comment 2 Masaki Furuta ( RH ) 2020-06-01 08:56:58 UTC 
Dear Localization Team,

Thank you for your time and efforts on localizing product documentation ( and of course, I am thanking to original version too) . 
These are really fantastic help for us.

I know all of you members in doc team are very busy and I am so sorry for urging you, but may I obtain your help to update following Japanese version based on changes on original Bug #1783437 ?

   https://access.redhat.com/documentation/ja-jp/openshift_container_platform/4.4/html-single/storage/index#vsphere-static-provisioning_persistent-storage-efs .

I am grateful for your help and support.

Thank you,

BR,
Masaki
Comment 3 Masaki Furuta ( RH ) 2020-06-01 08:58:09 UTC 
(In reply to Aiko from comment #1)

Yes. Thank you so much.

/mMasaki
Comment 5 Aiko 2020-06-01 10:37:45 UTC 
Created attachment 1694068 [details]
Japanese doc needs update on the section 2.14.2
Comment 9 Masaki Furuta ( RH ) 2020-06-04 11:31:52 UTC 
(In reply to Aiko from comment #8)
...
> The Japanese documentation is updated. Please confirm and let us know if any
> problem.
> Thank you.

Dear Aiko-san,

I am closing this BZ on behalf of the customer, as I have obtained feedback from them that they has been satified with current published version.

Thank you,

BR,
Masaki