Hi,  It depends on the type of change.  Some general configuration tasks like physical pool or FAST policy creation need to be performed by the individual element manager. Changes like volume creation will be discovered by ViPR automatically - by default every hour - or with manual re-discovery.  In addition, ViPR can see if the capacity of a physical volume was decreased but it will not ingest such volumes automatically but instead will wait until the administrators provides an instruction to ingest.  Changes like deletion of the volume created by ViPR are not supported.  For brownfield environments where existing array volumes and ViPR ingested volumes exist both ViPR and the element manager need to be used.   The main functions of ViPR remain the same regardless of array, vendor or storage provider (i.e. OpenStack Cinder, native SMI-S).  For information of the specific operations supported by ViPR please see the Data Sheet and Compatibility Matrix.  Cindy
How does ViPR handle the underlying capabilities  of the storage it provisions/manages in an ongoing fashion such as when a change is made?
Array capabilities handled by ViPR