[sos-devel] sosreport manifest?

[Jesse Jaggars]

On Mon, Mar 12, 2012 at 02:17:09PM +0000, Bryn M. Reeves wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 03/12/2012 01:00 PM, Andrew Hecox wrote:
> >> tar archives provide a journal/manifest of the names of files,
> >> and where they are. Because tar is a well known file format,
> >> there are already language bindings in place for everything
> >> anyone would want to do.
> 
> Unfortunately this does not solve the problem; as I mentioned before
> the tar structure should be considered an ABI. It is subject to change
> and is not discoverable in a way that will support upcoming changes in
> a robust way.
> 
> For instance, sos will soon need to have the ability to collect the
> same configuration file from multiple locations and to record this
> information in the archive. While it would be possible to search all
> archives for all possible paths this is inefficient and prone to
> failure. For instance, if we change the set of command line options
> used to run a program the path in the tarball will changes as might
> the content present at that path.
> 
> This also cannot address more complex manipulations of the data than a
> simple "read this data from this path". In looking at the tools that
> consume sos data there is huge overlap and commonality in the
> information that they retrieve and the processing that they carry out.
> Reinventing this in each project that has overlapping requirements is
> not maintainable long-term and will hinder sos's ability to adapt to
> meet changing requirements (since there will be pressure to not make
> changes that would affect downstream consumers).
> 
> Regards,
> Bryn.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iEYEARECAAYFAk9eBWUACgkQ6YSQoMYUY96fIQCgkMGxu0sSEFBSkU/NZ9HS39c9
> vHMAn0i/+ee4waOa5HrU0jh16tLXi6QX
> =qeBC
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Sos-devel mailing list
> Sos-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/sos-devel

I'm pretty ignorant here in that I'm not familiar with any of the
consumer tools. I've only seen the sosviewer thing that was recently
'integrated' into SFDC. What are some of the other tools that people
have written? I'd like to take a look at the sorts of things that the
are doing more specifically to help me get a better understanding of
what folks actually want.

Jesse
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/sos-devel/attachments/20120312/d8543b51/attachment.sig>