[katello-devel] async manifest import

[Tom McKay]

----- Original Message -----
> From: "Lukas Zapletal" <lzap at redhat.com>
> To: katello-devel at redhat.com
> Sent: Wednesday, July 4, 2012 3:24:13 AM
> Subject: Re: [katello-devel] async manifest import
> 
> Those are really good questions, but I would not them consider
> blockers.
> At least not the second point, which I think is appropriate.
> I was also thinking about async import - what happens if user will
> continue using Katello. But he already can! I mean, when any web app
> hangs showing me a spinner or something, I usually open another tab
> with
> it doing something else. And Katello user can do this too with old
> (sync) import.
> 
> Before locking anything, I would rather ask - what happens if we
> don't
> lock it and user does something? Did you try it?

When I say lock, I don't mean the entire page but perhaps the checkbox to enable repos is disabled. Have I tried it? No. Perhaps Petr has as the implementer of the feature.

> 
> We definitely need to do some manual testing scenarios in regard the
> new
> import trying to:
> 
> - mangle with repos
> - start syncing
> - registering and subscribing content
> - editing manifests being imported
> - ???
> 
> Once we find what the issues are, let's talk about how to fix them
> ;-)
> 
> LZ
> 
> On Tue, Jul 03, 2012 at 03:44:03PM -0400, Tom McKay wrote:
> > 
> > Several questions have come up during my work of integrating the
> > async manifest import into the two-pane subscriptions. I don't
> > think import can be considered complete before they are answered:
> > 
> > First, there is a disconnect between when the import finishes and
> > when the notices popup indicating success/failure. It may be
> > beneficial to move the notice code from the async thread up into
> > katello proper, allowing the UI to show the notice on its own
> > query schedule.
> > 
> > Second, and more importantly, there are probably many pages that
> > should have their functionality limited or disabled while a
> > manifest is being imported: Should any subscriptions be shown?
> > Should a subscription be allowed to be applied to a system or
> > activation key? What about repository enabling?
> > 
> > There are good reasons we've made the manifest import async, but
> > there are many reasons to lock down the interface while it is
> > going on.
> > 
> > _______________________________________________
> > katello-devel mailing list
> > katello-devel at redhat.com
> > https://www.redhat.com/mailman/listinfo/katello-devel
> 
> --
> Later,
> 
>  Lukas "lzap" Zapletal
>  #katello #systemengine
> 
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel
>