Update to match Netbox major version

[MajesticFalcon]

The current plugin is only designed to work with versions <3.0. Netbox v3 seems mature enough to begin porting over our internal projects. I will port this one over as well.

[jahknem]

Hi @MajesticFalcon , have you made any progress on this? Can I be of assistance? This plugin would make my life a lot easier.

[davama]

There has been some PON related work on the netbox project: https://github.com/netbox-community/netbox/issues?q=is%3Aissue+is%3Aopen+PON

im curious to understand what this plugin offers that the current netbox does not.

at least for us right now, the one-to-many/many-to-many connection relationship was a huge step forward

[jahknem]

There has been some PON related work on the netbox project: https://github.com/netbox-community/netbox/issues?q=is%3Aissue+is%3Aopen+PON

im curious to understand what this plugin offers that the current netbox does not.

at least for us right now, the one-to-many/many-to-many connection relationship was a huge step forward

@davama PON has, as far as I know, two layers. One layer is the physical layer, which is how the PON is connected to the ONT devices via one or more splitters. The other layer is the connection between the logical/virtual port on the OLT to which the ONT Device has a logical point to point connection. This logical connection is something which I am sorely missing in Netbox. Without it I cannot move forward with automation. I had hoped that this plugin would offer something similar, but could not test it yet due to the non-compatible version

[MajesticFalcon]

This plug-in came out way before pon was implemented in netbox. Additionally, it offers a lot more PON focused attributes. It understands splitters in a way that the current netbox is painful to configure. Unfortunately I’ve moved states and I’ve been so busy with new life that I havnt been able to devote any time to this project. On Jan 4, 2023, at 8:26 AM, Jan ***@***.***> wrote:  There has been some PON related work on the netbox project: https://github.com/netbox-community/netbox/issues?q=is%3Aissue+is%3Aopen+PON im curious to understand what this plugin offers that the current netbox does not. at least for us right now, the one-to-many/many-to-many connection relationship was a huge step forward @davama<https://github.com/davama> PON has, as far as I know, two layers. One layer is the physical layer, which is how the PON is connected to the ONT devices via one or more splitters. The other layer is the connection between the logical/virtual port on the OLT to which the ONT Device has a logical point to point connection. This logical connection is something which I am sorely missing in Netbox. Without it I cannot move forward with automation. I had hoped that this plugin would offer something similar, but could not test it yet due to the non-compatible version — Reply to this email directly, view it on GitHub<#2 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACBR6OMTUMUK3OKLV3IQ2XDWQWCA5ANCNFSM56NM7M6A>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[davama]

@MajesticFalcon and @jahknem thank you for the input

at least from a logical perspective, you could provide some form of relationship between the PON port and the ONT port. We still looking to see how else we can fully utilize the current PON implementation in netbox to an extent.

Best,
Dave

[jahknem]

@davama I would appreciate if you could elaborate on how the PON implementation helps you. From your screenshot I can only see the point2multipoint cabling update being used. I have also not yet found a reference in netbox code or docs on how the interfaces of the type PON are treated any differently from other interface types.

But I also think that this discussion is out of scope for an issue. Are you on the netbox slack server? You can find me there using my github username.

Best,
Jan