On Fri, 2012-01-20 at 11:50 -0600, Tony Asleson wrote: > I would like to give a brief background on the storage management API > and library that I have been working on** and discuss the design and > implementation challenges that I have encountered thus far. > > Most notable is the same topic Shyam Iyer brought up about proprietary > plug-in support (http://marc.info/?l=linux-scsi&m=132454179114038&w=2). > This very feature has influenced libStorageMgmt heavily and has raised a > number of discussions on design and licensing. > > Discussion topics > * Scope (What a storage library should/should not do) > * Role (library position in management stack) > * Features (specific: must have to would be nice) > * Usage scenarios which highlight needed features > * Licensing (most appropriate open source license) > * Proprietary plug-in support > > > ** http://sourceforge.net/apps/trac/libstoragemgmt Its a bit thin at 20 commits over 4 months. It's also a bit insular ... the first thing you usually ask in open source is what can I steal^Wborrow from other projects and how do I recruit others to do the work for me. Once you can actually answer that, the list you have above mostly takes care of itself. The first question is probably: is there anything we can liberate from the Oracle storage API fisasco to help with this. The second might be what would it take to get vendors interested in doing the array plugin glue. James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
