Comment by bradwood
4 years ago
They use a load of other FOSS software under the hood too, not least of which libvirt/KVM.
I wonder how many other licences they're violating this way.
4 years ago
They use a load of other FOSS software under the hood too, not least of which libvirt/KVM.
I wonder how many other licences they're violating this way.
libvirt uses LGPL and the KVM/linux kernel uses GPL. Both are fine to keep to yourself if you run it on your own machine and only expose it over the network.
MinIO uses AGPL which explicitly includes network usage so Nutanix is forced to provide all patches and associated code.
Recent versions of MinIO use AGPL. Much of what they talk about here are issues with Apache licensed code. (The switch happened in April 2021).
https://github.com/minio/minio/commits/master/LICENSE
This really seems like Nutanix just didn’t include the MinIO NOTICES file in their OSS disclosures for some reason. Something so minor should have been an easy oversight to fix. Without actually testing out Nutanix, it’s hard to know if they are actually violating this part of the Apache license. MinIO isn’t included in their “open source packages we use” webpage, but that’s not where the NOTICES message would need to be included. Either way, it’s odd that things escalated like this.
The newer AGPL versions of MinIO would offer its own licensing challenge for Nutanix (which is part of the reason for the switch to AGPL). But that’s not even what MinIO is focusing on in their post. MinIO also don’t show the version of their software that they claim Nutanix is using. And it’s very possible that Nutanix froze the minio version in April 2021 (quite likely the case).
Nutanix distributes their AHV hypervisor to clients so the GPL would apply, I think.
Wasn't nutanix using cassandra "modified" for some SAN product almost 10 years ago?