Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Additional PON Interface Types #14250

Closed
nick-bogle opened this issue Nov 10, 2023 · 7 comments · Fixed by #16208
Closed

Add Additional PON Interface Types #14250

nick-bogle opened this issue Nov 10, 2023 · 7 comments · Fixed by #16208
Assignees
Labels
type: feature Introduction of new functionality to the application

Comments

@nick-bogle
Copy link

NetBox version

v3.6.5

Feature type

Data model extension

Proposed functionality

I propose adding a new Interface Type of the following, that will be nested underneath the PON category in Netbox:

  • BPON (622 Mbps / 155Mbps)
  • 25G-PON (25 Gbps)

Use case

Currently the Interface Types in Netbox include 6 other PON port types, but notably missing are:
BPON (Broadband PON) which was what came before GPON. This would be helpful for users that still have BPON in their networks.

25G-PON is a new PON standard that has been implemented by Nokia and while it is still pre-standard, is being deployed by several telecommunications companies.

Database changes

N/A

External dependencies

N/A

@nick-bogle nick-bogle added the type: feature Introduction of new functionality to the application label Nov 10, 2023
@apellini
Copy link
Contributor

apellini commented Dec 4, 2023

if @jeremystretch approves I could do that

Copy link
Contributor

github-actions bot commented Mar 4, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Mar 4, 2024
@DorianXGH
Copy link
Contributor

I would even go as far as to add the 50G-PON Huawei has been doing recently.
All in all, no reason not to add them.

@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed pending closure Requires immediate attention to avoid being closed for inactivity labels Mar 27, 2024
@arthanson
Copy link
Collaborator

@nick-bogle can you please take a look at PR #16208 - would this address your request?

@arthanson arthanson self-assigned this May 20, 2024
@arthanson arthanson removed the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label May 20, 2024
@nick-bogle
Copy link
Author

@nick-bogle can you please take a look at PR #16208 - would this address your request?

I'd personally not make the 50G-PON type Huawei specific. While Hauwei is the first to market with an option for this, it is really being defined under ITU G.9804.3, and is being implemented and tested actively by ZTE, Nokia, and others.

@arthanson
Copy link
Collaborator

thanks @nick-bogle

@DorianXGH
Copy link
Contributor

@arthanson going through the changes, I just noticed I made a typo in the label of GPON when I wrote it, there's a missing 'b' in 'Gbps': (TYPE_GPON, 'GPON (2.5 Gbps / 1.25 Gps)') mayhaps this PR is a good opportunity to fix it ?

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: feature Introduction of new functionality to the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants