You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Animesh Chaturvedi (JIRA)" <ji...@apache.org> on 2013/07/22 23:44:50 UTC

[jira] [Updated] (CLOUDSTACK-509) S3-backed Secondary Storage

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Animesh Chaturvedi updated CLOUDSTACK-509:
------------------------------------------


These items are still not resolved for 4.2 Please review your items, if not ready for 4.2 please move them out to future release
                
> S3-backed Secondary Storage
> ---------------------------
>
>                 Key: CLOUDSTACK-509
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-509
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: ISO, Management Server, Snapshot, Storage Controller, Template, Xen, XenServer
>    Affects Versions: 4.1.0
>            Reporter: John Burwell
>            Assignee: John Burwell
>              Labels: features, newbie, patch
>             Fix For: 4.2.0
>
>
> Backs NFS-based secondary storage with an S3-compatible object store.  Periodically, a reaper thread synchronizes templates and ISOs stored on a NFS secondary storage mount with a configured S3 object store.  It also pushes snapshots to the object store when they are created and downloads them in other zones on-demand. In addition to permitting the use of commodity or IaaS storage solutions for static assets, it provides a means of automatically synchronizing template and ISO assets across multiple zones.
> Release Planning:
> Dev list discussion: http://markmail.org/message/vrq4t3f2mdmyatef
> Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/S3-backed+Secondary+Storage
> Feature Branch: review board https://reviews.apache.org/r/8123/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira