Yes! Right now I have created a kubernetes cluster in Hetzner cloud and tested its CSI driver. As I expected, it works by attaching and detaching volumes from VM to VM. The volume follows where the pod is scheduled. I can give you access to evaluate it if you like. Thanks
On Mon, Mar 15, 2021 at 1:10 PM Wei ZHOU <ustcweiz...@gmail.com> wrote: > Hi Alireza, > > Do you mean the Herzner cloud volume > https://docs.hetzner.com/cloud/volumes/faq/ ? > > -Wei > > On Mon, 15 Mar 2021 at 09:50, Alireza Eskandari <astro.alir...@gmail.com> > wrote: > > > Hi Wei > > I had a search among different CSI drivers and their corresponding cloud > > providers API, I can say that your opinion is not right! > > For example in Hetzner cloud CSI driver you can see the > > "ControllerPublishVolume" function calls "s.volumeService.Attach" that > > tells Hetzner cloud manager to attach a virtual disk to the VM that the > pod > > is hosting on it: > > > > > https://github.com/hetznercloud/csi-driver/blob/16d7f9af6a3ac9a0a4e35c5b640c5ace9d7b45e7/driver/controller.go#L159 > > Also other features for PV is handled by calling corresponding APIs for > > virtual disk in Hetzner cloud. > > Since the functionality of volume service in Hetzner cloud is similar to > > CloudStack volume, I think that we can do the same for CloudStack CSI > > driver. > > Regards, > > Alireza > > > > On Sat, Mar 13, 2021 at 2:14 PM Wei ZHOU <ustcweiz...@gmail.com> wrote: > > > > > Thanks Alireza. > > > It is a long list. Almost all drivers in the list are for block storage > > > solutions or file shares. containers can access the resources directly. > > > > > > Different to them, cloudstack volumes are attached to VMs, not to pods > or > > > containers. containers cannot attach cloudstack volumes. All IaaS > > platforms > > > have the same problem. > > > In the list there are no drivers for other IaaS projects (openstack, > > > opennebula, etc) and public cloud providers (amazon ec2, google gcp or > > > azure compute, etc). > > > > > > In my opinion, CSI drivers should be implemented by storage providers , > > not > > > cloud providers. > > > > > > -Wei > > > > > > > > > > > > > > > On Fri, 12 Mar 2021 at 21:56, Alireza Eskandari < > astro.alir...@gmail.com > > > > > > wrote: > > > > > > > From a technical viewpoint and low level operations in hypervisor, > does > > > it > > > > need something more than detaching disk from source VM and attaching > it > > > to > > > > destination VM that has already been implemented in CloudStack? Also > > > these > > > > features can be available for CSI because CloudStack support it: > > > > Raw Blcok, Snapshot, Expansion, Cloning > > > > But a volume in CloudStack can only operate in Read/Write Single Pod > > mode > > > > not multiple pods. > > > > You can see a list of already developed CSIs in this link: > > > > https://kubernetes-csi.github.io/docs/drivers.html > > > > Regards > > > > > > > > > >
