mirror of https://github.com/apache/cloudstack.git
b27512c431
The adaptive storage framework hard-coded FiberChannel as the KVM-side pool type for every provider it fronts. With a separate NVMeTCP pool type now available (and a dedicated NVMe-oF adapter on the KVM side), teach the lifecycle to route a pool to the right adapter based on a transport= URL parameter: https://user:pass@host/api?...&transport=nvme-tcp -> StoragePoolType.NVMeTCP -> NVMeTCPAdapter on the KVM host When the query parameter is absent the default stays FiberChannel, so existing FC deployments on Primera or FlashArray continue to work unchanged. The choice is made in the shared AdaptiveDataStoreLifeCycleImpl rather than inside each vendor plugin so every adaptive provider (FlashArray, Primera, any future one) speaks the same configuration vocabulary. |
||
|---|---|---|
| .. | ||
| adaptive | ||
| cloudbyte | ||
| datera | ||
| default | ||
| flasharray | ||
| linstor | ||
| nexenta | ||
| ontap | ||
| primera | ||
| sample | ||
| scaleio | ||
| solidfire | ||
| storpool | ||