Earlier  
Posted Nick Remark
#openstack-nova - 2018-11-27
20:23:32 mriedem hooks are use at your own risk (we can break them and not care to fix them), and the last time someone complained about the interface breaking on one of the hooks, upstream got real serious about just yanking them
20:23:42 mriedem kind of one of those squeeky wheel kinds of things - best not to talk about it
20:23:54 cdent yeah, I was wondering if the yanking was still an option
20:24:23 mriedem if we had a good reason to
20:24:29 cdent because the race I'm watching just showed up with a trace from one of them, but it appears it is more likely a coincidence
20:24:34 mriedem and someone that cared enough
20:25:29 cdent my running theory at this point is a totally unsurprising "it's probably eventlet"
20:28:12 mriedem no one was ever fired for blaming eventlet
20:32:24 mriedem GET /jaypipes
20:32:25 mriedem https://review.openstack.org/#/c/603352/7
20:36:15 mriedem i imagine jay is fighting with code using hooks within oath
20:36:31 mriedem hooks that call off to some chef thing
20:49:42 openstackgerrit Eric Fried proposed openstack/nova master: Reduce calls to placement from _ensure https://review.openstack.org/615677
20:49:42 openstackgerrit Eric Fried proposed openstack/nova master: SIGHUP n-cpu to clear provider tree cache https://review.openstack.org/615646
20:49:43 openstackgerrit Eric Fried proposed openstack/nova master: Commonize _update code path https://review.openstack.org/615705
20:49:43 openstackgerrit Eric Fried proposed openstack/nova master: Consolidate inventory refresh https://review.openstack.org/615695
20:49:44 openstackgerrit Eric Fried proposed openstack/nova master: Rip out the SchedulerClient https://review.openstack.org/617049
20:49:44 openstackgerrit Eric Fried proposed openstack/nova master: Rip the report client out of SchedulerClient https://review.openstack.org/617042
20:49:47 efried blayum
20:50:56 cdent huzzah
20:54:34 artom So eventlets are the reverse IBM? No one got fired for either buying IBM, or blaming eventlets?
20:59:28 mriedem that was the joke yes
21:02:44 tbachman <delayed boom-splash>
21:07:01 flwang could anybody please help me understand that if i can swift from v2 endpoint to v2.1 endpoint directly?
21:07:25 flwang 'directly' means change the endpoint url in keystone catalyst directly, thanks a lot
21:11:47 mriedem flwang: https://docs.openstack.org/nova/latest/reference/stable-api.html and https://specs.openstack.org/openstack/nova-specs/specs/liberty/implemented/api-relax-validation.html might help, but i think you also have to do something with the api-paste.ini
21:11:58 mriedem since that is config, it will require a change on upgrade to use v2.1
21:13:32 mriedem i'm thinking about this from liberty https://github.com/openstack/nova/commit/4a18f7d3bafcdbede48500aac389e0a770b8e6a8#diff-c29e518f0f69a48dc80705f43cf9a3b4
21:14:35 flwang mriedem: thanks for reply, we have enabled it based on my testing, the v2.1 endpoint works
21:14:45 flwang but i'm not sure how can we migrate the catalyst in keystone
21:14:50 flwang catalog
21:15:18 mriedem you can't just make the compute endpoint point at v2.1 rather than v2?
21:16:50 flwang because when you initialize a nova client, the code will talk to keystone catalog to get the endpoint
21:17:01 flwang and currently, we're using /v2/ in the endpint
21:17:07 flwang not v1
21:17:16 flwang for example, for horizon
21:17:20 flwang it's doing that
21:17:40 flwang and as a result, there are some features we can't enable without upgrading the endpint
21:20:38 flwang mriedem: i just checked, we have done the correct work for nova (api-paste.ini)
21:21:10 flwang and as I mentioned above, the endpoint is working correctly. im just not sure if we can change the keystone catalog now
21:21:30 mriedem the client just asks for the compute endpoint, right? which is an alias to some URL
21:21:49 mriedem the client shouldn't care if it's v1 or v2 or v2.1 really unless they have version-specific requests
21:23:21 flwang mriedem: yes, that's my understanding
21:23:49 flwang i think, as admin, it should be safe to switch the endpoint, but just wanna get more ideas at here
21:25:22 mriedem well it's been awhile since i've talked to any operators that went through this and the old kilo/liberty release notes are pretty sparse,
21:25:34 mriedem but the api-paste.ini was the big thing i knew of that hit people, like when oath upgraded,
21:25:39 mriedem but jpenick is out, and jaypipes insn't here
21:25:41 mriedem *isn't
21:25:47 mriedem jroll: were you around for the oath upgrade to ocata?
21:25:53 mriedem and compute api v2.1?
21:26:11 mriedem flwang: otherwise #openstack-operators is probably best
21:27:05 Sundar cdent: Please ping me when you have the time. Thanks.
21:28:50 flwang mriedem: got it, thank you so much
21:29:13 cdent Sundar: I'll try, but currently very busy. If it's something for which email will work: cdent@anticdent.org
#openstack-nova - 2018-11-28
00:05:09 openstack bug 1550919 in OpenStack Compute (nova) "[Libvirt]Evacuate fail may cause disk image be deleted" [Medium,In progress] https://launchpad.net/bugs/1550919 - Assigned to Matthew Booth (mbooth-9)
00:05:09 openstackgerrit Merged openstack/nova master: Add regression test for bug 1550919 https://review.openstack.org/591733
03:11:00 openstackgerrit Chris Dent proposed openstack/nova master: Use external placement in functional tests https://review.openstack.org/617941
03:11:30 openstackgerrit Chris Dent proposed openstack/nova master: Delete the placement code https://review.openstack.org/618215
03:38:41 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove Placement API reference https://review.openstack.org/614437
04:36:46 openstackgerrit Ghanshyam Mann proposed openstack/nova master: DNM: Testing nova gate on Bionic (Ubuntu LTS 18.04) https://review.openstack.org/620454
06:00:16 gmann nova api office hour
06:00:33 gmann #startmeeting nova api
06:00:34 openstack Meeting started Wed Nov 28 06:00:33 2018 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.
06:00:35 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
06:00:37 openstack The meeting name has been set to 'nova_api'
06:00:45 gmann PING List: gmann, alex_xu
06:00:48 gmann who all here today
06:01:06 gmann we are starting office hour after long time...
06:04:49 gmann seems alex_xu not here. i will do some bug triage during this office hour.
06:05:24 gmann some update- i have updated the subteam tracking etherpad with latest updates - Section API- https://etherpad.openstack.org/p/stein-nova-subteam-tracking
06:45:11 openstackgerrit jichenjc proposed openstack/nova master: Validate security group in API layer https://review.openstack.org/620473
06:56:34 gmann did 2 bug triage and 3rd in progress. will send the updates on ML. ending the office hour
06:56:38 gmann #endmeeting
06:56:40 openstack Meeting ended Wed Nov 28 06:56:38 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
06:56:41 openstack Minutes: http://eavesdrop.openstack.org/meetings/nova_api/2018/nova_api.2018-11-28-06.00.html
06:56:42 openstack Minutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2018/nova_api.2018-11-28-06.00.txt
06:56:43 openstack Log: http://eavesdrop.openstack.org/meetings/nova_api/2018/nova_api.2018-11-28-06.00.log.html
07:17:59 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Per-instance serial number https://review.openstack.org/619953
07:40:49 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Bump compute service to indicate attach/detach root volume is supported https://review.openstack.org/614750
07:41:45 openstackgerrit Vieri proposed openstack/python-novaclient master: add python 3.6 unit test job https://review.openstack.org/620509
07:58:32 kashyap artom: Thanks for the review.
07:59:07 alex_xu gmann: from this https://docs.openstack.org/nova/rocky/user/block-device-mapping.html#block-device-mapping-v2, we don't have deleted_on_termination param for bdmv2. Also we don't have that param for bdmv2 in nova cli. but I can pass that param by the API directly, does it support from the beginning or we leak something?
08:02:18 kashyap alex_xu: Hi, when you get a moment, mind having a look at this: https://review.openstack.org/#/c/620327
08:04:05 alex_xu kashyap: got it, will try
08:04:32 gmann alex_xu: humm, checking
08:04:41 kashyap alex_xu: Thanks
08:05:55 alex_xu kashyap: np
08:06:07 alex_xu gmann: thanks
08:07:07 alex_xu gmann: actually, I'm reviewing this spec https://review.openstack.org/#/c/580336
08:09:09 gmann alex_xu: delete_on_termination is bdmv1 attribute which is allowed for bdmv2 also
08:09:40 gmann alex_xu: you can see that in doc you mentioned also under Block device mapping v1 (aka legacy)¶ section
08:14:07 alex_xu gmann: so v2 inhertis all the attributes from v1, right?
08:15:41 gmann alex_xu: yeah, https://github.com/openstack/nova/blob/62245235bc15da6abcdfd3df1c24bd856d69fbb4/nova/api/openstack/compute/schemas/servers.py#L90
08:18:30 alex_xu gmann: it is strange that we don't have delete_on_termination on the CLI
08:18:54 gmann alex_xu: humm it is error ?
08:19:51 alex_xu gmann: i don't know
08:24:39 gmann alex_xu: i can see it is supported in CLI - https://github.com/openstack/python-novaclient/blob/58b3ac457aa817da28c757b4845bc39e565139dd/novaclient/v2/shell.py#L138
08:36:37 openstackgerrit Yikun Jiang proposed openstack/nova master: Use new ``initial_xxx_allocation_ratio`` CONF https://review.openstack.org/602804
08:36:37 openstackgerrit Yikun Jiang proposed openstack/nova master: Change the default values of XXX_allocation_ratio https://review.openstack.org/602803
09:22:20 openstackgerrit Ghanshyam Mann proposed openstack/nova-specs master: Spec for API inconsistency cleanup https://review.openstack.org/603969

Earlier   Later