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

2017-12-18 Thread Balazs Gibizer
Hi, Here is the last status update / focus settings mail for 2017 Bugs [High] https://bugs.launchpad.net/nova/+bug/1737201 TypeError when sending notification during attach_interface Fix proposed and needs a second core to look at: https://review.openstack.org/#/c/527920/ Versioned

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

2017-12-11 Thread Balazs Gibizer
Hi, Here is the status update / focus settings mail for 50 Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1535254 illustration of 'notify_on_state_change' are different from implementation The fix merged to the master and stable/pike. The stable/ocata backport has been proposed

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

2017-12-04 Thread Balazs Gibizer
On Sat, Dec 2, 2017 at 3:26 AM, Matt Riedemann wrote: On 12/1/2017 10:42 AM, Chris Dent wrote: > > December? Wherever does the time go? This is resource providers and > placement update 43. The first one of these was more than a year ago > > >

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

2017-12-04 Thread Balazs Gibizer
Hi, Here is the status update / focus settings mail for w49 Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1535254 illustration of 'notify_on_state_change' are different from implementation The fix merged to the master and backports has been proposed to the stable branches

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

2017-11-27 Thread Balazs Gibizer
Hi, Here is the status update / focus settings mail for w48 Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1535254 illustration of 'notify_on_state_change' are different from implementation As the behavior is unchanged in the last 5 years a patch is proposed to update the

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

2017-11-21 Thread Balazs Gibizer
Hi, Here is the status update / focus settings mail for w47 Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1535254 illustration of 'notify_on_state_change' are different from implementation As the behavior is unchanged in the last 5 years a patch is proposed to update the

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

2017-11-13 Thread Balazs Gibizer
Hi, Here is the status update / focus settings mail for w46 Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1535254 illustration of 'notify_on_state_change' are different from implementation As the behavior is unchanged in the last 5 years a patch is proposed to update the

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

2017-11-06 Thread Balazs Gibizer
Hi, Here is the status update / focus settings mail for w45 Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1535254 illustration of 'notify_on_state_change' are different from implementation As the behavior is unchanged in the last 5 years a patch is proposed to update the

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

2017-10-30 Thread Balazs Gibizer
Hi, Here is the status update / focus settings mail for w44. Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1535254 illustration of 'notify_on_state_change' are different from implementation As the behavior is unchanged in the last 5 years a patch is proposed to update the

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

2017-10-25 Thread Balazs Gibizer
Hi, Here is the status update / focus settings mail for w43. Bugs [High] https://bugs.launchpad.net/nova/+bug/1706563 TestRPC.test_cleanup_notifier_null fails with timeou [High] https://bugs.launchpad.net/nova/+bug/1685333 Fatal Python error: Cannot recover from stack overflow. - in py35

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

2017-10-20 Thread Balazs Gibizer
Hi, The next notification subteam meeting is canceled. Cheers, gibi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

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

2017-10-16 Thread Balazs Gibizer
Hi, Here is the status update / focus settings mail for w42. Bugs [High] https://bugs.launchpad.net/nova/+bug/1706563 TestRPC.test_cleanup_notifier_null fails with timeou [High] https://bugs.launchpad.net/nova/+bug/1685333 Fatal Python error: Cannot recover from stack overflow. - in py35

[openstack-dev] [nova] otification update week 41

2017-10-09 Thread Balazs Gibizer
Hi, Here is the status update / focus settings mail for w41. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1699115 api.fault notification is never emitted It seems that rackspace does not use api.fault notification [2][3] So the agreement seems to be to remove the dead code. Patch

[openstack-dev] [nova] notification subteam meeting is canceled

2017-10-03 Thread Balazs Gibizer
Hi, Today's notification subteam meeting is canceled not to disturb spec review focus. Cheers, gibi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [nova] notification update week 40

2017-10-02 Thread Balazs Gibizer
Hi, Here is the status update / focus settings mail for w40. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1699115 api.fault notification is never emitted We still have to figure out what is the expected behavior here based on:

Re: [openstack-dev] [nova] Running large instances with CPU pinning and OOM

2017-09-27 Thread Balazs Gibizer
On Wed, Sep 27, 2017 at 11:58 AM, Jakub Jursa wrote: On 27.09.2017 11:12, Jakub Jursa wrote: On 27.09.2017 10:40, Blair Bethwaite wrote: On 27 September 2017 at 18:14, Stephen Finucane wrote: What you're probably looking for is the

