Hi All ,
Thank all for you reviewing tacker patches [1]. Dharmendra: Big thank you for co-ordinating with tosca-parser team to merge critical patches without which we wouldn't have hope to merge this feature in Train cycle.
We have fixed all review comments and uploaded new patch sets. Request you to please take a look at it.
Also, we have reported a LP bug in python-tackerclient [2] and also fixed it in patch [3].
[1] : https://review.opendev.org/#/q/status:open+project:openstack/tacker+branch:m... [2] https://bugs.launchpad.net/python-tackerclient/+bug/1844625 [3] : https://review.opendev.org/#/c/683203
Regards, Tushar Patil
________________________________________ From: Dharmendra Kushwaha dharmendra.kushwaha@india.nec.com Sent: Friday, September 13, 2019 7:10 PM To: Patil, Tushar; openstack-discuss@lists.openstack.org Subject: Re: [tacker] Feature Freeze Exception Request - Add VNF packages support
Hi Tushar,
Thanks for your hard effort.
I had released tosce-parser1.6.0 as in [1], and lets wait [2] to get merged. Regarding tackerclient code, we already have merged it, and will release tackerclient today.
Tacker have cycle-with-rc release model, So ok, we can wait some time for this feature(server patches). We just needs to make sure that no broken code goes in the last movement and can be tested before rc release.
[1]: https://review.opendev.org/#/c/681240 [2]: https://review.opendev.org/#/c/681819
Thanks & Regards Dharmendra Kushwaha
________________________________________ From: Patil, Tushar Tushar.Patil@nttdata.com Sent: Friday, September 13, 2019 2:24 PM To: openstack-discuss@lists.openstack.org Subject: [tacker] Feature Freeze Exception Request - Add VNF packages support
Hi Dharmendra and all Core reviewers
In train cycle ,we are committed to implement spec “VNF packages support for VNF onboarding” [1].
All patches [2] are uploaded on the gerrit and code review is in progress but as we have dependency on tosca-parser library, patches are not yet merged. Now, tosca-parser library new version 1.6.0. is released but we are waiting for patch [3] to merge which will update the constraints of tosca-parser to 1.6.0 in requirements project. Once that happens, we will make changes to the tacker patch [4] to update the lower constraints of tosca-parser to 1.6.0 which will run all functional and unit tests added for this feature successfully on the CI job.
I would like to request feature freeze exception for “VNF packages support for VNF onboarding” [1]. We will make sure all the review comments on the patches will be fixed promptly so that we can merge them as soon as possible.
[1] : https://review.opendev.org/#/c/582930/ [2] : https://review.opendev.org/#/q/topic:bp/tosca-csar-mgmt-driver+(status:open+...) [3] : https://review.opendev.org/#/c/681819/ [4]: https://review.opendev.org/#/c/675600/
Thanks, tpatil 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.
________________________________ 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. 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.