From 1b2a35afdf5e8653e46a90b54f04578f7912083f Mon Sep 17 00:00:00 2001 From: Jay Faulkner Date: Mon, 13 Feb 2023 14:11:37 -0800 Subject: [PATCH] Add release note for node sharding Release note covers changes in the previous 4 commits in this chain. Change-Id: I5388e82e958acd930295215c9f9427080650866d --- .../notes/shard-support-a26f8d2ab5cca582.yaml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 releasenotes/notes/shard-support-a26f8d2ab5cca582.yaml diff --git a/releasenotes/notes/shard-support-a26f8d2ab5cca582.yaml b/releasenotes/notes/shard-support-a26f8d2ab5cca582.yaml new file mode 100644 index 0000000000..10104bf91e --- /dev/null +++ b/releasenotes/notes/shard-support-a26f8d2ab5cca582.yaml @@ -0,0 +1,14 @@ +features: + - Adds support for setting a shard key on a node, and filtering node or port + lists by shard. This shard key is not used for any purpose internally in + Ironic, but instead is intended to allow API clients to filter for a + subset of nodes or ports. Being able to fetch only a subset of nodes or + ports is useful for parallelizing any operational task that needs to be + performed across all nodes or ports. + - Adds support for querying for nodes which are sharded or unsharded. This + is useful for allowing operators to find nodes which have not been + assigned a shard key. + - Adds support for querying for a list of shards via ``/v1/shards``. This + endpoint will return a list of currently assigned shard keys as well as + the count of nodes which has those keys assigned. Using this API endpoint, + operators can see a high level listing of how their nodes are sharded.