Re: [openstack-dev] [nova] [placement] Which service is using port 8778?

Le 20/12/2016 09:29, Sylvain Bauza a écrit : > > > Le 20/12/2016 09:12, Sylvain Bauza a écrit : >> >> >> Le 20/12/2016 07:31, Ghanshyam Mann a écrit : >>> Changing placement API port to 8780 [1], hope this is not being used by any >>> services. &g

Re: [openstack-dev] [nova] [placement] Which service is using port 8778?

Le 20/12/2016 09:12, Sylvain Bauza a écrit : > > > Le 20/12/2016 07:31, Ghanshyam Mann a écrit : >> Changing placement API port to 8780 [1], hope this is not being used by any >> services. >> >> But I am not sure how to check all used port currently as wi

Re: [openstack-dev] [nova] [placement] Which service is using port 8778?

Le 20/12/2016 07:31, Ghanshyam Mann a écrit : > Changing placement API port to 8780 [1], hope this is not being used by any > services. > > But I am not sure how to check all used port currently as wiki does not seems > to have all. > > .. [1] https://review.openstack.org/#/c/412770/ >

Re: [openstack-dev] [nova] Upgrade readiness check notes

Le 16/12/2016 03:53, Matt Riedemann a écrit : > A few of us have talked about writing a command to tell when you're > ready to upgrade (restart services with new code) for Ocata because we > have a few things landing in Ocata which are going from optional to > required, namely cells v2 and the

Re: [openstack-dev] [nova] placement/resource providers update 5

Le 09/12/2016 15:50, Chris Dent a écrit : > > A shorter resource provider placement update this week. In part this > is because some of the things to think about from last week[0] got > resolved. What's below is essentially a collection of pending work > related to resource providers and the

Re: [openstack-dev] [nova] placement/resource providers update 4

Le 08/12/2016 02:28, Jay Pipes a écrit : > On 12/07/2016 07:06 PM, Matt Riedemann wrote: >> On 12/7/2016 2:40 AM, Sylvain Bauza wrote: >>> >>> FWIW, I think POST is not that complex and allows us to have room for >>> further request information like t

Re: [openstack-dev] [nova] placement/resource providers update 4

