It would be more appreciated to provide users with evaluation results
of migration and recovery tools by QA to avoid any disaster on
production environment, and get agreement with them
e.g.,
#1 Scenarios we test
#2 Images spec we use
and some
Does it make sense, or too much?
Regards,
On
On Wed, Jan 11, 2017 at 10:43 PM, Shinobu Kinjo wrote:
> +2
> * Reduce manual operation as much as possible.
> * A recovery tool in case that we break something which would not
> appear to us initially.
I definitely agree that this is an overdue tool and we have an
upstream
On Thu, Jan 12, 2017 at 12:28 PM, Christian Balzer wrote:
>
> Hello,
>
> On Wed, 11 Jan 2017 11:09:46 -0500 Jason Dillaman wrote:
>
>> I would like to propose that starting with the Luminous release of Ceph,
>> RBD will no longer support the creation of v1 image format images via
Hello,
On Wed, 11 Jan 2017 11:09:46 -0500 Jason Dillaman wrote:
> I would like to propose that starting with the Luminous release of Ceph,
> RBD will no longer support the creation of v1 image format images via the
> rbd CLI and librbd.
>
> We previously made the v2 image format the default
On Thu, Jan 12, 2017 at 2:41 AM, Ilya Dryomov wrote:
> On Wed, Jan 11, 2017 at 6:01 PM, Shinobu Kinjo wrote:
>> It would be fine to not support v1 image format at all.
>>
>> But it would be probably friendly for users to provide them with more
>>
On Wed, Jan 11, 2017 at 5:09 PM, Jason Dillaman wrote:
> I would like to propose that starting with the Luminous release of Ceph, RBD
> will no longer support the creation of v1 image format images via the rbd
> CLI and librbd.
>
> We previously made the v2 image format the
It would be fine to not support v1 image format at all.
But it would be probably friendly for users to provide them with more
understandable message when they face feature mismatch instead of just
displaying:
* rbd: map failed: (6) No such device or address
For instance, show the following
I would like to propose that starting with the Luminous release of Ceph,
RBD will no longer support the creation of v1 image format images via the
rbd CLI and librbd.
We previously made the v2 image format the default and deprecated the v1
format under the Jewel release. It is important to note