Help with Wasabi mounting

[marcusquinn]

TBH I can see the advantages for having a separate Nextcloud instance with just the Files app enabled as web interface for S3 to allow users to have it available as a slower cold-storage option, with having a faster standard NC setup for their daily hot-storage needs.

So, I wouldn't dismiss this aim, just with speed cautions, and the cautions in the article that the storage would then be unbrowsable directly without the NC database metadata interface, so it also has mass disruption risks if that were lost.

[robi]

@marcusquinn said in Help with Wasabi mounting:

@privsec Just reading this, not sure if you've read? I'm not saying i can't be done, just that we gave up. Maybe this helps? I'm still reading: https://autoize.com/s3-compatible-storage-for-nextcloud/

This is along the same lines as my advanced object store usage option above.

I didn't know this was possible from within NC, but it appears they engineered it in. Very smart & clever.

They are essentially caching everything recent in /tmp and background syncing to the object store over time.
The user experience is good as it's all mostly local, and the capacity is greatly extended as the Object Store is vast.

I've designed this for other use cases at IBM, and wrote their Redbook on it, hence advanced prior knowledge.

For this article to be applied in Cloudron, we'd need a new packaged NC App that is configured for this before the setup/install. Then one can point it at a local Minio instance or external S3 object store.

[girish]

@robi We have tried the setup of using S3 as objectstorage before in nextcloud and it just doesn't perform well. It also makes a very large number of s3 requests and for things like AWS this costs some real $$$. Other services like DO Spaces will promptly rate limit. Overall, the whole setup is unstable. It looks good on paper but doesn't work reliably for serious use.

for example: https://help.nextcloud.com/t/high-aws-s3-costs-due-to-nextcloud-requests/68687 and https://help.nextcloud.com/t/high-traffic-to-primary-storage-s3-from-nextcloud/83185 .

[robi]

@girish yes, the article explicitly warns about this, pointing out that AWS is not a good place to do this as it's not a part of the bandwidth alliance.

This is not a problem with NC, but of the underlying architecture chosen.

There is a way to make this work well, but one must understand all the pieces, as if you ignore one, it will be the lowest common denominator and bottleneck.

It is an Enterprise Deployment afterall.

[marcusquinn]

@girish This article suggests there's an old and a new way to do this, so I wonder if we're all talking about the same thing?

• https://autoize.com/s3-compatible-storage-for-nextcloud/

[robi]

@marcusquinn said in Help with Wasabi mounting:

@girish This article suggests there's an old and a new way to do this, so I wonder if we're all talking about the same thing?

• https://autoize.com/s3-compatible-storage-for-nextcloud/

old = adding an additional S3 store from within NC running locally.
new = setting up NC with S3 as primary storage.

[girish]

@robi @marcusquinn Both methods have been there for a some time. I have investigated this a year or so ago, for example, this and this. Back then, it was not really stable. It will create a lot of oid:xx files in the object backend and AFAIK there is no easy way to change an installation from one storage to another (it's setup once at install time). All this means, that as @robi pointed out, this is really targeted at enterprises and people having full time dedicated sysadmins and nextcloud support contract. Don't get me wrong, I am sure it can be made to work but it's not something we want to support (best to pay nextcloud for this)

[marcusquinn]

@girish Fair enough. Thanks.

[cdolson]

@robi I've managed to get this working using Digital Ocean Spaces on my Cloudron Nextcloud installation by following the instructions at this resource. This involved simply editing the config/config.php file to include the following:

'objectstore' => 
array (
  'class' => '\\OC\\Files\\ObjectStore\\S3',
  'arguments' => 
  array (
    'bucket' => 'yourbucketname',
    'key' => 'YOURKEY',
    'secret' => 'YOURSECRET',
    'hostname' => 'nyc3.digitaloceanspaces.com',
    'region' => 'nyc3',
    'port' => 443,
    'use_ssl' => true,
    'use_path_style' => true,
  ),
),
);

I added this to the very end of my config.php, and before the last closing );

Functionality tested and working. Uploads and downloads happen directly within the DO Spaces bucket. Configuration persists between reboots.

I am new to Cloudron, so I am not certain if these changes will persist after updates to the Nextcloud app or Cloudron.

[privsec]

@cdolson How are the speeds?