openstack team mailing list archive

[Ewan Mellor <Ewan.Mellor@xxxxxxxxxxxxx>]

It looks like it creates the file if it's not there -- it's just not smart enough to create /usr/etc if *that's* missing.  I reckon if you fix the path, everything will work fine.

I've no idea why that path was chosen even for XenServer (CentOS 5 based).  Something like /etc/openstack would be more appropriate in either environment, in my opinion.

Cheers,

Ewan.

> -----Original Message-----
> From: Thomas Goirand [mailto:thomas@xxxxxxxxxx]
> Sent: 28 December 2011 21:25
> To: Ewan Mellor
> Cc: Johannes Erdfelt; openstack@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Openstack] CRITICAL XENAPI_MISSING_PLUGIN xenhost
> 
> On 12/29/2011 10:40 AM, Ewan Mellor wrote:
> > You need chmod a+x /etc/xapi.d/plugins/*
> >
> > If you just want to install a package, Xen.org are building an RPM
> > for XenServer / XCP with these plugins:
> > http://downloads.xen.org/XCP/openstack/openstack-xen-plugins/.
> >
> > Cheers,
> >
> > Ewan.
> 
> Hi,
> 
> Thanks, but that's not what I'm trying to do here. I'm not interested
> in
> the RPM packages at all. I had a quick look though, in this package.
> 
> I'm working on the Debian packaging of both XCP and OpenStack. I worked
> closely with Mike and Jon from Citrix, and last week, I uploaded XCP
> in
> Debian SID (that would be the first milestone of the project Kronos).
> I'm currently modifying nova packaging so that these files are packaged
> in a convenient "nova-xcp-pluggins".
> 
> I have found out (by myself) that the plugin directory in Debian isn't:
> /etc/xapi.d/pluggins
> 
> but rather:
> /usr/lib/xcp/plugins
> 
> which indeed makes a lot more sense in a packaged, FHS respecting,
> environment, and I know both Jon and Mike worked on that.
> 
> Now, I'm having another error though:
> (nova): TRACE: Failure: ['XENAPI_PLUGIN_FAILURE', 'host_data',
> 'IOError', "[Errno 2] No such file or directory:
> '/usr/etc/xenhost.conf'"]
> 
> I don't really mind the path issue (the issue is in the xenhost python
> script, I can fix it and set it to /etc/xcp/xenhost.conf instead), but
> what does the plugin expect to see in this file?
> 
> Thomas