On Thu, Apr 20, 2017 at 03:21:05PM -0400, Don Zickus wrote: > Hi Dan, > > Shawn is working with Jon and myself to add system firmware/bios info to the > beaker database to be displayed on the system details page.
Ping Dan? > > The idea was to make it easy to find how old a bios is on our lab machines > and see which ones need an update. > > Shawn made all the front end changes in the inventory job, but the backend > work is becoming a challenge. > > It seems like we are going to have to add a table entry to the database in > server/model/inventory.py? Which would probably cause a database migration > event. > > For now, we are using numa_nodes as our template to copy the output of lshw > (from the inventory script) into the database and onto the webpage. > > > Are we going in the right direction? Is this more work than we thought? > > > > Then as a follow-on, we are assuming the database has to be updated to add > this entry, would it make sense to convert the whole database to a generic > key/value table to dynamically support new fields without having to migrate > the whole database all the time? And then to prevent random junk from being > added by the inventory script (or other script), have a whitelist filter > that only allows certain keys to be added/updated. Maintaining the > whitelist would be easier on the database then adding table entries. > > This is just us trying to understand the architecture a little more and > trying to see where we can add some value to make it easier to maintain our > tests. Hi Nick, Thanks for the response. I wasn't subscribed to the list, but I had Jeff forward it to me. It is good to know the historical perspective. A shame that the original approach had performance issues. Cheers, Don _______________________________________________ Beaker-devel mailing list -- beaker-devel@lists.fedorahosted.org To unsubscribe send an email to beaker-devel-le...@lists.fedorahosted.org
