Re: [openstack-dev] [nova][libvirt] Non-readonly connection to libvirt in unit tests

On Mon, Aug 04, 2014 at 06:46:13PM -0400, Solly Ross wrote: > Hi, > I was wondering if there was a way to get a non-readonly connection > to libvirt when running the unit tests > on the CI. If I call `LibvirtDriver._connect(LibvirtDriver.uri())`, > it works fine locally, but the upstream > CI barf

Re: [openstack-dev] [nova] fair standards for all hypervisor drivers

On Mon, Aug 11, 2014 at 08:57:31AM +1000, Michael Still wrote: > On Sun, Aug 10, 2014 at 2:33 AM, Jeremy Stanley wrote: > > On 2014-08-08 09:06:29 -0400 (-0400), Russell Bryant wrote: > > [...] > >> We've seen several times that building and maintaining 3rd party > >> CI is a *lot* of work. > > >

Re: [openstack-dev] [nova] fair standards for all hypervisor drivers

On Fri, Aug 08, 2014 at 09:06:29AM -0400, Russell Bryant wrote: > On 08/07/2014 08:06 PM, Michael Still wrote: > > It seems to me that the tension here is that there are groups who > > would really like to use features in newer libvirts that we don't CI > > on in the gate. Is it naive to think that

Re: [openstack-dev] [nova] fair standards for all hypervisor drivers

On Mon, Aug 11, 2014 at 07:58:41AM -0400, Russell Bryant wrote: > On 08/11/2014 05:53 AM, Daniel P. Berrange wrote: > > There is work to add support for this in devestack already which I > > prefer since it makes it easy for developers to get an environment > > which mat

Re: [openstack-dev] [nova] fair standards for all hypervisor drivers

On Mon, Aug 11, 2014 at 01:45:56PM +, Jeremy Stanley wrote: > On 2014-08-11 08:07:02 -0400 (-0400), Russell Bryant wrote: > > There's a pypi mirror at least. I'm not sure about mirroring > > other things. > > Right, that's a specific solution for mirroring the pypi.python.org > cheeseshop. We

Re: [openstack-dev] [nova] fair standards for all hypervisor drivers

On Mon, Aug 11, 2014 at 03:25:39PM -0700, Joe Gordon wrote: > I am not sure if I follow. The gate issue with live snapshots has been > worked around by turning it off [0], so presumably this patch is forward > facing. I fail to see how this patch is needed to help the gate in the > future. Wouldn

Re: [openstack-dev] [nova] Retrospective veto revert policy

On Tue, Aug 12, 2014 at 03:56:44PM +0100, Mark McLoughlin wrote: > Hey > > (Terrible name for a policy, I know) > > From the version_cap saga here: > > https://review.openstack.org/110754 > > I think we need a better understanding of how to approach situations > like this. > > Here's my atte

Re: [openstack-dev] [nova] so what do i do about libvirt-python if i'm on precise?

On Tue, Aug 12, 2014 at 10:09:52PM +0100, Mark McLoughlin wrote: > On Wed, 2014-07-30 at 15:34 -0700, Clark Boylan wrote: > > On Wed, Jul 30, 2014, at 03:23 PM, Jeremy Stanley wrote: > > > On 2014-07-30 13:21:10 -0700 (-0700), Joe Gordon wrote: > > > > While forcing people to move to a newer versio

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Wed, Aug 13, 2014 at 08:57:40AM +1000, Michael Still wrote: > Hi. > > One of the action items from the nova midcycle was that I was asked to > make nova's expectations of core reviews more clear. This email is an > attempt at that. > > Nova expects a minimum level of sustained code reviews fro

Re: [openstack-dev] [all] The future of the integrated release

On Mon, Aug 11, 2014 at 10:30:12PM -0700, Joe Gordon wrote: > On Fri, Aug 8, 2014 at 6:58 AM, Kyle Mestery wrote: > > > I really like this idea, as Michael and others alluded to in above, we > > are > > > attempting to set cycle goals for Kilo in Nova. but I think it is worth > > > doing for all o

Re: [openstack-dev] [all] The future of the integrated release

On Thu, Aug 07, 2014 at 03:56:04AM -0700, Jay Pipes wrote: > On 08/07/2014 02:12 AM, Kashyap Chamarthy wrote: > >On Thu, Aug 07, 2014 at 07:10:23AM +1000, Michael Still wrote: > >>On Wed, Aug 6, 2014 at 2:03 AM, Thierry Carrez > >>wrote: > >> > >>>We seem to be unable to address some key issues i

Re: [openstack-dev] [all] The future of the integrated release

