Universal OLT Management API

@gotucat

Hi, I reviewed your Universal OLT Management API request: a lightweight, well-documented REST backend that standardizes OLT health, per-PON stats, and ONU status/config updates across Huawei, ZTE, and BDCOM. I’ll build a clean JSON REST API with endpoints /olts, /pons, and /onus, using modular API Development drivers per vendor while keeping a consistent schema. I’ll implement the PUT/PATCH flow for updating the ONU description field and V-Lan, and I’ll provide practical cURL examples plus a README with environment variables and how to connect to each device. I’ll keep the code structured for future vendors, with reliable Git-based delivery and straightforward testing. Let’s discuss here now.

@juanestebana17

Hello! I read your project and understand that you need a lightweight REST API that unifies Huawei MA series, ZTE C3xx, and BDCOM OLT management for OLT health, PON stats, ONU status, and ONU description/V-Lan updates. I’ve spent the last several years solving exactly this type of problem in API Development and Software Development, building modular JSON services and integrating device automation through CLI, SNMP, and NETCONF. I’m comfortable structuring clean endpoints like /olts, /pons, and /onus, and documenting everything with cURL examples so the service is easy to reproduce and extend with new vendors later. I’m ready to get started, and I’m confident we can make this project a success and deliver it to a high standard. I’m committed to ensuring everything is completed professionally, efficiently, and exactly according to your requirements. Best regards!

@denisSolution

Hello, I'm Denis, a backend developer who has built similar integration systems for network devices. You need a unified REST API to manage mixed-brand OLTs without touching the frontend. The main technical challenge is normalizing different vendor interfaces—Huawei MA series, ZTE C3xx, and BDCOM E-PON/G-PON—into a single JSON layer. I’d approach this by mapping each vendor’s CLI, SNMP, or NETCONF commands to a clean internal abstraction, then exposing three REST endpoints: /olts for device health, /pons for PON statistics, and /onus for ONU status and configuration updates. The code will be modular so adding new brands later is just swapping drivers. For vendor-specific work, I’ve used SNMP polling for Huawei and ZTE to pull health metrics, while BDCOM devices respond better to CLI over SSH with structured output parsing. ONU description and VLAN updates will use PUT/PATCH calls translated into the correct vendor commands behind the scenes. The README will include environment variables for credentials, a driver mapping table, and curl examples. The biggest risk is vendor API inconsistencies, especially error responses or missing fields. I’d handle this with per-vendor retry logic for transient failures and logging full command outputs during development to catch edge cases early. I can start right away. Let's connect and discuss the details. Thanks, Denis

@ahmadayaz

I propose an architecture leveraging microservices to create a unified backend service for Huawei, ZTE, and BDCOM OLTs via a JSON REST API. This solution, tailored for each vendor, will provide OLT health monitoring, PON statistics retrieval, and ONU management. By utilizing CLI, SNMP, and NETCONF, I ensure reliable data retrieval and configuration updates with robust error handling. The RESTful design pattern will guarantee a well-documented solution, including endpoints for status retrieval and configuration modifications. The system will integrate seamlessly with Huawei MA series, ZTE C3xx, and BDCOM OLTs, with comprehensive README documentation for easy setup. Confidentiality and security are ensured through a private Git repository, with a detailed hand-off call provided for post-implementation support. With my expertise in network automation and integration, I am confident in delivering a solution that meets your needs.

@sf264

Hello, Fahad here from Pakistan. I would be happy to develop a single backend service that will talk to the network that you are running that mixes Huawei, ZTE and BDCOM OLTs. I am confident in my ability to deliver high quality results. Let's connect via chatbox to discuss our potential collaboration. Looking forward to the opportunity to work together.

@tyronet2

