OpenShift Origin is a distribution of Kubernetes optimized for continuous application development and multi-tenant deployment. Origin adds developer and operations-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.
Features:
- Easily build applications with integrated service discovery, DNS, load balancing, failover, health checking, persistent storage, and fast scaling
- Push source code to your Git repository and automatically roll out containerized applications (micro or macro)
- Easy to use client and web console for building and monitoring applications
- Centralized administration and management of an entire stack, team, or organization
- Templatize the components of your system, reuse them, and iteratively deploy them over time
- 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-tenant system
- Allow developers to run containers securely with fine-grained controls in production
- Limit, track, and manage the developers and teams on the platform
- Integrated Docker registry, automatic edge load balancing, cluster logging, and integrated metrics
Learn More:
- 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
- API Documentation
For questions or feedback, reach us on IRC on #openshift-dev on Freenode or post to our mailing list.
If you have downloaded the client tools, place the included binaries in your PATH.
- For a quick install of Origin, see the Getting Started Install guide.
- For an advanced installation using Ansible, follow the Advanced Installation guide
- To build and run from source, see CONTRIBUTING.adoc
We highly recommend trying out the Origin walkthrough which covers the core concepts in Origin. The walkthrough is accompanied by a blog series on blog.openshift.com that goes into more detail. It's a great place to start.
The Origin API is located on each server at https://<host>:8443/oapi/v1. These APIs are described via Swagger v1.2 at https://<host>:8443/swaggerapi/oapi/v1. For more, see the API documentation.
If you're looking for more information about using Kubernetes or the lower level concepts that Origin depends on, see the following:
If you run into difficulties running Origin, start by reading through the troubleshooting guide.
-
How does Origin relate to Kubernetes?
Origin is a distribution of Kubernetes optimized for enterprise application development and deployment, used by OpenShift 3 and Atomic Enterprise. Origin embeds Kubernetes and adds additional functionality to offer a simple, powerful, and easy-to-approach developer and operator experience for building applications in containers. Our goal is to do most of that work upstream, with integration and final packaging occurring in Origin.
You can run the core Kubernetes server components with
openshift start kube, usekubectlviaopenshift kube, and the Origin release zips include versions ofkubectl,kubelet,kube-apiserver, and other core components. You can see the version of Kubernetes included with Origin viaopenshift version. -
How does Atomic Enterprise relate to Origin and OpenShift?
Two products are built from Origin, Atomic Enterprise and OpenShift. Atomic Enterprise adds operational centric tools to enable easy deployment and scaling and long-term lifecycle maintenance for small and large teams and applications. OpenShift provides a number of developer-focused tools on top of Atomic Enterprise such as image building, management, and enhanced deployment flows.
-
What can I run on Origin?
Origin 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 Origin 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:
-
Why doesn't my Docker image run on OpenShift?
Security! Origin runs with the following security policy by default:
- Containers run as a non-root unique user that is separate from other system users
- They cannot access host resources, run privileged, or become root
- They are given CPU and memory limits defined by the system administrator
- Any persistent storage they access will be under a unique SELinux label, which prevents others from seeing their content
- These settings are per project, so containers in different projects cannot see each other by default
- Regular users can run Docker, source, and custom builds
- By default, Docker builds can (and often do) run as root. You can control who can create Docker builds through the
builds/dockerandbuilds/custompolicy resource.
- By default, Docker builds can (and often do) run as root. You can control who can create Docker builds through the
- Regular users and project admins cannot change their security quotas.
Many Docker containers expect to run as root (and therefore edit all the contents of the filesystem). The Image Author's guide gives recommendations on making your image more secure by default:
- Don't run as root
- Make directories you want to write to group-writable and owned by group id 0
- Set the net-bind capability on your executables if they need to bind to ports <1024
Otherwise, you can see the security documentation for descriptions on how to relax these restrictions.
- Containers run as a non-root unique user that is separate from other system users
-
How do I get networking working?
The Origin and Kubernetes network model assigns each pod (group of containers) an IP that is expected to be reachable from all nodes in the cluster. The default setup is through a simple SDN plugin with OVS - this plugin expects the port 4679 to be open between nodes in the cluster. Also, the Origin master processes need to be able to reach pods via the network, so they may require the SDN plugin.
Other networking options are available such as Calico, Flannel, Nuage, and Weave. For a non-overlay networking solution, existing networks can be used by assigning a different subnet to each host, and ensuring routing rules deliver packets bound for that subnet to the host it belongs to. This is called host subnet routing.
-
Why can't I run Origin in a Docker image on boot2docker or Ubuntu?
Versions of Docker distributed by the Docker team don't allow containers to mount volumes on the host and write to them (mount propagation is private). Kubernetes manages volumes and uses them to expose secrets into containers, which Origin uses to give containers the tokens they need to access the API and run deployments and builds. Until mount propagation is configurable in Docker you must use Docker on Fedora, CentOS, or RHEL (which have a patch to allow mount propagation) or run Origin outside of a container. Tracked in this issue.
You can develop locally on your host or with a virtual machine, or if you want to just try out Origin 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 - Origin 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 Origin 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 command-line integration test suite
$ 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 Origin 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.
Origin is licensed under the Apache License, Version 2.0.