Hello Thamanna, No, Kolla-Ansible did never support Tungsten Fabric as part of a standard deployment. There was a Kolla-Ansible fork under the TF namespace long time ago - but it looks unmaintained for very long time: https://github.com/tungstenfabric/tf-kolla-ansible Michal
On 5 Aug 2025, at 14:55, Thamanna Farhath <thamanna.f@zybisys.com> wrote:
Hello OpenStack Community,
We are currently using OpenStack Kolla Ansible (2023.1 release). As part of our networking design, we are evaluating the possibility of integrating Tungsten Fabric (TF) with Neutron.
I would like to clarify the following points:
Compatibility – Does the Kolla Ansible 2023.1 version officially support integration with Tungsten Fabric?
Reference Material – If supported, could you please suggest any official documentation, blogs, or reference implementations that describe the integration process?
Integration Guidance – What would be the recommended approach for integrating TF with Neutron in a Kolla-based deployment? Are there any specific configuration patterns or community best practices we should follow?
Necessity – In the context of building a public cloud, is Tungsten Fabric integration considered mandatory for production-grade networking, or can similar functionality be achieved with the default Neutron backends (e.g., OVN/OVS)?
We are currently at the early stages of our deployment plan and can make architectural changes before the release. Any guidance, experiences, or resources from the community will be highly valuable for our decision-making process.
Thank you in advance for your support.
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."