On Wed, Aug 13, 2014 at 12:55:48PM +0100, Steven Hardy wrote: > On Wed, Aug 13, 2014 at 11:42:52AM +0100, Daniel P. Berrange wrote: > > On Thu, Aug 07, 2014 at 03:56:04AM -0700, Jay Pipes wrote: > > > That said, I entirely agree with you and wish efforts to stabilize would >

Re: [openstack-dev] [all] The future of the integrated release

On Wed, Aug 13, 2014 at 09:11:26AM -0400, Russell Bryant wrote: > On 08/13/2014 08:52 AM, Mark McLoughlin wrote: > > On Tue, 2014-08-12 at 14:26 -0400, Eoghan Glynn wrote: > >> > It seems like this is exactly what the slots give us, though. The core > >> review > >>> team picks a number of slots

Re: [openstack-dev] [nova] so what do i do about libvirt-python if i'm on precise?

On Wed, Aug 13, 2014 at 04:24:57PM +0100, Mark McLoughlin wrote: > On Wed, 2014-08-13 at 10:26 +0100, Daniel P. Berrange wrote: > > On Tue, Aug 12, 2014 at 10:09:52PM +0100, Mark McLoughlin wrote: > > > On Wed, 2014-07-30 at 15:34 -0700, Clark Boylan wrote: > > > >

Re: [openstack-dev] Fwd: [nova][core] Expectations of core reviewers

On Wed, Aug 13, 2014 at 09:01:59AM -0700, Maru Newby wrote: > > On Aug 13, 2014, at 2:57 AM, Daniel P. Berrange wrote: > > > On Wed, Aug 13, 2014 at 08:57:40AM +1000, Michael Still wrote: > >> Hi. > >> > >> One of the action items from the nova midcycl

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Wed, Aug 13, 2014 at 09:18:09AM -0700, Maru Newby wrote: > > On Aug 13, 2014, at 2:57 AM, Daniel P. Berrange wrote: > > > On Wed, Aug 13, 2014 at 08:57:40AM +1000, Michael Still wrote: > >> Hi. > >> > >> One of the action items from the nova midcycl

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Thu, Aug 14, 2014 at 09:24:36AM +1000, Michael Still wrote: > On Thu, Aug 14, 2014 at 3:09 AM, Dan Smith wrote: > >> I'm not questioning the value of f2f - I'm questioning the idea of > >> doing f2f meetings sooo many times a year. OpenStack is very much > >> the outlier here among open source

Re: [openstack-dev] [all] 3rd Party CI vs. Gerrit

On Wed, Aug 13, 2014 at 12:05:27PM -0700, James E. Blair wrote: > cor...@inaugust.com (James E. Blair) writes: > > > Sean Dague writes: > > > >> This has all gone far enough that someone actually wrote a Grease Monkey > >> script to purge all the 3rd Party CI content out of Jenkins UI. People > >

Re: [openstack-dev] [nova] Retrospective veto revert policy

