[openstack-dev] [nova][neutron] Rocky PTG summary - nova/neutron

Hello Stackers, I've put together an etherpad [0] for the summary of the nova/neutron session from the PTG in the Croke Park Hotel breakfast area and included it as a plain text export on this email. Please feel free to edit or reply to this thread to add/correct anything I've missed.

Re: [openstack-dev] [nova] about rebuild instance booted from volume

>, openstack-operators <openstack-operat...@lists.openstack.org> Subject: Re: [openstack-dev] [nova] about rebuild instance booted from volume On 03/15/2018 09:46 AM, Dan Smith wrote: >> Rather than overload delete_on_termination, could another flag li

Re: [openstack-dev] [nova] about rebuild instance booted from volume

On 03/15/2018 09:46 AM, Dan Smith wrote: Rather than overload delete_on_termination, could another flag like delete_on_rebuild be added? Isn't delete_on_termination already the field we want? To me, that field means "nova owns this". If that is true, then we should be able to re-image the

Re: [openstack-dev] [nova][placement] update_provider_tree design updates

On Thu, 15 Mar 2018, Eric Fried wrote: One of the takeaways from the Queens retrospective [1] was that we should be summarizing discussions that happen in person/hangout/IRC/etc. to the appropriate mailing list for the benefit of those who weren't present (or paying attention :P ). This is

[openstack-dev] [nova][placement] update_provider_tree design updates

One of the takeaways from the Queens retrospective [1] was that we should be summarizing discussions that happen in person/hangout/IRC/etc. to the appropriate mailing list for the benefit of those who weren't present (or paying attention :P ). This is such a summary. As originally conceived,

Re: [openstack-dev] [nova] about rebuild instance booted from volume

> Rather than overload delete_on_termination, could another flag like > delete_on_rebuild be added? Isn't delete_on_termination already the field we want? To me, that field means "nova owns this". If that is true, then we should be able to re-image the volume (in-place is ideal, IMHO) and if not,

Re: [openstack-dev] [nova] about rebuild instance booted from volume

On 03/14/2018 08:46 AM, Matt Riedemann wrote: On 3/14/2018 3:42 AM, 李杰 wrote:              This is the spec about  rebuild a instance booted from volume.In the spec,there is a        question about if we should delete the old root_volume.Anyone who is interested in        booted from

Re: [openstack-dev] [nova] Rocky PTG summary - cells

I would also prefer not having to rely on reading all the cell DBs to calculate quotas. On Thu, Mar 15, 2018 at 3:29 AM, melanie witt wrote: > > > I would prefer not to block instance creations because of "down" cells, ​++ ​ > so maybe there is some possibility to

Re: [openstack-dev] [nova] Rocky PTG summary - cells

Thanks for the reply, both solution looks reasonable. On Thu, Mar 15, 2018 at 10:29 AM, melanie witt wrote: > On Thu, 15 Mar 2018 09:54:59 +0800, Zhenyu Zheng wrote: > >> Thanks for the recap, got one question for the "block creation": >> >> * An attempt to create an

[openstack-dev] [nova][libvirt] question on max cpu and memory

In order to work on [1] for prove libvirt is ok to do live-resize, I want to make following changes on xml file of instance to make maximum memory as 1G and current memory as 512M , and current CPU is a while maximum CPU is 2 so that we can hot resize through libvirt interface question I have is

Re: [openstack-dev] [nova] Rocky PTG summary - cells

On Thu, 15 Mar 2018 09:54:59 +0800, Zhenyu Zheng wrote: Thanks for the recap, got one question for the "block creation": * An attempt to create an instance should be blocked if the project has instances in a "down" cell (the instance_mappings table has a "project_id" column) because

Re: [openstack-dev] [nova] Rocky PTG summary - cells

Thanks for the recap, got one question for the "block creation": * An attempt to create an instance should be blocked if the project has > instances in a "down" cell (the instance_mappings table has a "project_id" > column) because we cannot count instances in "down" cells for the quota >

[openstack-dev] [nova] Rocky PTG summary - nova/cinder

