3rd party device Integration

I’ve read all articles about 3rd party device Integration with CoprHD (Southbound API, Storage Driver SDK), https://coprhd.atlassian.net/wiki/display/COP/CoprHD+Home.

There are some questions about the integration our storage systems (3rd party) with ViPR/CoprHD.

Our storages have both REST API and CLI interfaces. There is no Cinder Integration. So, what way of native CoprHD driver development is better: to use CLI or REST API?

Our storages needs both CoprHD and OpenStack integration. So there are two ways:

• To make Cinder driver for our storages;
• To make native CoprHDstorages.

What way is better? Is native CoprHD driver better than Cinder driver for CoprHD integration with storage?

If we’ll make native CoprHD driver for our storage systems, do we need to make Cinder driver to integrate storages with OpenStack?

Or OpenStack integration for our storages will works through CoprHD – CoprHD interacts with all OpenStack services (compute nodes, network), CoprHD integrated with Raidix by native driver (no Cinder driver for Raidix), so OpenStack services can interact with Raidix through CoprHD?