search

lavabit / robox

The tools needed to robotically create/configure/provision a large number of operating systems, for a variety of hypervisors, using packer.
626 stars 139 forks source link

Difference between ubuntu generic 20 3.0.14 and 3.0.16 #165

Closed matthew-gill closed 4 years ago

matthew-gill commented 4 years ago

Hey... think title says it all, just wondering what the difference is please!

ladar commented 4 years ago

I accidentally ran rm -rf while waiting for the 3.0.16 boxes to finish uploading. So rather than wait until I could rebuild, I simply used the 3.0.14 images for the boxes that got wiped out...

I was already building 3.0.18, which is now uploading (and has been for the last 8 hours). So that should be out soon.

The 3.0.18 release includes completely rebuilt images for every box, with the exception of those built for Parallels (the Mac is offline), and the Dragonfly BSD 5 on Hyper-V. I haven't been able to rebulld that last one in awhile due to a compatibility issue with Dragonfly BSD and Hyper-V.

When a release gets close to being finished, if I'm having trouble with particular images, I generally just carry forward the existing image, so I can release those boxes that have been rebuilt, rather than hold up the overall release.

Why do I release everything like that? It's so that users get presented with a all of the platform choices. Not just the providers available in the most recent version. That's also why I wait until every box/provider is uploaded before "releasing" them.

I just brought new build bots online at my data center, so this is all part of me working out the new kinks in the pipeline. Hence the rapid rebuilds. Hopefully I'll be able to keep the new servers in the mix. I'm currently in negotiations with my colo vendor on that matter.

I'll probably kick off another rebuild soon. I wanted to get the pipeline smoothed out before attempting images with bigger disk sizes.