You need one vendor-neutral REST API that normalizes OLT, PON, and ONU operations while keeping every vendor command isolated behind replaceable drivers. At Marin Software, I built Python services and real-time processing pipelines with modular integrations, retries, logging, and production monitoring. I would use FastAPI with separate BDCOM, VSOL, and Solitine adapters, selecting SNMP, SSH/CLI, or NETCONF according to each model’s supported interface. The shared schema will expose OLT health, PON statistics, ONU state, description updates, and VLAN changes through consistent JSON. Configuration writes will include validation, command confirmation, audit logs, timeouts, concurrency limits, and safe failure handling. I’ll provide Docker support, environment-based credentials, API documentation, cURL examples, tests against your devices, and private Git delivery. I should be transparent that I do not have proven automation experience with these specific OLT brands. Are Huawei and ZTE part of the first release, or is phase one limited to BDCOM, VSOL, and Solitine?

@jonasdedzo

Hi, I can help build a lightweight and modular REST API to manage Huawei, ZTE, and BDCOM OLT devices through a unified JSON interface. I have experience with API development, network automation, REST services, and integrating network devices using protocols such as CLI, SNMP, and NETCONF. I can develop: Unified REST endpoints: /olts, /pons, /onus OLT health monitoring PON statistics and status retrieval ONU status management ONU description and VLAN configuration updates Modular vendor drivers so new OLT brands can be added easily Clean JSON response structure Complete README with environment setup and cURL examples I will keep the architecture clean and scalable, with separate device handlers for Huawei, ZTE, and BDCOM so future expansion will not affect the core API. Deliverables: Full source code in private Git repository Documentation and setup instructions API usage examples Testing and handover support I am ready to review your test environment and start implementation. Looking forward to discussing your requirements.

@AndrewJSMAN

Built OLTs monitoring/management APIs before—mostly Huawei MA5600T series and ZTE C320, so this is familiar ground. I’ll use Python with FastAPI for the REST layer, add a driver layer with `paramiko` for SSH/CLI, `pysnmp` for SNMP, and `lxml` for NETCONF XML parsing, all wrapped in async tasks to keep it lightweight. Each vendor gets its own module under `drivers/` with a strict interface so new vendors slot in without schema breaks. Health, PON stats, and ONU status come from CLI/SNMP/NETCONF calls normalized to the same JSON schema, PUT/PATCH only expose ONU description and VLAN fields for safety. README covers env vars, driver matrix, and curl examples; repo pushed to your private Git with a 30-minute hand-off call once you validate endpoints against your credentials. Thanks, Andrii

@Tanmoy236

Hi There! I specialize in multi-vendor network API development with 9+ years of experience, and I can build one clean REST layer across your Huawei MA, ZTE C3xx and BDCOM OLTs. I’ll create modular device drivers for OLT/PON/ONU status, secure ONU description and VLAN updates, with consistent JSON responses, cURL examples and clear documentation. The architecture will also make adding future vendors straightforward. Can you share the exact OLT models and preferred backend stack so I can confirm compatibility and delivery time?

@carlosd178

Hello, As a result of a detailed review of your project requirements, I fully understand the scope and expectations. I have experience with REST API development, network-device automation, SNMP/CLI integrations, JSON normalization, Git, and modular backend architecture. In my opinion, the key challenge is abstracting Huawei, ZTE, and BDCOM differences behind one stable API schema while keeping vendor-specific commands and parsing isolated. I would implement separate device drivers/adapters for Huawei MA, ZTE C3xx, and BDCOM EPON/GPON, using SNMP, SSH/CLI, or NETCONF depending on what each model supports best. The REST layer would expose consistent `/olts`, `/pons`, and `/onus` endpoints, with PATCH/PUT operations for ONU description and VLAN changes, plus validation, timeouts, error normalization, and structured JSON responses. The code would be designed so additional vendors can be added through new adapters without changing the public API. I would also provide environment-based configuration, cURL examples, README documentation, private Git delivery, and hand-off support. A couple of quick questions: • Which exact Huawei MA and BDCOM models/firmware versions are in use? • For VLAN changes, do you need only service VLAN assignment, or also ONU port/tagging/profile configuration? Best regards, Carlos.

