On 2021-03-03 12:52:40 +0000 (+0000), Sean Mooney wrote: [...]
i know that the nodepool images are hosted publiclaly but i can never remberer where. if we wraped the cirror build in a dib element that might be an approch we coudl take. build it woith nodepool build then mirror that to the cloud and use it.
The images we build from Nodepool 1. are created with diskimage-builder (does DIB support creating Cirros images?), and are uploaded to Glance in all our donor-providers (are we likely to actually boot it directly in them?).
the other idea i had for this in the past was to put the image on tarballs.openstack.org we have the ironic ipa image there already so if we did a one of build we coud maybe see if infra were ok with hosting it there and the mirroing that to our cloud providres to avoid the need to pull it.
The files hosted on the tarballs site (including the IPA images) are built by Zuul jobs. If you can figure out what project that job should reside in and a cadence to run it, that might be an option.
the other option might be to embed it in the nodepool images. while not all jobs will need it most will so if we had a static copy of it we could inject it into the image in the devstack data dir or anogher whle know cache dir in the image and just have devstack use that instead of downloading it.
We already do that for official Cirros images: https://opendev.org/openstack/project-config/src/branch/master/nodepool/elem... If you look in the build logs of a DevStack-based job, you'll see it check, e.g., /opt/stack/devstack/files/cirros-0.4.0-x86_64-disk.img and then not wget that image over the network because it exists on the filesystem. -- Jeremy Stanley