[sos-devel] sosreport manifest?

[Adam Stokes]

On 03/09/2012 03:10 PM, Jesse Jaggars wrote:
> On Fri, Mar 09, 2012 at 01:29:19PM +0000, Bryn M. Reeves wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 03/09/2012 12:51 PM, Adam Stokes wrote:
>>> On 03/09/2012 06:18 AM, Bryn M. Reeves wrote: This is something
>>> that's come up a few times to assist in making the data in a sos
>>> tarball self-describing and discoverable (and to support the
>>> eventual creation of a library and language bindings to provide
>>> uniform access to the data).
>>>
>>> What would we want in the manifest and what would we want it to
>>> look like?
>>>
>>> Cheers, Bryn.
>>>>
>>> Would this be something outside of the diagnose routine?
>>>
>> Yes - diagnose hasn't really seen much development lately and there
>> are ongoing discussions about removing it (other tools outside of sos
>> seem a better place for this functionality).
>>
>> The manifest would be descriptive metadata that tells consumers of a
>> sos tarball what it contains and where.
>>
>> Regards,
>> Bryn.
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.12 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAk9aBa8ACgkQ6YSQoMYUY95/YACgmvVUipsYss+5f9Q0keh8JZ5i
>> uD4An27py0K/PmCRu0ptu+56R14n5KDv
>> =9La9
>> -----END PGP SIGNATURE-----
>>
>> _______________________________________________
>> Sos-devel mailing list
>> Sos-devel at redhat.com
>> https://www.redhat.com/mailman/listinfo/sos-devel
> Hey folks,
>
> To help me get a better idea what are some of the interface methods you
> would anticipate having in the long run? How would you go about using
> the library to work with a sosreport archive?
>
> Jesse
>
TBH the first thing that comes to mind is http://www.splunk.com/ and not 
necessarily trying to integrate with them but a more homegrown approach 
where it's all inclusive with sosreport.

Thanks,
Adam