"...the on-premise offering of Quay was released." It's my premise that the author of that press release doesn't know the difference between "premise" and "premises." I know we have a habit in American English to evolve the meaning of words faster than any other language but surely IBM's press team could offer to proof-read things like this before posting. https://www.merriam-webster.com/dictionary/premise (And yes,…
Red Hat Introduces Open Source Project Quay Container Registry
21–30 of 106 posts
Re: Red Hat Introduces Open Source Project Quay Container Registry
#22Love this. After Red Hat acquired Ansible I thought for sure they would cave on their open source principles, but they didn't . They really believe in open source, and we are all the better as a world for it. Disclaimer: I work for Red Hat but have been a fan decades longer than I've worked there.
They believe in making money. The issue is that OSS is the only way to compete with the cloud. Quay would die without 3rd party contributions vs Amazon, Google, Microsoft.
We happily make money without sacrificing our Open Source/Free Software principles. Does that bother you?
(Disclaimer: Red Hatter since almost 15 years. I never doubted for a second that we would open source what we buy. Ansible, 3Scale, CoreOS, we have a long history of sticking to our principles)
Re: Red Hat Introduces Open Source Project Quay Container Registry
#23"...the on-premise offering of Quay was released." It's my premise that the author of that press release doesn't know the difference between "premise" and "premises." I know we have a habit in American English to evolve the meaning of words faster than any other language but surely IBM's press team could offer to proof-read things like this before posting. https://www.merriam-webster.com/dictionary/premise (And yes,…
IBM use "on-premise" all the time. Like it or loathe it, it's become the accepted neologism for "self-hosted".
My personal preference is to use "on-prem" because:
1.) There are arguments but no definitive justification for choosing between on-premise and on-premises.
2.) A lot of what gets lumped under on-prem is not actually on your premises anyway. It's in a colo or a managed hosting provider, etc.
Re: Red Hat Introduces Open Source Project Quay Container Registry
#24Newbie question: How does quay differ to docker hub?
Once of the nicer features is that they offer an "encrypted password" where you login to quay and click the "generate encrypted password" option in your user preferences. Then instead of hardcoding your plaintext password into your docker config json, it puts the encrypted password that is only applicable to quay. For those that use LDAP authentication for this, it makes is a much smaller attack vector. The per-team…
Quay also integrates very well with OpenShift. It works fine stand-alone too, but if you're already using OpenShift it's worth looking into.
Re: Red Hat Introduces Open Source Project Quay Container Registry
#25ProjectQuay.io landing page is now live! https://projectquay.io
Re: Red Hat Introduces Open Source Project Quay Container Registry
#26Earlier quoted context omitted.
Yes, any for-profit company has to believe in making money. However I think they could make a lot more by being stingy with their code. Ansible for example had a lot of paying customers that no longer had to shell out after it went open source. I (and many people/companies I know) would likely pay for RHEL if CentOS weren't a thing. There's plenty of opportunities for a cash grab if that were Red Hat's thing.
What they need to do is to come up with a monetization model that makes more sense. As a devops, I rely heavily on Hashi and Ansible and Chef and so many other tools. However, their enterprise offerings are both too expensive and also too big for what I need. I can't get my employer to just donate money, so what can I simply and easily buy to fund the effort while still getting some value? Grafana, for example, with…
We happily make billions in revenue and just got bought by IBM for $34B. Why should we aim for more through betraying what binds us?
Re: Red Hat Introduces Open Source Project Quay Container Registry
#27Earlier quoted context omitted.
Kway makes more intuitive sense to me; it's like the word quail .
But this is also a word in common usage, and it already has a pronunciation: "key". English is not a good place to go if you are looking for intuitive pronunciation.
Nor consistency of pronunciation. Schedule / School is another good one if you’re in the UK.
Re: Red Hat Introduces Open Source Project Quay Container Registry
#28Earlier quoted context omitted.
But this is also a word in common usage, and it already has a pronunciation: "key". English is not a good place to go if you are looking for intuitive pronunciation.
Nor consistency of pronunciation. Schedule / School is another good one if you’re in the UK.
And Nippl-e
Re: Red Hat Introduces Open Source Project Quay Container Registry
#29Worth noting this is happening after the incorporation of VMware’s harbor registry into cncf. Harbor provides a solid enterprise registry with auth, Clair scanning, and a reasonable ux. https://goharbor.io/
Still, it’s great to see quay make it out into the open.
Re: Red Hat Introduces Open Source Project Quay Container Registry
#30Earlier quoted context omitted.
The "most correct" pronunciation of Quay is "key", as that link says, but the CoreOS team always pronounced it "kway". (I assume this has carried through to Red Hat.)
Kway makes more intuitive sense to me; it's like the word quail .
Mmmm, quail salad: https://upload.wikimedia.org/wikipedia/commons/thumb/2/20/Bo...
