Open Stack

Hi Dharmendra,

thanks for the insights.
We will see what we can do.
In the worst case we will leave it to the operator to provide the shared
filesystem (by documenting the need).

Are you planning to move to using glance-api? It would solve the locality
problem.

Kind regards,
Radek

pt., 11 paź 2019 o 09:31 Dharmendra Kushwaha <
dharmendra.kushwaha at india.nec.com> napisał(a):

> Hi Radosław,
>
> Sorry for inconvenience.
> We added support for vnf package with limited scope [1] 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 [2].
> 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.
>
> [1]:
> https://github.com/openstack/tacker/blob/master/releasenotes/notes/bp-tosca-csar-mgmt-driver-6dbf9e847c8fe77a.yaml
> [2]: https://review.opendev.org/#/c/688045/
>
> Thanks & Regards
> Dharmendra Kushwaha
> ________________________________________
> From: Radosław Piliszek <radoslaw.piliszek at gmail.com>
> Sent: Thursday, October 10, 2019 12:35 AM
> To: openstack-discuss
> Subject: [kolla][tacker][glance] Deployment of Tacker Train (VNF CSAR
> packages issues)
>
> Hello Tackers!
>
> Some time ago I reported a bug in Kolla-Ansible Tacker deployment [1]
> 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) [2]
> 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?
>
> [1] https://bugs.launchpad.net/kolla-ansible/+bug/1845142
> [2]
> https://review.opendev.org/#/c/684275/2/ansible/roles/tacker/templates/tacker.conf.j2
>
> Kind regards,
> Radek
>
> ________________________________
>  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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20191012/b4160028/attachment-0001.html>