[openstack-dev] [openstack][nova][specs] Where to store images used in the spec

Hi, I've just uploaded a new BP proposal to gerrit https://review.openstack.org/#/c/87978, but the gate failed as I included an image along with the .rst file in my patch. What is the good place to store the images that are used in the specs? Cheers, Gibi

Re: [openstack-dev] [Nova] Automatic evacuate

Hi, Sorry for the top posting but it was hard to fit my complete view inline. I'm also thinking about a possible solution for automatic server evacuation. I see two separate sub problems of this problem: 1)compute node monitoring and fencing, 2)automatic server evacuation Compute node

Re: [openstack-dev] [Nova] Automatic evacuate

-Original Message- From: Russell Bryant [mailto:rbry...@redhat.com] Sent: October 21, 2014 15:07 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova] Automatic evacuate On 10/21/2014 06:44 AM, Balázs Gibizer wrote: Hi, Sorry for the top posting

[openstack-dev] [nova] Host maintenance notification

Hi, I have the following scenario. I have an application consisting of multiple VMs on different compute hosts. The admin puts one of the hosts into maintenance mode (nova-manage service disable ...) because there will be some maintenance activity on that host in the near future. Is there a

Re: [openstack-dev] [nova] [searchlight] Difference in nova notifications versus API

Hi, There is a spec up [3] in nova to version notifications and also there will be a half session [4] tomorrow aftrenoon on the nova track to discuss it. Cheers, Gibi [3] https://review.openstack.org/#/c/224755/ [4]

[openstack-dev] [Nova] notification subteam meeting

Hi, The first meeting of the nova notification subteam will happen 2015-11-10 Tuesday 20:00 UTC [1] on #openstack-meeting-alt on freenode Agenda: - Agree on the mission and the tasks of the team - Status of the outstanding specs - Q/A - AOB See you there. Cheers, Gibi [1]

[openstack-dev] [Nova] notification subteam meeting

Hi, The next meeting of the nova notification subteam will happen 2015-11-17 Tuesday 20:00 UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - AOB See you there. Cheers, Gibi [1]

Re: [openstack-dev] [Nova] notification subteam

> From: Michael Davies [mailto:mich...@the-davies.net] > Sent: November 04, 2015 00:36 > > On Wed, Nov 4, 2015 at 8:49 AM, Michael Still wrote: > > > I'd be interested in being involved with this, and I know Paul > Murray is interested as well. > > I went to

[openstack-dev] [Nova] notification subteam

Hi, We discussed in the summit that nova notification API needs some care. It was suggested that forming a subteam around notifications might help coordinate and track the effort. So I have created a wikipage [1] and I added a section in the Mitaka tracking etherpad [2] for the subteam. We

Re: [openstack-dev] [Nova] notification subteam meeting

Hi, The next meeting of the nova notification subteam will happen 2015-12-08 Tuesday 20:00 UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - AOB See you there. Cheers, Gibi [1]

Re: [openstack-dev] [Nova] notification subteam meeting

Hi, The next meeting of the nova notification subteam will happen 2015-12-15 Tuesday 20:00 UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - Subteam meeting during the vacation period - AOB See you there. Cheers, Gibi [1]

[openstack-dev] [Nova] notification subteam meeting

Hi, The next meeting of the nova notification subteam will happen 2016-01-05 Tuesday 20:00 UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - AOB See you there. Cheers, Gibi [1]

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

> From: John Garbutt [mailto:j...@johngarbutt.com] > Sent: November 24, 2015 16:09 > On 24 November 2015 at 15:00, Balázs Gibizer <balazs.gibi...@ericsson.com> > wrote: > >> From: Andrew Laski [mailto:and...@lascii.com] > >> Sent: November 24, 2015 15:35 > &g

Re: [openstack-dev] [Nova] notification subteam meeting

Hi, The next meeting of the nova notification subteam will happen 2015-12-01 Tuesday 20:00 UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - Mid-cycle - AOB See you there. Cheers, Gibi [1]

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

