The question about upgrade was purely to see if it had been thought about -
I agree that the code is sufficiently broken that it is certainly not
necessary, and quite possibly impossible - I just wondered if I was right
in that analysis.
On 26 November 2014 at 06:43, John Griffith
On 11/25/14, 12:56 PM, Jay S. Bryant wrote:
Monty,
I agree that upgrade is not a significant concern right now if the
existing driver is not working.
Drew,
I am having trouble following where you guys are currently at with this
work. I would like to help get you guys up and going
On 14:37 Tue 25 Nov , Drew Fisher wrote:
On 11/25/14, 12:56 PM, Jay S. Bryant wrote:
Monty,
I agree that upgrade is not a significant concern right now if the
existing driver is not working.
Drew,
I am having trouble following where you guys are currently at with this
On Mon, Nov 24, 2014 at 10:53 AM, Monty Taylor mord...@inaugust.com wrote:
On 11/24/2014 10:14 AM, Drew Fisher wrote:
On 11/17/14 10:27 PM, Duncan Thomas wrote:
Is the new driver drop-in compatible with the old one? IF not, can
existing systems be upgraded to the new driver via some manual
On 11/17/14 10:27 PM, Duncan Thomas wrote:
Is the new driver drop-in compatible with the old one? IF not, can
existing systems be upgraded to the new driver via some manual steps, or
is it basically a completely new driver with similar functionality?
The driver in san/solaris.py focuses
On 11/24/2014 10:14 AM, Drew Fisher wrote:
On 11/17/14 10:27 PM, Duncan Thomas wrote:
Is the new driver drop-in compatible with the old one? IF not, can
existing systems be upgraded to the new driver via some manual steps, or
is it basically a completely new driver with similar
On 07:27 Tue 18 Nov , Duncan Thomas wrote:
Is the new driver drop-in compatible with the old one? IF not, can existing
systems be upgraded to the new driver via some manual steps, or is it
basically a completely new driver with similar functionality?
On 17 November 2014 07:08, Drew
Drew,
I would say that it would be good to open a Blueprint for this and push
the code up for review. Even if you don't have CI ready yet you can
post results of a driver cert test [1] and we can start reviewing the
code while you work on finishing up the process of getting your CI running.
Is the new driver drop-in compatible with the old one? IF not, can existing
systems be upgraded to the new driver via some manual steps, or is it
basically a completely new driver with similar functionality?
On 17 November 2014 07:08, Drew Fisher drew.fis...@oracle.com wrote:
We (here at Oracle)
The Open Solaris ZFS driver [1] is currently missing a lot of the minimum
features [2] that the Cinder team requires with all drivers. As a result, it's
really broken.
I wanted to gauge who is using it, and if anyone was interested in fixing the
driver. If there is not any activity with this
We (here at Oracle) have a replacement for this driver which includes
local ZFS, iSCSI and FC drivers all with ZFS as the underlying driver.
We're in the process of getting CI set up so we can contribute the
driver upstream along with our ZFSSA driver (which is already in the tree).
If anybody
11 matches
Mail list logo
