Earlier quoted context omitted.
disclaimer: I work on openshift.io, and there will be much more coming out as summit goes on so I can't refer to more than in current news: From https://www.redhat.com/en/about/press-releases/red-hat-unvei... Team Collaboration Agile Planning Developer Workspace Management Application Coding and Testing Runtime Stack Analysis Continuous Integration and Delivery thus it is more than "just" an online IDE in the traditi…
So if a company chooses openshift.io, then I'm not going to be able to use IntelliJ, NetBeans, emacs, vim, visual studio code, etc. That'll help attract talent.
Red Hat OpenShift.io – Free, end-to-end, cloud-native development
71–80 of 124 posts
Re: Red Hat OpenShift.io – Free, end-to-end, cloud-native development
#72I wonder if there's a name for this: that impatience and discomfort you feel about anything new until you understand what it is exactly and what to compare it to. Until that question is answered, you have ZERO patience for any marketing you read: especially fluffy visionary commentary about "digital transformation". You are quite literally making your readers angry because you are not answering their questions. For a…
> 2. Show photos, video, or screenshots. You'll literally be able to demo it yourself for free, on demand, in production (IF YOU DARE!), within the next few days.
A missed opportunity, but there is still time to recover.
Re: Red Hat OpenShift.io – Free, end-to-end, cloud-native development
#73Earlier quoted context omitted.
> I'll see if we can get a fix pushed out for this today/ASAP. The issue currently occurs when you have multiple Red Hat accounts that use the same email address (or a sub-addressed version of the same email address, like "chris@gmail.com" and "chris+123@gmail.com". Is this a special case for Google mail or do you assume foo+bar@example.domain is the same as foo@example.domain ? Why?
It's an abuse prevention mechanism. We do not permit users to have multiple OpenShift Online accounts. See 2.1 in the OpenShift Online terms of service: https://www.openshift.com/legal/terms.html "You may not (or permit third parties to) create multiple accounts or otherwise access the Services in a manner that is intended to avoid Fees or to circumvent maximum capacity thresholds for the Services."
Re: Red Hat OpenShift.io – Free, end-to-end, cloud-native development
#74What is this product about? I clicked "Learn more" and was greeted by a sweet, juicy corporate-speak ( https://www.openshift.io/end-to-end.html ): Digital transformation is about evolving into a technology business in order to compete in the digital economy. Businesses can’t transform without relying on the developer to implement the transformation strategy and deliver value. Mmm... tasty!
Re: Red Hat OpenShift.io – Free, end-to-end, cloud-native development
#75Earlier quoted context omitted.
> 2. Show photos, video, or screenshots. You'll literally be able to demo it yourself for free, on demand, in production (IF YOU DARE!), within the next few days.
There is video link in this blog post: https://developers.redhat.com/blog/2017/05/02/announcing-red...
Re: Red Hat OpenShift.io – Free, end-to-end, cloud-native development
#76Re: Red Hat OpenShift.io – Free, end-to-end, cloud-native development
#77I wonder if there's a name for this: that impatience and discomfort you feel about anything new until you understand what it is exactly and what to compare it to. Until that question is answered, you have ZERO patience for any marketing you read: especially fluffy visionary commentary about "digital transformation". You are quite literally making your readers angry because you are not answering their questions. For a…
- It is a PaaS, which would compete with Docker, EC2, and Heroku.
- It's development environment. Sublime?
- It's a collaboration tool. Github?
More to the point, it probably doesn't do any of those things in particular quite as well as those specific solutions do, but they're hoping you see the value in everything together. Would there be value in an IDE that had a deploy button that automatically marked a task as done?
I'm not sure that's exactly it, and I agree that this site isn't wonderfully done, but it's hard to get across "the thing" when there isn't a perfect comp to "the thing" already out there. Bad comparisons will pigeonhole your product forever.
Re: Red Hat OpenShift.io – Free, end-to-end, cloud-native development
#78So... it's like a poorly explained PaaS which is: - An IDE - A platform for running containers - A set of productivity and collaboration tools - CI service - Deployment tools ...all in one? Really? I'm scratching my head over this one. I really respect the work RedHat do, but there's this idea of picking one thing and doing it well... but heck, I mean, you can also just do everything as well, and hope one bit or anot…
Last I checked, OpenShift was comparable to Heroku.
From a naïve user experience perspective, OpenShift is probably a bit more like Heroku. Workflow does not (yet) have service brokers or add-ons that provide sidecars like a MySQL database or a Redis server. OpenShift provides those things in a manner more similar to Heroku's add-ons.
OpenShift also provides users with a point-and-click interface, but Deis Workflow expects you to use a command-line interface or bring your own dashboard (deisdash is a thing).
Deis Workflow depends on Kubernetes, and OpenShift =~(subsumes/supplants) Kubernetes in a marginally incompatible way, but to my knowledge Heroku has no relationship at all with Kubernetes. At least if it does, it's very opaque about it. (I couldn't tell you either way because it is opaque.)
Re: Red Hat OpenShift.io – Free, end-to-end, cloud-native development
#79Tried OpenShift last time and their cartridge model didn't make sense. What has changed since then?
My first instinct trying OpenShift v3 Developer Preview was to slap helm on it and see if I could deploy my Kubernetes projects. Turns out that Helm does not have much of a security model to speak of, and this was problematic to enabling support for Helm in OpenShift v3 where multi-tenancy was one of the concerns they wanted to address right away.
I got with claytonc in the #openshift-dev channel on freenode and he explained all of this to me, the long story short is that Helm on OpenShift is not well supported but that you can use it if you are willing to give it a service account with editor access to the whole cluster and make some other small changes like setting TILLER_NAMESPACE to something other than kube-system.
Instead, OpenShift basically uses the Kubernetes model with some additional primitives for deployments and builds. You define a BuildConfig (or let the point-and-click interface do it for you). Builds produce images, and images go into an ImageStream. A DeploymentConfig maps deployments to ImageStreams. [2]
The rest of the way down the stack, your deployment looks very similar to a regular Kubernetes deployment (except it's not using the Kubernetes deployment primitive, I believe that OpenShift implemented their own formal concept of Rolling Updates on DeploymentConfig before Kubernetes released the modern Deployment/ReplicaSet primitives that many k8s users are using for this now.) It is almost Kubernetes under the hood (but not quite, in subtly incompatible ways that depending on your size and current level of investment into Kubernetes, you might have an easy time or a hard time getting over.)
If you're looking for a short list of things that have changed from OpenShift v2 to v3, there isn't one because they are not really directly related products other than by name[3].
[1]: https://access.redhat.com/documentation/en-us/openshift_ente...
[2]: https://docs.openshift.org/latest/dev_guide/deployments/how_...
[3]: http://stackoverflow.com/questions/32477650/openshift-v3-vs-...
Re: Red Hat OpenShift.io – Free, end-to-end, cloud-native development
#80Earlier quoted context omitted.
So if a company chooses openshift.io, then I'm not going to be able to use IntelliJ, NetBeans, emacs, vim, visual studio code, etc. That'll help attract talent.
I think you are jumping to conclusions here, OpenShift.io is committing to a git repository. I'm guessing you'll still be able to clone this repo locally and use your own tools.