openstack team mailing list archive

[Ewan Mellor <Ewan.Mellor@xxxxxxxxxxxxx>]

It's a JSON dictionary.  It looks like it's only purpose is for the administrator to set arbitrary key-value pairs, and then get them again later.  It looks completely useless and overdone to me.  Both xapi and Nova already have databases -- I've no idea why someone felt the need to add a third.

I'd not worry about it if I were you -- as long as the path is set to a directory it can write in, then it'll just quietly stick '{}' in the xenhost.conf and get on with life.

Ewan.

> -----Original Message-----
> From: Thomas Goirand [mailto:thomas@xxxxxxxxxx]
> Sent: 28 December 2011 23:38
> To: Ewan Mellor
> Cc: Johannes Erdfelt; openstack@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Openstack] CRITICAL XENAPI_MISSING_PLUGIN xenhost
> 
> Hi Ewan,
> 
> Yes, fixing the path is easy, but *what is in this file*? (see below:
> it
> was what I was specifically asking for)
> 
> I've been searching for quite some time on the net, and didn't find any
> info about this, and I have no access to a XCP / XenServer machine...
> Is
> that file shipped by default with a XenServer?
> 
> Cheers,
> 
> Thomas
> 
> On 12/29/2011 01:47 PM, Ewan Mellor wrote:
> > 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
> >>
> >> [...]
> >>
> >> '/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