[openstack-dev] [nova] notification update week 39

2017-09-25 Thread Balazs Gibizer
Hi, Here is the status update / focus settings mail for w39. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1699115 api.fault notification is never emitted We still have to figure out what is the expected behavior here based on:

Re: [openstack-dev] [nova] [notification] not transforming HostAPI related versioned notifications

2017-09-20 Thread Balazs Gibizer
On Wed, Sep 20, 2017 at 2:37 AM, Matt Riedemann <mriede...@gmail.com> wrote: On 9/19/2017 10:35 AM, Balazs Gibizer wrote: > Hi, > > Similar to my earlier mail about not transforming legacy notifications > in the networking area [1] now I want to propose not to transform

[openstack-dev] [nova] [notification] not transforming HostAPI related versioned notifications

2017-09-19 Thread Balazs Gibizer
Hi, Similar to my earlier mail about not transforming legacy notifications in the networking area [1] now I want to propose not to transform HostAPI related notifications. We have the following legacy notifications on our TODO list [2] to be transformed: * HostAPI.power_action.end *

[openstack-dev] [nova]notification update week 38

2017-09-18 Thread Balazs Gibizer
Hi, Here is the status update / focus settings mail for w38. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1699115 api.fault notification is never emitted We still have to figure out what is the expected behavior here based on:

Re: [openstack-dev] [all] connecting nova notification users and developers

2017-09-11 Thread Balazs Gibizer
On Wed, Aug 30, 2017 at 4:30 PM, Balazs Gibizer <balazs.gibi...@ericsson.com> wrote: 1) We in the nova developer community would like to see which projects are using (or planning to use) the nova notification interface. Also we would like to know if you are using the legacy unver

[openstack-dev] [nova] [notification] cleaning up networking related notifications

2017-09-08 Thread Balazs Gibizer
Hi, The addFixedIp REST API was deprecated in Pike [1] (in microversion 2.44). As a result the legacy create_ip.start and create_ip.end notifications will not be emitted after microversion 2.44. We had a TODO[2] to transform this notification to the versioned format but now that seems a bit

Re: [openstack-dev] [nova][scheduling] Can VM placement consider the VM network traffic need?

2017-09-05 Thread Balazs Gibizer
On Mon, Sep 4, 2017 at 9:11 PM, Jay Pipes wrote: On 09/01/2017 04:42 AM, Rua, Philippe (Nokia - FI/Espoo) wrote: > Will it be possible to include network bandwidth as a resource in Nova scheduling, for VM placement decision? Yes. See here for a related Neutron spec that

[openstack-dev] [nova]notification update week 36

2017-09-04 Thread Balazs Gibizer
Hi, Here is the status update / focus settings mail for w36. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1699115 api.fault notification is never emitted We still have to figure out what is the expected behavior here based on:

Re: [openstack-dev] [nova][scheduling] Can VM placement consider the VM network traffic need?

2017-09-01 Thread Balazs Gibizer
On Fri, Sep 1, 2017 at 10:42 AM, Rua, Philippe (Nokia - FI/Espoo) wrote: Will it be possible to include network bandwidth as a resource in Nova scheduling, for VM placement decision? I think it will. Context: in telecommunication applications, the network traffic

[openstack-dev] [all] connecting nova notification users and developers

2017-08-30 Thread Balazs Gibizer
Hi, Nova emits notifications for many different event, like different instance actions[1]. Also the nova developer community is working on making nova notifications well defined and easy to consume [2]. The goal of this mail is twofold. 1) We in the nova developer community would like to

Re: [openstack-dev] [nova] Proposing Balazs Gibizer for nova-core

2017-08-30 Thread Balazs Gibizer
On Tue, Aug 29, 2017 at 6:02 PM, Matt Riedemann wrote: On 8/22/2017 8:18 PM, Matt Riedemann wrote: > I'm proposing that we add gibi to the nova core team. He's been around > for awhile now and has shown persistence and leadership in the > multi-release versioned

Re: [openstack-dev] [nova]notification update week 35

2017-08-29 Thread Balazs Gibizer
On Mon, Aug 28, 2017 at 11:27 PM, Matt Riedemann <mriede...@gmail.com> wrote: On 8/28/2017 10:52 AM, Balazs Gibizer wrote: > [Undecided] https://bugs.launchpad.net/nova/+bug/1700496 Notifications > are emitted per-cell instead of globally > Devstack config has already b

