An administrator is unable to launch a Calm blueprint (new and old). Launching an existing blueprint under this condition fails with the error message:
The project for this blueprint does not have any associated Nutanix account.
Downloading and uploading the new blueprint also fails with
Launch with Variables' Profile expected to fall as Windows Server VWs attached with deleted Account.
Please modify them to use different account and try again.
Why is the administrator seeing this issue?
Where would a Calm Developer find logging related to blueprint package failures?
Refer to the exhibit.
A subset of Linux VMs are required to be gracefully shutdown each evening. A Playbook is created to shutdown the targeted VMs, however the error message shown in the exhibit is displayed when the Playbook is executed.
What is causing the error message?
An administrator had provided Linux VM console access to the OS Team. However, the team is unable to access one of the newly-created Linux VMs.
How can the administrator resolve this issue?
An administrator at a busy software development company is looking to roll out Calm for automation and estimates they will be creating 200 Projects, 500 Runbooks, 1500 Blueprints and automating the deployment of 7500 VMs for their development teams.
What size of Prism Central VM(s) is recommended to host the Calm environment?
Submit Cancel
Currently there are no comments in this discussion, be the first to comment!