For development and testing it can be useful to install pavics-sdi in a virtual machine. Here we describe the configuration for an OpenStack environment.
Attach 2 openstack volumes to the vm (take note of its name looking like
Mount them at
/geoserver_datausing the following command:
mount /dev/vdx /[geoserver_]data
New volumes must first be formatted using the command mkfs.ext4 /dev/vdx
Docker can take a lot of space to maintain all containers and the default directory
/var/lib/docker on the host can rapidly run out of disk space. The easy solution is to mount a bigger volume at this position:
Attach an openstack volume to the vm (take note of its name looking like
Stop the docker service : service docker stop
Mount the new volume at
/var/lib/dockerusing the following command:
mount /dev/vdx /var/lib/docker
Start the docker service: service docker start
To automatically mount volumes at reboot we modified the
/etc/fstab file to include the attached OpenStack volumes. For example (mind the tabspaces):
LABEL=cloudimg-rootfs / ext4 defaults 0 0 /dev/vdb none swap sw,comment=cloudconfig 0 0 /dev/vdd /data ext4 defaults 0 0 /dev/vdc /var/lib/docker ext4 defaults 0 0
The virtual machine is publicly visible by using the OpenStack external IP. But this IP is not visible from inside, the internal IP must be used. To resolve this issue, create a DNS entry mapping a hostname to the external IP and edit
/etc/hosts from inside the VM so that the same hostname maps the internal IP.
outarde.crim.ca is resolved as 220.127.116.11 (OpenStack external IP) everywhere but from the inside of this vm the
/etc/hosts config resolve this hostname to 192.168.101.91 (OpenStack internal IP).