[openstack-dev] [nova]notification update week 35

2017-08-28 Thread Balazs Gibizer
Hi, After a couple of weeks of silence here is the status update / focus settings mail for w35. Bugs As there was no critical bug for Pike in the notification area there was not much progress in the bugs below. [Low] https://bugs.launchpad.net/nova/+bug/1696152 nova notifications use

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

2017-08-21 Thread Balazs Gibizer
Hi, The notification subteam meeting is canceled this week. Cheers, gibi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] [nova] notification subteam meeting is canceled

2017-08-15 Thread Balazs Gibizer
Hi, The notification subteam meeting is canceled this week. Cheers, gibi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [nova] Thanks gibi!

2017-08-11 Thread Balazs Gibizer
rnity, I wanted to take the time now to thank gibi (Balazs > Gibizer to his parents) for all the work he's been doing in Nova. > > Not only does gibi lead the versioned notification transformation work, > which includes running a weekly meeting (that only one other person > shows up t

[openstack-dev] [nova]notification update week 32

2017-08-07 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 32. Bugs [Low] https://bugs.launchpad.net/nova/+bug/1696152 nova notifications use nova-api as binary name instead of nova-osapi_compute Agreed not to change the binary name in the notifications. Instead we

[openstack-dev] [nova]notification update week 31

2017-07-31 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 31. Bugs [Low] https://bugs.launchpad.net/nova/+bug/1696152 nova notifications use nova-api as binary name instead of nova-osapi_compute Agreed not to change the binary name in the notifications. Instead we

[openstack-dev] [nova]notification update week 30

2017-07-25 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 30. Better late than never. Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1684860 Versioned server notifications don't include updated_at The fix is on review

Re: [openstack-dev] [nova][placement] scheduling with custom resouce classes

2017-07-20 Thread Balazs Gibizer
On Wed, Jul 19, 2017 at 3:54 PM, Chris Dent <cdent...@anticdent.org> wrote: On Wed, 19 Jul 2017, Balazs Gibizer wrote: I added more info to the bug report and the review as it seems the test is fluctuating. (Reflecting some conversation gibi and I have had in IRC) I've made a gabbi

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

2017-07-19 Thread Balazs Gibizer
rstand though that this late in the cycle it may not be possible. I can create a patch to add the status to the instance notifications but I don't know if nova cores accept it for this late in Pike. @Cores: Do you? Cheers, gibi Thanks, Steve On 7/19/17, 10:27 AM, "Balazs Gibizer&qu

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

2017-07-19 Thread Balazs Gibizer
Hi, Steve asked the following question on IRC [1] < sjmc7> hi gibi. sorry, meant to bring this up in the notifications meeting but i had to step away for a bit. we were having a discussion last week about the field that the API returns as 'status' - do the notifications have an equivalent?

Re: [openstack-dev] [nova][placement] scheduling with custom resouce classes

2017-07-19 Thread Balazs Gibizer
On Wed, Jul 19, 2017 at 1:13 PM, Chris Dent <cdent...@anticdent.org> wrote: On Wed, 19 Jul 2017, Balazs Gibizer wrote: We are trying to get some help from the related functional test [5] but honestly we still need some time to digest that LOCs. So any direct help is appreciate

Re: [openstack-dev] [nova][placement] scheduling with custom resouce classes

2017-07-19 Thread Balazs Gibizer
On Tue, Jul 18, 2017 at 2:39 PM, Balazs Gibizer <balazs.gibi...@ericsson.com> wrote: On Mon, Jul 17, 2017 at 6:40 PM, Jay Pipes <jaypi...@gmail.com> wrote: > On 07/17/2017 11:31 AM, Balazs Gibizer wrote: > > On Thu, Jul 13, 2017 at 11:37 AM, Chris Dent > <cdent.

Re: [openstack-dev] [nova][placement] scheduling with custom resouce classes

2017-07-18 Thread Balazs Gibizer
On Mon, Jul 17, 2017 at 6:40 PM, Jay Pipes <jaypi...@gmail.com> wrote: On 07/17/2017 11:31 AM, Balazs Gibizer wrote: > On Thu, Jul 13, 2017 at 11:37 AM, Chris Dent <cdent...@anticdent.org> > wrote: >> On Thu, 13 Jul 2017, Balazs Gibizer wrote: >> >>

