fix: bring back NutanixMachineDetails

Author: dkoshkin

api/v1alpha1/nutanix_node_types.go

@@ -12,6 +12,23 @@ import (
 )
 
 type NutanixNodeSpec struct {
+	MachineDetails NutanixMachineDetails `json:"machineDetails"`
+}
+
+func (NutanixNodeSpec) VariableSchema() clusterv1.VariableSchema {
+	return clusterv1.VariableSchema{
+		OpenAPIV3Schema: clusterv1.JSONSchemaProps{
+			Description: "Nutanix Node configuration",
+			Type:        "object",
+			Properties: map[string]clusterv1.JSONSchemaProps{
+				"machineDetails": NutanixMachineDetails{}.VariableSchema().OpenAPIV3Schema,
+			},
+			Required: []string{"machineDetails"},
+		},
+	}
+}
+
+type NutanixMachineDetails struct {
 	// vcpusPerSocket is the number of vCPUs per socket of the VM
 	VCPUsPerSocket int32 `json:"vcpusPerSocket"`
 
@@ -45,10 +62,10 @@ type NutanixNodeSpec struct {
 	SystemDiskSize resource.Quantity `json:"systemDiskSize"`
 }
 
-func (NutanixNodeSpec) VariableSchema() clusterv1.VariableSchema {
+func (NutanixMachineDetails) VariableSchema() clusterv1.VariableSchema {
 	return clusterv1.VariableSchema{
 		OpenAPIV3Schema: clusterv1.JSONSchemaProps{
-			Description: "Nutanix Node configuration",
+			Description: "Nutanix Machine configuration",
 			Type:        "object",
 			Properties: map[string]clusterv1.JSONSchemaProps{
 				"vcpusPerSocket": {