github.com/adelq/deis@v0.13.2-0.20141021145840-f05550607c59/README.md (about) 1 # Deis 2 3 Deis (pronounced DAY-iss) is an open source PaaS that makes it easy to deploy and manage applications on your own servers. Deis builds upon [Docker](http://docker.io/) and [CoreOS](http://coreos.com) to provide a lightweight PaaS with a [Heroku-inspired](http://heroku.com) workflow. 4 5 [![Build Status](http://ci.deis.io/buildStatus/icon?job=test-master)](http://ci.deis.io/job/test-master/) 6 [![Current Release](http://img.shields.io/badge/release-v0.13.1-blue.svg)](https://github.com/deis/deis/releases/tag/v0.13.1) 7 8 ![Deis Graphic](https://s3-us-west-2.amazonaws.com/deis-images/deis-graphic.png) 9 10 Deis is pre-release software. The current release is [v0.13.1](https://github.com/deis/deis/tree/v0.13.1). Until there is a stable release, we recommend you check out the latest ["master" branch](https://github.com/deis/deis) code and refer to the [latest documentation](http://docs.deis.io/en/latest/). Upgrading from a previous Deis release? See [Upgrading Deis](http://docs.deis.io/en/latest/installing_deis/upgrading-deis/) for additional information. 11 12 # Deploying Deis 13 14 Deis is a set of Docker containers that can be deployed anywhere including public cloud, private cloud, bare metal or your workstation. Decide where you'd like to deploy Deis, then follow the deployment-specific documentation for [Rackspace](contrib/rackspace/README.md), [EC2](contrib/ec2/README.md), [DigitalOcean](contrib/digitalocean/README.md), [Google Compute Engine](contrib/gce/README.md) or [bare-metal](contrib/bare-metal/README.md) provisioning. Want to see a particular platform supported? Please open an [issue](https://github.com/deis/deis/issues/new). 15 16 Trying out Deis? Continue following these instructions for a local installation using Vagrant. 17 18 ## Install prerequisites 19 20 * Due to its nature as a distributed system, we strongly recommend using Deis with a minimum of 3 nodes even for local development and testing 21 * The Deis "control plane" containers will consume approximately 2 GB of RAM across the cluster. Please be sure you have sufficient free memory before proceeding. 22 * Install [Vagrant v1.6.5+](http://www.vagrantup.com/downloads.html) and [VirtualBox](https://www.virtualbox.org/wiki/Downloads) 23 24 Note for Ubuntu users: the VirtualBox package in Ubuntu (as of the last known release for 14.04) has some issues when running in RAM-constrained environments. Please install the latest version of VirtualBox from Oracle's website. 25 26 ## Configure Discovery 27 28 Each time you spin up a new CoreOS cluster, you **must** provide a new [discovery service URL](https://coreos.com/docs/cluster-management/setup/cluster-discovery/) in the [CoreOS user-data](https://coreos.com/docs/cluster-management/setup/cloudinit-cloud-config/) file. This URL allows hosts to find each other and perform leader election. 29 30 Automatically generate a fresh discovery URL with: 31 32 ```console 33 $ make discovery-url 34 ``` 35 36 or manually edit [contrib/coreos/user-data](contrib/coreos/user-data) and add a unique discovery URL generated from <https://discovery.etcd.io/new>. 37 38 ## Boot CoreOS 39 40 Start the CoreOS cluster on VirtualBox. From a command prompt, `cd` to the root of the Deis project code and type: 41 42 ```console 43 $ export DEIS_NUM_INSTANCES=3 44 $ vagrant up 45 ``` 46 47 This instructs Vagrant to spin up 3 VMs. To be able to connect to the VMs, you must add your Vagrant-generated SSH key to the ssh-agent (`deisctl` requires the agent to have this key): 48 49 ```console 50 $ ssh-add ~/.vagrant.d/insecure_private_key 51 ``` 52 53 ## Provision Deis 54 55 Install the [deisctl utility](deisctl#installation) used to provision and operate Deis. 56 57 ```console 58 $ curl -sSL http://deis.io/deisctl/install.sh | sh 59 ``` 60 61 Export `DEISCTL_TUNNEL` so you can connect to one of the VMs using the `deisctl` client on your workstation. 62 63 ```console 64 $ export DEISCTL_TUNNEL=172.17.8.100 65 ``` 66 67 Use `deisctl install platform` to install all Deis components across the cluster, then `deisctl start platform` to start them. 68 69 ```console 70 $ deisctl install platform 71 $ deisctl start platform 72 ``` 73 74 This can take some time - the **builder** must download and install the beefy Heroku cedar stack. Grab some more coffee! 75 76 Your Deis platform should be accessible at `deis.local3.deisapp.com`. For clusters on other platforms see our guide to [Configuring DNS](http://docs.deis.io/en/latest/installing_deis/configure-dns/). 77 78 ## Configure Deis 79 80 Now that Deis is running there are a few administrative settings we need to provide. 81 82 Set the default domain used to anchor your applications. For a Vagrant environment, use `local3.deisapp.com` as it will resolve to your local routers: 83 84 ```console 85 $ deisctl config platform set domain=local3.deisapp.com 86 ``` 87 88 If you want to allow `deis run` for one-off admin commands, you must provide an SSH private key that allows Deis to gather container logs on CoreOS hosts: 89 90 ```console 91 $ deisctl config platform set sshPrivateKey=~/.vagrant.d/insecure_private_key 92 ``` 93 94 ## Install the Deis Client 95 96 If you're using the latest Deis release, use `pip install --upgrade deis` to install the latest [Deis Client](https://pypi.python.org/pypi/deis/) or download [pre-compiled binaries](https://github.com/deis/deis/tree/master/client#get-started). 97 98 If you're working off master, precompiled binaries are likely out of date. You should either symlink the python file directly or build a local copy of the client: 99 100 ```console 101 $ sudo ln -fs $(pwd)/client/deis.py /usr/local/bin/deis 102 ``` 103 or 104 ```console 105 $ cd client && python setup.py install 106 ``` 107 108 ## Register a User 109 110 Use the Deis Client to register a new user. 111 112 ```console 113 $ deis register http://deis.local3.deisapp.com 114 $ deis keys:add 115 ``` 116 117 Use `deis keys:add` to add your SSH public key for `git push` access -- normally `$HOME/.ssh/id_rsa.pub`. 118 119 # Usage 120 121 Deis supports 3 deployment workflows: 122 123 * Heroku Buildpacks via `git push` -- Learn more about [Using Buildpacks](http://docs.deis.io/en/latest/using_deis/using-buildpacks/) 124 * Dockerfiles via `git push` -- Learn more about [Using Dockerfiles](http://docs.deis.io/en/latest/using_deis/using-dockerfiles/) 125 * Docker Images via `deis pull` -- Learn more about [Using Docker Images](http://docs.deis.io/en/latest/using_deis/using-docker-images/) 126 127 As an example, we will walk through deploying a Ruby application using the Heroku Buildpack workflow. 128 129 ## Prepare an Application 130 Clone an example Ruby application: 131 132 ```console 133 $ git clone https://github.com/deis/example-ruby-sinatra.git 134 $ cd example-ruby-sinatra 135 ``` 136 137 ## Create an Application 138 From within the application directory, create an application on Deis: 139 140 ```console 141 $ cd example-ruby-sinatra 142 $ deis create 143 ``` 144 145 Use `deis create --cluster=prod` to place the app on a different cluster. Don't like our name-generator? Use `deis create myappname`. 146 147 ## Deploy 148 When you created the application, a git remote for Deis was added automatically. Deploy with `git push`. 149 150 ```console 151 $ git push deis master 152 ``` 153 This will use the Deis builder to package your application as a Docker Image and automatically deploy it to the platform. 154 Each build creates a new release, which can be rolled back. 155 156 ## Configure 157 Configure your application with environment variables. Each config change also creates a new release. 158 159 ```console 160 $ deis config:set DATABASE_URL=postgres:// 161 ``` 162 163 ## Test 164 Test the application by running your test suite inside an ephemeral Docker container. 165 166 ```console 167 $ deis run make test 168 ``` 169 170 Use the return code to integrate with a CI system. 171 172 ## Scale 173 Scale containers horizontally with ease. 174 175 ```console 176 $ deis scale web=8 177 ``` 178 179 ## Debug 180 Access to aggregated logs makes it easy to troubleshoot problems with your application. 181 182 ```console 183 $ deis logs 184 ``` 185 186 Use `deis run` to execute one-off commands and explore the deployed container. 187 188 ## Testing the cluster 189 190 Integration tests and corresponding documentation can be found under the [`tests/`](tests/) folder. 191 192 ## Hacking on Deis 193 194 Learn how to [hack on Deis](http://docs.deis.io/en/latest/contributing/hacking/) with a Docker-based development workflow. 195 196 ## Troubleshooting 197 198 Common issues that users have run into when provisioning Deis are detailed below. 199 200 #### When running a `deisctl` command - 'Failed initializing SSH client: ssh: handshake failed: ssh: unable to authenticate' 201 Did you remember to add your SSH key to the ssh-agent? `ssh-add -L` should list the key you used to provision the servers. If it's not there, `ssh-add -K /path/to/your/key`. 202 203 #### When running a `deisctl` command - 'All the given peers are not reachable (Tried to connect to each peer twice and failed)' 204 The most common cause of this issue is that a [new discovery URL](https://discovery.etcd.io/new) wasn't generated and updated in [contrib/coreos/user-data](contrib/coreos/user-data) before the cluster was launched. Each Deis cluster must have a unique discovery URL, else there will be entries for old hosts that etcd will try and fail to connect to. Try destroying and relaunching the cluster with a fresh discovery URL. 205 206 #### Scaling an app doesn't work, and/or the app shows 'Welcome to nginx!' 207 This usually means the controller failed to submit jobs to the scheduler. `deisctl journal controller` will show detailed error information, but the most common cause of this is that the cluster was created with the wrong SSH key for the `--auth` parameter. The key supplied with the `--auth` parameter must be the same key that was used to provision the Deis servers. If you suspect this to be the issue, you'll need to `clusters:destroy` the cluster and recreate it, along with the app. 208 209 #### A Deis component fails to start 210 Use `deisctl status <component>` to view the status of the component. You can also use `deisctl journal <component>` to tail logs for a component, or `deisctl list` to list all components. 211 212 The most common cause of services failing to start are sporadic issues with Docker Hub. We are exploring workarounds and are working with the Docker team to improve Docker Hub reliability. In the meantime, try starting the service again with `deisctl restart <component>`. 213 214 ### Any other issues 215 Running into something not detailed here? Please [open an issue](https://github.com/deis/deis/issues/new) or hop into [#deis](https://botbot.me/freenode/deis/) and we'll help! 216 217 ## License 218 219 Copyright 2014, OpDemand LLC 220 221 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at <http://www.apache.org/licenses/LICENSE-2.0> 222 223 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.