Bug #15734

Updated by Ward Vandewege over 2 years ago

Node manager drops a file called node.json in the container log collection, with an output like this:

<pre>
{
"created_at": "2017-04-12T04:37:11.016719000Z",
"crunch_worker_state": "busy",
"domain": "qr1hi.arvadosapi.com",
"etag": "xyrne3ax1barycf21f0xw49i",
"first_ping_at": "2019-06-01T18:53:52.714980000Z",
"hostname": "compute3",
"href": "/nodes/qr1hi-7ekkf-z6lokkesrtdw9ia",
"ip_address": "10.26.64.21",
"job_uuid": null,
"kind": "arvados#node",
"last_ping_at": "2019-06-01T18:56:02.166756000Z",
"modified_at": "2019-06-01T18:56:02.170027000Z",
"modified_by_client_uuid": null,
"modified_by_user_uuid": "qr1hi-tpzed-000000000000000",
"nameservers": [
"10.26.0.11"
],
"owner_uuid": "qr1hi-tpzed-000000000000000",
"properties": {
"cloud_node": {
"price": 0.192,
"size": "Standard_D4s_v3"
},
"total_cpu_cores": 4,
"total_ram_mb": 16018,
"total_scratch_mb": 32747
},
"slot_number": 3,
"status": "running",
"uuid": "qr1hi-7ekkf-z6lokkesrtdw9ia"
}
</pre>

This information originates from the Arvados node record. That table is no longer used by a-d-c. We need the 'properties' section to be available in that file for container cost accounting. A-d-c should populate the node.json file like this:

<pre>
{
"properties": {
"cloud_node": {
"price": 0.192,
"size": "Standard_D4s_v3"
},
"total_cpu_cores": 4,
"total_ram_mb": 16018,
"total_scratch_mb": 32747
},
}
</pre>

instead of just dropping an empty file in the container logs.

Back