-
Notifications
You must be signed in to change notification settings - Fork 363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Storage - HA-NAS - Update - Mounting HA-NAS via NFS share #3484
Conversation
Thanks for the job. |
|
||
- An [OVHcloud HA-NAS solution](https://www.ovhcloud.com/en-gb/storage-solutions/nas-ha/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my opinion, translating the product name is an issue , but I can understand this is a commercial decision.
However if the name is translated or not, we must take this in account in the URL path
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The product name is translated on https://www.ovhcloud.com/en-gb/storage-solutions/nas-ha/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes but why?
And why the path is not?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not our call inside the documentation team. Please ask website/marketing teams.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Notice that we had some inconsistencies if we look in the whole doc:
❯ grep -r "NAS-HA" pages/ | grep "en.gb"
pages/platform/kubernetes-k8s/configuring-multi-attach-persistent-volumes-with-ovh-nas-ha/guide.en-gb.md:title: Configuring multi-attach persistent volumes with OVHcloud NAS-HA
pages/platform/kubernetes-k8s/configuring-multi-attach-persistent-volumes-with-ovh-nas-ha/guide.en-gb.md:excerpt: 'Find out how to configure a multi-attach persistent volume using OVHcloud NAS-HA'
pages/platform/kubernetes-k8s/configuring-multi-attach-persistent-volumes-with-ovh-nas-ha/guide.en-gb.md:OVHcloud Managed Kubernetes natively integrates Block Storage as persistent volumes. This technology may however not be suited to some legacy or non cloud-native applications, often requiring to share this persistent data accross different pods on multiple worker nodes (ReadWriteMany or RWX). If you would need to do this for some of your workloads, one solution is to use NFS volumes. [OVHcloud NAS-HA](https://www.ovh.co.uk/nas/) is a managed solution that lets you easily configure an NFS server and multiple NFS volumes. In this tutorial we are going to see how to configure your OVHcloud Managed Kubernetes cluster to use [OVHcloud NAS-HA](https://www.ovh.co.uk/nas/) as an NFS provider for [Kubernetes Persistent Volumes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/).
pages/platform/kubernetes-k8s/configuring-multi-attach-persistent-volumes-with-ovh-nas-ha/guide.en-gb.md:It also assumes you have an OVHcloud NAS-HA already available. If you don't, you can [order one in the OVHcloud Control Panel](https://www.ovh.com/manager/dedicated/#/configuration/nas).
pages/platform/kubernetes-k8s/configuring-multi-attach-persistent-volumes-with-ovh-nas-ha/guide.en-gb.md:Your NAS-HA can expose multiple partitions, and supports a variety of protocols. Each partition is accessible only from a specific range of IPs. We will create one exposing NFS and make it accessible from your Kubernetes worker nodes.
pages/platform/kubernetes-k8s/configuring-multi-attach-persistent-volumes-with-ovh-nas-ha/guide.en-gb.md:Access the UI for OVHcloud NAS-HA by clicking the *NAS and CDN* menu in the [Server section of the OVHcloud Control Panel](https://www.ovh.com/manager/dedicated)
pages/platform/kubernetes-k8s/configuring-multi-attach-persistent-volumes-with-ovh-nas-ha/guide.en-gb.md:Congratulations, you have successfully set up a multi-attach persistent volume with OVHcloud NAS-HA!
pages/platform/kubernetes-k8s/known-limits/guide.en-gb.md:You can manually [configure multi-attach persistent volumes with NAS-HA](../Configuring-multi-attach-persistent-volumes-with-ovhcloud-nas-ha/).
pages/cloud/storage/nas_cifs/guide.en-gb.md:- CIFS mounting for a NAS-HA:
pages/account/billing/how_to_cancel_services/guide.en-gb.md:  [NAS-HA Server](#nas)<br />
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Duly noted, we'll do the necessary fixes to align them all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The product name is translated on https://www.ovhcloud.com/en-gb/storage-solutions/nas-ha/
But not in the URL
```sh | ||
/etc/init.d/rpcbind start | ||
```bash | ||
ubuntu@server:~$ sudo mount -t nfs -o _netdev,mountproto=tcp IP_HA-NAS:NFS_PATH /MOUNTING_FOLDER |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I seriously doubt the necessity of these options:
- do you have explanations for those?
- why we need to use it in a standard use case?
- fedora's example do not use those
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I took the commands from the existing guide and only edited for clarity and errors. Since the mount commands worked when I did my tests I had no reason to doubt the options. Feel free to apply changes.
```sh | ||
mount -t nfs -o _netdev,mountproto=tcp IP_NAS:/NFS_PATH /MOUNTING_FOLDER | ||
```bash | ||
ubuntu@server:~$ sudo mount -t nfs -o _netdev,mountproto=tcp 10.1.1.1:zpool-123456/partition01 /mount/ha_nas |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as upper comment
```sh | ||
mount -t nfs IP_NAS:/NFS_PATH /MOUNTING_FOLDER | ||
```bash | ||
centos@server:~$ sudo mount -t nfs -o _netdev,mountproto=tcp IP_HA-NAS:NFS_PATH /MOUNTING_FOLDER |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as upper comment
|
||
```bash | ||
centos@server:~$ sudo mount -t nfs -o _netdev,mountproto=tcp 10.1.1.1:zpool-123456/partition01 /mount/ha_nas |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as upper comment
URLs path are un-consistant:
Could we use a naming convention? A nice move will be using same convention between ❯ grep -r "https://docs.ovh.com/gb/en/storage/nas" pages/
pages/cloud/storage/nas_quick_api/guide.en-gb.md:[Mount your NAS via NFS share](https://docs.ovh.com/gb/en/storage/nas-nfs/)
pages/cloud/storage/nas_quick_api/guide.en-gb.md:[Mount your NAS on Windows Server via CIFS](https://docs.ovh.com/gb/en/storage/nas/nas-cifs/)
pages/cloud/storage/nas_managing_acls/guide.en-gb.md:[Mount your NAS via NFS share](https://docs.ovh.com/gb/en/storage/nas-nfs/)
pages/cloud/storage/nas_managing_acls/guide.en-gb.md:[Mount your NAS on Windows Server via CIFS](https://docs.ovh.com/gb/en/storage/nas/nas-cifs/)
pages/cloud/storage/nas_migration/guide.en-gb.md:- You need to have mounted your HA-NAS beforehand by following the guide to [mount your HA-NAS via an NFS](https://docs.ovh.com/gb/en/storage/nas-nfs/){.external} share.
pages/cloud/storage/nas_nfs/guide.en-gb.md:- [A partition created on the service with the NFS protcol enabled](https://docs.ovh.com/gb/en/storage/nas/get-started/#create_partition)
pages/cloud/storage/nas_nfs/guide.en-gb.md:- [An ACL entry for the server's IP address](https://docs.ovh.com/gb/en/storage/nas/get-started/#access_control)
pages/cloud/storage/nas_managing_snapshots/guide.en-gb.md:[Mount your NAS via NFS share](https://docs.ovh.com/gb/en/storage/nas-nfs/)
pages/cloud/storage/nas_managing_snapshots/guide.en-gb.md:[Mount your NAS on Windows Server via CIFS](https://docs.ovh.com/gb/en/storage/nas/nas-cifs/)
pages/cloud/storage/nas_managing_partitions/guide.en-gb.md:[Mount your NAS via NFS share](https://docs.ovh.com/gb/en/storage/nas-nfs/)
pages/cloud/storage/nas_managing_partitions/guide.en-gb.md:[Mount your NAS on Windows Server via CIFS](https://docs.ovh.com/gb/en/storage/nas/nas-cifs/)
pages/cloud/storage/enterprise-file-storage-quick-api/guide.en-sg.md:- Basic understanding of how to [mount a NFS volume](https://docs.ovh.com/gb/en/storage/nas-nfs/)
pages/cloud/storage/enterprise-file-storage-quick-api/guide.en-gb.md:- Basic understanding of how to [mount a NFS volume](https://docs.ovh.com/gb/en/storage/nas-nfs/)
pages/cloud/storage/nas_order_basics/guide.en-gb.md:You can manage your HA-NAS service via the [OVHcloud API](https://docs.ovh.com/gb/en/storage/nas/nas-quickapi/) or in your OVHcloud Control Panel.
pages/cloud/storage/nas_order_basics/guide.en-gb.md:[Managing partitions via API](https://docs.ovh.com/gb/en/storage/nas/nas-partitions-api/)
pages/cloud/storage/nas_order_basics/guide.en-gb.md:[Managing partition ACLs via API](https://docs.ovh.com/gb/en/storage/nas/nas-manage-acls/)
pages/cloud/storage/nas_order_basics/guide.en-gb.md:[Managing snapshots via API](https://docs.ovh.com/gb/en/storage/nas/nas-snapshots-api)
pages/cloud/storage/nas_order_basics/guide.en-gb.md:[Mounting your HA-NAS via NFS share](https://docs.ovh.com/gb/en/storage/nas-nfs/)
pages/cloud/storage/nas_order_basics/guide.en-gb.md:[Mount your NAS on Windows Server via CIFS](https://docs.ovh.com/gb/en/storage/nas/nas-cifs/) |
All storage pages will soon be re-classified, so we'll take advantage of this change to make organisation consistant. |
0020477
to
6ed330b
Compare
6ed330b
to
5943034
Compare
Sorry, I loose fight to sign commit with GPG. |
5943034
to
d7ce5fa
Compare
Ah ah! I finally did it! |
No description provided.