I have completed designs around evolving how we are displaying Capsule
(Smart Proxy) functionality [1]. This work has been specifically focused on
exposing existing data. In the future we plan to provide a more robust
editing capability. These designs account for not only immediate
requirements, but serve as a base for future plans.
[1] https://dl.dropboxusercontent.com/u/5892944/Capsule-2015-09-18.pdf
Note that I don't use smart proxies much so feedback is limited.
The current UI has four columns: Name, URL, Features, and action choice box. Besides Name, I don't see the other information presented prominently (or at all?).
In new UI I see column for Locations but not Organizations. Nor do I see where to set Org and Loc amongst the tabs.
The word "environment" is used throughout in an unqualified way: Is it a puppet environment or a lifecycle environment?
The hosts table columns look like they are content information (katello) and not puppet (foreman). With the upcoming merge of host and content-host, how will this table (and others) accomodate the various flavors of information?
Thanks Kyle, comments bellow:
page 2
Location: NYC/DC1, NYC/DC2, which means it serve content for both DC1 and
DC2.
(Granted its not the best example in the world, as it could be in the top
level NYC, but maybe you also have NYC/Floor-50 which would not want to
consume that proxy).
Its not clear to me what is the difference between service status and
capsule status? am i expected to see more info on hover?
What about the features, how would i find the proxy with my features? using
search? many times you just have one proxy with one feature etc.
page 3
start date- time from uptime, registration or… ?
timezone - why would i care? most servers are UTC anyway?
Status - deactive? what does this really means? imho its not a simple
process as you need to take care for every service running on the proxy.
(or would it be fade if any hosts are attached to any of its services)?
why do we have deactive twice? I don't think its a common operation at all,
does it mean we can't delete a capsule ? or rather deactive changes to
delete afterwards?
Packages info (bottom left)
Storage:
is it available storage for pulp (e.g. just the pulp volume) ? how often is
it refreshed?
Puppet:
uniq classes per environment? or all classes (duplicated across
environments etc?) I think this area needs to be extended much more with:
number of clients in the last xx minutes
avg time per client (puppet server, vs client) maybe graphs 
page 4
Hosts can belong to multiple proxies (based on feature), which one are we
showing here?
page 5
domains:
what do test mean? what are we testing?
what is active? do we test the process is running?
subnets:
I would suggest to show number of leases/ reservations out of the pool size.
what is network interface controller??
what is additional details?
page 6
I assume this are lifecycle environments?
page 8
does not make any sense to me? what are we trying to show?
additional questions:
thanks,
Ohad
I have completed designs around evolving how we are displaying Capsule
(Smart Proxy) functionality [1]. This work has been specifically focused on
exposing existing data. In the future we plan to provide a more robust
editing capability. These designs account for not only immediate
requirements, but serve as a base for future plans.[1] https://dl.dropboxusercontent.com/u/5892944/Capsule-2015-09-18.pdf
>
>
> Note that I don't use smart proxies much so feedback is limited.
>
> The current UI has four columns: Name, URL, Features, and action choice
> box. Besides Name, I don't see the other information presented prominently
> (or at all?).
>
The goal behind the design was to limit the content displayed to the bare
minimum information.
> In new UI I see column for Locations but not Organizations. Nor do I see
> where to set Org and Loc amongst the tabs.
In this design users can only view what exists not modify or update. They
will add all content in the CLI processes.
>
> The word "environment" is used throughout in an unqualified way: Is it a
> puppet environment or a lifecycle environment?
>
Noted.
>
> The hosts table columns look like they are content information (katello)
> and not puppet (foreman). With the upcoming merge of host and content-host,
> how will this table (and others) accomodate the various flavors of
> information?
>
Good feedback. It is hard to say what the future hold specifically related
to timing so I designed using the most relevant Host page. This may change
depending on development schedules.