Skip to content

Feature request: Way to tie SoftwareProductVersion to Platform #69

@natecohen

Description

@natecohen

Currently I use the SLM plugin to track EOL/lifecycle of our platforms. This requires that we assign a SoftwareProductInstallation object to every device and virtual machine. I have a script to do it, but it gets cumbersome when the following occurs:

  1. We create an installation for Windows Server 2019 to "SERVER01"
  2. We upgrade SERVER01 to Windows Server 2022 and change the platform on the object, but forget to change the SLM object - now we have inaccurate reporting
  3. We remember to add a new SLM install object to SERVER01 for Windows Server 2022, but we forgot to delete the assignment for Windows Server 2019 - we have two installations on SERVER01 and our reporting is still inaccurate

Since an object only has one platform at a time, I propose a new model for this use case, something like PlatformSoftwareMap, PlatformEOLMap, or PlatformSoftwareVersionLink.
It could have a foreign key to dcim.Platform with unique=True, and foreign key to netbox_slm.SoftwareProductVersion

I thought about tying SoftwareProductInstallation to Platform in some way, but it seemed clunkier.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions