Monday, 2017-07-03

*** makowals has joined #openstack-meeting-300:05
*** zhurong has joined #openstack-meeting-300:48
*** zhurong has quit IRC00:49
*** skelso has joined #openstack-meeting-300:53
*** baoli has joined #openstack-meeting-300:56
*** amotoki is now known as amotoki_away00:58
*** wanghao has joined #openstack-meeting-300:58
*** amotoki_away is now known as amotoki00:58
*** baoli has quit IRC01:01
*** wanghao has quit IRC01:07
*** wanghao has joined #openstack-meeting-301:11
*** skelso has quit IRC01:13
*** skelso has joined #openstack-meeting-301:14
*** tuanluong has joined #openstack-meeting-301:15
*** kkxue has joined #openstack-meeting-301:17
*** cshastri has joined #openstack-meeting-301:24
*** skelso has quit IRC01:27
*** skelso has joined #openstack-meeting-301:27
*** kkxue has quit IRC01:28
*** kkxue has joined #openstack-meeting-301:28
*** zhurong has joined #openstack-meeting-301:29
*** skelso has quit IRC01:32
*** skelso has joined #openstack-meeting-301:33
*** zhurong has quit IRC01:33
*** zhurong has joined #openstack-meeting-301:37
*** skelso has quit IRC01:41
*** skelso has joined #openstack-meeting-301:41
*** baoli has joined #openstack-meeting-301:42
*** zhurong has quit IRC01:47
*** skelso has quit IRC01:50
*** slaweq_ has joined #openstack-meeting-301:53
*** wanghao has quit IRC01:53
*** slaweq_ has quit IRC01:58
*** tuanluong has quit IRC01:59
*** gcb has joined #openstack-meeting-302:06
*** makowals has quit IRC02:09
*** wanghao has joined #openstack-meeting-302:14
*** makowals has joined #openstack-meeting-302:18
*** skelso has joined #openstack-meeting-302:43
*** shuyingya has joined #openstack-meeting-302:47
*** yamamoto has joined #openstack-meeting-302:49
*** slaweq_ has joined #openstack-meeting-302:54
*** slaweq_ has quit IRC02:59
*** reedip has quit IRC03:09
*** baoli has quit IRC03:21
*** skelso has quit IRC03:24
*** kiseok7 has joined #openstack-meeting-303:28
*** skelso has joined #openstack-meeting-303:35
*** amotoki is now known as amotoki_away03:47
*** yamamoto has quit IRC03:50
*** Fdaisuke has quit IRC03:52
*** yamamoto has joined #openstack-meeting-303:53
*** psachin has joined #openstack-meeting-304:15
*** amotoki_away is now known as amotoki04:15
*** shuyingy_ has joined #openstack-meeting-304:29
*** shuyingya has quit IRC04:29
*** skelso has quit IRC04:31
*** amotoki is now known as amotoki_away04:36
*** liangbo has joined #openstack-meeting-304:43
*** amotoki_away is now known as amotoki04:47
*** pewp has joined #openstack-meeting-304:48
*** pewp is now known as Guest692904:48
*** gcb has quit IRC04:48
*** gcb has joined #openstack-meeting-304:49
*** slaweq_ has joined #openstack-meeting-304:55
*** slaweq_ has quit IRC05:00
*** liangbo has quit IRC05:01
*** gcb has quit IRC05:06
*** gcb has joined #openstack-meeting-305:07
*** kkxue has quit IRC05:31
*** kkxue has joined #openstack-meeting-305:31
*** apetrich has joined #openstack-meeting-305:54
*** marios has joined #openstack-meeting-305:55
*** d0ugal has quit IRC06:02
*** Guest6929 has quit IRC06:05
*** pewp has joined #openstack-meeting-306:08
*** pewp has joined #openstack-meeting-306:09
*** pewp has joined #openstack-meeting-306:10
*** pewp has quit IRC06:10
*** anilvenkata has joined #openstack-meeting-306:10
*** pewp has joined #openstack-meeting-306:11
*** pewp has joined #openstack-meeting-306:11
*** pewp has joined #openstack-meeting-306:12
*** pewp is now known as Guest5120406:12
*** reedip has joined #openstack-meeting-306:13
*** pgadiya has joined #openstack-meeting-306:14
*** kkxue has quit IRC06:18
*** kkxue has joined #openstack-meeting-306:19
*** slaweq_ has joined #openstack-meeting-306:27
*** andreas_s has joined #openstack-meeting-306:29
*** kkxue has quit IRC06:30
*** kkxue has joined #openstack-meeting-306:30
*** slaweq_ has quit IRC06:32
*** slaweq_ has joined #openstack-meeting-306:44
*** slaweq_ has quit IRC06:44
*** slaweq_ has joined #openstack-meeting-306:45
*** tobberydberg has joined #openstack-meeting-306:51
*** pcaruana has joined #openstack-meeting-306:59
*** wanghao_ has joined #openstack-meeting-307:01
*** wanghao has quit IRC07:01
*** pcaruana has quit IRC07:03
*** pcaruana has joined #openstack-meeting-307:05
*** kkxue has quit IRC07:10
*** kkxue has joined #openstack-meeting-307:10
*** wanghao has joined #openstack-meeting-307:16
*** ralonsoh has joined #openstack-meeting-307:17
*** slaweq_ has quit IRC07:17
*** wanghao_ has quit IRC07:19
*** liangbo has joined #openstack-meeting-307:21
*** slaweq_ has joined #openstack-meeting-307:21
*** zhurong has joined #openstack-meeting-307:22
*** d0ugal_ has joined #openstack-meeting-307:28
*** slaweq_ has quit IRC07:30
*** d0ugal_ has quit IRC07:30
*** d0ugal has joined #openstack-meeting-307:31
*** d0ugal has quit IRC07:31
*** d0ugal has joined #openstack-meeting-307:31
*** d0ugal has quit IRC07:37
*** d0ugal has joined #openstack-meeting-307:40
*** d0ugal_ has joined #openstack-meeting-307:44
*** d0ugal has quit IRC07:45
*** ccamacho has joined #openstack-meeting-307:52
*** marios has quit IRC07:53
*** d0ugal has joined #openstack-meeting-307:55
*** d0ugal has quit IRC07:55
*** d0ugal has joined #openstack-meeting-307:55
*** marios has joined #openstack-meeting-307:55
*** d0ugal_ has quit IRC07:56
*** marios has quit IRC07:58
*** marios has joined #openstack-meeting-307:58
*** marios has quit IRC08:00
*** marios has joined #openstack-meeting-308:03
*** bobmel has joined #openstack-meeting-308:03
*** kkxue has quit IRC08:07
*** kkxue has joined #openstack-meeting-308:07
*** slaweq_ has joined #openstack-meeting-308:14
*** slaweq_ has quit IRC08:15
*** wanghao has quit IRC08:17
*** slaweq_ has joined #openstack-meeting-308:17
*** MarkBaker has joined #openstack-meeting-308:18
*** seanhandley_ has left #openstack-meeting-308:20
*** jtomasek has joined #openstack-meeting-308:26
*** lpetrut has joined #openstack-meeting-308:26
*** wanghao has joined #openstack-meeting-308:28
*** etingof has joined #openstack-meeting-308:29
*** slaweq_ has quit IRC08:29
*** rossella_ has joined #openstack-meeting-308:31
*** cshastri_ has joined #openstack-meeting-308:36
*** cshastri has quit IRC08:39
*** pgadiya has quit IRC08:40
*** qwebirc76466 has joined #openstack-meeting-308:44
*** d0ugal has quit IRC08:46
*** tobberyd_ has joined #openstack-meeting-308:47
*** tobberydberg has quit IRC08:50
*** pgadiya has joined #openstack-meeting-308:50
*** tobberyd_ has quit IRC08:52
*** jtomasek has quit IRC09:01
*** d0ugal has joined #openstack-meeting-309:04
*** etingof has quit IRC09:05
*** jtomasek has joined #openstack-meeting-309:10
*** cshastri has joined #openstack-meeting-309:11
*** Guest51204 has quit IRC09:12
*** pewp has joined #openstack-meeting-309:15
*** cshastri_ has quit IRC09:15
*** pewp is now known as Guest2189309:15
*** etingof has joined #openstack-meeting-309:18
*** yamamoto has quit IRC09:20
*** yamamoto has joined #openstack-meeting-309:22
*** MarkBaker has quit IRC09:24
*** etingof has quit IRC09:25
*** tobberydberg has joined #openstack-meeting-309:35
*** amotoki is now known as amotoki_away09:36
*** wanghao has quit IRC09:38
*** slaweq_ has joined #openstack-meeting-309:38
*** jtomasek has quit IRC09:39
*** etingof has joined #openstack-meeting-309:40
*** slaweq_ has quit IRC09:41
*** slaweq_ has joined #openstack-meeting-309:41
*** sambetts|afk is now known as sambetts09:41
*** anilvenkata has quit IRC09:45
*** anilvenkata has joined #openstack-meeting-309:47
*** slaweq_ has quit IRC10:01
*** dims has quit IRC10:14
*** dims has joined #openstack-meeting-310:15
*** cshastri has quit IRC10:18
*** gcb has quit IRC10:20
*** MarkBaker has joined #openstack-meeting-310:21
*** coolsvap has joined #openstack-meeting-310:21
*** yamamoto has quit IRC10:45
*** yamamoto has joined #openstack-meeting-310:46
*** yamamoto has quit IRC10:46
*** aignatov has quit IRC11:03
*** aignatov has joined #openstack-meeting-311:06
*** psachin has quit IRC11:14
*** mrtenio has joined #openstack-meeting-311:15
*** psachin has joined #openstack-meeting-311:15
*** slaweq_ has joined #openstack-meeting-311:17
*** slaweq_ has quit IRC11:18
*** Guest21893 has quit IRC11:18
*** slaweq_ has joined #openstack-meeting-311:21
*** slaweq_ has quit IRC11:22
*** pewp has joined #openstack-meeting-311:22
*** pewp is now known as Guest7499411:23
*** slaweq_ has joined #openstack-meeting-311:24
*** slaweq_ has quit IRC11:25
*** lyan has joined #openstack-meeting-311:31
*** baoli has joined #openstack-meeting-311:33
*** slaweq_ has joined #openstack-meeting-311:40
*** slaweq_ has quit IRC11:40
*** yamamoto has joined #openstack-meeting-311:46
*** yamamoto has quit IRC11:50
*** yamamoto has joined #openstack-meeting-311:50
*** yamamoto has quit IRC11:53
*** slaweq_ has joined #openstack-meeting-311:56
*** ducttape_ has joined #openstack-meeting-312:07
*** yamamoto has joined #openstack-meeting-312:10
*** kkxue has quit IRC12:10
*** slaweq_ has quit IRC12:11
*** slaweq_ has joined #openstack-meeting-312:12
*** MarkBaker has quit IRC12:14
*** slaweq_ has quit IRC12:15
*** MarkBaker has joined #openstack-meeting-312:16
*** ducttape_ has quit IRC12:19
*** yamamoto has quit IRC12:19
*** markvoelker has joined #openstack-meeting-312:23
*** yamamoto has joined #openstack-meeting-312:23
*** yamamoto has quit IRC12:28
*** etingof has quit IRC12:28
*** etingof has joined #openstack-meeting-312:29
*** shuyingy_ has quit IRC12:32
*** shuyingya has joined #openstack-meeting-312:32
*** baoli has quit IRC12:34
*** shuyingya has quit IRC12:37
*** daidv_ has joined #openstack-meeting-312:40
*** wanghao has joined #openstack-meeting-312:45
*** pgadiya has quit IRC12:48
*** tobberydberg has quit IRC12:56
*** tobberydberg has joined #openstack-meeting-312:57
*** yamamoto has joined #openstack-meeting-312:59
*** baoli has joined #openstack-meeting-313:00
*** gcb has joined #openstack-meeting-313:15
*** zhurong has quit IRC13:21
*** shuyingya has joined #openstack-meeting-313:22
*** shuyingya has quit IRC13:27
*** scottda has joined #openstack-meeting-313:30
*** liangbo has quit IRC13:33
*** wanghao has quit IRC13:35
*** wanghao has joined #openstack-meeting-313:35
*** wanghao has quit IRC13:35
*** wanghao has joined #openstack-meeting-313:36
*** wanghao has quit IRC13:36
*** wanghao has joined #openstack-meeting-313:36
*** wanghao has quit IRC13:37
*** wanghao has joined #openstack-meeting-313:37
*** wanghao has quit IRC13:38
*** wanghao has joined #openstack-meeting-313:38
*** wanghao has quit IRC13:39
*** wanghao has joined #openstack-meeting-313:39
*** wanghao has quit IRC13:39
*** wanghao has joined #openstack-meeting-313:40
*** wanghao has quit IRC13:40
*** wanghao has joined #openstack-meeting-313:41
*** julim has quit IRC13:42
*** lhx_ has joined #openstack-meeting-313:47
*** namnh has joined #openstack-meeting-313:50
*** daidv_ has quit IRC13:51
*** daidv_ has joined #openstack-meeting-313:54
*** kgiusti has joined #openstack-meeting-313:56
gcb#startmeeting oslo14:00
openstackMeeting started Mon Jul  3 14:00:07 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, 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
amrith./14:00
kgiustio/14:00
dimso/14:00
daidv_o/14:01
namnho/14:01
gcbamrith, kgiusti ,dims, daidv_, namnh  \o/14:01
gcb#topic Red flags for/from liaisons14:01
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"14:01
*** daidv__ has joined #openstack-meeting-314:02
amrithnothing from trove14:02
*** Guest74994 has quit IRC14:02
*** amotoki_away is now known as amotoki14:02
gcbamrith, ack, thanks14:03
lhx_o/14:03
*** pewp has joined #openstack-meeting-314:03
*** pewp is now known as Guest8191814:03
gcbhi lhx_14:03
lhx_hi, gcb14:04
gcbI found there is only one failure for cinder in http://logs.openstack.org/periodic/periodic-cinder-py27-with-oslo-master/7e3a366/testr_results.html.gz14:04
gcbwill check it later14:04
lhx_gcb, I will try it later14:04
gcblhx_: thanks14:04
gcb#topic Releases for Pike14:04
*** openstack changes topic to "Releases for Pike (Meeting topic: oslo)"14:04
gcbmaster: https://review.openstack.org/47982314:05
gcbstable/ocata: https://review.openstack.org/47911614:05
gcbstable/newton: https://review.openstack.org/47601714:05
gcbwill release for stable branch at least one time each month14:08
gcb#topic Stuck Reviews14:08
*** openstack changes topic to "Stuck Reviews (Meeting topic: oslo)"14:08
gcbwe have many doc-migration patches ready for approval, just check https://review.openstack.org/#/q/status:open+branch:master+topic:doc-migration14:09
gcbdims: dhellmann has many patches which need +A :-)14:09
dimsouch, that's a lot14:10
gcbdims: it's easy to review if you follow the instructions in https://etherpad.openstack.org/p/doc-migration-tracking14:11
dimsah it's everything (all projects). added  is:watched to get a subset of them14:11
dimsthanks gcb14:11
gcbnamnh, around ?14:12
namnhgcb: yes, I am here14:12
namnhcan I start our topic?14:12
gcbnamnh,  It's your turn :-)  " How to generate a new configuration for (N+n) (n>=2) relase from the exist configuration at N release"14:12
gcbplease go ahead14:13
namnhgcb: I and daidv_ come from the upgrade team of Fujitsu, we are interested in skip release upgrade14:13
namnhespecially how to generate new compatible configuration for (N+2) release from exist our system (N release).14:13
namnhgcb: so our idea is to develop a tool in oslo.config that can generate a new configurations for (N+2) release from old config (N release) and a config-mapping file14:13
namnhNo matter where our configurations is locating (file or etcd) and no matter how we are managing config version (Confd or so on).14:14
namnhWe have read the malling-list that discuss about etcd and confd but even when we have multi backend support or not, have plugable driver like confd or not, we should support operator generate reliable new configuration from old release14:14
namnhFor instance, we have config-mapping file at *Pike* release and keystone.conf at *Newton* release, with this tool, we can generate keystone.conf for Pike.14:15
daidv_how do u think about it?14:16
gcbnamnh, that's is an interesting function. I think I get your point14:17
namnhgcb: great, so how do you think about this idea?14:18
*** ducttape_ has joined #openstack-meeting-314:20
gcbnamnh: what' s your plan to implement it,  I think we have some existing functions to support your idea like config-genrator14:20
daidv_we knew that we can use yaml file is created by oslo-config-generator instead of config-mapping file in the near future in case we can declare full info about what options is replaced by something else like below link.14:21
daidv_#link https://github.com/openstack/keystone/blob/43362700d8c52b2af0ebae8593cad57c968df377/keystone/conf/eventlet_server.py#L26-L3714:21
namnhgcb: I and daidv_ are colleague14:23
gcbwe also have been doing some related work like https://review.openstack.org/384559 , which can collect deprecated config options14:24
gcbjust make sure we can leverage existing function :-)14:25
*** ducttape_ has quit IRC14:25
gcbnamnh: do you have the link of ML about the discussion14:25
gcbdhellmann, around, what do you think namh and daidv_ 's idea ?14:27
namnhgcb: for the malling-list, I am reading this malling-list: http://lists.openstack.org/pipermail/openstack-dev/2017-June/117943.html , is that your link?14:28
*** raildo has joined #openstack-meeting-314:28
daidv_gcb: For "related work like https://review.openstack.org/384559", we also thought about that. But I think we have not have completely list Opts for deprecated config.14:29
*** donghao has joined #openstack-meeting-314:30
daidv_in case we want to generate new configurations (from M to P for instance), we can loss some configs.14:31
namnhs/loss/lose/14:31
gcbdaidv_: please check https://review.openstack.org/#/c/451081/, its blueprint describes will list deprecated options14:32
*** rmart04 has joined #openstack-meeting-314:33
daidv_gcb: I have tryed it to gen yaml file for some projects.14:34
gcbdaiv_, namh: have you any details about how to implement the function ?  I suggest post a commit to oslo-specs to describe the proposal14:34
gcbthen, we can discuss the details in the review.  In general , I like your ideas ,need more input14:35
gcbto decide how to implement it :-)14:36
daidv_gcb: but as I said "we can lose some configurations." if we want to upgrade from N to N+5 or more.14:37
namnhgcb: let me overview this idea. we will create a config-mapping for each project, it's formal maybe is yaml14:38
*** julim has joined #openstack-meeting-314:38
namnhand the config-file can be maintained by each projects14:39
namnhthat they are expert in the project14:39
namnhand another input is config file like keystone.conf at old release14:40
namnhgcb:14:40
gcbthe import thing is the config options' value, which version of code your tools will scan ? N+2 or N code ?14:42
daidv_gcb: N+214:43
gcbwe always got the config options list for each version with oslo-config-generator14:43
gcbhow the config-file will be used ?14:44
*** hieulq_ has joined #openstack-meeting-314:46
namnhgcb: sorry for my mistable. I mean this sentence "and the config-file can be maintained by each projects" is "and the config-mapping can be maintained by each projects"14:46
*** emagana has joined #openstack-meeting-314:47
gcbnamnh, I didn't read the ML discussion before.  the problem is  got N+2 config options' values ,right ?14:48
*** tellesnobrega has quit IRC14:49
gcbnamnh, "we can lose some configurations." means  the values of configurations, right ?14:49
*** rbrady has joined #openstack-meeting-314:49
*** tellesnobrega has joined #openstack-meeting-314:50
*** ducttape_ has joined #openstack-meeting-314:51
*** ducttape_ has joined #openstack-meeting-314:52
namnhgcb: yes, you are right, that why we need two inputs: one is config-mapping at new release and one is config-file at old release.14:52
*** hieulq_ has quit IRC14:52
namnhgcb: to generate a new config file for new release14:53
gcbwhat's information in config-mapping ?  the values of config options  should depend on each deployment, I don't think one config-mapping can handle it14:54
daidv_gcb: config-mapping is the same idea with yaml file which generated by oslo-config-generator14:55
daidv_but oslo-config-generator depend on deprecated configuration name in each Opt()14:56
*** ducttape_ has quit IRC14:56
*** rama_y has joined #openstack-meeting-314:58
gcbhmm...,  the meeting time is over, let's discuss at  #openstack-olso14:59
gcb#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Mon Jul  3 14:59:39 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-07-03-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-07-03-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-07-03-14.00.log.html14:59
*** daidv_ has quit IRC15:00
namnhgcb: sure, please wait a moment15:00
*** namnh has quit IRC15:01
rakhmerov#startmeeting Mistral15:01
openstackMeeting started Mon Jul  3 15:01:33 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
d0ugalo/15:01
rakhmerovhey15:02
rakhmerovwaiting..15:02
tourehello15:02
rakhmerovhi toure15:02
tourerakhmerov hello15:02
rbradyo/15:02
rakhmerovhi rbrady15:02
*** tobberydberg has quit IRC15:02
rbradyhello rakhmerov.  How are you doing?15:02
rakhmerovdoing ok )15:03
rakhmerovstill alive15:03
rakhmerovyou?15:03
* d0ugal is alive too15:03
rakhmerov:)15:04
rakhmerovit's funny15:04
* toure is mostly alive15:04
d0ugalbut I hope you are feeling better rakhmerov!15:04
rakhmerovi was reading a book yesterday where the author has a joke about the word "job"15:04
toure+115:04
rakhmerovabout what it means15:04
rakhmerov"just over broke"15:04
rbradyrakhmerov: I'm doing okay15:04
rakhmerovjust a little better than a bankrupt ) kind of15:05
d0ugalhah15:05
rakhmerovbut I believe we're doing better than this ))15:05
rakhmerovdefinition15:05
apetrich:)15:05
rakhmerovok, let's start15:05
rakhmerov#topic Current status15:06
*** openstack changes topic to "Current status (Meeting topic: Mistral)"15:06
rakhmerovmy status: spent significant time on reviewing patches, including namespaces spec (please do too), also almost finished Mistral java client in OpenStack4j (will be polishing and testing it) and keep working on HA tasks15:07
rakhmerovspecifically, learning OpenStack CI and started working on a new gate15:07
d0ugalWith help from apetrich I was able to remove Mistral from the global requirements, which solved a number of problems15:08
*** tonyb has quit IRC15:08
rakhmerovexcellent!15:08
rbradymy status: slowing working on the port of keystone utils to mistral-lib.  I'm not a keystone expert and recent patches/changes have left me reading more code than writing it in the last week15:08
rakhmerovok15:08
tourestatus: workflow error analysis has taken a turn as sub-workflow tracking proves to be difficult, d0ugal pointed out this flaw in my proposal, He and I have been working on a solution. The problem stems from the parent execution not having the ability to track it's children tasks.15:09
rakhmerovyeah, it needs thinking15:09
apetrichme: as d0ugal said mistral-lib is going strong. I'm fixing some documentation to reflect that15:09
rakhmerovmaybe it's even worth changing the DB model for that15:09
rakhmerovtoure: I also left some questions in the patch, take a look15:09
tourerakhmerov that would help15:10
tourek, will take a look15:10
apetrichalso thanks rakhmerov to make the change to mistral-lib serializer so we can remove that from mistral soon15:10
rakhmerovapetrich: documentation where? TripleO?15:10
apetrichmistral/docs15:10
d0ugalhttps://docs.openstack.org/developer/mistral/developer/creating_custom_action.html15:10
apetrichrakhmerov, ^15:10
rakhmerovooh, ok15:10
rakhmerovwoops15:11
rakhmerov40415:11
rakhmerovI guess it's a temporary problem15:11
rakhmerovok, good anyway )15:11
d0ugalIt works for me :)15:11
rakhmerovreally?15:11
rakhmerovhaha15:11
apetrichhttps://github.com/openstack/mistral/blob/master/doc/source/developer/creating_custom_action.rst15:11
rakhmerovyes, ok15:12
rakhmerovwe need to strive to finish all main changes in mistral lib within 2 weeks15:13
rakhmerovit's very important15:13
rakhmerovI'll try to participate too as much as possible15:13
d0ugalWhat other changes do we need in mistral-lib?15:13
d0ugalI see the mistral-extra work (moving actions etc.) as a different task - I am not sure this will happen in time for P15:14
apetrichGood question15:14
rakhmerovd0ugal: I think we need to port OpenStack actions, it will prove that everything is ok with mistral-lib15:14
apetrichI see the serialization that we can move from mistral into mistral-lib15:14
rakhmerovI think it's not 100% a different task15:14
d0ugalrakhmerov: Mistral itself uses mistral-lib, that should be proof enough :)15:14
rakhmerovok, I may be wrong15:14
apetrichcontext will stay in mistral but we could use a contract from mistral-lib15:14
d0ugaland tripleo does too, which is some external proof.15:14
apetrichAFAIK15:15
rakhmerovI haven't really looked into it for a while and I just want to make sure that it's in a good shape15:15
rakhmerovand also documented well15:15
d0ugalbut yes, it would have been nice if mistral-extra used it as that would cover more use cases.15:15
d0ugal+115:15
*** emagana_ has joined #openstack-meeting-315:16
rakhmerovI'm talking about mistral-extra work because it may potentially point to some issues15:16
rakhmerovhopefully not15:16
d0ugalRight15:16
rakhmerovbtw, as with config options used by actions15:16
rbradyif we're going to port openstack actions to mistral-extra, does that mean we'll need to port the action generator too15:16
rbrady?15:16
d0ugalrbrady: yes, I think so.15:17
rakhmerovyes15:17
rakhmerovit's part of the framework related to actions15:17
rakhmerovit shouldn't be in mistral15:17
d0ugalI had thought about this a bit actually15:17
d0ugalWe have entry_points for invididual actions15:17
d0ugalbut maybe we should have a setup.py entry_point for action generators15:18
rbradythere is more to investigate wrt to the action generator imports15:18
d0ugalthen a generator for aws (for example) could be written and registered15:18
rbradyI like d0ugal's idea15:18
rakhmerovyeah15:18
rakhmerovsure15:18
d0ugalbut I have not looked into this idea at all :)15:18
d0ugalThere is lots that needs to happen first.15:18
*** emagana has quit IRC15:18
rakhmerovkeep in mind that what we've done so far in actions is pretty primitive and not very useable15:19
d0ugalWhat do you mean?15:19
rakhmerovthere should be better ways of configuring them15:19
*** zerick has quit IRC15:19
d0ugalaha15:19
rakhmerovI mean your idea is good! )15:19
d0ugalYes, I think mistral-extra will also need a configuration file15:19
rakhmerovdon't take what we have now as a good example15:20
d0ugalRight15:20
rakhmerovd0ugal: sure, yes, but that will be its own config15:20
rbradyrakhmerov: configure them?  as in configure the client constructors?15:20
rakhmerovof a separate project15:20
*** emagana_ has quit IRC15:20
rakhmerovin my view15:20
rakhmerovrbrady: no, I mean user experience in general. We have to update that huge mapping if something is out of date, we have to register individual entries in setup.cfg15:21
rakhmerovetc.15:21
rakhmerovI mean when you're working on this transition just try to think how to also improve it15:22
rakhmerovI know there's not much time but anyway15:22
d0ugalRight15:22
rakhmerovthis work will continue anyway15:22
d0ugalbecause it would also be better if you didn't need to restart Mistral15:22
d0ugalpeople always find that strange :)15:23
rakhmerovyes, ideally15:23
rbradyautodiscovery for actions sounds cool15:23
rakhmerovyes15:23
d0ugalI think we could solve that quite easily by executing actions in their own process - which would also open the door for non-python actions.15:23
rakhmerovtrue15:24
rakhmerovsome time ago we also thought about the idea of an action provider15:24
rakhmerovsome abstraction that knows how to deliver actions to the system15:24
rakhmerovits contract is basically: getActions()15:24
*** bobh has joined #openstack-meeting-315:24
rakhmerovand it would return all actions15:25
apetrichmmm15:25
rakhmerovonce it's integrated we could have implementations of action providers that could fetch actions from whatever comes to our mind15:25
*** emagana has joined #openstack-meeting-315:26
rakhmerovthey could generate them dynamically as wrappers around external processes, generate based on DB records, etc.15:26
rakhmerovit's just a general idea but it may be worth thinking of (there's even a BP for that)15:26
d0ugalyeah, that might be a nice feature for Q15:27
rakhmerovright15:27
*** psachin has quit IRC15:27
rbradydo I dare ask about actions as containers?15:27
apetrichrakhmerov, do you think have a rabbitmq topic that actions register themselves or a two way communication for getActions to work?15:27
rakhmerovby default, let's say we could have a provider that provides all built-in standard actions15:27
rakhmerovapetrich: yeah, sounds nice15:27
apetrichs/actions/actionproviders/ actually15:27
rakhmerovgot it, yes15:27
*** zerick has joined #openstack-meeting-315:28
apetrichnice15:28
rakhmerovanyway, all these ideas can possibly co-exist15:28
d0ugalyeah15:28
*** yamamoto has quit IRC15:28
rakhmerovhow to configure them, how to develop the them more efficiently, how to deliver them to the system15:28
rakhmerovlots of ideas )15:28
rakhmerovlet me formally open an open discussion15:29
rakhmerov#topic Open Discussion15:29
*** openstack changes topic to "Open Discussion (Meeting topic: Mistral)"15:29
rakhmerovone thing to share15:29
rakhmerovyou have probably seen the news about migrating docs15:30
rakhmerovkind of a sad news15:30
rakhmerovbut15:30
rakhmerovfor us it's kind of a good news because we don't need to move docs )15:30
rakhmerovthey are already in our repo15:30
rakhmerovwe'll just need to adjust docs according to the spec, basically change folder structure15:31
*** yamamoto has joined #openstack-meeting-315:31
rakhmerovand it's good that we got volunteers (my colleagues) to do this work15:31
rakhmerovand they also volunteered to improve docs in general, including installation/configuration guides15:31
*** emagana has quit IRC15:31
rakhmerovRPMs, etc.15:31
rakhmerovI think that's pretty much all from me15:32
d0ugalGreat, looking forward to that docs work.15:33
rakhmerovany other topics?15:33
rakhmerovyeah15:33
d0ugalNothing from me.15:33
rakhmerovok15:33
d0ugaloh, actually15:33
tourenothing from me either...15:33
d0ugal[openstack-dev] [tc][all] Move away from meeting channels15:34
rakhmerovok15:34
rakhmerovd0ugal: yeah?15:34
d0ugalI seen this discussion on openstack-dev, it seems there might be a move away from these channels15:34
d0ugaland it also sounds like some projects are moving away from meetings in general15:34
d0ugalwe don't need to change anything, but it is worth reading and we can then discuss what we want to change if anything.15:35
rakhmerovmaking them ad-hoc?15:35
rakhmerovyes, I read it briefly15:35
d0ugalI think so15:35
rakhmerovnot all the content though15:35
rakhmerovok, no problem15:35
rakhmerovI'm actually ok with the meetings we have15:35
*** daidv__ has quit IRC15:36
rakhmerovI still think that they are useful15:36
rakhmerovbut we can make them more flexible, for example15:36
rakhmerovnot the same day, not the same time15:36
d0ugalyup15:36
*** yamamoto has quit IRC15:36
rakhmerovor on demand15:36
*** gcb has quit IRC15:36
rakhmerovif someone wants to discuss something important we can have them15:37
rakhmerovso ok, let's think about it15:37
rakhmerovI don't have any immediate proposals15:37
rakhmerovregarding that15:37
rakhmerovok15:37
rakhmerovjust one more thing from me: as far as my personal contribution, I planned to participate actively in all things like docs and actions but I'll have to be focused on HA because of our internal very strict deadlines15:38
rakhmerovessentially I have to make it work in HA in the next 2 months :)15:38
rakhmerovno choice15:38
*** MarkBaker has quit IRC15:38
rakhmerovbut I'll be reviewing and helping anyway15:39
rakhmerovok, so let's end the meeting earlier then?15:39
rakhmerovd0ugal, rbrady, toure, apetrich?15:40
toureack15:40
apetrichaye15:40
rbradyack15:40
rakhmerovok15:40
d0ugalsounds good15:40
rakhmerovas usually, thanks for joining )15:40
rakhmerovand happy Independence Day, us folks! :)15:40
toureThansk15:40
tourethanks15:40
rakhmerov.. US folks ..15:40
toure:)15:40
rakhmerovok, bye15:40
rakhmerov#endmeeting15:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:41
openstackMeeting ended Mon Jul  3 15:41:11 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/mistral/2017/mistral.2017-07-03-15.01.html15:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/mistral/2017/mistral.2017-07-03-15.01.txt15:41
openstackLog:            http://eavesdrop.openstack.org/meetings/mistral/2017/mistral.2017-07-03-15.01.log.html15:41
*** bobh has quit IRC15:41
*** rbrady has left #openstack-meeting-315:41
tourewc15:42
*** toure has left #openstack-meeting-315:42
*** crushil_ has joined #openstack-meeting-315:49
*** donghao has quit IRC15:50
*** andreas_s has quit IRC15:52
*** liangbo has joined #openstack-meeting-315:57
*** tuanla_fujitsu has joined #openstack-meeting-316:00
*** tuanla__ has joined #openstack-meeting-316:01
*** crushil_ has quit IRC16:01
*** crushil_ has joined #openstack-meeting-316:01
*** MarkBaker has joined #openstack-meeting-316:03
*** crushil_ has quit IRC16:06
*** makowals has quit IRC16:06
*** akuznetsova has quit IRC16:14
*** rakhmerov has quit IRC16:14
*** rakhmerov has joined #openstack-meeting-316:15
*** tobberydberg has joined #openstack-meeting-316:16
*** amotoki is now known as amotoki_away16:17
*** akuznetsova has joined #openstack-meeting-316:19
*** liangbo has quit IRC16:19
*** borisnet[m] has quit IRC16:19
*** anubhaskar[m] has quit IRC16:19
*** Eko[m] has quit IRC16:20
*** zerga[m] has quit IRC16:20
*** tobberydberg has quit IRC16:21
*** NikitaKonovalov has quit IRC16:22
*** junbo has quit IRC16:22
*** NikitaKonovalov has joined #openstack-meeting-316:25
*** Eko[m] has joined #openstack-meeting-316:25
*** junbo has joined #openstack-meeting-316:28
*** ccamacho has quit IRC16:30
*** yamamoto has joined #openstack-meeting-316:33
*** anubhaskar[m] has joined #openstack-meeting-316:34
*** zerga[m] has joined #openstack-meeting-316:34
*** borisnet[m] has joined #openstack-meeting-316:34
*** pcaruana has quit IRC16:35
*** bobmel has quit IRC16:38
*** yamamoto has quit IRC16:39
*** makowals has joined #openstack-meeting-316:42
*** fellypefca has joined #openstack-meeting-316:43
*** bobmel has joined #openstack-meeting-316:43
*** bobmel has quit IRC16:43
*** bobmel has joined #openstack-meeting-316:43
*** rmart04 has quit IRC16:47
*** bobmel has quit IRC16:50
*** coolsvap has quit IRC16:51
*** Guest81918 has quit IRC16:51
*** liangbo has joined #openstack-meeting-316:51
*** _pewp_ has joined #openstack-meeting-316:52
*** ducttape_ has joined #openstack-meeting-316:53
*** marios has quit IRC16:53
*** crushil_ has joined #openstack-meeting-316:53
*** vmud213 has joined #openstack-meeting-316:54
*** crushil_ has quit IRC16:55
*** crushil_ has joined #openstack-meeting-316:56
*** ducttape_ has quit IRC16:57
*** milan has joined #openstack-meeting-316:58
*** nicodemos has joined #openstack-meeting-316:59
*** _pewp_ has quit IRC16:59
*** mgoddard_ has joined #openstack-meeting-316:59
TheJulia#startmeeting ironic17:00
openstackMeeting started Mon Jul  3 17:00:15 2017 UTC and is due to finish in 60 minutes.  The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
TheJuliao/17:00
mrtenioo/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
fellypefcao/17:00
milano/17:00
mgoddard_\o17:00
rama_yo/17:00
*** _pewp_ has joined #openstack-meeting-317:00
etingofo/17:01
TheJuliaThis being a holiday week, I'm expecting attendance to be light today.17:01
crushil_\o17:01
TheJuliaOur Agenda can be found on the wiki17:01
*** rpioso has joined #openstack-meeting-317:01
nicodemoso/17:02
vdroko/17:02
rpiosoo/17:02
TheJulia#link https://wiki.openstack.org/wiki/Meetings/Ironic17:02
*** tuanla_fujitsu has quit IRC17:02
*** tuanla__ has quit IRC17:02
*** xavierr has joined #openstack-meeting-317:02
*** stendulker has joined #openstack-meeting-317:02
TheJulia#topic Announcements / Reminder17:02
*** openstack changes topic to "Announcements / Reminder (Meeting topic: ironic)"17:02
stendulkero/17:02
xavierro/17:03
*** ralonsoh has quit IRC17:03
*** sauloaislan has joined #openstack-meeting-317:03
sauloaislanMorning!!!17:03
sambettso/17:03
TheJuliaFirst off, Our documentation on docs.o.o is broken. sambetts has started putting together changes to hopefully address this for our main repo, but all of our doc tress will likely require some attention over the next few days. I'll pickup on sambett's work after he decides to call it a night.17:04
*** ricardoas has joined #openstack-meeting-317:04
sambettsthanks TheJulia :)17:04
TheJuliaThis is a result of the project wide documentation migration project.17:04
ricardoaso/17:04
TheJulia#link https://etherpad.openstack.org/p/doc-migration-tracking17:04
*** Nisha_Agarwal has joined #openstack-meeting-317:05
TheJuliasambetts: I'll review them against the spec/docs/instructions as well, hopefully we can get the majority of this cleaned up quickly17:05
TheJuliaSecondly, milan wanted to let us know that we have a new person joining us.17:05
milanTheJulia, thanks! :)17:05
TheJuliaGreetings etingof!  Welcome to this crazy batch of people :)17:06
sambettshey etingof17:06
milanI'm very happy to introduce Ilya Etingof, etingof, to the Ironic folks!17:06
etingofthank you! I'm really excited joining you! ;-)17:06
vdrokwelcome :)17:06
*** bfournie has joined #openstack-meeting-317:07
xavierrhey etingof, welcome17:07
TheJuliaetingof: Please don't hesitate to ask questions. We've all learned this is a very complex project, so don't feel bad if you have questions, or need help at any time.17:07
milanTheJulia, ++17:08
etingofsure, thank you!17:08
TheJuliaWith that having been said, does anyone else have any announcements/reminders for us?17:08
* TheJulia guesses no17:09
TheJuliaMoving on!17:09
TheJulia#topic Subteam status report17:10
*** openstack changes topic to "Subteam status report (Meeting topic: ironic)"17:10
TheJulia#link https://etherpad.openstack.org/p/IronicWhiteBoard17:10
TheJuliaStarting at line 92...17:10
* TheJulia sense people typing furiously :)17:13
xavierrso...17:15
TheJuliaIt looks like we didn't get as much as we hoped done last week, and it also looks like some of the sections were not updated since people with context are jut not present17:15
* TheJulia is running a little slow because of connectivity17:16
TheJuliaI don't have any questions, and I guess we can just move forward to priorities for the week if nobody has questions/comments from the ether pad?17:17
*** MarkBaker has quit IRC17:19
*** crushil_ has quit IRC17:19
*** tonyb has joined #openstack-meeting-317:19
TheJuliamilan: If that is you typing, yes, we've all been impacted by the docs changes :(17:19
milanTheJulia, ack, yeah wanted to record it17:20
* milan files a bug17:20
milan* for inspector17:20
milanor do we have some template for that?17:20
NobodyCamalmost forgot17:20
NobodyCamo/17:21
*** lyan has quit IRC17:21
TheJuliamilan: the changes, see the ether pad for the doc migration.  It has a link to a spec with instructions. :)17:21
TheJulia\o NobodyCam17:21
milanTheJulia, ack, thanks :)17:21
TheJuliamilan: no problem. :)17:21
TheJuliaI guess we should move on17:22
TheJulia#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
sambettsI think the first one has to be docs right?17:22
TheJuliaYup!17:22
TheJuliaI think that is one we're going to have to update as we go17:23
TheJulia\o/ kicked off etherpad17:24
TheJuliaand it is still loading17:24
*** lyan has joined #openstack-meeting-317:24
TheJuliaSecond, I think would be BFV.  We have two patches before we can begin unblocking the client API patches. Both of the are in the list on the etherpad17:24
TheJuliaIt looks like the rest is fairly reasonable since it will be a relatively quiet week.17:25
TheJuliaDoes anyone have anything specific they wish to raise to that list?17:26
xavierrTheJulia: can we test BFV already? :)17:26
TheJuliaxavierr: Yes, There is a notes ether pad covering that someplace. I'll have to look17:27
mgoddard_it would be nice to get the physnet awareness work back on the priority list.17:27
sambetts+117:27
*** sambetts is now known as sambetts|afk17:28
mgoddard_there are a few patches backing up, some only tangentially related to physnets but seem to have ended up blocking it17:28
mgoddard_First blocker is https://review.openstack.org/47759717:28
TheJuliamgoddard_: sambetts|afk Is there anything that is needed in nova for it?17:28
xavierrTheJulia: ty, paste the link if you find it :)17:28
mgoddard_TheJulia: no nova changes required17:29
*** sambetts_ has joined #openstack-meeting-317:29
TheJuliamgoddard_: nothing neutron/client library related that needs to land this cycle?17:29
mgoddard_TheJulia: nope, it's all in ironic-governed projects17:30
sambetts_mgoddard_: do we need to add physical network to the client??17:30
sambetts_The field I mean, to like port create etc17:30
TheJuliaand does it need to occur this cycle for the client library release freeze?17:30
mgoddard_sambetts_: https://review.openstack.org/#/c/461893 adds physnet support to ironic OSC commands17:30
mgoddard_when's the client release freeze?17:30
TheJuliadouble checking17:31
xavierrmgoddard_: Jul 24 - Jul 2817:31
*** makowals_ has joined #openstack-meeting-317:31
xavierrhttps://releases.openstack.org/pike/schedule.html17:31
mgoddard_no pressure then :)17:32
TheJuliaI was just going to paste that :)17:32
TheJulia#link https://releases.openstack.org/pike/schedule.html17:32
* xavierr was faster17:32
TheJulia(or you just have less lossy internet)17:32
NobodyCam:)17:32
xavierrhahaha17:33
*** nicodemos has left #openstack-meeting-317:33
mgoddard_3 weeks. sambetts_, thoughts on parking the VIFPortIDMixin refactor in favour of pushing forward physnet support before feature freeze, which is apparently 4 weeks away?17:34
TheJuliaWe really need to get the stuffs in for nova for BFV this cycle, I'm personally okay if we cut >1 client library releases leading up to that date.  Personally I want to get the bfv stuff in a place where we have unblocked nova and can cut a client library release, and without dmitry, I'm hesitant to re-add it to the priorities list.  That being said, it sounds like the blocker needs to be resolved first?17:35
*** makowals has quit IRC17:35
TheJuliaThe key is client library freeze, we'll just become hesitant to land code to ironic the closer we get to when we need to cut a release, as we always do.17:35
vdrokwhich patches do we need to unblock nova? only the rest api one?17:36
mgoddard_it's really a soft blocker, in that an early code refactor makes later patches cleaner17:36
vdrokoh, and client17:36
TheJuliavdrok: two for the rest api to land, two client patches to which allows targets to be added if memory serves.17:37
sambetts_mgoddard_: can we make the field accessible on the API before we start using it in vif port mixin? That unties us from the client libs17:38
mgoddard_sambetts_: it's possible, just means we end up with a behaviour change without a corresponding API bump17:40
TheJuliaThat sounds a little dicey17:40
sambetts_Or we land messy vif port ID mixin with the promise that we clean it up before any more code gets landed in vif port ID mixin17:40
mgoddard_I guess we could later bump again if that is an issue17:40
sambetts_Making vif attach port attach pay attention to physical network doesn't require a bump17:41
TheJuliait shouldn't as long as behavior can stay consistent for the users17:42
sambetts_In the same we we didn't bump when we enable post deploy attachmeny17:42
mgoddard_ok, if there's a precedent then I guess it's ok17:42
sambetts_But this is a grey area for API bumping17:42
sambetts_Because it's actual driver functionality leaking through to the API17:43
TheJuliaYeah, given the timeframe, I'm okay with minimum viable path to get the client api patch landed and then doing the refactoring.  Dmitry may feel otherwise though, so as we say in the states, your milage may vary.17:43
vdrokI'd prefer both field and its use to be landed together, but yeah, it is possible to do separately17:44
sambetts_Ok then I say land messy patch with all the extra checks and follow it immediately with the vif port mixin refactoring17:45
TheJuliaIt seems like we need to get a plan together for that, and we should be able to move forward on that if we can also get bfv moving forward this week17:45
mgoddard_sambetts_: +117:46
* mordred waves17:46
TheJuliaSounds like we are in an okay shape for this week, and we can move forward to open discussion, that is if there are no objections?17:47
sambetts_Sounds good17:47
NobodyCammorning mordred :)17:47
TheJulia#topic Open Discussion17:47
*** openstack changes topic to "Open Discussion (Meeting topic: ironic)"17:47
TheJuliaAnyone have anything else to discuss today?17:48
rama_yHi, regarding this patch:17:48
rama_yhttps://review.openstack.org/#/c/358142/17:48
Nisha_AgarwalTheJulia, hi.17:48
rama_yThis has been reviewed by osprofiler cores several times. Needs Ironic cores' review.17:48
TheJuliarama_y: We have very few cores on hand today, but we can make a note of it?17:49
Nisha_Agarwalregarding https://review.openstack.org/#/c/408441/17:49
rama_yTheJulia, thanks very much.17:50
TheJulia#note rama_y is seeking core reviewers to review the osprofiler addition https://review.openstack.org/#/c/358142/17:50
* mordred can't remember who was working on the "consume endpoints from catalog" patches -but I wanted to let folks know that the keystoneauth patches to make that all work really well are mostly landed17:51
*** lhx_ has quit IRC17:51
mordredwe've landed list-of-interfaces, support for major version ranges and reporting discovered microversion support - hopefully will land service-type alias support this week or next week17:52
vdrokpas-ha was, I'll let him know, thx!17:52
Nisha_AgarwalThis patch as i understand is pending in lack of CI. We at HPE is lacking hardware to get this feature onto CI. I sit OK if we have it in tempest as of now and support it in CI when we get the hardware.17:53
Nisha_Agarwalhttps://review.openstack.org/#/c/408441/17:53
Nisha_Agarwals/I sit/Is it17:53
vdrokhrm , isn't it just a doc patch?17:54
* Nisha_Agarwal just asking opinion17:54
Nisha_Agarwalyes17:54
vdrokoh, I see the comment from JayF17:54
*** Nisha_Agarwal has quit IRC17:54
*** Nisha_Agarwal has joined #openstack-meeting-317:55
TheJulia\o/ irccloud17:55
TheJuliaAnyway!17:55
milanlol17:56
TheJuliaNisha_Agarwal: I think reviews on doc changes will need to wait unless it is on a critical path for client library release17:56
Nisha_Agarwalclient library includes third party libraries?17:56
TheJuliamordred: I'll pass that along to pas-ha17:57
* Nisha_Agarwal is always confused with these terminologies17:57
TheJuliaIronic's core reviewer bandwidth needs to focus on making sure python-ironicclient can be released in time for it to be consumed by other projects17:57
Nisha_Agarwalok17:58
*** slaweq has joined #openstack-meeting-317:58
TheJuliaWith that being said, we have two minutes left17:58
TheJuliaAnything else today17:58
Nisha_Agarwali understand that part and agree also17:58
Nisha_Agarwalnothing else from my side17:58
Nisha_Agarwal:)17:58
rama_yTheJulia, regarding the osprofiler patch, rloo has provided significant feedback on the patch and the patch has been revised; just wanted to add to my earlier request.17:58
Nisha_AgarwalThanks for clarifying17:58
vdrokregarding the client, would be also good to have some reviews on https://review.openstack.org/35906117:58
TheJuliaYeah, we do need to review that18:00
TheJuliathank you vdrok18:00
* TheJulia makes a note18:00
vdrokthanks all!18:00
TheJulia#note vdrok points out that we need reviews on the python-ironicclient patch https://review.openstack.org/35906118:00
TheJuliaThanks everyone! See you next week, and in #openstack-ironic in the mean time18:00
TheJulia#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Mon Jul  3 18:00:47 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-07-03-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-07-03-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-07-03-17.00.log.html18:00
*** stendulker has quit IRC18:01
*** fellypefca has left #openstack-meeting-318:01
*** mgoddard_ has quit IRC18:14
*** ducttape_ has joined #openstack-meeting-318:23
*** s3wong has joined #openstack-meeting-318:24
*** etingof has quit IRC18:25
*** lpetrut has quit IRC18:26
*** ducttape_ has quit IRC18:28
*** milan has quit IRC18:30
*** slaweq has quit IRC18:34
*** slaweq has joined #openstack-meeting-318:36
*** s3wong has quit IRC18:37
*** MarkBaker has joined #openstack-meeting-318:38
*** s3wong has joined #openstack-meeting-318:40
*** slaweq has quit IRC18:40
*** s3wong has quit IRC18:48
*** jtomasek has joined #openstack-meeting-318:54
*** slaweq has joined #openstack-meeting-319:05
*** slaweq has quit IRC19:05
*** slaweq has joined #openstack-meeting-319:07
*** slaweq has quit IRC19:12
*** lpetrut has joined #openstack-meeting-319:21
*** ducttape_ has joined #openstack-meeting-319:23
*** liangbo has quit IRC19:26
*** ducttape_ has quit IRC19:27
*** Nisha_Agarwal has quit IRC19:28
*** MarkBaker has quit IRC19:37
*** markvoelker has quit IRC19:45
*** markvoelker has joined #openstack-meeting-319:47
*** slaweq has joined #openstack-meeting-319:49
*** blancos has joined #openstack-meeting-319:59
*** julim has quit IRC20:04
*** jtomasek has quit IRC20:10
*** bfournie has quit IRC20:17
*** kzaitsev_mb has joined #openstack-meeting-320:27
*** _pewp_ has quit IRC20:27
*** kgiusti has quit IRC20:27
*** _pewp_ has joined #openstack-meeting-320:30
*** kzaitsev_mb has quit IRC20:33
*** s3wong has joined #openstack-meeting-320:35
*** kzaitsev_mb has joined #openstack-meeting-320:37
*** kzaitsev_mb has quit IRC20:54
*** lyan has quit IRC20:56
*** kzaitsev_mb has joined #openstack-meeting-321:03
*** yamahata has joined #openstack-meeting-321:06
*** jtomasek has joined #openstack-meeting-321:08
*** mrtenio has quit IRC21:16
*** bfournie has joined #openstack-meeting-321:20
*** bfournie has quit IRC21:22
*** kzaitsev_mb has quit IRC21:22
*** kzaitsev_mb has joined #openstack-meeting-321:22
*** ducttape_ has joined #openstack-meeting-321:24
*** lpetrut has quit IRC21:25
*** s3wong has quit IRC21:28
*** ducttape_ has quit IRC21:29
*** blancos has left #openstack-meeting-321:31
*** vmud213 has quit IRC21:38
*** neiljerram has quit IRC21:41
*** jtomasek has quit IRC21:50
*** julim has joined #openstack-meeting-321:56
*** lyan has joined #openstack-meeting-322:27
*** neiljerram has joined #openstack-meeting-322:30
*** armstrong has joined #openstack-meeting-322:34
*** armstrong has quit IRC22:36
*** slaweq has quit IRC22:48
*** slaweq has joined #openstack-meeting-322:49
*** neiljerram has quit IRC22:51
*** slaweq has quit IRC22:53
*** kzaitsev_mb has quit IRC22:57
*** rmascena has joined #openstack-meeting-323:38
*** raildo has quit IRC23:41
*** rmascena has quit IRC23:48

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