News for hackers. Stuff that matters.

A comment on Nutanix Objects violates MinIO’s open source license.

Re:Nutanix Objects violates MinIO’s open source license by manictothemax on Tuesday July 19, 2022 @11:05AM (#32152522)
Nutanix Objects does not use minio in the core data path. The presence of a binary in a kubernetes pod doesn't necessarily mean that the binary is being used or the fact that nutanix objects is nothing but a wrapper over minio. Earlier implementations did use minio purely as a S3 protocol adapter, i.e a protocol translator from S3 API to Nutanix internal storage protocol. This was something that was publicly acknowledged : https://blocksandfiles.com/2019/11/07/nutanix-objects-storag...

However, in later releases they seemed to have replaced the minio based protocol adapter to something that they developed in-house in C++ and have no longer using minio in their protocol stack.

[ Parent | on HN ]
Re:Nutanix Objects violates MinIO’s open source license by flatsix on Tuesday July 19, 2022 @01:48PM (#32155383)
I recently left Nutanix, but I worked on Objects for the past 12 months. The MinIO path was deprecated by the time that I joined. I don't have enough information to confidently side with either Nutanix or MinIO, but I'll clarify and confirm a few things:

- As you said, MinIO was used to translate S3 REST API requests to internal RPCs.

- MinIO was replaced with an in-house S3 API server.

- I distinctly remember seeing a patch 6-12 months ago where MinIO was removed from the build.

[ Parent | on HN ]
Re:Nutanix Objects violates MinIO’s open source license by justinclift on Wednesday July 20, 2022 @02:45AM (#32162336)
Out of curiosity, do you remember what language the in-house S3 API server was written in? :)
[ Parent | on HN ]
Re:Nutanix Objects violates MinIO’s open source license by jonhohle on Tuesday July 19, 2022 @11:17AM (#32152739)
Whether they use it or not is irrelevant if they are distributing it.
[ Parent | on HN ]
Re:Nutanix Objects violates MinIO’s open source license by mbreese on Tuesday July 19, 2022 @11:34AM (#32153038)
It would make it easier to remove though… which makes it even more odd that it is still there even after the three years of notice.
[ Parent | on HN ]
Re:Nutanix Objects violates MinIO’s open source license by manictothemax on Tuesday July 19, 2022 @01:55PM (#32155498)
Seems like an oversight that the binary got shipped with the pods
[ Parent | on HN ]
Re:Nutanix Objects violates MinIO’s open source license by jaywalk on Tuesday July 19, 2022 @02:28PM (#32155942)
It could have been an oversight initially. But three years later? Impossible to claim ignorance now.
[ Parent | on HN ]
Re:Nutanix Objects violates MinIO’s open source license by GK1981 on Tuesday July 19, 2022 @12:58PM (#32154649)
ROFL if you see block and files as the official disclosure fron Nutanix is a great testament of how that company is run :) Try getting their OSD file and see if MinIO is listed :)
[ Parent | on HN ]
Re:Nutanix Objects violates MinIO’s open source license by y4m4b4 on Tuesday July 19, 2022 @11:18AM (#32152751)
Nutanix does not carry EULA or reference even today while continuing to use it.

Read Apache v2 attribution clauses.

[ Parent | on HN ]
Re:Nutanix Objects violates MinIO’s open source license by justinclift on Tuesday July 19, 2022 @01:45PM (#32155322)
> while continuing to use it.

But the parent to your comment says they don't use it (any more)???

[ Parent | on HN ]
Re:Nutanix Objects violates MinIO’s open source license by y4m4b4 on Tuesday July 19, 2022 @05:41PM (#32158349)
Of course they use it, its there in their container :-)
[ Parent | on HN ]