Thanks Yacine! I'll take a detailed look soon. One immediate request: please use a more friendly format for review than JSON schema. I've had good luck with orderly, see http://orderly-json.org/ <http://orderly-json.org/> -- richard
> On Feb 6, 2015, at 10:50 AM, Yacine Kheddache <[email protected]> > wrote: > > Hi Guys, > > FYI, all json schemas are online on github : > https://github.com/Alyseo/zfs/tree/json > <https://github.com/Alyseo/zfs/tree/json> > https://github.com/Alyseo/zfs/blob/json/json/STATUS.md > <https://github.com/Alyseo/zfs/blob/json/json/STATUS.md> > > We are now waiting for community validation before we can keep going on > implementation : please > do some pull requests on each schemas if you have any suggestions/changes/... > > Thank you > Regards, > Yacine > > On Fri, Nov 21, 2014 at 9:39 AM, Francois Billard > <[email protected] <mailto:[email protected]>> wrote: > > Actually, we want to match as much as possible the (LD)JSON output to the zfs > command. > "zfs list" and "zfs get" are two distinct commands, so you have two separate > output to jsonify. > > We propose to the community to jsonify the zfs/zpool comands as they are. and > we will envision all kind of shortcuts after this step. > > -Francois > > > > 2014-11-19 22:05 GMT+01:00 Matthew Ahrens <[email protected] > <mailto:[email protected]>>: > A high-level question about what we want in the JSON output: > > Do we envision eventually adding a separate "zfs get -J" to get more detailed > JSON-formatted information about properties, or should we include that in the > "zfs list -J" output? Specifically, the property source (i.e. "zfs get -o > source"), and the received value (i.e. "zfs get -o received"). > > --matt > > On Fri, Nov 14, 2014 at 5:40 AM, Francois Billard > <[email protected] <mailto:[email protected]>> wrote: > Hi, > > A new version has been pushed by the Alyseo team, regarding the previous > comments, we have integrated the nvpair library as suggested. > > Advice and comments are welcome to continue the process of JSONification of > others command. > > Currently, command "zfs list" is implemented. > > https://github.com/Alyseo/zfs/tree/json > <https://github.com/Alyseo/zfs/tree/json> > > Regards, > The Alyseo Team > > On Mon, Nov 10, 2014 at 5:48 PM, Garrett D'Amore <[email protected] > <mailto:[email protected]>> wrote: > > > On Nov 8, 2014, at 8:01 AM, Matthew Ahrens <[email protected] > > <mailto:[email protected]>> wrote: > > > > > > FYI - Long term, we'd like the kernel to do more of the property > > processing, so this could eventually turn into simply: > > - do an ioctl to get the requested properties of the requested datasets, > > returning an nvlist > > - print nvlist as json (which has already been implemented, e.g. by Joyent) > > Is there an intent that the kernel do JSON encoding (or decoding)? > > Ultimately, I think this is best done in userland, as there are other formats > than JSON that are interesting (e.g. msgpack), and JSON’s inability (per > spec) to encode everything that might in our nvlist’s (specific numeric > types, especially 64-bit integers) is kind of annoying. > > Agree and will see what the community decide to focus on for mid-long term. > > In the mean time and based on all conversation done today during dev summit > event on this topic, > it has been decided to move forward on this proposal and include it in the > hackathon to give it a boost. > > To do so, Alyseo team will do the hackathon from France (night shift). You > can join the team : > - email = [email protected] <mailto:[email protected]> > - chat on skype = teamalyseo > > Goal is : > > 1/ to agree and clean up the code released (zfs list) implementation > available here : > https://github.com/Alyseo/zfs/tree/json > <https://github.com/Alyseo/zfs/tree/json> > > 2/ move forward and jsonify as much outputs as possible during the hackathon > > Thanks > Yacine > > > > > _______________________________________________ > developer mailing list > [email protected] <mailto:[email protected]> > http://lists.open-zfs.org/mailman/listinfo/developer > <http://lists.open-zfs.org/mailman/listinfo/developer> > > > > > _______________________________________________ > developer mailing list > [email protected] <mailto:[email protected]> > http://lists.open-zfs.org/mailman/listinfo/developer > <http://lists.open-zfs.org/mailman/listinfo/developer> > > > _______________________________________________ > developer mailing list > [email protected] > http://lists.open-zfs.org/mailman/listinfo/developer
_______________________________________________ developer mailing list [email protected] http://lists.open-zfs.org/mailman/listinfo/developer
