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:
- We create an installation for Windows Server 2019 to "SERVER01"
- 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
- 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.
Currently I use the SLM plugin to track EOL/lifecycle of our platforms. This requires that we assign a
SoftwareProductInstallationobject to every device and virtual machine. I have a script to do it, but it gets cumbersome when the following occurs:Since an object only has one platform at a time, I propose a new model for this use case, something like
PlatformSoftwareMap,PlatformEOLMap, orPlatformSoftwareVersionLink.It could have a foreign key to
dcim.Platformwithunique=True, and foreign key tonetbox_slm.SoftwareProductVersionI thought about tying
SoftwareProductInstallationto Platform in some way, but it seemed clunkier.