Up until now we've been using "Hosts" screen to launch mco commands
and show the results. But as we moved to asynchronous handling of
commands current approach to displaying the results is no longer
sufficient. It also prevents us from reviewing results of command
executions in the past.
I think the MCO UI would work better if:
we created a dedicated screen (or perhaps a tab on "Hosts" screen)
to display the history of results of MCO commands
The screen from the above can be used to launch new commands and
specify filter parameters, etc
Have "pre-canned" mco commands on "Hosts" screen (possibly
"Hostgroups", "Puppetclasses"): for example, we could execute "service
status" command on selected hosts (same selection as used for bulk
operations)
Such an approach would allow us to add more functionality around
command execution results down the line (for example we could repeat
command on hosts where it failed before). We'd also be able to use
simple UI for most common mco tasks on screens where these tasks make
the most sense.
Sounds sensible… the host index bulk actions menu isn't really the
primary UI for any action in Foreman today.
···
On 14/11/13 15:22, Dmitri Dolguikh wrote:
> Up until now we've been using "Hosts" screen to launch mco commands
> and show the results. But as we moved to asynchronous handling of
> commands current approach to displaying the results is no longer
> sufficient. It also prevents us from reviewing results of command
> executions in the past.
>
> I think the MCO UI would work better if:
> - we created a dedicated screen (or perhaps a tab on "Hosts" screen)
> to display the history of results of MCO commands
> - The screen from the above can be used to launch new commands and
> specify filter parameters, etc
> - Have "pre-canned" mco commands on "Hosts" screen (possibly
> "Hostgroups", "Puppetclasses"): for example, we could execute "service
> status" command on selected hosts (same selection as used for bulk
> operations)
>
> Such an approach would allow us to add more functionality around
> command execution results down the line (for example we could repeat
> command on hosts where it failed before). We'd also be able to use
> simple UI for most common mco tasks on screens where these tasks make
> the most sense.
>
> Thoughts?
> From: "Dominic Cleal" <dcleal@redhat.com>
> To: foreman-dev@googlegroups.com
> Sent: Thursday, November 14, 2013 10:31:20 AM
> Subject: Re: [foreman-dev] MCollective Integration UI
>
> > Up until now we've been using "Hosts" screen to launch mco commands
> > and show the results. But as we moved to asynchronous handling of
> > commands current approach to displaying the results is no longer
> > sufficient. It also prevents us from reviewing results of command
> > executions in the past.
> >
> > I think the MCO UI would work better if:
> > - we created a dedicated screen (or perhaps a tab on "Hosts" screen)
> > to display the history of results of MCO commands
> > - The screen from the above can be used to launch new commands and
> > specify filter parameters, etc
> > - Have "pre-canned" mco commands on "Hosts" screen (possibly
> > "Hostgroups", "Puppetclasses"): for example, we could execute "service
> > status" command on selected hosts (same selection as used for bulk
> > operations)
> >
> > Such an approach would allow us to add more functionality around
> > command execution results down the line (for example we could repeat
> > command on hosts where it failed before). We'd also be able to use
> > simple UI for most common mco tasks on screens where these tasks make
> > the most sense.
> >
> > Thoughts?
>
> Sounds sensible… the host index bulk actions menu isn't really the
> primary UI for any action in Foreman today.
Yep, and it's kind of awkward to implement large numbers of actions, like each thing you'd do with mco, into that dropdown.
···
----- Original Message -----
> On 14/11/13 15:22, Dmitri Dolguikh wrote:
Agreed. This menu was overly-crowded in the sprint demo.
···
On Thu, Nov 14, 2013 at 10:38 AM, Sam Kottler wrote:
>
>
> ----- Original Message -----
>> From: "Dominic Cleal"
>> To: foreman-dev@googlegroups.com
>> Sent: Thursday, November 14, 2013 10:31:20 AM
>> Subject: Re: [foreman-dev] MCollective Integration UI
>>
>> On 14/11/13 15:22, Dmitri Dolguikh wrote:
>> > Up until now we've been using "Hosts" screen to launch mco commands
>> > and show the results. But as we moved to asynchronous handling of
>> > commands current approach to displaying the results is no longer
>> > sufficient. It also prevents us from reviewing results of command
>> > executions in the past.
>> >
>> > I think the MCO UI would work better if:
>> > - we created a dedicated screen (or perhaps a tab on "Hosts" screen)
>> > to display the history of results of MCO commands
>> > - The screen from the above can be used to launch new commands and
>> > specify filter parameters, etc
>> > - Have "pre-canned" mco commands on "Hosts" screen (possibly
>> > "Hostgroups", "Puppetclasses"): for example, we could execute "service
>> > status" command on selected hosts (same selection as used for bulk
>> > operations)
>> >
>> > Such an approach would allow us to add more functionality around
>> > command execution results down the line (for example we could repeat
>> > command on hosts where it failed before). We'd also be able to use
>> > simple UI for most common mco tasks on screens where these tasks make
>> > the most sense.
>> >
>> > Thoughts?
>>
>> Sounds sensible.. the host index bulk actions menu isn't really the
>> primary UI for any action in Foreman today.
>
> Yep, and it's kind of awkward to implement large numbers of actions, like each thing you'd do with mco, into that dropdown.
>
>>
>> --
>> Dominic Cleal
>> Red Hat Engineering
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "foreman-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to foreman-dev+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
> --
> You received this message because you are subscribed to the Google Groups "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
