metropolis: first pass API for reconfiguring cluster
This implements management.ConfigureCluster. This API is based around
Protobuf FieldMasks, which is a new thing in the Metropolis codebase
(node config mutation is performed via optional fields).
Whether this is the right way to do this is to be discussed.
Alternatives considered are:
1. Always insert a full new config, providing the old one as a base. The
downside of that is the potential conflicts that will spring up the
moment we have systems regularly mutate independent parts of the
config. Additionally, this might lead to some odd behaviour when
dealing with clients that don't have support for newer versions of
the config proto.
2. Use optional fields, like in Node role code. However, this has the
downside of duplicating protos (one for the config state, one for the
mutation request). Plus, protobuf optionals are still somewhat
unusual.
3. Provide individual requests for mutating fields (like with Node
labels). This also results in a lot of boilerplate code.
4. Something akin to JSON Patch, but for protobufs, which doesn't seem
to exist.
Change-Id: I42e5eabd42076e947f4bc8399b843e0e1fd48548
Reviewed-on: https://review.monogon.dev/c/monogon/+/3591
Tested-by: Jenkins CI
Reviewed-by: Tim Windelschmidt <tim@monogon.tech>
diff --git a/metropolis/proto/ext/authorization.proto b/metropolis/proto/ext/authorization.proto
index e526ec3..81de8bd 100644
--- a/metropolis/proto/ext/authorization.proto
+++ b/metropolis/proto/ext/authorization.proto
@@ -30,6 +30,7 @@
PERMISSION_DELETE_NODE = 9;
PERMISSION_UPDATE_NODE_LABELS = 10;
PERMISSION_NODE_POWER_MANAGEMENT = 11;
+ PERMISSION_CONFIGURE_CLUSTER = 12;
}
// Authorization policy for an RPC method. This message/API does not have the