> -Original Message- > From: Andrew Laski [mailto:and...@lascii.com] > Sent: November 30, 2015 20:32 > On 11/30/15 at 07:32am, Sean Dague wrote: > >On 11/24/2015 10:09 AM, John Garbutt wrote: > >> On 24 November 2015 at 15:00, Balázs Gibizer > >>

Re: [openstack-dev] how do we get the migration status details info from nova

> -Original Message- > From: Paul Carlton [mailto:paul.carlt...@hpe.com] > Sent: November 26, 2015 12:11 > On 26/11/15 10:48, 少合冯 wrote: > > > Now, we are agree on getting more migration status details > info are useful. > > But How do we get them? > By REST API or

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

> From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: November 19, 2015 23:29 > On 11/19/2015 4:05 PM, Ryan Rossiter wrote: > > Reading through [1] I started getting worries in the back of my head > > about versioning these notifications. The main concern being how can > > the

Re: [openstack-dev] [Nova] notification subteam meeting

Hi, The next meeting of the nova notification subteam will happen 2015-11-24 Tuesday 20:00 UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - Mid-cycle - AOB See you there. Cheers, Gibi [1]

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

> From: Ryan Rossiter [mailto:rlros...@linux.vnet.ibm.com] > Sent: November 23, 2015 15:54 > On 11/23/2015 5:33 AM, John Garbutt wrote: > > On 20 November 2015 at 09:37, Balázs Gibizer > > <balazs.gibi...@ericsson.com> wrote: > >> > >> Min

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

> From: Andrew Laski [mailto:and...@lascii.com] > Sent: November 23, 2015 17:03 > > On 11/23/15 at 08:54am, Ryan Rossiter wrote: > > > > > >On 11/23/2015 5:33 AM, John Garbutt wrote: > >>On 20 November 2015 at 09:37, Balázs Gibizer > >><balazs.gi

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

> From: Ryan Rossiter [mailto:rlros...@linux.vnet.ibm.com] > Sent: November 23, 2015 22:33 > On 11/23/2015 2:23 PM, Andrew Laski wrote: > > On 11/23/15 at 04:43pm, Balázs Gibizer wrote: > >>> From: Andrew Laski [mailto:and...@lascii.com] > >>> Sent: November

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

> From: Andrew Laski [mailto:and...@lascii.com] > Sent: November 24, 2015 15:35 > On 11/24/15 at 10:26am, Balázs Gibizer wrote: > >> From: Ryan Rossiter [mailto:rlros...@linux.vnet.ibm.com] > >> Sent: November 23, 2015 22:33 > >> On 11/23/2015 2:23 PM, Andrew L

Re: [openstack-dev] [Nova] notification subteam meeting

Hi, The next meeting of the nova notification subteam will happen 2016-01-12 Tuesday 20:00 UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - AOB See you there. Cheers, Gibi [1]

[openstack-dev] [nova][notification] transformation TODO list

Hi, If you want to help nova to transform its notification interface to an API then you can find your new TODO list on the wiki [1]. You can find the basic how-to information and the list of work items there. If you have any questions just ping me (gibi) on IRC or join the weekly notification

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.06.07 17:00 UTC [1] on #openstack-meeting-4. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160607T17 __ OpenStack

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.06.14 17:00 UTC [1] on #openstack-meeting-4. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160614T17 __ OpenStack

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.05.31 17:00 UTC [1] on #openstack-meeting-4. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160531T17 __ OpenStack

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.06.21 17:00 UTC [1] on #openstack-meeting-4. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160621T17 __ OpenStack

Re: [openstack-dev] [Nova] notification subteam meeting

Hi, The next meeting of the nova notification subteam will happen 2016-01-19 Tuesday 20:00 UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - Agree on the new (reduced) frequency of the meeting - AOB See you there. Cheers, Gibi [1]

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.06.28 17:00 UTC [1] on #openstack-meeting-4. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160628T17 __ OpenStack

