openshift-origin

The goal is to be able take a Docker image on my laptop and push it to the OpenShift Origin image registry (started by oc cluster up ) to do local development. It's not clear if I'm doing something wrong or there's a bug in Docker or OpenShift Origin. For those unfamiliar with OpenShift Origin: https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md Any illuminating information would be appreciated. Here's what I've tried so far: # oc cluster up Starting OpenShift using openshift/origin:v3.6.0 ... OpenShift server started. The server is accessible via web console at: https:/

I'm searching for a main difference between OpenShift V3 and V2. Is OpenShift V2 working like this?: https://www.openshift.com/walkthrough/how-it-works And how are Docker and Kubernetes working in V3? Can someone give me a clear explanation about the build-up of OpenShift V2 and V3 This is a rather broadly asked question, so I will (and can) answer only in a rather broad manner. There are a lot of key concepts that have changed. These are the most important ones and you'll need some time to get into it, but they are a big improvement to OpenShift v2.: Cartridges vs. Docker Containers Gears vs.

In a default openshift install, there is an unused project titled kube-system . It seems like openshift-infra is for things like metrics, default is for the router and registry, and openshift is for global templates. What is the kube-system project used for though? I can't find any docs on it. kube-system is the namespace for objects created by the Kubernetes system. Typically, this would contain pods like kube-dns , kube-proxy , kubernetes-dashboard and stuff like fluentd, heapster, ingresses and so on. kube-system contains service accounts which are used to run the kubernetes controllers.

I installed a cartridge with "oo-admin-cartridge -a install -s /path/to/cartridge". It shows up in "oo-admin-cartridge -a list", however it doesn't show up in "rhc cartridges". This is on release 4 of the Origin VM. On release 3, I don't have any problems installing additional cartridges. I know similar questions have been asked before, like Deploying Custom Cartridges on Openshift Origin , but none of my attempts at clearing the cache seem to help. I've tried: oo-admin-broker-cache --console --clear cd /var/www/openshift/broker && scl enable ruby193 "bundle exec rake tmp:clear" rm -rf /var

I created a VM with OpenShift Origin in CentOS 6.5 which followed the oo-installer guide. However, when I follow the Install JBoss EAP and JBoss EWS Support to install JBoss EAP cartridge, I got dependency error which requires several dependencies, like jbossas-domain, maven3... as following... How can I fix this? Thanks. yum install openshift-origin-cartridge-jbosseap.noarch openshif t-origin-cartridge-jbossews.noarch openshift-origin-cartridge-jenkins.noarch ope nshift-origin-cartridge-jenkins-client.noarch Loaded plugins: fastestmirror, priorities, versionlock Repository 'jenkins-repo' is

While working on creating a platform that will do microservice deployments using Kubernetes, we want to take a Dependency on the Kubernetes Deployment Object. However, we saw the documentation http://kubernetes.io/v1.1/docs/user-guide/deployments.html says the following "Note that Deployment objects effectively have API version v1alpha1. Alpha objects may change or even be discontinued in future software releases" I am wondering if we should go about using the Deployment concept to do our deployments, essentially rolling updates or since it could be discontinued or change, should we just