
Instead of having cells service started for every api samples test, whether or not it is used, only start it on test_cells. This saves some setup / teardown time, and makes things a bit more explicit. It also removes the cells service from service listing for a couple of api samples (az and hosts). That's more indicative of what people will see in real systems as cells is still a minority and experimental deploy option. Change-Id: Ie6d7e8978fd2b3441a141c69d4191266d76e7327
35 lines
907 B
JSON
35 lines
907 B
JSON
{
|
|
"hosts": [
|
|
{
|
|
"host_name": "b6e4adbc193d428ea923899d07fb001e",
|
|
"service": "conductor",
|
|
"zone": "internal"
|
|
},
|
|
{
|
|
"host_name": "09c025b0efc64211bd23fc50fa974cdf",
|
|
"service": "compute",
|
|
"zone": "nova"
|
|
},
|
|
{
|
|
"host_name": "a942ebfa00064d9d89a9e5a175cb9ba8",
|
|
"service": "cert",
|
|
"zone": "internal"
|
|
},
|
|
{
|
|
"host_name": "e73ec0bd35c64de4a1adfa8b8969a1f6",
|
|
"service": "consoleauth",
|
|
"zone": "internal"
|
|
},
|
|
{
|
|
"host_name": "396a8a0a234f476eb05fb9fbc5802ba7",
|
|
"service": "network",
|
|
"zone": "internal"
|
|
},
|
|
{
|
|
"host_name": "abffda96592c4eacaf4111c28fddee17",
|
|
"service": "scheduler",
|
|
"zone": "internal"
|
|
}
|
|
]
|
|
}
|