[openstack-dev] [nova] How to enforce that no new legacy notification is added

Hi, Background: Versioned notification infra [1] is merged and on the midcycle we agreed that we don't allow new legacy notification [2]. I promised to create some automated way to detect if a new legacy notification is proposed in a review. I implemented [3] a monkey patch in the test that

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

> -Original Message- > From: Cheng, Yingxin [mailto:yingxin.ch...@intel.com] > Sent: January 28, 2016 04:21 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [nova] Better tests for nova scheduler(esp. > race conditions)? > > Thank you

Re: [openstack-dev] [Nova] notification subteam meeting

Hi, The next meeting of the nova notification subteam will happen 2016-02-02 Tuesday _17:00_ UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - AOB See you there. Cheers, Gibi [1]

Re: [openstack-dev] [Nova] notification subteam meeting

> -Original Message- > From: Balázs Gibizer [mailto:balazs.gibi...@ericsson.com] > Sent: February 01, 2016 12:57 > To: 'OpenStack Development Mailing List (not for usage questions)' > Subject: Re: [openstack-dev] [Nova] notification subteam meeting > > Hi,

Re: [openstack-dev] [Nova] notification subteam meeting

> From: Balázs Gibizer > Sent: February 01, 2016 13:05 > > > -Original Message- > > From: Balázs Gibizer [mailto:balazs.gibi...@ericsson.com] > > Sent: February 01, 2016 12:57 > > To: 'OpenStack Development Mailing List (not for usage questions)' >

Re: [openstack-dev] [nova] Nova Midcycle Summary (i.e. mid mitaka progress report)

> From: John Garbutt [mailto:j...@johngarbutt.com] > Sent: February 02, 2016 12:08 > > Hi, > > For all the details see this etherpad: > https://etherpad.openstack.org/p/mitaka-nova-midcycle > > Here I am attempting a brief summary, picking out some highlights. > Feel free to reply and add your

Re: [openstack-dev] [Nova] notification subteam meeting

no participants from that part of the world. If you are located in the affected areas and wants to join our meeting in the future please raise your voice. If there is no objection then I will reschedule the meeting next week according to the proposal. Cheers, Gibi > From: Balázs Gibizer > Sent: J

Re: [openstack-dev] [Nova] notification subteam meeting

Hi, The next meeting of the nova notification subteam will happen 2016-02-16 Tuesday _17:00_ UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - AOB See you there. Cheers, Gibi [1]

[openstack-dev] [neutron][tempest] When to put a test into the smoke suite?

Hi, I tried to find the rules defining which test qualifies to be in the smoke suite of tempest. Is there such a clear definition somewhere? Cheers, Gibi __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Nova] RFC Host Maintenance

> -Original Message- > From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com] > Sent: April 07, 2016 15:42 > > The only gap based on my limited understanding is that nova is not emitting > events compute host state changes. This knowledge is still kept inside nova > as some service states.

Re: [openstack-dev] [Nova] RFC Host Maintenance

gt; > To: OpenStack Development Mailing List (not for usage questions) > > <openstack-dev@lists.openstack.org> > > Subject: Re: [openstack-dev] [Nova] RFC Host Maintenance > > > > On Fri, Apr 08, 2016 at 09:52:31AM +, Balázs Gibizer wrote: > > > > -

[openstack-dev] [nova] Versioned notification work continues in Newton

Hi, I just want to let the community know that the versioned notification work we started in Mitaka is planned to be continued in Newton. The planned goals for Newton: * Transform the most important notification to the new format [1] * Help others to use the new framework adding new

Re: [openstack-dev] [Nova] notification subteam meeting

Hi, The next short meeting of the nova notification subteam will happen 2016-03-01 Tuesday _17:00_ UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - AOB See you there. Cheers, Gibi [1]

Re: [openstack-dev] [telemetry] Newton design summit planning

