Foundation preconfiguration JSON

  • 14 October 2019
  • 3 replies

Userlevel 2
Badge +1
Is there a KB or documentation providing the JSON format and any additional things that may be coded in? For example, in going through the portal to generate the JSON file it doesn't ask for NTP server of the hypervisor. In looking at the file, though, there's this line:

"hypervisor_nameserver": "",

I'd like to have our Nutanix deployments in code as much as possible (right now we're looking to various scripts for vSphere configurations). Being able to configure as much as possible up front and possibly make this a template for future deployments.

Best answer by HITESH0801 21 October 2019, 11:09

View original

This topic has been closed for comments

3 replies

Userlevel 4
Badge +5

Hello @tbailey1 

If you make manual entry to the json generated by it may not be readily importable on Foundation UI and is not recommended from Nutanix.

We try to keep the UI for aligned with major release of the actual foundation UI so that user can generate json.

However you could refer to the doc or sample of payload provided for image_node API provided at <foundation_ip>:8000/Foundation/docs.

You could also fill up the details on the Foundation UI and start an imaging session, which would generate persisted config in the backend which you could refer to and modify and try importing it to Foundation UI.

Userlevel 2
Badge +1

When I attempt to go to <foundation_ip>:8000/Foundation/docs I get a 404 error:

The path '/Foundation/docs' was not found.


When you say a persisted config that I could modify and try importing into there a way to export the config of an already configured environment?  Sorry, this may seem an obvious question and I’m still fairly new with the platform.



Userlevel 4
Badge +5


My mistake regarding the link
Can you try the following URL


I couldn’t find an option to export JSON configuration from a running cluster instead, I would suggest you create a sample JSON using the and taking help from the link provided above and use it to automate further deployments. 

You can also refer to the following documentation