Hello all, Here’s the PTG summary etherpad [0] for the nova/cinder session from the PTG, also included as a plain text export on this email. Cheers, -melanie [0] https://etherpad.openstack.org/p/nova-ptg-rocky-cinder-summary *Nova/Cinder: Rocky PTG Summary

Re: [openstack-dev] [nova] Rocky PTG summary - cells

On Wed, 14 Mar 2018, melanie witt wrote: I’ve created a summary etherpad [0] for the nova cells session from the PTG and included a plain text export of it on this email. Nice summary. Apparently I wasn't there or paying attention when something was decided: * An attempt to delete an

[openstack-dev] [nova] Rocky PTG summary - cells

Hi everyone, I’ve created a summary etherpad [0] for the nova cells session from the PTG and included a plain text export of it on this email. Thanks, -melanie [0] https://etherpad.openstack.org/p/nova-ptg-rocky-cells-summary *Cells: Rocky PTG Summary

Re: [openstack-dev] [nova][ThirdParty-CI] Nova s390x CI currently broken

A brief update: The root cause is that Neutron patch [1] broke Neutron DHCP and L3 agent on s390x (both use pyroute2 for network namespace management now). The issue needs to get fixed in pyroute2 itself. I opened a PR [2]. Ideally a new version gets released soon. [1]

Re: [openstack-dev] [nova] about rebuild instance booted from volume

On 14 March 2018 at 13:46, Matt Riedemann wrote: > On 3/14/2018 3:42 AM, 李杰 wrote: > >> >> This is the spec about rebuild a instance booted from >> volume.In the spec,there is a >>question about if we should delete the old root_volume.Anyone who >> is

Re: [openstack-dev] [nova] about rebuild instance booted from volume

Please do not default to deleting it, otherwise someone will eventually be back here asking why an irate user has just lost data. The better scenario is that the rebuild will fail (early - before impact to the running instance) with a quota error. Cheers, On Thu., 15 Mar. 2018, 00:46 Matt

Re: [openstack-dev] [nova] about rebuild instance booted from volume

penstack.org>, openstack-operators <openstack-operat...@lists.openstack.org> Subject: Re: [openstack-dev] [nova] about rebuild instance booted from volume On 3/14/2018 3:42 AM, 李杰 wrote: > > This is the spec about rebuild a instance booted from > volum

Re: [openstack-dev] [nova] about rebuild instance booted from volume

e questions)" <openstack-dev@lists.openstack.org> Date: Wednesday, 14 March 2018 at 14:55 To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org>, openstack-operators <openstack-operat...@lists.openstack.org> Subject: Re: [openstack-dev] [nov

Re: [openstack-dev] [nova] about rebuild instance booted from volume

On 3/14/2018 3:42 AM, 李杰 wrote:             This is the spec about  rebuild a instance booted from volume.In the spec,there is a       question about if we should delete the old root_volume.Anyone who is interested in       booted from volume can help to review this. Any suggestion is

Re: [openstack-dev] [nova] [placement] placement update 18-10

On Mon, 12 Mar 2018, Tetsuro Nakamura wrote: # Questions What's the status of shared resource providers? Did we even talk about that in Dublin? In terms of bug fixes related to allocation candidates, I'll try to answer that question :) Thanks very much for doing this. *

[openstack-dev] [nova] about rebuild instance booted from volume

Hi,all This is the spec about rebuild a instance booted from volume.In the spec,there is a question about if we should delete the old root_volume.Anyone who is interested in booted from volume can help to review this. Any suggestion is welcome.Thank you! The

[openstack-dev] [nova] about rebuild instance booted from volume

Hi,all This is the spec about backup a instance booted from volume, anyone who is interested in booted from volume can help to review this. Any suggestion is welcome. The link is here. Re:the backup spec:https://review.openstack.org/#/c/530214/ Best

[openstack-dev] [nova] Rocky PTG summary - Queens retrospective

Howdy Stackers, I’ve created a summary etherpad [0] of the Queens retrospective session from the PTG and included a plain text export of it on this email. Thank you to all who participated and please do add comments to the etherpad where I might have missed a perspective or interpretation in

[openstack-dev] [nova][ThirdParty-CI] Nova s390x CI currently broken