> -Original Message- > From: Chris Dent [mailto:cdent...@anticdent.org] > Sent: April 05, 2016 12:13 > > On Tue, 5 Apr 2016, Julien Danjou wrote: > > > Any items/ideas we could discussion in this remaining sessions? > > Any project we could/should invite to discuss with us? > > Nova has

[openstack-dev] [Nova] Nova notification subteam meeting is cancelled

Hi, We temporary cancel the nova notification subteam meeting due to low participation and low amount of thing to discuss. We will resurrect it after the summit. The way forward with the notification transformation is under review [1] so we can discuss the issues there or you can ping me

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.05.24 17:00 UTC [1] on #openstack-meeting-4. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160524T17 __ OpenStack

[openstack-dev] [nova] notification subteam meeting

Hi, The next notification subteam meeting will be held in 2016-05-17 Tuesday 17:00 UTC on #openstack-meeting-4. See you there! Cheers, Gibi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [nova] Austin summit versioned notification

Hi, Last week Friday in Austin we discussed the way forward with the versioned notification transformation in Nova. We agreed that when we separate the object model use for notifications from the nova object model we still use the NovaObject as a base class to avoid change in the wire format

Re: [openstack-dev] [nova] Austin summit versioned notification

> -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: May 03, 2016 15:58 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [nova] Austin summit versioned notification > > On 5/3/2016 3:10 AM, Balázs Gibizer wrote:

Re: [openstack-dev] [nova] Austin summit versioned notification

On May 3, 2016, at 8:58 AM, Matt Riedemann > <mrie...@linux.vnet.ibm.com> wrote: > > > > On 5/3/2016 3:10 AM, Balázs Gibizer wrote: > >> Hi, > >> > >> Last week Friday in Austin we discussed the way forward with the > versioned > >> notifica

[openstack-dev] [nova] notification subteam meeting is cancelled next week

Hi, As we agreed on Tuesday on the subteam meeting[1] the next week meeting is skipped due to lack of chairman. Please use the normal channels to sync during the week. Next meeting will be held on 17th of May 17:00 UTC on #openstack-meeting-4 [2] Cheers, Gibi [1]

[openstack-dev] [telemetry][nova] Versioned notification with JSON schema

Hi, Just want to give telemetry a heads up that top of the versioned notification transformation in nova [1] we are planning to provide JSON schemas for the versioned notifications [2]. I hope telemetry project has a view how they want to consume those schemas. Any comments are welcome in the

[openstack-dev] [nova] notification subteam meeting rescheduled to biweekly

Hi, As agreed on the last notification subteam meeting [1] I proposed to reschedule the subteam meeting to biweekly [2] as the workload is decreased due to non priority feature freeze. So the next notification subteam meeting will be held on 2016.07.26 17:00 UTC [1] on #openstack-meeting-4.

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.07.12 17:00 UTC [1] on #openstack-meeting-4. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160712T17 __ OpenStack

[openstack-dev] [nova] Status of the versioned notification transformation work

Hi, Here is a quick update on where we are with the work to transform the legacy notification interface of nova to the new versioned framework. The scope we agreed [1] for Newton has been merged and top of that we was able to merge some additional transformations. So the following

Re: [openstack-dev] [nova] Non-priority feature freeze and FFEs

> -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: July 01, 2016 23:03 > > We're now past non-priority feature freeze. I've started going through > some blueprints and -2ing them if they still have outstanding changes. I > haven't gone through the full

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.08.09 17:00 UTC [1] on #openstack-meeting-4. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160809T17 __ OpenStack

[openstack-dev] [nova] Next notification meeting

Hi, The next notification subteam meeting will be held on 2017.01.17 17:00 UTC [1] on #openstack-meeting-4. Cheers, gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170117T17 __ OpenStack

[openstack-dev] [nova] using the qemu memory overhead in memory resource tracking or scheduling

Hi, In our cloud we use 1G huge pages for the instance memory. We started notice that qemu has a relevant memory overhead per domain (something like 300MB per domain). As we use huge pages for the instance memory nova scheduler makes placement decision based on the available huge pages. However

