The problem with many proprietary storage vendor is that they simply say: "We do not support Proxmox". It won't help if we implement a Cinder plugin, because the other endpoint is still on the storage box and controlled by the storage vendor. So we could never debug or fix problem on that side...
No, that is not possible.
PBS does a lot of pre-processing on the client side:
- compression
- optional data encryption
- chunking
- checksum generation (SHA256)
Only speeding up TLS would not help at all.
Für größere installationen empfehlen wir CEPH als Storage zu verwenden.
Siehe auch: https://ceph.io/en/discover/technology/
Konfiguration und management sind in unser GUI integriert.
Success Stories: https://proxmox.com/en/about/stories?f=7
The "cluster/resources" status is a summary of all nodes. There can be a little lag, becaue data need to be sent to all nodes.
The "/nodes/vps2/qemu/200/status/current" status is more accurate, because that API call directly connets to the node the VM is running on.
AFAIK there is already such check based on the storage configuration. Of cause this fails if you have a wrong storage configuration.
Anyways, I guess this check could be further improved...
First, I want to notice that the recommended way is to use a shared storage for HA, for example Ceph.
Please notice that all things you describe above simply cant happen in such (the recommended) setup.
It is simply considered to dangerous to auto-cleanup, because it involves deleting volumes.
Yes
Yes
Yes, you can use PBS to allow simple disaster recovery and migrating. But keep in mind that VM IDs from different hosts may clash if you only use one datastore. To avoid that, you can define more than one datastore, i.e. one datastore for each host (or cluster).
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.