On Fri, Jul 24, 2015 at 09:56:41AM -0400, Doug Hellmann wrote:
Excerpts from Daniel P. Berrange's message of 2015-07-24 09:48:15 +0100:
On Thu, Jul 23, 2015 at 05:55:36PM +0300, mhorban wrote:
Hi all,
During development process in nova I faced with an issue related with
config
On Fri, Jul 24, 2015 at 12:29:56PM -0400, Doug Hellmann wrote:
Excerpts from Joshua Harlow's message of 2015-07-24 09:07:13 -0700:
Daniel P. Berrange wrote:
On Thu, Jul 23, 2015 at 05:55:36PM +0300, mhorban wrote:
Hi all,
During development process in nova I faced with an issue
On Fri, Jul 17, 2015 at 08:12:18AM +0300, Feodor Tersin wrote:
The third reason is that at least xen supports them.I know that vdr
becomes /dev/xvdr, but:1) I believe the main aim of specifying device
name is to easy distinguish among devices. A last char is enough for
that. And xen supports
On Fri, Jul 03, 2015 at 03:55:37PM +0100, Anthony PERARD wrote:
On Wed, Jul 01, 2015 at 02:45:13PM +0100, Daniel P. Berrange wrote:
On Tue, Jun 30, 2015 at 03:02:54PM +0100, Anthony PERARD wrote:
Hi all,
We have an issue with the driver libvirt-xen. When a guest is started by
Nova
On Tue, Jun 30, 2015 at 03:02:54PM +0100, Anthony PERARD wrote:
Hi all,
We have an issue with the driver libvirt-xen. When a guest is started by
Nova, nova-network is going to do some network setup and call
iptables-{save,restore}, and the Xen toolstack is going to setup the
vif of the
On Tue, Jun 30, 2015 at 02:42:01PM +0800, ChangBo Guo wrote:
CPU frequency is an import performance parameter, currently nova drivers
just report cpu_info without frequency. we stored the compute node
cpu_info in database with colum compute_nodes.cpu_info, we can add the
frequency
On Wed, Jun 24, 2015 at 06:30:06PM -0700, James Bottomley wrote:
On Wed, 2015-06-24 at 17:25 +0100, Daniel P. Berrange wrote:
On Wed, Jun 24, 2015 at 11:52:37AM -0400, Adam Young wrote:
On 06/24/2015 06:28 AM, Nikola Đipanov wrote:
Gerrit and our spec template are a horrible tool
On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote:
Hey Nova,
I'll cut to the chase and keep this email short for brevity and clarity:
Specs don't work! They do nothing to facilitate good design happening,
if anything they prevent it. The process layered on top with only a
On Wed, Jun 24, 2015 at 11:52:37AM -0400, Adam Young wrote:
On 06/24/2015 06:28 AM, Nikola Đipanov wrote:
Gerrit and our spec template are a horrible tool for
discussing design.
This is the heart of the problem.
I think that a proper RFE description in the bug tracker is the best place
On Wed, Jun 24, 2015 at 04:46:57PM +, Michael Krotscheck wrote:
On Wed, Jun 24, 2015 at 6:30 AM Matt Riedemann mrie...@linux.vnet.ibm.com
wrote:
There is the openstack-specs repo for cross-project specs:
http://specs.openstack.org/openstack/openstack-specs/
That'd be a good
In response to the proposal to add a VIF plugin script to the VIF port
binding data, I have put up a counter proposal which takes things a
bit further and in slightly different direction, with a strong focus
on object modelling.
Superficially inspired by os-brick, I'm suggesting, we put create a
On Mon, Jun 22, 2015 at 11:10:40AM -0500, Kevin L. Mitchell wrote:
On Sat, 2015-06-20 at 21:35 +0100, Daniel P. Berrange wrote:
In general I would say that is an unsupported deployment scenario to
have other random virt guests running on a nova compute node.
On the other hand
On Sun, Jun 21, 2015 at 11:14:00AM -0500, Matt Riedemann wrote:
On 6/20/2015 3:35 PM, Daniel P. Berrange wrote:
On Sat, Jun 20, 2015 at 01:50:53PM -0500, Matt Riedemann wrote:
Waking up from a rare nap opportunity on a Saturday, this is what was
bothering me:
The proposal
On Mon, Jun 22, 2015 at 11:28:35AM +0100, neil.jer...@metaswitch.com wrote:
It seems like we're possibly stuck now on the VIF plugin script spec [1];
there being core comments in apparently conflicting directions. I wonder if
it's still feasible for a version of this to land during Liberty?
On Sat, Jun 20, 2015 at 01:50:53PM -0500, Matt Riedemann wrote:
Waking up from a rare nap opportunity on a Saturday, this is what was
bothering me:
The proposal in the etherpad assumes that we are just getting bulk
host/domain/guest VM stats from the hypervisor and sending those in a
On Wed, Jun 17, 2015 at 11:37:04AM -0500, Matt Riedemann wrote:
On 6/17/2015 4:46 AM, Daniel P. Berrange wrote:
On Tue, Jun 16, 2015 at 04:21:16PM -0500, Matt Riedemann wrote:
The NFS, GlusterFS, SMBFS, and Quobyte libvirt volume drivers are all very
similar.
I want to extract a common
On Tue, Jun 16, 2015 at 04:21:16PM -0500, Matt Riedemann wrote:
The NFS, GlusterFS, SMBFS, and Quobyte libvirt volume drivers are all very
similar.
I want to extract a common base class that abstracts some of the common code
and then let the sub-classes provide overrides where necessary.
On Thu, Jun 11, 2015 at 12:54:54PM +0200, Andreas Scheuring wrote:
On Thu, 2015-06-11 at 09:30 +0100, Daniel P. Berrange wrote:
It seems the main reason for your new proposal is to deal with
the fact that on migration, you need to specify a different
NIC name in the XML
On Wed, Jun 10, 2015 at 04:47:41PM +0200, Andreas Scheuring wrote:
Hi Daniel, Neil and others,
I was thinking about introducing libvirt-network as a new vif type to
nova. It can be used when Neutron prepares a libvirt network for
attaching guests.
Would you see any general concerns with
On Thu, Jun 11, 2015 at 03:02:13PM +0100, Daniel P. Berrange wrote:
On Thu, Jun 11, 2015 at 12:54:54PM +0200, Andreas Scheuring wrote:
On Thu, 2015-06-11 at 09:30 +0100, Daniel P. Berrange wrote:
It seems the main reason for your new proposal is to deal with
the fact that on migration
On Wed, Jun 10, 2015 at 08:48:36AM +0200, Andreas Scheuring wrote:
Daniel,
if I got it right, the vif script blueprint only is about plug/unplug
operations and not about generating new xml representations for vif
types. What if for a new vif type it's sufficient to have the
get_config_*
On Wed, Jun 10, 2015 at 10:40:02AM -0500, Matt Riedemann wrote:
This is a follow-on to the thread [1] asking about modeling the
connection_info dict returned from the os-initialize_connection API.
The more I think about modeling that in Nova, the more I think it should
really be modeled in
On Tue, Jun 09, 2015 at 03:07:51PM +0100, Neil Jerram wrote:
On 04/06/15 13:05, Neil Jerram wrote:
Hi John,
On 04/06/15 12:21, John Garbutt wrote:
Hi,
We had a great discussion at the summit around priorities:
https://etherpad.openstack.org/p/YVR-nova-liberty-priorities
I have made a
On Tue, Jun 09, 2015 at 07:52:39PM +0300, Roman Bogorodskiy wrote:
Hi,
Few months ago I've started a discussion on FreeBSD host support for
OpenStack. [1] At a result of discussion it was figured out that there
are a number of limitations, mainly on the BHyVe (the FreeBSD hypervisor)
side,
On Fri, Jun 05, 2015 at 02:46:07PM +0200, Thierry Carrez wrote:
So.. summarizing the various options again:
Plan A
Just drop stable point releases.
(-) No more release notes
(-) Lack of reference points to compare installations
Plan B
Push date-based tags across supported projects from
On Wed, Jun 03, 2015 at 10:26:03AM -0400, Doug Hellmann wrote:
Excerpts from Daniel P. Berrange's message of 2015-06-03 14:28:01 +0100:
On Wed, Jun 03, 2015 at 03:09:28PM +0200, Thierry Carrez wrote:
John Garbutt wrote:
Given we are thinking Liberty is moving to semantic versioning,
On Wed, Jun 03, 2015 at 02:01:06PM +0100, John Garbutt wrote:
Hi,
(To be clear, this is a proposal to be discussed and not a decision.)
The version number can help us communicate that:
* you can consume a milestone release
** ... but the docs and translations may not be totally up to date
On Wed, Jun 03, 2015 at 03:09:28PM +0200, Thierry Carrez wrote:
John Garbutt wrote:
Given we are thinking Liberty is moving to semantic versioning, maybe
it could look like this:
* 12.0.1 (liberty-1) will have some features (hopefully), and will be a tag
* 12.0.2.dev1 is the first commit
On Mon, Jun 01, 2015 at 09:44:24AM +0100, John Garbutt wrote:
On 29 May 2015 at 18:32, Neil Jerram neil.jer...@metaswitch.com wrote:
Hi all,
Per yesterday's IRC meeting [1], and discussion in Vancouver, Nova work is
being somewhat driven by the etherpad at [2]. But this etherpad doesn't
On Fri, May 29, 2015 at 06:32:18PM +0100, Neil Jerram wrote:
Hi all,
Per yesterday's IRC meeting [1], and discussion in Vancouver, Nova work is
being somewhat driven by the etherpad at [2]. But this etherpad doesn't
have a section for libvirt / vif driver changes. The log at [1] briefly
On Thu, May 28, 2015 at 11:55:59AM +0300, Feodor Tersin wrote:
+1
But we should answer the following question before switching libvirt to
utils.get_image_from_system_metadata.
Some differences of utils.get_image_from_system_metadata from
compute.utils.get_image_metadata are:
1) Instance
On Thu, May 28, 2015 at 12:22:59PM +0300, Feodor Tersin wrote:
I mean the case:
- an image has long property AAA and non inheritable property BBB;
- an instance based on the image stores truncated AAA and full BBB;
- utils.get_image_from_system_metadata returns truncated AAA but not BBB;
-
On Wed, May 27, 2015 at 04:53:38PM +0200, Thierry Carrez wrote:
Hi everyone,
TL;DR:
IRC meetings list now lives at http://eavesdrop.openstack.org
ical file with meetings is now at
http://eavesdrop.openstack.org/irc-meetings.ical
This is very nice work indeed - must better than the wiki
As part of the work to object-ify the image metadata dicts, I'm looking
at the current way the libvirt driver fetches image metadata for an
instance, in cases where the compute manager hasn't already passed it
into the virt driver API. I see 2 methods that libvirt uses to get the
image metadata
On Fri, May 22, 2015 at 02:57:23PM -0700, Michael Still wrote:
Hey,
it would be cool if devs posting changes for nova which depend on us
approving their spec could use Depends-On to make sure their code
doesn't land until the spec does.
Does it actually bring any benefit ? Any change for
On Wed, May 20, 2015 at 03:01:50PM -0700, Michael Still wrote:
I note that we use instance.name to lookup the libvirt domain a bunch
in the driver. I'm wondering why we don't just use instance.uuid all
the time -- the code for that already exists. Is there a good reason
to not move to always
On Thu, May 21, 2015 at 09:34:20PM +1200, Xav Paice wrote:
On 21/05/15 21:23, Daniel P. Berrange wrote:
On Wed, May 20, 2015 at 03:01:50PM -0700, Michael Still wrote:
I note that we use instance.name to lookup the libvirt domain a bunch
in the driver. I'm wondering why we don't just use
On Wed, May 20, 2015 at 05:43:07PM +0800, Zhi Yan Liu wrote:
On Wed, May 20, 2015 at 5:23 PM, Zhi Yan Liu lzy@gmail.com wrote:
On Wed, May 20, 2015 at 5:06 PM, Daniel P. Berrange berra...@redhat.com
wrote:
On Wed, May 20, 2015 at 12:01:37AM +0200, Flavio Percoco wrote:
On 19/05/15 17
On Wed, May 20, 2015 at 06:11:26PM +0800, Luo Gangyi wrote:
Hi devs,
I find a serious problem when I try to live migrate a hybrid instance
(instance based on local disk and cinder volume attached) .
In current nova, such operation is allowed.
But I don't think libvirt can deal
On Wed, May 20, 2015 at 12:01:37AM +0200, Flavio Percoco wrote:
On 19/05/15 17:19 +0100, Daniel P. Berrange wrote:
In Nova we are attempting to model[1] the glance image metadata and
properties using the Nova object model (now oslo.versionedobjects).
The one item I'm stuck on understanding
On Tue, May 19, 2015 at 04:41:40PM +0200, Markus Zoeller wrote:
The libvirt driver logs a warning if:
hostarch not in (arch.I686, arch.X86_64))
The warning when I start the libvirt driver on system z (arch.S390X)
will be:
The libvirt driver is not tested on kvm/s390x by the OpenStack
In Nova we are attempting to model[1] the glance image metadata and
properties using the Nova object model (now oslo.versionedobjects).
The one item I'm stuck on understanding is the 'locations' field
and more specifically the 'metadata' element in each location
entry
In the file
On Fri, May 15, 2015 at 06:14:08PM +0100, John Garbutt wrote:
On 15 May 2015 at 17:41, Daniel P. Berrange berra...@redhat.com wrote:
Its tempting to say its scheduled for removal in N? So we have time to
work out if thats possible.
I think that at the start of each dev cycle, we look
On Thu, May 14, 2015 at 02:23:25PM -0500, Matt Riedemann wrote:
The minimum required version of libvirt in the driver is 0.9.11 still [1].
We've been gating against 1.2.2 in Ubuntu Trusty 14.04 since Juno.
The libvirt distro support matrix is here: [2]
Can we safely assume the people
On Fri, May 15, 2015 at 11:51:22AM +0100, Daniel P. Berrange wrote:
On Thu, May 14, 2015 at 02:23:25PM -0500, Matt Riedemann wrote:
The minimum required version of libvirt in the driver is 0.9.11 still [1].
We've been gating against 1.2.2 in Ubuntu Trusty 14.04 since Juno.
The libvirt
On Fri, May 15, 2015 at 11:51:22AM +0100, Daniel P. Berrange wrote:
On Thu, May 14, 2015 at 02:23:25PM -0500, Matt Riedemann wrote:
The minimum required version of libvirt in the driver is 0.9.11 still [1].
We've been gating against 1.2.2 in Ubuntu Trusty 14.04 since Juno.
The libvirt
On Fri, May 15, 2015 at 12:41:20PM +0100, Matthew Booth wrote:
I was looking at the migrations api, and I noticed that the api passes
the request query unchecked to get_migrations, where it ultimately ends
up in a db query. I was curious and spent a couple of hours checking
this morning. There
On Fri, May 15, 2015 at 02:45:06PM +0100, John Garbutt wrote:
On 15 May 2015 at 13:28, Daniel P. Berrange berra...@redhat.com wrote:
On Fri, May 15, 2015 at 11:51:22AM +0100, Daniel P. Berrange wrote:
On Thu, May 14, 2015 at 02:23:25PM -0500, Matt Riedemann wrote:
There are some
On Fri, May 15, 2015 at 05:27:35PM +0100, John Garbutt wrote:
On 15 May 2015 at 11:51, Daniel P. Berrange berra...@redhat.com wrote:
On Thu, May 14, 2015 at 02:23:25PM -0500, Matt Riedemann wrote:
The minimum required version of libvirt in the driver is 0.9.11 still [1].
We've been gating
On Mon, May 11, 2015 at 03:58:59PM -0400, Russell Bryant wrote:
On 05/11/2015 03:51 PM, Adrian Otto wrote:
I invite Nova and nova-docker team members to join us to discuss
this topic, and give us your input.
If the Magnum team is interested in helping to maintain it, why not just
keep it
On Mon, May 11, 2015 at 02:57:08PM +0100, John Garbutt wrote:
On 9 May 2015 at 17:55, Adrian Otto adrian.o...@rackspace.com wrote:
On the subject of extending the Nova API to accommodate special use cases
of containers that are beyond the scope of the Nova API, I think we should
resist
A friendly reminder that KVM Forum 2015 accepts proposal submissions
until this coming Friday.
Thanks on behalf of the KVM Forum 2015 Program Committee.
Daniel
On Wed, Mar 18, 2015 at 09:51:31AM +, Daniel P. Berrange wrote
On Wed, Apr 22, 2015 at 12:57:01PM +0200, Kashyap Chamarthy wrote:
On Tue, Apr 21, 2015 at 02:58:57PM -0700, Joe Gordon wrote:
On Fri, Apr 17, 2015 at 1:22 AM, Victor Stinner vstin...@redhat.com wrote:
For the full list, see the wiki page:
On Fri, Apr 17, 2015 at 12:16:25PM -0400, Jay Pipes wrote:
On 04/10/2015 11:48 AM, Neil Jerram wrote:
What I imagine, though, is that the _source_ of the plugging information
could move from Nova to Neutron, so that future plugging-related code
changes are a matter for Neutron rather than for
On Tue, Apr 14, 2015 at 01:44:45PM -0400, Russell Bryant wrote:
On 04/14/2015 12:22 PM, Matt Riedemann wrote:
This came up in IRC this morning, but the hypervisor support matrix is
listing evacuate as 'missing' for the libvirt driver:
On Tue, Mar 31, 2015 at 11:37:04AM +0800, zhang bo wrote:
On 2015/3/31 4:36, Eric Blake wrote:
On 03/30/2015 06:08 AM, Michal Privoznik wrote:
On 30.03.2015 11:28, zhang bo wrote:
On 2015/3/28 18:06, Rui Chen wrote:
snip/
The API virDomainShutdown's description is out of date,
On Tue, Apr 07, 2015 at 12:57:40PM +0200, Ihar Hrachyshka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+344 new lines of code for an exception patch? No way. Let's take time
to consider the patch outside the very next release.
Agreed, I think it needs a little more time to soak in
=
KVM Forum 2015: Call For Participation
August 19-21, 2015 - Sheraton Seattle - Seattle, WA
(All submissions must be received before midnight May 1, 2015)
=
KVM is an
On Wed, Mar 18, 2015 at 08:33:26AM +0100, Thomas Herve wrote:
Interesting bug. I think I agree with you that there isn't a good solution
currently for instances that have a mix of shared and not-shared storage.
I'm curious what Daniel meant by saying that marking the disk shareable is
On Tue, Mar 17, 2015 at 01:33:26PM -0700, Joe Gordon wrote:
On Thu, Jun 19, 2014 at 1:38 AM, Daniel P. Berrange berra...@redhat.com
wrote:
On Wed, Jun 18, 2014 at 11:09:33PM -0700, Rafi Khardalian wrote:
I am concerned about how block migration functions when Cinder volumes
On Wed, Mar 18, 2015 at 10:59:19AM -0700, Joe Gordon wrote:
On Wed, Mar 18, 2015 at 3:09 AM, Daniel P. Berrange berra...@redhat.com
wrote:
On Wed, Mar 18, 2015 at 08:33:26AM +0100, Thomas Herve wrote:
Interesting bug. I think I agree with you that there isn't a good
solution
On Fri, Mar 13, 2015 at 11:18:15AM -0600, Chris Friesen wrote:
On 03/13/2015 07:50 AM, Daniel P. Berrange wrote:
On Fri, Mar 13, 2015 at 08:42:25AM -0400, Steve Gordon wrote:
- Original Message -
From: park jianlong...@gmail.com
To: OpenStack Development Mailing List (not for usage
On Fri, Mar 13, 2015 at 08:42:25AM -0400, Steve Gordon wrote:
- Original Message -
From: park jianlong...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
hello Nova
By default, nova libvirt driver configuration
On Thu, Mar 12, 2015 at 09:07:30AM -0500, Flavio Percoco wrote:
On 11/03/15 15:06 -1000, John Bresnahan wrote:
FWIW I agree with #3 and #4 but not #1 and #2. Spelling is an easy enough
thing to get right and speaks to the quality standard to which the product
is held even in commit messages
On Sun, Mar 08, 2015 at 11:19:10PM +0100, Thomas Goirand wrote:
On 03/08/2015 06:34 PM, Mike Bayer wrote:
Ian Wells ijw.ubu...@cack.org.uk wrote:
With apologies for derailing the question, but would you care to tell us
what evil you're planning on doing? I find it's always best
On Thu, Mar 05, 2015 at 07:39:23PM +, Murray, Paul (HP Cloud) wrote:
Hi All,
I know Yunhong Jiang and Daniel Berrange have been involved in the following,
but I thought it worth sending to the list for visibility.
While writing code to convert the resource tracker to use the
On Wed, Mar 04, 2015 at 05:24:53PM +, Jiang, Yunhong wrote:
Daniel, thanks for your clarification.
Another related question is, what will be the guest's real cpu model
is the cpu_model is None? This is about a reported regression at
The guest CPU will be unspecified - it will be some
On Fri, Feb 27, 2015 at 08:57:53AM -0800, Dan Smith wrote:
Note that in the above case the libvirt driver changed the hypervisor
identifier despite the fact that the hypervisor had not changed, only
its communication endpoint.
I'd argue they're one and the same, and that's just fine. We
On Fri, Feb 27, 2015 at 04:24:36PM +, Matthew Booth wrote:
Gary Kotton originally posted this bug against the VMware driver:
https://bugs.launchpad.net/nova/+bug/1419785
I posted a proposed patch to fix this here:
https://review.openstack.org/#/c/158269/1
However, Dan Smith
On Fri, Feb 27, 2015 at 09:51:34AM +1100, Michael Still wrote:
On Fri, Feb 27, 2015 at 9:41 AM, Stefano Maffulli stef...@openstack.org
wrote:
Does it make sense to purge old stuff regularly so we have a better
overview? Or maybe we should chart a distribution of age of proposed
On Thu, Feb 26, 2015 at 01:06:14AM +0100, Thomas Goirand wrote:
On 02/24/2015 12:27 PM, Daniel P. Berrange wrote:
I'm actually trying to judge it from the POV of users, not just
developers. I find it pretty untenable that in the fast moving
world of cloud, users have to wait as long as 6
On Wed, Feb 25, 2015 at 11:46:05AM +, Neil Jerram wrote:
Although we are past the non-priority deadline, I have been encouraged
to request this late exception for Project Calico's spec and code adding
VIF_TYPE_TAP to Nova.
I'm afraid you're also past the freeze exception request deadline.
On Wed, Feb 25, 2015 at 10:31:58AM +0100, Thierry Carrez wrote:
Robert Collins wrote:
It's also worth noting that we were on a 3-month cycle at the start of
OpenStack. That was dropped after a cataclysmic release that managed the
feat of (a) not having anything significant done, and (b)
On Mon, Feb 23, 2015 at 03:24:01PM -0500, Jay Pipes wrote:
Here's another thought: is the big-bang integrated 6-month fixed release
cycle useful any more? Can we talk about using more of a moving train model
that doesn't have these long freeze cycles? At least for some of the
projects, I think
On Tue, Feb 24, 2015 at 11:48:29AM +, Chris Dent wrote:
On Tue, 24 Feb 2015, Daniel P. Berrange wrote:
need to do more work. If this is so, then I don't think this is a blocker,
it is just a sign that the project needs to focus on providing more resources
to the teams impacted
On Mon, Feb 23, 2015 at 04:14:36PM -0800, Joe Gordon wrote:
Was:
http://lists.openstack.org/pipermail/openstack-dev/2015-February/057578.html
There has been frustration with our current 6 month development cadence.
This is an attempt to explain those frustrations and propose a very rough
On Tue, Feb 24, 2015 at 08:50:45AM -0500, Sean Dague wrote:
On 02/24/2015 07:48 AM, Russell Bryant wrote:
On 02/24/2015 12:54 PM, Daniel P. Berrange wrote:
On Tue, Feb 24, 2015 at 11:48:29AM +, Chris Dent wrote:
On Tue, 24 Feb 2015, Daniel P. Berrange wrote:
need to do more work
On Fri, Feb 20, 2015 at 10:49:29AM -0800, Joe Gordon wrote:
On Fri, Feb 20, 2015 at 7:29 AM, Deepak Shetty dpkshe...@gmail.com wrote:
Hi Jeremy,
Couldn't find anything strong in the logs to back the reason for OOM.
At the time OOM happens, mysqld and java processes have the most RAM
On Mon, Feb 23, 2015 at 11:52:29AM +0100, Raphael Glon wrote:
On 02/23/2015 11:23 AM, Daniel P. Berrange wrote:
The alternative Nova implementation is*not* using fuse, it is using real
mounts on the host FS. This is not a potential issue, it is an*actual*
issue. There have been bugs in Linux
On Mon, Feb 23, 2015 at 11:08:31AM +0100, Raphael Glon wrote:
On 02/19/2015 12:45 PM, Richard W.M. Jones wrote:
On Wed, Feb 18, 2015 at 07:23:52PM +0100, Raphael Glon wrote:
I entcountered a similar case more recently on powerkvm 2.1.0
(defect with the libguestfs)
What's the actual bug?
On Mon, Feb 23, 2015 at 11:54:40AM +0100, Raphael Glon wrote:
On 02/23/2015 11:23 AM, Daniel P. Berrange wrote:
Fedora 19 is end of life so not really relevant any more as a target.
powerkvm 2.1.x is not eol
Well Fedora 19 is end of life, so if powerkvm is using Fedora 19, then
it is running
On Mon, Feb 23, 2015 at 03:47:20PM +0100, Nikola Đipanov wrote:
On 02/20/2015 11:33 PM, Sourabh Patwardhan (sopatwar) wrote:
Nova core reviewers,
May I request an FFE for Cisco VIF driver:
https://review.openstack.org/#/c/157616/
This is a small isolated change similar to the
On Wed, Feb 18, 2015 at 07:23:52PM +0100, Raphael Glon wrote:
Hi,
This is about review:
https://review.openstack.org/#/c/156633/
1 line, can be controversial
Its purpose is to add the possibility not to use libguestfs for data
injection in nova, even when installed.
Not discussing
On Tue, Feb 17, 2015 at 09:29:19AM -0800, Clint Byrum wrote:
Excerpts from Daniel P. Berrange's message of 2015-02-17 02:37:50 -0800:
On Wed, Feb 11, 2015 at 03:14:39PM +0100, Stefano Maffulli wrote:
## Cores are *NOT* special
At some point, for some reason that is unknown to me,
On Tue, Feb 17, 2015 at 09:32:53AM -0800, Stefano Maffulli wrote:
Changing the subject since Flavio's call for openness was broader than
just private IRC channels.
On Tue, 2015-02-17 at 10:37 +, Daniel P. Berrange wrote:
If cases of bad community behaviour, such as use of passwd
On Wed, Feb 11, 2015 at 03:14:39PM +0100, Stefano Maffulli wrote:
## Cores are *NOT* special
At some point, for some reason that is unknown to me, this message
changed and the feeling of core's being some kind of superheros became
a thing. It's gotten far enough to the point that I've
On Tue, Feb 17, 2015 at 11:28:58AM +0100, Christian Berendt wrote:
Is it safe to remove copyright statements above the Apache 2.0 license
headers stated in a lot of files?
We recenctly removed all @author tags and added a hacking check to not
longer add @author tags in the future. Can we do
On Tue, Feb 17, 2015 at 01:16:46PM +0100, Christian Berendt wrote:
On 02/17/2015 12:05 PM, Daniel P. Berrange wrote:
In section 4.(c) the LICENSE text says
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent
On Mon, Feb 16, 2015 at 04:31:21PM +0300, Dmitry Guryanov wrote:
On 02/13/2015 05:50 PM, Jay Pipes wrote:
On 02/13/2015 09:20 AM, Daniel P. Berrange wrote:
On Fri, Feb 13, 2015 at 08:49:26AM -0500, Jay Pipes wrote:
On 02/13/2015 07:04 AM, Daniel P. Berrange wrote:
Historically Nova has had
On Mon, Feb 16, 2015 at 03:06:34PM +0100, Philipp Marek wrote:
Hi all,
Nikola just told me that I need an FFE for the code as well.
Here it is: please grant a FFE for
https://review.openstack.org/#/c/149244/
which is the code for the spec at
The following page contains a list of (hopefully) all the feature
freeze exception requests that have been made so far for Nova
https://etherpad.openstack.org/p/kilo-nova-ffe-requests
Finding them all in the mailing list is not entirely easy, so if you
have requested FFE please do make sure
On Mon, Feb 16, 2015 at 01:39:21PM +1300, Robert Collins wrote:
On 19 June 2014 at 20:38, Daniel P. Berrange berra...@redhat.com wrote:
On Wed, Jun 18, 2014 at 11:09:33PM -0700, Rafi Khardalian wrote:
I am concerned about how block migration functions when Cinder volumes are
attached
On Sun, Feb 15, 2015 at 02:34:26PM +, Jeremy Stanley wrote:
On 2015-02-15 07:00:53 + (+), Gary Kotton wrote:
Yes, I think that they go out in batches. It would be best to check with
Stefano if you have any issues.
Also a reminder, you need to be the owner of a change in Gerrit
On Mon, Feb 16, 2015 at 02:53:08PM +0300, aburluka wrote:
Hi,
There are some questions about FFE policy that are not obvious for me as a
newbie.
Last version of my change was submitted at February, 11th, and has not been
changed since that date.
That change has +2 from Daniel and +1 from
Historically Nova has had a bunch of code which mounted images on the
host OS using qemu-nbd before passing them to libvirt to setup the
LXC container. Since 1.0.6, libvirt is able todo this itself and it
would simplify the codepaths in Nova if we can rely on that
In general, without use of user
On Thu, Feb 12, 2015 at 12:32:10PM -0500, Sean Dague wrote:
Looking recently at the following failure -
http://logs.openstack.org/04/154804/1/gate/gate-nova-python27/1fe94bf/console.html#_2015-02-12_15_02_19_593
It appears that the fakelibvirt fixture is potentially causing races in
tests
On Thu, Feb 12, 2015 at 01:17:55PM -0500, Sean Dague wrote:
On 02/12/2015 01:09 PM, Daniel P. Berrange wrote:
On Thu, Feb 12, 2015 at 12:32:10PM -0500, Sean Dague wrote:
Looking recently at the following failure -
http://logs.openstack.org/04/154804/1/gate/gate-nova-python27/1fe94bf
On Thu, Feb 12, 2015 at 11:49:12AM -0600, Matt Riedemann wrote:
On 2/12/2015 11:32 AM, Sean Dague wrote:
Looking recently at the following failure -
http://logs.openstack.org/04/154804/1/gate/gate-nova-python27/1fe94bf/console.html#_2015-02-12_15_02_19_593
It appears that the fakelibvirt
On Mon, Feb 09, 2015 at 10:04:49AM +, Czesnowicz, Przemyslaw wrote:
Hi,
I would like to request FFE for vhostuser vif driver.
2 reviews :
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/libvirt-vif-vhost-user,n,z
BP:
On Thu, Feb 12, 2015 at 12:18:49PM +, Claudiu Belu wrote:
Hello.
I would like to request a FFE for the Hyper-V unit tests refactoring
blueprint:
https://blueprints.launchpad.net/nova/+spec/hyper-v-test-refactoring
The point of the blueprint was to get rid of the ancient
201 - 300 of 744 matches
Mail list logo
