| *** dmellado81 is now known as dmellado8 | 04:55 | |
| minix | Hi everyone, I'm new to Ironic, and I apologize in advance for this seemingly silly question. Can you please explain the differences between whole disk and partitioned disks in Ironic? Additionally, based on your knowledge and experience, which approach is considered the best practice for production-level deployments? Thanks! | 13:41 |
|---|---|---|
| JayF | Hey, so first of all, it's a Saturday. That means most Ironic contributors aren't around | 16:50 |
| JayF | I'm not working today but hey I'm here so lets tackle the question :D | 16:50 |
| JayF | minix: basically, whole disk vs partition are referring to images: if you have an image which includes, for instance, what you'd have on a whole disk: including partition table and multiple partitions inside a single image; you're using a whole disk image | 16:51 |
| JayF | minix: if you're using an image that only contains the data for a system, but not also a partition table -- that's a partition image | 16:51 |
| JayF | minix: effectively the difference is: for a Whole Disk iamge; Ironic writes it and does little else (it will add a configdrive partition+populate it given correct sizing/configuration) | 16:52 |
| JayF | minix: For a partition image, Ironic handles the disk partitioning and bootloader installation, and extracts your provided image inside a partition it creates (using config you set) | 16:52 |
| JayF | You will find a lot of fiddly things like this in Ironic because hardware is fiddly, and lots of different people have lots of different opinions about best practices. | 16:52 |
| JayF | As for me? I'll say to use the type of image that you already have. I tend to personally deploy whole disk images if you had to make me choose ... but don't consider that an expert opinion so much as a personal preference to know exactly what's going to end up on the disk | 16:53 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!