{"action":"opened","issue":{"url":"https://api.github.com/repos/flynn/flynn/issues/2707","repository_url":"https://api.github.com/repos/flynn/flynn","labels_url":"https://api.github.com/repos/flynn/flynn/issues/2707/labels{/name}","comments_url":"https://api.github.com/repos/flynn/flynn/issues/2707/comments","events_url":"https://api.github.com/repos/flynn/flynn/issues/2707/events","html_url":"https://github.com/flynn/flynn/issues/2707","id":149006425,"number":2707,"title":"Better workflow for multi-host deployments","user":{"login":"jojobo","id":18481225,"avatar_url":"https://avatars.githubusercontent.com/u/18481225?v=3","gravatar_id":"","url":"https://api.github.com/users/jojobo","html_url":"https://github.com/jojobo","followers_url":"https://api.github.com/users/jojobo/followers","following_url":"https://api.github.com/users/jojobo/following{/other_user}","gists_url":"https://api.github.com/users/jojobo/gists{/gist_id}","starred_url":"https://api.github.com/users/jojobo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jojobo/subscriptions","organizations_url":"https://api.github.com/users/jojobo/orgs","repos_url":"https://api.github.com/users/jojobo/repos","events_url":"https://api.github.com/users/jojobo/events{/privacy}","received_events_url":"https://api.github.com/users/jojobo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-17T23:38:32Z","updated_at":"2016-04-17T23:38:32Z","closed_at":null,"body":"I love how super simple flynn is to deploy on a single host, and I wish multi-host deployments could become as easy, which is still confusing. Here are my two cents:\r\n1. Instead of round-robin (which is not immune to failovers etc), a load-balancer container can be used to distribute traffic to hosts, and this container will have to auto-update ips in case new nodes are added, removed. Rancher which is another docker-based paas, has taken this route, and it makes quite a difference.\r\n2. Docs on multi-host deployments are still confusing. Basically, \"using flynn\" section is only a single node setup tutorial ( https://flynn.io/docs ), while \"operating flynn\" section goes into multi-host deployments ( https://flynn.io/docs/operating ) . This \"operating flynn\" section assumes you're already familiar with flynn-host init --init-discovery  which is explained in the \"manual installation\" section, which is not true, because the \"cloud installer\" section is the preferred installation way, as it is right on top and the automatic way. In few words, if you want a multi host installation you need to go through the \"manual installation\" route.\r\n3. Adding nodes, flynn-init etc, would be much better if they were part of the dashboard. \r\n"}}