What happened:
Vmware Plugin code require wwn property in the LUN/volume. Vmware uses wwn to set disk id and path, through which the backing LUN/volume is identified.
Model change required
Model.volumespec should have wwn field.
DB schema update required
Architecture change required
As of now the volume creation is an async call, we need to make it sync call so that the backend created wwn can be updated in reposnse.
driver change required
real backend ( storage arrays) will have wwn attached to LUN, driver can pick and fill volumespec.
Volume created by volume manager (lvm/ ceph?) can specify a unique id as scsi_id in the attachemnt and the same can be picked as wwn for the volume.
What you expected to happen:
volme POST/GET response should have wwn field.
How to reproduce it (as minimally and precisely as possible):
/kind feature
What happened: Vmware Plugin code require wwn property in the LUN/volume. Vmware uses wwn to set disk id and path, through which the backing LUN/volume is identified. Model change required
Model.volumespec should have wwn field. DB schema update required
Architecture change required
As of now the volume creation is an async call, we need to make it sync call so that the backend created wwn can be updated in reposnse.
driver change required
real backend ( storage arrays) will have wwn attached to LUN, driver can pick and fill volumespec. Volume created by volume manager (lvm/ ceph?) can specify a unique id as scsi_id in the attachemnt and the same can be picked as wwn for the volume.
What you expected to happen: volme POST/GET response should have wwn field. How to reproduce it (as minimally and precisely as possible):