This is the source repository for OpenShift 3, based on top of Docker containers and the Kubernetes container cluster manager. OpenShift adds developer and operational centric tools on top of Kubernetes to enable rapid application development, easy deployment and scaling, and long-term lifecycle maintenance for small and large teams and applications.
Features:
- Build web-scale applications with integrated service discovery, DNS, load balancing, failover, health checking, persistent storage, and fast scaling
- Push source code to your Git repository and have image builds and deployments automatically occur
- Easy to use client tools for building web applications from source code
- Templatize the components of your system, reuse them, and iteratively deploy them over time
- Centralized administration and management of application component libraries
- Roll out changes to software stacks to your entire organization in a controlled fashion
- Team and user isolation of containers, builds, and network communication in an easy multi-tenancy system
- Allow developers to run containers securely by preventing root access and isolating containers with SELinux
- Limit, track, and manage the resources teams are using
Learn More:
- OpenShift Public Documentation
- The Trello Roadmap covers the epics and stories being worked on (click through to individual items)
- Technical Architecture Presentation
- System Architecture design document
For questions or feedback, reach us on IRC on #openshift-dev on Freenode or post to our mailing list.
NOTE: OpenShift Origin 1.0 has been released releases page. Feedback, suggestions, and testing are all welcome!
OpenShift is a system that runs Docker containers on your machine. In some cases (build operations) it does so using privileged containers. Those containers access your host's Docker daemon and perform docker build and docker push operations. As such, you should be aware of the inherent security risks associated with performing docker build operations on arbitrary images as they have effective root access. This is particularly relevant when running the OpenShift as a node directly on your laptop or primary workstation. Only build and run code you trust.
For more information on the security of containers, see these articles:
- http://opensource.com/business/14/7/docker-security-selinux
- https://docs.docker.com/articles/security/
Consider using images from trusted parties, building them yourself on OpenShift, or only running containers that run as non-root users.
The easiest way to run OpenShift Origin is in a Docker container (OpenShift requires Docker 1.6 or higher or 1.6.2 on CentOS/RHEL):
Important!: Docker 1.7 changed mount propagation to PRIVATE, which breaks running OpenShift inside a container. If you are on Docker 1.7 you will need to use the Vagrant or binary installation paths.
$ sudo docker run -d --name "origin" \
--privileged --net=host \
-v /:/rootfs:ro -v /var/run:/var/run:rw -v /sys:/sys:ro -v /var/lib/docker:/var/lib/docker:rw \
-v /var/lib/openshift/openshift.local.volumes:/var/lib/openshift/openshift.local.volumes \
openshift/origin start
Security! Why do we need to mount your host, run privileged, and get access to your Docker directory? OpenShift runs as a host agent (like Docker) and starts and stops Docker containers, mounts remote volumes, and monitors the system (/sys) to report performance and health info. You can strip all of these options off and OpenShift will still start, but you won't be able to run pods (which is kind of the point).
Once the container is started, you can jump into a console inside the container and run the CLI.
$ sudo docker exec -it origin bash
# Start the OpenShift integrated registry in a container
$ oadm registry --credentials=./openshift.local.config/master/openshift-registry.kubeconfig
# Use the CLI to login, create a project, and then create your app.
$ oc --help
$ oc login
Username: test
Password: test
$ oc new-project test
$ oc new-app -f https://raw.githubusercontent.com/openshift/origin/master/examples/sample-app/application-template-stibuild.json
# See everything you just created!
$ oc status
Any username and password are accepted by default (with no credential system configured). You can view the webconsole at https://localhost:8443/console in your browser - login with the same credentials you used above and you'll see the application you just created.
You can also use the Docker container to run our CLI (sudo docker exec -it origin cli --help) or download the oc command-line client from the releases page for Mac, Windows, or Linux and login from your host with oc login.
You can reset your server by stopping the origin container and then removing it via Docker. The contents of /var/lib/openshift can then be removed. See the public docs for more about running a permanent installation of OpenShift.
We highly recommend trying out the OpenShift walkthrough, which shows some of the lower level pieces of of OpenShift that will be the foundation for user applications. The walkthrough is accompanied by a blog series on blog.openshift.com that goes into more detail. It's a great place to start, albeit at a lower level than OpenShift 2.
Both OpenShift and Kubernetes have a strong focus on documentation - see the following for more information about them:
If you run into difficulties running OpenShift, start by reading through the troubleshooting guide.
The OpenShift APIs are exposed at https://localhost:8443/oapi/v1/*.
To experiment with the API, you can get a token to act as a user:
$ sudo docker exec -it openshift-origin bash
$ oc login
Username: test
Password: test
$ oc whoami -t
<prints a token>
$ exit
# from your host
$ curl -H "Authorization: bearer <token>" https://localhost:8443/oapi/v1/...
The API documentation can be found here.
-
How does OpenShift relate to Kubernetes?
OpenShift embeds Kubernetes and adds additional functionality to offer a simple, powerful, and easy-to-approach developer and operator experience for building applications in containers. Kubernetes today is focused around composing containerized applications - OpenShift adds building images, managing them, and integrating them into deployment flows. Our goal is to do most of that work upstream, with integration and final packaging occurring in OpenShift. As we iterate through the next few months, you'll see this repository focus more on integration and plugins, with more and more features becoming part of Kubernetes.
-
What can I run on OpenShift?
OpenShift is designed to run any existing Docker images. In addition you can define builds that will produce new Docker images from a Dockerfile. However the real magic of OpenShift can be seen when using Source-To-Image builds which allow you to simply supply an application source repository which will be combined with an existing Source-To-Image enabled Docker image to produce a new runnable image that runs your application. We are continuing to grow the ecosystem of Source-To-Image enabled images and documenting them here. Our available images are:
Your application image can be easily extended with a database service with our database images. Our available database images are:
You can develop locally on your host or with a virtual machine, or if you want to just try out OpenShift download the latest Linux server, or Windows and Mac OS X client pre-built binaries.
First, get up and running with the Contributing Guide.
All contributions are welcome - OpenShift uses the Apache 2 license and does not require any contributor agreement to submit patches. Please open issues for any bugs or problems you encounter, ask questions on the OpenShift IRC channel (#openshift-dev on freenode), or get involved in the Kubernetes project at the container runtime layer.
See HACKING.md for more details on developing on OpenShift including how different tests are setup.
If you want to run the test suite, make sure you have your environment set up, and from the origin directory run:
# run the unit tests
$ make check
# run a simple server integration test
$ hack/test-cmd.sh
# run the integration server test suite
$ hack/test-integration.sh
# run the end-to-end test suite
$ hack/test-end-to-end.sh
# run all of the tests above
$ make test
You'll need etcd installed and on your path for the integration and end-to-end tests to run, and Docker must be installed to run the end-to-end tests. To install etcd you should be able to run:
$ hack/install-etcd.sh
Some of the components of OpenShift run as Docker images, including the builders and deployment tools in images/builder/docker/* and 'images/deploy/*`. To build them locally run
$ hack/build-images.sh
To hack on the web console, check out the assets/README.md file for instructions on testing the console and building your changes.
OpenShift is licensed under the Apache License, Version 2.0.