# 20210603 Gangplank in FCOS pipeline

- driving the version number at a high level
- kicking off x86_64 and aarch64 builds from higher level job
- idea: kick off aarch64 pipeline after x86_64 qemu tests pass
- we already know the build version number at this point
- where can we run this?
- aws a1.metal instance
- aarch64 machine in centosCI
- best way to push bits back and forth
- separate minio instance in CentOS CI?
- want this eventually
- use SSH forwarding for minio (sharing the PV)
- can use this initially for testing/POC
- bump-lockfile - need to bump lockfiles for aarch64
- tie x86_64 to aarch64 promotion
- how is OSTree signing involved?
- hopefully the same path as x86_64
- sign with aarch64 signing key
- need to check robosignatory if this is possible today
- JL: I think they're all the same key today?
- you're right!

Next Steps:

- find out strategy for hardware
- run gangplank in aarch64 pipeline from JenkinsFile
- MVP: aarch64 QEMU qcow2 generated for every pipeline run