Hello, the s390x CI for nova is currently broken again. The reason seems to be a recent change that merged in neutron. I’m looking into it... --- Andreas Scheuring (andreas_s) __ OpenStack Development Mailing List (not

Re: [openstack-dev] [nova][notification] Full traceback in ExceptionPayload

On 3/13/2018 7:37 AM, Balázs Gibizer wrote: I filed the bp https://blueprints.launchpad.net/nova/+spec/add-full-traceback-to-error-notifications I added it to the weekly meeting agenda. I know you likely won't attend the meeting this week, but I can probably be your proxy on this one. --

Re: [openstack-dev] [nova][notification] Full traceback in ExceptionPayload

On Fri, Mar 9, 2018 at 5:08 PM, Balázs Gibizer wrote: On Fri, Mar 9, 2018 at 3:46 PM, Matt Riedemann wrote: On 3/9/2018 6:26 AM, Balázs Gibizer wrote: The instance-action REST API has already provide the traceback to the user (to the

[openstack-dev] [nova] Notification update week 11

Hi, Here is the status update / focus settings mail for w11. Bugs No new bug and no changes in the existing bugs from last week report http://lists.openstack.org/pipermail/openstack-dev/2018-March/127992.html Versioned notification transformation -

Re: [openstack-dev] [nova] [placement] placement update 18-10

# Questions > What's the status of shared resource providers? Did we even talk > about that in Dublin? In terms of bug fixes related to allocation candidates, I'll try to answer that question :) Most of the bugs that have been reported in https://bugs.launchpad.net/nova/+bug/1731072 are sorted

Re: [openstack-dev] [nova][notification] Full traceback in ExceptionPayload

On Fri, Mar 9, 2018 at 3:46 PM, Matt Riedemann wrote: On 3/9/2018 6:26 AM, Balázs Gibizer wrote: The instance-action REST API has already provide the traceback to the user (to the admin by default) and the notifications are also admin only things as they are emitted

Re: [openstack-dev] [nova][notification] Full traceback in ExceptionPayload

On 3/9/2018 6:26 AM, Balázs Gibizer wrote: The instance-action REST API has already provide the traceback to the user (to the admin by default) and the notifications are also admin only things as they are emitted to the message bus by default. So I assume that security is not a bigger concern

[openstack-dev] [nova] [placement] placement update 18-10

Welcome back to your regularly scheduled placement update. I'm still gathering loose ends from the PTG, so plenty of this will be context setting, but I'll try to provide the usual too many links. As mentioned in the last update I'm going to adjust these reports a bit to make them a bit more

[openstack-dev] [nova][notification] Full traceback in ExceptionPayload

Hi, On the PTG a question was raised that why don't we have the full traceback in the versioned error notifications as the legacy notifications has the full traceback. I dig into the past and found out that this difference was intentional. During the original versioned notification spec

Re: [openstack-dev] [nova][placement] PTG Summary and Rocky Priorities

- Multiple agreements about strict minimum bandwidth support feature in nova - Spec has already been updated accordingly: https://review.openstack.org/#/c/502306/ - For now we keep the hostname as the information connecting the nova-compute and the neutron-agent on the same host

Re: [openstack-dev] [nova][placement] PTG Summary and Rocky Priorities

On 3/8/2018 6:51 AM, Jay Pipes wrote: -  VGPU_DISPLAY_HEAD resource class should be removed and replaced with a set of os-traits traits that indicate the maximum supported number of display heads for the vGPU type How does a trait express a quantifiable limit? Would we end up have several

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

PM >> *To:* OpenStack Development Mailing List (not for usage >> questions) <openstack-dev@lists.openstack.org >> <mailto:openstack-dev@lists.openstack.org>> >> *Subject:* Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple >> functions

[openstack-dev] [nova][placement] PTG Summary and Rocky Priorities

We had a productive PTG and were able to discuss a great many scheduler-related topics. I've put together an etherpad [0] with a summary, reproduced below. Expect follow-up emails about each priority item in the scheduler track from those contributors working on that area. Best, -jay

[openstack-dev] [nova] [placement] Notes on eventually extracting placement

At the PTG we decided that while it was unlikely we could manage extracting Placement to its own project during Rocky, it would be useful to make incremental progress in that direction so the ground is prepared for when we do get around to it. This means making sure there are clear boundaries

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

penstack.org>> *Subject:* Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions __ __ On 2 March 2018 at 14:31, Jay Pipes <jaypi...@gmail.com <mailto:jaypi...@gmail.com>> wrote: On 03/02/2018 02:00 PM, Nadath

[openstack-dev] [nova] Notification update week 10 (PTG)

Hi, Here is the status update / focus settings mail for w10. We discussed couple of new notification related changes during the PTG. I tried to mention all of them below but if I missed something then please extend my list. Bugs [High] https://bugs.launchpad.net/nova/+bug/1737201

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

M >> *To:* OpenStack Development Mailing List (not for usage questions) < >> openstack-dev@lists.openstack.org> >> *Subject:* Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple >> functions >> >> >> >> On 2 March 2018 at 14:31,

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

ts.openstack.org> > *Subject:* Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions > > > > On 2 March 2018 at 14:31, Jay Pipes <jaypi...@gmail.com> wrote: > > On 03/02/2018 02:00 PM, Nadathur, Sundar wrote: > > Hello Nova team, > > During

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

From: Matthew Booth [mailto:mbo...@redhat.com] Sent: Saturday, March 3, 2018 4:15 PM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions On 2 March 2018 at 14:31, Jay

Re: [openstack-dev] [nova][neutron][openstackclient] The way to assign floating IPs to VM

On Mon, Mar 5, 2018 at 10:56 AM, Andrey Kurilin wrote: > Dean, I propose a patch (https://review.openstack.org/549820) which should > work for all environments where neutron is installed. Please check it when > you have free time. Thank you Andrey. Monty started one

Re: [openstack-dev] [nova][neutron][openstackclient] The way to assign floating IPs to VM

Matt, thanks! Unfortunately, I missed your thread. Dean, I propose a patch (https://review.openstack.org/549820) which should work for all environments where neutron is installed. Please check it when you have free time. 2018-03-05 17:17 GMT+02:00 Dean Troyer : > On Mon, Mar

Re: [openstack-dev] [nova][neutron][openstackclient] The way to assign floating IPs to VM

On Mon, Mar 5, 2018 at 8:07 AM, Matt Riedemann wrote: > On 3/5/2018 6:26 AM, Andrey Kurilin wrote: >> - openstackclient >> >> * command `openstack server add floating ip` calls `add_floating_ip` >> method of novaclient's server object[4]. This method is missed in the latest

Re: [openstack-dev] [nova][thirdparty-ci] s390x third party CI broken

CI seems to be running again, but with a reduced number of tests for now (only nova.api, excluded scenario tests). Will continue working on getting all tests executing again. --- Andreas Scheuring (andreas_s) On 5. Mar 2018, at 09:35, Andreas Scheuring wrote:

Re: [openstack-dev] [nova][neutron][openstackclient] The way to assign floating IPs to VM

On 3/5/2018 6:26 AM, Andrey Kurilin wrote: A year ago, Nova team decided to deprecate the addFixedIP, removeFixedIP, addFloatingIP, removeFloatingIP server action APIs and it was done[1]. It looks like not all the consumers paid attention to this change so after novaclient 10.0.0 release

[openstack-dev] [nova][neutron][openstackclient] The way to assign floating IPs to VM

Hi stackers! A year ago, Nova team decided to deprecate the addFixedIP, removeFixedIP, addFloatingIP, removeFloatingIP server action APIs and it was done[1]. It looks like not all the consumers paid attention to this change so after novaclient 10.0.0 release (which includes removal of these

[openstack-dev] [nova][thirdparty-ci] s390x third party CI broken

Hi all, the s390x nova CI is currently broken due to the bump of the grpcio version. I’m working on fixing it…. Regards, --- Andreas Scheuring (andreas_s) __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [nova] vendordata plugin for freeIPA host enrollment

I was thinking about this the other day... How do you de-register instances from freeipa when the instance is deleted? Is there a missing feature in vendordata there that you need? Michael On Fri, Nov 11, 2016 at 2:01 AM, Rob Crittenden wrote: > Wanted to let you know I'm

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

On 2 March 2018 at 14:31, Jay Pipes wrote: > On 03/02/2018 02:00 PM, Nadathur, Sundar wrote: > >> Hello Nova team, >> >> During the Cyborg discussion at Rocky PTG, we proposed a flow for >> FPGAs wherein the request spec asks for a device type as a resource class, >> and

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

On 03/02/2018 02:00 PM, Nadathur, Sundar wrote: Hello Nova team,     During the Cyborg discussion at Rocky PTG, we proposed a flow for FPGAs wherein the request spec asks for a device type as a resource class, and optionally a function (such as encryption) in the extra specs. This does not

[openstack-dev] [Nova] [Cyborg] Tracking multiple functions

Hello Nova team, During the Cyborg discussion at Rocky PTG, we proposed a flow for FPGAs wherein the request spec asks for a device type as a resource class, and optionally a function (such as encryption) in the extra specs. This does not seem to work well for the usage model that I'll

[openstack-dev] [nova][ptg] nova/neutron and nova/ironic cross-project sessions today

Hi everyone, Just wanted to send a fresh email that we’re having the nova/neutron and nova/ironic cross-project sessions going on today at the Croke Park Hotel. Nova/neutron is in-progress now at the breakfast area of the restaurant and nova/ironic will start at 4:00 PM, probably also in the

Re: [openstack-dev] [nova][ptg] room change after lunch to the lunch room (Hogan Suite)

> On Mar 1, 2018, at 11:24, melanie witt wrote: > > Because it’s uncomfortably cold in Davin Suite, I’ve booked Hogan Suite (the > lunch room) for us to use after lunch for the rest of today. > > So please be sure to go to Hogan Suite this afternoon for the Nova/Ironic and

Re: [openstack-dev] [nova][ptg] room change after lunch to the lunch room (Hogan Suite)

On Mar 1, 2018, at 11:24, melanie witt wrote: Because it’s uncomfortably cold in Davin Suite, I’ve booked Hogan Suite (the lunch room) for us to use after lunch for the rest of today. So please be sure to go to Hogan Suite this afternoon for the Nova/Ironic and Nova/Neutron

[openstack-dev] [nova][ptg] room change after lunch to the lunch room (Hogan Suite)

Hey everyone, Because it’s uncomfortably cold in Davin Suite, I’ve booked Hogan Suite (the lunch room) for us to use after lunch for the rest of today. So please be sure to go to Hogan Suite this afternoon for the Nova/Ironic and Nova/Neutron sessions. Cheers, -melanie

Re: [openstack-dev] [nova][ptg] reminder: cyborg nova-interaction discussion at 2pm this afternoon

THX Melanie ! :) On Tue, Feb 27, 2018 at 10:34 AM, melanie witt wrote: > Howdy everyone, > > This is just a reminder that we have some time scheduled to chat with the > Cyborg team at 2pm this afternoon at the Cyborg room (Suite 665). > > From our PTG etherpad agenda[1] : >

Re: [openstack-dev] [nova][ptg] team photo Thursday at 11:10 AM

On 2/27/2018 10:43 AM, melanie witt wrote: It will be really cold outside, so be prepared for that. If you live in California, sure... -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [nova][ptg] team photo Thursday at 11:10 AM

Hey everyone, We have time scheduled on Thursday morning 11:10-11:20 AM for a team photo at the PTG. For those in the Nova room (Davin Suite), we’ll walk together to the registration area before 11:10 AM to meet before we’ll be escorted down to the pitch (sports field) to take the photo. If

[openstack-dev] [nova][ptg] reminder: cyborg nova-interaction discussion at 2pm this afternoon

Howdy everyone, This is just a reminder that we have some time scheduled to chat with the Cyborg team at 2pm this afternoon at the Cyborg room (Suite 665). From our PTG etherpad agenda[1] : "Cyborg (previously known as Nomad) is an OpenStack project that aims to provide a general purpose

Re: [openstack-dev] [nova] [placement] resource providers update 18-07

On 02/24/2018 02:17 AM, Matt Riedemann wrote: On 2/16/2018 7:54 AM, Chris Dent wrote: Before I get to the meat of this week's report, I'd like to request some feedback from readers on how to improve the report. Over its lifetime it has grown and it has now reached the point that while it tries

Re: [openstack-dev] [nova] [placement] resource providers update 18-07

On 2/16/2018 7:54 AM, Chris Dent wrote: Before I get to the meat of this week's report, I'd like to request some feedback from readers on how to improve the report. Over its lifetime it has grown and it has now reached the point that while it tries to give the impression of being complete, it

[openstack-dev] [nova] nova 17.0.0.0rc3 (queens)

Hello everyone, A new release candidate for nova for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/nova/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

Re: [openstack-dev] [nova] Adding Takashi Natsume to python-novaclient core

Hi Takashi, As you know, nova-core and python-novaclient-core memberships are evaluated separately (they are different teams with some overlap in membership). While your contributions to Nova are absolutely appreciated and recognized, there is a different group that votes on nova-core membership

Re: [openstack-dev] [nova] Contrail VIF TAP plugging broken

Thanks a lot Matt, Jay and Dan for your reactivity and your time. Édouard. On Wed, Feb 21, 2018 at 9:50 PM, Matt Riedemann wrote: > On 2/21/2018 4:30 AM, Édouard Thuleau wrote: > >> Hi Seán, Michael, >> >> Since patch [1] moved Contrail VIF plugging under privsep, Nova

Re: [openstack-dev] [nova] Contrail VIF TAP plugging broken

On 2/21/2018 4:30 AM, Édouard Thuleau wrote: Hi Seán, Michael, Since patch [1] moved Contrail VIF plugging under privsep, Nova fails to plug TAP on the Contrail software switch (named vrouter) [2]. I proposed a fix in the beginning of the year [3] but it still pending approval even it got a

[openstack-dev] [nova] queens retrospective etherpad

Greetings Stackers, FYI we also have a retrospective etherpad [1] for Queens which we’ll cover at the PTG on Wednesday at 9:00 - 10:00 AM. Please add your thoughts to the etherpad on what you think went well in Queens and what you think could use some improvement going forward into the Rocky

[openstack-dev] [nova] Contrail VIF TAP plugging broken

Hi Seán, Michael, Since patch [1] moved Contrail VIF plugging under privsep, Nova fails to plug TAP on the Contrail software switch (named vrouter) [2]. I proposed a fix in the beginning of the year [3] but it still pending approval even it got a couple of +1 and no negative feedback. It's why

[openstack-dev] [nova] review priorities etherpad for rocky

Howdy Stackers, I’ve set up the review priorities etherpad [1] for us to use during the Rocky cycle. It’s the same format we had back in Pike with the exception of a couple of new sections I’ve added: "Non-priority approved blueprints” and "Co-authors wanted”. The idea of the etherpad is to

Re: [openstack-dev] [nova] Adding Takashi Natsume to python-novaclient core

Thank you, Matt and everyone. But I would like to become a core reviewer for the nova project as well as python-novaclient. I have contributed more in the nova project than python-novaclient. I have done total 2,700+ reviews for the nova project in all releases (*1). (Total 115 reviews only

Re: [openstack-dev] [nova] signing up as a bug tag owner

On Sat, Feb 17, 2018 at 7:40 AM, melanie witt wrote: >> On Feb 16, 2018, at 06:11, Balázs Gibizer >> wrote: >> >> Hi, >> >> On the weekly meeting melwitt suggested [1] to have people signed up for >> certain bug tags. I've already been trying to

Re: [openstack-dev] [nova] signing up as a bug tag owner

> On Feb 16, 2018, at 06:11, Balázs Gibizer wrote: > > Hi, > > On the weekly meeting melwitt suggested [1] to have people signed up for > certain bug tags. I've already been trying to follow the bugs tagged with the > 'notifications' tag so I sign up for this tag.

[openstack-dev] [nova] signing up as a bug tag owner

Hi, On the weekly meeting melwitt suggested [1] to have people signed up for certain bug tags. I've already been trying to follow the bugs tagged with the 'notifications' tag so I sign up for this tag. Cheers, gibi

[openstack-dev] [nova] [placement] resource providers update 18-07

Resource provider update 18-07. This will be the last one before the PTG and there won't be one during the PTG, so the next one will be 18-10 or later. Before I get to the meat of this week's report, I'd like to request some feedback from readers on how to improve the report. Over its lifetime

[openstack-dev] [nova] nova 17.0.0.0rc2 (queens)

Hello everyone, A new release candidate for nova for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/nova/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

Re: [openstack-dev] [nova] Adding Takashi Natsume to python-novaclient core

\o/ Welcome to the team! 2018-02-15 19:18 GMT+02:00 Matt Riedemann : > On 2/9/2018 9:01 AM, Matt Riedemann wrote: > >> I'd like to add Takashi to the python-novaclient core team. >> >> python-novaclient doesn't get a ton of activity or review, but Takashi >> has been a

Re: [openstack-dev] [nova] Adding Takashi Natsume to python-novaclient core

On 2/9/2018 9:01 AM, Matt Riedemann wrote: I'd like to add Takashi to the python-novaclient core team. python-novaclient doesn't get a ton of activity or review, but Takashi has been a solid reviewer and contributor to that project for quite awhile now:

Re: [openstack-dev] [nova] Adding Takashi Natsume to python-novaclient core

+1 Takashi, thanks for your contribution! 2018-02-11 4:48 GMT+02:00 Alex Xu : > +1 > > 2018-02-09 23:01 GMT+08:00 Matt Riedemann : > >> I'd like to add Takashi to the python-novaclient core team. >> >> python-novaclient doesn't get a ton of activity or

Re: [openstack-dev] [nova] Rocky PTG early planning

> On Jan 8, 2018, at 10:33, Matt Riedemann wrote: > > As the Queens release winds to a close, I've started thinking about topics > for Rocky that can be discussed at the PTG. > > I've created an etherpad [1] for just throwing various topics in there, > completely

Re: [openstack-dev] [nova][neutron][infra] zuul job definitions overrides and the irrelevant-file attribute

On Thu, Feb 15, 2018 at 1:43 AM, Andrea Frittoli wrote: > > > On Wed, Feb 14, 2018 at 4:05 PM James E. Blair wrote: >> >> Andrea Frittoli writes: >> >> >> That has no irrelevant-files matches, and so matches everything.

[openstack-dev] [nova] Queens blueprint burndown chart

I sent a similar email after Pike was released [1] and these are our blueprint burndown chart results for Queens [2]. Comparing to Pike, the trends are similar, with the overall numbers down. Things ramp up until the spec freeze, then tail off, with a little spike toward the end to get things

Re: [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

On 2/5/2018 9:00 PM, Matt Riedemann wrote: Given the size and detail of this thread, I've tried to summarize the problems and possible solutions/workarounds in this etherpad: https://etherpad.openstack.org/p/nova-aggregate-filter-allocation-ratio-snafu For those working on this, please

Re: [openstack-dev] [nova][neutron][infra] zuul job definitions overrides and the irrelevant-file attribute

On Wed, Feb 14, 2018 at 4:05 PM James E. Blair wrote: > Andrea Frittoli writes: > > >> That has no irrelevant-files matches, and so matches everything. If you > >> drop the use of that template, it will work as expected. Or, if you can > >> say

Re: [openstack-dev] [nova][neutron][infra] zuul job definitions overrides and the irrelevant-file attribute

Andrea Frittoli writes: >> That has no irrelevant-files matches, and so matches everything. If you >> drop the use of that template, it will work as expected. Or, if you can >> say with some certainty that nova's irrelevant-files set is not >> over-broad, you could

Re: [openstack-dev] [nova][neutron][infra] zuul job definitions overrides and the irrelevant-file attribute

On Fri, Jan 26, 2018 at 5:57 PM James E. Blair wrote: > Balázs Gibizer writes: > > > Hi, > > > > I'm getting more and more confused how the zuul job hierarchy works or > > is supposed to work. > > Hi! > > First, you (or others) may or may not

Re: [openstack-dev] [nova][neutron][infra] zuul job definitions overrides and the irrelevant-file attribute

On Fri, Jan 26, 2018 at 2:05 PM Balázs Gibizer wrote: > Hi, > > I'm getting more and more confused how the zuul job hierarchy works or is > supposed to work. > > First there was a bug in nova that some functional tests are not triggered > although the job

Re: [openstack-dev] [nova][cyborg]Dublin PTG Cyborg Nova Interaction Discussion

@melanie yes Cyborg has its meeting room I think :) Room details should be fixed this week or early next week I suppose. So it will be 2:00pm on Tuesday, first thing of buisness after lunch :) On Wed, Feb 14, 2018 at 7:20 AM, melanie witt wrote: > > On Feb 12, 2018, at

Re: [openstack-dev] [nova][neutron][infra] zuul job definitions overrides and the irrelevant-file attribute

On Sat, Jan 27, 2018 at 2:57 AM, James E. Blair wrote: > Balázs Gibizer writes: > >> Hi, >> >> I'm getting more and more confused how the zuul job hierarchy works or >> is supposed to work. > > Hi! > > First, you (or others) may or may not have

Re: [openstack-dev] [nova][cyborg]Dublin PTG Cyborg Nova Interaction Discussion

+1, I'm interested also. 2018-02-12 23:27 GMT+08:00 Eric Fried : > I'm interested. No date/time preference so far as long as it sticks to > Monday/Tuesday. > > efried > > On 02/12/2018 09:13 AM, Zhipeng Huang wrote: > > Hi Nova team, > > > > Cyborg will have ptg sessions on

Re: [openstack-dev] [nova][cyborg]Dublin PTG Cyborg Nova Interaction Discussion

> On Feb 12, 2018, at 16:06, Zhipeng Huang wrote: > > Let's settle on Tuesday afternoon session then, thanks a lot :) Do we have a proposed time and place for the session already? I checked the cyborg etherpad [1] and it looks like we’re thinking 2:00pm on Tuesday. Do we

Re: [openstack-dev] [nova] Notification update week 7

On Mon, Feb 12, 2018 at 8:47 PM, Matt Riedemann wrote: On 2/12/2018 11:11 AM, Balázs Gibizer wrote: Add the user id and project id of the user initiated the instance action to the notification - The bp

Re: [openstack-dev] [nova] github.com/openstack/nova-specs mirror temporarily broken

> On Feb 12, 2018, at 16:26, melanie witt wrote: > > Hey Stackers, > > This is just a heads up that the github mirror of the nova-specs repo has > been temporarily broken for the past few months and doesn’t have the > specs/rocky/ directory in it. Fixing it is on the TODO

[openstack-dev] [nova] github.com/openstack/nova-specs mirror temporarily broken

Hey Stackers, This is just a heads up that the github mirror of the nova-specs repo has been temporarily broken for the past few months and doesn’t have the specs/rocky/ directory in it. Fixing it is on the TODO list for the next scheduled maintenance window, but until then, please git clone

Re: [openstack-dev] [nova][cyborg]Dublin PTG Cyborg Nova Interaction Discussion

Let's settle on Tuesday afternoon session then, thanks a lot :) On Tue, Feb 13, 2018 at 1:43 AM, Ed Leafe wrote: > On Feb 12, 2018, at 9:57 AM, Chris Dent wrote: > > > > Tuesday would be best for me as Monday is api-sig day. > > Same, for the same

Re: [openstack-dev] [nova] Notification update week 7

On 2/12/2018 11:11 AM, Balázs Gibizer wrote: Add the user id and project id of the user initiated the instance action to the notification - The bp

Re: [openstack-dev] [nova][cyborg]Dublin PTG Cyborg Nova Interaction Discussion

On Feb 12, 2018, at 9:57 AM, Chris Dent wrote: > > Tuesday would be best for me as Monday is api-sig day. Same, for the same reason. -- Ed Leafe __ OpenStack Development Mailing List (not for

[openstack-dev] [nova] Notification update week 7

Hi, Here is the status update / focus settings mail for w7. Bugs No new bugs. No change from last week's bug status. Versioned notification transformation - The rocky bp has been created

<    6   7   8   9   10   11   12   13   14   15   >