As promised during yesterdays meeting, a quick summary of the situation
around feature freeze (FF) and the live migration branch.
All the major feature branches now landed with the notable exception of
the live-migration branch. There might still be a few default behavior
change branches that
Hello,
We made a decision that our live-migration branch make proceed to Cactus(not
Bexar),
since we considered that being rushed to Bexar is not good choice from QA point
of view.
In addition, being rushed to Bexar is surely a burden to especially core
developers, that is not our true will.
masumo...@nttdata.co.jp wrote:
We made a decision that our live-migration branch make proceed to Cactus(not
Bexar),
since we considered that being rushed to Bexar is not good choice from QA
point of view.
In addition, being rushed to Bexar is surely a burden to especially core
Hi,
I have noticed that recently a new way of configuring nova-api has been
introduced. It seems that the old gflags style has been replaced in favour of
paste.deploy style.
I am trying to find information about this transition, and how old config files
can be translated to new ones. Do we
After the complete lack of consensus observed during Tuesday's IRC
meeting (and the inadequacy of the IRC medium as a way to get one), I
pushed the decision to an OpenStack team Launchpad poll :)
Starting in a few hours, everyone in the ~openstack team (or ~nova, or
~swift...) should hopefully be
On Wed, Jan 19, 2011 at 6:41 AM, Armando Migliaccio
armando.migliac...@eu.citrix.com wrote:
I have noticed that recently a new way of configuring nova-api has been
introduced. It seems that the old gflags style has been replaced in favour
of paste.deploy style.
I am trying to find information
If more documentation enables deployers to properly deploy Nova, it's
in scope. At least, that's my opinion.
-jay
On Wed, Jan 19, 2011 at 2:00 PM, Andy Smith andys...@gmail.com wrote:
My understanding is that the paste.deploy config is unrelated to the flags
system and is rather separate in
I think the root of my confusion came from the fact that I was configuring
nova-api using --flagfile=nova-api.conf and nova-api.conf contained the list of
flags for the node. This is also the reason why I filed a bug to suggest that
nova-api.conf is not hardcoded in bin/nova-api
From:
Hi all:
What's the minimum version of Python officially supported by nova? In
particular, is 2.6.1 supported? I had some tests fail because of an issue in
Python 2.6.1 that's been resolved in Python 2.6.5
https://bugs.launchpad.net/nova/+bug/705052 .
(Note that Python 2.6.1 is the default
Hi all -
I believe paste.deploy configures web server gateway interfaces (wsgi) -
which are an interface between web servers and Python web applications or
frameworks. I think of this config change as applicable to people building
web consoles and the like. Plus it cleans up the interface layers
Before I start trying to get Windows 2008 Hyper-V system online as a nova
compute node has anyone tried this / worked with it etc? Any existing knowledge
on it would be helpful.
___
Mailing list: https://launchpad.net/~openstack
Post to :
http://wiki.openstack.org/HypervInstall
On 01/19/2011 06:02 PM, Jordan Rinke wrote:
Before I start trying to get Windows 2008 Hyper-V system online as a nova
compute node has anyone tried this / worked with it etc? Any existing knowledge
on it would be helpful.
Fantastic, thank you.
Chiradeep Vittal chirad...@cloud.com wrote:
http://wiki.openstack.org/HypervInstall
On 01/19/2011 06:02 PM, Jordan Rinke wrote:
Before I start trying to get Windows 2008 Hyper-V system online as a nova
compute node has anyone tried this / worked with it etc? Any
13 matches
Mail list logo
