Wednesday, 2017-07-12

*** ihrachys has quit IRC00:01
*** emagana_ has quit IRC00:03
*** abalutoiu has quit IRC00:05
*** reedip_ has joined #openstack-meeting00:07
*** gmann has quit IRC00:11
*** gmann has joined #openstack-meeting00:11
*** wanghao has joined #openstack-meeting00:16
*** thorst has quit IRC00:17
*** jbadiapa_ has quit IRC00:17
*** wxy- has joined #openstack-meeting00:19
*** rajathagasthya has quit IRC00:19
*** Swami has quit IRC00:22
*** Julien-zte has joined #openstack-meeting00:25
*** makowals has quit IRC00:27
*** vishwanathj has quit IRC00:30
*** reedip_ has quit IRC00:30
*** vishwanathj has joined #openstack-meeting00:30
*** jbadiapa_ has joined #openstack-meeting00:32
*** caowei has joined #openstack-meeting00:33
*** xyang1 has quit IRC00:35
*** zhurong has joined #openstack-meeting00:42
*** Julien-zte has quit IRC00:42
*** slaweq has joined #openstack-meeting00:43
*** Julien-zte has joined #openstack-meeting00:43
*** hieulq has quit IRC00:44
*** XueFeng has left #openstack-meeting00:45
*** wxy- has quit IRC00:46
*** wxy- has joined #openstack-meeting00:46
*** Apoorva has quit IRC00:48
*** slaweq has quit IRC00:48
*** Julien-zte has quit IRC00:48
*** Julien-zte has joined #openstack-meeting00:49
*** baoli has joined #openstack-meeting00:49
*** dmacpher has quit IRC00:50
*** Julien-zte has quit IRC00:50
*** wxy- has quit IRC00:51
*** vishwanathj has quit IRC00:53
*** RonghUI has joined #openstack-meeting00:54
*** vishwanathj has joined #openstack-meeting00:54
*** bobh has joined #openstack-meeting00:55
*** gcb has quit IRC00:57
*** Yipei has joined #openstack-meeting00:57
*** abalutoiu has joined #openstack-meeting00:58
*** hieulq has joined #openstack-meeting00:59
*** joehuang has joined #openstack-meeting00:59
*** Nel1x has quit IRC00:59
*** dongfeng has joined #openstack-meeting00:59
*** hejiawei has joined #openstack-meeting01:01
joehuang#startmeeting tricircle01:01
openstackMeeting started Wed Jul 12 01:01:39 2017 UTC and is due to finish in 60 minutes.  The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot.01:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:01
*** openstack changes topic to " (Meeting topic: tricircle)"01:01
openstackThe meeting name has been set to 'tricircle'01:01
joehuanghello01:01
hejiaweihi01:01
Yipeihi01:01
joehuang#topic rollcall01:01
*** openstack changes topic to "rollcall (Meeting topic: tricircle)"01:01
zhiyuanhi01:01
joehuang#info joehuang01:02
dongfenghi01:02
zhiyuan#info zhiyuan01:02
dongfeng#info dongfeng01:02
hejiawei#info hejiawei01:02
*** tovin07_ has joined #openstack-meeting01:02
*** xuzhuang has joined #openstack-meeting01:02
RonghUI#info ronghui01:02
*** yinxiulin has joined #openstack-meeting01:02
xuzhuang#info xuzhuang01:02
joehuang#topic feature implementation review01:02
*** openstack changes topic to "feature implementation review (Meeting topic: tricircle)"01:02
yinxiulin#info xiulin01:02
Yipei#info Yipei01:03
joehuangthe pike-3 is approching01:03
joehuangthe date is july 2801:03
joehuanglet's have a short review for the ongoing development features01:03
dongfengfor me, the pagination feature for routing is under review.01:04
joehuangto dongfeng, yes, almost done01:05
xuzhuangfor job pagination, paginate_query has finished, and some test cases has added, now I need to modify the code after your review01:05
dongfengen, a question left there after your comment.01:05
zhiyuanthe spec for smoke test has been merged, hopefully the patches for single/multiple gateway topology test can be merged in Pike01:05
*** gouthamr has quit IRC01:06
Yipeifor lbaas, already finish installing octavia in multiple pods, plan to test lbaas across instances of different subnets01:07
joehuang@dongfeng, ok, so should we support sort filter in the api request01:07
dongfengto joe, for simplicity, sort by id is more simple01:07
Yipeifor importing external network, already begin coding01:07
joehuangto zhiyuan, smoke test landing is very important to guarantee the code quality, so it'll be put with high priority01:08
yinxiulinthe sfc's update patch is under review01:08
joehuangto Yipei, great progress01:08
joehuanghope LBaaS can work soon for multi-pod01:08
Yipeiok, got it. i will make it01:09
*** s3wong has quit IRC01:09
joehuanghow do you guys think about the pagination sort key?01:09
dongfengif we sort by a key, then this key will served as marker.01:09
joehuanghow about server pagination and port pagination?01:10
*** bobh has quit IRC01:10
dongfengcurrently marker is hardcoded to id.01:10
dongfengwhat's the requirement for  server pagination and port pagination?01:11
joehuangI meant do you have an idea about the server pagination/port pagination to deal with sort01:12
zhiyuanaccording to https://specs.openstack.org/openstack/api-wg/guidelines/pagination_filter_sort.html01:12
zhiyuanthe sort key is usually the ID of the item, but not require to01:12
zhiyuanthis page also talks about ID: https://developer.openstack.org/api-guide/compute/paginated_collections.html01:13
zhiyuan"The ``marker`` parameter is the ID of the last item in the previous list. By default, the service sorts items by create time in descending order. When the service cannot identify a create time, it sorts items by ID.The ``marker`` parameter is the ID of the last item in the previous list. By default, the service sorts items by create time in descending order. When the service cannot identify a01:14
zhiyuancreate time, it sorts items by ID."01:14
joehuangBy default, the service sorts items by create time in descending order01:16
hejiaweifor qos, xiongqiu will update it tonight.01:16
*** hieulq has quit IRC01:16
*** tovin07_ has quit IRC01:16
*** vishwanathj has quit IRC01:16
*** vishwanathj has joined #openstack-meeting01:17
joehuangfor routing table, because the id is bigint, so desceding is fine01:17
*** bobh has joined #openstack-meeting01:17
joehuangfrom latest one to the oldest one01:17
*** vishwanathj has quit IRC01:18
joehuangsorry, from the last one to the first one01:18
dongfengyou mean like 4 3 2 1 ?01:18
*** vishwanathj has joined #openstack-meeting01:18
*** hjw_ has joined #openstack-meeting01:18
zhiyuanyes, just change "asc" to "desc"01:18
joehuangwhen you check, you often want to know the new added items01:19
dongfengso, filter won't contain sorts?01:19
joehuangso descending is more reasonable01:19
dongfengok, I will change sort direction.01:19
dongfengcurrently id representation can denote creation time01:21
joehuangok01:22
dongfengthen I will hardcoded sort key to id. change its direction to desc.01:23
joehuangfor qos, the patch needs to fix the issue in gate/check test, for example pep801:24
joehuangand functional test01:24
joehuangreviewers only do review if a patch passes all test01:25
*** wanghao_ has joined #openstack-meeting01:25
*** wanghao has quit IRC01:25
*** rossella_s has quit IRC01:26
*** dfflanders has quit IRC01:26
joehuang#topic open discussion01:27
*** openstack changes topic to "open discussion (Meeting topic: tricircle)"01:27
joehuangtopic to discuss?01:27
*** elynn has joined #openstack-meeting01:27
dongfengno for me01:27
RonghUIno  for me01:28
Yipeino01:28
zhiyuanno01:28
xuzhuangno for me01:28
joehuang#info reviewers only do review if a patch passes all test01:29
joehuangfine, let's end the meeting, and discuss in #openstack-tricicle if needed01:29
joehuang#endmeeting01:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"01:29
openstackMeeting ended Wed Jul 12 01:29:56 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)01:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tricircle/2017/tricircle.2017-07-12-01.01.html01:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tricircle/2017/tricircle.2017-07-12-01.01.txt01:30
openstackLog:            http://eavesdrop.openstack.org/meetings/tricircle/2017/tricircle.2017-07-12-01.01.log.html01:30
RonghUIbye01:30
joehuangbye01:30
Yipeibye01:30
dongfengbye..01:30
*** Yipei has quit IRC01:30
xuzhuangbye01:30
zhiyuanbye01:30
*** julim has joined #openstack-meeting01:31
*** ihrachys has joined #openstack-meeting01:31
*** xuzhuang has quit IRC01:32
*** bobh has quit IRC01:33
*** mriedem has quit IRC01:33
*** dmacpher has joined #openstack-meeting01:35
*** awaugama has quit IRC01:38
*** elynn_ has joined #openstack-meeting01:38
*** elynn has quit IRC01:41
*** galstrom_zzz is now known as galstrom01:42
*** makowals has joined #openstack-meeting01:44
*** slaweq has joined #openstack-meeting01:45
*** dongfeng has left #openstack-meeting01:49
*** slaweq has quit IRC01:49
*** fzdarsky_ has joined #openstack-meeting01:51
*** fzdarsky|afk has quit IRC01:53
*** wanghao has joined #openstack-meeting01:56
*** lakerzhou has joined #openstack-meeting01:58
*** wanghao_ has quit IRC01:58
*** annegentle has joined #openstack-meeting01:58
*** yamahata has quit IRC02:00
*** iyamahat has quit IRC02:00
*** bobh has joined #openstack-meeting02:03
*** anilvenkata has quit IRC02:06
*** tovin07_ has joined #openstack-meeting02:07
*** hieulq has joined #openstack-meeting02:07
*** hongbin has joined #openstack-meeting02:09
*** dtroyer has quit IRC02:11
*** dtroyer has joined #openstack-meeting02:12
*** unicell has quit IRC02:13
*** hjw_ has quit IRC02:13
*** litao__ has joined #openstack-meeting02:22
*** ricolin has joined #openstack-meeting02:24
*** gouthamr has joined #openstack-meeting02:25
*** annegentle has quit IRC02:29
*** julim has quit IRC02:29
*** julim has joined #openstack-meeting02:30
*** __huzhj has joined #openstack-meeting02:30
*** lakerzhou has quit IRC02:32
*** makowals has quit IRC02:33
*** julim has quit IRC02:38
*** thorst has joined #openstack-meeting02:39
*** hieulq has quit IRC02:39
*** tovin07_ has quit IRC02:40
*** wanghao_ has joined #openstack-meeting02:43
*** wanghao has quit IRC02:43
*** thorst has quit IRC02:44
*** slaweq has joined #openstack-meeting02:45
*** makowals has joined #openstack-meeting02:49
*** yamahata has joined #openstack-meeting02:50
*** slaweq has quit IRC02:50
*** wanghao has joined #openstack-meeting02:54
*** wanghao__ has joined #openstack-meeting02:55
*** wanghao has quit IRC02:55
*** wanghao_ has quit IRC02:58
*** makowals has quit IRC03:01
*** yinxiulin has quit IRC03:04
*** lakerzhou has joined #openstack-meeting03:04
*** rajathagasthya has joined #openstack-meeting03:05
*** rajathagasthya has quit IRC03:05
*** julim has joined #openstack-meeting03:07
*** zhurong has quit IRC03:08
*** bobh has quit IRC03:09
*** wanghao has joined #openstack-meeting03:10
*** julim has quit IRC03:11
*** wanghao__ has quit IRC03:14
*** hieulq has joined #openstack-meeting03:16
*** tovin07_ has joined #openstack-meeting03:21
*** baoli has quit IRC03:22
*** baoli has joined #openstack-meeting03:26
*** baoli has quit IRC03:31
*** joehuang has quit IRC03:33
*** lakerzhou has quit IRC03:33
*** lakerzhou has joined #openstack-meeting03:34
*** galstrom is now known as galstrom_zzz03:34
*** gcb has joined #openstack-meeting03:36
*** lakerzhou1 has joined #openstack-meeting03:37
*** lakerzhou has quit IRC03:37
*** julim has joined #openstack-meeting03:39
*** makowals has joined #openstack-meeting03:40
*** zhurong has joined #openstack-meeting03:44
*** gouthamr has quit IRC03:46
*** slaweq has joined #openstack-meeting03:46
*** tbh1 has joined #openstack-meeting03:49
*** beekhof_mb has joined #openstack-meeting03:51
*** slaweq has quit IRC03:51
*** beekhof_mb has quit IRC03:54
*** tbh1 has quit IRC03:58
*** beekhof_mb has joined #openstack-meeting04:02
*** tonyb has quit IRC04:05
*** lakerzhou2 has joined #openstack-meeting04:06
*** lakerzhou1 has quit IRC04:06
*** fnaval has quit IRC04:10
*** hughhalf has quit IRC04:12
*** lakerzhou has joined #openstack-meeting04:16
*** epico has joined #openstack-meeting04:17
*** lakerzhou2 has quit IRC04:19
*** YanXing_an has joined #openstack-meeting04:20
*** adisky__ has joined #openstack-meeting04:21
*** phuoc_ has joined #openstack-meeting04:22
*** andreas-f has joined #openstack-meeting04:24
*** lakerzhou has quit IRC04:25
*** HoloIRCUser4 has joined #openstack-meeting04:27
*** HoloIRCUser4 is now known as tbh104:27
*** tovin07_ has quit IRC04:27
*** tonyb has joined #openstack-meeting04:28
*** beekhof_mb has quit IRC04:28
*** tbh1 has quit IRC04:29
*** hieulq has quit IRC04:30
*** tbh_ has joined #openstack-meeting04:30
*** psachin has joined #openstack-meeting04:30
*** b1airo has quit IRC04:31
*** makowals has quit IRC04:32
*** yamamoto has joined #openstack-meeting04:33
*** dkushwaha has joined #openstack-meeting04:34
dkushwahao/04:34
YanXing_ano/04:34
*** tung_doan has joined #openstack-meeting04:34
*** hongbin has quit IRC04:35
dkushwahaYanXing_an: tung_doan hi04:35
tbh_dkushwaha, meeting started?04:35
tung_doandkushwaha: no meeting, today?04:35
*** gongysh has joined #openstack-meeting04:35
YanXing_anwait a minute04:35
dkushwahatbh_: not yet04:36
gongysh#startmeeting tacker04:36
openstackMeeting started Wed Jul 12 04:36:32 2017 UTC and is due to finish in 60 minutes.  The chair is gongysh. Information about MeetBot at http://wiki.debian.org/MeetBot.04:36
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:36
*** openstack changes topic to " (Meeting topic: tacker)"04:36
openstackThe meeting name has been set to 'tacker'04:36
gongysh#topic roll call04:37
*** openstack changes topic to "roll call (Meeting topic: tacker)"04:37
dkushwahao/04:37
YanXing_ano/04:37
tbh_o/04:37
tung_doano/04:37
*** tbh__ has joined #openstack-meeting04:38
*** tbh_ has quit IRC04:38
*** tbh__ is now known as tbh_04:38
gongyshwelcome everyone04:39
gongysh#topic bp04:39
*** openstack changes topic to "bp (Meeting topic: tacker)"04:39
gongyshwhat is the progress for mistral action policy?04:39
gongyshdkushwaha, hi04:39
gongyshdo we have any progress?04:39
gongyshI haven't seen there is patch coming.04:40
*** thorst has joined #openstack-meeting04:40
dkushwahagongysh: I have pushed a wip patch for mistral re-factoring https://review.openstack.org/48275304:40
*** arnewiebalck_ has joined #openstack-meeting04:41
dkushwahagongysh: and will push patch over this04:41
*** pcaruana has joined #openstack-meeting04:41
gongyshdkushwaha, ok, that's fine.04:41
gongyshfix the patch as soon as possible please.04:42
dkushwahagongysh: sure, it seems multiple mistral related duplicate code, so needs cleanup04:42
tung_doanHi cores, please review/merge this patch in tacker-horizon. Currently, tacker-horizon cannot work: https://review.openstack.org/#/c/481959/04:42
*** ekcs has joined #openstack-meeting04:43
gongyshYanXing_an, do you have any progress on ns with vnffg?04:43
*** armstrong has quit IRC04:43
YanXing_anSorry for no updation on it04:43
*** rbudden has quit IRC04:44
YanXing_ani am on business after last IRC, fixing some urgent issues.04:44
*** trinaths has joined #openstack-meeting04:44
*** thorst has quit IRC04:45
dkushwahatung_doan: needs Django expert. :)04:45
gongyshtung_doan, https://review.openstack.org/#/c/434974/04:46
gongyshdo you have any code patch for this?04:46
tung_doandkushwaha: :)) just need your try04:46
*** hieulq has joined #openstack-meeting04:47
trinathso/04:47
tung_doangongysh: i am still coding locally. Possibility I will upload patch this week04:47
gongyshtung_doan, ok04:48
gongysh#topic coding patch04:48
*** openstack changes topic to "coding patch (Meeting topic: tacker)"04:48
trinathstung_doan: the horizon fix did not work for me04:48
trinathstung_doan: please revisit the dix04:48
trinaths*fix04:48
gongyshhttps://review.openstack.org/#/c/481959/04:48
tung_doangongysh: thanks. need your try as well04:48
gongyshit seems tung_doan  and trinaths have different experience on it.04:49
tung_doantrinaths: It worked ok for me. Another guy already confirmed that. Not sure about your issue04:49
trinathsgongysh: i have installed fresh devstack based single node setup. horizon went wrong from tacker.04:50
trinathstung_doan: okay. let me give a try today.04:50
*** unicell has joined #openstack-meeting04:50
tung_doantrinaths: thanks :)04:50
tung_doangongysh: My colleague will join with us from now on. Firstly, he will try to support us with vnffg-scaling feature. We also has plan to wrap this bp soon04:52
gongyshit seems gitreview hangs now.04:52
tung_doangongysh: YanXing_an: https://review.openstack.org/#/c/469975/04:53
*** trinaths1 has joined #openstack-meeting04:53
gongyshtung_doan, https://review.openstack.org/#/c/462690/04:54
gongyshit is ok if we will fix the tosca parser.04:54
gongyshpleas file a bug to remember it.04:54
YanXing_antung_doan, welcome to your colleague04:55
tung_doansure. i will file bug now :)04:56
*** coolsvap has joined #openstack-meeting04:56
tung_doanYanXing_an: thanks. :)04:56
phuoc_Nice to meet all of you04:57
gongyshtung_doan, I remember we have problem on scale beyond the number of heat group.04:57
*** trinaths has quit IRC04:57
tung_doangongysh: yep. it is about selective VDUs04:57
YanXing_anphuoc_, welcome04:57
dkushwahaphuoc_: welcome04:58
tung_doantbh_: said we will offload this to heat-trabslator04:58
*** pcaruana has quit IRC04:58
gongyshtung_doan,  can you file a bug about scaling beyond numbers?04:58
tung_doanYanXing_an: dkushwaha: yeeahh... :)04:58
phuoc_YangXing, Dkushwaha thank :)04:58
gongyshphuoc_, welcome.04:58
tbh_tung_doan: sorry I haven't worked on it yet04:59
phuoc_Gongysh thank :)04:59
*** trinaths has joined #openstack-meeting04:59
*** tobberydberg has joined #openstack-meeting04:59
gongyshtung_doan,  can you file a bug about scaling beyond numbers?04:59
*** diablo_rojo has joined #openstack-meeting05:00
tung_doangongysh: that seems to be up to heat-translator. I need to time to deeply look into this path.05:00
*** trinaths1 has quit IRC05:00
gongyshtung_doan, first file a bug so that we will not forget it.05:00
tung_doangongysh: sure.. i am filing this05:00
tung_doangongysh: we had another choice for that issue. Using senling could overcome this issue05:01
gongyshtung_doan,  if we cannot fix it, we will need to remove the heat option.05:01
gongyshsenlin's integration is too slow.05:02
*** makowals has joined #openstack-meeting05:02
gongyshwe have no one working on it. and that author does not join meeting either.05:02
tung_doangongysh: yep.. this patch: https://review.openstack.org/#/c/449471/1105:02
tung_doangongysh: in fact, this patch need the scaling fix in Tacker, therefore i hope we can launch my patch soon: https://review.openstack.org/#/c/462690/05:03
*** slaweq has joined #openstack-meeting05:05
dkushwahagongysh: i will ping author for the same05:05
tung_doandkushwaha: +105:05
gongyshtung_doan, give your tosca parser bug at that patch.05:05
*** slaweq has quit IRC05:05
tung_doangongysh: yes.. I will file that bug in tosca-parser and fix it by myself :)05:06
*** julim has quit IRC05:06
gongyshand reply my comment. I will review again.05:06
tung_doangongysh: got it05:06
*** julim has joined #openstack-meeting05:06
gongyshthese are from my side.05:07
gongyshdo you guys have any bug or codes to talk?05:08
YanXing_angongysh, i have no much time on vnffg of ns before 7.24 due to that unexpected issues, please knowing it05:08
gongyshYanXing_an, got it.05:09
gongysh#topic open discussion05:09
*** openstack changes topic to "open discussion (Meeting topic: tacker)"05:09
dkushwahaYanXing_an: http://paste.openstack.org/show/615099/05:09
dkushwahaYanXing_an: while creating vnf, getting this traces, any clue?05:10
YanXing_anthe tenant account is the one creating the vim?05:11
dkushwahayup, i have just prepared env with stack.sh and trying to create05:12
YanXing_anin devstack, the default vim is created in nfv_user account05:12
phuoc_YanXing, i got this issue too05:12
phuoc_when I i switch to nfv_user, i can't list any vim05:13
gongyshdkushwaha, phuoc_  use your own account to create a vim and to create the vnf with this vim.05:13
*** armax has quit IRC05:14
*** armax has joined #openstack-meeting05:14
gongyshsince CI passed, it seems you guys have some mis-usage.05:14
dkushwahagongysh: sure, i will try again, but actually I am using admin privilege so it should not be failed05:15
*** armax has quit IRC05:15
*** armax has joined #openstack-meeting05:15
*** armax has quit IRC05:16
gongyshopenstack summit topic  acceptance is close to deadline05:16
*** armax has joined #openstack-meeting05:16
gongyshso please do it quickly if you have topic to summit.05:16
YanXing_anthis limitation is mainly due to barbican, even admin privilege can not access other account's secrets by default policy.05:16
*** armax has quit IRC05:16
trinathsgongysh: we have 4 proposals for summit05:17
*** armax has joined #openstack-meeting05:17
gongyshtrinaths, you are proposal specialist.05:17
*** armax has quit IRC05:17
*** krtaylor has quit IRC05:17
*** armax has joined #openstack-meeting05:17
YanXing_antrinaths, great05:17
trinathsgongysh: :) we are all such specialist05:18
trinathshttps://etherpad.openstack.org/p/tacker_sydney_summit_proposals_201705:18
trinathsthe porposal page05:18
*** armax has quit IRC05:18
tung_doantrinaths: great job :)05:18
*** armax has joined #openstack-meeting05:18
gongyshanything else?05:18
*** armax has quit IRC05:19
dkushwahagongysh: PTG?05:19
trinathsplease add your proposals to that etherpad and we will submit them before the deadline05:19
YanXing_anwe can add all proposals in that etherpad05:19
*** armax has joined #openstack-meeting05:19
*** armax has quit IRC05:20
gongyshwhat is the codename for next openstack release?05:20
*** ekcs has quit IRC05:20
trinathsQueen05:20
dkushwahaQ05:20
gongyshhttps://etherpad.openstack.org/p/tacker-queen-grooming05:20
gongyshwe will have a virtual meeting05:20
trinathsnice05:21
*** baoli has joined #openstack-meeting05:22
gongyshand please keep up reviewing05:22
gongyshlets decide PTG time05:24
gongyshwho knows the date of community PTG?05:24
dkushwaha11-1505:25
dkushwahasept05:25
dkushwahai guess05:25
*** baoli has quit IRC05:27
YanXing_anyes. September 11-15th 2017, Denver05:27
gongyshThe second Project Teams Gathering (PTG) will be hosted in Denver, September 11-15, 201705:27
*** hieulq has quit IRC05:27
gongyshwe will do it at the same time.05:28
*** stevebaker has left #openstack-meeting05:28
gongyshok thanks everyone.05:29
gongyshplease keep up the efforts.05:29
gongysh#endmeeting05:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:29
openstackMeeting ended Wed Jul 12 05:29:18 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2017/tacker.2017-07-12-04.36.html05:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2017/tacker.2017-07-12-04.36.txt05:29
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2017/tacker.2017-07-12-04.36.log.html05:29
*** rcernin has joined #openstack-meeting05:33
*** YanXing_an has quit IRC05:34
*** arnewiebalck_ has quit IRC05:35
*** gcb has quit IRC05:37
*** janki has joined #openstack-meeting05:40
*** julim has quit IRC05:40
*** ykatabam has quit IRC05:41
*** julim has joined #openstack-meeting05:42
*** mahatic_ is now known as mahatic05:42
*** hieulq has joined #openstack-meeting05:45
*** ekcs has joined #openstack-meeting05:45
*** lpetrut has joined #openstack-meeting05:46
*** tung_doan has left #openstack-meeting05:48
*** gyee has quit IRC05:52
*** prateek has joined #openstack-meeting05:58
*** jprovazn has joined #openstack-meeting06:04
*** slaweq_ has joined #openstack-meeting06:06
*** phuoc_ has quit IRC06:08
*** andreas-f has quit IRC06:08
*** andreas-f has joined #openstack-meeting06:10
*** slaweq_ has quit IRC06:12
*** markstur has quit IRC06:23
*** markstur has joined #openstack-meeting06:23
*** markstur has quit IRC06:28
*** gongysh has quit IRC06:34
*** marios has joined #openstack-meeting06:35
*** dkushwaha has quit IRC06:35
*** dkushwaha has joined #openstack-meeting06:35
*** smcginnis has quit IRC06:39
*** dkushwaha has left #openstack-meeting06:40
*** lpetrut has quit IRC06:41
*** rledisez has joined #openstack-meeting06:41
*** thorst has joined #openstack-meeting06:41
*** spn has quit IRC06:43
*** smcginnis has joined #openstack-meeting06:43
*** andreas_s has joined #openstack-meeting06:44
*** d0ugal has quit IRC06:44
*** thorst has quit IRC06:46
*** belmoreira has joined #openstack-meeting06:47
*** spn has joined #openstack-meeting06:48
*** ekcs has quit IRC06:48
*** m_kazuhiro has joined #openstack-meeting06:51
*** aloga has quit IRC06:55
*** zhurong has quit IRC06:55
*** patchbot has joined #openstack-meeting06:58
*** acoles has joined #openstack-meeting06:58
*** trinaths is now known as trinaths_lunch06:59
notmyname#startmeeting swift07:00
openstackMeeting started Wed Jul 12 07:00:06 2017 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.07:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:00
*** openstack changes topic to " (Meeting topic: swift)"07:00
openstackThe meeting name has been set to 'swift'07:00
notmynamewho's here for the 0700 swift team meeting?07:00
mahatico/07:00
*** kota_ has joined #openstack-meeting07:00
*** jeffli has joined #openstack-meeting07:00
notmynamemahatic: I know there's more than just you here right now ;-)07:01
kota_hello07:01
mathiasbo/07:01
mahaticnotmyname: lol, I'm waiting for other hellos too07:01
rledisezo/07:01
acoleshello07:01
*** vishnoianil has quit IRC07:01
m_kazuhiroo/07:01
jefflio/07:01
notmynameI wonder if christian will be here. doesn't seem like he's on irc07:01
*** diablo_rojo has quit IRC07:02
notmynamewelcome, everyone07:02
notmynamesince I'm chairing both the 0700 and the 2100 meeting today, we've got the same agenda for both :-)07:03
notmyname#link https://wiki.openstack.org/wiki/Meetings/Swift07:03
notmyname#topic Denver PTG07:03
*** openstack changes topic to "Denver PTG (Meeting topic: swift)"07:03
notmynamereminder that the PTG is coming up07:03
notmynameif you are able to attend, please make sure you are registered and have hotel room (do it soon. do it today)07:04
notmynamewe're collecting topics at...07:04
notmyname#link https://etherpad.openstack.org/p/swift-ptg-queens07:04
notmynameso please add your ideas/curent work/hopes/dreams/fears/thoughts to it07:05
*** cschwede has joined #openstack-meeting07:05
notmynamehi cschwede!!07:05
cschwedeHi notmyname!07:05
notmynamecschwede: we were just starting to talk about the ptg07:05
notmynameso seeing as everyone here except me lives *outside* the US and the ptg is inside the US, are there any particular things I can help with? anyone know already they won't be able to go?07:06
*** slaweq_ has joined #openstack-meeting07:07
notmynameI take the silence to mean that I'll see you all in person in denver at the ptg :-)07:07
*** unicell has quit IRC07:08
mahaticI won't be able to go07:08
psachino/07:08
notmynamemahatic: I'm sorry to hear that07:08
kota_no problem, right now from Japan/my company :-)07:08
acolesmahatic: :(07:08
kota_mahatic: :(07:08
notmynameif anyone is choosing either the PTG or the summit in sydney, please choose the PTG. this definitely includes swift ops people07:08
notmynameplease keep looking at the etherpad and add stuff as you have ideas07:10
notmyname#topic bug triage follow-up07:10
*** openstack changes topic to "bug triage follow-up (Meeting topic: swift)"07:10
notmynamecschwede: I'm putting you on the spot a little bit here :-)07:10
cschwedenotmyname: heh, thx :)07:11
notmynameat the last 0700 meeting you had some things you said you'd follow up on07:11
*** unicell has joined #openstack-meeting07:11
notmynamecschwede: "i'll have a look at Seans work, and on automating LP in general and will follow up in next weeks meeting07:11
notmynamecschwede to start etherpad for bug tag ideas, investigate automation of LP bug state changes and report in next meeting"07:11
cschwedeyes, so i played a bit with the tools written by Sean Dague (https://github.com/sdague/nova-bug-tools). These are pretty cool already, and we could use them IMO to automate quite a bit07:11
*** tesseract has joined #openstack-meeting07:11
notmynamewhat kind of things will it automate?07:12
*** andreas-f has quit IRC07:12
*** slaweq_ has quit IRC07:12
notmyname#link https://github.com/sdague/nova-bug-tools#existing-tools07:12
cschwedefor example, closing very old bugs without any changes in the last XXX days (would be my first choice to execute) or cleanup in progress bugs that got a fix07:12
notmynamecool, those would both be good07:13
cschwedealso link missing reviews to bugs (ie where the automation in Gerrit failed because it was not the first patchset)07:13
notmynamehave you done any dry-run of those yet to see how many bugs they would impact?07:13
cschwedeall of this needs some consensus, ie what do we want to close for example07:14
*** aloga has joined #openstack-meeting07:14
cschwedeyes, it's a large number ;)07:14
kota_sounds nice, it has dry-run07:14
cschwedeif one uses the default of 6 months, it would be 292 closed bugs07:15
notmynameof 43407:15
cschwedeyes :)07:15
notmynamedid you check 12 months?07:15
cschwedebut i think 6 months might be to hard07:15
acolescschwede: +1 for this "link missing reviews to bugs "07:15
cschwede12 months / 365 days would be 173 bugs07:16
notmynameI agree with acoles. linking bugs to gerrit would be fantastic07:17
cschwedei can paste the "to-be-closed" bugs to an etherpad, so we can do some spot checks before executing the script07:17
notmynamesince we're not in person, here's my off-the-top-of-my-head thoughts...07:18
acolesre closing old bugs - presumably with some other conditions (like status != confirmed, importance < high)? our two highest importance bugs right now are >12 months old07:19
notmynamegreat! close some old bugs. make the old list tractable. oh, but what if the old bugs are valid. we should check them. but if we check them, why do we need a script...07:19
cschwede"Could not submit your paste because your paste contains spam."07:19
cschwedethanks etherpad...07:19
notmynamehave you considered not pasting spam?07:19
notmyname;-)_07:19
*** hieulq has quit IRC07:19
mahatic:D07:20
cschwede#link http://paste.openstack.org/show/615112/07:20
cschwedei can add some checks for != confirmed and low importance and repost the list of to-be-closed bugs07:21
acoleswhat's wrong with spam paste? it sounds quite tasty ;)07:21
mahaticI'm not sure if right away closing bugs which has importance<high is a good thing to do. We still want "medium" priority bugs to get some attention I suppose07:21
cschwedenotmyname: that's a risk, but i'd say it's a minor one. if there is no update within 12 months, not yet confirmed and low prio it should be safe to close. can add a message like "reopen if you think this is wrong" or sth like that07:22
*** rbartal has joined #openstack-meeting07:22
acolesmahatic: oh, I was not suggesting <high as an appropriate condition, I was just suggesting conditions. sorry if i confused.07:23
notmynamethe option is close or not close?07:23
notmynamemaybe a half-measure would be to set it to needs info?07:23
*** edmondsw has joined #openstack-meeting07:24
cschwedeyeah, i think i can easily modify the script to do that07:24
acoleswe should not close bugs marked as wish-list, right?07:24
cschwedetrue07:24
notmynamehmm... yeah, spot checking just the titles of them, it's obvious that some are done, some are still important, and some are going to take some time to actually figure out07:25
notmynameeg https://bugs.launchpad.net/swift/+bug/1559347 is likely done (based on the title). ie we do concurrent reads now07:25
openstackLaunchpad bug 1559347 in OpenStack Object Storage (swift) " Add concurrent reads option to proxy" [Undecided,New]07:25
cschwedelooks like many really old bugs are in state new07:25
cschwedeso it might help to add the reviews first07:26
mahaticacoles: np! I read the follow on convo a bit later, looks like that's not what we're gonna d07:26
mahaticdo*07:26
notmynamecschwede: yeah, I definitely think linking bugs with gerrit would be the first thing to do07:26
*** ykatabam has joined #openstack-meeting07:26
cschwedewhat we could also do is to create an etherpad with bugs in NEW, and a bunch of volunteers grab parts of that list. so everyone tackles 10 or so bugs, and we avoid duplicate work07:27
notmynamedoes anyone else feel like doing the automated process to a huge number of bugs is somehow wrong? or giving up?07:28
notmynameI completely understand that there are hundreds of bugs that haven't been looked at in over six months07:28
*** edmondsw has quit IRC07:29
cschwedelet's do the following (if you agree):07:29
cschwede1. search for existing gerrit reviews and link them (ie bug NEW -> some other state)07:29
cschwede2. run tool to close fixed bugs (merged gerrit reviews), but as a dry-run -> save list07:29
cschwede3. dry-run close-bug script with low prio and still in new and > 365 days; save that list for review07:30
acolesnotmyname: I think it has already been useful if only to present us with a different view of the status quo. But I am nervous about a mass cull.07:30
cschwede4. discuss again if it makes sense to close that list from 3.07:30
*** alexchadin has joined #openstack-meeting07:30
*** pcaruana has joined #openstack-meeting07:31
notmynamecschwede: when do we close the list from step 2?07:31
cschwedeafter we reviewed it (should be fine, but at least looking at the titles could help to spot any issues)07:32
*** zhurong has joined #openstack-meeting07:32
*** aarefiev_afk is now known as aarefiev07:32
notmynamewhat are everyone else's thoughts? acoles, mahatic, m_kazuhiro, kota_, rledisez, mathiasb?07:32
notmynameoh, jeffli (sorry)07:33
acolescschwede: on point 3, low prio means precisely Importance=Low?? so Wishlist is not included?07:33
*** fzdarsky_ is now known as fzdarsky07:34
mahaticI think it's good. Agree with acoles that it definitely presents a different (better IMO) view of status quo. And so long as we initially take a look at the list before running the script to close, it seems quite helpful07:34
cschwedeacoles: we can exclude any bugs with tags (not only wishlist, but also low-hanging-fruit etc)07:34
*** unicell has quit IRC07:34
cschwedebtw, there are 18 bugs mostly in new that can be easily linked with existing gerrit reviews07:34
mathiasbI agree with mahatic and acoles07:35
*** hieulq has joined #openstack-meeting07:35
kota_on step 1, the list for bugs we're looking for the gerrit patches is the paste above?07:35
*** radez has quit IRC07:35
kota_http://paste.openstack.org/show/615112/ i mean07:35
cschwedekota_: no, that's the list with bugs without any update in the last 6 months07:35
kota_i see07:35
acolesstep 1 seems like an obvious win07:36
kota_so we may need the list for the bugs with *new* status07:36
kota_just asking to LP, maybe :P07:36
acolesstep 2. I would hope is a short list (I had always thought that released fixes closed bugs)07:36
cschwedekota_: i can do that with the tools07:37
cschwedeacoles: only if the bug was linked on the first review07:37
kota_https://bugs.launchpad.net/swift/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field07:37
kota_.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search07:37
kota_oops07:37
kota_the link looks broken07:38
notmynamegotta love gerrit urls ;-)07:38
notmynameoh, those are launchpad07:38
kota_https://goo.gl/X4f44b07:38
acolescschwede: yeah, I knew that first review linked to launchpad, but somehow I had hoped that on merge there was another cross-check. But IDK for sure07:38
notmynamecrazy idea: get openstack community to use tools with reasonable, pastable URLs ;-)07:38
cschwedeacoles: there isn't :/07:38
kota_notmyname: yeah, searching the bug reports with NEW status07:38
acolescschwede: in which case +100 for step 2 :)07:39
*** claudiub has joined #openstack-meeting07:39
notmynamecschwede: I think your plan sounds great07:39
notmynamethere's clearly some details (eg acoles is wise to bring up the specific levels instead of <)07:39
notmynamebut I think we should start working through it07:40
cschwedelet me do the following: i dry-run all the scripts, save the output and create an etherpad with task that could be done and the affected bugs07:40
notmynamethat sounds great. thanks07:40
mahaticcschwede: +1, thank you07:40
*** ionutbalutoiu has quit IRC07:40
*** ionutbalutoiu has joined #openstack-meeting07:40
notmynamecschwede: if you have a chance to do that today, I'll include the links in teh 2100 meeting. if not, that's ok, but I'll go over the general plan then, too07:41
mattoliverauOps, sorry forgot about meeting, was stuck at post office trying pick up the power pack that they said I wasn't home to deliver, when I was in fact at home.07:41
notmynamemattoliverau: welcome07:41
cschwedenotmyname: i'll do that this morning, will send you a mail afterwards07:41
notmynameok07:41
*** pcaruana has quit IRC07:41
notmynameok, two other topics, I think we can get through07:41
notmyname#topic docs migrations07:41
*** openstack changes topic to "docs migrations (Meeting topic: swift)"07:41
notmynamethis is mostly an FYI topic07:42
acolesThere are many reasons for how we got to this situation but one of them is that I sometimes do not feel confident to *unilaterally* mark a bug as Invalid or Wishlist. I wish there was a voting scheme on launchpad so we could form consensus.07:42
notmynameacoles: I can definitely sympathize with that07:42
acolesnotmyname: oops, we moved on, docs...07:43
notmynamethe docs that the docs team has been managing are moving into each respective project07:43
notmynamethis means that we're taking on a lot more docs in our repo07:43
notmynamewhile this set of work was prompted by bad circumstances (ie layoffs), the end result is very very good07:44
notmynameI've been working on the migration, and there will be a few more patches for the import07:44
notmynameso here's the high-level view07:44
notmynamefirst, there will be an import. there's been some patches already, and there will be a few more07:44
*** kristian__ has joined #openstack-meeting07:44
*** amotoki_away is now known as amotoki07:45
notmynamethe import will result in a lot of duplication and awareness of stale docs. we can update and refactor *after* the import07:45
*** kristian__ has quit IRC07:45
*** pcaruana has joined #openstack-meeting07:45
notmynamealso, in conjunction with the docs import, there is a general restructuring of the docs in each project07:45
notmynameyou know how we currently have several docs trees, several docs jobs, etc?07:46
notmynameall that's going away07:46
notmynamewe will have one docs directory. one conf.py07:46
*** arnewiebalck_ has joined #openstack-meeting07:46
mattoliverau\o/ nice, I docs root to rule them all07:46
notmynameand all the stuff that's currently in it (ie the "developer docs") will be moved, along with the imports from the docs team07:46
notmynamethis does mean that a lot of existing pages will move. this means links will break07:47
notmynamethat's sad07:47
notmynamebut we're doing it anyway07:47
notmynamebecause the end result is really really good07:47
notmynamewe (ie us here, the swift team) will have one place where we manage docs07:48
notmynameif we want to add something, we can07:48
mahaticnice07:48
*** phil_ has joined #openstack-meeting07:48
notmynameif we want to delete something, we can07:48
notmynameif we want to do whatever, we can07:48
mattoliverauAlso having it all in our repo means I can submit a patch to change everything to the queen's English, and acoles can +2 ;p07:48
acolesmattoliverau: soooper07:48
*** phil_ is now known as Guest7577907:48
mattoliverauOr would that be a translation :p07:48
*** toscalix has joined #openstack-meeting07:48
acoleslol07:48
mahaticlol @translation07:49
notmynameit also means that all the docs can be updates with a patch that actually implements stuff!07:49
mattoliverauYeah that's a big +107:49
mahaticyay07:49
notmynameall the existing high-level references (eg api guide, install guide, etc) will link into our singular docs tree07:49
notmynamewhich also means we will have one and only one docs job07:49
notmyname*gate job07:50
notmynameyou build docs. that's it. don't have to ask "which docs?". just docs. done07:50
acolesnotmyname: will it be possible to build subsets of docs (for speed, when working on a patch)?07:50
notmynameno07:50
notmynameonly one job07:51
notmynamewell, maybe you could run sphinx-build locally to do a subset. if you learn how, you can teach us all :-)07:51
acolesnerd swipe alert07:51
notmynamebut no that's not part of the design of the end goal07:51
*** tobberydberg has quit IRC07:51
*** tobberydberg has joined #openstack-meeting07:52
notmynameany quick questions about the docs stuff? I also want to briefly cover upcoming releases07:52
notmynameok07:52
notmyname#topic upcoming releases07:53
*** openstack changes topic to "upcoming releases (Meeting topic: swift)"07:53
notmynameI updated the priority reviews page07:53
notmyname#link https://wiki.openstack.org/wiki/Swift/PriorityReviews07:53
notmynameto have sections for the upcoming releases07:53
notmynameideally, I'd like to tag releases for both swift and swiftclient next week07:53
notmynameI expect that swiftclient will happen before swift itself. I want the two patches mentioned there, though07:54
notmynamepatch 449771 could use some eyes07:54
patchbothttps://review.openstack.org/#/c/449771/ - python-swiftclient - Buffer reads from disk07:54
notmynamethe other (stream stdin) is waiting on the author for a foudn bug07:54
notmynamewhen those land, I'll do the release07:54
notmynamefor swift, it's a little more ... what's the word? "fluid"07:55
notmynameie the list is longer, and some of the listed things haven't even been started07:55
notmynamethe first 2 patches mentioned are important07:56
notmynamepatch 448480 needs reviews07:56
patchbothttps://review.openstack.org/#/c/448480/ - swift - DB replicator cleanup07:56
*** tobberydberg has quit IRC07:56
notmynameclay is working on patch 478416 and should have something later this week to review (spoiler: at least a 7x improvement in the ec reconstructor cycle time)07:56
patchbothttps://review.openstack.org/#/c/478416/ - swift - WIP: Add multiple worker processes strategy to rec...07:56
mattoliverauNice!07:57
mattoliverauThat's the one we discussed in Boston right?07:57
notmynamethe 3 high priority bugs listed aren't blockers, but they are high priority and should be addressed asap.07:57
acolesmattoliverau: I believe so07:57
mattoliverauWell discussed what we could do and was how to implement Romain's thing07:57
notmynamemattoliverau: yes. multiprocess reconstructor. there's more that we discussed, but this is the first step07:57
mattoliverauCool, I look forward to that!07:58
notmynameso instead of going down the list of these to ask for reviews (or possibly patch authors!), there's the list. I trust you all to do what you can :-)07:58
notmynamealso, the list may be incomplete07:58
notmynameif it is, please update the wiki page and let me know. or let me know and I'll update it07:59
notmyname(while I don't expect there to be another meeting in here at 0800utc, I do want to respect your time)07:59
mattoliverauAlso I was involved in reviewing the earlier db replicator critical bug so will find time to look at the follow-up (or cleanup) tho it seems I'm a co author but I'll look anyway :p08:00
notmynameall this sound ok for upcoming releases? any questions?08:00
notmynamemattoliverau: thanks08:00
mattoliverauYup08:00
*** kristian__ has joined #openstack-meeting08:00
acolesnotmyname: sounds good08:00
mahaticsounds good08:00
kota_+108:00
notmynamekota_: rledisez: mahatic: mathiasb: jeffli: m_kazuhiro: cschwede: all good?08:00
m_kazuhiro+108:01
cschwede+108:01
notmynamegreat, thanks08:01
mahaticthank you for staying up late and leading the meeting!08:01
mattoliverau+108:01
notmynameI'm am really happy you're all working on swift. thank you for your work, and I'm looking forward to seeing you in denver :-)08:01
jeffli+108:01
notmynamemahatic: I just missed you all :-)08:01
acolesnotmyname: sleep well :)08:02
notmynamenow! bedtime for me! ;-)08:02
notmyname#endmeeting08:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:02
openstackMeeting ended Wed Jul 12 08:02:08 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:02
jefflinotmyname: good night08:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2017/swift.2017-07-12-07.00.html08:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2017/swift.2017-07-12-07.00.txt08:02
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2017/swift.2017-07-12-07.00.log.html08:02
*** gouthamr has joined #openstack-meeting08:02
*** kota_ has left #openstack-meeting08:02
*** rbartal has quit IRC08:03
*** patchbot has left #openstack-meeting08:03
*** rossella_s has joined #openstack-meeting08:04
*** acoles has left #openstack-meeting08:05
*** rbartal has joined #openstack-meeting08:06
*** m_kazuhiro has quit IRC08:07
*** slaweq_ has joined #openstack-meeting08:08
*** wxy- has joined #openstack-meeting08:13
*** slaweq_ has quit IRC08:13
*** trinaths_lunch is now known as trinaths08:13
*** tobberydberg has joined #openstack-meeting08:15
*** ralonsoh has joined #openstack-meeting08:17
*** makowals_ has joined #openstack-meeting08:18
*** dmacpher has quit IRC08:19
*** makowals has quit IRC08:20
*** gouthamr has quit IRC08:21
*** makowals has joined #openstack-meeting08:22
*** wxy- has quit IRC08:24
*** makowals_ has quit IRC08:24
*** kristian__ has quit IRC08:26
*** makowals has quit IRC08:30
*** dbecker has joined #openstack-meeting08:30
*** arnewiebalck_ has quit IRC08:32
*** pcaruana has quit IRC08:33
*** julim has quit IRC08:37
*** julim has joined #openstack-meeting08:38
*** makowals has joined #openstack-meeting08:40
*** makowals has quit IRC08:41
*** thorst has joined #openstack-meeting08:42
*** makowals has joined #openstack-meeting08:44
*** dklyle has joined #openstack-meeting08:45
*** david-lyle has quit IRC08:45
*** d0ugal has joined #openstack-meeting08:45
*** pcaruana has joined #openstack-meeting08:46
*** tobberydberg has quit IRC08:46
*** Douhet has quit IRC08:46
*** tobberydberg has joined #openstack-meeting08:46
*** thorst has quit IRC08:47
*** tbh_ has quit IRC08:48
*** electrofelix has joined #openstack-meeting08:48
*** jbadiapa_ has quit IRC08:50
*** jbadiapa_ has joined #openstack-meeting08:52
*** d0ugal has quit IRC08:54
*** d0ugal has joined #openstack-meeting08:55
*** d0ugal has quit IRC08:55
*** d0ugal has joined #openstack-meeting08:55
*** makowals has quit IRC08:58
*** makowals has joined #openstack-meeting09:04
*** Douhet has joined #openstack-meeting09:05
*** iyamahat has joined #openstack-meeting09:06
*** slaweq_ has joined #openstack-meeting09:09
*** claudiub|2 has joined #openstack-meeting09:11
*** edmondsw has joined #openstack-meeting09:12
*** claudiub has quit IRC09:14
*** slaweq_ has quit IRC09:14
*** iyamahat has quit IRC09:15
*** claudiub has joined #openstack-meeting09:15
*** edmondsw has quit IRC09:16
*** claudiub|2 has quit IRC09:18
*** beekhof_mb has joined #openstack-meeting09:20
*** lpetrut has joined #openstack-meeting09:27
*** e0ne has joined #openstack-meeting09:30
*** wanghao has quit IRC09:32
*** pcaruana has quit IRC09:32
*** askb has quit IRC09:32
*** pcaruana has joined #openstack-meeting09:32
*** yamahata has quit IRC09:34
*** sambetts|afk is now known as sambetts09:40
*** thorst has joined #openstack-meeting09:43
*** beekhof_mb has quit IRC09:44
*** thorst has quit IRC09:47
*** kristian__ has joined #openstack-meeting09:49
*** caowei has quit IRC09:53
*** kristian__ has left #openstack-meeting09:54
*** beekhof_mb has joined #openstack-meeting09:55
*** arnewiebalck_ has joined #openstack-meeting10:00
*** elynn_ has quit IRC10:01
*** Alex_Staf has joined #openstack-meeting10:07
*** epico has quit IRC10:08
*** slaweq_ has joined #openstack-meeting10:10
*** slaweq_ has quit IRC10:14
*** slaweq_ has joined #openstack-meeting10:14
*** slaweq_ has quit IRC10:14
*** hieulq has quit IRC10:16
*** sridharg has quit IRC10:21
*** rossella_s has quit IRC10:26
*** dklyle has quit IRC10:28
*** rossella_s has joined #openstack-meeting10:28
*** david-lyle has joined #openstack-meeting10:28
*** alexchadin has quit IRC10:28
*** sridharg has joined #openstack-meeting10:30
*** beekhof_mb has quit IRC10:33
*** arnewiebalck_ has quit IRC10:34
*** rossella_s has quit IRC10:36
*** zhurong has quit IRC10:41
*** rossella_s has joined #openstack-meeting10:48
*** d0ugal has quit IRC10:49
*** hieulq has joined #openstack-meeting11:04
*** jkilpatr has quit IRC11:06
*** beekhof_mb has joined #openstack-meeting11:08
*** hieulq has quit IRC11:08
*** markvoelker has quit IRC11:09
*** julim has quit IRC11:10
*** markvoelker has joined #openstack-meeting11:10
*** markvoelker has quit IRC11:14
*** slaweq_ has joined #openstack-meeting11:15
*** slaweq_ has quit IRC11:20
*** samP has quit IRC11:25
jeffliexit11:32
*** jeffli has quit IRC11:32
*** thorst has joined #openstack-meeting11:38
*** jkilpatr has joined #openstack-meeting11:43
*** hieulq has joined #openstack-meeting11:44
*** wxy- has joined #openstack-meeting11:51
*** efried_zzz is now known as efried11:52
*** rledisez has left #openstack-meeting11:54
*** markvoelker has joined #openstack-meeting11:55
*** pradk has joined #openstack-meeting11:55
*** rbudden has joined #openstack-meeting11:55
*** litao__ has quit IRC11:56
*** RonghUI has quit IRC11:57
*** RonghUI has joined #openstack-meeting11:58
*** alexchadin has joined #openstack-meeting12:00
*** rbowen has joined #openstack-meeting12:01
*** beekhof_mb has quit IRC12:03
*** oidgar has joined #openstack-meeting12:03
*** raildo has joined #openstack-meeting12:03
*** dprince has joined #openstack-meeting12:05
*** sridharg has quit IRC12:07
*** jtomasek_ has joined #openstack-meeting12:07
*** pchavva has joined #openstack-meeting12:13
*** slaweq_ has joined #openstack-meeting12:16
*** slaweq_ has quit IRC12:21
*** jamesden_ has joined #openstack-meeting12:21
*** krtaylor has joined #openstack-meeting12:23
*** jamesdenton has quit IRC12:24
*** sridharg has joined #openstack-meeting12:24
*** jtomasek_ has quit IRC12:25
*** ykatabam has quit IRC12:27
*** kbyrne has quit IRC12:28
*** wxy- has quit IRC12:29
*** kbyrne has joined #openstack-meeting12:30
*** julim has joined #openstack-meeting12:31
*** imcsk8 has quit IRC12:37
*** imcsk8 has joined #openstack-meeting12:37
*** kbyrne has quit IRC12:38
*** kbyrne has joined #openstack-meeting12:39
*** kamal____ has joined #openstack-meeting12:40
*** zhenguo_ has joined #openstack-meeting12:40
*** soren_ has joined #openstack-meeting12:40
*** persia__ has joined #openstack-meeting12:40
*** sballe__ has joined #openstack-meeting12:40
*** hrybacki_ has joined #openstack-meeting12:40
*** fmccrthy_ has joined #openstack-meeting12:40
*** snuffkin has quit IRC12:40
*** szaher has quit IRC12:40
*** __huzhj_ has joined #openstack-meeting12:40
*** zerick has quit IRC12:41
*** efried_ has joined #openstack-meeting12:41
*** yamamoto has quit IRC12:41
*** tbarron_ has joined #openstack-meeting12:41
*** fmccrthy has quit IRC12:41
*** soren has quit IRC12:41
*** DinaBelova has quit IRC12:41
*** rfolco has quit IRC12:41
*** vipul has quit IRC12:41
*** hrybacki has quit IRC12:41
*** zhenguo has quit IRC12:41
*** kamal___ has quit IRC12:41
*** sballe_ has quit IRC12:41
*** persia has quit IRC12:41
*** __huzhj has quit IRC12:41
*** dprince has quit IRC12:41
*** efried has quit IRC12:41
*** galstrom_zzz has quit IRC12:41
*** zaneb has quit IRC12:41
*** numans has quit IRC12:41
*** eglute_s has quit IRC12:41
*** tbarron has quit IRC12:41
*** loquacities has quit IRC12:41
*** melwitt has quit IRC12:41
*** rhagarty has quit IRC12:41
*** fmccrthy_ is now known as fmccrthy12:41
*** zbitter has joined #openstack-meeting12:41
*** __huzhj_ is now known as __huzhj12:41
*** kamal____ is now known as kamal___12:41
*** hrybacki_ is now known as hrybacki12:41
*** soren_ is now known as soren12:41
*** zhenguo_ is now known as zhenguo12:41
*** sballe__ is now known as sballe_12:41
*** zerick has joined #openstack-meeting12:41
*** melwitt has joined #openstack-meeting12:41
*** vipul has joined #openstack-meeting12:41
*** mrunge has quit IRC12:41
*** tbarron_ is now known as tbarron12:41
*** numans has joined #openstack-meeting12:41
*** melwitt is now known as Guest8620812:41
*** eglute has joined #openstack-meeting12:42
*** galstrom_zzz has joined #openstack-meeting12:42
*** mrunge has joined #openstack-meeting12:42
*** DinaBelova has joined #openstack-meeting12:42
*** rfolco has joined #openstack-meeting12:42
*** rhagarty has joined #openstack-meeting12:42
*** loquacities has joined #openstack-meeting12:43
*** notmyname has quit IRC12:44
*** kbyrne has quit IRC12:44
*** szaher has joined #openstack-meeting12:44
*** dgonzalez has quit IRC12:44
*** snuffkin has joined #openstack-meeting12:45
*** kbyrne has joined #openstack-meeting12:46
*** dgonzalez has joined #openstack-meeting12:46
*** notmyname has joined #openstack-meeting12:47
*** dprince has joined #openstack-meeting12:47
*** manikanta_tadi has quit IRC12:47
*** eharney has joined #openstack-meeting12:47
*** edmondsw has joined #openstack-meeting12:50
*** donghao has joined #openstack-meeting12:51
*** edmondsw_ has joined #openstack-meeting12:51
*** edmondsw has quit IRC12:52
*** jaypipes has joined #openstack-meeting12:53
*** julim has quit IRC12:56
*** d0ugal has joined #openstack-meeting12:56
*** ralonsoh has quit IRC12:58
*** ralonsoh_ has joined #openstack-meeting12:58
*** sridharg has quit IRC12:59
*** ykatabam has joined #openstack-meeting12:59
*** sridharg has joined #openstack-meeting13:00
*** ralonsoh_ is now known as ralonsoh13:00
*** hejiawei has quit IRC13:02
*** sridharg has quit IRC13:02
*** oidgar has quit IRC13:04
*** Julien-zte has joined #openstack-meeting13:05
*** yamamoto has joined #openstack-meeting13:08
*** yamamoto has quit IRC13:13
*** zhurong has joined #openstack-meeting13:14
*** efried_ is now known as efried13:14
*** kylek3h has joined #openstack-meeting13:15
*** slaweq_ has joined #openstack-meeting13:17
*** tobberyd_ has joined #openstack-meeting13:18
*** d0ugal has quit IRC13:19
*** oidgar has joined #openstack-meeting13:20
*** tobberydberg has quit IRC13:21
*** trinaths has left #openstack-meeting13:21
*** slaweq_ has quit IRC13:22
*** ykatabam has quit IRC13:22
*** rossella_s has quit IRC13:23
*** baoli has joined #openstack-meeting13:28
*** lakerzhou has joined #openstack-meeting13:28
*** bknudson has joined #openstack-meeting13:29
*** oidgar has quit IRC13:32
*** frickler has quit IRC13:33
*** wxy- has joined #openstack-meeting13:34
*** lakerzhou has left #openstack-meeting13:34
*** bobh has joined #openstack-meeting13:37
*** rossella_s has joined #openstack-meeting13:37
*** armax has joined #openstack-meeting13:39
*** frickler has joined #openstack-meeting13:41
*** oidgar has joined #openstack-meeting13:45
*** coolsvap has quit IRC13:45
*** mriedem has joined #openstack-meeting13:46
*** yamamoto has joined #openstack-meeting13:51
*** Fdaisuke has joined #openstack-meeting13:51
*** hosanai has joined #openstack-meeting13:54
*** xyang1 has joined #openstack-meeting13:56
*** frickler has quit IRC13:57
*** koji has joined #openstack-meeting13:58
*** arturb_ has joined #openstack-meeting13:59
*** rhochmuth has joined #openstack-meeting13:59
*** kornica has joined #openstack-meeting13:59
*** galstrom_zzz is now known as galstrom14:00
*** witek has joined #openstack-meeting14:00
rhochmuth#startmeeting monasca14:01
openstackMeeting started Wed Jul 12 14:01:07 2017 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: monasca)"14:01
openstackThe meeting name has been set to 'monasca'14:01
*** dbecker has quit IRC14:01
kornicao/14:01
rhochmutho/14:01
arturb_o/14:01
kojio/14:01
witekhello14:01
kornicafujitsu's power :D14:01
Fdaisukeo/14:01
hosanaio/14:01
kornicaoh...not entirely ?14:02
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda14:02
rhochmuthhi everyone14:02
*** xiaofandh12 has joined #openstack-meeting14:02
rhochmuthunofrtunately, i'm going to have to drop off shortly14:02
*** dbecker has joined #openstack-meeting14:02
*** janki has quit IRC14:03
*** frickler has joined #openstack-meeting14:03
rhochmuth#topic Monasca fails to meet Pike release goals14:03
*** openstack changes topic to "Monasca fails to meet Pike release goals (Meeting topic: monasca)"14:03
*** cdub has joined #openstack-meeting14:03
rhochmuthhttps://governance.openstack.org/tc/goals/pike/index.html14:03
kornicaok, I can go through this I guess14:04
rhochmuthso, this sounds like a but of work14:04
*** gcb has joined #openstack-meeting14:04
kornicarecently I managed to make monasca-notificiation14:04
rhochmuththx kornica14:04
kornicaso apart from api (which is a real monster...) and agent (for which we need to agree on just one thing)14:04
kornicaeverything is I guess green14:04
kornicafor notification and transform we need to make gates green14:05
*** awaugama has joined #openstack-meeting14:05
*** donghao has quit IRC14:05
kornicaand there's also idea from monasca-transform guys to run tempests under Py314:05
kornicabut that requires having all APIs Py3 compatible14:05
kornicawhich is a case only for log-api14:05
rhochmuthi had started work on the api, and agree it was more complicated than i originally thought14:05
rhochmuthi believe others had looked at this too14:05
*** hongbin has joined #openstack-meeting14:06
kornicaI've tried carrying on in this change > https://review.openstack.org/#/c/349195/14:06
kornicabut despite all the eforts everytyhing keeps going south around expressions and sqlalachemy14:06
kornicaparts14:06
kornicanot to mention that green Py27 does mean all is as it was...tempest gate is failing14:07
*** haruki has joined #openstack-meeting14:07
kornicaso, unless we get more people into this, I strongly doubt api will meet the goal14:07
witekthere is also monasca-ui which still doesn't has python 3 support14:07
kornicaah, right14:07
kornicathat to14:07
kornicathx14:07
witekwe have a story for that:14:08
witekhttps://storyboard.openstack.org/#!/story/200097514:08
kornicathx witek14:08
kornicatotally forgot about that14:08
witekso, it would be great to get some hands on ui and api, right?14:10
witekand review notification14:10
kornicafrom my POV, yeah, +114:11
*** rbrndt has joined #openstack-meeting14:11
rhochmuth+114:11
*** tobberyd_ has quit IRC14:12
kornicawe don't have that much of menpower (or manpower :/) to keep all covered :(...for api it was just me and some of my free time (same as for other components I took care of) but other stuff comes up and might be that this api won't reach py314:12
kornicais there someone from HPE that could sit to this maybe ? maybe stratch from scratch, I don't know :/14:13
*** tobberydberg has joined #openstack-meeting14:14
rhochmuthi'm not sure there is14:14
rhochmuthi'm wondering about the suse folks14:14
rhochmuthi can check with them14:14
rhochmuthformer hpe folks14:15
rhochmuthwhile there are hpe folks still working on monasca14:15
*** rmascena has joined #openstack-meeting14:16
rhochmuththe problem is getting resources on the upstream related issues14:16
rhochmuthlike CI14:16
*** makowals has quit IRC14:16
*** arxcruz has quit IRC14:17
rhochmuthi'm going to have to drop folks14:17
rhochmuthgot to take my dad to airport14:18
rhochmuthdidn't realize that needed to be now14:18
*** cloudrancher has quit IRC14:18
kornicaok...anyway, there's just one thing that you could look after14:18
*** raildo has quit IRC14:18
witekok, see you next time14:18
kornicaI guess I will need PTL+1 for project-config change to move Py35 to voting14:18
rhochmuthplease end the meeting later14:18
rhochmuththx witek14:18
kornicathat'd be all from my side14:18
kornicathx14:18
*** arxcruz has joined #openstack-meeting14:18
kornicacya14:18
*** slaweq_ has joined #openstack-meeting14:18
*** rhochmuth has left #openstack-meeting14:18
*** cloudrancher has joined #openstack-meeting14:19
witek#topic reviews14:19
*** makowals has joined #openstack-meeting14:19
witekhttps://review.openstack.org/#/c/479169/14:20
arturb_ok , so this is me and Tomasz14:20
kornicayeah, for that we'd need rhochmuth :/14:20
arturb_yeah14:20
kornicahopefully he'll read log later and see that cry out for help ^^14:20
arturb_but if anybody else is interested this is a first step for monasca-events-api, cleaning the repository14:21
witekthis change prepares infrastructure for the restart of the events-api14:21
kornicaand CI tooling14:21
kornicawell...that infra..I guess14:21
*** cdub has quit IRC14:21
witekanything else on it?14:22
kornicanot really...bunch of deletes and couple additions14:22
arturb_exactly14:22
witekhttps://review.openstack.org/#/c/482443/14:22
kornicaduring testing failing py{27,35} and cover are expected, so don't bother with them14:23
kornicathey will kick in once there is actual codebase14:23
arturb_this is a first draft of new events-api14:23
arturb_providing new edpoint with body schema and response codes14:23
*** slaweq_ has quit IRC14:23
witeknice, the api-ref will be published to developers.o.o, right?14:24
kornicathat's the goal14:24
arturb_yep14:24
kornicaonce we clean the repo14:24
kornicaarturb_ will, I guess push to project-config to have the same gate situation (apart from tempest)14:25
kornicaas in log-api14:25
*** tobberydberg has quit IRC14:25
witekfor now there is only one resource?14:25
kornica<shining example for other monasca-*> <being modest>14:25
kornicaan endpoint ?14:25
arturb_kornica yes this is the plan after merging the change with clean up the repository14:25
*** tobberydberg has joined #openstack-meeting14:25
kornicaarturb_, what about endpoints ?14:25
kornicajust one for start?14:26
arturb_there is only one endpoint for start14:26
arturb_for colecting events in a bulk mode14:26
kornicamight be good idea, to either try and see if specs are still used (there are jobs to build those) or mark that part of api-ref as spec14:27
kornicawith the rst note or something14:27
kornicawitek, any thoughts on that ?14:27
kornicaguess we didn't really reach any agreement on specs for new API endpoints...14:27
witekwe can switch on the infra jobs and then we'll see if they published correctly14:28
kornicathey will be published as long as setup is correct14:28
kornicapoint is that, what arturb_ is doing, is more or less just a spec14:28
kornicadrafting new feature14:28
witekI think it's OK to start like this14:29
witekarturb_ also starts implementing, right?14:29
arturb_yeah, today i started implementing oslo.policies14:29
*** tobberydberg has quit IRC14:29
arturb_the change is in review but still a lot of work14:30
arturb_https://review.openstack.org/#/c/482837/14:30
arturb_this is the change14:30
witekif someone has ideas how the events api for collecting notifications should look like, it's good time to review the spec14:30
arturb_it would be nice :)14:31
*** tobberydberg has joined #openstack-meeting14:31
*** armstrong has joined #openstack-meeting14:31
witekcan we move on?14:31
arturb_witek, yes we can14:31
witekhttps://review.openstack.org/48016014:31
kornicayeah, so that was mentioned before14:32
kornicarequires testing inside local VM I guess14:32
kornicaas there re no integrating tests for that part14:32
kornica(might be good idea to have them added)14:32
witekwould you like to add some? :)14:33
*** tobberydberg has quit IRC14:33
kornicaI can try14:33
kornicaactually that's not all that bad14:33
kornicathe idea14:33
kornicaI think I can start small with simple alarm def, send some metrics and expect that mailbox contains the email14:34
*** tobberydberg has joined #openstack-meeting14:34
*** Julien-zte has quit IRC14:34
kornicathough I am not really sure if I should setup some fake mail server (which will require a lot of work)14:34
kornicaor just try and access /var/mail14:34
witekkeep it simple14:34
*** gouthamr has joined #openstack-meeting14:35
kornicakiss14:35
kornicaforgot stupid14:35
kornica:D14:35
witek:)14:35
witekhttps://review.openstack.org/48289214:35
*** Julien-zte has joined #openstack-meeting14:35
kornicaok, but does that mean14:35
kornicathat we're waiting with this14:35
kornicaor manual testing and going further14:35
kornica?14:35
*** Julien-zte has quit IRC14:35
witekdo you want to add the test, or you don't have time?14:36
*** Julien-zte has joined #openstack-meeting14:36
kornicaI can add the test, but I'd consider that as much have for now14:36
witekI'm fine with leaving it as is14:36
*** Julien-zte has quit IRC14:36
kornicamailing part (or rather notifying part) and lack of integration tests14:36
kornicais not just a problem of monasca-notification14:37
*** Julien-zte has joined #openstack-meeting14:37
*** Julien-zte has quit IRC14:37
*** zbitter is now known as zaneb14:37
kornicaso we could have it talked over but looking at this change as Pike goal, I'd ask to just review that by hand14:37
witekworks for me14:38
*** Julien-zte has joined #openstack-meeting14:38
*** Julien-zte has quit IRC14:38
kornicaok then14:38
*** Julien-zte has joined #openstack-meeting14:38
witekhttps://review.openstack.org/48289214:39
*** Julien-zte has quit IRC14:39
witekjenkins -114:39
kornicanow it isn't :P14:39
kornica(just wait 2-3 minutes)14:39
kornicaforgot to remove sth from one plae14:39
witek:)14:39
kornicas/plae/place/g14:39
*** Julien-zte has joined #openstack-meeting14:39
*** Julien-zte has quit IRC14:39
witekok, will give +114:40
kornicathx14:40
*** Julien-zte has joined #openstack-meeting14:40
witekhttps://review.openstack.org/#/c/480030/14:40
*** Julien-zte has quit IRC14:40
kornicain overall same thing as already done for log-api14:40
kornicaadding tooling needed to start working monasca-api docs in the same format as in log-api14:41
*** Julien-zte has joined #openstack-meeting14:41
*** Julien-zte has quit IRC14:41
witekso what documents would be published?14:42
*** Julien-zte has joined #openstack-meeting14:42
kornicaapi-guide14:42
*** Julien-zte has quit IRC14:42
kornicauser (developer) docs14:42
kornicaapi-ref14:42
kornicareleasenotes14:42
kornicaas far as I checked that's the overall approach for Openstack14:42
kornicalooked for specs, but core projects seems not to have them anymore in trees14:43
witekwhat is the difference between api-guide and user (developer) docs?14:43
kornicauser (dev) docs goes as far as to installing, configuring, dev + review process14:44
kornicasome sample code14:44
kornicasome project wide policies regarding different activities14:44
witekso basically, landing page for the project, right?14:44
witeklike here: https://docs.openstack.org/neutron14:45
kornicawhile api-guides are some sort of an overview (as far as I understand them) regarding usage of api14:45
*** emagana has joined #openstack-meeting14:45
kornicayeah, like landing page14:45
kornicamight be actually the best way to describe it14:45
amotokii am not a monasca folk, but i can comment on doc-migration14:46
kornicayeah ?14:46
witekamotoki: yes please14:46
amotokithe role of user/ or other directories are described here http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html#proposed-change14:46
amotokiuser/ is for end-users of monasca in your case.14:46
kornicahmmm...might be that we good initial idea for us wrong ?14:47
amotokiif you haven't visit the doc-spec, it is better to read it first :)14:48
kornicaI mean...is api-guide something that should be covered inside doc/*14:48
amotokifor the api guide, it is not in the first step of the doc-migration.14:48
amotokiit is an option.14:49
amotokithe api guide is optional. IIUC, the API reference is highly recommended (though it is not a part of doc-migration)14:49
amotokiyou can have the api-guide either in doc/ or in a separate dir.14:50
kornicathat's nice feedback on that for sure14:50
witekso, the new place for API ref is doc/source/api, right?14:50
amotokiyou can see "Further discussion of the layout of the api/ and releasenotes/ directories is deferred until we are farther along with the initial migration work. " as a note.14:50
kornicaso I think that doc, api-ref and releasenotes can stay as it was14:51
amotokicurrently we don't start the migration of the API reference into doc/ yet.14:51
amotokikornica: exactly14:51
kornicauntil there's an agreement how to do this14:51
kornicabut the point that bugs me is we really need seperate api-guide and seperate jobs14:52
kornicaor should the ontent of it be merged into doc/14:52
kornicawe haven't started working on that part14:52
kornicabut now I have doubts is it really needed14:52
amotokikornica: I think API guide and API reference are different.14:52
amotokiright?14:53
*** zhurong has quit IRC14:53
kornicayeah, they are14:53
kornicaapi-ref is more or less a documented restful api as far as I understand :D14:53
kornicaapi-guide is though a different beast14:53
amotokifor API guide I think having it in doc/ makes things simpler.14:53
*** ad_rien_ has joined #openstack-meeting14:54
kornicawitek: guess we'll talk this through and see if that's actually a point of interest for us to have it14:54
amotokifor API ref, it currently uses a different sphinx config, so it might be better to have it separately ATM14:54
*** psachin has quit IRC14:54
kornicamight be as amotoki says, to have it inside doc/14:54
*** ramineni_ has joined #openstack-meeting14:54
amotokikornica: yes14:54
*** lhx_ has joined #openstack-meeting14:55
witekwhat we definitely should do, is to convert the existing documentation to rst14:55
witekand publish to docs.o.o14:55
*** reedip_ has joined #openstack-meeting14:56
kornicaok, so we'll move as we were with filling doc/ and api-ref (if needed) leaving api-guide in peace for now14:56
kornicafine with that ?14:56
witekkornica: I guess will still have to discuss it14:56
kornicakk14:57
kornicaanyway, amotoki really appreciate the input14:57
amotokikornica: you're welcome14:57
witekamotoki: thanks a lot14:57
witek#topic Documentation [monasca-log-api] live14:57
*** david-lyle has quit IRC14:58
*** david-lyle has joined #openstack-meeting14:58
kornicajust some live examples ;-)14:58
witekapart from the fact that there are many empty pages, I like it a lot :)14:58
kornicaphew :D14:58
*** prateek has quit IRC14:59
witekalso, I guess the most information should be included in monasca-api and has reference to monasca-log-api14:59
*** sc has joined #openstack-meeting15:00
witekI guess we have to end here15:00
witekbye everyone15:00
kornicacya15:00
*** haruki has quit IRC15:00
*** marst has joined #openstack-meeting15:00
witek#endmeeting15:00
kojibye15:00
*** hosanai has quit IRC15:01
*** kornica has quit IRC15:01
*** Fdaisuke has quit IRC15:01
*** rcernin has quit IRC15:01
*** arturb_ has quit IRC15:02
*** rbartal has quit IRC15:02
*** cloudrancher has quit IRC15:02
*** cloudrancher has joined #openstack-meeting15:02
*** makowals has quit IRC15:04
*** koji has quit IRC15:05
*** felipemonteiro has joined #openstack-meeting15:07
*** felipemonteiro_ has joined #openstack-meeting15:08
*** markstur has joined #openstack-meeting15:10
*** makowals has joined #openstack-meeting15:10
*** fzdarsky is now known as fzdarsky|afk15:10
*** tobberyd_ has joined #openstack-meeting15:11
*** felipemonteiro has quit IRC15:12
*** Alex_Staf has quit IRC15:12
*** aagate has joined #openstack-meeting15:13
*** tobberydberg has quit IRC15:14
*** Swanson has joined #openstack-meeting15:14
*** qwebirc64552 has joined #openstack-meeting15:16
*** tobberyd_ has quit IRC15:16
*** RonghUI has quit IRC15:17
*** slaweq_ has joined #openstack-meeting15:19
*** prateek has joined #openstack-meeting15:20
*** oidgar has quit IRC15:21
*** fnaval has joined #openstack-meeting15:22
*** chyka has joined #openstack-meeting15:22
*** cloudrancher has quit IRC15:23
*** cloudrancher has joined #openstack-meeting15:23
*** slaweq_ has quit IRC15:24
*** Guest75779 has quit IRC15:24
*** alexchadin has quit IRC15:25
*** chyka_ has joined #openstack-meeting15:26
*** dbecker has quit IRC15:28
*** chyka has quit IRC15:29
*** rmascena is now known as raildo15:29
*** tobberydberg has joined #openstack-meeting15:30
ttx#startmeeting releaseteam15:30
openstackttx: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.15:30
ttx#endmeeting ?15:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:30
openstackMeeting ended Wed Jul 12 15:30:56 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-07-12-14.01.html15:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-07-12-14.01.txt15:31
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-07-12-14.01.log.html15:31
ttx#startmeeting releaseteam15:31
openstackMeeting started Wed Jul 12 15:31:06 2017 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.15:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:31
*** belmoreira has quit IRC15:31
*** openstack changes topic to " (Meeting topic: releaseteam)"15:31
openstackThe meeting name has been set to 'releaseteam'15:31
ttxdhellmann, dims: o/15:31
dhellmanno/15:31
dhellmannfungi : o/15:31
ttxLet's try to fit in 30min15:31
ttxPing list: dims, fungi, tonyb, stevemar, lbragstad15:31
*** witek has left #openstack-meeting15:31
ttxalthough the unusual time is likely to mess up with attendance today15:31
ttx#topic Organize next week work15:32
*** openstack changes topic to "Organize next week work (Meeting topic: releaseteam)"15:32
ttxSo I'm traveling to Asia all week, being in planes every other day15:32
ttxwhich will mess up with my availability to do things15:32
*** makowals has quit IRC15:32
dhellmannI'll be around15:32
dhellmannI can keep an eye on library releases15:32
ttxWe have a number of tasks noted on the tracking doc15:32
ttxI think you can probably cover for all of them ?15:33
* dhellmann looks15:33
fungioh, right. the meeting moved for this week15:33
ttxI could probably do the two patches15:33
dhellmannyeah, I can do those15:34
dhellmannthe others, I mean15:34
*** coolsvap has joined #openstack-meeting15:34
ttxOK, let's do that15:34
dhellmannyou could do the patches this week, really15:34
*** edmondsw_ is now known as edmondsw15:34
ttxAny question re: next week ?15:34
*** tobberydberg has quit IRC15:34
lbragstado/15:34
*** Sukhdev has joined #openstack-meeting15:34
ttxyes, will try to :)15:34
dhellmannoh, and I think there were 2 patches before because I messed it up that time but they're the same file so you only need 115:35
ttxok15:35
*** yamahata has joined #openstack-meeting15:35
ttx#topic Prepare to force releases for: instack and glance-store15:35
*** openstack changes topic to "Prepare to force releases for: instack and glance-store (Meeting topic: releaseteam)"15:35
ttxWe have two non-client libs that haven't released in Pike yet15:35
ttxFor which we may have to force a release on master HEAD15:36
ttxas mentioned in the last countdown email15:36
ttx(I will repeat it again this week)15:36
dhellmannI'm surprised by instack15:36
ttxMight be a mismatch15:36
dhellmannyeah15:36
ttxAll I know is they have an empty file in openstack/releases deliverables/pike15:36
dimso/ sorry was afk15:37
dhellmannttx: maybe talk to EmilienM about it?15:37
ttxdhellmann: yeah, although my overlap with him is limited those days15:37
dhellmannI assume the glance-store situation is lack of team members watching15:37
*** makowals has joined #openstack-meeting15:37
ttxso better if you or dims ask it15:37
dhellmannok, I'll try to raise him15:37
*** andreas_s has quit IRC15:38
ttxguess we could ping a Glance team member. Or flaper8715:38
ttx(re: glance-store Pike release before next week deadline)15:38
dhellmannor jokke_15:38
ttxKeep me posted if the situation changes, so taht I don't shame them in tomorrow's relkease countdown email15:38
*** qwebirc64552 has quit IRC15:39
dhellmannok15:39
*** aagate has quit IRC15:39
ttx#topic Blurb to add to the countdown email about "Please complete doc migration work"15:39
EmilienMhello15:39
*** openstack changes topic to "Blurb to add to the countdown email about "Please complete doc migration work" (Meeting topic: releaseteam)"15:39
ttx#undo15:39
openstackRemoving item from minutes: #topic Blurb to add to the countdown email about "Please complete doc migration work"15:39
dhellmannhi, EmilienM, we were just talking about the fact that instack hasn't released yet this cycle, and last week is the last chance to do so15:39
ttxEmilienM: instack next week15:39
EmilienMI'm doing it this week15:40
ttxok, great15:40
dhellmannEmilienM : great, thanks15:40
EmilienMeven today in fact15:40
EmilienMI also need to check with my team - instack is deprecated and we plan to remove it15:40
EmilienMthx for the reminder15:40
dimsvery little has changed in glance_store (http://stackalytics.com/?module=glance_store&metric=commits), but definitely enough for a fresh cut15:40
ttx#topic Blurb to add to the countdown email about "Please complete doc migration work"15:41
*** openstack changes topic to "Blurb to add to the countdown email about "Please complete doc migration work" (Meeting topic: releaseteam)"15:41
ttxdhellmann: you mentioned that I should talk about that in next countdown email15:41
*** kaisers_ has joined #openstack-meeting15:41
ttxIf you have a paragraph I could add, I'll take it15:41
ttxI suspect the situation evolves contanstly :)15:41
dhellmannok, I'll send you something15:41
ttxconstantly15:41
*** marios has quit IRC15:42
dhellmannwe decided to send a separate email to point out some of the repos that haven't been started, so we may not need it in the release email15:42
*** liusheng has quit IRC15:42
ttxI'll likely send the email at the end of my day on Thursday (off Friday)15:42
ttxok, just let me know if you want me to mention anything about it15:42
dhellmannok15:42
ttx#topic Queens Release management PTL candidates ?15:42
*** openstack changes topic to "Queens Release management PTL candidates ? (Meeting topic: releaseteam)"15:42
ttxElections are coming up, I'm fine rotating if anyone feels up to take the hat15:43
*** liusheng has joined #openstack-meeting15:43
ttx"feels like taking the hat" sounds better15:43
dhellmannI anticipate needing time to continue the docs work, so I won't be running, but I'll still be on the team15:43
dimsttx : dhellmann : i am still trying to figure out how much workload will be on the internal side for new employer..15:44
fungiheh. pass the hat15:44
ttxI'm fine doing it again. I think dims is busy enough and may have to cover for requirements if nobody shows up there :P15:44
dimsy, requirements i can handle :)15:45
dhellmannok15:45
ttxOK, let's say I'll do it for Queens, with an eye on passing the baton for R15:45
ttx(assuming there are no other candidates)15:45
dimssmcginnis any interest in the release work?15:46
*** sc has left #openstack-meeting15:46
*** caboucha has joined #openstack-meeting15:46
* dhellmann watches for a dark horse candidate15:46
smcginnisdims: I'm game.15:46
ttxsmcginnis: aren't you knee-deep in cinder ?15:46
dimscool smcginnis !15:46
*** jtomasek_ has joined #openstack-meeting15:47
fungimaybe he wants to pass the hat too15:47
smcginnisttx: The water level comes and goes. It's manageable.15:47
smcginnisfungi: ;)15:47
ttxBy all means if you feel like you can cover it all, I'm more than happy to help you in the job15:47
*** VW has joined #openstack-meeting15:48
ttxIt's not as if dhellmanna nd me would go anywhere15:48
*** yamamoto has quit IRC15:48
ttxand dims15:48
smcginnisI never intended to be Cinder PTL as long as I have been, but it's not too bad until someone else steps up.15:48
dims++ smcginnis15:48
dhellmannsure, we'd be here to support15:49
ttxJob is mostly about sending reminders according to the process, holding the meetings, and then take up the work that nobody else takes15:49
smcginnisNot too scary.15:49
ttx(and of course some release request reveiwing)15:49
*** yamamoto has joined #openstack-meeting15:49
*** ad_rien_ has quit IRC15:49
*** cloudrancher has quit IRC15:50
ttxEven less scary knowing that dhellmann, dims and myself will be very much around. Actually more available having someone holding the PTLship15:50
*** cloudrancher has joined #openstack-meeting15:50
*** yamamoto has quit IRC15:51
*** cloudrancher has quit IRC15:51
dims++ ttx15:51
ttxAnd teh more people know the process the better15:51
smcginnisYeah, seems like there would be good support available.15:51
*** cloudrancher has joined #openstack-meeting15:51
dhellmannplus, we wrote instructions!15:51
*** iyamahat has joined #openstack-meeting15:51
smcginnisEither way, I'd definitely like to be more involved in the process to be able to help more.15:52
fungiever evolving instructions15:52
smcginnisdhellmann: Documentation?! Amazing. :)15:52
dimsdhellmann has automated all the stuff too! :)15:52
dhellmannsmcginnis : yep, see the process.rst file in the releases repo15:52
fungiwhich we have a probable update to we can discuss in #openstack-release once the meeting wraps15:52
ttxPROCESS.rst15:52
dhellmannyes, I forgot it's a shouty filename15:53
smcginnis:)15:53
ttxbecause it's a shouty PROCESS15:53
fungi#link http://git.openstack.org/cgit/openstack/releases/tree/PROCESS.rst15:53
*** zhonghua has quit IRC15:53
fungiperhaps it's a fortran process15:53
*** jtomasek_ has quit IRC15:53
dhellmannI was typing very hard that day.15:53
ttx#topic Open discussion15:53
*** openstack changes topic to "Open discussion (Meeting topic: releaseteam)"15:53
*** emagana has quit IRC15:54
dimssafe travels ttx15:54
*** ihrachys has quit IRC15:54
*** zhonghua has joined #openstack-meeting15:54
fungismcginnis: noticed that the `tox -e aclmanager -- groups post_release ...` step seems to have been missed for ocata15:55
*** Patifa has joined #openstack-meeting15:55
*** ihrachys has joined #openstack-meeting15:55
dhellmannsmcginnis : seriously, take a look through the file and let us know if there are any questions15:55
fungiat least according to http://git.openstack.org/cgit/openstack/releases/tree/PROCESS.rst#n299 that should have put the gerrit groups right for stable branch maintainers15:55
dhellmannhmm15:55
ttxfungi: I just run the prerelease step15:55
smcginnisdhellmann: Will do, I have it on my list to actually focus some time on this afternoon now.15:55
dhellmannfor all repos, or just cinder? (I saw the comment in #openstack-release)15:55
*** emagana has joined #openstack-meeting15:55
fungittx: oh, so that's a stable maint task?15:55
fungidhellmann: cinder looks consistent with, e.g., nova15:56
dhellmannwell, it might have been the previous PTL's responsibility15:56
*** amotoki is now known as amotoki_away15:56
fungiheh15:56
dhellmannthat slacker couldn't wait to be done with the release15:56
smcginnisHah15:56
ttxaclmanager sets the members of the $project-release-branch group in gerrit15:56
*** rajathagasthya has joined #openstack-meeting15:56
*** xiaofandh12 has quit IRC15:56
fungiyeah, https://review.openstack.org/#/admin/groups/nova-release-branch for example15:57
ttxPost-release that group needs to contain $project-stable-maint15:57
fungistill just the release managers and nova-release in therwe15:57
ttxPre-release that group needs to contain $project-release15:57
ttxWe are at pre-release stage now15:57
fungiso they're the only ones allowed to approve stable/ocata changes for now15:57
ttxOh15:57
dhellmannttx: this is for the ocata branch15:57
ttxThat's because we need to approve...15:57
ttxhttps://review.openstack.org/48295115:57
ttxfirst15:57
ttxI did both steps at the same time15:57
fungiyep, i saw that show up in my review queue today and have started looking at it15:57
dhellmannaha15:58
fungiaha! race condition ;)15:58
ttxso yes we should approve that ASAP15:58
smcginnisIsn't that supposed to flip before the next release gets going too far?15:58
*** emagana has quit IRC15:58
fungiso it's only been broken for a few hours. mystery solved15:58
ttxsmcginnis: actually that group is supposed to be used only for stable/pike15:58
*** emagana has joined #openstack-meeting15:58
ttxhttps://review.openstack.org/482951 swwitches it to stable/pike15:58
*** amotoki_away is now known as amotoki15:59
ttxbut that hasn't merged yet15:59
ttxand yet I updated the group members15:59
fungiwas just proposed earlier today15:59
smcginnisttx: So as soon as Ocata was final, we switch to stable/pike. In preparation for the next release even though it doesn't exist yet?15:59
*** amotoki is now known as amotoki_away15:59
ttxlet's switch to openstack-release15:59
fungismcginnis: yep, gerrit is fine having acls that refer to nonexistent refs15:59
ttxhtere is another meeting starting now here15:59
fungithanks ttx!15:59
dhellmanndo we have that step out of order in the process?15:59
ttxthis needs a rather lengthy explanation15:59
*** Rockyg has joined #openstack-meeting15:59
ttxno15:59
*** jamesden_ has quit IRC15:59
ttx#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Jul 12 16:00:01 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/releaseteam/2017/releaseteam.2017-07-12-15.31.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2017/releaseteam.2017-07-12-15.31.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/releaseteam/2017/releaseteam.2017-07-12-15.31.log.html16:00
ttx-> #openstack-release16:00
smcginnis#startmeeting Cinder16:00
openstackMeeting started Wed Jul 12 16:00:16 2017 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: Cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
SwansonHello.16:00
patrickeastHi16:00
tommylikehuhello!16:00
arnewiebalckhi16:00
diablo_rojo_phonHello :)16:01
jungleboyjo/16:01
*** jamesdenton has joined #openstack-meeting16:01
geguileohi!16:01
xyang1Hi16:01
smcginnisHello all.16:01
* geguileo is missing the ping };-)16:01
wxy-hi16:01
smcginnisping dulek duncant eharney geguileo winston-d e0ne jungleboyj jgriffith thingee smcginnis hemna xyang1 tbarron scottda erlon rhedlind jbernard _alastor_ bluex karthikp_ patrickeast dongwenjuan JaniceLee cFouts Thelo vivekd adrianofr mtanino karlamrhein diablo_rojo jay.xu jgregor lhx_ baumann rajinir wilson-l reduxio wanghao thrawn01 chris_morrell watanabe.isao,tommylikehu mdovgal ildikov wxy16:01
smcginnisviks ketonne abishop sivn16:01
geguileothanks!  ;-)16:01
smcginnis:)16:02
smcginnisI need a macro or something16:02
_pewp_hemna ヘ(°¬°)ノ16:02
bswartz.o/16:02
e0nehi16:02
*** abishop has joined #openstack-meeting16:02
tbarronhi16:02
*** csaikia has joined #openstack-meeting16:02
abishopo/16:02
smcginnisOK, guess we can get going.16:03
smcginnis#topic Announcements16:03
*** openstack changes topic to "Announcements (Meeting topic: Cinder)"16:03
smcginnis#link https://etherpad.openstack.org/p/cinder-spec-review-tracking Review focus16:03
smcginnisStill some open work on merged specs for Pike in there.16:03
smcginnisAnd we're running really low on time.16:03
smcginnisSo if at all possible, please help with reviews and updates.16:04
*** rbrndt has left #openstack-meeting16:04
*** esberglu has quit IRC16:04
smcginnisI hope to be a little more proactive this time arround and move merged specs that don't fully land.16:04
smcginnisSince we've just left them for the most part in the past.16:04
jungleboyjsmcginnis:  ++16:04
smcginnisThen people come along a few releases later and ask why it's not working.16:04
e0nesmcginnis: I didn't find API-WG decision as was asked for 'Backup Service Enabled API' - so let's move it to Queens16:05
*** tesseract has quit IRC16:05
lhx_o/ hi16:05
smcginnise0ne: OK, great. Want to propose that?16:06
rajiniro/16:06
e0nesmcginnis: I need to look on it a bit deeper forst16:06
e0nes/forst/first16:06
smcginnise0ne: OK, sounds good.16:06
smcginnis#link https://etherpad.openstack.org/p/cinder-ptg-queens Planning etherpad for PTG16:06
smcginnisWe have a topic planning etherpad started for the PTG.16:06
smcginnisPlease add any topics you think would be good to discuss face to face there.16:07
smcginnisHopefully many of you can attend.16:07
smcginnisOh, even if you don't have a topic, please add your name if you are planning to attend so we can get an idea of who will be there.16:07
e0neeven if you can't attend - please, add topic you are interesting  in16:07
diablo_rojo_phonIf you don't think you can, please apply for tsp.16:07
smcginnise0ne: ;)16:07
smcginnisdiablo_rojo_phon: Jumping the gun! :D16:08
smcginnis#link https://www.eventbrite.com/e/project-teams-gathering-denver-2017-tickets-33219389087 PTG registration16:08
e0neI think if topic is really important - it should be discussed16:08
smcginnis#link https://openstackfoundation.formstack.com/forms/travelsupportptg_denver16:08
e0nemaybe with some hangout session too16:08
smcginnisTravel support program is accepting applications.16:08
hemnadiablo_rojo_phon, tsp link?16:08
diablo_rojo_phonI know it's just important :)16:08
* e0ne still is not sure about PTG attandance16:08
smcginnisIf you are involved but are unable to get company funding, please apply for travel support.16:08
*** gcb has quit IRC16:09
smcginnise0ne: :(16:09
smcginnisWe willd definitely try to stream again.16:09
diablo_rojo_phonhemna smcginnis: has it on the agenda16:09
smcginnisHopefully with decent audio.16:09
hemnaoh yah it still costs $100 to attend16:09
e0nehemna: $100 + hotel + flight to US :(16:09
hemnayah16:09
hemnathanks for the links16:10
SwansonSwim.16:10
smcginnisdiablo_rojo_phon: Does the TSP cover anything with the registration cost?16:10
diablo_rojo_phonTap can cover all of it.16:10
diablo_rojo_phonTsp16:10
smcginnisSweet.16:10
diablo_rojo_phonReg, flight and hotel16:10
smcginnisSo definitely apply if you need it.16:10
diablo_rojo_phonOr some subset16:11
smcginnis#topic Update on mysql/pymysql issues with oslo.db16:11
*** openstack changes topic to "Update on mysql/pymysql issues with oslo.db (Meeting topic: Cinder)"16:11
smcginnisNo name on this one. Was that you arnewiebalck ?16:11
jungleboyjsmcginnis:  Sorry, that was me.16:11
arnewiebalcknope16:11
jungleboyjJust for awareness.16:11
arnewiebalcknot me, I mean :)16:11
smcginnisarnewiebalck: Well, it was you. ;)16:12
jungleboyjI talked to the Oslo team about this and they agreed that it was something to improve.16:12
smcginnis#link https://bugs.launchpad.net/oslo.db/+bug/169295616:12
openstackLaunchpad bug 1692956 in oslo.db "Warn about potentially misconfigured connection string " [Undecided,Fix committed]16:12
_alastor_o/16:12
* smcginnis marks _alastor_ as tardy16:12
jungleboyjThey will add a warning to logs when the config option is used and they will update the help text to indicate that the option can cause deadlocks.16:12
jungleboyjgcb was going to push the patch up.16:13
smcginnisjungleboyj: OK, great.16:13
_alastor_smcginnis: sorry teach :P16:13
jungleboyjLooks like he already has a patch linked in there.16:13
smcginnisI know there was some debate about just internally switching it to the pymysql connection, but didn't want to change behavior on people.16:13
jungleboyjarnewiebalck:  You mind taking a look and making sure it looks good to you?16:13
arnewiebalcksure, will do16:13
jungleboyjarnewiebalck:  Thank you sir.16:14
jungleboyjI will go look at the patch in the bug as well.16:14
*** evgenyf has joined #openstack-meeting16:14
*** annegentle has joined #openstack-meeting16:14
jungleboyjThat was all on that from me.  :-)16:15
smcginnisjungleboyj: Thanks for the update.16:15
smcginnis#info oslo.db proposal is to log warning and improve help text.16:15
jungleboyjsmcginnis:  Welcome.16:15
smcginnis#topic Documentation Migration16:16
*** openstack changes topic to "Documentation Migration (Meeting topic: Cinder)"16:16
smcginnisIt's the jungleboyj show today. :)16:16
jungleboyj:-)16:16
e0ne:)16:16
smcginnis#link https://review.openstack.org/48175616:16
jungleboyjJust wanted to make people aware of how this is progressing.16:16
smcginnis#link https://review.openstack.org/48184716:16
smcginnis#link https://review.openstack.org/48184816:16
jungleboyjSo, the main admin-guide content has been migrated and merged.16:16
jungleboyjWe have some cli documentation that hasn't merged yet.16:16
jungleboyjFound that the detailed driver config info hasn't been moved yet either.16:17
smcginnisSo in case anyone missed what was going on, it's been decided all documentation is moving out of openstack-manuals into the individual projects.16:17
smcginnisSo we can update docs along with patches.16:17
smcginnisSo first step is getting things moved over.16:17
jungleboyjsmcginnis:  Oh yeah, background is important.  :-)16:17
smcginnisThen we can improve any formatting and other issues.16:17
smcginnisjungleboyj: ;)16:17
jungleboyjThis is all because of the brain drain from the documentation team.16:18
*** esberglu has joined #openstack-meeting16:18
smcginnisWhich reminds me - no real need for DocImpact tags now.16:18
jungleboyjhemna:  Is super excited that we get to maintain our own documentation now.16:18
smcginnisAs if there is a DocImpact, the patch should just include the doc updates.16:18
jungleboyjsmcginnis:  Good note.16:18
tommylikehuwow16:18
geguileoI raised the subject of whether it makes sense or not having openstack commands in all the docs when we don't actually maintain that client...16:18
geguileoAnybody thinks this is kind of "weird"16:19
smcginnisAll english grammer and style questions can go to hemna16:19
smcginnis:D16:19
jungleboyjsmcginnis:  ++ So, now reviewers need to enforce doing documentation updates in their patches.16:19
bswartzgeguileo: +116:19
diablo_rojo_phonsmcginnis: :)16:19
smcginnisgeguileo: Yeah, I kind of agree there. But not sure if there's a way around that now.16:19
ildikovjungleboyj: +1, that's one of the key aspects here16:19
geguileosmcginnis: OK, so it is what it is :-(16:19
jungleboyjildikov: :-)  I will be the documentation Czar about would appreciate help enforcing the need for doc updates.16:20
geguileojungleboyj: or they could go in a different patch dependent on the code one, but they should be available before merging the code16:20
smcginnisYeah, I think things like the admin guide should show openstack CLI commands, since that's what we want end users to move to.16:20
smcginnisEven though we don't really have much to do with that.16:20
jungleboyjgeguileo:  That is good too.16:20
smcginnisgeguileo: +116:20
smcginnisjungleboyj: Sorry, I kind of hijacked that. Anything else?16:21
*** slaweq_ has joined #openstack-meeting16:21
jungleboyjgeguileo:  We need to move the cinderclient content right now.16:21
ildikovjungleboyj: with the Ceilometer team we've been for moving the admin-guide for a while to be able to handle the doc updates along with the code changes16:21
jungleboyjI don't know that we want that to go away but we do need to work on moving people to OpenStack client.  Let me think about that.16:21
*** esberglu has quit IRC16:22
jungleboyjAnyway, so I will be pushing up a patch for the driver config stuff soon.  Then we need to enable handing spinx warnings as errors.16:22
xyang1jungleboyj: are you just talking about doc or the cinderclient code?16:22
jungleboyjxyang1:  Just the doc.16:22
xyang1Ok16:22
jungleboyjThere are a lot of docstring issues in our code that I am going to have to push patches up to resolve.  Will do that in bite size pieces before enabling errors.16:23
jungleboyjSome have seen me -1 patches for docstring issues.16:23
tommylikehujungleboyj:  :)16:23
jungleboyjI need to work on better understanding what is right and wrong.  Hope to have that together for everyone to look at before next week's meeting and then can answer questions.16:23
jungleboyjI just know right now what causes the doc build to fail.  How to fix it.  Want to find if there are better ways to avoid the warnings.16:24
smcginnisjungleboyj: I think we all need to learn what is correct formatting, but once we are able to enable warnings as errors, at least it will be pretty obvious.16:24
jungleboyjIf you find missing documentation please let me know.16:25
smcginnisjungleboyj: Careful what you ask for. :)16:25
jungleboyjsmcginnis:  ++ Yeah,  that will help.16:25
*** slaweq_ has quit IRC16:25
jungleboyjI think people will need to get in the habit of doing a docs build with their changes.16:25
*** reedip_ has quit IRC16:25
jungleboyjOr we could make it a part of pep8 maybe?16:26
eharneyit's already a separate job, doesn't need to be done as part of pep816:26
diablo_rojo_phonI would just run their tox check build or whatever after16:26
*** rossella_s has quit IRC16:26
e0nejungleboyj: we already have doc job. can we re-use it?16:26
diablo_rojo_phonNot combine them16:26
ildikovjungleboyj: the docs job is fairly quick, so it should be fine16:26
*** esberglu has joined #openstack-meeting16:27
*** julim has joined #openstack-meeting16:27
ildikovjungleboyj: it's only the matter of raising awareness on that it counts from now on16:27
jungleboyjdiablo_rojo_phon:  Then people will need to remember to do 'tox -e docs' before the do a review.16:27
jungleboyjildikov:  Right.16:27
ildikovjungleboyj: people will learn form the docs job failures, I wouldn't add it to pep8 either16:27
smcginniseharney: I wonder if we should have a "tox -e pregitreview" target that does fast8, docs, and py27 or something.16:27
eharneypeople can just run "tox", dragging docs into pep8 is not the right thing to do16:27
smcginnisKind of a "here are the things you should really run before proposing a patch".16:28
jungleboyjsmcginnis:  That would be nice.16:28
eharneysmcginnis: shouldn't that be the list of what runs by default when no environment is specified...?16:28
smcginniseharney: Well, I think that does full pep8, not fast8, and both py27 and 35.16:28
*** ihrachys has quit IRC16:28
smcginniseharney: And now some jerk wants to add py36 as well.16:29
smcginnis:P16:29
*** ihrachys has joined #openstack-meeting16:29
eharneylol16:29
smcginnishehe16:29
smcginnisAnyway... anything else to cover jungleboyj?16:29
jungleboyjAnyway, we can bikeshed on that piece when I have the doc builds all working.  :-)16:30
smcginnis+116:30
*** trinaths has joined #openstack-meeting16:30
jungleboyjsmcginnis:  Not right now.  Appreciate everyone's support getting through the migration.16:30
jungleboyjAnd being aware that the docs have a new level of importance.16:30
smcginnisjungleboyj: Thanks!16:30
smcginnis#topic Gathering of thin provisioning stats in Ocata16:31
*** openstack changes topic to "Gathering of thin provisioning stats in Ocata (Meeting topic: Cinder)"16:31
smcginnisarnewiebalck: OK, now it's you.16:31
arnewiebalckOk :)16:31
arnewiebalckAs mentioned yesterday, we upgraded to Ocata and hit the problem that the provisioning stats gathering broke the upgrade.16:31
arnewiebalckThe prob is that it cycles through our 4000+ volumes and that takes too long.16:32
*** ralonsoh has quit IRC16:32
arnewiebalckSo, we had to disable it to upgrade.16:33
*** annegentle has quit IRC16:33
*** VW has quit IRC16:33
geguileoarnewiebalck: is that on a specific backend?16:33
smcginnis#link https://github.com/openstack/cinder/commit/d4fd5660736a1363a4e78480b116532c71b5ce4916:33
arnewiebalckCeph.16:33
eharneyit's a ceph issue16:33
*** VW has joined #openstack-meeting16:34
geguileoeharney: I thought so, but wanted to be sure16:34
*** etoews has joined #openstack-meeting16:34
arnewiebalckI have to admit I’m also struggling with the overall idea behind this.16:34
*** annegentle has joined #openstack-meeting16:34
geguileo'cause I remember Jon Bernard mentioning that that was slow16:34
*** etoews has joined #openstack-meeting16:34
geguileoarnewiebalck: I believe it was the only mechanism to get the data (though I don't remember the specifics)16:35
arnewiebalckFrom what I see the code queries Ceph for every volume to get the image size.16:35
arnewiebalckCinder knows these sizes already.16:35
arnewiebalckIt’s not getting the actual usage from what I see..16:35
*** lpetrut has quit IRC16:35
eharneyit only knows the provisioned size already, not the amount of data actually written/consumed16:35
arnewiebalckThe code doesn’t give you that either.16:36
arnewiebalckIt gives you the allocated size.16:36
*** Guest86208 is now known as melwitt16:36
eharneythe goal of this is to gather that to be able to calculate the overprovisioning ratio16:36
geguileoarnewiebalck: it does give you the real size16:36
eharneythere was lengthy discussion in reviews about this code (i think the first attempt was wrong and later fixed), so i hope it's doing the right thing at this point16:37
arnewiebalckgeguileo: I don’t think so. We patched the code and it gives you the allocated size, not the used space of each volume.16:37
geguileoit iterates over the diffs to calculate the real size16:37
arnewiebalckgeguileo: even if it does this, what you wnat to know in the end is how much space is used in the pool, no?16:38
*** VW has quit IRC16:38
geguileoand that is the sum of all the diffs16:38
*** jbernard has joined #openstack-meeting16:39
arnewiebalckgeguileo: right (if you get the real size :-) )16:39
geguileoarnewiebalck: correct16:39
eharneyassuming that there isn't other data written into the pool than just the cinder volumes16:39
arnewiebalckin our case you do 4000 calls to Ceph on startup16:39
arnewiebalckand on each create16:39
arnewiebalckand on each delete16:40
geguileojbernard: could you chime in?16:40
jbernardi agree with the direction, as long as pools are cinder-exclusive16:40
jbernardelse, stats will be misleading16:40
geguileoarnewiebalck: no, not on each create (afaik)16:40
smcginnisSeems like there should be a more efficient way than making 4000 calls.16:40
geguileosmcginnis: I don't think there is16:40
*** caboucha has quit IRC16:40
arnewiebalckgeguileo: ok ok, I got excited ;)16:40
jbernardand we need to preserve allocated reporting, and not virtual16:40
eharneythere was also a pending optimization to move to diff_iterate2 which hasn't been tried afaik16:41
jbernardbut i think we're all on the same page about that, from reading the backlog16:41
geguileosmcginnis: the pool could be used for other volumes16:41
*** Sukhdev has quit IRC16:41
jbernardgeguileo: then a per-pool call willl be inaccurate16:41
arnewiebalckgeguileo: if it used by other volumes, it will be very diffcult to do the over subscription correctly16:41
geguileojbernard: yes, that's what I meant16:41
geguileojbernard: that there's no easier way, because it could be shared16:42
*** evgenyf has quit IRC16:42
*** Patifa has quit IRC16:42
jbernardif it can, then we must iterate16:42
geguileoarnewiebalck: yes, but it's possible16:42
jbernardor, document that we perfer it not be16:43
arnewiebalckgeguileo: sounds pretty complicated16:43
jbernardor add a setting16:43
jbernardbut lets not do that16:43
geguileoarnewiebalck: unless we explicitly prevent it somehow it's possible16:43
*** claudiub has quit IRC16:43
jbernardgeguileo: the admin would have to adhere to a policy, and deploy as such16:43
smcginnisI don't suppose a call could be added for ceph to take a collection and return the result in one call?16:44
geguileojbernard: Or we could check on start that all volumes belong to cinder (or look like they do) and report a warning that data will be inaccurate if not16:44
smcginnisNot sure passing 4000 IDs is much better. Or possible.16:45
jbernardsmcginnis: it could, but we'd have to iterate there16:45
jbernardsmcginnis: and it would take time to adopt16:45
arnewiebalckWhy isn’t it enough to know how full the pool is?16:45
arnewiebalckIN the end, the admin needs to take action when some threshold of real usage is used, no?16:45
smcginnisYeah, seems like you would want to know the pool usage total, not just the cinder useage. So if it's used by non-cinder you can actually take some of that into account.16:46
arnewiebalckNo matter what filled the pool.16:46
jungleboyjsmcginnis:  Good point.  :-)16:46
geguileoarnewiebalck: it looks like it got broken and you are right16:46
geguileoI was looking at the original code16:46
geguileobut this broke it: https://review.openstack.org/#/c/410884/5/cinder/volume/drivers/rbd.py16:46
arnewiebalckgeguileo: ok, thx for checking!16:46
eharneyyeah, i also thought the current code still did diff_iterate, apparently not16:47
geguileoarnewiebalck: it's adding the total size so it's like you say, not doing what it should16:47
geguileoSo 2 issues, right no it's not returning the right data16:47
*** jamesden_ has joined #openstack-meeting16:48
geguileoAnd it's inefficient16:48
*** Patifa has joined #openstack-meeting16:49
smcginnisarnewiebalck: Not just inefficient. It breaks large deployments, right?16:49
arnewiebalcksmcginnis: c-vol for that pool didn’t start16:49
eharneypresumably it breaks them by causing a timeout somewhere to be exceeded that could be raised in config?16:49
geguileoarnewiebalck: it's not knowing how full the pool is, but how much space WE are using the problem16:49
arnewiebalckservice-list reported that c-vol as XXX16:49
*** jamesdenton has quit IRC16:50
*** ricolin has quit IRC16:51
*** yamamoto has joined #openstack-meeting16:51
smcginnisMaybe enough for the meeting? Sounds like there will need to be some follow up discussion later.16:52
arnewiebalckgeguileo: You would use a pool for something else than just Cinder volumes (and not have a separate pool)?16:52
geguileoarnewiebalck: or you could have 2 different cinder-volume services using the same pool16:53
arnewiebalcksmcginnis: Shall we open a bug for the follow-up?16:53
smcginnisarnewiebalck: Sounds like that might be good if the current bug doesn't cover all of it.16:53
e0nearnewiebalck: +1 for bug for it16:53
arnewiebalcksmcginnis: you mean https://bugs.launchpad.net/cinder/+bug/169878616:54
openstackLaunchpad bug 1698786 in Cinder "cinder-volume fails on start when rbd pool contains partially deleted images" [Undecided,In progress] - Assigned to Ivan Kolodyazhny (e0ne)16:54
arnewiebalck?16:54
arnewiebalckgeguileo: I can see how you use 2 pools for 1 service, but the other way round?16:55
geguileoarnewiebalck: I've seen it done16:55
geguileoI'm not saying it makes sense, buuuuut, I've seen it16:55
arnewiebalckgeguileo: was there an explanation ? ;)16:55
*** pcaruana has quit IRC16:56
arnewiebalckgeguileo: ah, I see :-D16:56
smcginnisarnewiebalck: Yeah, that's what I was thinking of.16:56
smcginnisAny other things we need to discuss yet? 4 minutes.16:56
*** gans has joined #openstack-meeting16:56
smcginnisOK, let's wrap up then. Thanks everyone.16:57
e0nearnewiebalck, smcginnis: it's a different bug16:57
arnewiebalcke0ne: ok, I’ll open one then16:58
*** jtomasek_ has joined #openstack-meeting16:58
smcginnis#endmeeting16:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:58
openstackMeeting ended Wed Jul 12 16:58:27 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2017/cinder.2017-07-12-16.00.html16:58
tommylikehuthanks16:58
diablo_rojo_phonThanks smcginnis :)16:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2017/cinder.2017-07-12-16.00.txt16:58
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2017/cinder.2017-07-12-16.00.log.html16:58
*** fnaval has quit IRC16:58
*** emagana has quit IRC16:59
jungleboyjThanks!16:59
jungleboyj@!16:59
_pewp_jungleboyj (;-_-)ノ16:59
*** unicell has joined #openstack-meeting16:59
*** abishop has left #openstack-meeting16:59
lhx_thanks16:59
*** sanfern has joined #openstack-meeting17:00
*** etoews has quit IRC17:00
*** fnaval has joined #openstack-meeting17:00
johnsom#startmeeting Octavia17:00
openstackMeeting started Wed Jul 12 17:00:29 2017 UTC and is due to finish in 60 minutes.  The chair is johnsom. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: Octavia)"17:00
openstackThe meeting name has been set to 'octavia'17:00
*** jniesz has joined #openstack-meeting17:00
*** emagana has joined #openstack-meeting17:00
johnsomHi folks17:00
sanfernhi17:01
ganshello17:01
*** jbernard has left #openstack-meeting17:01
*** lhx_ has quit IRC17:01
johnsomOutlook is fighting with me.  I updated it for our new time, but I guess it didn't update the full series.  Sigh17:01
jnieszhi17:01
*** evgenyf has joined #openstack-meeting17:01
johnsomAt least I am here on time...17:01
nmagnezio/17:01
evgenyfo/17:02
johnsom#topic Announcements17:02
*** openstack changes topic to "Announcements (Meeting topic: Octavia)"17:02
*** yamamoto has quit IRC17:02
johnsomWe are heading towards feature freeze Pike-3 July 24th17:02
*** csaikia has left #openstack-meeting17:02
johnsomMy normal reminder, just a few days left for new features in Pike17:02
johnsomAlso, I released python-octaviaclient 1.1.0 yesterday. It fixes the l7rules issue.17:03
johnsomWe have closed out our Pike community goals, py35 support and uwsgi17:03
johnsomSo, that is good stuff.17:03
johnsomAlso, our docs have moved under the new scheme: https://docs.openstack.org/octavia/latest/17:03
xgerman_o/17:04
*** Patifa has quit IRC17:04
johnsomThe old developer link will still work for some time, but this is the new location.17:04
*** cpuga has joined #openstack-meeting17:04
johnsomI did a basic restructuring to fit the new standard.  We can probably polish more, but it is a start.17:04
johnsomThe presentation deadline for Sydney is soon.17:05
johnsomTwo more days.17:05
nmagnezidon't forget to share a link for us to vote when time comes :)17:05
johnsomFYI, I do not plan to attend Sydney17:05
johnsom#link https://www.openstack.org/summit/sydney-2017/call-for-presentations/17:06
johnsomAny other announcements this week?17:06
*** Patifa has joined #openstack-meeting17:07
*** e0ne has quit IRC17:07
johnsom#topic Brief progress reports / bugs needing review17:07
*** openstack changes topic to "Brief progress reports / bugs needing review (Meeting topic: Octavia)"17:07
johnsom#link https://etherpad.openstack.org/p/Octavia-Pike-priority-patches17:07
johnsomWe are tracking a set of priority patches for Pike at that link.  If you can, please help review17:08
johnsomAlso, nmagnezi asked for reviews on:17:08
johnsom#link https://review.openstack.org/#/c/469850/17:08
johnsom#link https://review.openstack.org/#/c/464332/17:08
*** iyamahat has quit IRC17:09
johnsomI have been focused on Docs, governance, and API performance improvement issues recently.17:09
johnsomThis week I have some internal stuff to attend to, so will mostly be doing reviews and such.17:10
johnsomAny other progress updates to share?17:10
nmagneziabout tripleO17:10
nmagneziwe are close to merging this: https://review.openstack.org/#/c/447496/17:10
sanfernreview on https://review.openstack.org/#/c/478385/1017:11
nmagnezinext step would be to have this fully automated as well17:11
xgerman_Yeah!!17:11
nmagnezijust FYI.17:11
johnsomCool stuff17:11
johnsom#link https://review.openstack.org/#/c/478385/1017:11
johnsomsanfern FYI, we use the #link tag to get the URLs in the minutes.17:11
*** cschwede has quit IRC17:11
sanfernok17:12
johnsomIt highlights it a bit more17:12
*** eharney has quit IRC17:12
johnsom#topic Discuss publishing amphora images (xgerman_)17:12
*** openstack changes topic to "Discuss publishing amphora images (xgerman_) (Meeting topic: Octavia)"17:12
*** oidgar has joined #openstack-meeting17:12
johnsomxgerman_ I think you wanted to talk about publishing amp images17:12
xgerman_yes17:13
*** eharney has joined #openstack-meeting17:13
xgerman_#link https://governance.openstack.org/tc/resolutions/20170530-binary-artifacts.html17:13
xgerman_so the image building process has been a source for a lot of confusion for our users so I was wondering we could provide some artifacts to ease them into Octavia17:14
johnsomReading through that it seems like the TC's stance is "you are on your own"17:14
xgerman_yep17:14
xgerman_we would only provide stable images and not provide very timely updates aka if their is a security issue we might not get around pushing an update immediately17:15
xgerman_but if some vendor wants to step into doing that more timely…17:15
xgerman_anyhow, throughts?17:15
johnsomYeah, that is my big concern about this.  They would be heavily "at your own risk" unless we do something like a daily build with the base OS updates17:16
*** dbecker has joined #openstack-meeting17:16
xgerman_yeah, it might be more to help non-production users17:16
xgerman_but there is always the risk people ignore our disclosures…17:17
johnsomFrom the sound of the resolution we might not be able to get infra support to do daily builds either...17:17
xgerman_yeah, I think it would be manual for a while unless we get some server somewhere17:18
johnsomYeah, plus it's hard to include disclosures that are prominent with images.  Maybe if we gz them or something17:18
johnsomAnyone else have input on this?17:18
xgerman_nmagnezi?17:19
johnsomHe just stepped away17:19
sanferncan we send some kind of alert on security patch release so users can update17:20
*** weshay is now known as weshay|lunch17:20
*** weshay|lunch is now known as weshay17:20
johnsomIn theory yes.  Basically it would trigger any time that base OS vendor pushes a new cloud image.17:21
xgerman_since twe only monitor security issues in Octavia actively I doubt we will be able to for the OS17:21
johnsomAgain, I'm not sure we have the infra for that right now.17:21
*** slaweq_ has joined #openstack-meeting17:21
xgerman_yeah, I think it will be a journey from building images occasionally to setting up more infrastructure17:21
johnsomI guess the question I have for this group is, would you find value in it?  Was building your own image easy enough?17:21
*** claudiub has joined #openstack-meeting17:22
johnsomI have to say as well, those cloud images roll pretty often17:22
*** lpetrut has joined #openstack-meeting17:22
jnieszI would imagine there is custom packages that a lot of people will add when building their images17:23
johnsomYeah, I know most production shops customize the image to some degree17:24
jnieszand we are building our own images already17:24
xgerman_yeah, my big concern are those evaluating Octavia and to speed up some 3rd party stuff (e.g. OSA)17:24
*** mdovgal has quit IRC17:25
*** Apoorva has joined #openstack-meeting17:25
*** yamahata has quit IRC17:25
*** slaweq_ has quit IRC17:26
johnsomYeah.  So, I think the "best" solution would be a daily build if we can find a place to host that.  Highly label it DEMO or something.17:27
xgerman_yep17:27
johnsomDEMO-WARNING-NOT-PRODUCTION-You-have-been-warned.gz17:27
johnsomGrin17:27
jniesz+117:28
*** oidgar has quit IRC17:28
xgerman_wonder how my free dropbox feels about that ;-17:28
xgerman_)17:28
johnsomxgerman_ Do you want to ask infra about it?17:28
xgerman_sure, I can ask17:28
johnsomOk, let's at least inquire if they would support us in that.17:28
*** Patifa has quit IRC17:29
xgerman_#action (xgerman) ask infra about daily image build17:29
johnsomOk, anymore on that topic for today?17:29
johnsom#topic Discuss having a scenario tests gate the runs with ACTIVE_STANDBY amphoras (nmagnezi)17:30
*** openstack changes topic to "Discuss having a scenario tests gate the runs with ACTIVE_STANDBY amphoras (nmagnezi) (Meeting topic: Octavia)"17:30
johnsomSo, yes, we need that.  grin17:30
xgerman_+117:30
johnsomNot sure if he is back or not.17:30
johnsomFYI, I have setup a new repo for our go forward tempest tests:17:31
*** trinaths has left #openstack-meeting17:31
johnsom#link https://github.com/openstack/octavia-tempest-plugin17:31
*** gans has quit IRC17:31
johnsomIt looks like there will be a community goal for queens for projects to move to this model.17:31
johnsomIn reality our tempest tests need to be re-written using the new "tempest way".17:32
*** sambetts is now known as sambetts|afk17:32
johnsomThe other challenge we have had with act/stdby is the infra hosts have limited resources, so spinning up the VMs could be a problem.  But we can cross that bridge when we get there.17:33
johnsomI think really it comes down to do we have someone that can spend some time working on octavia-tempest-plugin and modernizing our tempest suite.17:34
xgerman_we should probably apply at the summer of code ;-)17:34
johnsomYes!  Interns!  Grin17:36
johnsomOur last intern wrote most of the act/stdby code.17:36
xgerman_yeah, maybe we need to wrk with some local college and hand out coursework17:36
johnsomHmmm, if I had the cycles I would hit up the local university.  I know they have done OpenStack courses in the past.17:37
xgerman_wasn’t there some QA team in OpenStack we could pawn things to?17:37
johnsomUmm, yeah, well, I think that team is short on folks now too.17:38
johnsomThey have been helpful with "how-to" type questions and such, but I don't think they are in the business of writing tests at the moment17:39
xgerman_ok, I guess we are not solving this today17:39
johnsomAnyway, it will probably become a focus for Queens if nothing else.17:39
*** cloudrancher has quit IRC17:39
xgerman_in Queens we also need to nail down the vendor driver stuff17:40
johnsomYeah, if anyone wants to help there...17:40
johnsomOh definitely, if we don't get started earlier17:40
johnsom#topic Open Discussion17:40
*** openstack changes topic to "Open Discussion (Meeting topic: Octavia)"17:40
*** cloudrancher has joined #openstack-meeting17:40
johnsomSince we have twenty minutes left, any other topics today?17:41
johnsomOh!17:41
xgerman_?17:41
johnsomFYI, there is another L3 Active/Active discussion scheduled for Friday.17:41
cpugaI'd like to request a review on flavor spec #link https://review.openstack.org/#/c/392485/17:42
johnsom#link http://lists.openstack.org/pipermail/openstack-dev/2017-July/119565.html17:42
xgerman_Ok, on th Active-Active front I reworked https://review.openstack.org/#/c/313006/ to make the distributor table look more like the one jsniez proposed17:42
*** iyamahat has joined #openstack-meeting17:43
xgerman_comments welcome17:43
johnsomcpuga it looks like there is a docs error, the new file needs to be added to an index.17:43
cpugaI'll take care of that, thx.17:44
xgerman_yeah, I think we are close with flavors17:44
xgerman_but that also hinges on the 3rd party interface17:44
johnsomIt will go in here: https://github.com/openstack/octavia/blob/master/doc/source/contributor/index.rst17:44
johnsomActually, that is odd since I have a wild card....17:45
*** rajathagasthya has quit IRC17:45
johnsomOh, I renamed the directory for the new docs migration stuff17:45
jnieszyes, I remember having to change mine from 1 to 1.017:46
*** rajathagasthya has joined #openstack-meeting17:46
johnsomYeah, flavors is on our priority review list.17:46
johnsomYeah, sorry about that.  The docs stuff is all getting changed due to the docs team reducing scope.17:46
johnsomOctavia docs should be pretty stable now.17:47
johnsomOther topics or concerns?17:47
*** annegentle has quit IRC17:47
johnsom#link https://etherpad.openstack.org/p/Octavia-Pike-priority-patches17:48
jnieszxgerman_ the change looks good to support [] for lb and amphora for distributor model17:48
johnsomOk, off to do reviews!17:48
xgerman_thanks17:48
*** diablo_rojo has joined #openstack-meeting17:48
johnsom#endmeeting17:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:48
openstackMeeting ended Wed Jul 12 17:48:46 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/octavia/2017/octavia.2017-07-12-17.00.html17:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/octavia/2017/octavia.2017-07-12-17.00.txt17:48
openstackLog:            http://eavesdrop.openstack.org/meetings/octavia/2017/octavia.2017-07-12-17.00.log.html17:48
*** lpetrut has quit IRC17:49
*** sanfern has left #openstack-meeting17:50
*** wxy- has quit IRC17:51
*** gyee has joined #openstack-meeting17:53
*** yamahata has joined #openstack-meeting17:54
*** evgenyf has quit IRC17:55
*** electrofelix has quit IRC17:57
*** jamesden_ has quit IRC18:00
*** jamesdenton has joined #openstack-meeting18:01
*** e0ne has joined #openstack-meeting18:04
*** yamamoto has joined #openstack-meeting18:04
*** ekcs has joined #openstack-meeting18:05
*** annegentle has joined #openstack-meeting18:09
*** lpetrut has joined #openstack-meeting18:10
*** ramineni_ has quit IRC18:14
*** jprovazn has quit IRC18:14
*** Patifa has joined #openstack-meeting18:17
*** yamamoto has quit IRC18:20
*** yamamoto has joined #openstack-meeting18:21
*** sshank has joined #openstack-meeting18:22
*** slaweq_ has joined #openstack-meeting18:22
*** Rockyg has quit IRC18:23
*** yamamoto has quit IRC18:26
*** slaweq_ has quit IRC18:27
*** jniesz has left #openstack-meeting18:29
*** lpetrut has quit IRC18:41
*** julim has quit IRC18:44
*** Sukhdev has joined #openstack-meeting18:45
*** makowals has quit IRC18:46
*** sshank has quit IRC18:47
*** lpetrut has joined #openstack-meeting18:48
*** Swami has joined #openstack-meeting18:50
*** rajathagasthya has quit IRC18:50
*** annegentle has quit IRC18:57
zara_the_lemur__does anyone feel like having a storyboard meeting?18:58
zara_the_lemur__I will say that if we cancel this week, we should definitely do one next week18:58
diablo_rojoStill following convos on watcher, tricircle, and octavia. No updates there.18:58
diablo_rojoI updated my patch and am waiting for reviews currently18:58
zara_the_lemur__right let's do a meeting so it's in the logs but skip straight to open discussion and keep it short18:59
*** baoli has quit IRC18:59
zara_the_lemur__#startmeeting storyboard18:59
openstackMeeting started Wed Jul 12 18:59:45 2017 UTC and is due to finish in 60 minutes.  The chair is zara_the_lemur__. Information about MeetBot at http://wiki.debian.org/MeetBot.18:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:59
*** openstack changes topic to " (Meeting topic: storyboard)"18:59
openstackThe meeting name has been set to 'storyboard'18:59
zara_the_lemur__#topic Open Discussion18:59
*** openstack changes topic to "Open Discussion (Meeting topic: storyboard)"18:59
zara_the_lemur__#info diablo_rojo has updated her patch and is waiting for reviews currently19:00
*** baoli has joined #openstack-meeting19:00
*** baoli has quit IRC19:00
SotKo/19:00
zara_the_lemur__o/19:01
zara_the_lemur__tristanC raised a point about the webclient tarball in-channel19:01
zara_the_lemur__I haven't had time to look at it yet19:01
SotKme neither I'm afraid19:01
zara_the_lemur__but I seem to recall him or someone else raising the same point a little while ago19:01
* diablo_rojo has reviews on her todo list19:01
*** baoli has joined #openstack-meeting19:01
zara_the_lemur__I'm hoping to have more time to get to reviews over the next few weeks19:02
*** annegentle has joined #openstack-meeting19:02
zara_the_lemur__though I also started learning the violin so we'll see how that goes19:02
*** dbecker has quit IRC19:02
zara_the_lemur__erm I mean I am a very busy professional individual with all the softwares19:02
fungii'm here, just also troubleshooting stuff in #-infra19:02
zara_the_lemur__hi fungi! :)19:02
zara_the_lemur__I am lurking in there with interest atm19:03
*** sshank has joined #openstack-meeting19:03
zara_the_lemur__I am also lurking on the nova bugs triage thread19:03
SotKreviews would be great because then I wouldn't have the vague feeling of stressing folk if I send patches :)19:03
*** coolsvap has quit IRC19:03
zara_the_lemur__oh no please do send them19:04
* SotK is also watching that thread with interest19:04
zara_the_lemur__I'm just rubbish19:04
zara_the_lemur__there's an interesting discussion about tags atm19:04
SotK(ha, I don't actually have any to send rn anyway)19:04
zara_the_lemur__(okay, when you stop sending them it makes it worse because I think my failure to review has totally demotivated you)19:04
zara_the_lemur__I'll find the link to that ml discussion19:05
*** sshank has quit IRC19:05
zara_the_lemur__I don't yet have thoughts in a coherent enough form to actually *post* on it19:05
*** annegentle has quit IRC19:06
zara_the_lemur__#link http://lists.openstack.org/pipermail/openstack-dev/2017-July/119608.html19:06
zara_the_lemur__and our outstanding reviews can be found over at:19:07
zara_the_lemur__#link https://review.openstack.org/#/q/project:openstack-infra/storyboard-webclient19:07
zara_the_lemur__#link https://review.openstack.org/#/q/project:openstack-infra/storyboard19:07
diablo_rojoSotK, I addressed all your comments from before :) So its ready to go again.19:08
zara_the_lemur__other things... i have not yet registered for the next ptg and probably should :/19:08
SotKdiablo_rojo: thanks! I will test it out in the near future19:08
fungion the nova bug triage thread, i didn't have a great followup to sdague's last reply there because it's not completely clear what combination of behaviors he's looking for (maybe he feels there should be task tags instead of tagging at the story level?)19:08
fungiseems like in shared jurisdiction situations there's a semantic collision over tag names19:09
SotKyeah19:09
zara_the_lemur__yeah, I wondered how solvable that would be by any tool19:09
fungiso a story with tasks for nova and ironic, to use his example, may have story tags set in ways that ironic bug triagers expect which conflicts with what nova bug triagers expect from the same tag names?19:10
SotKI got the impression of a need for per-project-involved-in-a-story tags, but idk for sure (hence not yet formulating a reply myself)19:10
zara_the_lemur__yeah, I'm wondering how compatible cross-project issues can be if the semantics can overlap or contradict for the same terms between projects19:11
zara_the_lemur__*cross project issues with understanding19:11
zara_the_lemur__sorry that sentence was a mess19:11
zara_the_lemur__now y'all can see how I haven't got to replying yet :D19:11
zara_the_lemur__I guess I'm wondering if at some point you might just have to enforce standard names... but I don't know how realistic that is19:12
*** arnewiebalck_ has joined #openstack-meeting19:12
diablo_rojoStandard names or like formalized list of tags?19:13
zara_the_lemur__yeah, effectively that19:13
zara_the_lemur__though then maybe that just pushes the problem elsewhere19:13
zara_the_lemur__ie: you get a long discussion about what should be on the list19:13
zara_the_lemur__so the disagreements just move to that19:14
fungialternatively, as we've suggested before, just prefix tags you expect to only have meaning for your team19:14
zara_the_lemur__yeah, personally that's my preferred option19:14
*** e0ne has quit IRC19:14
zara_the_lemur__though I wonder how safe the prefixes will be19:14
fungiso instead of the "compute" tag, nova can set "nova-compute" on stories and ironic can set "ironic-compute" on them and avoid stepping on each others toes19:15
zara_the_lemur__yeah19:15
diablo_rojoThat seems like a good solution to me19:15
zara_the_lemur__I have in the past used storyboard-foo, though for different reasons (at that time it made it easier to find them)19:15
fungienforcing that through some sort of acl isn't probably in the cards any time in the foreseeable future, but as an agreement across projects it's probably fine19:16
* zara_the_lemur__ wonders how likely people are to tag things and not follow the convention19:16
SotKseems sensible to me too19:16
diablo_rojoThat works for me.19:16
*** yamamoto has joined #openstack-meeting19:16
zara_the_lemur__I figure the most likely people to tag things will be triage teams anyway19:17
zara_the_lemur__who would know it19:17
fungilike, we agree as a community that the nova bug triagers are well within their rights to set or unset nova-.* tags on stories even if originally set by other teams19:17
*** harlowja has quit IRC19:17
*** david-lyle has quit IRC19:17
*** david-lyle has joined #openstack-meeting19:17
zara_the_lemur__that seems fine to me (I also think it's probably something we can only evaluate by trying out)19:18
fungiso if someone at random puts a nova-foo tag on a particular story, and the nova bug triagers subsequently unset that tag, then that's their perogative19:18
*** abalutoiu_ has joined #openstack-meeting19:18
zara_the_lemur__yeah. I do wonder if they'd end up spending a lot of time on that, but I really don't know and I'd *expect* most people wouldn't tag unless they'd been asked to19:19
zara_the_lemur__I think it's pretty rare for people to give more information than they need to to begin with19:19
* SotK agrees19:19
zara_the_lemur__(I'm thinking out loud a bit hehe)19:19
*** adisky__ has quit IRC19:20
zara_the_lemur__project renames could be painful but then they're always painful19:20
fungiless painful for sb than in most other places. can do it with a very simply update query (or several)19:20
fungis/simply/simple/19:21
*** timburke has joined #openstack-meeting19:21
fungino service downtime, no filesystem rearrangement, no new urls19:21
diablo_rojoEverything you could want.19:22
* zara_the_lemur__ was thinking of 'search by tag'19:22
*** abalutoiu has quit IRC19:22
zara_the_lemur__eg: https://storyboard.openstack.org/#!/story/list?tags=low-hanging-fruit19:22
zara_the_lemur__if that read something like tags=nova-foo19:22
zara_the_lemur__but I agree it's not technically difficult to change19:22
*** toscalix has quit IRC19:23
zara_the_lemur__just something to consider for those with 'find our bugs here' pages and the like19:23
*** slaweq_ has joined #openstack-meeting19:23
zara_the_lemur__but I also think that's the prerogative of those who want to change their project name19:24
SotKyeah, I think if folk are renaming their project its acceptable to make them need to change a link with the old name in19:26
zara_the_lemur__hahaha19:26
*** slaweq_ has quit IRC19:26
*** slaweq_ has joined #openstack-meeting19:26
* zara_the_lemur__ feels that there is consensus to say that 'use prefixes' is the official storyboard stance19:27
diablo_rojo_phonYep!19:28
zara_the_lemur__now I have not really done anything but feel a sense of accomplishment; we have an 'official stance' on something; this is great19:28
fungiit's good to feel all official and stuff19:29
*** e0ne has joined #openstack-meeting19:29
zara_the_lemur__:) I think I don't have anything else to talk about19:30
*** armstrong has quit IRC19:30
zara_the_lemur__so anyone got something they want to discuss?19:30
*** annegentle has joined #openstack-meeting19:30
zara_the_lemur__otherwise I'll end this meeting in 3 minutes19:30
SotKI don't think I have anything19:30
diablo_rojo_phonNada.19:31
zara_the_lemur__:)19:31
zara_the_lemur__1 minute remaining; anyone having anything nice for tea?19:32
zara_the_lemur__apparently not19:32
zara_the_lemur__#endmeeting19:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:32
openstackMeeting ended Wed Jul 12 19:32:45 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2017/storyboard.2017-07-12-18.59.html19:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2017/storyboard.2017-07-12-18.59.txt19:32
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2017/storyboard.2017-07-12-18.59.log.html19:32
zara_the_lemur__thanks, everyone! :)19:32
SotKthanks!19:32
diablo_rojo_phonThank you :)19:35
fungithanks!19:36
*** awaugama has quit IRC19:40
*** slaweq_ has quit IRC19:43
*** slaweq_ has joined #openstack-meeting19:43
*** cloudrancher has quit IRC19:44
*** cloudrancher has joined #openstack-meeting19:45
*** slaweq_ has quit IRC19:48
*** slaweq_ has joined #openstack-meeting19:49
*** cpuga has quit IRC19:52
*** yamamoto has quit IRC19:54
*** baoli has quit IRC19:56
*** ekhugen_alt has joined #openstack-meeting19:59
ekhugen_alt#startmeeting wos_mentoring20:00
openstackMeeting started Wed Jul 12 20:00:13 2017 UTC and is due to finish in 60 minutes.  The chair is ekhugen_alt. 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: wos_mentoring)"20:00
openstackThe meeting name has been set to 'wos_mentoring'20:00
ekhugen_altHi, who's here for women of openstack mentoring?20:00
*** MeganR has joined #openstack-meeting20:00
*** baoli has joined #openstack-meeting20:00
*** baoli has quit IRC20:00
ekhugen_altHi Megan!20:00
MeganRHello!20:01
ekhugen_altI think so far it's just the two of us20:02
*** harlowja has joined #openstack-meeting20:02
diablo_rojoAnd me :)20:02
MeganRand that makes three!  :)20:02
ekhugen_altHi Kendall!20:03
diablo_rojoPractically a party :)20:03
* ekhugen_alt gets her party hat and kazoo20:03
diablo_rojoHello ekhugen_alt  :)20:03
* diablo_rojo turns on the strobes and picks a spotify playlist20:04
ekhugen_altI think last week we were talking about restructuring the long term mentoring program20:04
*** NicoleH has joined #openstack-meeting20:04
ekhugen_altHi Nicole!20:04
NicoleHHi Emily!20:04
diablo_rojoMan, four people, now it is a party.20:04
NicoleHHow are you enjoying your summer?!20:04
NicoleHHaha!20:05
ekhugen_altmy summer is going too fast20:05
ekhugen_althow is it a week past independence day?20:06
MeganRYes, way too fast!20:06
* diablo_rojo was moving over the 4th 20:06
NicoleHCouldn't agree with you guys more!20:06
NicoleHHope it went smoothly, diablo_rojo!20:06
ekhugen_althow's the new apartment diablo_rojo?20:06
ekhugen_altdid you get all the computer equipment sorted?20:06
diablo_rojoMade it to Seattle safe and sound :) The car getting totaled the week before wasn't so awesome..20:06
ekhugen_altoh no! are you okay though?20:07
*** baoli has joined #openstack-meeting20:07
diablo_rojoYeah, got some xrays and it was all okay. Should probably go to a chiropractor though too.20:07
MeganRoh wow - I am sorry to hear that, like moving isn't stressful enough20:07
MeganRYes, deal with it now, so it isn't work 12 months from now20:07
ekhugen_alteesh, yeah, that sounds really tough!  hope you feel better soon!20:08
diablo_rojoMeganR, that was my thought. Though, down one car, I only had to get the moving truck to the new place, not both vehicles20:08
*** vishnoianil has joined #openstack-meeting20:08
NicoleHYikes!20:08
*** makowals has joined #openstack-meeting20:08
diablo_rojoIt was a nice drive through South Dakota, Wyoming, Montanta and Idaho to Washington :)20:09
MeganRoh, I hope you took photos during that drive20:09
NicoleHWelcome to the west coast. I love living in the Pacific Northwest. I'm only 3.5 hrs south, in Portland.20:10
ekhugen_altoh nice, that does sound like a pretty drive20:10
diablo_rojoMeganR, lots of snaps in snapchat, a few actual photos20:10
diablo_rojoNicoleH, OH MAN! I will keep that in mind when I go for workdays with other Foundation people.20:11
diablo_rojoYou could join us :)20:11
NicoleHPerfect -- I'd love to!20:11
NicoleHLet me know whenever you're in Portland. It'd be great to get together!20:11
*** raildo has quit IRC20:12
ekhugen_altso last week we were talking about restructuring the long term mentoring program20:14
ekhugen_altI think we talked about making it easier by doing check-ins every 2 months20:14
ekhugen_altand only giving people 7 days to respond before we unmatched them, no second chances or anything20:14
*** jamesdenton has left #openstack-meeting20:14
NicoleHsounds good on this end.20:15
NicoleHthat way, we'll know their level of commitment.20:16
NicoleHor, seems so, anyway!20:16
ekhugen_altso I think now we were talking about what to do for the check-ins, how to make them more helpful20:16
*** rajathagasthya has joined #openstack-meeting20:17
ekhugen_altlike do we want to try to schedule a half hour meeting with mentor and mentee20:18
ekhugen_altand coach them through any issues they're having?20:18
NicoleHi think it's helpful to make a "human" check-in, rather than via email or online.20:19
NicoleHhow do others feel?20:19
*** abalutoiu_ has quit IRC20:20
ekhugen_altdiablo_rojo, meganr any thoughts?20:23
MeganRI like the idea of the human check-in20:24
diablo_rojoYeah that sounds good20:24
*** sshank has joined #openstack-meeting20:24
*** jkilpatr has quit IRC20:25
diablo_rojoSounds good, and I am willing to help out with those :)20:25
ekhugen_altdo we think it would be good to have a script or suggestions of how to go through the meeting, or do we want to wing it for the first few and then later work on standardizing20:26
*** sshank has quit IRC20:29
*** sshank has joined #openstack-meeting20:29
NicoleHi think it would help us to have a list of a few questions that we ask. the conversion could go in different directions, and we'll learn from that, but this short list to start out with may help guide us initially.20:29
NicoleH*conversation20:29
*** e0ne has quit IRC20:29
MeganR+1 - and as a way to make certain nothing gets overlooked (more for my benefit, if I do these)  :)20:30
diablo_rojoI wouldnt have more than like three prompt questions to fall back on, but I think it would be okay to wait to figure out what those might be20:30
*** arnewiebalck_ has quit IRC20:31
ekhugen_altso could the questions be things kind of based on the forms?  like how often are you meeting, what are you finding is the best way to communicate, and then any questions or concerns?20:32
*** e0ne has joined #openstack-meeting20:33
*** makowals has quit IRC20:34
diablo_rojoYeah I think that would be a good place to start20:34
NicoleHsounds good!20:36
ekhugen_altso anything else to iron out before we talk about starting another round of long term mentoring?20:36
ekhugen_altwant to update the form at all? https://openstackfoundation.formstack.com/forms/mentor_mentee_signup_pre_barcelona20:37
NicoleHalso, in terms of questions, it'd be nice to get a sense of the discussions between the mentor & mentee, and a sense for how the mentor has helped the mentee.20:37
ekhugen_alt+1 nicole20:39
*** jkilpatr has joined #openstack-meeting20:41
*** pchavva has quit IRC20:44
ekhugen_altso maybe next week (or do we want to meet in 2 weeks?) we'll finalize any details for the next round of long term mentoring?20:45
ekhugen_altand start to get signup emails sent out?20:45
*** rledisez has joined #openstack-meeting20:46
diablo_rojoYes that sounds good. Next week :)20:47
diablo_rojoThe sooner we get rolling on this, the easier it will be to stop ignoring it ;)20:48
ekhugen_altokay, cool,20:48
ekhugen_altthanks everyone!20:48
diablo_rojoThanks Emily!20:49
NicoleHthanks, everyone!20:49
*** NicoleH has quit IRC20:49
ekhugen_alt#endmeeting20:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:49
openstackMeeting ended Wed Jul 12 20:49:55 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/wos_mentoring/2017/wos_mentoring.2017-07-12-20.00.html20:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/wos_mentoring/2017/wos_mentoring.2017-07-12-20.00.txt20:50
openstackLog:            http://eavesdrop.openstack.org/meetings/wos_mentoring/2017/wos_mentoring.2017-07-12-20.00.log.html20:50
*** pcregut1 has joined #openstack-meeting20:51
*** pcregut1 has left #openstack-meeting20:51
*** e0ne has quit IRC20:53
*** yamamoto has joined #openstack-meeting20:54
*** cschwede has joined #openstack-meeting20:58
*** kota_ has joined #openstack-meeting20:58
*** acoles has joined #openstack-meeting20:59
*** patchbot has joined #openstack-meeting20:59
*** torgomatic has joined #openstack-meeting21:00
notmynameswift team meeting time21:00
notmyname#startmeeting swift21:00
openstackMeeting started Wed Jul 12 21:00:08 2017 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
notmynamewho's here for the swift team meeting21:00
openstackThe meeting name has been set to 'swift'21:00
acoleshere21:00
jungleboyj@!21:00
_pewp_jungleboyj ( ^_^)/21:00
torgomatichi21:00
*** jrichli has joined #openstack-meeting21:00
cschwedeo/21:01
tdasilvahi21:01
*** yamamoto has quit IRC21:01
mattoliverauo/21:01
jrichlio/21:01
kota_hi21:01
mathiasbo/21:01
notmynamehi jrichli!21:01
jrichlinotmyname o/21:02
*** jtomasek_ has quit IRC21:02
*** m_kazuhiro has joined #openstack-meeting21:02
notmynameok, so just 9 hours ago, half of you were in the 0700 meeting where I said the 2100 meeting would be exactly the same :-)21:02
jungleboyj*Laughing*21:03
notmynamewelcome :-)21:03
cschwedenotmyname: shall we leave then? ;)21:03
notmynamecschwede: you should stay. everyone else can go ;-)\21:03
cschwedelol21:03
tdasilvalol, cschwede sounded like that ;)21:03
*** iyamahat_ has joined #openstack-meeting21:03
notmynameI just figured you wanted sleep/breakfast/dinner/whatever21:03
notmynameok, let's go through it then21:04
torgomatichere's a small difference for you: 3091a594d6dc0bd360f498af5bef4c7121:04
notmyname#link https://wiki.openstack.org/wiki/Meetings/Swift21:04
*** iyamahat has quit IRC21:04
mathiasbrepetition is the mother of all learning!21:04
torgomaticthat's 128 random bits, just to shake things up :)21:04
notmynametorgomatic: whoa!21:04
*** Sukhdev has quit IRC21:04
jungleboyjnotmyname:  They didn't trust you.21:04
notmynametorgomatic: it's unlikely any meeting ever will have that string again21:04
notmyname#topic Denver PTG21:04
*** openstack changes topic to "Denver PTG (Meeting topic: swift)"21:05
notmynamethe PTG is coming up21:05
claygi still haven't signed up - but will today21:05
notmynametopic etherpad is at21:05
jungleboyj3091a594d6dc0bd360f498af5bef4c7121:05
notmyname#link https://etherpad.openstack.org/p/swift-ptg-queens21:05
notmynameif you haven't signed up for the ticket or hotel, please do so soon. today would be good21:05
notmynameall the links can be found at https://www.openstack.org/ptg21:05
* tdasilva imagines everybody will copy and paste that string next week21:06
jrichlitdasilva, lol21:06
notmynamefor the week's schedule, monday and tuesday will be more of an emphasis on cross-project topics, and we'll have a room for swift wed-friday21:06
jungleboyjtdasilva:  Wondered if anyone was going to comment on me being a smart-a$$21:06
tdasilvajungleboyj: heh ;)21:06
*** iyamahat_ has quit IRC21:07
*** iyamahat has joined #openstack-meeting21:07
notmynameand I'm sure that if there are swift people together on mon-tues without something else going on, we'll grab a table, corner, or room21:07
notmynamealso, please encourage any ops you see to attend the PTG21:07
notmynameif you have to make a choice between the PTG and the sydney summit, choose the ptg21:07
notmynameI expect to have very light attendance at the sydney summit. the ptg will be far better for contributors (devs and ops) to work together21:08
notmynamehonestly, it's still an open question if I'll be going to the summit. don't know yet21:09
*** Manuel_112 has joined #openstack-meeting21:09
notmynameany questions about the ptg?21:09
*** galstrom is now known as galstrom_zzz21:09
notmynameok. moving on then21:09
notmyname#topic bug triage21:09
*** openstack changes topic to "bug triage (Meeting topic: swift)"21:09
notmynamecschwede has been doing some great work on organizing the work that needs to be done to get a handle on our bugs21:10
notmynamethere's some tools available at21:10
notmyname#link https://github.com/sdague/nova-bug-tools#existing-tools21:10
notmynamelook at the bottom of that page21:10
notmynamecschwede: can you give a quick recap of what we got to at the previous meeting?21:10
cschwedesure21:11
cschwedethere is one specific tool that runs over all bugs and can close them if they are too old. i dry-run it and this is the result (ordered by me):21:11
cschwede#link http://paste.openstack.org/show/615138/21:11
cschwedethere are a few more tools that can do some nice tricks like searching for gerrit reviews and attach them to the bugs21:12
cschwedeor update the state depending on the patch state21:12
cschwedehowever, these tools would only help with a small number of bugs (15-35, depending on what we want to do)21:12
*** edmondsw has quit IRC21:12
notmynamecschwede: nicely cleaned up list :-)21:13
*** edmondsw has joined #openstack-meeting21:13
cschwedethe tool that produced above linked list can be used to shrink the list, but it would be automatically. ie we have only a very limited influence on it21:13
notmynamewhat's the first column in that list?21:14
cschwedeage in days21:14
notmynameah21:14
*** edmondsw_ has joined #openstack-meeting21:14
*** edmondsw has quit IRC21:14
claygyeah i could work on a chunk!21:14
cschwedeso, one idea we had this morning was to paste the list into an etherpad, and everybody grabs a chunk of that list and works on that21:14
cschwedeto avoid duplicate work21:15
clayg*brilliant*21:15
*** edmondsw_ has quit IRC21:15
cschwedei think most of us are a little bit afraid of closing bugs without reviewing them21:15
*** andreas-f has joined #openstack-meeting21:15
*** lennyb has quit IRC21:15
claygroughly - terrified - why? - don't know21:15
*** bknudson has quit IRC21:15
*** edmondsw has joined #openstack-meeting21:15
claygwhat if the bug report was *the key* - THE KEY!?21:16
notmynameclayg: yep, that's exactly what we said this morning :-)21:16
cschwedeclayg: there might be some "good/nice to have" bugs in that list21:16
cschwedeand we don't want to autoclose them21:16
cschwede(we can exclude bugs with a tag like wishlist or low-hanging-fruit, but thats the minority of bugs)21:16
cschwededid i forget anything from this morning?21:17
claygcommunity todo lists are weird... on MY todo lists I can say "nope not today" or even "ah ^&*# it, it's not gunna get done" - it's harder to do that when the "who is responsible for this?" is *wide* open21:17
*** zaitcev has joined #openstack-meeting21:17
notmynamecschwede: I like the idea of chunking up the list of bugs. assign names to them for triage, and track it every meeting for accountability21:17
claygnotmyname: don't forget the part about "grab a list" to avoid duplicate work21:18
jungleboyjcschwede:  Cinder has just blanket closed things in the past.  The ones someone cares about get re-opened.  ;-)21:18
notmynameright. that's what I mean by assing names for triage. eg you take 1-15, I take 15-30, etc21:18
cschwedei mean it's "only" 300 bugs. if all active cores tackle at least 5 bugs per week, we're nearly done in Denver.21:18
claygnotmyname: it would help to have some common guidelines tho - so people can feel confidient making decisions independently w/o risk of reprisal?21:18
cschwedeclayg: good point! +121:19
claygcschwede: that's a great way to frame it!  I want to do 5 for sure - where is tdasilva ?21:19
cschwedewe should add a tag "needs-consensus" or sth like that21:19
*** kylek3h has quit IRC21:19
notmynameacoles mentioned that having some sort of voting in LP would be great, to avoid that very situation of one person only seeing or not seeing something21:19
cschwedenotmyname: add a specific tag for it?21:19
*** edmondsw has quit IRC21:20
claygtdasilva: you have been *Killing* it on bug triage!?  I see updates form lp and I constantly screaming at my computer "heck yes!  tdasilva!  get some!  go go go!"21:20
notmynamewhat if we assigned overlapping sets? eg I do 1-5, clayg does 3-8, cschwede does 6-10, etc21:20
acolesif we're tracking on an etherpad then if I am 50/50 about a bug I'll just mark it on etherpad and throw it back for second opinion?21:20
cschwedenotmyname: we split it into chunks in the etherpad because of that21:20
*** dprince has quit IRC21:20
cschwedenotmyname: and write our names to each chunk21:20
acoleswhich is nuts because we have launchpad, so yes maybe a tag would do it21:20
claygnotmyname: modulo strategies are subject to ordering issues21:20
tdasilvaclayg: yeah, but I do fear that I will get yelled at at some point21:20
notmynametdasilva: here's me yelling: "YOU'RE DOING A GREAT JOB! KEEP IT UP!"21:21
cschwedetdasilva: don't worry, rock on :D21:21
claygtdasilva: ^ that 100%21:21
tdasilvamy fear with needs-consensus tag, is that then it forces everyone to look at (almost) everything ??21:21
notmynameyeah21:21
acolestdasilva: we will escort you at all times at PTG :)21:21
tdasilvaacoles: lol21:21
notmynameso what acoles just said makes sense. most are likely to not need multiple people. if so, make a note on the etherpad, someone else will look at it on next block assignments21:22
claygtdasilva: i was hoping you could give more guidance like "there are what I see as 3 broad classes of bugs ..."21:22
tdasilvamaybe instead of assiging chunks to an individual, we can assign chunks to a group of 3 people21:22
claygand tell us a little bit about what's out there - and how you're taking that on?21:22
claygbasically - what is your secrets you brilliant man!?21:22
claygthen we can all say "yes, that 100% - everyone be like tdasilva - grab 5 and ask 'what would tdasilva do?'"21:23
notmynametdasilva: build a ring. each of us are drives. make the replica count the size of the chunks. part number is mapped to bugs. let get_nodes() sort it out ;-)21:23
claygtdasilva: notmyname: cschwede and this doesn't have to be an on-the-spot thing?21:23
*** thorst has quit IRC21:23
tdasilvanotmyname: perfect!21:24
mattoliverauLol21:24
kota_are we devices? :)21:24
torgomaticnotmyname: this makes an excellent incentive to lose weight...21:24
claygoh dear21:24
notmynametorgomatic: lol21:24
tdasilvarofl21:24
*** fnaval has quit IRC21:24
acolestdasilva: can i be in your group of 3? ;) I think what notmyname said - if in doubt leave a comment (e.g. I think this is invalid but...) and leave on etherpad, otherwise close it and delete from etherpad??21:24
notmynameok ok ok21:24
notmynamecan cschwede keep going on his data mining and build an etherpad?21:25
cschwedesure21:25
notmynameat first glance, I really like the organization in the pastebin21:25
claygI just want some rough guage of what I'm doing when I grab my 5 bugs?  is the goal to... reproduce the issue and add context?  decide if this is a bug or some feature that someone asked for but isn't working on?  Is it *terrible* and everything is mostly bad until it's fixed (think every client disconnect resource leak bug we've ever had and the current open ones)?21:25
*** efried has quit IRC21:25
*** trozet has quit IRC21:26
cschwedenotmyname: let me know if we need some other data, different groups or whatever21:26
notmynamefirst goal is to close it if it's obviously no longer valid or already fixed21:26
claygacoles: that's the ticket!  so one goal would be "close invalid bugs" - maybe 50% are invalid at this point?  Maybe it's 70%!?21:26
claygnotmyname: good restatement21:27
acolesclayg: my 2pence worth - first pass, categorize e.g. wishlists, invalids; second pass, try to confirm21:27
notmynamesecond is to repro it enough to confirm it or put it in needs info21:27
cschwedei can add the data from the other tools, like commits that mention that bug etc21:27
notmynamethird (bonus points) is to repro well enough to easily construct a failing test for it21:27
*** lennyb has joined #openstack-meeting21:27
acolesclayg: it's like we need handoffs_only to get rid of the crap ;)21:27
notmynameacoles: yeah, that's good21:27
claygtdasilva: have you *found* some of these "obviously invalid" bugs!?21:27
claygtdasilva: or do you have to more or less try and repo to be like "I'm ~80% sure this is fixed because it sure seems to not be a problem as described?"21:28
notmynameeg "mirror trans-id to openstack-request-id https://api.launchpad.net/1.0/bugs/1572786" is done and released already21:28
notmynameso there's an example21:28
claygI thought I saw some going from "fix released" to like "no srly fix released" or w/e the lp terms are?  Can't we just bot that state change away?  Does it *matter* to anyone what the difference is!?21:28
tdasilvaclayg: a lot of what I have been closing recently was bugs that were marked as fix committed, but never got set to fix released21:29
notmyname"fix committed" was something that used to be used by the openstack bots. don't use that. it's either open, being worked on, or "fix released"21:29
tdasilvaI think there's a bot to make that change, but it doesn't seem to change the state if the bug is not assigned to anyone21:29
claygwtf is up with hudson-openstack -> "This issue was fixed in the openstack/swift 2.11.0 release."21:30
claygcan we just *search* for that message!?  why is that bug still "in progress"21:30
*** lpetrut has quit IRC21:30
claygtdasilva: yeah - so I don't want my 5 bugs to be 3 of those - that's just lame - is that really where we're at?21:31
*** iyamahat_ has joined #openstack-meeting21:31
notmynameso far, what we've discussed/decided from this meeting and the 0700 one is that (1) there's some mapping from gerrit to LP that can happen via script and cschwede is doing that and (2) cschwede will group the old LP bugs of questionable status into an etherpad and we'll start triaging them a block at a time21:32
notmynamedoes that make sense?21:32
cschwedetdasilva: i didn't look into them, were the fixes really released?21:32
*** iyamahat has quit IRC21:32
notmynamedid I miss something?21:32
claygcschwede: have you looked at the source of any of these scripts you've been running - does it make more sense to apply humans to this or is the raw materials there to do this from the command line?21:32
cschwedeclayg: these scripts are pretty easy to hack, i already did that a bit21:32
*** Manuel_112 has quit IRC21:32
*** trozet has joined #openstack-meeting21:32
tdasilvacschwede: clayg but I think I closed all of the now :)21:32
claygcschwede: hellz yeah you did - awesome21:32
claygtdasilva: ah, ok - that's good!21:33
tdasilvaI left only one that was related to swift3 and i wasn't sure about21:33
*** Manuel_112 has joined #openstack-meeting21:34
claygnotmyname: I think you're summary is correct then - I think i side tracked on a particularlly weird/dumb state that you pointed at and tdasilva has mostly cleaned up - so let's move forward with the blocks - and we all do 5 for next week - then report back and correct!?21:34
claygcschwede: tdasilva: you guys are amazing!?  where's the etherpad link - i want to pick my 5 now - i want good ones21:34
tdasilvasounds good21:34
claygtorgomatic: don't you try and get my good ones21:34
notmynamecschwede is on the etherpad. he's about to go to bed, but he'll put it up tomorrow, I hope ;-)21:34
cschwedeclayg: there is no etherpad yet, but i will update the list and prepare one tomorrow21:34
notmyname(see what I did there?)21:34
claygoh...21:35
claygok, good call.  cschwede ML/async maybe then?21:35
cschwedeclayg: sure!21:35
claygand thanks again (and again and again and again!)21:35
acoles+ thank cschwede and tdasilva21:35
cschwedeno problem, you're welcome!21:35
mattoliverau+121:35
notmyname#topic docs migration21:36
*** openstack changes topic to "docs migration (Meeting topic: swift)"21:36
tdasilvanotmyname: just one more thing21:36
tdasilvaabout bugs21:36
clayg#action thank cschwede and tdasilva for amazing efforts and great results for swift bug triage21:36
acolesnotmyname: are you going to plot graphs of our bug burndown ;)21:36
notmynametdasilva: what's up?21:36
tdasilvaso, I think doing this fire drill of triaging existing bugs is great, but it's like day1, I think long term we should also thing about some kind of sane process to keep triaging21:37
tdasilvaonce we have (hopefully) gone through this big list, how do we not get into this state again?21:37
notmynamegood point21:37
tdasilvawe don't need to answer that now, but maybe a good discussion for ptg21:37
*** efried has joined #openstack-meeting21:38
notmynameI hope that going through the old ones will help us exercise our triage muscles so it's not as painful as ongoing work21:38
notmynameand yes, it's already listed on the topic etherpad :-)21:38
notmynametdasilva: cschwede: I really hope you can help lead that topic at the ptg21:38
tdasilvaheh, I see what you did there :)21:39
notmynameok, for docs migration...21:39
notmynameI said a lot of words this morning at http://eavesdrop.openstack.org/meetings/swift/2017/swift.2017-07-12-07.00.log.html#l-14221:39
*** fnaval has joined #openstack-meeting21:39
notmynamebut the summary of that summary is that we're taking on a lot more docs, and it's a really really good thing21:39
claygand I also hope we can remember that as much as good ideas/tools/process - effective bug triage takes elbow grease too!  So be prepared to pitch in - it's totally worth it!21:39
*** fnaval has quit IRC21:39
notmynamebut it will result in some more work, of course, and it will result in some existing docs links breaking21:40
claygtdasilva: cschwede: thanks for being doers/leaders!21:40
*** awaugama has joined #openstack-meeting21:40
*** fnaval has joined #openstack-meeting21:40
claygnotmyname: from my desk that host is broke?21:40
notmynameweird. here too, but I had it pulled up already21:41
notmynameit's ok, it's fine to read async later21:41
notmyname#topic upcoming releases21:41
*** openstack changes topic to "upcoming releases (Meeting topic: swift)"21:41
notmynameI'd like to tag swift and swiftclient as early as next week, if possible21:42
notmynameI think swiftclient is possible, swift slightly less likely (but still possible)21:42
notmyname#link https://wiki.openstack.org/wiki/Swift/PriorityReviews21:42
notmynamepriority reviews has new "next release" sections21:42
notmynamefor swiftclient, patch 449771 needs reviews21:43
patchbothttps://review.openstack.org/#/c/449771/ - python-swiftclient - Buffer reads from disk21:43
*** rbudden has quit IRC21:43
notmynamepatch 475038 will get another patch set from timur, but likely not until late this week21:43
patchbothttps://review.openstack.org/#/c/475038/ - python-swiftclient - Allow for uploads from standard input.21:43
notmynamefor swift, patch 448480 needs reviews21:43
patchbothttps://review.openstack.org/#/c/448480/ - swift - DB replicator cleanup21:43
notmynameand keep and eye on clay's new patch 47841621:43
patchbothttps://review.openstack.org/#/c/478416/ - swift - WIP: Add multiple worker processes strategy to rec...21:43
notmynamesuper awesome stuff, but not quite ready for full review21:44
notmynamethe bugs are high priority: important, but not blocking21:44
notmynameif there's stuff that needs to be added, please addit and let me know or let me know and i can add it21:44
notmynameany questions/thoughts on this?21:44
notmyname#topic open discussion21:45
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:45
notmynameanything else to bring up this week?21:45
*** edmondsw has joined #openstack-meeting21:46
notmynameif you've been looking at contributor trends, you've noticed swift's been down recently. however, the graphs show a recent uptick21:46
notmynamehttp://d.not.mn/active_contribs.png21:46
notmynameso that's nice :-)21:47
notmynametdasilva: cschwede: thanks again for the bug triage work21:47
notmynameplease don't forget to register for the ptg asap21:47
notmynameI'm looking forward to seeing everyone there21:47
notmynamethanks for all your work on swift21:47
notmyname#endmeeting21:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:47
openstackMeeting ended Wed Jul 12 21:47:49 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2017/swift.2017-07-12-21.00.html21:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2017/swift.2017-07-12-21.00.txt21:47
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2017/swift.2017-07-12-21.00.log.html21:47
jungleboyj@!21:47
_pewp_jungleboyj (;-_-)ノ21:47
clayg@!21:48
_pewp_clayg (♦亝д 亝)ノ21:48
claygheh21:48
jungleboyj:-)21:48
*** patchbot has left #openstack-meeting21:49
*** acoles has left #openstack-meeting21:49
*** edmondsw has quit IRC21:50
*** kota_ has left #openstack-meeting21:50
*** m_kazuhiro has quit IRC21:50
*** zaitcev has left #openstack-meeting21:50
*** armax has quit IRC21:51
*** jrichli has left #openstack-meeting21:52
*** felipemonteiro_ has quit IRC21:52
*** armax has joined #openstack-meeting21:52
*** Manuel_112 has quit IRC21:53
*** eharney has quit IRC21:54
*** ihrachys has quit IRC21:54
*** cschwede has quit IRC21:54
*** armax has quit IRC21:56
*** Apoorva has quit IRC21:58
*** timburke has left #openstack-meeting22:03
*** Apoorva has joined #openstack-meeting22:04
*** Apoorva has quit IRC22:04
*** galstrom_zzz is now known as galstrom22:05
*** Patifa has quit IRC22:06
*** fnaval has quit IRC22:07
*** Apoorva has joined #openstack-meeting22:10
*** esberglu has quit IRC22:11
*** vmatt has joined #openstack-meeting22:12
*** MeganR has quit IRC22:13
*** makowals has joined #openstack-meeting22:14
*** ykatabam has joined #openstack-meeting22:15
*** dprince has joined #openstack-meeting22:16
*** Manuel_112 has joined #openstack-meeting22:21
*** markstur has quit IRC22:22
*** dprince has quit IRC22:22
*** slaweq_ has quit IRC22:23
*** Manuel_112 has quit IRC22:26
*** makowals has quit IRC22:28
*** mmethot_ has joined #openstack-meeting22:31
*** mmethot has quit IRC22:31
*** d34dh0r53 has quit IRC22:32
*** X-dark_ has joined #openstack-meeting22:32
*** artom has quit IRC22:32
*** d34dh0r53 has joined #openstack-meeting22:32
*** rm_work has quit IRC22:32
*** bobh has quit IRC22:32
*** X-dark has quit IRC22:32
*** X-dark_ is now known as X-dark22:32
*** rm_work has joined #openstack-meeting22:32
*** artom has joined #openstack-meeting22:33
*** rhagarty has quit IRC22:35
*** raginbajin has quit IRC22:35
*** yuval has quit IRC22:35
*** slagle has quit IRC22:35
*** slagle has joined #openstack-meeting22:35
*** sambetts|afk has quit IRC22:36
*** szaher has quit IRC22:37
*** szaher has joined #openstack-meeting22:37
*** yuval has joined #openstack-meeting22:37
*** rhagarty has joined #openstack-meeting22:37
*** sambetts_ has joined #openstack-meeting22:37
*** claudiub has quit IRC22:38
*** raginbajin has joined #openstack-meeting22:42
*** markstur has joined #openstack-meeting22:42
*** thorst has joined #openstack-meeting22:45
*** thorst has quit IRC22:45
*** cdub has joined #openstack-meeting22:45
*** makowals has joined #openstack-meeting22:46
*** ihrachys has joined #openstack-meeting22:46
*** markstur has quit IRC22:47
*** cdub has quit IRC22:50
*** makowals has quit IRC22:50
*** cdub has joined #openstack-meeting22:51
*** yamamoto has joined #openstack-meeting22:52
*** cdub has quit IRC22:53
*** cdub has joined #openstack-meeting22:56
*** armax has joined #openstack-meeting22:58
*** cdub has quit IRC22:58
*** awaugama has quit IRC23:00
*** cdub has joined #openstack-meeting23:01
*** annegentle has quit IRC23:01
*** cdub has quit IRC23:03
*** markstur has joined #openstack-meeting23:03
*** cdub has joined #openstack-meeting23:06
*** galstrom is now known as galstrom_zzz23:06
*** markstur has quit IRC23:08
*** cdub has quit IRC23:10
*** cdub has joined #openstack-meeting23:11
*** d0ugal has joined #openstack-meeting23:12
*** emagana has quit IRC23:12
*** emagana has joined #openstack-meeting23:12
*** cdub has quit IRC23:13
*** baoli_ has joined #openstack-meeting23:16
*** cdub has joined #openstack-meeting23:16
*** emagana has quit IRC23:17
*** cdub has quit IRC23:18
*** baoli has quit IRC23:18
*** cdub has joined #openstack-meeting23:21
*** cdub has quit IRC23:23
*** slaweq_ has joined #openstack-meeting23:23
*** baoli_ has quit IRC23:26
*** cdub has joined #openstack-meeting23:26
*** slaweq_ has quit IRC23:28
*** cdub has quit IRC23:29
*** cdub has joined #openstack-meeting23:32
*** cdub has quit IRC23:32
*** cdub has joined #openstack-meeting23:37
*** cdub has quit IRC23:38
*** sshank has quit IRC23:39
*** hongbin has quit IRC23:40
*** chyka_ has quit IRC23:40
*** chyka has joined #openstack-meeting23:41
*** marst has quit IRC23:41
*** cdub has joined #openstack-meeting23:42
*** cdub has quit IRC23:44
*** chyka has quit IRC23:45
*** cdub has joined #openstack-meeting23:47
*** cdub has quit IRC23:49
*** cdub has joined #openstack-meeting23:52
*** wanghao has joined #openstack-meeting23:54
*** pcregut1 has joined #openstack-meeting23:54
*** Swami has quit IRC23:54
*** cdub has quit IRC23:55
*** bobh has joined #openstack-meeting23:56
*** Julien-zte has joined #openstack-meeting23:57
*** cdub has joined #openstack-meeting23:57

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