OpenSDN Roadmap- 2025

[prithvi1307]

OpenSDN Minimal Resource Roadmap (2025)

Executive Summary

This roadmap leverages parallel work streams and community volunteers to maximize output with minimal core developer resources. The first release focuses on stabilization and documentation, while the second release delivers two major features: Floating IP/Load Balancing enhancements and a complete monitoring transformation to OpenTelemetry.

---

Resource Model & Work Streams

Core Development Team (Minimal)

• Stream 1: Python 3 migration & dependency updates (Progmatic Labs Team?)
• Stream 2: OpenTelemetry transformation (1 senior dev, can start immediately - who?)
• Stream 3: Floating IP/LB features (1-2 devs, starts after planning)

Community Resources (Required)

• Documentation Team: 2-3 interns or volunteers
• Video Content Creators: 1-2 community members
• Testing Team: 3-5 community volunteers (Progmatic?)
• Code Review: 2-3 experienced community members

---

First Release: Stabilization & Foundation (June-August 2025)

Timeline: 2-3 months | Focus: Technical debt & documentation

Development Track (Core Team)

Stream 1: Dependency Updates & Security (June-July)

Owner: Progmatic?

Week 1-2: Assessment & Planning

• Python 2 dependency audit
• Security vulnerability scan
• Cassandra upgrade impact analysis

Week 3-6: Python 3 Migration

• Automated conversion (2to3 tool?)
• Manual fixes for complex cases
• Update all scripts and utilities
• CI/CD pipeline updates

Week 7-8: Dependency Updates

• Cassandra to current version
• OpenStack library updates
• Security patches (CVE fixes)
• Build dependency modernization

Stream 2: OpenTelemetry Planning (June - Parallel)

Owner: 1 Senior Developer (Different person)

Week 1-4: Architecture Design

• Current telemetry framework analysis
• OpenTelemetry integration design
• Migration strategy document
• Performance impact assessment
• Define metrics to preserve
• API compatibility planning

Documentation Track (Community/Interns)

Documentation Team Requirements

Need: 2-3 dedicated interns or volunteers

Responsibilities:

1. Essential Guides

   • Quick Start Guide (single-node setup)
   • Comprehensive Installation Guide
   • Troubleshooting Guide
   • Migration Guide (Python 2→3, version upgrades)
   • Configuration Reference

2. Architecture Documentation

   • System architecture overview
   • Component interaction diagrams
   • Data flow documentation
   • Network topology examples

3. Developer Documentation

   • Code structure guide
   • API documentation
   • Contributing guidelines
   • Testing procedures

Video Content Team Requirements

Need: 1-2 community volunteers with screen recording experience

Deliverables:

• Getting Started (5 minutes)
• Installation Walkthrough (10 minutes)
• Basic Configuration (10 minutes)
• Troubleshooting Common Issues (15 minutes)
• Architecture Overview (20 minutes)

Community Mobilization Plan

Recruitment Strategy (May 2025)

1. University outreach: Internship opportunities (NIPA & Dr Abhisak?)
2. Social media campaign: LinkedIn, Twitter (Prithvi)
3. Direct asks: Telegram, Slack/Discord community (Prithvi)
4. Incentives: Recognition, swag, recommendation letters (?)
5. Bug/Enhancement Bounty: Is this possible? (Randy)

Volunteer Coordination

• Weekly sync meetings
• Shared documentation workspace
• Review and feedback process
• Public recognition program

Stability & Quick Wins (July-August)

Critical Fixes Only

• vRouter crash patches
• Flow zombie cleanup
• Memory leak fixes
• Connection stability

Prometheus Basic Integration

• Export existing metrics
• Configuration templates
• Grafana dashboard examples
• No code changes required

---

Second Release: Major Features (September-November 2025)

Timeline: 3 months | Two parallel feature developments

Feature 1: OpenTelemetry Transformation

Owner: Same developer from Stream 2
Start: Immediately after design phase (July)

Phase 1: Core Implementation (July-August)

