Red Hat OpenShift.io – Free, end-to-end, cloud-native development

Re:Red Hat OpenShift.io – Free, end-to-end, cloud-native dev... by cwt137 on Tuesday May 02, 2017 @10:02AM (#14246358)

OpenShift has existed for a while. There are basically two versions; the original version was like a Heroku competitor. Then about 2 or so years ago, they came out with a new version based on Docker and Kubernetes called OpenShift Origin (OpenShift 3). I bet this is some type of OpenShift 3 offering, but it would be nice to know how it differs from their current offerings.

[ Parent | on HN ]

Re:Red Hat OpenShift.io – Free, end-to-end, cloud-native dev... by sbose78 on Tuesday May 02, 2017 @10:37AM (#14246665)

Disclosure: I work on openshift.io

Openshift.io is the end-to-end development environment which is built over the OpenShift PaaS.

[ Parent | on HN ]

Re:Red Hat OpenShift.io – Free, end-to-end, cloud-native dev... by lldata on Tuesday May 02, 2017 @11:18AM (#14247058)

Sorry, but you are doing a terrible job of explaining what OpenShift is to outsiders.

OpenShift is a Platform-as-a-Service offering from RedHat. It provides a fully integrated solution to building and deploying applications on Docker and Kubernetes. What makes it a PaaS is that it integrates Jenkins, so you can build images from source and promote them though environments. https://www.openshift.com/

OpenShift is a private cloud offering, so it is something you install and run yourself on your own infrastructure or in a public cloud.

So OpenShift.io is the "battery-included" version that is already installed on a public cloud, managed by RedHat?

[ Parent | on HN ]

Re:Red Hat OpenShift.io – Free, end-to-end, cloud-native dev... by yebyen on Tuesday May 02, 2017 @03:04PM (#14249533)

> What makes it a PaaS is that it integrates Jenkins

Not just Jenkins. There is a Jenkins button and you can use Jenkins for CI/CD, but you can define BuildConfig and ImageStream through their point-and-click interface without ever adding Jenkins or writing a line of config by hand.

You just need to use one of their built-in ImageStreams and DeploymentConfigs. I got my first exposure to OpenShift through the Developer Preview/OpenShift Console beta. At the time I was testing it out, deployment of Jenkins was outright broken, but I was able to get my app working and builds automatically generated in response to GitHub webhooks (eg, CD without Jenkins.)

The Developer Preview was a very interesting experience, and their support people were quite responsive in #openshift-dev, but I'm giving them some latitude in that it was clearly labeled as Preview / Beta and a totally free product with built-in expiration date.

I would not have been likely to call it a good experience except that it was clearly labeled beta. But if it says Beta on the tin, and I am able to complain until it works, that's about where I set the bar for good experience. It was a good beta experience.

If I had to guess, OpenShift.io is the next phase of this:

https://console.preview.openshift.com/console/

(I am certain that you will not need to use OpenShift.io online IDE to get "batteries included" OpenShift from RedHat.)

[ Parent | on HN ]

Re:Red Hat OpenShift.io – Free, end-to-end, cloud-native dev... by sbose78 on Tuesday May 02, 2017 @12:06PM (#14247578)

Ok so this is "OpenShift.IO" :) And not just openshift

This is openshift + planner + code editor + pipelines + 'analytics'.

Here analytics does code quality checks and lets you, the developer know, if they should be using a different Jar/package ( example: the one used by the developer might have a security vulnerability reported which the developer was unaware of )

[ Parent | on HN ]

Re:Red Hat OpenShift.io – Free, end-to-end, cloud-native dev... by imron on Tuesday May 02, 2017 @12:25PM (#14247784)

They should have paid you to write copy for their website.

[ Parent | on HN ]