Bug 1849752
| Summary: | [Doc RFE] Document Azure 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: | unspecified | ||
| Version: | 4.4 | CC: | dcain, ebenahar, edonnell, etamir, fbalak, kbg, khartsoe, nbecker, nberry, ocs-bugs, rcyriac |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | OCS 4.4.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Technology Preview | |
| Doc Text: |
.Microsoft Azure Technology Preview support
OpenShift Container Storage can now be installed and managed on Microsoft Azure. For more information see, the link:https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.5/html-single/deploying_and_managing_openshift_container_storage_on_microsoft_azure/index[Deploying and managing OpenShift Container Storage on Microsoft Azure] guide.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-08-04 16:24:07 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: | 1859307 | ||
| Attachments: | |||
|
Comment 7
Elad
2020-07-13 15:14:04 UTC
In addition to comment #7, there are some things to fix in the docs: - In the preview docs, there are some wrong references to AWS and AWS components, like in chapter `8.4.3. Available dynamic provisioning plug-ins` - 'AWS Elastic Block Store (EBS)' is mentioned. - UPI is mentioned as a deployment type where different operations are possible, like scaling out (add node) and replacing a node - chapter `6.2.2. Adding a node on Azure user-provisioned infrastructure`. The problem is that OCS is supposed to be supported on Azure IPI only There could be more, Martin and I will continue the review @Elad, Don't think we need to. Once the Azure BS was crated and set as the default, it will be used when not providing a specific BS when creating an OBC. Moving back to ASSIGNED following Filip's input Created attachment 1710240 [details]
Azure screenshot for "Figure 2.9. Details card in Persistent Storage Overview Dashboard"
Created attachment 1710241 [details]
Azure screenshot for "Figure 2.11. Details card in Object Service Overview Dashboard"
|