I’m also not sure how CloudStack’s CI/CD setup works and how easy/complicated it may be to run a full build on Rocky. But we could always run a build of the 4.15.0 release on a standalone Rocky server - planning to do that in the next couple of days, once I build a Rocky template on our test infrastructure.
Got Rocky to work just fine on an advanced networking zone in CloudStack powered by KVM. Pretty normal. Trying Xen now. On another note - the whole point about versioning is to avoid situations where something new breaks what’s working just fine. I’m honestly not sure what Red Hat is driving at with this stream approach, and I’m willing to bet it will be a disaster. Best! Rudraksh Mukta Kulshreshtha Vice-President - DevOps & R&D IndiQus Technologies O +91 11 4055 1411 | M +91 99589 54879 indiqus.com This message is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential and/or privileged. If you are not the intended recipient please delete the original message and any copy of it from your computer system. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited unless proper authorization has been obtained for such action. If you have received this communication in error, please notify the sender immediately. Although IndiQus attempts to sweep e-mail and attachments for viruses, it does not guarantee that both are virus-free and accepts no liability for any damage sustained as a result of viruses. On 22 Jun 2021, 11:20 PM +0530, Nathan McGarvey <nathanmcgar...@gmail.com>, wrote: > All, > Since CentOS8 (not stream) is officially EOL at the end of this > year, I'd say keep supporting it until then, but don't support it past > then. This may be a good 6-month transition to support > Rocky/Alma/Springdale/whatever. Realistically, I'd be surprised if one > of those worked and one didn't since they should be by-and-large > binary-compatible rebuilds from RHEL sources. Possibly slightly lagging > in release times, but compatible. > > Rocky is nice since it isn't "tied" to another company, which is the > obvious double-edged sword of funding, etc. But it may mean it aligns > with the ASF more closely in spirit. > > Alma has only said they'll support it through the RHEL 8 lifecycle > (2029): https://almalinux.org/ "Until when will we support AlmaLinux > OS? AlmaLinux partners has committed to supporting AlmaLinux OS until > 2029, ...", which is generous, but they do stem from selling CloudLinux. > So it could become paid-for pretty easily. > > CentOS Stream could be fine or a disaster, and it is hard to tell: "a > rolling preview of future RHEL kernels and features." as the RedHat CTO > said seems to imply cloudstack might run into a lot more issues due to > the squishy nature of kernel releases, kvm/libvirt, etc. I don't think > it will be unusable, but it will be hard to say what is supported. (E.g. > what version is "Centos 8 Stream"? Stuff can change out from under you > pretty quickly in that paradigm. Even rolling distros like Debian have > point releases. > > > My $0.02 would likely to transition to Rocky, but it may be prudent > to wait a month or two to make sure it really is stable since they > *just* released a GA. > > > > How hard would it be to make a test build on the new Rocky GA and > see if it looks similar/identical to the CentOS 8.4? Not sure how > CloudStack's CICD is setup, internally. > > > Thanks, > -Nathan McGarvey > > > > On 6/22/21 9:41 AM, n...@li.nux.ro wrote: > > Hi, > > > > Drop support for CentOS8, 8-Stream or both? > > > > Regards > > > > On 2021-06-22 08:41, Rohit Yadav wrote: > > > All, > > > > > > With GA release of Rocky Linux 8.4 > > > (https://docs.rockylinux.org/release_notes/8.4) does it make sense now > > > to completely drop support for CentOS8 in the next major release? I > > > did a quick test and it seems rpms built on centos8 container continue > > > to work on Rocky release. Thoughts? > > > > > > Regards, > > > Rohit Yadav
