[12:58:41] I wanted to audit bios settings for a bunch of hosts in https://phabricator.wikimedia.org/T225713#5307808 is there already a way to do that programmatically via e.g. cumin ? I was thinking via ssh on the mgmt interface, but if we have a way to do that already from the os that works too [13:14:44] godog: I don't know what's the latest on that (I remember jbond42 working on an IPMI cumin module I think?) [13:14:48] but from a HW perspective [13:15:04] it will be vastly different between vendors, as well as within generations of HW from the same vendor [13:15:20] exposing BIOS settings to the mgmt interface is a relatively new development [13:18:59] soon in your local registry [13:19:00] root@boron:/srv/images/base# docker run docker-registry.discovery.wmnet/wikimedia-buster bash -c 'cat /etc/debian_version' [13:19:00] 10.0 [13:20:39] godog: i dont think there is anything in spicerack which dose that right now but there is https://doc.wikimedia.org/spicerack/master/api/spicerack.ipmi.html#spicerack.ipmi.Ipmi.command so you could write a cook book using that to get the infor you need [13:21:10] i also have an open CR to add some more facts https://gerrit.wikimedia.org/r/c/operations/puppet/+/517694/3/modules/ipmi/lib/facter/ipmi.rb so it might be possible to extend that with the info you need [13:21:16] paravoid: indeed, I noticed that too with the whole hierarchy in /system1 which AIUI is supposed to be somewhat standardized [13:21:20] but it all depends on what bios config you want [13:21:46] the standard nowadays is Redfish [13:21:49] replaces IPMI [13:21:55] HTTP RESTful APIs :) [13:22:07] there are python libraries for it (e.g. openstack ironic has some of them) [13:22:54] jbond42: sweet, thank you! I'm looking to read the power regulator settings for https://phabricator.wikimedia.org/T225713 [13:24:22] heh fingers crossed on redfish, I'm reading up on it now [13:49:01] godog: i have created a patch to add a new cpu_details.governor fact if its helpfull https://gerrit.wikimedia.org/r/c/operations/puppet/+/520885 [13:50:32] jbond42: yeah! thank you, for sure selecting hosts e.g. in cumin will come handy, I'll comment on the review [13:52:18] in fact if you want to query via cumin i think i will have to create a legacy fact as well perhaps $cpu_governor (cumin cant currently query structured facts) [13:56:39] hah, ok if it comes to that I'll poke you jbond42, good to have structured facts for now [13:57:09] its fine its wasy to add just doing another cut now and will add scaling_driver as well[3~ [14:59:26] * volans around [15:36:13] godog: i have pushed that CR so the facts should be avalible in ~30 mins [15:40:28] jbond42: \o/ thank you [15:40:37] np :) [16:19:52] i have a weird thing on swift. Just published a docker image which is backed by swift. then there is a file which contains the blob image from docker on codfw while replicating to eqiad's swift this file disappears on swift [16:20:03] https://www.irccloud.com/pastebin/vkCaHPuO/ [16:20:07] pertinent logs [16:21:09] i do see some 409 conflicts on some backends but i expect this to be usual