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 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://wiki.onap.org/display/DW/vCPE+with+Tosca+VNF+Test+Guide, direct link
to example TOSCA:
<https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=tosca/vCPE/vgw/MainSer
viceTemplate.yaml;h=5a8611a056462cfe4f42da8a942e19eab83b33fd;hb=HEAD>
https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=tosca/vCPE/vgw/MainServ
iceTemplate.yaml;h=5a8611a056462cfe4f42da8a942e19eab83b33fd;hb=HEAD) 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). 

 

VNF Requirements project seems to agree in some relatively recent comments (
<https://wiki.onap.org/display/DW/VNF+Package+Requirement+Testability>
https://wiki.onap.org/display/DW/VNF+Package+Requirement+Testability
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+Prod
uct>
https://wiki.lfnetworking.org/display/LN/VNF+Validation+Minimum+Viable+Produ
ct

 

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://wiki.onap.org/display/DW/Image+Manager) 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


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#18872): https://lists.onap.org/g/onap-discuss/message/18872
Mute This Topic: https://lists.onap.org/mt/34089398/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to