Hi Howard, please support this issue.
发件人: Thamanna Farhath [mailto:thamanna.f@zybisys.com] 发送时间: 2024年8月6日 13:39 收件人: Alex Song (宋文平) songwenping@inspur.com 抄送: katonalala@gmail.com; openstack-discuss@lists.openstack.org 主题: Issue with Backporting FWaaS V2 in Kolla Ansible - Missing Files
Hello,
Thankyou for your support
I am currently working on integrating FWaaS V2 into my OpenStack deployment using Kolla Ansible 2023.1. Following the guidelines provided, I attempted to backport the changes from the following reviews:
1. https://review.opendev.org/c/openstack/kolla-ansible/+/914854 2. https://review.opendev.org/c/openstack/kolla/+/914855/6
While I successfully made the necessary changes to each file in the first review, I encountered an issue with the second review. Specifically, the following files are missing from my environment:
* docker/horizon/extend_start.sh * kolla/common/sources.py
I am unsure why these files are missing and how I can resolve this issue to complete the backport process. Could you please provide guidance on how to address this problem? Any assistance or pointers would be greatly appreciated.
Thank you for your support.
---- On Tue, 30 Jul 2024 06:42:27 +0530 Alex Song (宋文平) <songwenping@inspur.com mailto:songwenping@inspur.com > wrote ---
Hi, the master branch has supported but not backport to 2023.1 https://review.opendev.org/c/openstack/kolla-ansible/+/914854 , you can backport on your own env.
发件人: Thamanna Farhath [mailto:thamanna.f@zybisys.com mailto:thamanna.f@zybisys.com ] 发送时间: 2024年7月28日 19:45 收件人: Lajos Katona <katonalala@gmail.com mailto:katonalala@gmail.com > 抄送: openstack-discuss <openstack-discuss@lists.openstack.org mailto:openstack-discuss@lists.openstack.org > 主题: Re: Firewall as a Service - kolla ansible 2023.1
Hi,
Thanks for your support , Is that possible without devstack environment.
---- On Tue, 09 Jul 2024 13:46:53 +0530 Lajos Katona <katonalala@gmail.com mailto:katonalala@gmail.com > wrote ---
Hi,
As I see the kolla-ansible support was never done for neutron-fwaas, so that is a feature request for kolla-ansible.
From a practical perspective I would check how we deploy fwaas in devstack, for that please check the devstack plugin in
neutron-fwaas repo:
https://opendev.org/openstack/neutron-fwaas/src/branch/master/devstack
These functions and config settings can be the base part for ansible also I believe.
Best wishes
Lajos Katona (lajoskatona)
Thamanna Farhath <thamanna.f@zybisys.com mailto:thamanna.f@zybisys.com > ezt írta (időpont: 2024. júl. 9., K, 8:01):
Hello OpenStack Community,
I hope this message finds you well. My name is Thamanna , and I am currently working with the OpenStack Kolla-Ansible deployment version 2023.1.
I am interested in deploying Firewall as a Service (FWaaS) within our OpenStack environment. However, I have noticed that FWaaS is not available in the Kolla-Ansible 2023.1 version.
Could anyone please provide guidance on the following points?
1. Is there an official or recommended way to integrate FWaaS with Kolla-Ansible 2023.1?
2. Are there any specific configurations or additional components required to enable FWaaS?
3. Has anyone in the community successfully deployed FWaaS with this version, and if so, could you share your experience and any potential challenges faced?
4. Are there alternative approaches or tools that you would recommend for deploying FWaaS in an OpenStack environment?
Any help or pointers to relevant documentation would be greatly appreciated.
Thank you in advance for your assistance!
Best regards,
Thamanna
thamanna.f@zybisys.com mailto:thamanna.f@zybisys.com
_____
Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender.
E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."
_____
Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender.
E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."
_____
Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender.
E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."