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 distinction between OS1 and OS2 for singlemode fiber in constants.py #2878

Closed
fischa opened this issue Feb 12, 2019 · 4 comments
Closed
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@fischa
Copy link

fischa commented Feb 12, 2019

Environment

  • Python version: 3.6 (from netbox-community docker image)
  • NetBox version: 2.5.5

Proposed Functionality

Addition of OS1 and OS2 singlemode fiber options in constants.py. No changes to workflow or user interface needed as far as I can see. I can add a PR if requested.

Use Case

This is needed for being able to choose from this two types of singlemode fiber for cable "creation". Till now there is just "Singlemode Fiber" available but four types of multimode fiber.

Database Changes

Not that I'm aware of. Name and ID come from constants.py and are probably stored as such in the DB.

External Dependencies

None.

@fischa
Copy link
Author

fischa commented Feb 12, 2019

image

@DanSheps
Copy link
Member

As discussed in Slack, there are other types beyond OS1 and OS2, so I would propose keep SMF as 3500, then add OS1 and OS2 as something like 3510, 3520 as they are derivative of the SMF type but rename it Singlemode Fiber (Generic)

@tb-killa
Copy link
Contributor

http://www.thefoa.org/tech/ref/basic/fiber.html

I prefer using official Names (see Graphic) if we allow to specify them:
http://www.thefoa.org/tech/ref/basic/FiberFamilyTree.jpg

@jeremystretch
Copy link
Member

For consistency, I'm going to:

  1. Add a generic MMF type
  2. Keep the existing generic SMF type in place
  3. Add two new types for OS1 and OS2

This leaves it up the user whether they want to specify just MMF or SMF, or a specific class.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application labels Feb 15, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

4 participants