Re: [openstack-dev] [nova]notification update week 29

2017-07-18 Thread Balazs Gibizer
On Mon, Jul 17, 2017 at 9:32 PM, Matt Riedemann <mriede...@gmail.com> wrote: On 7/17/2017 2:36 AM, Balazs Gibizer wrote: > Hi, > > Here is the status update / focus setting mail about notification work > for week 29. > > Bugs > > [Undecided] https://bugs.l

Re: [openstack-dev] [nova][placement] scheduling with custom resouce classes

2017-07-17 Thread Balazs Gibizer
On Thu, Jul 13, 2017 at 11:37 AM, Chris Dent <cdent...@anticdent.org> wrote: On Thu, 13 Jul 2017, Balazs Gibizer wrote: /placement/allocation_candidates?resources=CUSTOM_MAGIC%3A512%2CMEMORY_MB%3A64%2CVCPU%3A1" but placement returns an empty response. Then nova scheduler falls bac

[openstack-dev] [nova]notification update week 29

2017-07-17 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 29. Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1684860 Versioned server notifications don't include updated_at The fix https://review.openstack.org/#/c/475276/ is in focus but comments needs to

[openstack-dev] [nova][placement] scheduling with custom resouce classes

2017-07-13 Thread Balazs Gibizer
Dear Placement developers, I'm trying to build on top of the custom resource class implementation [1][2] from the current master [3]. I'd like to place instances based on normal resources (cpu, ram) and based on a custom resource I will call MAGIC for this discussion. So far I managed to use

[openstack-dev] [nova] notification update week 28

2017-07-10 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 28. Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1684860 Versioned server notifications don't include updated_at Takashi's fix needs a second +2 https://review.openstack.org/#/c/475276/ [Low]

[openstack-dev] [nova] notification update week 27

2017-07-03 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 27. Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1684860 Versioned server notifications don't include updated_at Takashi proposed the fix https://review.openstack.org/#/c/475276/ that is ready

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

2017-06-26 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 26. Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1684860 Versioned server notifications don't include updated_at Takashi proposed the fix https://review.openstack.org/#/c/475276/ that only needs

[openstack-dev] [nova] api.fault notification is never emitted

2017-06-20 Thread Balazs Gibizer
Hi, I come across a questionable behavior of nova while I tried to use the notify_on_api_faults configuration option [0] while testing the related versioned notification transformation patch [1]. Based on the description of the config option and the code that uses it [2] nova sends and

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

2017-06-19 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 25. Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1684860 Versioned server notifications don't include updated_at Takashi proposed the fix https://review.openstack.org/#/c/475276/ that looks

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

2017-06-12 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 24. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1657428 The instance notifications are sent with inconsistent timestamp format. One of the prerequisite patches needs some discussion

[openstack-dev] [nova] notification update week 23

2017-06-06 Thread Balazs Gibizer
Hi, After two weeks of silence here is the status update / fucus setting mail about notification work for week 23. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1657428 The instance notifications are sent with inconsistent timestamp format. One of the prerequisite patches needs

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

2017-05-19 Thread Balazs Gibizer
Hi, The next two notification subteam meetings are canceled so the next meeting will be held on 6th of June. https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170606T17 Cheers, gibi __ OpenStack

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

2017-05-15 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 20. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1657428 The instance notifications are sent with inconsistent timestamp format. The solution is now consits of three patches and the series is wait for

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

2017-05-08 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 19. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1657428 The instance notifications are sent with inconsistent timestamp format. The solution still needs time and effort from the subteam

[openstack-dev] [nova] notification update week 18

2017-05-02 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 18. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1657428 The instance notifications are sent with inconsistent timestamp format. We need to iterate more on the solution

Re: [openstack-dev] [QA][Nova] Special scenario tests

2017-04-28 Thread Balazs Gibizer
On Thu, Apr 27, 2017 at 11:56 PM, Matt Riedemann wrote: On 4/21/2017 8:36 AM, Ferenc Horváth wrote: > Dear OpenStackerz, > > I'd like to improve the coverage of the current test suite over some > special code parts in Nova. > My main target is to add a few scenarios [1]

[openstack-dev] [nova] notification update week 16

2017-04-24 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 16. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1657428 The instance notifications are sent with inconsistent timestamp format. We need to iterate more on the solution I updated last week.

[openstack-dev] [nova] notification update week 14

