Dirk Müller schrieb:

...

1. Build Power

At the moment there's one openQA worker running on a PPC64 host (power8). That host is fast enough to run the emulation reasonably well. To do serious tests we need real hardware with kvm though.

We have some hardware available.. does it need to be in the external network?

Jain. I agreed with Lars to create a separate openQA worker VLAN. This new network will not be reachable from the internet. The setup will allow to easily switch workers between OBS and openQA without physical rewiring.

...

Meanwhile maybe an installation DVD could help. The limited set of packages on the DVD probably has a chance to finish in time.

We can do that as well, unfortunately the DVD builds require the pattern/package list magic which I still don't know about. its certainly not ideal to maintain those package lists (that are slightly different than x86_64) ourselves manually. Any idea where to start on that?

See below.

...

2. Project Setup

To get a real Tumbleweed for aarch64 the OBS setup needs to be changed:

- openSUSE:Factory:ARM/_product need to become a link to openSUSE:Factory/_product. That way arm inherits the Tumbleweed version number.

you mean the date based version number like 20150331 ? is that all? when does it need to be bumped? is there a script involved that bumps it once openqa passes?

There are two scripts involved. The staging plugin and the totest manager.

It used to be a link but we had tons of merge conflicts all the time, which is why we removed the link at some point.

Looking at PowerPC I guess some of those conflicts could be avoided by splitting more things out of openSUSE.product and include architecture specific files instead.

it would be nicer to maintain the ARM related things in openSUSE:Factory but SR's don't get accepted and bribing by email to get one liner fixes committed in less than a week of roundtrip is also not always the best thing to spend time on.

One of the reasons why it took so long to get a testable aarch64 into openQA... The separate project is fine as long as it only contains the products most of the time. PowerPC is doing the same after all.

...

- openSUSE:Factory:ARM:ToTest needs to be created to hold the snapshots that go into openQA

created. who needs to have write privileges?

The user who runs the totest manager.

...

3. Scripts

The magic factory scripts (totest manager, pattern generator) need to be adjusted. Dinar did most of the heavy lifting for ppc so the scripts are now able to handle another architecture. The spots needed for aarch64 should be easy to find by searching for ppc.

git url?

totest manager: https://github.com/openSUSE/osc-plugin-factory pattern generator: https://github.com/openSUSE/package-lists cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5; 90409 Nürnberg; Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Donnerstag, 2. April 2015, 09:19:44 wrote Andreas Schwab:

Dirk Müller writes:

...

We're building with native hardware since ~ 12 hours on Factory after some hickups (and still sorting out the fallout of that). So that problem should be solved hopefully. The tree is about to be ready to be published (if only the OBS scheduler would actually notice it).

Does it actually publish if the repository isn't ready yet? We still have the emulated armv6l which blocks the images/local repo from finishing.

kiwi type repos get always published immediatly after each build job. So one image can not block the others. -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org