You need to install the xenapi plugins:
If you are using devstack (https://github.com/openstack-dev/devstack), the
code below from build_domU.sh does this for you.
# Checkout nova
if [ ! -d $TOP_DIR/nova ]; then
env GIT_SSL_NO_VERIFY=true git clone $NOVA_REPO
cd $TOP_DIR/nova
git
On Mon, 2012-03-12 at 17:57 -0500, Josh Kearney wrote:
Is this is really a problem that needs solving? I'd like to believe that no
member of Nova Core would approve something that they aren't familiar with.
I think the issue is more a case of allowing some time for other
reviewers to come along
Maybe it is just me, but most reviews seem to take hours to days to
complete. I'm been sitting here waiting for a one line change to get
a second +2 / approved so I can redeploy our test cluster for the
last 2 hours.
When lots of people are active, reviews can be approved in quickly -
especially
On 03/13/2012 02:32 PM, Renuka Apte wrote:
You need to install the xenapi plugins:
If you are using devstack (https://github.com/openstack-dev/devstack), the
code below from build_domU.sh does this for you.
I'm part of the debian Openstack packaging team, and I worked with Mike
on packaging
2012/3/12 Josh Kearney j...@jk0.org:
Is this is really a problem that needs solving? I'd like to believe
that no member of Nova Core would approve something that they aren't
familiar with.
That's not the point. The review process isn't just about finding enough
people who agree with your
Hi Joe,
On 12/03/12 21:59, Joe Gordon wrote:
I have noticed that some Gerrit branches get approved very quickly,
sometimes in a matter of minutes. While most of the time these
branches are vetted properly, the window for reviewing can be so small
that a non-trivial branch lands but without
Cheers Padraig - I'll grab a Fedora install and compare notes.
I guess if Fedora has an installation candidate, the problem is probably
Ubuntu packaging - at least I can direct my issues at Ubuntu rather than
OpenStack as a whole...
Kev
2012/3/13 Pádraig Brady p...@draigbrady.com
On
Your stacktrace:
['XENAPI_PLUGIN_FAILURE', 'non-zero exit', '', '']
2012-03-13 05:41:32 ERROR nova.virt.xenapi.host [-] The call to
host_data returned an error: ['XENAPI_PLUGIN_FAILURE', 'non-zero
exit', '', ''].
2012-03-13 05:41:32 CRITICAL nova [-] 'str' object does not support
item assignment
On Behalf Of Thomas Goirand
which installs the above in the correct folders (which are *NOT* the same as
for CentOS). I'd love to have a bit of help from Citrix to test all this by
the way.
I hear you, and want to help out :-)
I hope we can setup some Jenkins tests on various
Hi Kevin,
As others have said, I can only speak to what I'm familiar with ( the
Managed I.T. packages).
They should be fairly up-to-date, there has been very few bugfixes to the
stable branch that I'm aware of since I last updated the packages.
Re EC2 compatibility, they are as compatible as
2012/3/9 Hengqing Hu huda...@hotmail.com:
Last few weeks I spend some time to speed up unittest in Nova.
This is great stuff! Thanks!
--
Soren Hansen | http://linux2go.dk/
Senior Software Engineer | http://www.cisco.com/
Ubuntu Developer | http://www.ubuntu.com/
OpenStack
On Tue, Mar 13, 2012 at 7:43 AM, Kevin Jackson
ke...@linuxservices.co.uk wrote:
Hi Andi,
Sure - the methods aren't meant for automated production installs, but to
get to a world where I can automate using Orchestra or variations on PXE
booting,
Well.. setting up a distributed system where all
Thanks a lot for the points Andi (and the links), but not to stray away
from my original post: I don't want complexity at this stage - I want a
single server that works. I haven't even got that.
I had a multi node set up working (to some degree of butchery) of an early
Essex-1 release using
I certainly understand your position Thierry. However, I think it is
important that we target one 'golden' platform, and that we take
responsibility for any issues with that platform. Otherwise we simply
end up pointing fingers and being blocked on backports, and the end
result is a system that
On Mar 13, 2012, at 11:54 AM, Josh Kearney wrote:
On Tue, Mar 13, 2012 at 5:07 AM, Soren Hansen so...@linux2go.dk wrote:
2012/3/13 Jesse Andrews anotherje...@gmail.com:
Maybe it is just me, but most reviews seem to take hours to days to
complete. I'm been sitting here waiting for a one
On Tue, Mar 13, 2012, Lorin Hochstein lo...@nimbisservices.com wrote:
As long as we're talking about review issues, I'd really like to have a
set of reviewing guidelines. Even better would be to have them in
checklist form to make sure we don't miss things as we do reviews
(checklists are
On 03/13/2012 03:08 PM, Joseph Heck wrote:
* https://bugs.launchpad.net/keystone/+bug/954089 (service-list returns empty
set for TemplatedCatalog backend)
On it.
* https://bugs.launchpad.net/keystone/+bug/954087 (endpoint-list with
TemplatedCatalog backend raises AttributeError)
Adam G's
On 03/13/2012 03:25 PM, Joseph Heck wrote:
On a different note,
Who all out there is providing public packages for OpenStack?
The Fedora Project is providing packages for both Fedora and EPEL (Extra
Packages for Enterprise Linux).
background:
Anne Gentle brought up wanting to reference
On 03/13/2012 03:08 PM, Joseph Heck wrote:
Additionally, I'd like to ask anyone who's running under latest RHEL/Fedora
and/or Debian/Ubuntu systems to try the packages and see if there's any
explicit notes that we should be making related to installing Keystone. I
haven't tried the Precise
Hi Jophep,
I can speak from Debian side. We provide OpenStack packages, but with
our target being Essex (maybe Folsom) + Debian Wheezy. In the case of
keystone, we support multiple database options (sqlite, mysql and
postgresql) that can be selected at install time (both interactively and
also
On 03/13/2012 10:55 PM, Todd Deshane wrote:
On Mon, Mar 12, 2012 at 2:10 PM, Eduardo Nunes eduardo.ke...@gmail.com
wrote:
I read all the docs about it but i dont get it, what release shold i use, i
run the xcp under the linux or i run linux under the xcp?
You actually have two options for
max_messages actually corresponds to how many messages we try to send to the
configured recipient before it moves onto the next queue in the list.
Basically, it's super rudimentary QoS.
As for expiration, that's controlled by redis itself. Under the persistence
configuration section, you can
Adam (and others I've not instantly replied to),
Thanks for the reply. I understand that OpenStack (moving target) on
Ubuntu (moving target) is no mean feat, but I no doubt expect a lot of
people are in the same boat as me. Ubuntu (and other distros) have set a
certain level of expectation for
I understand the sentiment that leads one to want minimum review times; there
have been occasions where it's frustrated me that something I objected to got
merged without my seeing it or while I was trying to comment.
However, I'd like to present several arguments against a minimum review time:
Just my 2 cents.
Shouldn't openstack be dependent only on a known set of package versions and
not a distro?
It seems like it should be the job of openstack to define those versions and
let the distro's match that as they choice.
If 12.04 matches these versions, then it should work, if
yes, in your yagi.conf, in the persistence section, set the entry_ttl value
like so:
For 120 second expiration:
[persistence]
entry_ttl = 120
The value is in seconds, so for 1 hr use 3600, etc.
On Mar 13, 2012, at 1:50 PM, Craig Vyvial wrote:
I noticed that in the configuration file
Is there a reason there isn't a unique contraint on display_names per
account for volumes, instances, etc? I see this potentially causing
some operational problems and customer confusion.Also, currently
the python-nova-client will only list the first one when you use the
show command.
What
Oh thats awesome! Looks like i just overlooked the definition of some of
the configuration parameters.
I found this:
default('entry_ttl', 60*60*24*30)
Thanks for that explanation its exactly what i needed.
-Craig Vyvial
On Tue, Mar 13, 2012 at 3:22 PM, Matt Dietz
On 12/03/12 17:42, John Dickinson wrote:
On Mar 10, 2012, at 5:58 AM, John Leach wrote:
I think what I need here is hierarchical zones - I'd define one
parent zone per data-centre, and then multiple child zones within
each (representing racks or whatever).
Swift would be configured to
On 03/13/2012 01:53 PM, Kevin Jackson wrote:
Whilst OpenStack is being developed, a lot of people's entry into
OpenStack is through deb packages (or insert your fave package
management in here) - therefore Ubuntu becomes unofficial (but vocal)
PR to OpenStack. If the Ubuntu debs don't
there have been occasions where it's frustrated me that something I
objected to got merged without my seeing it or while I was trying to
comment.
I've heard of this several times in the past as well - some merge prop is
mid-review, and then it merges. Is there an easy mechanism to flag a
Sent this to kevin earlier, thought i would throw it out to the list.. here are
the steps i take to get a working keystone and glance on Ubuntu-12.04 using the
ubuntu packages.
http://paste.openstack.org/show/9101/
These steps produce a working keystone and glance.. not 100% sure they are the
Hello folks,
I, Dave Nielsen and Lloyd Dewolf (the elections committee) met today to
close the loop of the spring 2012 OpenStack elections with a brief
post-mortem analysis. Here are the results of our chat (and below for
your convenience).
** Also affects: openstack-common
Importance: Undecided
Status: New
** Changed in: openstack-common
Assignee: (unassigned) = Joe Gordon (joe-gordon0)
--
You received this bug notification because you are a member of OpenStack
Common Drivers, which is the registrant for
Fix proposed to branch: master
Review: https://review.openstack.org/5306
** Changed in: openstack-common
Status: New = In Progress
--
You received this bug notification because you are a member of OpenStack
Common Drivers, which is the registrant for openstack-common.
35 matches
Mail list logo