2017-04-10 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 14. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1657428 The instance notifications are sent with inconsistent timestamp format. Fix seems abandoned by the original author so I will update it soon to

[openstack-dev] [nova] notification update week 13

2017-04-03 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 13. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1657428 The instance notifications are sent with inconsistent timestamp format. Fix is ready for the cores to review

Re: [openstack-dev] rebuild_instance (nova evacuate) failed to add trunk port

2017-03-31 Thread Balazs Gibizer
On Thu, Mar 30, 2017 at 10:14 PM, KHAN, RAO ADNAN wrote: In Juno, there is an issue with instance rebuild (nova evacuate) when trunk port is associated with that instance. On the target, it is not provisioning tbr (bridge) and hence 'ovs-vsctl' command failed when adding trunk

[openstack-dev] [nova] notification update week 12

2017-03-27 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 12. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1657428 The instance notifications are sent with inconsistent timestamp format. Fix is ready for the cores to review

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

2017-03-17 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 11. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1657428 The instance notifications are sent with inconsistent timestamp format. Fix is ready for the cores to review

Re: [openstack-dev] [nova] [notification] BlockDeviceMapping in InstancePayload

2017-03-16 Thread Balazs Gibizer
On Wed, Mar 15, 2017 at 1:44 PM, John Garbutt <j...@johngarbutt.com> wrote: On 13 March 2017 at 17:14, Balazs Gibizer <balazs.gibi...@ericsson.com> wrote: Hi, As part of the Searchlight integration we need to extend our instance notifications with BDM data [1]. As far as

[openstack-dev] [nova] [notification] BlockDeviceMapping in InstancePayload

2017-03-13 Thread Balazs Gibizer
Hi, As part of the Searchlight integration we need to extend our instance notifications with BDM data [1]. As far as I understand the main goal is to provide enough data about the instance to Searchlight so that Nova can use Searchlight to generate the response of the GET

[openstack-dev] [nova] notification update week 10

2017-03-13 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 10. Bugs There are couple of important outstanding bugs: [High] https://bugs.launchpad.net/nova/+bug/1665263 The legacy instance.delete notification is missing for unscheduled instance. The Pike fix

Re: [openstack-dev] [nova] Question to clarify versioned notifications

2017-03-08 Thread Balazs Gibizer
On Tue, Mar 7, 2017 at 8:42 PM, Matt Riedemann wrote: While digging through nova code today to compare versioned and unversioned notifications, and reading specs and seeing how seachlight handles nova notifications, I noticed that the unversioned notifications have a

Re: [openstack-dev] [nova][searchlight] When do instances get removed from Searchlight?

2017-03-06 Thread Balazs Gibizer
On Mon, Mar 6, 2017 at 3:06 PM, Lei Zhang wrote: On Mon, Mar 6, 2017 at 1:21 AM, Matt Riedemann wrote: So I'm wondering at what point instances stored in searchlight will be removed. Maybe there is already an answer to this and the

Re: [openstack-dev] [nova][searchlight] When do instances get removed from Searchlight?

2017-03-06 Thread Balazs Gibizer
d user with certain role can list it using deleted=true, so we should also do it in SL Yes, that is really different. If SL should be able to return hard deleted instances as well then the catching the soft_delete notification would not help. Cheers, gibi On Monday, March 6, 2017, Balazs G

[openstack-dev] [nova] notification update week 9

2017-03-06 Thread Balazs Gibizer
Hi, As we agreed on the PTG I will send out short status update / focus-setting mail about notifications work items to the ML weekly. Bugs There are couple of important outstanding bugs: [High] https://bugs.launchpad.net/nova/+bug/1665263 The legacy instance.delete notification is

Re: [openstack-dev] [nova][searchlight] When do instances get removed from Searchlight?

2017-03-06 Thread Balazs Gibizer
On Mon, Mar 6, 2017 at 3:09 AM, Zhenyu Zheng wrote: Hi, Matt AFAIK, searchlight did delete the record, it catch the instance.delete notification and perform the action:

[openstack-dev] [nova] Pike PTG recap - notifications

2017-03-01 Thread Balazs Gibizer
Hi, We discussed couple of notification related items last week on the PTG [1]. Searchlight related notification enhancements - We decided that the Extending versioned notifications for searchlight integration blueprint [2] has high priority for

[openstack-dev] [nova] Next notification meeting

