On Tue, Jul 29, 2014 at 03:06:40AM +0000, Everett Toews wrote: > On Jul 28, 2014, at 9:16 PM, Andrew Phillips <aphill...@qrmedia.com> wrote: > > > As regards karaf and cli: would they belong in core, or in tools or > > elsewhere? They're really more downstream consumers of jclouds than *parts* > > of jclouds themselves. > > Originally I thought of the tools dir as just being a collection of scripts > but it could be more than that. If we did put karaf and cli and the BlobStore > stuff in there it’s clear that it would become something of a catch-all for > jclouds related stuff that we want to keep close. I’m not necessarily against > that but we need to be clear about the intention of the tools dir. > > Personally, I’ve never used karaf or the cli so I don’t feel strongly about > where they go or even if they stay within our repo. I hope the maintainers of > these things speak up here.
The frequently-suggested blobstore tools are much smaller than karaf and potentially a much larger user base; these could help users diagnose connectivity, authentication, proxy, and other configuration issues in a dependable way instead of the zoo of user application problems, including logging. Further there is a legitimate administrative use and potentially a way to reach new users. Check out how clean BlobStoreCli is compared to anything in karaf/cli: https://github.com/andrewgaul/jclouds/blob/blobstore-cli/blobstore-cli/src/main/java/org/jclouds/blobstore/cli/BlobStoreCli.java I would really like to find a way forward on these tools. -- Andrew Gaul http://gaul.org/
