[Maas-devel] xml-to-yaml

[Jeffrey Lane]

Just to be clear, I didn't mean get rid of the raw XML, merely don't
display it in favor of something easier to read... I think the XML is
way too valuable to just remove and didn't mean it that way (if that's
how you interpreted that).

Out of curiosity, is the tag creation manual or auto (meaning does a
user have to see the XML to create the tags, or is MAAS doing some
parsing in the background to generate tags that the user can add some
other way?

On Mon, Aug 25, 2014 at 11:19 AM, Andres Rodriguez
<andres.rodriguez at canonical.com> wrote:
> For the time being, I think it is a good idea to keep the raw results as
> they are being used for tag creation. When we create tags we use Xpath to
> navigate through the xml output. Once we decide to start using the YAML
> output to do the tag creation filtering, we can get rid of the raw output.
>
> Thanks
>
>
> On Mon, Aug 25, 2014 at 11:05 AM, Newell Jensen
> <newell.jensen at canonical.com> wrote:
>>
>> Jeff,
>>
>> Valid points.  Reason we were doing the tabs is because I was instructed
>> to do it that way but I do agree with you that an another alternative could
>> be to have it so you could just download it somehow.
>> Andres, what are your thoughts on this?  Do you like having the tabs or do
>> you you think a "Download Raw" link to download the xml would be more
>> sufficient?
>>
>>
>> On Mon, Aug 25, 2014 at 6:53 AM, Jeffrey Lane <jeffrey.lane at canonical.com>
>> wrote:
>>>
>>> On Mon, Aug 25, 2014 at 8:58 AM, Andres Rodriguez
>>> <andres.rodriguez at canonical.com> wrote:
>>> > Instead of providing totally different pages for the commissioning
>>> > results
>>> > per node (xml_lshw, yaml_lshw), I'd suggest you provide just one page
>>> > with
>>> > Tabs to differentiate between the output type (Exactly the same way as
>>> > in
>>> > the Node View)
>>>
>>>
>>> My only comment is a question about why show both at all?  Just IMO,
>>> but as a user:
>>> 1: I HATE having to read XML
>>> 2: If XML is provided, how about just as a download option so I can
>>> parse or feed it into whatever tool I have.
>>> 3: Since you're already converting it to YAML, which is a good bit
>>> easier to read, why also have an XML view of the same data?
>>>
>>> I guess the point to 3 is that, why provide two different views of the
>>> exact same data, one that is a headache to read and one that is
>>> slightly better/easier to read?
>>>
>>> IMO, As Andres said, a simple OK link to the results would be best,
>>> but I'd change it so that instead of tabs, you simply displayed the
>>> YAML converted data and provide a download button for either the YAML
>>> or raw XML.
>>>
>>> Anyway, I don't have anything more useful than that to add, Andres had
>>> some very good points.
>>>
>>> Perhaps one other question, since you're going to the trouble of
>>> parsing the XML into YAML to make it readable, why not just parse it
>>> the rest of the way and provide really readable output instead?  In
>>> reality, you're really just swapping one markup language for another,
>>> it's just that the new one happens to be more friendly to the eyes
>>> than the original one.  But, that is just a curiosity point, and maybe
>>> a suggestion for the next iteration of this output display, once they
>>> YAML bits are solidified and merged.
>>>
>>> Either way, looks like a great start!
>>>
>>> Jeff
>>>
>>> --
>>> "Entropy isn't what it used to be."
>>>
>>> Jeff Lane - Server Certification Team Lead, Tools Developer, Warrior
>>> Poet, Lover of Pie
>>> Phone: 919-442-8649
>>> Ubuntu Ham: W4KDH                          Freenode IRC: bladernr or
>>> bladernr_
>>> gpg: 1024D/3A14B2DD 8C88 B076 0DD7 B404 1417  C466 4ABD 3635 3A14 B2DD
>>
>>
>
>
>
> --
> Andres Rodriguez
> Engineering Manager, HWE Team
> Canonical USA, Inc.



-- 
Jeff Lane - Server Certification Team Lead, Tools Developer, Warrior
Poet, Lover of Pie
Ubuntu Ham: W4KDH
Freenode IRC: bladernr or bladernr_
gpg: 1024D/3A14B2DD 8C88 B076 0DD7 B404 1417  C466 4ABD 3635 3A14 B2DD