Releases: thecodeteam/libstorage
v0.1.5-rc1
Version 0.1.5-rc1 (2016/07/11)
This release candidate comes hot on the heels of the previous release, but some dynamite bug fixes have improved the performance of the server by leaps and bounds. Operations that were taking minutes now take seconds or less. Memory consumption that could exceed 50GB is now kept neat and tidy.
Bug Fixes
Enhancements
- Make Gometalinter optional (#223)
Documentation
Please see the v0.1.5-rc1 documentation for more information.
v0.1.4
Version 0.1.4 (2016/07/08)
This update provides a major performance improvement as well as a few other,
minor bug fixes and enhancements.
Bugfixes
- Performance degradation bug (#218)
- Close bug in ScaleIO driver (#213)
- Panic when checking attached instances with Isilon driver (#211)
Enhancements
- Improved build process (#220)
- Improved executor logging (#217)
- Log timestamps in ms (#219)
- Updated ScaleIO docs (#214)
Documentation
Please see the v0.1.4 documentation for more information.
v0.1.1
Version 0.1.1 (2016/06/10)
This is the initial GA release of libStorage.
Features
libStorage is an open source, platform agnostic, storage provisioning and
orchestration framework, model, and API. Features include:
- A standardized storage orchestration
model and API - A lightweight, reference client implementation with a minimal dependency
footprint - The ability to embed both the libStorage client and server, creating native
application integration opportunities
Operations
libStorage supports the following operations:
| Resource Type | Operation | Description |
|---|---|---|
| Volume | List / Inspect | Get detailed information about one to many volumes |
| Create / Remote | Manage the volume lifecycle | |
| Attach / Detach | Provision volumes to a client | |
| Mount / Unmount | Make attached volumes ready-to-use, local file systems | |
| Snapshot | Coming soon | |
| Storage Pool | Coming soon |
Getting Started
Using libStorage can be broken down into several, distinct steps:
- Configuring libStorage
- Understanding the API
- Identifying a production server and client implementation, such as
REX-Ray
Thank You
| Name | Blame |
|---|---|
| Clint Kitson | His vision come to fruition. That's his vision, thus please assign all bugs to Clint :) |
| Vladimir Vivien | A nascent player, Vlad had to hit the ground running and has been a key contributor |
| Kenny Coleman | While some come close, none are comparable to Kenny's handlebar |
| Jonas Rosland | Always good for a sanity check and keeping things on the straight and narrow |
| Steph Carlson | Steph keeps the convention train chugging along... |
| Amanda Katona | And Amanda is the one keeping the locomotive from going off the rails |
| Drew Smith | Drew is always ready to lend a hand, no matter the problem |
| Chris Duchesne | His short time with the team is in complete opposition to the value he has added to this project |
| David vonThenen | David has been a go-to guy for debugging the most difficult of issues |
| Steve Wong | Steve stays on top of the things and keeps use cases in sync with industry needs |
| Travis Rhoden | Another keen mind, Travis is also a great font of technical know-how |
| Peter Blum | Absent Peter, the EMC World demo would not have been ready |
| Megan Hyland | And absent Megan, Peter's work would only have taken things halfway there |
| Eugene Chupriyanov | For helping with the EC2 planning |
| Matt Farina | Without Glide, it all comes crashing down |
| Josh Bernstein | The shadowy figure behind the curtain... |
And many more...
Documentation
Please see the v0.1.1 documentation for more information.