Page MenuHomePhabricator

mount nfs directly into pods
Closed, ResolvedPublic


PAWS currently mounts nfs into the cluster nodes, then the pods use a hostpath to mount into themselves. This prevents us from moving to a more cloud based solution, as it requires we have special worker nodes. Additionally has resulted in PAWS going down due to stale nfs mounts on some of the nodes. Should this task be completed we should be able to remove that requirement from the puppet manifest for PAWS increasing stability of the service.

Event Timeline

I am aware of one breaking change in this patch.
Currently one can access nfs through a series of sim links on the worker node as follows:

rook@paws-k8s-worker-3:~$ ls -l /public/dumps/
total 8
lrwxrwxrwx 1 root root 54 Oct  3 13:05 incr -> /mnt/nfs/
lrwxrwxrwx 1 root root 70 Oct  3 13:05 pagecounts-all-sites -> /mnt/nfs/
lrwxrwxrwx 1 root root 64 Oct  3 13:05 pagecounts-raw -> /mnt/nfs/
lrwxrwxrwx 1 root root 59 Oct  3 13:05 pageviews -> /mnt/nfs/
lrwxrwxrwx 1 root root 44 Oct  3 13:05 public -> /mnt/nfs/

It is unclear to me on why these links to other/ exist, as they are all accessible through public. As such anyone accessing data through /public/dumps/<incr/pagecounts-all-sites/pagecounts-raw/pageviews> would experience a file not found kind of error with this change. This seems manageable through an announcement of the change. Though is anyone aware of why these links exist to begin with?