Wednesday, 2017-06-07

*** dane_leblanc has quit IRC00:00
*** zhhuabj has quit IRC00:04
*** annabelleB has quit IRC00:07
*** markvoelker has quit IRC00:07
*** ihrachys has quit IRC00:12
*** annabelleB has joined #openstack-meeting00:12
*** artom has joined #openstack-meeting00:13
*** annabelleB has quit IRC00:15
*** zhhuabj has joined #openstack-meeting00:19
*** mtanino has quit IRC00:25
*** wanghao has joined #openstack-meeting00:26
*** sshank has quit IRC00:27
*** yamamoto_ has joined #openstack-meeting00:38
*** Julien-zte has joined #openstack-meeting00:43
*** yamamoto_ has quit IRC00:44
*** joehuang has joined #openstack-meeting00:52
*** jbadiapa has quit IRC00:52
*** Yipei has joined #openstack-meeting00:56
*** diablo_rojo has quit IRC00:56
*** dongfeng has joined #openstack-meeting00:58
*** yinxiulin has joined #openstack-meeting00:59
*** xiangxinyong has quit IRC00:59
*** jbadiapa has joined #openstack-meeting00:59
joehuanghello01:00
dongfenghi01:00
*** electrocucaracha has joined #openstack-meeting01:00
Yipeihi01:00
yinxiulinhello01:00
joehuang#startmeeting tricircle01:00
openstackMeeting started Wed Jun  7 01:00:52 2017 UTC and is due to finish in 60 minutes.  The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot.01:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:00
*** openstack changes topic to " (Meeting topic: tricircle)"01:00
openstackThe meeting name has been set to 'tricircle'01:00
*** Apoorva_ has joined #openstack-meeting01:01
joehuang#topic rollcall01:01
*** openstack changes topic to "rollcall (Meeting topic: tricircle)"01:01
joehuang#info joehuang01:01
dongfeng#info dongfeng01:01
Yipei#info Yipei01:01
yinxiulin#info xiulin01:02
joehuang#topic Pike-201:02
*** openstack changes topic to "Pike-2 (Meeting topic: tricircle)"01:02
joehuanghello, according to the plan, we'd like to tag the pike-2 on Jun.901:03
*** markvoelker has joined #openstack-meeting01:03
*** zhiyuan has joined #openstack-meeting01:03
zhiyuan#info zhiyuan01:04
joehuangis there any challenge for the pike-2?01:04
*** Apoorva has quit IRC01:04
*** Apoorva_ has quit IRC01:05
*** caowei has joined #openstack-meeting01:05
*** slaweq has joined #openstack-meeting01:05
dongfengactually no for me. my pagination feature can't catch up with it.01:05
*** tovin07_ has joined #openstack-meeting01:05
joehuangto Dongfeng, thanks01:05
joehuangI saw patches submitted for the pagination01:06
*** thorst_afk has joined #openstack-meeting01:06
dongfengyes, it need further test.01:06
Yipeistill working on lbaas, but i think i can finish it soon, still have some problems with health management01:06
Yipeiwill discuss it with you later01:07
joehuangIs there any new feature need to implement for LBaaS?01:07
*** priteau has joined #openstack-meeting01:08
*** fnaval has quit IRC01:08
Yipeinot sure yet, maybe health management needs some code01:08
joehuangGood01:08
joehuangTricircle not only can work with multi-region deployment, but also nova cells v201:09
joehuangfor nove cells v2, LBaaS will only work with one Nova instance, it'll be much easier01:09
*** slaweq has quit IRC01:10
*** fnaval has joined #openstack-meeting01:10
*** abalutoiu has quit IRC01:10
joehuangcurrently you are working on LBaaS in multi-region ( multi-nova instances) scenario01:10
Yipeino still one region01:11
Yipeino, still one region01:11
joehuangstill one region, ok01:11
*** thorst_afk has quit IRC01:11
*** thorst_afk has joined #openstack-meeting01:11
joehuangok, so we'll still tag the pike-2 on Jun.9, if patches can not land before this, will postpone to next cycle01:12
*** priteau has quit IRC01:12
joehuang#info tag pike-2 on Jun.901:12
joehuangBy the way, there will be a demo in OPNFV Beijing SUmmit next week01:14
joehuangAchieving Global Scale VNF High Availability with Multi-Site (Huawei Technologies, Orange, China Mobile)   http://events.linuxfoundation.org/events/archive/2017/opnfv-summit/extend-the-experience/opnfv-poc-zone01:15
joehuangnext week I'll be attending OPNFV Beijing summit.01:15
joehuangcan someone take the responsibility to chair the weekly meeting?01:15
*** gcb has quit IRC01:17
*** trozet has quit IRC01:17
zhiyuanI have submitted several bug fixes, can see if we can land them in pike-201:17
*** gcb has joined #openstack-meeting01:17
*** kevzha01 has joined #openstack-meeting01:17
joehuangok, will review these patches01:17
*** trozet has joined #openstack-meeting01:18
zhiyuanok, let me have a try01:18
joehuangthank you zhiyuan01:19
*** thorst_afk has quit IRC01:20
joehuangcommunity is working on storyboard experiment to see if launchpad can be migrated to storyboard01:21
joehuang#link https://storyboard-dev.openstack.org/01:22
joehuang#link https://storyboard.openstack.org/01:22
joehuang#link https://storyboard-blog.io/01:22
joehuang#link http://docs.openstack.org/infra/storyboard/01:23
joehuangHow do you think about using storyboard to replace launchpad?01:25
*** gyee has quit IRC01:25
zhiyuanhmm, need to go through this page "https://storyboard-blog.io/" to know more about storyboard01:27
joehuangIt's not so intuitive like launch pad01:27
joehuangand not sure how well it work with bug tracking01:27
joehuangand notification service01:28
*** zhurong has joined #openstack-meeting01:28
*** asselin_ has joined #openstack-meeting01:29
dongfengI will play with it and be more familiar with it.01:29
joehuangok, feedback are welcome in next weekly meeting01:30
zhiyuanI find that we can login with our ubuntu open ID01:30
*** fzdarsky_ has joined #openstack-meeting01:30
zhiyuanthe one we use to login review.openstack.org01:30
*** Julien-zte has quit IRC01:30
joehuang#info feedback for storyboard and opinion for migration01:31
*** asselin has quit IRC01:31
joehuang#topic open discussion01:31
*** openstack changes topic to "open discussion (Meeting topic: tricircle)"01:31
*** Julien-zte has joined #openstack-meeting01:31
joehuangother topic?01:31
Yipeiyes01:31
joehuangplease01:32
Yipeifor lbaas, after creating the lb, the lb and the amphora can be created successfully, but the health management cannot ping the amphora in the management network01:32
Yipeii checked01:32
*** RonghUI has joined #openstack-meeting01:33
*** fzdarsky has quit IRC01:33
Yipeiand found that the vlan tag of the interface o-hm0 of br-int is changed to 409601:33
Yipeiinstead of the one which is the same to the dhcp port of the health management network01:34
Yipeibefore creating the lb, the o-hm0 interface and the tap of the dhcp port is added to br-int01:35
*** cdub has joined #openstack-meeting01:35
Yipeiand share the same vlan tag01:35
Yipeiso the dhcp port is ping-able in default network namespace01:36
zhiyuanyipei, you mean ovs-vswitch will modify the vlan tag o-hm0 from a valid value to 4096?01:36
joehuangso the o-hm is not in the management network, it should be, isn't it?01:36
Yipeiyes01:36
Yipeito zhiyuan, yes01:36
*** edmondsw has quit IRC01:36
Yipeito joehuang, o-hm is a port added to the br-int, its ip and mac address are a port in management network01:37
*** SerenaFeng has joined #openstack-meeting01:38
diablo_rojo_phonjoehuang: if you or anyone  have any questions about storyboard in the #storyboard channel.01:38
joehuangok01:38
joehuangto diablo_rojo_phon01:39
*** yamamoto_ has joined #openstack-meeting01:40
*** unicell has quit IRC01:40
*** cdub has quit IRC01:40
zhiyuanstrange, if ovs-vswitch will set the vlan tag of a unrecognized interface to 4096, the original LB without Tricircle will have the same problem01:41
*** gongysh has joined #openstack-meeting01:41
Yipeialso, i checked the plugin.sh in octavia, there is not code for setting the vlan tag01:41
Yipeiso i think maybe there is something wrong when creating the o-hm0 interface manually. but i do i following the plugin.sh01:42
joehuang#link https://github.com/openstack/octavia/blob/master/devstack/plugin.sh#L28901:43
joehuanghow about the plugin for non-tricircle environment?01:43
Yipeinot tested, but should be OK, i will have a try01:44
joehuangyes, and check the ovs flow01:44
Yipeiafter running the line289, the vlan tag of o-hm0 port is 409601:45
joehuangthis is incorrect if VLAN tag is 409601:45
Yipeiwhich caused the problem discussed last week01:45
*** yamamoto_ has quit IRC01:45
zhiyuandid you apply all the parameter?01:46
zhiyuanI see this "-- set Interface o-hm0 external-ids:iface-id=$MGMT_PORT_ID"01:46
Yipeiyes, all the parameters, without any modification01:46
zhiyuanso I guess the vlan tag is set by ovs-agent01:47
*** cloudrancher has quit IRC01:47
*** cloudrancher has joined #openstack-meeting01:47
joehuangHow about the lb management network segment id in local neutron01:50
*** lbragstad has joined #openstack-meeting01:51
Yipeiyou mean whether the network id is in local neutorn?01:53
joehuangvlan id of the network in local neutron01:54
*** thorst_afk has joined #openstack-meeting01:56
Yipeito joehuang, i checked, the management network in the local neutron is vxlan01:56
joehuangor vxlan id01:56
joehuangyes, what's the vxlan id if it's vxlan network01:56
Yipeisegment_id is 108601:56
joehuangfor vxlan network, in the same node, there is one local vlan used inside that compute node01:58
zhiyuanis the port for o-hm0 created in local Neutron?01:58
*** iyamahat has quit IRC01:59
*** anilvenkata has joined #openstack-meeting01:59
*** yamahata has quit IRC01:59
joehuangneed to get port in local neutron too02:00
joehuangexcept get network02:00
Yipeito zhiyuan, no, it is created in central neutron02:00
joehuangok, time is up, please move to #openstack-tricircle for further discussion02:00
Yipeiok02:01
joehuang#endmeeting02:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"02:01
openstackMeeting ended Wed Jun  7 02:01:03 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)02:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tricircle/2017/tricircle.2017-06-07-01.00.html02:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tricircle/2017/tricircle.2017-06-07-01.00.txt02:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tricircle/2017/tricircle.2017-06-07-01.00.log.html02:01
*** dongfeng has left #openstack-meeting02:01
*** salv-orlando has joined #openstack-meeting02:05
*** salv-orl_ has quit IRC02:08
*** mriedem has quit IRC02:10
*** litao__ has joined #openstack-meeting02:16
*** yamamoto_ has joined #openstack-meeting02:16
*** galstrom_zzz is now known as galstrom02:22
*** SerenaFeng has quit IRC02:24
*** marst has joined #openstack-meeting02:27
*** lbragstad has quit IRC02:30
*** zhurong has quit IRC02:30
*** thorst_afk has quit IRC02:32
*** julim has joined #openstack-meeting02:32
*** thorst_afk has joined #openstack-meeting02:33
*** thorst_afk has quit IRC02:37
*** epico has joined #openstack-meeting02:40
*** galstrom is now known as galstrom_zzz02:41
*** edmondsw has joined #openstack-meeting02:46
*** dimtruck is now known as zz_dimtruck02:47
*** zz_dimtruck is now known as dimtruck02:47
*** mickeys has joined #openstack-meeting02:47
*** galstrom_zzz is now known as galstrom02:50
*** edmondsw has quit IRC02:51
*** mickeys has quit IRC02:52
*** links has joined #openstack-meeting02:52
*** diablo_rojo has joined #openstack-meeting02:54
*** dimtruck is now known as zz_dimtruck02:56
*** VW has joined #openstack-meeting02:59
*** Fdaisuke has joined #openstack-meeting03:00
*** rfolco has quit IRC03:03
*** jamesmcarthur has joined #openstack-meeting03:04
*** VW_ has joined #openstack-meeting03:04
*** VW has quit IRC03:04
*** slaweq has joined #openstack-meeting03:07
*** jamesmcarthur has quit IRC03:08
*** ricolin has joined #openstack-meeting03:08
*** electrocucaracha has left #openstack-meeting03:11
*** slaweq has quit IRC03:11
*** Yipei has quit IRC03:14
*** VW_ has quit IRC03:15
*** jamesmcarthur has joined #openstack-meeting03:17
*** dbecker has quit IRC03:19
*** jamesmcarthur has quit IRC03:19
*** jamesmcarthur has joined #openstack-meeting03:20
*** hongbin has joined #openstack-meeting03:20
*** rfolco has joined #openstack-meeting03:23
*** dbecker has joined #openstack-meeting03:33
*** unicell has joined #openstack-meeting03:33
*** unicell has quit IRC03:33
*** aeng has quit IRC03:34
*** thorst_afk has joined #openstack-meeting03:43
*** jamesdenton has joined #openstack-meeting03:45
*** julim has quit IRC03:47
*** marst has quit IRC03:49
*** galstrom is now known as galstrom_zzz03:50
*** aeng has joined #openstack-meeting03:51
*** galstrom_zzz is now known as galstrom03:51
*** rfolco has quit IRC03:52
*** aselius has quit IRC03:55
*** zhonghua2 has joined #openstack-meeting03:57
*** zhurong has joined #openstack-meeting04:00
*** zhonghua has quit IRC04:00
*** thorst_afk has quit IRC04:02
*** jamesdenton has quit IRC04:06
*** slaweq has joined #openstack-meeting04:08
*** aeng has quit IRC04:09
*** slaweq has quit IRC04:13
*** trinaths has joined #openstack-meeting04:21
*** jamesdenton has joined #openstack-meeting04:21
*** jamesmcarthur has quit IRC04:22
*** aeng has joined #openstack-meeting04:23
*** ___h45h74x___ has joined #openstack-meeting04:25
*** YanXing_an has joined #openstack-meeting04:27
*** Julien-zte has quit IRC04:27
*** Julien-zte has joined #openstack-meeting04:28
*** tung_doan has joined #openstack-meeting04:29
*** zhurong has quit IRC04:30
*** janki has joined #openstack-meeting04:31
gongysh#startmeeting tacker04:31
openstackMeeting started Wed Jun  7 04:31:32 2017 UTC and is due to finish in 60 minutes.  The chair is gongysh. Information about MeetBot at http://wiki.debian.org/MeetBot.04:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:31
*** openstack changes topic to " (Meeting topic: tacker)"04:31
openstackThe meeting name has been set to 'tacker'04:31
gongyshhi04:31
jankiHi gongysh04:31
gongysh#topic roll call04:32
*** openstack changes topic to "roll call (Meeting topic: tacker)"04:32
gongyshjanki, welcome04:32
YanXing_anhello04:32
*** markstur has quit IRC04:33
*** diablo_rojo has quit IRC04:33
tung_doanhi all04:34
jankigongysh, thanks :)04:34
YanXing_anping tung_doan04:34
trinathso/04:34
tung_doanYanXing_an: Hi there04:35
*** edmondsw has joined #openstack-meeting04:35
gongyshwe are toward deadline of pike-204:36
gongyshhope some core will join us later04:36
gongysh#topic bp04:37
*** openstack changes topic to "bp (Meeting topic: tacker)"04:37
gongyshtung_doan, let talk about your bp first04:37
gongyshhttps://review.openstack.org/#/c/434974/10/specs/pike/vnffg-autohealing.rst04:37
tung_doangongysh: I am trying to wrap this bo04:37
gongyshtoday, I want to do meeting reviewing04:37
tung_doangongysh: only one concern is abt API04:37
YanXing_anwhen is deadline? not 2017-6-5?04:37
gongyshso please go to this bp review page.04:38
*** galstrom is now known as galstrom_zzz04:38
tung_doanI need Tacker guys about API in my bp04:38
gongyshfirst, what is vnffg-ha meaning?04:38
gongyshtung_doan, hi04:38
tung_doangongysh: vnffg-ha is meaning high availability for VNFFG04:39
tung_doanit includes both scaling and autohealing support04:39
gongyshha in general means there are two or more for this kind of stuff.04:39
gongyshdo we have two vnffg to do ha?04:39
*** edmondsw has quit IRC04:39
tung_doangongysh: exactly, i just did not have other names for it04:40
*** zhurong has joined #openstack-meeting04:40
*** trinaths has left #openstack-meeting04:40
gongyshso we will have two vnffg if we run 'tacker vnffg-create xxx'04:40
gongysh?04:40
tung_doangongysh: in case of scaling, we have 2 paths with the same vnffg04:41
*** trinaths has joined #openstack-meeting04:41
YanXing_angongysh, IMO, we do not have two vnffg to do ha04:41
gongyshscaling just scaling member vnf's vdu, right?04:42
tung_doanYanXing_an: +104:42
*** diga has joined #openstack-meeting04:42
digaHi04:42
gongyshdiga, welcome04:42
digagongysh: Hi04:42
tung_doangongysh: it looks like a different use case04:42
gongyshdiga, we are talking about https://review.openstack.org/#/c/434974/10/specs/pike/vnffg-autohealing.rst04:42
digagongysh: okay, I will go through it04:42
tung_doangongysh: pls look at this diagram: https://review.openstack.org/#/c/469975/2/specs/pike/vnffg-scaling.rst@7304:43
gongyshtung_doan, vnffg-ha is the first question.04:43
tung_doangongysh: we still have the same vnffg but we have a group of VNF for scaling case04:44
YanXing_anmaybe vnffg-supports-vnf-ha is a better name04:44
gongyshtung_doan, so it is not vnffg ha itself.04:44
*** janki has left #openstack-meeting04:44
gongyshwe need a different name04:44
*** janki has joined #openstack-meeting04:44
*** yamamoto_ has quit IRC04:44
tung_doangongysh: ok. pls review and give me your suggestion. thanks04:44
gongyshsecond question is: why do we need a url?04:45
gongysh**POST on  /v1.0/vnffghas/<vnf-id>/<monitoring-policy>/<action-name>/<params>**04:45
tung_doangongysh: when vnf is respawned, it is just in VNFM level04:45
tung_doangongysh: vnffg is in NFVO level, we need to specify which vnffg VNF is belong to04:46
tung_doangongysh: that's why we need to have API in NFVO04:46
*** zz_dimtruck is now known as dimtruck04:47
*** hongbin has quit IRC04:47
tung_doangongysh: Is it clear to you?04:48
gongyshtung_doan, it seems reasonable.04:49
*** mickeys has joined #openstack-meeting04:49
YanXing_antung_doan, in policy action, we call the rest api to notify NFVO?04:49
tung_doangongysh: thanks.04:49
gongyshit is based on nfvo and vnfm separation.04:49
tung_doanYanXing_an: correct!04:49
tung_doanYanXing_an: one vnf can belong to several vnffgs or NSs. We need to have api to notify them04:50
gongyshtung_doan, ok make sense.04:51
YanXing_antung_doan, it's nice method, i think.04:51
tung_doangongysh: YanXing_an: happy to know that :)04:52
gongyshtrinaths, please have a look at this spec too04:52
gongyshdiga, you too.04:52
trinathsgongysh: sure.04:52
trinathsgongysh:  looking now04:52
digagongysh: yes, going through it04:52
gongyshI will try to merge the spec with your review, even without core's score.04:53
trinathsI believe vnfs and vsfs must be sharable04:53
*** mickeys has quit IRC04:53
gongyshtung_doan, https://review.openstack.org/#/c/469975/04:53
gongyshplease work on it too.04:54
gongyshlet's get them merged as soon as possbile.04:54
tung_doangongysh: work in parallel with vnffg-healing04:54
tung_doangongysh: got it04:54
gongyshjanki, hi04:54
*** pcaruana has joined #openstack-meeting04:56
gongyshit seems janki  is not here.04:56
gongyshnext bp is from me:04:56
gongyshhttps://review.openstack.org/#/c/467479/04:56
gongyshalso please have a look at it.04:57
trinathssure04:57
gongyshthis is for bp04:57
*** dimtruck is now known as zz_dimtruck04:57
gongyshdo you guys have other bp hanging?04:58
tung_doangongysh: your bp should be prior. will look at this04:58
gongyshYanXing_an, yes the pike2 is 6-5.04:58
trinathswhen is pike-3 ?04:59
jankigongysh, hey04:59
gongyshtrinaths, I will move all unmerged stuff into pike-304:59
trinathsok04:59
gongyshjanki, do you have anything to talk about tacker bp?04:59
YanXing_anp3 is 7-2405:00
jankigongysh, yes. I did some research and looks like magnum won't be of use to us05:00
jankiwe can use zun to create containers05:00
jankibut zun doesnot create docker image05:00
trinathsjanki: the work is related to cVNF management ?05:01
jankiso I need to figure out a way to create a docker image from tosca template05:01
jankitrinaths, what do you mean by cvnf?05:01
gongyshjanki, nice to hear that. you can have a demo implementation.05:01
tung_doanjanki: why magnum cannot be a candidate?05:01
trinathscontainerized vnf05:01
jankitung_doan, magnum proivdes COEs. and not a way to create container05:01
jankitrinaths, yes. it is for cVNF05:01
trinathsjanki: okay.05:02
gongyshnext topic05:02
jankiif anybody has any idea about converting tosca template to docker image, please reach out to me05:02
tung_doanjanki: i think any update from your bp will be good to see :))05:02
gongyshjanki, what do you mean by 'convert tosca temmplate into docker image'?05:03
digajanki: make sure, we should provision containers on COE05:03
jankigongysh, from a VNFD we need a docker image05:03
digain zun we provide, magnum support as COE & on top of that, we can create containers05:03
jankitung_doan, I will update once I have some understanding on this part05:03
tung_doanjanki: +105:04
gongyshjanki, go on the research.05:04
gongyshthanks05:04
trinathsjanki: can you elaborate on VNFD to DI ?05:04
gongysh#topic codes and bug05:04
*** openstack changes topic to "codes and bug (Meeting topic: tacker)"05:04
jankitrinaths, lets take this discussion furhter on #tacker after this meeting05:04
*** adisky__ has joined #openstack-meeting05:05
gongyshYanXing_an, https://bugs.launchpad.net/tacker/+bug/166790505:05
openstackLaunchpad bug 1667905 in tacker "can't delete vnffg if it get stuck at PENDING_DELETE state" [Medium,In progress] - Assigned to sajuptpm (sajuptpm)05:05
YanXing_anjanki, does it mean, launch a container from vnfd, to replace kvm VM?05:05
trinathsjanki: okay05:05
jankiYanXing_an, yes05:05
trinathsYanXing_an: yes05:05
gongyshhttps://review.openstack.org/#/c/469304/05:06
*** Julien-zte has quit IRC05:06
YanXing_angongysh, have no much time on it this week05:06
gongyshYanXing_an, but I have seen you had a state transition diagram draw05:06
trinathsYanXing_an: fixing that bug stated above ?05:06
YanXing_anyes, it can help to fixing this bug05:07
*** Julien-zte has joined #openstack-meeting05:08
trinathsYanXing_an: i suggest to own the bug on your name. its will be good for tracking.05:08
*** priteau has joined #openstack-meeting05:08
*** slaweq has joined #openstack-meeting05:08
*** dims has quit IRC05:09
gongyshnext code patch:05:09
gongyshhttps://review.openstack.org/#/c/465080/05:09
trinathsther are x`https://bugs.launchpad.net/tacker/+bug/1667905 https://bugs.launchpad.net/tacker/+bug/168942605:09
openstackLaunchpad bug 1667905 in tacker "can't delete vnffg if it get stuck at PENDING_DELETE state" [Medium,In progress] - Assigned to sajuptpm (sajuptpm)05:09
openstackLaunchpad bug 1689426 in tacker "VNF in PENDING_DELETE status can not be deleted" [Undecided,In progress] - Assigned to Bao Fangyan (baofangyan)05:09
trinathsduplocate ?05:09
YanXing_anvnffg and vnf both have this bug05:10
trinathsYanXing_an: okay.05:10
trinathsi was confused05:10
gongyshhttps://review.openstack.org/#/c/465080/ is almost done05:11
YanXing_anwe can fix it together05:11
trinathsYanXing_an: good05:11
gongyshI have tested it. and just one nit left over.05:11
gongyshonce it is done and get CI passed, I will +205:11
gongyshhope you guys have a review and test too.05:11
gongyshYanXing_an,  well done05:12
YanXing_angongysh, thanks05:12
gongyshdo you guys have other code patch or bugs to talk about?05:12
*** priteau has quit IRC05:12
jankigongysh, I want to talk about integration with ooo05:13
gongyshooo?05:13
tung_doantriple )05:13
*** slaweq has quit IRC05:13
jankisorry, Tripleo05:13
gongyshso what will we need to do for it?05:14
tung_doanjanki: I heard that tacker already integrated in OOO, right?05:14
jankigongysh, tacker is integrated in tripleo.05:14
*** pcaruana has quit IRC05:14
jankinow all services are getting containerised in TripleO05:14
jankitung_doan, yes05:14
*** bkopilov has joined #openstack-meeting05:14
jankigongysh, we need to containerise Tacker in TripleO05:15
*** prateek has joined #openstack-meeting05:15
jankitung_doan, it is integration but disabled by default05:15
gongyshjanki, yes, that is awesome.05:15
gongyshjanki, do you want to do it?05:15
jankigongysh, I can take that up05:15
tung_doanjanki: nice05:15
gongyshjanki, fine.05:15
YanXing_anjanki, it's good to deploy tacker in container for me05:16
gongyshif you think it needs a spec bp, you can do one.05:16
jankigongysh, i will open a bug about this on tripleo05:16
gongyshor just start a launchpad to do it.05:16
tung_doanjanki: +105:16
jankigongysh, no spec needed. just a bug. the code will go in tripleo and kolla05:16
jankiI odnt think there would be any Tacker code change05:17
trinathsin opnfv-models setup, tacker is containerized.05:17
gongyshjanki, kolla already has it.05:17
jankitrinaths, can you point the url?05:17
*** Julien-z_ has joined #openstack-meeting05:17
jankigongysh, ohh, then it is just TRipleo changes we need05:17
jankigongysh, let me reconfirm it on tripleo front too05:17
gongyshjanki, put a bug on tacker and write a install doc in tacker05:18
YanXing_anI have tried to launch tacker in contrainer several months ago, but failed, no time to fix it05:18
digaFirst verify, what support we have in tripleo then go ahead and file the bug05:18
gongyshwe need guys to know how to install it using kolla.05:18
*** unicell has joined #openstack-meeting05:18
jankigongysh, the bug will go in Tripleo launch pad. there won't be any doc needed as this will be part of Tripleo installation05:18
jankiand the doc should already be in tripleo repo05:19
digagongysh: I know kolla, will take a look at it05:19
trinathsjanki: https://wiki.opnfv.org/display/models/Testing05:19
jankitrinaths, thanks05:19
*** Julien-zte has quit IRC05:19
gongyshjanki, diga you can change the tacker's installation doc about kolla or tripleo installation.05:20
gongyshdiga, thanks05:20
digagongysh: sure05:20
gongyshguys,  taker installation should not need nova, cinder components.05:21
gongyshin devstack installation, we name it as standalone installation.05:21
gongyshso the kolla or tripleo way to install tacker should be the 'standalone' way.05:22
digaokay05:22
gongysh#topic open discussion05:22
*** openstack changes topic to "open discussion (Meeting topic: tacker)"05:22
*** claudiub has joined #openstack-meeting05:22
gongyshany other stuff to talk?05:22
*** sridharg has joined #openstack-meeting05:23
gongyshif not we can end the meeting earlier05:23
tung_doangongysh: I am the way to harmonize scaling code between Tacker and heat-translator. pls have a look05:23
tung_doanhttps://review.openstack.org/#/c/471049/05:24
tung_doanhttps://review.openstack.org/#/c/462690/05:24
gongyshtung_doan, I was trying, but it is not easy to do the review since I don't know what is the point.05:24
tung_doanok.. i really need Kanagaraj and tbh05:25
tung_doanbut seems they are not here. will ping them latter05:25
*** Julien-z_ has quit IRC05:25
gongyshtrinaths, heard opnfv meeting is on near.05:25
gongyshdo you want to share?05:25
gongyshtrinaths, hi05:26
*** Julien-zte has joined #openstack-meeting05:26
trinathsgongysh: I have 3 presentations planned 14 and 15th  jue05:26
trinathsjune05:26
gongyshin beijing?05:26
trinathspresentation stuff got approved yesterday.05:26
trinathsgongysh: yes.05:26
jankigongysh, what is our plan for PTG?05:27
gongyshok, but I have no ticket there.05:27
trinathsgongysh: JW marriot and Ritz Carlton  hotel05:27
gongyshtrinaths, I have to get a ticker first.05:27
gongyshjanki, do you want to organize the PTG this time?05:27
jankigongysh, I am not sure whether I would be travelling or not05:28
jankiso can't commit05:28
trinathsi have got 20 minutes of talk05:28
trinathsgongysh: https://events.linuxfoundation.org/events/opnfv-summit/attend/registration05:28
*** Julien-zte has quit IRC05:28
gongyshjanki, I think we will doing the virtual PTG again.05:28
jankigongysh, sounds good :)05:28
trinathsgongysh: 'idea nest' is a informal talk for 20 minutes.05:29
gongyshtime is up. lets go to tacker channel05:29
trinathsgongysh: I want to propose tacker - ongoing and future work.05:29
tung_doantrinaths: nice05:29
gongyshtrinaths, sure, that's nice.05:29
gongysh#endmeeting05:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:29
openstackMeeting ended Wed Jun  7 05:29:52 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2017/tacker.2017-06-07-04.31.html05:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2017/tacker.2017-06-07-04.31.txt05:29
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2017/tacker.2017-06-07-04.31.log.html05:29
*** Julien-zte has joined #openstack-meeting05:31
*** yamamoto has joined #openstack-meeting05:31
*** numan_ has joined #openstack-meeting05:36
*** tung_doan has left #openstack-meeting05:36
*** dims has joined #openstack-meeting05:41
*** asselin has joined #openstack-meeting05:46
*** Julien-zte has quit IRC05:46
*** zz_dimtruck is now known as dimtruck05:47
*** Julien-zte has joined #openstack-meeting05:47
*** asselin_ has quit IRC05:48
*** mickeys has joined #openstack-meeting05:49
*** KanagarajM has joined #openstack-meeting05:51
*** mickeys has quit IRC05:54
*** mlakat has joined #openstack-meeting05:54
*** KanagarajM has quit IRC05:54
*** YanXing_an has quit IRC05:54
*** noslzzp has joined #openstack-meeting05:55
*** dimtruck is now known as zz_dimtruck05:56
*** mickeys has joined #openstack-meeting05:57
*** thorst_afk has joined #openstack-meeting05:59
*** aeng has quit IRC06:01
*** thorst_afk has quit IRC06:04
*** yinxiulin has quit IRC06:07
*** Julien-zte has quit IRC06:10
*** Julien-zte has joined #openstack-meeting06:12
*** mlakat has quit IRC06:12
*** tobberydberg has joined #openstack-meeting06:14
*** tobberydberg has joined #openstack-meeting06:14
*** bkopilov has quit IRC06:17
*** markstur has joined #openstack-meeting06:19
*** rcernin has joined #openstack-meeting06:21
*** jamesmcarthur has joined #openstack-meeting06:23
*** edmondsw has joined #openstack-meeting06:23
*** wanghao_ has joined #openstack-meeting06:24
*** markstur has quit IRC06:24
*** wanghao has quit IRC06:25
*** salv-orlando has quit IRC06:25
*** radeks has joined #openstack-meeting06:26
*** jamesmcarthur has quit IRC06:27
*** fnaval has quit IRC06:27
*** edmondsw has quit IRC06:28
*** unicell1 has joined #openstack-meeting06:28
*** fnaval has joined #openstack-meeting06:29
*** unicell has quit IRC06:29
*** ltomasbo|away is now known as ltomasbo06:30
*** armax has quit IRC06:36
*** unicell has joined #openstack-meeting06:37
*** unicell1 has quit IRC06:38
*** noslzzp has quit IRC06:38
*** zz_dimtruck is now known as dimtruck06:47
*** belmoreira has joined #openstack-meeting06:55
*** dimtruck is now known as zz_dimtruck06:57
*** slaweq has joined #openstack-meeting06:59
*** zz_dimtruck is now known as dimtruck07:00
*** thorst_afk has joined #openstack-meeting07:01
*** afazekas has quit IRC07:01
*** afazekas has joined #openstack-meeting07:01
*** pcaruana has joined #openstack-meeting07:03
*** thorst_afk has quit IRC07:05
*** tmorin has joined #openstack-meeting07:06
*** mickeys has quit IRC07:07
*** rbartal has joined #openstack-meeting07:09
*** salv-orlando has joined #openstack-meeting07:09
*** dimtruck is now known as zz_dimtruck07:10
*** tesseract has joined #openstack-meeting07:11
*** Fdaisuke has quit IRC07:12
*** mickeys has joined #openstack-meeting07:14
*** Fdaisuke has joined #openstack-meeting07:14
*** wanghao_ has quit IRC07:19
*** qwebirc64411 has joined #openstack-meeting07:19
*** qwebirc64411 has left #openstack-meeting07:19
*** wanghao has joined #openstack-meeting07:19
*** qwebirc73344 has joined #openstack-meeting07:20
*** bkopilov has joined #openstack-meeting07:20
*** qwebirc73344 has left #openstack-meeting07:21
*** Julien-zte has quit IRC07:23
*** unicell1 has joined #openstack-meeting07:28
*** noslzzp has joined #openstack-meeting07:29
*** unicell has quit IRC07:29
*** salv-orl_ has joined #openstack-meeting07:32
*** oidgar has joined #openstack-meeting07:33
*** numan_ has quit IRC07:35
*** cloudrancher has quit IRC07:35
*** alexchadin has joined #openstack-meeting07:36
*** salv-orlando has quit IRC07:37
*** hashar has joined #openstack-meeting07:38
*** cloudrancher has joined #openstack-meeting07:38
*** manikanta_tadi has quit IRC07:38
*** hashar has quit IRC07:38
*** hashar has joined #openstack-meeting07:39
*** epico has quit IRC07:47
*** epico has joined #openstack-meeting07:48
*** slaweq has quit IRC07:50
*** slaweq has joined #openstack-meeting07:51
*** epico has quit IRC07:51
*** pnavarro has joined #openstack-meeting07:52
*** rcernin has quit IRC07:52
*** priteau has joined #openstack-meeting07:52
*** rcernin has joined #openstack-meeting07:52
*** slaweq has quit IRC07:54
*** zz_dimtruck is now known as dimtruck08:01
*** slaweq has joined #openstack-meeting08:01
*** rossella_ has joined #openstack-meeting08:01
*** thorst_afk has joined #openstack-meeting08:01
*** tmorin has quit IRC08:02
*** rossella_ has quit IRC08:09
*** edmondsw has joined #openstack-meeting08:11
*** tinwood has quit IRC08:11
*** mickeys has quit IRC08:12
*** rossella_ has joined #openstack-meeting08:12
*** dimtruck is now known as zz_dimtruck08:12
*** tinwood has joined #openstack-meeting08:12
*** Julien-zte has joined #openstack-meeting08:15
*** edmondsw has quit IRC08:16
*** thorst_afk has quit IRC08:21
*** rossella_ has quit IRC08:21
*** numans has joined #openstack-meeting08:22
*** Julien-zte has quit IRC08:24
*** epico has joined #openstack-meeting08:25
*** gongysh has quit IRC08:25
*** alexchadin has quit IRC08:26
*** tmorin has joined #openstack-meeting08:26
*** trinaths has left #openstack-meeting08:30
*** gongysh has joined #openstack-meeting08:33
*** alexchadin has joined #openstack-meeting08:35
*** Fdaisuke has quit IRC08:40
*** Fdaisuke_ has joined #openstack-meeting08:40
*** rossella_ has joined #openstack-meeting08:41
*** Julien-zte has joined #openstack-meeting08:41
*** ChrisPriceAB_ is now known as ChrisPriceAB08:42
*** neil__ has joined #openstack-meeting08:44
*** zhurong has quit IRC08:47
*** rossella_ has quit IRC08:49
*** rossella__ has joined #openstack-meeting08:49
*** mgoddard_ has joined #openstack-meeting08:51
*** ykatabam has quit IRC08:52
*** rossella_ has joined #openstack-meeting08:54
*** noggin143 has joined #openstack-meeting08:54
*** rossella__ has quit IRC08:55
*** oneswig has joined #openstack-meeting08:57
oneswig#startmeeting scientific_wg09:00
openstackMeeting started Wed Jun  7 09:00:30 2017 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: scientific_wg)"09:00
openstackThe meeting name has been set to 'scientific_wg'09:00
oneswigGreetings09:00
arnewiebalcko/09:01
*** rossella__ has joined #openstack-meeting09:01
oneswig#link agenda for today https://wiki.openstack.org/wiki/Scientific_working_group#IRC_Meeting_June_7th_201709:01
oneswigarnewiebalck: hi!  Thanks for coming09:01
priteauo/09:01
oneswigHi priteau09:01
arnewiebalckoneswig: np09:01
priteauHello09:01
*** rossella_ has quit IRC09:01
mgoddard_o/09:02
noggin143o/09:02
*** zhurong has joined #openstack-meeting09:02
*** wanghao_ has joined #openstack-meeting09:02
oneswigSo today we'll cover the CephFS user experience first, then the archive on Zenodo, then the other business09:03
*** verdurin has joined #openstack-meeting09:03
oneswig#topic CephFS for user home dirs09:03
*** zz_dimtruck is now known as dimtruck09:03
*** openstack changes topic to "CephFS for user home dirs (Meeting topic: scientific_wg)"09:03
verdurinMorning09:03
oneswigHi verdurin mgoddard_ noggin143, welcome all09:04
oneswigWe've been working on a cluster-as-a-service deployment, aiming to be more than superficially useful, and we wanted to graft in a good choice for a home directory.09:05
oneswigI saw Arne's video from Boston which covers a very similar subject09:05
oneswig#link CERN's CephFS story https://www.openstack.org/videos/boston-2017/manila-on-cephfs-at-cern-the-short-way-to-production09:05
oneswigarnewiebalck: you've been using it since last summer, right?09:06
*** wanghao has quit IRC09:06
arnewiebalckYes.09:06
oneswigWhy did you choose CephFS originally over (say) nfs09:06
arnewiebalckNot for global home dirs, though.09:06
arnewiebalckCephFS was chosen to fill a gap we had for the HPC use case.09:07
arnewiebalckWe did not have a parallel FS for HPC apps.09:07
oneswigDid you look at other options there? Lustre, Glusterfs, etc.?09:08
arnewiebalckIt is now also used for the home dirs, but only for the HPC users within the cluster.09:08
*** tmorin has quit IRC09:08
arnewiebalckWe looked at Lustre some years ago.09:08
verdurinarnewiebalck: this is instead of CVMFS?09:08
arnewiebalckAt the time, to consolidate our stoarge solutions.09:08
arnewiebalckverdurin: No, cvmfs fulfills yet another use case.09:09
*** neil__ has quit IRC09:09
arnewiebalckWe had Ceph and needed a parallel FS, so CephFS was the natueral choice to try out.09:09
arnewiebalckWe were not convinced by Lustre from an operational point of view (at the time).09:10
*** sw3__ has joined #openstack-meeting09:10
*** rossella_ has joined #openstack-meeting09:10
arnewiebalckSo, CephFS is in prod for HPC since last summer.09:10
oneswigMakes sense. Are you using CentOS Ceph Jewel or some other Ceph packages?09:10
arnewiebalckWe’re using upstream Jewel.09:10
*** zioproto has joined #openstack-meeting09:11
zioprotohello all09:11
oneswigHi zioproto - just starting on Cephfs09:11
zioprotothanks09:11
*** rossella__ has quit IRC09:11
arnewiebalckOnce we established CephFS with HPC, some other use cases came up, such as K8s.09:11
sw3__hi everyone..09:11
oneswigarnewiebalck: Did you choose to deploy from upstream because of stability or something else?09:12
arnewiebalckAnd now we’re trying to replace our current NFS use cases with our CephFS deployment.09:12
oneswighi sw3__ welcome09:12
sw3__thx09:13
*** mickeys has joined #openstack-meeting09:13
arnewiebalckoneswig: The Ceph team has a pretty direct link to the upstream Ceph team.09:13
*** dimtruck is now known as zz_dimtruck09:13
zioprotoarnewiebalck: are you using Jewel ?09:13
arnewiebalckzioproto: yes09:14
arnewiebalckzioproto: testing Luminous as well09:14
arnewiebalckor pre-Luminous09:14
arnewiebalckfrom our experience it wroks pretty well so far09:14
verdurinarnewiebalck: pre-Luminous with BlueStore?09:14
oneswigarnewiebalck: Can you describe the storage pool configuration ?09:14
arnewiebalckmain issues as Tim mentioned yesterday are quotas09:14
*** rossella_ has quit IRC09:15
arnewiebalckoneswig: I’m somewhat out of my depth here … anything specific you’re interested in?09:15
oneswigSpecifically, things like bluestore, or journaled vs SSD pool for metadata09:16
noggin143Some more details on the CERN Ceph install from Dan at https://indico.cern.ch/event/542464/contributions/2202295/attachments/1289543/1921810/cephday-dan.pdf09:16
arnewiebalckwe don’t have SSD only pools09:17
oneswigWe started with a journaled OSD for our metadata pool.  Our user applications immediately found problems with that.09:17
oneswignoggin143: thanks, will study!09:17
arnewiebalckoneswig: the usage from the HPC use is pretty moderate so far09:17
*** thorst_afk has joined #openstack-meeting09:18
arnewiebalckand no BlueStore on the production ones09:18
oneswigarnewiebalck: We see issues with file access patterns involving fsync - up to 5s system call latency - is this something you've found?  Apparently it is resolved in lumninous but I haven't checked09:18
arnewiebalckyes, there were issue with specific use cases as well09:19
oneswigarnewiebalck: can you talk about any specific lessons learned?09:19
*** mickeys has quit IRC09:19
*** rossella_ has joined #openstack-meeting09:20
arnewiebalcknot really: most of the issues we found were resolved quickly09:21
arnewiebalckthere is a list on my slide deck09:21
arnewiebalckbut I can check with the Ceph team if I missed sth09:21
oneswigDo you know when the quota support goes into the kernel client?09:22
*** thorst_afk has quit IRC09:22
arnewiebalckno09:22
arnewiebalckbut this mostly affects K8s09:22
arnewiebalckwe use cpeh-fuse everywhere else09:22
arnewiebalckand recommend this as the preferred way to access CephFS09:23
arnewiebalckalso due to the way features are added09:23
arnewiebalckbut also on fuse quota is only advisory09:23
*** jamesmcarthur has joined #openstack-meeting09:23
oneswigarnewiebalck: have you measured the overhead of fuse for your hpc use cases?09:24
arnewiebalckbut at least it prevents users from accidentally filling the cluster09:24
arnewiebalckoneswig: compared to the kernel client?09:24
*** wanghao_ has quit IRC09:24
arnewiebalckno09:24
oneswigI'm in the process of trying to compare the two (and NFS)09:24
oneswigarnewiebalck: something that intrigued me about the video of your talk - somebody asked a question about RDMA - I hadn't realised that project was active, do you know more about it?09:25
arnewiebalckI briefly talked to Dan about it after the summit.09:26
oneswigDan van der Ster?09:27
arnewiebalckIf set up hyperconverged servers, he’d like to try it out.09:27
arnewiebalckoneswig: yes, he’s our Ceph expert09:27
*** jamesmcarthur has quit IRC09:27
oneswigarnewiebalck: we'd like to try it too! :-)09:28
arnewiebalckfor RDMA, that’s basically all I know :)09:28
arnewiebalckwe’ll get some new clusters later this year, this may be an opportunity for testing09:29
*** tmorin has joined #openstack-meeting09:29
oneswigarnewiebalck: do you manage access to the CephFS using Manila?09:29
arnewiebalckwe didn’t in the beginning, but now we do, yes09:29
arnewiebalckand we moved the pre-Manila users to Manila09:30
oneswigDoes that mean you have multiple CephFS filesystems active?  I believe that's considered experimental (but safe on latest Jewel)?09:31
verdurinarnewiebalck: encouraging to see some real use of Manila09:31
*** sdague has joined #openstack-meeting09:31
arnewiebalckoneswig: we have multiple clusters09:31
*** e0ne has joined #openstack-meeting09:31
arnewiebalckverdurin: it works pretty well09:31
arnewiebalckverdurin: apart from minor issues ;)09:31
arnewiebalckoneswig: multiple share types with separate clusters works for us09:32
oneswigarnewiebalck: It's certainly interesting to hear that - but our use case is bare metal so no Manila for us (AFAIK)09:32
arnewiebalckoneswig: why not?09:32
noggin143You could still use Manila to handle the creation etc.09:33
arnewiebalckoneswig: Manila is basically only used for creation as a self-service portal and accounting09:33
oneswigAh, so it is, but what of the access to the storage network?09:33
noggin143oneswig: Extract the secret cephx and then define a mountable filesystem on the bare metal09:33
arnewiebalckwell, the Manila server must be able to talk to the CephFS cluster, of course09:34
*** joehuang has quit IRC09:34
oneswignoggin143: That's essentially what we do manually, providing per-project cephx keys for Ceph access09:34
*** number80 has quit IRC09:34
oneswigI had thought there was plumbing Manila adds in the hypervisor space too?09:34
arnewiebalckoneswig: no09:35
*** rossella_ has quit IRC09:35
oneswigarnewiebalck: OK, sounds promising to me - I'll check it out.  Thanks!09:35
arnewiebalckoneswig: unless you want NFS re-export09:36
noggin143oneswig: what's cute with Manila is that the secrets are only visible to the project members so no need to mail around secrets09:36
*** Hosam has joined #openstack-meeting09:36
oneswignoggin143: sounds good.  We've been using Barbican for that.  It ties in well with our deploy scripts.  It's exciting to hear that there could be a smoother way through though09:37
oneswigAny more on CephFS for today?09:37
*** Hosam_ has joined #openstack-meeting09:37
oneswigI recommend Arne's video BTW, very useful09:37
*** neil__ has joined #openstack-meeting09:38
oneswigOK - thanks Arne!  Lets move on09:38
arnewiebalckoneswig: :)09:38
oneswig#topic OpenStack research paper archive09:38
*** openstack changes topic to "OpenStack research paper archive (Meeting topic: scientific_wg)"09:38
oneswigThanks for the blog post yesterday Tim09:39
oneswig#link OpenStack in production blog post http://openstack-in-production.blogspot.co.uk/2017/06/openstack-papers-community-on-zenodo.html09:39
noggin143oneswig: I tested the curate functionality with some folk from the EU Indigo Datacloud project and it works well09:40
oneswigSo for example, if I wanted to submit this paper on virtualised GPU direct: http://grids.ucs.indiana.edu/ptliupages/publications/15-md-gpudirect%20(3).pdf - what would I need to do?09:40
zioprotooneswig: I guess here ? https://zenodo.org/login/?next=%2Fdeposit09:41
noggin143oneswig: if you sign up to Zenodo (and there are various login options), you'll see a submit button09:41
zioprotothere is that big 'upload' button on top09:41
*** Hosam has quit IRC09:41
noggin143zioproto: that's right, it's upload, not submit09:41
oneswigIs it fair to assume any paper available online can be uploaded here?09:42
noggin143oneswig: when you upload, you can put in details of authors, conference and DOI if you have it09:42
noggin143oneswig: Chatting with the library folk here, the feeling is that if the paper is available on the internet freely, it could be uploaded to the repository.09:42
*** phil_ has joined #openstack-meeting09:43
oneswignoggin143: that's a huge barrier to entry removed09:43
*** phil_ is now known as Guest9656709:43
noggin143oneswig: it's part of the opendata movement to move publically funded research to be available to the general public.09:44
*** mriedem has joined #openstack-meeting09:44
*** abalutoiu has joined #openstack-meeting09:44
noggin143oneswig: and also to preserve results. Often we find pointers to talks which are then 404s since the project funding has completed09:44
oneswignoggin143: you're looking at linking with planet.openstack.org - any other thoughts on ways of keeping the archive prominent and maintained?09:45
noggin143oneswig: I'm having a chat with the Zenodo folk to see if there is a possibility of RSS. However, there is a lot on their plate at the moment.09:45
oneswignoggin143: I am sure that would help, and not just for this use case09:46
noggin143oneswig: I was thinking about adding a blog with papers uploaded in the past month so that planet openstack would get the feed09:46
noggin143oneswig: but people would not be overwhelmed by lots of entries09:46
priteauoneswig: I am not sure we can upload random PDFs found on the web unless they are granting rights to redistribute09:47
*** rossella_ has joined #openstack-meeting09:47
oneswigIs there a distinction made between research on infrastructure itself vs research performed using the infrastructure?09:47
noggin143priteau: it depends on the journal for scientific papers. Creative Commons etc. is OK. I will review the documents when they are uploaded as part of the curation role.09:48
oneswigpriteau: that was my concern - my example grants permission provided it's not for profit.09:49
oneswignoggin143: so zenodo takes some responsibility for the rights of the papers uploaded?09:49
noggin143oneswig: I will clarify to be sure and update the blog accordingly.09:50
priteauoneswig: the notice says "for personal or classroom use", I don't think uploading on zenodo qualifies. Indeed it even says later: "to post on servers or to redistribute to lists, requires prior specific permission and/or a fee."09:50
noggin143oneswig: one of the fields on the submission is the license09:50
*** zhurong has quit IRC09:51
oneswigpriteau: so it does, well spotted. So this is tricky09:51
noggin143oneswig: I propose to check this as part of the curation process when content is submitted.09:52
priteauThe authors who uploaded this paper to their own server may even be breaching the licence09:52
oneswigThanks noggin143 priteau - some clarification I think will help hugely.09:53
oneswigAny more to add on the research paper archive?09:54
oneswig#topic AOB09:54
*** openstack changes topic to "AOB (Meeting topic: scientific_wg)"09:54
oneswigAnyone going to ISC in Frankfurt in a couple of weeks?09:54
*** diga has quit IRC09:55
*** markstur has joined #openstack-meeting09:55
oneswigThere's a side-workshop - Exacomm - being run by DK Panda.  We are starting on the process of evaluating their RDMA-enabled Spark09:55
*** ralonsoh has joined #openstack-meeting09:55
oneswigOne immediately thinks of the maintenance of a special version, but perversely the OSU HiBD Spark is too new for Sahara support... seems like it's Sahara that's in need of updates!09:57
oneswig#link In case you're at ISC http://nowlab.cse.ohio-state.edu/exacomm/09:57
oneswigI had one further event - OpenStack Days UK in London, 26th September09:58
*** fzdarsky_ is now known as fzdarsky|lunch09:58
oneswig#link OpenStack Days UK CFP https://www.papercall.io/openstackdaysuk09:58
oneswigAny other events coming up?09:59
zioprotothe operators meetup in Mexico09:59
zioprotobut I did not follow closely09:59
zioprotoI dont know the details09:59
oneswigAh, true, you going?09:59
zioprotobut I think dates and location are set09:59
noggin143zioproto: it's at the start of August09:59
*** edmondsw has joined #openstack-meeting09:59
zioprotostill have to decide if I can go10:00
noggin143oneswig: I'll be on a beach then :-)10:00
*** markstur has quit IRC10:00
oneswigAgain, a great choice of location for hungry operators - I thought Milan was good, but Mexico...10:00
zioproto:)10:00
oneswigSadly we are out of time10:00
zioprotohave a good day ! :) ciao !10:00
oneswigThanks again noggin143 arnewiebalck & co10:00
oneswigUntil next time10:01
verdurinThanks, and bye.10:01
oneswig#endmeeting10:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"10:01
openstackMeeting ended Wed Jun  7 10:01:08 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-06-07-09.00.html10:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-06-07-09.00.txt10:01
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-06-07-09.00.log.html10:01
*** oneswig has left #openstack-meeting10:02
*** noggin143 has quit IRC10:04
*** edmondsw has quit IRC10:04
*** alexchadin has quit IRC10:04
*** zz_dimtruck is now known as dimtruck10:04
*** alexchadin has joined #openstack-meeting10:04
*** sw3__ has quit IRC10:05
*** Hosam has joined #openstack-meeting10:06
*** mgoddard_ has left #openstack-meeting10:10
*** Hosam_ has quit IRC10:10
*** caowei has quit IRC10:11
*** manikanta_tadi has joined #openstack-meeting10:14
*** dimtruck is now known as zz_dimtruck10:14
*** markstur has joined #openstack-meeting10:16
*** mickeys has joined #openstack-meeting10:16
*** kevzha01 has quit IRC10:16
*** Hosam has quit IRC10:19
*** Hosam has joined #openstack-meeting10:19
*** markstur has quit IRC10:20
*** mickeys has quit IRC10:20
*** mlakat has joined #openstack-meeting10:21
*** gcb has quit IRC10:24
*** Hosam has quit IRC10:24
*** tmorin has quit IRC10:27
*** tovin07_ has quit IRC10:29
*** alexchadin has quit IRC10:29
*** alexchadin has joined #openstack-meeting10:31
*** sambetts|afk is now known as sambetts10:32
*** zz_dimtruck is now known as dimtruck10:35
*** alexchadin has quit IRC10:36
*** markstur has joined #openstack-meeting10:37
*** alexchadin has joined #openstack-meeting10:38
*** markstur has quit IRC10:42
*** rossella_ has quit IRC10:43
*** hashar has quit IRC10:44
*** dimtruck is now known as zz_dimtruck10:45
*** anilvenkata has quit IRC10:48
*** zioproto has left #openstack-meeting10:52
*** Hosam has joined #openstack-meeting10:52
*** Julien-zte has quit IRC10:57
*** markstur has joined #openstack-meeting10:57
*** rossella_ has joined #openstack-meeting10:59
*** Julien-zte has joined #openstack-meeting10:59
*** epico has quit IRC11:02
*** markstur has quit IRC11:02
*** e0ne has quit IRC11:04
*** raildo has joined #openstack-meeting11:08
*** yamamoto has quit IRC11:10
*** jkilpatr has joined #openstack-meeting11:10
*** mickeys has joined #openstack-meeting11:17
*** rfolco has joined #openstack-meeting11:17
*** mickeys has quit IRC11:21
*** jamesmcarthur has joined #openstack-meeting11:24
*** number80 has joined #openstack-meeting11:25
*** LanceHaig has joined #openstack-meeting11:26
*** LanceHaig has quit IRC11:26
*** LanceHaig has joined #openstack-meeting11:26
*** edmondsw has joined #openstack-meeting11:27
*** jamesmcarthur has quit IRC11:29
*** julim has joined #openstack-meeting11:33
*** markstur has joined #openstack-meeting11:33
*** julim has quit IRC11:33
*** julim has joined #openstack-meeting11:34
*** lpetrut has joined #openstack-meeting11:35
*** zz_dimtruck is now known as dimtruck11:36
*** lpetrut has quit IRC11:37
*** markstur has quit IRC11:38
*** fzdarsky|lunch is now known as fzdarsky11:38
*** litao__ has quit IRC11:38
*** rossella_ has quit IRC11:41
*** Julien-zte has quit IRC11:45
*** dimtruck is now known as zz_dimtruck11:45
*** thorst_afk has joined #openstack-meeting11:49
*** markstur has joined #openstack-meeting11:54
*** zhiyuan has quit IRC11:57
*** markstur has quit IRC11:58
*** alexchadin has quit IRC12:02
*** rbudden has joined #openstack-meeting12:04
*** noslzzp has quit IRC12:04
*** hashar has joined #openstack-meeting12:15
*** markstur has joined #openstack-meeting12:15
*** sgrasley1 has quit IRC12:15
*** mickeys has joined #openstack-meeting12:18
*** gongysh has quit IRC12:19
*** gongysh has joined #openstack-meeting12:19
*** markstur has quit IRC12:19
*** egallen_ has joined #openstack-meeting12:19
*** egallen has quit IRC12:22
*** egallen_ is now known as egallen12:22
*** mickeys has quit IRC12:22
*** gongysh has quit IRC12:23
*** rossella_ has joined #openstack-meeting12:27
*** pewp has quit IRC12:28
*** lpetrut has joined #openstack-meeting12:28
*** pewp has joined #openstack-meeting12:28
*** rossella_ has quit IRC12:31
*** Hosam_ has joined #openstack-meeting12:34
*** markstur has joined #openstack-meeting12:36
*** yamamoto has joined #openstack-meeting12:36
*** zz_dimtruck is now known as dimtruck12:36
*** Hosam has quit IRC12:37
*** julim has quit IRC12:37
*** markstur has quit IRC12:40
*** Julien-zte has joined #openstack-meeting12:42
*** hashar has quit IRC12:42
*** rossella_ has joined #openstack-meeting12:43
*** tovin07 has joined #openstack-meeting12:44
*** tovin07 has quit IRC12:44
*** askb has quit IRC12:44
*** sridharg has quit IRC12:45
*** dimtruck is now known as zz_dimtruck12:46
*** yamamoto has quit IRC12:47
*** salv-orl_ has quit IRC12:49
*** salv-orlando has joined #openstack-meeting12:50
*** alexchadin has joined #openstack-meeting12:50
*** bobmel has quit IRC12:53
*** salv-orlando has quit IRC12:54
*** eharney has joined #openstack-meeting12:56
*** bobmel has joined #openstack-meeting12:56
*** markstur has joined #openstack-meeting12:56
*** julim has joined #openstack-meeting13:00
*** markstur has quit IRC13:01
*** e0ne has joined #openstack-meeting13:06
*** rmascena has joined #openstack-meeting13:07
*** yamamoto has joined #openstack-meeting13:08
*** fnaval has quit IRC13:10
*** raildo has quit IRC13:10
*** sridharg has joined #openstack-meeting13:13
*** bobh has joined #openstack-meeting13:14
*** felipemonteiro has joined #openstack-meeting13:15
*** kevzha01 has joined #openstack-meeting13:16
*** felipemonteiro_ has joined #openstack-meeting13:16
*** markstur has joined #openstack-meeting13:17
*** mickeys has joined #openstack-meeting13:18
*** felipemonteiro has quit IRC13:20
*** markstur has quit IRC13:22
*** mickeys has quit IRC13:22
*** baoli has joined #openstack-meeting13:23
*** fnaval has joined #openstack-meeting13:26
*** e0ne has quit IRC13:26
*** kevzha01_ has joined #openstack-meeting13:26
*** pradk has quit IRC13:27
*** hashar has joined #openstack-meeting13:27
*** e0ne has joined #openstack-meeting13:28
*** kevzha01 has quit IRC13:29
*** links has quit IRC13:30
*** eharney has quit IRC13:31
*** jprovazn has joined #openstack-meeting13:31
*** xyang2 has joined #openstack-meeting13:31
*** eharney has joined #openstack-meeting13:34
*** annabelleB has joined #openstack-meeting13:35
*** zz_dimtruck is now known as dimtruck13:37
*** markstur has joined #openstack-meeting13:38
*** lhx__ has joined #openstack-meeting13:41
*** armstrong has joined #openstack-meeting13:41
*** armstrong has quit IRC13:42
*** markstur has quit IRC13:43
*** noslzzp has joined #openstack-meeting13:44
*** hashar has quit IRC13:44
*** dane_leblanc has joined #openstack-meeting13:46
*** Hosam_ has quit IRC13:48
*** armstrong has joined #openstack-meeting13:48
*** Hosam has joined #openstack-meeting13:49
*** Fdaisuke has joined #openstack-meeting13:49
*** dimtruck is now known as zz_dimtruck13:50
*** hosanai has joined #openstack-meeting13:51
*** Hosam has quit IRC13:53
*** kgiusti has joined #openstack-meeting13:53
*** zhurong has joined #openstack-meeting13:54
*** pchavva has joined #openstack-meeting13:57
*** annabelleB has quit IRC13:57
*** rhochmuth has joined #openstack-meeting13:57
*** koji has joined #openstack-meeting13:58
*** markstur has joined #openstack-meeting13:59
*** Haruki has joined #openstack-meeting13:59
*** rossella__ has joined #openstack-meeting13:59
*** awaugama has joined #openstack-meeting14:00
rhochmuth#startmeeting monasca14:00
openstackMeeting started Wed Jun  7 14:00:25 2017 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: monasca)"14:00
openstackThe meeting name has been set to 'monasca'14:00
*** alexchadin has quit IRC14:01
rhochmuthuh oh, no agenda for today's meeting14:01
rhochmuththat's a first14:01
*** fnaval has quit IRC14:01
rhochmutho/14:01
rhochmuthanyone around today?14:01
kojio/14:01
hosanaio/14:01
Harukio/14:01
*** sgrasley1 has joined #openstack-meeting14:01
*** fnaval has joined #openstack-meeting14:01
rhochmuthhi koji and hosanai and haruki14:02
Fdaisukeo/14:02
hosanaihello14:02
Harukihi14:02
kojihello14:02
rhochmuthi guess the new time-slot works out a little better for everyone in japan14:02
rhochmuthbut, it is still a little late14:02
*** yamamoto has quit IRC14:03
*** rossella_ has quit IRC14:03
hosanaiyeah, it works for me :-)14:03
koji11:00pm on our time zone now14:03
rhochmuthdoes anyone have any topics or reviews14:03
rhochmuthmy wife is in japan14:03
rhochmuthshe called me at 4:00 AM14:03
*** yamamoto has joined #openstack-meeting14:03
*** markstur has quit IRC14:04
hosanaihahaha. she tries to kill you :-)14:04
rhochmuthshe does her best14:04
hosanaiI would like to share info of analytics status.14:04
rhochmuthtorture is her specialty though14:04
rhochmuthhosanai: you have the floor14:04
rhochmuth#topic monasca-analytics14:04
*** openstack changes topic to "monasca-analytics (Meeting topic: monasca)"14:04
hosanaithanks!14:05
*** shinya_kwbt has joined #openstack-meeting14:05
hosanaibrad gave us data for analytics14:05
Harukiinteresting!14:05
rhochmuthbrad klein?14:05
hosanaiyeah14:05
rhochmuthvery nice14:05
hosanaiand Fdaisuke checked the data but information is not enough for analytics14:06
*** VW has joined #openstack-meeting14:06
*** VW has quit IRC14:06
rhochmuthwhat data did you get?14:06
hosanaiWe got it.14:06
rhochmuthi meant type of data14:06
*** VW has joined #openstack-meeting14:06
rhochmuthwas it metrics, logs?14:06
hosanaisorry, i miss understood. Fdaisuke, could you explain it?14:07
*** yamamoto has quit IRC14:08
Fdaisukeok14:08
*** jgu has joined #openstack-meeting14:08
Fdaisukethere is no metorisc and logs, just only "timestamps" and "value" (100% or not)14:09
hosanaimy rough understanding is we got timestamp, value and value_meta for each services such as swift, nova and so on14:10
*** armax has joined #openstack-meeting14:10
rhochmuthdo you have the metric name and dimensions?14:10
Fdaisukethanks, hosanai14:10
kojiisn't the "value" a metric?14:11
*** zz_dimtruck is now known as dimtruck14:12
Harukimemory usage or like that?14:12
hosanaiin dimensions, there is service and in measurements we have timestamp, value and value_meta. i think.14:13
hosanaiit looks status of services.14:14
rhochmuthand are there any points in which incidents have been labeled?14:14
*** noslzzp has quit IRC14:14
*** cdub has joined #openstack-meeting14:14
rhochmuthfor example, do you have a set of timestamps and label, for an incident and/or type of incident14:15
hosanaiyeah, he explained us unexpected behavior and the time.14:15
rhochmuthso, you have a bunch of metrics, and then a set of incidents and the timestamps for when they occured it sounds like14:16
*** janki has quit IRC14:16
hosanaiwe don't have metric like memory in the data.14:17
*** ansmith has joined #openstack-meeting14:17
hosanaionly service status14:17
*** zhurong has quit IRC14:17
hosanais/memory/memory usage/14:18
rhochmuthoh, so basically if swift goes down, the value of some metric, such as status with dimension service=swift is 1.014:18
*** mickeys has joined #openstack-meeting14:19
Harukionly 1 or 0?14:19
*** markstur has joined #openstack-meeting14:20
hosanaiFdaisuke, could you give us an example? you said the data looks like 100%, 90%...14:20
*** diablo_rojo has joined #openstack-meeting14:21
*** jamesmcarthur has joined #openstack-meeting14:22
*** kamil_ has joined #openstack-meeting14:22
*** prateek has quit IRC14:22
Fdaisukei saw 100%, 90%, 40%, sometimes 0%14:22
rhochmuthok, so other than the status metric, is there anything else of interest?14:23
rhochmuthif that is all you have, then i agree, the dataset is not going to offer a lot of insight14:23
hosanaiyeah so Fdaisuke sent email to brad to get additional data.14:23
*** mickeys has quit IRC14:23
rhochmuthor data analysis opportunites14:23
*** jsuchome has joined #openstack-meeting14:24
rhochmuthi think what you need is a lot of metrics14:24
rhochmuththe status metric is already informing you about incidents14:24
*** markstur has quit IRC14:24
*** pradk has joined #openstack-meeting14:24
hosanaii think so. I hope brad keep the data :-)14:24
*** rbrndt has joined #openstack-meeting14:25
rhochmuthif you had more data, you could potentially identity other metrics that represent the incident14:25
rhochmuthor possibly RCA14:25
hosanaihopefully :-)14:26
rhochmuthit would also be interesting to have the set of alarms that occurred14:26
rhochmuththen you could train your data set using the alarms as the response/labels14:27
*** galstrom_zzz is now known as galstrom14:27
rhochmuthand then try and predict incidents when you don't have the alarms14:27
*** pradk has quit IRC14:28
hosanaii see the alarms are useful to create labels.14:28
rhochmuthin other works can you develop a model for predicting alarms14:28
rhochmuthyeah, i think that would be an interesting problem14:29
rhochmuthgiven a set X of all the metrics and a set y that consists of all the alarms14:29
hosanaibrad explained us if the status is not 100%, it's a problem from operator point of view.14:30
*** Guest96567 has quit IRC14:30
rhochmuthso, status can be used too14:30
rhochmuthi guess 0 is no problem14:30
*** pradk has joined #openstack-meeting14:31
rhochmuth25% could be low status14:31
rhochmuth100% could be there is a problem14:31
rhochmuth> 75% could be there is a high probability there is a problem14:31
rhochmuthso, that could be useful if you had the other metrics14:31
rhochmuthyou could use status as the response/label set14:31
rhochmuthand then train on that using the metrics as predictors14:32
hosanaithanks for the info/advise:-)14:32
rhochmuthsimilar to how alarms would be used14:32
rhochmuthyour welcom14:32
hosanaithat's all I would like to share14:32
rhochmuthi think you need a lot more data14:32
hosanaiyeah that's right14:33
rhochmuthyou could also take the status variables, and treat it as binary14:33
rhochmuthfor example, anything above 50% is a problem14:33
*** annabelleB has joined #openstack-meeting14:33
*** annabelleB has quit IRC14:33
rhochmuththen your problem turns into a binary classification problem14:33
rhochmuthbut, i'm not sure that is what you want to do14:34
hosanaia binary classification means 2 values classification?14:34
rhochmuthcorrect14:34
rhochmuthbut, you can also treat the predictor as continous, which is what the status is14:35
*** annabelleB has joined #openstack-meeting14:35
*** annabelleB has quit IRC14:35
hosanaiit's a good way to handle the problem as a binary classification to get good result14:36
rhochmuthso, if brad can get you more data, even without the alarms, i think you might have something you can start with14:36
hosanaiyeah, we can push analytics ahead with brad's help14:37
rhochmuthit would also be very interesting to know what metrics correlate well with problems14:37
hosanaii think so it's kind of RC14:38
rhochmuththat would be good for RCA14:38
hosanaiyeah, and witec introduced Fujitsu's colleagues who created original algorithm (i forgot the approach) for analytics14:40
*** markstur has joined #openstack-meeting14:41
rhochmuthdo you know the names?14:41
*** rbartal has quit IRC14:41
*** rossella__ has quit IRC14:41
hosanaii forgot it I got a paper but did't read it yet :(14:42
*** Hosam has joined #openstack-meeting14:43
hosanainames for the guys?14:44
hosanaiyou mean14:44
rhochmuthwell, i was wondering if they were hpe or fujitsu folks14:44
*** markstur has quit IRC14:45
*** rossella__ has joined #openstack-meeting14:45
hosanaiI will send you the names later. I can't access company email now.14:46
*** mtanino_ has joined #openstack-meeting14:46
rhochmuthnp14:46
hosanaiat least 9 hours later :-)14:46
*** mabderrahim has joined #openstack-meeting14:46
rhochmuthi thought you were still at work14:47
rhochmuthi'm dissapointed14:47
rhochmuth:-)14:47
hosanaihahaha14:47
rhochmuthso, is that it for today?14:49
*** rossella__ has quit IRC14:50
hosanaii don't have anything now14:50
*** hongbin has joined #openstack-meeting14:50
rhochmuththx hosanai14:51
rhochmuthi guess i'll end the meetign a little early14:51
rhochmuth#endmeeting14:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:51
openstackMeeting ended Wed Jun  7 14:51:29 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:51
hosanaithanks rhochmuth and all14:51
Harukithx14:51
*** kamil_ has quit IRC14:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-06-07-14.00.html14:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-06-07-14.00.txt14:51
*** sgrasley1 has quit IRC14:51
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-06-07-14.00.log.html14:51
rhochmuthbye14:51
kojithx14:51
*** koji has quit IRC14:51
Fdaisukethank you, bye14:51
*** Haruki has quit IRC14:52
*** hosanai has quit IRC14:52
*** Fdaisuke has quit IRC14:52
*** lbragstad has joined #openstack-meeting14:52
*** rbrndt has left #openstack-meeting14:53
*** Menthos has joined #openstack-meeting14:54
*** Menthos has quit IRC14:54
*** slaweq has quit IRC14:54
*** banhgao has joined #openstack-meeting14:54
*** slaweq has joined #openstack-meeting14:54
*** slaweq has quit IRC14:54
*** Menthos has joined #openstack-meeting14:54
*** kevzha01_ has quit IRC14:55
*** armstrong has quit IRC14:56
*** ad_rien_ has joined #openstack-meeting14:57
*** marst has joined #openstack-meeting14:57
*** mlakat has quit IRC14:58
*** msimonin has joined #openstack-meeting14:59
*** manjeets__ has joined #openstack-meeting14:59
Menthos#startmeeting massively_distributed_clouds15:00
openstackMeeting started Wed Jun  7 15:00:03 2017 UTC and is due to finish in 60 minutes.  The chair is Menthos. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: massively_distributed_clouds)"15:00
openstackThe meeting name has been set to 'massively_distributed_clouds'15:00
Menthos#chair ad_rien_15:00
openstackCurrent chairs: Menthos ad_rien_15:00
ad_rien_Hi guys15:00
ad_rien_#topic roll call15:00
MenthosHello guys15:00
msimonino/15:00
*** openstack changes topic to "roll call (Meeting topic: massively_distributed_clouds)"15:00
banhgaoo/15:00
ansmitho/15:00
kgiustio/15:00
mabderrahimo/15:00
ad_rien_please add your name in the pad15:00
*** cebruns has quit IRC15:00
*** rcherrueau has joined #openstack-meeting15:00
ad_rien_#info agenda15:01
ad_rien_#link https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 67515:01
*** manjeets has quit IRC15:01
*** isq has quit IRC15:01
*** korzen_ has quit IRC15:01
*** pbressan has joined #openstack-meeting15:01
*** markstur has joined #openstack-meeting15:01
knikollao/15:02
*** cebruns has joined #openstack-meeting15:02
ad_rien_ok15:02
ad_rien_so let's start15:02
*** aselius has joined #openstack-meeting15:02
*** parnexius has joined #openstack-meeting15:02
*** georgk has joined #openstack-meeting15:03
ad_rien_parnexius should join us soon15:03
ad_rien_so I think we can move to the first item15:03
pbressanhe is on15:03
parnexiusgoodday!15:03
ad_rien_Just saw it yes15:03
georgk#info Georg Kunz15:03
*** markstur has quit IRC15:03
*** korzen has joined #openstack-meeting15:03
ad_rien_Hi parnexius15:03
ad_rien_#topic announcements15:03
*** openstack changes topic to "announcements (Meeting topic: massively_distributed_clouds)"15:03
*** markstur has joined #openstack-meeting15:03
ad_rien_so from my side15:03
ad_rien_we exchanged a few emails with the foundation and cockroach folks. We arranged a meeting15:04
*** AliSan has joined #openstack-meeting15:04
*** julim has quit IRC15:04
ad_rien_for June the 16th.15:04
ad_rien_more information will be delivered later.15:04
*** jamesdenton has quit IRC15:04
*** ralonsoh_ has joined #openstack-meeting15:04
ad_rien_Then we exchanged also a couple of emails with other WG Chairs in order to see how we can improve cross collaborations.15:05
ad_rien_jamemcc was in charge of finding the best slot. He opened a doodle.15:05
ad_rien_But I don't know whether a final slot has been identified.15:05
ad_rien_jamemcc:  ?15:05
*** rossella__ has joined #openstack-meeting15:06
ad_rien_maybe you can give us a few details regarding this meeting15:06
*** tobberyd_ has joined #openstack-meeting15:06
ad_rien_ok not sure jamemcc is available.15:06
*** ralonsoh has quit IRC15:07
*** ralonsoh_ is now known as ralonsoh15:07
parnexiusad_rien: please let me know the details when you find out.15:07
ad_rien_so last point I want to announce from my side is that we are going to change the tag for the emails from MassivelyDistributed to FEMDC15:07
*** jgu has left #openstack-meeting15:07
ad_rien_shorter and ….shorter15:07
msimonin:)15:08
Menthos#info email tag will now be FEMDC15:08
ad_rien_so FEMDC for Fog / Edge / Massively Distributed Clouds15:08
ad_rien_so I will make an emal to announce that on the ML and update the wiki page15:08
ad_rien_#action ad_rien_ announce the new tag on the ML and on the wiki page15:09
ad_rien_that's all from my side15:09
ad_rien_so guys the floor is yours15:09
*** jaypipes has joined #openstack-meeting15:09
*** kornica has joined #openstack-meeting15:09
ad_rien_ok15:10
ad_rien_so seems not15:10
parnexiusSmall update on my side:15:10
*** tobberydberg has quit IRC15:10
ad_rien_ok sorry15:10
ad_rien_please parnexius go on15:10
parnexiusPlease note my new email address paul-andre.raymond@b-yond.com15:10
parnexiusI will keep the parnexius handle for now... but that may change in the future.15:10
ad_rien_ok15:11
parnexiusWhen we get to use cases.... I will give updates on that topic.15:11
parnexiusthat is all15:11
ad_rien_ok15:11
*** rossella__ has quit IRC15:11
*** rcernin has quit IRC15:11
ad_rien_Could you please update the wikipage parnexius15:11
ad_rien_?15:11
ad_rien_with your new nick and email15:11
parnexiusI will take the action.15:12
*** kornica has quit IRC15:12
ad_rien_ok15:12
ad_rien_anything else ?15:12
ad_rien_if not we can switch to the AMQP point.15:12
ad_rien_1, 215:12
ad_rien_… 3..15:13
ad_rien_ok so let's move to AMQP15:13
ad_rien_#topic Roadmap AMQP15:13
*** openstack changes topic to "Roadmap AMQP (Meeting topic: massively_distributed_clouds)"15:13
kgiustihey!  ansmith want to cover kolla status?15:13
*** sgrasley1 has joined #openstack-meeting15:13
ansmithgood progress on kolla front as recorded in etherpad15:13
ansmithblueprints to enable separate messaging backends and a role for the qdrouterd15:13
ansmithtwo reviews in progress15:14
Menthos#chair parnexius15:14
openstackCurrent chairs: Menthos ad_rien_ parnexius15:14
msimoninansmith: that's great !15:14
*** tobberyd_ has quit IRC15:14
ansmithwe then went back to log from last meeting to build out deliverables/roadmap15:14
ad_rien_ansmith:  which line  in the pad please?15:15
ansmith#70415:15
kgiustistill some Q's about goals/deliverables...15:15
*** felipemonteiro_ has quit IRC15:15
kgiustiesp. in terms of tests and metrics desired this cycle15:16
kgiustiup to now, we've tested only the messaging layer (clients of oslo.messaging)15:16
kgiustifor thruput/latency against various mb tech (at load).15:16
msimoninwith ombt ?15:17
kgiustithese are fairly specific (and static) load tests - I would think not very useful for FEMDC15:17
kgiustimsimonin: yep!15:17
ad_rien_I'm seeing ombt as micro bench15:17
msimoninDid you test several topology of qdrouterd topology  ?15:17
ad_rien_whereas Rally/….. can be macrobenchs15:17
ad_rien_so both are useful15:17
msimoninI mean qdrouterd in network mode ?15:18
*** bastafidli has joined #openstack-meeting15:18
kgiustimsimonin: in general no - just rpc throughput/latency wrt a rabbitmq deployment (non clustered)15:18
*** sridharg has quit IRC15:18
*** slaweq__ has joined #openstack-meeting15:18
kgiustiSo both micro (ombt2) and macro (ralley/osprofiler) for different message bus topologies?15:19
ad_rien_yes15:19
*** mdovgal has joined #openstack-meeting15:19
msimoninkgiusti: yes different bus topologies are in the scope (I guess)15:19
ad_rien_I think that should be our experimental protocol15:19
kgiustitesting multi-hop effect of latency/thruput15:19
kgiustiand failure/recovery aspects15:19
kgiustikewl.15:19
*** mickeys has joined #openstack-meeting15:20
ad_rien_yes.15:20
msimoninkgiusti ansmith One question regarding kolla integration15:20
kgiustiThe other bit of news is still no new maintainers for zeromq - that may impact testing.15:20
ad_rien_I think we can open a thread and iterate by mail to move forward on that protocol15:20
kgiustiad_rien_: +1 will email FEMDC15:20
msimoninis it planned to enable the deployment of a network of qdrouterd ?15:20
ansmithyes, kolla-ansible provides an all-in-one and multinode inventory15:21
ansmithintend to support multinode, it is still on the punchlist for the qdrouterd role15:21
msimoninyes sure but I saw that the qdrouterd was configured in a standalone mode15:21
*** salv-orlando has joined #openstack-meeting15:22
ansmithnot reflected in the patch yet15:22
msimoninThat's maybe too much for this patch ;à15:22
*** noslzzp has joined #openstack-meeting15:22
ansmithyes, it may follow once the qdrouterd role lands15:22
*** slaweq__ has quit IRC15:22
msimoninansmith: cool :)15:23
msimoninbecause I guess that's one of the thing we would like to experiment15:23
*** jamesdenton has joined #openstack-meeting15:23
ansmith+115:23
*** rossella__ has joined #openstack-meeting15:24
ad_rien_regarding the jepsen test,15:24
*** mickeys has quit IRC15:24
ad_rien_while I like the idea I think it will be rather focus on the bus itself15:24
ad_rien_not sure whether this can help us for the FEDMC15:25
ad_rien_i.e. we already have ombt (thanks guys ;))15:25
ad_rien_so ombt  + rally/… should be sufficient.15:25
ansmithsounds good15:25
ad_rien_what was your idea guys ?15:25
ansmiththe idea for jepsen was to understand the behaviors of the backends themselves15:25
ansmithwith regard to resiliency, etc.15:25
ad_rien_ok +115:26
ad_rien_good point15:26
ad_rien_I don't know whether rally has some injection fault scenarios?15:26
ansmithyes, it injects network faults, etc. to see how service recovers15:26
ad_rien_rcherrueau:  and msimonin have discovered osfault15:26
msimonin#link https://os-faults.readthedocs.io/en/latest/15:27
ad_rien_also from their side but seems not kolla/docker ready15:27
kgiustiooooh  - new shiney!!!15:27
ad_rien_so we should probably investigate more in the rally scenarios.15:27
*** julim has joined #openstack-meeting15:27
ansmithagree15:27
kgiustiad_rien_: yep - ombt2 + Rally in the near term.15:28
msimonin+115:28
ad_rien_ok so to summarize15:28
ad_rien_action 1: start a thread for defining the experimental protocol15:29
ad_rien_action 2: Inria can give a first try to deploy qpid router with EnoS15:29
*** julim has quit IRC15:29
ad_rien_guys do you see other actions?15:30
ad_rien_that we can do in a short term?15:30
msimoninnetwork of qdrouterd ?15:30
ad_rien_kgiusti: ansmith: if you are interested we can give you an open access to G5K15:30
ad_rien_so you can perform some integration tests with EnOS also from your side (if it helps).15:31
*** dteselkin has quit IRC15:31
kgiustimsimonin: we should really focus on that - single router doesn't buy us much in terms of distribution and redundancy15:31
ansmiththat would be very helpful15:31
msimoninkgiusti: +115:31
kgiustiad_rien_: yes!15:31
ad_rien_or if you have a testbed you can also use EnOS directly15:31
msimoninkgiusti: how can we help ?15:31
*** TxGirlGeek has joined #openstack-meeting15:32
* ad_rien_ takes his Discovery/Inria chair hat15:32
parnexiusIs there more details on the high level use cases we are trying to test?15:32
ad_rien_Please note that the engineer that will focus on AMQP experiments should not arrive before July15:32
kgiustiparnexius: I think that's what we need to iron out first (via email thread)15:33
parnexiusSounds good.15:33
kgiustiparnexius: for example, what's a good topology for say nova?  router on controller, per conductor, per compute?15:33
ad_rien_so to be honest, Inria will put significant efforts only when this engineer will be hired. Right now, we can only provided minimal support15:33
*** caboucha has joined #openstack-meeting15:33
*** dteselkin has joined #openstack-meeting15:34
ad_rien_s/provided/provide15:34
*** rderose has joined #openstack-meeting15:34
ad_rien_just to be sure that we do not take too much commitments15:34
kgiustiad_rien_: np - we can define the test scenarios first, test the smaller ones here are rh15:34
ad_rien_ok15:34
ad_rien_maybe yes15:34
ad_rien_1./ test scenarios15:34
ad_rien_2./ required testbeds15:35
ad_rien_3./ divide and conquer15:35
ad_rien_ok15:35
kgiustiad_rien_: +115:35
ad_rien_kgiusti would you agree to start the thread for identifying the scenarios15:35
ad_rien_?15:35
kgiustiad_rien_: certainly!15:36
ad_rien_#action Inria give a try to deploy qpid with EnOS15:36
*** LanceHaig has quit IRC15:36
ad_rien_#action kgiusti open a thread for identifying the experimental protocol15:36
ad_rien_ok15:36
ad_rien_anything else on that topic or we can switch to the next one ,15:37
ad_rien_?15:37
kgiustiI'm done :)15:37
*** caboucha has quit IRC15:37
ad_rien_msimonin:  s/#action Inria/#action msimonin15:37
ad_rien_:-)15:37
msimoninLOL15:37
ad_rien_:-P15:37
ad_rien_ok so next topic15:38
Menthosansmith: what about Strawman?15:38
*** reedip_ has joined #openstack-meeting15:39
ansmithah, it was a stab at putting some dates down15:39
*** rderose has left #openstack-meeting15:39
ad_rien_milestones?15:39
ad_rien_:-)15:39
Menthosansmith: okay :-)15:39
ansmithif we track 1. and 2. above it would help us assess progress towards milestonew15:39
ad_rien_ok so next topic15:39
*** julim has joined #openstack-meeting15:39
ad_rien_#topic roadmap cockroach15:40
*** openstack changes topic to "roadmap cockroach (Meeting topic: massively_distributed_clouds)"15:40
ad_rien_ok so as I announced at the begining15:40
ad_rien_we succeeded to get a positive reply from cockroach folks.15:41
*** gyee has joined #openstack-meeting15:41
ad_rien_and we arranged a one hour meeting to present the use-case in general and to ask a few couples of questions15:41
ad_rien_regarding cockroach internals15:41
ad_rien_we copy/paste the question in the pad15:42
ad_rien_these are general questions15:42
ad_rien_if you have additional ideas please15:42
ad_rien_feel free to complete it ;)15:42
*** rossella__ has quit IRC15:43
ad_rien_ok so that' s all on that point.15:43
ad_rien_if there is no comment/questions then we can move to the next point;15:43
ad_rien_#topic roadmap identification use-cases15:44
*** openstack changes topic to "roadmap identification use-cases (Meeting topic: massively_distributed_clouds)"15:44
*** belmoreira has quit IRC15:44
ad_rien_parnexius: the floor is yours15:44
parnexiusThanks.15:44
parnexiusThe first point is that I would like to request for help.15:44
parnexiusPlease let me know if you want to contribute to this effot.15:45
ad_rien_there was a person in Boston15:45
ad_rien_Andrew XXXX15:45
*** mlakat has joined #openstack-meeting15:46
ad_rien_but unfortunately I didn't find his contact.15:46
parnexiusI will look him up n the attendee list. There was just one andrew.15:46
ad_rien_Maybe on can send an email on the ML15:46
ad_rien_(dev, operator,…) and see whether we got some answer15:46
parnexiusAny Ukasick from ATT15:47
ad_rien_something like. Ok for this cycle we agree to move forward on  (i) AMQP (ii)  and (iii) use-case identifications.15:47
jamemccJamey (with AT&T hat on):  There was a Boston Talk somewhat on this topic in Boston.  I believe that the speaker - Kandan should want to participate - or more likely assign to participate.15:47
jamemccLooking for link to the talk15:47
*** felipemonteiro has joined #openstack-meeting15:47
parnexiusOK. I saw both talks by Kandan. Can you make an intro?15:48
*** AliSan has quit IRC15:48
ad_rien_ok sounds great thanks jamemcc15:48
*** felipemonteiro_ has joined #openstack-meeting15:48
parnexiusSecond question on logistics.15:48
jamemccYes Paul15:48
parnexiusWhat is the best way to share information in this group?15:49
ad_rien_mL15:49
ad_rien_dev15:49
parnexiusI have some notes on powerpoint .... are you OK with attachments on the email List?15:49
ad_rien_so we can make references to threads when relevant15:49
ad_rien_put the link15:49
ad_rien_and your slides online15:50
ad_rien_?15:50
ad_rien_would it be a good solution from your side15:50
ad_rien_ok sorry (back to US today so rather tired from my side)15:50
parnexiusWhat would be online ? Github? Slideshare?15:50
jamemcc#link  https://www.youtube.com/watch?v=7DuKzaBaRwY Telco Edge Cloud Use Cases15:50
ad_rien_I was saying that we should use the dev ML because then it enables us to make links towards relevant threads15:50
*** oidgar has quit IRC15:50
ad_rien_when you want to attach some documents just put them online and add the link within the mail you will send on the ML15:51
ad_rien_is it a good solution from your side parnexius ?15:51
parnexiusOK. Sounds good.15:51
parnexius+115:51
ad_rien_ok15:51
parnexiusLast point.15:51
ad_rien_please note that we changed the tag15:51
*** trinaths has joined #openstack-meeting15:51
ad_rien_[MassivelyDistributed] -> [FEDMC]15:51
parnexiusI have put some notes on etherpad about what I think some test use cases are.15:51
ad_rien_ok15:52
ad_rien_15:52
parnexiusThere may be other ways to think about use cases: (service scenarios, topology...)15:52
ad_rien_52min15:52
*** felipemonteiro has quit IRC15:52
parnexiusI think we want to cover all.15:52
ad_rien_would it be possible to discuss that deeper15:52
ad_rien_during our next meeting15:52
ad_rien_we will put it sooner in the agenda15:53
parnexiusI will start with a thread on the mailing list and report back next meeting.15:53
*** Rockyg has joined #openstack-meeting15:53
ad_rien_I would appreciate to get some feedbacks from jamemcc regarding the last LCCO meeting and the extreme testing challenges.15:53
ad_rien_ok thanks parnexius15:53
*** annabelleB has joined #openstack-meeting15:53
ad_rien_can we move to the next topic?15:53
parnexiusI am done15:53
ad_rien_ok thanks15:53
ad_rien_#action parnexius start a thread on the ML: objective gather external/additional contributors15:54
*** rossella__ has joined #openstack-meeting15:54
ad_rien_#action adrien send an email to the foundation to collect a few email addresses15:54
ad_rien_#action jamey introduce Kandan to parnexius15:55
ad_rien_ok15:55
ad_rien_so let's move to the next topic15:55
ad_rien_#topic EnoS15:55
*** openstack changes topic to "EnoS (Meeting topic: massively_distributed_clouds)"15:55
ad_rien_jamemcc:  can you please tell us15:55
ad_rien_what is the current status regarding the discussion within the LCCO15:55
ad_rien_?15:55
jamemccFor Extreme Testing - the main work is now going on in this Atlasssian Space - lke an Etherpad but with more join editign features: #link https://openstack-lcoo.atlassian.net/wiki/display/LCOO/Working+Space+for+Exteme+Testing+and+related+topics15:55
ad_rien_did you make progress15:55
ad_rien_so what is the idea (just 4 min left)15:56
ad_rien_we read the page15:56
ad_rien_and prepare questions?15:56
jamemccThe section that mostly describes the work is in the Tasks section.  I can't really give better stytus on the tasks.15:56
ad_rien_ok15:56
ad_rien_maybe we can discuss deeper next time too?15:57
jamemccYeah - I can try to bring a specialty team member to the next session15:57
ad_rien_cool15:57
ad_rien_the idea is to see whether we can combine our effort15:57
*** hieulq_ has joined #openstack-meeting15:57
ad_rien_ok15:57
jamemccOK good from our side15:57
ad_rien_thanks15:57
ad_rien_We have a todo from our side15:57
ad_rien_but we will discuss next time too15:57
ad_rien_sorry15:57
ad_rien_for the timing today15:57
ad_rien_I don't think we have time for opendiscussion15:58
ad_rien_unless there is something really important15:58
ad_rien_if not please15:58
ad_rien_put it in the pad15:58
jamemccI'll put Cross WG info in the pad15:58
ad_rien_we will discuss next time15:58
ad_rien_thanks jamemcc15:58
ad_rien_+115:58
*** Sukhdev has joined #openstack-meeting15:58
ad_rien_ok thanks guys for attending the meeting15:58
parnexiusThank you!15:58
ad_rien_and for all your contributions15:58
msimoninthanks ad_rien_15:58
ad_rien_let's keep in touch by mail15:58
ad_rien_lot of actions15:58
ad_rien_++15:58
ad_rien_;)15:58
Menthosthanks all15:59
Menthos#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Wed Jun  7 15:59:03 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/massively_distributed_clouds/2017/massively_distributed_clouds.2017-06-07-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/massively_distributed_clouds/2017/massively_distributed_clouds.2017-06-07-15.00.txt15:59
*** Apoorva has joined #openstack-meeting15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/massively_distributed_clouds/2017/massively_distributed_clouds.2017-06-07-15.00.log.html15:59
*** parnexius has quit IRC15:59
*** pbressan has quit IRC15:59
smcginnis#startmeeting Cinder16:00
openstackMeeting started Wed Jun  7 16:00:03 2017 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: Cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
*** kgiusti has left #openstack-meeting16:00
*** banhgao has left #openstack-meeting16:00
mdovgalHi16:00
geguileohi!16:00
tbarronhi16:00
smcginnisping dulek duncant eharney geguileo winston-d e0ne jungleboyj jgriffith thingee smcginnis hemna xyang1 tbarron scottda erlon rhedlind jbernard _alastor_ bluex karthikp_ patrickeast dongwenjuan JaniceLee cFouts Thelo vivekd adrianofr mtanino karlamrhein diablo_rojo jay.xu jgregor lhx_ baumann rajinir wilson-l reduxio wanghao thrawn01 chris_morrell watanabe.isao,tommylikehu mdovgal ildikov wxy16:00
e0nehi16:00
*** sambetts is now known as sambetts|afk16:00
smcginnisviks ketonne abishop sivn16:00
*** msimonin has left #openstack-meeting16:00
Swansonhi16:00
rajiniro/16:00
hemna@!16:00
pewphemna |ʘ‿ʘ)╯16:00
scottdahi16:00
_alastor_o/16:00
smcginnishemna: That bot is calm today. :)16:00
wxyhi16:01
jungleboyj@!16:01
pewpjungleboyj (。Ő▽Ő。)ノ゙16:01
*** fzdarsky is now known as fzdarsky|afk16:01
lhx__o/16:01
jungleboyjsmcginnis:  It can just do a friendly wave now.16:01
smcginnisjungleboyj: A kinder, gentler pewpbot. :)16:02
smcginnis#topic Announcements16:02
*** openstack changes topic to "Announcements (Meeting topic: Cinder)"16:02
jungleboyjsmcginnis: pewpbot doesn't have to always be angry.16:02
smcginnisOur P-2 deadline is today.16:02
smcginnisI will probably request that cut later in the day.16:03
* diablo_rojo_phon sneaks in16:03
xyang2hi16:03
tommylikehuoh16:03
smcginnisLast chance for drivers and specs. Anything that didn't make it can get in line for Queens.16:03
e0nesmcginnis: do we have anything to get merged before P-2?16:03
bswartz.o/16:03
smcginnise0ne: I think all the remaining drivers still had issues to resolve.16:03
smcginnisEither code or CI.16:04
*** Menthos has quit IRC16:04
smcginnisI haven't looked too closely at specs in the last few days, but I have the feeling we've already bitten off more than we can chew for this cycle with new things.16:04
* e0ne forgot about specs deadline :(16:05
smcginnis#link https://releases.openstack.org/pike/schedule.html Pike release schedule16:05
smcginnisSo we are 12 weeks out from release.16:06
smcginnisStill some good time to get things done.16:06
smcginnisBut let's not forget about it until it's too late.16:06
SwansonCould fit in an entire ocata2 in that time.16:06
e0neit's only 2 months before feature freeze16:06
smcginnisWould be great not to have a crunch at the end, but I know that's inevitable.16:06
smcginnise0ne: Yeah, that'll go quick.16:06
*** david-lyle has joined #openstack-meeting16:07
smcginnis#topic targetd driver for remote LVM management16:07
*** openstack changes topic to "targetd driver for remote LVM management (Meeting topic: Cinder)"16:07
smcginnise0ne: All yours.16:07
e0nesmcginnis: thanks16:07
*** noslzzp has quit IRC16:07
e0ne#link https://github.com/open-iscsi/targetd16:07
e0neI just want to know if community is interested in this ^^16:08
e0neI played with this last week and get working target driver for create/delete/attach/detach16:08
*** mlakat has quit IRC16:08
eharneyi think it's a good idea, i was long ago attempting to write a driver for this as well16:08
e0neit's a remote LVM management16:08
smcginnisI like it.16:08
e0neso we can use LVM driver as any other16:09
eharneyi don't like the idea of trying to move from the LVM driver to this16:09
eharneybut having both, sure16:09
hemnae0ne, nice.   I could have used that for my rpi demo :)16:09
jungleboyjhemna:  +116:09
jungleboyjYeah, seems like a cool idea.16:09
e0neeharney: sure, it's just adding a new (target) driver16:09
hemnaI would hope this would be a completely separate driver16:10
eharneytarget driver?16:10
eharneyit should be a volume driver...16:10
hemnaeharney, +116:10
e0neeharney, hemna:  it makes sense16:10
e0neI'll propose a patch early next week16:10
eharneydoing it as a target driver implies it would still use local lvm, which i think is not the goal unless i'm misinterpreting this16:10
jungleboyjSeems like it should be handled as a separate driver.16:11
e0neeharney: target driver is not enough  for snapshot-related operations16:11
smcginnisSo queens and we would need an associated gate job running to test it, just to state that explicitly.16:11
*** jamesdenton has quit IRC16:11
*** ad_rien_ has left #openstack-meeting16:12
e0neit could be easier to implement a separate driver16:12
eharneyit should be a separate driver16:12
e0nesmcginnis: sure, it's too late for P16:12
e0neeharney: ok16:12
eharneyas far as gate jobs, does targetd function on ubuntu?16:12
e0neeharney: yes16:12
eharneygood to know16:12
e0neeharney: I tried it on my ubuntu-based devstack16:13
e0nethanks everybody for feedback. It's everything from me if no more questions16:13
smcginnise0ne: Great, thanks for looking into it.16:13
e0nesmcginnis: np16:13
smcginnisI think that could address a few peoples needs.16:13
*** sshank has joined #openstack-meeting16:14
eharneyi'll be happy to review16:14
smcginnisThat was all on the agenda. Anything else to bring up? Or do we get to get out of here early for once?16:14
*** bh526r has joined #openstack-meeting16:14
e0neeharney: thanks! I'll let you know when it will be ready for review16:14
hemnasmcginnis,16:15
* jungleboyj brings up replication so we can rathole for 45 minutes.16:15
smcginnishemna:16:15
*** julim has quit IRC16:15
e0ne:)16:15
hemnaI tried +A'ing a few of the mark drivers unsupported16:15
hemnathere was one that got a response from the maintainer16:15
hemnahe said he was working on the CI16:16
smcginnishemna: I saw that.16:16
smcginnis#topic Open discussion16:16
*** openstack changes topic to "Open discussion (Meeting topic: Cinder)"16:16
Swansonjungleboyj, Still think replication v3 should be no replication.16:16
hemnaso I didn't issue a recheck on it, as it would go through16:16
*** georgk has quit IRC16:16
smcginnishemna: Probably OK to wait a few days for that since they appear to be so close.16:16
hemnaSwanson, +A16:16
e0nesmcginnis, hemna:  the same for virtuozzo driver16:16
patrickeastSwanson: +116:16
hemnalets remove replication.16:16
e0neI believe we can mark drivers as supported once CI issues will be fixed16:16
* jungleboyj shakes my head.16:16
mdovgalhemna, from everywhere. good idea16:17
hemnasmcginnis, https://review.openstack.org/#/c/463029/16:17
hemnathat one16:17
smcginnise0ne: Yes, as soon as we get good responses we can either abandon or revert those.16:17
e0nesmcginnis: +1. that's what I replied in IRC16:17
smcginnishemna: I'm fine if that really is just over the weekend. But if there's no movement there by late Monday I will do the recheck if no one else does.16:17
Swansonhemna, let custom extra specs handle it for each driver and cinder can wash its hands of it.16:17
e0nehemna: here is one more https://review.openstack.org/#/c/463030/16:18
hemnasmcginnis, ok cool.  I just wanted to raise visibility on it, and that's why I didn't recheck.16:18
smcginnisSwanson: jgriffith must not be here or I think he would be blowing up. :)16:18
Swansonsmcginnis, I know, right?16:18
smcginnishemna: Cool, thanks.16:18
hemnasmcginnis, I doubt it.  I think he'd be on the bandwagon :)16:18
eharneyon CI... we currently have https://review.openstack.org/#/c/471352/ pending to fix the Ceph job16:18
patrickeastalso ci related, one thing we may want to consider is that the upstream openstackci stuff is pretty broken for anyone new coming in, doesn't look like its really being maintained16:19
smcginnishemna: I think he'd blow up because that was what he was saying all along. :)16:19
hemnahrmm " I promise that this cyle our CI will start reporting again before summer ends."16:19
patrickeastsomewhat affects us since we have hard requirements for one16:19
*** rcherrueau has quit IRC16:19
hemnathat's like months from now.16:19
smcginnishemna: Yeah, wrong answer16:19
smcginniseharney: Would be nice to have ceph passing again. Since apparently everyone in the user survey uses it.16:20
* smcginnis would really, really love to see the NFS job passing again too16:20
eharneysmcginnis: we're reaching out to find some folks on the tempest side now -- we have a regular problem of tempest landing changes which break the Ceph job16:20
hemnapatrickeast, the CI projects aren't being maintained?16:20
eharneysmcginnis: and we need to find a way to address it in that project16:21
*** mickeys has joined #openstack-meeting16:21
smcginniseharney: +116:21
patrickeasthemna: the one for like jenkins jenkins is, but not the like 3rd party ci portion of it16:21
smcginniseharney: Seems to be happening more and more.16:21
hemnahuh16:21
hemnahow are those tempest patches landing in the first place then?16:21
patrickeasthemna: like these directions would 100% not work https://github.com/openstack-infra/puppet-openstackci/blob/master/doc/source/third_party_ci.rst16:21
jungleboyjeharney:  What is broken now?16:21
eharneyhemna: Ceph job on tempest is non-voting and it gets ignored.16:21
smcginnispatrickeast: Aren't there still regular weekly meetings for third party CI?16:21
hemna:(16:21
patrickeastsmcginnis: not sure, i haven't been involved with the 3rd party ci stuff much the last few months :(16:21
hemnaeharney, that seems like a major problem since ceph is the most widely used backend.16:22
jungleboyjsmcginnis:  Yes, there is still a 3rd Party CI group that meets.16:22
* smcginnis is just going to casually drop this right here: https://github.com/stmcginnis/openstack-ci16:22
e0neI would like to have ceph job voting once it's fixed16:22
eharneymy current hope is to turn off broken tests and try to get Ceph back to voting status in Cinder, Nova, Tempest, etc, so this stops happening16:22
eharneyhemna: right16:22
hemnasadness16:22
patrickeastsmcginnis: yea thats probably a better option at this point16:22
eharneycurrently things break quicker than they get fixed16:22
smcginniseharney: +116:22
e0neeharney: it's a good plan!16:23
hemna@!r16:23
pewphemna (ノಠ益ಠ)ノ彡┻━┻16:23
jungleboyjeharney:  +116:23
SwansonOut of your mind to use infra's stuff. Yours works great (still).16:23
smcginnisUh uh, pewpbot has gotten angry again.16:23
smcginnisSwanson: ;)16:23
jungleboyjNothing like 3rd Party CI to extend a meeting.16:24
*** lpetrut has quit IRC16:24
smcginnisjungleboyj: No kidding.16:24
hemnajungleboyj, we can go back and rathole on removing replication.....16:24
* jungleboyj shuts up16:25
smcginnishemna: I guess, since we have time - I've been asking folks at ops meetups and things, and have yet to find anyone that uses or wants replication. :/16:25
* diablo_rojo_phon imagines a cinder block puking cheesecake16:25
hemnanot surprising really16:25
smcginnisAt least via cinder16:25
*** mickeys has quit IRC16:25
smcginnisdiablo_rojo_phon: hah!16:25
Swansonsmcginnis, Exactly! v3, pull it!16:25
_alastor_On the subject of 3rd-party CI, I've recently written a backup driver, do we require CI or anything beyond unit tests?16:25
*** jbernard has joined #openstack-meeting16:25
patrickeastsmcginnis: i've got one that is interested... the biggest problem is all the "big" deployments are all like on kilo16:25
patrickeastso they don't have it as a feature yet16:26
smcginnisI think karbor had talked about using it at one point, but IIRC there was some technical hurdle to doing that.16:26
e0ne_alastor_: not yet. we not agreed about CI for backup drivers yet16:26
hemnadoes the ceph driver support replication (or does that even make sense?) ?16:26
_alastor_e0ne: Thanks.  At least it makes my life easy for now :)16:26
Swansonpatrickeast, do they know we only cover meteor strike of the primary?16:26
eharneyhemna: it does16:26
hemnaif it doesn't, that might be why nobody is asking for it/using it16:26
smcginnispatrickeast: Interested in it being an official Cindner API? Or do they just have a need that could easily be addressed by extra specs?16:26
patrickeastSwanson: no, thats the problem : /16:26
hemnahuh, I stand corrected then.  dang16:26
*** trinaths has left #openstack-meeting16:27
patrickeastsmcginnis: good point, i suspect they wouldn't really care with the right marketing pitch16:27
xyang2smcginnis: a customer asked me about after our presentation in Boston.  they want to be able to protect workloads.  so group replication would be handy for that16:27
*** diablo_rojo has quit IRC16:28
smcginnisxyang2: That could be more useful than what we have now.16:28
* lbragstad sneaks in late16:28
SwansonI think we are barely 1/4 a$$ed on DR with this stuff and it is hard to explain all the limitations.16:29
smcginnis_alastor_: We had wanted to have backup driver CI, but last I looked there's only like two backup tempest tests, so it wasn't that interesting.16:29
*** lhx___ has joined #openstack-meeting16:29
smcginnislbragstad: I suppose you want to talk about policy, huh? :)16:29
hemnaSwanson, yah I believe we will always be chasing a ghost with replication and not provide something that's usable for real world scenarios.16:29
*** reedip_ has quit IRC16:30
lbragstadsmcginnis: only if there is a few minutes in open discussion :)16:30
*** caboucha has joined #openstack-meeting16:30
smcginnislbragstad: We've just been kind of rambling for the last several minutes, so sure.16:30
lbragstads/is/are/16:30
mdovgallbragstad, we have at least 30)16:30
e0nesmcginnis, _alastor_: we covered all backup APIs via tempest since the last conversation, AFAIK16:30
lbragstadsounds like i get to ramble!16:30
smcginnise0ne: Oh good16:31
*** lhx__ has quit IRC16:31
e0nesmcginnis: I need to check if all patches were merged to tempest16:31
lbragstadso - quick update on the policy efforts16:33
lbragstadi've attempted to document the current state of things and how we can make them better16:33
lbragstadmy goal was to generate discussions that result in different solutions to the problems at hand16:34
lbragstad(which i think has happened)16:34
*** tesseract has quit IRC16:34
e0nesmcginnis: https://github.com/openstack/cinder/blob/master/cinder/tests/tempest/api/volume/test_volume_backup.py16:34
lbragstadit looks like we're getting close to an optimal solution16:34
smcginnislbragstad: Great! I'm hoping to pick up my policy-in-code spec for queens.16:35
lbragstadin the interest of cross-project open-ness, it'd be awesome to get some feedback from the cinder folks on the approach16:35
e0nesmcginnis: and there are some tests in a tempest repo16:35
lbragstadsmcginnis: ++ sweet!16:35
lbragstad#link https://review.openstack.org/#/c/460344/ attempts to document where we are with policy today16:35
smcginnise0ne: Cool, thanks. Still not aton, but it's not a lot to cover I guess.16:36
lbragstad#link https://review.openstack.org/#/c/462733/ is an attempt to generate discussion around improving security with policy16:36
lbragstad#link https://review.openstack.org/#/c/464763/ is a specification for global roles16:36
smcginnislbragstad: Nice!16:36
lbragstad^ that last one will eventually impact cinder to some extent16:36
*** tobberydberg has joined #openstack-meeting16:36
*** jkilpatr has quit IRC16:36
lbragstadi've tried to highlight how projects will be impacted through examples in each of those documents16:37
lbragstadif you have specific questions though, i'd be happy to field them here16:37
*** rossella__ has quit IRC16:38
smcginnislbragstad: Cool, I'll have to read through those to see what kind of questions come up.16:38
smcginnislbragstad: The policy meeting overlaps with this one, right?16:38
lbragstadsmcginnis: yes, unfortunately16:38
jungleboyjlbragstad:  Thanks for putting that all together.16:38
lbragstadwe ended early today so i was able to swing by16:39
lbragstadjungleboyj: o/16:39
lbragstadjungleboyj: anytime16:39
smcginnislbragstad: Maybe one of these times where we have a short agenda we can get it on the list to discuss some more.16:39
lbragstadsince policy is scattered across all the projects - my goal with those first two was to level set to try and get everyone on the same page16:39
smcginnislbragstad: Good goal, IMO.16:40
lbragstadsmcginnis: yeah - that would be good idea16:40
lbragstadi'm hoping the work we have staged for queens and rocky will help projects achieve capability APIs16:40
*** jkilpatr has joined #openstack-meeting16:40
lbragstadin a way that makes sense16:41
lbragstadi thought i remember cinder having an interest int hat16:41
lbragstadin that*16:41
*** tobberydberg has quit IRC16:41
smcginnisYep, definitely16:41
lbragstadawesome16:41
*** Sukhdev has quit IRC16:42
smcginnisOK, I'll try to follow up on those. Anyone have anything else to discuss today?16:42
lbragstadsmcginnis: awesome - thanks for the time!16:42
smcginnislbragstad: Thanks for working on that. Glad to see someone pushing it forward.16:42
lbragstadabsolutely - ping me anytime if you, or anyone else, has questions16:43
smcginnisThanks!16:43
smcginnisOK, I guess we're done for today. Thank you everyone.16:43
jungleboyjThanks!16:43
smcginnis#endmeeting16:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:43
openstackMeeting ended Wed Jun  7 16:43:58 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2017/cinder.2017-06-07-16.00.html16:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2017/cinder.2017-06-07-16.00.txt16:44
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2017/cinder.2017-06-07-16.00.log.html16:44
tommylikehuthanks16:44
diablo_rojo_phonThank you!16:44
e0nesee you next week16:44
*** ricolin has quit IRC16:46
*** xyang2 has quit IRC16:47
*** sshank has quit IRC16:47
*** jbernard has left #openstack-meeting16:48
*** sshank has joined #openstack-meeting16:49
*** julim has joined #openstack-meeting16:49
*** Swami has joined #openstack-meeting16:50
*** salv-orlando has quit IRC16:51
*** julim has quit IRC16:52
*** lhx___ has quit IRC16:53
*** rossella__ has joined #openstack-meeting16:55
*** unicell1 has quit IRC16:55
*** pewp has quit IRC16:56
*** ltomasbo is now known as ltomasbo|away16:56
*** pewp has joined #openstack-meeting16:56
*** pewp has quit IRC16:57
*** jsuchome has left #openstack-meeting16:57
*** e0ne has quit IRC16:57
*** tobberydberg has joined #openstack-meeting16:57
*** pewp has joined #openstack-meeting16:59
*** mabderrahim has quit IRC16:59
*** tobberydberg has quit IRC17:02
*** bastafidli has quit IRC17:02
*** pnavarro has quit IRC17:04
*** ralonsoh has quit IRC17:06
*** yamamoto has joined #openstack-meeting17:06
*** julim has joined #openstack-meeting17:08
*** bastafidli has joined #openstack-meeting17:09
*** yamamoto has quit IRC17:11
*** pewp has quit IRC17:11
*** pewp has joined #openstack-meeting17:12
*** pewp has quit IRC17:13
*** pewp has joined #openstack-meeting17:13
*** salv-orlando has joined #openstack-meeting17:14
*** pewp has quit IRC17:17
*** pnavarro has joined #openstack-meeting17:17
*** pewp has joined #openstack-meeting17:17
*** diablo_rojo has joined #openstack-meeting17:19
*** unicell has joined #openstack-meeting17:19
*** Rockyg has quit IRC17:20
*** annabelleB has quit IRC17:24
*** pewp has quit IRC17:28
*** pewp has joined #openstack-meeting17:28
*** pewp has quit IRC17:29
*** pewp has joined #openstack-meeting17:29
*** rcernin has joined #openstack-meeting17:31
*** pewp has quit IRC17:33
*** pewp has joined #openstack-meeting17:33
*** markstur has quit IRC17:35
*** pewp has quit IRC17:36
*** pewp has joined #openstack-meeting17:36
*** jamesdenton has joined #openstack-meeting17:37
*** cloudrancher has quit IRC17:38
*** pewp has quit IRC17:39
*** cloudrancher has joined #openstack-meeting17:39
*** e0ne has joined #openstack-meeting17:39
*** pewp has joined #openstack-meeting17:39
*** rossella__ has quit IRC17:41
*** pewp has quit IRC17:42
*** pewp has joined #openstack-meeting17:42
*** annabelleB has joined #openstack-meeting17:46
*** pewp has quit IRC17:50
*** pewp has joined #openstack-meeting17:51
*** pewp has quit IRC17:53
*** pewp has joined #openstack-meeting17:53
*** jamesmcarthur has quit IRC17:56
*** mlakat has joined #openstack-meeting17:57
*** julim has quit IRC17:57
*** julim has joined #openstack-meeting17:58
*** julim has quit IRC17:58
*** TxGirlGeek has quit IRC17:59
bh526r#startmeeting gluon18:00
openstackMeeting started Wed Jun  7 18:00:11 2017 UTC and is due to finish in 60 minutes.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
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
bh526r#info Bin Hu18:00
*** pewp has quit IRC18:01
*** e0ne has quit IRC18:02
jinliHi18:02
jinli#info JinLi18:02
*** electrofelix has quit IRC18:02
*** pewp has joined #openstack-meeting18:02
bh526rHi Jin18:02
bh526rLooks like only you and I18:02
jinli:)18:03
bh526rWe can do it quickly :)18:03
jinlisure18:03
bh526r#topic Admin Update18:03
*** openstack changes topic to "Admin Update (Meeting topic: gluon)"18:03
bh526r#info No update18:03
*** pewp has quit IRC18:03
bh526r#topic Pike Release Tasks and Status18:03
*** openstack changes topic to "Pike Release Tasks and Status (Meeting topic: gluon)"18:03
*** pewp has joined #openstack-meeting18:03
bh526r#info Two patches were approved and merged since last week:18:04
*** TxGirlGeek has joined #openstack-meeting18:04
*** pewp has quit IRC18:04
bh526r#link https://review.openstack.org/#/c/459894/ Gluon and Proton Version Management18:04
bh526r#link https://review.openstack.org/#/c/469369/ Fix doc gate failure18:05
*** pewp has joined #openstack-meeting18:05
bh526r#info Current oustanding patch is Moving hardcoded constants to config file18:05
bh526r#link https://review.openstack.org/#/c/455854/18:06
*** unicell has quit IRC18:06
*** pewp has quit IRC18:06
*** sgrasley1 has quit IRC18:06
*** pewp has joined #openstack-meeting18:06
bh526r#info Jin has consolidated config options from gluon/common/paths.py and gluon/db/sqlalchemy/models.py into gluon/cmd/config.py18:07
*** TxGirlGeek has quit IRC18:08
*** unicell has joined #openstack-meeting18:08
*** xyang1 has joined #openstack-meeting18:08
*** TxGirlGeek has joined #openstack-meeting18:09
bh526r#info Jin is working on the update of proton.conf.sample18:09
bh526r#info a new patchset is expected for review18:10
*** jamesdenton has quit IRC18:11
*** pvaneck has joined #openstack-meeting18:11
bh526r#info regarding Replaces uuid.uuid4 with uuidutils.generate_uuid()18:11
*** jamesmcarthur has joined #openstack-meeting18:11
bh526r#link https://review.openstack.org/#/c/453519/18:11
bh526r#info The author hasn't responded to review comments for 2 months, which needs to fix the error after "import uuid as UUID" is commented18:13
*** jamesmcarthur has quit IRC18:13
bh526r#info We will wait for another 2 weeks. If author still won't respond, we may consider to abandon18:13
bh526r#info Ian has responded to patch Remove elements from core plugin that are simply pass-through18:14
*** TxGirlGeek has quit IRC18:14
bh526r#link https://review.openstack.org/#/c/430446/18:14
bh526r#info waiting for further review and comment18:15
*** jamesmcarthur has joined #openstack-meeting18:15
bh526r#info (WIP) Devstack plugin is still a work in progress, and not ready for review yet18:15
*** jamesmcarthur has quit IRC18:15
bh526r#link https://review.openstack.org/#/c/404069/18:15
*** jamesmcarthur has joined #openstack-meeting18:16
bh526ranything else from you, Jin?18:16
*** jamesmcarthur has quit IRC18:16
jinliyes18:16
*** jamesmcarthur has joined #openstack-meeting18:16
*** TxGirlGeek has joined #openstack-meeting18:16
*** jamesmcarthur has quit IRC18:17
jinlirobert and the others are going to the OPVFN, so we won't do f2f meeting next week?18:17
*** jamesmcarthur has joined #openstack-meeting18:17
bh526rWe will, if Ian's proposal is ready.18:17
*** jamesmcarthur has quit IRC18:18
*** jamesmcarthur has joined #openstack-meeting18:18
jinliok18:18
*** TxGirlGeek has quit IRC18:18
jinlithanks18:18
*** jamesmcarthur has quit IRC18:18
jinlithat's all I have18:18
bh526rIt all depends on Neutron experts' availability, i.e. Ian and Sukhdev, because their availablity and attendance are the most important to move forward.18:18
*** jamesmcarthur has joined #openstack-meeting18:19
jinliok18:19
*** jamesmcarthur has quit IRC18:19
bh526rI will let you know if they confirm their availability - whenever.18:19
jinlisure18:19
jinlithank18:19
jinliyou18:19
*** e0ne has joined #openstack-meeting18:19
bh526rI will adjust my schedule for them18:19
*** jamesmcarthur has joined #openstack-meeting18:19
bh526rIf you plan to attend, I will let you know too18:20
*** TxGirlGeek has joined #openstack-meeting18:20
*** jamesmcarthur has quit IRC18:20
*** jamesmcarthur has joined #openstack-meeting18:20
jinliyes, please let me know18:20
*** salv-orlando has quit IRC18:21
*** jamesmcarthur has quit IRC18:21
*** jamesmcarthur has joined #openstack-meeting18:21
bh526rAmong the group, I think only Robert goes to OPNFV next week. I won't go. I will make myself available for Ian and Sukhdev :)18:21
*** TxGirlGeek has quit IRC18:21
*** pewp has quit IRC18:21
*** salv-orlando has joined #openstack-meeting18:21
*** jamesmcarthur has quit IRC18:21
*** pewp has joined #openstack-meeting18:22
*** TxGirlGeek has joined #openstack-meeting18:22
bh526ranything else?18:22
jinliI am good18:22
bh526rgreat. That's all for today. Thank you18:22
*** jamesmcarthur has joined #openstack-meeting18:23
bh526r#info Meeting adjourned18:23
bh526rBye Jin18:23
bh526r#endmeeting18:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:23
openstackMeeting ended Wed Jun  7 18:23:24 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gluon/2017/gluon.2017-06-07-18.00.html18:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gluon/2017/gluon.2017-06-07-18.00.txt18:23
openstackLog:            http://eavesdrop.openstack.org/meetings/gluon/2017/gluon.2017-06-07-18.00.log.html18:23
*** jamesmcarthur has quit IRC18:23
*** jamesmcarthur has joined #openstack-meeting18:24
*** TxGirlGeek has quit IRC18:24
*** pewp has quit IRC18:24
*** jamesmcarthur has quit IRC18:25
*** pewp has joined #openstack-meeting18:25
*** jamesmcarthur has joined #openstack-meeting18:25
*** julim has joined #openstack-meeting18:25
*** salv-orlando has quit IRC18:25
*** jamesmcarthur has quit IRC18:25
*** mickeys_ has joined #openstack-meeting18:26
*** jamesmcarthur has joined #openstack-meeting18:26
*** jamesmcarthur has quit IRC18:26
*** jamesmcarthur has joined #openstack-meeting18:27
*** jamesmcarthur has quit IRC18:27
*** TxGirlGeek has joined #openstack-meeting18:28
*** jamesmcarthur has joined #openstack-meeting18:28
*** jamesmcarthur has quit IRC18:28
*** pchavva has quit IRC18:29
*** jamesmcarthur has joined #openstack-meeting18:29
*** jamesmcarthur has quit IRC18:29
*** TxGirlGeek has quit IRC18:29
*** jamesmcarthur has joined #openstack-meeting18:30
*** Apoorva_ has joined #openstack-meeting18:31
*** jamesmcarthur has quit IRC18:31
*** julim has quit IRC18:31
*** jamesmcarthur has joined #openstack-meeting18:31
*** hieulq_ has quit IRC18:31
*** jamesmcarthur has quit IRC18:32
*** TxGirlGeek has joined #openstack-meeting18:32
*** pchavva has joined #openstack-meeting18:33
*** jamesmcarthur has joined #openstack-meeting18:33
*** jamesmcarthur has quit IRC18:33
*** jamesmcarthur has joined #openstack-meeting18:34
*** julim has joined #openstack-meeting18:34
*** Apoorva has quit IRC18:34
*** TxGirlGeek has quit IRC18:34
*** jamesmcarthur has quit IRC18:34
*** jamesmcarthur has joined #openstack-meeting18:35
*** jamesmcarthur has quit IRC18:36
*** jamesmcarthur has joined #openstack-meeting18:36
*** jamesmcarthur has quit IRC18:36
*** TxGirlGeek has joined #openstack-meeting18:36
*** Sukhdev has joined #openstack-meeting18:37
*** jamesmcarthur has joined #openstack-meeting18:37
*** jamesmcarthur has quit IRC18:38
*** jamesmcarthur has joined #openstack-meeting18:38
*** ayoung has quit IRC18:43
*** jamesmcarthur has quit IRC18:43
*** sshank has quit IRC18:45
*** Swami has quit IRC18:46
*** Hosam has quit IRC18:49
*** Hosam has joined #openstack-meeting18:49
*** bastafidli has quit IRC18:52
*** jamesmcarthur has joined #openstack-meeting18:53
*** Hosam has quit IRC18:54
*** julim has quit IRC18:55
*** pewp has quit IRC18:56
zara_the_lemur__anybody about for the illustrious *storyboard meeting*?18:59
SotKo/19:00
zara_the_lemur__warning: it will be short!19:00
zara_the_lemur__wonderful!19:00
zara_the_lemur__#startmeeting storyboard19:00
openstackMeeting started Wed Jun  7 19:00:10 2017 UTC and is due to finish in 60 minutes.  The chair is zara_the_lemur__. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: storyboard)"19:00
openstackThe meeting name has been set to 'storyboard'19:00
zara_the_lemur__#topic announcements19:00
*** openstack changes topic to "announcements (Meeting topic: storyboard)"19:00
zara_the_lemur__NOTHING TO ANNOUNCE EXCEPT THAT WE ARE HAVING A VERY SHORT MEETING TODAY19:00
fungiwoo!19:00
zara_the_lemur__#info this meeting will go straight to open discussion19:00
zara_the_lemur__#topic open discussion19:00
*** openstack changes topic to "open discussion (Meeting topic: storyboard)"19:00
zara_the_lemur__okay if anyone wants to say stuff, go for it19:00
zara_the_lemur__note your inprogress work, etc19:01
*** bastafidli has joined #openstack-meeting19:01
zara_the_lemur__have a ball19:01
diablo_rojoParty time!19:01
zara_the_lemur__:D19:01
fungi#link http://specs.openstack.org/openstack-infra/infra-specs/ OpenStack Project Infrastructure Design Specifications19:01
fungii'm trying to get the infra specs tidied19:01
diablo_rojohttps://review.openstack.org/#/c/471859/19:01
diablo_rojoI did my part ^^19:01
fungidiablo_rojo: mind adding yourself as the phase 1 assignee in the task tracker spec there and removing it from the help wanted section of the index?19:02
diablo_rojofungi,  did I not do it right? I thought that is what I did19:02
*** annabelleB has quit IRC19:02
fungidiablo_rojo: oh! i probably just haven't seen the change yet19:03
fungizara_the_lemur__: SotK: diablo_rojo: i'm wondering about some of the other storyboard specs we have listed there which might already be implemented or have become out of scope and should be abandoned19:03
fungifor example, we have a spec for adding worklists and boards19:03
zara_the_lemur__ah, yes, haha, I think SotK wrote that a couple of years ago19:04
fungii know we already have worklists and boards at this point19:04
fungiso probably already implemented?19:04
SotKI think everything in that spec is now implemented, I'll check later and move it into the place for done specs if so19:04
fungiSotK: that would be a huge help!19:04
*** adisky__ has quit IRC19:04
fungithere are several unassigned ones in the help wanted section too (integration tests, story tags, subscriptions and events, branches)19:05
zara_the_lemur__as for the others... I think Story Tags is partly implemented, and we have some stuff for Subscriptions and Events but I don't think I've ever looked at the spec for that19:05
zara_the_lemur__(since both spec + functionality were before my time)19:05
fungidiablo_rojo: aha, i see the link you added above is the thing i was asking for... thanks!19:05
diablo_rojofungi, no problem :)19:05
fungizara_the_lemur__: cool, any info you come up with will be appreciated. mostly just trying to clear out the cobwebs where we can19:06
SotKiirc subscriptions and events is the old spec for a proper events stream and the ability for folk to subscribe to said stream19:06
SotKI'll check on that later too19:06
zara_the_lemur__I think the branches stuff is on hiatus indefinitely19:07
fungisaying "this spec is for something completely different than what we ended up with" is fine too. i don't mind updating the spec before moving it into the implemented section, or just abandoning if we went a completely different direction19:07
zara_the_lemur__(the spec says : "Implementation details should be left to the person that would do the implementation work. What follows is just a suggestion." )19:07
zara_the_lemur__(and nobody has focused on doing that work yet)19:07
zara_the_lemur__(so aiui details tbc)19:07
fungialso fine to leave things which are not getting attention in the help wanted section as long as needed19:08
*** yamamoto has joined #openstack-meeting19:08
zara_the_lemur__cool. :) (at a skim, I think the subscriptions stuff has been at least partially implemented since the other spec was written, since there's stuff about 'install rabbitmq on the storyboard server')19:09
fungii just wanted to do a better job of tracking what work was going on and knowing where to point people for specs that they can pick up and drive too19:09
zara_the_lemur__np19:09
*** markstur has joined #openstack-meeting19:09
fungithat's all i had19:09
zara_the_lemur__we should try to get better at making specs really; there's a lot of stuff we just decide on irc.19:10
*** tinwood has quit IRC19:10
fungiwell, i don't mind specless development as long as there's documentation to point people at19:10
*** thorst_afk has quit IRC19:11
fungibut specs can be useful if you're collaborating and need someone else to be able to easily pick up where you leave off and still know what your vision was for a feature19:11
*** yamamoto has quit IRC19:12
*** tinwood has joined #openstack-meeting19:13
zara_the_lemur__yeah, storyboard itself can work okay for that, though things are harder to *find* there than in specs since there are more stories (I find it okay for things if I'm around to find the link, but people tend not to stumble across stories without a direct link)19:13
*** markstur has quit IRC19:14
*** julim has joined #openstack-meeting19:15
*** thorst_afk has joined #openstack-meeting19:15
fungioh, watcher are discussing in their meeting (today?) whether to migrate to sb19:16
fungisaw that on the ml a little while ago19:17
fungi#link http://lists.openstack.org/pipermail/openstack-dev/2017-June/117963.html watcher migration to storyboard19:17
*** rcernin has quit IRC19:17
diablo_rojoYep I emailed them again :)19:17
diablo_rojoThem, Tricircle, and Octavia19:17
fungicool, and thanks19:18
diablo_rojoNo problem.19:18
diablo_rojoTricircle was saying that sb isnt intuitive and that they would like to use soemthing else..Haven't responded to that email yet.19:18
zara_the_lemur__heh19:19
*** cdub has quit IRC19:19
*** thorst_afk has quit IRC19:20
*** mlakat has quit IRC19:21
diablo_rojoYeah crafting an email to respond today.19:21
diablo_rojoIn their meeting last night they chatted about it a bit and are looking at the links I sent them19:22
diablo_rojohopefully once they read the blog posts and play around a bit, things will get better.19:22
zara_the_lemur__hopefully, and hey, if there are specific things they find confusing, there might be scope for someone to patch it19:24
diablo_rojoAlso true. I can mention that as well.19:25
*** salv-orlando has joined #openstack-meeting19:26
fungithat reminds me i still want to play around with maintaining a second rethemed and simplified webclient in parallel as a bug reporting interface19:26
fungidepending on what they think is unintuitive that may be what they're looking for19:27
zara_the_lemur__yeahhh, I'm also very curious to see what people make of that19:27
*** annabelleB has joined #openstack-meeting19:27
fungiso for advanced task tracking use the main webclient interface, and for just submitting defects here's a url projects can include in their readme files which walks users through it using terminology they're used to/expecting19:28
fungiwe'll see how long it takes me to get around to working on that19:29
zara_the_lemur__hahaha19:29
zara_the_lemur__yeah part of me wants to go 'it should be simple enough so I'll try to take a look'19:29
*** thorst_afk has joined #openstack-meeting19:29
zara_the_lemur__but last week I meant to do a ton of reviews19:29
zara_the_lemur__and did one review19:29
zara_the_lemur__so I'm pacing myself.19:29
*** sshank has joined #openstack-meeting19:30
fungiright, i too have had to learn to stop volunteering for things i'll never get around to19:30
fungiso i can find time to do the rest19:30
*** baoli_ has joined #openstack-meeting19:31
diablo_rojozara_the_lemur__, one is better than none :)19:31
zara_the_lemur__:) this week I'll aim for two19:32
zara_the_lemur__okay, any more discussion or shall I end this meeting now?19:33
funginothing else on my end!19:33
*** baoli has quit IRC19:33
*** annabelleB has quit IRC19:35
zara_the_lemur__great! :)19:35
zara_the_lemur__#endmeeting19:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:35
openstackMeeting ended Wed Jun  7 19:35:24 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2017/storyboard.2017-06-07-19.00.html19:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2017/storyboard.2017-06-07-19.00.txt19:35
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2017/storyboard.2017-06-07-19.00.log.html19:35
zara_the_lemur__thanks, all :)19:35
fungithanks zara_the_lemur__!19:35
diablo_rojoThank you zara_the_lemur__ !19:35
*** rcernin has joined #openstack-meeting19:36
*** georgk has joined #openstack-meeting19:36
*** slaweq has joined #openstack-meeting19:40
*** slaweq has quit IRC19:44
*** slaweq has joined #openstack-meeting19:45
*** slaweq has quit IRC19:50
*** slaweq has joined #openstack-meeting19:51
*** pewp has joined #openstack-meeting19:52
*** annabelleB has joined #openstack-meeting19:54
*** pewp has quit IRC19:56
*** pewp has joined #openstack-meeting19:56
*** annabelleB has quit IRC19:59
*** slaweq has quit IRC20:00
*** slaweq has joined #openstack-meeting20:01
*** Sukhdev has quit IRC20:02
*** slaweq has quit IRC20:05
*** rbowen has quit IRC20:06
*** rbowen has joined #openstack-meeting20:06
*** annabelleB has joined #openstack-meeting20:07
*** julim has quit IRC20:08
*** tobberydberg has joined #openstack-meeting20:10
*** jamesmcarthur has quit IRC20:11
*** jamesmcarthur has joined #openstack-meeting20:13
*** jprovazn has quit IRC20:13
*** tobberydberg has quit IRC20:15
*** armstrong has joined #openstack-meeting20:16
*** sshank has quit IRC20:18
*** sgrasley1 has joined #openstack-meeting20:19
*** e0ne_ has joined #openstack-meeting20:19
*** marst_ has joined #openstack-meeting20:20
*** Hosam has joined #openstack-meeting20:20
*** e0ne has quit IRC20:22
*** markstur has joined #openstack-meeting20:22
*** marst has quit IRC20:23
*** annabelleB has quit IRC20:27
*** pnavarro has quit IRC20:39
*** annabelleB has joined #openstack-meeting20:40
*** annabelleB has quit IRC20:40
*** e0ne has joined #openstack-meeting20:40
*** e0ne has quit IRC20:42
*** e0ne_ has quit IRC20:42
*** bastafidli has quit IRC20:43
*** salv-orl_ has joined #openstack-meeting20:43
*** e0ne has joined #openstack-meeting20:44
*** sshank has joined #openstack-meeting20:45
*** salv-orlando has quit IRC20:46
*** annabelleB has joined #openstack-meeting20:46
*** ansmith has quit IRC20:46
*** annabelleB has quit IRC20:47
*** sgrasley1 has quit IRC20:47
*** bastafidli has joined #openstack-meeting20:47
*** annabelleB has joined #openstack-meeting20:47
*** pchavva has quit IRC20:51
*** pcaruana has quit IRC20:53
*** pcaruana has joined #openstack-meeting20:53
*** jamesdenton has joined #openstack-meeting20:56
*** acoles has joined #openstack-meeting20:57
*** slaweq has joined #openstack-meeting20:58
*** jrichli has joined #openstack-meeting20:58
*** patchbot has joined #openstack-meeting20:58
*** priteau has quit IRC20:58
*** m_kazuhiro has joined #openstack-meeting20:59
*** rledisez has joined #openstack-meeting20:59
*** kota_ has joined #openstack-meeting20:59
*** timburke has joined #openstack-meeting20:59
notmyname#startmeeting swift21:00
openstackMeeting started Wed Jun  7 21:00:04 2017 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
*** annabelleB has quit IRC21: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:00
mattoliverauo/21:00
timburkeo/21:00
m_kazuhiroo/21:00
jrichlihi21:00
rledisezo/21:00
mathiasbo/21:00
kota_hello21:00
notmynameacoles: tdasilva: clayg: ping21:00
acolesnotmyname: pong21:00
tdasilvahello21:01
claygdon't @ me21:01
notmynamedon't tell me what to do ;-)21:01
notmynamewelcome, everyone21:01
notmynameagenda this week is at ...21:02
notmyname#link https://wiki.openstack.org/wiki/Meetings/Swift21:02
notmynameyou'll see that I reorganized that page quite a bit21:02
notmynameI hope it's easier to read now21:02
notmynamealso, OH MY there's a lot of stuff on it!21:02
tdasilvait is until you add items to the other meeting21:02
*** Apoorva_ has quit IRC21:02
notmynameheh21:02
notmynamereminder that our next 0700 meeting is june 14 (ie before the next 2100 meeting) and acoles will be leading it21:03
*** Apoorva has joined #openstack-meeting21:03
*** joeljwright has joined #openstack-meeting21:03
notmynamelet's see how quickly we can go through some stuff21:04
claygyeah let's go!21:04
clayggo go go !21:04
notmynameoh! I just saw an email on the mailing list from Erin Disney about the next PTG21:04
notmynamehas a registration link and hotel info21:04
*** annabelleB has joined #openstack-meeting21:04
timburkehttp://lists.openstack.org/pipermail/openstack-dev/2017-June/118002.html21:04
notmynameso be sure to read that21:04
notmynametimburke: thanks21:04
claygalready!?21:04
notmyname#link http://lists.openstack.org/pipermail/openstack-dev/2017-June/118002.html21:04
*** julim has joined #openstack-meeting21:04
notmyname#topic follow-up from previous meeting21:05
*** openstack changes topic to "follow-up from previous meeting (Meeting topic: swift)"21:05
notmynameLSOF status21:05
rlediseznothing new here, didn't had time to do the bench, just writing code21:05
notmynamerledisez: you said you'd been swamped with other stuff and haven't been able to make much progress on this yet21:05
notmynameack21:05
notmynameTC goals status21:05
rledisezstill on todolist, hopefuly for next week21:05
*** torgomatic has joined #openstack-meeting21:06
notmynameacoles did a great job with the uwsgi one21:06
claygright on!21:06
notmynamealthough the conversation sortof went in a "but do we really need this?" direction21:06
*** julim has quit IRC21:06
notmynamehowever, it's documented, and as far as I can tell, we're done with that one21:06
notmynamestill no progress on the py3 docs21:07
mattoliverauNice21:07
notmynameok, `mount_check` for containers patch21:07
notmyname#link https://review.openstack.org/#/c/466255/21:07
patchbotpatch 466255 - swift - Make mount_check option usable in containerized en...21:07
notmynamewe discussed it last week. clayg has +2'd it. zaitcev has a +121:07
notmynamehmm... cschwede?21:07
tdasilvai think i signed up to review that, but have not had a chance yet, will review tomorrow21:07
notmynameack21:08
notmynamethanks21:08
notmynameah, yes. you're name is on it in gerrit :-)21:08
*** ayoung has joined #openstack-meeting21:08
notmynameand depricating known-bad EC config21:08
notmyname#link https://review.openstack.org/#/c/468105/21:08
patchbotpatch 468105 - swift - Require that known-bad EC schemes be deprecated21:08
notmynameclayg: you have a comment on it saying someone should send an email to the ops mailing list21:08
notmynameclayg: could that someone be you?21:09
claygnotmyname: yeah you should do that21:09
tdasilvalol21:09
notmyname"someone" ;-)21:09
claygI can barely spell EC21:09
*** armstrong has quit IRC21:09
notmynameok ok. I'll do it21:09
claygwe don't have to send jack - we can just merge it21:09
claygI also don't really know who reads the ops ML?21:09
notmynamewell, that shoudl happen too :-)21:09
tdasilvajack might not want to go21:09
notmyname#action notmyname to send email to ops ML about https://review.openstack.org/#/c/468105/21:10
patchbotpatch 468105 - swift - Require that known-bad EC schemes be deprecated21:10
notmynamewe shouldn't wait for a ML post to land that patch, though21:10
notmynametdasilva: your name is on it in gerrit too. are you planning on reviewing?21:10
claygeither way - I *think* we landed on we want to make proxies not start in at least some conditions - which is pretty ballsy IMHO - maybe it's a great thing - for our product it means a bunch of work before we can safely upgrade to a version of swift with that behavior - i have no idea what it means for other people21:10
notmynameIIRC the "some conditions" were when you had the bad EC policy as the only policy21:11
*** armstrong has joined #openstack-meeting21:11
notmynameotherwise, auto-set the bad config to depricated, right?21:11
claygi'm really pretty sure the code is top shelf (duh, timburke wrote it) - the question is really about what is the process for the canonical openstack never-breaks-compat project when they want to break compat?21:11
notmynameit's not an API compat breakage. it's a "stop slowly deleting data when your have a certain config" change. with a strong signal to move your data to a different policy21:12
claygnotmyname: I guess?  is that what timburke implemented?  that was one suggestion... is it *really* any better to automatically hide a policy and let you continue to ignore the error?  Does it mean any less work for someone that wants to start to consume this version of swift - but *somehow* still doesn't know they have these bad policies and isn't dealing with them?21:12
notmynametimburke: I think that's questions best answered by you21:13
claygnotmyname: data is only corrupted if you have a sufficiently old liberasurecode - which AFAIK isn't really part of the warning21:13
claygyeah timburke why are you doing this?  put your head back in the sand?21:13
timburkeclayg: i like turning over rocks?21:14
claygj/k21:14
clayglol!21:14
notmynamealso, this would be a great place for input from kota_ cschwede acoles mattoliverau tdasilva jrichli (all the cores)21:14
notmynamerledisez: what do you want to happen in this case?21:14
*** askb has joined #openstack-meeting21:15
timburkeso the change as it currently stands is to stop services (all of them!) from starting if you have a known-bad policy that hasn't been deprecated21:15
rledisezi would prefer the process not to start. at least it's obvious something must be changed in config, i can't miss it. if policy is auto-set deprecated, an oeprator might miss it and then, getting called because "i can't create containers anymore"21:15
*** armstrong has quit IRC21:16
claygeasier to cache in staging - i like it21:16
acolesclayg: are you saying that isa_l_rs_vand with parity>5 is ok if you have recent libec?21:16
claygacoles: nope21:16
claygacoles: just that it doesn't corrupt data21:16
timburkejust that we won't still silently corrupt data21:16
*** sdague has quit IRC21:16
*** pcaruana has quit IRC21:16
* acoles confused21:17
claygacoles: it might still 503 - we could also add more code to make it 503 less-ish if you can manage to get enough frags to get yourself out of a bad erase list21:17
acolesOIC, we don't corrupt it noisily, we refuse to decode it?21:17
timburkeyeah21:17
claygacoles: but I like don't start if you have these policies - i just have a to write a bunch of code to make sure it doesn't come to that - and we don't really offer cluster-assisted-policy-migration yet - so if someone gets the "if you upgrade swift you are boned" message - there's no clear path to #winning21:18
claygyou could deprecate it and continue to ignore it i guess?21:18
mattoliverauNot starting services seems like something that would annoy people, but it seems the lesser of 2 evils. I mean we can log, but loosing data if you miss a log entry is kinda scary21:18
* jungleboyj sneaks in late21:19
*** Swami has joined #openstack-meeting21:19
acoleslet's not do this in a release that you also cannot roll back from21:19
*** georgk has quit IRC21:19
*** georgk has joined #openstack-meeting21:19
claygdo we support rollback sometimes!21:19
notmynameacoles: yeah, that's a scary part because we've never really done anything around supporting rollbacks21:19
*** annabelleB has quit IRC21:19
*** e0ne has quit IRC21:19
notmynamealthough most of the time it should work. probably.21:20
kota_iirc, the newer pyeclib/liberasurecode stops to decode on that bad case21:20
acolesno but we have had release where we warn that rollback would be really hard e.g. changing hashes.pkl format21:20
acolesI guess if you never start the new release you're ok21:21
*** eharney has quit IRC21:21
timburkeif you really want to continue with the policy un-deprecated, you could always go in and comment out the raise21:21
claygugh, i'm bored - this sucks - anyone that has these policies is screwed - but what can we do?  Does this patch actually *help* someone?  I will punch you in the face until you check this checkbox - BAM do you like that!? <checks checkbox> - warning: you are still hozed21:21
kota_so operators can deploy the policy but sometimes they will see decode error on reconstructor logs or proxy log on GET requests21:21
kota_note that that is if the operators uses newer version of pyeclib/liberasurecode21:22
clayglet's just ignore this and work on cluster-assisted-policy-migration?21:22
*** dimtruck is now known as zz_dimtruck21:22
*** rbak_ has joined #openstack-meeting21:22
notmynameclayg: right, so it's what mattoliverau said. this one is less bad than ignoring it21:22
*** edmondsw_ has joined #openstack-meeting21:22
claygok cool21:23
*** Apoorva_ has joined #openstack-meeting21:23
acolestimburke: but if you go in, comment out the raise, and find your can read your data, you then feel mad at devs21:23
notmynameI'll send the ML message, and this patch should be reviewed and merged when we like it and operators will be in a better place21:24
*** dpyzhov_ has joined #openstack-meeting21:24
notmynameacoles: if you're editing the code on your own in prod, you're already off the reservation :-)21:24
*** tommylikehu_ has joined #openstack-meeting21:24
*** betherly_ has joined #openstack-meeting21:24
*** sweston_ has joined #openstack-meeting21:24
mattoliverau+121:24
*** cargonza_ has joined #openstack-meeting21:24
acolesnotmyname: wasn't my suggestion21:24
notmyname:-)21:24
notmynameok, let's move on. we've at least got a little bit of a plan for it21:25
timburkeacoles: you'll find you can read your data just by deprecating the policy, too21:25
acolestimburke: not if it is your only policy21:25
*** Sukhdev has joined #openstack-meeting21:25
acolesso, yeah, go make another policy. I know.21:25
tdasilvaso did we agree the current patch is ok?21:25
*** zerick_ has joined #openstack-meeting21:25
claygEVERYTHING IS AWESOME - PAINT IT BLUE!21:25
notmynameit's not a bikeshed argument!21:26
*** hwoarang_ has joined #openstack-meeting21:26
notmynamebut yeah, I haven't heard any other paint colors being proposed ;-)21:26
*** frickler_ has joined #openstack-meeting21:26
* acoles needs to find power cord, bbiab21:26
claygi suggested we still have the nuclear-reactor^Wcluster-assisted-policy-migration that would be a great *solution* to these policies being terrible?21:26
*** rmascena has quit IRC21:27
notmynameyes, that would be awesome. but when? m_kazuhiro's had patches to help with that up for a long time21:27
timburkeso get behind https://review.openstack.org/#/c/173580/ or https://review.openstack.org/#/c/209329/ first?21:27
patchbotpatch 173580 - swift - wip: Cluster assisted Storage Policy Migration21:28
patchbotpatch 209329 - swift - WIP: Changing Policies21:28
mattoliverauclayg: yeah, thats a feature that would make this mute more of a moot point.21:28
notmynamefor the time being (ie until we have the cluster assisted policy migration) we've got timburke's patch to not start unless the bad config is depricated21:29
*** jamesmcarthur has quit IRC21:29
*** mtreinish has quit IRC21:29
*** tommylikehu has quit IRC21:29
*** cargonza has quit IRC21:29
*** betherly has quit IRC21:29
*** dpyzhov has quit IRC21:29
*** sweston has quit IRC21:29
*** torgomatic has quit IRC21:29
*** aloga has quit IRC21:29
*** frickler has quit IRC21:29
*** edmondsw has quit IRC21:29
*** rbak has quit IRC21:29
*** gnarld_ has quit IRC21:29
*** jgriffith has quit IRC21:29
*** Kevin_Zheng has quit IRC21:29
*** tomhambleton_ has quit IRC21:29
*** Apoorva has quit IRC21:29
*** hwoarang has quit IRC21:29
*** zerick has quit IRC21:29
*** dpyzhov_ is now known as dpyzhov21:29
*** betherly_ is now known as betherly21:29
*** sweston_ is now known as sweston21:29
*** jgriffith_ has joined #openstack-meeting21:29
claygwin!21:29
*** tommylikehu_ is now known as tommylikehu21:29
*** cargonza_ is now known as cargonza21:29
*** torgomatic has joined #openstack-meeting21:29
*** egallen has quit IRC21:30
*** jamesmcarthur has joined #openstack-meeting21:30
*** zerick_ is now known as zerick21:30
*** aloga has joined #openstack-meeting21:30
*** mtreinish has joined #openstack-meeting21:30
*** gnarld_ has joined #openstack-meeting21:30
*** slaweq has quit IRC21:30
notmynameok, let's move on21:30
*** JillS has joined #openstack-meeting21:30
*** slaweq has joined #openstack-meeting21:31
notmynamelooking at nicks that just netsplit, I don't actually think anyone but torgomatic was here in this meeting (and he's already rejoined--if he was doing more than lurking)21:31
notmyname#topic discuss: follow-up vs patch overwrite. what's the better pattern?21:31
*** openstack changes topic to "discuss: follow-up vs patch overwrite. what's the better pattern? (Meeting topic: swift)"21:31
notmynamerecently I've noticed us, as a group, doing a lot more of "oh this patch looks good, but..." and proposing a small follow-on patch21:31
*** vipul- has quit IRC21:32
acolesnotmyname: both. if patch can be landed now, follow-up, it it needs revisions anyway, overwrite21:32
notmynamemaybe that's great. maybe it's better to give the original author diffs or push over the current patch set21:32
acolesunless follow up is so trivial, then overwrite and land21:32
mattoliverauso/mute/much21:33
mattoliverauArrg phone autocomplete :p21:33
*** bastafidli has quit IRC21:33
notmynameit's something that seems to be a relatively recent change (at least in frequency), so i wanted to address it and either make sure we're all ok with it or know if people are worried by it (or want something differnt)21:33
notmynameso what are your thoughts?21:33
notmynameacoles: seems reasonable (ie "use your judgement") as long as we don't end up getting tests and docs in the follow-up patches?21:34
acolesnotmyname: agree21:34
notmynamewhat do other people thing?21:34
notmyname*think21:34
*** esberglu has quit IRC21:34
* acoles wonders if notmyname is now going to tell I have just done exactly that?21:34
*** esberglu has joined #openstack-meeting21:35
*** slaweq has quit IRC21:35
mattoliverauYeah what acoles said, but also follow up if it's a change that's building apon the last one but a little out of scope.21:35
mattoliverauIe, Critical bug (stop bleeding) then maybe improve21:36
notmynameheh, so I can see were not likely to get some "this is good" or "this is bad" sort of comment. but i at least wanted to raise it as a way to point it out as a thing that's happening21:36
notmynameso... pay attention! :-)21:36
claygnotmyname: please clarify, you observed -> doing a lot more of "oh this patch looks good, but..." as opposed to give the original author diffs or push over the current patch set21:37
acolesI sometimes feel we could use commit subject line for more useful words than 'follow up for...' and just use a Related-Change tag in the commit msg body21:37
rledisezi also feel "trust your judgement" is the best choice i feel like the follow-up when you start a patch, and the more you dig, the more you want to change things because the new-way-to-do is diffferent than years ago. so splitting things like the bugfixe vs the code improvement (in a follow-up) seems reasonable. also, it helps separate what's everybody agree and what makes debate21:37
notmynameclayg: yes, correct21:37
*** vipul has joined #openstack-meeting21:37
claygof "give the original author diffs" or "push over the current patch set" which do you thin was more common before you observed this change?21:37
jrichliI have seen two different types of "follow-up" patches.  1) something more that can be done after the original merges 2) a suggested change, intended to be rolled into original, then abandoned21:37
*** slaweq has joined #openstack-meeting21:38
notmynameI think previously we waited more for the original author to write something (and occasionally gave a diff) -- at least for frequent contributors.21:38
jungleboyjjrichli:  That second approach sounds dangerous.21:39
acolesnotmyname: but, but... you told us we needed to merge more stuff faster ;)21:39
jungleboyjIn that case it would be better to work with the original author to fix it or push up a new patch.21:39
*** esberglu has quit IRC21:39
claygnotmyname: thanks for clarifying;  ok, I think trying to approve changes and address additional improvements in follow patches is a categorical improvement and something we did on purpose based on community review sessions that you've lead at summits and stuff21:39
notmynameacoles: I don't think the current situation is necessarily bad21:40
jungleboyjPolicy I have always followed is to push up a dependent patch unless it is something really minor that isn't worth waiting for the other person to fix, then push up a new aptch.21:40
notmynameeg https://review.openstack.org/#/c/468011/3 and https://review.openstack.org/#/c/465184/21:40
patchbotpatch 468011 - swift - Update Global EC docs with reference to composite ...21:40
patchbotpatch 465184 - swift - Ring doc cleanups21:40
*** ansmith has joined #openstack-meeting21:40
*** radeks has quit IRC21:41
claygdon't use docs as the example - doc patches are terrible - they're so subjective21:41
timburkehttps://review.openstack.org/#/c/466952/ maybe fell on the other side of that line21:41
patchbotpatch 466952 - swift - Follow-up for per-policy proxy configs (MERGED)21:41
*** sshank has quit IRC21:41
notmynamethey were just easy ones I knew were proposed as follow-on that I had quick access to21:41
timburkethough parts of it were definitely out of scope for the original21:41
claygnotmyname: i know i was just whining21:42
notmynameI think landing more stuff faster is better. and it seems like this pattern has helping in that regard21:42
mattoliveraujrichli's second approach is how we're working through sharding patch. Seems to work as we can break down the large patch and then merge it back in.21:42
*** sshank has joined #openstack-meeting21:42
acolesnotmyname: I'm not sure I see them as follow-up. The ring doc cleanup is standalone, just may been prompted by timburke reviewing another change??21:43
notmynamebut since it is a change, then I want to make sure people are feeling ok with it now that it's been happening for a bit21:43
claygwfm21:43
*** rcernin has quit IRC21:44
notmynamekota_: tdasilva: are you concerned with the current pattern of using minor follow-on patches?21:44
kota_hmm21:44
kota_I'm not feeling so bad on the current follow up use cases right now21:45
notmynamegreat :-)21:45
tdasilvanotmyname: no concern from me. I've noticed different people do different things...hasn't really bothered me21:45
notmynamegreat :-)21:45
*** zz_dimtruck is now known as dimtruck21:45
timburkei definitely find myself more likely to take that second approach -- otherwise i'd worry that by pushing over a patch and +2ing it, the original author may not get a chance to protest before someone else comes along for the +A21:45
notmynameok, if someone *does* have comments, please feel free to say something, publicly or privately21:46
notmynameok, let's move on21:46
notmyname#topic priority items21:46
*** openstack changes topic to "priority items (Meeting topic: swift)"21:46
notmynameTHERE'S SO MUCH STUFF TO DOOOO!!21:46
notmynameok, we're not going to be able to talk about all the stuff on https://wiki.openstack.org/wiki/Meetings/Swift21:46
*** hongbin has quit IRC21:47
notmynameI think I'll take this section and copy it over to the priority reviews page :-)21:47
*** slaweq has quit IRC21:47
notmynamebut I do want to mention a few of the high priority bugs and some small follow-on things21:47
notmynamehttps://bugs.launchpad.net/swift/+bug/156865021:47
openstackLaunchpad bug 1568650 in OpenStack Object Storage (swift) "Connection between client and proxy service does not closes" [High,Confirmed] - Assigned to drax (devesh-gupta)21:47
notmynamerelated to https://bugs.launchpad.net/swift/+bug/157271921:47
openstackLaunchpad bug 1572719 in OpenStack Object Storage (swift) "Client may hold socket open after ChunkWriteTimeout" [High,Confirmed]21:47
*** slaweq has joined #openstack-meeting21:48
notmynamehigh priority bugs, open for a while, no current patches for them21:48
notmynameis there someone who can look in to them this week? if not to write a full patch, at least to outline what needs to be done to help someone who *can* write a patch21:48
*** esberglu has joined #openstack-meeting21:48
claygyeah... stupid connection close bugs... timburke found another one21:48
notmynameyep21:49
notmynametimburke: you seem to be on this topic lately. can you check these?21:49
claygwhoa!  poor timburke :'(21:49
*** cloudrancher has quit IRC21:49
*** yamahata has joined #openstack-meeting21:49
claygi was going to just suggest we move the medium and wait for them to bite us?21:50
*** jamesmcarthur has quit IRC21:50
notmynamemaybe that's the best21:50
timburkei suppose i can try... need to go digging into eventlet anyway...21:50
*** cloudrancher has joined #openstack-meeting21:50
notmynameright, I mean keep these in mind as you're doing the investigation on the new bug you found21:51
notmynamethanks21:51
*** rfolco has quit IRC21:51
notmynameok, next: DB replicators lose metadata21:51
*** hongbin has joined #openstack-meeting21:51
notmynamehttps://review.openstack.org/#/c/302494/21:51
patchbotpatch 302494 - swift - Sync metadata in 'rsync_then_merge' in db_replicator21:51
notmynamehttps://bugs.launchpad.net/swift/+bug/157011821:51
openstackLaunchpad bug 1570118 in OpenStack Object Storage (swift) "Metadata can be missing by account/container replication" [High,In progress] - Assigned to Daisuke Morita (morita-daisuke)21:52
kota_I added +2 already?21:52
notmynamekota_: you did! thanks!21:52
claygi'ma look at that21:52
notmynameclayg: thanks!21:52
claygwerd21:52
notmynameok, we already mentioned the EC docs updates...21:52
notmynamenow https://bugs.launchpad.net/swift/+bug/165232321:53
openstackLaunchpad bug 1652323 in OpenStack Object Storage (swift) "ssync syncs an expired object as a tombstone, probe test_object_expirer fails" [Medium,Confirmed]21:53
kota_timburke: fyi -> https://review.openstack.org/#/c/471613/21:53
patchbotpatch 471613 - swift - Use config_number method instead of node_id + 121:53
*** esberglu has quit IRC21:53
*** thorst_afk has quit IRC21:53
*** dtrainor has quit IRC21:53
kota_related on the db_replicator's probe21:53
timburkekota_: i saw; thanks21:53
*** dtrainor has joined #openstack-meeting21:53
notmynameacoles: on that bug, anything to do right now? it's listed as medium21:53
notmynamethe title mentions the probe tests failing, but the comments indicate something more serious (ssynv failing to replicate data)21:54
notmynamewhich is why I mention it here today21:54
acolesnotmyname: I'm not sure how best to close that one. I discussed it with rledisez this week - do we do a lot of work to be able to reconstruct an expired frag, or just ignore that it is missing ... cos it has expired anyway??21:55
notmynamerledisez: is this something your devs at OVH can help with?21:55
acolesnotmyname: we fixed the probe test with a workaround21:55
notmynameah, ok21:55
*** slaweq has quit IRC21:55
acolesbut we didn;t fix ssync :/21:55
notmynameok, so we need to update tis bug or get a different bug to track21:55
*** slaweq has joined #openstack-meeting21:56
notmynamewhich do you think is best?21:56
rlediseznotmyname: right now no, but i want this fixed, so i might take some time to look into it, but i still don't know what would be the best way21:56
acolesthe recent change rledisez made so we can open an expired diskfile helps, but doesn;t get us everything we need to fix this one21:56
acolesnotmyname: I'll update the bug21:56
notmynameacoles: perfect. thanks21:56
notmynamehttps://review.openstack.org/#/c/439572/21:56
patchbotpatch 439572 - swift - Limit number of revert tombstone SSYNC requests21:56
notmynamefor https://bugs.launchpad.net/swift/+bug/166885721:57
openstackLaunchpad bug 1668857 in OpenStack Object Storage (swift) "EC reconstructor revert tombstone SSYNCs with too many primaries" [Medium,In progress] - Assigned to Mahati Chamarthy (mahati-chamarthy)21:57
acolesany other opinions - missing frag, but expired, can we just leave it missing??21:57
tdasilvaacoles: what's the cons to that?21:57
notmynamekota_: on this patch, youv'e got a +121:57
*** ykatabam has joined #openstack-meeting21:57
acolestdasilva: inconsistent state, for a while21:57
*** edmondsw_ has quit IRC21:58
*** chyka has joined #openstack-meeting21:58
notmynamekota_: will you get a chance to revisit it?21:58
kota_notmyname: yup, i reviewd yesterday again but i'm still on +1 not +2 yet21:58
kota_still want to collect clay's opinion21:58
notmynamekota_: ok. what do you want to see before you get to a +2? what's missing?21:58
notmynameoh, clayg is already +2 ;-)21:58
kota_diff from clay's description with current code21:58
kota_for the number of primary nodes to push the tombstone21:58
claygkota_: is it > 3 and < replicas?  I will +2 it so hard!21:59
kota_i added my thought yesterday so now waiting on the ack. I just was thinking to poke clayg after this meeting21:59
notmynameok21:59
kota_it's on non duplicated case21:59
*** annabelleB has joined #openstack-meeting21:59
kota_to clayg21:59
claygk, we can chat22:00
notmynamekota_: clayg: thank you22:00
*** Julien-zte has quit IRC22:00
notmynameok, we're at time, but please check the other patches linked on the meeting agenda (and i'll move them to the priority reviews page as well)22:00
notmynamethank you, everyone, for your work on swift22:01
notmynameand thanks for coming today!22:01
jungleboyjThanks.22:01
notmyname#endmeeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:01
openstackMeeting ended Wed Jun  7 22:01:17 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2017/swift.2017-06-07-21.00.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2017/swift.2017-06-07-21.00.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2017/swift.2017-06-07-21.00.log.html22:01
*** patchbot has left #openstack-meeting22:01
*** joeljwright has quit IRC22:01
*** timburke has left #openstack-meeting22:01
*** bobh has quit IRC22:02
*** Julien-zte has joined #openstack-meeting22:02
*** mickeys_ has quit IRC22:02
*** Julien-zte has quit IRC22:03
*** jrichli has left #openstack-meeting22:05
*** m_kazuhiro has quit IRC22:05
*** Julien-zte has joined #openstack-meeting22:06
*** Swami has quit IRC22:07
*** rfolco has joined #openstack-meeting22:07
*** aeng has joined #openstack-meeting22:11
*** baoli_ has quit IRC22:12
*** jamesdenton has quit IRC22:13
*** abalutoiu has quit IRC22:14
*** galstrom is now known as galstrom_zzz22:17
*** kaisers has quit IRC22:18
*** pradk has quit IRC22:20
*** pvaneck has quit IRC22:20
*** Sukhdev has quit IRC22:20
*** georgk has quit IRC22:22
*** thorst_afk has joined #openstack-meeting22:28
*** xyang1 has quit IRC22:30
*** thorst_afk has quit IRC22:32
*** kaisers has joined #openstack-meeting22:33
*** jkilpatr has quit IRC22:34
*** salv-orl_ has quit IRC22:37
*** salv-orlando has joined #openstack-meeting22:37
*** ayoung has quit IRC22:40
*** salv-orlando has quit IRC22:41
*** kota_ has left #openstack-meeting22:51
*** annabelleB has quit IRC22:51
*** annabelleB has joined #openstack-meeting22:51
*** marst_ has quit IRC22:52
*** felipemonteiro_ has quit IRC22:52
*** awaugama has quit IRC22:56
*** lbragstad has quit IRC23:00
*** thorst_afk has joined #openstack-meeting23:02
*** mickeys_ has joined #openstack-meeting23:03
*** annabelleB has quit IRC23:05
*** mickeys_ has quit IRC23:07
*** bobh has joined #openstack-meeting23:10
*** yamamoto_ has joined #openstack-meeting23:11
*** openstack has joined #openstack-meeting23:13
*** ChanServ sets mode: +o openstack23:13
*** annabelleB has joined #openstack-meeting23:14
*** rhochmuth has quit IRC23:14
*** yamamoto_ has quit IRC23:16
*** VW_ has joined #openstack-meeting23:16
*** claudiub has quit IRC23:17
*** thorst_afk has quit IRC23:17
*** edmondsw has joined #openstack-meeting23:18
*** VW has quit IRC23:19
*** dane_leblanc has quit IRC23:20
*** tomhambleton_ has joined #openstack-meeting23:21
*** VW_ has quit IRC23:21
*** Kevin_Zheng has joined #openstack-meeting23:21
*** edmondsw has quit IRC23:23
*** annabelleB has quit IRC23:23
*** jaypipes has quit IRC23:30
*** Julien-zte has quit IRC23:32
*** chyka has quit IRC23:35
*** chyka has joined #openstack-meeting23:36
*** Julien-zte has joined #openstack-meeting23:37
*** chyka has quit IRC23:40
*** Julien-zte has quit IRC23:41
*** armstrong has joined #openstack-meeting23:46
*** yamamoto_ has joined #openstack-meeting23:47
*** armstrong has quit IRC23:50
*** sshank has quit IRC23:54
*** ramineni_ has joined #openstack-meeting23:57
*** ekcs has joined #openstack-meeting23:59

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