On Thu, Aug 14, 2014 at 10:06:13AM +0100, Mark McLoughlin wrote: > On Tue, 2014-08-12 at 15:56 +0100, Mark McLoughlin wrote: > > Hey > > > > (Terrible name for a policy, I know) > > > > From the version_cap saga here: > > > > https://review.openstack.org/110754 > > > > I think we need a bette

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Thu, Aug 14, 2014 at 08:31:48AM -0400, Russell Bryant wrote: > On 08/13/2014 11:31 PM, Michael Still wrote: > > On Thu, Aug 14, 2014 at 1:24 PM, Jay Pipes wrote: > > > >> Just wanted to quickly weigh in with my thoughts on this important topic. I > >> very much valued the face-to-face interact

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Thu, Aug 14, 2014 at 10:30:59AM -0500, Kyle Mestery wrote: > On Thu, Aug 14, 2014 at 10:13 AM, Sandy Walsh > wrote: > > On 8/14/2014 11:28 AM, Russell Bryant wrote: > >> On 08/14/2014 10:04 AM, CARVER, PAUL wrote: > >>> Daniel P. Berrange [

[openstack-dev] Using gerrymander, a client API and command line tool for gerrit

Over the past couple of months I've worked on creating a python library and command line tool for dealing with gerrit. I've blogged about this a number of times on http://planet.openstack.org, but I figure there are quite a few people who won't be reading the blogs there or easily miss some posts h

Re: [openstack-dev] [nova] Review priorities as we approach juno-3

On Fri, Aug 15, 2014 at 06:53:41AM +1000, Michael Still wrote: > On Fri, Aug 15, 2014 at 6:37 AM, Dan Smith wrote: > >> == Move Virt Drivers to use Objects (Juno Work) == > >> > >> I couldn't actually find any code out for review for this one apart > >> from https://review.openstack.org/#/c/94477/

Re: [openstack-dev] [neutron][ml2] Mech driver as out-of-tree add-on

On Thu, Aug 14, 2014 at 12:09:26PM +0200, Salvatore Orlando wrote: > I think there will soon be a discussion regarding what the appropriate > location for plugin and drivers should be. > My personal feeling is that Neutron has simply reached the tipping point > where the high number of drivers and

[openstack-dev] [nova] running pep8 tests much faster

We recently had a change merged to the run_tests.sh script that Nova developers would really benefit from knowing about: https://review.openstack.org/#/c/110746/ Basically, it provides a way to run the pep8 tests *only* against the files which you have actually touched in your patch. For most

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Mon, Aug 18, 2014 at 12:18:16PM +0200, Thierry Carrez wrote: > Doug Hellmann wrote: > > On Aug 13, 2014, at 4:42 PM, Russell Bryant wrote: > >> Let me try to say it another way. You seemed to say that it wasn't much > >> to ask given the rate at which things happen in OpenStack. I would > >>

Re: [openstack-dev] [All] LOG.warning/LOG.warn

On Mon, Aug 18, 2014 at 07:57:28AM +1000, Michael Still wrote: > My recollection is that this was a request from the oslo team, but it > was so long ago that I don't recall the details. > > I think the change is low value, so should only be done when someone > is changing the logging in a file alr

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Mon, Aug 18, 2014 at 11:18:52AM -0400, Russell Bryant wrote: > On 08/18/2014 06:18 AM, Thierry Carrez wrote: > > Doug Hellmann wrote: > >> On Aug 13, 2014, at 4:42 PM, Russell Bryant wrote: > >>> Let me try to say it another way. You seemed to say that it wasn't much > >>> to ask given the rat

Re: [openstack-dev] [All] LOG.warning/LOG.warn

On Mon, Aug 18, 2014 at 11:27:39AM -0400, Doug Hellmann wrote: > > On Aug 18, 2014, at 10:15 AM, Daniel P. Berrange wrote: > > > On Mon, Aug 18, 2014 at 07:57:28AM +1000, Michael Still wrote: > >> My recollection is that this was a request from the oslo team, but it >

Re: [openstack-dev] [TripleO] Specs and approvals

On Tue, Aug 19, 2014 at 09:31:48PM +1200, Robert Collins wrote: > Hey everybody - https://wiki.openstack.org/wiki/TripleO/SpecReviews > seems pretty sane as we discussed at the last TripleO IRC meeting. > > I'd like to propose that we adopt it with the following tweak: > > 19:46:34 so I propose

Re: [openstack-dev] Using gerrymander, a client API and command line tool for gerrit

On Thu, Aug 14, 2014 at 05:54:27PM +0100, Daniel P. Berrange wrote: > > In terms of how I personally use it (assuming the above config file)... > Vish pointed out that I made a bunch of stupid typos in my examples here. Next time I'll actually double-check what I write :-) >

Re: [openstack-dev] [Nova] Scheduler split wrt Extensible Resource Tracking

On Wed, Aug 20, 2014 at 08:33:31AM -0400, Jay Pipes wrote: > On 08/20/2014 04:48 AM, Nikola Đipanov wrote: > >On 08/20/2014 08:27 AM, Joe Gordon wrote: > >>On Aug 19, 2014 10:45 AM, "Day, Phil" >>> wrote: > >>> > -Original Message- > From: Nikola Đipanov [

Re: [openstack-dev] [nova][neutron] Migration from nova-network to Neutron for large production clouds

On Wed, Aug 20, 2014 at 03:17:40PM +, Tim Bell wrote: > Michael has been posting very informative blogs on the summary of > the mid-cycle meetups for Nova. The one on the Nova Network to > Neutron migration was of particular interest to me as it raises a > number of potential impacts for the CE

[openstack-dev] [nova] Prioritizing review of potentially "approvable" patches

Tagged with '[nova]' but this might be relevant data / idea for other teams too. With my code contributor hat on, one of the things that I find most the frustrating about Nova code review process is that a patch can get a +2 vote from one core team member and then sit around for days, weeks, even

Re: [openstack-dev] [nova] Prioritizing review of potentially "approvable" patches

On Thu, Aug 21, 2014 at 08:26:29AM -0500, Matt Riedemann wrote: > > > On 8/21/2014 7:09 AM, Sean Dague wrote: > >FWIW, this is one of my normal morning practices, and the reason that > >that query is part of most of the gerrit dashboards - > >https://github.com/stackforge/gerrit-dash-creator/blob

Re: [openstack-dev] [nova][libvirt] Non-readonly connection to libvirt in unit tests

On Thu, Aug 21, 2014 at 10:52:42AM -0400, Solly Ross wrote: > FYI, the context of this is that I would like to be able to test some > of the libvirt storage pool code against a live file system, as we > currently test the storage pool code. To do this, we need at least to > be able to get a prope

Re: [openstack-dev] New feature on Nova

On Thu, Aug 21, 2014 at 05:00:59PM +0200, thomas.pessi...@orange.com wrote: > Hello, > > Sorry if I am not on the right mailing list. I would like to get some > information. > > I would like to know if I am a company who wants to add a feature on > an openstack module. How do we have to proceed ?

Re: [openstack-dev] [nova][libvirt] Non-readonly connection to libvirt in unit tests

On Thu, Aug 21, 2014 at 11:14:33AM -0400, Solly Ross wrote: > (reply inline) > > - Original Message - > > From: "Daniel P. Berrange" > > To: "OpenStack Development Mailing List (not for usage questions)" > > > > Sent: Thursday, Au

Re: [openstack-dev] Criteria for giving a -1 in a review

On Thu, Aug 21, 2014 at 05:05:04PM +0100, Matthew Booth wrote: > "I would prefer that you didn't merge this." > > i.e. The project is better off without it. A bit off topic, but I've never liked this message that gets added as it think it sounds overly negative. It would better written as "Thi

Re: [openstack-dev] Criteria for giving a -1 in a review

On Thu, Aug 21, 2014 at 11:34:48AM -0500, Dolph Mathews wrote: > On Thu, Aug 21, 2014 at 11:21 AM, Daniel P. Berrange > wrote: > > > On Thu, Aug 21, 2014 at 05:05:04PM +0100, Matthew Booth wrote: > > > "I would prefer that you didn't merge this." >

Re: [openstack-dev] Criteria for giving a -1 in a review

On Thu, Aug 21, 2014 at 12:42:43PM -0400, Adam Young wrote: > On 08/21/2014 12:34 PM, Dolph Mathews wrote: > > > >On Thu, Aug 21, 2014 at 11:21 AM, Daniel P. Berrange ><mailto:berra...@redhat.com>> wrote: > > > >On Thu, Aug 21, 2014 at 05:05:04PM +0100,

Re: [openstack-dev] Criteria for giving a -1 in a review

On Thu, Aug 21, 2014 at 12:40:59PM -0400, Adam Young wrote: > On 08/21/2014 12:21 PM, Daniel P. Berrange wrote: > >On Thu, Aug 21, 2014 at 05:05:04PM +0100, Matthew Booth wrote: > >>"I would prefer that you didn't merge this." > >> > >>i.e. The p

Re: [openstack-dev] Criteria for giving a -1 in a review

On Thu, Aug 21, 2014 at 01:12:16PM -0400, Zane Bitter wrote: > On 21/08/14 12:21, Daniel P. Berrange wrote: > >On Thu, Aug 21, 2014 at 05:05:04PM +0100, Matthew Booth wrote: > >>>"I would prefer that you didn't merge this." > >>> > >>>i

Re: [openstack-dev] [nova][libvirt] Non-readonly connection to libvirt in unit tests

On Thu, Aug 21, 2014 at 12:23:12PM -0500, Matt Riedemann wrote: > > > On 8/21/2014 11:37 AM, Clark Boylan wrote: > > > > > >On Thu, Aug 21, 2014, at 09:25 AM, Matt Riedemann wrote: > >> > >> > >>On 8/21/2014 10:23 AM, Daniel P. Berrange wrote

Re: [openstack-dev] Criteria for giving a -1 in a review

On Thu, Aug 21, 2014 at 04:52:37PM -0500, Dolph Mathews wrote: > On Thu, Aug 21, 2014 at 11:53 AM, Daniel P. Berrange > wrote: > > > On Thu, Aug 21, 2014 at 11:34:48AM -0500, Dolph Mathews wrote: > > > On Thu, Aug 21, 2014 at 11:21 AM, Daniel P. Berrange < > >

Re: [openstack-dev] Adding GateFailureFix tag to commit messages

On Thu, Aug 21, 2014 at 09:02:17AM -0700, Armando M. wrote: > Hi folks, > > According to [1], we have ways to introduce external references to commit > messages. > > These are useful to mark certain patches and their relevance in the context > of documentation, upgrades, etc. > > I was wondering

Re: [openstack-dev] Criteria for giving a -1 in a review

On Fri, Aug 22, 2014 at 10:49:51AM +0100, Steven Hardy wrote: > On Thu, Aug 21, 2014 at 05:05:04PM +0100, Matthew Booth wrote: > > I also think it's worth explicitly documenting a few things we > > might/should mention in a review, but which aren't a reason that the > > project would be better off

Re: [openstack-dev] [glance] [infra] Glance review patterns and their impact on the gate

On Fri, Aug 22, 2014 at 07:09:10AM -0500, Sean Dague wrote: > Earlier this week the freshness checks (the ones that required passing > results within 24 hrs for a change to go into the gate) were removed to > try to conserve nodes as we get to crunch time. The hopes were that > review teams had eno

Re: [openstack-dev] [all] [ptls] The Czar system, or how to scale PTLs

On Fri, Aug 22, 2014 at 02:33:27PM +0200, Thierry Carrez wrote: > Hi everyone, > > We all know being a project PTL is an extremely busy job. That's because > in our structure the PTL is responsible for almost everything in a project: > > - Release management contact > - Work prioritization > - Ke

Re: [openstack-dev] [nova][libvirt] Non-readonly connection to libvirt in unit tests

On Fri, Aug 22, 2014 at 11:32:31AM -0400, Solly Ross wrote: > (response inline) > > - Original Message - > > From: "Daniel P. Berrange" > > To: "Solly Ross" > > Cc: "OpenStack Development Mailing List (not for usage questions)&qu

Re: [openstack-dev] [all] Design Summit reloaded

On Wed, Aug 27, 2014 at 02:51:55PM +0200, Thierry Carrez wrote: > Hi everyone, > > I've been thinking about what changes we can bring to the Design Summit > format to make it more productive. I've heard the feedback from the > mid-cycle meetups and would like to apply some of those ideas for Paris

Re: [openstack-dev] [nova] Configuring libivrt VIF driver

On Tue, Aug 26, 2014 at 05:02:10PM +0300, Itzik Brown wrote: > Hi, > > Following the conversation [1]: > My understanding was that the way to use out of the tree vif_driver is to > set vif_driver option in nova.conf > until there is a better way to support such cases but the commit [2] removed > t

Re: [openstack-dev] [nova][NFV] VIF_VHOSTUSER

On Wed, Aug 27, 2014 at 04:06:25PM +0200, Luke Gorrie wrote: > Howdy! > > I am writing to ask whether it will be possible to merge VIF_VHOSTUSER [1] > in Juno? > > VIF_VHOSTUSER adds support for a QEMU 2.1 has a feature called vhost-user > [2] that allows a guest to do Virtio-net I/O via a usersp

Re: [openstack-dev] [nova] Configuring libivrt VIF driver

On Thu, Aug 28, 2014 at 06:45:58AM +0300, Itzik Brown wrote: > > On 27/08/2014 17:06, Daniel P. Berrange wrote: > >On Tue, Aug 26, 2014 at 05:02:10PM +0300, Itzik Brown wrote: > >>Hi, > >> > >>Following the conversation [1]: > >>My understanding wa

Re: [openstack-dev] [nova] Is the BP approval process broken?

On Thu, Aug 28, 2014 at 01:04:57AM +, Dugger, Donald D wrote: > I'll try and not whine about my pet project but I do think there > is a problem here. For the Gantt project to split out the scheduler > there is a crucial BP that needs to be implemented ( > https://review.openstack.org/#/c/89893

Re: [openstack-dev] [nova] [neutron] Specs for K release

On Thu, Aug 28, 2014 at 11:51:32AM +, Alan Kavanagh wrote: > How to do we handle specs that have slipped through the cracks > and did not make it for Juno? Rebase the proposal so it is under the 'kilo' directory path instead of 'juno' and submit it for review again. Make sure to keep the Chang

Re: [openstack-dev] [nova] Is the BP approval process broken?

On Thu, Aug 28, 2014 at 03:44:25PM -0400, Jay Pipes wrote: > On 08/27/2014 09:04 PM, Dugger, Donald D wrote: > >I’ll try and not whine about my pet project but I do think there is a > >problem here. For the Gantt project to split out the scheduler there is > >a crucial BP that needs to be implemen

Re: [openstack-dev] [nova] Is the BP approval process broken?

On Thu, Aug 28, 2014 at 04:27:59PM -0600, Chris Friesen wrote: > On 08/28/2014 04:01 PM, Joe Gordon wrote: > > > > > > > >On Thu, Aug 28, 2014 at 2:43 PM, Alan Kavanagh > >mailto:alan.kavan...@ericsson.com>> wrote: > > > >I share Donald's points here, I believe what would help is to > >clea

Re: [openstack-dev] [nova] Is the BP approval process broken?

On Fri, Aug 29, 2014 at 11:07:33AM +0200, Thierry Carrez wrote: > Joe Gordon wrote: > > On Thu, Aug 28, 2014 at 2:43 PM, Alan Kavanagh > > mailto:alan.kavan...@ericsson.com>> wrote: > > > >> I share Donald's points here, I believe what would help is to > >> clearly describe in the Wiki the

Re: [openstack-dev] [nova] feature branch for Nova v2.1 API?

On Tue, Sep 02, 2014 at 08:54:31AM -0400, Sean Dague wrote: > I think we finally got to a largely consensus agreement at the mid-cycle > on the path forward for Nova v2.1 and microversioning. Summary for > others: Nova v2.1 will be Nova v2 built on the v3 infrastructure (which > is much cleaner), w

Re: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt

On Wed, Sep 03, 2014 at 08:37:17AM -0400, Sean Dague wrote: > I'm not sure why people keep showing up with "sort requirements" patches > like - https://review.openstack.org/#/c/76817/6, however, they do. > > All of these need to be -2ed with predjudice. > > requirements.txt is not a declarative i

[openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

Position statement == Over the past year I've increasingly come to the conclusion that Nova is heading for (or probably already at) a major crisis. If steps are not taken to avert this, the project is likely to loose a non-trivial amount of talent, both regular code contributors an

Re: [openstack-dev] [Nova] Feature Freeze Exception process for Juno

On Thu, Sep 04, 2014 at 09:05:57AM +, Day, Phil wrote: > > > > -Original Message- > > From: Nikola Đipanov [mailto:ndipa...@redhat.com] > > Sent: 03 September 2014 10:50 > > To: openstack-dev@lists.openstack.org > > Subject: Re: [openstack-dev] [Nova] Feature Freeze Exception process

Re: [openstack-dev] [Nova][FFE] Feature freeze exception for virt-driver-numa-placement

On Thu, Sep 04, 2014 at 01:58:58PM +0200, Nikola Đipanov wrote: > Hi team, > > I am requesting the exception for the feature from the subject (find > specs at [1] and outstanding changes at [2]). > > Some reasons why we may want to grant it: > > First of all all patches have been approved in tim

Re: [openstack-dev] [nova] FFE request serial-ports

On Thu, Sep 04, 2014 at 02:42:11PM +0200, Sahid Orentino Ferdjaoui wrote: > Hello, > > I would like to request a FFE for 4 changesets to complete the > blueprint serial-ports. > > Topic on gerrit: > > https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/se

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

been facing. Separate repos will also facilitate more targetted application of our testing resources, so vmware repo changes wouldn't need to suffer false failures from libvirt tempest jobs, and similarly vmware CI could be made gating for vmware without causing libvirt code to suffer insta

Re: [openstack-dev] [Nova][FFE] Feature freeze exception for virt-driver-numa-placement

On Thu, Sep 04, 2014 at 03:07:24PM +0200, Nikola Đipanov wrote: > On 09/04/2014 02:31 PM, Sean Dague wrote: > > On 09/04/2014 07:58 AM, Nikola Đipanov wrote: > >> Hi team, > >> > >> I am requesting the exception for the feature from the subject (find > >> specs at [1] and outstanding changes at [2]

Re: [openstack-dev] [nova] [feature freeze exception] FFE for libvirt-start-lxc-from-block-devices

On Thu, Sep 04, 2014 at 03:22:14PM +0200, Vladik Romanovsky wrote: > Hello, > > I would like to ask for an extension for libvirt-start-lxc-from-block-devices > feature. It has been previously pushed from Ice house to Juno. > The spec [1] has been approved. One of the patches is a bug fix. Another

Re: [openstack-dev] [vmware][nova][FFE] vmware-spawn-refactor

On Thu, Sep 04, 2014 at 02:09:26PM +0100, Matthew Booth wrote: > I'd like to request a FFE for the remaining changes from > vmware-spawn-refactor. They are: > > https://review.openstack.org/#/c/109754/ > https://review.openstack.org/#/c/109755/ > https://review.openstack.org/#/c/114817/ > https://

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Thu, Sep 04, 2014 at 02:33:27PM +, Dugger, Donald D wrote: > Basically +1 with what Daniel is saying (note that, as mentioned, > a side effect of our effort to split out the scheduler will help > but not solve this problem). Thanks for taking the time to read & give feedback > My only ques

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Thu, Sep 04, 2014 at 10:18:04AM -0500, Matt Riedemann wrote: > > >> > >> - Changes submitted to nova common code would trigger running of CI > >>tests against the external virt drivers. Each virt driver core team > >>would decide whether they want their driver to be tested upon Nova >

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

er it to smaller dedicated > >review teams. This is one way to do it. Thanks Dan for pulling this > >together :) > > > >A couple comments inline: > > > >Daniel P. Berrange wrote: > >> [...] > >> This is a crisis. A large crisis. In fact, if you got a m

Re: [openstack-dev] [Nova][FFE] requesting FFE for LVM ephemeral storage encryption

On Thu, Sep 04, 2014 at 11:41:48AM -0400, Dan Genin wrote: > I would like to request a feature freeze exception for > > LVM ephemeral storage encryption[1]. > > The spec[2] for which was approved early in the Juno release cycle. > > This feature provides security for data at-rest on comput

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Thu, Sep 04, 2014 at 03:49:26PM +, Dugger, Donald D wrote: > Actually, I think Sylvain's point is even stronger as I don't think > splitting the virt drivers out of Nova is a complete fix. It may > solve the review latency for the virt driver area but, unless virt > drivers are the bulk of

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Thu, Sep 04, 2014 at 05:11:22PM +0100, Duncan Thomas wrote: > On 4 September 2014 16:00, Solly Ross wrote: > >> My only question is about the need to separate out each virt driver into a > >> separate project, wouldn't you > >> accomplish a lot of the benefit by creating a single virt project

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Thu, Sep 04, 2014 at 02:56:04PM -0500, Kyle Mestery wrote: > On Thu, Sep 4, 2014 at 5:24 AM, Daniel P. Berrange > wrote: > > Proposal / solution > > === > > > > In the past Nova has spun out its volume layer to form the cinder > > projec

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Thu, Sep 04, 2014 at 10:44:17PM -0600, John Griffith wrote: > Just some thoughts and observations I've had regarding this topic in Cinder > the past couple of years. I realize this is a Nova thread so hopefully > some of this can be applied in a more general context. > > TLDR: > 1. I think mov

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Thu, Sep 04, 2014 at 12:57:57PM -0700, Joe Gordon wrote: > On Thu, Sep 4, 2014 at 3:24 AM, Daniel P. Berrange > wrote: > > Proposal / solution > > === > > > > In the past Nova has spun out its volume layer to form the cinder > > projec

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Thu, Sep 04, 2014 at 06:48:33PM -0400, Russell Bryant wrote: > On 09/04/2014 06:24 AM, Daniel P. Berrange wrote: > > Position statement > > == > > > > Over the past year I've increasingly come to the conclusion that > > Nova is headin

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

> cinder, as I know they're having similar conversations. > > I don't have a strong opinion on the solution you and Kyle seem to be > leaning toward, I just have a couple of comments/warnings below > > On 09/04/2014 03:24 AM, Daniel P. Berrange wrote: > > saying &

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Fri, Sep 05, 2014 at 07:31:50PM +0930, Christopher Yeoh wrote: > On Thu, 4 Sep 2014 11:24:29 +0100 > "Daniel P. Berrange" wrote: > > > > - A fairly significant amount of nova code would need to be > >considered semi-stable API. Certainly everything und

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Thu, Sep 04, 2014 at 06:22:18PM -0500, Michael Still wrote: > On Thu, Sep 4, 2014 at 5:24 AM, Daniel P. Berrange > wrote: > > [Heavy snipping because of length] > > > The radical (?) solution to the nova core team bottleneck is thus to > > follow this lead and

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Fri, Sep 05, 2014 at 11:29:43AM +0100, John Garbutt wrote: > On 4 September 2014 23:48, Russell Bryant wrote: > > On 09/04/2014 06:24 AM, Daniel P. Berrange wrote: > > If we ignored gerrit for a moment, is rapid increase in splitting out > > components the ideal workflow

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Fri, Sep 05, 2014 at 12:40:59PM +0200, Nikola Đipanov wrote: > On 09/04/2014 12:24 PM, Daniel P. Berrange wrote: > > - A fairly significant amount of nova code would need to be > >considered semi-stable API. Certainly everything under nova/virt > >and any object w

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Fri, Sep 05, 2014 at 07:00:44AM -0400, Sean Dague wrote: > On 09/05/2014 06:22 AM, Daniel P. Berrange wrote: > > On Fri, Sep 05, 2014 at 07:31:50PM +0930, Christopher Yeoh wrote: > >> On Thu, 4 Sep 2014 11:24:29 +0100 > >> "Daniel P. Berrange" wrote: >

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Fri, Sep 05, 2014 at 07:12:37AM -0400, Sean Dague wrote: > On 09/05/2014 06:40 AM, Nikola Đipanov wrote: > > A handy example of this I can think of is the currently granted FFE for > > serial consoles - consider how much of the code went into the common > > part vs. the libvirt specific part, I

Re: [openstack-dev] [nova] [feature freeze exception] FFE for libvirt-disk-discard-option

On Fri, Sep 05, 2014 at 06:28:55AM +, Bohai (ricky) wrote: > Hi, > > I'd like to ask for a feature freeze exception for blueprint > libvirt-disk-discard-option. > https://review.openstack.org/#/c/112977/ > > approved spec: > https://review.openstack.org/#/c/85556/ > > blueprint was approved

Re: [openstack-dev] [FFE] [nova] Barbican key manager wrapper

On Thu, Sep 04, 2014 at 05:19:45PM +, Coffman, Joel M. wrote: > A major concern about several encryption features within Nova [1, 2] has been > the lack of secure key management. To address this concern, work has been > underway to integrate these features with Barbican [3], which can be used

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Fri, Sep 05, 2014 at 07:49:04AM -0400, Sean Dague wrote: > On 09/05/2014 07:26 AM, Daniel P. Berrange wrote: > > On Fri, Sep 05, 2014 at 07:00:44AM -0400, Sean Dague wrote: > >> On 09/05/2014 06:22 AM, Daniel P. Berrange wrote: > >>> On Fri, Sep 05, 2014 at 07:3

Re: [openstack-dev] [nova][FFE] websocket-proxy-to-host-security

On Thu, Sep 04, 2014 at 12:59:07PM -0400, Solly Ross wrote: > I would like to request a feature freeze exception for the Websocket Proxy to > Host Security. > The spec [1] was approved for Nova, and the patches [2] are currently sitting > there with one > +2 (courtesy of @danpb), with a +1 from J

Re: [openstack-dev] [Nova] [FFE] Final Libvirt User Namespaces Patch

On Fri, Sep 05, 2014 at 01:49:20PM +, Andrew Melton wrote: > Hey Devs, > > I'd like to request a feature freeze exception for: > https://review.openstack.org/#/c/94915/ > > This feature is the final patch set for the User Namespace BP > (https://blueprints.launchpad.net/nova/+spec/libvirt-lx

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Fri, Sep 05, 2014 at 10:25:09AM -0500, Kevin L. Mitchell wrote: > On Fri, 2014-09-05 at 10:26 +0100, Daniel P. Berrange wrote: > > > 2. Removal of drivers other than the reference implementation for each > > > project could be the healthiest option > > > a

Re: [openstack-dev] [Nova][FFE] Feature freeze exception for virt-driver-numa-placement

On Fri, Sep 05, 2014 at 04:20:14PM +0100, John Garbutt wrote: > On 5 September 2014 13:59, Nikola Đipanov wrote: > > Since this did not get an 'Approved' as of yet, I want to make sure that > > this is not because the number of sponsors. 2 core members have already > > sponsored it, and as per [1]

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

On Mon, Sep 08, 2014 at 05:20:54PM -0700, Stefano Maffulli wrote: > On 09/05/2014 07:07 PM, James Bottomley wrote: > > Actually, I don't think this analysis is accurate. Some people are > > simply interested in small aspects of a project. It's the "scratch your > > own itch" part of open source.

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

On Tue, Sep 09, 2014 at 05:14:43PM -0700, Stefano Maffulli wrote: > > To me, this means you don't really want a sin bin where you dump > > drivers and tell them not to come out until they're fit to be > > reviewed by the core; You want a trusted driver community which does > > its own reviews and m

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

On Thu, Sep 11, 2014 at 09:23:34AM +1000, Michael Still wrote: > On Thu, Sep 11, 2014 at 8:11 AM, Jay Pipes wrote: > > > a) Sorting out the common code is already accounted for in Dan B's original > > proposal -- it's a prerequisite for the split. > > Its a big prerequisite though. I think we're

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

On Wed, Sep 10, 2014 at 07:35:05PM -0700, Armando M. wrote: > Hi, > > I devoured this thread, so much it was interesting and full of > insights. It's not news that we've been pondering about this in the > Neutron project for the past and existing cycle or so. > > Likely, this effort is going to t

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Wed, Sep 10, 2014 at 12:41:44PM -0700, Vishvananda Ishaya wrote: > > On Sep 5, 2014, at 4:12 AM, Sean Dague wrote: > > > On 09/05/2014 06:40 AM, Nikola Đipanov wrote: > >> > >> > >> Just some things to think about with regards to the whole idea, by no > >> means exhaustive. > > > > So mayb

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Thu, Sep 04, 2014 at 05:27:06PM +, Alessandro Pilotti wrote: > This means that if we reach a point in which we agree to spin off the drivers > in > separate core projects, we need to consider how driver related CIs will be > still > included in the Nova review process, possibly with voting

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Thu, Sep 11, 2014 at 02:02:00PM -0400, Dan Prince wrote: > I've always referred to the virt/driver.py API as an internal API > meaning there are no guarantees about it being preserved across > releases. I'm not saying this is correct... just that it is what we've > got. While OpenStack attempts

  1   2   3   4   5   6   7   8   9   >