[kolla][tacker][glance] Deployment of Tacker Train (VNF CSAR packages issues)
dharmendra.kushwaha at india.nec.com
Fri Oct 11 07:31:12 UTC 2019
Sorry for inconvenience.
We added support for vnf package with limited scope  in train cycle, and have ongoing activity for U cycle, so we didn't published proper doc for this feature. But yes, we will add doc for current dependent changes. I have just pushed a manual installation doc changes in .
We needs vnf_package_csar_path(i.e. /var/lib/tacker/vnfpackages/) path to keep extracted data locally for further actions, and filesystem_store_datadir(i.e. /var/lib/tacker/csar_files) for glance store. In case of multi node deployment, we recommend to configure filesystem_store_datadir option on shared storage to make sure the availability from other nodes.
Thanks & Regards
From: Radosław Piliszek <radoslaw.piliszek at gmail.com>
Sent: Thursday, October 10, 2019 12:35 AM
Subject: [kolla][tacker][glance] Deployment of Tacker Train (VNF CSAR packages issues)
Some time ago I reported a bug in Kolla-Ansible Tacker deployment 
Eduardo (thanks!) did some debugging to discover that you started requiring internal Glance configuration for Tacker to make it use the local filesystem via the filestore backend (internally in Tacker, not via the deployed Glance) 
This makes us, Koalas, wonder how to approach a proper production deployment of Tacker.
Tacker docs have not been updated regarding this new feature and following them may result in broken Tacker deployment (as we have now).
We are especially interested in how to deal with multinode Tacker deployment. Do these new paths require any synchronization?
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
More information about the openstack-discuss