Skip to main content
Welcome! Our community is open, inclusive, growing and evolving. Come on in and have a look at our open-source code and other resources. Events are a great place to see the community and other explorers like you. In the meantime, ask a question, make a suggestion, or offer your own contributions.

New Name, Same Faces

You might remember us as OpenContrail. In preparation to join the Linux Foundation, we renamed our community in early 2018. Please be patient as we move over code, docs, resources and engagement from OpenContrail forums to Tungsten Fabric forums. Our groups of leaders haven’t changed, but we’re adding a community Ambassador program of helpful folks across the globe that can lead talks such as Meetups.

Our Mission

Build the world’s most ubiquitous, easy-to-use, scalable, secure, and cloud-grade SDN stack, providing a network fabric connecting all environments, all clouds, all people.

Flip through our project overview for the details.


Find Us on Github

Mailing Lists

Follow Us on Twitter

Follow Us on LinkedIn

Community Calendar

Whether it’s conferences, Meetups, online calls or otherwise, if you’re looking to find or add events, look no further than our community calendar.

Community Leadership Groups

Technical Steering Committee

  • Szymon Krasuski – CodiLime
  • Sukhdev Kapur – Juniper
  • Marek Chwal – CodiLime
  • Nick Davey – Juniper
  • Szymon Golebiewski – CodiLime (TSC Chair)
  • Ian Rae – CloudOps

Release Manager

  • Marek Chwal- CodiLime

Marketing Liaison

  • Adam Grochowski – Juniper


Find or join a group of people in the community helping to make Tungsten Fabric local to you. Ambassadors can speak at local events like Meetups, tour some project technology, and help locally.

  • To volunteer an Ambassador, we politely ask that you have given at least one talk on the project and are familiar with the TF Overview deck. To get listed on the map, reach out to someone on the Marketing Working Group.

Becoming a Contributor

Whether you want to fix a typo in comments or introduce a brand new feature, there are a few steps which make the process smoother:

  • Create a Linux Foundation ID, if you don’t have one yet. You’ll need this to subscribe to the mailing lists and to access the bugs and blueprints.
  • Subscribe to the mailing list. If you wish, there are also several other mailing lists you can join as well.
  • The wiki currently contains legal and technical docs, event decks and similar resources to boost your understanding of Tungsten Fabric. This material will eventually be moving to the wiki or Git repositories.
  • Join Slack. Post your questions to relevant channels, don’t abuse @here, get help and help others. The mailing list works best for long-running discussions; Slack is great for ad-hoc conversations.
  • Before you push anything, you’ll need to sign a Contributor License Agreement or CLA: either Individual CLA (ICLA) if you are an independent contributor, or Corporate CLA (CCLA). We suggest you sign a CCLA if you are employed at a company which pays you for your Tungsten Fabric-related work. CCLA also simplifies things if your teammates plan to contribute as well. Both ICLA and CCLA are legal documents. Please read them carefully. It’s usually smart to run the document past your company’s legal department before signing and submitting it, if only to verify that your contribution will be within your company’s policy. You can find all ICLA/CCLA documents in the Tungsten Fabric CLA Wiki.
  • If you’ve found a bug, file a bug report against the respective release in Jira. Be sure to describe both expected and actual behavior. You’ll need the bug ID later, so please do this even if you feel the change is trivial.
  • If you plan to develop a new feature, you must create or provide three things:
    • A blueprint. A blueprint is a short piece of text describing which feature do you propose, why it is good to have it in Tungsten Fabric, and who will be developing it. Blueprints are very important as they are used to plan future releases of Tungsten Fabric.
    • A detailed technical spec. Each blueprint should link to a more detailed technical specification document. These specifications must be submitted to the contrail-specs GitHub repository. They are not stored or tracked in Jira.
    • A Jira bug ticket. While the blueprint briefly describes the work that will be done, the ticket is where the work actually happens (commits get linked to the ticket).
    • Here is an example of a complete Jira blueprint.
  • Although contrail-specs and other Tungsten Fabric repositories are hosted on GitHub, they are managed with Gerrit. Please don’t send Pull Requests to the GitHub repositories, and go to instead. Blueprint specs are submitted this way as well.
  • Note that Tungsten Fabric is currently migrating from Juniper owned to [] email for the latest information.
  • After getting Gerrit access as described below, clone the specs repository with the command: git clone and install the git-review extension which will allow you to submit specs as well as code changes. In order to write a spec, start by copying the template to a meaningful name in the appropriate subdirectory for the release that you would like to target.

With all of these in place, you are now ready to submit your specs and code to Tungsten Fabric! How to write these specs and code is a different story though, but we hope the links in the next section will help you to get started. You may also want to consult a more detailed how-to available here, in the contrail-community-docs repo. And of course, feel free to ask questions on the mailing list and in Slack channels!

Start Developing Tungsten Fabric

Build Tungsten Fabric

Debug Tungsten Fabric