Re: future work: rtslib
On 11/19/2014 05:55 AM, Christophe Vu-Brugier wrote:
> The other thing I've been thinking about is rtslib and
rtslib-fb
> co-installability. Achieving this would be a first step towards unifying
> development, which rtslib developer Jerome and I have discussed a
> little. While of course their APIs have diverged, what's worse is that
> they share the same import name. Thus the author of a script using
> rtslib on Debian, upon moving to RHEL, (or vice versa) will find the
> library is present but likely misbehaves at runtime.
Just curious: what are the differences between rtslib and rtslib-fb that
can cause misbehaviours in scripts?
One big thing is the removal of Backstore and its children from the API.
There's also IBlockStorageObject renamed to BlockStorageObject, and the
removal of a number of functions from utils.py. Child-listing properties
return generators instead of lists. There are also a number of parameter
type changes and smaller things that are different.
Basically, compatibility was not a priority. which is ok, but should
have been paired from the start with the move to a new import name.
-- Andy