> What if a container could be marked as "versioning enabled"
> and therefore the proxy server would rewrite uploads to
> distinct versioned objects and translate plain gets to the latest version?
>
> Example:
>
> Upload sample.txt, becomes sample.txt-1306882418.68949
> Upload sample.txt again, b
On May 31, 2011, at 4:49 PM, Rostyslav Slipetskyy wrote:
> I assume that in this scenario there is only one user/file of huge size and
> all
> the other users/files are much smaller (in other case, there will be not much
> difference in distribution among drives). But the suggested backup/reco
> Let's say you're backing up a Nova instance to Swift every day using
> versioning, and each backup is 5gb. After a few weeks, that hard
> drive may be storing over 100gb for one "file". Swift has no way of
> taking that into account when placing files, so the distribution is
> going to get clum
On Tue, May 31, 2011 at 5:54 AM, Rostyslav Slipetskyy
wrote:
>> The problem is that every version would be stored on the same drives, which
>> is
>>gonna screw with storage distribution.
>
> Could you please clarify this?
Sure. We've talked about this as a method of adding a "versioning"
featur
> The problem is that every version would be stored on the same drives, which
> is
>gonna screw with storage distribution.
Could you please clarify this?
I understand that drives are selected based on "account/container/object" path
and do not depend on the current storage distribution. So,
(re-sent to list)
On Mon, May 30, 2011 at 4:56 PM, Rostyslav Slipetskyy
wrote:
> It looks like backup/recovery can be easily added to swift without many
> changes
> in the source code. After successful file upload via PUT method, stored file
> receives name equal to timestamp and all the previou
6 matches
Mail list logo
