Boost Nokia SR OS Classic Mode With Containerlab

Hey guys! Ever wrestled with getting Nokia SR OS (SROS) nodes in classic mode running smoothly within Containerlab? If so, you're not alone. There have been some real head-scratchers, but the good news is, we're diving deep into improvements to make this process a whole lot easier. This article is all about how we can enhance the support for nokia_srsim nodes when they're operating in classic mode. We'll explore the current pain points, the proposed solutions, and the nitty-gritty implementation details. Get ready to level up your SROS classic mode game!

The Challenges with Nokia SR OS Classic Mode in Containerlab

Let's be real, working with nokia_srsim nodes in classic mode hasn't always been a walk in the park. There are a couple of key hurdles that have made life a bit more complicated. First up, when you're trying to get things rolling with a partial startup configuration, you can't just flip the switch to classic mode. You're stuck with md mode or have to go to mixed mode. This is a bummer because it means you're often forced to provide a complete configuration right from the get-go. This can lead to issues, especially when you're using the same config or pipeline across different SROS releases. Nobody wants to be constantly tweaking their configurations just to keep things running, right?

Secondly, the integration with Ansible inventory is a bit rigid. It's statically mapped, which means that for SROS nodes, it always assumes the model mode, even if the node is actually running in mixed or classic mode. This can cause discrepancies and headaches when you're trying to manage your network with Ansible. It's like trying to fit a square peg in a round hole – it just doesn't work! These limitations can be frustrating and can hinder your ability to efficiently manage and test your SROS environments.

Now, I know what you might be thinking: "Why bother with classic mode anyway?" Well, while the model mode is the recommended path for new integrations, there are still plenty of scenarios where classic mode is the way to go. These include validating the SROS Ansible collection, developing and testing traditional EMS/NMS, and setting up Digital Twin scenarios. So, supporting classic mode effectively is still crucial.

We need to make it easier to work with SROS in classic mode within Containerlab. This means addressing these issues and providing a smoother, more flexible experience for everyone involved.

To summarize, the core problems revolve around the inflexibility in configuring classic mode and the static Ansible inventory mapping. Addressing these is crucial for seamless integration and management. So, let's look at how we're planning to tackle these issues.

Proposed Solution: Enhancing Classic Mode Support

Alright, let's talk solutions. We're not just complaining about the problems; we're actively working on making things better! Here's the plan to improve the support for nokia_srsim nodes running in classic mode:

• Classic Mode Activation: We're going to create a new, nokia_srsim-specific option. This will allow you to enable classic mode after the node has successfully started. This means more flexibility and control over your configurations. No more wrestling with full configs right from the start!
• Dynamic Ansible Inventory: We're making sure that the Ansible inventory is populated in accordance with the mode the SROS node is actually running in. This means no more assumptions about the model mode when a node is operating in mixed or classic mode. Your Ansible playbooks will be able to accurately reflect the state of your network.

We're keeping things focused on these core improvements for now. We're not aiming for any advanced features like configuration saves right away. The main goal is to get the basics right and make classic mode integration a seamless experience. We believe that by addressing these two key points, we can significantly improve the usability and efficiency of working with nokia_srsim nodes in classic mode.

This approach strikes a balance between functionality and simplicity, ensuring that users can easily leverage classic mode without unnecessary complexity. By focusing on these core improvements, we aim to provide a more streamlined and reliable experience for everyone working with SROS in Containerlab. So, how are we going to make it happen? Let's dive into some implementation details!

Implementation Details: Making it Happen

Okay, let's get into the technical weeds a bit. Here's how we're planning to implement these improvements:

When running in classic mode, the configuration automatically added by Containerlab needs a little tweaking. Here's what we're considering:

• Adjusting Automatic Configuration: We will adjust the automatic configurations that Containerlab adds. This includes not enabling netconf and gRPC servers if they aren't needed, streamlining the startup process.
• SNMP Configuration: We might want to automatically add the snmp-community private (RWA) setting, which is used by NFMP. This will save you the trouble of manually configuring it every time.
• Snapshot/Rollback Configuration: We're also considering automatically configuring snapshot/rollback settings used for Ansible. This would be a huge time-saver when automating configuration changes.
• SNMP Persistency: We may consider enabling SNMP persistency by default, making sure that your SNMP settings are always up-to-date.

By tweaking these settings, we'll ensure that the classic mode nodes are set up correctly from the beginning, reducing manual configuration steps and improving overall ease of use. These changes are designed to streamline the setup process and provide a more intuitive experience for users. We are aiming for a solution that's both powerful and user-friendly, allowing you to focus on the core tasks without getting bogged down in configuration details.

These adjustments will collectively streamline the setup process, reduce the need for manual configuration, and create a smoother, more efficient experience for users. The ultimate goal is to make it as easy as possible to work with classic mode SROS nodes within Containerlab, allowing you to concentrate on your network tasks without getting bogged down in configuration details. So, the idea is to provide a comprehensive, ready-to-use environment for classic mode SROS nodes.

Impact and Benefits

The improvements outlined above will have a tangible impact on anyone working with Nokia SR OS in classic mode within Containerlab. First, you'll experience a simplified configuration process. The new option to enable classic mode after startup gives you more flexibility and control. The dynamic Ansible inventory mapping ensures your automation scripts accurately reflect your network's status. All of this translates to reduced troubleshooting time and fewer manual configuration errors. Second, you can expect improved efficiency. Automatic configuration adjustments and streamlined setups will speed up deployment and reduce the time it takes to get your SROS nodes up and running. This means more time for testing, development, and other critical tasks. Finally, the ability to validate your SROS Ansible collection and work on Digital Twin scenarios becomes easier and more reliable. This leads to increased confidence in your network configurations and a more robust overall network management strategy.

In short, these improvements will enable you to work more efficiently, reduce errors, and focus on the important stuff: building and maintaining a reliable network. You'll have more time to innovate and less time fighting with configurations!

Conclusion

Alright, folks, that's the lowdown on the improvements coming to Nokia SR OS classic mode support in Containerlab. We're working hard to make it easier than ever to work with nokia_srsim nodes in classic mode. The new options, dynamic Ansible inventory, and configuration adjustments will make your life a whole lot easier. Stay tuned for updates and be sure to try out the new features when they're released. We're excited to see what you guys build!