[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-305) What are the different types of OpenShift servers when creating new connections?

[ https://issues.jboss.org/browse/TOOLSDOC-305?page=com.atlassian.jira.plug... ] Andre Dietisheim edited comment on TOOLSDOC-305 at 4/12/13 5:27 AM: -------------------------------------------------------------------- @Michelle: * *OpenShift Origin* is the PaaS "application"/"platform" we're developing at Red Hat. This is just the software as we develop it. To get this up and running you'd need a hosting: * Packaged and certified we call this *OpenShift Enterprise*. A customer gets a subscription for it and hosts it in his own data center (private cloud). * We also offer a *live-CD* (https://www.openshift.com/wiki/getting-started-with-openshift-origin-live...) that you may run on your machine, most likely for development purposes * We host Origin on http://openshift.redhat.com and offer it to whoever wants to try/use it. We call this *OpenShift* (public cloud). * Internally we also have *staging and internal environments* that we use to test our code before it goes productive on openshift.redhat.com * etc. was (Author: adietish): @Michelle: * *OpenShift Origin* is the PaaS "application"/"platform" we're developing at Red Hat. This is just the software as we develop it. To get this up and running you'd need a hosting: * Packaged and certified we call this *OpenShift Enterprise*. A customer gets a subscription for it and hosts it in his own data center (private cloud). * We also offer a [live-CD^https://www.openshift.com/wiki/getting-started-with-openshift-ori...] that you may run on your machine, most likely for development purposes * We host Origin on http://openshift.redhat.com and offer it to whoever wants to try/use it. We call this *OpenShift* (public cloud). * Internally we also have *staging and internal environments* that we use to test our code before it goes productive on openshift.redhat.com * etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira