ivampiresp/longhorn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(typo): codespell tested failed

Browse Source 
Fixed some typos that codespell found.

Signed-off-by: James Lu <james.lu@suse.com>
This commit is contained in:
James Lu 2023-10-05 09:22:41 +08:00 committed by David Ko
parent e1914963a6
commit 8c6a3f5142
3 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
enhancements/20220428-storage-network-through-grpc-proxy.md
View File

@ -51,7 +51,7 @@ https://github.com/longhorn/longhorn/issues/3546
- Introduce a new gRPC server in Instance Manager.
- Keep re-usable connections between Manager and Instance Managers.
- Keep reusable connections between Manager and Instance Managers.
- Allow Manager to fall back to engine binary call when communicating with old Instance Manager.

2
enhancements/20230526-volume-backup-policy-for-longhorn-system-backup.md
View File

@ -30,7 +30,7 @@ Overall, the proposed volume backup policies aim to improve the Longhorn system
1. When volume backup policy is specified:
- `if-not-present`: Longhorn will create a backup for volumes that do not have an existing backup.
- `alway`: Longhorn will create a backup for all volumes, regardless of their existing backups.
- `always`: Longhorn will create a backup for all volumes, regardless of their existing backups.
- `disabled`: Longhorn will not create any backups for volumes.
1. If a volume backup policy is not specified, the policy will be automatically set to `if-not-present`. This ensures that volumes without any existing backups will be backed up during the Longhorn system backup.

2
enhancements/20230807-backingimage-backup-support.md
View File

@ -181,7 +181,7 @@ This improve the user experience and reduce the operation overhead.
5. In `BackingImageDataSourceController`
- No need to change, it will create the `BackingImageDataSourcePod` to do the restore.
6. In `BackingImageManager - data_source`
- When init the service, if the type is `restore`, then restore from `backup-url` by resquesting sync service in the same pod.
- When init the service, if the type is `restore`, then restore from `backup-url` by requesting sync service in the same pod.
```go
requestURL := fmt.Sprintf("http://%s/v1/files", client.Remote)
req, err := http.NewRequest("POST", requestURL, nil)