search

threefoldtecharchive / 0-templates

0-robot templates
Apache License 2.0
1 stars 1 forks source link

vms using zdb disks over the private container ip #225

Open muhamadazmy opened 5 years ago

muhamadazmy commented 5 years ago

I found out that the VMs (minio) disks are using zdb disks which are served over the private container IP (not using port forwards).

This works fine UNTIL u restart the zdb container. which makes it get a new IP and then the disk stops working.

A good solution for this problem is to use port forwards and then a zdb service will always have the same ip:port even if zdb was restarted

Currently there is a problem with portforwards that it doesn't work from local node!!

Note: this is only a problem for vms that are hosted on the same node as their zdbs

muhamadazmy commented 5 years ago

Another solution for this problem is to always make sure a VM doesn't consume a ZDB that is running on the same node

zaibon commented 5 years ago

Another solution for this problem is to always make sure a VM doesn't consume a ZDB that is running on the same node

Problem with this, is you then need to make sure you vdisk is access using a fast network. which we cannot really ensure for now. That's why we install on the same node.

now the vm template has a recurring action that check the address of the vdisk and update it when needed. So even after a reboot we should be covered