<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body style="font-family: tt;" bgcolor="#FFFFFF" text="#000000"><div
style="font-family: tt;"><span style="font-family: monospace;">Marc
Heckmann wrote:</span><blockquote style="font-family: monospace;"
cite="mid:1423682241.35592.7.camel@localhost.localdomain" type="cite">I
can definitely relate to the problem that it's trying to solve. We
have a backend that has both thin-provisioning and compression. Right
now, we have no easy way to filter which storage node that a volume
should be created on if compression and thin provisioning is to be taken
into account.
That being said, I'm not sure about the implementation as such. I could
see how it needs to remain flexible to accommodate a bunch of different
types of drivers.
I suppose that it's a start.
-m</blockquote><span style="font-family: monospace;">I agree with the
substance of Marc's remarks. There is clearly value for being able to
discriminate between various storage backends transparently (from the
user's perspective at least). That being said, I am not in a position to
judge the quality of the code or cleanliness of integration.</span><br><br>Regards,<br><br>Richard
Raseley<br><br>SysOps Engineer<br>Puppet Labs<br style="font-family:
monospace;"></div></body></html>