Merge branch 'PalisadoesFoundation:main' into feature/Typescript-Type-Checking/Eslint-linting

Author: 18bharathkumar

docs/internships/reports/gsoc/2025-abhi.md

@@ -1,18 +1,18 @@
 ---
 id: 2025-abhishek
 title: GSoC 2025 - Abhishek Raj
-sidebar_position: 7
+sidebar_position: 202507
 ---
 
-
 **Project:** Enhanced SwitchMap-NG Scalability
 **Contributor:** [Abhishek Raj](https://github.com/abbi4code)
 **Mentors:** [Aashima Wadhwa](https://github.com/aashimawadhwa), [Dominic Mills](https://github.com/DMills27)
 **Organization:** [The Palisadoes Foundation](https://github.com/PalisadoesFoundation/)
 **Duration:** June–October 2025
 
 ### About me
-I’m **Abhishek Raj**, a **final-year student at NIT Durgapur** with a strong interest in backend engineering and distributed systems. 
+
+I’m **Abhishek Raj**, a **final-year student at NIT Durgapur** with a strong interest in backend engineering and distributed systems.
 I started my open-source journey with the Palisadoes Foundation in December 2024, where I made my first contributions and grew into the workflow.
 
 ### Project Goals
@@ -29,23 +29,27 @@ When I began this project, Switchmap-NG faced several critical challenges:
 
 My GSoC project focused on modernizing Switchmap-NG through four key initiatives:
 
-**1. Legacy Synchronous Architecture**: 
-- Current SNMP polling system relied on the deprecated EasySNMP library and synchronous operations, causing performance bottlenecks. 
-- Replacing `EasySNMP` with  `PySNMP`'s async API for non-blocking operations, enabling efficient polling of thousands of devices. 
+**1. Legacy Synchronous Architecture**:
+
+- Current SNMP polling system relied on the deprecated EasySNMP library and synchronous operations, causing performance bottlenecks.
+- Replacing `EasySNMP` with `PySNMP`'s async API for non-blocking operations, enabling efficient polling of thousands of devices.
+
+**2. Removed resource intensive multiprocessing**:
 
-**2. Removed resource intensive multiprocessing**: 
 - Replaced the legacy **CPU-bound** multiprocessing design with a fully asynchronous polling architecture using Python’s asyncio.
 - Implemented semaphore-based device polling control
 - Removed legacy code and consolidated async implementations
 
 **3. Feature Enhancements**
+
 - Added **multi-vendor** system monitoring (CPU/memory for Cisco and Juniper)
 - Extended **interface statistics** with comprehensive packet/byte counters
 - Implemented GraphQL hostname-based device lookup
 
 **4. Developer Experience**
+
 - Created **automated setup scripts** for complete deployment
-- Written and expanded test coverage  with  async tests from 50% to 85%.
+- Written and expanded test coverage with async tests from 50% to 85%.
 - **Improved documentation** and contributor onboarding
 
 ### Completed Work
@@ -54,7 +58,7 @@ My GSoC project focused on modernizing Switchmap-NG through four key initiatives
 
 - Complete migration of SNMP polling infrastructure from synchronous EasySNMP to **asynchronous PySnmp**. This foundational change enabled all subsequent **performance improvements**.
 - MIB queries and collectors converted to async with controlled concurrency, lazy data loading, safer merging, improved error/log handling, and **better** SNMPv1/v2/v3 timeout/fallback behavior.
--  **Resolved** polling freeze when encountering invalid OID prefixes during SNMP walks and fixed leading dot OID parsing.
+- **Resolved** polling freeze when encountering invalid OID prefixes during SNMP walks and fixed leading dot OID parsing.
 
 2. [[GSoC]: Replace bottleneck multiprocessing with async for device polling & fix failing tests in CI ](https://github.com/PalisadoesFoundation/switchmap-ng/pull/334)
 
@@ -77,42 +81,46 @@ My GSoC project focused on modernizing Switchmap-NG through four key initiatives
 - Reworked insert_row/update_row to build insert/update dicts incrementally and encode oui/organization bytes only when non-null.
 - Added resolve_device_by_hostname(obj, info, hostname=None) (returns None for falsy hostnames, UTF‑8 encodes hostname, queries Device where enabled==1 ordered by ts_created desc). Exposed deviceByHostname(hostname: String) on Query and wired the resolver.
 - Added L1Interface fields: ifin_octets, ifout_octets, ifin_nucast_pkts, ifout_nucast_pkts, ifout_errors, ifout_discards. Updated RL1Interface row mapping to include new fields.
-- Populates new L1 interface fields  when constructing IL1Interface rows during device ingest/update.
+- Populates new L1 interface fields when constructing IL1Interface rows during device ingest/update.
 - Updated fixtures, seeded data, and expectations to include new per-interface fields. Adjusted IL1Interface constructions and L1Interface tuple size expectations.
 
 5. [[GSoC]: Increased SNMP poller test coverage with comprehensive async tests ](https://github.com/PalisadoesFoundation/switchmap-ng/pull/350)
 
 - **Increased test coverage** across multiple SNMP modules
-- Restrict _oid_valid_format to reject OIDs where any octet (after the initial empty segment) has leading or trailing whitespace (function returns False for such octets), preserving integer parsing otherwise.
+- Restrict \_oid_valid_format to reject OIDs where any octet (after the initial empty segment) has leading or trailing whitespace (function returns False for such octets), preserving integer parsing otherwise.
 
 6. [[GSoC]: add automated setup script for complete Switchmap deployment](https://github.com/PalisadoesFoundation/switchmap-ng/pull/360)
 
 - Added a complete set of **management scripts** (setup.sh, start.sh, stop.sh, restart.sh, status.sh, logs.sh, cleanup.sh) that automate the entire Switchmap-NG lifecycle from initial setup to daily operations.
-- **One-Command Setup** Implemented with setup.sh with Docker MySQL as well (*opt local mysql usage also supports) support that handles the entire installation process - from prerequisite checks to database initialization, dependency installation, and service startup - reducing setup time from manual hours to a single command.
--  Added service Lifecycle Scripts and New lifecycle scripts to start/stop/restart services and frontend, manage PIDs, validate health and ports, check MySQL accessibility, and display colored status summaries and quick commands. Logs & Cleanup scripts/logs.sh, scripts/cleanup.sh logs.sh tails service-specific or aggregated logs; cleanup.sh provides interactive, flag-driven cleanup for var, venv, etc/config.yaml, frontend node_modules, and Docker containers/volumes with confirmation prompts and status messages.
--  Converted many SNMP tests modules to async (IsolatedAsyncioTestCase) expanded mocks and assertions to exercise SNMP GET/swalk/walk, VLAN/MAC/context handling, error/edge cases, and added Juniper process tests.
+- **One-Command Setup** Implemented with setup.sh with Docker MySQL as well (\*opt local mysql usage also supports) support that handles the entire installation process - from prerequisite checks to database initialization, dependency installation, and service startup - reducing setup time from manual hours to a single command.
+- Added service Lifecycle Scripts and New lifecycle scripts to start/stop/restart services and frontend, manage PIDs, validate health and ports, check MySQL accessibility, and display colored status summaries and quick commands. Logs & Cleanup scripts/logs.sh, scripts/cleanup.sh logs.sh tails service-specific or aggregated logs; cleanup.sh provides interactive, flag-driven cleanup for var, venv, etc/config.yaml, frontend node_modules, and Docker containers/volumes with confirmation prompts and status messages.
+- Converted many SNMP tests modules to async (IsolatedAsyncioTestCase) expanded mocks and assertions to exercise SNMP GET/swalk/walk, VLAN/MAC/context handling, error/edge cases, and added Juniper process tests.
 
 ### Current State
 
 **Async SNMP Infrastructure**
+
 - Fully migrated to PySnmp with async/await
 - Concurrent device polling with configurable limits
 - Robust error handling and retry logic
 - Comprehensive logging and monitoring
 
 **Multi-Vendor Support**
+
 - Generic RFC-standard MIBs (IF, BRIDGE, LLDP, Q-BRIDGE, ENTITY, etc.)
 - Cisco-specific MIBs (CDP, VTP, STACK, PROCESS, etc.)
 - Juniper-specific MIBs (VLAN, PROCESS)
 - Extensible architecture for additional vendors
 
 **System Monitoring & Interface Statistics**
+
 - CPU utilization tracking (5-minute average)
 - Memory usage monitoring (used/free)
 - Comprehensive packet counters (unicast, non-unicast)
 - Byte counters (inbound, outbound) & Error and discard tracking
 
 **Developer Experience**
+
 - One-command automated setup
 - Comprehensive documentation
 - Service management scripts
@@ -128,28 +136,30 @@ My GSoC project focused on modernizing Switchmap-NG through four key initiatives
 - **API Response Time**: under 100ms for typical queries
 - **Setup Time**: 3-5 minutes (down from 2-3 hours)
 
-
 ### What Remains
 
 While the project has achieved its primary goals and delivered a production-ready async monitoring system, there are still exciting opportunities for future enhancements that will extend Switchmap-NG's capabilities:
 
 **Distributed Architecture with Store-and-Forward**:
+
 - The current architecture works well for centralized deployments, but could be enhanced for distributed scenarios where pollers may have intermittent connectivity to the central API server.
 - Test coverage has been significantly improved from around 50% to 85%. However, achieving full coverage remains challenging since some core SNMP polling components involve complex asynchronous flows and low-level network interactions. Ongoing work focuses on building reliable test harnesses and mocks for these components to reach the 100% goal.
 
 ### Challenges and Lessons Learned
 
 1. **Handling Real-World SNMP Data**
+
 - SNMP responses were often malformed or encoded inconsistently across libraries. For instance, whitespace within OIDs or double-encoded MAC addresses caused silent failures and data mismatches. These edge cases revealed the importance of strict input validation and careful data decoding when migrating from EasySNMP to PySNMP.
-**Lesson:** Never assume external data is clean. Validate everything at the boundaries, it’s far easier to fail early than debug downstream corruption.
+  **Lesson:** Never assume external data is clean. Validate everything at the boundaries, it’s far easier to fail early than debug downstream corruption.
 
 2. **From Multiprocessing to Async Concurrency**
-The legacy multiprocessing model didn’t translate directly to async patterns. Replacing process pools with semaphores and refactoring shared state into async-safe structures took significant design effort. Adopting async context managers and using aiohttp for non-blocking HTTP calls ultimately simplified resource management.
-**Lesson:** Asyncio and multiprocessing solve different problems understanding when and how to use each is crucial for scalability and stability.
+   The legacy multiprocessing model didn’t translate directly to async patterns. Replacing process pools with semaphores and refactoring shared state into async-safe structures took significant design effort. Adopting async context managers and using aiohttp for non-blocking HTTP calls ultimately simplified resource management.
+   **Lesson:** Asyncio and multiprocessing solve different problems understanding when and how to use each is crucial for scalability and stability.
 
 3. **Complexity of Async Testing**
+
 - Testing asynchronous code was far more challenging than expected. The initial test suite, built for synchronous behavior, didn’t work well with async patterns. I had to think in different way for mocking async methods, and design new test flows to validate concurrency and async-safe resource handling.
-**Lesson:** Async systems demand a new mindset for testing. Once the right patterns are in place, async tests can be just as reliable and even faster to execute.
+  **Lesson:** Async systems demand a new mindset for testing. Once the right patterns are in place, async tests can be just as reliable and even faster to execute.
 
 ### Conclusion
 
@@ -158,4 +168,4 @@ The legacy multiprocessing model didn’t translate directly to async patterns.
 ### Acknowledgements
 
 - I'm incredibly grateful to my mentors **Aashima Wadhwa**, **Dominic Mills**, and **Peter Harrison** for their guidance and support throughout this project. Their feedback and code reviews were invaluable in shaping my work and pushing me to grow as a developer.
-- A huge shoutout to my fellow mentee **Abhi** as well  for sharing ideas & feedback with each other and tackling challenges together made this journey so much more enjoyable and rewarding.
+- A huge shoutout to my fellow mentee **Abhi** as well for sharing ideas & feedback with each other and tackling challenges together made this journey so much more enjoyable and rewarding.