Open Stack

Thats what i was asking to show me the exact command that you were running,
cause there's a bug if you dont specify the availabily zone on creating
volumes :)

https://bugs.launchpad.net/nova/+bug/988993

Glad you solve it

Greets


On Fri, Nov 16, 2012 at 8:47 PM, Joe Topjian <joe.topjian at cybera.ca> wrote:

> Hi Abel,
>
> Similarly, can you share your entire nova.conf file (censored of course)?
>
> Thanks,
> Joe
>
>
> On Fri, Nov 16, 2012 at 3:33 PM, Leandro Reox <leandro.reox at gmail.com>wrote:
>
>> Can you paste the command that youre issuing on the nova-client to create
>> the volume ?
>>
>>
>> On Fri, Nov 16, 2012 at 7:29 PM, Abel Lopez <alopgeek at gmail.com> wrote:
>>
>>> I have the rabbit_host defined in nova.conf across the whole farm.
>>> Everything else works fine, except volume.
>>>
>>> On Nov 16, 2012, at 2:23 PM, Leandro Reox wrote:
>>>
>>> The server were your running the volume server its not connecting with
>>> the "controller" or the server whos running the rabbitmq. Thats generates
>>> your stacktrace.
>>>
>>> How your nova.conf looks like on all nodes ?
>>>
>>> Yo need to have a line there like :
>>>
>>>
>>> *--rabbit_host=$(YOUR RABBITMQ SERVER)*
>>>
>>>
>>> On Fri, Nov 16, 2012 at 7:02 PM, Joe Topjian <joe.topjian at cybera.ca>wrote:
>>>
>>>> Hi Abel,
>>>>
>>>> What is your OpenStack setup like? Do you have everything all on one
>>>> server? Or split up?
>>>>
>>>> If you do "nova-manage service list" do you see nova-volume listed with
>>>> a :-) ?
>>>>
>>>> Thanks,
>>>> Joe
>>>>
>>>>
>>>> On Fri, Nov 16, 2012 at 2:23 PM, Abel Lopez <alopgeek at gmail.com> wrote:
>>>>
>>>>> I am removing the netapp from the equation. I'm simply trying now with
>>>>> a standard lvm VG named 'nova-volumes'
>>>>> Here is a link to my log when I restart nova-volume
>>>>> http://pastebin.com/T8fnEXZ6
>>>>>
>>>>> Here is a link to the nova-scheduler.log when I try to create a volume
>>>>> http://pastebin.com/Xnhi9v1m
>>>>>
>>>>> Any help or advice would go a long way!
>>>>>
>>>>> On Nov 16, 2012, at 11:56 AM, Alejandro Comisario wrote:
>>>>>
>>>>> Can you post the whole nova-volume.log that happens when you
>>>>> start/restart the nova-volume service ?
>>>>>
>>>>> *
>>>>> *
>>>>> *
>>>>> *
>>>>> *Alejandro Comisario
>>>>> #melicloud CloudBuilders*
>>>>> Arias 3751, Piso 7 (C1430CRG)
>>>>> Ciudad de Buenos Aires - Argentina
>>>>> Cel: +549(11) 15-3770-1857
>>>>> Tel : +54(11) 4640-8443
>>>>>
>>>>>
>>>>> On Fri, Nov 16, 2012 at 3:32 PM, Abel Lopez <alopgeek at gmail.com>wrote:
>>>>>
>>>>>> Thanks for the tips.
>>>>>> As far as we can tell, everything in the netapp is ok. When
>>>>>> nova-volume starts up, I can see in the logs where it gets the wsdl file
>>>>>> fine. Also verified that nova-volume is only running on 1 host.
>>>>>>
>>>>>> It might be interesting to note, that this site was without any prior
>>>>>> volume service.
>>>>>>
>>>>>> On Nov 16, 2012, at 8:01 AM, Joe Topjian wrote:
>>>>>>
>>>>>> Hi Abel,
>>>>>>
>>>>>> I have two NetApp filers working with OpenStack, but I'm new to
>>>>>> NetApp equipment, so I can try to help :)
>>>>>>
>>>>>> I just read over the doc you linked to. It's actually quite detailed
>>>>>> and a lot better than the docs that were available when I was doing this -
>>>>>> lucky!
>>>>>>
>>>>>> Anyway, just to confirm/review a few things, you:
>>>>>>
>>>>>> * have an OnCommand server set up with the Storage Service,
>>>>>> Provisioning Policy, and Resource Pool all configured. (Do they look OK in
>>>>>> the nmconsole GUI?)
>>>>>> * have the wsdl file available for download and can confirm access
>>>>>> with wget.
>>>>>> * have nova-volume running on only 1 server (When using LVM, it makes
>>>>>> sense to run nova-volume on several servers, but with a central storage
>>>>>> appliance, 1 instance of nova-volume makes sense).
>>>>>>
>>>>>> For Essex, one recommendation I was given was to use NetApp's updated
>>>>>> driver:
>>>>>>
>>>>>> https://github.com/bswartz/nova/pull/1
>>>>>>
>>>>>> The reason I link to a pull request is because I have a small fix
>>>>>> that was needed for Essex.
>>>>>>
>>>>>> This driver is a drop-in replacement for netapp.py
>>>>>>
>>>>>> And is nova running in debug mode? If so, tail -f
>>>>>> /var/log/nova/nova-volume.log and see if nova-volume is talking to the
>>>>>> NetApp correctly. The conformance log (/opt/log/conformance.log) might also
>>>>>> have some good pointers.
>>>>>>
>>>>>> Hope that helps,
>>>>>> Joe
>>>>>>
>>>>>>
>>>>>> On Fri, Nov 16, 2012 at 1:01 AM, Abel Lopez <alopgeek at gmail.com>wrote:
>>>>>>
>>>>>>> Hi Everyone,
>>>>>>>
>>>>>>> Testing out netapp volume driver in Essex.
>>>>>>> Starting from "unconfigured netapp" and "no prior volume service",
>>>>>>> Having had followed the docs provided from netapp
>>>>>>> https://communities.netapp.com/docs/DOC-19826
>>>>>>> I have a "happy" nova-volume service, configured the nova.conf,
>>>>>>> appropriately, verify all network connectivity.
>>>>>>>
>>>>>>> When I try to create a volume using nova client, I see in the
>>>>>>> scheduler logs
>>>>>>> Failed to schedule_create_volume: No valid host was found. Is the
>>>>>>> appropriate service running?
>>>>>>>
>>>>>>> Anyone have any tips or tricks?
>>>>>>> _______________________________________________
>>>>>>> OpenStack-operators mailing list
>>>>>>> OpenStack-operators at lists.openstack.org
>>>>>>>
>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Joe Topjian
>>>>>> Systems Administrator
>>>>>> Cybera Inc.
>>>>>>
>>>>>> www.cybera.ca
>>>>>>
>>>>>> Cybera is a not-for-profit organization that works to spur and
>>>>>> support innovation, for the economic benefit of Alberta, through the use
>>>>>> of cyberinfrastructure.
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> OpenStack-operators mailing list
>>>>>> OpenStack-operators at lists.openstack.org
>>>>>>
>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Joe Topjian
>>>> Systems Administrator
>>>> Cybera Inc.
>>>>
>>>> www.cybera.ca
>>>>
>>>> Cybera is a not-for-profit organization that works to spur and support
>>>> innovation, for the economic benefit of Alberta, through the use
>>>> of cyberinfrastructure.
>>>>
>>>>
>>>> _______________________________________________
>>>> OpenStack-operators mailing list
>>>> OpenStack-operators at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>>
>>>>
>>>
>>>
>>
>
>
> --
> Joe Topjian
> Systems Administrator
> Cybera Inc.
>
> www.cybera.ca
>
> Cybera is a not-for-profit organization that works to spur and support
> innovation, for the economic benefit of Alberta, through the use
> of cyberinfrastructure.
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20121116/f4ef84a9/attachment.html>