[katello-devel] Another reason for manifest-import to be asynchronous

Bryan Kearney bkearney at redhat.com
Fri May 25 12:58:27 UTC 2012


On 05/24/2012 08:43 AM, Ivan Nečas wrote:
> Hi,
>
> I've been working on z stream bug
> https://bugzilla.redhat.com/show_bug.cgi?id=823890, the solution
> (https://github.com/Katello/katello/pull/144) is to remote the products
> (including repositories) that were removed from the newly-imported
> manifest. This slows down of the manifest import - time is needed for
> removing the repositories which is not big problem for unsynchronized
> repos, but there might be significant change for repositories already
> synchronized.
>
> I would like to get more ideas on this. Is this the right time to move
> manifest import to asynchronous state.
>
> Also removing repositories (not only in this case) causes records about
> their promotions in changeset to vanish. We probably need other (softer)
> mechanism for removing repositories that still leaves some marks that
> the repository was there once.
>
The user can really not do much else while the import is going on. But.. 
i would be happy to add this to the backlog if the team wants to.

-- bk




More information about the katello-devel mailing list