• OpenTelemetry SDK integration
• Metrics collector implementation
• Trace collection framework
• Log aggregation setup

Phase 2: Migration Tools (September)

• Analytics to OpenTelemetry migrator
• Historical data converter
• Configuration migration scripts
• Backwards compatibility layer

Phase 3: Deprecation (October-November)

• Remove old telemetry code
• Update all components
• Performance optimization
• Final testing

Deliverables

• Complete OpenTelemetry implementation
• Migration tools and scripts
• Operations guide
• Performance benchmarks
• Grafana dashboards
• Jaeger integration for tracing

Feature 2: Floating IP & Load Balancing

Owner: 1-2 developers
Start: After planning complete (August)

Planning Phase (Late July)

• Feature specification
• API design
• WebUI mockups
• Test plan creation

Implementation (August-October)

1. Floating IP for Octavia VIP

   • Core implementation
   • API endpoints
   • WebUI integration
   • Testing

2. Active-Active LB with ECMP

   • ECMP algorithm implementation
   • Octavia integration
   • Performance optimization
   • Load testing

3. EVPN VxLAN Floating IP

   • Protocol implementation
   • Configuration framework
   • WebUI support
   • Migration tools

Final Phase (November)

• Integration testing
• Documentation
• Performance validation
• Bug fixes

---

Timeline Overview

May 2025 - Pre-work

• Recruit documentation volunteers
• Set up community infrastructure
• Begin OpenTelemetry research

June 2025

• Week 1-2: Python 3 migration starts, OpenTelemetry design
• Week 3-4: Documentation sprint begins, security audit

July 2025

• Week 1-2: Python 3 migration continues, OpenTelemetry development starts
• Week 3-4: Dependency updates, Floating IP planning begins

August 2025

• Week 1-2: Stability fixes, Floating IP development starts
• Week 3-4: First release testing and preparation
• End of August: First Release

September-November 2025

• Parallel development of both features
• Monthly beta releases
• Community testing
• Late November: Second Release

---

Success Metrics

First Release

• Python 3 migration 100% complete
• Zero high/critical security vulnerabilities
• 10+ documentation guides published
• 5+ video tutorials created
• 20+ community contributors engaged

Second Release

• OpenTelemetry fully replacing old analytics
• 3 Floating IP features implemented
• <5% performance impact from monitoring
• 95% test coverage on new features
• Adoption by 40% of users within 3 months

---

Community Volunteer Requirements

Critical Needs

1. Documentation Lead (1 person)

   • Coordinate interns/volunteers
   • Review all documentation
   • Maintain consistency

2. Technical Writers (2-3 people)

   • Create user guides
   • Document APIs
   • Write tutorials

3. Video Creators (1-2 people)

   • Screen recording skills
   • Basic video editing
   • Clear communication

4. Testers (5+ people)

   • Beta testing
   • Bug reproduction
   • Performance testing

Recognition Program

• Contributors page
• LinkedIn recommendations
• Conference talk opportunities
• Project swag
• Potential job referrals

---

Risk Management

Resource Risks

• Volunteer shortage: Partner with universities, bootcamps
• Developer availability: Clear separation of work streams
• Quality control: Establish review processes early

Technical Risks

• OpenTelemetry complexity: Start early with design phase
• Python 3 breaking changes: Comprehensive testing plan
• Feature integration: Feature flags for gradual rollout

---

Call to Action

For the Community

• Documentation volunteers needed NOW
• Internship opportunities available
• Testing help critical for success

For Organizations Using OpenSDN

• Sponsor developer time
• Provide testing resources
• Share use cases and requirements

[mjvi-odoo]

💬 Count me in! This roadmap is 🔥 — I’d love to help out with documentation or testing (whichever is more urgent). The Python 3 migration and OpenTelemetry transformation sound especially exciting. Looking forward to contributing and learning with the community. 🙌

Anyone else thinking about joining — now’s the time. Let's make OpenSDN awesome together! 💪

[aignatov]

Not clear which release will contain full removal of Centos7 dependencies?