@emilesd617

Hi, I am a backend and network automation developer with 8 years of rich experience in software development, with a strong background in REST APIs and multi-vendor network integrations. I am familiar with Python, REST APIs, SNMP, SSH/CLI automation, NETCONF, JSON, cURL, Git, network management, OLT/ONU provisioning, VLAN configuration, and modular driver architecture. For your project, I can build a lightweight API with a common interface for BDCOM, VSOL, Solitine, Huawei, and ZTE while keeping each vendor implementation isolated behind its own driver. The `/olts`, `/pons`, and `/onus` endpoints can return a consistent JSON schema for health and status, while PUT/PATCH operations handle ONU description and VLAN changes through the protocol supported by each device. I would start with BDCOM, VSOL, and Solitine for both EPON and GPON as requested, then keep the structure ready for the Huawei MA and ZTE C3xx drivers. I'm an individual freelancer and can work on any time zone you want. Please contact me with the best time for you to have a quick chat. Looking forward to discussing more details. Thanks. Emile.

@codeandcommand

I run a network myself, so mixing Huawei, ZTE and BDCOM under one API is a real pain, especially with BDCOM's E-PON and G-PON units having different command sets. I'd wrap each vendor's SNMP or Telnet interface behind one REST layer with consistent JSON responses. Node.js, documented with Postman. Can start today, working version in 5 days. Want me to send a quick scope doc?

@lazarr4

Hello, I built a similar vendor-agnostic network monitoring API last year that talked to Cisco, Juniper, and MikroTik devices via SSH, SNMP, and NETCONF. The trickiest part was normalizing wildly different CLI outputs into clean JSON without overloading the drivers. The core problem is translating three distinct device ecosystems into one predictable REST schema. I’d use a plugin-based driver system in Python (FastAPI) because it keeps vendors isolated and the schema stable. The biggest win will be consistent error handling so a failing Huawei OLT doesn’t break the whole API. You’ll get immediate visibility into OLT health and per-PON stats without vendor lock-in, plus safe ONU config updates without touching the CLI manually. Every change will run through unit tests and a staging OLTs to catch regressions before they reach your production network. Let me know if you’d like to review the driver structure or test a mock endpoint. Thanks, Lazar

@mubeenm5026

As the lead of an experienced team at Web Crest, we not only have the breadth of technical expertise to take on projects of this nature, but we also adopt a business-focused approach to ensure that the solutions we build are tailored to meet our clients' precise needs. Our capabilities in developing APIs, documenting comprehensive READMEs, and utilizing Git for efficient code management align perfectly with the assignment at hand. Moreover, our proficiency in automation systems including NMS and OSS platforms combined with our familiarity with network equipment from multiple manufacturers including Huawei, ZTE, BDCOM as well as Huawei MA series, ZTE C3xx, and BDCOM OLTs equip us excellently for the Universal OLT Management API project. We understand that modularity is vital for creating a robust solution where new vendors can be easily integrated without complications or disruptions to the existing schema. This project relies on using SDKs provided by OEMs, so familiarity with models like VSOL and Solitine is an important part of the equation – one which we've successfully handled during various projects. Timeliness is crucial when it comes to delivering on technology projects and it's something we prioritize. So once we develop the lightweight and well-documented RESTful API capable of handling all your OLT models including Git backend push on private repository; I'll provide a detailed handover - ensuring smooth continuity for you.

@KasjanovaEste

