- Solidfire Element OS
- VASA Provider (VP)
- The VASA Provider runs on all SF cluster nodes and logs to /var/log/sf-vasa.info. The VP is responsible for translating VASA requests into zero or more SF API calls to perform various actions like creating and deleting virtual volumes. Only the VP on the CM node actively processes VASA requests from vSphere.
- VASA requests are sent by ESX hosts and vCenter servers to the VP on the CM using SOAP protocol. The VASA requests and responses are logged to sf-vasa.info. An ESX host or vCenter server must create a VASA session with the VP before making VVol-related requests. VASA sessions are created using the setContext VASA request.
The Service: sfvasa Provider provides monitoring and management of vVols from VMware, vVols will continue to work even without it. If the sfvasa provider is not working you will not be able to manage (add, delete or modify) vVols from v-Center.