Name: atomic-enterprise
Owner: Project Atomic
Description: Atomic Enterprise - deploy and manage your containers with Docker and Kubernetes
Created: 2015-05-28 14:54:00.0
Updated: 2018-04-26 08:44:04.0
Pushed: 2015-07-17 07:20:15.0
Homepage: http://www.projectatomic.io/
Size: 112588
Language: Go
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
This is the source repository for Atomic Enterprise, based on top of Docker containers and the Kubernetes container cluster manager. Atomic Enterprise adds operational centric tools on top of Kubernetes to enable easy deployment and scaling and long-term lifecycle maintenance for small and large teams and applications.
Features:
You should be aware of the inherent security risks associated with performing docker build operations on arbitrary images as they have effective root access. Only build and run code you trust.
For more information on the security of containers, see these articles:
Consider using images from trusted parties, building them yourself, or only running containers that run as non-root users.
Take a look at the Quick Start Tutorial or give Atomic Enterprise a shot with a docker container (Atomic Enterprise requires Docker 1.6 or higher or 1.6.2 on CentOS/RHEL):
$ 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? Atomic Enterprise 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 Atomic Enterprise 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 Atomic Enterprise 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
# See everything you just created!
$ oc status
Any username and password are accepted by default (with no credential system configured).
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 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/atomic-enterprise can then be removed.
We highly recommend trying out the Atomic Enterprise Walkthrough, which shows some of the lower level pieces of of Atomic Enterprise that will be the foundation for user applications.
If you run into difficulties running Atomic Enterprise, start by reading through the troubleshooting guide.
The Atomic Enterprise 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/...
How does Atomic Enterprise relate to Kubernetes?
Atomic Enterprise embeds Kubernetes and adds additional functionality to offer a simple, powerful, and easy-to-approach operator experience for deploying and scaling applications in containers. Kubernetes today is focused around composing containerized applications - Atomic Enterprise adds managing images and integrating them into deployment flows. Our goal is to do most of that work upstream, with integration and final packaging occurring in Atomic Enterprise.
How does Atomic Enterprise relate to Openshift
OpenShift provides a number of developer-focused tools on top of
Atomic Enterprise such as Source-To-Image, a tool to automatically rebuild
Docker images from git push.
What can I run on Atomic Enterprise?
Atomic Enterprise is designed to run any existing Docker images, including ones built via OpenShift.
You can develop locally on your host or with a virtual machine, or if you want to just try out Atomic Enterprise 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 - Atomic Enterprise 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 or get involved in the Kubernetes project at the container runtime layer.
See HACKING.md for more details on developing on Atomic Enterprise 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 atomic-enterprise directory run:
n the unit tests
ke check
n a simple server integration test
ck/test-cmd.sh
n the integration server test suite
ck/test-integration.sh
n the end-to-end test suite
ck/test-end-to-end.sh
n all of the tests above
ke 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:
ck/install-etcd.sh
Some of the components of Atomic Enterprise run as Docker images, including the builders and deployment tools in images/builder/docker/* and 'images/deploy/*`. To build them locally run
ck/build-images.sh
Atomic Enterprise is licensed under the Apache License, Version 2.0.