---- From: Alexander von Gluck IV <kallisti5@xxxxxxxxxxx> -- Sent: 2020-06-08 -
19:17 ----
June 8, 2020 12:34 AM, "A L" <mail@xxxxxxxxxxxxxx> wrote:
---- From: waddlesplash <waddlesplash@xxxxxxxxx> -- Sent: 2020-06-07 - 22:57
----
On Sun, Jun 7, 2020 at 11:05 AM Alexander von Gluck IV <
kallisti5@xxxxxxxxxxx> wrote:
Haikuports uses us *bunch* of symlinks and other local filesystem hacks
via haikuporter buildmaster.
It uses hardlinks, not symlinks, which is not a hack.
Someone should redesign the backend storage of it to be flexible enough
for object storage, or at least
not be heavily dependent on symlinks and large amount (~200-300GiB) of
local server files.
We discussed this before and determined that we could use s3fs, but it
would waste a ton of bandwidth. Most other OSes seem to do something
similar to what we are doing (some hundreds of GB of files on a server
somewhere.)
We don't have to be like everyone else though, we're not linux :-)
You could use s3fs (read only) to offer mirror access to our wasabi
repositories
We should make HaikuPorts available as an rsyncable mirror though. We had
few volunteers to mirror that, however...
Haiku already has a few (generous!) rsync mirrors in place for the OS + haiku
repos.
Could always use more though!
https://github.com/haiku/infrastructure/blob/master/data/repo-mirror/haiku-release/rsync-whitelist
https://github.com/haiku/infrastructure/blob/master/data/repo-mirror/haiku-repositories/rsync-whitelist
This process does need improved.
I wouldn't mind having a mirror for this too if you decide that's beneficial.
What's the issue with using either soft or hard links, or even reflinks?
The issue is the cheap/fast object storage like Wasabi doesn't really work
with
hard/soft links. (all numbers USD)
1 TiB @ Wasabi == $4.99 / month with no bandwidth limits + $60 / mo for the
vm
1 TiB @ SSD attached to a VM == $102.40 / month + $60 for the vm +
3TiB /mo of bandwidth.
It's not the end of the world, just something that ties Haiku to dragging
around
several hundred GiB of packages on a local file system (adding to costs,
reducing
our flexibility, etc)
-- Alex
