Hi Catherine during the Integration weekly meeting we got a discussion on the definition of a test around Backup&restore for Honolulu.
Minutes can be found here: https://wiki.onap.org/display/DW/Integration+Meeting+Minutes And slide deck can be found here: https://wiki.onap.org/download/attachments/6593670/Backup_and_restore_discussion.pdf?version=1&modificationDate=1615311793610&api=v2 It seems that it is still too early to consider a backup&restore scenario for the moment. Andreas took the action to add a warning on the documentation page provided by Aarna and shared during the last TSC meeting. This page is interesting, it describes how to use velero but from a Service Provider perspective it is far from providing a B&R solution for ONAP. As such it could be misleading. Several company community members already gave a try to velero in the past and it seems that as ONAP is not yet fully cloud native enough to use this tool straight forward Moreover most of participants who are managing labs reported resiliency issues concretely components may not survive a restart of a k8s node, pods remain stuck when we would expect them to be evacuated to working nodes according to built-in kubernetes feature. So the plan for Honolulu for Integration will be to focus on resiliency testing for core components (part of the MVP under definition) Test Serie 1 for core component;do run basic tests delete pods(component) run basic tests Test Serie 2 for core component;do run basic_tests delete common DB associated(component) run basic_tests Test Serie 3 for core component;do run basic tests reboot a k8s Node run basic tests I assume the tests from serie 3 will not necessarily work But in the official documentation , we shall be able to identify the non resilient points For the B&R, it is a good idea to setup a task force, Integration team will be happy to participate. this task force will have to deal with several topics 1) management of the DBs in ONAP OOM project already mentioned this topic during last DDF currently more than 30 DB of at least 8 types (Cassandra, Postgresql, Mongo, Maria, MySQL, Redis, Memcached, etcd,...) are running within a full ONAP cluster. It corresponds to 55 pods representing a huge part of the memory required by ONAP..and of course 2 cassandra DB are very costly in terms of memory - the one used exclusively for Music (no more maintained) is maybe not needed. [X] => prepare recommendation to limit the diversity which would ease the B&R operations and reduce the security vulnerability scope like for the baseline image, every project is free to use any DB they want .... but if not using the common DBs, then it is up to the project to provide the resiliency testing and the B&R procedure 2) remove embedded DB (mixed with applicative code) 3) help the projects to migrate and use the recommended images/charts provided by OOM 4) Prepare scenarios (disaster recovery, active/standby, component upgrade, dist upgrade) and create test plan 5) Execute tests OOM project (especially Sylvain & Krzysztof) did already an incredible work but if we want more resiliency the equation is simple: we need more contributors in OOM to work on the cloud native aspects / DB charts and in Integration to test if not possible, my view is that we shall indicate that resiliency is out of the community scope and shall be managed by each company. /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 (#7591): https://lists.onap.org/g/onap-tsc/message/7591 Mute This Topic: https://lists.onap.org/mt/81234024/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
