[openstack-dev] [Nova] SR-IOV IRC meeting and sub-team - passing the torch

Hi team, As I'll be focusing on different things going forward, I was wondering if someone from the group of people who were normally working in this area would want to step up and take over the sub-team IRC meeting. It is normally not a massive overhead, mostly tracking ongoing efforts and patch

Re: [openstack-dev] [nova] bug 1550250: delete_on_termination" flag: how to proceed?

On 03/29/2016 09:14 AM, Markus Zoeller wrote: > The discussion around Bug 1550250 [1] doesn't show a clear path on how > to proceed. In short, it's about if we want to keep the flag > "delete_on_termination" for volumes which get migrated. Right now that > flag gets reset during the migration proce

Re: [openstack-dev] [nova] NUMA + SR-IOV

On 03/24/2016 04:18 PM, Sergey Nikitin wrote: > > Hi, folks. > > I want to start a discussion about NUMA + SR-IOV environment. I have a > two-sockets server. It has two NUMA nodes and only one SR-IOV PCI > device. This device is associated with the first NUMA node. I booted a > set of VMs with SR

Re: [openstack-dev] [Nova] Grant FFE to "Host-state level locking" BP

On 03/04/2016 02:06 PM, John Garbutt wrote: > tl;dr > As on IRC, I don't think this should get an FFE this cycle. > > On 4 March 2016 at 10:56, Nikola Đipanov wrote: >> Hi, >> >> The actual BP that links to the approved spec is here: [1] and 2 >> outstan

[openstack-dev] [Nova] Grant FFE to "Host-state level locking" BP

