Hi Morgan, thanks for the info. We would also prefer option 2) for the BBS use case. What would be the next step to create the integration/usecase/bbs repo? is the LFN team creating it?
Regards, David On 12 Feb 2020, at 14:14, [email protected]<mailto:[email protected]> wrote: Hi David we had this discussions some months ago, there is still no real best practices. there are 2 options 1) use existing demo repository (https://git.onap.org/demo/tree/vnfs<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.onap.org%2Fdemo%2Ftree%2Fvnfs&data=02%7C01%7CDavid.PerezCaparros%40swisscom.com%7Cf4d4ee7dbf424f9580c108d7afbd7ce3%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637171100681338614&sdata=%2Bg4SCgXGLaCQ%2BVc3hws%2FFnqznT8OSLkakt1PzmwCo0U%3D&reserved=0>, https://git.onap.org/demo/tree/heat<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.onap.org%2Fdemo%2Ftree%2Fheat&data=02%7C01%7CDavid.PerezCaparros%40swisscom.com%7Cf4d4ee7dbf424f9580c108d7afbd7ce3%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637171100681338614&sdata=MtIrwcRgyDelFW%2BIwkShpgL5Y221a6R5oudPc03%2FXxs%3D&reserved=0>, https://git.onap.org/demo/tree/tosca<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.onap.org%2Fdemo%2Ftree%2Ftosca&data=02%7C01%7CDavid.PerezCaparros%40swisscom.com%7Cf4d4ee7dbf424f9580c108d7afbd7ce3%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637171100681348570&sdata=c9fR0Wjq04DYIlMjWsYTqb5GLdxl8W91pfabd8akyeo%3D&reserved=0>).. include what is needed for your use case assuming that the doc shall remain in integration repository That is what we are doing today As a consequence the repository is becoming big, hard to maintain because from one version to another, code is not necessarily maintained for all the use cases but we do not always know But there is only 1 repository to deal with (from an admin perspective it is easier) 2) create a new repository integration/usecase/bbs (it may take time for the creation but it is possible...) you will be responsible in the INFO.yaml + integration committer as committers + people from the use case you could put the linters you want in the verification chains (python/bash/robot/..) you will be responsible of this repo (license, Code quality,..) it will be easier to detect when the use case is not maintained anymore I assume it would make sense also to reference the simulators/emulators (e.g. integration/simulator/simu-X) the same way (so we could eventually reuse them from one use case to another - today the synergies are limitted between the use cases I prefer to have small repositories with the acurate information I am not very fond of using repository as shared storage disc so my recommendation will be 2) but 1) is possible /Morgan Le mercredi 12 février 2020 à 11:57 +0000, [email protected]<mailto:[email protected]> a écrit : Hi Morgan, as part of the BBS use case development, we are updating our APEX policy to make it compatible with the latest version of the Policy framework. We cannot store this new use case specific policy in the ONAP Policy repository, as advised by the Policy PTL, in order to keep separated use case and platform code. Can we use the ONAP demo repository for pushing use case specific code like BBS APEX policy? what’s the best practice in these cases? Regards, David -- David Pérez Caparrós Lead DevOps Engineer, 5G Service Orchestration Operations & Network Engineering, Mobile Swisscom (Switzerland) [email protected]<mailto:[email protected]> _________________________________________________________________________________________________________________________ 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 (#20054): https://lists.onap.org/g/onap-discuss/message/20054 Mute This Topic: https://lists.onap.org/mt/71210179/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
