You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Fred Krone (JIRA)" <ji...@apache.org> on 2017/08/15 22:34:00 UTC
[jira] [Updated] (GEODE-3446) Add cloud store option for export /
import
[ https://issues.apache.org/jira/browse/GEODE-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fred Krone updated GEODE-3446:
------------------------------
Description:
Users would like the ability to export a region to an external cloudstore like S3, Azure, or GoogleCloud.
A few things to think about is how to handle the credentials.
Should we create a new gfsh command to configure an S3 connection which can be used anytime? Or should that be handled inline with the export command?
was:
Users would like the ability to export a region to an external cloudstore like S3, Azure, or GoogleCloud.
A few things to think about is how to handle the credentials.
Should we create a new gfsh command to configure an S3 connection which can be used anytime? Or should that be handled inline with the export command?
We need to encrypt and decrypt the data before sending it to S3.
> Add cloud store option for export / import
> ------------------------------------------
>
> Key: GEODE-3446
> URL: https://issues.apache.org/jira/browse/GEODE-3446
> Project: Geode
> Issue Type: Sub-task
> Components: snapshot
> Reporter: Fred Krone
>
> Users would like the ability to export a region to an external cloudstore like S3, Azure, or GoogleCloud.
> A few things to think about is how to handle the credentials.
> Should we create a new gfsh command to configure an S3 connection which can be used anytime? Or should that be handled inline with the export command?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)