[OpenAFS] A call to potential GSOC students: Modifying the output of vos commands to include server UUIDs

[Derrick Brashear]

Hey GSoC candidates! here's a simple project for you. vos examine
already includes a "-format" switch to display a fixed, parseable
format. add a "-xml" switch, and output in xml! Everything you need to
change is in src/volser (vos.c and vsprocs.c). Ideally you won't
require an external library to do this, but instead can just output
xml directly, as we are unlikely to have any given xml library on all
supported platforms.

On Wed, Apr 14, 2010 at 11:50 AM, Andy Cobaugh <phalenor@gmail.com> wrote:
> On 2010-04-14 at 11:23, Jeffrey Altman ( jaltman@secure-endpoints.com )
> said:
>>
>> On 4/14/2010 10:51 AM, Steve Simmons wrote:
>>>
>>> On Apr 13, 2010, at 5:28 PM, Jeffrey Altman wrote:
>>>
>>>>>
>>>>> I'm a long-time fan of having a switch that causes tools to dump their
>>>>> data in an easy-to-machine-parse format. That isn't always doable, but when
>>>>> it is, it's a big win.
>>>>
>>>> As Andrew pointed out in another reply in this thread, the -format
>>>> switch is support to provide that but it fails to provide a consistent
>>>> (value - data) pair per line.
>>>
>>> Exactly my point. We currently snarf off all that data nightly via script
>>> that parses the output from vos e -format. It works but was a pain.
>>>
>>> Note, tho, that some data doesn't adapt well to single-line output. For
>>> example,
>>>
>>> just doesn't map well to single-line. We currently deal with this by
>>> creating four records, each will all the data from the rest of the output
>>> and the specifics of the four entries above.
>>>
>>> Steve
>>
>> Anyone want a -xml option?
>
> Yes, please. As much as I am not a fan of XML, it would make some of our
> lives easier for those of us using languages that include xml parsers.
>
> --andy
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>



-- 
Derrick