filter out unsupported volume type for a given compute node
Hello Stackers, Our company is operating many sophisticated clusters with different storage types, such Ceph and SAN storage. What makes things trickier is that some compute node cannot use certain volume types. For example, some compute nodes do not have HBA, so they cannot take advantage of FC based SAN storage; the others do not have 10GbE ethernet, so they cannot connect to Ceph. Such deployment sometimes makes resize virtual machine quite tricky. So my question is what is best practice for this situation? Is it possible to determine if certain volume type is usable on a given compute node? Thank you very much for help. -- Best Regards, Jiatong Shen
Le jeudi 1 août 2024, 15:07:40 CEST Jiatong Shen a écrit :
Hello Stackers,
Our company is operating many sophisticated clusters with different storage types, such Ceph and SAN storage. What makes things trickier is that some compute node cannot use certain volume types. For example, some compute nodes do not have HBA, so they cannot take advantage of FC based SAN storage; the others do not have 10GbE ethernet, so they cannot connect to Ceph. Such deployment sometimes makes resize virtual machine quite tricky.
So my question is what is best practice for this situation? Is it possible to determine if certain volume type is usable on a given compute node? Thank you very much for help.
Hello, The common way to handle that is : - create host agregates for hosts having some specifics (FC access, Ceph access...) and metadata to identify them - create flavors with understandable names and metadatas targeting host agregates If you also want cinder volumes to target those storage, you'll need volume types with metadata targeting the volume backend. Of course if you create an epehemeral instance on a server that cannot access, let's say Ceph, you will not be able to attach a volume create with the Ceph type...
participants (2)
-
Gilles Mocellin
-
Jiatong Shen