Re: [openstack-dev] [nova] using the qemu memory overhead in memory resource tracking or scheduling

he host OS. The qemu memory overhead is allocated from the 4k memory. If the compute runs out of 4k memory but still have free 1G pages then the claim is successful as overall there is free memory however qemu or the host OS can fail as there is no free 4k memory. Cheers, gibi > > On Tue

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.09.06 17:00 UTC [1] on #openstack-meeting-4. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160906T17 __ OpenStack

[openstack-dev] [nova] Notification tranformation burndown chart

Hi, Notification transformation work continues in nova for Ocata [1]. I've created a burndown chart that is automatically updated from gerrit based on sdague's api-ref burndown code. Please use that page [2] to follow the work; to see what to do and what to review. [1]

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.09.20 17:00 UTC [1] on #openstack-meeting-4. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160920T17 __ OpenStack

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.08.23 17:00 UTC [1] on #openstack-meeting-4. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160823T17 __ OpenStack

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.10.04 17:00 UTC [1] on #openstack-meeting-4. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20161004T17 __ OpenStack

Re: [openstack-dev] Event notification descriptors/schemas (? swagger ?)

> -Original Message- > From: Joshua Harlow [mailto:harlo...@fastmail.com] > Sent: October 11, 2016 22:36 > > Chris Dent wrote: > > On Tue, 11 Oct 2016, Joshua Harlow wrote: > > > >> Damn, that's crazy that the projects emitting events don't want to > >> own the formats and versions (and

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.11.15 17:00 UTC [1] on #openstack-meeting-4. Cheers, gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20161115T17 __ OpenStack

Re: [openstack-dev] [nova] [searchlight] Discrepancies between nova server notifications and API response

> -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: October 31, 2016 14:01 > > On 10/28/2016 4:32 PM, McLellan, Steven wrote: > > Hi, > > > > I was unfortunately unable to make the summit but I'm told there were > > some good discussions around possible

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.11.08 17:00 UTC [1] on #openstack-meeting-4. Also I proposed [2] to change the meeting frequency from biweekly to weekly until the feature freeze of Ocata. Cheers, Gibi [1]

[openstack-dev] [nova] Next notification meeting in 2017

Hi, Due to the holiday season the next notification subteam meeting will be held on 3rd of January [1]. Cheers, gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170103T17 __ OpenStack Development

[openstack-dev] [oslo][nova]Accessing nullable, not set versioned object field

Hi, What is the expected behavior of accessing a nullable and not set versioned object field? See the following example code: from oslo_versionedobjects import base from oslo_versionedobjects import fields @base.VersionedObjectRegistry.register class MyObject(base.VersionedObject):

Re: [openstack-dev] [oslo][nova]Accessing nullable, not set versioned object field

From: Dan Smith Sent: 16 December 2016 16:33 >> NotImplementedError: Cannot load 'nullable_string' in the base class >> >> Is this the correct behavior? > > Yes, that's the expected behaviour. Yes. >> Then what is the expected behavior if the field is also defaulted to >>

Re: [openstack-dev] [nova][searchlight] status of an instance on the REST API and in the instance notifications

> -Original Message- > From: Matt Riedemann [mailto:mriede...@gmail.com] > Sent: July 26, 2017 03:23 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [nova][searchlight] status of an instance on the > REST API and in the instance notifications > > On 7/19/2017 10:54

Re: [openstack-dev] [nova] nova-manage cell_v2 map_instances uses invalid UUID as marker in the db

On Thu, May 10, 2018 at 8:48 PM, Dan Smith wrote: The oslo UUIDField emits a warning if the string used as a field value does not pass the validation of the uuid.UUID(str(value)) call [3]. All the offending places are fixed in nova except the nova-manage cell_v2

Re: [openstack-dev] [nova] nova-manage cell_v2 map_instances uses invalid UUID as marker in the db

On Mon, May 14, 2018 at 11:49 AM, Balázs Gibizer <balazs.gibi...@ericsson.com> wrote: On Thu, May 10, 2018 at 8:48 PM, Dan Smith <d...@danplanet.com> wrote: Personally, I'd just make the offending tests shut up about the warning and move on, but I'm also okay with the ab

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

Hi, Here is the latest notification subteam update. Bugs [Low] https://bugs.launchpad.net/nova/+bug/1757407 Notification sending sometimes hits the keystone API to get glance endpoints Fix needs some additional work: https://review.openstack.org/#/c/564528/ [Medium]

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

Hi, After a bit of silence here is the latest notification status. Bugs [Low] https://bugs.launchpad.net/nova/+bug/1757407 Notification sending sometimes hits the keystone API to get glance endpoints Fix has been proposed has many +1s https://review.openstack.org/#/c/564528/ [Medium]

[openstack-dev] [nova] nova-manage cell_v2 map_instances uses invalid UUID as marker in the db

Hi, The oslo UUIDField emits a warning if the string used as a field value does not pass the validation of the uuid.UUID(str(value)) call [3]. All the offending places are fixed in nova except the nova-manage cell_v2 map_instances call [1][2]. That call uses markers in the DB that are not

[openstack-dev] [nova] Next notification subteam meeting is cancelled

Hi, I have to cancel the next notification subteam meeting as it happens to be on 1st of May which is (inter)national holiday. So the next meeting expected to be held on 8th of May. Cheers, gibi __ OpenStack

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

Hi, Here is the latest notification subteam update. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1739325 Server operations fail to complete with versioned notifications if payload contains unset non-nullable fields This is also visible in tssurya's environment. I'm wondering if we

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

Hi, Here is the latest notification subteam update. Bugs No update on bugs and we have no new bugs tagged with notifications. Features Sending full traceback in versioned notifications ~

Re: [openstack-dev] [requirements][nova] weird error on 'Validating lower constraints of test-requirements.txt'

On Fri, Jun 15, 2018 at 11:36 AM, Chen CH Ji wrote: on patch [1] , PS 50 and PS51 just a minor rebase but PS51 start to fail on requirements-check with following error in [2] Validating lower constraints of test-requirements.txt *** Incompatible requirement found! *** See

Re: [openstack-dev] [nova] review runways check-in and feedback

On Wed, Jun 13, 2018 at 10:33 PM, melanie witt wrote: Howdy everyone, We've been experimenting with a new process this cycle, Review Runways [1] and we're about at the middle of the cycle now as we had the r-2 milestone last week June 7. I wanted to start a thread and gather thoughts

Re: [openstack-dev] [nova] [placement] Upgrade concerns with nested Resource Providers

On Thu, May 31, 2018 at 11:10 AM, Sylvain Bauza wrote: After considering the whole approach, discussing with a couple of folks over IRC, here is what I feel the best approach for a seamless upgrade : - VGPU inventory will be kept on root RP (for the first type) in Queens so that a

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

Hi, Here is the latest notification subteam update. Bugs No new bugs, no progress on open bugs. Features Sending full traceback in versioned notifications ~

Re: [openstack-dev] [nova] [placement] Upgrade concerns with nested Resource Providers

On Tue, May 29, 2018 at 9:38 AM, Sylvain Bauza wrote: On Tue, May 29, 2018 at 3:08 AM, TETSURO NAKAMURA wrote > In that situation, say for example with VGPU inventories, that would mean > that the compute node would stop reporting inventories for its root RP, but > would rather

Re: [openstack-dev] [nova] [placement] Upgrade concerns with nested Resource Providers

On Tue, May 29, 2018 at 11:52 AM, Sylvain Bauza wrote: 2018-05-29 11:01 GMT+02:00 Balázs Gibizer : On Tue, May 29, 2018 at 9:38 AM, Sylvain Bauza wrote: On Tue, May 29, 2018 at 3:08 AM, TETSURO NAKAMURA wrote > In that situation, say for example with VGPU inventor

Re: [openstack-dev] [nova] [placement] Upgrade concerns with nested Resource Providers

On Tue, May 29, 2018 at 1:47 PM, Sylvain Bauza wrote: Le mar. 29 mai 2018 à 11:02, Balázs Gibizer a écrit : On Tue, May 29, 2018 at 9:38 AM, Sylvain Bauza wrote: > > > On Tue, May 29, 2018 at 3:08 AM, TETSURO NAKAMURA > wrote > >> > In that situation, s

Re: [openstack-dev] [nova] [placement] Upgrade concerns with nested Resource Providers

On Tue, May 29, 2018 at 3:12 PM, Sylvain Bauza wrote: On Tue, May 29, 2018 at 2:21 PM, Balázs Gibizer wrote: On Tue, May 29, 2018 at 1:47 PM, Sylvain Bauza wrote: Le mar. 29 mai 2018 à 11:02, Balázs Gibizer a écrit : On Tue, May 29, 2018 at 9:38 AM, Sylvain Bauza wrote

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

On Tue, Jun 19, 2018 at 7:07 PM, Matt Riedemann wrote: On 6/18/2018 10:10 AM, Balázs Gibizer wrote: * Introduce instance.lock and instance.unlock notifications https://blueprints.launchpad.net/nova/+spec/trigger-notifications-when-lock-unlock-instances This hasn't been updated in quite

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

Hi, Here is the latest notification subteam update. Bugs [Undecided] "IndexError: list index out of range" in ExceptionPayload.from_exception during resize failure https://bugs.launchpad.net/nova/+bug/1777540 I failed to reproduce and based on the newly provided logs in the parent bug

[openstack-dev] [nova] [libvirt] [scaleio] ScaleIO libvirt volume driver native mode

Hi, Two years ago a patch merged [1] that set AIO mode of some of the libivrt volume drivers to 'native' instead of the default 'threading'. At that time the ScaleIO driver was not modified. Recently we did some measurements (on Mitaka base) and we think that the ScaleIO volume driver could

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

Hi, Here is the status update / focus settings mail for 2018 w2. Bugs [High] https://bugs.launchpad.net/nova/+bug/1737201 TypeError when sending notification during attach_interface Fix merged to master. Backports have been proposed: * Pike: https://review.openstack.org/#/c/531745/ *

[openstack-dev] Notification update week 3

Hi, Here is the status update / focus settings mail for 2018 w3. Bugs [High] https://bugs.launchpad.net/nova/+bug/1742935TestServiceUpdateNotificationSample fails intermittently: u'host2' != u'host1': path: root.payload.nova_object.data.host The openstack-tox-functional (and

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

Hi, Here is the status update / focus settings mail for w4. Bugs [High] https://bugs.launchpad.net/nova/+bug/1742962 nova functional test does not triggered on notification sample only changes During the zuul v3 migration the project-config generated based on the zuul v2 jobs. It contained

Re: [openstack-dev] [nova] PTL Election Season

On Tue, Jan 23, 2018 at 12:09 AM, Matt Riedemann wrote: On 1/15/2018 11:04 AM, Kendall Nelson wrote: Election details: https://governance.openstack.org/election/ Please read the stipulations and timelines for candidates and electorate contained in this governance

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

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-)definition in the nova part of the project-config should not prevent it to run [1]. There we

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

On Fri, Jan 26, 2018 at 6:57 PM, James E. Blair <cor...@inaugust.com> wrote: Balázs Gibizer <balazs.gibi...@ericsson.com> 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 n

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

Hi, Here is the status update / focus settings mail for w6. Bugs No new bugs and the below bug status is the same as last week. [High] https://bugs.launchpad.net/nova/+bug/1737201 TypeError when sending notification during attach_interface Fix merged to master. Backports have been

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

Hi, Here is the status update / focus settings mail for w5. Bugs [High] https://bugs.launchpad.net/nova/+bug/1742962 nova functional test does not triggered on notification sample only changes Fix merged to master, backports are on the gate. When backport lands we can merge the removal

  1   2   >