Never mind, I see my issue!
Having trouble getting it to work, is there anyone I can reach out to specifically to speak with? Can't get postman to get the session ID
I have gotten past this, but now it seems nothing is listening on the DSC appliance port of 8010. it just times out, so I can't get the session ID and keys, to go on to the next steps. any ideas?
Hi Erik, Can you start by examining the VMDSC log file (/home/vmdsc/logs)? You can find instructions in section 8.3 in the User Guide. I suspect the VMDSC service is failing to establish a connection to your vCenter.
We would like feature such as enabling/disabling hot-add added in a future release. Would that be possible?
Hi Donn,
Thank you for the feedback! We will keep this in mind for future roadmap items.
Hi Alan, Today we only support CPU, Cores per Socket, and Memory, but we would love to hear more about your specific use case.
We can automate updating the OS on servers, but this remnant gets left behind. We have been told by VMWare that having a, for example, 2019 server that vmware thinks is a 2012 server will cause performance issues. We have hundreds of vms we have to change this on, everyone one we have to schedule a power down. change the setting, and power back up.
Thanks.
Thank you for that Alan! This will help us when considering future additions to our roadmap.
Why does memory have to be in powers of 4?