Monday, 2017-06-05

*** D9 has quit IRC00:01
*** D9 has joined #openstack-meeting-300:04
*** dimtruck is now known as zz_dimtruck00:14
*** zz_dimtruck is now known as dimtruck00:14
*** gouthamr has quit IRC00:21
*** yamamoto has joined #openstack-meeting-300:23
*** yamamoto has quit IRC00:30
*** markvoelker has quit IRC00:31
*** wanghao has joined #openstack-meeting-300:37
*** yamamoto has joined #openstack-meeting-300:43
*** julim has joined #openstack-meeting-300:45
*** mickeys has joined #openstack-meeting-300:52
*** mickeys has quit IRC00:57
*** gcb has joined #openstack-meeting-301:19
*** mickeys has joined #openstack-meeting-301:33
*** zhurong has joined #openstack-meeting-301:34
*** zhurong has quit IRC01:44
*** baoli has joined #openstack-meeting-301:46
*** cinerama` has quit IRC02:02
*** neil__ has quit IRC02:03
*** cinerama has joined #openstack-meeting-302:06
*** baoli has quit IRC02:20
*** markvoelker has joined #openstack-meeting-302:28
*** baoli has joined #openstack-meeting-302:28
*** VW has joined #openstack-meeting-302:31
*** zhurong has joined #openstack-meeting-302:32
*** mickeys has quit IRC02:33
*** baoli has quit IRC02:40
*** markvoelker has quit IRC03:02
*** julim has quit IRC03:09
*** VW has quit IRC03:20
*** gouthamr has joined #openstack-meeting-303:20
*** dimtruck is now known as zz_dimtruck03:31
*** julim has joined #openstack-meeting-303:39
*** julim has quit IRC03:39
*** psachin has joined #openstack-meeting-303:42
*** reedip_ has joined #openstack-meeting-303:54
*** markvoelker has joined #openstack-meeting-303:58
*** reedip_ has quit IRC04:07
*** gouthamr has quit IRC04:12
*** markvoelker has quit IRC04:32
*** mickeys has joined #openstack-meeting-304:35
*** zenirc369 has joined #openstack-meeting-304:35
*** tuanluong has joined #openstack-meeting-304:39
*** mickeys has quit IRC04:39
*** mickeys has joined #openstack-meeting-304:57
*** salv-orlando has joined #openstack-meeting-305:08
*** Fdaisuke_ has joined #openstack-meeting-305:10
*** beekneemech has quit IRC05:11
*** Fdaisuke_ has quit IRC05:11
*** Fdaisuke has quit IRC05:11
*** Fdaisuke has joined #openstack-meeting-305:11
*** MarkBaker has joined #openstack-meeting-305:16
*** yamamoto has quit IRC05:28
*** anilvenkata has joined #openstack-meeting-305:40
*** cshastri has joined #openstack-meeting-305:44
*** tobberydberg has joined #openstack-meeting-305:47
*** pgadiya has joined #openstack-meeting-305:49
*** pgadiya has quit IRC05:49
*** salv-orlando has quit IRC06:05
*** mickeys has quit IRC06:05
*** yamamoto has joined #openstack-meeting-306:13
*** sgordon has quit IRC06:20
*** MarkBaker has quit IRC06:25
*** markvoelker has joined #openstack-meeting-306:28
*** ltomasbo|away is now known as ltomasbo06:36
*** mfedosin has joined #openstack-meeting-306:48
*** anilvenkata has quit IRC06:50
*** tuanluong has quit IRC06:50
*** cinerama has quit IRC06:50
*** carl_baldwin has quit IRC06:50
*** vdrok has quit IRC06:50
*** amit213 has quit IRC06:50
*** alex_didenko has quit IRC06:50
*** raddaoui has quit IRC06:50
*** kong has quit IRC06:50
*** hogepodge has quit IRC06:50
*** TheJulia has quit IRC06:50
*** sballe_ has quit IRC06:50
*** uli-k has quit IRC06:50
*** pasquier-s has quit IRC06:50
*** ameade has quit IRC06:50
*** diablo_rojo_phon has quit IRC06:50
*** fyxim has quit IRC06:50
*** xgerman has quit IRC06:50
*** cinerama` has joined #openstack-meeting-306:50
*** xgerman_ has joined #openstack-meeting-306:50
*** anilvenkata has joined #openstack-meeting-306:50
*** fyxim has joined #openstack-meeting-306:50
*** carl_baldwin has joined #openstack-meeting-306:50
*** tuanluong has joined #openstack-meeting-306:50
*** pasquier-s_ has joined #openstack-meeting-306:50
*** kong has joined #openstack-meeting-306:50
*** raddaoui has joined #openstack-meeting-306:51
*** vdrok has joined #openstack-meeting-306:51
*** sballe_ has joined #openstack-meeting-306:51
*** alex_didenko has joined #openstack-meeting-306:51
*** TheJulia has joined #openstack-meeting-306:51
*** ameade has joined #openstack-meeting-306:51
*** hogepodge has joined #openstack-meeting-306:51
*** amit213 has joined #openstack-meeting-306:51
*** diablo_rojo_phon has joined #openstack-meeting-306:51
*** uli-k has joined #openstack-meeting-306:51
*** markvoelker has quit IRC07:02
*** salv-orlando has joined #openstack-meeting-307:04
*** pcaruana has joined #openstack-meeting-307:04
*** mickeys has joined #openstack-meeting-307:06
*** mickeys has quit IRC07:11
*** ccamacho has joined #openstack-meeting-307:18
*** mickeys has joined #openstack-meeting-307:19
*** mickeys has quit IRC07:21
*** shuyingya has joined #openstack-meeting-307:26
*** salv-orl_ has joined #openstack-meeting-307:28
*** salv-orlando has quit IRC07:31
*** zhurong has quit IRC07:31
*** zhurong has joined #openstack-meeting-307:39
*** markvoelker has joined #openstack-meeting-307:59
*** rossella_s has joined #openstack-meeting-308:06
*** salv-orl_ has quit IRC08:07
*** neil__ has joined #openstack-meeting-308:09
*** salv-orlando has joined #openstack-meeting-308:10
*** rossella_s has quit IRC08:14
*** shuyingy_ has joined #openstack-meeting-308:17
*** zhurong has quit IRC08:20
*** shuyingya has quit IRC08:21
*** mickeys has joined #openstack-meeting-308:22
*** mickeys has quit IRC08:28
*** rossella_s has joined #openstack-meeting-308:30
*** markvoelker has quit IRC08:32
*** julim has joined #openstack-meeting-308:33
*** julim has quit IRC08:39
*** zhurong has joined #openstack-meeting-308:50
*** salv-orlando has quit IRC08:50
*** salv-orlando has joined #openstack-meeting-308:51
*** wanghao_ has joined #openstack-meeting-309:06
*** wanghao has quit IRC09:06
*** itamaro has quit IRC09:08
*** anilvenkata has quit IRC09:09
*** sambetts|afk is now known as sambetts09:13
*** salv-orlando has quit IRC09:13
*** salv-orlando has joined #openstack-meeting-309:14
*** wanghao_ has quit IRC09:21
*** mickeys has joined #openstack-meeting-309:24
*** mickeys has quit IRC09:29
*** markvoelker has joined #openstack-meeting-309:29
*** rossella_s has quit IRC09:30
*** cshastri has quit IRC09:32
*** rossella_s has joined #openstack-meeting-309:46
*** cshastri has joined #openstack-meeting-309:49
*** rossella_s has quit IRC09:54
*** zhurong has quit IRC09:59
*** anilvenkata has joined #openstack-meeting-310:00
*** iyamahat has joined #openstack-meeting-310:01
*** markvoelker has quit IRC10:02
*** cshastri has quit IRC10:06
*** iyamahat has quit IRC10:07
*** zhurong has joined #openstack-meeting-310:13
*** yamamoto has quit IRC10:17
*** cshastri has joined #openstack-meeting-310:17
*** jtomasek is now known as jtomasek|brb10:23
*** mickeys has joined #openstack-meeting-310:25
*** mickeys has quit IRC10:29
*** anilvenkata has quit IRC10:43
*** markvoelker has joined #openstack-meeting-311:00
*** sdague has joined #openstack-meeting-311:05
*** shuyingy_ has quit IRC11:12
*** eliqiao has quit IRC11:12
*** shuyingya has joined #openstack-meeting-311:12
*** eliqiao has joined #openstack-meeting-311:15
*** anilvenkata has joined #openstack-meeting-311:22
*** mickeys has joined #openstack-meeting-311:26
*** yamamoto has joined #openstack-meeting-311:27
*** mickeys has quit IRC11:30
*** markvoelker has quit IRC11:33
*** salv-orlando has quit IRC11:35
*** shuyingy_ has joined #openstack-meeting-311:35
*** salv-orlando has joined #openstack-meeting-311:35
*** shuyingya has quit IRC11:38
*** salv-orlando has quit IRC11:39
*** shuyingy_ has quit IRC11:45
*** shuyingya has joined #openstack-meeting-311:46
*** ducttape_ has joined #openstack-meeting-311:50
*** tuanluong has quit IRC11:56
*** numans_ has quit IRC11:57
*** ducttape_ has quit IRC12:00
*** ducttape_ has joined #openstack-meeting-312:01
*** zhurong has quit IRC12:04
*** ducttape_ has quit IRC12:05
*** julim has joined #openstack-meeting-312:08
*** rossella_s has joined #openstack-meeting-312:13
*** markvoelker has joined #openstack-meeting-312:16
*** julim has quit IRC12:18
*** rossella_s has quit IRC12:20
*** rossella_s has joined #openstack-meeting-312:20
*** shuyingya has quit IRC12:24
*** mickeys has joined #openstack-meeting-312:27
*** jtomasek|brb is now known as jtomasek12:28
*** tellesnobrega has joined #openstack-meeting-312:29
*** mickeys has quit IRC12:31
*** lyan has joined #openstack-meeting-312:37
*** salv-orlando has joined #openstack-meeting-312:40
*** cleong has joined #openstack-meeting-312:44
*** tellesnobrega has quit IRC12:52
*** shuyingya has joined #openstack-meeting-312:54
*** sgordon has joined #openstack-meeting-312:57
*** shuyingya has quit IRC13:00
*** shuyingya has joined #openstack-meeting-313:00
*** ducttape_ has joined #openstack-meeting-313:01
*** ducttape_ has quit IRC13:06
*** tellesnobrega has joined #openstack-meeting-313:09
*** bobh has joined #openstack-meeting-313:11
*** baoli has joined #openstack-meeting-313:13
*** ducttap__ has joined #openstack-meeting-313:17
*** lucasxu has joined #openstack-meeting-313:17
*** salv-orlando has quit IRC13:23
*** ducttap__ has quit IRC13:24
*** ducttape_ has joined #openstack-meeting-313:27
*** mickeys has joined #openstack-meeting-313:27
*** rpodolyaka has quit IRC13:29
*** mickeys has quit IRC13:32
*** gouthamr has joined #openstack-meeting-313:33
*** baoli has quit IRC13:38
*** baoli has joined #openstack-meeting-313:38
*** ducttape_ has quit IRC13:41
*** ducttape_ has joined #openstack-meeting-313:41
*** crushil has joined #openstack-meeting-313:44
*** zhurong has joined #openstack-meeting-313:46
*** ducttape_ has quit IRC13:54
*** ducttape_ has joined #openstack-meeting-313:54
*** julim has joined #openstack-meeting-313:55
*** kgiusti has joined #openstack-meeting-313:56
*** ansmith has joined #openstack-meeting-313:56
*** zz_dimtruck is now known as dimtruck13:58
gcb#startmeeting  oslo14:00
openstackMeeting started Mon Jun  5 14:00:06 2017 UTC and is due to finish in 60 minutes.  The chair is gcb. 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: oslo)"14:00
openstackThe meeting name has been set to 'oslo'14:00
*** bnemec has joined #openstack-meeting-314:00
gcbcourtesy ping for amotoki, amrith, bknudson, bnemec, crushil, dansmith, dhellmann14:00
gcbcourtesy ping for dims, dougwig, e0ne, electrocucaracha, flaper87, garyk, gcb14:00
gcbcourtesy ping for GheRivero, haypo, jd__, jecarey, johnsom, jungleboyj, kgiusti14:00
gcbcourtesy ping for kragniz, lhx_, lifeless, lxsli, Nakato, ozamiatin, rbradfor14:00
gcbcourtesy ping for redrobot, rpodolyaka, sergmelikyan, sileht, spamaps, sreshetnyak, sreshetnyak14:00
gcbcourtesy ping for stevemar, therve, thinrichs, toabctl, viktors, zhiyan, zzzeek14:00
crushil\o14:00
kgiustio/14:00
ansmitho/14:00
amrithgcb, hello. i have to head out, can't attend today. no red flags from trove14:00
gcbwelcome everyone \o/14:00
gcbamrith: thanks14:01
gcb#topic Red flags for/from liaisons14:01
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"14:01
gcbhttp://status.openstack.org/openstack-health/#/?groupKey=build_name&resolutionKey=hour&searchProject=-with-oslo14:01
gcbThere is no redflag from me14:01
*** shuyingya has quit IRC14:02
*** shuyingya has joined #openstack-meeting-314:02
*** janzian has joined #openstack-meeting-314:02
gcbthere is a oslo.messaging issue when using 'blocking' executor , sileht and kgiusti have been working on it14:03
gcb#link https://review.openstack.org/#/q/topic:bug/169472814:03
gcb#topic Releases for Pike14:04
*** openstack changes topic to "Releases for Pike (Meeting topic: oslo)"14:04
gcbhttps://review.openstack.org/#/c/470861/14:04
*** ducttape_ has quit IRC14:05
gcbas dhellmann  suggested, we will release stable branch release in Pike-2 milestone14:05
gcb#topic Stuck Reviews14:06
*** openstack changes topic to "Stuck Reviews (Meeting topic: oslo)"14:06
gcbIs there any stuck reviews ?14:06
*** shuyingya has quit IRC14:07
kgiustigcb: should we hold off releasing oslo.messaging until sileht's patches merge?14:07
*** VW has joined #openstack-meeting-314:08
gcbkgiusti: the bug only affects 'blocking' executor, we can request a new release once sileht's patches merge14:08
gcbwhat do you think ?14:09
kgiustigcb: one sec...14:09
gcbhttps://review.openstack.org/#/c/470861/ was just merged ....14:09
*** galstrom_zzz is now known as galstrom14:10
kgiustigcb: kk - then let's do a new release when the blocking fix lands (and nobody sees any new issues from it)14:10
gcbkgiusti: yeah, dhellman is our oslo release liaison, please add him as reviewer when I'm not available14:12
kgiustigcb: +114:12
gcbkgiusti: that will quicken the release process :-)14:13
*** shuyingya has joined #openstack-meeting-314:13
gcb#topic Open discussion14:14
*** openstack changes topic to "Open discussion (Meeting topic: oslo)"14:14
gcbanybody have items to raise here ?14:14
* gcb gcb still at the office, will go home later14:16
gcbplease feel free to discuss in the #openstack-oslo14:17
*** persia has quit IRC14:17
gcbthanks everyone,  sorry for the quick meeting today14:17
gcb#endmeeting14:18
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:18
openstackMeeting ended Mon Jun  5 14:18:25 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-06-05-14.00.html14:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-06-05-14.00.txt14:18
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-06-05-14.00.log.html14:18
*** crushil has left #openstack-meeting-314:19
*** galstrom is now known as galstrom_zzz14:19
*** janzian has left #openstack-meeting-314:20
*** persia has joined #openstack-meeting-314:21
*** shuyingya has quit IRC14:26
*** galstrom_zzz is now known as galstrom14:26
*** shuyingya has joined #openstack-meeting-314:26
*** anilvenkata has quit IRC14:27
*** zenirc369 has quit IRC14:28
*** mickeys has joined #openstack-meeting-314:28
*** psachin has quit IRC14:31
*** mickeys has quit IRC14:32
*** rbrady has joined #openstack-meeting-314:33
*** psachin has joined #openstack-meeting-314:33
*** baoli has quit IRC14:34
*** baoli has joined #openstack-meeting-314:35
*** baoli has quit IRC14:35
*** baoli has joined #openstack-meeting-314:37
*** psachin has quit IRC14:47
*** cshastri has quit IRC14:48
*** toure has joined #openstack-meeting-314:55
*** fultonj has joined #openstack-meeting-314:56
*** yamahata has joined #openstack-meeting-314:57
*** julim has quit IRC14:57
*** thrash has joined #openstack-meeting-314:57
*** mgershen has joined #openstack-meeting-314:57
rakhmerov#startmeeting Mistral15:00
openstackMeeting started Mon Jun  5 15:00:16 2017 UTC and is due to finish in 60 minutes.  The chair is rakhmerov. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
rakhmerovhello15:00
*** openstack changes topic to " (Meeting topic: Mistral)"15:00
openstackThe meeting name has been set to 'mistral'15:00
thrasho/15:00
rakhmerovhi )15:00
tourehello15:00
fultonjhi15:00
mgersheno/15:00
d0ugalHey15:00
rakhmerovhi all15:01
rakhmerov#topic Review action items15:01
*** openstack changes topic to "Review action items (Meeting topic: Mistral)"15:01
rakhmerov1. rakhmerov: review https://review.openstack.org/443217 again15:01
rakhmerovI think it's done but let me check..15:01
rakhmerovyes, done15:01
toureyup15:01
rakhmerov:)15:02
rakhmerov#topic Current status (progress, issues, roadblocks, further plans)15:02
*** openstack changes topic to "Current status (progress, issues, roadblocks, further plans) (Meeting topic: Mistral)"15:02
*** shuyingy_ has joined #openstack-meeting-315:02
rakhmerovmy status: reviews, Java Client for Mistral (OpenStack4J), fixed a couple of small things, and started working on HA & Scalability15:02
tourerakhmerov I think there may be a refactor of the cli name, but other than that it should be done15:03
rakhmerovthe spec was submitted today: https://review.openstack.org/#/c/470928/15:03
thrashrakhmerov: I am discontinuing work on the securing secrets bp. There are some technical challenges to it that I don't have time right now to overcome.15:03
*** julim has joined #openstack-meeting-315:03
mgershenstatus: Just created the next spec from creating and running a workflow within a namespace: https://review.openstack.org/#/c/470996/15:03
rakhmerovtoure: ok, please don't hesitate to remove [WIP] from your patches if you think they are ready15:04
d0ugalNothing to report from me, I have been tied up with TripleO tasks and have not had time to continue the mistral-lib/mistral-extra work. I hope to get back to it soon, but I am concerned about deadlines15:04
tourerakhmerov ack, almost there15:04
rakhmerovmgershen: ooh, I haven't seen it yet15:04
rakhmerov#action rakhmerov: review https://review.openstack.org/#/c/470996/15:04
rakhmerovd0ugal: ok15:04
thrashrakhmerov: as I currently see it, it would be a bunch of work to effectively redact a secret in about 4 places in the code. And most of those places would involve doing a db lookup15:04
rakhmerovd0ugal: what deadlines do you mean?15:05
rakhmerovPike-2?15:05
mgershenI published it less than 15 minutes ago15:05
thrashwhich seems rather pointless to me... A db lookup for a log message15:05
d0ugalrakhmerov: yeah, originally I wanted to have the OpenStack actions ported for pike-215:05
tourestatus: Testing server side workflow error analysis changes, once done will remove WIP and let all take a look15:05
rakhmerovthrash: have you left comments in the patch so we could see?15:05
*** shuyingya has quit IRC15:06
rakhmerovd0ugal: Pike-3 would be ok, no worries15:06
rakhmerovbut we need to do it in Pike15:06
rakhmerovfor many reasons15:06
d0ugalrakhmerov: Yup, I am now aiming for that - but I have 2 weeks that I am away. I might see if I can recruit a helper :)15:06
thrashrakhmerov: I have some made locally... I'll push it up...15:07
rakhmerovthrash: at the moment, I'm now aware of these challenges although I would assume that the whole task is not easy to deal with15:07
*** julim has quit IRC15:07
thrashrakhmerov: that it is. :D15:07
rakhmerovthrash: yeah, please try to leave all needed info so that we could continue at least discussing it15:07
d0ugal+1, some record of learnings would be useful.15:08
rakhmerovd0ugal: ok )15:08
rakhmerovyes15:08
rakhmerovthrash: just to inspire you a little bit: I can remember 3-4 people who tried to tackle this task and all gave up )15:08
thrashrakhmerov: That's depressing. :|15:09
d0ugalhaha15:09
rakhmerov:))15:09
thrashhehe15:09
tourehahaha15:09
rakhmerovI mean no worries )15:09
rakhmerovwe'll eventually get it done15:09
*** ducttape_ has joined #openstack-meeting-315:09
thrashI guess I don't feel so stupid anymore. lol15:09
rakhmerovno doubts :)15:09
rakhmerovyeah, that's that I tried to do!15:09
rakhmerovso that you don't feel stupid15:09
rakhmerovook15:10
rakhmerovanything else in this part?15:10
rakhmerovrbrady: ^15:10
*** tobberydberg has quit IRC15:10
rbradyrakhmerov: I have been working with thrash and have come to the same conclusion15:10
rakhmerovhaha :))15:11
rakhmerovgot it15:11
rakhmerovok15:11
rakhmerovok15:11
rakhmerov(why did I type it twice, hm...?)15:11
rakhmerovlet me see what's next15:11
rakhmerov#topic Sync on Pike 2 progress15:12
*** openstack changes topic to "Sync on Pike 2 progress (Meeting topic: Mistral)"15:12
rakhmerovso, here basically I just would like to ask you to wrap up what's possible this week15:12
rakhmerovand pay a little more attention to reviewing15:12
rakhmerovand if you need help with something please don't be silent15:12
rakhmerovand update statuses of you tasks please anyway so that we could see where we are15:13
rakhmerovI did some of that today but not all15:13
rakhmerovthere's also a couple of BPs that I'd like to clarify with rbrady, d0ugal and apetrich15:14
rakhmerovhttps://blueprints.launchpad.net/mistral/+spec/mistral-actions-api-fix-engine15:14
rakhmerovhttps://blueprints.launchpad.net/mistral/+spec/mistral-actions-api-fix-executor15:14
rakhmerovI asked apetrich to update them but he's off today I guess15:14
d0ugalrakhmerov: I am not sure what "fix engine" means? Just to migrate them to mistral-lib?15:14
rakhmerovso15:14
rakhmerovthose BPs were created long long ago15:15
rakhmerovonce upon a time... Renat created blueprints..15:15
d0ugalhttps://github.com/openstack/mistral-specs/blob/master/specs/newton/approved/mistral-custom-actions-api.rst#work-items15:15
d0ugalhaha15:15
mgershenhaha15:15
*** zhurong has quit IRC15:15
rakhmerovthe idea was that after creating mistral-lib with all needed stuff we'd make changes on the server side whatever is needed15:16
rakhmerov:)15:16
rakhmerovin engine possible and executor15:16
rakhmerovthat was my understanding15:16
d0ugalRight. I think at the time we expected mistral-lib to be much large (containing the context etc.)15:16
d0ugalbut I'm glad we didn't go down that route15:16
d0ugalso I think we can consider these to be completed.15:16
rakhmerovbut I guess they may not be relevant anymore and we can close them15:16
rakhmerovas far as engine, I left a comment in whiteboard15:17
rakhmerovI found a patch that seems to implement this BP15:17
rakhmerovfor executor, I'm not sure15:17
rakhmerovI remember that we inserted some condition to check if the action is from mistral-lib or not15:17
rakhmerovd0ugal: was it you who made it?15:17
rakhmerovso, I'm just wondering whether it's enough or not15:18
rakhmerovfor executor15:18
d0ugalrakhmerov: the patch you linked? no, that was apetrich15:18
d0ugalrakhmerov: but yes, I think it is enough15:18
rakhmerovno-no, I'm now talking about executor15:18
rakhmerovsecond..15:18
rakhmerovd0ugal: this, https://github.com/openstack/mistral/blob/master/mistral/executors/default_executor.py#L10915:19
*** bnemec has quit IRC15:19
d0ugalrakhmerov: right15:19
rakhmerovdoes it seem all we had to do in there?15:19
d0ugalrakhmerov: I believe so, we just need to leave that there until we can remove the old actions API15:19
rakhmerovsorry, I just lost track of this work a little bit..15:19
rakhmerovright15:20
d0ugalI'm not sure how long the deprecation is for a change like that15:20
rakhmerovwhich will happen in a couple of cycles I believe.. not earlier15:20
d0ugalyup15:20
rakhmerovfirst we need to gently deprecate old stuff and bring it to our lovely users15:20
rakhmerovd0ugal: I would think it's in our interest to make it long )15:21
rakhmerovbut yes, we need to figure out15:21
rakhmerov#action: rakhmerov, d0ugal: figure out for how long old actions should be deprecated before complete removal15:21
rakhmerovokay15:22
rakhmerovthey I'm closing them? Marking "implemented"?15:22
rakhmerovthen..15:22
d0ugalthanks15:22
rakhmerovok15:22
d0ugalthat works for me15:22
rakhmerovwith these two implemented the situation looks much more positive )15:23
rakhmerovfor Pike 215:23
d0ugal:-D15:23
rakhmerovyeah, sorry, I just have this kind of mood today )15:23
apetrichrakhmerov, d0ugal sorry. still sick.. I wasn't able to concentrate enough to read the blueprint15:24
*** bnemec has joined #openstack-meeting-315:24
rakhmerovapetrich: we've discussed them a little bit and seems like they can be closed15:24
rakhmerovbut if you look at them tomorrow and disagree we can reopen them, np15:24
*** julim has joined #openstack-meeting-315:24
rakhmerovthanks15:24
apetrichrakhmerov, I only think that we have to move some Results from mistral to mistral_lib. I have those changes but didn't create a patch because the gates were still failing15:25
apetrichbut it is a simple change15:25
apetrichon openstack actions15:25
rakhmerovok15:25
rakhmerovthe gates were fixed today15:25
rakhmerovwe had issues with docs but it's ok now15:26
rakhmerovanything else on that?15:26
apetrichrakhmerov, I don't think so. besides that I think we can close it15:26
rakhmerovthere's also a bunch of bugs, please take a look and see what can be quickly fixed (what's assigned to you) and what we need to move to P-315:26
rakhmerovapetrich: ok, thanks15:27
rakhmerovd0ugal: like, for example https://bugs.launchpad.net/mistral/+bug/166461215:27
openstackLaunchpad bug 1664612 in Mistral "tasks with a hyphen in their name don't work" [Undecided,Confirmed] - Assigned to Dougal Matthews (d0ugal)15:27
d0ugaloh, wow. I forgot about that one15:27
rakhmerovI might have asked you but it's worth checking again if it really exists15:28
d0ugalI thought I fixed it actually, but I should check.15:28
rakhmerovyeah, I'm not sure it exists but we need to update the status15:28
rakhmerovat least15:28
rakhmerovplease go over them and check15:28
d0ugalWill do15:28
rakhmerovthanks15:28
rakhmerovok, let's move on15:28
*** julim has quit IRC15:28
rakhmerov#topic Decide if new release model "cycle-with-intermediary" is ok for Mistral15:29
*** openstack changes topic to "Decide if new release model "cycle-with-intermediary" is ok for Mistral (Meeting topic: Mistral)"15:29
rakhmerovyeah, so, there is a ML thread opened recently15:29
*** tobberydberg has joined #openstack-meeting-315:29
rakhmerovabout release model for several projects including Mistral15:29
rakhmerovthe problem is that 'mistral' is in reqiurements.txt in tripleO15:30
d0ugal#link http://lists.openstack.org/pipermail/openstack-dev/2017-May/117658.html15:30
rakhmerovd0ugal: right? (still trying to understand that myself)15:30
d0ugalrakhmerov: yes, that is the problem15:30
rakhmerovok15:30
d0ugalMistral is in requirements, that means it is treated like a library but it is only released at the end of the cycle15:31
d0ugalthis means that the requirements in mistral limit the requirements in other projects15:31
rakhmerovas a solution Thierry suggested us to switch to a different release model: cycle-with-intermediary15:31
rakhmerovyes15:31
rakhmerovexactly15:31
rakhmerovcycle-with-intermediary does not assume having beta releases at all15:31
rakhmerovlike mistral-5.0.0.0b115:32
rakhmerovbut only full releases (without letters)15:32
rakhmerovwhich means all of them must be stable15:32
d0ugalAFAICT with cycle-with-intermediary, we can release stable releases at any point15:32
rakhmerovstable branch management remains the same, one per cycle, of course15:32
rakhmerovyes15:32
rakhmerovwe talked today a little bit and it seems like the problem of having 'mistral' in TripleO dependencies may be gone soon15:33
rakhmerovbut anyway, we can make a decision to switch to this release model15:33
rakhmerov1) to me it seems more flexible15:34
d0ugalso, if we made a release today, would it be 5.0?15:34
rakhmerov2) all our releases are considered stable15:34
*** tobberydberg has quit IRC15:34
rakhmerovgood question, probably yes15:34
d0ugaland then after pike is released we would start to release 6.015:34
rakhmerovthe thing is that this week is the last chance to make that decision15:34
*** marst has joined #openstack-meeting-315:34
rakhmerovafter pike-2 we'll have to wait till the next cycle15:34
*** julim has joined #openstack-meeting-315:34
*** lucasxu has quit IRC15:35
*** reedip_ has joined #openstack-meeting-315:35
d0ugalI have one concern...15:35
rakhmerovd0ugal: yes, the docs don't say anything about numbers for release but we can do something like that15:35
rakhmerovd0ugal: yep?15:35
d0ugalMistral master is developed against KeyStone master for auth and all the other openstack projects15:35
d0ugalso if we released 5.0 today, we might have a stable release that only works with unreleased projects15:36
d0ugalso we release 5.0 today (or soon) which will be Pike but that needs to be tested against Ocata15:36
d0ugalDoes that make sense? I only just thought of it.15:37
*** shuyingy_ has quit IRC15:37
rakhmerovhm..15:37
rakhmerovgood question15:37
*** shuyingya has joined #openstack-meeting-315:38
rakhmerovbut that's probably ok that intermediary releases work with keystone of full release of the previous cycle15:38
rakhmerovwhat are other options?15:38
rakhmerovin any case, we're supposed to make a normal release at the end of the cycle15:39
*** slaweq has joined #openstack-meeting-315:39
rakhmerovbut that release will be integrated with the latest changes in other projects15:39
rakhmerovthat's my understanding15:39
d0ugalright15:39
d0ugalI just think it will be confusing for our users if we tell them they need to install mistral, but not the latest version - the one that matches the latest OpenStack release15:40
d0ugalwe already need to tell them to avoit 2015.1 :(15:40
rakhmerovwell, yeah..15:40
rakhmerovtrue15:40
d0ugalI think it probably makes more sense to remove Mistral from requirements.txt - we will do that anyway15:41
rakhmerovwell, ok, maybe what we need to understand for now then is how critical it is for solving that dependency issue15:41
rakhmerovif it's not I think we need to wait for next cycle15:41
d0ugalright15:42
d0ugalI guess I'll reply to the thread and ask some questions15:42
rakhmerovd0ugal: yes, but the question is: how urgent is it?15:42
*** shuyingya has quit IRC15:42
rakhmerovand when can we do it in TripleO?15:42
rakhmerovd0ugal: yes, let's do this15:42
rakhmerovjust not to rush with this..15:42
d0ugaltripleo only needs it in requirements.txt for the unit tests :)15:42
rakhmerovd0ugal: so, as far as I understand, it's not a risky change, you just need to make it? right?15:43
rakhmerovI mean, technically there's no risk15:43
rakhmerovall is clear15:43
d0ugalrakhmerov: agreed, there is no risk.15:43
rakhmerovok15:43
rakhmerovthen please reply to the thread, I'd prefer not to rush15:44
d0ugalok15:44
rakhmerovespecially that I now remember Thierry saying that he'd prefer to give Mistral an exception of switching the model in the middle of the cycle )15:44
rakhmerovusually it's forbidden, only in the beginning15:45
rakhmerovbefore first milestone releaes15:45
rakhmerovok, deal15:45
rakhmerovif there's no other thoughts..15:45
*** slaweq has quit IRC15:46
rakhmerovso then15:47
rakhmerov#topic Open Discussion15:47
*** openstack changes topic to "Open Discussion (Meeting topic: Mistral)"15:47
rakhmerovis there anything else from you?15:47
d0ugalNot from me15:47
rbradynot from me today15:48
mgershennot from me15:48
rakhmerovok, many thanks15:48
thrashno15:48
rakhmerovplease update the tickets15:48
rakhmerovthanks15:48
rakhmerovthen let's finish15:48
rakhmerovhave a good week, thanks for being with us today15:48
rakhmerovbye15:48
mgershenBye15:48
rakhmerov#endmeeting15:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:49
openstackMeeting ended Mon Jun  5 15:49:03 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/mistral/2017/mistral.2017-06-05-15.00.html15:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/mistral/2017/mistral.2017-06-05-15.00.txt15:49
openstackLog:            http://eavesdrop.openstack.org/meetings/mistral/2017/mistral.2017-06-05-15.00.log.html15:49
*** thrash has left #openstack-meeting-315:49
*** mgoddard_ has joined #openstack-meeting-315:59
*** mgoddard_ has left #openstack-meeting-316:02
*** julim has quit IRC16:07
*** salv-orlando has joined #openstack-meeting-316:07
*** rbak has joined #openstack-meeting-316:09
*** reedip_ has quit IRC16:09
*** rbak has quit IRC16:09
*** rossella_s has quit IRC16:15
*** rbak has joined #openstack-meeting-316:19
*** nicodemos has joined #openstack-meeting-316:21
*** diablo_rojo has joined #openstack-meeting-316:22
*** pcaruana has quit IRC16:23
*** yamamoto has quit IRC16:24
*** crushil has joined #openstack-meeting-316:25
*** lucasxu has joined #openstack-meeting-316:28
*** mickeys has joined #openstack-meeting-316:30
*** mickeys has quit IRC16:34
*** slaweq has joined #openstack-meeting-316:34
*** ltomasbo is now known as ltomasbo|away16:37
*** iyamahat has joined #openstack-meeting-316:42
*** harlowja has joined #openstack-meeting-316:45
*** stendulker has joined #openstack-meeting-316:48
*** bfournie has joined #openstack-meeting-316:51
*** lyan has quit IRC16:54
*** fellypefca has joined #openstack-meeting-316:55
*** rloo has joined #openstack-meeting-316:55
*** izumi777 has joined #openstack-meeting-316:56
*** dtantsur has joined #openstack-meeting-316:57
*** lyan has joined #openstack-meeting-316:58
*** rama_y has joined #openstack-meeting-316:59
dtantsuranyone up for an ironic meeting?16:59
*** mjturek has joined #openstack-meeting-316:59
dtantsur#startmeeting ironic17:00
openstackMeeting started Mon Jun  5 17:00:02 2017 UTC and is due to finish in 60 minutes.  The chair is dtantsur. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: ironic)"17:00
openstackThe meeting name has been set to 'ironic'17:00
mjtureko/17:00
dtantsuro/17:00
rlooo/17:00
nicodemoso/17:00
TheJuliao/17:00
stendulkero/17:00
NobodyCamo/17:00
dtantsurhi everyone! welcome to our small ironic part...serious meeting :)17:00
fellypefcao/17:01
NobodyCam:)17:01
dtantsurour very light agenda is as usual at17:01
*** Nisha_Agarwal has joined #openstack-meeting-317:01
dtantsur#link https://wiki.openstack.org/wiki/Meetings/Ironic17:01
mjturek:)17:01
*** anupn has joined #openstack-meeting-317:01
*** baha has joined #openstack-meeting-317:01
izumi777o/17:02
bahao/17:02
dtantsur#topic Announcements / Reminder17:02
*** openstack changes topic to "Announcements / Reminder (Meeting topic: ironic)"17:02
dtantsurwe've had an IPA intermediary release17:03
*** rpioso has joined #openstack-meeting-317:03
crushil\o17:03
rpiosoo/17:03
dtantsurour stable releases are still pending with 2x +2, I guess I need to ping someone (ttx?) to proceed with them17:03
dtantsurfinally, this is the weak of Pike-2. I don't plan on any releases of ironic, just something to keep in mind.17:04
*** ricardoas has joined #openstack-meeting-317:04
rama_yo/17:04
ricardoaso/17:04
dtantsuranything else from anyone?17:04
krtayloro/17:04
TheJuliaNothing here17:05
dtantsurok, moving on17:05
dtantsur#topic Review subteam status reports (capped at ten minutes)17:05
*** openstack changes topic to "Review subteam status reports (capped at ten minutes) (Meeting topic: ironic)"17:05
dtantsur#link https://etherpad.openstack.org/p/IronicWhiteBoard starting with line 9417:06
rloodtantsur: the critical bug, is that the ironic-lib one?17:06
dtantsurrloo: yes17:06
rloosigh, and 4 more high bugs :-(17:06
dtantsurso yeah, I've broken the ironic-lib CI, sorry for that17:06
rloodtantsur: thx17:06
rloodtantsur: you break, you pay for it :-)17:06
dtantsurI'm working on making it building IPA from source to actually test ironic-lib changes17:06
dtantsurand I'm still figuring out zuul-pbr-tinyipa interactions17:07
dtantsurrloo: we're ready to review the version column again, right?17:07
rloodtantsur: yes, although i have a patch updating the spec. might be worth reading/agreeing with that first.17:08
xavierro/17:08
rloodtantsur: or review the patch and if you understand it w/o the spec update, that means it is good :)17:08
dtantsurrloo: yeah, I have it starred in gerrit, just did not get to actuall reviewing17:08
*** mgoddard_ has joined #openstack-meeting-317:08
mgoddard_o/17:08
dtantsur#info OSC driver-properties command spec https://review.openstack.org/#/c/439907/ has 2x +2 and is ready for landing17:09
*** sauloaislan has joined #openstack-meeting-317:09
dtantsurstendulker: hi! when updating the rescue section, please change the date, so that we know *when* the status was last updated17:09
sauloaislano/17:09
dtantsursambetts: any plans to update the IPA API version code soon(ish)?17:10
rloodtantsur: well, maybe that really was the status for 4/10...17:10
stendulkerdtantsur: ok.17:10
dtantsurrloo: no, there was new stuff added17:10
dtantsurstendulker: thanks!17:10
stendulkerdtantsur: thank you,17:11
sambettsdtantsur: yeah I need to do that I've not had a chance since the spec merges17:11
sambettsmerged*17:11
dtantsurack, updating the status17:12
dtantsursambetts: do you know if we need to do something in ironic for https://bugs.launchpad.net/ironic/+bug/1658964 ?17:12
openstackLaunchpad bug 1658964 in Ironic "[RFE] Implement neutron routed networks support in Ironic" [Wishlist,Confirmed] - Assigned to Sam Betts (sambetts)17:12
rloodtantsur: wrt cross-project. there was a thread last? week about install guides, do you know if we need to do anything there (agree, disagree, whatever)?17:12
dtantsurrloo: I don't think there was action items coming out of it17:13
dtantsurbut I guess we'll have all the guides in-tree eventually17:13
sambettsdtantsur: main thing is the physnet awareness, then I have some experimentation to do regarding neutron + agents + placement etc17:13
dtantsurthat's more or less inevitable, the exact way is still shaping17:13
dtantsursambetts: but that's a separate RFE, no?17:13
rloodtantsur: ok. to be honest, i didn't read it, all i know it was something about intree/out of tree, and putting them all under some common dir intree17:13
*** lucasxu has quit IRC17:13
rloodtantsur: yeah, well, we have almost all our docs intree now, so better support for that would be great17:14
*** lucasxu has joined #openstack-meeting-317:14
sambettsdtantsur: correct, there are changes in networking-baremetal related routed networks, but not in ironic (as far as I'm aware so far)17:14
dtantsuryeah, we need a proper user-guide, as now our user-guide is spread between install-guide and dev docs17:14
rloodtantsur: i think we wanted an admin guide...17:14
dtantsursambetts: so, can we close this RFE and remove it from the statuses?17:14
dtantsurrloo: right17:15
mgoddard_sambetts: did you look into what jroll was saying about physnet scheduling for routed networks not working with ironic due to the nova compute service/host mismatch?17:15
rloostendulker: wrt rescue, is the status updated?17:16
dtantsurjlvillal: around? I wonder if we still plan on splitting the tempest plugin. if so, let's get a plan on doing it (maybe as part of today's discussions)17:16
rloodtantsur: jlvillal still on vacation17:16
dtantsurah, ok17:16
rloodtantsur: he is back next week17:16
sambettsmgoddard_: yeah, I had loads of disucssions about it at the summit, and it turns out the aggregates that are used for routed networks are placement service aggregates which != nova host aggregates, and the placement aggregate operate per baremetal node17:17
dtantsurcool, thanks rloo17:17
sambettsmgoddard_: not just per nova compute17:17
sambettsmgoddard_: so \o/17:17
* dtantsur is super confused by all these aggregates and the placement changes17:17
mgoddard_sambetts: ok, that's good to know17:17
sambettsdtantsur: how are we tracking networking-baremetal work? and there is some stuff I'd like to discuss about whether it lives in networking-baremetal or in ironic as a periodic task17:17
dtantsursambetts: I wonder if we (as in "you" ;) can have some knowledge sharing about recent nova stuff17:17
*** mrmartin has quit IRC17:17
dtantsursambetts: we are not particularly tracking it so far. mostly because less than a half of people here understand it well17:18
* TheJulia looks at the clock17:18
dtantsursuggestions are welcome, I highly encourage someone to take initiative17:18
sambettsdtantsur: sure, jaypipes gave some great talks at the summit to bring people up to speed too, I wonder if we can get hold of those recordings/slides to help people understand17:18
dtantsurTheJulia: you're right; but these are good discussions17:18
dtantsur:)17:18
TheJuliadtantsur: absolutely ;)17:18
*** zenirc369 has joined #openstack-meeting-317:18
dtantsursambetts: mind asking him please?17:18
dtantsurwe're out of time indeed, let's reserve "how to track networking-baremetal work" to the discussions17:19
sambettsdtantsur: I'll ping him and see if we can dig them out17:19
TheJuliadtantsur: and I feel like we need a map, or a kanban board, or something for all the networking stuff at this point.17:19
* TheJulia will settle for ether pad too17:19
*** yamahata has quit IRC17:19
dtantsuryeah17:19
dtantsureveryone done with the statuses?17:19
dtantsurwe need to agree on priorities, and then we can jump back into discussing cool stuff :)17:19
*** wanyen has joined #openstack-meeting-317:19
*** iyamahat has quit IRC17:20
* dtantsur will assume "yes" really soon17:20
* rloo done except for rescue but stendulker hasn't replied17:20
dtantsur#topic Deciding on priorities for the coming week17:20
*** openstack changes topic to "Deciding on priorities for the coming week (Meeting topic: ironic)"17:20
*** iyamahat has joined #openstack-meeting-317:20
dtantsurso, we've landed two documentation patches, thanks all for reviews17:21
dtantsurthe OSC spec is really, really close17:21
*** stendulker has quit IRC17:21
NobodyCamgreat work on the doc patches!17:21
dtantsur++17:21
dtantsurshould we take the version column back?17:21
rloo++ :)17:21
TheJuliaso, re BFV priority, I completely missed the meeting last week, and I guess I'm the designated victim (wait, is that right?) to update that patch this week, but I wouldn't have it as #1 at the moment.17:22
rloodtantsur: do you think the spec update should be approved first?17:22
dtantsurmmm, we can do it in parallel, hopefully17:22
dtantsurrloo: do you have a link handy?17:22
rloohttps://review.openstack.org/#/c/469940/17:22
dtantsurTheJulia: to be honest, I'm worried about BFV. we have so much stuff ahead. I'd keep pushing on it, if we still hope for Pike.17:23
dtantsurthanks rloo17:23
rloowhen's the nova deadline for feature code?17:23
TheJuliadtantsur: likewise :(17:23
dtantsurrloo: Pike-3 IIRC17:24
mjturekTheJulia: would it help if I took over the wire-in patch or you good?17:24
*** stendulker has joined #openstack-meeting-317:24
TheJuliamjturek: if you have the bandwidth, that would help me a lot.17:24
rloodtantsur: week of july 24. we have a bit over 1 month.17:24
mjturekTheJulia: will do17:24
dtantsurrloo: yeah, which leaves us really no time, unless we land the whole ironic part in 2-3 weeks..17:25
rloodtantsur: well, we have maybe at most 1 month. ironic code for bfv needs to work before nova will look at the nova patch and that needs to land by week of july 24.17:25
dtantsurI mean, my optimistic hope is to finish ironic and ironicclient bits17:25
*** yamamoto has joined #openstack-meeting-317:25
stendulkerrloo: lost connection. rescue status is updated.17:25
rloothx stendulker17:25
rlooTheJulia, mjturek: you think it is doable? ^^17:25
dtantsurmjturek: thanks, that's awesome! we're getting good pace, let's keep it :)17:25
mjturek:)17:26
TheJuliarloo: if we have sufficient review bandwidth and get revisions updated quickly, I think so.17:26
dtantsurderekh (on holidays today) seems to get some progress with testing17:26
rlooTheJulia: thx.17:26
mjturekrloo: I think so. I know that derekh was able to boot from volume with the current code17:27
dtantsur"have sufficient review bandwidth" is the reason I want it on the priority list17:27
TheJuliamjturek: that is music to my ears17:27
mjturek:)17:27
rlooso is bfv the 'highest' priority cuz of nova? are there other features that need nova changes too?17:28
TheJuliadtantsur: makes sense, I really can't be one to review my own code, but I can tackle other stuff :)17:28
dtantsurrloo: it matches the current priorities order17:28
rloothe network stuff worries me too. maybe we should put one of those patches for this week.17:28
dtantsurrloo: but I don't care about relative order too much, to be honest17:28
dtantsurrloo: I'm all for it, given that the OSC spec is nearly done.17:28
dtantsurdoes anyone has a patch in mind for ^^^?17:29
* SotK will keep it similar17:29
SotKsorry, wrong window :/17:29
rloodtantsur: i think the pyhsical network awareness stuff is needed17:29
rloodtantsur: https://review.openstack.org/#/c/461301/ is first in series17:29
rloosambetts: ^^ is that your understanding?17:30
rloomgoddard_: ^^ ?17:30
sambetts+1 that would be a great series to start, I think its a pretty straight forward model and API change for ports17:30
mgoddard_rloo: that's correct17:30
*** mickeys has joined #openstack-meeting-317:30
dtantsurok, it's there. how does the list look now?17:30
dtantsurare we ok with landing the API bits even if they're not wired in?17:31
sambettsnot sure what you mean not wired in?17:31
dtantsurI'm not sure either :) what will happen if users put stuff to the new fields/tables?17:32
* TheJulia wonders which patches exactly17:32
dtantsurTheJulia: I'm talking about https://review.openstack.org/#/c/461301/17:32
sambettsdtantsur: I believe it'll influence how their neutron ports are mapped onto phyiscal interfaces17:32
rloodtantsur: that patch isn't API; it is db change I think17:33
dtantsurooops17:33
* dtantsur is stupid17:33
dtantsurthanks rloo, you're right17:33
sambettsyup, its a classic 3 part patch, DB first, Conductor, then API17:33
mgoddard_until later patches are merged there should be no effects, even if the user modifies the DB17:33
*** yamamoto has quit IRC17:33
dtantsurok, any more objections to the list?17:33
rloodtantsur: i think sambetts mentioned API, but I think he was referring to the entire feature :-)17:33
dtantsurack :)17:33
TheJuliadtantsur: none17:33
rloolist looks good to me17:34
dtantsurok, let's move on?17:34
mgoddard_this one modifies the VIF attachment algorithm, which is where things change: https://review.openstack.org/#/c/470406/117:34
dtantsurthanks mgoddard_17:34
dtantsur#topic Open discussion17:34
*** openstack changes topic to "Open discussion (Meeting topic: ironic)"17:34
dtantsursambetts: do you want to discuss what we do with networking-baremetal?17:34
dtantsurI personally like what the BFV subteam does with their etherpad and a separate meeting17:35
*** mickeys has quit IRC17:35
sambettsyeah I think we can start that stuff again to cover the new features17:35
sambettsnot sure if we need a meeting or not yet17:35
TheJuliaWell, we kind of already have a meeting slot, it is just not actively meeting :)17:36
sambettsmy main question is how are we managing the code that is living in networking-baremetal17:36
dtantsurTheJulia: for networking?17:36
TheJuliadtantsur: yeah, neutron integration specifically17:36
dtantsurmmm, we should use it then17:36
dtantsursambetts: wdym by "managing" here?17:36
NobodyCamdtantsur: saw the comment on my RFE for not adding ports, Thank you. and just a quick thought on none vs noadd I picked NoAdd so it would be confused with the python None in a conf file.17:36
rlooTheJulia: we had that meeting; do we still have the slot? It used to be before this meeting i think.17:36
sambettsRFE's reviews, releases etc etc17:37
dtantsurNobodyCam: good call, hmmm. "disabled"?17:37
TheJuliarloo: we still have it, it was still on eavesdrop last time I looked a few weeks ago17:37
NobodyCamdtantsur: ++ that works!17:37
rlooTheJulia: good17:37
TheJuliahttp://eavesdrop.openstack.org/#Ironic/neutron_Integration_team_meeting17:37
dtantsursambetts: releases are simple: the release team is doing them with the help of the release liaison and the PTL17:37
rlooTheJulia: we should probably put it/link back on our meetings page.17:37
dtantsurTheJulia: I have internal conflicts for this slot :(17:38
dtantsurwell, people can meet without me obvoiusly17:38
TheJuliaI am happy to attend, as long as I'm not on a plane17:38
rloosukhdev was chairing that meeting. do we want neutron folks there, or is this to get our/ironic act together?17:38
dtantsursambetts: RFE reviews, I think, should happen in this meeting. we even have a topic for that.17:38
TheJuliarloo: I think it is get our act together17:39
sambettsdtantsur: do they go into launchpad/ironic?17:39
sambettsor their own project?17:39
TheJuliarloo: we can always adjust the meeting title17:39
dtantsursambetts: we tend to have launchpad projects per project17:39
rlooTheJulia: in that case, we should pick a time where dtantsur can attend.17:39
dtantsursambetts: it depends on the project-config configuration for this repo. we can check after the meeting17:39
*** toure has left #openstack-meeting-317:40
rloosambetts: where does networking-baremetal live? (under neutron, under ironic, under ?)17:40
sambettsrloo: under ironic17:40
sambettsi think (although thats another question I had)17:40
rloosambetts: ok, so we treat it like we treat all/most of the other projects under ironic17:40
rloosambetts: ha ha, so we're not sure. that's probably the first question to answer then.17:40
sambettsI think it should live under Ironic because I believe there will be things in there soon that might become hard requirements to make ironic+neutron work17:41
rloosambetts: are we the only project to ahve this? I thought nova or some other project had a similar thing. networking-baremetal is the plugin for neutron, right?17:41
dtantsursambetts, rloo, it's under ironic: https://github.com/openstack/governance/blob/771e492a997c528f60019d148f9cf824dc294eae/reference/projects.yaml#L174917:41
sambettsrloo: yeah, but neutrons model for plugins is they don't live in neutron17:41
sambettsdtantsur: oh awesome :)17:42
sambettsrloo: s/in/under17:42
rloosambetts: so you answered my question. it lives in ironic then :-)17:42
dtantsurso I'm its PTL for now, and you can throw questions at me :)17:42
dtantsurhttps://github.com/openstack-infra/project-config/blob/master/gerrit/projects.yaml#L5136-L5138 is its configuration17:43
*** stendulker_ has joined #openstack-meeting-317:43
sambettslooks like we have a separate launchpad for it already17:43
dtantsuras I don't see "groups" configuration, then a separate launchpad project should be created17:43
sambettshttps://launchpad.net/networking-baremetal17:43
dtantsuraha17:43
sambettsit appears that we need to change its ownership17:44
dtantsursambetts: we need to ask vsaienk0 to move it under ironic-drivers (both "driver" and "maintainer")17:44
dtantsursambetts, rloo: does it clarify something?17:44
rlooyup17:45
sambettsyup sounds good, so we treat it similar to ironic-inspector and RFE's go into the separate project17:45
rlooi like that it provides deep ironic/neutron integration, not shallow, but deep :-)17:45
sambettshahaha17:45
sambettsdeep dark intergration17:46
*** stendulker has quit IRC17:46
sambettsblack magic if you will17:46
dtantsursambetts: yes. and we have a core subteam, like in ironic-inspector17:46
dtantsurthis will help with reviews17:46
dtantsurs/we have/we can have/17:46
TheJuliasambetts: ironic magic ;)17:46
sambettsI guess it'll have its own section on the whiteboard to o17:47
dtantsuryes17:47
rloodtantsur: the rfes for networking-baremetal may affect ironic code. how do we coordinate that?17:47
dtantsuractually, we have the same situation with sushy and virtualbmc17:47
sambettsmy guess it the same as with insepction ones we create them in inspector with multiple projects affect right?17:47
dtantsurrloo: what we do with inspector is to have a spec againt ironic, if it covers both projects, against inspector otherwise17:47
*** iyamahat has quit IRC17:47
rloodtantsur: ok, that makes sense.17:47
dtantsurthis is about specs. for RFEs you can add many projects to them17:47
sambettsgot it17:48
dtantsurand then approve the overall request17:48
sambettswe don't need a networking-baremetal-specs repo at the momement then?17:48
dtantsursambetts: I don't see a pressing need for that17:48
dtantsurwe started having it for ironic-inspector when we got complex features that did not touch ironic essentially17:49
dtantsurlike inspector HA17:49
sambettsyeah, I think we'll see how the project grows first17:49
dtantsurwith this in mind: please add networking-baremetal, virtualbmc and sushy to your review dashboards, depending on your area of expertise17:50
dtantsur(and of course ironic-inspector and bifrost, but things look happier there for now)17:50
*** galstrom is now known as galstrom_zzz17:51
dtantsuranything else to discuss?17:51
dtantsursambetts: wanna take an action item to establish and etherpad/trello/whatever and revive the meeting?17:51
*** lucasxu has quit IRC17:51
sambettsdtantsur: sure17:52
dtantsurthanks!17:52
dtantsurif nobody has anything to bring up, I'm ready to finish a bit earlier :)17:52
*** lucasxu has joined #openstack-meeting-317:52
TheJuliaThanks!17:53
dtantsurthanks everyone, a good meeting17:53
dtantsur#endmeeting ironic17:53
rloountil next week...17:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:53
openstackMeeting ended Mon Jun  5 17:53:42 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-06-05-17.00.html17:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-06-05-17.00.txt17:53
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-06-05-17.00.log.html17:53
*** dtantsur has left #openstack-meeting-317:53
*** izumi777 has quit IRC17:54
*** Nisha_Agarwal has left #openstack-meeting-317:55
*** anupn has left #openstack-meeting-317:55
*** crushil has left #openstack-meeting-317:56
*** sambetts is now known as sambetts|afk17:57
*** wanyen has quit IRC17:58
*** mgoddard_ has left #openstack-meeting-318:00
*** galstrom_zzz is now known as galstrom18:00
*** MeganR has joined #openstack-meeting-318:02
*** rockyg has joined #openstack-meeting-318:02
*** salv-orlando has quit IRC18:02
*** salv-orlando has joined #openstack-meeting-318:03
*** fellypefca has left #openstack-meeting-318:05
*** iyamahat has joined #openstack-meeting-318:06
*** salv-orlando has quit IRC18:08
*** lucasxu has quit IRC18:08
*** lucasxu has joined #openstack-meeting-318:09
*** stendulker_ has quit IRC18:14
*** sauloaislan has quit IRC18:22
*** nicodemos has left #openstack-meeting-318:24
*** yamahata has joined #openstack-meeting-318:25
*** rbrady has left #openstack-meeting-318:28
*** mickeys has joined #openstack-meeting-318:31
*** mickeys has quit IRC18:36
*** VW has quit IRC18:39
*** VW has joined #openstack-meeting-318:40
*** slaweq has quit IRC18:45
*** zenirc369 has quit IRC18:51
*** rockyg has quit IRC18:59
*** bfournie has left #openstack-meeting-319:04
*** Neptu has joined #openstack-meeting-319:05
*** baha has left #openstack-meeting-319:07
*** lucasxu has quit IRC19:15
*** slaweq has joined #openstack-meeting-319:18
*** MeganR has quit IRC19:22
*** armstrong has joined #openstack-meeting-319:22
*** egallen has joined #openstack-meeting-319:24
*** mickeys has joined #openstack-meeting-319:32
*** armstrong has quit IRC19:34
*** lucasxu has joined #openstack-meeting-319:34
*** mickeys has quit IRC19:36
*** MarkBaker has joined #openstack-meeting-319:39
*** egallen has quit IRC19:41
*** tobberydberg has joined #openstack-meeting-319:45
*** julim has joined #openstack-meeting-319:47
*** tobberydberg has quit IRC19:49
*** julim has quit IRC19:58
*** blancos has joined #openstack-meeting-319:58
ildikov#startmeeting openstack_upstream_institute20:00
openstackMeeting started Mon Jun  5 20:00:09 2017 UTC and is due to finish in 60 minutes.  The chair is ildikov. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: openstack_upstream_institute)"20:00
openstackThe meeting name has been set to 'openstack_upstream_institute'20:00
jungleboyjo/20:00
diablo_rojo_phonHello :)20:01
kmARCo/20:01
ildikovhi :)20:01
blancoso/20:01
ildikovlet's wait a minute more and the dive in20:02
ildikovour agenda for today is here: https://etherpad.openstack.org/p/openstack-upstream-institute-meetings20:03
*** mlavalle has joined #openstack-meeting-320:03
ildikov#topic Announcements20:03
*** openstack changes topic to "Announcements (Meeting topic: openstack_upstream_institute)"20:03
* mlavalle snicks in quetly20:03
*** salv-orlando has joined #openstack-meeting-320:03
ildikovas a recap to the Boston training we have 12 responses to the survey20:04
jungleboyjildikov:  :-(  That is a low response rate.20:04
jungleboyjGuess that means they loved it?  ;-)20:04
ildikovjungleboyj: I think we had just a few more after Barcelona and we had more more people attending there so it's not bad :)20:05
ildikovthe responses are mainly good20:05
ildikovwe need to put a bit more emphasis on letting people know how the training is structured and what they can expect20:05
kmARCany highlights on what went really good / bad?20:05
ildikovfor some it was too beginner for others it was almost a bit too much20:06
ildikovdiablo_rojo_phon: do we plan one more push for getting more feedback and/or summarizing the results?20:07
diablo_rojo_phonI don't know that I'll push that much more since I've already bugged them twice :)20:08
diablo_rojo_phonBut I will work on summarizing results.20:08
ildikovdiablo_rojo_phon: sounds good, tnx20:08
diablo_rojo_phonIf you think I should poke again I can though20:08
ildikovkmARC: people pretty much appreciated the mentors in the room from the different projects20:09
ildikovdiablo_rojo_phon: nah, I just saw the comment on the etherpad and that's why I asked20:09
ildikovdiablo_rojo_phon: maybe that's an older one, I just wnated to confirm20:09
kmARCyeah, I think that was the strongest part of it, kudos to whoever came up with the idea originally :-)20:09
ildikovI think it was a team effort overall to have more project representation20:10
jungleboyjildikov: That is good.  I am glad we were able to have better representation this time around.20:10
ildikovand we will try to extend our liaison team for the upcoming events20:10
ildikovjungleboyj: +120:10
jungleboyjHaving Jay Pipes was a huge help.20:10
ildikov:)20:11
*** MarkBaker has quit IRC20:11
ildikovAlong with all of you who were there!20:12
diablo_rojo_phonI did write up a super user article and it's been posted for those interested20:12
*** MarkBaker has joined #openstack-meeting-320:12
jungleboyjdiablo_rojo_phon:  Link?20:12
kmARCLink!20:12
jungleboyjkmARC:  Jinx.  ;-)20:12
*** mickeys has joined #openstack-meeting-320:12
ildikov#link http://superuser.openstack.org/articles/openstack-upstream-institute-update/20:12
diablo_rojo_phonLet me grab it.20:13
ildikovI hope that's the one :)20:13
diablo_rojo_phonI retweeted it last week20:13
jungleboyjOk.20:13
diablo_rojo_phonildikov: beat me to it :)20:13
ildikovGoogle did :)20:14
jungleboyjAll hail google.20:14
ildikovfurther news is that we're bringing the Upstream Institute training to the OPNFV Summit next week20:14
ildikovit will be overall slightly shorter, but we hope for all the best still :)20:15
*** egallen has joined #openstack-meeting-320:15
ildikovwe have a few volunteers from overall and the local community and expecting 30 students in the room20:15
jungleboyjGreat.  Look forward to hearing how that goes.20:16
ildikovwe will give an update how it went when we're back20:16
ildikovdiablo_rojo_phon, csatari and me will be there with a few more volunteers20:16
ildikovkmARC: BTW did you do any further updates to the image in/after Boston?20:17
kmARCa minimal set of changes, but that was already pushed into the git repo.20:17
diablo_rojo_phonOkay cool. I was gonna copy it onto some jump drives to have in hand.20:18
kmARCI did some further minifactions tho, however that's not production ready. Will update you guys on the current state however I'd just suggest using the latest stable20:18
ildikovkmARC: and is that uploaded as a built image as well?20:18
kmARCyes it is. Let's gimme a task and will update you guys after the CEE days20:18
ildikovkmARC: I was just wondering about that race issue, I'm not concerned about the size for this one20:19
ildikovkmARC: cool, sounds good, thanks :)20:19
ildikovthen we can move on20:20
diablo_rojo_phonThank you :)20:20
ildikov#topic Boston training retrospective20:20
*** openstack changes topic to "Boston training retrospective (Meeting topic: openstack_upstream_institute)"20:20
ildikov#link https://etherpad.openstack.org/p/BOS_OUI_Post_Mortem20:21
*** slaweq has quit IRC20:21
ildikovI think we have the action items mainly covered from the etherpad already20:21
ildikovthe further comments were more on how to organize ourselves better for next time20:21
ildikovwe might write up a training best practices from it20:21
diablo_rojo_phon+1 to that idea20:22
ildikovif anyone wants to take that feel free to, otherwise I will start to put together something and then we can iterate on it20:22
diablo_rojo_phonCan link to it on our wiki20:22
*** lucasxu has quit IRC20:22
diablo_rojo_phonI can help if no one else wants it.20:23
ildikovI didn't think of anything fancy, but as the training gets picked up by others as well and we also need more organization I think it would be a good addition to our materials20:23
ildikovdiablo_rojo_phon: +120:23
ildikovanyone/anything else to the retro?20:24
kmARCildikov: I am happy to point out workflow related issues and suggestions on what-how-when to say and what not :-)20:25
*** slaweq has joined #openstack-meeting-320:25
*** dimtruck is now known as zz_dimtruck20:26
ildikovkmARC: I'll create an etherpad for ideas and post the link on the team channel after the meeting20:26
kmARCperfect20:26
ildikovkmARC: tnx :)20:26
ildikovok, moving on then20:27
ildikov#topic Wiki Updates20:27
*** openstack changes topic to "Wiki Updates (Meeting topic: openstack_upstream_institute)"20:27
ildikovtwo things20:27
ildikovif anyone here hasn't update their info on our team wiki please do so20:28
ildikovlike time zone, etc20:28
*** tobberydberg has joined #openstack-meeting-320:28
ildikov#link https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute20:28
*** egallen has quit IRC20:28
ildikovthe other is, I created another wiki page for people who we have confirmed for an event and attended to help out: https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute_Occasions20:29
*** slaweq has quit IRC20:29
ildikov#link https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute_Occasions20:29
ildikovso we can more easily get a better view and also a history this way20:30
jungleboyjCool.  That is a good addtion!20:30
ildikovas we are planning to bring versions of the training to local events this might help to coordinate that as well20:30
ildikovwe will see how it works out :)20:31
*** shuyingya has joined #openstack-meeting-320:31
ildikovanyone has any questions or further comments to the wiki?20:31
*** slaweq has joined #openstack-meeting-320:32
ildikovok, moving on :)20:32
ildikov#topic Alternating meeting slots proposal20:32
*** openstack changes topic to "Alternating meeting slots proposal (Meeting topic: openstack_upstream_institute)"20:32
*** tobberydberg has quit IRC20:32
ildikovso as we talked about it a short while ago we have a couple of team members in the Europe and Asia areas where this meeting time is either inconvenient or impossible to make20:32
ildikovbased on the recent Doodle poll to find a more Europe-Asia friendly slot we got a winner, which would be Tuesdays at 0900 UTC20:33
ildikovmy proposal would be to start with the new slot next week20:33
ildikovso have this slot for odd weeks and the alternate one on even weeks20:34
ildikovand I hope I checked it right that it's week 23 now :)20:34
ildikovdoes this overall sound acceptable for everyone?20:34
*** cleong has quit IRC20:35
*** skelso has joined #openstack-meeting-320:36
*** shuyingya has quit IRC20:36
mlavalleildikov: yes, according to google calendar, this is week 2320:36
*** slaweq has quit IRC20:36
mlavalleildikov: and yes, the time slot for the odd numbered week is fine with me20:36
ildikovmlavalle: thanks for double checking, I always mess up calendars... :)20:36
ildikovmlavalle: cool, thanks20:37
ildikovis there anyone against the proposal?20:37
mlavalleildikov: on even numbered week, I will be soundly asleep, I hope ;-)20:37
ildikovmlavalle: fair enough :)20:37
jungleboyj:-)  Sounds like it is worth giving a try and see what happens.20:37
ildikovcoolio, then I'll submit a patch to get the slot secured20:38
ildikov#action ildikov to register alternating meeting slots20:38
ildikov#topic Open discussion20:38
mlavalleildikov: another todo is to update the wiki20:38
*** openstack changes topic to "Open discussion (Meeting topic: openstack_upstream_institute)"20:38
ildikovmlavalle: right, will do that too, tnx!20:39
ildikov#action ildikov to update the wiki too20:39
*** VW has quit IRC20:39
ildikovI think I will just add a link to the main meetings page as I should've originally as well :)20:40
*** VW has joined #openstack-meeting-320:40
ildikovany further topics we should discuss?20:40
ildikovthis sounds like a no :)20:41
ildikovthank you all20:41
mlavalleo/20:41
ildikovsee you here in two weeks :)20:42
jungleboyjThank you!20:42
ildikovhave a good day20:42
skelsoo/20:42
jungleboyjildikov:  You too.20:42
ildikov#endmeeting20:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:42
openstackMeeting ended Mon Jun  5 20:42:28 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_upstream_institute/2017/openstack_upstream_institute.2017-06-05-20.00.html20:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_upstream_institute/2017/openstack_upstream_institute.2017-06-05-20.00.txt20:42
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_upstream_institute/2017/openstack_upstream_institute.2017-06-05-20.00.log.html20:42
mlavalleildikov, diablo_rojo_phon: enjoy your trip to China20:42
*** blancos has left #openstack-meeting-320:42
ildikovmlavalle: thanks!20:42
mlavallediablo_rojo_phon: en tu caso, que tengas un feliz viaje a China20:43
diablo_rojo_phonmlavalle: gracias :)20:45
*** lucasxu has joined #openstack-meeting-320:47
*** zz_dimtruck is now known as dimtruck20:48
*** mlavalle has left #openstack-meeting-320:53
*** ansmith has quit IRC20:58
*** MeganR has joined #openstack-meeting-320:59
*** egallen has joined #openstack-meeting-321:01
*** rockyg has joined #openstack-meeting-321:01
*** lucasxu has quit IRC21:07
*** rockyg has quit IRC21:07
*** rockyg has joined #openstack-meeting-321:10
*** tobberydberg has joined #openstack-meeting-321:13
*** rocky_g has joined #openstack-meeting-321:14
*** rockyg has quit IRC21:14
*** tobberydberg has quit IRC21:18
*** rloo has left #openstack-meeting-321:18
*** rocky_g has quit IRC21:19
*** julim has joined #openstack-meeting-321:20
*** slaweq has joined #openstack-meeting-321:21
*** slaweq has quit IRC21:25
*** slaweq has joined #openstack-meeting-321:25
*** rocky_g has joined #openstack-meeting-321:27
*** marst has quit IRC21:29
*** baoli has quit IRC21:34
*** mfedosin has quit IRC21:38
*** gouthamr has quit IRC21:43
*** iyamahat has quit IRC21:43
*** julim has quit IRC21:52
*** slaweq has quit IRC21:53
*** diablo_rojo has quit IRC21:55
*** iyamahat has joined #openstack-meeting-321:55
*** slaweq has joined #openstack-meeting-321:55
*** rpioso has left #openstack-meeting-321:58
*** slaweq has quit IRC22:00
*** MeganR has quit IRC22:01
*** MarkBaker has quit IRC22:07
*** tobberydberg has joined #openstack-meeting-322:08
*** egallen has quit IRC22:08
*** egallen has joined #openstack-meeting-322:09
*** neil__ has quit IRC22:10
*** tobberydberg has quit IRC22:12
*** rocky_g has quit IRC22:13
*** salv-orlando has quit IRC22:19
*** gouthamr has joined #openstack-meeting-322:22
*** neil__ has joined #openstack-meeting-322:23
*** ducttape_ has quit IRC22:31
*** galstrom is now known as galstrom_zzz22:32
*** bobh has quit IRC22:32
*** neil__ has quit IRC22:37
*** gouthamr has quit IRC22:46
*** gouthamr has joined #openstack-meeting-322:48
*** lyan has quit IRC22:49
*** ansmith has joined #openstack-meeting-322:50
*** neil__ has joined #openstack-meeting-322:56
*** slaweq has joined #openstack-meeting-322:56
*** ducttape_ has joined #openstack-meeting-323:00
*** slaweq has quit IRC23:01
*** neil__ has quit IRC23:14
*** skelso has quit IRC23:17
*** marst has joined #openstack-meeting-323:25
*** sdague has quit IRC23:26
*** tobberydberg has joined #openstack-meeting-323:30
*** ducttap__ has joined #openstack-meeting-323:32
*** ducttape_ has quit IRC23:32
*** tobberydberg has quit IRC23:34
*** ducttap__ has quit IRC23:42
*** gouthamr has quit IRC23:43
*** gouthamr has joined #openstack-meeting-323:53
*** baoli has joined #openstack-meeting-323:55
*** slaweq has joined #openstack-meeting-323:57

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