Thursday, 2019-05-30

*** lseki has quit IRC00:03
*** yamamoto has quit IRC00:04
*** wwriverrat has joined #openstack-meeting00:04
*** yamamoto has joined #openstack-meeting00:08
*** slaweq has joined #openstack-meeting00:11
*** gyee has quit IRC00:14
*** slaweq has quit IRC00:16
*** yamamoto has quit IRC00:26
*** hongbin has quit IRC00:28
*** markvoelker has quit IRC00:32
*** yamamoto has joined #openstack-meeting00:35
*** yamamoto has quit IRC00:42
*** yaawang has quit IRC00:46
*** yaawang has joined #openstack-meeting00:47
*** dtrainor has quit IRC00:47
*** dtrainor has joined #openstack-meeting00:54
*** ianychoi has quit IRC00:56
*** carloss has quit IRC00:56
*** slaweq has joined #openstack-meeting01:11
*** wwriverrat has quit IRC01:12
*** slaweq has quit IRC01:16
*** ykatabam has quit IRC01:17
*** yamamoto has joined #openstack-meeting01:19
*** bbowen has joined #openstack-meeting01:21
*** markvoelker has joined #openstack-meeting01:21
*** ykatabam has joined #openstack-meeting01:22
*** yamamoto has quit IRC01:29
*** whoami-rajat has joined #openstack-meeting01:35
*** lbragstad has quit IRC01:40
*** Liang__ has joined #openstack-meeting01:46
*** Liang__ is now known as LiangFang01:46
*** yamahata has quit IRC01:47
*** iyamahat_ has quit IRC01:53
*** ykatabam has quit IRC02:02
*** ykatabam has joined #openstack-meeting02:31
*** ykatabam has quit IRC02:36
*** ykatabam has joined #openstack-meeting02:48
*** yamamoto has joined #openstack-meeting03:38
*** imsurit_ofc has joined #openstack-meeting04:03
*** iyamahat has joined #openstack-meeting04:08
*** slaweq has joined #openstack-meeting04:11
*** slaweq has quit IRC04:16
*** ricolin has joined #openstack-meeting04:45
*** pcaruana has joined #openstack-meeting05:00
*** igordc has joined #openstack-meeting05:15
*** sridharg has joined #openstack-meeting05:20
*** ricolin has quit IRC05:25
*** akhil_jain has joined #openstack-meeting05:27
*** ricolin has joined #openstack-meeting05:28
*** enriquetaso has quit IRC05:29
*** jgriffith has quit IRC05:34
*** absubram has joined #openstack-meeting05:35
*** jgriffith has joined #openstack-meeting05:40
*** absubram has quit IRC05:50
*** radeks has joined #openstack-meeting05:59
*** igordc has quit IRC06:01
*** lpetrut has joined #openstack-meeting06:02
*** armax has quit IRC06:02
*** radeks has quit IRC06:05
*** slaweq has joined #openstack-meeting06:06
*** radeks has joined #openstack-meeting06:10
*** plutoinmii has joined #openstack-meeting06:11
*** plutoinmii has quit IRC06:11
*** radeks_ has joined #openstack-meeting06:14
*** plutoinmii has joined #openstack-meeting06:15
*** radeks has quit IRC06:16
*** radeks_ has quit IRC06:19
*** radeks_ has joined #openstack-meeting06:20
*** efried1 has joined #openstack-meeting06:21
*** plutoinmii has quit IRC06:22
*** efried has quit IRC06:23
*** efried1 is now known as efried06:23
*** ricolin has quit IRC06:26
*** plutoinmii has joined #openstack-meeting06:48
*** boxiang has joined #openstack-meeting06:51
*** ianychoi has joined #openstack-meeting06:57
ianychoiHello! Anyone for I18n meeting?07:00
*** markvoelker has quit IRC07:01
*** markvoelker has joined #openstack-meeting07:01
*** ykatabam has quit IRC07:03
*** markvoelker has quit IRC07:06
plutoinmiiyes07:06
plutoinmiithis is Horace.07:06
plutoinmiigood afternoon, Ian.07:06
plutoinmiiw07:06
plutoinmiiianychoi: good afternoon.07:07
ianychoiplutoinmii, HI!07:07
plutoinmiifirst time to join IRC meeting.07:07
plutoinmiiw07:07
ianychoiNice to see u in IRC!07:08
plutoinmiii sent meeting notice to openstack translators wechat group, but not sure who will be online today.07:08
ianychoiThat's fine :)07:09
ianychoi(I am finding some commands... to open a meeting)07:09
plutoinmiisure..take your time.07:09
plutoinmiiw07:09
ianychoi#startmeeting openstack_i18n_meeting07:09
openstackMeeting started Thu May 30 07:09:48 2019 UTC and is due to finish in 60 minutes.  The chair is ianychoi. Information about MeetBot at http://wiki.debian.org/MeetBot.07:09
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:09
*** openstack changes topic to " (Meeting topic: openstack_i18n_meeting)"07:09
openstackThe meeting name has been set to 'openstack_i18n_meeting'07:09
ianychoiI have finally found it :)07:09
ianychoi#topic open discussion07:10
*** openstack changes topic to "open discussion (Meeting topic: openstack_i18n_meeting)"07:10
ianychoiplutoinmii, so are u in Beijing? :)07:10
*** rcernin has quit IRC07:10
*** helenafm has joined #openstack-meeting07:10
plutoinmiiianychoi: I am in Shanghai.07:11
plutoinmii:-)07:11
ianychoiAha I see :)07:11
ianychoiAlthough it is so near from Korea, I have never been to China unfortunately.07:11
plutoinmiicome to Shanghai this Nov!!07:12
plutoinmiiw07:12
ianychoiSure - I have strong willingness to go there :)07:12
plutoinmiihope there is an i18n meeting on PTG this time as well.07:12
plutoinmiiw07:12
ianychoiFor I18n team, Daisy previously initiated translation team in OpenStack world07:12
plutoinmiitold by the previous China interface a little bit. I got chance to have a call with Daisy several months ago.07:13
ianychoiWow :) How is she?07:13
ianychoiI joined in the translation team from 2014 - at that time I think we all translation team have communicated well.07:13
plutoinmiiShe is good, still in IBM. I was told her new focus is about containers, and she is more focused in K8S recently.07:14
ianychoiAnd time goes... now I feel that I18n core governance and the governance in language teams have some distance.07:14
ianychoiGood I so miss her... :)07:15
plutoinmiiwasn't got the chance to experience the golden era of i18n team, but would like to learn a bit and support to  revive it.07:15
ianychoiSo, this release cycle, as PTL, I would like to have more communication with active translators how the team needs to continue.07:15
plutoinmiicurrently Chinese translators are not very active, I saw 1-2 are still responding.07:16
ianychoiThanks a lot for kind words :)07:16
plutoinmiiand also I am not sure the priority of the translation tasks and what the roadmap is.07:16
plutoinmiiianychoi: sure, agree to comminucate more.07:17
ianychoiWhen I experienced some previous release cycles - Mitaka, Newton, Ocata, Pike, Queens, and so on, there were some attendees on PTGs or Design Summits, so we had conversation for translation priorities.07:17
ianychoiUnfortunately, this PTG, I couldn't go there - Frank were there but we have not discussed a lot on translation priority07:18
plutoinmiido we generally translate the release note of each cycle? or what documentations we put on the list?07:18
ianychoiFor translation priority, generally, I18n team update on https://translate.openstack.org/07:18
plutoinmiigot it. i will take a look.07:18
ianychoiFor plans, it can be different by different categories.07:19
plutoinmiiTrain Dashboard translation07:19
plutoinmiiDocumentation translation Dashboard07:19
plutoinmiiI18n contributor guide translation07:19
plutoinmiithese are the three, right?07:20
ianychoiFor dashboards, since dashboards are in development during release cycle, some strings can be changed a lot.07:20
plutoinmiii see.07:20
ianychoiSo, generally, translators are more engaged on especially around Soft StringFreeze: https://releases.openstack.org/train/schedule.html07:20
ianychoiSoft StringFreeze means that development projects try to freeze strings as much as possible for documentation and translation.07:21
plutoinmiithese are useful info. thanks a lot!07:21
ianychoiAnd Hard StringFreeze means that strings will not changed without proper exception - if there are still more activities on translations, I can ask for projects e.g., please release RC2, RC3, and so on with more translation resources..07:22
plutoinmiii would like to summarize these basic info in Chinese and share in wechat group, so that others could understand basic working flow.07:23
ianychoiSo for dashboard translation, the best period would be from around Soft StringFreeze to one week / a few days before Hard StringFreeze07:23
*** ricolin has joined #openstack-meeting07:23
ianychoiThanks a lot :) If it is fine, please share via any blog (in Chinese should be fine) and share a link with I18n team :)07:24
plutoinmiidoes it matter is translation falls into after Hard StringFreeze?07:24
ianychoiAround Hard StringFreeze, project teams package software as a package (e.g., v12.0.0)07:24
plutoinmiiso translations will be packed in the package as well, and it would be not possible to change it afterwards?07:25
ianychoiIf translation lands after such package release, then I need to ask to project teams: e.g., please create a new branch (e.g., v12.0.1) including up to date translation07:25
plutoinmiigot it..07:25
plutoinmiiw07:25
ianychoiIdeally projects can handle but in reality, for example, the branch sources will be shared with Red Hat, Canonical, and so on.07:26
ianychoiThe vendor's update will be slower07:27
ianychoi(Not ideal explanation.. but I think it would be easy to understand to you, hopefully)07:27
plutoinmiiit does.07:28
ianychoiAnd.. for releasenotes, since versions are just increased, we only translate in master branch07:28
ianychoiSo anytime you can translate releasenotes07:28
ianychoiBut.. projects which have >=75% translations run sync jobs between Zanata and project repos07:28
plutoinmiiokay07:29
ianychoiAnd I need to sync with Foundation but I will share when user-survey needs to be translated :)07:30
ianychoi#action ianychoi will ask Foundation for user-survey translation07:30
ianychoiHow many members are in Chinese wechat group?07:31
plutoinmii9407:34
plutoinmiibut not many of them are responding.07:34
ianychoiAha I see07:35
plutoinmiii am seeing any chance if a solid plan or detailed task was set up so as to communicate in the group.07:35
plutoinmiiI feel they are not responding because they don't know how to start with, like me.07:35
plutoinmiiif more guidance or info could be shared, it might be helpful.07:36
ianychoiAha... thanks a lot - if it is possible, would you see https://docs.openstack.org/i18n/latest/zh_CN/index.html and share your feedback?07:36
ianychoiFor example, which is useful / not useful, which things need to be more described, and so on07:37
plutoinmiithis is good. I involved in part of the translation to this guide, I think.07:37
plutoinmiiI will take a look and share feedback.07:37
plutoinmiishould I create an "action" as well? :-)07:38
ianychoiNot should but it would be so nice :)07:40
plutoinmii#action plutoinmii share feedback after reviewing zh_CN translation guide07:40
ianychoiThank you :)07:42
plutoinmiino problem.07:42
ianychoiAnd for official team -> working group, do you have any question?07:43
plutoinmiiwhat would be the difference between current team and working group.07:44
ianychoi#link https://docs.openstack.org/contributors/common/governance.html07:45
ianychoiI think this link explain better than my previous explanation through e-mail07:45
plutoinmiiWG = SIG?07:46
ianychoiyep07:46
plutoinmiiSIG will not get space on PTG?07:47
ianychoiSome active SIGs can get a space - I am not sure the detail logistics but we can say that "Every official projects should get space, and SIGs might have space"07:47
ianychoiHonestly, there might have little difference on detail activities I believe.07:48
plutoinmiiyes, noticed there is a list of activity guarantees as a project team instead of working group.07:49
ianychoiBut, we might have weaker relationship with Technical Committee07:49
plutoinmiii am okay with it and have no question to operate as a working group.07:49
*** toabctl has quit IRC07:50
ianychoiAnd.. my worry is related with some change on a statement "Translation >=300 words would get ATC"07:50
ianychoiThis might be removed07:50
ianychoiAnd.. one more imagination might be there might have no PTL election activities :(07:51
plutoinmiiright...these are all projects team guaranteed.07:51
plutoinmiihow many translators in total around i18n team?07:52
plutoinmiiglobally.07:52
ianychoiI don't have up-to-date statistics but https://docs.openstack.org/i18n/latest/atc-stats.html#train-cycle might be helpful :)07:53
*** priteau has joined #openstack-meeting07:53
plutoinmiithis is helpful. I see more zh_CN translators than I've thought.07:54
plutoinmiiw07:54
ianychoi:)07:55
ianychoiBut as you see, translation ratio is getting decreased unfortunately07:56
ianychoiplutoinmii, it is really great to see you!07:57
plutoinmiisame here! ianychoi07:58
plutoinmiithanks for sharing these guidance and info with me, it is a good start for me.07:58
ianychoiI18n team has IRC meetings weekly but alternating time - next week it will start from midnight (your timezone) but two weeks later it will start the same as today07:58
plutoinmiiokay.07:59
plutoinmiii will see which timeslot best works for me.07:59
ianychoiplutoinmii, by the way, I am not sure but would it be fine if I nominate you as a language coordinator in Chinese team in Zanata?07:59
plutoinmiiyes, that is for sure.07:59
ianychoi(Or already language coordinator? not sure)08:00
plutoinmiivuuv asked if I could become the coordinator as he recently got working position change.08:00
ianychoiThanks a lot for today meeting! I would like to close this meeting if there are not no more issues08:00
ianychoiAha.. vuuv.. I see08:00
plutoinmiii said yes, but not sure how to operate it or announce it.08:00
ianychoiI thought you were mentioning zzxwill08:00
plutoinmiibut would like to help on coordinating the translation effort.08:01
ianychoiYep fine - a existing coordinator asks to you and you share your willingness here :)08:01
ianychoiI will share also via I18n mailing list - would it be okay?08:01
ianychoi(closing for future possible meetings)08:03
ianychoi#endmeeting08:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:03
openstackMeeting ended Thu May 30 08:03:04 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2019/openstack_i18n_meeting.2019-05-30-07.09.html08:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2019/openstack_i18n_meeting.2019-05-30-07.09.txt08:03
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2019/openstack_i18n_meeting.2019-05-30-07.09.log.html08:03
ianychoiplutoinmii, thanks a lot! :)08:03
plutoinmiisounds good to me. nice to talk to you, ianychoi08:03
plutoinmiikeep in touch08:03
ianychoiplutoinmii, sure!08:04
*** baojg has joined #openstack-meeting08:09
*** rossella_s has joined #openstack-meeting08:13
*** baojg has quit IRC08:14
*** iyamahat has quit IRC08:28
*** Lucas_Gray has joined #openstack-meeting08:29
*** ykatabam has joined #openstack-meeting08:39
*** plutoinmii has quit IRC08:46
*** baojg has joined #openstack-meeting08:50
*** LiangFang has quit IRC08:56
*** markvoelker has joined #openstack-meeting09:02
*** ricolin has quit IRC09:09
*** ykatabam has quit IRC09:14
*** kopecmartin|off is now known as kopecmartin09:17
*** panda is now known as panda|ruck09:17
*** ociuhandu has joined #openstack-meeting09:20
*** Lucas_Gray has quit IRC09:32
*** yamamoto has quit IRC09:35
*** markvoelker has quit IRC09:35
*** Lucas_Gray has joined #openstack-meeting09:39
*** electrofelix has joined #openstack-meeting09:44
*** e0ne has joined #openstack-meeting09:52
*** boxiang has quit IRC09:55
*** yamamoto has joined #openstack-meeting10:25
*** yamamoto has quit IRC10:25
*** yamamoto has joined #openstack-meeting10:25
*** yamamoto has quit IRC10:30
*** sridharg has quit IRC10:32
*** bbowen has quit IRC10:37
*** sridharg has joined #openstack-meeting10:45
*** yamamoto has joined #openstack-meeting10:51
*** Lucas_Gray has quit IRC11:05
*** njohnston has joined #openstack-meeting11:06
*** rcernin has joined #openstack-meeting11:11
*** JangwonLee_ has joined #openstack-meeting11:33
*** JangwonLee has quit IRC11:37
*** imsurit_ofc has quit IRC11:46
*** bbowen has joined #openstack-meeting11:48
*** _erlon_ has joined #openstack-meeting11:51
*** baojg has quit IRC11:53
*** Lucas_Gray has joined #openstack-meeting11:56
*** lseki has joined #openstack-meeting11:58
*** priteau has quit IRC12:01
*** priteau has joined #openstack-meeting12:04
*** raildo has joined #openstack-meeting12:05
*** carloss has joined #openstack-meeting12:10
*** rcernin has quit IRC12:10
*** Lucas_Gray has quit IRC12:18
*** Lucas_Gray has joined #openstack-meeting12:18
*** niceplace has quit IRC12:26
*** niceplace has joined #openstack-meeting12:29
*** yamamoto has quit IRC12:29
*** priteau has quit IRC12:36
*** gmann has joined #openstack-meeting12:46
*** Lucas_Gray has quit IRC12:54
*** jaypipes has joined #openstack-meeting12:54
*** priteau has joined #openstack-meeting13:00
*** Lucas_Gray has joined #openstack-meeting13:00
*** lbragstad has joined #openstack-meeting13:02
*** mriedem has joined #openstack-meeting13:02
*** eharney has joined #openstack-meeting13:05
*** cheng1__ has joined #openstack-meeting13:09
*** takashin has joined #openstack-meeting13:19
*** priteau has quit IRC13:23
*** pcaruana has quit IRC13:23
*** yamamoto has joined #openstack-meeting13:29
*** Liang__ has joined #openstack-meeting13:35
*** cheng1__ has quit IRC13:45
*** artom has quit IRC13:46
*** akhil_jain has quit IRC13:46
*** pcaruana has joined #openstack-meeting13:47
*** enriquetaso has joined #openstack-meeting13:50
*** jangutter has joined #openstack-meeting13:50
*** artom has joined #openstack-meeting13:55
*** johnthetubaguy has joined #openstack-meeting13:57
efried#startmeeting nova14:00
openstackMeeting started Thu May 30 14:00:13 2019 UTC and is due to finish in 60 minutes.  The chair is efried. 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: nova)"14:00
openstackThe meeting name has been set to 'nova'14:00
mriedemo/14:00
takashino/14:00
gmanno/14:00
edleafe\o14:00
gibio/14:00
artomo/14:00
johnthetubaguyo/14:01
*** cdent has joined #openstack-meeting14:01
efried#link agenda https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting14:01
stephenfino/14:01
cdento/14:01
efried#topic Last meeting14:02
efried#link Minutes from last meeting: http://eavesdrop.openstack.org/meetings/nova/2019/nova.2019-05-23-21.00.html14:02
*** openstack changes topic to "Last meeting (Meeting topic: nova)"14:02
efriedI think the only update from here is to mention that https://blueprints.launchpad.net/nova/+spec/remove-consoleauth got the necessary federal background check and has now been approved.14:03
efriedstephenfin: just noticed this isn't tagged against a release - assume you're planning to do this in Train?14:03
stephenfin(y)14:03
efriedk, fixed14:03
efriedanything else from last meeting?14:03
efried#topic Release News14:04
*** openstack changes topic to "Release News (Meeting topic: nova)"14:04
efriedI'm thinking it might be a good idea to do a spec scrub soon14:04
stephenfinOoh, yes please14:05
* johnthetubaguy nods14:05
cdentya14:05
efriedHow does next Tuesday grab y'all?14:05
mriedemwfm14:05
gibimostly wfm14:05
gmann+114:06
efried#action efried to post on ML re spec review sprint Tuesday June 4th14:06
efriedanything else release newsy?14:06
efried#topic Bugs (stuck/critical)14:06
efriedNo Critical bugs14:06
efried#link 82 new untriaged bugs (down 3 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New14:06
efried#link 10 untagged untriaged bugs (down 1 since the last meeting): https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW14:06
*** openstack changes topic to "Bugs (stuck/critical) (Meeting topic: nova)"14:06
*** martial has quit IRC14:07
efriedany bugs in the spotlight?14:07
efriedGate status14:07
efried#link check queue gate status http://status.openstack.org/elastic-recheck/index.html14:07
efried3rd party CI14:07
efried#link 3rd party CI status http://ciwatch.mmedvede.net/project?project=nova&time=7+days14:07
efriedzuul has seemed ungodsly slow lately14:07
mriedemwere we going to put up patches to log a warning on start of drivers that don't have 3rd party ci?14:07
mriedemat least xenapi,14:07
mriedemsounds like powervm is working on fixing their ci14:07
efriedI saw them put up a fix this morning, yah. Haven't caught up on the ML yet todya.14:08
efriedtoday14:08
cdentgee, guess what, vmware's ci was dead again and the keepers took days to notice :(14:08
cdent(but it's been kicked now)14:08
efriedmriedem: I remember we agreed to do that, yes. Who's volunteering to put up that patch?14:08
mriedemi suppose i can14:08
mriedemgive me an action item14:09
efried#action mriedem to propose patch logging warning that xenapi is not supported because no 3pCI14:09
efriedthanks mriedem14:09
stephenfinwarning or deprecating outright?14:09
artomI guess where's the line between no ci and half & maintained ci, but il leave that for the review14:10
mriedemstephenfin: i was going to start with a warning14:10
johnthetubaguyI spoke to bob ball about that, some neutron "bug" is blocking things working14:10
stephenfinI imagine that depends on whether there's anyone in the wild still using it. Might be worth bringing up on openstack-discuss14:10
efriedin any case we should be sure to add all the xen folks we know about to that review.14:10
stephenfinAh, okay. That's fair14:10
johnthetubaguybut, yeah, +1 the log message warning about removal14:10
mriedemartom: i don't know what you're asking, the xenserver ci has been dead for months14:11
johnthetubaguyyeah, its a dead ci at this point, we just merge the log message ASAP14:11
johnthetubaguyif it gets removed as the CI becomes stable again, then whoop whoop, go for it14:11
cdentya14:11
efriedcool, moving on.14:12
artommriedem, just saying that some 3pcis are more reactive than others14:12
efriedyeah, we're not deprecating every driver that goes red for two weeks14:12
efried....14:12
efriedAnyone know anything about zuul slowitude?14:12
artomlet's move on, I'll nitpick the review ;)14:12
mriedemefried: you'd have to ask infra, but i'm guessing fewer nodes14:12
mriedemhttp://grafana.openstack.org/d/T6vSHcSik/zuul-status?14:13
mriedemhttp://grafana.openstack.org/d/T6vSHcSik/zuul-status?orgId=1&fullscreen&panelId=2014:13
efriedthose are very pretty14:14
efriedfraid I don't really know what I'm looking at though14:14
efriedI guess what I really want is for somebody to say, "Yes, it's a known issue, and we're working on it, and it'll all be fixed very very soon, so your jobs will wait in queue for five minutes tops."14:15
mriedemclarkb: fungi: ^ if there are known infra issues can we get a summary in the ML?14:15
mriedemi.e. fewer nodes, lots of gate failures, etc14:15
cdentefried: I think to get that you're going to need to have your employer pony up a cloud :(14:15
mriedemhttp://status.openstack.org/elastic-recheck/data/integrated_gate.html is pretty good as far as classification rates14:16
efriedI've brought it up14:16
cdentme too. no luck.14:16
clarkbthe only known issue I know of is 1 of 12 zuul executors was misconfigured on its mirror node for about 12hours14:16
efriedyeah, I don't feel like the spurious failure rate is overly high. It's just taking forever to get a build through.14:16
clarkb10 hours i guess14:16
*** yamamoto has quit IRC14:16
efriedclarkb: So is it mainly just a matter of too many jobs, not enough hardware?14:16
clarkbotherwise if you want more throughput we need to run fewer jobs, or make jobs faster, or add resources14:17
artomif we're for real losing gate nodes, do we need to start a conversation about removing some tests?14:17
efriedSounds like a good idea to me.14:17
mriedemhere are some ideas14:17
mriedemhttps://review.opendev.org/#/c/650300/14:18
mriedemhttps://review.opendev.org/#/c/651865/14:18
mriedemi'm not cool with dropping tests, but being smarter about the jobs we use can be done (and i've tried to do)14:18
gmannwe discussed about decreasing the test run in QA PTG.14:18
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005871.html14:18
gmannfor nova it is just removing the swift test but for other proejct it will be good amount of improvement14:18
*** sean-k-mooney has joined #openstack-meeting14:19
efriedforgive my ignorance, but when I see the zuul report in a patch, does each line represent stuff having run on a separate node?14:19
mriedemyes14:20
fungior sometimes more than one14:20
clarkbalso I imagine that every round of cpu vulnerability fixes decreases our throuput by some amount14:20
artoma lot of our unit tests is test_python_works, as edleafe put it14:20
clarkbefried: possibly more than one per line too14:20
artombut improving that is a massive thankless job14:20
efriedso it seems like we could e.g. run all the pyXX unit tests on the same node, what harm?14:20
fungiwhat gain?14:20
clarkbefried: that isnt really much faster because nova already uses all cpus for the tests14:21
efriedFor those short-running tests, doesn't node setup & teardown consume most of the time?14:21
mriedemnot for unit tests14:21
sean-k-mooneyefried: not really14:21
efriedokay, never mind14:21
clarkbparticularly not for nova14:21
mriedemyou're thinking devstack + tempest14:21
fungicounter-intuitive. most of our node capacity is consumed by long-running jobs14:21
efried...and for those we don't want to share nodes because of weird interaction potentials and/or different configs...14:22
fungioptimizing the overhead on fast jobs only gets us a few percent, bar-napkin-math14:22
efriedokay, I'll stop14:22
efriedso one other thing we could consider14:22
efriedis changing the way we do patch series14:22
efriedaspiers and I were talking about this yesterday or the day before14:22
*** armax has joined #openstack-meeting14:23
gmanntempest-full run a lot and long . with optimized integrated-gate idea, it will make it faster for many projects14:23
sean-k-mooneyefried: how by using more fixup patches at the end? if so that would break the master is always deployable goal14:23
efriedthe way I've always seen it done, at least in nova, is if you have a series of changes, and you need to fix something on the bottom, you download the whole series, restack, fix the bottom, rebase the rest, and push the whole lot. The top N-1 patches are just rebase with no conflict, but they get to run again in the gate.14:23
efriedaspiers was being particularly gate-conservative by only fixing the one bottom patch and leaving the rest with the green tildes on them14:24
fungiyeah, i frequently avoid updating lower patches in a series and just comment that new change <whatever> addresses it14:24
sean-k-mooneyright that work in some cases14:24
clarkbthe others cant merge unless you push the new commit though14:24
fungidepends on what you need to fix14:24
clarkbbecause their parent will be outdated14:24
sean-k-mooneyclarkb: or you rely on gerrit to create a merge comit14:24
clarkbsean-k-mooney: doesnt work if it is a stack14:25
mriedemmy cross-cell resize gate enablement is at the end of a 40+ patch series, and without rebasing the whole thing i can't get a gate run on the live code14:25
mriedemso not going to work for me in that case14:25
*** yamamoto has joined #openstack-meeting14:25
fungiyeah, gerrit is extra picky about parent changes being in their final state in the dependency relationship14:25
*** yamamoto has quit IRC14:25
sean-k-mooneyclarkb: i think it does as long as it does not create a merge conflict14:25
clarkbnope gerrit refuses14:25
sean-k-mooneyclarkb: ok14:25
fungitry it sometime ;)14:25
*** sridharg has quit IRC14:25
*** yamamoto has joined #openstack-meeting14:26
fungigerrit considers an explicit parent which is out of date as a blocker14:26
mriedemfeels like this is tangential to the nova meeting...14:26
sean-k-mooneyfungi: i generally collect comments on the serires and address and rebase tehm all in one go14:26
*** sridharg has joined #openstack-meeting14:26
efriedpoint is, if we as a team try to adopt a more gate-conservative aspiers-ish approach to pushing patches, in or out of series, where possible and practical, it could help gate throughput.14:27
efriedmoving on14:27
efried#topic Reminders14:27
*** openstack changes topic to "Reminders (Meeting topic: nova)"14:27
efriedany?14:27
*** Liang__ has quit IRC14:28
efried#topic Stable branch status14:28
efried#link Stein regressions: http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005637.html14:28
efriedbug 1824435 still pending14:28
efried#link stable/stein: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/stein14:28
efried#link stable/rocky: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/rocky14:28
efried#link stable/queens: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/queens14:28
*** openstack changes topic to "Stable branch status (Meeting topic: nova)"14:28
openstackbug 1824435 in OpenStack Compute (nova) stein "fill_virtual_interface_list migration fails on second attempt" [Medium,Triaged] https://launchpad.net/bugs/182443514:28
mriedemsomeone else should probably work on ^14:29
mriedemi'm not14:29
mriedemi've got a stein release request up as well https://review.opendev.org/#/c/661376/14:29
mriedemjust waiting on the release gods14:29
*** artom has quit IRC14:29
*** artom has joined #openstack-meeting14:30
*** yamamoto has quit IRC14:30
sean-k-mooneythis is related to the force refresh change correct14:31
efriedmriedem: we could bump that hash at this point, had another couple patches merge, including the unversioning of reno docs14:31
mriedemhuh?14:31
sean-k-mooneymriedem: the force refresh of the instance info cache?14:31
mriedemi'm not sure what you're asking me14:31
sean-k-mooneywe added a migration to populate the virtual interface table for old instance14:31
mriedemthat upgrade ga bug?14:31
mriedemyes14:31
mriedemthere were a couple of upgrade issues from that14:31
mriedemsome fixed and waiting to release in that stein release patch,14:32
mriedemthat other one is still outstanding14:32
mriedemefried: i could rev, but i don't really care to and lose the +214:32
mriedemfor a docs fix14:32
efriedmriedem: nod, I +1d fwiw14:32
efriedanything else stable-y?14:33
efried#topic Sub/related team Highlights14:33
efriedPlacement (cdent)14:33
efried#link latest pupdate http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006601.html14:33
efried#link Spec for can_split https://review.opendev.org/#/c/658510/14:33
efried#link Spec for the rest of nested magic https://review.opendev.org/#/c/662191/14:33
efried#link spec for rg/rp mapping https://review.opendev.org/#/c/657582/14:33
*** openstack changes topic to "Sub/related team Highlights (Meeting topic: nova)"14:33
efriedcdent: your mic14:33
cdentthanks14:33
cdenttwo main things:14:34
cdentone is that there won't be a placement meeting any more, office hours are being arranged (see email)14:34
*** helenafm has quit IRC14:34
efried#link placement office hours http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006728.html14:34
cdentthe other is that can_split is proven to be problematic, an email has been sent out http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006726.html to ask ops if they'll live if we don't do it14:34
cdentpeople like artom or stephenfin if there are people in RH who should see that please pass it on14:35
cdentthat's all14:35
artomcdent, I can get our NFV PM eyes's on that I guess14:35
cdentthanks14:36
efriedPer links above, note that can_split is now in its own spec. The other, uncontroversial, bits of nested magic are in https://review.opendev.org/#/c/662191/14:36
artom(I thought NUMA stuff in placement kinda required can_split to work at all, but I'll read the email)14:36
efried^ this should be pretty close to approvable, if we could get some nova eyes to make sure it satisfies the use case.14:36
efriedartom: I'll be happy to TLDR the issue for you in -nova after this, if the email doesn't suffice.14:36
efried(I haven't read it yet)14:36
artomefried, ack, thanks :)14:36
efried(but probably can't see the forest for the trees anyway)14:36
artomAnd the squirrels. Don't forget the squirrels.14:37
cdentfreakin' everywhere14:37
efried(why must they play chicken with my tires?)14:37
efriedmoving on14:37
efriedAPI (gmann)14:37
efriedUpdates on ML- #link http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006699.html14:37
efriedgmann: anything to add?14:37
gmannother than that, policy improvement spec is under review #link https://review.opendev.org/#/c/547850/1914:38
gmannreplied on johnthetubaguy comments, we will put more details about exact check_str etc in spec14:38
efriedthanks gmann14:38
efried#topic Stuck Reviews14:38
*** openstack changes topic to "Stuck Reviews (Meeting topic: nova)"14:39
efriedany?14:39
*** njohnston has quit IRC14:39
mriedemhttps://review.opendev.org/#/c/579897/ came up yesterday14:39
mriedemnot sure if cern or ovh are going to pick it up again14:39
*** njohnston has joined #openstack-meeting14:40
mriedemsounds like mel wants a bp for it14:40
mriedemand should remove a lot of the nvidia specific language from the code comment,14:40
mriedembut otherwise jay dropped his -114:40
efriedit might be a helpful signal if ^ were represented as a -114:41
mriedemidk that it's really a feature,14:41
mriedemit's an existing support that only worked for linux guests14:41
mriedemthis makes it work for windows guests14:41
efriedand we could pester tssurya to see if cern is still interested in driving it14:42
sean-k-mooneyso i was previous +1 on that patch but stopped reviewing when it became political14:42
sean-k-mooneyit looks like its not in merge conflict so if we clean up the paperwork i think its fine to add14:43
sean-k-mooneyassuming they still want it14:43
mriedemanyway, we can move on, the action is to find an owner14:43
mriedemi'm sure cern and ovh forgot about it b/c they are already using it in production14:43
mriedemwe can move on...14:45
efried..okay..14:45
efried#topic Review status page (still NEW)14:45
efriedhttp://status.openstack.org/reviews/#nova14:45
efried#help Ideas for how we should use this?14:45
*** openstack changes topic to "Review status page (still NEW) (Meeting topic: nova)"14:45
efriedAs of last time, someone (sean-k-mooney?) figured out that you can hover over things to figure out how the scores are calculated14:46
mriedemi keep looking at https://review.opendev.org/#/c/361438 when you bring up that link,14:46
mriedemthe dependent neutron patch is abandoned,14:46
mriedemtherefore i'd like to abandon if unless someone (adrianc from mellanox?) is going to fix it14:46
efriedmriedem: ++, go ahead and abandon it please, it can always be restored if they care.14:46
mriedemi'll ask adrianc_ about it, or cfriesen14:47
efriedyou left that last comment over a month ago.14:47
efriedfair warning14:47
sean-k-mooneythe dependent patch is over 2 years old aswell14:48
sean-k-mooneyand was abandonded in feb 201714:49
mriedemok i abandoned it14:49
efriedthanks mriedem14:49
efriedSo I'm going to throw this out as a suggestion: It would be lovely if each nova team member would grab a patch from the top of that list - something with a 4-digit score - and figure out what needs to be done to make it go away (merge, abandon, whatever) and drive that.14:49
efriedmriedem: you're done for the week :)14:49
cdentten minute warning14:50
mriedemheh, i asked about https://review.opendev.org/#/c/489484 weeks ago too and never got a reply14:50
mriedemfrom bauzas14:50
cdentwhy not force abandon any over N days stale and let other people sort it out?14:50
efriedI don't have a problem core-abandoning patches that have .... yeah, like that ^14:50
cdentif it was important, itwill come back around14:50
sean-k-mooneymriedem: bauzas is on PTO today as its a holiday in france14:50
efriedlet's discuss the specifics of core-abandoning old stuff, separately.14:51
efriedso we can move on to14:51
efried#topic Open discussion14:51
*** openstack changes topic to "Open discussion (Meeting topic: nova)"14:51
*** gagehugo has joined #openstack-meeting14:51
efriedany?14:51
mriedemoh i guess it's the 3 month EU summer holiday season14:51
sean-k-mooneyyep14:51
sean-k-mooneyand no items form me14:51
efriedThanks all.14:52
efriedo/14:52
efried#endmeeting14:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:52
openstackMeeting ended Thu May 30 14:52:42 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2019/nova.2019-05-30-14.00.html14:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2019/nova.2019-05-30-14.00.txt14:52
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2019/nova.2019-05-30-14.00.log.html14:52
*** ricolin has joined #openstack-meeting14:53
*** takashin has left #openstack-meeting14:53
*** lpetrut has quit IRC14:57
*** nickthetait has joined #openstack-meeting14:58
gagehugo#startmeeting security15:00
openstackMeeting started Thu May 30 15:00:08 2019 UTC and is due to finish in 60 minutes.  The chair is gagehugo. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: security)"15:00
openstackThe meeting name has been set to 'security'15:00
gagehugo#link https://etherpad.openstack.org/p/security-agenda agenda15:00
gagehugoo/15:00
fungihi there15:00
nickthetaithey15:01
*** artom has quit IRC15:01
gagehugogive it a few minutes before we start, agenda is light this week so far15:01
*** artom has joined #openstack-meeting15:01
redrobot\o15:04
gagehugo#topic Open Discussion15:05
*** openstack changes topic to "Open Discussion (Meeting topic: security)"15:05
gagehugo#link https://duo.com/decipher/docker-bug-allows-root-access-to-host-file-system15:05
gagehugointeresting article fungi linked (yesterday?)15:06
*** zbr_ has joined #openstack-meeting15:06
gagehugootherwise does anyone have anything?15:07
nickthetaiti have some good news :)15:07
nickthetaitA project I'll be dedicating one workday per week to is updating the security guide docs15:08
gagehugonice!15:08
nickthetaitmy goal today is to gague how up to date these bugs are https://bugs.launchpad.net/ossp-security-documentation/15:08
nickthetaitand if there are any obviously missing bugs I should create15:09
*** zbr has quit IRC15:09
fungiexcellent, thank you so much for picking this up!15:10
nickthetaitwelcome15:10
nickthetaitis there somewhere I can get a handle on what security features have been added during a release? Looking at the release notes is a starting point I imagine15:11
gagehugofungi: speaking of security docs, I emailed the security-doc-core group list, haven't heard back from anyone unfortunately15:11
gagehugoquite a few of the emails were returned as invalid as well15:11
*** cdent has left #openstack-meeting15:12
fungigagehugo: not surprising15:12
funginickthetait: maybe start by going through release highlights? and then move on to release notes15:13
nickthetaitokay15:13
* fungi gets the highlights link15:13
*** jangutter has left #openstack-meeting15:13
fungifor example...15:14
*** absubram has joined #openstack-meeting15:14
fungi#link https://releases.openstack.org/stein/highlights Stein release highlights15:14
fungithe idea is that projects publish a list of their most important developments in a given release15:14
nickthetaitthats handy15:15
fungithey go back as far as queens, which is precisely where you wanted to start anyway i think?15:15
fungi(the guide claims to be updated for pike already)15:15
gagehugoyeah15:15
fungiquality of the notes may vary, they're primarily meant as a source for media/analyst types drafting press releases15:16
nickthetaitnice15:16
fungibut at least they provide a starting point, and should correspond to more detailed stuff in release notes and/or project docs15:16
fungijust require a bit of digging to make those connections probably15:17
*** iyamahat has joined #openstack-meeting15:18
nickthetaitand its okay for me to start making noise on these bugs? https://bugs.launchpad.net/ossp-security-documentation/15:20
nickthetaitclosing old ones, changing tags, creating new...15:20
gagehugoI would say sure, start triaging things would be ok15:22
gagehugolook into existing ones15:22
nickthetaitgreat15:22
nickthetaitok that's all the questions I have for now15:23
*** e0ne has quit IRC15:23
gagehugoI'll subscribe and follow up on changes then when I can15:24
nickthetaitthx15:24
fungiyeah, please do whatever you like with the bug reports15:24
fungii'd like to promise i could subscribe and follow up on them without prompting, but i doubt i have the bandwidth15:25
fungihowever, if there's one you feel needs input from me, please do bring it to my attention15:25
nickthetaitI understand that ;)15:25
fungifind me in #openstack-security or feel free to e-mail me or whatever15:25
*** gyee has joined #openstack-meeting15:28
*** macza has joined #openstack-meeting15:31
gagehugothanks for coming everyone, have a good weekend!15:32
gagehugonickthetait you can ping me as well if needed or email15:33
*** pcaruana has quit IRC15:33
gagehugo#endmeeting15:33
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:33
openstackMeeting ended Thu May 30 15:33:17 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/security/2019/security.2019-05-30-15.00.html15:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/security/2019/security.2019-05-30-15.00.txt15:33
openstackLog:            http://eavesdrop.openstack.org/meetings/security/2019/security.2019-05-30-15.00.log.html15:33
*** enriquetaso has quit IRC15:37
nickthetaitbye15:37
*** nickthetait has left #openstack-meeting15:38
*** enriquetaso has joined #openstack-meeting15:42
*** Lucas_Gray has quit IRC15:45
*** rfolco has quit IRC16:06
*** rfolco has joined #openstack-meeting16:11
*** electrofelix has quit IRC16:16
*** electrofelix has joined #openstack-meeting16:22
*** lpetrut has joined #openstack-meeting16:48
*** ekcs has joined #openstack-meeting16:49
*** enriquetaso has quit IRC16:59
*** armax has quit IRC16:59
*** enriquetaso has joined #openstack-meeting16:59
*** iyamahat has quit IRC17:02
*** armax has joined #openstack-meeting17:05
*** iyamahat has joined #openstack-meeting17:16
*** armax has quit IRC17:17
*** armax has joined #openstack-meeting17:18
*** iyamahat_ has joined #openstack-meeting17:19
*** iyamahat has quit IRC17:22
*** kopecmartin is now known as kopecmartin|off17:28
*** yamahata has joined #openstack-meeting17:33
*** ociuhandu has quit IRC17:37
*** armax has quit IRC17:38
*** armax has joined #openstack-meeting17:38
*** ricolin has quit IRC17:42
*** sridharg has quit IRC17:48
*** electrofelix has quit IRC17:48
*** Lucas_Gray has joined #openstack-meeting17:48
*** electrofelix has joined #openstack-meeting17:50
*** absubram has quit IRC17:52
*** Lucas_Gray has quit IRC17:55
*** electrofelix has quit IRC18:03
*** njohnston has quit IRC18:05
*** pcaruana has joined #openstack-meeting18:24
*** bbowen has quit IRC18:26
*** bbowen has joined #openstack-meeting18:26
*** armstrong has joined #openstack-meeting18:30
*** hongbin has joined #openstack-meeting18:40
*** njohnston has joined #openstack-meeting18:44
*** bbowen has quit IRC18:57
*** diablo_rojo has joined #openstack-meeting19:06
*** yamamoto has joined #openstack-meeting19:42
*** yamamoto has quit IRC19:48
*** igordc has joined #openstack-meeting19:49
*** armstrong has quit IRC19:49
*** igordc has quit IRC19:50
*** lpetrut has quit IRC19:57
*** igordc has joined #openstack-meeting20:00
*** bbowen has joined #openstack-meeting20:01
*** ekcs has quit IRC20:02
*** ekcs has joined #openstack-meeting20:02
*** radeks has joined #openstack-meeting20:05
*** radeks_ has quit IRC20:06
*** Lucas_Gray has joined #openstack-meeting20:19
*** ekcs has quit IRC20:19
*** Lucas_Gray has quit IRC20:24
*** Lucas_Gray has joined #openstack-meeting20:26
*** radeks has quit IRC20:27
*** diablo_rojo has quit IRC20:31
*** _alastor_ has quit IRC20:41
*** artom has quit IRC20:59
*** Lucas_Gray has quit IRC21:15
*** pcaruana has quit IRC21:18
*** Lucas_Gray has joined #openstack-meeting21:23
*** whoami-rajat has quit IRC21:24
*** Wryhder has joined #openstack-meeting21:31
*** Lucas_Gray has quit IRC21:32
*** Wryhder is now known as Lucas_Gray21:32
*** raildo has quit IRC21:35
*** _alastor_ has joined #openstack-meeting21:59
*** bobh has joined #openstack-meeting22:10
*** bobh has quit IRC22:15
*** efried1 has joined #openstack-meeting22:19
*** efried has quit IRC22:20
*** efried1 is now known as efried22:20
*** carloss has quit IRC22:26
*** _alastor_ has quit IRC22:27
*** mriedem is now known as mriedem_away22:35
*** _alastor_ has joined #openstack-meeting22:36
*** _alastor1 has joined #openstack-meeting22:41
*** _alastor_ has quit IRC22:41
*** _alastor1 has quit IRC22:41
*** yamamoto has joined #openstack-meeting22:45
*** macza has quit IRC22:52
*** bobh has joined #openstack-meeting22:54
*** bobh has quit IRC22:59
*** njohnston has quit IRC23:07
*** ykatabam has joined #openstack-meeting23:09
*** ianychoi has quit IRC23:13
*** ekcs has joined #openstack-meeting23:14
*** rcernin has joined #openstack-meeting23:17
*** panda|ruck has quit IRC23:22
*** panda has joined #openstack-meeting23:23
*** hongbin has quit IRC23:46
*** artom has joined #openstack-meeting23:48
*** yamamoto has quit IRC23:49

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!