forked from docs/docsportal
fixing some formatting issues
This commit is contained in:
parent
37438d7b53
commit
db80a84bcb
@ -4,6 +4,6 @@ Are there any plans to move other documents CDR, HLD, and PD as well to the plat
|
|||||||
|
|
||||||
Yes, the plan for this year is:
|
Yes, the plan for this year is:
|
||||||
|
|
||||||
Start integration of Hybrid Documentation to Help Center 3.0. Kevin Heyong has already confirmed that he initiates the talks to R&D.
|
- Start integration of Hybrid Documentation to Help Center 3.0. Kevin Heyong has already confirmed that he initiates the talks to R&D.
|
||||||
|
|
||||||
Start integration of internal Huawei documents to Help Center 3.0 (this will be a bit challenging as this sort of documents are not present in Huawei documentation system and R&D is taking care of them by their own so the only existing source of the documentation is doc word type)
|
- Start integration of internal Huawei documents to Help Center 3.0 (this will be a bit challenging as this sort of documents are not present in Huawei documentation system and R&D is taking care of them by their own so the only existing source of the documentation is doc word type)
|
||||||
|
|||||||
@ -2,4 +2,4 @@
|
|||||||
How and where should we submit bugs when a non-conformity is found in an already released/deployed PROD documentation?
|
How and where should we submit bugs when a non-conformity is found in an already released/deployed PROD documentation?
|
||||||
======================================================================================================================
|
======================================================================================================================
|
||||||
|
|
||||||
Using Gitea/Github issues on respective repositories already mentioned in very first questions.
|
Using Gitea/Github issues on respective repositories already mentioned in :ref:`very first question <where_and_how_can_i_access_the_system_to_check_all_squad_components_and_the_current_tasks_or_raised_issues>`.
|
||||||
|
|||||||
@ -2,4 +2,4 @@
|
|||||||
How and where should we submit bugs when the documentation URL is wrong (the link is not working)?
|
How and where should we submit bugs when the documentation URL is wrong (the link is not working)?
|
||||||
==================================================================================================
|
==================================================================================================
|
||||||
|
|
||||||
Using Gitea/Github issues on respective repositories already mentioned in very first questions depending on the affected environment.
|
Using Gitea/Github issues on respective repositories already mentioned in :ref:`very first question <where_and_how_can_i_access_the_system_to_check_all_squad_components_and_the_current_tasks_or_raised_issues>` depending on the affected environment.
|
||||||
|
|||||||
@ -2,4 +2,4 @@
|
|||||||
How can the docs be deployed to PRE-PROD and PROD and who will be the responsible to do that?
|
How can the docs be deployed to PRE-PROD and PROD and who will be the responsible to do that?
|
||||||
=============================================================================================
|
=============================================================================================
|
||||||
|
|
||||||
By triggering the label "gate" on gitea/github the respective automated jobs will trigger final merge and build of the documentation as well as publishing of the documentation to respective portal (PREPROD/PROD). Responsibility can be addressed to the labelling permission. Remaining stuff is in hands of zuul automation.
|
By triggering the label "**gate**" on gitea/github the respective automated jobs will trigger final merge and build of the documentation as well as publishing of the documentation to respective portal (PREPROD/PROD). Responsibility can be addressed to the labelling permission. Remaining stuff is in hands of zuul automation.
|
||||||
|
|||||||
@ -2,4 +2,4 @@
|
|||||||
How can we accept the entire document when we are fine with it? Who will have the right to make a doc version final?
|
How can we accept the entire document when we are fine with it? Who will have the right to make a doc version final?
|
||||||
====================================================================================================================
|
====================================================================================================================
|
||||||
|
|
||||||
See the last option in previous comment. This can be delegated to different persion chosen by squad.
|
See the last option in :ref:`Previous question <how_can_we_revert_back_to_a_previous_document_version>`. This can be delegated to different person chosen by squad.
|
||||||
|
|||||||
@ -4,8 +4,8 @@ How can we revert back to a previous document version?
|
|||||||
|
|
||||||
In git the revert action would mean just another PR with changes pushing the document to previous state. To minimize revert situations both Gitea/Github represents 3 phases of validatiing the documentation.
|
In git the revert action would mean just another PR with changes pushing the document to previous state. To minimize revert situations both Gitea/Github represents 3 phases of validatiing the documentation.
|
||||||
|
|
||||||
Automated check jobs which validate syntax, conversion and build possibility of the documentation change.
|
- Automated check jobs which validate syntax, conversion and build possibility of the documentation change.
|
||||||
|
|
||||||
Manual approval based on QA/UAT review.
|
- Manual approval based on QA/UAT review.
|
||||||
|
|
||||||
Labelling the PR with Gate Label which is only applicable when previous 2 conditions are succefully completed. (Final Gate label will initiate auto-merge jobs and final publishing of the documentation change to Help Center portal). Squad can decide that this final "Go" can be triggered by different person only delegated for releasing activities.
|
- Labelling the PR with **gate** label which is only applicable when previous 2 conditions are succefully completed. (Final Gate label will initiate auto-merge jobs and final publishing of the documentation change to Help Center portal). Squad can decide that this final "Go" can be triggered by different person only delegated for releasing activities.
|
||||||
|
|||||||
@ -4,4 +4,4 @@ How to check the rendered HTML of the entire document in the browser (which butt
|
|||||||
|
|
||||||
In the document PR (for example https://gitea.eco.tsi-dev.otc-service.com/docs/resource-template-service/pulls) search for the latest documentation check job result (for example build-otc-umn) if it's older than one week please add comment in PR "recheck" which will trigger new check jobs and will pre-render documentation again. If it's actual (not older than one week) click on the job, then click on artifacts then click on docs preview site and you should appear on pre-rendered HTML documentation.
|
In the document PR (for example https://gitea.eco.tsi-dev.otc-service.com/docs/resource-template-service/pulls) search for the latest documentation check job result (for example build-otc-umn) if it's older than one week please add comment in PR "recheck" which will trigger new check jobs and will pre-render documentation again. If it's actual (not older than one week) click on the job, then click on artifacts then click on docs preview site and you should appear on pre-rendered HTML documentation.
|
||||||
|
|
||||||
service doc PR -> Conversation -> build jobs (build-otc-api-ref, build-otc-umn, otc-tox-docs) -> Artifacts -> Docs preview site -> choose doc type -> HTML
|
**service doc PR -> Conversation -> build jobs (build-otc-api-ref, build-otc-umn, otc-tox-docs) -> Artifacts -> Docs preview site -> choose doc type -> HTML**
|
||||||
|
|||||||
@ -4,8 +4,8 @@ How to request a document modification (for a single comment or for multiple com
|
|||||||
|
|
||||||
After finishing the review (and raising the comments) you have 3 options how to close the review:
|
After finishing the review (and raising the comments) you have 3 options how to close the review:
|
||||||
|
|
||||||
Approve - PR is being approved and can be moved to the next stage
|
- **Approve** - PR is being approved and can be moved to the next stage
|
||||||
|
|
||||||
Comment - Raising the comments without explicit requirement of any changes (not blocking approval)
|
- **Comment** - Raising the comments without explicit requirement of any changes (not blocking approval)
|
||||||
|
|
||||||
Request Changes - Approval is not given and PR is blocked by requesting the changes which means that PR should receive another commit of changes and only after that PR will be ready for next review round
|
- **Request Changes** - Approval is not given and PR is blocked by requesting the changes which means that PR should receive another commit of changes and only after that PR will be ready for next review round
|
||||||
|
|||||||
@ -2,4 +2,4 @@
|
|||||||
How will we be notified once Huawei will upload something (new doc, or modify existing doc)?
|
How will we be notified once Huawei will upload something (new doc, or modify existing doc)?
|
||||||
============================================================================================
|
============================================================================================
|
||||||
|
|
||||||
After Huawei will create new PR in doc-exports respective PR is autocreated in target document repository (for example in https://gitea.eco.tsi-dev.otc-service.com/docs/resource-template-service/pulls) as QA/UAT or other members of the squad are also members of the gitea group which is taking care of the respective service document repositories they should be automatically notified by email about newly created PR in the respective service document repository.
|
After Huawei creates new PR in doc-exports repository the respective PR is autocreated in target document repository (for example in https://gitea.eco.tsi-dev.otc-service.com/docs/resource-template-service/pulls). QA/UAT or other squad members are also members of the gitea group with defined ownership of the respective service document repositories and they should be automatically notified by email about newly created PRs.
|
||||||
|
|||||||
@ -4,25 +4,28 @@ Where and how can I access the system to check all squad components and the curr
|
|||||||
|
|
||||||
There are multiple places based on source of the review task. All Gitea links are related to Huawei changes and changes being introduced on the PREPROD docportal:
|
There are multiple places based on source of the review task. All Gitea links are related to Huawei changes and changes being introduced on the PREPROD docportal:
|
||||||
|
|
||||||
https://gitea.eco.tsi-dev.otc-service.com/docs/doc-exports/pulls - general place where Huawei is introducing new PRs with the documents imports in HTML file (this is meta repository and not the final repository for a review of the change)
|
- https://gitea.eco.tsi-dev.otc-service.com/docs/doc-exports/pulls - general place where Huawei is introducing new PRs with the documents imports in HTML file (this is meta repository and not the final repository for a review of the change)
|
||||||
|
|
||||||
https://gitea.eco.tsi-dev.otc-service.com/docs/TARGET-SERVICE-NAME/pulls - this is place where Huawei's PRs are converted to service RST PRs which are ready for a review by QA/UAT for example https://gitea.eco.tsi-dev.otc-service.com/docs/resource-template-service/pulls
|
- https://gitea.eco.tsi-dev.otc-service.com/docs/TARGET-SERVICE-NAME/pulls - this is place where Huawei's PRs are converted to service RST PRs which are ready for a review by QA/UAT for example https://gitea.eco.tsi-dev.otc-service.com/docs/resource-template-service/pulls
|
||||||
|
|
||||||
https://gitea.eco.tsi-dev.otc-service.com/org/docs/teams/docs-orchestration-rw/repositories - good starting point for seeing all service doc repositories of the whole squad for PREPROD documentation
|
- https://gitea.eco.tsi-dev.otc-service.com/org/docs/teams/docs-orchestration-rw/repositories - good starting point for seeing all service doc repositories of the whole squad for PREPROD documentation
|
||||||
|
|
||||||
https://github.com/opentelekomcloud-docs/TARGET-SERVICE-NAME/pulls - this is place where PRs are being created for changes coming from gitea after approval or from external changes (customer/TSI..) for example https://github.com/opentelekomcloud-docs/resource-template-service/pulls
|
- https://github.com/opentelekomcloud-docs/TARGET-SERVICE-NAME/pulls - this is place where PRs are being created for changes coming from gitea after approval or from external changes (customer/TSI..) for example https://github.com/opentelekomcloud-docs/resource-template-service/pulls
|
||||||
|
|
||||||
https://github.com/orgs/opentelekomcloud-docs/teams/docs-orchestration-rw/repositories - good starting point for seeing all service doc repositories of the whole squad for PROD documentation
|
- https://github.com/orgs/opentelekomcloud-docs/teams/docs-orchestration-rw/repositories - good starting point for seeing all service doc repositories of the whole squad for PROD documentation
|
||||||
|
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
In future we plan to implement also some monitoring dashboard to have all different PRs under one roof
|
In future we plan to implement also some monitoring dashboard to have all different PRs under one roof
|
||||||
|
|
||||||
|
|
||||||
There are multiple places based on source of the issue. All Gitea links are related to issues addressed to Huawei or Ecosystem squad and issues related to PREPROD doc portal
|
There are multiple places based on source of the issue. All Gitea links are related to issues addressed to Huawei or Ecosystem squad and issues related to PREPROD doc portal
|
||||||
|
|
||||||
https://gitea.eco.tsi-dev.otc-service.com/docs/docsportal/issues - general PREPROD docsportal issues
|
- https://gitea.eco.tsi-dev.otc-service.com/docs/docsportal/issues - general PREPROD docsportal issues
|
||||||
|
|
||||||
https://gitea.eco.tsi-dev.otc-service.com/docs/TARGET-SERVICE-NAME/issues - this is place for service based issue towards Huawei or Ecosystem squad for PREPROD for example https://gitea.eco.tsi-dev.otc-service.com/docs/resource-template-service/issues
|
- https://gitea.eco.tsi-dev.otc-service.com/docs/TARGET-SERVICE-NAME/issues - this is place for service based issue towards Huawei or Ecosystem squad for PREPROD for example https://gitea.eco.tsi-dev.otc-service.com/docs/resource-template-service/issues
|
||||||
|
|
||||||
https://github.com/opentelekomcloud-docs/docsportal/issues - general PROD docsportal issues (also customers can raise the issues here)
|
- https://github.com/opentelekomcloud-docs/docsportal/issues - general PROD docsportal issues (also customers can raise the issues here)
|
||||||
|
|
||||||
https://github.com/opentelekomcloud-docs/TARGET-SERVICE-NAME/issues - this is place for service based issue towards TSI (also customers can raise issues here) for PROD for example https://github.com/opentelekomcloud-docs/resource-management-service/issues
|
- https://github.com/opentelekomcloud-docs/TARGET-SERVICE-NAME/issues - this is place for service based issue towards TSI (also customers can raise issues here) for PROD for example https://github.com/opentelekomcloud-docs/resource-management-service/issues
|
||||||
|
|||||||
@ -2,5 +2,5 @@
|
|||||||
Where should we check whether a document related bug exists or not for our components, if a customer opens it or it is coming from another squad?
|
Where should we check whether a document related bug exists or not for our components, if a customer opens it or it is coming from another squad?
|
||||||
=================================================================================================================================================
|
=================================================================================================================================================
|
||||||
|
|
||||||
looking at Gitea/Github issues on respective repositories already mentioned in very first questions. Eventually in future we would like to introduce some dashboard for monitoring and visualization such issues based on the service/squad.
|
looking at Gitea/Github issues on respective repositories already mentioned in :ref:`very first question <where_and_how_can_i_access_the_system_to_check_all_squad_components_and_the_current_tasks_or_raised_issues>`. Eventually in future we would like to introduce some dashboard for monitoring and visualization such issues based on the service/squad.
|
||||||
Q23:
|
Q23:
|
||||||
|
|||||||
@ -4,10 +4,10 @@ Who and how will request a new document update when for instance a new feature i
|
|||||||
|
|
||||||
Again multiple way how to request documentation update:
|
Again multiple way how to request documentation update:
|
||||||
|
|
||||||
as a part of standard JIRA RM process there's task for Huawei (delivery documentation task) with mandatory field Documentation PR link which Huawei need to fill in with gitea link to be able to close the task.
|
- as a part of standard JIRA RM process there's task for Huawei (delivery documentation task) with mandatory field Documentation PR link which Huawei need to fill in with gitea link to be able to close the task.
|
||||||
|
|
||||||
as a new issue in https://gitea.eco.tsi-dev.otc-service.com/docs/doc-exports/issues
|
- as a new issue in https://gitea.eco.tsi-dev.otc-service.com/docs/doc-exports/issues
|
||||||
|
|
||||||
as a new issue in https://gitea.eco.tsi-dev.otc-service.com/docs/TARGET-SERVICE-NAME/issues
|
- as a new issue in https://gitea.eco.tsi-dev.otc-service.com/docs/TARGET-SERVICE-NAME/issues
|
||||||
|
|
||||||
email contact to Huawei R&D from this link: https://confluence.tsi-dev.otc-service.com/display/HUAW/Documentation+Gitops+Rollout+and+Status+page
|
- email contact to Huawei R&D from this link: https://confluence.tsi-dev.otc-service.com/display/HUAW/Documentation+Gitops+Rollout+and+Status+page
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user