Quantcast
Channel: VMware Communities : All Content - vRealize Automation Tools
Viewing all articles
Browse latest Browse all 9859

Why put Model Manager on IaaS Web instead of IaaS Management?

$
0
0


I have implemented vCAC 5.2 and vCAC 6.0.1. In each case the location of the Model Manager was different (Manager vs. Web), but in both cases I was working with PSO. I am also reading the documentation for vRA 6.2.x and see that on page 18 of VMware_vRA_6.2_documentation/vrealize-automation-62-installation-and-configuration.pdf (EN-001649-04) that VMware has put the Model Manager on the IaaS Web layer. As the Model Manager service is the one that communicates with the IaaS database it seems really counter intuitive to put it on the Web layer and not the Management layer, following the principle of keeping the database as far away from the user interface as possible. For my question I am going to make the assumption that the reason is not related to performance simply because we have enough of the latest high-end hardware that it should not be a problem, either scaling up or scaling out.

 

1) Why does VMware put the Model Manager on the Web layer (for vRA 6.2.x)? What is so magical about the Web layer that they put the Model Manager here?

2) If I opt to install the Model Manager on the Manager layer (for vRA 6.2.x) does this in any way deminish supportability?

 

Thanks.


Viewing all articles
Browse latest Browse all 9859

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>