{"issue":{"created_at":"2011-09-27T21:12:40Z","state":"open","updated_at":"2011-11-25T20:24:54Z","user":{"gravatar_id":"2fac8d0146536433f3507b74d2619ecf","id":131416,"url":"https://api.github.com/users/nathanmarz","login":"nathanmarz","avatar_url":"https://secure.gravatar.com/avatar/2fac8d0146536433f3507b74d2619ecf?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"comments":6,"body":"This issue is a list of cases where people have wanted more control over how Storm schedules workers/tasks:\r\n\r\n1. Limit #workers/machine for a topology because of a large shared memory resource\r\n2. Only have a license for running software on a single machine, so want to limit a bolt to just one machine","assignee":null,"id":1756503,"number":11,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"labels":[{"name":"New feature","color":"02e10c","url":"https://api.github.com/repos/nathanmarz/storm/labels/New+feature"}],"title":"Topology-level control in task/worker scheduling","closed_at":null,"html_url":"https://github.com/nathanmarz/storm/issues/11","url":"https://api.github.com/repos/nathanmarz/storm/issues/11","milestone":null},"action":"created","comment":{"created_at":"2011-11-25T20:24:54Z","updated_at":"2011-11-25T20:24:54Z","user":{"gravatar_id":"38a2400e9f8848c0729cefcbf8ea0ec7","id":112275,"url":"https://api.github.com/users/pathouk","login":"pathouk","avatar_url":"https://secure.gravatar.com/avatar/38a2400e9f8848c0729cefcbf8ea0ec7?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"+1\r\n\r\nOur use case is similar to sybrandy's and nahap's.","id":2877850,"url":"https://api.github.com/repos/nathanmarz/storm/issues/comments/2877850"}}