You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the long operations triggered through the salt API are difficult to follow and are lacking of fine-grained progression or events, that could be consumed from a UI in order to provide more visibility to the IT Generalist. We could also imagine, those events are used to better understand the set of operations that were performed on the cluster.
One example is cluster expansion: when adding a node to the cluster, many different operations are triggered (sys pkgs installation, K8S master or etcd pod scheduling, etc ...). When some issue occurs during one of this step, it is important to have a clear notification on Salt API client-side to ease the understanding and investigation.
What should be done:
Implementation proposal (strongly recommended):
Test plan:
The text was updated successfully, but these errors were encountered:
Component:
'salt', 'ui'
Why this is needed:
Currently, the long operations triggered through the salt API are difficult to follow and are lacking of fine-grained progression or events, that could be consumed from a UI in order to provide more visibility to the IT Generalist. We could also imagine, those events are used to better understand the set of operations that were performed on the cluster.
One example is cluster expansion: when adding a node to the cluster, many different operations are triggered (sys pkgs installation, K8S master or etcd pod scheduling, etc ...). When some issue occurs during one of this step, it is important to have a clear notification on Salt API client-side to ease the understanding and investigation.
What should be done:
Implementation proposal (strongly recommended):
Test plan:
The text was updated successfully, but these errors were encountered: