Rahul,
There are 2 primary trains of though for doing it this way.
1. For several reasons related to how the sosreport plugin architecture works, processing an entire sosreport in the way it would have to be processed to do this sort of work is problematic. Bryn and the sosreport team are working on that issue as time allows, but it's still several iterations away.
2. During our discussions with people who want this usability, having it decoupled from the process of creating an sosreport is desirable. Since many systems have limited or no outbound connectivity, an sosreport for one system is usually analyzed and uploaded from another. Another desire for uses is to maintain a 'gold' copy of the sosreport and then upload the 'cleaned' one for troubleshooting, etc. The current sosreport architecture would make it difficult to create two copies at the same time.
Does that answer your question?
Thanks,
Jamie Duncan, RHCE
Senior Technical Account Manager
Red Hat, Inc.
jduncan@redhat.com
w-804.343.6086
c-804.307.7079
tech support-888.GO.REDHAT
From: "Rahul Sundaram" <metherid@gmail.com>
To: "Development discussions related to Fedora" <devel@lists.fedoraproject.org>
Sent: Wednesday, June 4, 2014 2:34:05 PM
Subject: Re: self-introduction: Jamie Duncan
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct