Yep - that was it. There was an old version in /etc/nova.
I copied the new version there and nova-api works now.
Thanks,
Andy
From: Brian Waldon [mailto:brian.wal...@rackspace.com]
Sent: Wednesday, November 30, 2011 12:57 PM
To: Andy Bierman
Cc: openstack@lists.launchpad.net
Subject: Re
Hi,
I am running the code from yesterday (lp:nova) on Ubuntu 11.04 (x64).
All nova-* programs except nova-api are starting OK.
That program terminates because it cannot import 'metadatarequesthandler'.
See the trackback attached. How can I get nova-api working?
thanks,
Andy
2011-11-30 11:55:45,
I agree only the major version should be in the URL, and the major version
must be bumped if any API is changed such that the 'API contract' with existing
clients
is broken somehow. (Standard 'old manager/new agent' stuff.)
Traditionally, the software release version IDs need to be precise,
so w
om/>" to
"hkp://keyserver.ubuntu.com:80<http://keyserver.ubuntu.com/>"
3.Save and close.
Andy
From: openstack-bounces+biermana=brocade@lists.launchpad.net
[mailto:openstack-bounces+biermana=brocade@lists.launchpad.net] On Behalf
Of Andy Bierman
Sent:
Hi,
Not sure anybody else ran into this problem installing nova,
but if add-apt-repository is timing out, your firewall is probably
blocking port 11371. Try this:
http://superuser.com/questions/64922/how-to-work-around-blocked-outbound-hkp-port-for-apt-keys
Andy
_
IMO, defining an API by providing 1 example of the API is not really
interoperable.
The point of defining a schema is to specify the 'contract' the API provider
will honor, so a developer coding against the API knows what to write
(for that particular message exchange).
As for extensibility, YAN
+1 to your +1.
I was wondering about formal definitions for the Quantum plugin APIs.
Will there be WADL definitions? I really want to use RelaxNG schemas to
validate the XML payloads (request and response) defined by the API.
Andy
-Original Message-
From: openstack-bounces+biermana=br
7 matches
Mail list logo
