libStorageMgmt release 1.3.4

[Tony Asleson]

A new version of libStorageMgmt is now available.

https://github.com/libstorage/libstoragemgmt/releases/download/1.3.4/libstoragemgmt-1.3.4.tar.gz

shasum (19efb8f05cc2607849fbfa43030dd2fc0c3fa176)
md5sum (11cf5348dcb45f6e5b1af02cd335fb0b)

- Fixes
* https://github.com/libstorage/libstoragemgmt/pull/177

Giving it a try:
http://libstorage.github.io/libstoragemgmt-doc/doc/user_guide.html

Thanks to all those that helped make this release better by submitting
pull requests, reporting bugs and engaging in design discussions. All
is appreciated!

*Warning/disclaimer*
This library has the ability to destroy any and all data on a storage
controller (either from user error or because of a code bug in the
library itself). I would suggest using and developing on
only non-production storage arrays which have no data of value or
utilizing the simulator while developing with the library.

As always any feedback, improvements, and pull requests are welcomed.

Regards,
Tony

[Subhendu Ghosh]

Hi Tony

Has anyone looked into the libstorage project that EMC started for their rexray releases? 

Redundant or overlapping intent? 

Thanks 
Subhendu 

________________________________
From: Tony Asleson
Sent: Aug 2, 2016 16:18
To: libstoragemgmt-***@lists.fedorahosted.org; libstoragemgmt-***@lists.fedorahosted.org
Subject: libStorageMgmt release 1.3.4

A new version of libStorageMgmt is now available.

https://github.com/libstorage/libstoragemgmt/releases/download/1.3.4/libstoragemgmt-1.3.4.tar.gz

shasum (19efb8f05cc2607849fbfa43030dd2fc0c3fa176)
md5sum (11cf5348dcb45f6e5b1af02cd335fb0b)

- Fixes
* https://github.com/libstorage/libstoragemgmt/pull/177

Giving it a try:
http://libstorage.github.io/libstoragemgmt-doc/doc/user_guide.html

Thanks to all those that helped make this release better by submitting
pull requests, reporting bugs and engaging in design discussions.  All
is appreciated!

*Warning/disclaimer*
This library has the ability to destroy any and all data on a storage
controller (either from user error or because of a code bug in the
library itself).  I would suggest using and developing on
only non-production storage arrays which have no data of value or
utilizing the simulator while developing with the library.

As always any feedback, improvements, and pull requests are welcomed.

Regards,
Tony

[Handzik, Joseph]

I have looked at it. It’s pretty Docker-focused today, and unless I’m missing something I don’t see how it would ever support the lower-level functionality that I’ve been pitching and helping to develop. Seems like it would go more in the direction of managing Ceph than managing the lower level hardware that I work with (in fact, they have Ceph support tagged as a goal: https://github.com/emccode/libstorage/issues/191).

Joe

From: Subhendu Ghosh [mailto:***@redhat.com]
Sent: Tuesday, August 2, 2016 3:38 PM
To: ***@redhat.com; libstoragemgmt-***@lists.fedorahosted.org; libstoragemgmt-***@lists.fedorahosted.org
Subject: Re: libStorageMgmt release 1.3.4

Hi Tony

Has anyone looked into the libstorage project that EMC started for their rexray releases?

Redundant or overlapping intent?

Thanks
Subhendu

________________________________
From: Tony Asleson
Sent: Aug 2, 2016 16:18
To: libstoragemgmt-***@lists.fedorahosted.org<mailto:libstoragemgmt-***@lists.fedorahosted.org>; libstoragemgmt-***@lists.fedorahosted.org<mailto:libstoragemgmt-***@lists.fedorahosted.org>
Subject: libStorageMgmt release 1.3.4


A new version of libStorageMgmt is now available.

https://github.com/libstorage/libstoragemgmt/releases/download/1.3.4/libstoragemgmt-1.3.4.tar.gz

shasum (19efb8f05cc2607849fbfa43030dd2fc0c3fa176)
md5sum (11cf5348dcb45f6e5b1af02cd335fb0b)

- Fixes
* https://github.com/libstorage/libstoragemgmt/pull/177

Giving it a try:
http://libstorage.github.io/libstoragemgmt-doc/doc/user_guide.html

Thanks to all those that helped make this release better by submitting
pull requests, reporting bugs and engaging in design discussions. All
is appreciated!

*Warning/disclaimer*
This library has the ability to destroy any and all data on a storage
controller (either from user error or because of a code bug in the
library itself). I would suggest using and developing on
only non-production storage arrays which have no data of value or
utilizing the simulator while developing with the library.

As always any feedback, improvements, and pull requests are welcomed.

Regards,
Tony
_______________________________________________
libstoragemgmt-devel mailing list
libstoragemgmt-***@lists.fedorahosted.org<mailto:libstoragemgmt-***@lists.fedorahosted.org>
https://lists.fedorahosted.org/admin/lists/libstoragemgmt-***@lists.fedorahosted.org