On Mon, Oct 15, 2018 at 7:07 PM, melanie witt
wrote:
> Hey all,
>
> Milestone s-1 is coming up next week on Thursday Oct 25 [1] and I was
> thinking it would be a good idea to have a spec review day next week
> on Tuesday Oct 23 to spend some focus on spec reviews together.
>
> Spec freeze
On Wed, Oct 10, 2018 at 2:46 PM, Jay Pipes wrote:
> On 10/10/2018 06:32 AM, Balázs Gibizer wrote:
>> Hi,
>>
>> Thanks for all the feedback. I feel the following consensus is
>> forming:
>>
>> 1) remove the force flag in a new microversion. I've
will continue with #1)
later in the cycle.
Nothing is set in stone yet so feedback is still very appreciated.
Cheers,
gibi
[1] https://review.openstack.org/#/c/609330/
On Tue, Oct 9, 2018 at 11:40 AM, Balázs Gibizer
wrote:
> Hi,
>
> Setup
> -
>
> nested allocation: an a
On Tue, Oct 9, 2018 at 11:01 PM, Eric Fried wrote:
>
>
> On 10/09/2018 02:20 PM, Jay Pipes wrote:
>> On 10/09/2018 11:04 AM, Balázs Gibizer wrote:
>>> If you do the force flag removal in a nw microversion that also
>>> means
>>> (at least to me)
On Tue, Oct 9, 2018 at 5:32 PM, Sylvain Bauza
wrote:
>
>
> Le mar. 9 oct. 2018 à 17:09, Balázs Gibizer
> a écrit :
>>
>>
>> On Tue, Oct 9, 2018 at 4:56 PM, Sylvain Bauza
>>
>> wrote:
>> >
>> >
>> > Le mar. 9 oct. 2
2.29 ?
> In general, even in the case of an emergency, you still want to make
> sure you don't throw your compute under the bus by massively
> migrating instances that would create an undetected snowball effect
> by having this compute refusing new instances. Or are you disablin
or not, root resources or no, on the source and/or
> destination.
If you do the force flag removal in a nw microversion that also means
(at least to me) that you should not change the behavior of the force
flag in the old microversions.
Cheers,
gibi
>
> -efried
>
> On 10/09
Hi,
Setup
-
nested allocation: an allocation that contains resources from one or
more nested RPs. (if you have better term for this then please suggest).
If an instance has nested allocation it means that the compute, it
allocates from, has a nested RP tree. BUT if a compute has a nested R
Hi,
Due to low amount of ongoing work in the area there is a low interest to
have this meeting going. So I'm cancelling it indefinitely[1].
Of course I'm still intereseted in helping any notification related
work in the future and you can reach me in #openstack-nova as usual.
cheers,
gibi
[1]
On Sat, Sep 29, 2018 at 10:35 PM, Matt Riedemann
wrote:
Nova, cinder and tempest run the nova-multiattach job in their check
and gate queues. The job was added in Queens and was a specific job
because we had to change the ubuntu cloud archive we used in Queens
to get multiattach working. Si
On Fri, Sep 28, 2018 at 3:25 PM, Eric Fried wrote:
It's time somebody said this.
Every time we turn a corner or look under a rug, we find another use
case for provider traits in placement. But every time we have to have
the argument about whether that use case satisfies the original
"intended
On Mon, Sep 24, 2018 at 11:10 AM, Andreas Jaeger wrote:
> On 11/09/2018 19.13, Stephen Finucane wrote:
>> On Mon, 2018-09-10 at 13:48 -0600, Doug Hellmann wrote:
>>> Melanie gave me the go-ahead to propose the patches, so here's the
>>> list
>>> of patches for the zuul migration, doc job update
On Wed, Sep 19, 2018 at 5:25 PM, Chris Dent
wrote:
I'd like to nominate Tetsuro Nakamura for membership in the
placement-core team. Throughout placement's development Tetsuro has
provided quality reviews; done the hard work of creating rigorous
functional tests, making them fail, and fixing
Hi,
Reworked and rebased the series based on this thread. The series starts
here https://review.openstack.org/#/c/591597
Cheers,
gibi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstac
notification transformation patches [3] are merged.
Cheers,
gibi
[2] https://review.openstack.org/#/c/603079
[3]
https://review.openstack.org/#/q/topic:bp/versioned-notification-transformation-stein
On Tue, Aug 28, 2018 at 4:31 PM, Balázs Gibizer
wrote:
Thanks for all the responses. I
1:30.
Cheers,
gibi
-melanie
On Thu, Aug 30, 2018 at 3:55 AM, Balázs Gibizer
<mailto:balazs.gibi...@ericsson.com>> wrote:
Hi,
Based on the Nova PTG planning etherpad [1] there is a need to
talk
about the current state of the bandwidth work [2][3]. Bence
(rubaso
On Tue, Sep 4, 2018 at 7:01 PM, Jay Pipes wrote:
On 09/04/2018 12:59 PM, Balázs Gibizer wrote:
On Tue, Sep 4, 2018 at 6:25 PM, Jay Pipes wrote:
On 09/04/2018 12:17 PM, Doug Hellmann wrote:
Excerpts from Jay Pipes's message of 2018-09-04 12:08:41 -0400:
On 09/04/2018 11:44 AM,
On Tue, Sep 4, 2018 at 6:25 PM, Jay Pipes wrote:
On 09/04/2018 12:17 PM, Doug Hellmann wrote:
Excerpts from Jay Pipes's message of 2018-09-04 12:08:41 -0400:
On 09/04/2018 11:44 AM, Doug Hellmann wrote:
Excerpts from Chris Dent's message of 2018-09-04 15:32:12 +0100:
On Tue, 4 Sep 2018, Ja
Balázs Gibizer
wrote:
Thanks for all the responses. I collected them on the nova ptg
discussion etherpad [1] (L186 at the moment). The nova team will talk
about deprecation of the legacy interface on Friday on the PTG. If
you
want participate in the discussion but you are not planning to sit in
Hi,
This week's and next week's notification subteam meeting has been
cancelled. See you in Denver.
Cheers,
gibi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.op
On Fri, Aug 31, 2018 at 5:45 PM, Eric Fried wrote:
The openstack/placement project [1] and its core team [2] have been
established in gerrit.
I hereby nominate Chris Dent for membership in the placement-core
team.
He has been instrumental in the design, implementation, and
stewardship
of th
gibi
-melanie
On Thu, Aug 30, 2018 at 3:55 AM, Balázs Gibizer
mailto:balazs.gibi...@ericsson.com>>
wrote:
Hi,
Based on the Nova PTG planning etherpad [1] there is a need to
talk
about the current state of the bandwidth work [2][3]. Bence
(rubasov) has already planned to s
Hi,
Based on the Nova PTG planning etherpad [1] there is a need to talk
about the current state of the bandwidth work [2][3]. Bence (rubasov)
has already planned to show a small demo to Neutron folks about the
current state of the implementation. So Bence and I are wondering about
bringing th
day then let me know and I will try to ping you
over IRC when we about to start the item.
Cheers,
gibi
[1] https://etherpad.openstack.org/p/nova-ptg-stein
On Thu, Aug 9, 2018 at 11:41 AM, Balázs Gibizer
wrote:
Dear Nova notification consumers!
The Nova team made progress with the new
Hi,
There won't be notification subteam meeting this week.
Cheers,
gibi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://li
On Tue, Aug 28, 2018 at 1:20 PM, Chris Dent
wrote:
On Mon, 27 Aug 2018, melanie witt wrote:
I think we should use the openstack review system (gerrit) for
moving the code. We're moving a critical piece of nova to its own
repo and I think it's worth having the review and history contained
On Mon, Aug 27, 2018 at 5:31 PM, Matt Riedemann
wrote:
On 8/24/2018 7:36 AM, Chris Dent wrote:
Over the past few days a few of us have been experimenting with
extracting placement to its own repo, as has been discussed at
length on this list, and in some etherpads:
https://etherpad.opensta
On Fri, Aug 17, 2018 at 5:40 PM, Eric Fried wrote:
gibi-
- On migration, when we transfer the allocations in either
direction, a
conflict means someone managed to resize (or otherwise change
allocations?) since the last time we pulled data. Given the global
lock
in the report client,
On Sat, Aug 18, 2018 at 2:25 PM, Chris Dent
wrote:
So my hope is that (in no particular order) Jay Pipes, Eric Fried,
Takashi Natsume, Tetsuro Nakamura, Matt Riedemann, Andrey Volkov,
Alex Xu, Balazs Gibizer, Ed Leafe, and any other contributor to
placement whom I'm forgetting [1] would expr
Hi,
There won't be subteam meeting this week.
Cheers,
gibi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.o
tance_uuid}/action with forceDelete body would use DELETE
/allocations and therefore will ignore any consumer generation.
Cheers,
gibi
Thanks,
efried
On 08/16/2018 06:43 AM, Balázs Gibizer wrote:
reformatted for readabiliy, sorry:
Hi,
tl;dr: To properly use consumer generation (placemen
reformatted for readabiliy, sorry:
Hi,
tl;dr: To properly use consumer generation (placement 1.28) in Nova we
need to decide how to handle consumer generation conflict from Nova
perspective:
a) Nova reads the current consumer_generation before the allocation
update operation and use that gener
Hi,
tl;dr: To properly use consumer generation (placement 1.28) in Nova we
need to
decide how to handle consumer generation conflict from Nova perspective:
a) Nova reads the current consumer_generation before the allocation
update
operation and use that generation in the allocation update o
Hi,
There won't be notification subteam meeting this week.
Cheers,
gibi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://list
Dear Nova notification consumers!
The Nova team made progress with the new versioned notification
interface [1] and it is almost reached feature parity [2] with the
legacy, unversioned one. So Nova team will discuss on the upcoming PTG
the deprecation of the legacy interface. There is a list
Hi,
Here is the latest notification subteam update.
Bugs
No RC potential notification bug is tracked.
No new bug since last week.
Weekly meeting
--
No meeting is planned for this week.
Cheers,
gibi
__
Hi,
Here is the latest notification subteam update.
Bugs
No RC potential notification bug is tracked.
No new bug since last week.
Features
We hit FeatureFreeze. Every tracked bp is merged before FF except
verioned notification transformation. That will be re-proposed to Stein
t
Hi,
Here is the latest notification subteam update.
Bugs
No new bugs tagged with notifications and no progress with the existing
ones.
Features
Versioned notification transformation
-
We have only a handfull of patches left before we can final
On Mon, Jul 9, 2018 at 12:38 PM, Balázs Gibizer
wrote:
Hi,
Here is the latest notification subteam update.
[...]
Weekly meeting
--
The next meeting is planned to be held on 10th of June on
#openstack-meeting-4
https://www.timeanddate.com/worldclock/fixedtime.html?iso
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 h
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
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
~
https://blueprints.launchpad.net/nova/+spec
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 and
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 http://docs.opensta
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
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 comp
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
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
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 inventories, t
Hi,
Here is the latest notification subteam update.
Bugs
No new bugs, no progress on open bugs.
Features
Sending full traceback in versioned notifications
~
https://blueprints.launchpad.net/nova/+spec/add-full-traceback-to-error-no
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 repor
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] https://bugs.launchpad
On Mon, May 14, 2018 at 11:49 AM, Balázs Gibizer
wrote:
On Thu, May 10, 2018 at 8:48 PM, Dan Smith wrote:
Personally, I'd just make the offending tests shut up about the
warning
and move on, but I'm also okay with the above solution if people
prefer.
I think that was
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 map_instances call [1][2
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 val
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] ht
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 Development
On Tue, Apr 24, 2018 at 9:08 AM, Alex Xu wrote:
2018-04-24 5:51 GMT+08:00 Arvind N :
Thanks for the detailed options Matt/eric/jay.
Just few of my thoughts,
For #1, we can make the explanation very clear that we rejected the
request because the original traits specified in the original i
Hi,
New week, new status mail.
Bugs
New bugs
[Undecided] https://bugs.launchpad.net/nova/+bug/1764927 Should send
out notification when instance metadata get updated
Nova already sends instance.update notification when instance.metadata
is changed so I marked the bug invalid.
On Thu, Apr 19, 2018 at 2:27 PM, Eric Fried wrote:
gibi-
Can the proximity param specify relationship between the
un-numbered and
the numbered groups as well or only between numbered groups?
Besides that I'm +1 about proxyimity={isolate|any}
Remembering that the resources in the un-num
On Thu, Apr 19, 2018 at 12:45 AM, Eric Fried wrote:
I have a feeling we're just going to go back and forth on this, as
we
have for weeks now, and not reach any conclusion that is
satisfactory to
everyone. And we'll delay, yet again, getting functionality into
this
release that serves 90%
Hi,
After the long silence here is the current notification status info.
Bugs
New bugs
[Low] https://bugs.launchpad.net/nova/+bug/1757407 Notification sending
sometimes hits the keystone API to get glance endpoints
As the versioned notifications does not use the glance endpoints
Hi,
The get_all_bw_counters() virt driver [1] is only supported by xenapi
today. However Matt raised the question [2] if this is a nova-network
only feature. As in that case we can simply remove it.
Cheers,
gibi
[1]
https://github.com/openstack/nova/blob/68afe71e26e60a3e4ad30083cc244c57540d
+1
On Tue, Mar 27, 2018 at 4:00 AM, melanie witt
wrote:
Howdy everyone,
I'd like to propose that we add Eric Fried to the nova-core team.
Eric has been instrumental to the placement effort with his work on
nested resource providers and has been actively contributing to many
other areas of
Hi,
Here is the status update / focus settings mail for w12.
Bugs
One new bug from last week:
[Undecided] https://bugs.launchpad.net/nova/+bug/1756360 Serializer
strips Exception kwargs
The bug refers to an oslo.serialization change as the reason of the
changed behavior but I failed to
On Fri, Mar 16, 2018 at 12:04 AM, Matt Riedemann
wrote:
On 3/15/2018 3:30 PM, melanie witt wrote:
* We don't need to block bandwidth-based scheduling support for
doing port creation in conductor (it's not trivial), however, if
nova creates a port on a network with a QoS policy, nova
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 admin by default) and the notifications are
also
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
-
W
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 to the message bus by
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 revi
- 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 b
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 TypeE
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
[1]http://eavesdrop.openstack.org/meetings/nova/2018/nova.2018-02-15-21.01.lo
On Wed, Feb 14, 2018 at 6:45 AM, Andreas Jaeger wrote:
On 2018-02-14 01:28, Ghanshyam Mann wrote:
On Wed, Feb 14, 2018 at 12:06 AM, Paul Belanger
wrote:
On Tue, Feb 13, 2018 at 11:05:34PM +0900, gmann wrote:
Hi Infra Team,
I have 1 quick question on zuulv3 jobs and their migration par
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
https
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
https://blueprints.launchpad.net/nova/+spec/versioned-notificatio
On Fri, Feb 9, 2018 at 4:01 PM, 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:
http://stackalytics.com
On Tue, Feb 6, 2018 at 7:04 PM, Matt Riedemann
wrote:
On 2/5/2018 9:32 AM, Balázs Gibizer wrote:
Introduce instance.lock and instance.unlock notifications
-
A specless bp has been proposed to the Rocky cycle
https
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 propose
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 of
On Fri, Jan 26, 2018 at 6: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 have seen this already -- some
of
it didn't exist whe
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 figu
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 documentation.
Be aware
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
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 functional-p
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 a
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/
* Quee
> -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 A
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 Developmen
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
>> None?
>>
>> fields
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):
VERSI
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 M
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 Developm
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] https://www.timeanddate.com/worldclock/fixedtime.html?iso
> -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
> -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 sc
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]
https://blueprints.l
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 Developme
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 Developme
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 Developme
1 - 100 of 162 matches
Mail list logo
