Alexander Haase

Thanks for your contribution! NetBox core already has a documentation for supported colors [here](https://netboxlabs.com/docs/netbox/en/stable/configuration/data-validation/#field_choices). I'm not sure if we need to add this to the plugin documentation. However, if so,...

@jeremystretch should this be a replacement for the [netbox-inventory](https://github.com/ArnesSI/netbox-inventory) plugin? Right now the communication when using the plugin is that an asset is something in inventory and it becomes a...

Revisiting the [RFC of OSPFv2](https://www.rfc-editor.org/rfc/rfc2328#page-15), it appears that sessions can involve more than two peers. Consequently, I propose modifying my feature request to introduce a dedicated `OSPFSession` model for managing...

> As a counterpoint to your "Doesn't automatically tear down", this mimics real life where if you remove a device, you need to remove the OSPF session on the peer...

The background jobs framework of #15692 will include the ability to schedule system jobs, i.e. housekeeping or other tasks that run periodically in the background. While the plugin still requires...

The `JobRunner` framework now supports the implementation of any kind of task, including housekeeping. However, the automatic registration of jobs on plugin load did not make it into the PR...

How about adding the auto-registration to the beginning of the `rqworker` management command? It would only be called once for each worker started - not for the frontend and not...

I'm not sure if this is possible. Usually the registry handles static variables like a list of middleware to load. To register a `JobRunner`, its `enqueue_once()` method needs to be...

@jeremystretch can you assign this to me so I can work on a PR? Maybe we can still make it into 4.1.

@jeremystretch did you have any chance to review this? This would be the last missing piece to add auto-scheduling background tasks, which didn't make it into the `JobRunner` framework.