On Sat, Nov 8, 2014 at 5:01 PM, Matthew Ahrens <[email protected]> wrote:
> The overall idea of printing "zfs list" output as JSON seems good. > > I took a quick look at the code (https://github.com/Alyseo/zfs/compare/json > ). > > It looks like this is a work in progress. E.g: > Absolutely this is really to exchange and agree with the community first. > - it would seem to do the wrong thing with "zfs list -J -o <prop>" > Will be fix > - there are many style errors > Can you give us more details, guess you are dealing with the code and not the JSON output ? > Why do we need cb_header when we already have cb_proplist? > Will check this out, good point. 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) > Agree it will be giant as a long term vision, but will this kernel integration gonna be possible for all distro (ZoL case) ? > There are going to be a couple of talks about how this might be achieved > at the OpenZFS Developer Summit on Monday, you might want to catch the live > stream (or recordings will be posted later in the week). > I'm joining you guys today and the team will check the live stream for sure. > (However, that long-term plan doesn't mean we shouldn't in the mean time > do JSON printing with the current infrastructure, as you're proposing.) > +1 and this is what we need to agree on ;-) Regards, Francois & Yacine @Alyseo
_______________________________________________ developer mailing list [email protected] http://lists.open-zfs.org/mailman/listinfo/developer
