From 3da9f2212f0481a87b9ef2256b9db59a279451d2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20Han?= Date: Tue, 24 Nov 2020 11:41:09 +0100 Subject: [PATCH] bot: fix codespell issue MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Make the bot happy. Signed-off-by: Sébastien Han --- .github/workflows/codespell.yaml | 2 +- design/ceph/object/ceph-multisite-overview.md | 12 ++++++------ design/nfs/nfs.md | 2 +- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/.github/workflows/codespell.yaml b/.github/workflows/codespell.yaml index 2063b2b39..4522147e8 100644 --- a/.github/workflows/codespell.yaml +++ b/.github/workflows/codespell.yaml @@ -18,6 +18,6 @@ jobs: uses: codespell-project/actions-codespell@master with: skip: .git,*.png,*.jpg,*.svg,*.sum - ignore_words_list: aks,keyserver,atleast,dne,ser,ist,files',ba,dum,iam,te + ignore_words_list: aks,keyserver,atleast,dne,ser,ist,files',ba,dum,iam,te,parm check_filenames: true check_hidden: true diff --git a/design/ceph/object/ceph-multisite-overview.md b/design/ceph/object/ceph-multisite-overview.md index 51b3003ee..c0c2820b5 100644 --- a/design/ceph/object/ceph-multisite-overview.md +++ b/design/ceph/object/ceph-multisite-overview.md @@ -1,8 +1,8 @@ ## Ceph Multisite Overview -Multisite is a feature of Ceph that allows object stores to replicate its data over multiple Ceph clusters. +Multisite is a feature of Ceph that allows object stores to replicate its data over multiple Ceph clusters. -Multisite also allows object stores to be independent and isloated from other object stores in a cluster. +Multisite also allows object stores to be independent and isolated from other object stores in a cluster. ### Ceph Multisite data model @@ -34,11 +34,11 @@ When a ceph-object-store is created without the `zone` section; a realm, zone gr Since it is the only ceph-object-store in the realm, the data in the ceph-object-store remain independent and isolated from others on the same cluster. -When a ceph-object-store is created with the `zone` section, the Ceph Multisite will be configured. +When a ceph-object-store is created with the `zone` section, the Ceph Multisite will be configured. The ceph-object-store will join a zone, zone group, and realm with a different than it's own. -This allows the ceph-object-store to replacte it's data over multiple Ceph clusters. +This allows the ceph-object-store to replace it's data over multiple Ceph clusters. ### Overview Ceph Multisite Steps To enable Ceph's multisite, the following steps need to happen. @@ -66,7 +66,7 @@ To enable Ceph's multisite, the following steps need to happen. ### Future Design Roadmap -At the moment the multisite resources only handles Day 1 initial configuration. +At the moment the multisite resources only handles Day 1 initial configuration. Changes made to the resource's configuration or deletion of the resource are not reflected on the Ceph cluster. @@ -75,7 +75,7 @@ To be clear, when the ceph-object-{realm, zone group, zone} resource is deleted Future iterations of this design will address these Day 2 operations and other such as: - Initializing and modifying Storage Classes -- Deletion of the CR relecting deletion of the realm, zone group, & zone +- Deletion of the CR reflecting deletion of the realm, zone group, & zone - The status of the ceph-object-{realm, zone group, zone} reflecting the status of the realm, zone group, and zone. - Changing the master zone group in a realm - Changing the master zone in a zone group diff --git a/design/nfs/nfs.md b/design/nfs/nfs.md index d8c40c658..3e035383d 100644 --- a/design/nfs/nfs.md +++ b/design/nfs/nfs.md @@ -43,7 +43,7 @@ The NFS CRD spec will specify the following: - client (The host or network to which the export is being shared) - client options (The options to be used for the client) e.g., read and write permission, root squash etc. -The parameters to configure NFS CRD are demonstrated in the example bellow which is followed by a table that explains the parameters: +The parameters to configure NFS CRD are demonstrated in the example below which is followed by a table that explains the parameters: A simple example for sharing a volume(could be hostPath, cephFS, cephRBD, googlePD, EBS etc.) using NFS, without client specification and per export based configuration, whose NFS-Ganesha export entry looks like: ```