Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

You can skip this step if your Kubernetes cluster deployment is on a single VM.


When setting up a Kubernetes cluster, the folder /dockerdata-nfs must be shared between all of the Kubernetes nodes. This folder is used as a volume by the ONAP pods to share data, so there can only be one copy.


On this page we will attempt to do this by setting up an NFS server on one of the Kubernetes node VM and then mount the exported directory on every other Kubernetes nodes' VMs. 

These instruction where written using VMs created from a ubuntu-16.04-server-cloudimg-amd64-disk1 image.

Any user can be used to run the steps in this page, as all the commands are "sudo".



On the NFS Server

The actual /dockerdata-nfs folder will live on one of the Kubernetes nodes' VMs which will also be running the NFS server to export this folder.

Choose one VM, from the to-be-Kubernetes node VMs, to be the NFS server and execute the steps in this section on this VM. 

Set up the /dockerdata-nfs Folder

Choose one of the following to create the /dockerdata-nfs folder on this VM:

Use local directory

Run the following command as root:

sudo mkdir -p /dockerdata-nfs
Use separate volume

Following instruction from Create an OpenStack Volume to:

(where the VM Instance is the one that you have chosen)

Setup the NFS Server and Export  /dockerdata-nfs Folder

Execute the following commands:

nfs server
sudo apt update
sudo apt  install nfs-kernel-server

sudo vi /etc/exports
# append the following
#  /dockerdata-nfs *(rw,no_root_squash,no_subtree_check)

sudo vi /etc/fstab 
# append the following
#  /home/ubuntu/dockerdata-nfs /dockerdata-nfs    none    bind  0  0

sudo service nfs-kernel-server restart
 An example of validate NFS server running

$ ps -ef|grep nfs
root 2205 2 0 15:59 ? 00:00:00 [nfsiod]
root 2215 2 0 15:59 ? 00:00:00 [nfsv4.0-svc]
root 13756 2 0 18:19 ? 00:00:00 [nfsd4_callbacks]
root 13758 2 0 18:19 ? 00:00:00 [nfsd]
root 13759 2 0 18:19 ? 00:00:00 [nfsd]
root 13760 2 0 18:19 ? 00:00:00 [nfsd]
root 13761 2 0 18:19 ? 00:00:00 [nfsd]
root 13762 2 0 18:19 ? 00:00:00 [nfsd]
root 13763 2 0 18:19 ? 00:00:00 [nfsd]
root 13764 2 0 18:19 ? 00:00:00 [nfsd]
root 13765 2 0 18:19 ? 00:00:00 [nfsd]
ubuntu 13820 23326 0 18:19 pts/0 00:00:00 grep --color=auto nfs
$


On the Other VMs

Mount the /dockerdata-nfs Folder

On each of the other Kubernetes cluster node VMs, mount the /dockerdata-nfs folder that is being served from the NFS server.  

mount nfs mount
sudo apt update
sudo apt install nfs-common 
sudo mkdir /dockerdata-nfs
sudo chmod 777 /dockerdata-nfs


# Option 1:
sudo mount -t nfs -o proto=tcp,port=2049 <host|IP of NFS server>:/dockerdata-nfs /dockerdata-nfs
sudo vi /etc/fstab
# append the following
#  <host|IP of NFS server>:/dockerdata-nfs /dockerdata-nfs   nfs    auto  0  0


# Option 2:
#  (verified on Ubuntu 16.04 AWS EC2 EBS volume)
sudo vi /etc/fstab
# append the following
# cdrancher.onap.info:/dockerdata-nfs /dockerdata-nfs   nfs    auto  0  0
sudo mount -a

Tips

unmount

Use the lazy (-l) option to force unmount the mount point.

For example,

sudo umount -l /dockerdata-nfs


  • No labels