{"action":"created","issue":{"url":"https://api.github.com/repos/docker/compose/issues/1661","labels_url":"https://api.github.com/repos/docker/compose/issues/1661/labels{/name}","comments_url":"https://api.github.com/repos/docker/compose/issues/1661/comments","events_url":"https://api.github.com/repos/docker/compose/issues/1661/events","html_url":"https://github.com/docker/compose/issues/1661","id":93344796,"number":1661,"title":"Feature request: add scale parameter in yml","user":{"login":"jmmills","id":49523,"avatar_url":"https://avatars.githubusercontent.com/u/49523?v=3","gravatar_id":"","url":"https://api.github.com/users/jmmills","html_url":"https://github.com/jmmills","followers_url":"https://api.github.com/users/jmmills/followers","following_url":"https://api.github.com/users/jmmills/following{/other_user}","gists_url":"https://api.github.com/users/jmmills/gists{/gist_id}","starred_url":"https://api.github.com/users/jmmills/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jmmills/subscriptions","organizations_url":"https://api.github.com/users/jmmills/orgs","repos_url":"https://api.github.com/users/jmmills/repos","events_url":"https://api.github.com/users/jmmills/events{/privacy}","received_events_url":"https://api.github.com/users/jmmills/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/docker/compose/labels/area/scale","name":"area/scale","color":"c7def8"},{"url":"https://api.github.com/repos/docker/compose/labels/kind/feature","name":"kind/feature","color":"bfd4f2"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":48,"created_at":"2015-07-06T18:32:34Z","updated_at":"2015-11-20T08:19:43Z","closed_at":null,"body":"As a user of compose (formally fig), I would like to be able to specify the number of nodes started for any given definition (a.k.a scale) from inside the manifest (yaml configuration file), so that I can ship my cluster definition with my service orchestration. \r\n\r\nE.g. syntax:\r\n    \r\n    worker:\r\n        build: rqworker\r\n        scale: 5\r\n        links:\r\n           - redis\r\n        command: rqworker -u tcp://redis "},"comment":{"url":"https://api.github.com/repos/docker/compose/issues/comments/158319269","html_url":"https://github.com/docker/compose/issues/1661#issuecomment-158319269","issue_url":"https://api.github.com/repos/docker/compose/issues/1661","id":158319269,"user":{"login":"bitgandtter","id":1316125,"avatar_url":"https://avatars.githubusercontent.com/u/1316125?v=3","gravatar_id":"","url":"https://api.github.com/users/bitgandtter","html_url":"https://github.com/bitgandtter","followers_url":"https://api.github.com/users/bitgandtter/followers","following_url":"https://api.github.com/users/bitgandtter/following{/other_user}","gists_url":"https://api.github.com/users/bitgandtter/gists{/gist_id}","starred_url":"https://api.github.com/users/bitgandtter/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bitgandtter/subscriptions","organizations_url":"https://api.github.com/users/bitgandtter/orgs","repos_url":"https://api.github.com/users/bitgandtter/repos","events_url":"https://api.github.com/users/bitgandtter/events{/privacy}","received_events_url":"https://api.github.com/users/bitgandtter/received_events","type":"User","site_admin":false},"created_at":"2015-11-20T08:19:43Z","updated_at":"2015-11-20T08:19:43Z","body":"In production cases you may want to star your services with a minimum scale. Let's say for example you are migrating from one cluster to another, and lets keep some hard parts of the migration as copy data out for the simplicity of the example; and you really need to start dealing with some traffic from the start so you need to deploy with docker-compose up at least (n) instances of some service lets say web. \r\n\r\nHaving scale under the service on the config file will really handle that. It's also an usability use case since if the use case in fact expose the requirement of having at least (n) instances of some service runnign and not just one at start point. \r\n\r\nFrom my point of view scale is in fact a defining parameter of a topology and composing. "}}