[Openstack-operators] Netapp volume, anyone?
joe.topjian at cybera.ca
Fri Nov 16 22:02:57 UTC 2012
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
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
> Here is a link to the nova-scheduler.log when I try to create a volume
> 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 -
>> 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
>> * have the wsdl file available for download and can confirm access with
>> * 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
>> 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,
>> 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
>>> 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
>>> 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
>> Joe Topjian
>> Systems Administrator
>> Cybera Inc.
>> 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
Cybera is a not-for-profit organization that works to spur and support
innovation, for the economic benefit of Alberta, through the use
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-operators