![]() ![]() mnt/somedrive/subdirectory is the directory you'd like clients to be able to access, and 10.1.2.0/24 is the IP range that should be allowed to talk to your NFS server. ![]() edit /etc/exports to look something like this: /mnt/somedrive/subdirectory 10.1.2.0/24(rw,async,no_subtree_check) Simply install the relevant package: sudo apt install nfs-kernel-server If you don't have a trusted network, use the WireGuard Mesh VPN trick in part 4 of this series. You should ensure that NFS is only run on a trusted network. If you're going to choose NFS like me though, you should be warned that it's neither encrypted not authenticated. This is hardly the only solution to the issue though - other options include: In this one, we're going to look at running our first job on our Nomad cluster! If you haven't read the previous posts in this series, you'll probably want to go back and read them now, as we're going to be building on the infrastructure we've setup and the groundwork we've laid in the previous posts in this series.īefore we get to that though, we need to sort out shared storage - as we don't know which node in the cluster tasks will be running on. boxes? | Expanding the Hashicorp stack with Docker and Nomad Cluster, Part 6: Superglue Service Discovery | Setting up Consul.Cluster, Part 5: Staying current | Automating apt updates and using apt-cacher-ng.Cluster, Part 4: Weaving Wormholes | Peer-to-Peer VPN with WireGuard.Cluster, Part 3: Laying groundwork with Unbound as a DNS server.Cluster, Part 1: Answers only lead to more questions. ![]() As a refresher, here's a list of all the parts in the series so far: ![]() Welcome back! It's been a bit of a while, but now I'm back with the next part of my cluster series. Cluster, Part 8: The Shoulders of Giants | NFS, Nomad, Docker Registry ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |