Thursday, 2020-10-15

*** macz_ has joined #openstack-meeting-300:15
*** macz_ has quit IRC00:20
*** artom has quit IRC00:28
*** jamesmcarthur has quit IRC00:36
*** jamesmcarthur has joined #openstack-meeting-300:36
*** jamesmcarthur has quit IRC00:41
*** jamesmcarthur has joined #openstack-meeting-300:49
*** macz_ has joined #openstack-meeting-301:09
*** macz_ has quit IRC01:14
*** jamesmcarthur has quit IRC01:19
*** jamesmcarthur has joined #openstack-meeting-301:20
*** jamesmcarthur has quit IRC01:24
*** jamesmcarthur has joined #openstack-meeting-301:43
*** jamesmcarthur has quit IRC02:45
*** jamesmcarthur has joined #openstack-meeting-302:46
*** jamesmcarthur has quit IRC02:51
*** jamesmcarthur has joined #openstack-meeting-303:14
*** jamesmcarthur has quit IRC04:33
*** jamesmcarthur has joined #openstack-meeting-304:34
*** jamesmcarthur has quit IRC04:37
*** jamesmcarthur has joined #openstack-meeting-304:37
*** jamesmcarthur has quit IRC05:12
*** jamesmcarthur has joined #openstack-meeting-305:12
*** jamesmcarthur has quit IRC05:16
*** jamesmcarthur has joined #openstack-meeting-305:47
*** jamesmcarthur has quit IRC05:59
*** slaweq has joined #openstack-meeting-306:35
*** ralonsoh has joined #openstack-meeting-306:53
*** e0ne has joined #openstack-meeting-307:24
*** jamesmcarthur has joined #openstack-meeting-307:38
*** jamesmcarthur has quit IRC07:41
*** tosky has joined #openstack-meeting-307:42
*** jamesmcarthur has joined #openstack-meeting-307:49
*** jamesmcarthur has quit IRC08:43
*** jamesmcarthur has joined #openstack-meeting-308:44
*** jamesmcarthur has quit IRC08:49
*** jamesmcarthur has joined #openstack-meeting-309:07
*** jamesmcarthur has quit IRC09:12
*** jamesmcarthur has joined #openstack-meeting-310:20
*** jamesmcarthur has quit IRC10:25
*** belmoreira has joined #openstack-meeting-311:38
*** raildo has joined #openstack-meeting-312:06
*** artom has joined #openstack-meeting-312:34
*** macz_ has joined #openstack-meeting-312:40
*** macz_ has quit IRC12:45
*** jamesmcarthur has joined #openstack-meeting-312:45
*** jamesmcarthur has quit IRC13:49
*** jeremyfreudberg_ has joined #openstack-meeting-313:55
jeremyfreudberg_#startmeeting sahara14:00
openstackMeeting started Thu Oct 15 14:00:33 2020 UTC and is due to finish in 60 minutes.  The chair is jeremyfreudberg_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: sahara)"14:00
openstackThe meeting name has been set to 'sahara'14:00
*** jeremyfreudberg_ is now known as jeremyfreudberg14:00
*** jeremyfreudberg is now known as jeremyfreudberg_14:01
jeremyfreudberg_#chair jeremyfreudberg14:01
openstackWarning: Nick not in channel: jeremyfreudberg14:01
openstackCurrent chairs: jeremyfreudberg jeremyfreudberg_14:01
*** jeremyfreudberg_ is now known as jeremyfreudberg14:01
jeremyfreudbergo/14:01
jeremyfreudbergtosky: are you around?14:04
toskyhi!14:05
jeremyfreudberg#topic open discussion14:05
*** openstack changes topic to "open discussion (Meeting topic: sahara)"14:05
jeremyfreudbergjust want to say for the record that i worked on https://storyboard.openstack.org/#!/story/2008233 but the issue could not be reproduced14:06
*** jamesmcarthur has joined #openstack-meeting-314:06
jeremyfreudbergrelated to that, we lack any documentation about the necessary environment variables for devstack to clone sahara-plugin-* from stable branch vs master14:06
jeremyfreudbergso i will document it when i find some time14:07
toskyoh, good point14:07
jeremyfreudbergyeah, it took me a minute to realize it14:09
toskyI've noticed your comments, and I was kind of sure that was the result (no real bug)14:09
jeremyfreudbergand i only realized it because master is python3-only but i was installing train on ubuntu 18 which is python214:09
jeremyfreudberganyway, we can wait for the user to come back any hopefully agree with my assessment14:10
jeremyfreudberg*and14:10
jeremyfreudbergokay, is there anything else we need to discuss14:12
jeremyfreudberganything about releases?14:12
toskyit seems the requirements fixes in victoria haven't landed in the stable released version14:13
toskyso we may do a follow-up soon-ish14:13
jeremyfreudbergright14:13
jeremyfreudbergokay, i guess we can close14:16
jeremyfreudberg#endmeeting14:18
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:18
toskythere was also a request for a pike sahara image on the list14:18
openstackMeeting ended Thu Oct 15 14:18:50 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2020/sahara.2020-10-15-14.00.html14:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2020/sahara.2020-10-15-14.00.txt14:18
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2020/sahara.2020-10-15-14.00.log.html14:18
toskybut I answered :)14:18
*** jeremyfreudberg has left #openstack-meeting-314:22
*** macz_ has joined #openstack-meeting-314:28
*** macz_ has quit IRC14:33
*** macz_ has joined #openstack-meeting-315:01
*** belmoreira has quit IRC15:18
*** mlavalle has joined #openstack-meeting-315:22
*** jamesmcarthur has quit IRC15:44
*** jamesmcarthur has joined #openstack-meeting-315:50
*** jamesmcarthur has quit IRC15:50
*** jamesmcarthur has joined #openstack-meeting-315:50
*** elod has joined #openstack-meeting-315:56
*** jamesmcarthur has quit IRC15:57
*** jamesmcarthur has joined #openstack-meeting-315:57
gibi#startmeeting nova16:00
openstackMeeting started Thu Oct 15 16:00:09 2020 UTC and is due to finish in 60 minutes.  The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: nova)"16:00
openstackThe meeting name has been set to 'nova'16:00
gibio/16:00
melwitto/16:00
dansmitho/16:00
bauzas\o16:00
elodo/16:01
gibilets get started16:01
gibi#topic Bugs (stuck/critical)16:01
*** openstack changes topic to "Bugs (stuck/critical) (Meeting topic: nova)"16:01
gibiNo critical bugs16:01
gibi#link 6 new untriaged bugs (0 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New16:01
gibiis there any specific bug we need to talk about?16:02
melwittI have a bug to bring up16:02
artomo/16:02
melwitthttps://bugs.launchpad.net/nova/+bug/1799298 is two years old but recently flagged as a security issue downstream,16:02
openstackLaunchpad bug 1799298 in OpenStack Compute (nova) rocky "Metadata API cross joining instance_metadata and instance_system_metadata" [Medium,Triaged]16:02
melwittjust wanted to bring it to attention and ask for help in solving it as it does not look straightforward based on the past bug comments16:03
dansmithwe don't join those tables for pulling the instance,16:03
dansmithand haven't since icehouse-ish16:04
dansmithis this a query specifically that metadata uses that is still doing a join?16:04
melwittthere is a query and they confirmed it's this one... and they said they also found it present in train16:05
gibireading the bug mriedem said that the instance password is needed from the system_metadata16:06
dansmithright, but when we load an instance now, we actually query the instance, then query metadata, then sysmeta, and squash them together16:07
dansmiththat's what instances_fill_metadata() is16:07
melwittwould this not do the join with system_metadata? https://github.com/openstack/nova/blob/master/nova/api/metadata/base.py#L67516:08
dansmithso I'm wondering if there's a specific db api method that metadata uses to pull the instance, which is somehow letting those columns get into the initial query, but shouldn't?16:08
dansmithmelwitt: well, those are supposed to be treated differently down the stack,16:09
dansmiththey are for instance_get(), but my point is maybe this metadata-only query is bypassing that somehow16:09
melwittack16:09
dansmithanyway, we should probably not derail the meeting and can discuss in -nova16:10
melwittyep, thanks, at least there's some thread to pull now16:11
gibiOK16:11
gibiis there any other bug we need to talk about?16:11
gibi#topic Release Planning16:12
*** openstack changes topic to "Release Planning (Meeting topic: nova)"16:12
gibiVictoria has been released16:12
gibiThank you all for your valuable contributions16:12
gibimaster is now fully open for Wallaby16:12
gibiand we should focus on reviewing incoming specs and preparing for the PTG16:12
gibiI will create the wallaby runway etherpad tomorrw16:13
gibianything else about Victoria or Wallaby?16:13
gibi#topic Stable Branches16:14
*** openstack changes topic to "Stable Branches (Meeting topic: nova)"16:14
gibielod left comments on the wiki ...16:14
gibi"Victoria is now a fully normal stable branch, and the normal stable policy now applies."16:15
gibistable/stein will transition to Extended Maintenance in 2020-11-1116:15
gibishould prepare a final release from Stein16:15
gibi consider which patches should be part of the final release16:15
gibicurrent list of patches: https://etherpad.opendev.org/p/nova-stable-stein-em16:15
elodyepp, that's all, actually,16:16
elodI'll focus on Stein in the coming weeks16:16
gibithanks16:16
elodlet me know if you see any patch that should be definitely be part of the final release16:16
elodnp16:16
gibi#topic Sub/related team Highlights16:17
*** openstack changes topic to "Sub/related team Highlights (Meeting topic: nova)"16:17
gibiskipping API as gmann cannot join today16:17
gibiLibvirt (bauzas)16:17
gibiI guess the silence means no news16:19
gibi#topic PTG and Forum planning16:19
*** openstack changes topic to "PTG and Forum planning (Meeting topic: nova)"16:19
gibiNext week is Summit week: #link https://www.openstack.org/summit/2020/summit-schedule16:19
gibiWeek after next week is PTG # link https://etherpad.opendev.org/p/nova-wallaby-ptg16:20
gibiis there anything we need to discuss regarding these events?16:21
gibiI will focus my time on Fishbowls during next week16:21
gibi#topic Open discussion16:22
*** openstack changes topic to "Open discussion (Meeting topic: nova)"16:22
gibiwe have one topic from stephenfin16:22
gibi(stephenfin) Specless BP approval for https://blueprints.launchpad.net/nova/+spec/compact-db-migrations-wallaby16:22
gibitl;dr: I want to go at least as far as Train, and then rework any Ussuri or Victoria migrations to use alembic. Initial cleanup work available at https://review.opendev.org/#/q/topic:bp/compact-db-migrations-wallaby16:22
gibican we approve this specless bp?16:23
dansmithI suspect this will be a lot more work than it seems,16:24
artomMy paranoid nature is immediately skeptical of changing something as crucial as DB schema in stable releases16:24
gibiartom: this compacts the old migration on master16:24
dansmithas my experience from briefly touching alembic in glance is that the replicability of the schema stuff can get weird in things like unit tests16:24
dansmithartom: right, not actually touching older releases,16:24
artomAh, sorry, *facepalm*16:25
dansmithjust squashing everything into state as of train16:25
melwittyeah, I made a note on the ptg etherpad but basically I know we've talked about this before, and IIRC the conclusion was it wouldn't be a good idea to convert everything to alembic. but I'd have to go see if I can find artifacts from those discussions16:25
gibidansmith: as far as I understand the current bp only propose the compaction not the alembic migration16:25
dansmithgibi: yeah, but using alembic going forward right?16:25
dansmithmy point is just about converting all our db fixture stuff to alembic, multi-cells and all16:26
gibidansmith: this would enable to move to alembic, yes16:26
gibidansmith: but that move would be still a separate bp16:26
dansmithI totally recognize the need to compact, but I want to make sure we're super sure that the schema ends the same as it is now, so I hope we'll be very diligent about approving that compaction only after lots of review16:26
bauzasgibi: sorry, parenting urgent issue16:26
dansmithgibi: ack, okay16:26
bauzasgibi: nothing to report16:27
gibibauzas: OK, thanks16:27
dansmithgibi: if the specless bp is just for the compaction, then that's fine with me16:27
gibidansmith: I do suggest to talk about the alembic plans during the PTG16:27
bauzasI think there are two asks16:27
bauzas#1 for packing DB upgrades16:28
artomdansmith, we could do something with tests, I think. This stuff is supposed to be 100% deterministic, so... run the old uncompacted migrations, run the news one, starting the the exact same schema, and assert the resulting schema is the same?16:28
bauzas#2 for using alembic16:28
bauzasfwiw, #1 seems good to me, but for #2, meh16:28
dansmithartom: yes16:28
artomThis wouldn't apply to data migrations, right?16:28
dansmithartom: my point is, it's easy to say "the tests pass that used to pass, so they must be identical" and that's not enough,16:28
bauzasactually, I have the same opinion than dansmith16:28
dansmithartom: we need to make sure they emit the same schema16:28
dansmithartom: this has nothing to do with data migrations16:29
artomAck16:29
artomSo, if we can have a one-time test that asserts the new thing results in the same schema as the old thing, I don't see why not16:30
dansmiththat's what I'm saying16:30
artomThat's what *I'm* saying ;)16:30
dansmithliterally diff the mysqldump from a run generated with the current, and compacted thing, and they should be zero16:30
bauzasare we discussing about how to compacting the DB upgrades ? then yes ^16:31
dansmithbauzas: how to *verify* the compaction16:31
bauzashow to verify* indeed, my bad16:32
gibiI dont see any objection against approving stephenfin's bp with a comment that it only covers the compaction of the migrations and not the alembic move.16:32
bauzas++16:32
gibido I see it right?16:32
bauzasgood luck tho16:32
bauzasI don't think it will be simple16:32
bauzasbut meh16:32
dansmithgibi: yes, just footnote that we should be super review-y on the compaction please16:33
gibidansmith: ack I will add that comment too16:33
gibinothing else on the agenda for toda16:34
gibiy16:34
gibianything else in the room to discuss?16:34
* artom throws a small flat round object16:34
gibiwhat do you have there artom ? :)16:35
artomA pun is what I have16:35
gibi:D16:35
gibithen thanks for joining today16:36
gibio/16:36
gibi#endmeeting16:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:36
openstackMeeting ended Thu Oct 15 16:36:37 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-10-15-16.00.html16:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-10-15-16.00.txt16:36
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-10-15-16.00.log.html16:36
elodthanks o/16:37
*** lpetrut has joined #openstack-meeting-316:44
*** lpetrut has quit IRC16:59
*** jamesmcarthur has quit IRC17:01
*** elod has left #openstack-meeting-317:06
*** jamesmcarthur has joined #openstack-meeting-317:07
*** Vadmacs has joined #openstack-meeting-318:16
*** artom has quit IRC18:22
*** artom has joined #openstack-meeting-318:22
*** ralonsoh has quit IRC18:22
*** jamesmcarthur has quit IRC18:31
*** jamesmcarthur has joined #openstack-meeting-318:39
*** Vadmacs has quit IRC20:36
*** jamesmcarthur has quit IRC21:05
*** raildo has quit IRC21:13
*** jamesmcarthur has joined #openstack-meeting-321:15
*** jamesmcarthur has quit IRC21:22
*** jamesmcarthur has joined #openstack-meeting-321:24
*** jamesmcarthur has quit IRC21:25
*** jamesmcarthur has joined #openstack-meeting-321:25
*** slaweq has quit IRC21:31
*** jamesmcarthur has quit IRC21:48
*** slaweq has joined #openstack-meeting-322:22
*** slaweq has quit IRC22:38
*** macz_ has quit IRC23:03
*** mlavalle has quit IRC23:23
*** tosky has quit IRC23:23
*** jamesmcarthur has joined #openstack-meeting-323:46

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!