Hi, The actual BP that links to the approved spec is here: [1] and 2 outstanding patches are [2][3]. Apart from the usual empathy-inspired reasons to allow this (code's been up for a while, yet only had real review on the last day etc.) which are not related to the technical merit of the work, th

Re: [openstack-dev] [Nova] Re-booting the SR-IOV meeting

is why I think it would be good to meet and figure this out together. N. > Cheers, > Shinobu > > > On Fri, Feb 26, 2016 at 11:58 PM, Nikola Đipanov wrote: >> Hello folks, >> >> We are closing in on Mitaka-3 and it would be good to have a meeting and >> see w

[openstack-dev] [Nova] Re-booting the SR-IOV meeting

Hello folks, We are closing in on Mitaka-3 and it would be good to have a meeting and see which SR-IOV related bugfixes we want to try to land for Mitaka. The next meeting slot is next week on Tuesday (March 1st) at 13:00 UTC, so if there are any bugs you would like to discuss - that would be a g

Re: [openstack-dev] [nova] A prototype implementation towards the "shared state scheduler"

On 02/15/2016 09:27 AM, Sylvain Bauza wrote: > > > Le 15/02/2016 06:21, Cheng, Yingxin a écrit : >> >> Hi, >> >> >> >> I’ve uploaded a prototype https://review.openstack.org/#/c/280047/ >> to testify its design goals >> in accuracy, performance, reliab

Re: [openstack-dev] [nova] Better tests for nova scheduler(esp. race conditions)?

proper reasource accounting tests. Yingxin - in case you are still interested in doing some of this stuff, we can discuss here or on IRC. Thanks, Nikola On 12/15/2015 03:33 AM, Cheng, Yingxin wrote: > >> -Original Message- >> From: Nikola Đipanov [mailto:ndipa...@redh

Re: [openstack-dev] [Nova] PCI CI is down

; > -Original Message- > From: Nikola Đipanov [mailto:ndipa...@redhat.com] > Sent: Wednesday, January 20, 2016 4:41 PM > To: OpenStack Development Mailing List > Subject: [openstack-dev] [Nova] PCI CI is down > > Hey Nova, > > It seems the a bug [1] sneaked

[openstack-dev] [Nova] PCI CI is down

Hey Nova, It seems the a bug [1] sneaked in that made the PCI CI jobs fail 100% of the time so they got turned off. Fix for the bug should be making it's way through the queue soon, but it was hinted on the review that there may be further problems. I'd like to help fix these issues ASAP as the r

Re: [openstack-dev] [nova] Better tests for nova scheduler(esp. race conditions)?

On 12/15/2015 03:33 AM, Cheng, Yingxin wrote: > >> -Original Message- >> From: Nikola Đipanov [mailto:ndipa...@redhat.com] >> Sent: Monday, December 14, 2015 11:11 PM >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: Re: [o

Re: [openstack-dev] [nova] Better tests for nova scheduler(esp. race conditions)?

On 12/14/2015 08:20 AM, Cheng, Yingxin wrote: > Hi All, > > > > When I was looking at bugs related to race conditions of scheduler > [1-3], it feels like nova scheduler lacks sanity checks of schedule > decisions according to different situations. We cannot even make sure > that some fixes succ

Re: [openstack-dev] [oslo][messaging] configurable ack-then-process (at least/most once) behavior

On 11/30/2015 01:28 PM, Bogdan Dobrelya wrote: > Hello. > Please let's make this change [0] happen to the Oslo messaging. > This is reasonable, straightforward and backwards compatible change. And > it is required for OpenStack applications - see [1] - to implement a > sane HA. The only thing left

Re: [openstack-dev] [Nova] [Neutron] SR-IOV subteam

review and comment. [1] http://eavesdrop.openstack.org/meetings/sriov/2015/sriov.2015-11-10-13.09.log.html On 11/10/2015 01:42 AM, Nikola Đipanov wrote: > On 11/04/2015 07:56 AM, Moshe Levi wrote: >> Maybe we can you use the pci- passthrough meeting slot >> http://eavesdro

Re: [openstack-dev] [Nova] SR-IOV subteam

On 11/04/2015 07:56 AM, Moshe Levi wrote: > Maybe we can you use the pci- passthrough meeting slot > http://eavesdrop.openstack.org/#PCI_Passthrough_Meeting > It been a long time since we had a meeting. > I think that slot works well (at least for me). I'd maybe change the cadence to bi-weekly

Re: [openstack-dev] [nova] Proposal to add Alex Xu to nova-core

On 11/06/2015 03:32 PM, John Garbutt wrote: > Hi, > > I propose we add Alex Xu[1] to nova-core. > +1 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?su

Re: [openstack-dev] [nova] Proposal to add Sylvain Bauza to nova-core

On 11/06/2015 03:32 PM, John Garbutt wrote: > Hi, > > I propose we add Sylvain Bauza[1] to nova-core. > +1 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.

[openstack-dev] [Nova] SR-IOV subteam

Hello Nova, Looking at Mitaka specs, but also during the Tokyo design summit sessions, we've seen several discussions and requests for enhancements to the Nova SR-IOV functionality. It has been brought up during the Summit that we may want to organize as a subteam to track all of the efforts bett

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/21/2015 10:17 PM, Joshua Harlow wrote: > Question on some things seen in the below paste. > > What is with 'finished' -> 'reverted' and 'finished' -> 'confirmed'? > > Why does it jump over 'reverting' or 'confirming'? Should it? > > The other question is the difference between 'failed' and

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/19/2015 11:13 AM, Tang Chen wrote: > Hi, all, > > If you don't mind, how about approve the BP, and I can start this work. > This is IMHO the biggest drawback of the current spec process (as I've written before). There is no reason why you should doubt that this particular spec will get ap

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/14/2015 04:29 AM, Tang Chen wrote: >> >> On Wed, Oct 14, 2015 at 10:05 AM, Tang Chen > > wrote: >> >> Hi, all, >> >> Please help to review this BP. >> >> https://blueprints.launchpad.net/nova/+spec/live-migration-state-machine >> >> >> Currently

Re: [openstack-dev] [nova][mistral] Automatic evacuation as a long running task

On 10/06/2015 04:34 PM, Matthew Booth wrote: > Hi, Roman, > > Evacuated has been on my radar for a while and this post has prodded me > to take a look at the code. I think it's worth starting by explaining > the problems in the current solution. Nova client is currently > responsible for doing thi

Re: [openstack-dev] [nova] how to address boot from volume failures

On 09/30/2015 10:45 PM, Andrew Laski wrote: > On 09/30/15 at 05:03pm, Sean Dague wrote: >> Today we attempted to branch devstack and grenade for liberty, and are >> currently blocked because in liberty with openstack client and >> novaclient, it's not possible to boot a server from volume using jus

Re: [openstack-dev] Scheduler hints, API and Objects

On 09/04/2015 02:31 PM, Sylvain Bauza wrote: > > > Le 04/09/2015 14:57, Nikola Đipanov a écrit : >> On 06/25/2015 04:50 PM, Monty Taylor wrote: >>> On 06/25/2015 10:22 AM, Andrew Laski wrote: >>>> I have been growing concerned recently with some attempts to

Re: [openstack-dev] Scheduler hints, API and Objects

On 06/25/2015 04:50 PM, Monty Taylor wrote: > On 06/25/2015 10:22 AM, Andrew Laski wrote: >> I have been growing concerned recently with some attempts to formalize >> scheduler hints, both with API validation and Nova objects defining >> them, and want to air those concerns and see if others agree

Re: [openstack-dev] [cinder][nova] snapshot and cloning for NFS backend

On 07/28/2015 09:00 AM, Kekane, Abhishek wrote: > Hi Devs, > > > > There is an NFS backend driver for cinder, which supports only limited > volume handling features. Specifically, "snapshot" and "cloning" > features are missing. > > > > Eric Harney has proposed a feature of "NFS driver snap

Re: [openstack-dev] [nova] should we allow overcommit for a single VM?

On 08/17/2015 08:22 PM, Chris Friesen wrote: > > I tried bringing this up on the irc channel, but nobody took the bait. > Hopefully this will generate some discussion. > > I just filed bug 1485631. Nikola suggested one way of handling it, but > there are some complications that I thought I shoul

Re: [openstack-dev] [Nova] Device names supplied to the boot request

On 07/16/2015 06:35 PM, Matt Riedemann wrote: > > > On 7/16/2015 11:47 AM, Nikola Đipanov wrote: >> On 07/16/2015 11:24 AM, Sean Dague wrote: >>> On 07/15/2015 01:41 PM, Andrew Laski wrote: >>>> On 07/15/15 at 12:19pm, Matt Riedemann wrote: >>> >

Re: [openstack-dev] [Nova] Device names supplied to the boot request

On 07/16/2015 05:47 PM, Nikola Đipanov wrote: > > Also, not being able to specify device names would make it impossible to > implement certain features that EC2 API can provide, such as overriding > the image block devices without significant effort. > I forgot to add links that

Re: [openstack-dev] [Nova] Device names supplied to the boot request

On 07/16/2015 11:24 AM, Sean Dague wrote: > On 07/15/2015 01:41 PM, Andrew Laski wrote: >> On 07/15/15 at 12:19pm, Matt Riedemann wrote: > >>> The other part of the discussion is around the API changes, not just >>> for libvirt, but having a microversion that removes the device from >>> the reques

[openstack-dev] [Nova] Device names supplied to the boot request

I'll keep this email brief since this has been a well known issue for some time now. Problem: Libvirt can't honour device names specified at boot for any volumes requested as part of block_device_mapping. What we currently do is in case they do get specified, we persist them as is, so that we can

Re: [openstack-dev] [nova] schedule instance based on CPU frequency ?

On 06/30/2015 07:42 AM, 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 easily. > > The us

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 06/29/2015 11:32 AM, Thierry Carrez wrote: > Nikola Đipanov wrote: >> It's not only about education - I think Gerrit is the wrong medium to >> have a design discussion and do design work. Maybe you disagree as you >> seem to imply that it worked well in some cases? &

Re: [openstack-dev] [Nova] The unbearable lightness of specs

, Daniel P. Berrange wrote: > 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 happen

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 06/26/2015 08:15 PM, Tim Bell wrote: > > Limiting those who give input to the people who can analyse python and > determine the impacts of the change has significant risks. Many of those > running OpenStack clouds can give their feedback as part of the specs > process. While this may not be

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 06/25/2015 05:39 PM, Tim Bell wrote: > > > On 25/06/15 09:49, "Thierry Carrez" wrote: > >> Maxim Nestratov wrote: >>> 24.06.2015 20:21, Daniel P. Berrange пишет: On Wed, Jun 24, 2015 at 04:46:57PM +, Michael Krotscheck wrote: > First: Overhead > - 1 week for vacation > -

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 06/25/2015 09:46 PM, Joe Gordon wrote: > On Thu, Jun 25, 2015 at 1:39 AM, Nikola Đipanov > > > > As someone who does a lot of spec reviews, I take +1s from the right > > people (not always nova-cores) to mean a lot, so much that I regularly > > will

Re: [openstack-dev] [Nova][Keystone] The unbearable lightness of specs

On 06/24/2015 09:00 PM, Adam Young wrote: > On 06/24/2015 12:25 PM, Daniel P. Berrange wrote: >> Which happened repeatedly. You could say that >> the first patch submitted to the code repository should simply be a doc >> file addition, that describes the feature proposal and we should discuss >> th

Re: [openstack-dev] [Nova] The unbearable lightness of specs

9 AM, Kashyap Chamarthy wrote: > > >On Wed, Jun 24, 2015 at 02:51:38PM +0100, Nikola Đipanov wrote: > > >>On 06/24/2015 02:33 PM, Matt Riedemann wrote: > > [. . .] > > > >This is one of the _baffling_ aspects -- that a so-called "su

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 06/24/2015 04:42 PM, Andrew Laski wrote: > On 06/24/15 at 02:38pm, Nikola Đipanov wrote: >> On 06/24/2015 01:42 PM, Daniel P. Berrange wrote: >>> On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote: >>>> Hey Nova, >>>> >>>> I

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 06/24/2015 03:08 PM, Dan Smith wrote: >> Why do cores need approved specs for example - and indeed for many of us >> - it's just a dance we do. I refuse to believe that a core can be >> trusted to approve patches but not to write any code other than a bugfix >> without a written document explain

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 06/24/2015 02:33 PM, Matt Riedemann wrote: > > > On 6/24/2015 8:23 AM, Sahid Orentino Ferdjaoui wrote: >> 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 fo

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 06/24/2015 01:42 PM, Daniel P. Berrange wrote: > 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

[openstack-dev] [Nova] The unbearable lightness of specs

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 minority (!) of cores being able to approve them, yet they are a prereq of

Re: [openstack-dev] [nova] Availability of device names for operations with volumes and BDM and other features.

s:open+project:openstack/nova+branch:master+topic:bug/1370250,n,z [2] https://bugs.launchpad.net/nova/+bug/1370250 > > On 5/29/15 11:32 PM, Nikola Đipanov wrote: >> On 05/29/2015 12:55 AM, Feodor Tersin wrote: >>> Nicola, i would add some words to Alexandre repsonse. >>>

Re: [openstack-dev] [rally][scaling up development] Rally core team re-organization

On 06/05/2015 06:31 PM, Doug Hellmann wrote: > Excerpts from Boris Pavlovic's message of 2015-06-05 20:03:44 +0300: >> Hi stackers, >> >> Seems likes after stackforge/rally -> openstack/rally Rally project started >> being more attractive. >> According recent stats we are on top 3 position (based o

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

On 06/03/2015 05:57 PM, John Garbutt wrote: > +1 to ttx and Jame's points on trust and relationships, indeed > referencing the summit session that ttx mentioned: > https://etherpad.openstack.org/p/liberty-cross-project-in-team-scaling > > On 3 June 2015 at 16:01, Nikola Đipa

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

On 06/03/2015 02:43 PM, Boris Pavlovic wrote: > > I don't believe even my self, because I am human and I make mistakes. > My goal on the PTL position is to make such process that stops "human" > mistakes before they land in master. In other words everything should be > automated and pre not post

Re: [openstack-dev] [nova][scheduler] Updating Our Concept of Resources

On 06/03/2015 02:13 PM, John Garbutt wrote: > On 3 June 2015 at 13:53, Ed Leafe wrote: >> On Jun 2, 2015, at 5:58 AM, Alexis Lee wrote: >> >>> If you allocate all the memory of a box to high-mem instances, you may >>> not be billing for all the CPU and disk which are now unusable. That's >>> why

Re: [openstack-dev] [nova] RequestSpec object and Instance model

On 06/02/2015 03:14 PM, Sylvain Bauza wrote: > Hi, > > Currently working on implementing the RequestSpec object BP [1], I had > some cool comments on my change here : > https://review.openstack.org/#/c/145528/12/nova/objects/request_spec.py,cm > > Since we didn't discussed on how to persist that

Re: [openstack-dev] [nova] Availability of device names for operations with volumes and BDM and other features.

On 05/29/2015 12:55 AM, Feodor Tersin wrote: > Nicola, i would add some words to Alexandre repsonse. > > We (standalone ec2api project guys) have filed some bugs (the main is > [1]), but we don't know how to fix them since the way Nova's device > names are moved on is unclear for us. Neither BP, n

Re: [openstack-dev] [nova] Availability of device names for operations with volumes and BDM and other features.

On 05/27/2015 09:47 AM, Alexandre Levine wrote: > Hi all, > > I'd like to bring up this matter again, although it was at some extent > discussed during the recent summit. > > The problem arises from the fact that the functionality exposing device > names for usage through public APIs is deteriora

Re: [openstack-dev] [nova] usefulness of device parameter at volumeAttachment

On 05/26/2015 11:13 AM, Daniel P. Berrange wrote: > On Sat, May 23, 2015 at 11:00:32AM +0200, Géza Gémes wrote: >> Hi, >> >> When someone calls nova volume-attach or the block-device-mapping parameter >> at boot, it is possible to specify a device name for the guest. However I >> couldn't find any

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

On 04/30/2015 12:30 PM, John Garbutt wrote: > Hi, > > I propose we add Melanie to nova-core. > > She has been consistently doing great quality code reviews[1], > alongside a wide array of other really valuable contributions to the > Nova project. > > Please respond with comments, +1s, or objecti

Re: [openstack-dev] [Nova][QA] Use case of Nova to boot VM from volume only

On 04/03/2015 07:33 AM, GHANSHYAM MANN wrote: > Hi, > > This is regarding bug - https://bugs.launchpad.net/tempest/+bug/1436314 > > When Nova is configured to boot VM from volume only, current Tempest > integration tests will fails. We are not sure how feasible and valid > this configuration is f

Re: [openstack-dev] [nova] Revert "objects: introduce numa topology limits objects"

On 03/23/2015 02:06 PM, Dan Smith wrote: >> I am really sorry it got in as I have -1ed it several times for the same >> reason (I _really_ hate using the -2 hammer - we're all adults here >> after all). > > I guess that I should take some blame as a reviewer on that patch, but > only after this ma

[openstack-dev] [nova] Revert "objects: introduce numa topology limits objects"

I'd really like the following commit reverted: https://review.openstack.org/#/c/137817/ I am really sorry it got in as I have -1ed it several times for the same reason (I _really_ hate using the -2 hammer - we're all adults here after all). My reasoning for it is quite simple and is outlined i

Re: [openstack-dev] [nova] Block Device Mapping is Invalid error

On 03/16/2015 03:55 PM, aburluka wrote: > Hello Nova! > > I'd like to ask community to help me with some unclear things. I'm > currently working on adding persistent storage support into a parallels > driver. > > I'm trying to start VM. > > nova boot test-vm --flavor m1.medium --image centos-vm-

Re: [openstack-dev] [nova] blueprint about multiple workers supported in nova-scheduler

On 03/06/2015 03:19 PM, Attila Fazekas wrote: > Looks like we need some kind of _per compute node_ mutex in the critical > section, > multiple scheduler MAY be able to schedule to two compute node at same time, > but not for scheduling to the same compute node. > > If we don't want to introduce a

Re: [openstack-dev] [nova] blueprint about multiple workers supported in nova-scheduler

ad.net/nova/+spec/no-db-scheduler [2] https://bugs.launchpad.net/nova/+bug/1341420 > Best Regards. > > 2015-03-05 21:12 GMT+08:00 Sylvain Bauza <mailto:sba...@redhat.com>>: > > > Le 05/03/2015 13:00, Nikola Đipanov a écrit : > > On 03/04/2015 09:23

Re: [openstack-dev] [nova] blueprint about multiple workers supported in nova-scheduler

On 03/04/2015 09:23 AM, Sylvain Bauza wrote: > > Le 04/03/2015 04:51, Rui Chen a écrit : >> Hi all, >> >> I want to make it easy to launch a bunch of scheduler processes on a >> host, multiple scheduler workers will make use of multiple processors >> of host and enhance the performance of nova-sch

Re: [openstack-dev] [nova] Plans to fix numa_topology related issues with migration/resize/evacuate

On 03/04/2015 03:17 PM, Wensley, Barton wrote: > Hi, > > I have been exercising the numa topology related features in kilo (cpu > pinning, numa topology, huge pages) and have seen that there are issues > when an operation moves an instance between compute nodes. In summary, > the numa_topology is

Re: [openstack-dev] [nova] Outcome of the nova FFE meeting for Kilo

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 vhostuser / open contrail > vif drivers for which FFE has been granted.

Re: [openstack-dev] [nova] Ubuntu, qemu, NUMA support

On 02/23/2015 06:17 AM, Tom Fifield wrote: >> Also, we currently assume that qemu can pin to NUMA nodes. This is an >> invalid assumption since this was only added as of qemu 2.1, and there >> only if it's compiled with NUMA support. At the very least we should >> have a version check, but if Ubu

Re: [openstack-dev] [nova] Question about force_host skip filters

On 02/17/2015 04:59 PM, Chris Friesen wrote: > On 02/16/2015 01:17 AM, Nikola Đipanov wrote: >> On 02/14/2015 08:25 AM, Alex Xu wrote: > >>> Agree with Nikola, the claim already checking that. And instance booting >>> must be failed if there isn't pci dev

Re: [openstack-dev] [nova] Feature Freeze Exception Request (DRBD for Nova) WAS: Re: [nova] Request Spec Freeze Exception (DRBD for Nova)

On 02/16/2015 03:27 PM, Nikola Đipanov wrote: > Re-titling the email so that it does not get missed as it does not have > the right subject line. > Ugh - as Daniel pointed out - the spec is not actually approved so please disregard this email - I missed that bit. Although - I still sta

[openstack-dev] [nova] Feature Freeze Exception Request (DRBD for Nova) WAS: Re: [nova] Request Spec Freeze Exception (DRBD for Nova)

Re-titling the email so that it does not get missed as it does not have the right subject line. I looked at the code and it is quite straightforward - some small nits inline but other than that - no reason to keep it out. This is the first contribution to Nova by Philipp and his team, and their e

Re: [openstack-dev] [nova] Question about force_host skip filters

On 02/14/2015 08:25 AM, Alex Xu wrote: > > > 2015-02-14 1:41 GMT+08:00 Nikola Đipanov <mailto:ndipa...@redhat.com>>: > > On 02/12/2015 04:10 PM, Chris Friesen wrote: > > On 02/12/2015 03:44 AM, Sylvain Bauza wrote: > > > >> A

Re: [openstack-dev] [nova] Question about force_host skip filters

On 02/12/2015 04:10 PM, Chris Friesen wrote: > On 02/12/2015 03:44 AM, Sylvain Bauza wrote: > >> Any action done by the operator is always more important than what the >> Scheduler >> could decide. So, in an emergency situation, the operator wants to >> force a >> migration to an host, we need to

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 02/11/2015 06:20 PM, Clint Byrum wrote: > Excerpts from Nikola Đipanov's message of 2015-02-11 05:26:47 -0800: >> On 02/11/2015 02:13 PM, Sean Dague wrote: >>> >>> If core team members start dropping off external IRC where they are >>> communicating across corporate boundaries, then the local tr

Re: [openstack-dev] [nova] Feature Freeze Exception Request (libvirt vhostuser vif driver)

On 02/09/2015 11:04 AM, 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/li

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 02/11/2015 02:13 PM, Sean Dague wrote: > > If core team members start dropping off external IRC where they are > communicating across corporate boundaries, then the local tribal effects > start taking over. You get people start talking about the upstream as > "them". The moment we get into us v

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

+ Inf for writing this Flavio! Only some observations below. On 02/11/2015 10:55 AM, Flavio Percoco wrote: > Greetings all, > > During the last two cycles, I've had the feeling that some of the > things I love the most about this community are degrading and moving > to a state that I personally

Re: [openstack-dev] [nova] Feature Freeze Exception Request for Quiesce boot from volume instances

On 02/10/2015 11:12 AM, Daniel P. Berrange wrote: > On Fri, Feb 06, 2015 at 10:20:04PM +, Tomoki Sekiyama wrote: >> Hello, >> >> I'd like to request a feature freeze exception for the change >> https://review.openstack.org/#/c/138795/ . >> >> This patch makes live volume-boot instance snapsho

Re: [openstack-dev] Need nova-specs core reviews for Scheduler spec

On 02/06/2015 02:15 PM, Ed Leafe wrote: > At the mid-cycle we discussed the last spec for the scheduler cleanup: > Isolate Scheduler DB for Instances > > https://review.openstack.org/#/c/138444/ > > There was a lot of great feedback from those discussions, and that has been > incorporated into

Re: [openstack-dev] [nova] Nominating Melanie Witt for python-novaclient-core

On 01/27/2015 11:41 PM, Michael Still wrote: > Greetings, > > I would like to nominate Melanie Witt for the python-novaclient-core team. > > (What is python-novaclient-core? Its a new group which will contain > all of nova-core as well as anyone else we think should have core > reviewer powers on

Re: [openstack-dev] [nova][gate][stable] How eventlet 0.16.1 broke the gate

On 01/15/2015 10:35 AM, Joe Gordon wrote: > So how could we have avoided this problem? By capping stable branch > requirements so we only have to worry about uncapped dependencies on > master. Capping stable branches has been previous discussed but no > action has been taken. So going forward I pr

Re: [openstack-dev] [Nova] Spring cleaning nova-core

On 12/07/2014 08:52 PM, Michael Still wrote: > > You know what makes me really sad? No one has suggested that perhaps > Padraig could just pick up his review rate a little. I've repeatedly > said we can re-add reviewers if that happens. > This is of course not true - everybody *but* the people o

Re: [openstack-dev] [Nova] Spring cleaning nova-core

On 12/07/2014 06:02 PM, Jay Pipes wrote: > On 12/07/2014 04:19 AM, Michael Still wrote: >> On Sun, Dec 7, 2014 at 7:03 PM, Gary Kotton wrote: >>> On 12/6/14, 7:42 PM, "Jay Pipes" wrote: >> >> [snip] >> -1 on pixelbeat, since he's been active in reviews on various things AFAICT in the la

Re: [openstack-dev] [Nova] Spring cleaning nova-core

On 12/05/2014 01:05 AM, Michael Still wrote: > One of the things that happens over time is that some of our core > reviewers move on to other projects. This is a normal and healthy > thing, especially as nova continues to spin out projects into other > parts of OpenStack. > > However, it is import

Re: [openstack-dev] [nova] NUMA Cells

On 12/04/2014 05:30 AM, Michael Still wrote: > Hi, > > so just having read a bunch of the libvirt driver numa code, I have a > concern. At first I thought it was a little thing, but I am starting > to think its more of a big deal... > > We use the term "cells" to describe numa cells. However, tha

Re: [openstack-dev] [nova] Consistency, efficiency, and safety of NovaObject.save()

On 11/13/2014 02:45 AM, Dan Smith wrote: >> I’m not sure if I’m seeing the second SELECT here either but I’m less >> familiar with what I’m looking at. compute_node_update() does the >> one SELECT as we said, then it doesn’t look like >> self._from_db_object() would emit any further SQL specifi

Re: [openstack-dev] Taking a break..

On 10/22/2014 07:37 PM, Chris Behrens wrote: > Hey all, > > Just wanted to drop a quick note to say that I decided to leave Rackspace to > pursue another opportunity. My last day was last Friday. I won’t have much > time for OpenStack, but I’m going to continue to hang out in the channels. > Ha

Re: [openstack-dev] [nova] Pulling nova/virt/hardware.py into nova/objects/

On 10/20/2014 07:38 PM, Jay Pipes wrote: > Hi Dan, Dan, Nikola, all Nova devs, > > OK, so in reviewing Dan B's patch series that refactors the virt > driver's get_available_resource() method [1], I am stuck between two > concerns. I like (love even) much of the refactoring work involved in > Dan's

Re: [openstack-dev] [Nova] Cells conversation starter

On 10/20/2014 08:00 PM, Andrew Laski wrote: > One of the big goals for the Kilo cycle by users and developers of the > cells functionality within Nova is to get it to a point where it can be > considered a first class citizen of Nova. Ultimately I think this comes > down to getting it tested by de

Re: [openstack-dev] [nova] Nova Project Priorities for Kilo

On 10/07/2014 01:01 AM, Joe Gordon wrote: > Hi all, > > One of the outcomes of the nova midcyle meetup was to pick several > things for nova, as a team, to prioritize in Kilo. More background on > this can be found at [0] > > We are now collecting ideas for project priorities on this etherpad [1]

Re: [openstack-dev] [Nova] What's holding nova development back?

On 09/14/2014 12:27 AM, Boris Pavlovic wrote: > Michael, > > I am so glad that you started this topic. > I really like idea of of taking a pause with features and concentrating > on improvement of current code base. > > Even if the >1 k open bugs https://bugs.launchpad.net/nova are vital > iss

Re: [openstack-dev] [Nova] What's holding nova development back?

On 09/13/2014 11:07 PM, Michael Still wrote: > Just an observation from the last week or so... > > The biggest problem nova faces at the moment isn't code review latency. > Our biggest problem is failing to fix our bugs so that the gate is > reliable. The number of rechecks we've done in the last

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

On 09/05/2014 05:20 PM, 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, a

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

/2014-September/044669.html On 09/04/2014 01:58 PM, 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

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

On 09/04/2014 10:25 PM, Solly Ross wrote: > Anyway, I think it would be useful to have some sort of page where people > could say "I'm an SME in X, ask me for reviews" and then patch submitters > could go > and say, "oh, I need an someone to review my patch about storage backends, > let me > ask

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

On 09/05/2014 01:26 AM, Jay Pipes wrote: > On 09/04/2014 10:33 AM, 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). > > The difference between Dan's propo

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

On 09/04/2014 12:24 PM, Daniel P. Berrange wrote: > 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

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

On 09/04/2014 07:42 PM, Murray, Paul (HP Cloud) wrote: > > >> > >>> Anyway, not enough to -1 it, but enough to at least say something. > >> > >>> > >> > >> > >> > >> .. but I do not want to get into the discussion about software testing > >> > >> here, not the place really. > >>

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

On 09/04/2014 11:23 AM, John Garbutt wrote: > Sorry for another top post, but I like how Nikola has pulled this > problem apart, and wanted to respond directly to his response. > Thanks John - I'm glad this caught your eye. > On 3 September 2014 10:50, Nikola Đipanov wrote: &

Re: [openstack-dev] [nova] requesting an FFE for SRIOV

On 09/04/2014 05:16 PM, Dan Smith wrote: >> The main sr-iov patches have gone through lots of code reviews, manual >> rebasing, etc. Now we have some critical refactoring work on the >> existing infra to get it ready. All the code for refactoring and sr-iov >> is up for review. > > I've been doi

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

On 09/04/2014 04:51 PM, Murray, Paul (HP Cloud) wrote: > > > On 4 September 2014 14:07, 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, > >>> > >>

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

On 09/04/2014 03:46 PM, Daniel P. Berrange wrote: > 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/10975

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

On 09/04/2014 02:42 PM, 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/serial-ports,n,z >

  1   2   >