fling logo of VMware Cloud Foundation Powernova

VMware Cloud Foundation Powernova

version 1.0 — February 23, 2021


VMware Cloud Foundation Powernova is a Fling built on top of VCF that provides the users the ability to perform Power Operations (Power ON, Power OFF) seamlessly across the entire inventory. It has a sleek UI to visualize the entire VCF inventory (which is the first of its kind for VCF) across the domains of VCF.

The UI is easy to use and elucidates the current Health and Power State of each node in the VCF inventory. Powernova lets the user work on the Power Operations on the components with domain specific inter dependencies automatically resolved.

Powernova also performs valid health checks on all nodes in the VCF inventory to ensure Power Operations are performed only on healthy nodes. Powernova takes minimal input (4 user defined inputs on their VCF system) and does all the magic for the users behind the scenes.

If any infrastructure maintenance activity, VCF migration activity, or power operations need to be performed only on specific domains in VCF, then Powernova is the one stop solution for all VCF users.


  • Compatible with VCF  4.1 and VCF 4.2 versions.
  • Deploy the VMware Cloud Foundation Powernova OVA on the Management vCenter of SDDC Manager.
  • Reserve a Valid IP Address and FQDN for VMware Cloud Foundation Powernova node and make appropriate DNS record for the same.
  • Any of the latest versions of Chrome/Firefox/Opera browser.
  • VMware Cloud Foundation Powernova is built for VSRN and does not have support yet for vXRail Hosts
  • VMware Cloud Foundation Powernova does not have support yet for WCP/Tanzu configured Workload Domains.
  • VMware Cloud Foundation Powernova does not have support yet for Nested ESXI Hosts.


  • Download the OVA attached in this Fling and deploy it on the Management vCenter of SDDC Manager.
  • Power ON the deployed OVA.
  • Login via vCenter Remote Console using credentials root/VMware123!
  • Edit Network configurations by providing valid Gateway, IP Address [IP Address/24] and DNS in /etc/systemd/network/10-eth0-en.network file. (See attached image-1)
  • Configure the Hostname using the command hostnamectl set-hostname HostName
  • Restart the following services to reflect the IP Address and Hostname on the vApp.

            systemctl restart systemd-networkd

  systemctl restart systemd-resolved

  • Do a PING check to Sddc Manager using ping -a SddcManagerHostName. The PING should be successful.
  • Start Powernova Service

 cd /opt/vmware/powernova


  • The output from the script should look like this (See attached image-2)
  • Once the service is up and running.  Open your browser and login to the url https://<powernova-hostname>
  • Provide the following inputs

Enter the VCF Hostname in the Host name field

Click on Verify Certificate Link

Verify the Certificate Thumbprint and Click on Accept

Enter the VCF SSO Username in Username field

Enter the VCF SSO Password in the User Password field

Enter the VCF Root Password in the Root User Password field

Click on Submit

Additional Information

  • By default VMware Cloud Foundation Powernova is deployed using self-signed certificates. If the user wants to configure CA certificates then they can place the cert.pem and key.pem files in /opt/vmware/powernova location and start the Powernova Service as mentioned above.
  • If the Workload Domain Inventory is large (more than 1500 ESXI Hosts) expect the first screen load of Inventory to take around 4 mins to load.

Similar Flings

Feb 05, 2019
fling logo of ESXi Embedded Host Client

ESXi Embedded Host Client

version 1.33.1

This version of the ESXi Embedded Host Client is written purely in HTML and JavaScript, and is served directly from your ESXi host and should perform much better than any of the existing solutions.

Sep 21, 2023
fling logo of USB Network Native Driver for ESXi

USB Network Native Driver for ESXi

version 1.13

This Fling supports the most popular USB network adapter chipsets found in the market.

May 23, 2022
fling logo of Virtual Machine Desired State Configuration

Virtual Machine Desired State Configuration

version 1.1.3 (4092207)

Virtual Machine Desired State Configuration (VMDSC) allows virtual administrators to specify VM CPU/Memory desired state which will take effect upon the next Guest OS reboot. This removes the burden of having to schedule a downtime window with the business/app owners.