Specifically talking to the new host wizard, it was designed to allow users
to basically choose a certain type of workflow which would populate the
wizard with the relevant data entry forms. This obviously only addresses
the creation of things, not necessarily the editing or viewing of them. I
Perhaps another (or additional) approach to consider is having different
"views" of the objects.
Consider hosts currently. Depending on the user's role for that moment, the
information and flows needed will be vastly different. The first engineer
may, for example, be the provisioning one. Perhaps
You're right, there are cases where it's better to separate facets and cases
where it's better to combine them. While we can define what page belongs to
which category I think more natural approach is simply say that we need to
allow both. For me, provisioning a host is a combination of
Marek, you lead me to an interesting conclusion:
I think we have to distinguish two things here - there are workflows (such
as provisioning, config management, fact reporting) and there are
information aspects.
An information aspect is a set of properties that describe a host in
different
I think these screenshots illustrate that pure option 2 can have negative
impact on usability. If I'm a puppet user, the puppet environment is one of
the most important thing to set. Having it in last tab completely separate
from hostgroup does not feel right. If some field of facet is part of
Thanks for the screenshots!
I like that the information is grouped together. I think that this could
easily be integrated into the host designs that were done.
On Sunday, November 12, 2017 at 1:36:08 PM UTC-5, ssh...@redhat.com wrote:
>
>
> OK, I have managed to create some screenshots of the
I prefer 2 with adding new extension points for the individual cases where
necessary.
M.
On Tue, Nov 14, 2017 at 12:45 AM, Walden Raines wrote:
> I see. Yeah I'm sticking with option 2, thanks for the screenshots.
>
> Cheers,
> Walden
>
> On Sun, Nov 12, 2017 at 1:36 PM,
I see. Yeah I'm sticking with option 2, thanks for the screenshots.
Cheers,
Walden
On Sun, Nov 12, 2017 at 1:36 PM, wrote:
>
> OK, I have managed to create some screenshots of the before and after
> state. Please don't judge the styling - it's more about the technical
>
OK, I have managed to create some screenshots of the before and after
state. Please don't judge the styling - it's more about the technical
abilities than the styling.
I will take Puppet as an example. Let's say we have puppet facet that has
the following data: puppet environment, puppet
Hey Shim,
Can you please include screenshots (or, even better, a quick video or gif)
of the new UI to make it easier for people to visualize who don't have the
code checked out?
Assuming I'm understanding your description of the two options, I would
also vote for option #2 as option #1 sounds
I have been playing with Facets the last few weeks and must say, that they
are really great. It's pretty easy to add dedicated functionality to the
host model and I want to use that for some of my plugins (Omaha,
Monitoring, something new, ...).
Everything is great so far except for the missing
11 matches
Mail list logo