| Summary: | [RFE] Official page of users defined domain name | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Shinobu KINJO <skinjo> |
| Component: | documentation | Assignee: | Dan Macpherson <dmacpher> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | RHOS Documentation Team <rhos-docs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 (Liberty) | CC: | dmacpher, lbopf, rhos-docs, skinjo, srevivo |
| Target Milestone: | --- | Keywords: | Documentation |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-11-15 13:21:03 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: | |
|
Description
Shinobu KINJO
2016-11-10 02:47:48 UTC
Hi Kinjo-san, My apologies for the delay. At the moment, our writing resources are focused primarily on documentation work for the Red Hat OpenStack Platform 10 release. I agree with you that adding all solution/KBase content to the documentation is not something that we can or should do. If this information is interesting and useful to many customers, we may be able to add links from the Director Installation and Usage guide to these solutions. If the customers are looking directly to the Customer Portal to find this information in solutions, rather than in the initial setup guide, adding links may not be useful. What do you think? (In reply to Lucy Bopf from comment #1) > Hi Kinjo-san, > > My apologies for the delay. At the moment, our writing resources are focused > primarily on documentation work for the Red Hat OpenStack Platform 10 > release. > > I agree with you that adding all solution/KBase content to the documentation > is not something that we can or should do. If this information is > interesting and useful to many customers, we may be able to add links from > the Director Installation and Usage guide to these solutions. If the > customers are looking directly to the Customer Portal to find this > information in solutions, rather than in the initial setup guide, adding > links may not be useful. It would be good enough to add pointers KCS/KBase to the official guide with titles. e.g., APPENDIX NN - Title1 URL - Title2 URL or something similar. Because volumes of current guide is already big enough. Important thing here is that the customers would be able to get all necessary information to build their stack system from same content. > > What do you think? Can you kindly update this BZ? Hi Shinobu, Sorry for the delay on this. We discussed this item and decided it might be a good idea to include a link to all kbase articles tagged with openstack. Here's an example: https://access.redhat.com/search/#/knowledgebase?q=&product=Red%20Hat%20OpenStack%20Platform&documentKind=Solution,Article How does that sound? Hi Kinjo-san, Do you have any thoughts about Dan's proposal in comment 4? Would adding the suggested link be helpful? No response in several months and have tried contacting requester. Closing this BZ. |