Update patch set 4

Patch Set 4:

(4 comments)

Patch-set: 4
CC: Gerrit User 11655 <11655@4a232e18-c5a9-48ee-94c0-e04e7cca6543>

31378e9720b4dc6ab4f61ea0036b6cf116fe0a49

@@ -0,0 +1,90 @@
+{
+  "comments": [
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "26bab73f_c122c543",
+        "filename": "priorities/2024-2-workitems.rst",
+        "patchSetId": 4
+      },
+      "lineNbr": 7,
+      "author": {
+        "id": 11655
+      },
+      "writtenOn": "2024-04-22T16:13:37Z",
+      "side": 1,
+      "message": "nit: This connecting word could likely be removed. Past tense is established with the following word. We discussed the things and stuff. 😊",
+      "range": {
+        "startLine": 7,
+        "startChar": 44,
+        "endLine": 7,
+        "endChar": 48
+      },
+      "revId": "31378e9720b4dc6ab4f61ea0036b6cf116fe0a49",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    },
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "827294f0_403a8458",
+        "filename": "priorities/2024-2-workitems.rst",
+        "patchSetId": 4
+      },
+      "lineNbr": 55,
+      "author": {
+        "id": 11655
+      },
+      "writtenOn": "2024-04-22T16:13:37Z",
+      "side": 1,
+      "message": "Question for janders, dtantsur: Is there really an actionable thing we can do today. Update service is a neat idea, but maybe not something we can act upon in the next cycle.",
+      "revId": "31378e9720b4dc6ab4f61ea0036b6cf116fe0a49",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    },
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "42f85e87_e12fc35d",
+        "filename": "priorities/2024-2-workitems.rst",
+        "patchSetId": 4
+      },
+      "lineNbr": 65,
+      "author": {
+        "id": 11655
+      },
+      "writtenOn": "2024-04-22T16:13:37Z",
+      "side": 1,
+      "message": "I\u0027m not sure I can really commit to this.",
+      "range": {
+        "startLine": 62,
+        "startChar": 1,
+        "endLine": 65,
+        "endChar": 15
+      },
+      "revId": "31378e9720b4dc6ab4f61ea0036b6cf116fe0a49",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    },
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "c0539276_193fe09b",
+        "filename": "priorities/2024-2-workitems.rst",
+        "patchSetId": 4
+      },
+      "lineNbr": 201,
+      "author": {
+        "id": 11655
+      },
+      "writtenOn": "2024-04-22T16:13:37Z",
+      "side": 1,
+      "message": "We likely should use some other terminology here.\n\nSpecifically I think of \"flat\" as in static networking, but what most operators are is more dynamic networking, in other words ability to toggle ports to networks, as in most standalone operators the actual addressing and background resources can be static in complex deployments.\n\nMaybe what is needed is \"For complete usage in an enterprise use case, Ironic needs a means of networking control, which today is manual *unless* in a fully integrated OpenStack context. Furthermore, the OpenStack integrated context has some known issues which makes it harder to adopt, so we plan to look for solutions to this difficult operations problem during this development cycle.\"",
+      "range": {
+        "startLine": 201,
+        "startChar": 68,
+        "endLine": 201,
+        "endChar": 72
+      },
+      "revId": "31378e9720b4dc6ab4f61ea0036b6cf116fe0a49",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    }
+  ]
+}