Netos Open Sourcing Strategy

October 10, 2024

Introduction

Early on in the development of Netos we found that deploying NetBox, Airflow, and Elastic instances for development was very time consuming. We needed each development environment to be consistent, and having one person almost full time building complex platforms, simply didn’t work.

Initially to support our internal development we built different layers of automation using Ansible and GitLab CI/CD. It became apparent that the tooling and infrastructure-as-code would be beneficial to the Netos product offerings.

We then deployed Ansible Semaphore UI to centrally manage all of our systems and development environment. We can provision all of this in a few steps (which previously took days per-pod):

Why Open Source

Our goal is to de-couple any non-core parts of our business. For example, in Phase 1, deploying and managing NetBox is not a core part of our business, however providing a stable and easy to deploy and manage instance of NetBox is critical to our success.

Netos are advocates of NetBox and we hope that by releasing a framework deploying, managing, and testing on NetBox we can increase adoption, and support others developing plugins.

More Than Code

The Ansible Semaphore UI deployment and associated projects are the first stage of our open sourcing strategy. Our goal is to additionally support the platform engineering aspects, and over time add more value to the network community.

Find Out More

Check our Support Portal for more information.

 

Table of Contents

Open Source

Netos Open Sourcing Strategy

We’re pleased to announce that we’ve open sourced Netos NetOps. Our first solution allows you to manage NetBox from within Ansible Semaphore.