Bug 1868270
| Summary: | [Doc RFE] Document GCP support for OCS 4.x (Technology Preview) | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Container Storage | Reporter: | Anjana Suparna Sriram <asriram> |
| Component: | documentation | Assignee: | Kusuma <kbg> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Bukatovic <mbukatov> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.5 | CC: | bkunal, ebenahar, ebondare, etamir, mbukatov, ocs-bugs, rcyriac |
| Target Milestone: | --- | Keywords: | Documentation, FutureFeature |
| Target Release: | OCS 4.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-09-18 13:20:11 UTC | Type: | Bug |
| 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: | |||
| Bug Blocks: | 1826399 | ||
|
Comment 5
Elena Bondarenko
2020-08-31 10:26:57 UTC
Chapter 1.4. Creating a new backing store, explains that. Chapter 7 is a generic instructions and the user can create multiple backing stores on any cloud provider, including AWS, even if the platform is hosted on GCP. It should go back to ON_QA. In section 1.3, the `standard` storage class is being mentioned as the one for OCS installation. This storageclass means that OSDs will reside on HDDs and not SSDs. For SSD, we should instruct on using the `faster` storage class: apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: faster provisioner: kubernetes.io/gce-pd parameters: type: pd-ssd volumeBindingMode: WaitForFirstConsumer I installed new cluster, manually following the sections:
- 1. Deploying OpenShift Container Storage on Google Cloud
- 2. Verifying OpenShift Container Storage deployment
And I was able to install OCS cluster, and verify the installation with success.
Versions used:
- OCP 4.5.0-0.ci-2020-09-04-161649
- OCS 4.5.0-546.ci
Minor issues
------------
In "Verification steps" part of section "1.3. Creating a new backing store", the output
of noobaa cli tool looks like this:
```
.
.
.
------------------
- Backing Stores -
------------------
NAME TYPE TARGET-BUCKET PHASE AGE
gcp-backing-store google-cloud-storage ocs-backing-store Ready 10m27s
------------------
- Bucket Classes -
------------------
NAME PLACEMENT PHASE AGE
noobaa-default-bucket-class {Tiers:[{Placement: BackingStores:[gcp-backing-store]}]} Ready 1h58m21s
```
Which could be little misleading, because the instructions doesn't include removal of pv-pool, and so
the backing store for pv-pool should be listed there as well, like this:
```
NAME TYPE TARGET-BUCKET PHASE AGE
gcp-backing-store google-cloud-storage ocs-backing-store Ready 10m27s
noobaa-default-backing-store pv-pool Ready 1h58m21s
```
So basically the fix includes adding one like with noobaa-default-backing-store.
For the sake of simplicity of tech-preview instructions, I'm not suggesting to remove the pv-pool (procedure would require to remove buckets and then the backing store ...).
A similar issue is visible in the Table 2.1. Pods corresponding to OpenShift Container storage cluster, which
doesn't include noobaa-default-backing-store-noobaa-pod-* pod.
Minor issues from comment 11 were fixed in current doc preview. Based on this and on comment 10 and comment 11, I'm moving this BZ to VERIFIED state. |