Hi Timo, I’m not aware of such effort in ONAP currently (especially not in El Alto which doesn’t include new functionalities). I think this should be discussed in modeling subcommittee first.
Ofir From: [email protected] [mailto:[email protected]] On Behalf Of t.puha via Lists.Onap.Org Sent: Tuesday, September 10, 2019 10:10 AM To: [email protected]; Sonsino, Ofir <[email protected]>; [email protected] Cc: [email protected]; 'ARINDAM MONDAL' <[email protected]> Subject: Re: [onap-discuss] [onap-sdc] VM Images in VNF Packages and elsewhere in ONAP Hi, and more strange thing I forgot, the vCSCF.csar on https://wiki.onap.org/display/DW/Csar+Structure<https://urldefense.proofpoint.com/v2/url?u=https-3A__protect2.fireeye.com_url-3Fk-3D1da2a2bdceffdbc0.1da329f2-2Dddd7a08cf87e6704-26u-3Dhttps-3A__wiki.onap.org_display_DW_Csar-2BStructure&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=r9I4HaeTZWnzwEqiRY1_Hv-5a-5rlv9P2qxiDTBCt58&m=2Gbq2q6CDQnUqYvAou5z9fgUqKXpcKImg6w25a58SmE&s=DrKw9kj_IEZPca9LV32KRYm3ZEkQ6qd9kU82es4y7ss&e=> refers to an image in still another way: ImageFile_OMP: attributes: tosca_name: ImageFile_OMP properties: file_url: /SoftwareImages/cscf_v5_2016_1213_1423.vmdk container_type: bare name: cscf_v5_2016_1213_1423.vmdk disk_format: qcow2 type: tosca.nodes.nfv.ext.ImageFile I suspect this refers to a filesystem inside somewhere in VFC, but I can’t find any documentation about this and how the image is supposed to get there. -Timo From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of t.puha via Lists.Onap.Org Sent: tiistai 10. syyskuuta 2019 9.51 To: 'Sonsino, Ofir' <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]>; 'ARINDAM MONDAL' <[email protected]<mailto:[email protected]>> Subject: [onap-sdc] VM Images in VNF Packages and elsewhere in ONAP Hi, I’ve been looking around VNF packaging and modeling issues lately. One critical piece of that is handling of VM images and I have found some traces of multiple ways of handling these. Mostly I’m interested in TOSCA versions of VNF packages but I hope that this is handled the same way for Heat packages. In terms of https://wiki.onap.org/display/DW/Csar+Structure<https://urldefense.proofpoint.com/v2/url?u=https-3A__protect2.fireeye.com_url-3Fk-3D1da2a2bdceffdbc0.1da329f2-2Dddd7a08cf87e6704-26u-3Dhttps-3A__wiki.onap.org_display_DW_Csar-2BStructure&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=r9I4HaeTZWnzwEqiRY1_Hv-5a-5rlv9P2qxiDTBCt58&m=2Gbq2q6CDQnUqYvAou5z9fgUqKXpcKImg6w25a58SmE&s=DrKw9kj_IEZPca9LV32KRYm3ZEkQ6qd9kU82es4y7ss&e=> I’m interested in “CSAR provided by the vendor to the SDC for onboarding” and ” CSAR created by SDC for VF” types of things mostly. This page clearly says “Images are not supported.” in the artifact section. Some of the examples (like these https://wiki.onap.org/display/DW/vCPE+with+Tosca+VNF+Test+Guide<https://urldefense.proofpoint.com/v2/url?u=https-3A__protect2.fireeye.com_url-3Fk-3D5ad02a407346ffbd.5ad1a10f-2Dd4b9f73ea03ad319-26u-3Dhttps-3A__wiki.onap.org_display_DW_vCPE-2Bwith-2BTosca-2BVNF-2BTest-2BGuide&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=r9I4HaeTZWnzwEqiRY1_Hv-5a-5rlv9P2qxiDTBCt58&m=2Gbq2q6CDQnUqYvAou5z9fgUqKXpcKImg6w25a58SmE&s=rG55tAikVp97OlYRgFvXVD1I9L8G1MLRMQFBlxgpv3I&e=>, direct link to example TOSCA: https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=tosca/vCPE/vgw/MainServiceTemplate.yaml;h=5a8611a056462cfe4f42da8a942e19eab83b33fd;hb=HEAD<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Ddemo.git-3Ba-3Dblob-3Bf-3Dtosca_vCPE_vgw_MainServiceTemplate.yaml-3Bh-3D5a8611a056462cfe4f42da8a942e19eab83b33fd-3Bhb-3DHEAD&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=r9I4HaeTZWnzwEqiRY1_Hv-5a-5rlv9P2qxiDTBCt58&m=2Gbq2q6CDQnUqYvAou5z9fgUqKXpcKImg6w25a58SmE&s=uHpdvDaFnoqu8CIH17J9lydZFMYjxRHtHmVPxnAxvqg&e=>) look like they include just a name of the image and expect that the image has already been uploaded to the correct OpenStack instance (and possibly VNF Manager in VFC and any other relevant components in the runtime) where they possibly can be instantiated. The same seems to apply to Heat templates in demo repo (e.g. https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/vFW/base_vfw.yaml;h=6137e8ab8ba74d9f7f245d95fd00faeca2fbde5a;hb=HEAD<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Ddemo.git-3Ba-3Dblob-3Bf-3Dheat_vFW_base-5Fvfw.yaml-3Bh-3D6137e8ab8ba74d9f7f245d95fd00faeca2fbde5a-3Bhb-3DHEAD&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=r9I4HaeTZWnzwEqiRY1_Hv-5a-5rlv9P2qxiDTBCt58&m=2Gbq2q6CDQnUqYvAou5z9fgUqKXpcKImg6w25a58SmE&s=J_NlGWiPepkbs8gaketYimlqJazRXOjGeaCguvBtc4Y&e=>). VNF Requirements project seems to agree in some relatively recent comments (https://wiki.onap.org/display/DW/VNF+Package+Requirement+Testability<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_VNF-2BPackage-2BRequirement-2BTestability&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=r9I4HaeTZWnzwEqiRY1_Hv-5a-5rlv9P2qxiDTBCt58&m=2Gbq2q6CDQnUqYvAou5z9fgUqKXpcKImg6w25a58SmE&s=TOhZliSFRduQrtCEVwd8APV_Mc501_sxEZvwP5kFq1Q&e=> R-26881: Note: Currently , ONAP doesn't have the capability of Image management, we upload the image into VIM/VNFM manually.) These guys seem to be concerned with ETSI NFV SOL004 which does include images in the VNF package and somehow ONAP seems to be striving for compatibility with that but here this seems to break. VNF Validation program seems to assume external management of images as well in their relatively recent plans: https://wiki.lfnetworking.org/display/LN/VNF+Validation+Minimum+Viable+Product<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.lfnetworking.org_display_LN_VNF-2BValidation-2BMinimum-2BViable-2BProduct&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=r9I4HaeTZWnzwEqiRY1_Hv-5a-5rlv9P2qxiDTBCt58&m=2Gbq2q6CDQnUqYvAou5z9fgUqKXpcKImg6w25a58SmE&s=i7-YkzmCARw6ODlGRqHIQsmz5JHQB8GhaBiYe3svhCc&e=> I’m quite sure I remember seeing some ONAP VNF CSARs with images included in Casablanca time, but maybe that was in some stuff inherited from Open-O that did support including images to VNF packages. There is also a very old project proposal for handling this (https://wiki.onap.org/display/DW/Image+Manager<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Image-2BManager&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=r9I4HaeTZWnzwEqiRY1_Hv-5a-5rlv9P2qxiDTBCt58&m=2Gbq2q6CDQnUqYvAou5z9fgUqKXpcKImg6w25a58SmE&s=LVoFbkuA22VO9eyz-hCAedtx86KKn3XnnvRkFLIyGNY&e=>) but as far as I can see this was rejected. The main question is that how is it supposed to go in El Alto? And in Frankfurt if that is different? Most sources seem to agree that the whole issue of managing images is left outside of ONAP. This is not very nice because then again a higher level system is needed to keep everything aligned. Or fall back to non-coordinated manual actions in various systems breaking things in random ways. -Timo [http://ext.w1.samsung.net/mail/ext/v1/external/status/update?userid=t.puha&do=bWFpbElEPTIwMTkwOTEwMDY1MTEzZXVjYXMxcDI0OWZlODRkOWNkYzQ4YzFiMzJjOWZlNjBhOWZjMDc2NCZyZWNpcGllbnRBZGRyZXNzPW9uYXAtc2RjQGxpc3RzLm9uYXAub3Jn] [cid:[email protected]] [http://ext.w1.samsung.net/mail/ext/v1/external/status/update?userid=t.puha&do=bWFpbElEPTIwMTkwOTEwMDcwOTM0ZXVjYXMxcDI5NjQ1OGJjNGI2MDQxMjA1ODljYTJmM2Y2NmQxMjYxMiZyZWNpcGllbnRBZGRyZXNzPW9uYXAtZGlzY3Vzc0BsaXN0cy5vbmFwLm9yZw__] -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18962): https://lists.onap.org/g/onap-discuss/message/18962 Mute This Topic: https://lists.onap.org/mt/34089509/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
