[
https://issues.apache.org/jira/browse/LIBCLOUD-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahendra M updated LIBCLOUD-252:
--------------------------------
Description:
The idea is to provide a 'local' storage driver. This will provide developers
with the ability to implement storage features with libcloud such that it can
be deployed on a cloud platform or over local file-systems (for eg: over a
local disk or a n/w mounted storage). This will allow for hybrid deployments
where the storage layer can be altered via config changes.
In addition, this also let's users play around with the library without the
need to access a cloud system
A sample implementation could
* use the 'key' argument as the base file-system where the objects will be
stored
* use a file-system hierarchy to represent containers and objects
was:
The idea is to provide a 'local' storage driver. This will provide developers
with the ability to implement storage features with libcloud such that it can
be deployed on a cloud platform or over local file-systems (for eg: over a
local disk or a n/w mounted storage). This will allow for hybrid deployments
where the storage layer can be altered via config changes.
In addition, this also let's users play around with the library without the
need to access a cloud system
> Implement a local storage driver
> --------------------------------
>
> Key: LIBCLOUD-252
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-252
> Project: Libcloud
> Issue Type: New Feature
> Components: Storage
> Reporter: Mahendra M
> Priority: Minor
> Labels: features
> Attachments: libcloud-252.patch
>
>
> The idea is to provide a 'local' storage driver. This will provide developers
> with the ability to implement storage features with libcloud such that it can
> be deployed on a cloud platform or over local file-systems (for eg: over a
> local disk or a n/w mounted storage). This will allow for hybrid deployments
> where the storage layer can be altered via config changes.
> In addition, this also let's users play around with the library without the
> need to access a cloud system
> A sample implementation could
> * use the 'key' argument as the base file-system where the objects will be
> stored
> * use a file-system hierarchy to represent containers and objects
--
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
