Investigate the roadmap of integration with fluid project

[sighingnow]

Describe your problem

The fluid project manages a data cache layer (provided by alluxio or jindofs) for on-top bigdata applications. Fluid abstract the data caching services as a Dataset, and mount it to worker pods via a CSI driver. Besides, based the affinity of volumes, fluid also considering the data locality when scheduling.

Vineyard also consider the data locality when scheduling. Currently vineyard abstracts objects as CRDs to make them visible for kubernetes. And volumes also fit vineyard's design well. Integrating with fluid would benifits vineyard to make the sheduler plugin and vineyard-operator more lightweight.

To be abbreviated, vineyard could work as a fluid runtime. Things need to be done to work together with fluid are as follows (if
I understand it correctly):

• allowing mount an vineyard object as a volume. Vineyard server may need to provided a seperated IPC service for that.
• implements a controller for vineyard in fluid (a fluid runtime).

Additional context

N/A

[sighingnow]

Closing as we have getting started on the integration with fluid, see also #1596.