Hi, I got several questions from use case owners recently. As we are approaching the M4 milestone, I prefer to make a global answer even if some use cases are not directly concerned by these questions.
Please note that a session during the Use case meeting will take place on the 11th of March, it will be the occasion to exchange on this topic and more generally to improve the formal process dealing with use case integration. the use case weather board can be found here: https://wiki.onap.org/display/DW/2%3A+Frankfurt+Release+Integration+Testing+Status until tests are automated in CI, this will be the reference page for our exchange. In M4, the content of the page is supposed to be frozen (no additional features/use cases/..). Only the status shall be updated from M4 to the release. For the release the status shall be completed. @All please review this wiki page before the M4. Add the link to your documentation. 1) Testing on windriver if it is a new use case, you need to validate it on an Integration lab (windriver) The procedure to get access to the windriver lab is described in the FAQ https://wiki.onap.org/pages/viewpage.action?pageId=29787070 Then you could have access to one of the labs. I am still not always fully clear on the config of the different lab SB-00, SB-01, SB-XX, but Marco has a better view than me on that. It is a reccurent issue to get the good view of the versions used in the deployment especially when you need components in staging state. SB-00 has been reinstalled 7 days ago but as far as I can see several healthcheck tests are currently failing . an html page describing the status of the different lab would be helpful but it is not available for the moment. Please note that the onap-k8s test integrated in the CI daily runs now provides the full view of the cluster including a html report to get the version of all the components but as it is based on Master, there is no staging components. It shoudl be possible to run this test on each SB-0X then build a web page to reference the results. 2) documentation the use case documentation must be ready for review for M4 (so before the completion of the tests). Of course the documentation could be amended during the integration test phase to include the known issues, restrictions, ... Documentation shall be pushed through a gerrit patchset in the integration repository. it shall include a rst (describing) the use case + amend the main page referencing all the use cases (https://git.onap.org/integration/tree/docs/docs_usecases.rst). These rst files are used to build the official documentation (wiki is a working documentation, not an official one) In a previous mail, most of you indicated that the documentation was already almost ready, minor adaptations were needed. It is time to finalize these adaptations. I would suggest a circular review as imagined in El Alto, it means asking people to review your doc and you review the doc of other use cases in order to improve the consistancy of the documentation. The documentation shall allow any user (including ONAP newcomers) to replay the use case in his/her lab. It shall include a high level definition, an architecture, an installation procedure, a testing procedure. Documentation shall be finalized for the M4 (https://jira.onap.org/browse/INT-1444<https://jira.onap.org/browse/INT-1444?jql=labels%20%3D%20relman%20AND%20fixversion%20%3D%20%22Frankfurt%20Release%22%20AND%20%22Epic%20Link%22%20%3D%20%22R6%20M4%20Code%20Freeze%22%20AND%20project%20not%20in%20(SANDBOX%2C%20CIMAN)%20AND%20type%20%3D%20Task%20AND%20project%20%3D%20%22INT%22%20ORDER%20BY%20status%20ASC%2C%20updated%20ASC>) 3) sync meeting a slot dedicated to use cases will be systematically added in the agenda of the integration weekly meeting to collect the issues/concerns during this M4 and ensure the status follow-up -> release phase (Wednesday 2 PM UTC) Please join the mmeting if you can. If you cannot (time zone), please update the wiki page status and/or send me a mail for specific information. If you detect a bug during your tests - select the good project, do not put Integration if the problem is clearly located in a component. If you do not know, use Integration - please add the label integration and usecase, with some filters it is possible to create a dedicated integration dashboard https://jira.onap.org/secure/RapidBoard.jspa?rapidView=207&view=detail&selectedIssue=INT-793&quickFilter=633 Do not hesitate to join the rocketchat realtime support line on https://team.onap.eu (accept the security exception then go on onap-integration) if you have any question. Regards Morgan _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20159): https://lists.onap.org/g/onap-discuss/message/20159 Mute This Topic: https://lists.onap.org/mt/71697635/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
