Re: [atomic-devel] ARM builds?

[Richard Henwood <Richard Henwood arm com>]

> -----Original Message-----
> From: Josh Berkus [mailto:jberkus redhat com]
> Sent: Thursday, September 01, 2016 2:58 PM
> To: Richard Henwood; Jason DeTiberus
> Cc: atomic-devel
> Subject: Re: [atomic-devel] ARM builds?
>
> On 08/26/2016 07:58 AM, Richard Henwood wrote:
>
> > After briefly chatting with Josh at RH summit, the short term goal is
> > 'build Atomic Host for AArch64'. Following that, I guess there might
> > be some work to make Atomic Registry 'do the right thing'? And
> > orchestration 'do the right thing'?
>
> So, here's my thoughts on an order of implementation:
>
>
> 1. Get base Atomic Host with a stable ARM port, on either Fedora or CentOS.
>

I'm looking into getting some AArch64 access for interested parties for this first stage. I have a couple of leads:
  + Linaro Developer Cloud. https://www.linaro.cloud/
     I've look, but not used this service. CentOS7 is an option, but currently Fedora 24 isn't. I've asked to see F24 can become an option.
  + Donated hardware. If I can find something, is there somewhere suitable to host it?

>From my experience over the last few days:
Following https://github.com/jasonbrooks/byo-atomic

Fedora 24 Atomic Host looked like the easier option to me. I filled in the following missing packages from CentOS repo:
cockpit-docker-0.77-3.1.f24.1.aarch64.rpm
kubernetes-1.2.0-0.12.0.1.gita4463d9.el7.centos.aarch64.rpm
kubernetes-client-1.2.0-0.12.0.1.gita4463d9.el7.centos.aarch64.rpm
kubernetes-master-1.2.0-0.12.0.1.gita4463d9.el7.centos.aarch64.rpm
kubernetes-node-1.2.0-0.12.0.1.gita4463d9.el7.centos.aarch64.rpm
I put these in a local repo, which worked well.

There are a few x86 specific bits in json, tdl, and .repo that are all simple enough to resolve; I removed grub2 from the packages and included boot_location: "both". I twiddled a few bit in the kickstart w.r.t. efi booting. The 'rpm-ostree tree compose' works now, with a healthy looking tree output.

HOWEVER: I'm currently not able to get an image out of ostree imagefactory. I believe the issue is within the phase wherein Qemu is instantiated. This is failing silently and outputting an empty qcow image.

Best regards,
Richard

<snip>
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.