From fb8fd1a060d6f2e51917b5acdf6d79be6ffd1eb4 Mon Sep 17 00:00:00 2001 From: chrislu Date: Fri, 29 Jul 2022 15:46:15 -0700 Subject: [PATCH] moving --- Async-Backup.md | 3 +-- Cloud-Drive-Architecture.md | 2 +- Cloud-Drive-Benefits.md | 2 +- Gateway-to-Remote-Object-Storage.md | 2 +- Home.md | 4 ++-- 5 files changed, 6 insertions(+), 7 deletions(-) diff --git a/Async-Backup.md b/Async-Backup.md index c4756ab..8fa6de4 100644 --- a/Async-Backup.md +++ b/Async-Backup.md @@ -9,7 +9,7 @@ Of course, you can also backup to local disks on another machine. # Architecture -![SeaweedFS Architecture](https://raw.githubusercontent.com/chrislusf/seaweedfs/master/note/SeaweedFS_Filer_Backup.png) +![SeaweedFS Architecture](https://raw.githubusercontent.com/seaweedfs/seaweedfs/master/note/SeaweedFS_Filer_Backup.png) All file meta data changes in Filer are saved in the logs and can be subscribed. See [[Filer Change Data Capture]]. @@ -80,4 +80,3 @@ The backup destination will have the following directory structure. /2021-03-02/dir1/file1 /2021-03-02/dir1/file4 ``` - diff --git a/Cloud-Drive-Architecture.md b/Cloud-Drive-Architecture.md index 49f62a8..af8d71b 100644 --- a/Cloud-Drive-Architecture.md +++ b/Cloud-Drive-Architecture.md @@ -20,7 +20,7 @@ SeaweedFS Cloud Drive can also optionally cache or uncache specific files accord With this feature, SeaweedFS can cache data that is on cloud. It can cache both metadata and file content. Given SeaweedFS unlimited scalability, the cache size is actually unlimited. Any local changes can be write back to the cloud asynchronously. -![SeaweedFS Cloud Drive](https://raw.githubusercontent.com/chrislusf/seaweedfs/master/note/SeaweedFS_RemoteMount.png) +![SeaweedFS Cloud Drive](https://raw.githubusercontent.com/seaweedfs/seaweedfs/master/note/SeaweedFS_RemoteMount.png) ``` [HDFS|Mount|HTTP|S3|WebDAV] <== Filer / Volume Server <== `remote.mount` <== Cloud diff --git a/Cloud-Drive-Benefits.md b/Cloud-Drive-Benefits.md index 8d06113..26fd5ec 100644 --- a/Cloud-Drive-Benefits.md +++ b/Cloud-Drive-Benefits.md @@ -39,7 +39,7 @@ However, how to make SeaweedFS work with data already on cloud? # Design -![SeaweedFS Remote Storage](https://raw.githubusercontent.com/chrislusf/seaweedfs/master/note/SeaweedFS_RemoteMount.png) +![SeaweedFS Remote Storage](https://raw.githubusercontent.com/seaweedfs/seaweedfs/master/note/SeaweedFS_RemoteMount.png) # Benefits diff --git a/Gateway-to-Remote-Object-Storage.md b/Gateway-to-Remote-Object-Storage.md index 9f729a5..d0eb1c5 100644 --- a/Gateway-to-Remote-Object-Storage.md +++ b/Gateway-to-Remote-Object-Storage.md @@ -10,7 +10,7 @@ How to synchronize them automatically? # Design of Gateway to Remote Object Store -![SeaweedFS Gateway to RemoteObjectStorage](https://raw.githubusercontent.com/chrislusf/seaweedfs/master/note/SeaweedFS_Gateway_RemoteObjectStore.png) +![SeaweedFS Gateway to RemoteObjectStorage](https://raw.githubusercontent.com/seaweedfs/seaweedfs/master/note/SeaweedFS_Gateway_RemoteObjectStore.png) The `weed filer.remote.gateway -createBucketAt=cloud1` process can mirror local changes to remote object storage, i.e.: diff --git a/Home.md b/Home.md index cd65975..28a9c42 100644 --- a/Home.md +++ b/Home.md @@ -2,7 +2,7 @@ Here is the white paper for [SeaweedFS Architecture.pdf](SeaweedFS_Architecture.pdf) -![SeaweedFS Architecture](https://raw.githubusercontent.com/chrislusf/seaweedfs/master/note/SeaweedFS_Architecture.png) +![SeaweedFS Architecture](https://raw.githubusercontent.com/seaweedfs/seaweedfs/master/note/SeaweedFS_Architecture.png) # Make Cloud Storage Cheaper and Faster! @@ -12,4 +12,4 @@ To reduce API cost and transmission cost, and minimize read-write latency, you c * Asynchronously propagate local updates to the cloud storage. * Works well with existing cloud ecosystems. -![SeaweedFS Remote Storage](https://raw.githubusercontent.com/chrislusf/seaweedfs/master/note/SeaweedFS_RemoteMount.png) +![SeaweedFS Remote Storage](https://raw.githubusercontent.com/seaweedfs/seaweedfs/master/note/SeaweedFS_RemoteMount.png)