[dev][tacker] Steps to setup tacker for testing VNF packages

Uikey, Nitin Nitin.Uikey at nttdata.com
Thu Sep 5 06:05:50 UTC 2019


Hi All,

Small correction.
Added `default_backend = file` because `default_store` option is deprecated.

>c) Path to store CSAR file at glance store
        >default configuration in /devstack/lib/tacker

        >filesystem_store_datadir = /var/lib/tacker/csar_files
         default_backend = file
        >filesystem_store_datadir should have Read and Write access (+rw)

Regards,
Nitin Uikey










From: Uikey, Nitin <Nitin.Uikey at nttdata.com>

Sent: Thursday, September 5, 2019 11:54 AM

To: openstack-discuss at lists.openstack.org <openstack-discuss at lists.openstack.org>

Subject: [dev][tacker] Steps to setup tacker for testing VNF packages




Hi All,



Please find below the steps to set-up tacker for managing vnf packages.



Steps to set-up tacker for managing vnf packages:-



1. Api-paste.ini



        [composite:tacker]

        /vnfpkgm/v1: vnfpkgmapi_v1



        [composite:vnfpkgmapi_v1]

        use = call:tacker.auth:pipeline_factory

        noauth = request_id catch_errors extensions vnfpkgmapp_v1

        keystone = request_id catch_errors authtoken keystonecontext extensions vnfpkgmapp_v1



        [app:vnfpkgmapp_v1]

        paste.app_factory = tacker.api.vnfpkgm.v1.router:VnfpkgmAPIRouter.factory



You can also copy api-paste.ini available in patch :
https://review.opendev.org/#/c/675593



2. Configuration options changes : tacker.conf



a) Periodic task to delete the vnf package artifacts from nodes and glance store.

        default configuration in tacker/tacker/conf/conductor.py



        vnf_package_delete_interval = 1800



b) Path to store extracted CSAR file on compute node

        default configuration in tacker/conf/vnf_package.py



        vnf_package_csar_path = /var/lib/tacker/vnfpackages/



        vnf_package_csar_path should have Read and Write access (+rw)





c) Path to store CSAR file at glance store

        default configuration in /devstack/lib/tacker



        filesystem_store_datadir = /var/lib/tacker/csar_files



        filesystem_store_datadir should have Read and Write access (+rw)



3. Apply python-tackerclient patches

        https://review.opendev.org/#/c/679956/

        https://review.opendev.org/#/c/679957/

        https://review.opendev.org/#/c/679958/



4. Apply tosca parser changes

        https://review.opendev.org/#/c/675561/



5. Sample CSAR file to create VNF package tacker/tacker/samples/vnf_packages/sample_vnf_pkg.zip



6. Commands to manage VNF packages



        To create a VNF package



                - openstack vnfpack create —user-data key=value



                <package_UUID> will be generated by this command which will be used in other commands to manage VNF Package.



        To upload the CSAR file



                1. using direct path



                        - openstack vnfpack upload <package_UUID>  --upload-method direct-file --path <path of CSAR file>



                2. using web



                        - openstack vnfpack upload <package_UUID> --upload-method web-download  --path <web URL>



        To list all the VNF Package



                        - openstack vnfpack list



        To show a VNF package details



                        - openstack vnfpack show <package_UUID>



        To delete a VNF package



                        - openstack vnfpack delete <package_UUID>



        use `openstack vnfpack --help` command for more information



Regards,

Nitin Uikey

Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying
 promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.



Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.



More information about the openstack-discuss mailing list