There has been significant design work completed and shared previously
around the Remote Execution functionality [1]. This work has been
specifically focused on the data layer. The next step with this work is
designing the user interface. The goal behind the design was to take a
complex action and simplify it to as few steps as possible without limiting
flexibility. These designs account for not only immediate requirements, but
future functionality [2].
[1] http://theforeman.github.io/foreman_remote_execution/design/
[2]
https://dl.dropboxusercontent.com/u/5892944/Remote%20Execution-2015-08-04.pdf
Just some thoughts - hopefully constructive:
The multiple circle indicators on pages 16 & 20 of the pdf could be
combined into a single circle. This would use multiple colours to show the
percentage of Pending, Processing, Failed, and Successful. Perhaps grey =
pending, amber = processing, red = failed, green = successful?
I know that we regularly process jobs through Satellite 5.x with to
deliberately succeed or fail to tell us something that we need to discover.
We then pick all the successes or fails for the next task. The ability to
select systems for the next task based on whether they failed or succeeded
the current task would be great.
Also on page 8 you show a box that will list all of the servers selected on
the previous page/screen. This could run into the thousands on some
estates. The SSM in Satellite 5.x allows us to work with a union or
intersection between various groups, but we can then add/remove systems
from the set individually. On a large estate, I will not be able to create
Host Collections or Bookmarks for every large set that I want to work on.
D
ยทยทยท
On Tuesday, 4 August 2015 16:58:26 UTC+1, Kyle Baker wrote:
>
> There has been significant design work completed and shared previously
> around the Remote Execution functionality [1]. This work has been
> specifically focused on the data layer. The next step with this work is
> designing the user interface. The goal behind the design was to take a
> complex action and simplify it to as few steps as possible without limiting
> flexibility. These designs account for not only immediate requirements, but
> future functionality [2].
>
> [1] http://theforeman.github.io/foreman_remote_execution/design/
> [2]
> https://dl.dropboxusercontent.com/u/5892944/Remote%20Execution-2015-08-04.pdf
>
>
