[katello-devel] New "Synchronization" item in Administer menu

[Eric Helms]

Can we incorporate some reference or discussion here about who the 'user' is for cross-org features and the permission set(s) that would be required to view, and/or interact with the cross-org features?  I know we have done that to some degree with users and roles, but as we add more functionality to cross-org views I think we should keep authorization in line with the conversation.

-Eric

----- Original Message -----
From: "Tom McKay" <thomasmckay at redhat.com>
To: "katello-devel" <katello-devel at redhat.com>
Sent: Wednesday, October 10, 2012 1:26:12 PM
Subject: Re: [katello-devel] New "Synchronization" item in Administer menu


I think most (all?) would agree that Synchronization is out of place in the Administer menu.

What I'll propose is that when switching to an "all orgs" functional category, that the nav structure changes to the attached screenshot.

The new Synchronization page would become a portlet (or two) on the all orgs dashboard (I did not mock this up but you get the idea, I hope).

You'll also see the All Organizations in the org selector (perhaps could be bold or something to differentiate it further). The existing cross-org features would become first class navigation elements.

To return to working in the context of a single org, use the org selector to choose org.

The effort to implement this would, hopefully, be low and would leave us with a paradigm to handle future cross-org features.

Kyle did mention that the "unified" aeolus/katello UI design work currently underway may impact this. I have no idea what this entails so others will need to chime in if what I'm suggesting steps on that work.

P.S. I don't think the "synchronize now" button really belongs on this page. The user should be forced to go to an org to kick off sync jobs. If that's not the case, this opens up a whole new can of worms.

----- Original Message -----
> From: "Tom McKay" <thomasmckay at redhat.com>
> To: "Kyle Baker" <kybaker at redhat.com>
> Cc: "katello-devel" <katello-devel at redhat.com>
> Sent: Wednesday, October 10, 2012 11:04:30 AM
> Subject: Re: [katello-devel] New "Synchronization" item in Administer menu
> 
> 
> 
> ----- Original Message -----
> > From: "Kyle Baker" <kybaker at redhat.com>
> > To: "Tom McKay" <thomasmckay at redhat.com>
> > Cc: "katello-devel" <katello-devel at redhat.com>
> > Sent: Wednesday, October 10, 2012 10:57:58 AM
> > Subject: Re: [katello-devel] New "Synchronization" item in
> > Administer menu
> > 
> > 
> > 
> > ----- Original Message -----
> > > 
> > > I understand the logic of adding this item to the Administer
> > > menu:
> > > The Synchronization status page spans orgs. However, it seems
> > > very
> > > out of place there and I am strongly voting against it.
> > > 
> > > My suggestion:
> > > 
> > > Make the Dashboard have user scope instead of org scope. By this
> > > I
> > > mean that the portlets do not have to be tied to a specific org
> > > necessarily, though some will of course. Perhaps each portlet
> > > could
> > > get a decorated header that includes the org name. This would
> > > also
> > > let an admin of more than one org plop down multiple "System
> > > Subscription Status" portlets, one for each org they are
> > > monitoring.
> > 
> > I understand your concern. I agree that the Administer tab is not
> > the
> > right place. It does have the correct org context as it is org
> > agnostic, but it's intended as housing for traditional tool
> > administration tasks not for monitoring status. The ideal solution
> > that fits the tools current structure would be filtering the sync
> > status page to only show the sync status for the org you are
> > currently viewing.
> > 
> > Your suggestion is interesting as it introduces the idea of having
> > a
> > cross organizational view. Adding the cross org view to the content
> > would involve heavily modifying what we have built as the user has
> > already gone though the process for choosing their org on log in
> > and
> > the informational hierarchy is setup to support that after log in
> > as
> > well. I could see this having it's own area where you could see
> > status on everything or having the ability to add/edit/delete
> > content. The user could have access to this as a "Status" button at
> > the top or even specify all orgs on log in. Though I think for this
> > issue the proper solution with the least dev overhead would be
> > filtering the sync status page to the org selected.
> 
> I'm not sure I understand: Are you saying remove it from Administer
> or not?
> 
> The final sentence, "filtering the sync status page to the org
> selected," what does that mean? The Content -> Sync Management ->
> Sync Status is where the current org's sync status is displayed. The
> new menu entry shows _all_ orgs. Are you suggesting upgrading the
> existing Sync Status single org page to allow cross-org views? I'm
> not against that as I feel the single-org strictness is a rule that
> deserves to be bent (or thrown out).
> 
> 
> > 
> > -Kyle
> > 
> > > 
> > 
> > _______________________________________________
> > katello-devel mailing list
> > katello-devel at redhat.com
> > https://www.redhat.com/mailman/listinfo/katello-devel
> > 
> 
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel
> 

_______________________________________________
katello-devel mailing list
katello-devel at redhat.com
https://www.redhat.com/mailman/listinfo/katello-devel