Hi Keith, Process-wise, I believe it would be simpler and less taxing on effort / testing / supportability to standardize on one final OS target platform. Supporting a choice of OS platforms is hard and more effort than rewards. While selecting the OS, we could consider the following (this is just my top-of-mind, there may be more aspects to consider):
- End-of-life / LTS status for that OS. - Licensing and commercial implications if any. - Ready and wide availability of image(s) for the cloud providers (Azure, EC2). - We should not require the user of Muchos to have to build their own image. - Those cloud provider image(s) should support cloud-init. - Those cloud provider image(s) should be updated by the cloud provider (or partners thereof) on a reasonably regular (quarterly or more frequent?) basis to try to include as many security patches out-of-the-box. - The OS should be reasonably "stable" in that it should not increase burden on the user of Muchos by introducing any regressions (functional / perf) of its own origin. - There should be ready availability of OpenJDK binary distribution for that OS. ... etc. BTW, I did some work in December to evaluate Ubuntu 20.04 as a candidate OS for the Muchos cluster nodes on Azure. In the proof-of-concept that I did, the changes to the Muchos code base seemed to be contained to yum packages, OpenJDK package names, and similar relatively minor changes. The downstream playbooks for Zookeeper, Hadoop, Accumulo "just worked". I hope this helps. Arvind. -----Original Message----- From: Keith Turner <ke...@deenlo.com> Sent: Wednesday, January 5, 2022 2:00 PM To: fluo-dev <dev@fluo.apache.org> Subject: [EXTERNAL] [DISCUSS] Move Muchos from Centos 7 to another OS We need to move Muchos from Centos 7 to another OS. Not completely sure how we should proceed. Below is a possible process we could follow to make this change. * We collaborate to create a list of candidate OSes with pros and cons for each OS, not sure where is best to do this. I don't think a mailing list is the best place for this collaboration, however it's nice for the collaboration to be recorded on the mailing list. * We hold a vote (possibly iterative voting or ranked voting) to try to reach consensus on one of the candidate OSes we would like Muchos to use. * After a candidate is selected we can create a branch and start submitting PRs to move Muchos to that new OS in the branch. When it's functional we can merge that branch into main. Can anyone think of another process we could follow to move Muchos to another OS? Does anyone object to the process proposed above or have suggestions to improve it? Keith