Hi, Fernando here from Mexico City. I want the REST layer for /olts, /pons and /onus on your Universal OLT Management API. I note you need lightweight, well documented REST endpoints /olts /pons /onus with GET for status and PUT PATCH for editing ONU description and V Lan, a clean consistent JSON REST layer that works against Huawei MA series ZTE C3xx and BDCOM OLTs, plus a README with environment variables device drivers used and simple cURL examples and source code pushed to a private Git repository. I recently built a Python FastAPI service that wrapped SNMP and CLI for mixed vendor switches into one JSON API, so wiring Huawei ZTE and BDCOM OLTs behind a modular REST interface is close to how I already work. Do you want per vendor drivers abstracted behind a common interface or a shared SNMP first approach with vendor specific fallbacks? That decides how I structure the driver modules. Should VLAN edits be part of the same PUT PATCH on /onus or exposed as a separate endpoint? That changes how the schema evolves when new vendors are added. First I will map the Huawei MA ZTE C3xx and BDCOM command sets into a small driver interface and draft the exact JSON shapes for /olts /pons /onus so you can review before I connect to your test devices. Thanks

@rofeald

Hi, I can build a vendor-agnostic REST API that provides one consistent JSON interface for managing your BDCOM, VSOL, Solitine, Huawei, and ZTE OLT infrastructure across EPON and GPON. The main challenge is that each vendor exposes different CLI/SNMP/management structures. I’ll isolate those differences behind modular device drivers while keeping the REST schema consistent, so adding another OLT vendor later won’t require changing the API consumers. I’ll implement `/olts`, `/pons`, and `/onus` endpoints for health and status data, plus secure PUT/PATCH operations for ONU description and VLAN configuration where supported. Device communication will use the most reliable available protocol per vendor. I’ll include environment configuration, authentication handling, error responses, logging, cURL examples, and clear driver documentation, then test against your supplied devices before handoff. Let’s establish the exact command/API capabilities of the initial OLT models and build the abstraction around them. Regards, Rofeal

@razmiks2

Hi, I’ll deliver a lightweight Universal OLT Management API with clean REST endpoints /olts, /pons, and /onus. The service will normalize health, per-PON statistics, and ONU status into consistent JSON, while handling vendor-specific drivers for Huawei MA, ZTE C3xx, and BDCOM E-PON/G-PON. For ONU description and V-Lan updates, I’ll implement safe PUT/PATCH flows with idempotent payload validation and vendor adapters behind a stable schema. You’ll get a practical README covering required environment variables, supported protocol options, and quick cURL examples for end-to-end testing, plus a private Git repo for modular future vendor additions. Best, Razmik

@naeem1114

When mixing Huawei, ZTE and BDCOM OLTs, the biggest hidden snag is each vendor’s differing authentication timeout, which can cause failures during bulk polling. I’ll wrap each vendor’s CLI, SNMP or NETCONF calls in a driver that normalizes responses into a single JSON schema and adds retry logic. A lightweight FastAPI service will expose /olts, /pons and /onus with GET and PUT/PATCH as you need. A common pitfall is assuming all OLTs return the same status codes; many devices use vendor-specific error strings that break generic parsers. I’ll map those strings to standard HTTP codes inside the driver so the REST layer stays consistent. Ready to start immediately and get the first endpoints running on your test OLTs.

@sihalaths9

Dear Sir, I am thrilled to bid your project. I can build this as a modular REST API with a vendor-driver layer, giving you one consistent JSON schema while keeping CLI, SNMP, NETCONF, or other device-specific logic isolated behind adapters. I’ll cover OLT health, per-PON status/statistics, ONU details, and safe PUT/PATCH operations for ONU description and VLAN changes, with validation, timeouts, error handling, and clear device-level responses. The API can be structured around /olts, /pons, and /onus, with configuration driven by environment variables and each vendor driver independently replaceable or extendable. I’ll also provide a clean README, cURL examples, private Git delivery, and handoff testing against the credentials/devices you provide. One key question: for the first delivery, should support target Huawei/ZTE/BDCOM as listed in the acceptance criteria, or BDCOM/VSOL/Solitine as stated in the final note? That needs to be fixed upfront because it directly defines the initial driver set and testing scope. Sincerely.