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 noti
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 http
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
>
>
>
http://lists.openstack.org/pipermail/openstack-d
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 https://re
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 documentati
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 documentati
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 documentati
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 documentati
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 document
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 un
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
http://lists.op
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 un
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 is
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-requ...@lists.openstack.org?s
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:
http://lists.openstack.org/pipermail/openstack-dev/2017-Ju
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 'reserved_host_memory_mb'
option. This
defaults t
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:
http://lists.openstack.org/pipermail/openstack-dev/2017-Ju
On Wed, Sep 20, 2017 at 2:37 AM, Matt Riedemann
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
> HostAPI related noti
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
* HostAPI.p
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:
http://lists.openstack.org/pipermail/openstack-dev/2017-Ju
On Wed, Aug 30, 2017 at 4:30 PM, Balazs Gibizer
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 unversioned
notifications or the new versioned
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 p
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 mentions Placement:
h
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:
http://lists.openstack.org/pipermail/openstack-dev/2017-Ju
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 is an
important dimensi
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 see
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 notifications effort, which als
On Mon, Aug 28, 2017 at 11:27 PM, Matt Riedemann
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 been modified so notifications are
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
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
http://l
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
http://lis
o 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 to) and sen
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
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
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 https://review.openstack.org/#/c/475276/
On Wed, Jul 19, 2017 at 3:54 PM, Chris Dent
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-based replication of the de
at 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"
wro
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?
On Wed, Jul 19, 2017 at 1:13 PM, Chris Dent
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 appreciated.
I managed to create a functional
On Tue, Jul 18, 2017 at 2:39 PM, Balazs Gibizer
wrote:
On Mon, Jul 17, 2017 at 6:40 PM, Jay Pipes wrote:
> On 07/17/2017 11:31 AM, Balazs Gibizer wrote:
> > On Thu, Jul 13, 2017 at 11:37 AM, Chris Dent
>
> > wrote:
> >> On Thu, 13 Jul 2017, Balazs Gibizer wrot
On Mon, Jul 17, 2017 at 6:40 PM, Jay Pipes wrote:
On 07/17/2017 11:31 AM, Balazs Gibizer wrote:
> On Thu, Jul 13, 2017 at 11:37 AM, Chris Dent
> wrote:
>> On Thu, 13 Jul 2017, Balazs Gibizer wrote:
>>
>>>
/placement/allocation_candidates?resources=CUSTOM_M
On Mon, Jul 17, 2017 at 9:32 PM, Matt Riedemann
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.launchpad.net/nova/+bug/16
On Thu, Jul 13, 2017 at 11:37 AM, Chris Dent
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
back to legacy behavior [4] and p
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 b
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 t
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] https
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 for
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 a
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 api.fa
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 good
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
https://revie
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 som
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 Developme
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
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
https://rev
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 https://review.openstack.org/#/c
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] that would exercise the
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.
https://rev
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
f
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 https://review.openstack.org/#/c/42
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 port.
Does Jun
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 https://review.openstack.org/#/c/42
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 https://review.openstack.org/#/c/42
On Wed, Mar 15, 2017 at 1:44 PM, John Garbutt
wrote:
On 13 March 2017 at 17:14, Balazs Gibizer
wrote:
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
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
/servers/{server_id}
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 has
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 "compute." prefix in the n
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
searchlight team can just inform me. Otherwise we mig
n 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 Gibizer
wrote:
On Mon,
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 miss
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:
http://git.openstack.org/cgit/openstack/searchlight/tree/searchlight/elasticsearch/plugins/nova/notification_handler.py#n
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 Pi
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 Devel
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 whether you guys discussed or no
On Wed, Feb 15, 2017 at 10:31 PM, Matt Riedemann
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 instance. Unfortunately the legacy
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] f
On Tue, Feb 7, 2017 at 3:56 PM, Matt Riedemann
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 #openstack-meeting-4.
Ch
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
__
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 Develop
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 Devel
On Fri, Jan 13, 2017 at 9:51 AM, Balazs Gibizer
wrote:
On Thu, Jan 12, 2017 at 4:56 PM, Jay Pipes 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
the
projects field of the Flavor object is also lazy-loaded. Now
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 Dev
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.
The existing non-versi
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* nova, or people *interested*
84 matches
Mail list logo
