{"action":"created","issue":{"url":"https://api.github.com/repos/rabbitmq/rabbitmq-server/issues/598","labels_url":"https://api.github.com/repos/rabbitmq/rabbitmq-server/issues/598/labels{/name}","comments_url":"https://api.github.com/repos/rabbitmq/rabbitmq-server/issues/598/comments","events_url":"https://api.github.com/repos/rabbitmq/rabbitmq-server/issues/598/events","html_url":"https://github.com/rabbitmq/rabbitmq-server/issues/598","id":130710919,"number":598,"title":"We would like the ability to be able to work around having to take a RabbitMQ cluster down to upgrade between major versions. ","user":{"login":"davidhiston","id":8375252,"avatar_url":"https://avatars.githubusercontent.com/u/8375252?v=3","gravatar_id":"","url":"https://api.github.com/users/davidhiston","html_url":"https://github.com/davidhiston","followers_url":"https://api.github.com/users/davidhiston/followers","following_url":"https://api.github.com/users/davidhiston/following{/other_user}","gists_url":"https://api.github.com/users/davidhiston/gists{/gist_id}","starred_url":"https://api.github.com/users/davidhiston/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davidhiston/subscriptions","organizations_url":"https://api.github.com/users/davidhiston/orgs","repos_url":"https://api.github.com/users/davidhiston/repos","events_url":"https://api.github.com/users/davidhiston/events{/privacy}","received_events_url":"https://api.github.com/users/davidhiston/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-02-02T15:11:26Z","updated_at":"2016-02-02T15:12:40Z","closed_at":"2016-02-02T15:12:40Z","body":"Hi, \r\n\r\nWe are looking to use RabbitMQ in production environments with quite strict SLA's around service downtime.  We would therefore like the capability to initiate rolling upgrades for major release versions which will would allow each node to be upgraded in turn, while keeping the messaging service as a whole on-line.  \r\n\r\nOne suggested method of attack could be to support something like the following: \r\n\r\nHave the RabbitMQ cluster behind a VIP.  To upgrade the RabbitMQ cluster, it should be possible to  spin up an alternate cluster and switch the VIP over to the alternate cluster to maintain message queue availability.  We should then have a tool which moves messages between clusters (like the shovel). When the 'master' cluster's update is done, the process is reversed.\r\n\r\nThanks, \r\n\r\nDave "},"comment":{"url":"https://api.github.com/repos/rabbitmq/rabbitmq-server/issues/comments/178625488","html_url":"https://github.com/rabbitmq/rabbitmq-server/issues/598#issuecomment-178625488","issue_url":"https://api.github.com/repos/rabbitmq/rabbitmq-server/issues/598","id":178625488,"user":{"login":"davidhiston","id":8375252,"avatar_url":"https://avatars.githubusercontent.com/u/8375252?v=3","gravatar_id":"","url":"https://api.github.com/users/davidhiston","html_url":"https://github.com/davidhiston","followers_url":"https://api.github.com/users/davidhiston/followers","following_url":"https://api.github.com/users/davidhiston/following{/other_user}","gists_url":"https://api.github.com/users/davidhiston/gists{/gist_id}","starred_url":"https://api.github.com/users/davidhiston/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davidhiston/subscriptions","organizations_url":"https://api.github.com/users/davidhiston/orgs","repos_url":"https://api.github.com/users/davidhiston/repos","events_url":"https://api.github.com/users/davidhiston/events{/privacy}","received_events_url":"https://api.github.com/users/davidhiston/received_events","type":"User","site_admin":false},"created_at":"2016-02-02T15:12:40Z","updated_at":"2016-02-02T15:12:40Z","body":"@"}}