Le 07/12/2016 01:07, melanie witt a écrit : > On Tue, 6 Dec 2016 16:04:14 -0500, Jay Pipes wrote: >> We're discussing only doing: >> >> GET /resource_providers? >> >> Once we start doing claims in the scheduler, we'll have the ability to >> do: >> >> POST /allocations >> { >> > all kinds

Re: [openstack-dev] [nova] Is this a correct use of scheduler hints and nova-scheduler

Le 07/12/2016 04:21, Zhenyu Zheng a écrit : > Hi all, > > I want to ask a question about using scheduler-hints, could we add > custom scheduler keys to work with our custom filters? Is it designed to > allow vendors add own custom filters and keys? > I tend to disagree with that approach from

Re: [openstack-dev] [nova] placement/resource providers update 4

Le 06/12/2016 22:02, Ed Leafe a écrit : > On Dec 6, 2016, at 2:42 PM, Jay Pipes wrote: > >> Oh, absolutely, I wasn't arguing about length of URI or anything. >> >> To be clear, I could either go the above route or even do a POST >> /resource_providers that returns a list

Re: [openstack-dev] [Blazar] Blazar weekly teem meeting starts again

Le 05/12/2016 05:45, Masahito MUROI a écrit : > Hi Stackers, > > I'm happy to announce it in openstack-dev ML that weekly Blazar team > meeting is going to start again from 6th Dec. > > Some of folks who are interested in resource reservation feature met > together in Barcelona summit and

Re: [openstack-dev] [nova] Nominating Stephen Finucane for nova-core

Le 02/12/2016 16:22, Matt Riedemann a écrit : > I'm proposing that we add Stephen Finucane to the nova-core team. > Stephen has been involved with nova for at least around a year now, > maybe longer, my ability to tell time in nova has gotten fuzzy over the > years. Regardless, he's always been

Re: [openstack-dev] [nova] [telemetry] PostgreSQL gate broken

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 25/11/2016 18:24, Sylvain Bauza a écrit : > > > Le 24/11/2016 13:58, Sylvain Bauza a écrit : > > >> Le 24/11/2016 11:57, Julien Danjou a écrit : >>> Hi, > >>> It seems Nova broke its PostgreS

Re: [openstack-dev] [nova] [telemetry] PostgreSQL gate broken

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 24/11/2016 13:58, Sylvain Bauza a écrit : > > > Le 24/11/2016 11:57, Julien Danjou a écrit : >> Hi, > >> It seems Nova broke its PostgreSQL support recently, and that >> impacts Telemetry as we do gate

Re: [openstack-dev] [nova] [telemetry] PostgreSQL gate broken

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 24/11/2016 11:57, Julien Danjou a écrit : > Hi, > > It seems Nova broke its PostgreSQL support recently, and that > impacts Telemetry as we do gate on PostgreSQL. I opened a bug: > > https://bugs.launchpad.net/nova/+bug/1644513 > > Could

Re: [openstack-dev] [Nova] Stepping back

Le 22/11/2016 17:39, Andrew Laski a écrit : > I should have sent this weeks ago but I'm a bad person who forgets > common courtesy. My employment situation has changed in a way that does > not afford me the necessary time to remain a regular contributor to > Nova, or the broader OpenStack

Re: [openstack-dev] [nova] Welcome Lee Yarwood to nova-stable-maint core

Le 17/11/2016 14:53, Matt Riedemann a écrit : > I've added Lee Yarwood to the nova-stable-maint core team: > > https://review.openstack.org/#/admin/groups/540,members > > Lee has done a great job the last few months of proposing backports and > reviewing changes to nova on the stable branches.

Re: [openstack-dev] [nova] About doing the migration claim with Placement API

Le 02/11/2016 12:26, Alex Xu a écrit : 2016-11-02 16:26 GMT+08:00 Sylvain Bauza <sba...@redhat.com <mailto:sba...@redhat.com>>: Le 01/11/2016 15:14, Alex Xu a écrit : Currently we only update the resource usage with Placement API in the instance claim and t

Re: [openstack-dev] [nova] About doing the migration claim with Placement API

Le 01/11/2016 15:14, Alex Xu a écrit : Currently we only update the resource usage with Placement API in the instance claim and the available resource update periodic task. But there is no claim for migration with placement API yet. This works is tracked by

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

Le 10/10/2016 19:24, Clint Byrum a écrit : Excerpts from Matt Riedemann's message of 2016-10-10 11:51:36 -0500: On 10/10/2016 8:59 AM, Sean McGinnis wrote: On Mon, Oct 10, 2016 at 08:37:53AM -0400, Doug Hellmann wrote: We had a lot of feedback that the unstructured discussion time from

Re: [openstack-dev] [nova] Draft Ocata design summit schedule is up

Le 06/10/2016 15:41, Chris Dent a écrit : On Wed, 5 Oct 2016, Matt Riedemann wrote: The draft design summit schedule for nova is here: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Nova%3A [snip] If there are any questions or issues with this please

Re: [openstack-dev] postgresql fails mitaka -> newton migrations on nova

Le 05/10/2016 08:18, Matthew Thode a écrit : I've found two possible bugs, one with the online_data_migrations and one after services are started again (ignoring the online_data_migration failures). The online_data_migration bug is located at: https://bugs.launchpad.net/nova/+bug/1630446

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Le 03/10/2016 12:27, Sylvain Bauza a écrit : Le 03/10/2016 12:02, Sylvain Bauza a écrit : Le 03/10/2016 02:54, Matt Riedemann a écrit : There was a pycparser 2.14 package update on pypi today which is making cinder-manager db sync fail. This is making all dsvm/grenade jobs fail

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Le 03/10/2016 12:02, Sylvain Bauza a écrit : Le 03/10/2016 02:54, Matt Riedemann a écrit : There was a pycparser 2.14 package update on pypi today which is making cinder-manager db sync fail. This is making all dsvm/grenade jobs fail in master and stable/newton. The upstream issue being

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Le 03/10/2016 02:54, Matt Riedemann a écrit : There was a pycparser 2.14 package update on pypi today which is making cinder-manager db sync fail. This is making all dsvm/grenade jobs fail in master and stable/newton. The upstream issue being tracked is:

Re: [openstack-dev] [nova] Latest news on placement API and Ocata rough goals

have a good idea of assignees for various work and what is going to be realistic to complete in Ocata. Best, -jay [1] I'd like to personally thank Chris Dent, Dan Smith, Sean Dague, Ed Leafe, Sylvain Bauza, Andrew Laski, Alex Xu and Matt Riedemann for tolerating my sometimes lengthy absences

Re: [openstack-dev] [nova] TL; DR A proposed subsystem maintainer model

Le 20/09/2016 13:07, Matthew Booth a écrit : * +A is reserved for cores. * A subsystem maintainer's domain need not be defined by the directory tree: subteams are a good initial model. * A maintainer should only +2 code in their own domain in good faith, enforced socially, not

Re: [openstack-dev] [nova] Question about fixing missing soft deleted rows

Le 15/09/2016 14:21, Sean Dague a écrit : On 09/14/2016 09:21 PM, Matt Riedemann wrote: I'm looking for other input on a question I have in this change: https://review.openstack.org/#/c/345191/4/nova/db/sqlalchemy/api.py We've had a few patches like this where we don't (soft) delete entries

Re: [openstack-dev] [nova] Question about fixing missing soft deleted rows

Le 15/09/2016 03:21, Matt Riedemann a écrit : I'm looking for other input on a question I have in this change: https://review.openstack.org/#/c/345191/4/nova/db/sqlalchemy/api.py We've had a few patches like this where we don't (soft) delete entries related to an instance when that instance

Re: [openstack-dev] [nova] Bug team meeting

Le 07/09/2016 10:50, Kashyap Chamarthy a écrit : On Tue, Sep 06, 2016 at 03:41:04PM -0700, Augustina Ragwitz wrote: I should add that I also expressed interest in taking over the Bug Czar role. I've been actively involved with the bugs team since Markus revived it earlier this year. I've run

Re: [openstack-dev] [nova] resignation from bug czar role

Le 05/09/2016 13:19, Markus Zoeller a écrit : TL;DR: bug czar role for Nova is vacant from now on After doing bug triage for ~1 year, which was quiet interesting, it's time for me to move to different topics. My tasks within the company internal team are shifting too. Unfortunately less Nova

Re: [openstack-dev] Seeking Mobile Beta Testers

Le 02/09/2016 19:57, Jimmy McArthur a écrit : We're looking for a handful of community members to test our updated OpenStack Summit mobile Apps. If you're interested, shoot me a note, along with iOS/Android preference, and we'll get you set up. Count me in. The previous experience in

Re: [openstack-dev] [nova] Next steps for resource providers work

Le 31/08/2016 13:08, Jay Pipes a écrit : On 08/29/2016 12:40 PM, Matt Riedemann wrote: I've been out for a week and not very involved in the resource providers work, but after talking about the various changes up in the air at the moment a bunch of us thought it would be helpful to lay out

Re: [openstack-dev] [Nova] Reconciling flavors and block device mappings

Le 29/08/2016 14:43, Andrew Laski a écrit : On Mon, Aug 29, 2016, at 08:20 AM, Jay Pipes wrote: On 08/29/2016 05:11 AM, Sylvain Bauza wrote: Le 29/08/2016 13:25, Jay Pipes a écrit : On 08/26/2016 09:20 AM, Ed Leafe wrote: On Aug 25, 2016, at 3:19 PM, Andrew Laski <and...@lascii.com>

Re: [openstack-dev] [Nova] Reconciling flavors and block device mappings

Le 29/08/2016 14:20, Jay Pipes a écrit : On 08/29/2016 05:11 AM, Sylvain Bauza wrote: Le 29/08/2016 13:25, Jay Pipes a écrit : On 08/26/2016 09:20 AM, Ed Leafe wrote: On Aug 25, 2016, at 3:19 PM, Andrew Laski <and...@lascii.com> wrote: One other thing to note is that while a

Re: [openstack-dev] [Nova] Reconciling flavors and block device mappings

Le 29/08/2016 13:25, Jay Pipes a écrit : On 08/26/2016 09:20 AM, Ed Leafe wrote: On Aug 25, 2016, at 3:19 PM, Andrew Laski wrote: One other thing to note is that while a flavor constrains how much local disk is used it does not constrain volume size at all. So a user

Re: [openstack-dev] [Nova] Reconciling flavors and block device mappings

Le 26/08/2016 12:33, Chris Dent a écrit : On Thu, 25 Aug 2016, Sylvain Bauza wrote: Of course, long-term, we could try to see how to have composite flavors for helping users to not create a whole handful of flavors for quite the same user requests, but that would still be flavors

Re: [openstack-dev] [Nova] Reconciling flavors and block device mappings

Le 25/08/2016 16:19, Andrew Laski a écrit : Cross posting to gather some operator feedback. There have been a couple of contentious patches gathering attention recently about how to handle the case where a block device mapping supersedes flavor information. Before moving forward on either of

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

Le 15/08/2016 22:59, Andrew Laski a écrit : On Mon, Aug 15, 2016, at 10:33 AM, Jay Pipes wrote: On 08/15/2016 09:27 AM, Andrew Laski wrote: Currently in Nova we're discussion adding a "capabilities" API to expose to users what actions they're allowed to take, and having compute hosts expose

Re: [openstack-dev] [nova] [placement] unresolved topics in resource providers/placement api

Le 28/07/2016 15:57, Chris Dent a écrit : I've been reviewing my notes from the mid-cycle and discussions leading up to it and realized I have a few unresolved or open topics that I hope discussion here can help resolve: # fairly straightforward things * At what stage in the game (of the

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

Le 23/06/2016 02:42, Tony Breeds a écrit : On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote: Le 22/06/2016 à 10:49, Thomas Goirand a écrit : Do you think it looks like possible to have Nova ported to Py3 during the Newton cycle? It doesn't depend on me: I'm sending patches,

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Le 21/06/2016 14:00, Sean Dague a écrit : On 06/21/2016 07:39 AM, Jay Pipes wrote: On 06/21/2016 05:43 AM, Sylvain Bauza wrote: Le 21/06/2016 10:04, Chris Dent a écrit : On Mon, 20 Jun 2016, Jay Pipes wrote: Flask seems to be the most widely used and known WSGI framework so

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Le 21/06/2016 10:04, Chris Dent a écrit : On Mon, 20 Jun 2016, Jay Pipes wrote: Flask seems to be the most widely used and known WSGI framework so for consistency's sake, I'm recommending we just use it and not rock this boat. There are more important things to get hung up on than this

Re: [openstack-dev] [nova] [api] [placement] strategy for placement api structure

Le 20/06/2016 16:04, Jay Pipes a écrit : On 06/17/2016 11:23 AM, Sylvain Bauza wrote: +1000 yes to that. Now the devil could be in the details, in particular how we implement the WSGI server, the corresponding WSGI app and the associated routing, and that's exactly the problem below. We

Re: [openstack-dev] [nova] [api] [placement] strategy for placement api structure

Le 17/06/2016 18:11, Dean Troyer a écrit : On Fri, Jun 17, 2016 at 10:23 AM, Sylvain Bauza <sba...@redhat.com <mailto:sba...@redhat.com>> wrote: In the review, you explain why you don't trust Routes and I respect that. That said, are those issues logged as real problems

Re: [openstack-dev] [nova] [api] [placement] strategy for placement api structure

Le 17/06/2016 12:55, Chris Dent a écrit : tl;dr: Have a look at https://review.openstack.org/#/c/329386/ to help move some placement API decisions along. Not really that long, do read: As part of the generic resource pools spec[1] a new, independent of the rest of nova, API is being

Re: [openstack-dev] [nova] [placement] conducting, ovo and the placement api

Le 04/06/2016 16:37, Dan Smith a écrit : There was a conversation earlier this week in which, if I understood things correctly, one of the possible outcomes was that it might make sense for the new placement service (which will perform the function currently provided by the scheduler in Nova)

Re: [openstack-dev] [nova] [cinder] nova's broken py27/py33 and functional tests

requirements for UTs (instead, we directly download the upper-constraints file) Thanks, -Sylvain -- Dims On Mon, May 30, 2016 at 11:15 AM, Sylvain Bauza <sba...@redhat.com> wrote: (titling now accordingly) Le 30/05/2016 14:01, Sylvain Bauza a écrit : Hi, For the moment, we have

Re: [openstack-dev] [nova] [cinder] nova's broken py27/py33 and functional tests

(titling now accordingly) Le 30/05/2016 14:01, Sylvain Bauza a écrit : Hi, For the moment, we have a non-resolved critical bug hitting our UTs and functional tests : https://bugs.launchpad.net/nova/+bug/1586976 Markus Z. and I are currently investigating the root cause, but in the meantime

[openstack-dev] [nova] Broken py27/py33 and functional tests

Hi, For the moment, we have a non-resolved critical bug hitting our UTs and functional tests : https://bugs.launchpad.net/nova/+bug/1586976 Markus Z. and I are currently investigating the root cause, but in the meantime, please refrain asking for rechecks unless you're sure why you're

Re: [openstack-dev] [neutron] [nova] scheduling bandwidth resources / NIC_BW_KB resource class

Le 22/04/2016 16:14, Matt Riedemann a écrit : On 4/22/2016 2:48 AM, Sylvain Bauza wrote: Le 22/04/2016 02:49, Jay Pipes a écrit : On 04/20/2016 06:40 PM, Matt Riedemann wrote: Note that I think the only time Nova gets details about ports in the API during a server create request is when

Re: [openstack-dev] [neutron] [nova] scheduling bandwidth resources / NIC_BW_KB resource class

Le 22/04/2016 02:49, Jay Pipes a écrit : On 04/20/2016 06:40 PM, Matt Riedemann wrote: Note that I think the only time Nova gets details about ports in the API during a server create request is when doing the network request validation, and that's only if there is a fixed IP address or

Re: [openstack-dev] [nova] Proposing Andrey Kurilin for python-novaclient core

Le 13/04/2016 19:53, Matt Riedemann a écrit : I'd like to propose that we make Andrey Kurilin core on python-novaclient. He's been doing a lot of the maintenance the last several months and a lot of times is the first to jump on any major issue, does a lot of the microversion work, and is

Re: [openstack-dev] [nova] Newton midcycle planning

Le 11/04/2016 22:49, Matt Riedemann a écrit : A few people have been asking about planning for the nova midcycle for newton. Looking at the schedule [1] I'm thinking weeks R-15 or R-11 work the best. R-14 is close to the US July 4th holiday, R-13 is during the week of the US July 4th

Re: [openstack-dev] [all][elections] Results of the TC Election

Le 08/04/2016 14:24, Eoghan Glynn a écrit : Please join me in congratulating the 7 newly elected members of the TC. << REMOVE UNEEDED > * Davanum Srinivas (dims) * Flavio Percoco (flaper87) * John Garbutt (johnthetubaguy) * Matthew Treinish (mtreinish) * Mike Perez (thingee) *

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

Le 06/04/2016 06:44, Qiming Teng a écrit : Not an expert of Nova but I am really shocked by such a change. Because I'm not a Nova expert, I don't have a say on the *huge* efforts in maintaining some builtin/default flavors. As a user I don't care where the data have been stored, but I do care

Re: [openstack-dev] [all] Austin Design Summit track layout

Le 29/03/2016 09:48, Thierry Carrez a écrit : Matt Riedemann wrote: I see one problem. The single stable team fishbowl session is scheduled for the last slot on Thursday (5pm). The conflict I have with that is the nova team does it's priority/scheduling talk in the last session on the last

Re: [openstack-dev] [nova] no more expand/contract for live upgrade?

Le 18/03/2016 09:48, Dulko, Michal a écrit : On Fri, 2016-03-18 at 08:27 +, Tan, Lin wrote: Hi, I noticed that expand/migrate/contract was revert in https://review.openstack.org/#/c/239922/ There is a new CMD 'online_data_migrations' was introduced to Nova and some data-migration

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

Le 15/03/2016 14:48, Matt Riedemann a écrit : On 3/15/2016 8:37 AM, Chris Dent wrote: On Tue, 15 Mar 2016, Markus Zoeller wrote: Long story short, I'm in favor of abandoning the use of "wishlist" as an importance in bug reports to track requests for enhancements. While I'm very much in

Re: [openstack-dev] [nova] Nova PTL for Newton

Le 11/03/2016 20:22, John Garbutt a écrit : Hi, It has been greatly rewarding serving you all as Nova PTL over the Liberty and Mitaka cycles. I thank you all for the support, encouragement and advice I have been given over the last year. I really appreciate that. (That's british speak for "I

Re: [openstack-dev] [all][zaqar][cloudkitty] Default ports list

Le 09/03/2016 23:41, Matt Fischer a écrit : This is not the first time. Monasca and Murano had a collision too[1]. When this happens the changes trickle down into automation tools also and complicates things. [1] https://bugs.launchpad.net/murano/+bug/1505785 IMHO, all that info has to

Re: [openstack-dev] [all][i18n] Liaisons for I18n

Le 04/03/2016 12:24, Ihar Hrachyshka a écrit : Tony Breeds wrote: On Mon, Feb 29, 2016 at 05:26:44PM +0800, Ying Chun Guo wrote: If you are interested to be a liaison and help translators, input your information here:

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

Both of you, thanks for your insights. Greatly appreciated. Le 04/03/2016 09:25, Cheng, Yingxin a écrit : Hi, First of all, many delayed thanks to Jay Pipes's benchmarking framework, learnt a lot from it : ) Other comments inline. On Friday, March 4, 2016 8:42 AM Jay Pipes wrote: Hi again,

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

Le 02/03/2016 09:15, Cheng, Yingxin a écrit : On Tuesday, March 1, 2016 7:29 PM, John Garbutt wrote On 1 March 2016 at 08:34, Cheng, Yingxin wrote: Hi, I have simulated the distributed resource management with the incremental update

Re: [openstack-dev] [all] A proposal to separate the design summit

Le 01/03/2016 11:08, Eoghan Glynn a écrit : Current thinking would be to give preferential rates to access the main summit to people who are present to other events (like this new separated contributors-oriented event, or Ops midcycle(s)). That would allow for a wider definition of "active

Re: [openstack-dev] [all] A proposal to separate the design summit

Honestly, it took me a while before having an opinion on that subject. Le 26/02/2016 18:08, Thierry Carrez a écrit : Thierry Carrez wrote: 1. "Two trips instead of one" There is a section of attendees which benefited from a single event: in-between people who do not generally go to any

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

Le 24/02/2016 01:10, Jay Pipes a écrit : On 02/22/2016 04:23 AM, Sylvain Bauza wrote: I won't argue against performance here. You made a very nice PoC for testing scaling DB writes within a single python process and I trust your findings. While I would be naturally preferring some shared

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

verything goes terribly, terribly wrong. Best, -jay [1] https://docs.google.com/document/d/1iNUkmnfEH3bJHDSenmwE4A1Sgm3vnqa6oZJWtTumAkw/edit?usp=sharing [2] https://review.openstack.org/#/c/271823/ Regards, -Yingxin *From:*Sylvain Bauza [mailto:sba...@redhat.com] *Sent:* Monday, Februar

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

(sorry, quoting off-context, but I feel it's a side point, not the main discussion) Le 17/02/2016 16:40, Cheng, Yingxin a écrit : IMHO, the authority to allocate resources is not limited by compute nodes, but also include network service, storage service or all other services which have

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

Le 17/02/2016 12:59, Chris Dent a écrit : On Wed, 17 Feb 2016, Cheng, Yingxin wrote: To better illustrate the differences between shared-state, resource- provider and legacy scheduler, I've drew 3 simplified pictures [1] in emphasizing the location of resource view, the location of claim and

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

Le 16/02/2016 13:01, Sean Dague a écrit : On 02/16/2016 03:33 AM, Sylvain Bauza wrote: Le 16/02/2016 09:30, Sylvain Bauza a écrit : Le 16/02/2016 04:09, Alex Xu a écrit : 2016-02-16 9:47 GMT+08:00 GHANSHYAM MANN <ghanshyamm...@gmail.com <mailto:ghanshyamm...@gmail.com>>:

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

Le 16/02/2016 09:30, Sylvain Bauza a écrit : Le 16/02/2016 04:09, Alex Xu a écrit : 2016-02-16 9:47 GMT+08:00 GHANSHYAM MANN <ghanshyamm...@gmail.com <mailto:ghanshyamm...@gmail.com>>: Regards Ghanshyam Mann On Mon, Feb 15, 2016 at 12:07 PM, Alex Xu <s

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

Le 16/02/2016 04:09, Alex Xu a écrit : 2016-02-16 9:47 GMT+08:00 GHANSHYAM MANN >: Regards Ghanshyam Mann On Mon, Feb 15, 2016 at 12:07 PM, Alex Xu > wrote: > If we

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

. That is one of the things I'd like to see in your spec, and how you could interact with the new model. Thanks, -Sylvain Regards, -Yingxin *From:*Sylvain Bauza [mailto:sba...@redhat.com] *Sent:* Monday, February 15, 2016 5:28 PM *To:* OpenStack Development Mailing List (not for usage questions

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

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, reliability and compatibility improvements. It will also be an Austin

[openstack-dev] [nova] New API DB in use

(Sorry I usually hate cross-posting, but I've been told to reach both communities) Starting from Kilo, a new DB has been added for Nova that we call "API DB" [1]. It's part of the on-going Cells V2 effort that is not yet to be production-ready. During Liberty, we populated this fresh

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

Le 30 janv. 2016 09:32, "Julien Danjou" <jul...@danjou.info> a écrit : > > On Fri, Jan 29 2016, Sylvain Bauza wrote: > > > While my heart is about that, my brain thinks about some regressions could > > be happening because of a +W even for a small change.

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

Le 29 janv. 2016 18:45, "Julien Danjou" a écrit : > > On Fri, Jan 29 2016, Doug Hellmann wrote: > > > Right. I trust everyone on the team to exercise judgment when > > choosing which patches to review, and how to review them. I proposed > > Alexis for oslo-core rather than

Re: [openstack-dev] [Openstack-operators] [nova][cells] Should flavors in the API DB for cells v2 be soft-deletable?

Le 08/01/2016 15:10, Andrew Laski a écrit : On 01/08/16 at 12:43pm, John Garbutt wrote: On 7 January 2016 at 19:59, Matt Riedemann wrote: There is a cells v2 change up for review [1] which creates the flavor tables in the API DB. I noted that those table

[openstack-dev] [nova] Next meeting is tomorrow 2100UTC

Hi, Just a reminder that we're alternating meetings [1] but since this week number is odd, the next meeting will be held on Thursday Jan 7th at 2100UTC. Explanations can be found here http://lists.openstack.org/pipermail/openstack-dev/2016-January/083216.html "Odd" and "Even" meetings will

Re: [openstack-dev] Nova scheduler startup when database is not available

Le 24/12/2015 02:35, Morgan Fainberg a écrit : On Wed, Dec 23, 2015 at 10:32 AM, Jay Pipes > wrote: On 12/23/2015 12:27 PM, Lars Kellogg-Stedman wrote: I've been looking into the startup constraints involved when

Re: [openstack-dev] [nova][api] does validation bug-fix require microversion bump?

Le 21/12/2015 08:25, Ken'ichi Ohmichi a écrit : Hi nova-api team, I'd like to get a feedback about the way to bump a microversion. Short version: We found a validation bug on Nova v2.1 API. To fix the bug, do we need to bump a new microversion? Long version: As LP bug report[1], nova

Re: [openstack-dev] [nova] proposed new compute review dashboard

Le 18/12/2015 15:20, Sean Dague a écrit : With Gerrit 2.11 upgrade in place, we get access to a few new query parameters. I've retooled the compute review dashboard in gerrit-dash-creator (https://github.com/openstack/gerrit-dash-creator) to take advantage of it. The url is -

Re: [openstack-dev] [doc] DocImpact vs. reno

Le 18/12/2015 20:31, Andreas Jaeger a écrit : On 12/18/2015 07:45 PM, Sean Dague wrote: On 12/18/2015 01:34 PM, Andreas Jaeger wrote: On 12/18/2015 07:03 PM, Sean Dague wrote: Recently noticed that a new job ended up on all nova changes that was theoertically processing commit messages for

Re: [openstack-dev] [gate] any project using olso.db test_migrations is currently blocked

Le 16/12/2015 14:59, Sean Dague a écrit : oslo.db test_migrations is using methods for alembic, which changed in the 0.8.4 release. This ends up causing a unit test failure (at least in the Nova case) that looks like this -

Re: [openstack-dev] [nova] jsonschema for scheduler hints

Le 08/12/2015 21:23, Andrew Laski a écrit : On 12/06/15 at 02:49pm, Ken'ichi Ohmichi wrote: Hi Sean, 2015-12-02 23:23 GMT+09:00 Sean Dague : We have previously agreed that scheduler hints in Nova are an open ended thing. It's expected for sites to have additional scheduler

Re: [openstack-dev] [Openstack-operators] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

Le 07/12/2015 11:27, Dina Belova a écrit : Ok, so due to the responses I propose to finalise this decision and move the meeting to *16:00 UTC (Tuesdays)*. So tomorrow please join me *on #openstack-performance at 16:00 UTC.* Why are you not using the meeting channels? You should also

Re: [openstack-dev] [nova] jsonschema for scheduler hints

Le 04/12/2015 04:21, Alex Xu a écrit : 2015-12-02 23:12 GMT+08:00 Sylvain Bauza <sba...@redhat.com <mailto:sba...@redhat.com>>: Le 02/12/2015 15:23, Sean Dague a écrit : We have previously agreed that scheduler hints in Nova are an open ended

Re: [openstack-dev] [nova] jsonschema for scheduler hints

Le 02/12/2015 15:23, Sean Dague a écrit : We have previously agreed that scheduler hints in Nova are an open ended thing. It's expected for sites to have additional scheduler filters which expose new hints. The way we handle that with our strict jsonschema is that we allow additional

[openstack-dev] [nova] Milestone 13.0.0.0b1 (aka. Mitaka-1) to be cut tomorrow

Hi, As you probably know, the Mitaka Release schedule for Nova defines a first milestone between Dec 1-3 [1] We had an hard dependency for translations and reno changes [2] but now everything is landed in tree. As a consequence, the release patch is provided for cutting the milestone

Re: [openstack-dev] [nova-scheduler] Scheduler sub-group meeting - Agenda 11/30

Le 30/11/2015 15:17, Dugger, Donald D a écrit : Sorry guys, I can't get onto IRC so, if any of you can connect you'll just have to muddle through without me :-) Hopefully freenode will be back up next week. We had a discussion on the channel, and the agreement was to cancel the meeting

Re: [openstack-dev] [nova] nova-manage db archive_deleted_rows broken

Le 20/11/2015 17:36, Matt Riedemann a écrit : On 11/20/2015 10:04 AM, Andrew Laski wrote: On 11/20/15 at 09:51am, Matt Riedemann wrote: On 11/20/2015 8:18 AM, Sean Dague wrote: On 11/17/2015 10:51 PM, Matt Riedemann wrote: I *don't* see any DB APIs for deleting instance actions.

Re: [openstack-dev] [nova] release notes with reno and which patches need that?

Le 19/11/2015 18:37, Markus Zoeller a écrit : If you ever had a patch which contained "UpgradeImpact" or "DocImpact", this mail is for you. You may have already heard of "reno" and how it will change the handling of the release notes. If not, [1] is the announcement and [2] is an example. I

Re: [openstack-dev] [nova] release notes with reno and which patches need that?

Le 19/11/2015 20:46, Sylvain Bauza a écrit : Le 19/11/2015 18:37, Markus Zoeller a écrit : If you ever had a patch which contained "UpgradeImpact" or "DocImpact", this mail is for you. You may have already heard of "reno" and how it will change the handling of

Re: [openstack-dev] [oslo] [nova] default-next-release opt flag

Le 18/11/2015 16:34, Sean Dague a écrit : On 11/17/2015 05:31 PM, Matt Riedemann wrote: On 11/17/2015 2:05 PM, Sylvain Bauza wrote: Le 17/11/2015 20:25, Sean Dague a écrit : On 11/17/2015 01:48 PM, Matt Riedemann wrote: On 11/17/2015 11:28 AM, Alexis Lee wrote: Often in Nova we

Re: [openstack-dev] [oslo] [nova] default-next-release opt flag

Le 17/11/2015 20:25, Sean Dague a écrit : On 11/17/2015 01:48 PM, Matt Riedemann wrote: On 11/17/2015 11:28 AM, Alexis Lee wrote: Often in Nova we introduce an option defaulted off (so as not to break people) but then we want to make it default in the next release. Someone suggested an opt

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

Le 13/11/2015 10:36, John Garbutt a écrit : On 6 November 2015 at 15:32, John Garbutt <j...@johngarbutt.com> wrote: Hi, I propose we add Sylvain Bauza[1] to nova-core. Over the last few cycles he has consistently been doing great work, including some quality reviews, particularly

[openstack-dev] [nova] How can I contribute to the scheduler codebase?

Hi, During the last Nova scheduler meeting (held every Mondays 1400UTC on #openstack-meeting-alt), we identified some on-going effort that could possibly be addressed by anyone wanting to step in. For the moment, we are still polishing the last bits of agreement, but those blueprints should

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

Le 06/11/2015 07:08, Tony Breeds a écrit : Hello all, I came across [1] which is notionally an ironic bug in that horizon presents VM operations (like suspend) to users. Clearly these options don't make sense to ironic which can be confusing. There is a horizon fix that just disables

Re: [openstack-dev] [nova][bugs] weekly bug status + bug tag contacts

Le 03/11/2015 12:53, Markus Zoeller a écrit : Hey Nova folks, this is your bug lord speaking. You may have noticed that we have around 3 bugs open ... just kidding, it's above 1000 and keeps growing. During the summit, we concluded that the "fix all the crap" action item was a bit too

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

Le 28/09/2015 16:19, Sean Dague a écrit : On 09/28/2015 10:11 AM, Andrew Laski wrote: On 09/28/15 at 08:50am, Monty Taylor wrote: On 09/28/2015 07:58 AM, Sylvain Bauza wrote: Specifically, I want "nova boot" to get me a VM with an IP address. I don't want it to do fancy orchest

<    1   2   3   4   5   6   >