cloud: use machine_id for all agent communication
The original proto used provider-scoped provider_ids, these are being
replaced by a single machine_id, assigned by the BMaaS service.
Its API works in terms of machine_id, not provider_id (see
AgentHeartbeatRequest), so this needs to be changed.
Change-Id: If13942d02a8ac0e2901c549a92a67b6b10a1e196
Reviewed-on: https://review.monogon.dev/c/monogon/+/1263
Tested-by: Leopold Schabel <leo@monogon.tech>
Reviewed-by: Leopold Schabel <leo@monogon.tech>
diff --git a/cloud/agent/api/takeover.proto b/cloud/agent/api/takeover.proto
index 47b531f..788c5a3 100644
--- a/cloud/agent/api/takeover.proto
+++ b/cloud/agent/api/takeover.proto
@@ -5,13 +5,12 @@
// TakeoverInit is the message sent to the takeover process over an SSH session
// during initialization.
message TakeoverInit {
- // provider is the provider name the machine was created at.
- string provider = 1;
- // provider_id is the machine's provider-assigned ID.
- string provider_id = 2;
+ // Machine ID of this machine to be taken over as assigned by the BMaaS
+ // service.
+ string machine_id = 1;
// bmaas_endpoint is an address of the BMaaS service the agent should call
// back to.
- string bmaas_endpoint = 3;
+ string bmaas_endpoint = 2;
}
message TakeoverSuccess {