Hi Fred and Gil, When VNF vendors make new VNF release, what is the process in which this new release is instantiated replacing the old instantiation?
I guess new VNF release instantiation replacing the old one should consider following: - No impact to exiting traffic flows. - New traffic flows shall not use old VNF workload. - Old instantiation to get terminated only after existing traffic flows disappear. - Since new release may need more memory, cores, accelerators, I guess new release instantiation has to take advantage of placement path again. - Configuration upgrade (new image might only understand new configuration schema and hence sometimes it is required to run configuration upgrade tool provided by vendor) to transform the existing configuration. - Traffic flow management At the VNF level, traffic flow management can be taken care typically using service mesh technologies (such as ISTIO for L7 and above traffic flows and NSM for L2/L3/L4 traffic flows), but these service mesh technologies need to be configured with right traffic rules upon instantiating new VNF releases). What needs to be taken care at the ONAP level? - How do one onboard new release of VNFs? o How does user indicate that new VNFD is a new release of old VNFD? o Is there any TOSCA representation? How about existing SDC VNFD based on HEAT? - If old release of VNF is already instantiated (once or multiple times), there are manual options of upgrade and auto upgrade? If it is auto upgrade, which component of ONAP shall initiate new upgrade mechanism. I guess it is SO. - Traffic flow management configuration - Since there are various technologies used in different clouds, I guess this belongs in Multi-Cloud plugins. - Since both old and new release would be there for some time together, are there any changes required in virtual inventory of A&AI? - Which component is responsible to upgrade configuration? I guess this should happen before new VNF instantiation starts. Is this a problem that is important for operators? How is this software upgrade problem being solved in ETSI NFV MANO specifications? It would be great if this is considered in orchestration scenarios. Thanks Srini -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15426): https://lists.onap.org/g/onap-discuss/message/15426 Mute This Topic: https://lists.onap.org/mt/29725626/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
