Open Stack

W dniu 12.01.2018 o 15:49, Paul Belanger pisze:
> On Fri, Jan 12, 2018 at 11:17:33AM +0100, Marcin Juszkiewicz wrote:
>> Wu dniu 12.01.2018 o 01:09, Ian Wienand pisze:
>>> On 01/10/2018 08:41 PM, Gema Gomez wrote:
>>>> 1. Control-plane project that will host a nodepool builder with 8 vCPUs,
>>>> 8 GB RAM, 1TB storage on a Cinder volume for the image building scratch
>>>> space.
>>> Does this mean you're planning on using diskimage-builder to produce
>>> the images to run tests on?  I've seen occasional ARM things come by,
>>> but of course diskimage-builder doesn't have CI for it (yet :) so it's
>>> status is probably "unknown".
>>
>> I had a quick look at diskimage-builder tool.
>>
>> It looks to me that you always build MBR based image with one partition.
>> This will have to be changed as AArch64 is UEFI based platform (both
>> baremetal and VM) so disk needs to use GPT for partitioning and EFI
>> System Partition needs to be present (with grub-efi binary on it).
>>
> This is often the case when bringing new images online, that some changes to DIB
> will be required to support them. I suspect somebody with access to AArch64
> hardware will first need to run build-image.sh[1] and paste the build.log. That
> will build an image locally for you using our DIB elements.

Or someone will try to target q35/uefi emulation instead of i440fx one
on x86 alone. I am tired of yet another disk image building projects.
All think they are special, all have same assumptions. btdt.

If I disable installing grub I can build useless one partition disk
image on arm64. Nothing will boot it.