Hi Dan, I'm Tri Nguyen from Tata Communications. I am working on the rolling upgrade of SDNC, which has the JIRA Ticket https://jira.onap.org/browse/OOM-2273. I would like to ask an issue relate to the SDNC upgrade from release E to F. In the code of SDNC release F, there is a script file named "InstallSDNC.sh" which is included in the Job Post-install helm hook template. This is used to initialize a brand new database of SDNC inside mariadb, a.k.a sdnctl. This is the case when we install a new SDNC application in release F. However, when we upgrade SDNC from release E to release F, database sdnctl in release E is migrated to release F. There are two events required some anticipation:
* Job Post-install helm hook trigger InstallSDNC.sh will not be executed. * Old data sdnctl from release E will be replicated to release F Due to these events, will there be any incompatibility using old data sdnctl from release E by the SDNC of release F? I notice that the docker image of SDNC is different between release E and F, so that I don't know if the data populated in release F using Job Post-install helm hook Is any different from data in release E. For example, is there any new structure of table in sdnctl in release F compared to release E? Assuming that we have a few user-customized artifacts that are developed by SDNC in release E. When we migrate the data of artifacts to release F using rolling upgrade, will SDNC continue to query old data of these artifacts successfully? Since these questions are very specific to SDNC project, I hope you can give us some information to address these issues for a proper SDNC upgrade. Hope to hear from you. Regards Tri -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20982): https://lists.onap.org/g/onap-discuss/message/20982 Mute This Topic: https://lists.onap.org/mt/74031709/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
