Recently, we've got a need to change device type template in the Lab beyond what's shipped in LAVA releases. These changes either specific to peculiar hardware combinations/issues happening in the Lab, or something which isn't practical to propagate to the LAVA distribution at this time: https://git.lavasoftware.org/lava/lava/-/merge_requests/1481
Ideally, such changes should be tracked via Lab's configuration management system, but I may imagine it may take some time to setup that process, and some changes are experimental (cancelled or flip-flopping) anyway. But given that we have 2nd change like that, I'd like them to be captured and visible via change management process, even via interim solution.
To not create yet another repo which will be forgotten and hard to find later, I propose to track those in the existing repo (which then becomes "catch-all things LAVA/LITE" instead of just "LITE LAVA/docker setup").
Recently, we've got a need to change device type template in the Lab beyond what's shipped in LAVA releases. These changes either specific to peculiar hardware combinations/issues happening in the Lab, or something which isn't practical to propagate to the LAVA distribution at this time: https://git.lavasoftware.org/lava/lava/-/merge_requests/1481
Ideally, such changes should be tracked via Lab's configuration management system, but I may imagine it may take some time to setup that process, and some changes are experimental (cancelled or flip-flopping) anyway. But given that we have 2nd change like that, I'd like them to be captured and visible via change management process, even via interim solution.
To not create yet another repo which will be forgotten and hard to find later, I propose to track those in the existing repo (which then becomes "catch-all things LAVA/LITE" instead of just "LITE LAVA/docker setup").