From: Tiziano Bacocco via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Tiziano Bacocco <tizbac2@gmail.com>
Subject: [pve-devel] S3 Support
Date: Tue, 16 Jul 2024 00:20:31 +0200 [thread overview]
Message-ID: <mailman.478.1721082051.331.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 4896 bytes --]
From: Tiziano Bacocco <tizbac2@gmail.com>
To: pve-devel@lists.proxmox.com
Subject: S3 Support
Date: Tue, 16 Jul 2024 00:20:31 +0200
Message-ID: <CAMLJ59xq0qBDCfVSDyirB8J++SZUSHYJvHdKYr4bOZks8123_w@mail.gmail.com>
Hi, to everyone, i'm interested in native S3 support on proxmox, is anyone
working on it ( to avoid double work )?
Second question, my idea is to reuse existing pbs code but upload chunks
and index to s3, sounds good? The thing puzzling me is that a lot of code
will end up duplicated , when actually only the part uploading to S3
instead of pbs would be different, chunking, fleeching, restoring, backup,
qemu interface would be almost identical
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-07-15 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 22:20 Tiziano Bacocco via pve-devel [this message]
2024-07-16 6:37 ` Fabian Grünbichler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.478.1721082051.331.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=tizbac2@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox