On 15 July 2014 11:59, Johnson Cheng wrote:
> May I ask you another question that how cinder choose volume node to create
> volume if I have multi volume nodes?
>
> For example,
>
> when controller node and compute node are alive, the volume will be created
> at compute node.
>
> When I shutdown c
: Duncan Thomas [mailto:duncan.tho...@gmail.com]
Sent: Tuesday, July 15, 2014 3:51 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Can not create cinder volume
On 15 July 2014 08:24, Johnson Cheng
mailto:johnson.ch...@qsantechnology.com>>
wro
On 15 July 2014 08:24, Johnson Cheng
wrote:
>
>
> I have two questions here,
>
> 1. It still has “Error encountered during initialization of driver:
> LVMISCSIDriver” error message in cinder-volume.log, how to fix this issue?
>
> 2. From cinder-scheduler.log, it shows “volume service is
.0.0 driver is uninitialized.
>
>
>
> My cinder version is 1.0.8, and “cinder service-list” output is listed as
> below,
>
>
> +--++--+-+---++
>
> | Binary |Host| Zone | Status | State |
> Updated_at |
>
>
> +------
On Mon, Jul 14, 2014 at 8:13 AM, Duncan Thomas
wrote:
> Please post up more (all) of your cinder-volume.log - something is
> stopping your driver being initialised, but you haven't provided enough
> logs to tell what the issue it.
>
>
> On 14 July 2014 12:22, Johnson Cheng
> wrote:
>
>> Dear Al
Please post up more (all) of your cinder-volume.log - something is stopping
your driver being initialised, but you haven't provided enough logs to tell
what the issue it.
On 14 July 2014 12:22, Johnson Cheng
wrote:
> Dear All,
>
>
>
> When I use “cinder create –display-name myVolume 1” to crea
