{"action":"opened","issue":{"url":"https://api.github.com/repos/openebs/openebs/issues/440","repository_url":"https://api.github.com/repos/openebs/openebs","labels_url":"https://api.github.com/repos/openebs/openebs/issues/440/labels{/name}","comments_url":"https://api.github.com/repos/openebs/openebs/issues/440/comments","events_url":"https://api.github.com/repos/openebs/openebs/issues/440/events","html_url":"https://github.com/openebs/openebs/issues/440","id":261709733,"number":440,"title":"Support for cloning a new volume from a snapshot of an existing volume. ","user":{"login":"kmova","id":12488783,"avatar_url":"https://avatars2.githubusercontent.com/u/12488783?v=4","gravatar_id":"","url":"https://api.github.com/users/kmova","html_url":"https://github.com/kmova","followers_url":"https://api.github.com/users/kmova/followers","following_url":"https://api.github.com/users/kmova/following{/other_user}","gists_url":"https://api.github.com/users/kmova/gists{/gist_id}","starred_url":"https://api.github.com/users/kmova/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kmova/subscriptions","organizations_url":"https://api.github.com/users/kmova/orgs","repos_url":"https://api.github.com/users/kmova/repos","events_url":"https://api.github.com/users/kmova/events{/privacy}","received_events_url":"https://api.github.com/users/kmova/received_events","type":"User","site_admin":false},"labels":[{"id":689991238,"url":"https://api.github.com/repos/openebs/openebs/labels/area/volume","name":"area/volume","color":"1d76db","default":false},{"id":540359854,"url":"https://api.github.com/repos/openebs/openebs/labels/kind/feature","name":"kind/feature","color":"88bbee","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-09-29T17:25:38Z","updated_at":"2017-09-29T17:25:38Z","closed_at":null,"author_association":"OWNER","body":"There are some usecases, like in data-science tasks, which require cloning of openebs volumes and provide the cloned volume with read/write access to a new pod. For example, consider this data-science task workflow:\r\n- Download the data (from opensourced dataset) and store it in an OpenEBS Volume\r\n- Start parallel tasks that needs access to the downloaded data, and tasks could either clean the data (generating a new dataset) or can add some missing information. \r\n- Some of these tasks actually can err on their initial runs and the tasks may have to be re-started with some modified logic. \r\n\r\nOne of the solution could be provide an read-only access to the original data (downloaded dataset). But this would require the modified data to be complete replicated. Making multiple copies of the data for different parallel \"experimental\" tasks would be -inefficient usage of space, especially if the delta of changes made is relatively small in size. "}}
{"actor":{"display_login":"kmova"}}