{"action":"created","issue":{"url":"https://api.github.com/repos/Tendrl/documentation/issues/34","repository_url":"https://api.github.com/repos/Tendrl/documentation","labels_url":"https://api.github.com/repos/Tendrl/documentation/issues/34/labels{/name}","comments_url":"https://api.github.com/repos/Tendrl/documentation/issues/34/comments","events_url":"https://api.github.com/repos/Tendrl/documentation/issues/34/events","html_url":"https://github.com/Tendrl/documentation/issues/34","id":178790823,"number":34,"title":"Document the replace storage device workflow in tendrl","user":{"login":"shtripat","id":6771252,"avatar_url":"https://avatars.githubusercontent.com/u/6771252?v=3","gravatar_id":"","url":"https://api.github.com/users/shtripat","html_url":"https://github.com/shtripat","followers_url":"https://api.github.com/users/shtripat/followers","following_url":"https://api.github.com/users/shtripat/following{/other_user}","gists_url":"https://api.github.com/users/shtripat/gists{/gist_id}","starred_url":"https://api.github.com/users/shtripat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/shtripat/subscriptions","organizations_url":"https://api.github.com/users/shtripat/orgs","repos_url":"https://api.github.com/users/shtripat/repos","events_url":"https://api.github.com/users/shtripat/events{/privacy}","received_events_url":"https://api.github.com/users/shtripat/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Tendrl/documentation/labels/documentation","name":"documentation","color":"5319e7"},{"url":"https://api.github.com/repos/Tendrl/documentation/labels/workflow","name":"workflow","color":"fef2c0"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-09-23T05:51:16Z","updated_at":"2016-10-04T08:29:52Z","closed_at":null,"body":"If a storage device goes faulty (which is supposed to happen in real world), we need to clearly have workflows defined how a new device could be brought in the system and replaced for the faulty one\r\n- This needs to take care of movement of data new device coming up into picture\r\n- Then slowly phasing out the old faulty device\r\n- Finally bring down the faulty device and remove from the underlying cluster\r\n\r\nThis flow looks simpler but involves lot of technicalities in ceph and gluster and its a risky stuff and need to be done very carefully, so flow and steps involved should be well thought through and implemented."},"comment":{"url":"https://api.github.com/repos/Tendrl/documentation/issues/comments/251326335","html_url":"https://github.com/Tendrl/documentation/issues/34#issuecomment-251326335","issue_url":"https://api.github.com/repos/Tendrl/documentation/issues/34","id":251326335,"user":{"login":"nthomas-redhat","id":6671718,"avatar_url":"https://avatars.githubusercontent.com/u/6671718?v=3","gravatar_id":"","url":"https://api.github.com/users/nthomas-redhat","html_url":"https://github.com/nthomas-redhat","followers_url":"https://api.github.com/users/nthomas-redhat/followers","following_url":"https://api.github.com/users/nthomas-redhat/following{/other_user}","gists_url":"https://api.github.com/users/nthomas-redhat/gists{/gist_id}","starred_url":"https://api.github.com/users/nthomas-redhat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nthomas-redhat/subscriptions","organizations_url":"https://api.github.com/users/nthomas-redhat/orgs","repos_url":"https://api.github.com/users/nthomas-redhat/repos","events_url":"https://api.github.com/users/nthomas-redhat/events{/privacy}","received_events_url":"https://api.github.com/users/nthomas-redhat/received_events","type":"User","site_admin":false},"created_at":"2016-10-04T08:29:52Z","updated_at":"2016-10-04T08:29:52Z","body":"Replace nothing but expand the cluster and then removing(shrink cluster) the faulty node. Its not going to be a single operation."}}
{"actor":{"display_login":"nthomas-redhat"}}