refactor(scheduler): coreos scheduler implementation

Note an SSH wrapper is used to get around fleetctl ssh-agent requirement.  We will ultimately want to transition to an HTTP API for talking to fleet.  Until then, we should explore modifying fleetctl to remove the ssh-agent requirement for tunneling.

add cluster setup and teardown

announce to /deis/services/{container_name} with a sidekick container

 - add pull before start
 - add stop and remove in ExecStop
 - use hardcoded expose port 5000 for deis/slugrunner

parallelize scheduler tasks, add appropriate blocking

exclude scheduler from max-line-length

add sidekick container for logging, unit cleanup

add unit name regex, use it when templating units

add domain and options to SchedulerClient
fix destroy bug

update readme to reflect new scheduler workflow, with placeholders for not-yet-implemented features

first pass at systemd units for components

coreos contrib scripts, units and user-data helpers

Author: Gabriel Monroy

README.md

@@ -1,71 +1,138 @@
 # Deis
 
-Deis is a Django/Celery API server, Python CLI and set of [Chef cookbooks](https://github.com/opdemand/deis-cookbook) that combine to provide a Heroku-inspired application platform for public and private clouds.  Your PaaS. Your Rules.
+Deis is an open source PaaS that makes it easy to deploy, scale and manage Docker containers used to host applications and services. Deis builds upon Docker and CoreOS to provide a private PaaS that is lightweight and flexible.
 
 [![Build Status](https://travis-ci.org/opdemand/deis.png?branch=master)](https://travis-ci.org/opdemand/deis)
 [![Coverage Status](https://coveralls.io/repos/opdemand/deis/badge.png?branch=master)](https://coveralls.io/r/opdemand/deis?branch=master)
 
 ![Deis Graphic](https://s3-us-west-2.amazonaws.com/deis-images/deis-graphic.png)
 
-## What is Deis?
+# Installation
 
-Deis is an open source PaaS that makes it easy to deploy and scale LXC containers and Chef nodes used to host applications, databases, middleware and other services. Deis leverages Chef, Docker and Heroku Buildpacks to provide a private PaaS that is lightweight and flexible.
+Deis is a set of Docker containers that can be deployed anywhere including public cloud, private cloud, bare metal or your workstation.  You will need Docker and a CoreOS cluster to get started.
 
-Deis comes with out-of-the-box support for Ruby, Python, Node.js, Java, Clojure, Scala, Play, PHP, Perl, Dart and Go. However, Deis can deploy *anything* using Heroku Buildpacks, Docker images or Chef recipes.  Deis can be deployed on any system including every public cloud, private cloud or bare metal.
+## Run Deis
 
-## Why Deis?
+Build Deis and run the `deis/deis` Docker image.
 
-##### Deploy anything
+```
+make build
+make run
+```
 
-Deploy a wide range of languages and frameworks with a simple `git push` using [Heroku Buildpacks](https://devcenter.heroku.com/articles/buildpacks) or [Dockerfiles](http://docs.docker.io/en/latest/use/builder/). Use custom Chef layers to deploy databases, middleware and other add-on services.
+## Install the Deis Client
+Use `pip` to install the latest Deis Client, or download pre-compiled binares.
 
-##### Control everything
+```
+pip install deis
+```
 
-Choose your hosting provider configuration. Define a [formation](http://docs.deis.io/en/latest/gettingstarted/concepts) with your own proxy and runtime layers. Retain full root access to every node. Manage your platform with a private Deis controller.
+## Register a User
+Use the Deis Client to register a new user.
 
-##### Scale effortlessly
+```
+deis register http://localhost:8000
+```
 
-Scale nodes and containers with a single command.  Node provisioning, container balancing and proxy reconfiguration are completely automated.
+## Initalize a Cluster
 
-##### 100% Open Source
+Initalize a `dev` cluster with a list of CoreOS hosts and your CoreOS private key.
 
-Free, transparent and easily customized. Join the open-source PaaS and DevOps community by using Deis and complimentary projects like Docker, Chef and Heroku Buildpacks.
+```
+deis clusters:create dev deisapp.com --hosts=coreos-host1,coreos-host2,coreos-host3 --auth=~/.ssh/coreos
+```
 
-## Getting Started
+The `dev` cluster will be used as the default cluster for future `deis` commands.
 
-First read about Deis core [concepts](http://docs.deis.io/en/latest/gettingstarted/concepts/) so you can answer:
+# Usage
 
- * What is a [Formation](http://docs.deis.io/en/latest/gettingstarted/concepts/#formations) and how does it relate to an application?
- * What are [Layers and Nodes](http://docs.deis.io/en/latest/gettingstarted/concepts/#layers), and how do they work with Chef?
- * How does the [Build, Release, Run](http://docs.deis.io/en/latest/gettingstarted/concepts/#build-release-run) process work?
- * How do I connect an application to [backing services](http://docs.deis.io/en/latest/gettingstarted/concepts/#backing-services)?
+## Create an Application
+Create an application on the default `dev` cluster.
 
-Next, choose which cloud provider should host your Deis controller.
-Regardless of whether your controller is hosted with
-[Amazon EC2](http://docs.deis.io/en/latest/installation/ec2/),
-[Rackspace](http://docs.deis.io/en/latest/installation/rackspace/), or
-[DigitalOcean](http://docs.deis.io/en/latest/installation/digitalocean/),
-it can create and manage nodes on any of those cloud providers.
+```
+deis create
+```
 
-Proceed to the [Operations Guide](http://docs.deis.io/en/latest/operations/)
-documentation to start building your own private PaaS.
+Use `deis create --cluster=prod` to place the app on a different cluster.  Don't like our name-generator?  Use `deis create myappname`.
 
-## Credits
+## Push
+Push builds of your application from your local git repository or from a Docker Registry.  Each build creates a new release, which can be rolled back.
 
-Deis stands on the shoulders of leading open source technologies:
+#### From a Git Repository
+When you created the application, a git remote for Deis was added automatically.
 
-  * [Chef](http://www.opscode.com/)
-  * [Docker](http://www.docker.io/)
-  * [Django](https://www.djangoproject.com/)
-  * [Celery](http://www.celeryproject.org/)
-  * [Heroku Buildpacks](https://devcenter.heroku.com/articles/buildpacks)
-  * [Slugbuilder](https://github.com/flynn/slugbuilder) and [slugrunner](https://github.com/flynn/slugrunner)
+```
+git push deis master
+```
+This will use the Deis builder to package your application as a Docker Image and deploy it on your application's cluster.
+
+#### From a Docker Registry
+
+You can also push builds directly from the Docker Index or a private Docker registry.  First, build and push the Docker images as you normally do:
+
+```
+docker build -t gabrtv/example
+docker push gabrtv/example
+```
+
+Then use `deis push` to deploy.
+
+```
+deis push gabrtv/example
+```
+
+Use the fully qualfied image path to push from a private registry: `deis push registry.local:5000/gabrtv/example`
+
+## Configure
+Configure your application with environment variables.  Each config change also creates a new release.
+
+```
+deis config:set DATABASE_URL=postgres://
+```
+
+Coming soon: Use the integrated ETCD namespace for service discovery between applications on the same cluster.
+
+## Test
+Test your application by running commands inside an ephemeral Docker container.
+
+```
+deis run make test
+```
+
+To integrate with your CI system, check the return code.
+
+## Scale
+Scale containers horizontally with ease.
+
+```
+deis scale 8
+```
+
+To scale by process type, use `deis scale web=8 worker=2` .  Just make sure the process types can be run via `/start web`.
+
+## Publish
+Publish your application via each cluster's integrated router.
+
+```
+deis publish 8080/http
+deis domain myapp.example.com
+```
+
+Use `deis open` to pop into a browser pointed at your application.  Use `--sslCert=cert.pem --sslKey=key.pem` to secure the connection with SSL/TLS.
+
+## Debug
+Access to aggregated logs makes it easy to troubleshoot problems with your application.
+
+```
+deis logs
+```
+
+Use `deis run` to execute one-off commands and explore the deployed container.  Coming soon: `deis attach` to jump into a live container.
 
 ## License
 
-Copyright 2013, OpDemand LLC
+Copyright 2014, OpDemand LLC
 
 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>
 
 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.
-

builder/systemd/deis-builder.service

@@ -0,0 +1,12 @@
+[Unit]
+Description=deis-builder
+After=docker.service
+Requires=docker.service
+Requires=docker-tcp.socket
+
+[Service]
+ExecStart=/bin/bash -c '/usr/bin/docker start -a deis-builder || /usr/bin/docker run --name deis-builder -P -e HOST=10.1.42.1 -e ETCD=10.1.42.1:4001--privileged deis/builder'
+ExecStop=/usr/bin/docker stop deis-builder
+
+[Install]
+WantedBy=multi-user.target

cache/systemd/deis-cache.service

@@ -0,0 +1,12 @@
+[Unit]
+Description=deis-cache
+After=docker.service
+Requires=docker.service
+Requires=docker-tcp.socket
+
+[Service]
+ExecStart=/bin/bash -c '/usr/bin/docker start -a deis-cache || /usr/bin/docker run --name deis-cache -P -e HOST=10.1.42.1 -e ETCD=10.1.42.1:4001 deis/cache'
+ExecStop=/usr/bin/docker stop deis-cache
+
+[Install]
+WantedBy=multi-user.target

contrib/coreos/default-user-data.yml

@@ -0,0 +1,6 @@
+#cloud-config
+coreos:
+  etcd:
+      addr: 172.17.8.100:4001
+      peer-addr: 172.17.8.100:7001
+  units: []

contrib/coreos/gen-user-data.rb

@@ -0,0 +1,33 @@
+#!/usr/bin/ruby
+# encoding: utf-8
+
+# NOTE: proper serialization of yaml literal blocks seems to require ruby 2.0
+require 'yaml'
+
+def prepare_units
+  units = []
+  source_dirs = [
+    File.join('contrib/coreos/systemd'),
+    #File.join('controller/systemd'),
+    #File.join('cache/systemd'),
+    #File.join('database/systemd'),
+    #File.join('logger/systemd'),
+    #File.join('registry/systemd'),
+    #File.join('router/systemd'),
+  ]
+  source_dirs.each do |dir|
+    Dir.glob(File.join(dir, '*')) do |path|
+      name = File.basename(path)
+      unit = {'name' => name, 'command' => 'start',
+              'content' => IO.read(path)}
+      units.push(unit)
+    end
+  end
+  return units
+end
+
+# join generated/default user-data and write to stdout
+user_data = YAML.load_file('contrib/coreos/default-user-data.yml')
+user_data['coreos']['units'].concat(prepare_units())
+puts "#cloud-config\n"
+puts user_data.to_yaml

contrib/coreos/override-plugin.rb

@@ -0,0 +1,45 @@
+# -*- mode: ruby -*-
+# # vi: set ft=ruby :
+
+# <hack>
+
+# NOTE: This monkey-patching of the coreos guest plugin is a terrible
+# hack that needs to be removed once the upstream plugin works with the
+# new CoreOS images.
+
+require Vagrant.source_root.join("plugins/guests/coreos/cap/configure_networks.rb")
+
+module VagrantPlugins
+  module GuestCoreOS
+	module Cap
+	  class ConfigureNetworks
+		include Vagrant::Util
+
+		def self.configure_networks(machine, networks)
+		  machine.communicate.tap do |comm|
+			# Read network interface names
+			interfaces = []
+			comm.sudo("ifconfig | grep enp0 | cut -f1 -d:") do |_, result|
+			  interfaces = result.split("\n")
+			end
+
+			# Configure interfaces
+			# FIXME: fix matching of interfaces with IP adresses
+			networks.each do |network|
+			  comm.sudo("ifconfig #{interfaces[network[:interface].to_i]} #{network[:ip]} netmask #{network[:netmask]}")
+			end
+
+		  end
+		end
+	  end
+
+      class ChangeHostName
+        def self.change_host_name(machine, name)
+			# do nothing!
+        end
+      end
+    end
+  end
+end
+
+# </hack>

contrib/coreos/systemd/docker-tcp.socket

@@ -0,0 +1,10 @@
+[Unit]
+Description=Docker Socket for Remote API
+
+[Socket]
+ListenStream=4243
+Service=docker.service
+BindIPv6Only=both
+
+[Install]
+WantedBy=sockets.target

contrib/coreos/systemd/etcd.service

@@ -0,0 +1,10 @@
+[Unit]
+Description=etcd
+
+[Service]
+User=etcd
+PermissionsStartOnly=true
+Environment=ETCD_DATA_DIR=/var/lib/etcd ETCD_NAME=default
+ExecStart=/usr/bin/etcd
+Restart=always
+RestartSec=10s

contrib/coreos/systemd/fleet.service

@@ -0,0 +1,8 @@
+[Unit]
+Description=fleet
+
+[Service]
+ExecStart=/usr/bin/fleet
+
+[Install]
+WantedBy=multi-user.target

contrib/coreos/systemd/stop-reboot-manager.service

@@ -0,0 +1,10 @@
+[Unit]
+Description=stop update-engine-reboot-manager
+
+[Service]
+Type=oneshot
+ExecStart=/usr/bin/systemctl stop update-engine-reboot-manager.service
+ExecStartPost=/usr/bin/systemctl mask update-engine-reboot-manager.service
+
+[Install]
+WantedBy=multi-user.target