For #1825

API for introspection is already implemented, this structure will store NUMA details that we will receive from introspection.
Below is the sample introspection data for NUMA Topology that is received from ironic-inspector after baremetal introspection of a node -:

"numa_topology": {
"nics": [{
"numa_node": 0,
"name": "p2p1"
}, {
"numa_node": 0,
"name": "p2p2"
}, {
"numa_node": 0,
"name": "p1p2"
}],
"ram": [{
"numa_node": 0,
"size_kb": 99289532
}, {
"numa_node": 1,
"size_kb": 100663296
}],
"cpus": [{
"numa_node": 1,
"thread_siblings": [3, 27],
"cpu": 6
}, {
"numa_node": 0,
"thread_siblings": [20, 44],
"cpu": 10
}, {
"numa_node": 0,
"thread_siblings": [8, 32],
"cpu": 3
}, {
"numa_node": 1,
"thread_siblings": [23, 47],
"cpu": 11
}]
}

Gophercloud is introspecting the baremetal-nodes and storing the introspection data in the respective pre-defined structures. There is no structure defined for details like, NUMA topology that we receive from Ironic introspection. To fetch the NUMA details for further use, we recommend adding the NUMA topology structure in the Gophercloud.

type Data struct {
...
NumaTopology  NumaTopology                 `json:"numa_topology"`
}

// Sub Types defined under Data and deeper in the structure for NumaTopology

type NumaTopology struct {
	NumaNics	[] NumaNICS 	`json:"nics"`
	NumaRAM  	[] NumaRAM  	`json:"ram"`
	NumaCPU  	[] NumaCPU  	`json:"cpus"`
}
type NumaNICS struct {
	NumaNodeID 		int    	`json:"numa_node"`
	Name       		string       `json:"name"`
}
type NumaRAM struct {
	NumaNodeID 		int     `json:"numa_node"`
	SizeKb     		int     `json:"size_kb"`
}
type NumaCPU struct {
	NumaNodeID      int 	`json:"numa_node"`
	CPUID                  int 	`json:"cpu"`
	ThreadSiblings   [] int  	`json:"thread_siblings"`
}