Monday, 2017-04-03

*** yamahata has joined #openstack-meeting-300:02
*** reedip has joined #openstack-meeting-300:25
*** bobh has joined #openstack-meeting-300:38
*** bobh has quit IRC00:44
*** baoli has quit IRC00:52
*** baoli has joined #openstack-meeting-300:58
*** yamahata has quit IRC01:03
*** gcb has joined #openstack-meeting-301:14
*** baoli has quit IRC01:19
*** donghao has joined #openstack-meeting-301:20
*** baoli has joined #openstack-meeting-301:29
*** tuanluong has joined #openstack-meeting-301:35
*** reedip has quit IRC01:40
*** baoli has quit IRC01:43
*** reedip has joined #openstack-meeting-301:59
*** galstrom_zzz is now known as galstrom02:09
*** baoli has joined #openstack-meeting-302:28
*** yamamoto has joined #openstack-meeting-302:29
*** baoli_ has joined #openstack-meeting-302:30
*** baoli has quit IRC02:33
*** galstrom is now known as galstrom_zzz02:34
*** amotoki has joined #openstack-meeting-302:39
*** gouthamr has quit IRC02:41
*** baoli_ has quit IRC02:50
*** baoli has joined #openstack-meeting-302:51
*** amotoki has quit IRC03:00
*** anilvenkata has joined #openstack-meeting-303:06
*** baoli has quit IRC03:16
*** amotoki has joined #openstack-meeting-303:20
*** amotoki has quit IRC03:29
*** yamamoto has quit IRC03:37
*** amotoki has joined #openstack-meeting-303:38
*** VW_ has quit IRC03:45
*** VW has joined #openstack-meeting-303:46
*** reedip has quit IRC03:52
*** reedip has joined #openstack-meeting-304:00
*** amotoki has quit IRC04:01
*** amotoki has joined #openstack-meeting-304:08
*** yamamoto has joined #openstack-meeting-304:16
*** persia has quit IRC04:17
*** psachin has joined #openstack-meeting-304:26
*** pgadiya has joined #openstack-meeting-305:11
*** lamt has quit IRC05:14
*** VW has quit IRC05:16
*** claudiub has joined #openstack-meeting-305:17
*** dimtruck is now known as zz_dimtruck05:24
*** zz_dimtruck is now known as dimtruck05:24
*** lpetrut has joined #openstack-meeting-305:30
*** lpetrut has quit IRC05:33
*** dimtruck is now known as zz_dimtruck05:33
*** Fdaisuke has joined #openstack-meeting-305:40
*** IRCFrEAK has joined #openstack-meeting-305:47
*** IRCFrEAK has left #openstack-meeting-305:50
*** yamahata has joined #openstack-meeting-305:56
*** pgadiya has quit IRC06:04
*** makowals_ has quit IRC06:05
*** gcb has quit IRC06:07
*** ltomasbo|away is now known as ltomasbo06:08
*** nkrinner_afk is now known as nkrinner06:20
*** cshastri has joined #openstack-meeting-306:25
*** tobberydberg has joined #openstack-meeting-306:25
*** tobberyd_ has joined #openstack-meeting-306:26
*** tobberydberg has quit IRC06:29
*** makowals has joined #openstack-meeting-306:30
*** bobh has joined #openstack-meeting-306:37
*** bobh has quit IRC06:42
*** ralonsoh has joined #openstack-meeting-306:43
*** andreas_s has joined #openstack-meeting-306:50
*** belmoreira has joined #openstack-meeting-306:50
*** pcaruana has joined #openstack-meeting-306:57
*** ccamacho has joined #openstack-meeting-307:00
*** zz_dimtruck is now known as dimtruck07:01
*** neiljerram has joined #openstack-meeting-307:03
*** dimtruck is now known as zz_dimtruck07:11
*** matrohon has joined #openstack-meeting-307:11
*** neiljerram has quit IRC07:19
*** tobberydberg has joined #openstack-meeting-307:30
*** tobberyd_ has quit IRC07:34
*** amotoki_ has joined #openstack-meeting-307:41
*** MarkBaker has quit IRC07:41
*** xiaofandh12 has joined #openstack-meeting-307:43
*** amotoki has quit IRC07:44
*** donghao has quit IRC07:46
*** zz_dimtruck is now known as dimtruck08:02
*** rossella_s has joined #openstack-meeting-308:09
*** dimtruck is now known as zz_dimtruck08:12
*** jtomasek has joined #openstack-meeting-308:22
*** MarkBaker has joined #openstack-meeting-308:26
*** reedip has quit IRC08:28
*** bobh has joined #openstack-meeting-308:38
*** lpetrut has joined #openstack-meeting-308:41
*** bobh has quit IRC08:43
*** yamahata has quit IRC08:48
*** mtreinish has quit IRC08:53
*** kaz_ has joined #openstack-meeting-308:54
*** neiljerram has joined #openstack-meeting-308:54
*** kaz_ has quit IRC08:55
*** mtreinish has joined #openstack-meeting-308:57
*** stevejims has joined #openstack-meeting-309:02
*** tobberydberg has quit IRC09:02
*** zz_dimtruck is now known as dimtruck09:02
*** tobberydberg has joined #openstack-meeting-309:03
*** neiljerram has quit IRC09:04
*** reedip has joined #openstack-meeting-309:08
*** dimtruck is now known as zz_dimtruck09:12
*** MarkBaker has quit IRC09:17
*** itamaro has joined #openstack-meeting-309:18
*** MarkBaker has joined #openstack-meeting-309:24
*** amotoki_ has quit IRC09:25
*** sambetts|afk is now known as sambetts09:25
*** lpetrut has quit IRC09:26
*** abalutoiu has joined #openstack-meeting-309:28
*** MarkBaker has quit IRC09:34
*** lpetrut has joined #openstack-meeting-309:48
*** lpetrut has quit IRC09:51
*** lpetrut has joined #openstack-meeting-309:53
*** lpetrut has quit IRC09:53
*** zz_dimtruck is now known as dimtruck10:03
*** xiaofandh12 has quit IRC10:09
*** lpetrut has joined #openstack-meeting-310:10
*** dimtruck is now known as zz_dimtruck10:13
*** donghao has joined #openstack-meeting-310:15
*** donghao has quit IRC10:16
*** donghao has joined #openstack-meeting-310:17
*** lpetrut has quit IRC10:21
*** sdague has joined #openstack-meeting-310:23
*** lpetrut has joined #openstack-meeting-310:27
*** stendulker has joined #openstack-meeting-310:31
*** lpetrut has quit IRC10:34
*** lpetrut has joined #openstack-meeting-310:34
*** psachin has quit IRC10:34
*** lpetrut has quit IRC10:39
*** psachin has joined #openstack-meeting-310:51
*** shoaib has joined #openstack-meeting-310:52
*** zz_dimtruck is now known as dimtruck11:04
*** alexismonville has quit IRC11:04
*** shoaib has quit IRC11:09
*** dimtruck is now known as zz_dimtruck11:14
*** neiljerram has joined #openstack-meeting-311:20
*** MarkBaker has joined #openstack-meeting-311:20
*** MarkBaker has quit IRC11:20
*** MarkBaker has joined #openstack-meeting-311:21
*** stendulker has quit IRC11:23
*** ccamacho is now known as ccamacho|lunch11:24
*** alexismonville has joined #openstack-meeting-311:27
*** ppiela_ has joined #openstack-meeting-311:27
*** ppiela has quit IRC11:29
*** alexismonville has quit IRC11:31
*** shuyingya has joined #openstack-meeting-311:34
*** VW has joined #openstack-meeting-311:35
*** bobh has joined #openstack-meeting-311:37
*** ttx has quit IRC11:38
*** ttx has joined #openstack-meeting-311:38
*** alexismonville has joined #openstack-meeting-311:38
*** lpetrut has joined #openstack-meeting-311:41
*** dhellmann has quit IRC11:42
*** dhellmann has joined #openstack-meeting-311:42
*** tuanluong has quit IRC11:42
*** lpetrut has quit IRC11:44
*** neiljerram has quit IRC11:47
*** jgr is now known as jgrassler11:49
*** ccamacho|lunch is now known as ccamacho11:56
*** psachin has quit IRC11:58
*** zz_dimtruck is now known as dimtruck12:05
*** MarkBaker has quit IRC12:06
*** psachin has joined #openstack-meeting-312:11
*** VW has quit IRC12:12
*** jjung has joined #openstack-meeting-312:12
*** dimtruck is now known as zz_dimtruck12:15
*** alexismonville has quit IRC12:16
*** elmiko_ is now known as elmiko12:19
*** elmiko has left #openstack-meeting-312:20
*** gouthamr has joined #openstack-meeting-312:21
*** bobh has quit IRC12:27
*** lpetrut has joined #openstack-meeting-312:34
*** neiljerram has joined #openstack-meeting-312:39
*** tonytan4ever has quit IRC12:41
*** edleafe- is now known as edleafe12:51
*** alexismonville has joined #openstack-meeting-312:55
*** baoli has joined #openstack-meeting-313:00
*** lyan has joined #openstack-meeting-313:01
*** bobmel has joined #openstack-meeting-313:03
*** tobberyd_ has joined #openstack-meeting-313:03
*** zz_dimtruck is now known as dimtruck13:06
*** tobberydberg has quit IRC13:08
*** alexismonville has quit IRC13:09
*** cleong has joined #openstack-meeting-313:11
*** qwebirc90446 has joined #openstack-meeting-313:14
*** dimtruck is now known as zz_dimtruck13:15
*** qwebirc90446 has quit IRC13:15
*** MarkBaker has joined #openstack-meeting-313:17
*** srobert has joined #openstack-meeting-313:18
*** lpetrut has quit IRC13:20
*** dhellmann has quit IRC13:24
*** tobberyd_ has quit IRC13:24
*** tobberydberg has joined #openstack-meeting-313:25
*** dhellmann has joined #openstack-meeting-313:25
*** makowals_ has joined #openstack-meeting-313:28
*** baoli has quit IRC13:29
*** tobberydberg has quit IRC13:29
*** tobberydberg has joined #openstack-meeting-313:30
*** makowals has quit IRC13:30
*** baoli has joined #openstack-meeting-313:30
*** belmorei_ has joined #openstack-meeting-313:32
*** belmoreira has quit IRC13:33
*** donghao has quit IRC13:40
*** gcb has joined #openstack-meeting-313:41
*** sdoyle has joined #openstack-meeting-313:45
*** rossella_s has quit IRC13:46
*** rossella_s has joined #openstack-meeting-313:47
*** akuznetsova has joined #openstack-meeting-313:57
*** akuznetsova_ has joined #openstack-meeting-313:58
*** belmorei_ has quit IRC13:58
*** makowals_ has quit IRC13:58
gcb#startmeeting oslo14:00
openstackMeeting started Mon Apr  3 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
gcbcourtesy ping for amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dims,dougwig, e0ne, electrocucaracha, flaper87, garyk, gcb, GheRivero,haypo, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz, lhx_, lifeless, lxsli, Nakato, ozamiatin, rbradfor, redrobot,crushil, rloo,rpodolyaka, sergmelikyan, sileht, spamaps, sreshetnyak, sreshetnyak, stevemar,therve, thinrichs, toabctl, viktors, zhiyan, zzzeek14:00
dimso/14:00
rpodolyakao/14:00
shuyingyao/14:01
*** belmoreira has joined #openstack-meeting-314:01
gcb\o/14:01
*** lpetrut has joined #openstack-meeting-314:01
gcb#topic Red flags for/from liaisons14:02
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"14:02
*** makowals has joined #openstack-meeting-314:02
*** bobmel_ has joined #openstack-meeting-314:02
*** akuznetsova_ has quit IRC14:02
gcbI checked our periodic-job, there is no red flags14:03
dimsnice!14:03
jungleboyjNo red flags from Cinder.  :-)14:03
*** mrunge_ has joined #openstack-meeting-314:03
gcbshyingya, any issues in Sahara from oslo side ?14:03
gcbjungleboyj, yeah, thanks14:03
*** bobh has joined #openstack-meeting-314:03
shuyingyathere is no special. But I would like to know how to check the red flags. ^^14:04
*** lpetrut has quit IRC14:04
gcbshuyingya,  just check sahara, if there is issue related with oslo14:04
*** amotoki has joined #openstack-meeting-314:05
shuyingyagcb, Yeah. no special means no patch related to oslo14:05
*** bobmel has quit IRC14:05
shuyingya\o/14:05
gcbshuyingya,  we have periodic jobs like  http://status.openstack.org/openstack-health/#/g/build_name/periodic-nova-py27-with-oslo-master14:05
gcbto make sure master branch oslo libs don't break things before we release them14:06
*** belmoreira has quit IRC14:06
shuyingyathanks, gcb.14:06
gcbokay, let's move on14:06
gcb#topic Releases for Pike14:06
*** openstack changes topic to "Releases for Pike (Meeting topic: oslo)"14:06
*** zz_dimtruck is now known as dimtruck14:06
*** electrocucaracha has joined #openstack-meeting-314:06
*** lucasxu has joined #openstack-meeting-314:07
*** galstrom_zzz is now known as galstrom14:07
gcb#link https://review.openstack.org/452606 our weekly releases were just merged14:07
*** rbak has joined #openstack-meeting-314:08
gcbAs dhellmann suggested ,we released futurist 1.014:08
gcb#Stuck reviews14:09
gcb#topic Stuck reviews14:09
*** openstack changes topic to "Stuck reviews (Meeting topic: oslo)"14:09
gcbAnyone have specific review to raise ?14:10
*** VW has joined #openstack-meeting-314:10
gcbI have one #link https://review.openstack.org/328692.  I wonder this will break some projects14:10
dimsfyi, i am cleaning up old oslo.messaging reviews14:11
*** itamaro has quit IRC14:11
gcbMake method set_override's parameter enforce_type=True by default, this enforces developer to write valid test cases about config options. please help review when you're free14:12
*** haleyb has quit IRC14:12
dimsgcb : let's drop a note to -dev and remove it after a few days14:12
gcbdims: thanks, I can aslo help review oslo.messaging patches14:13
*** diablo_rojo has joined #openstack-meeting-314:13
gcbdims:  ++, will send to -dev before we merge it14:13
*** reedip has quit IRC14:13
gcbThere are aslo some updates about oslo this week14:15
*** bobmel has joined #openstack-meeting-314:15
jungleboyjI will also bring that up in the weekly Cinder meeting to make people aware.  I am not sure if we have that already set.  Will check.14:15
gcbjungleboyj, thanks14:16
jungleboyjNo problem.14:16
gcb1. #link https://review.openstack.org/449137 Move castellan under Oslo governance, thanks dims14:16
*** galstrom is now known as galstrom_zzz14:16
gcb2. #link http://lists.openstack.org/pipermail/openstack-dev/2017-March/113941.html   - Storing configuration options in etcd(?)14:17
dimsanyone from barbican around? :)14:17
gcb3. #link http://lists.openstack.org/pipermail/openstack-dev/2017-March/114823.html  Introduction of new driver for oslo.messaging14:17
gcbdims: I don't think so14:18
*** bobmel_ has quit IRC14:18
dimsgcb : the #3 was for April 1st :)14:18
dimsEmilienM : are we going to do #2 above for pike?14:19
*** dimtruck is now known as zz_dimtruck14:19
EmilienMhello14:19
EmilienMdims: I hope we can make progress14:20
gcbdims: really?  you must be joking ,  engineers shouldn't do that14:20
dimsgcb :) it was a joke14:20
EmilienMdims: do we have people working on it?14:20
dimsEmilienM : nope14:20
EmilienMyeah that's the problem14:21
EmilienMa lot of folks want it but not sure anyone is active on this task14:21
dimsEmilienM : i did some background work, got a library that works with eventlet + etcd3 - https://pypi.python.org/pypi/etcd3gw14:21
dimsand will be adding support in tooz to use that library14:21
*** kgiusti has joined #openstack-meeting-314:21
EmilienMdims: i'll check with therve, he also started something a few weeks ago14:21
dimsEmilienM : i thought bnemec may be interested and dhellmann was asking for specific details i think14:22
dimsthanks EmilienM14:22
EmilienMok I'll also check with Ben14:22
gcbEmilienM, dims: that's really a useful feature, I can help review(learn etcd at the same time)14:22
dimsgcb : cool. will ping you on the review14:23
gcbdims: sure14:23
gcbokay, that's all update about oslo14:24
gcb#topic Open discussion14:24
*** openstack changes topic to "Open discussion (Meeting topic: oslo)"14:24
kgiustiI've got one!14:25
kgiustiI've been working with the Massively Distributed working group14:25
*** amotoki has quit IRC14:25
kgiustitrying to help them scale with respect to messaging...14:25
kgiustiWe're trying to determine which backends make sense for a given deployment14:26
*** crushil has joined #openstack-meeting-314:26
*** reedip has joined #openstack-meeting-314:26
kgiustifor example, why would one use ZeromMQ instead of rabbitmq?14:26
kgiustior kafka?  What are the deployment strategies14:27
kgiusti?  So I'm proposing a forum topic on this: http://forumtopics.openstack.org/cfp/details/6214:27
kgiusti@ the boston summit.14:27
gcbkgiusti,  the question we talked many times before :-)14:27
dimskgiusti : ++14:27
kgiustiI'd like to work towards some recommendations, backed up with data ideally :)14:28
gcbkgiusti, ++14:28
*** lyan has quit IRC14:29
kgiustiTBH - I'm not really an expert in some of these drivers, so it would be great if the other driver specialists would weigh in here and help out.14:29
*** lyan has joined #openstack-meeting-314:29
kgiustiIn any case, something to think about.14:29
*** bobh has quit IRC14:30
gcbkgiusti,  we use rabbit backend in production, would like to help if I can :-)14:31
kgiustigcb great thanks - also anyone interested in joining the MDWG discussions that would be great.14:31
*** galstrom_zzz is now known as galstrom14:32
kgiustifyi: https://wiki.openstack.org/wiki/Massively_Distributed_Clouds14:32
*** bnemec has joined #openstack-meeting-314:32
*** seanatcisco has joined #openstack-meeting-314:33
gcbkgiusti, you got my questions, haha, just want to ask lol14:33
*** cshastri has quit IRC14:33
*** zz_dimtruck is now known as dimtruck14:33
kgiustiOne other topic:14:33
kgiustiI've got a proposal accepted @ boston to talk about "dual messaging backends"14:34
kgiustie.g.: rabbitmq for notifications, Zeromq for rpc, etc...14:34
kgiustiIf anyone would like to join the presentation and help out, just ping me on irc.  Thanks.14:35
* jungleboyj 's head explodes14:35
kgiustiWed 10th 11 am14:35
kgiustijungleboyj: yeah that happens alot.14:36
jungleboyjI have a hard enough time understanding the setup with one message service.  :-)14:36
jungleboyjkgiusti: Ok, glad it isn't just me.14:36
kgiusti:)  hopefully with Triple0, etc, support it will be a great bit less painful than it is now.14:36
*** haleyb has joined #openstack-meeting-314:37
kgiustijungleboyj: but there are tests in CI (heat I believe) that are doing this atm.14:37
jungleboyjOk, that is good.14:37
gcbjungleboyj,  just checkout #link http://forumtopics.openstack.org/cfp/details/79 , bring all of your pain points about oslo  there14:38
kgiustibut it would be great if we could get kafka, zeromq folks to join the preso14:38
gcbkgiusti, agree14:39
jungleboyjkgiusti:  Thanks.14:39
kgiustithanks everyone.14:40
gcbkgiusti, please go ahead, hope I didn't disturb you :-)14:41
kgiustigcb: not at all - that's all I have for now.14:41
gcbokay,  anyone has other things to discuss ?14:42
gcbI think we can call it a meeting, and back to openstack-oslo to discuss any oslo stuff14:44
gcbBTW, Chinese have 3 days holiday,  I will be back on April 514:45
gcbthanks everyone14:45
jungleboyjSounds good.  Thanks gcb14:46
jungleboyjHave a good vacation.14:46
*** julim has quit IRC14:46
gcbjungleboyj,  thanks, have a nice day14:47
gcb#endmeeting14:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:47
openstackMeeting ended Mon Apr  3 14:47:11 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-04-03-14.00.html14:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-04-03-14.00.txt14:47
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-04-03-14.00.log.html14:47
*** electrocucaracha has left #openstack-meeting-314:47
*** bsilverman_9 has quit IRC14:47
*** bsilverman_ has joined #openstack-meeting-314:47
*** baoli has quit IRC14:49
*** julim has joined #openstack-meeting-314:49
*** marst has quit IRC14:49
*** julim has quit IRC14:50
*** sharatss has joined #openstack-meeting-314:50
*** julim has joined #openstack-meeting-314:51
*** kgiusti has left #openstack-meeting-314:54
*** mgershen has joined #openstack-meeting-314:55
*** lpetrut has joined #openstack-meeting-314:55
*** lyan has quit IRC14:56
*** bobh has joined #openstack-meeting-314:56
*** marst has joined #openstack-meeting-314:56
*** lpetrut has quit IRC14:56
*** tobberyd_ has joined #openstack-meeting-314:57
*** tobberyd_ has quit IRC14:57
*** lyan has joined #openstack-meeting-314:58
*** tobberyd_ has joined #openstack-meeting-314:58
*** rbrady has joined #openstack-meeting-314:58
*** amotoki has joined #openstack-meeting-314:59
*** sdoyle has quit IRC15:00
*** tobberydberg has quit IRC15:00
*** bobmel has quit IRC15:01
rakhmerov#startmeeting Mistral15:01
openstackMeeting started Mon Apr  3 15:01:28 2017 UTC and is due to finish in 60 minutes.  The chair is rakhmerov. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: Mistral)"15:01
openstackThe meeting name has been set to 'mistral'15:01
d0ugalHey all!15:01
*** bobmel has joined #openstack-meeting-315:01
mgersheno/15:01
sharatsshi15:01
akuznetsovahi there15:01
rakhmerovhi15:02
rbradyo/15:02
rakhmerovhi all15:02
rakhmerov1 sec15:02
*** apetrich has joined #openstack-meeting-315:03
rakhmerov#topic Review Action items15:03
*** openstack changes topic to "Review Action items (Meeting topic: Mistral)"15:03
rakhmerov1. d0ugal to check for doc liaison tasks15:03
*** toure has joined #openstack-meeting-315:03
*** sdoyle has joined #openstack-meeting-315:03
d0ugaloops, I have not done this.15:03
rakhmerov:)15:04
*** tobberyd_ has quit IRC15:04
rakhmerov#action d0ugal to check for doc liaison tasks15:04
tourehello...15:04
rakhmerovtoure: hey15:04
rakhmerov2. rakhmerov: ask Michal to review the spec about mistral-extra15:04
rakhmerovdone15:04
*** makowals has quit IRC15:04
rakhmerov3. mgershen/team to talk with Renat about bug https://bugs.launchpad.net/mistral/+bug/167237915:04
openstackLaunchpad bug 1672379 in Mistral "default task on error not running when task fail to evaluate input" [Undecided,Invalid]15:04
d0ugalrakhmerov: I think maybe that wasn't needed in the end15:05
rakhmerovyes15:05
*** corey__ has joined #openstack-meeting-315:05
rakhmerovwe've kind of touched that, it's not an easy thing to solve now15:05
rakhmerov4. rbrady start sensitive data spec15:05
*** anilvenkata has quit IRC15:05
*** bobmel has quit IRC15:05
*** cleong has quit IRC15:05
rakhmerovit was done15:06
mgershenabout 3, should I open a blueprint?15:06
tourehey rakhmerov once I finish fighting with gerrit I have the client code ready for review15:06
rakhmerovit even has one +215:06
toure:)15:06
rakhmerovtoure: for error analysis?15:06
toureyup15:06
rakhmerovawesome )15:06
touremerge conflicts15:06
d0ugal#link https://review.openstack.org/45085315:06
toure:(15:06
rakhmerovmgershen: yes, please15:06
d0ugal^ that's the sensitive data spec15:06
rakhmerovyes15:07
*** makowals has joined #openstack-meeting-315:07
rakhmerovok15:07
mgershenrakhmerov: do you want to add an action to make sure I won't forget?15:07
rakhmerov#action mgershen: create a BP about "on-error" semantics15:08
rakhmerov#topic Current status (quick info from team members)15:08
*** openstack changes topic to "Current status (quick info from team members) (Meeting topic: Mistral)"15:08
*** crushil has quit IRC15:09
rakhmerovmy status: reviewing, working on advanced publishing (actually got stuck with lang changes unexpectedly, will probably have to do some serious refactoring first), investigating an issue introduced by new SQLAlchemy15:09
rakhmerovthe last one was finally fixed today15:09
rakhmerovso please provide a short update if you have anything15:10
d0ugalI'm now working on mistral-extra, and starting the ground work for moving the OpenStack actions over. The spec merged today (thanks for reviews!)15:10
mgershenI will have almost no time in the next few weeks to work on mistral, but if something needs reviewing try to ping me.15:10
rakhmerovthat is great15:10
*** seanatcisco has quit IRC15:10
rakhmerovmgershen: sure, understandable15:11
rakhmerovjust FYI: akuznetsova is now helping us with some tasks again (which is awesome)15:11
rakhmerovakuznetsova: could you please tell a little bit about your activities?15:12
akuznetsovayes, for the old times' sake15:12
rakhmerov:)15:12
akuznetsovaI've published fixes for two bugs15:12
* d0ugal needs to catch up with reviews.15:13
*** makowals has quit IRC15:13
rakhmerovd0ugal: yes! :)15:13
akuznetsovaand looked through the list of bugs in mistralclient, there were a lot of old bugs which I closed15:13
d0ugalbug triage ++15:13
rakhmerovd0ugal: yeah, I was actually going to do that today at the meeting )15:14
rakhmerovbut akuznetsova volunteered to do some pre-filtering15:14
d0ugalgreat15:14
rakhmerovakuznetsova: thanks a lot!15:14
mgershenthank you akuznetsova :)15:14
apetrichI'm working on moving some imports from mistral to mistral-lib mostly in tripleo-common (sorry for for the tripleo centric status)15:15
akuznetsovarakhmerov, mgershen you are welcome15:15
d0ugalapetrich: it is extremely valuable for Mistral to show this stuff working, it is all theoretical so far :)15:15
rakhmerovmgershen, d0ugal: we got a bunch of patches passed through check queue today after we rebased them after merging an SQLA issue so please try to find some time to review them15:16
d0ugalsure15:16
mgershenrakhmerov: do you have links?15:16
rakhmerovd0ugal, apetrich: this is very very good, the only thing I'm worried about is that isn't it too early? :)15:17
apetrichd0ugal, I can see that15:17
rakhmerovmgershen: there's too many of them, just look at gerrit pls15:17
d0ugalrakhmerov: possibly - but we need to start some time and it'll help direct us what we need to do next. We wont land anything in tripleo yet.15:17
apetrichrakhmerov, it is more of proof of concept and identify the early pitfalls15:17
d0ugal+115:17
rakhmerovooh, ok15:17
rakhmerovif so then it's fine15:17
rakhmerovbecause otherwise the APIs may not be stable yet etc.15:18
rakhmerovthen this is good really15:18
mgershenrakhmerov: ok, I will.15:18
rakhmerovok15:18
rakhmerovmgershen: I just usually look at "Watched Changes" tab and see patches that recently changed on the top15:19
rakhmerovok, is there anything else on that?15:21
rakhmerovrbrady: do you have any updates today?15:21
*** baoli has joined #openstack-meeting-315:21
rbradyrakhmerov: thrash took care of the spec, I've only done reviews since last week15:22
rakhmerovok, thanks15:22
rakhmerovgood15:22
rakhmerovrbrady: as far as mistral-lib, are you planning to make more changes in the near future?15:22
rakhmerovrbrady: what do you think is now left?15:23
rakhmerovfrom what we planned15:23
rbradyrahkmerov: I think the next steps are the keystone_utils and the openstack actions15:23
d0ugalWe need Mistral to depend on msitral-lib and to pass the context15:23
d0ugalrbrady: ^ I think we need that first maybe, but it is easy to hack in for testing :)15:23
rbrady^^ and what d0ugal said :)15:23
*** baoli has quit IRC15:24
*** crushil has joined #openstack-meeting-315:24
d0ugalI have a patch locally that does it, I could put it up for review but we need mistral-lib in global-requirements first15:24
d0ugalI'll post it as a starting point at least.15:24
rakhmerovyes15:24
rakhmerovagree15:24
rakhmerovd0ugal: having it in global-requirements should not be a huge problem, right?15:25
rakhmerovafaik15:25
d0ugalrakhmerov: no, that should be easy15:25
d0ugalI just need to find the process and follow it15:25
rakhmerovok15:26
d0ugaland we need to figure out rpm packaging for the tripleo side - just adding the dep will break tripleos CI I think15:26
d0ugalbut again, that should be quite easy.15:26
rakhmerovyep15:27
rakhmerovso, we can probably go to an open discussion15:27
rakhmerovI don't have any special topics today15:27
rakhmerovif you do please bring them up15:28
rakhmerov#topic Open Discussion15:28
*** openstack changes topic to "Open Discussion (Meeting topic: Mistral)"15:28
*** annegentle has joined #openstack-meeting-315:28
rakhmerovone thing I'd like to share about what I'm doing is that I stumbled on making changes in workflow language in the last few days15:29
rakhmerovI found that it became very hard to make such changes15:29
d0ugalWhat makes it so difficult?15:29
rakhmerovthis Spec class hierarchy became enormously complex15:29
d0ugalah15:29
d0ugalThe code in mistral.lang.*?15:30
rakhmerovd0ugal: too many places to change in order to make even relatively small changes15:30
rakhmerovyes15:30
d0ugalInteresting, I wonder how we can make it easier15:30
rakhmerovand then if you look at how to alter tests it's not easier )15:30
rakhmerovd0ugal: yeah, that's what I'm thinking about now15:30
rakhmerovI have some ideas, will try to implement them15:31
rakhmerovone more thing related to that is we may want to have a new version of the language some time in the future15:31
rakhmerovand I believe it may happen relatively soon15:31
*** baoli has joined #openstack-meeting-315:31
rakhmerovbecause we've been adding more and more feature into the language15:32
*** revon has joined #openstack-meeting-315:32
rakhmerovthey are all backwards compatible and hence we lose some opportunities to make the lang more concise and elegant15:32
d0ugalMigrating workflows doesn't sound like fun :)15:32
rakhmerovno, wait :)15:32
rakhmerovI didn't mean that )15:32
d0ugalhaha, I know15:33
*** sharatss has quit IRC15:33
rakhmerovwhat I meant is that we'll have to support more than one language version15:33
*** joanna__ has joined #openstack-meeting-315:33
rakhmerovI know, sounds scary15:33
d0ugalyup, but even in that case we would want to upgrade older workflows over time.15:33
rakhmerovand especially scary for me after I looked again at how it's now implemented :)15:33
d0ugallol15:33
rakhmerovd0ugal: yeah, true we'll probably need to provide some aid to upgrade to a newer version15:34
rakhmerovanyway, this is something that I've discussed with a number of people already and seems like this idea of the new lang version may not be that theoretical15:34
rakhmerovso, that's just one thing I'm involved in now15:35
d0ugalcool, it would be interesting to see those ideas.15:35
rakhmerovideally I'd like to improve it somehow15:35
rakhmerovand btw, I found one thing that makes WF validation slower, I'll fix it soon15:35
rakhmerovyeah, the mechanism is powerful but it became too heavy15:36
rakhmerovthat is all from my side15:36
d0ugalI don't really have anything to discuss this week.15:37
rakhmerovguys, next time let's sync on Pike-1 tasks15:37
d0ugalsure15:37
toureack15:37
*** crushil has quit IRC15:37
rakhmerovplease try to find time to check if you're going to meet the scope of Pike-115:37
rakhmerovanother topic I'd like to bring up next week is something I discussed with my boss at Nokia recently15:38
rakhmerovso essentially I set up 4 goals for 2017 regarding Mistral15:39
*** amotoki has quit IRC15:39
rakhmerovmostly from our business perspective15:39
rakhmerovbut anyway, I think these goals reflect my vision of how Mistral should evolve in the next year15:39
rakhmerovI'd be interested in discussing these goals with you15:40
d0ugalcool15:40
touresounds good15:40
rakhmerovso that we all understand the direction15:40
d0ugalSounds like it'll be a busy meeting :)15:40
rakhmerovyes15:40
*** stevejims has quit IRC15:40
rakhmerovmy suggestion would be even to declare these goals (if we agree on them) somewhere, in the spec repo or a wiki (seriously outdated now btw)15:41
d0ugala spec?15:41
rakhmerovmaybe a spec, yes15:41
rakhmerovso, just to be even more clear: I believe these goals is the 3-4 main things that we should be focusing on in order to make the project more successful15:42
rakhmerovand attract more people to it (both users and contributors)15:42
rakhmerovok, details next time )15:42
rakhmerovI am done for sure15:42
* toure waits for details 15:42
rakhmerovnow15:42
toure:)15:42
d0ugallook forward to it :)15:42
d0ugaltoure: haha, rakhmerov is teasing us!15:43
rakhmerov:))15:43
toureindeed15:43
*** tonytan4ever has joined #openstack-meeting-315:43
tourehehe15:43
rakhmerovyeah, may be a little :)15:43
rakhmerovI've been teasing d0ugal for a looong time with a UI tool :)15:43
rakhmerovthat is something I'd really love to demonstrate some time soon15:43
tourecool15:44
tourecan't wait to see it15:44
d0ugal+115:44
rakhmerovI'm going to bring that up soon with my management in order to find out when and how we're going to announce it15:44
rakhmerovok15:44
*** julim has quit IRC15:45
rakhmerovanything else may be?15:45
d0ugalnot from me15:45
rakhmerovor we can finish for today15:45
tourenothing for me15:45
mgershennothing for me15:45
akuznetsovanothing from my side15:45
*** nhairston has joined #openstack-meeting-315:46
*** VW has quit IRC15:46
*** VW has joined #openstack-meeting-315:46
rakhmerovok15:46
rakhmerovthank you all for coming and for the interesting discussion15:46
rakhmerovsee you next week15:46
d0ugalthanks all!15:46
tourehave a good one15:47
rakhmerovhave a wonderful week guys )15:47
akuznetsovathanks, bye15:47
rakhmerovbye15:47
toureta15:47
rakhmerov#endmeeting15:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:47
openstackMeeting ended Mon Apr  3 15:47:16 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/mistral/2017/mistral.2017-04-03-15.01.html15:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/mistral/2017/mistral.2017-04-03-15.01.txt15:47
openstackLog:            http://eavesdrop.openstack.org/meetings/mistral/2017/mistral.2017-04-03-15.01.log.html15:47
*** rbrady has left #openstack-meeting-315:48
*** toure has left #openstack-meeting-315:48
*** nkrinner is now known as nkrinner_afk15:51
*** pcaruana has quit IRC15:53
*** andreas_s has quit IRC15:56
*** bobmel has joined #openstack-meeting-315:59
*** rpioso has joined #openstack-meeting-315:59
*** ijw has joined #openstack-meeting-316:01
*** rpioso has quit IRC16:01
*** iyamahat has joined #openstack-meeting-316:01
ijw#startmeeting networking-vpp16:01
openstackMeeting started Mon Apr  3 16:01:34 2017 UTC and is due to finish in 60 minutes.  The chair is ijw. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: networking-vpp)"16:01
openstackThe meeting name has been set to 'networking_vpp'16:01
*** mgoddard has joined #openstack-meeting-316:01
ijwAnybody about?16:01
*** bobmel_ has joined #openstack-meeting-316:01
*** mgoddard has left #openstack-meeting-316:02
*** matrohon has quit IRC16:03
*** bobmel has quit IRC16:03
*** gcb has quit IRC16:03
*** yamahata has joined #openstack-meeting-316:05
*** iyamahat has quit IRC16:06
ijw#info Port resync on restart of the agent has just been approved16:07
ijw#info provisioning_blocks is now in use for delaying L2 binding until all connectivity is established16:07
*** vgadiraj_ has joined #openstack-meeting-316:08
*** donghao has joined #openstack-meeting-316:08
ijw#The L3 plugin will shortly be added.16:08
ijw#info The L3 plugin will shortly be added.16:08
ijw#info The launchpad buglist has been updated to reflect bugs and RFEs for 17.04.  Please refer to that for work remaining, and feel free to add any tests you consider valuable.16:08
ijw#endmeeting16:08
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:08
openstackMeeting ended Mon Apr  3 16:08:57 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:09
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_vpp/2017/networking_vpp.2017-04-03-16.01.html16:09
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_vpp/2017/networking_vpp.2017-04-03-16.01.txt16:09
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_vpp/2017/networking_vpp.2017-04-03-16.01.log.html16:09
*** psachin has quit IRC16:10
*** galstrom is now known as galstrom_zzz16:11
*** galstrom_zzz is now known as galstrom16:12
*** tobberydberg has joined #openstack-meeting-316:16
*** d0ugal has quit IRC16:19
*** tobberydberg has quit IRC16:20
*** lucasxu has quit IRC16:25
*** julim has joined #openstack-meeting-316:25
*** Patifa has joined #openstack-meeting-316:30
*** crushil has joined #openstack-meeting-316:37
*** galyna1 has joined #openstack-meeting-316:38
*** stendulker has joined #openstack-meeting-316:42
*** stendulker has quit IRC16:42
*** stendulker has joined #openstack-meeting-316:42
*** seanatcisco has joined #openstack-meeting-316:43
*** Patifa has quit IRC16:44
*** galyna1 has quit IRC16:45
*** rossella_s has quit IRC16:47
*** shuyingy_ has joined #openstack-meeting-316:49
*** sambetts is now known as sambetts|afk16:50
*** shuyingya has quit IRC16:52
*** annegentle has quit IRC16:53
*** aarefiev_afk is now known as aarefiev16:56
*** dtantsur has joined #openstack-meeting-316:56
*** galyna1 has joined #openstack-meeting-316:56
*** mariojv has joined #openstack-meeting-316:57
*** baha has joined #openstack-meeting-316:57
*** diablo_rojo_phon has joined #openstack-meeting-316:57
*** sivak has quit IRC16:58
*** vsaienk0 has joined #openstack-meeting-316:58
dtantsurwho's up for an ironic meeting? :)16:59
*** galstrom is now known as galstrom_zzz16:59
jroll\o/16:59
*** rpioso has joined #openstack-meeting-316:59
dtantsur#startmeeting ironic17:00
openstackMeeting started Mon Apr  3 17:00:00 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
NobodyCamo/17:00
*** openstack changes topic to " (Meeting topic: ironic)"17:00
openstackThe meeting name has been set to 'ironic'17:00
aarefievo/17:00
mariojvo/17:00
stendulkero/17:00
TheJuliao/17:00
vdroko/17:00
rpiosoo/17:00
*** soliosg has joined #openstack-meeting-317:00
crushil\o17:00
jroll\o17:00
*** rloo has joined #openstack-meeting-317:00
rama_yo/17:00
soliosgo/17:00
dtantsurhi everyone, thanks for joining :)17:00
dtantsuras usual, our agenda (relatively light today), can be found at:17:01
rlooo/17:01
vgadiraj_o/17:01
alezilo/17:01
joannao/17:01
dtantsur#link https://wiki.openstack.org/wiki/Meetings/Ironic17:01
*** mgoddard has joined #openstack-meeting-317:01
mgoddardo/17:01
dtantsur#topic Announcements / Reminders17:01
*** openstack changes topic to "Announcements / Reminders (Meeting topic: ironic)"17:01
dtantsur#info dtantsur had some good time in Barcelona during his PTO :)17:01
dtantsurnothing else from me, really :)17:01
mgoddardA couple of quick announcements from me.17:02
mgoddard1. We've just open sourced a project based on kolla for deployment of OpenStack with a focus on baremetal for the scientific computing use case. https://github.com/stackhpc/kayobe. Please get in touch if you're interested in finding out more.17:02
mgoddard2. In the above project we're doing some interesting things with ironic inspector with the aim of reaching 'zero touch' commissioning of a bare metal cloud. Blog post about it here: https://www.stackhpc.com/ironic-idrac-ztp.html.17:02
*** Nisha_Agarwal has joined #openstack-meeting-317:02
*** yuriyz|2 has joined #openstack-meeting-317:02
dtantsur#link https://github.com/stackhpc/kayobe a project based on kolla for deployment of OpenStack with a focus on baremetal for the scientific computing use case17:02
yuriyz|2o/17:02
Nisha_Agarwalo/17:03
*** nicodemos has joined #openstack-meeting-317:03
rloowe did a few releases last week17:03
dtantsur#link https://www.stackhpc.com/ironic-idrac-ztp.html Zero-Touch Provisioning using Ironic Inspector and Dell iDRAC by mgoddard17:03
dtantsurrloo, indeed!17:03
TheJuliaOne announcement from me: I'll be at the leadership training event next week, and on vacation the following week, so I'll be somewhat unavailable.  I'll likely need someone to volunteer to run the UI and BFV meetings, or otherwise cancel them.17:03
dtantsur#info first round of Pike releases done last week17:03
dtantsurTheJulia, the UI one is 8pm for me, but I can run the BFV. it does conflict with the api-wg meeting though..17:04
joannaI can run BFV, I'm there anyway17:04
dtantsurjoanna, thanks!17:05
joanna:)17:05
dtantsur#action joanna to run the next BFV subteam meeting17:05
* jroll notes that he has a bunch of downstream things going on this week, and also at leadership training next week, so mostly out for two weeks but I'll be around irc if people need a thing17:05
dtantsurdo we have someone to run the UI meeting?17:05
TheJuliaI can just cancel the UI meeting, I think it will be fine for a week.17:05
jrolladditional info on releases: everything else is done, but the ironic release is waiting on a couple of patches: https://review.openstack.org/#/c/452806/ https://review.openstack.org/#/c/452787/17:06
crushilI don't have much experience, but I can try because I am going to be there anyways17:06
rajiniro/17:06
TheJuliacrushil: it is easy, I can give you a run down this week :)17:06
crushilTheJulia, Thanks17:06
dtantsurthanks crushil!17:06
crushilnp17:06
TheJuliacrushil: thank you!17:06
dtantsur#action crushil to run the next UI subteam meeting17:06
dtantsuroh, I guess it's not "the next"..17:07
*** vmud213 has joined #openstack-meeting-317:07
* dtantsur wonders if he should #undo that actions, or it's clear enough..17:07
TheJuliaWeek after, I'm sure I'll be on some next week.17:07
* TheJulia thinks undo and then note it again17:07
dtantsur#undo17:07
openstackRemoving item from minutes: #action crushil to run the next UI subteam meeting17:07
dtantsur#undo17:07
openstackRemoving item from minutes: #action joanna to run the next BFV subteam meeting17:07
dtantsur#action joanna to run the BFV meeting next week17:08
dtantsurbetter?17:08
jroll++17:08
dtantsur#action crushil to run the UI subteam meeting next week17:08
TheJuliaYeah I guess17:08
dtantsurcool :) anything else from folks?17:08
dtantsur#topic Review subteam status reports17:09
*** openstack changes topic to "Review subteam status reports (Meeting topic: ironic)"17:09
xavierro/17:09
dtantsur#link https://etherpad.openstack.org/p/IronicWhiteBoard17:09
dtantsurstarting with line 8717:09
rloodtantsur: as a side note, did you decide wrt trello?17:11
rloodtantsur: thinking we should delete the trello links17:11
dtantsurrloo, nope, we can have a voting later :) /me knows folks like voting17:11
* rloo likes votes, reminder of how democracy could work17:12
rlooso the physical network stuff, that spec merged last week, didn't it?17:12
rlooL19617:12
*** ltomasbo is now known as ltomasbo|away17:12
rlooJayF, TheJulia: wrt documentation reorg, it is April. L207.17:13
dtantsur#link http://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/physical-network-awareness.html17:13
jrollrloo: it did17:13
TheJuliarloo: Good point, I've been waiting on a spec, but I've not seen it yet.17:13
rloofolks, please remember to update the status's :)17:13
mgoddardrloo: my bad17:14
* rloo updates status' with guesses :)17:14
TheJuliaheh17:14
* TheJulia liked the ORLY17:14
*** d0ugal has joined #openstack-meeting-317:14
jroll:D17:15
dtantsurrpioso, hey! do you plan on creating a new-style hardware type for Drac or should one of us (one of me?) write it?17:15
*** wanyen has joined #openstack-meeting-317:16
rloowrt the oslo note (L276). anyone want to volunteer to look into any impact on ironic?17:16
* rloo wonders how many dtantsurs there are17:17
rpiosodtantur: Welcome back!17:17
dtantsurrloo, I am qualitative, not quantitative! :)17:17
dtantsurrpioso, thanks!17:17
jrollthe oslo thing should be easy, just stare at logs for warnings :)17:17
rloojroll: we need a starer!17:18
dtantsuror we can proactively switch that flag to true17:18
jrollI'd rather not take that task but can if we get no volunteers17:18
TheJuliaWhy not automate that?17:18
* TheJulia ducsk17:18
TheJuliaducks17:18
jrollcurl $logfile | grep 'the warning'17:18
TheJuliaIt actually should be easy, pull down the library, merge, manually install with pip, restart17:18
rloojroll: would be nice if a noncore takes that on.17:18
jrollrloo: indeed17:18
rpiosodtantsur: Please elaborate.17:18
rloojroll: we could file a bug, 'low hanging fruit'?17:19
TheJulia+1 to bug17:19
rloook, /me files a bug then :)17:19
jrollTheJulia: even easier, we only use it in unit tests17:19
rpiosodtantsur: We could discuss outside of this meeting.17:19
* jroll may jfdi17:19
dtantsurrpioso, yep, let's do it. not really urgent.17:19
rpiosodtantsur: Cool!  ty17:20
*** bobmel_ has quit IRC17:21
dtantsurwe're past 10 minutes cap for the review. are folks still reviewing?17:22
vdrokseems like time to move on :)17:22
dtantsur#topic Deciding on priorities for the coming week17:22
*** openstack changes topic to "Deciding on priorities for the coming week (Meeting topic: ironic)"17:22
rlooi'm done with subteam reports. but leading to next stuff. there are some deadlines coming up, next week: glance, manila, nova spec freeze17:22
rloodoes that impact us, are there things we ought to look at soon?17:22
jrollI can check on our nova work this week17:23
dtantsurdo we need nova specs for any priorities? BFV?17:23
dtantsur#action jroll to check on our nova work this week17:23
TheJulialast I looked we only needed a blueprint for BFV with nova17:23
jrollafaik we have approved BPs for everything we want to do, but I'll double check17:23
dtantsurthanks!17:23
jrollnp17:23
dtantsuras to priorities, I applied only minimal changes to the list from last week17:23
dtantsurwell, I'd prefer to bump redfish priority for reasons already known to the core team :-/17:24
dtantsur(sorry for secrecy here)17:24
rloodtantsur: true, but I don't think we should.17:25
dtantsurrloo, why?17:25
rloodtantsur: can discuss later17:25
* mariojv is lost here17:25
* TheJulia thinks she groks it17:25
rlooit isn't a high priority17:25
rlooi think if the community wants it, they'll review, regardless if it is on our list of priorities or not17:26
dtantsurwell, it's going to be on my personal high priority list anyway17:26
dtantsurbut ok17:26
rloodtantsur: which is perfectly fine!17:26
jrollrloo: I think you and dtantsur agree, don't have it on this weeks priorities17:26
jrollright?17:26
* TheJulia agrees17:26
* jroll not sure if bump means bump up or bump off here17:27
mariojvi agree with bumping for this week17:27
* TheJulia wonders if we should be using more specific words17:27
mariojvit can stay on the spec priority list imo17:27
dtantsuryeah, my English lets me down sometimes. I meant to raise its priority.17:27
jrollspec is merged :)17:27
jrollah17:27
mariojvand we can update and have gerrit votes on that, if that has to change, im17:27
mariojv*imo17:27
rlooredfish driver isn't on this week's list of priorities17:27
rloosee L75+17:27
*** shuyingy_ has quit IRC17:28
TheJuliaI think organically through community reviews would be best, if the community wants to see it sooner rather than later, it will get reviews17:28
dtantsursorry for confusion, everyone. what I suggested (and what rloo correctly understood, I think) is adding redfish to the prio list17:28
dtantsurit seems like we're in agreement that we should not.17:28
TheJuliaseems like it17:29
jrollyeah, I'm fine leaving it off17:29
jrollactually I'm fine either way :P17:29
dtantsurso, does the list look ok now?17:29
jrollwould be nice to just get it done, but it isn't a high priority17:29
jrollyep, fine with me17:29
* dtantsur blames daylight saving change for his condition >_<17:29
rloothe osc default API version change. is there an urgency with that, or we just have to do it anyttime in pike?17:29
mariojvi think it's fine as long as it gets in 3 months before queens17:30
TheJuliawhat mariojv just said17:30
dtantsur++17:30
rloomariojv: ok, remind us if we get close and it ain't17:30
mariojvwill do17:30
jrollif it doesn't, we just need to drop it later in queens, is that a problem? :)17:30
TheJuliaI don't see it as a problem personally, just revise the spec17:31
mariojvi still need to get ironic CLI patch up and have it log when using client library17:31
rloojroll: i'd like it to be done, sooner rather than later17:31
mariojvbut spec and openstack CLI patches are up17:31
TheJulia+1 on just getting it done.17:31
mariojvjroll: not a problem, but no reason to not do it soon :)17:31
rlooi think i'm good with priorities for this week. will maybe ask aout network ones next week :)17:31
jrollyep17:31
mariojv+1 priorities look fine to me17:31
jrollthey LGTM17:31
TheJuliasame17:31
vdrok+117:31
dtantsurawesome17:31
dtantsur#topic RFE review17:32
*** openstack changes topic to "RFE review (Meeting topic: ironic)"17:32
dtantsurwe have some this time!17:32
mariojv\o/17:32
* jroll gets ready to yell17:32
*** yamahata has quit IRC17:32
vdrokthis time I added a couple17:32
dtantsur#link https://bugs.launchpad.net/ironic/+bug/1669243 - Support for zmq in ironic17:32
openstackLaunchpad bug 1669243 in Ironic "[RFE] Ironic doesn't support zmq with oslo.messaging" [Wishlist,In progress] - Assigned to Galyna Zholtkevych (gzholtkevych)17:32
*** ricardoas has joined #openstack-meeting-317:32
vdrokfirst one seems to be pretty easy, do we want to support zeromq?17:33
jrollthis one shouldn't be an RFE, IMO - we claim to support any oslo.messaging-supported backend, feels like a bug if zmg is broken17:33
jrolls/zmg/zmq/17:33
mariojv+1 to what jroll said17:33
vdrokyup, I'm fine with that too17:33
TheJulia+117:33
mariojvif there's not a huge technical reason not to support it, we should, imo17:33
rloo+1, seems like a bug17:33
dtantsurany objections to treating it as a bug?17:34
TheJulianone17:34
dtantsur#agreed treat broken zmq support as a bug, not RFE17:34
rloobut pleeeeeze, if it needs an rpc bump, can it wait til after rolling upgrades? :) me adds comment17:34
jroll++17:34
dtantsurhah, ++17:34
dtantsurnext17:35
dtantsur#link https://bugs.launchpad.net/ironic-inspector/+bug/1678134 - plugin for setting local link connection switch info from LLDP system name17:35
openstackLaunchpad bug 1678134 in Ironic Inspector "[RFE] plugin for setting local link connection switch info from LLDP system name" [Wishlist,In progress] - Assigned to Mark Goddard (mgoddard)17:35
vdrokthe second one is a bit harder, it seems like there is a confusion among the ml2 drivers maintainers17:35
vdrokit seems like cisco and oneview ml2 drivers implemented the switch_info as dictionaries17:35
jrollI thought switch_info was intended to be a dict17:36
vdrokand in case of oneview, they want to make switch_info required i suppose, at least from this change https://review.openstack.org/#/c/377106/917:36
vsaienk0jroll: according to the spec it was designed as a string17:36
mgoddardthe ironic-neutron ml2 spec didn't specify what format it should take, but gave the suggestion that it could be switch system anem, which is a string17:36
mgoddards/anem/name17:37
vsaienk0mgoddard: it is specified in the spec both port_id switch_id and switch_info are string fields17:37
jrolloh right, it does say it's a string17:37
* jroll scratches his head17:37
vdrokwell, it explicitly stated strings :) but, we have to deal with it somehow at this point17:37
mgoddardright you are vsaienko17:37
dtantsurcan't we fix the plugins to (also?) allow strings there?17:38
* jroll bets it's a string that looks like a dict17:38
vsaienk0https://review.openstack.org/#/c/188528/7/specs/liberty/ironic-ml2-integration.rst@9417:38
jrollregardless, the switch_info field is meant to be optional, and vendor-specific. so a plugin layer for inspector seems sane enough there17:38
dtantsurI'm also fine with putting a name there, and allowing plugins to overwrite, but dunno..17:39
jrollkinda sucks that we have to do it, but it's explicitly vendor specific, so what can you do17:39
ricardoasthats right, jroll... we've been using switch_info as a string that looks like a dict17:39
mgoddardsambetts made the point that the plugin may need to be aware of the switch that the node is connected to in order to determine the correct thing to put there17:40
dtantsurI'm pretty sure I don't like the base class approach though17:40
ricardoasjroll in fact, more like a json object17:40
jrollricardoas: which I don't quite like, but alas17:40
dtantsurwe need separate plugins layered on top of the generic one, not inheriting from it17:40
vsaienk0it is better to use a new key switch_capabilities to define a switch capabilities as LLDP field is capabilities not info17:40
jrollthe confusion around this makes it sound spec-able17:41
jrolllots of ideas here17:41
jrollshould be a quick spec to write17:41
mgoddarddtantsur: it is layered in my proposal, as the generic plugin now inherits from the base17:41
TheJuliaspec-able, and also it feels like all of the information needs to be presented17:41
jrollTheJulia: ++17:41
TheJuliabecause it seems like there are several vectors that can and should be addressed17:41
dtantsurmgoddard, well, I'm probably using the wrong word, but I'd like inheriting to disappear for the picture17:42
TheJuliaincluding possibly changing the ml2 drivers to be more consistent or possibly small architectural changes to improve the overall experience.17:42
dtantsurmgoddard, in favor of just having another small plugin running after the generic one and adding the name. dunno how easily doable it is17:42
dtantsurmgoddard, I suspect we need to plug bfournie's LLDP work in17:42
dtantsuralso ++ for a spec17:43
*** galstrom_zzz is now known as galstrom17:43
dtantsurobjections?17:43
mgoddarddtantsur: it's doable, would just require a refactor17:43
vdroknope, makes sense to me17:43
jrolldtantsur: +117:44
mgoddardseems reasonable17:44
dtantsur#agreed https://bugs.launchpad.net/ironic-inspector/+bug/1678134 will need a spec to clarify all the details17:44
openstackLaunchpad bug 1678134 in Ironic Inspector "[RFE] plugin for setting local link connection switch info from LLDP system name" [Wishlist,In progress] - Assigned to Mark Goddard (mgoddard)17:44
dtantsuranything else here before we move on?17:44
dtantsur#topic What about having the first mid(not really mid)cycle soon?17:45
*** openstack changes topic to "What about having the first mid(not really mid)cycle soon? (Meeting topic: ironic)"17:45
TheJulia+117:45
dtantsurI remember we talked about having more virtual meet-ups17:45
rloowhy do we want it?17:45
*** s3wong has joined #openstack-meeting-317:45
dtantsurrloo, high throughput, especially around RFE/spec reviews and agreeing on contentions points17:45
TheJuliaI think it would be really good to get on the same page, even if it just for a couple hours talking on a call prior to the summit.17:45
jrollI'd almost prefer having a discrete list of things to work through, but syncing up is always helpful too17:46
TheJuliaI agree with jroll17:46
dtantsurI remember we had 8 4-hour slot on the last virtual midcycle, right? we can have only 2 slots now, one in each time17:46
dtantsurs/8/6/ maybe, it was 3 days17:46
rloooh. i don't mind a meeting to sync up. guess i'm not sure i want it to be called a midcycle meetup.17:46
jrollI think it was 6 slots, but yeah17:46
rpiosoDo we plan to meet at the Summit Forum?17:46
TheJuliaIt was 617:46
mariojvi'd be fine with that ^ i think later in the cycle might be better for a real midcycle17:46
dtantsurrloo, I used word "midcycle" to give folks a quick idea what I mean17:47
TheJuliado we have a curated list of items to discuss dtantsur ?17:47
mariojvby "that" i mean the 2 slots17:47
rlooi mean, several short syncs during a cycle are great. we should have them when we 'need' them.17:47
jrollrpioso: afaik we only have 2-3 devs going, so while they will probably meet up it won't be a team meetup17:47
dtantsurTheJulia, not now, but I do have a few things in mind. e.g. ongoing nova work and what to do about capabilities..17:47
rlooeg, if we have say 2 features that are ready, then lets just meet to *do* them.17:47
dtantsurrloo, e.g. rolling upgrades, I guess, could use more eyes and discussion17:48
dtantsurthis is really just a guess though17:48
*** lucasxu has joined #openstack-meeting-317:48
rpiosojroll: ty17:48
dtantsuranyway, what I wanted today is to suggest it and let you think if you have something for a high-throughput discussion17:48
TheJuliadtantsur: It might also be prudent to spend a little time discussing stand-alone usage related items, but that is just a thought17:48
rloodtantsur: so TheJulia and jroll are away next week, and TheJulia is away the week after. Shall we tentatively schedule something the week TheJulia is back?17:49
dtantsurTheJulia, yep, especially if you'll have a list of rough edges by then17:49
*** jjung has quit IRC17:49
dtantsurrloo, ++17:49
TheJuliadtantsur: already mostly typed out :)17:49
wanyendtantsur, will virtual meetup logistics be published so non-core can participate?17:49
dtantsurwanyen, definitely!17:49
vdrokwanyen: sure17:49
rlooand then the/a big problem is time...17:49
wanyenthanks17:49
dtantsurthis is one of the big goals17:49
dtantsurwanyen, it will probably be something like SIP, but other FOSS-friendly options will be considered too17:50
dtantsurTheJulia, which dates are you free? I'm confused with "next" here..17:50
TheJuliadtantsur: Starting back the week of the 24th17:51
dtantsurack17:51
*** ijw has quit IRC17:51
rloothat's the week just before summit17:51
dtantsurwhich is good, I guess17:51
rloooh no. there is another week after that.17:51
rloothat woudl be a good week then.17:52
dtantsur#agreed Let's think if we find value in a virtual meetup (similar to previous virtual midcycle) e.g. on the week of Apr 24th17:52
dtantsurright?17:52
TheJuliaYup17:52
rlooyup. i guess we shoudl have an etherpad for people to suggest things.17:52
rlooand possible days/times.17:52
dtantsur#action dtantsur to announce this idea on the mailing list and create an etherpad for potential topics17:52
rlooi hope it is just one day, one block of time. but i guess it depends on what we talk about.17:52
dtantsurrloo, probably 2 blocks on one day because of timezones...17:53
dtantsurbut ok, let's think about it for some more time17:53
rloodtantsur: i really would like to see more focused things, to get concrete stuff done, but yeah, let's see.17:53
dtantsurrloo++17:53
dtantsurany more comments before I open the floor?17:54
dtantsur#topic Open discussion17:54
*** openstack changes topic to "Open discussion (Meeting topic: ironic)"17:54
mariojvi have a small thing about rescue mode i'd like to bring up, proxying for JayF17:54
mariojvbasically, in nova, they allow a user to specify which image will be used when rescuing an instance - so the image will specify info about which user is created for SSH access when rescue finishes17:54
mariojvwith ironic, we're not letting the user specify the rescue image, since that doesn't really make sense in our case17:54
mariojvso this brings up the question of what to call our rescue user17:54
mariojvcurrent behavior is to create a user called "rescue" that has passwordless sudo: https://review.openstack.org/#/c/423521/15/imagebuild/coreos/oem/finalize_rescue.sh (L6)17:54
*** shuyingya has joined #openstack-meeting-317:54
mariojvi prefer this over having the user just login as root immediately with the password given from nova17:54
mariojvbut it's still a decision we didn't really spell out explicitly in the spec, so i wanted to get community opinion on this17:54
dtantsurso, these are two questions, right? whether to allow user images and what user to use?17:55
jrollmaybe make the user configurable?17:55
*** mrhillsman has joined #openstack-meeting-317:55
mariojvi mainly wanted to focus on which user, for this discussion17:55
dtantsurtbh, I'm fine with having root, if 'sudo -i' is going to be the first thing for people to do..17:55
rloomariojv: dumb question cuz i am not familar with rescue. shouldn't it work with nova's rescue?17:55
TheJuliaThe person maintaining the volume connection API patch would like to get some reviews in order to head off nitpicking when it finally comes time to land the patch.  https://review.openstack.org/#/c/214586/  It has a few pep8 errors which I'll try to fix today.17:56
mariojvrloo: yes - but in the nova case, they have user images when rescuing, so that's where they specify it17:56
mariojvi think i'd be fine with having it root by default, in that case, dtantsur17:56
dtantsurin other words: do we have a use case for non-root access to the rescue image?17:56
dtantsur#link https://review.openstack.org/#/c/214586/ - volume connection API patch that could use early reviews17:56
mariojvand maybe just have some docs for how to change it when building IPA if they want to (make it configurable in that way like jroll suggested)17:57
*** baoli has quit IRC17:57
jrollI'm okay with just root17:57
*** Sukhdev has joined #openstack-meeting-317:57
mariojvdtantsur: i guess i was just a bit worried about giving a user something that they can do damage with, by default17:57
jrollit doesn't really increase security to use a non-root user, if they have sudo17:57
mariojvbut maybe that's ok, since it's a ramdisk17:57
TheJulia3 minutes17:57
mariojvyeah, not security, more prevent you from accidentally doing bad things17:57
dtantsurmariojv, without root they won't even be able to mount disks (neither to access them)17:57
mariojvah that's a good point17:58
mariojvok, let's keep it as root then17:58
wanyenso why it doesn't make sense for user to pick what rescue image?17:58
mariojvthat seems to be the default in a lot of nova docs for rescue mode anyway17:58
TheJulia2 minute warning17:58
mariojvwanyen: that's a longer discussion than we have time for here17:58
jrolltl;dr because pxe boot17:58
dtantsuroh that Pixie :D17:59
mariojvwanyen: but basically it opens up a huge amount of security risk, allowing someone to boot an arbitrary ramdisk17:59
vdrokI'm not sure if anyone seen this spec from yuriyz -- https://review.openstack.org/452182, while it was intended for 1st april, it seems like whis will work for ipa authentication, if someone has a bit of time to read through17:59
*** d0ugal has quit IRC17:59
*** shuyingya has quit IRC17:59
mariojvand it'd be a big pain implementation wise17:59
dtantsurwe're running out of time. thanks everyone!18:00
mariojvthanks!18:00
vdrokthanks18:00
TheJuliaThanks!18:00
NobodyCam:)18:00
dtantsur#endmeeting ironic18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Mon Apr  3 18:00:14 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-04-03-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-04-03-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-04-03-17.00.log.html18:00
*** aarefiev is now known as aarefiev_afk18:00
*** wanyen has quit IRC18:00
*** dtantsur has left #openstack-meeting-318:00
*** soliosg has left #openstack-meeting-318:00
*** yuriyz|2 has quit IRC18:01
*** mgoddard has left #openstack-meeting-318:01
*** baoli has joined #openstack-meeting-318:01
*** mariojv has left #openstack-meeting-318:02
*** markmcclain has quit IRC18:05
*** markmcclain has joined #openstack-meeting-318:07
*** reed has quit IRC18:07
*** stendulker has quit IRC18:07
*** pvaneck has joined #openstack-meeting-318:07
*** vmud213 has quit IRC18:08
*** reed has joined #openstack-meeting-318:08
*** nicodemos has left #openstack-meeting-318:08
*** vmud213 has joined #openstack-meeting-318:09
*** dhellmann has quit IRC18:10
*** vmud213 has quit IRC18:10
*** dhellmann has joined #openstack-meeting-318:11
*** Swami has joined #openstack-meeting-318:12
*** sdoyle has quit IRC18:12
*** harlowja has joined #openstack-meeting-318:12
*** sdoyle has joined #openstack-meeting-318:12
*** Nisha_Agarwal has quit IRC18:13
*** Nisha_Agarwal has joined #openstack-meeting-318:13
*** crushil has quit IRC18:16
*** d0ugal has joined #openstack-meeting-318:20
*** Patifa has joined #openstack-meeting-318:21
*** joanna__ has quit IRC18:22
*** baha has left #openstack-meeting-318:22
*** ralonsoh has quit IRC18:23
*** alexismonville has joined #openstack-meeting-318:23
*** annegentle has joined #openstack-meeting-318:24
*** kzaitsev_mb has joined #openstack-meeting-318:25
*** rpioso has left #openstack-meeting-318:27
*** galyna1 has quit IRC18:38
*** raddaoui has joined #openstack-meeting-318:38
*** crushil has joined #openstack-meeting-318:40
*** bsilverman_10 has joined #openstack-meeting-318:40
*** bsilverman_ has quit IRC18:40
*** makowals has joined #openstack-meeting-318:44
*** dimtruck is now known as zz_dimtruck18:46
*** zz_dimtruck is now known as dimtruck18:53
*** donghao has quit IRC19:04
*** julim has quit IRC19:08
*** julim has joined #openstack-meeting-319:08
*** alexismonville has quit IRC19:13
*** joanna__ has joined #openstack-meeting-319:17
*** lpetrut has joined #openstack-meeting-319:21
*** iyamahat has joined #openstack-meeting-319:21
*** d0ugal has quit IRC19:23
*** sdoyle has quit IRC19:24
*** d0ugal has joined #openstack-meeting-319:25
*** lpetrut has quit IRC19:28
*** sdoyle has joined #openstack-meeting-319:29
*** bobh has quit IRC19:29
*** makowals has quit IRC19:32
*** marst_ has joined #openstack-meeting-319:32
*** galstrom is now known as galstrom_zzz19:32
*** galstrom_zzz is now known as galstrom19:32
*** jjung has joined #openstack-meeting-319:34
*** marst has quit IRC19:35
*** d0ugal has quit IRC19:36
*** harlowja has quit IRC19:37
*** yamahata has joined #openstack-meeting-319:40
*** dimtruck is now known as zz_dimtruck19:45
*** mlavalle has joined #openstack-meeting-319:47
*** galyna1 has joined #openstack-meeting-319:53
*** mrmartin has joined #openstack-meeting-319:54
*** blancos has joined #openstack-meeting-319:56
*** HoloIRCUser has joined #openstack-meeting-319:56
*** julim has quit IRC19:57
ildikov#startmeeting openstack_upstream_institute20:00
openstackMeeting started Mon Apr  3 20:00:24 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
mlavalleo/20:00
blancoso/20:00
kmARCo/20:00
mrmartino/20:00
diablo_rojoHello :)20:00
ildikovhi all :)20:00
*** donghao has joined #openstack-meeting-320:01
ildikovagenda for today: https://etherpad.openstack.org/p/openstack-upstream-institute-meetings20:01
*** julim has joined #openstack-meeting-320:02
HoloIRCUserHi20:02
*** HoloIRCUser is now known as skelso20:02
ildikovas for the TODO's I started to update the web page with the latest information20:02
skelsoTrying again w/correct nick20:03
ildikovI need to look nito the Intro slides to get that up to date as well20:03
*** galyna1 has left #openstack-meeting-320:03
ildikovjungleboyj is on vacation today, so we can take the releases section to the next week's meeting20:03
*** rloo has left #openstack-meeting-320:04
ildikovlast time we started to go through the sections and discuss what to clean up and improve on them20:04
diablo_rojoI have updated the Communication, Overview of Contribution Processes and Events sections and the changes have been merged.20:04
ildikovreviews can be found here: https://review.openstack.org/#/q/project:openstack/training-guides20:05
ildikovcurrently we don't have open reviews, so I would like to encourage everyone to create some :)20:06
diablo_rojoildikov, +120:06
*** donghao has quit IRC20:06
ildikovI think we can start with the wiki agenda topic and then go back to reviews the material20:06
ildikovdiablo_rojo: does it sound good?20:06
*** crushil has quit IRC20:06
diablo_rojoWorks for me20:07
*** skelso has quit IRC20:07
diablo_rojoThe first topic I had was just updates on last weeks TODO's20:07
ildikov#topic Wiki page updates20:07
*** openstack changes topic to "Wiki page updates (Meeting topic: openstack_upstream_institute)"20:07
*** iyamahat has quit IRC20:07
*** ricardoas has left #openstack-meeting-320:07
ildikov#link https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute20:07
ildikovas a reminder we have a team wiki page20:08
ildikovplease check whether you're listed among the team members20:08
ildikovalso please check whether the information there is all filled and up to date20:08
ildikovif you know already that you're available for the Boston training please highlight that there as well20:09
diablo_rojoIt would be especially helpful if people could fill in if they are attending the training in Boston20:09
ildikovif you cannot join for both days that's still ok, please provide the info when you'll be available so we can figure out the setup and plans20:09
*** crushil has joined #openstack-meeting-320:10
ildikovdiablo_rojo: is there anything I missed?20:10
spotzhey all20:11
ildikovspotz: hi :)20:11
ildikovspotz: thanks for joining20:11
spotzSorry I'm late20:12
ildikovok, we can move on from the wiki if no one has related questions20:12
ildikovspotz: no worries, we're on the administrative side still :)20:12
diablo_rojoildikov, nope thats it20:13
ildikovdiablo_rojo: cool, thanks!20:13
ildikovas I saw kmARC around, if it works for him it would be good to quickly touch on the VM image :)20:13
kmARCyepp, let's do that! :-)20:13
*** Sukhdev_ has joined #openstack-meeting-320:13
ildikov#topic VM image update for the training20:13
*** openstack changes topic to "VM image update for the training (Meeting topic: openstack_upstream_institute)"20:13
ildikovkmARC: can you give us a brief update on what needs to be done?20:14
kmARCI'm trying to upgrade it to Ubuntu 16.04 and Ocata20:14
kmARCran into some problems, but hopefully will tackle them20:14
ildikovkmARC: also if there's anything you need more hands on, please highlight those too20:14
kmARCsure20:15
*** sekelso has joined #openstack-meeting-320:15
ildikovkmARC: is there anything from those problems we should discuss here?20:15
* mlavalle updated wiki20:15
kmARCquestion to all of you: anyone misses anything from the VM that would be desirable to be installed / set up?20:15
kmARC@ildikov not for the time being20:15
ildikovmlavalle: tnx20:16
*** rmart04 has joined #openstack-meeting-320:16
ildikovkmARC: as we have new people on board, can you give a quick list on what we have there already?20:16
kmARCSure. bit.ly/training-vm , check it out! ;-)20:17
kmARCbasically this VM is a downloadable asset, published a day or two before the upstream training20:17
ildikovkmARC: :)20:18
*** crushil has quit IRC20:18
kmARCit has all the tools installed with which one can start development on openstack projects20:18
kmARCit utilizes devstack, with networking set up properly, some text editors and a Windows95-like UI (XFCE)20:18
spotzkmARC: So it has git and gerrit already installed?20:18
kmARCyes20:18
spotzcool20:19
kmARCAlso set's up some convenience bookmarks, etc.20:19
kmARCsets*20:19
spotznice20:19
kmARCit's built automatically through Vagrant, so one can assemble their own, however we also release (automatically built of course ;-) ) one version before the training in ova format, so the students just need to import into their virtualbox20:20
kmARCThat is it in a nutshell20:20
sekelsoSorry, rejoining after a bit...do we pub pre-reqs for the VM before the meeting?20:20
kmARCyes20:20
kmARCit's on the link20:20
kmARCcheck it out ;-)20:20
sekelsoCool.20:20
diablo_rojosekelso, I think it is also in our docs for the upstream training20:21
*** julim has quit IRC20:21
kmARCbasically the README.md on github tells everything20:21
ildikovkmARC: do we already have a version up on tarballs.o.o?20:22
kmARCUnfortunately not.20:22
*** lucasxu has quit IRC20:22
mrmartinI can help with that if we are talking infra / jenkins integration here.20:22
ildikovkmARC: do you need any help with that?20:22
ildikovmrmartin: we started to discussed this with them already20:23
sekelsoAh, I'm thinking more like on the session page in the Summit agenda. A "go read this before you show up" kind of thing.20:23
kmARC@ildikov yes, we definitely should get some help with that20:24
diablo_rojosekelso, last time we sent out something to people that were registered with that info in it20:24
sekelsoK, got it. Thanks.20:24
ildikovsekelso: we send out reminder mails to people who registered and add info there20:24
diablo_rojosekelso, No problem :)20:24
*** sekelso is now known as skelso20:24
ildikovsekelso: although it might make people more interested if they have some more pointers in the description on the schedule :)20:24
*** zz_dimtruck is now known as dimtruck20:25
*** baoli has quit IRC20:25
ildikovdiablo_rojo: sorry, I've just seen you type way faster than me :)20:25
skelsoAgreed...20:25
ildikovkmARC: I guess there's no point in uploading the old image20:25
kmARCNo20:26
*** Nisha_Agarwal has quit IRC20:26
ildikovkmARC: so I think when we have something that works close to the training we can publish that20:26
kmARCWe should find an automated way to deploy it, after all it's just a shell script, however last time we run into some problems - which I cannot recall right now20:26
*** Nisha_Agarwal has joined #openstack-meeting-320:26
kmARCexactly20:26
ildikovkmARC: and then update in case we had to fix smth on it20:26
ildikovkmARC: yes, I just meant that we agreed with the infra guys last time that the first version goes up manually20:27
ildikovkmARC: and then we automate20:27
ildikovkmARC: if we look into automation after the training I think that should be fine too, not the highest priority right now20:27
*** megm has quit IRC20:27
kmARCokay, then let's do this20:28
ildikovkmARC: although if you can recall what the issues were we can ping people with that to get progres sin parallel20:28
kmARCsure, it should be somewhere in my IRC Logs :-)20:28
ildikovkmARC: we also talked about moving the source/scripts to the training-guides repo20:28
ildikovkmARC: :)20:29
ildikovkmARC: are you planning to do that?20:29
kmARCI can look into that too20:29
ildikovkmARC: cool, tnx20:29
*** Sukhdev has quit IRC20:30
*** Sukhdev_ is now known as Sukhdev20:30
*** megm has joined #openstack-meeting-320:30
ildikovkmARC: if there's anything to bring up, we have an IRC channel now: #openstack-upstream-institute20:30
diablo_rojokmARC, you have a lot of todo's :)20:30
*** haleyb has quit IRC20:30
ildikovkmARC: and we're using the os-upstream-institute tag on the mailing list20:30
kmARC(I love the new name Upstream Institute a LOT. sounds like a fancy R&D lab or something :-D )20:31
ildikovkmARC: no need to wait until the next meeting if you need help with anything20:31
ildikovkmARC: lol :)20:31
ildikovkmARC: do you have anything else in mind we should talk about in connection to the VM image?20:32
*** baoli has joined #openstack-meeting-320:32
kmARCRight now nothing. If anyone has any suggestions or so, just ping me, I am a nice person, will answer ;-)20:33
*** rmart04 has quit IRC20:33
ildikovkmARC: coo, tnx :)20:34
ildikov*cool20:34
ildikovI would like to encourage everyone to look into what we have and give feedback and suggestions if you have anything in mind that would be needed/useful!20:35
ildikovlet's move on :)20:35
*** abalutoiu_ has joined #openstack-meeting-320:36
ildikov#topic Updating the material20:36
*** openstack changes topic to "Updating the material (Meeting topic: openstack_upstream_institute)"20:36
ildikovI think last time we stopped at the Governance section20:37
ildikovI think we were all in an agreement that it could use some thoughts and updates to make it better20:37
ildikovespecially with the mindset of an interactive training, where we would like to get the people involved20:38
*** Nisha_Agarwal has quit IRC20:38
ildikovas a quick reminder the training room is planned to have round tables in it and we will try to group people by area of interest20:38
diablo_rojoWe agreed that it was important to cover, but I think that was about it20:38
ildikovdiablo_rojo: +120:39
*** abalutoiu has quit IRC20:39
ildikovIIRC we came up with ideas like trying to get the groups at the tables to have a team structure20:39
ildikovlike cores and a PTL20:39
diablo_rojoYeah that sounds right20:40
ildikovif we can come up with exercises that leverages this setup we could bring back a few parts of the earlier Lego slot, that we removed from the training before Barcelona20:40
ildikovwhat do you all think about this?20:40
skelsoIn a role-playing sort of way? Or do we expect there will be a more experienced person at each table?20:40
kmARCin this case even I agree with the moderated version of the Lego excercises20:41
ildikovskelso: role playing way20:41
mrmartin+1 to Lego20:41
ildikovkmARC: mrmartin: to clarify, we will not have Lego in Boston20:42
ildikovkmARC: mrmartin: the idea is to bring back some of the ideas from it that brings people closer to get an idea how the community operates20:43
mrmartinok20:43
ildikovmrmartin: does 'ok' equals to 'that sound good'? :)20:44
kmARCwell I think it were the _ideas_ that weren't relevant but at least the plastic lego pieces were fun ;-)20:44
mrmartinexactly.20:44
kmARCwhat I am saying, let's don't start talking about SCCRUM and other corporate BS which isn't applicable at all to how the OpenStack community operates20:45
ildikovkmARC: tnx, always good to have kids around :)20:45
mrmartindo you have any specific ideas for those role playing games?20:45
ildikovkmARC: exactly, that's why we came up with idea to form project teams from the groups we have in the room for instance20:45
kmARC(I like the roundtable idea btw.)20:46
ildikovkmARC: so people can understand some bits of the governance structure, but no Agile or Scrum20:46
kmARCmakes sense, thanks for the clarification20:47
ildikovmrmartin: long term it would be great with come up with a bigger task that requires people in the groups to interact with each other and also interaction within groups20:47
*** alexismonville has joined #openstack-meeting-320:47
diablo_rojosomething more for the second day20:48
*** dimtruck is now known as zz_dimtruck20:48
ildikovmrmartin: but we don't have a concrete theme at this point20:48
*** zz_dimtruck is now known as dimtruck20:48
diablo_rojomrmartin, got any ideas? ;)20:48
ildikovdiablo_rojo: +120:48
skelsoFrom my POV, the challenge is if you put a bunch of corp. folks (and that's who seemed to dominate the Barceolona class, me included), they'll get confused without a "this is different" bit of preaching somewhere in the beginning.20:48
mrmartinI can ask my coach friends to suggest something useful.20:48
ildikovfirst day is more introduction to what we have as for processes/tools still, but we're trying to bring as much exercises/interaction into the whole thing as possible20:48
jungleboyjildikov:  I didn't get to make any progress on my work items the last week.  Had other things to tackle prepping for vacation.20:48
jungleboyjildikov:  Hoping to tackle things when back next week.20:49
skelsoB/c we'll all want to elect a project manager to tell us what to do :)20:49
ildikovskelso: do you mean compared to Agile?20:49
ildikovjungleboyj: no worries20:49
skelsoYeah...that being one of the dominant contexts folks come to the class from.20:49
diablo_rojoA pm is basically a scrum master20:49
ildikovjungleboyj: you can also upload a patch for review when you get there and we can discuss it on the meeting, etc.20:50
diablo_rojoskelso, thats why the governance section is important, we want to make it clear that it is not the same as in your companies20:50
ildikovskelso: we have a short Agile block as part of the intro section20:50
skelsoTrue, this is why I'm thinking about it. Governance is great context, but it's a floor or two above the team level.20:51
*** david-lyle has quit IRC20:51
ildikovskelso: and we have an exercise in connection to that for the groups to dicuss what can be different in open source and why, etc.20:51
*** david-lyle has joined #openstack-meeting-320:51
skelsoNow that sounds helpful20:51
ildikovskelso: so we open it up for discussion and summarize the outcome of the group chats at the beggining20:52
*** annegentle has quit IRC20:52
ildikovskelso: I think we can kind of complement this with the governance section to get to the big picture20:52
skelsoOkay, cool. We need to equip folks to tell their managers both how the community works, and also why it works that way.20:52
jungleboyjskelso We talked about this last week as well.  Important to give people the context of how decisions are made for the community..20:53
skelsoK, understood.20:53
diablo_rojoThose sections of the slides were there in Barcelona, maybe we need to stress it a bit more.20:53
*** harlowja has joined #openstack-meeting-320:53
jungleboyjI will need to look at those.  Don't remember what all was there.20:54
diablo_rojohttps://docs.openstack.org/upstream-training/intro-openstack-as-community.html#620:54
ildikovjungleboyj: the Agile part is one slide and one more for the exercise :)20:55
diablo_rojoThe last two slides in that deck are what ildikov and I are talking about20:55
skelsoReading...20:55
ildikovas for governance we need to find the right amount of information to share so we don't overload people with information20:55
ildikovalso we have 5 minutes left from the today's meeting20:56
*** corey__ has quit IRC20:56
ildikovis there anyone of you who can look into the Governance section and come up with ideas on how to improve it?20:57
diablo_rojoildikov, I can take a look20:57
*** vgadiraj_ has quit IRC20:57
skelsoYes, I'll take a look also20:57
*** rockyg has joined #openstack-meeting-320:57
ildikovdiablo_rojo: skelso: cool, thanks!20:58
jungleboyjdiablo_rojo:  Ok, I remember those slides now.20:58
jungleboyjI think those questions are still good to work with.20:58
ildikovdiablo_rojo: skelso: if you can also give some thoughts to the role playing game and whether or not we could simulate the elections for instance that would be great20:58
skelsoYes, certainly.20:59
ildikovjungleboyj: +120:59
ildikovok, we need to wrap up20:59
jungleboyjildikov: I thought we weren't gong to do the role playing due to time.21:00
*** haleyb has joined #openstack-meeting-321:00
ildikovnext week we will look into the tools part and the deep dives to get progress on that too21:00
mrmartinbye21:00
jungleboyjOk.  Sounds good.21:00
diablo_rojoIf everyone could just take a look at all the slides for next week that would be super helpful. That way we can spend less time talking about what is there and more time about how to make them better :)21:00
ildikovthanks everyone, talk to you on the channel or next week the latest21:00
spotz:)21:00
kmARCdiablo_rojo: +121:00
ildikovdiablo_rojo: +121:00
*** d0ugal has joined #openstack-meeting-321:00
ildikovhave a good week!21:00
jungleboyjOk, will do.21:00
spotzjust grab me in channel if you guys need me for anything in the meantime21:00
*** MeganR has joined #openstack-meeting-321:01
kmARCbye21:01
ildikov#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Mon Apr  3 21:01:05 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
mlavallebye21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_upstream_institute/2017/openstack_upstream_institute.2017-04-03-20.00.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_upstream_institute/2017/openstack_upstream_institute.2017-04-03-20.00.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_upstream_institute/2017/openstack_upstream_institute.2017-04-03-20.00.log.html21:01
ildikovspotz: tnx!21:01
*** julim has joined #openstack-meeting-321:01
jungleboyjBye.21:01
*** blancos has left #openstack-meeting-321:01
*** mlavalle has left #openstack-meeting-321:02
*** tonytan4ever has quit IRC21:04
*** sdoyle has quit IRC21:13
*** revon has quit IRC21:13
*** MarkBaker has quit IRC21:13
*** annegentle has joined #openstack-meeting-321:15
*** mariannelm has joined #openstack-meeting-321:16
*** srobert has quit IRC21:18
*** seanatcisco has quit IRC21:20
*** skelso has quit IRC21:21
*** darrenc has quit IRC21:24
*** darrenc has joined #openstack-meeting-321:24
*** gouthamr has quit IRC21:24
*** reedip has quit IRC21:35
*** mickeys has joined #openstack-meeting-321:38
*** kzaitsev_mb has quit IRC21:44
*** seanatcisco has joined #openstack-meeting-321:47
*** Sukhdev_ has joined #openstack-meeting-321:47
*** lamt has joined #openstack-meeting-321:51
*** nhairston has quit IRC22:00
*** iyamahat has joined #openstack-meeting-322:01
*** galstrom is now known as galstrom_zzz22:02
*** MeganR has quit IRC22:02
*** donghao has joined #openstack-meeting-322:03
*** Swami has quit IRC22:04
*** donghao has quit IRC22:08
*** iyamahat has quit IRC22:08
*** marst_ has quit IRC22:13
*** galstrom_zzz is now known as galstrom22:13
*** lyan has quit IRC22:17
*** marst_ has joined #openstack-meeting-322:21
*** baoli has quit IRC22:24
*** rbak has quit IRC22:25
*** galstrom is now known as galstrom_zzz22:25
*** Sukhdev has quit IRC22:26
*** VW_ has joined #openstack-meeting-322:29
*** aunnam has quit IRC22:30
*** VW has quit IRC22:32
*** VW_ has quit IRC22:33
*** rockyg has quit IRC22:35
*** aunnam has joined #openstack-meeting-322:39
*** crushil has joined #openstack-meeting-322:47
*** sdague has quit IRC22:57
*** marst_ has quit IRC23:00
*** lamt has quit IRC23:01
*** annegentle has quit IRC23:03
*** armstrong has joined #openstack-meeting-323:08
*** seanatcisco has quit IRC23:09
*** armstrong has quit IRC23:10
*** marst has joined #openstack-meeting-323:13
*** diablo_rojo has quit IRC23:15
*** siva_krishnan has quit IRC23:16
*** aunnam has quit IRC23:17
*** aunnam has joined #openstack-meeting-323:19
*** yamahata has quit IRC23:21
*** doffm has left #openstack-meeting-323:22
*** reed_ has joined #openstack-meeting-323:29
*** reed_ has quit IRC23:35
*** bobh has joined #openstack-meeting-323:35
*** sneti has joined #openstack-meeting-323:40
*** donghao has joined #openstack-meeting-323:44
*** Patifa has quit IRC23:45
*** shuyingya has joined #openstack-meeting-323:58

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