2017-02-28 Thread Balazs Gibizer
Hi, The next notification subteam meeting will be held on 2017.02.28 17:00 UTC [1] on #openstack-meeting-4. Cheers, gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170228T17 __ OpenStack

Re: [openstack-dev] [nova] Pike PTG recap - cells

2017-02-28 Thread Balazs Gibizer
On Tue, Feb 28, 2017 at 3:10 AM, Zhenyu Zheng wrote: Matt, Thanks for the recap, it's a pity I cannot attend PTG due to personal reason, I will be willing to take the work you mentioned, and will check the details with you. And another thing, I don't know

Re: [openstack-dev] [nova] notification impact of moving the instance create to the conductor

2017-02-16 Thread Balazs Gibizer
On Wed, Feb 15, 2017 at 10:31 PM, Matt Riedemann <mriede...@gmail.com> wrote: On 2/15/2017 11:07 AM, Balazs Gibizer wrote: Hi, It seems that the Move instance creation to conductor commit [1] changed when and how the instance.delete notification is emitted for an unscheduled in

[openstack-dev] [nova] notification impact of moving the instance create to the conductor

2017-02-15 Thread Balazs Gibizer
Hi, It seems that the Move instance creation to conductor commit [1] changed when and how the instance.delete notification is emitted for an unscheduled instance. Unfortunately the legacy notification doesn't have test coverage and the versioned notification coverage are still on review [2]

Re: [openstack-dev] [nova] Next notification meeting on 02.14.

2017-02-08 Thread Balazs Gibizer
On Tue, Feb 7, 2017 at 3:56 PM, Matt Riedemann <mriede...@gmail.com> wrote: On 2/7/2017 7:40 AM, Balazs Gibizer wrote: Hi, As we agreed last week's meeting there won't be meeting this week. The next notification subteam meeting will be held on 2017.02.14 17:00 UTC [1] on #ope

[openstack-dev] [nova] Next notification meeting on 02.14.

2017-02-07 Thread Balazs Gibizer
Hi, As we agreed last week's meeting there won't be meeting this week. The next notification subteam meeting will be held on 2017.02.14 17:00 UTC [1] on #openstack-meeting-4. Cheers, gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170214T17

[openstack-dev] [nova] Next notification meeting

2017-01-30 Thread Balazs Gibizer
Hi, The next notification subteam meeting will be held on 2017.01.31 17:00 UTC [1] on #openstack-meeting-4. Cheers, gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170131T17 __ OpenStack

[openstack-dev] [nova] Next notification meeting

2017-01-24 Thread Balazs Gibizer
Hi, The next notification subteam meeting will be held on 2017.01.24 17:00 UTC [1] on #openstack-meeting-4. Cheers, gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170124T17 __ OpenStack

Re: [openstack-dev] [Openstack] [nova] Accessing instance.flavor.projects fails due to orphaned Flavor

2017-01-19 Thread Balazs Gibizer
On Fri, Jan 13, 2017 at 9:51 AM, Balazs Gibizer <balazs.gibi...@ericsson.com> wrote: On Thu, Jan 12, 2017 at 4:56 PM, Jay Pipes <jaypi...@gmail.com> wrote: On 01/12/2017 05:31 AM, Balazs Gibizer wrote: Hi, The flavor field of the Instance object is a lazy-loaded field and

[openstack-dev] [nova] Next notification meeting

2017-01-09 Thread Balazs Gibizer
Hi, The next notification subteam meeting will be held on 2017.01.10 17:00 UTC [1] on #openstack-meeting-4. Cheers, gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170110T17 __ OpenStack

Re: [openstack-dev] [nova] Consistency in versioned notification payloads

2017-01-01 Thread Balazs Gibizer
On Sat, Dec 31, 2016 at 5:08 PM, Doug Hellmann wrote: Excerpts from Matt Riedemann's message of 2016-12-30 16:23:24 -0600: While reviewing patches today to add versioned notifications for CRUD operations on aggregates and flavors I've come across some inconsistency.

Re: [openstack-dev] [nova] Feedback for upcoming user survey questionnaire

2016-12-28 Thread Balazs Gibizer
On Tue, Dec 27, 2016 at 12:08 AM, Matt Riedemann wrote: We have the opportunity to again [1] ask a question in the upcoming user survey which will be conducted in February. We can ask one question and have it directed to either *users* of Nova, people *testing*