Wednesday, 2017-08-16

*** brault has quit IRC00:00
*** edmondsw has quit IRC00:00
*** Manuel_112 has quit IRC00:01
*** Swami has quit IRC00:03
*** wanghao has quit IRC00:09
*** wanghao has joined #openstack-meeting00:09
*** gouthamr has joined #openstack-meeting00:12
*** dongfeng has joined #openstack-meeting00:26
*** wanghao_ has joined #openstack-meeting00:26
*** pvaneck has quit IRC00:27
*** wanghao has quit IRC00:29
*** markvoelker has quit IRC00:30
*** hongbin has joined #openstack-meeting00:35
*** jiaopengju has joined #openstack-meeting00:41
*** thorst has joined #openstack-meeting00:42
*** Yipei has joined #openstack-meeting00:53
*** markstur has quit IRC00:56
*** xuzhuang has joined #openstack-meeting00:57
*** RongHui11 has joined #openstack-meeting00:57
*** Manuel_112 has joined #openstack-meeting00:57
*** hejiawei has joined #openstack-meeting00:57
*** zhurong has joined #openstack-meeting00:58
*** artom has quit IRC00:58
*** ricolin has joined #openstack-meeting00:58
*** litao__ has joined #openstack-meeting00:58
*** joehuang has joined #openstack-meeting00:59
*** kiennt has joined #openstack-meeting01:01
joehuang#startmeeting tricircle01:01
openstackMeeting started Wed Aug 16 01:01:28 2017 UTC and is due to finish in 60 minutes.  The chair is joehuang. Information about MeetBot at
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
joehuang#topic rollcall01:01
*** openstack changes topic to "rollcall (Meeting topic: tricircle)"01:01
joehuang#info joehuang01:01
dongfeng#info dongfeng01:01
xuzhuang#info xuzhuang01:01
RongHui11#info ronghui01:01
hejiawei#info jiawei01:02
Yipei#info Yipei01:02
*** Manuel_112 has quit IRC01:02
joehuangcurrently new PTL election is ongoing, and almost done01:03
joehuangonly one candidate for tricircle project, If I am correctly01:03
*** tovin07_ has joined #openstack-meeting01:03
joehuangso no voting for tricircle project01:03
joehuangnext week, the chair of the weekly meeting will be handed over to new PTL01:04
joehuangis it ok?01:05
RongHui11no problem01:05
Yipeifine, got it01:05
joehuang#topic regression test01:05
*** openstack changes topic to "regression test (Meeting topic: tricircle)"01:05
joehuangAs discussed in the maillist, ttx thought that we need to cut stable/pike branch early, so that if there is any critical issue, we have chance to fix it01:07
*** fredli__ has joined #openstack-meeting01:07
fredli__good morning, tricircle team01:08
joehuanghello, fred01:08
joehuangwe had planned to cut stable/pike August 2201:08
joehuangWe may need to move the cutting earlier this week01:09
joehuanghave you found any critical issues in regression test?01:09
dongfengI conduct the tests for admin API for tricircle and tricircleclient, the CRUD operation for pods/routing/jobs works well. only job pagination is needed in tricirclelient.01:09
joehuangI found two bugs need to be addressed soon01:10
openstackLaunchpad bug 1711001 in Tricircle "Job list not filtered by project" [Undecided,New]01:10
*** number80 has quit IRC01:10
openstackLaunchpad bug 1711003 in Tricircle "routing list not filtered by project" [Undecided,New]01:10
joehuangboth these two API processing need to consider the project filtering01:11
joehuangwould someone help fix these two bugs ASAP, then we can cut the stable/pike branch01:12
*** gouthamr has quit IRC01:13
dongfengI remember that project is a mandatory filter but later we didn't implement it.01:13
dongfengok, I will fix it01:13
zhiyuanit can be passed via the filter01:13
joehuangcould you fix it today? we have to move fast for the stable/pike branch01:14
zhiyuanthen you need to extract project id in tricircle client01:14
zhiyuanor you add a new client option for project id?01:14
*** lhx_ has quit IRC01:14
dongfengchange project id filter from optional to mandatory in tricircle and tricircleclient01:15
joehuangsupport it in tricircle side in pike01:15
joehuangbecause tricricleclient has already cut the stable/pike branch, and no fix will be included in pike01:15
*** wanghao_ has quit IRC01:16
zhiyuanso extract the project id in the context and pass it as the filter by default?01:16
*** wanghao has joined #openstack-meeting01:17
*** wanghao has quit IRC01:17
dongfengok. got it. so new command for routings will be  "curl -x get /routings/project-id"?01:17
*** wanghao has joined #openstack-meeting01:17
joehuangthere is project in the context for the user's request01:17
dongfeng so new command for routings will be  "curl -x get /routings?project-id=xxx"?01:17
zhiyuanI think asking user to always pass the project-id is not user-friendly01:18
joehuangthe client side is freeze now, not to change the command, and API format is also freeze, it is very serious to change API01:19
zhiyuanwhat if the project-id is not passed, dongfeng? will you return a bad request error?01:19
dongfengno error.01:19
*** claudiub has quit IRC01:20
*** liusheng has quit IRC01:21
dongfenghow about specifying project_id internally and remove the project_id filter ?01:21
joehuangno, by default, you need to filter by the project-id in the request context01:22
dongfengso project_id also serves as filter and can be specify from command line ?01:24
joehuangyes, if there is project id specified, then check whether the user has the right to query data from the specified project, if yes, filter by the specified project, otherwise, filter with the project-id in the context by default01:26
joehuang if there is project id specified, then check whether the user has the right to query data from the specified project, if yes, filter by the specified project, if not, reject the request. If no project-id is specified, filter with the project-id in the context by default01:27
zhiyuanhere is a problem, can we directly know from the context whether the user has the "admin" role of another project?01:28
zhiyuancontext may only contain (userA, projectA, role of userA in projectA)01:29
zhiyuanbut user may pass projectB as filter01:29
*** gouthamr has joined #openstack-meeting01:30
*** gcb has joined #openstack-meeting01:32
joehuangso we have to only use the project id in the context to filter the query data01:33
dongfengthen no project id filter ?01:33
*** liusheng has joined #openstack-meeting01:34
dongfengthen no project id filter from command line?01:34
*** esberglu has quit IRC01:34
joehuangnot to add currently, and no need indeed01:35
*** esberglu has joined #openstack-meeting01:35
*** jamesmcarthur has joined #openstack-meeting01:35
*** yamahata has quit IRC01:35
joehuangmore comment for the filtering?01:36
zhiyuanso we do the following changes (1) extract project id from context ans use as filter (2) if project id is passed, check if it match the project id in the context01:37
zhiyuanis that right?01:37
dongfengif only one project id, then no need specify it from cli01:38
zhiyuanbut user may deliberately pass a project id which doesn't match his/her context01:39
*** esberglu has quit IRC01:39
joehuangwe have to ignore the project-id passed from the cli, because no idea whether the user has enough right to query the project01:39
*** jamesmcarthur has quit IRC01:39
joehuangwe only filtering the data the user is authorized01:40
zhiyuanoh, just ignore it?01:40
joehuangso only using the project-id and role in the context(which is authenticated)01:40
joehuangcurrently just ignore that, and update the API document to stress this01:41
*** slaweq has joined #openstack-meeting01:42
*** esberglu has joined #openstack-meeting01:43
*** esberglu has quit IRC01:43
dongfengstress like "project id must be current user" ?01:43
*** lbragstad has quit IRC01:44
*** edmondsw has joined #openstack-meeting01:44
joehuangproject-id filter will be ignored, and only the project id in which the user is authorized will be used as the filter.01:45
dongfenggot it.01:45
*** Apoorva_ has joined #openstack-meeting01:46
joehuangproject-id filter in URL query string will be ignored, and only the project id in which the user is authorized will be used as the filter.01:47
*** slaweq has quit IRC01:47
joehuangthe last description is better01:47
dongfenggot it01:48
joehuangso these two bugs are put in "high" importance01:48
*** edmondsw has quit IRC01:48
joehuangand hope it can be fixed today, so that we can cut the stable/pike branch if no high/critical bug is reported today01:49
dongfengen, I will handle asap.01:49
joehuang#topic open discussion01:49
*** openstack changes topic to "open discussion (Meeting topic: tricircle)"01:49
joehuangother topic?01:49
*** Apoorva has quit IRC01:50
Yipeifor lbaas, some modification on get_subnet is needed to adapt lbaas, once it is finished the lbaas is compeleted. since i commented the line of checking whether subnet exists, it works well in both neutron-lbaas api and octavia api01:50
*** Apoorva_ has quit IRC01:50
joehuangGood, yipei, welcome the LBaaS to land in Queen01:51
zhiyuanso next step is trying to modify get_subnet in central_plugin/local_plugin ?01:51
Yipeionly in local01:51
Yipeito joehuang, not in pike?01:52
joehuangno, pike is feature freeze, and now it's regression test, no feature is allowd01:52
RongHui11for QoS, we pass all the test yesterday and please review it :)01:52
zhiyuanmodifying get_subnet in local_plugin needs to be careful since get_subnet is also used to handle VM creation01:53
joehuangto Ronghui, please include functional test too, just like what zhiyuan did for the smoke test for other features01:53
Yipeito zhiyuan, got it, i will discuss the details with you guys01:53
zhiyuanso do we plan a PTG for Queens?01:54
joehuangPTG for queens is indeed to be in the table now01:55
joehuangother topic?01:56
RongHui11no for me01:56
dongfengno for me01:56
Yipeino for me01:56
zhiyuanno more01:56
joehuangthank you for attending the meeting01:58
*** openstack changes topic to "OpenStack Meetings ||"01:58
openstackMeeting ended Wed Aug 16 01:58:10 2017 UTC.  Information about MeetBot at . (v 0.1.4)01:58
openstackMinutes (text):
*** thorst has quit IRC01:59
*** xuzhuang has quit IRC02:00
*** markstur has joined #openstack-meeting02:00
*** Yipei has quit IRC02:02
*** gongysh has joined #openstack-meeting02:07
*** trozet has quit IRC02:08
*** trozet has joined #openstack-meeting02:10
*** bkopilov has quit IRC02:11
*** trozet has quit IRC02:17
*** unicell has quit IRC02:19
*** trozet has joined #openstack-meeting02:20
*** markstur has quit IRC02:22
*** RongHui has joined #openstack-meeting02:25
*** Manuel_112 has joined #openstack-meeting02:28
*** epico has joined #openstack-meeting02:28
*** RongHui has quit IRC02:30
*** RongHui11 has quit IRC02:30
*** markvoelker has joined #openstack-meeting02:31
*** RongHui11 has joined #openstack-meeting02:31
*** Manuel_112 has quit IRC02:32
*** RongHui has joined #openstack-meeting02:32
*** gouthamr has quit IRC02:34
*** yamahata has joined #openstack-meeting02:34
*** diablo_rojo has joined #openstack-meeting02:35
*** RongHui11 has quit IRC02:36
*** trozet has quit IRC02:38
*** RongHui11 has joined #openstack-meeting02:39
*** dongfeng has left #openstack-meeting02:40
*** RongHui has quit IRC02:40
*** unicell has joined #openstack-meeting02:42
*** krtaylor has joined #openstack-meeting02:42
*** slaweq has joined #openstack-meeting02:43
*** unicell has quit IRC02:46
*** gongysh has quit IRC02:47
*** baoli has joined #openstack-meeting02:47
*** baoli has quit IRC02:48
*** slaweq has quit IRC02:48
*** baoli has joined #openstack-meeting02:48
*** baoli has quit IRC02:49
*** gongysh has joined #openstack-meeting02:53
*** RongHui11 has quit IRC02:59
*** dongfeng has joined #openstack-meeting03:01
*** joehuang has left #openstack-meeting03:01
*** markvoelker has quit IRC03:04
*** myoung|remote has joined #openstack-meeting03:09
*** myoung|remote has quit IRC03:10
*** dklyle has quit IRC03:12
*** vishwana_ has joined #openstack-meeting03:18
*** vishwanathj has quit IRC03:21
*** zhhuabj has quit IRC03:27
*** yangyapeng has quit IRC03:28
*** Manuel_112 has joined #openstack-meeting03:28
*** bkopilov has joined #openstack-meeting03:30
*** david-lyle has joined #openstack-meeting03:31
*** yangyapeng has joined #openstack-meeting03:32
*** edmondsw has joined #openstack-meeting03:32
*** Manuel_112 has quit IRC03:33
*** hejiawei has quit IRC03:35
*** edmondsw has quit IRC03:37
*** martial has joined #openstack-meeting03:37
*** epico has quit IRC03:37
*** martial has quit IRC03:39
*** martial has joined #openstack-meeting03:39
*** zhhuabj has joined #openstack-meeting03:40
*** martial has quit IRC03:42
*** martial has joined #openstack-meeting03:42
*** martial has quit IRC03:43
*** slaweq has joined #openstack-meeting03:44
*** fredli__ has quit IRC03:45
*** links has joined #openstack-meeting03:47
*** makowals has quit IRC03:47
*** epico has joined #openstack-meeting03:49
*** slaweq has quit IRC03:49
*** makowals has joined #openstack-meeting03:58
*** phuoc has joined #openstack-meeting03:59
*** markvoelker has joined #openstack-meeting04:01
*** david-lyle has quit IRC04:06
*** david-lyle has joined #openstack-meeting04:08
*** dtrainor has quit IRC04:11
*** dtrainor has joined #openstack-meeting04:11
*** yangyapeng has quit IRC04:15
*** dklyle has joined #openstack-meeting04:15
*** brault has joined #openstack-meeting04:16
*** david-lyle has quit IRC04:18
*** brault has quit IRC04:21
*** hongbin has quit IRC04:24
*** YanXing_an has joined #openstack-meeting04:25
*** trinaths has joined #openstack-meeting04:30
gongysh#startmeeting tacker04:30
openstackMeeting started Wed Aug 16 04:30:16 2017 UTC and is due to finish in 60 minutes.  The chair is gongysh. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:30
*** openstack changes topic to " (Meeting topic: tacker)"04:30
openstackThe meeting name has been set to 'tacker'04:30
gongysh#topic roll call04:30
*** openstack changes topic to "roll call (Meeting topic: tacker)"04:30
*** markstur has joined #openstack-meeting04:30
gongyshwho are you guys for tacker meeting?04:30
gongyshtrinaths, hi04:30
trinathsgongysh: hi,04:31
trinathsYanXing_an: hi04:31
*** sridharg has joined #openstack-meeting04:32
phuochi all04:32
gongyshlets wait until 3504:32
YanXing_anthe Sydney summit presentation voting have result?04:33
gongyshin particular for tung_doan and dharmendra04:33
trinathsYanXing_an: august month end we might receive notifications whether in or out04:34
YanXing_anTrinaths, ok, thanks04:34
*** markvoelker has quit IRC04:34
gongyshit seems these two guys will be absent04:36
gongysh#topic bp04:36
*** openstack changes topic to "bp (Meeting topic: tacker)"04:36
gongyshYanXing_an, does your ns spec can be merged these days?04:36
gongyshI want to release tacker server.04:37
gongyshand need to know what I should wait for.04:37
gongyshI thought I should wait for tung_doan and dharmendra patches.04:37
*** tung_doan has joined #openstack-meeting04:37
tung_doanhi all04:38
gongyshtung_doan, hi04:38
gongyshjust talk about your patches.04:38
gongyshI said I wanted to release tacker server.04:38
gongyshand wait for your commitment to your patches.04:38
gongyshhow long I should wait for your patches?04:38
tung_doangongysh: yep. Please let me know the deadline.. i will procedure this patch soon04:38
YanXing_anI will try to finish it before tung_doan and dharmendra's patches, otherwise, not wait for me.04:39
gongyshat most two weeks.04:39
tung_doangongysh: my main effort will be put on this week04:39
gongyshtung_doan,  ok, thanks04:40
YanXing_anthe vnffg spec still have some issues to discuss and be confirmed04:40
gongyshYanXing_an,  trinaths , please review closely for tung_doan's patches.04:40
*** markstur has quit IRC04:40
tung_doangongysh: thanks04:40
YanXing_angongysh, ok, that patch is first priority04:41
gongyshdharmendra's patches are important to us too, but he is not stable to do the contribution.04:41
*** dkushwaha has joined #openstack-meeting04:41
*** markstur has joined #openstack-meeting04:41
tung_doanYanXing_an: trinaths: probably pls wait after i push the new patch this week04:41
gongyshdkushwaha, hi04:41
YanXing_anHi, dhushwaha04:41
dkushwahasorry i amlate04:41
gongyshdkushwaha, in the end we got you.04:42
gongysh<gongysh>dharmendra's patches are important to us too, but he is not stable to do the contribution.04:43
gongyshI want to release tacker server in 2 weeks.04:43
tung_doangongysh: got it04:43
gongyshdkushwaha, your patches about vnf monitor policies are important for this cycle.04:43
gongyshdo you have plan to finish it in these two weeks?04:44
gongyshdkushwaha, hi04:44
dkushwahagongysh, i could not work much in last week,  but yes, i am hoping to complete it in couple of days04:45
*** slaweq has joined #openstack-meeting04:45
*** markstur has quit IRC04:45
gongyshdkushwaha, ok,  let's do it with moonlight effort.04:46
*** brault has joined #openstack-meeting04:46
gongyshdkushwaha, I have commented your patch.04:46
gongyshyou can reply quickly, and if you need more review, you can ping me via wechat.04:47
gongyshI can review once I got the notification.04:47
gongyshlets merge it in this cycle.04:47
gongyshif you have no time, let me know, I will arrange my company guy to help.04:48
dkushwahagongysh, sure, i will be able to check after 2 hours, and will respond/update04:48
gongyshdkushwaha,  ok, thanks.04:48
gongyshYanXing_an, hi04:48
gongyshwhat do you want to discuss about ns with vnffg?04:49
YanXing_anI have researched on ns last week, tested it04:49
YanXing_ani think we have two ways to support vnffg in ns04:49
YanXing_anthe first is importing vnffg in ns, similar with vnf in ns,04:50
*** slaweq_ has joined #openstack-meeting04:50
*** slaweq has quit IRC04:50
*** brault has quit IRC04:50
YanXing_anthe second is defining vnffg details in ns, I don't know which one is best.04:50
YanXing_anWhat do you think?04:50
gongyshdkushwaha, do you have idea?04:50
YanXing_anHave updated a draft patchset04:51
dkushwahaYanXing_an, i think it will be better to have vnffg in ns, instead to going through vnffg details04:52
tung_doandkushwaha: +104:52
gongyshdkushwaha, you choose first or second one?04:53
tung_doanimport vnffgd inside ns seems complicated04:53
YanXing_anOk, I also suggest to use the first way04:53
dkushwahai mean first one04:53
tung_doanwhy we dont follow the second one?04:53
phuocI think the second option is better04:54
tung_doanit seems ETSI standard also had the same desccription04:54
gongyshLets do step by step.04:54
YanXing_anThe problem is, when we create nsd, we should create vnfd, vnffgd at first.04:54
tung_doaneven the second one will be easy to do04:54
*** slaweq_ has quit IRC04:55
gongyshYanXing_an, now we support create with direct descriptors to create resources.04:55
gongyshcreate -> creating04:55
tung_doanvnffg is the combinatin of VNFs.. it should be abstracted in ns. I think04:55
YanXing_anIf using the second one, we should define vnfd details in ns too. tung_doan, yes, you got the point04:57
gongyshYanXing_an, first lets do via import vnffgd way, and also we need to do via embedded vnffgd in nsd04:58
dkushwahagongysh, in my openion first we should go with 1st approach as we already have stable vnffg. And then we can think to move 2nd one04:58
gongyshdkushwaha, two minds think the same.04:58
dkushwahagongysh, +104:58
YanXing_anOk, got it, thanks all04:58
gongyshYanXing_an,  do you have else about NS with vnffg?04:59
*** Manuel_112 has joined #openstack-meeting04:59
gongysh#topic coding04:59
*** openstack changes topic to "coding (Meeting topic: tacker)"04:59
gongyshtung_doan, what do you want to talk about your two bps' coding?05:00
gongyshI cannot see new code patches in05:00
tung_doangongysh: vnffg healing and scaling has some similar code05:00
tung_doanonce i finish vnffg-healing, vnffg-scaling will be done soon05:00
gongyshtung_doan, ok05:01
tung_doannow phuoc and I are trying to wrap two these features05:01
gongyshlook forwards to your code patches.05:01
tung_doangongysh: sure. really want to finish both of them this week05:01
gongysh#topic open discuss05:02
*** openstack changes topic to "open discuss (Meeting topic: tacker)"05:02
tung_doandkushwaha: gongysh: could you help merge this:
gongyshYanXing_an, I think we have talked about state transition diagram before.05:02
tung_doansome tacker users are not happy because of this bug :)05:02
*** janki has joined #openstack-meeting05:03
gongyshYanXing_an, do you have any progress on that?05:04
YanXing_anIf so, I must draw the diagram asap.05:04
*** Manuel_112 has quit IRC05:04
dkushwahatung_doan, its again horizon05:04
tung_doandkushwaha: right.. it is also up to ocata version05:05
gongyshYanXing_an, you help to do it, put it into related dev doc or user guide.05:05
YanXing_anGongysh, ok, will do it05:06
gongyshtung_doan, I saw you have rechecked
gongyshit failed a test case.05:06
gongyshdo you have any idea for it?05:06
tung_doangongysh: ah. i think if we recheck again it will work :) multi-vdu testing sometime gets failed :)05:07
YanXing_antung_doan, :)05:08
tung_doanjust like weather :)05:08
gongyshchildren's face :)05:09
gongyshlets thought it about new features in queen cycle.05:11
gongyshthought -> think05:11
dkushwahaany update on sydny topic selection ?05:11
gongyshafter the tacker server release, we will have one virtual meeting.05:12
gongyshI will send out the ptg meeting announcement via openstack dev mail list today.05:13
YanXing_anIf we have the meeting link, please broadcast it at first time05:14
*** gyee has quit IRC05:17
gongyshthats my all.05:18
*** edmondsw has joined #openstack-meeting05:20
*** openstack changes topic to "OpenStack Meetings ||"05:21
openstackMeeting ended Wed Aug 16 05:21:18 2017 UTC.  Information about MeetBot at . (v 0.1.4)05:21
openstackMinutes (text):
*** knikolla has quit IRC05:22
*** tung_doan has left #openstack-meeting05:22
*** phuoc has left #openstack-meeting05:22
*** reedip has quit IRC05:23
*** edmondsw has quit IRC05:24
*** tobberydberg has joined #openstack-meeting05:31
*** markvoelker has joined #openstack-meeting05:32
*** jamesmcarthur has joined #openstack-meeting05:36
*** anilvenkata has joined #openstack-meeting05:37
*** reedip has joined #openstack-meeting05:37
*** dkushwaha has quit IRC05:38
*** jamesmcarthur has quit IRC05:40
*** kiennt has quit IRC05:43
*** brault has joined #openstack-meeting05:44
*** pcaruana has joined #openstack-meeting05:45
*** brault has quit IRC05:48
*** slaweq has joined #openstack-meeting05:51
*** slaweq has quit IRC05:56
*** zhouyaguo has quit IRC05:58
*** Manuel_112 has joined #openstack-meeting05:59
*** marios has joined #openstack-meeting06:00
*** kiennt has joined #openstack-meeting06:02
*** zhouyaguo has joined #openstack-meeting06:03
*** wanghao_ has joined #openstack-meeting06:04
*** jbadiapa has joined #openstack-meeting06:04
*** markvoelker has quit IRC06:05
*** brault has joined #openstack-meeting06:05
*** wanghao has quit IRC06:08
*** brault has quit IRC06:10
*** kiennt has quit IRC06:11
*** YanXing_an has quit IRC06:11
*** kiennt has joined #openstack-meeting06:16
*** zhurong has quit IRC06:19
*** adisky__ has joined #openstack-meeting06:19
*** zhurong has joined #openstack-meeting06:22
*** alexchadin has joined #openstack-meeting06:31
*** hemna__ has quit IRC06:43
*** markstur has joined #openstack-meeting06:45
*** markstur has quit IRC06:50
*** tobiajo has joined #openstack-meeting06:52
*** zhurong has quit IRC06:53
*** coolsvap has joined #openstack-meeting06:54
*** rcernin has joined #openstack-meeting06:57
*** kiennt has quit IRC06:57
*** kiennt has joined #openstack-meeting06:58
*** wanghao_ has quit IRC06:59
*** wanghao has joined #openstack-meeting07:01
*** markvoelker has joined #openstack-meeting07:02
*** ricolin has quit IRC07:05
*** edmondsw has joined #openstack-meeting07:08
*** unicell has joined #openstack-meeting07:12
*** diablo_rojo has quit IRC07:12
*** edmondsw has quit IRC07:13
*** masuberu has joined #openstack-meeting07:14
*** rcernin has quit IRC07:16
*** masber has quit IRC07:16
*** wanghao has quit IRC07:16
*** number80 has joined #openstack-meeting07:17
*** masuberu has quit IRC07:18
*** unicell has quit IRC07:18
*** rcernin has joined #openstack-meeting07:19
*** wanghao has joined #openstack-meeting07:22
*** brault has joined #openstack-meeting07:25
*** jaypipes has joined #openstack-meeting07:25
*** masuberu has joined #openstack-meeting07:28
*** dmellado has joined #openstack-meeting07:28
*** toscalix has joined #openstack-meeting07:31
*** masuberu has quit IRC07:31
*** markstur has joined #openstack-meeting07:32
*** phil has joined #openstack-meeting07:35
*** phil is now known as Guest2279007:35
*** markvoelker has quit IRC07:36
*** markstur has quit IRC07:37
*** Alex_Staf has joined #openstack-meeting07:37
*** alexchadin has quit IRC07:37
*** wanghao has quit IRC07:38
*** oidgar has joined #openstack-meeting07:40
*** brault has quit IRC07:40
*** guoshan has joined #openstack-meeting07:47
*** brault has joined #openstack-meeting07:49
*** rbartal_ has joined #openstack-meeting07:49
*** guoshan_ has joined #openstack-meeting07:50
*** abalutoiu has joined #openstack-meeting07:51
*** guoshan has quit IRC07:53
*** slaweq_ has joined #openstack-meeting07:53
*** Guest22790 is now known as preisner07:55
*** markstur has joined #openstack-meeting07:57
*** slaweq_ has quit IRC07:58
*** e0ne has joined #openstack-meeting08:01
*** markstur has quit IRC08:01
*** abalutoiu has quit IRC08:01
*** wanghao has joined #openstack-meeting08:03
*** thorst has joined #openstack-meeting08:04
*** ralonsoh has joined #openstack-meeting08:04
*** thorst has quit IRC08:09
*** ralonsoh has quit IRC08:12
*** ralonsoh has joined #openstack-meeting08:12
*** alexchadin has joined #openstack-meeting08:13
*** XueFeng has quit IRC08:20
*** claudiub has joined #openstack-meeting08:20
*** yamamoto has joined #openstack-meeting08:33
*** markvoelker has joined #openstack-meeting08:33
*** jamesmcarthur has joined #openstack-meeting08:36
*** jamesmcarthur has quit IRC08:40
*** wanghao has quit IRC08:45
*** yamamoto has quit IRC08:49
*** jbadiapa_ has joined #openstack-meeting08:50
*** jbadiapa has quit IRC08:51
*** slaweq has joined #openstack-meeting08:54
*** edmondsw has joined #openstack-meeting08:57
*** sambetts|afk is now known as sambetts08:58
*** slaweq has quit IRC08:59
*** edmondsw has quit IRC09:01
*** thorst has joined #openstack-meeting09:05
*** enolfc has joined #openstack-meeting09:06
*** markvoelker has quit IRC09:06
*** thorst has quit IRC09:09
*** electrofelix has joined #openstack-meeting09:09
*** tobiajo has quit IRC09:15
*** tobiajo has joined #openstack-meeting09:15
*** enolfc has quit IRC09:19
*** enolfc has joined #openstack-meeting09:19
*** enolfc has quit IRC09:20
*** alexchadin has quit IRC09:24
*** ricolin has joined #openstack-meeting09:36
*** wanghao has joined #openstack-meeting09:43
*** wanghao has quit IRC09:45
*** Manuel_112 has quit IRC09:46
*** chyka has joined #openstack-meeting09:46
*** chyka has quit IRC09:50
*** ociuhandu has quit IRC09:54
*** slaweq has joined #openstack-meeting09:55
*** tovin07_ has quit IRC09:57
*** slaweq has quit IRC10:00
*** markstur has joined #openstack-meeting10:01
*** markvoelker has joined #openstack-meeting10:03
*** kiennt has quit IRC10:05
*** markstur has quit IRC10:05
*** thorst has joined #openstack-meeting10:05
*** jiaopengju has quit IRC10:08
*** thorst has quit IRC10:11
*** dtrainor has quit IRC10:11
*** ociuhandu has joined #openstack-meeting10:12
*** Manuel_112 has joined #openstack-meeting10:15
*** abalutoiu has joined #openstack-meeting10:15
*** lpetrut has joined #openstack-meeting10:17
*** abalutoiu has quit IRC10:20
*** tobiajo has quit IRC10:20
*** yamahata has quit IRC10:21
*** chandankumar is now known as chkumar|travel10:27
*** jbadiapa_ has quit IRC10:30
*** jbadiapa_ has joined #openstack-meeting10:31
*** kevinz has quit IRC10:32
*** markvoelker has quit IRC10:38
*** guoshan_ has quit IRC10:40
*** abalutoiu has joined #openstack-meeting10:40
*** ralonsoh has quit IRC10:44
*** ralonsoh_ has joined #openstack-meeting10:44
*** priteau has joined #openstack-meeting10:44
*** edmondsw has joined #openstack-meeting10:45
*** edmondsw has quit IRC10:49
*** bkopilov has quit IRC10:50
*** jkilpatr has quit IRC10:54
*** daveholland has joined #openstack-meeting10:55
*** oneswig has joined #openstack-meeting10:56
*** epico has quit IRC10:57
*** martial_ has joined #openstack-meeting11:00
oneswig#startmeeting scientific-wg11:00
openstackMeeting started Wed Aug 16 11:00:44 2017 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.11:00
*** openstack changes topic to " (Meeting topic: scientific-wg)"11:00
openstackThe meeting name has been set to 'scientific_wg'11:00
*** enolfc has joined #openstack-meeting11:00
martial_Hello Stig11:01
oneswig#chair martial_11:01
openstackCurrent chairs: martial_ oneswig11:01
*** verdurin has joined #openstack-meeting11:01
oneswigMorning martial_11:01
zz9pzzaHi :)11:01
oneswigHi zz9pzza verdurin enolfc11:01
oneswigand daveholland!11:01
oneswig#link agenda for today (such as it is)
oneswigMain item of interest this week is the second edition of the book11:02
martial_my, quite a good turnout of people I do not remember before. Welcome all11:02
oneswigHi priteau11:02
oneswigIndeed, welcome everyone11:02
*** noggin143 has joined #openstack-meeting11:02
oneswig#topic Scientific OpenStack book revision11:03
*** openstack changes topic to "Scientific OpenStack book revision (Meeting topic: scientific-wg)"11:03
daveholland@oneswig possibly for that (or for AOB) I would like to ask people's opinions and experiences about reporting "availability" of an entire Openstack platform (not just nagios)11:03
oneswigdaveholland: good topic, lets keep time for AOB11:03
oneswigSo, the book was created for Supercomputing 2016 and handed out by various people at the conference11:04
oneswigI think it was really popular and well received11:04
oneswigI've seen a number of people since with copies of it11:04
*** thorst has joined #openstack-meeting11:04
oneswigSo this is a great way we can make a difference11:04
oneswigThe plan is to revise / improve / extend the book for SC201711:05
* johnthetubaguy enjoyed reading the previous edition11:05
zz9pzzahi john congrats btw11:05
oneswigHi johnthetubaguy, good to see you11:05
martial_#link Working document to organize resources
oneswigthanks martial_11:06
oneswigI missed last week's meeting, can you recap the discussion from the US timezone?11:06
oneswigOr should I just read the etherpad :-)11:06
martial_sorry, copying data, but basically11:07
oneswigOK, there's some very useful contributions offered there.11:07
martial_Mr Hoge said "With time running out, real-time update from Kathy regarding the book. Deadline is Sept 22"11:07
zz9pzzaDave has been grabbed by someone, "Sangar multi-tenant Lustre integration ?" I will talk with him later as my English skills are minimal11:08
martial_a few people offered to work on updates of previous chapters11:08
martial_and we have --so far-- a short number of new papers to to add11:09
oneswig#link document source is here
oneswigmartial_: one of the hoped-for contributions is a section on federation, right?11:09
enolfconeswig: who's contributing to the federated identity chapter?11:10
oneswigenolfc: well volunteered? :-)11:10
oneswigHow is EGI federation going BTW?11:10
martial_oneswig: I tried to reach out to Dr Bohn but he will not be able to do one, so there is a possibility about the ORC11:10
enolfconeswig: I guess I have volunteered :)11:10
oneswigI believe there was jmlowe from Indiana University looking to make a contribution.11:11
*** zioproto has joined #openstack-meeting11:11
enolfcEGI is now ready to move to federated identity with OpenID Connect and planning to do so in production in the next months11:11
zioprotohello, sorry I guess I am 10 minutes late11:11
oneswigthanks enolfc, that'd be great to have your input11:11
noggin143I'll have a chat with Jose. We could certainly review the federation chapter but may not have time to write it.11:11
oneswigHi zioproto, welcome11:11
martial_and Mr Fernandez just did volunteer :)11:11
enolfcI can also check with INDIGO colleagues as I see you also mention it in the current text11:12
martial_welcome zioproto11:12
oneswigHi noggin143, thanks, that would be a great help.  What tends to happen is a body of text is written followed by 2-3 case studies.  A case study is typically half a page with a picture11:12
oneswigPerhaps that might not be too onerous for Jose?11:13
noggin143That sounds OK.11:13
noggin143A sample configuration on how to do federated id with Edugain and Active Directory11:13
oneswigI recall much of the existing text came from the user story zioproto put together last year11:13
noggin143we could do that.11:13
oneswignoggin143: that would be brilliant.11:14
oneswigmartial_: do you recall the ID federation jmlowe was discussion - was it Globus via OIDC?11:14
martial_that sounds right11:15
oneswigmartial_: who can we approach wrt a closing paragraph on ORC?11:15
oneswigOr should we wait for results first there?11:16
martial_enol is involved with it11:16
enolfconeswig, nogging143: we can have 3 use cases, Edugain, AD and EGI11:16
oneswigAh, great, of course.11:16
enolfconeswig: I can provide the ORC text11:17
oneswigIdeally we'd have diverse approaches in the case studies.  Any keycloak users out there?  I recall that was discussed positively11:17
oneswigThanks enolfc, appreciated11:18
davehollandnot sure who added Sanger Lustre integration to the etherpad (it wasn't us!) but as I'm presenting it at LAD in October then - given guidance on number of words/diagrams, expected audience, etc - that might be do-able. Is it too niche?11:18
martial_Enol: I missed the last ORC meeting but I will be able to join the next one. We can add this conversation to the agenda for the next meeting11:19
oneswigdaveholland: Not at all.  We have a whole chapter on filesystems IIRC, this would make a great case study11:19
martial_daveholland: I would love to see this paper11:19
zz9pzzaWe are going to spend a chunk of time going over things and writing it up as a paper ish could be done.11:19
davehollandOK, I will have to read the current version :)11:19
enolfcmartial_: sure, I think will start joining again next week also11:19
martial_as we get closer, we are going to need to make sure we have reviewers also11:20
oneswigCan those who volunteered add their names + details to the end of the etherpad so we can keep track?  thanks11:20
verdurinmartial_: given everything else I'm doing at the moment, I'm unlikely to be able to submit new material, but happy to be a reviewer11:20
*** gcb has quit IRC11:20
martial_maybe we should request for the deadline to be made shorter (vs the official 22nd) to get a couple reviewers per chapter11:21
oneswigThanks verdurin, that would be appreciated11:21
martial_the 22nd is a Friday so our meeting is likely the 19th that week ... 2 days to review, 2 days to fix11:21
oneswigmartial_: We'll probably need all the time we can, but definitely want to avoid a massive body of unreviewed documentation come the 21st11:22
oneswigExcellent - any more to cover here?11:23
oneswigThanks for everyone's volunteering :-)11:23
oneswig#topic OpenStack London11:23
*** openstack changes topic to "OpenStack London (Meeting topic: scientific-wg)"11:23
oneswigNot much defined here but for those who are planning to attend OpenStack Days UK on 26th September, we have a slot booked for the WG.11:24
oneswigI was wondering how we should fill it...11:24
martial_how long are you talking about?11:24
zz9pzzaDave has a hurdy gurdy.11:25
martial_(that seems to be about the same time as the ORC meeting?)11:25
oneswigIt's probably an hour, might be 40 mins.  Will need to check11:25
*** dweaver has joined #openstack-meeting11:25
oneswigzz9pzza: Thanks for your input :-)11:25
noggin143I'll be there too.11:26
martial_10 minutes intro to the group, a stig-sentation follow by a couple lighting talks?11:26
noggin143but I think I'm talking in another slot.11:26
oneswignoggin143: at the same time?  We can't have that.  I haven't seen timing but I'll try to get things shuffled if so11:26
noggin143don't know the schedule yet11:27
oneswigmartial_: That's a good model, has worked previously.11:27
noggin143+1 for the lightning talks11:27
*** jbadiapa_ has quit IRC11:27
martial_stig: you can make a tease about the meeting in Sydney as well :)11:28
oneswigDo we have volunteers for talks?11:28
oneswigI might know one or two interested people11:28
*** rm_mobile has joined #openstack-meeting11:29
*** martinkopec has joined #openstack-meeting11:29
zz9pzzaTim or Pete are doing the lustre talk as a separate slot.11:29
oneswigzz9pzza: daveholland: Is Tim C presenting?  Ah OK11:29
*** brett has joined #openstack-meeting11:29
*** jkilpatr has joined #openstack-meeting11:30
oneswigI'll sound out some people11:30
martial_sounds like it is going to be a great pesentation, will it be streamed?11:30
oneswigWe can also offer to people on the day, but that's uncertain11:30
oneswigmartial_: The talks were filmed last year, so I would expect so11:31
*** brault has quit IRC11:31
oneswigOK, was there anything more on OSD UK?  Nothing here11:32
oneswig#topic Open Research Clouds11:32
*** openstack changes topic to "Open Research Clouds (Meeting topic: scientific-wg)"11:32
oneswigHow is it going?11:32
martial_I missee the last meeting, maybe enol can let us know?11:33
enolfcI also missed last meeting11:33
enolfcbut from EGI we have the logistics ready for having the congress in Amsterdam11:34
martial_okay, well the last meeting I attended, things were still in definition11:34
enolfcregistration is already open11:34
martial_working groups were forming'11:34
oneswigenolfc: It's end September, right?11:34
enolfcNow there is some discussion about sponsorship11:34
enolfcyes, 27-2911:34
*** markvoelker has joined #openstack-meeting11:35
enolfcI plan to have AAI wg starting to meet from next week11:35
oneswigenolfc: can you link to the EGI page for it?11:35
*** brett has left #openstack-meeting11:35
enolfcwhen some EGI people is back from holiday11:35
oneswigAh, thanks :-)11:35
oneswigIntriguing fish11:35
enolfcWe now need to start moving things in the other wg, and finalise agenda11:36
oneswigWho should attend?11:36
martial_here are the latest happenings (had to find the link)
*** brett has joined #openstack-meeting11:38
oneswigOK, thanks martial_ enolfc - any more to add here?11:38
martial_oneswig: as to who should attend, I think anybody that can contribute to the effort11:38
enolfcmartial_ +111:39
enolfconeswig: no more updates from me so far11:39
martial_oneswig: there was a request to contribute from the point of view of scientific computing as well11:39
martial_oneswig: so it is going to depend on the narrative of that conversation11:39
martial_I think Tim mentioned he might be able to make it11:40
martial_I am possibly going to be there as well11:40
oneswigmartial_: The timing is possible for me, however my level of contribution is uncertain11:40
oneswigOK - next item?11:41
martial_Khalil requested a small presentation on the state of scientific computing and why an ORC would be welcome11:41
martial_oneswig: go ahead11:41
oneswig#topic AOB11:41
*** openstack changes topic to "AOB (Meeting topic: scientific-wg)"11:41
oneswigdaveholland: take it away mr music11:41
martial_I wanted to share this link ... a cool program I discussed with Flanders11:41
*** tobiajo has joined #openstack-meeting11:42
davehollandta :) so, we are happy measuring e.g. "is the API up" with nagios. But we are dancing around a measurement for "availability" for an OpenStack platform. e.g. if one user cannot deploy a large flavour instance because of hypervisor memory fragmentation, that's a showstopper for him, but the platform is still available.11:42
martial_and for those who have not seen it so far ...11:42
davehollandanyone got thoughts, experiences, opionions?11:42
*** jbadiapa_ has joined #openstack-meeting11:42
zz9pzzaWhat happens if say I can't create new volumes but everything else is working ...11:43
johnthetubaguydaveholland: did you look at using rally to regular test if you can create an instance?11:43
noggin143For those interested in nested quotas, I have posted the CERN model proposal to Happy to discuss if there are other proposals too.11:43
daveholland@johnthetubaguy an "end to end" nagios test (maybe using heat) is on my radar, not thought of rally, I'd mentally got that as a post-deploy benchmark - am I wrong?11:44
noggin143At CERN, we run Rally to give the availability. A sample set of workloads runs constantly, creating VMs, attaching volumes etc. It works great.11:44
oneswignoggin143: is it on CERN ops github?11:44
johnthetubaguyI knew someone told me about that before, must have been noggin14311:44
davehollandOK I will take a look. (it will inflate the headline "12345 instances launched to date" number, but hey)11:45
noggin143old presentation is at for details.11:45
*** simon-AS559 has joined #openstack-meeting11:45
noggin143It's great for the VMs/hour graphs too :-)11:45
daveholland@noggin143 thanks!11:45
johnthetubaguynoggin143: quota wise, I guess that is going to come up at the PTG, I might try sync up with that effort again, are other folks there to discuss that already?11:46
oneswigI thought this was pretty cool from Nectar:
oneswigIt's not directly related, but plugs the gap of revealing the available capacity on a private cloud11:46
noggin143For quota, I'd passed the information to Sean Dague who was looking for the 'rulesets'.11:47
daveholland@oneswig that's something else we've been asked for, in the context of a small host aggregate/ceph-backed flavour for "pets"11:47
johnthetubaguynoggin143: cool, he is leading that discussion AFAIK11:47
johnthetubaguythe placement API should help some with capacity queries:
johnthetubaguy#link might be the better link11:49
priteaujohnthetubaguy: What is the default access policy to discover capacity?11:50
oneswigThis autogenerated documentation is really good johnthetubaguy11:50
johnthetubaguyoneswig: its largely hand written now, to get it better, ups and downs11:50
johnthetubaguypriteau: its admin only API at the moment11:50
oneswigIn which case, I should say this hand-written documentation is really consistent :-011:51
davehollandeven an admin API is fine for populating metrics to produce a user-visible graph/number11:51
priteaujohnthetubaguy: That's a sound default, but it would be nice if most academic/community clouds allowed users to query it11:51
johnthetubaguypriteau: its got a policy rule you can change, as usual, I think, that should just be the default11:52
johnthetubaguydaveholland: +111:52
johnthetubaguyI think its probably better to build graphs like the nectar ones from that info11:53
johnthetubaguyit used to be crazy hard to extract that data, should be easier / more portable now11:53
*** raildo has joined #openstack-meeting11:54
*** litao__ has quit IRC11:54
noggin143Placement stuff looks promising... time to throw away the nasty local legacy database scripts...11:54
*** lhx_ has joined #openstack-meeting11:55
oneswigjohnthetubaguy: are you looking at the resource provider inventories here?11:55
*** brault has joined #openstack-meeting11:56
*** artom has joined #openstack-meeting11:56
johnthetubaguyoneswig: that is one way, you can also query what resource providers have space for a particular flavor you are interested in11:56
johnthetubaguywell, its a resource request, rather than a flavor, but there is a mapping11:56
oneswigand in response you'd get a 'yes' or 'I can accommodate 800 of those'?11:57
*** slaweq_ has joined #openstack-meeting11:57
johnthetubaguyI think you get a list of candidates where it can fit, with info on how many you could fit in each candidate (not sure how obvious the second part is)11:57
*** edmondsw has joined #openstack-meeting11:57
oneswigjohnthetubaguy: sounds very good for this case (and not at all what a public cloud would want to share)11:58
johnthetubaguythe real answer is probably need to add some APIs to make life easier, but I think its possible without11:58
oneswigOK we are nearly upon the hour - any more to add?11:59
davehollandlots to think about and try out. thanks all11:59
johnthetubaguyyeah, its currently not exposed externally by default (I would recommend)11:59
*** noggin143 has quit IRC11:59
oneswigOK time to close the meeting - thanks everyone, very useful discussion12:00
martial_very good conversation, the meeting notes are going to be fun :)12:00
*** openstack changes topic to "OpenStack Meetings ||"12:00
openstackMeeting ended Wed Aug 16 12:00:36 2017 UTC.  Information about MeetBot at . (v 0.1.4)12:00
openstackMinutes (text):
oneswigUntil next time!12:00
priteauGood bye everyone12:00
davehollandbye all!12:00
martial_thanks everybody12:00
*** brett has quit IRC12:00
*** martial_ has quit IRC12:01
*** slaweq_ has quit IRC12:02
*** dtrainor has joined #openstack-meeting12:05
*** markstur has joined #openstack-meeting12:05
*** markvoelker has quit IRC12:08
*** oneswig has quit IRC12:09
*** markstur has quit IRC12:10
*** enolfc has quit IRC12:10
*** dprince has joined #openstack-meeting12:15
*** bkopilov has joined #openstack-meeting12:28
*** trinaths has left #openstack-meeting12:30
*** trinaths_m has joined #openstack-meeting12:31
*** eharney has joined #openstack-meeting12:41
*** spzala has quit IRC12:51
*** brett has joined #openstack-meeting12:56
*** kevzha01 has joined #openstack-meeting12:58
*** slaweq_ has joined #openstack-meeting12:58
*** markvoelker has joined #openstack-meeting12:59
*** gongysh has quit IRC13:00
*** gongysh has joined #openstack-meeting13:00
*** gongysh has quit IRC13:00
*** oidgar_ has joined #openstack-meeting13:00
*** gongysh has joined #openstack-meeting13:00
*** Julien-z_ has joined #openstack-meeting13:00
*** trozet has joined #openstack-meeting13:02
*** oidgar has quit IRC13:02
*** slaweq_ has quit IRC13:03
*** baojg has joined #openstack-meeting13:03
*** Julien-zte has quit IRC13:03
*** gongysh has quit IRC13:05
*** markstur has joined #openstack-meeting13:08
*** esberglu has joined #openstack-meeting13:08
*** brault has quit IRC13:09
*** brault has joined #openstack-meeting13:09
*** oidgar_ is now known as oidgar13:10
*** spzala has joined #openstack-meeting13:12
*** spzala has quit IRC13:12
*** spzala has joined #openstack-meeting13:12
*** markstur has quit IRC13:12
*** gouthamr has joined #openstack-meeting13:15
*** VW has joined #openstack-meeting13:17
*** jamesmcarthur has joined #openstack-meeting13:19
*** knikolla has joined #openstack-meeting13:23
*** markstur has joined #openstack-meeting13:23
*** sgrasley1 has joined #openstack-meeting13:26
*** markstur has quit IRC13:28
*** janki has quit IRC13:28
*** janki has joined #openstack-meeting13:28
*** jamesmcarthur has quit IRC13:28
*** jamesmcarthur has joined #openstack-meeting13:29
*** oidgar_ has joined #openstack-meeting13:31
*** oidgar has quit IRC13:33
*** felipemonteiro has joined #openstack-meeting13:35
*** simon-AS5591 has joined #openstack-meeting13:35
*** felipemonteiro_ has joined #openstack-meeting13:36
*** simon-AS559 has quit IRC13:38
*** markstur has joined #openstack-meeting13:39
*** felipemonteiro has quit IRC13:40
*** cleong has joined #openstack-meeting13:41
*** markstur has quit IRC13:43
*** awaugama has joined #openstack-meeting13:46
*** Fdaisuke has joined #openstack-meeting13:46
*** aagate has joined #openstack-meeting13:58
*** brett has quit IRC13:58
*** rhochmuth has joined #openstack-meeting13:58
*** slaweq_ has joined #openstack-meeting13:59
*** zhouyaguo has quit IRC14:00
rhochmuth#startmeeting monasca14:00
openstackMeeting started Wed Aug 16 14:00:22 2017 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: monasca)"14:00
openstackThe meeting name has been set to 'monasca'14:00
*** zhouyaguo has joined #openstack-meeting14:00
*** dimak has quit IRC14:01
rhochmuthis anyone here for the weekly monasca meeting?14:01
*** dimak has joined #openstack-meeting14:01
*** Christian_ has joined #openstack-meeting14:02
*** haruki has joined #openstack-meeting14:02
*** yavor_OP5 has joined #openstack-meeting14:02
*** awaugama has quit IRC14:02
rhochmuthhi sgrasley114:02
*** alexchadin has joined #openstack-meeting14:02
rhochmuthwell, it looks like a pretty small group this week14:02
rhochmuthjust you and i14:02
Christian_Hi Roland!14:03
sgrasley1Well a short meeting then.14:03
*** kaiyan has joined #openstack-meeting14:03
rhochmuthhi Shristian_14:03
yavor_OP5Hi Roland, Yavor here from OP5, thanks for the invite14:03
rhochmuthso, i t hink some folks are out this week on vacation14:03
*** kevzha01 has quit IRC14:03
rhochmuthi know witek is out14:03
*** yangyapeng has joined #openstack-meeting14:03
rhochmuthhi yavor_OP514:04
rhochmuthglad you guys made it14:04
*** slaweq_ has quit IRC14:04
*** daveholland has quit IRC14:04
*** qwebirc46285 has joined #openstack-meeting14:04
yavor_OP5trip down memory lane, this... must be 20 yrs since I last used irc ;)14:05
rhochmuthyou'll love it14:05
rhochmuthok, the agenda doesn't have anything in it14:07
rhochmuthi think we can go with an open floor14:08
rhochmuthso do folks have any topics to discss this week14:08
rhochmuthwe have a nice backlog on reviews14:08
*** oidgar_ is now known as oidgar14:09
rhochmuthOP5 folks, have you had a chance to review some of the areas of development and come to any direction?14:10
rhochmuthor conclusion14:10
*** felipemonteiro_ has quit IRC14:10
yavor_OP5we've started investigating "poor man's clustering" on influxdb on our side...14:10
rhochmuthwe had a number of strategies that we had considered that would involve some changes to monasca14:11
rhochmuthone idea is that if an influxdb node/container goes down14:11
rhochmuthwhen it is brought back on-line it would have to catch-up14:12
yavor_OP5yup, we thought about that14:12
*** lbragstad has joined #openstack-meeting14:13
rhochmuththerefore, queries from the monasca-api to that influxdb node would not occur until the consumer offset of the persister for that node was close to the producer offset14:13
rhochmuththis assumes that persister storage of some type is being used, such as EBS in an AWS environment14:13
rhochmuthor that the influxdb node is the same node as before with the same disks available14:13
rhochmuthif the node is down for a while, then it could take a while to catach-up via kafka and the persister14:14
*** jaypipes has quit IRC14:14
rhochmuthso another option is to copy the data from a working node to the new node14:14
rhochmuththat is more invovled14:14
rhochmuthand at some point i think data to both nodes would need to stop14:15
yavor_OP5would it be OK to assume that the kafka cluster would provide storage needed for catch-up?14:16
*** ralonsoh_ has quit IRC14:16
yavor_OP5since it is already a part of the reference architecture14:16
rhochmuthyou could store data in kafka for several days or a week14:16
yavor_OP5otherwise we put constraints on the influx implementation14:16
yavor_OP5which may vary from instance to instance14:16
*** qwebirc46285 has quit IRC14:16
rhochmuththe data is uncompressed in kafka, so the amount of storage is possibly the biggest issue14:17
sgrasley1What are options for persisting to 2 influxdb instances14:17
rhochmuthyou would need to size capacity appropriately to handle your injest rate14:17
rhochmuthsgrasley1: you can replicate influxdb using the open-source code14:18
yavor_OP5what do you believe is a reasonable expectation of time to catch up with no loss? 2hrs? 2days? We have to have an idea about some sort of duration14:18
rhochmuthor you can use infludb's proprietary clustering solution14:18
rhochmuthi think the catch-up time is related to your amount of downtime, injest rate of metrics, and the throughput to the infludb node14:19
rhochmuthif your injest rate is 50K metrics/sec and you can only write 50K metrics/sec to influxdb, you would never catch-up14:19
rhochmuthso, you would have to measure that as it is dependent on systems, number of persisters14:20
yavor_OP5but I still think that one needs to have a reasonable expectation of how long an influx outage can last without losing data...14:20
*** gongysh has joined #openstack-meeting14:21
rhochmuthin a kubernetes environment recovery times can be very quick14:21
yavor_OP5to exemplify: from our company view if we can sustain an influx outage for a particular ingestion rate of 6 hrs x ingestion rate and then catchup then this is a perfectly acceptable clustering solution14:22
*** janki has quit IRC14:22
yavor_OP5which obviously leads to a question of how you monitor your Monasca instance ;)'14:22
yavor_OP5rhochmuth: how would you like us to structure our findings?14:23
rhochmuthgood question14:24
rhochmuthi think an overview of the various alternatives, pros/cons of each one14:24
rhochmuththe usual place where this ends-up in openstack is an etherpad14:24
rhochmuthFor example, the monasca team meeting is at,
rhochmuthbut you could easily add an etherpad for influxdb14:25
yavor_OP5ok, will look into it14:25
rhochmuthand, unless you are done earlier than the midcycle, we could review at one of the weekly meetings14:26
rhochmuthbut covering this at the mid-cycle woukld be best as that is just a few weeks away14:26
rhochmuthwitek will be organizing that14:26
*** zhouyaguo has quit IRC14:26
rhochmuthbut, due to his vacation, it will take him another week to cover that14:26
*** jaypipes has joined #openstack-meeting14:27
*** zhouyaguo has joined #openstack-meeting14:27
*** rbartal_ has quit IRC14:27
rhochmuthso, should we wrap-up a little early this week?14:28
rhochmuthunless there are other topics/questions to cover14:28
Christian_I'm good14:28
*** kaiyan has quit IRC14:28
rhochmuththx Christian_14:29
Christian_Yavor was the active one this time :-)14:29
*** annp has joined #openstack-meeting14:29
rhochmuththanks for getting invovled in the project, we are looking forward to the involvement14:29
rhochmuthand sorry about the small group today14:29
yavor_OP5thanks for the update!14:30
rhochmuthbut it is that time of year when folks are taking vacations14:30
yavor_OP5yeah, anything for you?14:30
yavor_OP5in terms of vacation that is14:30
rhochmuthi have a backlog, but probably in september14:30
*** simon-AS5591 has quit IRC14:31
rhochmuthOK everyone, thanks for the meeting today14:31
rhochmuthsee you all next week14:31
yavor_OP5have a nice one!14:31
*** openstack changes topic to "OpenStack Meetings ||"14:31
openstackMeeting ended Wed Aug 16 14:31:29 2017 UTC.  Information about MeetBot at . (v 0.1.4)14:31
openstackMinutes (text):
*** dweaver has left #openstack-meeting14:31
*** rbrndt has joined #openstack-meeting14:31
*** rhochmuth has left #openstack-meeting14:31
harukiThank you14:31
*** links has quit IRC14:32
*** fnaval has joined #openstack-meeting14:32
*** dongfeng has quit IRC14:32
*** rbrndt has left #openstack-meeting14:32
*** Christian_ has quit IRC14:34
*** Manuel_112 has quit IRC14:35
*** Fdaisuke has quit IRC14:39
*** sgrasley1 has quit IRC14:40
*** haruki has quit IRC14:41
*** felipemonteiro has joined #openstack-meeting14:41
*** pchavva has joined #openstack-meeting14:42
*** felipemonteiro_ has joined #openstack-meeting14:42
*** annp has quit IRC14:42
*** jamesmcarthur has quit IRC14:43
*** Alex_Staf has quit IRC14:45
*** felipemonteiro has quit IRC14:46
*** makowals has quit IRC14:48
*** makowals has joined #openstack-meeting14:48
*** alexchadin has quit IRC14:54
*** jprovazn has joined #openstack-meeting14:54
*** xyang1 has joined #openstack-meeting14:54
*** markstur has joined #openstack-meeting14:55
*** sridharg has quit IRC14:56
*** yavor_OP5 has quit IRC14:57
*** lhx__ has joined #openstack-meeting15:00
*** setuid has quit IRC15:00
*** setuid has joined #openstack-meeting15:00
*** slaweq has joined #openstack-meeting15:00
*** spzala has quit IRC15:01
*** spzala has joined #openstack-meeting15:01
*** gyee has joined #openstack-meeting15:02
*** lhx_ has quit IRC15:02
*** oidgar has quit IRC15:04
*** slaweq has quit IRC15:05
*** rcernin has quit IRC15:07
*** jgu has joined #openstack-meeting15:09
*** Manuel_112 has joined #openstack-meeting15:12
*** tobberyd_ has joined #openstack-meeting15:14
*** tobiajo has quit IRC15:14
*** Jamemcc_ has joined #openstack-meeting15:15
*** hemna__ has joined #openstack-meeting15:15
*** Manuel_112 has quit IRC15:16
*** tobberydberg has quit IRC15:17
*** tobberyd_ has quit IRC15:19
*** marst has joined #openstack-meeting15:19
*** reedip_ has joined #openstack-meeting15:21
*** Sukhdev has joined #openstack-meeting15:22
*** zhonghua has quit IRC15:23
*** zhonghua has joined #openstack-meeting15:23
*** baojg has quit IRC15:26
*** coolsvap has quit IRC15:27
*** baojg has joined #openstack-meeting15:27
*** chyka has joined #openstack-meeting15:31
*** links has joined #openstack-meeting15:33
*** donghao has joined #openstack-meeting15:37
*** dimak has quit IRC15:38
*** dimak has joined #openstack-meeting15:39
*** brault has quit IRC15:41
*** reedip_ has quit IRC15:42
*** brault has joined #openstack-meeting15:45
*** caboucha has joined #openstack-meeting15:45
*** yamahata has joined #openstack-meeting15:47
*** ircuser-1 has quit IRC15:47
*** links has quit IRC15:49
*** tobberydberg has joined #openstack-meeting15:49
*** spzala has quit IRC15:51
*** spzala has joined #openstack-meeting15:51
*** marios has quit IRC15:51
*** ircuser-1 has joined #openstack-meeting15:52
*** Sukhdev_ has joined #openstack-meeting15:53
*** martinkopec has quit IRC15:55
*** abhishekk_ has joined #openstack-meeting15:55
*** spzala has quit IRC15:55
*** tobberydberg has quit IRC15:56
*** pcaruana has quit IRC15:57
*** jaypipes has quit IRC15:58
*** wxy- has joined #openstack-meeting15:59
smcginnis#startmeeting Cinder16:00
openstackMeeting started Wed Aug 16 16:00:28 2017 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at
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
_pewp_jungleboyj ( ・_・)ノ16:00
*** preisner has quit IRC16:00
smcginnisdulek duncant eharney geguileo winston-d e0ne jungleboyj jgriffith thingee smcginnis hemna xyang1 tbarron scottda erlon jbernard _alastor_ bluex karthikp_ patrickeast dongwenjuan JaniceLee cFouts Thelo vivekd adrianofr mtanino karlamrhein diablo_rojo jay.xu jgregor lhx_ rajinir wilson-l reduxio wanghao thrawn01 chris_morrell watanabe.isao,tommylikehu mdovgal ildikov wxy viks ketonne abishop16:00
_pewp_hemna \(-_- )16:01
*** slaweq has joined #openstack-meeting16:01
*** abishop has joined #openstack-meeting16:02
smcginnisShort agenda today. Any bets we'll take the whole time anyway? :)16:02
DuncanTThat time already?16:02
lhx__o/ hi16:02
jungleboyjIt's a DuncanT !16:02
*** tobberydberg has joined #openstack-meeting16:02
smcginnis#topic Announcements16:03
*** openstack changes topic to "Announcements (Meeting topic: Cinder)"16:03
jungleboyjsmcginnis:  All bets are off.16:03
smcginnisWe are now in R-2. The end is near.16:03
smcginnisJust reminders that we are in hard string freeze now, so we should not allow anything with translations into stable/pike.16:04
* jungleboyj is picturing the sandwich board again.16:04
*** Guest20591 is now known as cFouts16:04
smcginnisBut if we have anything else critical, make sure you are proposing backport to stable/pike.16:04
*** lpetrut has quit IRC16:04
smcginnisWe also have some os-brick and python-cinderclient patches merged for stable issues.16:05
smcginnisWe are still in freeze for those. Queens has not officially opened up yet.16:05
smcginnisStill a few more housekeeping things need to be done before we can really open the flood gates.16:05
smcginnisBut as soon as that's through, we will get stable releases of those libraries for a couple important bug fixes.16:06
ildikovsmcginnis: +1 :)16:06
*** slaweq has quit IRC16:06
smcginnisildikov: I know you are just waiting there. :)16:06
ildikovsmcginnis: story of my life :)16:07
smcginnis#link Planning etherpad for PTG16:07
smcginnisildikov: Hah!16:07
smcginnisGetting more topics for the PTG. That's great. Please keep adding things as they come up.16:07
smcginnisI can now leave it to jungleboyj to decide how to arrange them. :)16:08
smcginnisjungleboyj: I will try to avoid it as much as possible, but realized I may have some conflicts now Wed-Fri.16:08
jungleboyjsmcginnis:  You can't leave me!16:09
smcginnisjungleboyj: Fly little birdy, fly! :P16:09
smcginnis#link PTG registration16:09
*** tobberydberg has quit IRC16:10
smcginnisIf you haven't yet, please register for the ptg.16:10
jungleboyjsmcginnis:  I will coordinate with your schedule if there are things you want to make sure you are available for.16:10
smcginnisjungleboyj: ++16:10
smcginnisdiablo_rojo_phon: Do we have any numbers yet on registration?16:10
jungleboyjPeople actually used the hotel this time.  :-)16:10
*** dmellado has quit IRC16:11
diablo_rojo_phonOverall registration is around 300 I think?16:11
diablo_rojo_phonHotel block is full16:11
smcginnisGood, that seems better than ATL at this time of the cycle.16:11
diablo_rojo_phonThere are still rooms available but you don't get the rate anymore.16:11
*** Manuel_112 has joined #openstack-meeting16:12
lhx__smcginnis, what number do you mean, the number of people that cinder room can hold?16:12
smcginnislhx__: Was just curious on both the total number of registered attendees as well as Cinder attendees.16:13
smcginnisdiablo_rojo_phon: Any idea how many are planning to attend Cinder? Actually can't remember now if it asked this time.16:13
jungleboyjsmcginnis:  I don't remember that it did.16:14
lhx__smcginnis, 300 seems a big number :)16:14
tommylikehu12 on the etherpad16:14
*** Apoorva has joined #openstack-meeting16:14
smcginnislhx__: Yeah, not bad.16:14
diablo_rojo_phonHaven't looked. The numbers weren't that reliable last time though.16:14
jungleboyj:-)  The regulars.16:15
smcginnistommylikehu: I'm hoping there's more than 12. :)16:15
jungleboyjtommylikehu:  Any update from you?16:15
tommylikehujungleboyj:  no :(16:15
smcginnisGood reminder though - please add your name to the etherpad if you are planning (or hoping) to attend.16:15
smcginnistommylikehu: Oh man, really?16:15
smcginnistommylikehu: That's too bad.16:15
tommylikehusmcginnis:  ok, I am wrong it's 1316:15
smcginnisHa! :)16:15
smcginnis#topic Open Discussion16:16
*** openstack changes topic to "Open Discussion (Meeting topic: Cinder)"16:16
smcginnisAnyone have anything important to discuss as a team?16:16
*** Manuel_112 has quit IRC16:16
jungleboyjIs there any update on our mascot?16:17
smcginnisjungleboyj: I see a mix of the new and the new-new mascot being used. I haven't received anything other than the old one.16:17
tommylikehujungleboyj:  what update?16:18
jungleboyjI feel like they threw something at us to appease us but the links on the website haven't been updated.16:18
smcginnisjungleboyj: I have a bunch of stickers for you now.16:18
jungleboyjtommylikehu:  Like when they are going to add something to the offical list.16:18
smcginnisjungleboyj: Kind of got caught with Heidi Joy leaving.16:18
jungleboyjsmcginnis:  Which version?16:18
smcginnisjungleboyj: Old-new16:18
jungleboyjsmcginnis:  Oh, that is right.16:18
xyang1smcginnis: have they turned that thing around?  Do we see head now?:)16:19
smcginnisxyang1: Backen.16:19
jungleboyjxyang1:  You wish.16:19
*** Apoorva_ has joined #openstack-meeting16:19
smcginnisbrb Talk amongst yourselves. :)16:19
xyang1Too bad:)16:19
jungleboyjjgriffith:  Did you hear about smcginnis ?16:20
jgriffithjungleboyj ?16:20
smcginnisOK, that was quicker than I thought.16:20
smcginnisNo talking about my hair and starting rumors. :D16:20
jungleboyjjgriffith:  Nevermind , he is back.  ssshhhh.  ;-)16:20
jgriffithOh that!!!16:21
smcginnisAnything else or should we wrap up?16:21
jungleboyjsmcginnis:  Was just going to say you have a new office.  ;-)16:21
hemnaso I'm working on setting up an env to try out the active active HA for a few drivers, since it seems nobody has.16:21
xyang1Congrats to both jungleboyj and smcginnis !16:21
jungleboyjhemna:  That is great.16:21
jungleboyjI think pots has been doing work around that for the Lenovo driver as well.16:22
jungleboyjxyang1:  Thank you!16:22
smcginnishemna: Awesome!16:22
smcginnisxyang1: Thanks :)16:22
lhx__hemna, do you have a blog to share?16:22
hemnanah not yet, I'm just setting up my 2 blades16:23
hemnajust starting really.16:23
smcginnisjungleboyj: In new office now. Thought my chair was here before when I had to run to the door, but I had just locked my wife out. :D16:23
*** Apoorva has quit IRC16:23
*** tobberydberg has joined #openstack-meeting16:23
smcginnisTesting HA, and getting drivers certified, defnitely needs to happen in Queens.16:23
smcginnisI feel like we announced we have HA and then told everyone they can't use it.16:24
hemnamy plan is to try out ceph and 3par16:24
hemnasmcginnis, yup...we did.16:24
jungleboyjsmcginnis:  Awesome!  The office, not locking the wife out.16:24
e0ne hemna: cool. feel free to ping me if you need any help with ceph16:24
jungleboyjsmcginnis:  Agreed.  Need to focus on that stuff in Queens.16:24
hemnae0ne, thanks I'm sure I'll need to at some point :)16:25
smcginnisOK, let's wrap it up then.16:26
smcginnisThanks everyone.16:26
_pewp_jungleboyj (。・∀・)ノ16:26
*** openstack changes topic to "OpenStack Meetings ||"16:26
openstackMeeting ended Wed Aug 16 16:26:40 2017 UTC.  Information about MeetBot at . (v 0.1.4)16:26
openstackMinutes (text):
lhx__e0ne, hah, another guru for ceph besides Gorka :)16:26
*** abalutoiu has quit IRC16:26
*** tobberydberg has quit IRC16:27
lhx__thanks smcginnis16:28
*** ihrachys has quit IRC16:28
*** abishop has left #openstack-meeting16:30
*** Apoorva_ has quit IRC16:31
*** Apoorva has joined #openstack-meeting16:31
*** TxGirlGeek has joined #openstack-meeting16:32
*** e0ne has quit IRC16:33
*** yamahata has quit IRC16:36
*** yangyapeng has quit IRC16:44
*** lpetrut has joined #openstack-meeting16:45
*** tobberydberg has joined #openstack-meeting16:47
*** yangyapeng has joined #openstack-meeting16:47
*** rcernin has joined #openstack-meeting16:49
*** tobberydberg has quit IRC16:52
*** spzala has joined #openstack-meeting16:52
*** yangyapeng has quit IRC16:52
*** dprince has quit IRC16:58
*** tobberydberg has joined #openstack-meeting16:58
*** anilvenkata has quit IRC16:58
*** JudeC has joined #openstack-meeting16:59
johnsom#startmeeting Octavia17:00
openstackMeeting started Wed Aug 16 17:00:04 2017 UTC and is due to finish in 60 minutes.  The chair is johnsom. Information about MeetBot at
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
*** strigazi_OFF is now known as strigazi17:00
johnsomHi folks17:00
johnsomI expect it to be pretty quiet this week17:00
johnsom#topic Announcements17:01
*** openstack changes topic to "Announcements (Meeting topic: Octavia)"17:01
johnsom"You are stuck with me for another release" or johnsom is Queens PTL17:01
johnsomNo one ran against me so per OpenStack election rules I am your PTL again for Queens.17:01
johnsomI'm looking forward to it.  We have some great things to get done.17:02
johnsomJust a reminder, the PTG is coming up: PTG is September 11-15th17:02
*** tobberydberg has quit IRC17:02
*** slaweq has joined #openstack-meeting17:03
johnsomPlease sign up whether you are attending and add any topics you think we should cover.17:03
johnsomRoom schedules, etc. are almost done so soon I will work on our schedule as well17:03
*** Swami has joined #openstack-meeting17:04
johnsomAny other announcements?17:04
johnsom#topic Planning an octavia RC2 this week17:04
*** openstack changes topic to "Planning an octavia RC2 this week (Meeting topic: Octavia)"17:04
johnsomThere are two bugs that have enough impact I think we should cut an RC2 for Pike17:05
johnsomFix a bad revert method and add hacking check17:05
johnsomFix health monitor DB locking17:05
johnsomBoth are waiting on reviews before we can start the backport/RC2 work17:05
*** sshank has joined #openstack-meeting17:06
johnsomAny comments on those or other candidates folks would like to propose?17:06
rm_mobileI'll look this morning17:06
*** diablo_rojo has joined #openstack-meeting17:07
johnsomThank you!  I expect this will take some time for backports/reviews etc. and the RC2 window is closing.17:07
*** slaweq has quit IRC17:07
*** lpetrut has quit IRC17:07
johnsomOnce RC2 is cut and we have had a few days we can consider doing an early Pike release.  There is a bunch of stuff pending that can probably fast merge for Queens17:08
johnsom#topic Brief progress reports / bugs needing review17:08
*** openstack changes topic to "Brief progress reports / bugs needing review (Meeting topic: Octavia)"17:08
johnsomI have mostly been looking into these bugs and updating the OSC plugin to give better error messages.17:09
*** Sukhdev_ has quit IRC17:09
johnsomI don't think we can get that into the official Pike release, but we can do a release early in queens.17:09
johnsomAny other updates or patches of note?17:10
johnsom#topic Open Discussion17:10
*** openstack changes topic to "Open Discussion (Meeting topic: Octavia)"17:10
johnsomAny other topics for today?17:11
johnsomI guessed it was going to be quiet today....17:11
johnsomOk, thanks for joining.  See you in the channel!17:12
*** openstack changes topic to "OpenStack Meetings ||"17:12
openstackMeeting ended Wed Aug 16 17:12:12 2017 UTC.  Information about MeetBot at . (v 0.1.4)17:12
openstackMinutes (text):
*** Manuel_112 has joined #openstack-meeting17:13
*** yamahata has joined #openstack-meeting17:16
*** Manuel_112 has quit IRC17:18
*** Jamemcc_ has quit IRC17:18
*** lhx__ has quit IRC17:19
*** toscalix has quit IRC17:21
*** e0ne has joined #openstack-meeting17:21
*** sambetts is now known as sambetts|afk17:23
*** Apoorva has quit IRC17:23
*** Apoorva has joined #openstack-meeting17:23
*** markstur_ has joined #openstack-meeting17:26
*** dprince has joined #openstack-meeting17:26
*** tobberydberg has joined #openstack-meeting17:29
*** markstur has quit IRC17:29
*** Apoorva_ has joined #openstack-meeting17:30
*** Sukhdev has quit IRC17:32
*** Apoorva has quit IRC17:33
*** tobberydberg has quit IRC17:33
*** spzala has quit IRC17:34
*** e0ne has quit IRC17:34
*** spzala has joined #openstack-meeting17:35
*** spzala has quit IRC17:39
*** donghao has quit IRC17:39
*** ricolin has quit IRC17:46
*** lpetrut has joined #openstack-meeting17:50
*** bh526r has joined #openstack-meeting17:53
*** krenczewski has joined #openstack-meeting17:54
*** gongysh has quit IRC17:54
*** ociuhandu has quit IRC17:55
*** strigazi is now known as strigazi_OFF17:55
*** e0ne has joined #openstack-meeting17:57
bh526r#startmeeting gluon18:00
openstackMeeting started Wed Aug 16 18:00:17 2017 UTC and is due to finish in 60 minutes.  The chair is bh526r. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: gluon)"18:00
openstackThe meeting name has been set to 'gluon'18:00
bh526r#topic Roll Call18:00
*** openstack changes topic to "Roll Call (Meeting topic: gluon)"18:00
*** electrofelix has quit IRC18:00
bh526r#info Bin Hu18:00
jinli#info JinLi18:00
jinliHi Bin18:00
bh526rHi Jin18:00
bh526rlooks like only you and I. so let's quickly discuss those patches18:01
bh526r#topic Pike Status18:01
*** openstack changes topic to "Pike Status (Meeting topic: gluon)"18:01
bh526r#info Bin cut the stable/pike branch, and tagged 1.0.518:02
bh526r#info There are 4 outstanding patches18:02
jinliHi paul18:02
bh526rHi Paul18:02
bh526r#info Patch 1: Gluon object-level authorization18:03
bh526r#info Patch 2: Policies in yaml18:03
krenczewski#info Kamil Renczewski18:03
*** slaweq has joined #openstack-meeting18:03
*** spzala has joined #openstack-meeting18:03
bh526rHi Kamil18:03
jinliHi Kamil18:04
bh526r#info Bin, Jin and Tin discussed offline, and concluded that for Gluon, because the APIs are generated from YAML, putting policies in YAML is a more flexible way for Gluon18:05
bh526r#info Default policies will be in base.yaml.18:05
*** zhouyaguo has quit IRC18:05
*** zhouyaguo has joined #openstack-meeting18:06
bh526r#info Policies for new services (new YAML) will be defined in the same YAML. In this case, service-specific policies defined in YAML will be used18:06
bh526r#info If new YAML doesn't contain service-specific policies, default policies in base.YAML will be used18:06
*** e0ne has quit IRC18:07
bh526r#info Jin will finalize the coding in above 2 patches this week based on the way to go18:07
bh526r#info Patch 3: WIP: Resolve warnings in Sphinx documentation18:08
*** e0ne has joined #openstack-meeting18:08
bh526r#info This patch seems completed.18:08
*** e0ne has quit IRC18:08
*** slaweq has quit IRC18:09
bh526r@jinli, I saw your comments and new patchset uploaded by Omar.18:09
bh526rDo you have more comments?18:09
*** pcaruana has joined #openstack-meeting18:09
jinliI think this patch should be ok, I just have some questions.18:09
jinlilet me discuss with Omar18:10
jinlithen we can merge it later this week18:10
bh526rsounds good to me. So I will wait for your signal18:10
jinliTin reviewed it and gave a +1, Tin is the one who discovered this issue18:10
jinliTin gave +1 in patch 518:11
bh526rI see. Now it is patchset 6.18:11
jinliI am glad we fix this issue. it causes random errors and fail jenkin once a while18:12
bh526rCan you discuss with Omar, and check with Tin regarding your questions on patchset 6?18:12
bh526rIf you are good, we can merge it later this week18:12
bh526r#info Jin has some comments. Jin will discuss with Omar and double check with Tin.18:13
bh526r#info If everything is fine, it will be approved. Bin will take action to merge it.18:14
bh526r#info Patch 4: The para into "add_model()“ should be changed to model in function ”build_api()“18:14
*** slaweq has joined #openstack-meeting18:15
bh526rany comments on this patch?18:15
*** JudeC has quit IRC18:15
jinlithat load_model_for_service(service) is a singleton, so it doesn't make that much difference to replace it with model.18:16
jinlithe patch is ok, less confusing18:16
bh526rIf no more comments, I suggest we approve it.18:17
*** tobberydberg has joined #openstack-meeting18:18
bh526r#info Group approved it. Bin will take the action to merge it in master and cherrypick to stable/pike18:19
bh526rI think that's all outstanding patches.18:19
*** tobberydberg has quit IRC18:19
*** tobberydberg has joined #openstack-meeting18:20
*** makowals_ has joined #openstack-meeting18:21
bh526rKamil, do you feel we can do a PoC in Sydney with Contrail really working with ODL?18:21
*** ociuhandu has joined #openstack-meeting18:21
krenczewskiI think yes18:21
*** tobberydberg has quit IRC18:22
bh526rGeorg is still on family leave.18:22
krenczewskiI didn't discuss details about Sydney summin with Sukhdev yet18:22
*** tobberydberg has joined #openstack-meeting18:22
krenczewskiSo we need to agree on scenario first18:22
bh526rI will draft the demo scenario, and share with you18:22
krenczewskiOK, great18:23
bh526rThen we can see which are doable, and which are stretch18:23
bh526rInput from Georg is also important once he comes back18:24
bh526rLet me put together the scenario first, and we can discuss it further.18:25
bh526r#topic AOB18:25
*** openstack changes topic to "AOB (Meeting topic: gluon)"18:25
krenczewskiWe're working on same lab as previously?18:25
bh526r#info Group discussed a potential PoC/demo in Sydney summit18:26
bh526rYes, the same lab is working as I checked last week.18:26
bh526rIn Germany18:26
krenczewskiI will need to re-deploy Contrail18:26
*** tobberydberg has quit IRC18:26
krenczewskiWe're using now R4.0 branch, previously was R3.118:27
bh526rSurely, because this time, we want to see the API calls go through Contrail, and through ODL18:27
bh526rAnd we also need to re-deploy Gluon once we have stable Pike version18:27
bh526r#info We need to:18:29
bh526r#info 1. Complete Gluon Pike stable version18:29
bh526r#info 2. Re-deploy Gluon18:29
bh526r#info 3. Re-deploy Contrail (4.0)18:29
bh526r#info 4. Double check Lab's availability18:30
bh526r#info 5. perhaps re-deploy ODL and ONOS18:30
bh526r#info 6. Ensure API call flows through Contrail, ODL and ONOS18:30
bh526r#info Bin will draft the demo scenarion first, and share with everyone for further discussion18:31
bh526ranything else?18:31
krenczewskiI am good18:32
bh526rgreat and thank you.18:32
bh526rIf nothing else, we can adjourn our meeting for now18:32
*** unicell has joined #openstack-meeting18:32
bh526r#info Meeting adjourned18:33
*** openstack changes topic to "OpenStack Meetings ||"18:33
openstackMeeting ended Wed Aug 16 18:33:06 2017 UTC.  Information about MeetBot at . (v 0.1.4)18:33
openstackMinutes (text):
bh526rthank you everyone, and bye all18:33
krenczewskiThank you, Bye18:33
jinlibye all118:33
*** marst_ has joined #openstack-meeting18:34
*** sshank has quit IRC18:37
*** marst has quit IRC18:37
*** thingee_ has joined #openstack-meeting18:40
*** Manuel_112 has joined #openstack-meeting18:43
*** tobberydberg has joined #openstack-meeting18:46
*** Manuel_112 has quit IRC18:49
*** tobberydberg has quit IRC18:51
*** Sukhdev has joined #openstack-meeting18:52
*** e0ne has joined #openstack-meeting18:54
*** rm_mobile has quit IRC18:59
fungifrom chatter in #storyboard, sounds like probably no meeting this week19:00
*** bh526r has quit IRC19:08
*** armstrong has joined #openstack-meeting19:11
*** krenczewski has quit IRC19:18
*** simon-AS559 has joined #openstack-meeting19:23
*** adisky__ has quit IRC19:23
*** pchavva has quit IRC19:26
*** simon-AS559 has quit IRC19:39
*** Sukhdev has quit IRC19:43
*** jprovazn has quit IRC19:43
*** yangyapeng has joined #openstack-meeting19:44
*** rmascena has joined #openstack-meeting19:48
*** yangyapeng has quit IRC19:49
*** raildo has quit IRC19:51
*** rcernin has quit IRC19:55
*** abhishekk_ has quit IRC19:55
*** sshank has joined #openstack-meeting20:00
*** Manuel_112 has joined #openstack-meeting20:11
*** sshank has quit IRC20:11
*** trozet has quit IRC20:11
*** Sukhdev has joined #openstack-meeting20:13
*** sshank has joined #openstack-meeting20:14
*** Manuel_112 has quit IRC20:16
*** dprince has quit IRC20:18
*** sshank has quit IRC20:18
*** sshank has joined #openstack-meeting20:18
*** trozet has joined #openstack-meeting20:26
*** rmascena has quit IRC20:29
*** makowals_ has quit IRC20:36
*** e0ne has quit IRC20:36
*** trozet has quit IRC20:40
*** pcaruana has quit IRC20:41
*** torgomatic has joined #openstack-meeting20:44
*** simon-AS559 has joined #openstack-meeting20:45
*** gouthamr has quit IRC20:46
*** Apoorva_ has quit IRC20:47
*** Apoorva has joined #openstack-meeting20:47
*** felipemonteiro_ has quit IRC20:48
*** brault has quit IRC20:49
*** thingee_ has quit IRC20:49
*** esberglu has quit IRC20:50
*** esberglu has joined #openstack-meeting20:50
*** cleong has quit IRC20:51
*** ykatabam has joined #openstack-meeting20:54
*** trozet has joined #openstack-meeting20:54
*** esberglu has quit IRC20:55
*** diablo_rojo has quit IRC20:55
*** lpetrut has quit IRC20:56
*** rledisez has joined #openstack-meeting20:57
*** simon-AS559 has left #openstack-meeting20:57
*** diablo_rojo has joined #openstack-meeting20:57
*** lpetrut has joined #openstack-meeting20:58
*** spzala has quit IRC20:58
*** acoles has joined #openstack-meeting20:59
*** joeljwright has joined #openstack-meeting20:59
notmynameswift team meeting time21:00
notmyname#startmeeting swift21:00
openstackMeeting started Wed Aug 16 21:00:51 2017 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at
*** spzala has joined #openstack-meeting21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
openstackThe meeting name has been set to 'swift'21:00
notmynamewho's here for the swift team meeting?21:01
joeljwrighthello o/21:01
rledisezhi o/21:01
notmynameclayg: ping21:02
*** timburke has joined #openstack-meeting21:02
notmynameall right, let's get started21:02
timburkei'm here, i'm here!21:02
notmynametimburke: :-)21:03
notmynamea couple of topics to go over this week21:03
*** vishwana_ has quit IRC21:03
notmyname#topic pre/post amble patch21:03
*** openstack changes topic to "pre/post amble patch (Meeting topic: swift)"21:03
notmynamelet me set some context here21:03
*** esberglu has joined #openstack-meeting21:03
*** vishwanathj has joined #openstack-meeting21:04
notmynamewe have from joeljwright that's been open a while21:04
notmynamehmm.. patchbot isn't joining...21:04
timburke"Add Preamble and Postamble to SLO and SegmentedIterable"21:05
*** spzala has quit IRC21:05
claygi've seen more patchsets than that21:05
claygi'm only mildly impressed21:05
notmynameok, so joeljwright is asking for a reasonable thing: is this patch (and therefore the idea behind it) something that we will actually land, or should he investigate other options21:05
notmynamea historic IRC conversation was at21:05
*** slaweq has quit IRC21:06
notmynamein my opinion, it seems like a relatively novel extension to the SLO manifest format that is not breaking anything existing and that adds new functionality21:06
*** slaweq has joined #openstack-meeting21:06
*** VW_ has joined #openstack-meeting21:06
notmynamebut to quote the earlier conversation "there's such a huge difference between "this patch is good enough to land" and "this patch should land" " and "I'm a little worried about inventing something to solve a bunch of use cases that we make up"21:07
notmynameso... joeljwright, where does that leave us?21:07
*** kota_ has joined #openstack-meeting21:07
notmynameshare more about your use of this functionality at sohonet21:07
* kota_ is late21:07
notmynamekota_: welcome. we're just getting started (you didn't miss much)21:08
joeljwrightwell, this all came about when we wanted to share multiple files using a tempurl and preserve some structure (so initially a tarball)21:08
joeljwrightbut when we started the work we realised it could be so much more21:08
claygjoeljwright: notmyname was highlighting that you're past "this is one way I can see to solve this" and all the way into "we're using this and it is working"21:08
claygfor like ... business needs - not just like "i tested it and it does what it says on the tin"21:08
joeljwrighthence the generic extension to SLO21:08
joeljwrightyes, we're not using exactly this (because it's not released)21:09
notmynameyeah, what clayg said is what i'm interested in21:09
joeljwrightbut it makes a big difference to our use case of building tarballs using existing segments21:09
joeljwrightwe don't want to store thousands of tiny objects21:09
*** VW has quit IRC21:09
joeljwrightbecause download performance is bad21:09
joeljwrightand we're not interested in that data21:10
notmynamethe tiny objects being the *ambles for tarfile segments?21:10
joeljwrightyes, sorry21:10
joeljwrightin order to build tarballs we have to generate 2 very small objects for every stored object21:10
joeljwrighta tar header and tar padding21:10
joeljwrightboth in the 0-1024 byte size range21:11
*** patchbot has joined #openstack-meeting21:11
*** VW_ has quit IRC21:11
*** slaweq has quit IRC21:11
notmynameok. and you're using this today in prod?21:11
joeljwrightin exploring how to make it better we realised that with a fairly simple addition to SLO we could explore not only tar, but also buyilding other container formats21:11
joeljwrightwe're using a related version in testing21:12
claygyeah, I think doing the tar SLO client side is weird - I could see just *not* bothering with the tar and just making the client do GET for the objects it wants but *shrug* in the tempurl case (before) prefix... there's some flexibility here to be really prescriptive21:12
joeljwrightwe haven't deployed it to prod because of maintaining a patch21:12
notmynameok. did you find other non-tar formats that work here?21:12
claygyou can download these 10K things, in a tarball, with this single tempurl21:12
joeljwrightclayg: to extend that "with these names, and fail if anything on disk changes"21:13
claygi do believe that is a thing that will be useful from time to time - if they can figure out how to solve that with this they probably could have figured out a way to solve it w/o this21:13
claygjoeljwright: good point!21:13
claygso... where are you at?21:13
claygI think a lot of people have got past "yeah that is probably be a thing we could do"21:13
joeljwrightcurrently I have a test system that uses this patch and builds the premables/postambles manually21:14
joeljwrightI also have an experimental middleware that's just a pre-SLO manifest transform to make the headers/padding21:14
clayglike stub data - or using your data model?  Like your business use case?  with the existing segments and stuff?21:14
joeljwrightclayg: can you elaborate what you're after21:15
rledisezjoeljwright: is there any reason not to dynamically generate the tar headers on a requests (eg: POST req containing the list of objects to include in the archive)? i don't know the tar format, but i used to do that for zip. maybe it just does not match your use case21:15
claygthe manifests are big right?  a few MB?  Can you share for a production like use-case one a real world example?21:15
joeljwrightyeah, our main product that uses Swift is a file transfer application21:16
claygrledisez: that cuts out the tempurl use case - or at least you still have to distribute a manifest thing that enumerates the things21:16
joeljwrightwe build packages to be downloaded by recipients who do not have swift accounts21:16
joeljwrightwe use SLO + tempurl to achieve this21:16
claygrledisez: I think it's related but distinct from joeljwright's use-case - but there is probably a use-case to make for more dynamic stuff too.21:16
joeljwrightrledisez: the reason not to do it dynamically is to get the SLO data validation check21:17
notmynameone thing I like about joeljwright's patch is that it has the hooks for future stuff like dynamic *ambles, but it does not add that complexity now21:17
joeljwrightif it downloads/validates the data is what the sender wanted to share21:17
claygjoeljwright: specific elaboration on what I'm after (not sure if this helps anyone else) a real world example of a for-realzy-sovling-a-customer-use-case segment with *ambles21:17
claygLike... in python stdlib folks always say "wouldn't it be great if this was in stdlib" and python core be like "yeah, probably, you should put it on pypi and after a bunch of people use it and you flesh out some of the edges of rubber meats the road we'll bring it in"21:18
joeljwrightthe only real-world I need it now use case is making tar-SLOs that don't cripple performance with loads of read for tiny objects on the object servers21:18
timburkei'm still a little up in the air about whether the inline data should be attached to a segment or to have a new "segment type" -- but i guess since we already have the *amble patch, may as well go with it? what i definitely *don't* want to do is change our minds on it after-the-fact21:18
joeljwrightI have other things I want to explore - zip, ISO even mov21:18
claygare you *waiting* on upstream to enter "maintenance" mode before you *use* it?  Don't wait on us.  Show us how stupid we are for not having it work *exactly like this* already21:19
*** thorst has quit IRC21:19
joeljwrightI have been waiting for upstream to validate that I'll get it eventually before I use it in production21:19
joeljwrightotherwise I have to maintain many different code bases21:19
claygi think that's created some of the tension we're experiencing21:20
claygi mean middleware is middleware - i have middleware - lots of people that run swift have middleware - you're supposed to?21:20
claygrledisez: you have middleware?21:20
notmynamejoeljwright: ok, so to clarify, you've got a real problem, you've got a pretty cool idea on how it could be solved and patch for that, but you have *not* actually used this functionality yet to solve your problem in prod21:20
joeljwrightthe problem with this approach is it requires patching SLO and helpers21:20
rledisezclayg: sure…21:20
joeljwrightnotmyname: that's a fair assessment, I've held off pushing to get this in prod21:21
* timburke has definitely *never* released a spike of a swift-provided middleware...21:21
joeljwrightI would deploy it tomorrow if I could though :)21:21
notmynameyeah, I can sympathinze with joeljwright's position, though, because he's not only maintaining swift in prod, AFAIK he's the only one doing it and adding the differences from upstream (even just patching slo middleware locally) could be daunting21:22
claygok, well I'm not saying that should change, and i'm *definitely* not saying that running hacks on upstream code is ideal (it definitely is crappy)21:22
notmynamebut it does create the tension of committing to support new SLO manifest formats forever in the hopes that we got the new stuff right before seeing it used21:23
notmynameit's a tricky situation21:23
timburkeclayg: thinking of use-cases, imagine researchers wanting to share large data sets together with the scripts used to analyze them21:23
timburkethe datasets are large, they don't want to waste space by uploading a separate tar copy. the scripts are small, so even if we solve the de-dupe problem with small objects for headers/padding, we still have the ratelimiting problem21:23
notmynametimburke: we can imagine a lot of places where new code could be useful... that's never been the problem, right?21:24
joeljwrightthis all feels a bit catch-2221:24
notmynameheh yes! totally unfair to joeljwright21:24
claygif I *had* such a use-case I would just see if joeljwright's existing solution works and then +2 (literally *works* for me!)21:24
timburkenotmyname: clayg was looking for "a real world example of a for-realzy-sovling-a-customer-use-case segment with *ambles" -- i gave him something!21:24
torgomatictimburke: +121:25
claygtimburke: nope - i don't need an *idea*21:25
notmynameso that's the thing here. as a big community (with different employers, different use cases, etc), to some extent we can't only approve the stuff that we personally see use cases for21:25
notmynamejoeljwright actually has a for realzy use case here. the question is more about if the give patch is maintainable by the community, *not* if it's actually useful functionality21:26
torgomaticclayg: isn't that what joeljwright's users have? like, he's got SLOs with big segments and tiny segments, and they make a tarball, but performance sucks due to all the tiny segments21:26
*** JudeC has joined #openstack-meeting21:27
joeljwrighttorgomatic: not to mention all the extra time making 3* the number of SLO manifests I really need :)21:27
notmynameso we get back to the basic question of "who's gonna review it?"21:28
notmynameright? is that where we're at?21:28
notmynameclayg: but I want to know your thoughts too. is joeljwright's existing use case ok? even though he admits he hasn't run this code in his prod yet?21:29
claygyou can't say someone's use case is "not ok"21:29
claygit'd be like saying "you're not mad at me"21:29
claygIt's just everytime I think about joel's use-case I write a TLO middleware - not add preamble to SLO21:30
notmynameright. sorry. I didn't want to trap your answer there.21:30
notmynameok, yeah. so if one wanted to solve downloading .tar files, one would likely do somethign a lot simpler than *ambles in SLOs21:31
timburkeand how much of slo does that reinvent? what about when you realize you want cpio archives instead?21:31
joeljwrighttimburke: you beat me to it21:31
notmynameand the *amble idea is interesting because we see that it might be useful, but it's not actually been asked for, even by joeljwright's users21:31
notmynamewhich makes it hard to justify the more complex solution21:31
notmynameclayg: is that about right?21:31
timburkei *am* a bit nervous about the number of variations we're adding to slo segments. that's one of the reasons i've been thinking about having "object" segments and "inline" segments -- i feel like it might make things easier to reason about21:32
claygidk, I think it's fine - if we have folks that "might" review it I don't think that really answer's joeljwright's problem really well21:32
*** edmondsw has quit IRC21:32
joeljwrighttimburke: that's a fair suggestion21:32
joeljwrightbut we'd probably want to stop inline-only manifests21:33
joeljwrightwhich is why I shied away from that21:33
claygtimburke: I have no strong intuition that I should prefer one solution over the other - it depends on the % of use-cases that need to envelope individual segments vs totally independent in-between and around datas21:33
joeljwrightI wanted to make it obvious that this is for making the data your store more useful21:33
claygboth are complex and workable21:33
joeljwrightnot storing data in manifests21:33
timburkeand i've certainly contributed! ... ...21:34
notmynamejoeljwright: so what do you want to see? review the current patch with a goal of landing it? it sounds to me that timburke has some interesting alternative suggestions21:34
clayglike - SLO's are almost turing complete now21:34
joeljwrightclayg: :D21:34
*** lpetrut has quit IRC21:34
timburkejoeljwright: on inline-only manifests... maybe just write the damn data?21:34
timburke"look, you wanted this data written, i wrote it! what else do you want?"21:35
timburke(as a non-slo, i mean)21:35
joeljwrightI'm really after some review that say (a) this is too complex or (b) this looks useful or (c) this would be better if you changed...21:35
timburkedefinitely b, maybe a21:35
joeljwrightI'd like to know if this has any likelihood of landing21:35
*** slaweq has joined #openstack-meeting21:36
joeljwrightbecause I need to solve this problem21:36
notmynameacoles: kota_: tdasilva: you all are being quiet. what are your thoughts? what do you see as the best path forward?21:36
torgomaticokay, I'll volunteer to take an in-depth look at it in the next few days21:36
joeljwrighttorgomatic: thanks!21:36
notmynametorgomatic: that's very helpful. thanks21:36
*** felipemonteiro has joined #openstack-meeting21:36
*** aeng has joined #openstack-meeting21:38
joeljwrightI'll be around on the swift channel if anyone wants to talk about this separately21:38
mattoliverauNow that I've heard of the problems joeljwright's having and how he solves it, it has me sold.. well that we need a solution. I haven't looked at the patch so can't say it's it, but willing to go look at it in the mindset of we should solve it21:38
kota_notmyname: still at catching up the history yet but...21:38
mattoliverauI'll find time to have an initial look today21:39
joeljwrightmattoliverau: kota_: thanks for looking!21:39
acolesI'm torn - I'd prefer not to make SLO more complex but I can see the desire to re-use SLO by adding ambles21:39
*** bobh has joined #openstack-meeting21:40
kota_primary question, i didn't find any reason why it is needed for tar archive case (it might be discussed before i joined here)21:40
notmynamekota_: yeah, that's in some of the earlier links21:40
joeljwrightkota_: the pre/postambles avoid the need to store tiny objects for tar header/padding21:41
kota_it looks just a feature to add binaries by manifest to each segment21:41
joeljwrightbut preserve the SLO features of validating that the data you wanted in the tar is what you're downloading21:41
claygtick tock21:41
notmynameok, I want to move on the meeting, but thank you for your comments here. let's see if I can summarize where we are21:41
claygI don't feel we're in a drastically different place that we've been before21:41
*** Manuel_112 has joined #openstack-meeting21:41
joeljwrightyeah, but 40 minutes is enough!21:42
kota_joeljwright: oic21:42
claygit is complex, it is worth solving, no one is *sure* what should change because we have no external pressure driving the design21:42
*** slaweq has quit IRC21:42
notmynameheh, clayg just summarized it very well21:42
joeljwrightclayg: maybe we can catch up some time tomorrow to talk about alternatives?21:42
claygjoeljwright: no, this code is already written21:43
*** Apoorva_ has joined #openstack-meeting21:43
notmynameand torgomatic and mattoliverau offered to look at the patch21:43
*** slaweq has joined #openstack-meeting21:43
joeljwrightI'll stop stressing now :)21:43
joeljwright(until the reviews arrive!)21:43
claygwe just have to have enough of a WAG at how to "qualify" it - and bandwidth to review21:43
notmynameok, let's move on. thank you joeljwright21:43
notmyname#topic deadlock patch21:43
*** openstack changes topic to "deadlock patch (Meeting topic: swift)"21:43
patchbotpatch 493636 - swift - Fix deadlock when logging from a tpool thread.21:43
notmynametorgomatic did a great job finding and solving this issue21:44
notmynamewe worried earlier this week that it would add some linux-only things, but that's been removed (so we still only test linux, but it might work somewhere else maybe)21:44
*** yamamoto has joined #openstack-meeting21:44
*** yamamoto has quit IRC21:45
notmynameclayg: you said we'd likely land this right after the meeting today :-)21:45
claygoh yeah, can answer any questions?21:45
claygthere's two I can NOT answer21:45
*** armstrong has quit IRC21:45
*** Apoorva has quit IRC21:46
clayg#1 how do we prevent this kind of lockup bug in future (no idea, it's a huge space, probably ripe)21:46
*** Manuel_112 has quit IRC21:46
clayg#2 is torgomatic some sort of super genius mutant (probably, we have some evidence of that, but one can not be sure - he may just be a cyborg)21:46
mattoliverauThat would confirm my theory that swiftstack Devs don't sleep21:47
*** sofianes has joined #openstack-meeting21:47
*** slaweq has quit IRC21:47
tdasilvaor are bots21:47
notmynametorgomatic: you just pushed a new patch set during this meeting. is it all good from your perspective? timburke, clayg, acoles: are you planning on or expecting to +A it shortly?21:47
claygwhat?  new patch set!?21:48
acolesnotmyname: I was planning to sleep shortly :)21:48
torgomaticnotmyname: I think it's good, but then, I would ;)21:48
notmynameacoles: proving mattoliverau and tdasilva wrong ;-)21:48
torgomaticclayg: added a check to make sure you can't unlock someone else's mutex, like threading._RLock has21:48
claygslry, I will +A it so hard21:49
*** eharney has quit IRC21:49
timburkeso...probably +A soon? might be worth having someone *outside* of swiftstack understand the problem and how this fixes it, though...21:49
claygI honestly need to package it today or in the am.. so.. my life is non-trivially better if we +A now - is that... workable for folks?21:49
claygI hate it when things happen to quickly - it's so foreign to how we normally work it makes me uneasy.21:50
notmynameok. mostly for this topic I just wanted to make sure people understand it and are aware of it21:50
claygAre we *supposed* to be this agile and responsive?!  Is this ok!?21:50
*** sshank has quit IRC21:50
tdasilvaclayg: if a patch doesn't take 6 months then something feels wrong?21:50
joeljwrighttdasilve: :D21:51
notmynameis there anyone who has *not* read the bug report and understand why this needs to be fixed ASAP?21:51
*** yamamoto has joined #openstack-meeting21:51
claygyeah I think understanding is useful-ish - because... and this came up this morning - this is so awesome we should probably backport it - it could be RC on lp bug #1575277 or lp bug #165971221:51
openstackLaunchpad bug 1575277 in OpenStack Object Storage (swift) "object-replicator goes into bad state when lockup timeout < rsync timeout" [Medium,Confirmed]
openstackLaunchpad bug 1659712 in OpenStack Object Storage (swift) "Object replicator hang" [Undecided,New]
notmynameif so, then read soon21:52
openstackLaunchpad bug 1710328 in OpenStack Object Storage (swift) "object server deadlocks when a worker thread logs something" [High,In progress] - Assigned to Samuel Merritt (torgomatic)21:52
rlediseznot very helpful, but i need to say this patch is amazing. what used to never work (logging in diskfile) now works perfectly!21:52
claygok, I'll probably kick it in ~1.5 hrs21:52
rledisezwe stressed it today with success21:52
*** thorst has joined #openstack-meeting21:53
notmynamerledisez: can you leave a short comment in gerrit saying that?21:53
claygrledisez: zomg rledisez doing *reviews*!?21:53
*** thorst has quit IRC21:53
notmynameok. last thing (and related to this patch)...21:53
claygtdasilva: i won't even be able to keep up we move so fast21:53
timburkerledisez: did that come up much for you before? i thought part of why it took so long to pin down was the fact that we *don't* do much logging in diskfile...21:53
notmyname#topic swift 2.15.1 for pike21:53
*** openstack changes topic to "swift 2.15.1 for pike (Meeting topic: swift)"21:53
clayg2.15.1 - best swift release YET21:53
notmynametiming for the pike release is coming up quickly. what's on master at the end of the week is what I'll be tagging for pike as 2.15.121:54
claygi have hard stop at 3pm, i might leave 2 mins early if we're not done21:54
rlediseztimburke: we figured it was because of this bug. alecuyer ahs been working around for so long, when we saw the patch coming, it was like "omg, we are so excited" :D21:54
*** felipemonteiro_ has joined #openstack-meeting21:54
notmynamewhich includes torgomatic's patch for the deadlock21:54
*** vishwana_ has joined #openstack-meeting21:54
notmynamerledisez: that's great :-)21:54
*** caboucha has quit IRC21:54
acolestimburke: IDK but I have distant memory that whenever I tried to add debug logging to diskfile something broke ... and maybe this was it21:54
notmynameany other questions/comments from anyone?21:55
claygthree cheers for torgomatic21:55
clayghip hip!21:55
acoleship hip21:55
torgomatic"hip hip hip hip awww!" is an appropriate set of cheers for a concurrency bug :)21:55
claygnotmyname: sorry, you said tag on Friday yeah!?21:55
notmynameland on master by friday. I'll tag this weekend or monday21:56
notmynamethank you, everyone, for coming21:56
tdasilvado we care for patch 472659 being in the release?21:56
patchbot - swift - Allow to rebuild a fragment of an expired object21:56
rledisezfor swift 2.15.1, i'd love to see this merged, i think it's ready now, last comment was about a header name, waiting for a +A ;) :
patchbotpatch 472659 - swift - Allow to rebuild a fragment of an expired object21:56
acoles <-review21:56
patchbotpatch 472659 - swift - Allow to rebuild a fragment of an expired object21:56
notmynamethanks especially for going over the *amble patchw ith joeljwright and joeljwright for sticking with us on it ;-)21:56
joeljwrightthanks everyone21:56
acolesok that's three request for same thing, it must happen!21:57
claygyes merge that one21:57
claygit must happen21:57
tdasilvaok, i was reviewing that today, will continue tomorrow21:57
notmynametdasilva: thanks21:57
acolestdasilva: thank you21:57
notmynamethanks for your work on swift21:57
*** openstack changes topic to "OpenStack Meetings ||"21:57
openstackMeeting ended Wed Aug 16 21:57:44 2017 UTC.  Information about MeetBot at . (v 0.1.4)21:57
openstackMinutes (text):
*** felipemonteiro has quit IRC21:57
*** timburke has left #openstack-meeting21:58
*** yamamoto has quit IRC21:58
*** vishwanathj has quit IRC21:58
*** priteau has quit IRC21:59
*** joeljwright has left #openstack-meeting21:59
*** sofianes has quit IRC22:00
*** sshank has joined #openstack-meeting22:00
*** iyamahat has joined #openstack-meeting22:07
*** jkilpatr has quit IRC22:09
*** xyang1 has quit IRC22:11
*** rledisez has left #openstack-meeting22:11
*** esberglu has quit IRC22:22
*** thorst has joined #openstack-meeting22:24
*** unicell has quit IRC22:26
*** unicell has joined #openstack-meeting22:27
*** thorst has quit IRC22:29
*** VW has joined #openstack-meeting22:33
*** felipemonteiro_ has quit IRC22:34
*** VW has quit IRC22:35
*** fnaval has quit IRC22:35
*** Manuel_112 has joined #openstack-meeting22:42
*** VW has joined #openstack-meeting22:42
*** bobh has quit IRC22:43
*** bobh has joined #openstack-meeting22:43
*** VW has quit IRC22:45
*** fnaval has joined #openstack-meeting22:46
*** Manuel_112 has quit IRC22:47
*** fnaval has quit IRC22:47
*** fnaval has joined #openstack-meeting22:47
*** bobh has quit IRC22:48
*** jkilpatr has joined #openstack-meeting22:49
*** edmondsw has joined #openstack-meeting22:49
*** brault has joined #openstack-meeting22:49
*** brault has quit IRC22:54
*** edmondsw has quit IRC22:54
*** esberglu has joined #openstack-meeting22:59
*** aeng has quit IRC23:02
*** esberglu has quit IRC23:03
*** marst_ has quit IRC23:06
*** makowals has quit IRC23:06
*** sshank has quit IRC23:10
*** makowals has joined #openstack-meeting23:11
*** thorst has joined #openstack-meeting23:11
*** thorst has quit IRC23:13
*** patchbot has quit IRC23:17
*** notmyname has quit IRC23:19
*** aeng has joined #openstack-meeting23:19
*** notmyname has joined #openstack-meeting23:23
*** gouthamr has joined #openstack-meeting23:27
*** chyka has quit IRC23:32
*** chyka has joined #openstack-meeting23:33
*** Swami has quit IRC23:33
*** spzala has joined #openstack-meeting23:34
*** Apoorva_ has quit IRC23:35
*** Apoorva has joined #openstack-meeting23:35
*** spzala has quit IRC23:38
*** Manuel_112 has joined #openstack-meeting23:43
*** chyka has quit IRC23:45
*** yangyapeng has joined #openstack-meeting23:45
*** Manuel_112 has quit IRC23:48
*** aeng has quit IRC23:49
*** gongysh has joined #openstack-meeting23:52
*** yangyapeng has quit IRC23:54
*** ekcs has joined #openstack-meeting23:59

Generated by 2.15.3 by Marius Gedminas - find it at!