Hi Mick, Brandon, Thanks for your reply and explanation. Mick Semb Wever <m...@apache.org> 于2021年4月12日周一 下午11:49写道：
> Sheng Liu, > > > > The ARM CI will be a gate to ensure long term development support ARM64 > in Cassandra. > > > The servers that Huawei have provided have been instrumental in > getting the build and tests running on arm64. This is a huge > contribution to the community and I would like to say a big and public > "thank you" for the initiative from all of us. > > > > Now maybe we can consider more > > about that, is it possible to publish releases with ARM specific binary > > packages like Hadoop[4] did? > > > Part of the CI pipeline is generating the tarball, debian and redhat > packages for each commit, which are now stored under nightlies. And we > now have those for ARM, for example: > > https://nightlies.apache.org/cassandra/trunk/Cassandra-trunk-artifacts/519/Cassandra-trunk-artifacts/jdk=jdk_11_latest,label=cassandra-arm64/build/ > > That looks great! > Going from nightlies to releases, the biggest challenge I see is the > gpg signing of them. > > From ASF INFRA's policy¹ on releases: > • Private keys must not be stored on any ASF machine. Likewise, > signatures for releases must not be created on ASF machines. > > I don't know how Hadoop's release process² deals with it in its > create-release script³. From the 3.3.0 release, all staged artefacts > are listed together…⁴ > > But my understanding of it all is that we can't create ARM specific > releases until we have a release manager that owns an ARM machine > where they can keep their gpg private key. It might be possible to > create a release via SSH and gpg-agent⁵ if we update our release > scripts⁶, but this should be double-checked with INFRA. > > Oh sorry, that's my mistake, I forgot that, yes, the Hadoop 3.3.0 ARM artifacts was published with Brahma Reddy Battula help, who is Hadoop PMC member and is also working for Huawei, he has served as the Hadoop 3.3.0 release manager, and has talked with Hadoop community that he will also take charge of the ARM artifacts of future releases. there is a discussion: http://mail-archives.apache.org/mod_mbox/hadoop-yarn-dev/202003.mbox/%3CCAPwQCrkgwcDDFtC4+i_pv0pO8Zx6UG_43K=szxtv6k7-h4v...@mail.gmail.com%3E For Cassandra, Maybe it is a really a big challenge. > To move forward on the issue, we need the following information: > - how is hadoop creating (and gpg signing) multi-architecture > releases? Is it from multiple `create-release` executions? > yes it is from multiple `create-release` executions, but I am not soure about if there is addtions operations in Apache infra side. - are there other apache projects doing multi-architecture releases? > are they part of one release, or separately created and labelled > releases? how are they doing the gpg signing? > So far only the Hadoop has multi-architecture releases with ARM artifacts. some other projects only publish the source code release package, what can we do is to try to add annoucement about ARM support. > - can we SSH gpg-agent sign releases on hardware the release manager > does not own? > Or add an announcement about ARM platform support in Cassandra doc ? > > > Absolutely! I hope this becomes one significant part of the 4.0 > announcement. > Thanks for doing that. I am not sure if we can find a way to solve the above problems finally. But if we cannout publish official ARM64 artifacts due to the Apache policy limit, maybe we can publish an unofficial ARM64 artifacts ? > > regards, > Mick > > > [1] https://infra.apache.org/release-distribution.html#sigs-and-sums > [2] https://cwiki.apache.org/confluence/display/HADOOP2/HowToRelease > [3] > https://github.com/apache/hadoop/blob/trunk/dev-support/bin/create-release > [4] https://home.apache.org/~brahma/Hadoop-3.3.0-RC0/ > [5] https://wiki.gnupg.org/AgentForwarding > [6] > https://github.com/apache/cassandra-builds/tree/trunk/cassandra-release > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
