Hello,

I been testing the VMDSC solutions for a few weeks now. This a great solution. I have perform testing with this solution on vRealize Orchestrator and PowerVMDSC.

I would prefer to use Orchestrator for this rightsizing project that I am working on. Rightsizing works with Orchestrator with no issues. I have few questions that you can answer.

1. Can the VMDSC appliance connect to multiple vCenters or just one vCenter per VMDSC?
2. Will I need to deploy separate Orchestrator appliances per vCenter for the workflows to execute correctly for that vCenter? I have more than one vCenter that I will to apply this to.

Hello Antonio,

as for VMDSC, a single Orchestrator appliance can serve multiple vCenters. However after importing the VMDSC package, I had to clone the VMDSC Configuration (found in vRO under Assets -> Configuration) for every vCenter. Since every vCenter needs a unique VMDSC appliance and the VMDSC appliance has to be listed in the VMDSC configuration. After that I also had to clone the VMDSC workflows for every vCenter, because the workflows are tied to the VMDSC configuration for the respective vCenter.

Thanks Steven.

Are you importing the workflows into vROPs and using vROPs recommendation or making your own recommendation?
I want to see how everyone is rightsizing their VMs.

Thanks

Steven,

Did you have to create a new package also in VRO or add the configurations and workflows in the existing package?

There is a one to one relationship between a VMDSC appliance and a vCenter.

I'm not 100% sure on orchestrator, I feel like the answer is no. With vRA 7.x deployments I had one orchestrator appliance talking to multiple vCenters. Way back in the vCO days (2015) there were some issues with multiple vCenters and SSO but I don't think any of those issues impact vRO currently, but I no longer work with vRO every day so I can't say with 100% certainty.

Hello,

Are there any issues / or recommendations when upgrading an existing VMDSC appliance?

There isn't an upgrade path from one version to another. What I've been doing is using powervmdsc to do a Get-VMDSCAll and list the current configs, then piping that output to a CSV file. Then I use that CSV file as the input to a Clear-VMDSC for-each loop. So now the current VMDSC appliance has no pending configs, and I have a CSV of the pending configs I want on the new one. I then power off the current appliance, and deploy the new one. (Before powering off the old appliance it is important that there are no pending configurations).

Once the new appliance is deployed use the Add-VMDSC command on a for-each loop with your CSV files of configurations you exported from the old appliance.

Hello Heath,

Can you provide examples of for each loop?

Thanks

I figured it out. Thanks

Hello,

I need some help resolving this SSL certificate issue. I copied the CA root to /etc/ssl/certs directory. I still get x509: certificate signed by unknown authority.

I have root and immediate cerficates.

Can help me in resolving this issue?

Thanks

I was able to get my certificate chain to work with the VMDSC appliance.

I am also having issues with certificates, but I am getting the "Unable to verify the first certificate" error when I run getVMID, but I have no issue running getVCSessionID.

What did you have to do to resolve your certificate errors? It might be a good place for me to start...

It sounds like that you have root, intermediate certficates.

Here is what I need to resolve the issue.

1. Get your root and intermediate certificates.
2. Copy them to /home/vmdsc/config folder on the VMDSC appliance
3. SSH to VMDSC appliance
4. cd to /home/vmdsc/config
5. run command cat <name of your intermediate.pem certifcate name> > trustchain.pem
6. run command cat <name of your root.pem certificate name> > trustchain.pem
7. run command curl -k https://<your vcenter fdqn>/afd/vecs/ca --output ca.cer
8. run command openssl x509 -in trustchain.pem -out ca-cert.pem

Now if you go to /home/vmdsc/logs and run cat vmdsc.logs, Port 8010 should come up.
Now, if you reboot the VMDSC, you will have to do this again.

If your certificate doesn't have a root and intermediate, just copy the SSL certificate for that vcenter to /home/vmdsc/configs and execute steps 7 and 8. It has worked for me everytime.

We have 10-14 vCenters. I am having to deploy a VMDSC per vCenter.

Can you tell me how you are automation the rightsizing of the VMs? I am look for a way to automated.

Thanks

I am also having issues with certificates, but I am getting the "Unable to verify the first certificate" error when I run getVMID, but I have no issue running getVCSessionID.

What did you have to do to resolve your certificate errors? It might be a good place for me to start...

I see the following error message in the logs

Error connecting to VCPost "https://vcenter fqdn /sdk": x509: certificate signed by unknown authority

vROPS has not issue with this vCenter certificate.

Trying to connect to vmdsc port 8010 times out.

Any help to resolve this issue would be great.

Thanks

How can I add the CA root certificate to the Trusted Root store in the VMDSC appliance? I am getting unable to the following errors below when I run openssl s_client -showcerts -servename server.crt -connect vcenter servername:443 > cacert.pem

get local issuer certificate
unable to verify the first certificate

How can I add the CA root certificate to the Trusted Root store in the VMDSC appliance? I am getting unable to the following errors below when I run openssl s_client -showcerts -servename server.crt -connect vcenter servername:443 > cacert.pem

get local issuer certificate
unable to verify the first certificate