Tip |
---|
You can skip step if your kubernetes deployment in on a single VM or physical system. |
...
When setting up a kubernetes cluster, the folder /dockerdata-nfs must be shared between all the kubernetes nodes. This folder is used as a volume by the onap pods to share data and so there can only be one copy.
On this page we will attempt to do this by setting up nfs server on the kubernetes master node and then mount the exported directory on each of kubernetes’ nodes.
These instruction where written using VMs create from a ubuntu-16.04-server-cloudimg-amd64-disk1 image.
Table of Contents |
---|
Create OpenStack Volume
In our environment we provision an Openstack volume to allocate more space instead of instead of using the VM default backing store.
This is an optional and can be skipped.
...
Warning | ||
---|---|---|
| ||
More investigatio needed (as part of multi-nodes kubernetes cluser) as I'm having "Operation not permitted" error in sdnc-dbhost pod when deploying SDN-C cluster with the mounted /dockerdata-nfs from this instruction:
|
...
# | Purpose | Command and Example | |||||
---|---|---|---|---|---|---|---|
1 | On the server of the attached VM instance | ||||||
1.1 | Install exportfs | if exportfs is not installed, install it with the following command:
| |||||
1.2 | Modify /etc/exports file to export the /dockerdata-nfs mount point |
| |||||
1.3 | Export the /dockerdata-nfs mount point | ||||||
2 | On the server of the other VM instance | ||||||
2.1 | Install nfs-common | sudo apt install nfs-common | |||||
2.2 | Mount the volume as the /dockerdata-nfs directory | sudo mkdir -p /dockerdata-nfs sudo mount <mount point server IP>:/dockerdata-nfs /dockerdata-nfs | |||||
2.3 | Validate the mount |
|
Tips
unmount
Use the lazy (-l) option to force unmount the mount point.
...