Wednesday, 2017-07-19

*** Manuel_112 has joined #openstack-meeting00:02
*** aeng has quit IRC00:03
*** Manuel_112 has quit IRC00:05
*** aeng has joined #openstack-meeting00:05
*** esberglu has joined #openstack-meeting00:10
*** gmann has quit IRC00:13
*** baoli has joined #openstack-meeting00:13
*** gmann has joined #openstack-meeting00:13
*** esberglu has quit IRC00:15
*** gcb has joined #openstack-meeting00:15
*** frank_young has joined #openstack-meeting00:15
*** edmondsw has joined #openstack-meeting00:19
*** frank_young has quit IRC00:20
*** dmacpher has quit IRC00:24
*** edmondsw has quit IRC00:24
*** annabelleB has joined #openstack-meeting00:30
*** annabelleB has quit IRC00:33
*** dmacpher has joined #openstack-meeting00:37
*** RongHui11 has joined #openstack-meeting00:38
*** wanghao has joined #openstack-meeting00:45
*** kiennt has joined #openstack-meeting00:49
*** thorst has joined #openstack-meeting00:49
*** thorst has quit IRC00:50
*** dmacpher has quit IRC00:51
*** tovin07_ has joined #openstack-meeting00:52
*** Yipei has joined #openstack-meeting00:55
*** Manuel_112 has joined #openstack-meeting00:56
*** csomerville has quit IRC00:56
*** xuzhuang has joined #openstack-meeting00:57
*** dongfeng has joined #openstack-meeting00:57
*** yinxiulin has joined #openstack-meeting01:00
*** Manuel_112 has quit IRC01:00
*** baoli has quit IRC01:01
*** cody-somerville has joined #openstack-meeting01:03
*** Apoorva_ has quit IRC01:04
*** baoli has joined #openstack-meeting01:04
*** Manuel_112 has joined #openstack-meeting01:04
*** Apoorva has joined #openstack-meeting01:05
*** dmacpher has joined #openstack-meeting01:05
*** joehuang has joined #openstack-meeting01:06
joehuanghello01:06
RongHui11hello01:06
dongfenghi01:06
joehuangjust enter a wrong meeting room01:06
Yipeihi01:06
zhiyuanhi01:06
joehuang#startmeeting tricircle01:07
openstackMeeting started Wed Jul 19 01:07:01 2017 UTC and is due to finish in 60 minutes.  The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot.01:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:07
*** openstack changes topic to " (Meeting topic: tricircle)"01:07
openstackThe meeting name has been set to 'tricircle'01:07
joehuang#topic pike release schedule01:07
*** openstack changes topic to "pike release schedule (Meeting topic: tricircle)"01:07
joehuanghello, the pike release schedule is https://releases.openstack.org/pike/schedule.html01:07
joehuang#info pike release schedule01:08
joehuang#info pike release schedule https://releases.openstack.org/pike/schedule.html01:08
joehuangwe'll have pike-3 on Jul 2801:08
joehuanglet's discuss whether there is challenge for features to land01:09
joehuangone by one?01:09
*** Manuel_112 has quit IRC01:09
dongfengdocumentation for routing pagination is under review. may be land in time01:09
xuzhuangfor job pagination, under modifying after reviews01:11
joehuangok01:12
RongHui11for the QoS, merge the two parts and try to pass the jenkins test01:12
zhiyuanthe smoke test engine has been implemented, may be landed on time. also I have written test for trunk/service function chaining using that engine01:12
*** harlowja has quit IRC01:13
*** zhurong has joined #openstack-meeting01:13
joehuangyes, I saw that many tests not passed for QoS patch01:13
Yipeifor lbaas, already finish lbaas in multiple region, it works across instances residing in one subnet, but fail among instances of different subnets01:13
zhiyuanthough only creation is tested for trunk/service function chaining, it can be improved later01:13
zhiyuanso I mark them as WIP01:13
*** hongbin has joined #openstack-meeting01:14
joehuangok, fine. Smoke test should be in high priority to ensure code is merged with quality01:14
*** ykatabam has quit IRC01:14
*** ykatabam has joined #openstack-meeting01:14
joehuangTo yipei, this is great progress01:14
Yipeineutron_lbaas checks whether the subnet of another region exists, and fail to find it01:14
zhiyuanbecause the subnet is not created in that region?01:15
*** kevzha01 has joined #openstack-meeting01:15
*** hejiawei has joined #openstack-meeting01:16
Yipeito zhiyuan, yes, i try to add an instance of anther region as a member01:16
joehuangI remember that we discussed in the past for subnet in the local Neutron01:18
joehuanghow to deal with the subnet issue if it's not there for LBaaS01:18
zhiyuanyes, I remember that we need to recognize that the get-subnet request is from LB so we redirect the request to central Neutron01:19
joehuang#info for lbaas, already finish lbaas in multiple region, it works across instances residing in one subnet, but fail among instances of different subnets01:19
joehuangRonghui, please make sure the patch pass all test, so that further review can be done01:20
RongHui11got01:20
RongHui11 it01:21
*** bobh has quit IRC01:21
zhiyuanto yipei, need to check the LB code to see how it validates the existence of the subnet so we can figure out how to play the trick01:21
joehuangok, it's better to include the cli for tricircle API in pike01:21
*** Daisy_ has joined #openstack-meeting01:21
joehuangcurl is not friendly01:22
*** mriedem1 has joined #openstack-meeting01:22
Yipeito zhiyuan, got it01:22
*** dmacpher has quit IRC01:23
dongfengadd a link to python tricircleclient at tricircle github directly?01:23
joehuang#info discuss how to validates the existence of the subnet in LBaaS01:23
*** Daisy_ has quit IRC01:23
*** frank_young has joined #openstack-meeting01:23
joehuangto dongfeng, just need to finish the feature tricircle client, it's can be discovered by openstackclient01:23
*** Daisy_ has joined #openstack-meeting01:24
dongfengyes01:24
*** mriedem has quit IRC01:24
dongfengI use openstack --help can find the command for it01:24
dongfengI find some issues in current implementation of job cli. I'm modifying it01:25
*** gouthamr has quit IRC01:25
joehuangok, dongfeng, do you think the cli for job and routing could be ready in two weeks?01:26
dongfengcli for routing already implemented01:26
dongfengit's done by victor01:26
dongfengnow I only need to implement job cli. I think it can be complete01:26
joehuanggreat, so only job, but how to support pagination in cli?01:27
dongfengjob pagination in not implemented in tricircle01:27
dongfengrouting pagination can be added to cli in the future01:28
joehuangok01:28
joehuangdongfeng, could you initiate one discussion in openstack mail-list, how to implement pagination in cli01:31
joehuangif cli will query all pages and display together, the client will be too busy to display information01:32
joehuanghow openstack deal  with cli in pagination with consistent experienec?01:32
dongfengok, no problem01:33
joehuang#action discuss how to implement pagination query in cli, not lead to cli not working01:34
joehuangso I am wondering the usability of CLI if we can not make CLI work well with huge mount of data01:37
joehuangpagination is to divide the burden from the server side01:37
joehuangbut if cli can now work well for pagination(have to show all data in one command), then it's terrible in production01:38
*** Julien-zte has quit IRC01:38
joehuangbut if cli can not work well for pagination(have to show all data in one command), then it's terrible in production01:39
*** Apoorva_ has joined #openstack-meeting01:39
*** Julien-zte has joined #openstack-meeting01:39
joehuangfortunately we support API first, the client side can use curl to query page by page01:40
joehuangHi, Ronghui, do you think QoS can be landed in time for pike-301:41
joehuangthe milestone is Jul 2801:42
*** Apoorva has quit IRC01:42
RongHui11i think there is no problem01:42
*** yamahata has quit IRC01:43
*** iyamahat has quit IRC01:43
*** Apoorva_ has quit IRC01:44
*** Daisy_ has quit IRC01:44
*** fzdarsky_ has joined #openstack-meeting01:44
*** Daisy_ has joined #openstack-meeting01:44
joehuangok, let's try best to review the code. And if you want QoS to land in Pike-3, please update the patch as fast as possible after new review comment arrived, and make sure all test passed before next review01:45
RongHui11ok01:45
*** bobh has joined #openstack-meeting01:45
joehuang#topic open discussion01:46
*** openstack changes topic to "open discussion (Meeting topic: tricircle)"01:46
joehuangany topic to discuss?01:46
zhiyuanno from me01:46
*** aeng has quit IRC01:46
Yipeino from me01:46
RongHui11no01:46
xuzhuangno from me01:47
*** fzdarsky has quit IRC01:48
joehuangok, one more topic01:48
joehuang#topic PTL election01:48
*** openstack changes topic to "PTL election (Meeting topic: tricircle)"01:48
*** Daisy_ has quit IRC01:48
joehuanghello, the PTL election season starts01:48
*** Daisy_ has joined #openstack-meeting01:48
joehuangplease nominate yourself if you want to serve as PTL in Queen cycle01:49
*** yinxiulin has quit IRC01:49
*** phuoc_ has joined #openstack-meeting01:50
*** aeng has joined #openstack-meeting01:50
joehuangthe election process is here : https://governance.openstack.org/election/01:50
joehuang#info PTL nominationJul 31, 2017 23:59 UTCAug 09, 2017 23:45 UTC01:51
joehuang#info PTL electionsAug 09, 2017 23:59 UTCAug 16, 2017 23:45 UTC01:51
*** RongHui11 has quit IRC01:52
joehuangI will be happy to stepping down from PTL after Pike for I have been PTL many cycles, so I  hope you guys can step up for PTL role in Queen01:52
joehuangAny question on PTL election, you can send mail in openstack-dev mail-list01:53
joehuangother topic01:54
joehuang>01:54
joehuangother topic?01:54
dongfengno01:54
Yipeino01:54
xuzhuangno01:54
zhiyuanno01:54
joehuangok, let's end the meeting01:55
joehuang#endmeeting01:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"01:55
openstackMeeting ended Wed Jul 19 01:55:09 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)01:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tricircle/2017/tricircle.2017-07-19-01.07.html01:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tricircle/2017/tricircle.2017-07-19-01.07.txt01:55
openstackLog:            http://eavesdrop.openstack.org/meetings/tricircle/2017/tricircle.2017-07-19-01.07.log.html01:55
joehuangthanks, bye01:55
zhiyuanbye01:55
Yipeibye01:55
dongfengbye.01:55
xuzhuangbye01:55
*** Yipei has quit IRC01:58
*** mriedem1 is now known as mriedem01:59
*** Manuel_112 has joined #openstack-meeting01:59
*** Manuel_112 has quit IRC02:03
*** Manuel_112 has joined #openstack-meeting02:07
*** edmondsw has joined #openstack-meeting02:07
*** Manuel_112 has quit IRC02:10
*** edmondsw has quit IRC02:12
*** caowei has joined #openstack-meeting02:13
*** ricolin has joined #openstack-meeting02:16
*** hejiawei has quit IRC02:16
*** gyee has quit IRC02:17
*** yamamoto has joined #openstack-meeting02:17
*** zengchen has quit IRC02:18
*** joehuang has quit IRC02:20
*** gouthamr has joined #openstack-meeting02:22
*** xuzhuang has quit IRC02:29
*** epico has joined #openstack-meeting02:29
*** dongfeng has quit IRC02:29
*** epico has quit IRC02:37
*** __huzhj has quit IRC02:37
*** yamamoto has quit IRC02:38
*** dmacpher has joined #openstack-meeting02:47
*** jamesmcarthur has joined #openstack-meeting02:47
*** yamamoto has joined #openstack-meeting02:48
*** thorst has joined #openstack-meeting02:51
*** epico has joined #openstack-meeting02:56
*** jamesmcarthur has quit IRC02:56
*** jamesmcarthur has joined #openstack-meeting02:56
*** thorst has quit IRC02:59
*** markvoelker has quit IRC02:59
*** jamesmcarthur has quit IRC03:01
*** Manuel_112 has joined #openstack-meeting03:01
*** mriedem has quit IRC03:02
*** xuzhuang has joined #openstack-meeting03:02
*** rbudden has joined #openstack-meeting03:04
*** Manuel_112 has quit IRC03:06
*** Daisy_ has quit IRC03:09
*** Manuel_112 has joined #openstack-meeting03:10
*** Daisy_ has joined #openstack-meeting03:10
*** bobh has quit IRC03:11
*** Manuel_112 has quit IRC03:13
*** Daisy_ has quit IRC03:14
*** annabelleB has joined #openstack-meeting03:17
*** litao__ has joined #openstack-meeting03:22
*** epico has quit IRC03:26
*** xuzhuang has quit IRC03:31
*** annabelleB has quit IRC03:31
*** hongbin has quit IRC03:36
*** ekcs has joined #openstack-meeting03:47
*** edmondsw has joined #openstack-meeting03:55
*** martial has joined #openstack-meeting03:56
*** hieulq has quit IRC03:57
*** hieulq has joined #openstack-meeting03:57
*** yamamoto has quit IRC03:57
*** links has joined #openstack-meeting03:58
*** yamamoto has joined #openstack-meeting03:59
*** edmondsw has quit IRC04:00
*** Manuel_112 has joined #openstack-meeting04:04
*** yamamoto has quit IRC04:04
*** yamamoto has joined #openstack-meeting04:05
*** Manuel_112 has quit IRC04:07
*** pfallenop has quit IRC04:08
*** dmacpher has quit IRC04:09
*** Dinesh_Bhor has joined #openstack-meeting04:11
*** epico has joined #openstack-meeting04:11
*** andreas-f has joined #openstack-meeting04:11
*** Manuel_112 has joined #openstack-meeting04:12
*** gouthamr has quit IRC04:14
*** yamamoto has quit IRC04:14
*** Dinesh_Bhor has quit IRC04:14
*** reedip has quit IRC04:14
*** Dinesh_Bhor has joined #openstack-meeting04:15
*** reedip has joined #openstack-meeting04:15
*** yamamoto has joined #openstack-meeting04:15
*** martial has quit IRC04:17
*** Manuel_112 has quit IRC04:17
*** yamamoto has quit IRC04:21
*** psachin has joined #openstack-meeting04:21
*** dmacpher has joined #openstack-meeting04:22
*** noslzzp_ has quit IRC04:25
*** noslzzp has joined #openstack-meeting04:25
*** frank_young has quit IRC04:26
*** trinaths has joined #openstack-meeting04:26
*** noslzzp has quit IRC04:31
*** harlowja has joined #openstack-meeting04:31
*** janki has joined #openstack-meeting04:33
*** frank_young has joined #openstack-meeting04:36
*** prateek has joined #openstack-meeting04:38
*** xuzhuang has joined #openstack-meeting04:38
*** frank_young has quit IRC04:41
*** Daisy_ has joined #openstack-meeting04:41
*** gouthamr has joined #openstack-meeting04:42
*** yamamoto has joined #openstack-meeting04:44
*** yamahata has joined #openstack-meeting04:46
*** Daisy_ has quit IRC04:46
*** harlowja has quit IRC04:47
*** janki has quit IRC04:50
*** lpetrut__ has joined #openstack-meeting04:51
*** elynn has joined #openstack-meeting04:53
*** apetrich has quit IRC04:54
*** tobberydberg has joined #openstack-meeting04:54
*** xuzhuang has quit IRC04:55
*** zhurong has quit IRC04:55
*** apetrich has joined #openstack-meeting04:56
*** markvoelker has joined #openstack-meeting05:00
*** Daisy_ has joined #openstack-meeting05:00
mrhillsmano/05:01
tobberydbergo/05:01
mrhillsmanany others here for uc meeting?05:02
*** ad_rien_ has joined #openstack-meeting05:02
mrhillsmani will start and others can join i guess :)05:03
*** martial has joined #openstack-meeting05:03
mrhillsman#startmeeting uc05:03
openstackMeeting started Wed Jul 19 05:03:42 2017 UTC and is due to finish in 60 minutes.  The chair is mrhillsman. Information about MeetBot at http://wiki.debian.org/MeetBot.05:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:03
*** openstack changes topic to " (Meeting topic: uc)"05:03
openstackThe meeting name has been set to 'uc'05:03
mrhillsman#topic RollCall05:04
*** openstack changes topic to "RollCall (Meeting topic: uc)"05:04
ad_rien_o/ Hi guys05:04
mrhillsmanhey there ad_rien_05:04
tobberydberghi05:05
*** arnewiebalck_ has joined #openstack-meeting05:05
mrhillsmanhi tobberydberg05:05
*** b1airo has joined #openstack-meeting05:05
b1airoo/05:05
*** Manuel_112 has joined #openstack-meeting05:06
mrhillsmanhey b1airo05:06
mrhillsmananyone else?05:06
mrhillsmanalright, we'll go into the updates05:07
martialwell me, but only for a short little bit longer05:07
*** gouthamr has quit IRC05:07
mrhillsmanok, i'll create a topic for each wg/team to provide an update05:08
ad_rien_I read that the meeting will take place also on a video conf (but I didn't find the link)?05:08
*** Manuel_1_ has joined #openstack-meeting05:08
mrhillsmanyeah, i saw that too, jamemcc initially championed this maybe he had one, i did not see it iether05:08
b1airoI am on mobile so could be a little flakey/slow - apologies in advance05:08
mrhillsman#topic Scientific WG Update05:09
*** openstack changes topic to "Scientific WG Update (Meeting topic: uc)"05:09
mrhillsmansince you have to run martial figured you could start us off05:09
martialmrhillsman: thanks05:09
martialmrhillsman: b1airo and I are representing05:10
mrhillsmanah ok05:10
martialwhat do you want to know?05:10
*** Manuel_1_ has quit IRC05:10
mrhillsmanlet's say 1-3 things currently working on05:11
*** Manuel_112 has quit IRC05:11
martialsure thing, so we have a few entries on the SWG wiki at https://wiki.openstack.org/wiki/Scientific_working_group05:12
mrhillsman#link https://wiki.openstack.org/wiki/Scientific_working_group05:12
b1airoWe have probably 5-10 ppl (maybe ~15 distinct) showing up to IRC every week and discussing various topics of interest and new in the community. Particular areas of interest include: performance tuning for HPC workloads, scientific application sharing, federation, GPUs and accelerators05:12
*** sridharg has joined #openstack-meeting05:13
ad_rien_b1airo:  may I ask you wether the WG is active on each of these items (quite impressive actually)?05:13
martialThanks b1airo, a particular topic lately is also the discussion of the possible coverage of OpenStack and Scientific research at SuperComputing1705:14
ad_rien_(BTW, I'm ad_rien_ representing the FEMDC WG)05:14
b1airoBoth Stig and I have presented/represented in various forums over the last 6 months, e.g., next week I'll be talking at the HPC Advisory Council meeting in Perth05:14
*** aeng has quit IRC05:14
*** armax has quit IRC05:14
*** armax has joined #openstack-meeting05:15
*** aeng has joined #openstack-meeting05:15
*** armax has quit IRC05:15
martialad_rien: we have people introduce their work and discuss their research at different meetings05:15
b1airoIn terms of activity, we are not currently driving any dev effort from within the WG but various members are active contributors to several projects and we try to promote specs/reviews of interest to the broader research/science computing community05:16
*** armax has joined #openstack-meeting05:16
*** Manuel_112 has joined #openstack-meeting05:16
*** armax has quit IRC05:16
ad_rien_are you maintaining a etherpad/wiki page/…. where we can find details regarding progress of each sub activity?05:16
*** armax has joined #openstack-meeting05:17
martialresearch efforts are split, just as blair was explained05:17
*** armax has quit IRC05:17
*** Dinesh_Bhor has quit IRC05:17
ad_rien_I guess that questions related to the federation challenge are addressed/discussed in other WGs05:17
martialwe usually add the etherpad links to the wiki page05:17
*** armax has joined #openstack-meeting05:17
b1airoWe are currently looking at adding some content to the existing OpenStack HPC book, and I have a GPU guide draft waiting to find a home05:17
*** armax has quit IRC05:18
*** armax has joined #openstack-meeting05:18
*** armax has quit IRC05:18
martialdepends on the topic of course, we tend to create those pads as needed05:18
ad_rien_ok thanks05:19
b1airoThe overarching Scientific-WG is really much more like a SIG. There are then some sub efforts, the most established of which right now is the Federation stuff05:19
mrhillsmanthanks for sharing the update b1airo and martial05:19
ad_rien_#link https://wiki.openstack.org/wiki/ScientificWGFederatedIdentityManagement05:19
mrhillsmanthx for that link ad_rien_05:19
ad_rien_Is it that link for instance for the Federation Stuff?05:19
mrhillsman^05:20
b1airoI am quite keen to see a way in which we can use our member base to contribute into spec reviews etc in a less ad-hoc fashion. E.g. using tags05:20
mrhillsmanb1airo would you have time to draft up your idea?05:22
mrhillsmani'd like to move to the next group at this time05:23
martialI followed this link, it adds a Federated Identity user story05:23
martialad_rien_: other topics are listed at #link https://wiki.openstack.org/wiki/Scientific_working_group#Activity_Areas05:23
mrhillsmanwe can create some kind of summary from today and continue discussing and have some items for next meeting as well05:23
b1airoAlso, right now I would characterise most of our membership as operators and/or architects (+ part time support/power users). So they are all keen to share but have little real time to give05:24
b1airomrhillsman: yes, there is already a recent openstack-dev thread regarding actually - will ping it...05:24
mrhillsmancool05:24
mrhillsmanthx05:24
martial#link https://etherpad.openstack.org/p/Scientific-WG-boston05:24
*** frickler has quit IRC05:24
martialthis was the etherpad were we last discussed the work of the working group and our follow up topics for Sydney05:25
*** diablo_rojo has joined #openstack-meeting05:25
mrhillsmanawesome, thx for that link05:25
martialit will give you a better understanding of the scope of work of the members of the group05:26
mrhillsmanad_rien_ you're up :)05:26
ad_rien_ok thanks05:26
mrhillsman#topic FEMDC WG05:26
*** openstack changes topic to "FEMDC WG (Meeting topic: uc)"05:26
*** frickler has joined #openstack-meeting05:27
mrhillsman#topic FEMDC WG Update05:27
*** openstack changes topic to "FEMDC WG Update (Meeting topic: uc)"05:27
ad_rien_so we are running our WG for 3 or 4 cycles right now05:27
*** Manuel_112 has quit IRC05:27
ad_rien_We try to maintain our wikipage05:27
ad_rien_#link https://wiki.openstack.org/wiki/Fog_Edge_Massively_Distributed_Clouds#Planned_Actions_for_Queen_cycle_.28additional_actions_can_be_proposed_during_our_IRC_meetings.2905:27
*** noslzzp has joined #openstack-meeting05:28
ad_rien_and you can find details of our meetings (including progress on current actions at the end of the following etherpad)05:28
ad_rien_#link https://etherpad.openstack.org/p/massively_distributed_ircmeetings_201705:28
ad_rien_Currently we are working on three actions: 1./ Evaluating RabbitMQ alternatives (mainly focusing on the qpid router solution proposed by Redhat) 2./ investigating the opportunity of using cockroachDB with keystone 3./ Idenfiying use-cases05:30
*** janki has joined #openstack-meeting05:30
ad_rien_1./ is mainly leaded by RedHat and Inria 2./ By Inria with the support of cockRoachlab and 3./ by few folks (beyond, Orange Labs, FBK, …)05:31
*** andreas-f has quit IRC05:31
martialvery nice I must say05:31
mrhillsman++05:31
ad_rien_The general goal of our WG is to evaluate Vanilla OpenStack code in the context of Fog/Edge and Massively Distributed Clouds.05:31
ad_rien_You can find the former actions on the wikipage.05:31
ad_rien_We mainly evaluated OpenStack at WANWide scale05:32
*** rbudden has quit IRC05:33
b1airoLots of (potentially) small Cells?05:33
*** frickler has quit IRC05:33
ad_rien_thanks to a tool the WG has developped/used for the three last cycles (I can give you further information if you want or just give a look to enOS in the aforementioned etherpad)05:33
*** noslzzp has quit IRC05:33
ad_rien_yes the way of segregating OpenStack is also an action we discussed a few couple of times but because the cell V2 is still not mature (at least until the last cycle) this is an action we  have postponed.05:34
ad_rien_but we already identified several ways of segregating each micro DC (using regions or cells or…)05:34
*** markvoelker has quit IRC05:34
mrhillsmanhave folks from tricircle engaged with you all?05:34
ad_rien_we discussed a couple of time with joechang (we had a shared presentation in Boston).05:35
ad_rien_we are in touch but they do not take part to the meeting right now.05:35
mrhillsmanok good to know05:35
ad_rien_One Phd student will start next October to investigate neutron related challenges (still in the context of FEMDC)05:35
ad_rien_so we will probably get back to Tricircle.05:36
mrhillsmanthis coming october or next (2018) october?05:36
ad_rien_this one mrhillsman05:36
mrhillsmanok great05:36
ad_rien_our goal is really to try avoiding reinventing the wheel05:36
mrhillsman++05:37
martial#link https://github.com/beyondtheclouds/enos05:37
ad_rien_(i.e., we want to check whether the current code can satisfied the FEMDC requirements before implementing new pieces of software)05:37
mrhillsmangotcha, totally makes sense05:38
*** frickler has joined #openstack-meeting05:38
ad_rien_we try to collaborate withe the NFV WG and LCCO (jamemcc)05:38
ad_rien_but right now it is difficult to find recurrent people and combine our efforts05:38
ad_rien_I hope these monthly meeting will enable us to solve the issue (or at least to enable collaborations)05:39
mrhillsmanthat is good to know, hopefully more meetings like this will help05:39
ad_rien_From my side, I will read the document regarding the federation use-cases, it is definitely relevant for our WG.05:39
mrhillsmanvery good, any further details you would like to share or anyone would like to ask discuss re FEMDC WG?05:40
ad_rien_that's ok from my side , thanks mrhillsman05:40
mrhillsmani think we had one more tobberydberg am I right?05:40
tobberydbergYes =)05:41
mrhillsmancool, which WG/Team are you with tobberydberg05:41
b1airomrhillsman: re. tags see e.g. "Re: [Openstack-operators] [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs"05:41
mrhillsmanthx b1airo i will check it05:41
b1airoSean Dague suggested it there05:42
tobberydbergSince I'm pretty new here I start by introducing myself. Representing the still "un-official" working group Public Cloud05:42
mrhillsman#topic PublicCloud WG Update05:42
*** openstack changes topic to "PublicCloud WG Update (Meeting topic: uc)"05:42
b1airoBut it's also something I raised to os-tags team in Barcelona05:42
martialad_rien_: the next SWG meeting is in a little over 5 hours (1100 UTC), I am unclear if the people that wrote the Federation document are going to be present, but FYI05:42
b1airoHi tobberydberg05:42
tobberydbergMy name is Tobias Rydberg - I'm one of three chairs of the group05:42
*** kiennt has quit IRC05:42
mrhillsmanawesome, ty sir, i will get informed and we can work to push it05:42
mrhillsmanwelcome Tobias for joining05:43
tobberydbergThanks!05:43
mrhillsmanthx for joining :)05:43
*** edmondsw has joined #openstack-meeting05:43
tobberydbergsince we still are in-official we are of course working on getting approved =)05:43
ad_rien_martial:  thanks for letting me know05:44
tobberydbergBut, in general...we would like to be the voice of public clouds inside the community05:44
tobberydbergWe "started" late 2016, had a couple of pretty good Forum sessions in Boston - so we feel we are getting some traction05:45
mrhillsmangreat to hear05:46
tobberydbergAverage of 5 people in our bi-weekly meetings that we have05:46
*** harlowja has joined #openstack-meeting05:46
tobberydberg#link https://wiki.openstack.org/wiki/PublicCloudWorkingGroup05:46
*** arnewiebalck_ has quit IRC05:46
mrhillsmani like this - #link https://docs.google.com/spreadsheets/d/1Mf8OAyTzZxCKzYHMgBl-QK_2-XSycSkOjqCyMTIedkA05:47
*** Manuel_112 has joined #openstack-meeting05:47
*** frank_young has joined #openstack-meeting05:48
martialtobberydberg: something that might be relevant to your WG effort: https://wiki.openstack.org/wiki/Boston-Cloud-Congress05:48
*** edmondsw has quit IRC05:48
tobberydbergThe things that we are working on right now is 1. Organising PublicCloud WG Meetups 2. Keep working on out "missing features" list - turn them into specs 3. Something we call OpenStack Passport05:48
tobberydbergThanks mrhillsman ... thats the link for missing features ... we will try to get that into a more official format during this cycle as well05:49
mrhillsmani linked to #2 above, stood out based on recent ML discussions regarding SIGs :)05:49
*** zhurong has joined #openstack-meeting05:50
tobberydbergmartial: Haven't seen that - will look into it05:50
*** rcernin has joined #openstack-meeting05:50
*** ykatabam has quit IRC05:51
tobberydbergAnd I guess that we will become more of a SIG than a traditional WG =)05:51
mrhillsmanyes, i think there will be some structuring that affects everyone re move to SIGs05:52
tobberydbergWe will very soon produce a draft of a spec for the OpenStack Passport05:52
ad_rien_I though that a SIG will be temporary05:52
mrhillsmani love the passport idea, looking forward to it05:52
tobberydbergcool =)05:52
*** Daisy_ has quit IRC05:52
tobberydbergThat's basically all from my short update. Looking forward to be officially accepted ;-)05:53
*** Daisy_ has joined #openstack-meeting05:53
mrhillsmanawesome, thx tobberydberg05:54
mrhillsmani will add the wg proposal for monday for official uc vote05:54
b1airoad_rien_: I believe SIGs are intended to be long lived, Working Groups will be temporary, Teams I'm still a little confused about05:54
tobberydbergthanks mrhillsman05:55
ad_rien_b1airo:  thanks (I read a google doc a few days ago where I found the definition)05:55
*** aeng has quit IRC05:55
mrhillsman#topic Open Discussion05:55
*** openstack changes topic to "Open Discussion (Meeting topic: uc)"05:55
b1airoBut an example world be docs team05:55
b1airo*would05:55
mrhillsmana good example of wg vs team is auc recognition wg vs product wg05:55
mrhillsmanauc recognition is right for wg05:55
ad_rien_I have another questions: there are many other WGs/Teams (for instance the LDT: large deployment team…)05:56
mrhillsmanproduct wg will not be product team under newly ratified doc05:56
*** thorst has joined #openstack-meeting05:56
mrhillsman#link https://review.openstack.org/#/c/484208/05:56
ad_rien_I'm wondering how we can make them participating in such a meeting where we can share questions/issues/on-going actions05:56
b1airo"now be" you mean mrhillsman ?05:56
ad_rien_at least from my side, I would really like to have an update of alll those WGs/teams.05:57
mrhillsmanyes, sorry05:57
mrhillsmanagreed05:57
*** Daisy_ has quit IRC05:57
ad_rien_I'm still convinced that there is a huge overlap between each WG/team05:57
mrhillsmani think a key to your question/desire ad_rien_ is for you all to let the UC know these and say it is what you want05:57
ad_rien_:-)05:58
mrhillsmanone thing we recently implemented/created is #openstack-uc05:58
mrhillsmanrather than having to wait for an "official" meeting we now have that channel for async communication05:58
*** Daisy_ has joined #openstack-meeting05:58
mrhillsmani am pretty much in there all day05:59
ad_rien_#link https://docs.google.com/document/d/1r3KwaG-SbvaKCuAE52XwPCF7cRGDrNRg6dUhPQWs0vU/edit05:59
mrhillsmanyeah, we approved that and it is merged05:59
ad_rien_I read this yesterday, it is writtent each WG char should join  the UC IRC meeting ;)05:59
ad_rien_I added a comment ( not sure it has been taken into account)05:59
mrhillsmanso the meeting will be over in a couple minutes06:00
ad_rien_sorry06:00
mrhillsmandefinitely06:00
ad_rien_we can discuss that next time06:00
mrhillsmanno need to wait so long #openstack-uc :)06:00
mrhillsmanfeel free to talk as much as you'd like there06:00
ad_rien_right06:00
martial:)06:00
ad_rien_I didn't see the merge request06:00
mrhillsman#link https://review.openstack.org/#/c/484208/06:01
ad_rien_mrhillsman:  thanks highly appreciated06:01
*** thorst has quit IRC06:01
ad_rien_ok I think the time is over06:01
ad_rien_thanks for chairing the discussion mrhillsman06:01
mrhillsmanalso the uc channel is connected to gerrit so changes hit that channel06:01
mrhillsmanvery welcome06:01
mrhillsmanthank you all for joining!06:01
tobberydbergThanks mrhillsman .. and rest of you06:02
mrhillsmanreally looking forward to doing more06:02
mrhillsmanbe sure you all are prepared for upcoming UC elections06:02
*** kiennt has joined #openstack-meeting06:02
mrhillsman3 seats are up for election :)06:02
mrhillsmananything more?06:03
ad_rien_mrhillsman:  Link?06:03
mrhillsmanwe wrote up an article #link http://superuser.openstack.org/articles/user-committee-elections/06:03
mrhillsmangoing to end meeting now to be in order :)06:03
mrhillsman#endmeeting06:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:03
openstackMeeting ended Wed Jul 19 06:03:58 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:04
openstackMinutes:        http://eavesdrop.openstack.org/meetings/uc/2017/uc.2017-07-19-05.03.html06:04
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/uc/2017/uc.2017-07-19-05.03.txt06:04
openstackLog:            http://eavesdrop.openstack.org/meetings/uc/2017/uc.2017-07-19-05.03.log.html06:04
*** lpetrut__ has quit IRC06:04
martialthank you, good bye06:05
*** martial has quit IRC06:06
*** martinkopec has joined #openstack-meeting06:06
*** tobberydberg has quit IRC06:06
*** wanghao_ has joined #openstack-meeting06:06
*** tobberydberg has joined #openstack-meeting06:07
*** marios has joined #openstack-meeting06:07
*** Adri2000 has joined #openstack-meeting06:07
*** wanghao has quit IRC06:09
*** tobberydberg has quit IRC06:11
*** radeks has joined #openstack-meeting06:16
*** caowei_ has joined #openstack-meeting06:16
*** caowei has quit IRC06:16
*** caowei_ is now known as caowei06:16
*** ekcs has quit IRC06:20
*** kiennt has quit IRC06:21
*** aeng has joined #openstack-meeting06:21
*** baoli has quit IRC06:22
*** martinkopec has quit IRC06:27
*** martinkopec has joined #openstack-meeting06:29
*** aeng has quit IRC06:30
*** markvoelker has joined #openstack-meeting06:31
*** kevzha01 is now known as kevinz06:32
*** andreas_s has joined #openstack-meeting06:32
*** anilvenkata has joined #openstack-meeting06:33
*** harlowja has quit IRC06:42
*** frickler has quit IRC06:42
*** frickler has joined #openstack-meeting06:42
*** ykatabam has joined #openstack-meeting06:43
*** Dinesh_Bhor has joined #openstack-meeting06:50
*** Dinesh_Bhor has quit IRC06:50
*** rbartal_ has joined #openstack-meeting06:51
*** ykatabam has quit IRC07:00
*** annegentle has quit IRC07:01
*** epico has quit IRC07:03
*** markvoelker has quit IRC07:04
*** lpetrut has joined #openstack-meeting07:06
*** cschwede_ has joined #openstack-meeting07:11
*** dmacpher has quit IRC07:13
*** tesseract has joined #openstack-meeting07:17
*** adisky__ has joined #openstack-meeting07:20
*** diablo_rojo has quit IRC07:21
*** epico has joined #openstack-meeting07:25
*** ad_rien_ has quit IRC07:27
*** epico has quit IRC07:31
*** edmondsw has joined #openstack-meeting07:31
*** edmondsw has quit IRC07:36
*** kiennt has joined #openstack-meeting07:40
*** zeih has joined #openstack-meeting07:43
*** pfallenop has joined #openstack-meeting07:44
*** ralonsoh has joined #openstack-meeting07:46
*** epico has joined #openstack-meeting07:47
*** toscalix has joined #openstack-meeting07:48
*** zeih has quit IRC07:53
*** zeih has joined #openstack-meeting07:54
*** oidgar has joined #openstack-meeting07:54
*** lpetrut has quit IRC07:55
*** ad_rien_ has joined #openstack-meeting07:56
*** thorst has joined #openstack-meeting07:57
*** zeih has quit IRC08:01
*** ociuhandu_ has joined #openstack-meeting08:01
*** thorst has quit IRC08:02
*** pfallenop has quit IRC08:03
*** pfalleno1 has joined #openstack-meeting08:03
*** zeih has joined #openstack-meeting08:03
*** mlakat has quit IRC08:06
*** dbecker has joined #openstack-meeting08:06
*** b1airo has quit IRC08:15
*** electrofelix has joined #openstack-meeting08:27
*** ociuhandu_ has quit IRC08:29
*** artom_ has quit IRC08:31
*** artom_ has joined #openstack-meeting08:32
*** ralonsoh has quit IRC08:33
*** ralonsoh_ has joined #openstack-meeting08:33
*** cody-somerville has quit IRC08:36
*** cody-somerville has joined #openstack-meeting08:36
*** cody-somerville has quit IRC08:36
*** cody-somerville has joined #openstack-meeting08:36
*** Daisy_ has quit IRC08:41
*** Daisy_ has joined #openstack-meeting08:42
*** mlakat has joined #openstack-meeting08:42
*** radeks has quit IRC08:43
*** egallen has joined #openstack-meeting08:43
*** Daisy__ has joined #openstack-meeting08:45
*** Daisy_ has quit IRC08:46
*** tovin07_ has quit IRC08:50
*** radeks has joined #openstack-meeting08:56
*** markvoelker has joined #openstack-meeting09:02
*** radeks has quit IRC09:05
*** yamamoto has quit IRC09:06
*** tobberydberg has joined #openstack-meeting09:08
*** rwsu has quit IRC09:10
*** yamamoto has joined #openstack-meeting09:10
*** yamamoto has quit IRC09:10
*** egallen has quit IRC09:11
*** rwsu has joined #openstack-meeting09:12
*** tobberydberg has quit IRC09:14
*** yamamoto has joined #openstack-meeting09:14
*** radeks has joined #openstack-meeting09:18
*** edmondsw has joined #openstack-meeting09:19
*** caowei has quit IRC09:20
*** edmondsw has quit IRC09:24
*** wanghao_ has quit IRC09:26
*** radeks has quit IRC09:27
*** vishnoianil has quit IRC09:33
*** markvoelker has quit IRC09:35
*** yamamoto has quit IRC09:36
*** yamamoto has joined #openstack-meeting09:36
*** sdague has joined #openstack-meeting09:37
*** radeks has joined #openstack-meeting09:39
*** maeca has joined #openstack-meeting09:41
*** sambetts|afk is now known as sambetts09:42
*** kevinz has quit IRC09:44
*** Daisy__ has quit IRC09:45
*** ad_rien_ has quit IRC09:48
*** ad_rien_ has joined #openstack-meeting09:50
*** lpetrut has joined #openstack-meeting09:50
*** jamesmcarthur has joined #openstack-meeting09:57
*** thorst has joined #openstack-meeting09:58
*** jamesmcarthur has quit IRC10:01
*** thorst has quit IRC10:03
*** zz9pzza has joined #openstack-meeting10:04
*** zhhuabj has quit IRC10:17
*** caowei has joined #openstack-meeting10:23
*** Manuel_112 has quit IRC10:24
*** Daisy_ has joined #openstack-meeting10:24
*** Dinesh_Bhor has joined #openstack-meeting10:27
*** Daisy_ has quit IRC10:29
*** zhhuabj has joined #openstack-meeting10:30
*** yamahata has quit IRC10:30
*** elynn_ has joined #openstack-meeting10:30
*** markvoelker has joined #openstack-meeting10:32
*** elynn has quit IRC10:32
*** jkilpatr has quit IRC10:36
*** Manuel_112 has joined #openstack-meeting10:40
*** radeks has quit IRC10:40
*** priteau has joined #openstack-meeting10:41
*** epico has quit IRC10:45
*** kiennt has quit IRC10:45
*** radeks has joined #openstack-meeting10:53
*** zhurong has quit IRC10:53
*** lpetrut_ has joined #openstack-meeting10:54
*** yamamoto has quit IRC10:55
*** Pelalil has joined #openstack-meeting10:55
*** gcb has quit IRC10:55
*** lpetrut has quit IRC10:56
*** verdurin has joined #openstack-meeting10:56
*** gcb has joined #openstack-meeting10:57
*** Shrews has left #openstack-meeting10:57
*** andreas_s has quit IRC10:57
*** daveholland has joined #openstack-meeting10:57
*** neiljerram has joined #openstack-meeting10:59
*** oneswig has joined #openstack-meeting10:59
*** elynn_ has quit IRC10:59
oneswig#startmeeting scientific-wg11:00
openstackMeeting started Wed Jul 19 11:00:24 2017 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at http://wiki.debian.org/MeetBot.11:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.11:00
*** openstack changes topic to " (Meeting topic: scientific-wg)"11:00
openstackThe meeting name has been set to 'scientific_wg'11:00
verdurinAfternoon, oneswig11:00
oneswigPrecisely so11:00
oneswigafternoon verdurin11:00
oneswig#link Agenda for today https://wiki.openstack.org/wiki/Scientific_working_group#IRC_Meeting_July_19th_201711:01
Pelaliloneswig, tom here, thanks for the email reminder 30min ago :)11:01
daveholland(I'm in a training course so just lurking in this meeting)11:01
*** martial has joined #openstack-meeting11:01
oneswigHi Tom, very welcome11:01
oneswig#chair martial11:01
openstackCurrent chairs: martial oneswig11:01
oneswigWe have a shortish agenda for today but the main event is an interesting presentation on research by James at Sanger11:02
zz9pzzaHi11:03
oneswiggreetings :-)11:03
verdurinHello11:03
oneswig#topic OpenStack and Lustre11:03
*** openstack changes topic to "OpenStack and Lustre (Meeting topic: scientific-wg)"11:03
oneswig#link presentation on Lustre is at https://docs.google.com/presentation/d/1kGRzcdVQX95abei1bDVoRzxyC02i89_m5_sOfp8Aq6o/edit#slide=id.g22aee564af_0_011:04
*** frank_young has quit IRC11:04
oneswigzz9pzza: can you tell us a bit about the background?11:04
zz9pzzaOne of the things we have been worrying about is posix file access in openstack11:05
*** b1airo has joined #openstack-meeting11:05
b1airoo/11:05
oneswigHi b1airo11:06
oneswig#chair b1airo11:06
zz9pzzaWe did some work with DDN ( not using any none standard/open software ) to see if we could allow access to lustre from different tenants to different bits of a lustre filesystem11:06
openstackCurrent chairs: b1airo martial oneswig11:06
b1airoevening11:06
zz9pzzaHi11:06
*** markvoelker has quit IRC11:06
zz9pzzaThe short story is I think we could provide it as a service  and we are definitely considering doing so11:06
zz9pzzaWe have one tenant about to use it in anger11:06
verdurinHello b1airo11:06
oneswigDoes it depend on the DDN Lustre distribution?11:06
zz9pzzaNo11:06
zz9pzzaYou need to have atleast lustre 2.911:07
zz9pzzaAnd 2.10 is an lts release11:07
zz9pzzaThere a lbug that needs fixing but the fix is public11:07
verdurinAh - was going to ask if any fixes had gone upstream11:07
zz9pzzahttps://jira.hpdd.intel.com/browse/LU-928911:07
*** edmondsw has joined #openstack-meeting11:07
zz9pzzaits a one line fix for a null termination error11:08
zz9pzza( from memory )11:08
Pelalilzz9pzza, are you using the ddn software stack, or just the ddn hardware with your own lustre install?11:08
zz9pzzaIt says it is in 2.1011:08
zz9pzzaWe use DDN hardware. I believe the software is a ddn release but it is not required. DDN reinstalled a set of old servers for us as we didn't have the time11:09
*** alexchadin has joined #openstack-meeting11:09
*** frank_young has joined #openstack-meeting11:09
zz9pzza( We used to install our own lustre servers but people wanted a more appliance approach  ) We could still do it but we are a bit busy11:09
zz9pzzaBasically the approach is to use lustre routers to isolate the tenant11:10
zz9pzzaUse the 2.9 file sets and uid mapping so each tenant gets a different @tcp network11:10
zz9pzzaWe tried with both pyhsical and virtual lustre routers, both work11:11
b1airowhy the net LNET routing, is that to integrate with OpenStack tenant/private networks ?11:11
b1airos/net/need/11:11
zz9pzzaIts because you can't trust the tenant not to alter the network and the isolation is based on the lustre nid11:12
*** edmondsw has quit IRC11:12
*** fzdarsky_ is now known as fzdarsky|lunch11:12
*** jkilpatr has joined #openstack-meeting11:12
zz9pzzaThe routers are in the control of the openstack/filesystem operators11:12
b1airoahh ok, don't know anything about how the isolation works, guess that is a hard requirement then!11:12
verdurinzz9pzza: could all the background Lustre work be triggered by tenant creation in OpenStack? Or does it have to be handled separately?11:13
oneswigzz9pzza: how does the special role fit in?11:13
*** armstrong has joined #openstack-meeting11:14
zz9pzza"could all the background Lustre work be triggered by tenant creation in OpenStack? Or does it have to be handled separately?" I can imagine doing it all as part of a tenant creation SOP/script however we havn't done it. I would pre create the provisioning networks otherwise you would need to restart neutron on a tenant creation11:14
zz9pzzaWhat do you mean by special role oneswig ?11:14
oneswigThe Lnet-5 role11:15
zz9pzzaSo each filesystem isolation area needs to have a role associated with it.11:15
oneswigThis role enables the creation of ports, the admins create the network and routers - is that it?11:15
zz9pzzaThat role allows the user to create a machine that has access to the provisioning network that has a lustre router on it11:16
zz9pzzaSo the role allows a user to create a machine where that machine has all the access to the data in that tenant11:16
zz9pzzaMy experiments only used a single uid/guid as root in the tenant could change their user to be what ever they wished.11:17
zz9pzzaDoes that make sense ?11:17
zz9pzza( and yes "the admins create the network and routers - is that it?" )11:17
zz9pzzaIf you had a tenant which had real multiple users in it you could expose more uid/guid space to that tenant11:18
oneswigI think so thanks.11:18
zz9pzza( but root in the tenant could still read all the data of the tenant )11:18
oneswigIt makes sense for situations where there are project power users who create and set up infra for others on the team11:19
zz9pzzait could do yes11:20
oneswigThe VLAN interface on the instances, have you tried using direct-bound ports on that, ie SR-IOV?11:20
zz9pzzaWe haven't we have a tendancy to keep things as simple as we can and optimise when we are more confident11:21
zz9pzzaThe performance was better than I expected without it.11:22
oneswigSounds reasonable.  What's the hypervisor networking configuration - a standard Red Hat setup or tuned in any particular way?11:22
zz9pzzaThe orignal runs were done completely in optimally. We had a kernel where we had to turn all hardware acceleration off.11:23
zz9pzzaWe upgraded the kernel and got a large performance boost with hardware acceleration on.11:23
b1airozz9pzza, have you submitted this for a talk in Sydney by any chance?11:24
oneswigI think I saw something similar in our tests, but that was for offloads on VXLAN-tunneled packets11:24
zz9pzzaWhen is Sydney  ( and I present really really badly )11:25
zz9pzzaI don't think I can make that time in November11:25
zz9pzzaIf any one wanted to talk around it I wouldn't object and would help :)11:26
oneswigAlas, the formal deadline for presentation submissions was last Friday11:26
b1airopity to waste a perfectly good slide-deck though!11:26
zz9pzzaAnd it does work and solves a problem we in scientific research do have11:27
oneswigagreed!11:27
zz9pzzaAnd it is all free software11:27
oneswigThe results on slide 23 - what is the missing text in the legend "bare metal with..."?11:28
zz9pzzaJust looking11:28
*** Alex_Staf has joined #openstack-meeting11:29
zz9pzzaI think it is dual physical routers, but I think that is an artifact of how our first instance of openstance uses bonding11:30
*** edmondsw has joined #openstack-meeting11:30
oneswigFor comparison, the Ceph filesystem was giving you about 200MB/s read performance, and you're seeing around 1300MB/s for single-client Lustre bandwidth?11:30
zz9pzzaOur hypevisors are not using l3/l411:30
*** fzdarsky|lunch is now known as fzdarsky11:31
oneswig... but about 3000MB/s in an equivalent bare metal test11:31
zz9pzzaLet me see if I can find the spreadsheet of doom which has raw numbers in it ( and the headings are less than obvious )11:31
b1airotwo instances of openstack = two completely separate clouds? or different regions, AZs, Cells, or something else...?11:32
*** noslzzp has joined #openstack-meeting11:33
zz9pzzaSo are next openstack instance is on the same set of physical hardware11:33
zz9pzzaWe have enough controller type machines to have two instances running at once11:33
martialvery nice speed up11:33
zz9pzzaThe next one is newton11:33
zz9pzza( which has a better kernel and better bonding config )11:34
zz9pzzahttps://docs.google.com/spreadsheets/d/1E-YOso5-aDTzn2m6lKoYwBNWHvgAIcrxM5SpxSBw0_Y/edit?usp=sharing11:35
zz9pzzaI think that is it :)11:35
zz9pzzasorry its a bit incomprehensable11:36
zz9pzzaSo a single client got up to about 900MB/s write11:37
*** noslzzp has quit IRC11:37
oneswigzz9pzza: there's a certain amount of admin setup (the provider networks, role definitions etc). Is this a blocker for orchestrating through Manila?  It does sound quite similar to the CephFS sharing model11:38
zz9pzzaI don't know enough about Manila to comment.11:38
zz9pzzaI would have to check if Manila is supported in redhats rdo as well11:38
b1airoi'm curious as to why you ended up with Arista switching and Mellanox HCAs?11:38
zz9pzzaAnd I am still abit nervous about cephfs11:38
oneswigzz9pzza: my experiments with it confirm those nerves, but I have great hope for luminous11:39
zz9pzzaSo the Mellanox HCA's appear to have lots of hardware acceleration and were not significantly more expensive11:39
*** hashar has joined #openstack-meeting11:39
*** kaisers has quit IRC11:39
zz9pzzaThe Arista switches are very good software and for the ports supported very cost effective11:40
oneswigHow are you doing 25G - breakout cables?11:40
zz9pzzaDual 32 port 100/50/40/25/10 gig switches are very reasonable11:40
*** yamamoto has joined #openstack-meeting11:40
zz9pzzaYes the 25gb breakout is a cable11:40
zz9pzzaso we could have 128 ports of 25GB/s11:41
zz9pzzaWe have a mixture of 25 and 10011:41
zz9pzzaWe hope to use the arista to do the vxlan encoding in the next itteration as well11:41
b1airoany RDMA traffic?11:41
zz9pzzaWe don't do that right now, the next itteration of ceph should have it and the cards do support it11:42
zz9pzza( For vxlan encoding in the switch redhats lack of being able to set the region name is a complete pain ()11:42
oneswigzz9pzza: You have a mix of VLANs and VXLANs?11:42
zz9pzzayes its fine11:42
zz9pzzaThis itteration all the tenant networking is double encapsulated.11:43
zz9pzzaOnce on the switch, once on the hypervisor11:43
*** zeih has quit IRC11:43
oneswigb1airo: did you have any data that compares lnet tcp and o2ib approaches?11:43
oneswigzz9pzza: your presentation is very thorough, thanks for that - is there anything that isn't working yet that you're still working on?11:44
b1airono, both our Lustres are in o2ib mode at the moment, but we have considered going back to TCP on the ConnectX-3 based system due to some recurring LNET errors11:44
zz9pzzaI think I would be happy enough putting it in to production, I am not sure if virtual or physical lustre routers are the right approach both have advantages.11:45
b1aironot easy with it all in production and long job queues11:45
zz9pzzaI think I would buy physical routers in the first instance.11:45
zz9pzza( physical routers makes it easy to bridge ethernet and ib too )11:46
oneswigzz9pzza: is 1300MB/s fast enough for your needs or are you looking at closing that gap to bare metal?11:46
zz9pzzaWell a single vm got to 900MB/s write and 1.2GB/s read11:46
*** kaisers has joined #openstack-meeting11:47
zz9pzzawhich is not too bad for a 6 year old server set up11:47
zz9pzza( and not at the same time )11:47
zz9pzza( look at single machine 4MB/2VCPU New Kernel )11:47
zz9pzza( it should be 4GB )11:47
b1airoare LNET routers particularly resource hungry? i'm guessing they don't need much memory, just decent connectivity and a bit of CPU (maybe not even much of that if using RDMA) ?11:50
zz9pzzaNo you just need a bit of cpu11:50
oneswigDid you try more VCPUs and the new kernel?  Just interested in exploring what the bottleneck is cf bare metal11:50
zz9pzzaI didn't the new kernel came came very close to my deadline11:50
*** litao__ has quit IRC11:51
b1airozz9pzza, that spreadsheet is all Lustre numbers? what was the ceph comparison you mentioned?11:51
zz9pzzaAt the very beginning on our first ceph I just used dd,11:51
oneswigI saw some numbers on slide 911:51
zz9pzzaLet me look11:52
*** rbowen has quit IRC11:52
zz9pzzaThat was a dd in a volume, not really comparable11:52
b1airoah ok, so no direct comparison, hat was just a single client dd "does this work" test?11:52
zz9pzzaYes11:52
zz9pzzaI could do that now and I am happy to do so11:52
zz9pzza( our ceph cluster has also just doubled in size )11:52
b1airofun times11:53
zz9pzzaAnd we are getting another 2.5PB of useable in a couple of weeks11:53
oneswignice!  At that scale, I guess you're erasure coding?11:53
zz9pzzaNo.11:53
zz9pzzaWe are not confident yet.11:54
b1airodo you have any support now? i see you discounted RH on price (can understand that)11:54
oneswigI'd be interested to hear experiences with that11:54
zz9pzzaRedhat have got back to us on pricing and it is worth talking to them again if you are accedemic11:54
b1airooneswig, can't EC for RBD or CephFS yet unless you're on Bluestore etc11:54
zz9pzza( we have yet to buy support but I think we will  in the long term )11:55
oneswigah, thanks b1airo11:55
b1airowe do have RH support, at a significant discount, it is still fairly pricey compared to others (e.g. SUSE, Canonical)11:55
zz9pzzaI would check again11:55
b1airooneswig, however we use EC for radosgw objects11:55
zz9pzza( I mean I would get an upto date quote for ceph support )11:56
b1airoit works just fine - main difference operationally is that things like scrub and recovery/backflll take much longer as the PGs are much wider11:56
oneswigb1airo: and does it become CPU limited, or is that not a concern?11:57
oneswigfor the OSDs that is11:57
b1aironot really a concern for HTTP object store workloads (at least that we have hit yet!)11:57
oneswigfair point11:57
zz9pzzaWhat kind of performance do you get though rados gw ?11:57
oneswigWe are close to time... final questions11:58
*** dprince has joined #openstack-meeting11:58
verdurinJust a shame it's Lustre, rather than GPFS...11:58
zz9pzza:)11:58
verdurinThanks a lot, though zz9pzza - very impressive11:58
oneswigverdurin: well timed to wind up the debate :-)11:58
*** kevzha01 has joined #openstack-meeting11:58
b1airoit can scale pretty well, think we tested to over a GB/s with just three 2core radosgw VM hosts11:59
oneswigthanks indeed, that presentation is thorough and very informative zz9pzza11:59
b1airocareful with big buckets though - if you are not prepared for them it can be a real pain to get rid of them!11:59
martialyes, thank you. I will share the log to a couple colleagues11:59
zz9pzzaFeel free to steal bits if any one wants to11:59
b1airoyes thanks zz9pzza - great presentation12:00
oneswig"share and enjoy" you mean :-)12:00
zz9pzzaIndeed12:00
oneswigOK, time to wrap up all12:00
verdurinBye all12:00
oneswigthanks everyone12:00
oneswig#endmeeting12:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"12:00
openstackMeeting ended Wed Jul 19 12:00:32 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-07-19-11.00.html12:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-07-19-11.00.txt12:00
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-07-19-11.00.log.html12:00
armstrongThanks12:00
b1airogood night all!12:00
martialbye12:01
armstrongBye12:01
priteaubye, thanks for the presentation12:01
zz9pzzattfn12:01
*** raildo has joined #openstack-meeting12:01
*** arnewiebalck_ has joined #openstack-meeting12:02
*** elynn has joined #openstack-meeting12:02
*** thorst has joined #openstack-meeting12:02
*** oneswig has quit IRC12:02
*** verdurin has left #openstack-meeting12:02
*** markvoelker has joined #openstack-meeting12:03
*** yamamoto has quit IRC12:03
*** thorst_ has joined #openstack-meeting12:04
*** noslzzp has joined #openstack-meeting12:06
*** thorst has quit IRC12:06
*** rbowen has joined #openstack-meeting12:12
*** martial has quit IRC12:14
*** lhx__ has joined #openstack-meeting12:15
*** anilvenkata has quit IRC12:15
*** ociuhandu_ has joined #openstack-meeting12:15
*** daveholland has quit IRC12:15
*** b1airo has quit IRC12:19
*** yamamoto has joined #openstack-meeting12:21
*** neiljerram has quit IRC12:23
*** frank_young has quit IRC12:24
*** markvoelker has quit IRC12:25
*** markvoelker has joined #openstack-meeting12:26
*** pchavva has joined #openstack-meeting12:26
*** caowei has quit IRC12:26
*** eharney has joined #openstack-meeting12:27
*** julim has quit IRC12:28
*** arnewiebalck_ has quit IRC12:28
*** kevzha01 has quit IRC12:31
*** mriedem has joined #openstack-meeting12:31
*** baoli has joined #openstack-meeting12:31
*** ralonsoh_ has quit IRC12:32
*** baoli_ has joined #openstack-meeting12:33
*** baoli has quit IRC12:37
*** elynn has quit IRC12:44
*** Pelalil has quit IRC12:51
*** kylek3h has joined #openstack-meeting12:51
*** gcb has quit IRC12:54
*** frank_young has joined #openstack-meeting12:54
*** tobberydberg has joined #openstack-meeting12:56
*** gouthamr has joined #openstack-meeting12:58
*** frank_young has quit IRC12:59
*** esberglu has joined #openstack-meeting13:09
*** tobberydberg has quit IRC13:11
*** tobberydberg has joined #openstack-meeting13:12
*** dongfeng has joined #openstack-meeting13:12
*** tobberydberg has quit IRC13:16
*** mriedem is now known as mriedem_meeting13:17
*** ralonsoh has joined #openstack-meeting13:19
*** ralonsoh has quit IRC13:20
*** ralonsoh has joined #openstack-meeting13:20
*** bknudson has joined #openstack-meeting13:28
*** bknudson has quit IRC13:29
*** bknudson has joined #openstack-meeting13:33
*** julim has joined #openstack-meeting13:36
*** bobh has joined #openstack-meeting13:37
*** askb has quit IRC13:39
*** Daisy_ has joined #openstack-meeting13:40
*** Fdaisuke has joined #openstack-meeting13:43
*** trinaths has left #openstack-meeting13:45
*** Daisy_ has quit IRC13:45
*** rwsu has quit IRC13:49
*** hongbin has joined #openstack-meeting13:49
*** martial_ has joined #openstack-meeting13:49
*** jamesmcarthur has joined #openstack-meeting13:51
*** shinya_kwbt has joined #openstack-meeting13:52
*** frank_young has joined #openstack-meeting13:52
*** jrist has quit IRC13:53
*** phuoc_ has quit IRC13:54
*** koji has joined #openstack-meeting13:56
*** frank_young has quit IRC13:57
*** ataraday has quit IRC13:57
*** rwsu has joined #openstack-meeting13:57
*** rhochmuth has joined #openstack-meeting13:57
*** kornica has joined #openstack-meeting13:57
*** sc has joined #openstack-meeting13:58
*** awaugama has joined #openstack-meeting13:58
*** tobberydberg has joined #openstack-meeting13:59
*** armax has joined #openstack-meeting13:59
rhochmuth#startmeeting monasca14:00
openstackMeeting started Wed Jul 19 14:00:43 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
rhochmutho/14:00
kojio/14:01
shinya_kwbto/14:01
kornicao/14:01
rhochmuthhi everyone14:01
Fdaisukeo/14:01
*** sridharg has quit IRC14:01
*** alexchadin has quit IRC14:02
kornicahello14:02
scyo14:02
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda14:02
rhochmuthAgenda for Wednesday July 19 2017 (14:00 UTC)14:02
rhochmuth1.Reviews14:02
rhochmuth1.https://review.openstack.org/#/c/479169/  - Needs +1 to move forward and to start reenabling  the gates (Added by Artur Basiak, unfortunatelly I cannot join meeting)14:02
rhochmuth2.monasca-docker14:02
rhochmuth1.https://github.com/monasca/monasca-docker/pull/12114:02
rhochmuth2.https://github.com/monasca/monasca-docker/pull/12014:02
rhochmuth3.https://github.com/monasca/monasca-docker/issues/12214:02
rhochmuthnot a huge agenda for the day14:02
rhochmuthbut, we can work through it14:02
rhochmuth#topic https://review.openstack.org/#/c/479169/ 14:03
*** openstack changes topic to "https://review.openstack.org/#/c/479169/  (Meeting topic: monasca)"14:03
kornicaI can take it, Artur has some apartment stuff or sth going on these days14:03
*** armstrong has quit IRC14:03
kornicain overall, Witek wanted you to take a look and approve the cleanup, that said - the change is more or less dropping old codebase and adding all of the tooling14:04
kornicawe've developed recently for other components14:04
*** toscalix has quit IRC14:04
*** haru_ has joined #openstack-meeting14:05
rhochmuthok, i'll look through and add a +114:05
rhochmuthalthough, my time lately has been difficult14:05
kornicaif you want there are already 3 related changes14:05
kornicafrom which the most notable is an idea of extending monasca-persister to handle events14:06
kornicapersisting raw events into database14:06
*** jrist has joined #openstack-meeting14:06
kornicahttps://review.openstack.org/#/c/485113/14:06
kornicaI know that having a time is difficult these days (oh...yeah...I know that)14:06
kornicastill we know this is vital to have such details communicated14:06
rhochmuthyup14:07
kornicaother side of the coing is the idea of adding new project14:07
rhochmuthso, you are planning on extending the persister, rather than add a new one14:07
kornicawe had such a plan initially14:07
kornicabut witek stepped in (no offense or sth) in a pretty much correct momement to point out14:07
kornicathat basically we might not need new repo / service14:08
kornicabut we can extend persister14:08
*** rbrndt has joined #openstack-meeting14:08
kornicaand roll with the idea I presented in comments for https://review.openstack.org/#/c/485113/14:08
rhochmuthi see, so witek is in charge now14:08
*** felipemonteiro__ has joined #openstack-meeting14:08
rhochmuth:-)14:08
kornicahe's not in charge14:08
kornica:D14:08
kornicathough we've been talking a lot how to approach the events topic14:08
kornicathe best way we could14:09
rhochmuthi'm just kidding14:09
*** yamamoto has quit IRC14:09
kornicai know ;-)14:09
kornicajust giving some background :D14:09
kornicaanyway, if could you find some time to tell which idea might be better14:09
kornicathat'd be really great ;-014:09
kornica:)14:09
rhochmuthsure14:09
rhochmuthi probably would have said keep them separate14:09
rhochmuthhowever, everytime we add a new repo it is a lot of overhead14:10
*** anilvenkata has joined #openstack-meeting14:10
rhochmuthso, not exactly for adding more overhead14:10
rhochmuthso, i'm probably ok with that in the persister14:10
kornicathat's pretty much the argument that Witek has given14:10
kornicaquestion is should be do the same for every other part of events :/14:10
kornicaand that is somehow unclear14:11
rhochmuthyou can get caried away with microservices14:11
kornicathere are benefits of such approach14:11
kornicaand there re downsides14:11
*** hoppalm has joined #openstack-meeting14:11
rhochmuthyup14:11
*** felipemonteiro_ has joined #openstack-meeting14:11
kornicayeah, that'd be the downside14:11
kornicaI will ask then14:11
rhochmuthi see, so are think thinking about adding to the monasca-api directly then too14:11
kornicawell yeah14:11
rhochmuthwould that be still under consideration?14:11
kornicaif you see this as better idea, yeah - we would reconsider14:12
kornicaat the moment events-api is on hold14:12
kornicano gates, no CI - pretty much dead repo14:12
*** jaypipes has joined #openstack-meeting14:12
rhochmuthyup, lot's of fun enabliing all that infrastructure too14:12
kornicawe can either go direction we are now going14:13
kornicaor retire the project14:13
*** VW has joined #openstack-meeting14:13
rhochmuthlet's ask witek14:13
kornicahe will most likely read all that14:13
kornicaand we decided to talk about all that14:13
*** frank_young has joined #openstack-meeting14:14
kornicaso most likely we will continue with current approach and if necessary just port all that to exisiting repos14:14
rhochmuthi'm going to have to think a bit off-line and look closer at what you've done so far14:14
rhochmuthand talk to a few folks14:14
*** felipemonteiro__ has quit IRC14:14
kornicanevertheless I am sure we will try and communicate14:14
rhochmuthsure14:14
kornicathough I am not really into events now (my priorities goes to other items on agenda) :D14:14
kornicabut I will ask arturb to put some focus on that fact14:15
rhochmuthok14:15
kornicaand thx for having a look14:15
rhochmuthi'll send an email14:15
*** jamesmcarthur has quit IRC14:15
rhochmuthso, probably time to move to the next topic14:15
rhochmuth#topic monasca-docker14:16
*** openstack changes topic to "monasca-docker (Meeting topic: monasca)"14:16
rhochmuth2.monasca-docker14:16
rhochmuth1.https://github.com/monasca/monasca-docker/pull/12114:16
rhochmuth2.https://github.com/monasca/monasca-docker/pull/12014:16
rhochmuth3.https://github.com/monasca/monasca-docker/issues/12214:16
kornicawell, we started working on log-pipeline in docker (finally decided on container course in fujitsu ;P)14:16
*** kevzha01 has joined #openstack-meeting14:16
hoppalmwoohooo!!!14:16
rhochmuththis looks really exciting14:16
*** qwebirc94930 has joined #openstack-meeting14:16
kornicaand in overall figured that we want to get on board with y'all :D14:17
rhochmuthi see timothyb89 has been working on it14:17
kornicafor now we've just have mainly #121 (log-pipeline extension)14:17
kornicacouple of ideas14:17
rhochmuthwitek gave me a heads-up last week14:17
kornicaso I am sure he might have mentioned that we want to contribute to monasca-helm as well ?14:18
*** links has quit IRC14:18
rhochmuthsounds good14:18
kornicayeah, it's just helm is much tougher nut to crack :D14:18
*** xyang1 has joined #openstack-meeting14:19
hoppalmif you need any help or want us to walk you through it we would be happy to14:19
kornicawell, at leat today, was first time I sat and tried to write sth...ended up trying something already there14:19
kornicawe've got a gist list of activites/features/changes we would like to apply to monasca-docker14:19
kornicabut we're still consolidating that internally14:20
kornicathose would be the things we consider important to have but shouldn't conflict too much with your idea14:20
kornica*idea14:20
kornicahoppalm: thx - for start a reviews of images I've written would be great14:20
*** Mutter has joined #openstack-meeting14:20
hoppalmyes we can do that14:20
*** mtanino_ has joined #openstack-meeting14:21
hoppalmwe will look at the two docker prs14:21
kornicathere is one breaking point there, but I've put that point into comments under #12114:21
scI did some test with odcker14:21
hoppalmyes travis always lacks behind on docker version14:21
scI changed the order of box creation14:21
hoppalmwe can try to manually upgrade it14:21
hoppalmwe have been thinking about switching to multistage build14:22
hoppalmfor some of our stuff14:22
kornicahoppalm: actually I was referring to the kafka topics creation (my idea was to make log-pipeline an extension without affecting docker-compose.yml which in overall is metric pipeline)14:22
kornicahoppalm: I already have this for kibana (but as you saw it requires newer docker)14:23
hoppalmohhh okay yes I will go through it with Tim and we will review it14:23
*** qwebirc94930 has quit IRC14:23
kornicahoppalm: big thumb up and high five :D14:23
kornicasc: what about box order ?14:24
sckornica: I changed the order in docker-compose14:24
kornicayou have any code ? at least me - well I am not sure I understand what that means :D14:25
scI just put mysql up, it looks to me it speads up setup14:25
sckornica: OK, I'll share ASAP14:25
kornicaah ok :)14:26
hoppalmprobably did as multiple things need to talk to it so the sooner it comes up the better, and please put up any changes you think are good14:26
hoppalmand we will look14:26
kornicasure14:26
kornicaok, I think I've exhausted the topic - nice to see that you're happy with that contribution14:27
kornicaI have one openstack-reviews item in my agenda, that I did not post but figured now it is worth discussing14:28
kornicaunless someone has anything to add about sth else, I could just elaborate on that14:29
rhochmuthyou have the floor14:29
*** frank_young has quit IRC14:30
*** Mutter has quit IRC14:30
kornicathe changes I wanted to mentioned are about inhibit,silencing and grouping14:30
rhochmuthoh14:31
kornicaI had to -2 one of them as it would break the CI14:31
kornicabut apperently there is now nobody who would adress that :/14:31
kornicaI mean, is that really that bad of situation from HPE side that such promissing features are left behind ;-(14:31
kornica?14:31
rhochmuthwe haven't left it behind14:32
kornicasimilar comments goes to monasca-agent mods that, for example https://review.openstack.org/#/c/448895/14:32
*** tobberydberg has quit IRC14:32
kornicaoh...I mean, as reviewer, I am not quite sure what else apart from pinging owner we could do14:32
kornica-2 is pretty strong, but breaking CI was never sth that we were accepting14:33
*** zengyingzhe has joined #openstack-meeting14:33
*** tobberydberg has joined #openstack-meeting14:33
*** Mutter has joined #openstack-meeting14:33
*** annegentle has joined #openstack-meeting14:34
hoppalmwe are planning on finishing it as it is a feature important to us we want14:34
kornicait's just the time ?14:34
rhochmuthandrea has been out?14:34
rhochmuthso, we are trying to figure out how to address/load-balance this on the team14:34
kornicawell, 've given this -2 over 2 weeks from now14:34
*** marst has joined #openstack-meeting14:35
*** frank_young has joined #openstack-meeting14:35
kornicaI mean, please don't get me wrong or anything like that - just trying to finally understand what should we expect in upstream14:35
rhochmuth not sure how to address right now as the developer is not around14:37
rhochmuthso, we've been trying to address this14:37
*** tobberydberg has quit IRC14:37
kornicamaybe someone (you, I believe would be the best guy) or someone else, could just go through open changes14:38
kornicaabandon what is really not needed14:38
kornicamark needed changes with -1@W14:38
*** Sukhdev has joined #openstack-meeting14:39
rhochmuthyeah, we had talked about that a few months ago14:39
rhochmuthbut, i wouldn't abandon these changes14:39
*** gyee has joined #openstack-meeting14:39
rhochmuthfor alarm inhibition, silencing, ...14:39
*** frank_young has quit IRC14:40
kornicathat's out of a question - those should be left for future work14:40
kornicawhat about agent mods around container monitoring ?14:40
*** dsantoro has joined #openstack-meeting14:41
rhochmuthhttps://review.openstack.org/#/c/448895/14:41
*** elynn has joined #openstack-meeting14:41
hoppalmso i need to go through them again14:41
kornicahoppalm: thx14:42
hoppalmit was during the time when we were trying to learn what we want for kubernetes monitoring14:42
*** tobberydberg has joined #openstack-meeting14:42
kornicamight be that now, that I finally have k8s and docker functional at my workstatation (finally off the proxy hook, yeah)14:42
kornicaI will be able to properly test those14:42
hoppalmsweeet :) if you see gaps in our container monitoring let us know as well14:43
kornicasure :D14:43
kornicathe only thing I would most certainly need would have them rebased by author :D14:43
kornicalater hopefully I will be smart enough to understand them and test them14:43
kornica:D14:43
hoppalm:)14:44
rhochmuthbtw, on another topic, has anyone from fujitsu thought about, https://www.netways.de/nocache/en/events/osmc/cfp/14:44
rhochmuthdeadline is uly 31st14:44
kornicaBTW: I've noticed that in helm repo you;ve been referring to minikube14:44
kornicahaving that said - https://github.com/kornicameister/journeys/tree/master/kubernetes/scripts14:44
kornicathose might be come in handy for you ;-)14:44
kornicathat;s for kubeadm14:45
kornicarhochmuth: I will ping rest of my team14:45
kornicarhochmuth: thx14:45
rhochmuththx kornica14:46
rhochmuthi need to run to another meeting right now14:46
rhochmuthi know weird time14:46
hoppalmoh sweet14:46
kornicahoppalm: kubeadm scripts ?14:46
rhochmuthcan someone end the meeting when done14:46
*** radeks has quit IRC14:46
*** rhochmuth has left #openstack-meeting14:47
hoppalmoyeah14:47
kornicaI think someone should know how :D14:47
*** Manuel_112 has quit IRC14:48
hoppalmanything else from anyone?14:48
kornicahoppalm: I am using those everyday since I wrote them (or rather reforged knowledge of my collegue associated with kubernetes-dashboard project :D)14:48
*** tobberydberg has quit IRC14:48
kornicahoppalm: so they should be fine enough14:48
kornicahoppalm: from my side - no14:48
hoppalmcool anyone else or good to end meeting?14:48
hoppalmill take that as a no14:49
hoppalm#endmeeting14:49
kornicait's a trap14:49
hoppalmdangit whats the exact command :)14:50
kornica#endmeeting14:50
kornicathat should be it14:50
kornicawitek used that last time :D14:50
*** dpertin has joined #openstack-meeting14:50
hoppalm#end-meeting14:50
hoppalm:)14:50
kornicajust copied and pasted here14:50
hoppalmhoepfully it doesnt require roland to do it14:50
kornicarotfl....14:50
*** haru_ has quit IRC14:51
hoppalmlet me send him a pm14:51
kornicahmmm....ok...so how many developers you need to end the meeting14:51
*** Mutter has quit IRC14:51
rbrndtn+1 developers14:51
kornica#endmeeting14:53
kornicaok, this has to be the correct command14:53
*** rhochmuth has joined #openstack-meeting14:53
kornicajust checked other meeting logs14:53
kornicaI am out of juice to end meeting ;/14:53
rhochmuth#endmeeting14:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:53
openstackMeeting ended Wed Jul 19 14:53:36 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-07-19-14.00.html14:53
kornicavoila14:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-07-19-14.00.txt14:53
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-07-19-14.00.log.html14:53
*** rhochmuth has quit IRC14:53
*** koji has quit IRC14:53
*** qwebirc52135 has joined #openstack-meeting14:53
kornicacya14:54
*** kgiusti has joined #openstack-meeting14:54
kornicahoppalm: thx once again and if you will run kubeadm - good luck ;-)14:54
*** martial_ has quit IRC14:55
*** rossella_ has joined #openstack-meeting14:55
*** rossella_s has quit IRC14:56
*** ansmith has joined #openstack-meeting14:57
*** ArturoM has joined #openstack-meeting14:57
*** maeca has quit IRC14:58
*** shinya_kwbt has left #openstack-meeting14:58
*** iyamahat has joined #openstack-meeting14:59
*** Fdaisuke has quit IRC14:59
*** galstrom_zzz is now known as galstrom15:00
*** kornica has quit IRC15:00
ad_rien_#startmeeting massively_distributed_clouds15:00
openstackMeeting started Wed Jul 19 15:00:48 2017 UTC and is due to finish in 60 minutes.  The chair is ad_rien_. 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
ad_rien_#chair ad_rien_15:01
openstackCurrent chairs: ad_rien_15:01
*** donghao has joined #openstack-meeting15:01
*** qwebirc52135 has quit IRC15:01
jamemccHello15:01
ad_rien_#topic roll call15:02
*** openstack changes topic to "roll call (Meeting topic: massively_distributed_clouds)"15:02
ad_rien_Hi folks, please remind to add you nick in the pad15:02
ad_rien_#link https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017  agenda line 92415:02
ad_rien_so I don't know how many guys will attend today the meeting. From Inria we are only me and dpertin if I'm right15:03
*** parus has joined #openstack-meeting15:03
ad_rien_#chair parus15:03
openstackCurrent chairs: ad_rien_ parus15:03
*** janki has quit IRC15:03
*** mriedem_meeting is now known as mriedem15:03
ad_rien_ok so let's start15:04
*** pbressan has joined #openstack-meeting15:04
ad_rien_#topic announcements15:04
*** openstack changes topic to "announcements (Meeting topic: massively_distributed_clouds)"15:04
ad_rien_I added a couple of information in the pad.15:04
ad_rien_Regarding the sydney submissions, I am aware of three proposals15:04
ad_rien_is there any other?15:04
jamemccI added that there is one from LCOO as well15:05
parusI also made a proposals about use cases.15:05
*** rhochmuth has joined #openstack-meeting15:05
parusI have not heard back15:05
ad_rien_ok sorry jamemcc (I just saw that now)15:05
jamemccI know that this question/overlap of the LCOO work on Extreme Testing had come up here before15:05
jamemccSo I just added those links as well15:05
*** electrofelix has quit IRC15:05
ad_rien_great thanks15:06
*** electrofelix has joined #openstack-meeting15:06
*** rhochmuth has left #openstack-meeting15:06
jamemccWhen we can get either SamP or Gautam Divgi here - would be a better time for Q&A15:06
ad_rien_ok15:06
jamemccI'll work on that and getting it into the main agenda ahead of time15:06
ad_rien_thanks15:06
ad_rien_can you please add an action in the pad ;)15:07
ad_rien_thanks15:07
ad_rien_So regarding the first cross WG meeting.15:07
ad_rien_it took place this morning (quite early or quite lately depending where you are worldwide :-P)15:07
*** andreas-f has joined #openstack-meeting15:07
jamemccYes - I feel badly for not getting to it after working to set it up15:08
ad_rien_While we didn't define any concrete action, I think it is a good way to share information between WGs/teams15:08
*** psachin has quit IRC15:08
jamemccBut you and the other 2 WG Chairs and UC lead MRHillsman really did a great example of what it can be like15:08
ad_rien_For instance, the Scientific WG is intensively working on Federation issue15:08
* ad_rien_ is looking for the URL15:08
*** kevzha01 has quit IRC15:08
ad_rien_#link https://review.openstack.org/#/c/400738/3/user-stories/proposed/federated-identity.rst Federation use-case described by Scientific WG15:09
*** alisanhaji has joined #openstack-meeting15:09
*** rbartal_ has quit IRC15:09
*** yamamoto has joined #openstack-meeting15:09
*** dsantoro has quit IRC15:11
ad_rien_the UC opened a new irc chat room where you can ask any kind of questions.15:11
*** dsantoro has joined #openstack-meeting15:11
ad_rien_so do not hesitate to join this channel if you want further information15:11
ad_rien_Last but not the least, We talked a few weeks ago about a possible opendev event next september. I received an email two days ago about the foundation15:12
ad_rien_(I put information within the pad, line 952)15:12
mrhillsmanthat channel is #openstack-uc btw :)15:12
ad_rien_So this is not an open event like the summit but if you are interested by attending it. Please put your name/email in the pad. I should forward those emails to the foundation.15:13
ad_rien_mrhillsman:  thanks15:13
ad_rien_it is in the pad ;)15:13
mrhillsmanaha :)15:13
*** kevzha01 has joined #openstack-meeting15:13
ad_rien_From Inria, we will try to send one or two persons at least (we are currently checking who is available)15:13
*** frank_young has joined #openstack-meeting15:13
ad_rien_that's all for the announcement from my side.15:14
ad_rien_Any news/comments from your side guys?15:14
jamemccThis seems to me to be related to the Use Case discussion15:14
*** maeca has joined #openstack-meeting15:14
parusjamemcc: what is related to Use Case?15:15
jamemccI had a verbal conversation with Kandan of AT&T who indicated that a significant part of that conference will be to go through various Use Cases15:15
ad_rien_jamemcc:  Yes at the first sight but actually if you dive into details it seems that they want to have technical and specific discussions.15:15
jamemccRElated to: https://docs.google.com/presentation/d/1sBczuC2Wu1d_misBmPahLPdvyhOI4QuVy129EHunuUM/edit?usp=sharing15:15
parusjamecc: Will Kandan be at the opendev event?15:16
*** yamahata has joined #openstack-meeting15:16
ad_rien_he is in the PC.15:16
ad_rien_If I'm correct.15:16
jamemcc@parus - the conference in September:  http://www.opendevconf.com/15:16
jamemccYes15:16
jamemccYes - he is in the PC15:16
ad_rien_Can we move to the next topic (unless there is other news to share)?15:17
parusOK! I will plan to attend.15:17
mrhillsmanagree with ad_rien_ from my discussion with Lauren Sell, it will be focused on what work to do for edge/fog in open tech and i assume who will do what15:17
*** felipemonteiro_ has quit IRC15:18
ad_rien_so next topic :) (sorry but the more time we have for discussing on-going actions, the better it is ;))15:18
ad_rien_?15:18
mrhillsman++15:19
ad_rien_#topic on-going action: AMP alternatives15:19
*** openstack changes topic to "on-going action: AMP alternatives (Meeting topic: massively_distributed_clouds)"15:19
kgiustihey15:19
ad_rien_ansmith:  kgiusti:15:19
ad_rien_:)15:19
ad_rien_thanks15:19
*** yamamoto has quit IRC15:19
kgiustislow progress - some external issues (customers, bugs etc)15:19
kgiustiupdated epad.  Still 2 outstanding kolla-ansible reviews15:20
kgiustibut not much else to report.15:20
kgiustiansmith: anything I missed?15:20
ansmiththat is it15:20
ad_rien_ok from Inria, Matthieu is on vacations. He sent me an email this morning, telling me that he will spend some times on synchronizing enos with the kolla master after August, the 15th.15:21
ad_rien_so nothing more from our side too15:21
kgiusti8/15 - understood, thanks.15:21
ad_rien_if there is nothing to add let's move to  Cockroach15:21
kgiusti+115:22
ad_rien_#topic on-going action: cockroachDB15:22
*** openstack changes topic to "on-going action: cockroachDB (Meeting topic: massively_distributed_clouds)"15:22
ad_rien_So we made concrete actions from our side that enabled us to unfortunately discover lot of issues regarding the compliance between cockroach and SQLalchemy15:23
*** kevzha01 has quit IRC15:23
parusad_rien_: Have you documented those issues somewhere?15:24
ad_rien_Ronan and Antoine are offline today but basically they faced a lot of issue that prevents OpenStack to use directly sqlachemy on top of cockroach. They should make a point with cockroach folks by beginning of august15:24
ad_rien_Ronan is working on a long email If I correctly understood. He wants to send this email and arrange another meeting with the cockroach guys15:25
ad_rien_they suceeded to start a keystone on top of cockroach but they had to do a lot of hack to do it15:25
ad_rien_that's all15:26
ad_rien_unless there are questions/remarks, we can move to the next topic?15:26
ad_rien_seems we can :)15:27
ad_rien_#topic on-going action: use-case specifications15:28
*** openstack changes topic to "on-going action: use-case specifications (Meeting topic: massively_distributed_clouds)"15:28
parusWe have made good progress on  use cases. I have updated the slides per my action.15:28
ad_rien_thanks parus15:28
parusAnd we received a great deck from Daniele.15:28
ad_rien_I went through the two presentations and I put some comments from my side15:28
ad_rien_maybe we can go through them shortly15:29
parusPlease.15:29
ad_rien_we can spend 15 min on this action if everyone agrees?15:29
dsantorook for me15:29
ad_rien_so let's start with the FBK presentation15:29
ad_rien_#link  https://docs.google.com/presentation/d/1FLCjUx1xiQxRcgTG78vg255g6N2RRp8_W0B0Sz0bJH8/edit#slide=id.p4615:29
dsantoro@ad_rien_: I ve jsut replied to comments but if you have any other question or details I am here15:30
ad_rien_so first of all thanks dsantoro for those slides15:30
ad_rien_quite helpfull15:30
ad_rien_so in the first use case.15:30
ad_rien_Slide 1015:30
ad_rien_you do not use Compute 1 and 215:31
ad_rien_you put them just to because they are there but they are not used. Did I understand correctly ?15:31
dsantorono this is a baseline use-case and we need it mostly to be able to do a comparison between15:31
dsantorohaving application on the cloud VS having them on the edge15:31
ad_rien_ok15:31
ad_rien_so in this baseline use-case everything is executed in the cloud15:32
dsantoroin that UC1 we just put application on compute 0 which is located somewhere in the cloud15:32
ad_rien_right?15:32
*** gcb has joined #openstack-meeting15:32
ad_rien_ok15:32
dsantoroand is charaterized by low bandwidth and high latency15:32
dsantoroyes you are right15:32
ad_rien_ok15:32
*** Alex_Staf has quit IRC15:32
*** rbrndt has left #openstack-meeting15:33
ad_rien_thanks regarding low bandwidth (and actually this is also a question I have for parus). Once you are in the backhaul, the bandwith is generally large.15:33
ad_rien_(it depends obviously if you have a DSL connexion or a fiber one)15:33
ad_rien_so maybe it would be usefull to mention what kind of connexions you have between Compute 1/2 and Compute 015:34
dsantoroI agree, we can specify it. We suppose to have a WANWide connection between those computes15:35
ad_rien_yes but WANwide means so many things15:35
*** alisanhaji has quit IRC15:35
ad_rien_if you are an operator (a telco)15:35
dsantoroin the links we put just some example of bandwidth in Mbit15:35
ad_rien_once you are in the backhaul the bandwidth is rather 10gbps (and sometimes even more)15:35
parusad_rien_: I do not have precise data on backhaul BW. But sometimes it is scarce.15:36
ad_rien_if you are an end-users we a xDSL connexion, you're right having a couple of Mbits is the maximum you can have15:36
ad_rien_parus:  +1,  that's why we should clarify that point I think15:36
dsantoroI agree but I think it also depends on the kind of connection that the infrastructure provider has towards the backhaul. right ?15:37
ad_rien_yes15:37
ad_rien_so it is better to specify it. some people also consider that edge devices will be connected through WIFI connexions to fiber POPs15:37
parusIt depends on the Backhaul Technology. It depends if the operator owns the backhaul or needs to lease it.15:37
*** annabelleB has joined #openstack-meeting15:37
ad_rien_(POP, network point of presence)15:37
ad_rien_exactly15:37
*** Apoorva has joined #openstack-meeting15:38
ad_rien_don't get me wrong, I didn't say you are wrong, just say that we should explain that.15:38
ad_rien_that, i.e. these differences viewpoint.15:38
ad_rien_s/differences/different15:38
ad_rien_sorry15:38
parusPoint Taken!15:38
*** chyka has joined #openstack-meeting15:38
*** Apoorva_ has joined #openstack-meeting15:38
ad_rien_ok I do not have additional remarks on those first slides from my side.15:39
*** Sukhdev_ has joined #openstack-meeting15:39
ad_rien_does anyone want to add something?15:39
ad_rien_… yes, dsantoro I forgot to mention that it would be nice that you explain why you are leveraging OpenStack15:39
*** anilvenkata has quit IRC15:39
dsantorowe envision a scenario in which the municipality is the infrastructure owner (owner of the sensor network) so the bandwidth depends on the type of connection it has with the rest of the world15:39
ad_rien_and not simply k8S15:39
dsantorook15:40
parusThere are a number of things identified in slide 1515:40
jamemccI can speak to backhaul from the large mobile provider point of view in general15:40
dsantorowe can add a slide pointing this out15:40
*** gyee has quit IRC15:40
ad_rien_you already explained me in a previous exchange but I think it would be valuable for everyone to know why15:40
ad_rien_thanks15:40
ad_rien_jamemcc:  I think it would be great if you can work with parus on one dedicated slide to explain the different viewpoints for the network bandwidth/latency challenges15:41
dsantoro@parus: https://github.com/cockroachdb/cockroachvation on slide 15 but we could add other if valuable15:41
*** frank_young has quit IRC15:41
parus#action jamecc and parus to work on a Backhaul slide15:41
dsantoro@parus: yes we added some motivation on slide 15 but we could add other if valuable15:42
*** Apoorva has quit IRC15:42
*** gyee has joined #openstack-meeting15:42
ad_rien_ok let's move to the second deck15:42
ad_rien_ok ?15:42
dsantorook15:42
parusok?15:42
ad_rien_#link 1sBczuC2Wu1d_misBmPahLPdvyhOI4QuVy129EHunuUM15:42
ad_rien_sorry my bad15:43
ad_rien_#link https://docs.google.com/presentation/d/1sBczuC2Wu1d_misBmPahLPdvyhOI4QuVy129EHunuUM/edit?usp=sharing use-case slides15:43
ad_rien_so my comments on slide 5 and 6 will be addressed ;) so no need to discuss them15:44
ad_rien_Slide 11.15:44
*** oidgar has quit IRC15:44
ad_rien_I think we can add one item regarding network partitionnng issue15:44
parusWhat do you mean?15:44
ad_rien_what does happen if we lose the connexion between some control services and compute nodes?15:44
*** Manuel_112 has joined #openstack-meeting15:45
ad_rien_if the disconnection lasts a couple of seconds/minutes this should be ok15:45
ad_rien_for the control plane15:45
parusThat is a good point.15:45
ad_rien_but what does happen if it lasts one hour15:45
ad_rien_and obviously these questions are relevant for each of the deployment scenarios you illustrate (central control services/remote computes, regions, cells)15:46
ad_rien_(thanks BTW for the slides once again really helpful)15:46
ad_rien_Regarding the 4th question, not sure I correctly understood. Can you please elaborate a bit parus?15:46
dsantorothat is an important topic also for us. We would like to address decentralization in our UCs in the future (see FBK slide 15 point 3)15:47
parusitem 4 is about VLAN.15:47
parusDepending if we have a L2 or a L3 network implementation, the solutions to separate control, management and user traffic would be different.15:48
ad_rien_ok15:48
ad_rien_thanks15:48
ad_rien_Slide 13.15:48
ad_rien_can you clarify the relations to slicing issue?15:49
parusThere is a lot of activity around Network Slicing in particular in relation to 5G.15:49
parusNetwork slices, affect RF, RAN, Core.15:50
parusShoudl it affect Edge too?15:50
*** emagana has joined #openstack-meeting15:50
ad_rien_so it is 5G related ?15:51
parusIt is really a wireless use case question in relation to 5G.15:51
ad_rien_I mean here also if you are considering WIFI links15:51
*** frank_young has joined #openstack-meeting15:51
ad_rien_or if you consider edge clouds that are interconnected with other clouds through wired cables?15:51
*** gyee has quit IRC15:52
*** Rockyg has joined #openstack-meeting15:52
ad_rien_maybe you can put a link/reference in the slide to help the reader15:52
parusgood point.15:52
*** vishwana_ has joined #openstack-meeting15:52
dsantoroI suppose network slicing affects Edge ie: If you have many tenants running application on edge nodes and they have each one special network requirements…15:52
*** marios has quit IRC15:53
ad_rien_8 min left15:53
ad_rien_let's move to the slide 1515:53
ad_rien_I really like it :)15:53
ad_rien_I think it gives an excellent overview of all the questions we should answer.15:54
*** Manuel_112 has quit IRC15:54
parusWe also had an email exchange on things with FBK on things that might be needed from Openstack and Kubernetes.15:54
ad_rien_so a general comment. It would be great if we can have one slide for each entry15:54
*** gcb has quit IRC15:54
ad_rien_as the slide 16 for Entry 115:54
dsantoroWhy not add also storage capabilities on edge nodes on slide 15 ?15:55
ad_rien_and then we will be able to idenfity concrete actions to move forward on each entry15:55
ad_rien_we can dsantoro15:55
ad_rien_I think15:55
ad_rien_this is also a good comment15:55
*** gcb has joined #openstack-meeting15:55
ad_rien_SWIFT is distributed by default15:55
ad_rien_but deploying SWIFT on top of a fog/edge infrastructure can highlight possible issues/performance degradations ....15:56
*** vishwanathj has quit IRC15:56
ad_rien_So I think we can try to explain in details each entry and what is/are the challenges related to each one15:56
*** frank_young has quit IRC15:56
ad_rien_We already discussed with dpertin Entry 115:56
parusthis would be the goal.... Help would be welcome in expanding that.15:57
ad_rien_and we will conduct preliminary experiments to see whether there is/are real challenges or ''just'' technical issues15:57
ad_rien_parus:  I can help you by exchaning by mail15:57
ad_rien_if it can help15:57
parusGreat!15:57
*** abishop has joined #openstack-meeting15:58
*** diablo_rojo has joined #openstack-meeting15:58
ad_rien_(I will ask also one of my colleague here that can be interested to take part in this action) I will get back to you by the end of the week15:58
ad_rien_but please keep in mind that the period is not really the best one in France (summer vacations)15:58
ad_rien_ok two min left15:58
ad_rien_#topic open discussion15:58
*** openstack changes topic to "open discussion (Meeting topic: massively_distributed_clouds)"15:58
ad_rien_ok who plan to attend the sydney summit15:59
parusI will.15:59
ad_rien_from my side it is still unclear whether I can go or not15:59
ad_rien_dpertin will represent Inria15:59
dsantoroWe will be there, probably two people from FBK15:59
ad_rien_ok great16:00
*** jamesmcarthur has joined #openstack-meeting16:00
ad_rien_ok we have to end the meeting16:00
ad_rien_thanks you folks16:00
parusthx16:00
ad_rien_#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
pbressan thx16:00
openstackMeeting ended Wed Jul 19 16:00:35 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/massively_distributed_clouds/2017/massively_distributed_clouds.2017-07-19-15.00.html16:00
dsantorotnks guys see u16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/massively_distributed_clouds/2017/massively_distributed_clouds.2017-07-19-15.00.txt16:00
smcginnis#startmeeting Cinder16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/massively_distributed_clouds/2017/massively_distributed_clouds.2017-07-19-15.00.log.html16:00
*** diablo_rojo has quit IRC16:00
*** frank_young has joined #openstack-meeting16:00
openstackMeeting started Wed Jul 19 16:00:42 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
scottdahi16: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
*** parus has quit IRC16:00
SwansonHallo.16:00
*** pbressan has quit IRC16: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:01
*** caboucha has joined #openstack-meeting16:01
smcginnisviks ketonne abishop sivn16:01
tbarronhi16:01
*** diablo_rojo has joined #openstack-meeting16:01
scottdaI thought that last bit was some German or something smcginnis16:01
scottda"viks ketonne abishop sivn"16:01
smcginnisNien16:01
wiggin15Hi16:01
rajinirhi16:01
DuncanTHi16:01
smcginnisHah, does sound a little like it. :)16:01
lhx__hi all16:01
guyr-infinidathi16:02
abishopo/16:02
lpetrut_hi16:02
tommylikehuhey16:02
diablo_rojoHello16:02
zengyingzheHi16:02
jungleboyj@!16:02
_pewp_jungleboyj (=゚ω゚)ノ16:02
smcginnis#topic Announcements16:02
*** openstack changes topic to "Announcements (Meeting topic: Cinder)"16:02
smcginnisThe usual...16:03
smcginnis#link https://etherpad.openstack.org/p/cinder-spec-review-tracking Review focus16:03
smcginnisI need to go through and update the approved specs there.16:03
smcginnisWe've been able to get a few more through.16:03
smcginnisNext week is Pike-3, so there are probably some that we can revert or move to the queens folder.16:04
*** aarefiev is now known as aarefiev_afk16:04
smcginnisTomorrow is non-client library freeze.16:04
smcginnisBarring anything major cropping up with os-brick, we should be all set there now with 1.15.1.16:04
*** ArturoM has quit IRC16:05
smcginnis#link https://etherpad.openstack.org/p/cinder-ptg-queens Planning etherpad for PTG16:05
*** wxy- has joined #openstack-meeting16:05
smcginnisIf you have any topics for the PTG, please add them to the etherpad.16:05
*** felipemonteiro has joined #openstack-meeting16:05
smcginnisWhether you are physically able to attend or not.16:05
*** Apoorva_ has quit IRC16:05
smcginnisWe will hopefully stream the sessions for anyone unable to attend.16:06
*** sridhar_ram has quit IRC16:06
smcginnisAnd if you have a topic that requires your participation, we can try to get two way communication going with hangouts or something.16:06
*** fzdarsky has quit IRC16:06
smcginnisOr Duo or whatever it's called now. :)16:06
*** felipemonteiro_ has joined #openstack-meeting16:07
*** trinaths has joined #openstack-meeting16:07
smcginnisIf you are able to attend in person, please register so they can start getting a feel for numbers.16:07
smcginnis#link https://www.eventbrite.com/e/project-teams-gathering-denver-2017-tickets-33219389087 PTG registration16:07
smcginnisAnd if you need it, look in to the travel support program.16:07
*** fzdarsky has joined #openstack-meeting16:08
jungleboyjsmcginnis:  Does registration close at some point?16:08
*** anilvenkata has joined #openstack-meeting16:08
smcginnisjungleboyj: I think they closed it just a day or two before last time. Not entirely sure.16:08
jungleboyjsmcginnis:  Ok, good.  I have people dragging their feet.  :-)16:08
smcginnisTell them the deadline is Friday then. :)16:08
*** donghao has quit IRC16:09
*** rcernin has quit IRC16:09
jungleboyjAye aye captain.16:09
smcginnis#topic Documentation migration update16:09
*** openstack changes topic to "Documentation migration update (Meeting topic: Cinder)"16:09
*** elynn has quit IRC16:09
*** jamesmcarthur has quit IRC16:09
jungleboyjHey.16:09
smcginnisjungleboyj: Captian Docs? Doctor Docs? We need another name for you.16:09
jungleboyjSo, just wanted to update people on progress.16:09
jungleboyjsmcginnis:  I will leave that up to you.  ;-)16:10
tommylikehu:)16:10
smcginnisDocMan16:10
* jgriffith picks up his feet16:10
jungleboyjSo, thank you to those who are helping reviews and thanks to tommylikehu  for pitching in.16:10
jungleboyjI have all the trivial changes going in under the doc-bld-fix topic.16:10
tommylikehujungleboyj:  np16:10
jungleboyjThe sooner we get that stuff merged the sooner I can be done.  :-)16:11
*** felipemonteiro has quit IRC16:11
*** Apoorva has joined #openstack-meeting16:11
jungleboyjI have one more large patch coming today that will move existing content to the right places based on the migration plan:  http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html#proposed-change16:11
jungleboyjThe patch adds a template for how everything should look and has README.rts in each directory to describe appropriate content.16:12
SwansonDocboyJ16:12
smcginnis#link https://review.openstack.org/#/q/project:openstack/cinder+topic:doc-bld-fix+status:open16:12
jungleboyjericyoung:  And I had a good chat with Doug yesterday and he is working on some automation improvements for Cinder but they are still future work.16:12
jungleboyjSo, at this point please remember that any changes to configuration items or functionality will need an associated doc change.16:13
smcginnis++16:13
smcginnisNo more DocImpact tag. If you have a DocImpact, doc it.16:13
jungleboyjWe will talk about making the docs look decent at some point in the future.  They are an ugly mess, but at least we can get the content there.16:13
jungleboyjsmcginnis:  ++16:13
jungleboyjThat was all I had.  Cores, just please help me get the bld fixes in place.16:14
jungleboyjThey are easy reviews.16:14
smcginnisjungleboyj: Thanks for working on that. You too tommylikehu16:14
smcginnis#topic max_over_subscription_ratio: the ratio between total capacities or free capacities16:15
*** openstack changes topic to "max_over_subscription_ratio: the ratio between total capacities or free capacities (Meeting topic: Cinder)"16:15
jungleboyjsmcginnis:  Welcome.  Something I am passionate about.  Just wish the doc build didn't take forever to do.16:15
smcginniswiggin15: You're up.16:15
wiggin15Thanks16:15
smcginnis#link https://bugs.launchpad.net/cinder/+bug/170478616:15
openstackLaunchpad bug 1704786 in Cinder "CapacityFilter calculates free virtual capacity incorrectly" [Undecided,Opinion] - Assigned to Arnon Yaari (arnony)16:15
wiggin15Regarding the configuration value max_over_subscription_ratio. I noticed there is a bit of inconsistency in the code.16:15
lhx__jungleboyj, what's the mean of BLD?16:15
wiggin15Parts of the code treat this value as the ratio between the _total_ physical capacity and total virtual capacity (e.g. caculate_virtual_free_capacity)16:16
wiggin15(where physical is data you can write and virtual is data you can allocate, when using thin provisioning with oversubscription)16:16
wiggin15Other parts of the code treat it as the ratio between the _free_ physical capacity and free virtual capacity (e.g. CapacityFilter.backend_passes and some volume drivers).16:16
tommylikehubuild?16:16
jungleboyjlhx__:  Build ... they are fixes to correct WARNINGS in the build.16:16
lhx__thanks , very clear16:16
wiggin15The issue is that the ratio between the "free" capacities is not constant because they are not directly related. So the way I see it, what the drivers and CapacityFilter calculate is not accurate.16:16
wiggin15I opened a bug about this but there was disagreement about what the value means.16:17
wiggin15I wanted to hear your input...16:17
smcginniswiggin15: My understanding was it was supposed to be the second one you described.16:17
smcginnisxyang1: You introduced this in Kilo, right?16:18
xyang1smcginnis: yes16:18
wiggin15Most of the code uses caculate_virtual_free_capacity (the first one)16:18
wiggin15and the second one can be inconsistent16:18
xyang1smcginnis: we had lots of discussions on this over the years:)16:18
xyang1smcginnis: the current code is after some discussion in the reviews16:18
geguileoAnd the first one (that uses the method) is *wrong*16:18
*** annegentle has quit IRC16:19
wiggin15umm, I'm not sure it is16:19
geguileomethod just doesn't calculate % correctly16:19
xyang1smcginnis: I have to spend some time and find the patch that adds this change16:19
xyang1smcginnis: not just the initial patch16:19
geguileowell, you do the percentage of the physical total and then decrement it from the virtual16:19
smcginnis#link http://specs.openstack.org/openstack/cinder-specs/specs/kilo/over-subscription-in-thin-provisioning.html Original spec16:19
patrickeast^ a bunch has shifted around since then iirc16:20
xyang1In summary this is a safer way to evaluate after some review discussion16:20
xyang1smcginnis: there is another patch after that16:20
xyang1smcginnis: I don't have it now16:20
geguileoxyang1: how is it correct to decrease the reserved based on the real total from the virtual total?16:20
xyang1smcginnis: will find it and reference in the patch16:21
xyang1geguileo: I need to find that patch16:21
geguileoxyang1: ok16:21
geguileobut in my mind is simple16:21
geguileoreserved must be calculated either from total and then that space is not used to calculate the virtual16:21
wiggin15<geguileo> even if we need to decrease reserved from total.. that doesn't answer the question16:21
xyang1geguileo: unfortunately this has always been controversial16:21
wiggin15I'm not asking about reserved. I'm asking about the ratio16:22
geguileoor is reserved from the virtual total directly16:22
geguileowiggin15: and I'm saying that the method in question you referenced is *wrong*16:22
wiggin15so let's say for the sake of the discussion that reserved should be from the virtual total16:22
wiggin15let's also drop the specific method that calculates it16:22
*** caboucha has quit IRC16:22
jgriffithwiggin15 but what if that's infinite :)16:23
wiggin15when we do calculate the virtual capacity - do we take the total physical and multiply it by the ratio?16:23
wiggin15jgriffith there is a default of 20, even if it is infinite16:23
*** annabelleB has quit IRC16:23
*** frank_young has quit IRC16:23
*** rcernin has joined #openstack-meeting16:23
*** bobh has quit IRC16:24
xyang1wiggin15: if it is infinite it does not matter what the ratio is16:24
geguileowiggin15: that's the over subscription, not the total capacity, right?16:24
jgriffithwiggin15 sorry, I'll refrain from my historical comments and why I think that sucks16:24
xyang1It always passes16:24
wiggin15A key question (from the bug report) is this: if we have 1 TB physical capacity and 1.2 TB virtual capacity, and we provisio and write 1 TB - should we allow creation? We can't *write* any more but maybe we can *provision* because we have more virtual capacity... CapacityFilter currently doesn't pass in this case.16:24
jgriffithwe've made this way more complex and difficult than it needs to be.16:24
smcginnisjgriffith: You're referring to the array capacty, not the ratio, right?16:24
jgriffithsmcginnis correct16:24
*** rwsu has quit IRC16:24
*** ad_rien_ has quit IRC16:25
jgriffithsmcginnis was going to go back to the "just report actual capacity" and deal with over-subscription and quit screwing around with so many "virtual" numbers that are all dependent and variable16:25
wiggin15jgriffith when you deal with totals then the numbers aren't variable, and when you deal with used or free then they are. That's the problem16:26
smcginnisjgriffith: Well, yeah. But I know one array very well that really has no good number for "actual capacity", because there are too many variables that go in to determining that.16:26
jungleboyjjgriffith:  It seems that making this less complex is better and less likely to cause issues.16:26
geguileoif you don't have free space, why keep allowing the creation of volumes just because the over-subscription ration allows it?16:26
geguileowould be the counter argument16:27
*** arnewiebalck_ has joined #openstack-meeting16:27
jgriffithgeguileo I agree with that 100%16:27
patrickeastgeguileo: space can be added or recolaimed16:27
jungleboyjgeguileo:  :-)  That makes sense to me.16:27
patrickeastreclaimed even16:27
wiggin15geguileo because that's always the case in over probisioning16:27
geguileopatrickeast: then it would be reported as free again, right?16:27
wiggin15if you have 1 TB physical and ratio of 20 then you can create a 20 TB volume even if you don't have space to write16:27
patrickeastyea but like after it is provisioned16:27
patrickeastbut before data is written16:28
geguileopatrickeast: or you mean that it's being reported as full, but if I create a volume it will reclaim space and say that it's no longer full?16:28
wiggin15that sounds right16:28
geguileopatrickeast: to me that doesn't make sense16:29
patrickeastgeguileo: so like, the array is full (and for whatever reason the scheduler has no better alternatives) if it can provision the volume and the volume doesn't go immediately over the edge the admin can add more space, or cleanup old stuff as needed16:29
jgriffithgeguileo I think the problem he's pointing out is that for those that do dedupe, compression etc you can easily store 2TB of data on a 1TB device16:29
geguileocreating a volume when there's no free space...16:29
*** designbybeck has joined #openstack-meeting16:29
wiggin15geguileo do you agree that in over-provisioning you can provision more data than you can write?16:29
*** rwsu has joined #openstack-meeting16:29
patrickeastits just a part of over-provisioning storage and dealing with it when the arrays get full16:29
patrickeastjgriffith: +116:29
patrickeastthats the other part of it16:30
*** bobh has joined #openstack-meeting16:30
*** maeca has quit IRC16:30
patrickeastshit, if its a copy of a volume you might put the whole 2TB into like 1K of metadata16:30
geguileojgriffith: and that's ok with over provisioning now, it's not a problem16:30
jgriffithand in turn, even though my 1TB device has 2TB's of "data" on it, I may very well still be able to store another 2TB's16:30
geguileojgriffith: as long as you have free space >= requested * max_over_provisioning16:30
wiggin15If you have 1 TB physical and 1.2 ratio, you write 900 GB. Now you can create a 100GB * 1.2  = 120 GB volume (whatever that number means). That means you will still provision MORE than you can write16:30
* jungleboyj 's head explodes16:31
wiggin15because that's what the feature means!16:31
jgriffithwiggin15 don't have to yell :)16:31
wiggin15geguileo wrong...16:31
wiggin15sorry :)16:31
xyang1jungleboyj: I'll send you a review links with more calculations for you to enjoy:)16:32
jgriffithwiggin15 I'm just kidding, I'm the resident "yeller" here ;)16:32
smcginnisjgriffith: WHAT?16:32
jungleboyjxyang1:  No thank you.16:32
jgriffithsmcginnis YOU HEARD ME!!!!16:32
wiggin15So..16:32
*** fzdarsky is now known as fzdarsky|afk16:32
jungleboyj@!h16:32
_pewp_jungleboyj (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. )16:32
patrickeastxyang1: maybe thats what we need, is for some documentation that shows how all the math works today and what is expected behaviors/use-cases16:32
patrickeastinstead of knowledge buried into reviews16:33
jungleboyjpatrickeast:  Not an all bad idea.16:33
wiggin15like I said, I looked at the code and current behavior is not consistent16:33
xyang1patrickeast: sure, let me dig something out:)16:33
patrickeastthen we can take a look at it and decide if it is actually what we need16:33
smcginnisSince there's inconsistency between drivers, I do think that's a sign we need to better document expectations here.16:33
jungleboyjWould go into doc/source/user or doc/source/reference16:33
geguileothis is pretty easy, let's vote if we want to change it from free to the normal overprovisioning mechanism16:33
smcginniswiggin15: +1 - it should at least be consistent.16:33
*** frank_young has joined #openstack-meeting16:33
*** Patifa has joined #openstack-meeting16:33
wiggin15Do we agree that over-provisioning means you can provision more capacity than we can write?16:33
geguileoI'm OK with changing it, but what about backward compativility? Do we care?16:33
smcginnisConsistently right would be best, but consistently wrong is maybe a little better than inconsistently wrong.16:34
geguileopeople may be expecting Cinder to work as it was16:34
xyang1geguileo: I disagree with a vote16:34
xyang1geguileo: this needs more thoughts16:34
*** david-lyle has quit IRC16:34
*** tobberydberg has joined #openstack-meeting16:34
smcginnisDocument expectations, fix inconsistent behavior, release note upgrade impacts for those that are "fixed" at least.16:35
geguileoxyang1: ok, I have already thought about this when reading the bug and the patch16:35
wiggin15Before we move maybe I can get thoughts on the question  from above. Let me repeat16:35
*** kgiusti has left #openstack-meeting16:35
geguileoxyang1: so I'm ok with people having time to do as well16:35
wiggin15if we have 1 TB physical capacity and 1.2 TB virtual capacity, and we provisio and write 1 TB - should we allow creation? We can't write any more but maybe we can provision because we have more virtual capacity... CapacityFilter currently doesn't pass in this case.16:35
patrickeastsmcginnis: +1, lets do that16:35
xyang1geguileo: that's just you, not everyone who votes have already thought about it16:35
xyang1geguileo: I just saw it a few minutes before the meeting16:36
smcginniswiggin15: Yes, if that's what they have configured, I believe we should allow creation of that .2 TB more.16:36
geguileoxyang1: that's why I said I'm ok with giving time to other people16:36
xyang1geguileo: even I need to dig out the old patches16:36
geguileo;-P16:36
xyang1:)16:36
*** Apoorva has quit IRC16:37
wiggin15so.. should I bring this up next week again?16:37
*** frank_young has quit IRC16:37
geguileoI think we should agree that we have to look at it16:38
*** cloudrancher has joined #openstack-meeting16:38
geguileowho is going to be looking at this besides wiggin15 and me?16:38
smcginnisWho has an action to move this forward? xyang1 to find patches for background?16:38
wiggin15xyang1 I would really appreciate if you leave your input in the bug report16:38
xyang1I'll take a look16:38
wiggin15thanks16:38
smcginnis#action geguileo to add thoughts to bug report16:38
*** dsantoro has left #openstack-meeting16:38
xyang1smcginnis: yes16:38
*** dsantoro has joined #openstack-meeting16:38
geguileosmcginnis: I already did that!16:38
smcginnis#action xyang1 to find patches for historical reference.16:38
wiggin15geguileo already commented, we are in disagreement :)16:39
smcginnisgeguileo: Then that's an easy action item to check off. :)16:39
geguileooh, I'm ok to change it16:39
xyang1smcginnis: geguileo if we can simplify this, that will be great, but I could not get there in the past16:39
jgriffithI hate to say this... but would it be worth a new spec to try and resolve all of this again?  Or are we resolute in what we have?16:39
geguileoI was more explaining what we have and why it makes sense in a way16:39
*** tobberydberg has quit IRC16:39
geguileoxyang1: probably wiggin15 approach will simplify it16:39
smcginnisjgriffith: That may be the documentation we're looking for.16:39
xyang1jgriffith: you really think so?:)16:40
jgriffithand honestly perhaps an opportunity to discuss at PTG?16:40
smcginnisAlthough I'd like to see something in the devref.16:40
*** dsantoro has left #openstack-meeting16:40
*** dsantoro has joined #openstack-meeting16:40
smcginnisPTG discussion sounds good. I have a feeling we won't resolve all questions by then.16:40
jgriffithxyang1 I'm not a fan, but honestly we don't seem to be on the same page as a group here which is part of our problem16:40
*** dsantoro has left #openstack-meeting16:41
jgriffithanybody you ask about this seems to have a different interpretation, which explains the recurring bugs and the differences from device to device16:41
*** jamesmcarthur has joined #openstack-meeting16:41
*** dsantoro has joined #openstack-meeting16:41
guyr-infinidatCan we try just to summarize the disagreement? it is about whether the capacity filter should lo ok at the free physical capacity when over-provisioned or not?16:41
jgriffithwe may not have done a very good job of communicating/documenting this.  Maybe that's all we need is some authoritative documentation16:41
eharneythere is an existing spec on this, so it would be interesting to look through it and see if it matches what the code is doing at this point or not, and if the spec still agrees with how we think this is supposed to work16:41
*** dsantoro has left #openstack-meeting16:41
*** dsantoro has joined #openstack-meeting16:41
smcginnis[18 minutes left and two more topics on the agenda]16:42
*** dsantoro has left #openstack-meeting16:42
*** dsantoro has joined #openstack-meeting16:42
xyang1The spec was actually updated after the code was merged, but after that there are additional changes to the code16:42
*** dsantoro has left #openstack-meeting16:42
wiggin15I'm ok to move forward16:42
smcginniswiggin15: Can you add this to the PTG etherpad referenced earlier?16:43
wiggin15We'll have to continue discussion though16:43
smcginniswiggin15: Yep, agree.16:43
wiggin15I'm not sure I can attend. but ok16:43
smcginniswiggin15: We'll see how far we can get before then.16:43
wiggin15Thank you16:43
smcginnisAnd hopefully have a better common understanding by then.16:43
smcginnis#topic Where should 3rd party drivers store their private data16:43
*** openstack changes topic to "Where should 3rd party drivers store their private data (Meeting topic: Cinder)"16:43
smcginniszengyingzhe: Hi, you're up.16:44
zengyingzhesmcginnis, thanks.16:44
zengyingzhehere's the thing.16:44
zengyingzheI commited a patch for Huawei driver, which moved some driver private data from admin-metadata to the volume DB field provider_location, because non-admin user creating volume from image would fail due to not having the admin metadata access permission.16:44
smcginnis#link https://review.openstack.org/#/c/47577416:44
zengyingzhehowever, looks like there're some controversy about this change, the main question is if provider_location is a good place to store private data.16:44
zengyingzheSo I start this topic to discuss where is the proper place to record driver private data, cause we found that there're else drivers already16:45
zengyingzhe using provider_location.16:45
smcginnisAnd I think a key point is some of this is private data to the driver, not metadata for the admin.16:45
eharneyprovider_location isn't the correct place for what is being stored here16:45
eharneybut there is also some confusion, because the original bug was that non-admins can't write to where it was previously stored -- and that is usually fixed by just elevating context and then you don't have to move the data16:45
*** jamesmcarthur has quit IRC16:45
DuncanTI certainly thought this was what admin_metadata is for16:46
jgriffithzengyingzhe can you clarify *what* s in that metadata?  I was under the impression that it was lun_id and lun_wwn ?16:47
smcginnisImage data is one thing, but I believe the Huawei driver has some other internal only data it needs to store.16:47
jgriffithzengyingzhe or is it that entire list of lun_params?16:47
zengyingzhejgriffith, currently, we store LUN wwn in admin metadata.16:47
jgriffithzengyingzhe right16:48
jgriffithand that certainly fits in provider info IMO16:48
jgriffithI'm asking if there are things I'm missing here?16:48
zengyingzhejgriffith, only LUN WWN in admin metadata, no other stuff16:49
*** dpertin has quit IRC16:49
tbarronfwiw manila has "driver-private-data" - driver can return arbitrary key-values of significance only to it in this as a model update and it will be stored in DB16:49
zengyingzhebut we also store some other data in normal metadata, it may incur an issure at the circumstance backup&restore16:50
* tbarron fills in for bswartz bingo role on that one16:50
*** gcb has quit IRC16:50
smcginnistbarron: :)16:50
jgriffithzengyingzhe maybe another way of asking; can you show me what the resultant provider-info dict will look like after your change?16:50
zengyingzheSo we also move those data.16:50
eharneyis backup and restore not keeping track of some data that it should?16:50
zengyingzhejgriffith, something like this, {'lun_wwn':***, 'lun_id':***} and also other info about LUN itself.16:51
*** Manuel_112 has joined #openstack-meeting16:51
*** sshank has joined #openstack-meeting16:52
*** david-lyle has joined #openstack-meeting16:52
*** hoppalm has quit IRC16:52
*** hashar has quit IRC16:53
zengyingzheso after this change, all the private data about lun is stored in provider_location, no use admin metadata or normal metadata anymore.16:53
smcginnisI believe it's the only usable field we have for privae driver data at the moment.16:53
geguileosmcginnis: is that good enough reason to use it?16:54
jgriffithprovider_id is another one16:55
eharneydoes it fit into DriverInitiatorData at all?16:55
smcginnisgeguileo: If we don't want to expose certain data externally, I think so.16:55
zengyingzheeharney, while restoring to 3rd volume, metadata is also restored to the new created volume, but this will incur overwrite.16:55
eharneyzengyingzhe: what overwrites it?16:56
*** pksingh has joined #openstack-meeting16:56
*** hoppalm has joined #openstack-meeting16:56
smcginnis4 minutes.16:56
*** jniesz has joined #openstack-meeting16:56
*** Manuel_112 has quit IRC16:57
zengyingzhesome private info about original LUN, was written to the new created volume's metadata16:57
tommylikehueharney:  zengyingzhe 's point is if we use metadata the lun information will be overwrited, I guess16:57
zengyingzhetommylikehu, yes16:57
eharneyok16:57
zengyingzheso we must make this change I think.16:58
smcginnisThey want to store private data in the private data field. Not sure why the pushback really.16:58
eharneythe pushback was because the original explanation didn't make sense16:58
eharneyif they want to move it they can move it16:59
*** efried has quit IRC16:59
eharneyi was just trying to figure out if the change was being made with a correct understanding of how we manage this data16:59
smcginniseharney: OK, so maybe just need a better commit mesage explaining some more of the background?16:59
smcginnisOut of time...17:00
geguileolucky me!17:00
*** arnewiebalck_ has quit IRC17:00
smcginnisSorry geguileo, I guess we'll have to save your for next time.17:00
geguileosmcginnis: I'll bug everyone in the channel, no problem17:00
smcginnisgeguileo: Thanks17:01
johnsomo/17:01
smcginniszengyingzhe: We'll have to follow up. Thanks for the discussion.17:01
smcginnis#endmeeting17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:01
openstackMeeting ended Wed Jul 19 17:01:34 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2017/cinder.2017-07-19-16.00.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2017/cinder.2017-07-19-16.00.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2017/cinder.2017-07-19-16.00.log.html17:01
zengyingzhesmcginnis, thanks.17:01
lhx__thanks17:01
tommylikehuthanks17:01
johnsom#startmeeting Octavia17:01
openstackMeeting started Wed Jul 19 17:01:46 2017 UTC and is due to finish in 60 minutes.  The chair is johnsom. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
xgerman_o/17:01
*** openstack changes topic to " (Meeting topic: Octavia)"17:01
openstackThe meeting name has been set to 'octavia'17:01
*** sanfern has joined #openstack-meeting17:01
pksinghPradeep17:01
johnsomHi folks!17:02
sanfernHi17:02
jnieszHi17:02
johnsom#topic Announcements17:02
*** openstack changes topic to "Announcements (Meeting topic: Octavia)"17:02
*** zengyingzhe has left #openstack-meeting17:02
johnsomPTL elections are coming up17:02
johnsom#link https://governance.openstack.org/election/17:02
johnsomPlease consider running for Octavia PTL.  The link above has information on criteria, etc.17:03
*** pksingh has left #openstack-meeting17:03
*** pksingh has joined #openstack-meeting17:03
johnsomI cannot say at this time whether I will run for another release....17:03
jniesz:(17:04
xgerman_:-(17:04
johnsomPlus, it's always good to have new folks involved.17:04
sanfern:(17:04
pksinghjohnsom: u are awesome :)17:04
xgerman_+117:04
johnsomYeah, I'm not sure if my employer will want me to run again17:04
*** arnewiebalck_ has joined #openstack-meeting17:04
sanfern+117:04
jniesz+117:04
xgerman_hopefully we don’t go the way of designate17:05
johnsomThanks folks!  grin17:05
johnsomYeah, I have faith in our community (couldn't do it without your support)17:05
pksinghxgerman_: what happened with designate?17:05
pksinghmay be not important17:06
xgerman_they imploded because of lack of participants/leadership17:06
johnsomAlso, the PTG is September 11-15th.  I have an Octavia room reserved Wednesday through Friday, though I will be there all week.17:06
pksinghxgerman_: ohh17:06
johnsom#link https://www.openstack.org/ptg17:06
johnsomThe next summit is in Sydney, Australia November 6-8.  I am not planning to attend this one.17:07
*** cloudrancher has quit IRC17:07
johnsom#link https://www.openstack.org/summit/17:07
xgerman_rm_work and I submitted a talk17:08
johnsomYes, I think some folks are planning to attend.17:08
xgerman_well, I wouldn’t call that planning17:08
johnsomWell, I'm pretty sure at least one other person is....17:08
xgerman_but if somebody has budget and the talk is approved we can add people17:09
johnsomYeah, our talks are usually a community collaboration.17:09
johnsomWhich I think is cool.17:09
johnsomFinal announcement I have: Feature freeze and Pike-3 milestone is next week, July 24th!!!!17:10
johnsom#link https://releases.openstack.org/pike/schedule.html17:10
johnsomNext week we will be locking down the features for Pike.  Please plan accordingly.  If you have something critical to get in, please add it to the priority bug list and let me know.17:11
johnsom#link https://etherpad.openstack.org/p/Octavia-Pike-priority-patches17:11
johnsomAny other announcements I am forgetting about?17:11
*** efried has joined #openstack-meeting17:11
johnsom#topic Brief progress reports / bugs needing review17:12
*** openstack changes topic to "Brief progress reports / bugs needing review (Meeting topic: Octavia)"17:12
xgerman_https://review.openstack.org/#/c/418530/ - needs review17:12
nmagnezijohnsom, just joined in. I think you'll get our votes even if you won't run.17:12
johnsomOk, so I just mentioned a reminder about the priority bug list.17:12
xgerman_yep added17:12
johnsomCool17:13
xgerman_but we should probably discuss if/how much we swotch to V2 API17:13
xgerman_later17:13
johnsomnmagnezi also wanted input on:17:13
johnsom#link https://bugs.launchpad.net/octavia/+bug/170525917:13
openstackLaunchpad bug 1705259 in octavia "Octavia health-manager and worker should work better with any given interface_driver " [Undecided,New] - Assigned to Nir Magnezi (nmagnezi)17:13
johnsomOk17:13
nmagneziyup, please have a look and comment i'd like to work on that one17:14
johnsomRecently I have started to pick up the python-openstacksdk patches that the folks from Intel started17:14
johnsom#link https://review.openstack.org/#/c/454410/17:14
johnsom#link https://review.openstack.org/#/c/451574/17:14
*** Apoorva has joined #openstack-meeting17:15
johnsom#link https://review.openstack.org/44926417:15
johnsomThis is a python library for OpenStack that will include Octavia.17:15
johnsomI plan to use it for the octavia-dashboard17:15
johnsomI think I can get most of API done this week.17:16
*** jamesmcarthur has joined #openstack-meeting17:16
johnsomAny other progress updates or bugs to note?17:16
johnsom#topic Proposed mascot17:17
*** openstack changes topic to "Proposed mascot (Meeting topic: Octavia)"17:17
johnsomThe foundation has come back with a proposed mascot rendering17:17
johnsom#link https://usercontent.irccloud-cdn.com/file/KdpSnmb0/OctaviaMascot.jpg17:18
*** rm_mobile has joined #openstack-meeting17:18
johnsomI think rm_work had some comments/feedback.  Any other thoughts from the team?17:18
nmagnezilooks nice!17:18
rm_mobileo/17:18
xgerman_+117:18
xgerman_ship it17:18
*** martinkopec has quit IRC17:18
nmagnezi+117:18
nmagnezilooks good17:18
rm_mobileI did have some feedback17:18
pksinghit looks nice17:18
rm_mobileCan you link it again?17:18
nmagnezirm_mobile, https://usercontent.irccloud-cdn.com/file/KdpSnmb0/OctaviaMascot.jpg17:18
sanfernlooks good17:19
rm_mobileI thought it looked really busy17:19
rm_mobileAnd why wasn't it 8 feathers17:19
rm_mobileThat'd help with the busyness17:19
pksinghits our national birs17:19
pksinghbird17:19
rm_mobileAnd make it a pun17:19
johnsomNice17:19
pksinghgreat :)17:19
rm_mobileOct-avia17:20
johnsomSo, proposing dropping the two bottom feathers?17:20
xgerman_sounds good17:20
sanfern+117:20
rm_mobileThey could do that or resize them all17:20
pksinghrm_mobile: avia?17:20
rm_mobileI actually was hoping for the resize but both work17:21
rm_mobilePksingh "oct"17:21
rm_mobileMeans 8 :P17:21
johnsomWhat do others think about dropping the two bottom feathers to make it eight (octa)?17:21
rm_mobileJust dropping those two might make it look awkward because of the lines17:22
pksinghthen we can increase the width of feathers little bit, to look it full17:22
johnsomPersonally I'm fine with it as-is, but looking for feedback17:22
nmagneziif that's important for Adam I'd vote in favor of it :P17:22
johnsomTo give context, the foundation is putting them here:17:22
xgerman_yeah, for me it’s more important we get a mascot/sticker after what happened the last time ;-)17:22
johnsom#link https://www.openstack.org/software/project-navigator/17:22
johnsomThey will also make up stickers for the summit/PTG17:23
*** gyee has joined #openstack-meeting17:23
xgerman_I already reserved a space on my laptop ;-)17:23
* nmagnezi needs a mascot shipped :D17:24
johnsomnmagnezi We can probably make that happen17:24
xgerman_+117:24
sanfernplease ship to us ;)17:24
nmagnezithat would be really nice :-)17:24
*** harlowja has joined #openstack-meeting17:25
johnsomWe can figure out a way to get any active contributor a sticker17:25
rm_mobileYeah just note how simple most are17:25
rm_mobileOn that page17:25
johnsomOk, so should we vote on this?  More discussion?17:25
*** harlowja has quit IRC17:25
rm_mobileTo many lines makes them look really bad as a low res icon17:25
*** harlowja has joined #openstack-meeting17:26
johnsomWhen I zoom it small in chrome the dark and light sections show up pretty well actually17:26
rm_mobileYeah it's close17:26
johnsomhttps://usercontent.irccloud-cdn.com/file/FwOSBaQh/image.png17:27
rm_mobileEugh17:27
*** kornica has joined #openstack-meeting17:27
rm_mobileYeah less plz17:27
jnieszi think less feathers would help that17:28
rm_mobile8!17:28
johnsom#startvote Should we change the proposed mascot? Yes, No17:29
openstackBegin voting on: Should we change the proposed mascot? Valid vote options are Yes, No.17:29
openstackVote using '#vote OPTION'. Only your last vote counts.17:29
johnsomJust to keep our voting heritage alive....17:29
xgerman_ol17:29
rm_mobile#vote yes17:29
*** bobh has quit IRC17:29
johnsom#vote No17:30
rm_mobile#vote Yes17:30
pksingh#vote No17:30
jniesz#vote yes17:30
sanfern#vote yes17:30
nmagnezi#vote yes17:30
*** rossella_ has quit IRC17:31
johnsomOk, going once...17:31
johnsomgoing twice....17:31
johnsom#endvote17:31
openstackVoted on "Should we change the proposed mascot?" Results are17:31
openstackYes (4): sanfern, nmagnezi, rm_mobile, jniesz17:31
openstackNo (2): johnsom, pksingh17:31
*** bobh has joined #openstack-meeting17:31
*** rossella_ has joined #openstack-meeting17:31
rm_mobile8 feathers wins the day! Huzzah17:32
johnsomOk, so help me with instructions for the artist.  We want eight feathers, how do we do that?17:32
rm_mobileReduce the number of feathers by 217:32
rm_mobile:P17:32
* johnsom glares17:32
rm_mobileIdeally scale the others around to match the current layout17:32
jnieszreduce by 2 resize the rest17:32
*** lpetrut_ has quit IRC17:33
johnsomSo we still want two dropped features, just remove two, resize and some white space between feathers?17:33
johnsomHelp me, to help you, help the artist....  grin17:33
rm_mobileErr I don't know about white space17:34
rm_mobileJust drop two and resize imo17:34
johnsomSo, you are thinking making the feathers bigger?17:34
jnieszyea, no whitespace17:34
rm_mobileYes17:34
johnsomOk17:34
johnsomEveryone good with that?  Additional comments?17:35
johnsomDon't make me call another vote...  grin17:35
johnsomAll right, moving on17:36
johnsom#topic Discuss L3 active-active spec confusion (xgerman)17:36
*** openstack changes topic to "Discuss L3 active-active spec confusion (xgerman) (Meeting topic: Octavia)"17:36
*** lhx__ has quit IRC17:36
*** ekcs has joined #openstack-meeting17:36
johnsomxgerman and I were talking this week about the active/active patch he is working on and the distributor driver17:36
johnsomI think there is some confusion about the L3 spec17:37
*** dprince has quit IRC17:37
johnsomSpecifically, what actions the L3 act/act distrubutor driver will take against the top of rack switch?17:37
*** annegentle has joined #openstack-meeting17:37
xgerman_and what part the bgp speaker plays17:38
jnieszthe ToR will be the bgp peer17:38
johnsomWhat are the mechanics if an amphora needs to be removed from rotation?  (distributor-> ToR switch?)17:38
johnsomAnd what exactly the BGP speaker will be sending out.17:38
johnsomxgerman_ Does that capture the questions?17:38
jnieszthe bgp speaker will essentially be sending out route announcements17:38
jnieszto the bgp peer of the ToR17:39
xgerman_ok, johnsom thought the speaker would just annoucne and cold be configured when starting an amp and didn’t need to be reconfigured17:39
jnieszwe would want the ability to cleanly withdraw the route as well17:40
jnieszso when we remove it from the distributor17:40
jnieszit will pull the route17:40
jnieszotherwise have to wait for timeout17:40
jnieszwhich is dictated by the hold time17:40
johnsomSo, give us a little detail on how that would work.  Is that a distributor driver call to ToR?17:41
jnieszno calls directly to the ToR17:41
jnieszall the calls would go through the bgp speaker on the amphora17:41
johnsomOk, so to remove an amphora, it needs to stop speaking.  Correct?17:41
jnieszto remove it would have to withdraw the /32 route and then terminate the peering session17:42
*** gyee has quit IRC17:42
*** ralonsoh has quit IRC17:42
jnieszthat is for shutdown17:42
johnsomBecause essentially, in your model the "distributor" is the ToR doing the ECMP right?17:42
jnieszthe ToR is just bgp neighbor that is taking the route and injecting it into the L3 fabric17:43
*** deep-book-gk_ has joined #openstack-meeting17:43
jnieszthe neighbor could be a route reflector as well17:43
jnieszdoesn't have to be the ToR17:43
*** deep-book-gk_ has left #openstack-meeting17:43
jnieszin our model it will be ToR17:43
jnieszbut the design should work with different network topologies based on L3 fabric17:43
*** andreas-f has quit IRC17:44
jnieszwhen the amphora boots up we can automatically create the peer session17:44
johnsomSo, to setup the ECMP hashing, your distributor driver would talk to what?17:44
jnieszand then announce the route when everything is ready17:44
*** gyee has joined #openstack-meeting17:44
*** gyee has quit IRC17:44
jnieszfor the ECMP hashing, we would need multiple amphora launched17:45
johnsomOr are you planning to just accept any multi-advertised route as an ECMP hashed17:45
jnieszand they would inject the same anycast VIP route with different next-hops17:45
jnieszeach amphora injects the same route with different next hop17:46
jnieszECMP happens when you have 2+17:46
jnieszas the network then has multiple best paths of equal eight17:46
jnieszweight17:46
*** tesseract has quit IRC17:46
* johnsom Thinks he had this all wrong and German was on the right path.17:47
johnsomI think we need to step back and re-think the distributor driver.17:47
xgerman_well, we still should note that in the spec17:47
xgerman_so others can read & understand17:47
johnsomjniesz Can we update the spec to call out who is talking to what components for each of the actions?  I think that would help clarify.17:48
johnsom+1 Yeah, that was what I was typing.17:48
xgerman_it can also just be an example and we can go from there17:48
jnieszyes, it would be an example, as a different operator might have different devices17:48
johnsomBonus points for a lifecycle17:48
jnieszthat they BGP peer with17:48
johnsomRight17:49
xgerman_yes, but it would help us to understand ;-)17:49
jnieszok, I can add some details in the spec with our example17:49
johnsomThanks!17:50
xgerman_I still feel we need to whiteboard ACTIVE-ACTIVE and talk that through at the PTG17:50
jnieszalso for the distributor driver talk if you want to discuss after on a call I can set up17:50
johnsomok, so now the discussion is really about how we abstract the act/act to support the "service vm distributor", "appliance distributor", and 'L3 fabric distributor" models.17:50
xgerman_indeed17:51
xgerman_and where we put the abstraction: flows for each or hide it in the driver17:51
jnieszyea, I remember the flow question came up17:51
johnsomI can't do a call today, I have some other meetings, but yeah, whiteboard and/or proposals would be good.17:52
johnsomI need to think about that abstraction a bit.17:52
jnieszthey are pretty different, as some you just call api from driver, others you have to orchestrate the service vm distributor17:53
xgerman_same here and we probably should loop in rm_work to see if it fits "our architecture”17:53
johnsomRight17:53
*** Manuel_112 has joined #openstack-meeting17:53
*** Rockyg has quit IRC17:54
johnsom#action Think about how we abstract the act/act to support the "service vm distributor", "appliance distributor", and 'L3 fabric distributor" models.17:54
johnsom#topic Open discussion17:54
*** openstack changes topic to "Open discussion (Meeting topic: Octavia)"17:54
*** yamahata has quit IRC17:54
*** iyamahat has quit IRC17:54
johnsomAny other topics for the last 5-6 minutes today?17:54
xgerman_My main things is how much do we want to switch to V2 API?17:54
pksinghhttps://review.openstack.org/#/c/484325/17:54
xgerman_Are we planning to change the default in devstack. etc.17:55
xgerman_unrelated I asked infra and they can build  diskiamges…17:55
*** trinaths has left #openstack-meeting17:55
johnsomHmmm, so changing the service "octavia" to not require neutron-lbaas?17:56
xgerman_and making the proxy default driver in Neutron17:56
johnsomWe need to merge that  first...17:56
xgerman_indeed17:56
johnsom(needs some reviews)17:56
xgerman_but depending on what we decide that might inform priorities17:57
johnsomYeah17:57
johnsomIt might be a bit late to pull that switch on other projects.  I'm thinking heat for example17:57
xgerman_well, I think we can punt that until next week…if we do proxy it shoudl eb transparent17:58
johnsomI would propose making sure the proxy gets into Pike, then at the start of queens making the switch17:58
xgerman_yeah, just wanted us to have a decision… works for me17:58
johnsomOk, let's do that.17:59
johnsompksingh17:59
*** Manuel_112 has quit IRC17:59
pksinghjohnsom: i replied to your comments17:59
johnsomReading your comments.   I will comment there as we are now out of time17:59
pksinghjohnsom: sure, thanks :)17:59
johnsomOther please chime in17:59
johnsomOk, thanks folks!18:00
xgerman_thanks18:00
johnsom#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Wed Jul 19 18:00:20 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/octavia/2017/octavia.2017-07-19-17.01.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/octavia/2017/octavia.2017-07-19-17.01.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/octavia/2017/octavia.2017-07-19-17.01.log.html18:00
*** bknudson1 has joined #openstack-meeting18:00
*** pksingh has quit IRC18:02
*** bknudson has quit IRC18:02
*** electrofelix has quit IRC18:05
*** kornica has quit IRC18:05
*** jkilpatr has quit IRC18:06
*** ociuhandu_ has quit IRC18:06
*** baoli_ has quit IRC18:11
*** iyamahat has joined #openstack-meeting18:12
*** baoli has joined #openstack-meeting18:15
*** boris-42___ has joined #openstack-meeting18:17
*** u_nuSLASHkm8 has joined #openstack-meeting18:17
*** u_nuSLASHkm8 has left #openstack-meeting18:17
*** ekcs has quit IRC18:20
*** Julien-zte has quit IRC18:20
*** jkilpatr has joined #openstack-meeting18:22
*** ekcs has joined #openstack-meeting18:22
*** Julien-zte has joined #openstack-meeting18:23
*** dprince has joined #openstack-meeting18:23
*** sanfern has left #openstack-meeting18:23
*** efried is now known as efried_lunch18:23
*** bobh has quit IRC18:24
*** dprince has quit IRC18:26
*** baoli has quit IRC18:27
*** ociuhandu_ has joined #openstack-meeting18:29
*** rbudden has joined #openstack-meeting18:30
*** yamahata has joined #openstack-meeting18:31
*** hoppalm has quit IRC18:38
*** bobh has joined #openstack-meeting18:38
*** Sukhdev has quit IRC18:39
*** annabelleB has joined #openstack-meeting18:45
*** rm_mobile has quit IRC18:45
*** hoppalm has joined #openstack-meeting18:45
*** andreas-f has joined #openstack-meeting18:49
*** hoppalm has quit IRC18:50
*** hoppalm has joined #openstack-meeting18:52
*** bknudson1 has quit IRC18:52
*** hoppalm has quit IRC18:53
*** hoppalm has joined #openstack-meeting18:53
*** cschwede_ has quit IRC18:54
*** bknudson has joined #openstack-meeting18:55
*** hoppalm_ has joined #openstack-meeting18:55
*** hoppalm has quit IRC18:56
*** jkilpatr has quit IRC18:56
*** Manuel_112 has joined #openstack-meeting18:56
*** dprince has joined #openstack-meeting18:56
*** Swami has joined #openstack-meeting18:57
*** jamesmcarthur has quit IRC18:58
*** adisky__ has quit IRC18:58
*** jamesmcarthur has joined #openstack-meeting18:59
zara_the_lemur__anybody about for this week's storyboard meeting?19:00
zara_the_lemur__we even have an out-of-tune violin19:00
*** Manuel_112 has quit IRC19:01
*** frank_young has joined #openstack-meeting19:01
* zara_the_lemur__ will give it a few min19:02
diablo_rojoHello :)19:02
zara_the_lemur__hi :)19:02
*** jniesz has left #openstack-meeting19:02
zara_the_lemur__#startmeeting storyboard19:02
openstackMeeting started Wed Jul 19 19:02:54 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:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: storyboard)"19:02
openstackThe meeting name has been set to 'storyboard'19:02
zara_the_lemur__#topic Open Discussion19:03
*** openstack changes topic to "Open Discussion (Meeting topic: storyboard)"19:03
zara_the_lemur__continuing our trend of short meetings that just provide a space for people to raise stuff if they want to19:03
zara_the_lemur__discuss, or don't; I'll end the meeting at quarter past if no discussion19:03
diablo_rojoI heard back from Octavia finally and they want to wait till the start of the next release. Still no word from the others. If we can test some more projects I can reach out to another batch19:04
zara_the_lemur__ah, okay19:04
fungiwoo!19:04
zara_the_lemur__do we have a list for the other projects to be tested yet?19:04
* diablo_rojo thinks there is a story out there somewhere19:04
SotKi shall test some when i test your patch :)19:05
*** jkilpatr has joined #openstack-meeting19:05
*** annabelleB has quit IRC19:05
diablo_rojoSotK, that would be EXCELLENT19:05
diablo_rojohttps://storyboard.openstack.org/#!/story/200087619:06
zara_the_lemur__hah, I was just looking for the link19:06
zara_the_lemur__neat19:06
diablo_rojoI haven't tested mine yet, cause all kinds of issues and lack of time, but I will try again next week.19:06
diablo_rojoI can add some more projects to test too19:06
fungi#link https://storyboard.openstack.org/#!/story/2000876 Migrate Project to Storyboard19:06
*** frank_young has quit IRC19:06
*** sshank has quit IRC19:07
zara_the_lemur__I think I got through mine but that was some time ago and they've likely changed in the interim19:07
*** jamesmcarthur has quit IRC19:07
*** hoppalm_ has quit IRC19:07
diablo_rojozara_the_lemur__, would you mind retesting and posting the results in the tasks?19:07
zara_the_lemur__sure, I can do.19:08
*** vishnoianil has joined #openstack-meeting19:09
diablo_rojozara_the_lemur__, thank you :)19:09
zara_the_lemur__np :)19:10
zara_the_lemur__I also managed to test a patch the other day!19:10
zara_the_lemur__but there was a bug19:10
zara_the_lemur__so I left a -1 and felt bad19:10
zara_the_lemur__but I just wanted to tell everyone that I actually reviewed something for the first time in a while19:11
funginext time you leave a -1, feel good that you kept a bug out!19:11
*** kjw3 has joined #openstack-meeting19:11
diablo_rojoHa ha don't feel bad, you did something helpful :)19:11
zara_the_lemur__haha, thanks19:11
zara_the_lemur__it was a 3 month old patch ;_;19:12
zara_the_lemur__but steadily, I am getting back on track with it19:12
diablo_rojoWorks for me :)19:12
*** hoppalm has joined #openstack-meeting19:12
zara_the_lemur__also argh ptg19:13
diablo_rojoOh yes, who will be there besides myself and fungi ?19:13
diablo_rojozara_the_lemur__, SotK ?19:13
fungi#link https://etherpad.openstack.org/p/infra-ptg-queens Infra planning pad for Queens PTG in Denver19:13
fungiput ideas there if you have any19:13
zara_the_lemur__diablo_rojo: I haven't yet booked anything though I'd like to go19:14
zara_the_lemur__things have been a bit hectic, should be able to say more next week.19:14
diablo_rojoApply to TSP if you need help19:14
fungithat's what it's there for, after all19:14
diablo_rojoTruth!19:15
fungii have no problem as infra ptl vouching for tsp applicants who work on sb19:15
fungithe foundation sets aside the tsp fund explicitly for making sure that we can get as much of our community as possible to these events19:16
*** christian1110 has joined #openstack-meeting19:16
zara_the_lemur__neato, one thing I'm wondering is what happens if I ask for tsp and then find out I can get funding? can I pay it back or something?19:16
zara_the_lemur__that's part of the reason I've dithered.19:17
diablo_rojoAnd thanks to Verizon we have 10 more spots than we would have19:17
diablo_rojoI think we could just take a TSP donation for the same amount things cost?19:17
christian1110where?19:17
*** annabelleB has joined #openstack-meeting19:17
diablo_rojoThat would basically be the same zara_the_lemur__19:17
*** tinyurl_comSLASH has joined #openstack-meeting19:17
zara_the_lemur__ah, okay, great19:18
fungithe way the tsp stuff works, most of it isn't really fungible anyway (for example, we already have the room block, flights get booked by travel support, et cetera) i think19:18
*** gyee has joined #openstack-meeting19:18
*** tinyurl_comSLASH has left #openstack-meeting19:18
zara_the_lemur__ah, right19:18
diablo_rojoIt wouldn't be like you would take your name off the list for this round, but next round there would be whatever money you gave back.19:19
diablo_rojoIts one giant budget that gets split.19:19
diablo_rojoFrom what I understand19:19
fungiso if you can't go they reassign the ticket or get it refunded, they take the unused rate on the room or reassign it, and so on19:19
fungibut anyway, don't let thinking there's a chance you might not need it stop you from applying if you want to go and aren't sure you'll have funding otherwise19:20
zara_the_lemur__okay, thank you19:20
zara_the_lemur__If I have other questions I guess I'll ping, then :)19:21
fungihappy to get you answers or get you someone who has them19:21
zara_the_lemur__thanks :)19:21
diablo_rojoAgreed, apply if you think you might need it. Easier to ask first and then take your name off the list later than to not apply and then need it and have missed the boat19:22
*** kbyrne has quit IRC19:22
zara_the_lemur__right, I'll try to have something done on that front by the end of this week19:23
zara_the_lemur__and hopefully get a traditional task-tracking session planned ;)19:23
diablo_rojoCoolio19:24
diablo_rojoLol19:24
*** kbyrne has joined #openstack-meeting19:25
fungiyeah, could consider doing some sb q&a in a shared room slot for teams interested in migrating, and/or hang out on the first two days when the horizontal teams are hosting a sort of help desk meet-n-greet in their rooms for people who have questions or want our assistance19:25
fungiand then have some nice fingers-to-the-keyboard time to hack out new stuff on wednesday through friday if you want19:26
zara_the_lemur__that would work, at the last ptg I kinda floated around at the start of the week advertising my location so people could come over with questions19:26
fungiyeah, that has been formalized into a feature for the first two days basically ;)19:27
diablo_rojofungi, +119:27
*** annabelleB has quit IRC19:27
zara_the_lemur__:D (as for the second half of the week, I think I spent most of it regretting I hadn't organised an aquarium trip)19:27
zara_the_lemur__*regretting that19:27
fungi#link http://www.aquariumrestaurants.com/downtownaquariumdenver/default.asp Downtown Aquarium - Denver, CO19:29
*** tinyurl_comSLASH has joined #openstack-meeting19:29
fungiyou could eat and watch fish at the same time19:29
zara_the_lemur__ooh, neat19:30
zara_the_lemur__I haven't looked at what sorts of things are around in denver more generally19:30
diablo_rojoTORCHYS TACOS19:30
diablo_rojoVOODOO DONUTS19:30
zara_the_lemur__wow they even have mermaids19:30
zara_the_lemur__according to their slideshow19:30
*** makowals has quit IRC19:32
*** eharney has quit IRC19:32
*** tinyurl_comSLASH has left #openstack-meeting19:32
*** rossella_ has quit IRC19:32
*** bknudson has quit IRC19:33
zara_the_lemur__#action Zara will organise some kind of task tracking ptg plan and maybe a trip out19:33
*** rossella_ has joined #openstack-meeting19:33
zara_the_lemur__I don't have anything else19:33
zara_the_lemur__I'll leave the meeting going for another minute or so jic19:34
funginothing important from me, but great meeting!19:34
zara_the_lemur__haha :)19:35
zara_the_lemur__okay, meeting ends in 519:35
zara_the_lemur__419:35
zara_the_lemur__319:35
zara_the_lemur__219:35
zara_the_lemur__119:35
zara_the_lemur__#endmeeting19:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:35
openstackMeeting ended Wed Jul 19 19:35:26 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-07-19-19.02.html19:35
zara_the_lemur__thanks, all! :D19:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2017/storyboard.2017-07-19-19.02.txt19:35
zara_the_lemur__you're the best!19:35
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2017/storyboard.2017-07-19-19.02.log.html19:35
fungithanks zara_the_lemur__!19:35
diablo_rojoThanks zara_the_lemur__ :)19:35
* fungi gets back to the mailing list equivalent of boring paperwork19:35
zara_the_lemur__oh no19:36
zara_the_lemur__I could've extended the meeting19:36
zara_the_lemur__I could restart it19:36
funginah, if i don't get it done now, i just have to do it later19:36
zara_the_lemur__heh, okay I will not do '#startmeeting fungi-procrastination'19:37
*** tobberydberg has joined #openstack-meeting19:37
*** awaugama has quit IRC19:38
*** arnewiebalck_ has quit IRC19:41
*** tobberydberg has quit IRC19:42
*** frank_young has joined #openstack-meeting19:44
*** frank_young has quit IRC19:48
*** andreas-f has quit IRC19:49
*** kjw3 has quit IRC19:49
*** dprince has quit IRC19:50
*** coolsvap has quit IRC19:51
*** pchavva has quit IRC19:51
*** lpetrut_ has joined #openstack-meeting19:52
*** annegentle has quit IRC19:55
*** radeks has joined #openstack-meeting19:56
*** Manuel_112 has joined #openstack-meeting19:57
*** efried_lunch is now known as efried19:59
ekhugen_alt#startmeeting wos_mentoring20:00
openstackMeeting started Wed Jul 19 20:00:14 2017 UTC and is due to finish in 60 minutes.  The chair is ekhugen_alt. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: wos_mentoring)"20:00
openstackThe meeting name has been set to 'wos_mentoring'20:00
ekhugen_altHi, who's here for women of openstack mentoring?20:00
ekhugen_altwell not for mentoring, but for the team meeting about it20:00
*** rwsu has quit IRC20:00
*** Daisy_ has joined #openstack-meeting20:04
*** mhayden has joined #openstack-meeting20:04
*** dtroyer has quit IRC20:05
*** rwsu has joined #openstack-meeting20:06
*** anilvenkata has quit IRC20:06
*** thorst_ has quit IRC20:07
*** Manuel_112 has quit IRC20:07
*** Daisy_ has quit IRC20:09
*** annabelleB has joined #openstack-meeting20:09
*** thorst has joined #openstack-meeting20:10
*** andreas-f has joined #openstack-meeting20:10
*** NicoleH has joined #openstack-meeting20:11
ekhugen_altokay, last call for women of openstack mentoring?20:11
NicoleHEmily, did anyone join for women of openstack mentoring, or am I just late?20:12
ekhugen_altHi Nicole, you're the only other one who's joined20:12
ekhugen_altshould we just continue discussions via email?20:12
NicoleHOh, ok20:12
NicoleHSure, happy to continue discussions via email :)20:13
ekhugen_altI think kendall sent out the survey and we were discussing if we want to remove any questions20:13
NicoleHYep, I saw that in email. I'll take another look at that string.20:14
ekhugen_altdid you have any topics you wanted to discuss?20:14
*** thorst has quit IRC20:14
NicoleHHow are we coming along on the mentoring session for Sydney?20:15
NicoleHI think I remember that we had volunteers who were going to run with that one, right?20:15
*** annegentle has joined #openstack-meeting20:15
ekhugen_altwe did, Amrith and Swami volunteered20:15
ekhugen_altbut they haven't been able to make these meetings I think20:15
*** makowals has joined #openstack-meeting20:16
ekhugen_altplus there was the discussion at the Women of OpenStack level about whether we even wanted a separate event for speed mentoring20:16
ekhugen_altor if we should roll it into the wos lunch20:16
*** cloudrancher has joined #openstack-meeting20:17
*** sshank has joined #openstack-meeting20:17
*** jkilpatr has quit IRC20:18
NicoleHOh, interesting thought about combining the speed mentoring session with the wos lunch.20:19
NicoleHThe wos lunch included a mini panel discussion in Boston, right?20:19
*** Sukhdev_ has quit IRC20:19
*** eharney has joined #openstack-meeting20:20
ekhugen_altright, it did20:20
*** annabelleB has quit IRC20:20
ekhugen_altbut in barcelona the breakfast had kind of a open networking part to it20:20
*** Sukhdev has joined #openstack-meeting20:20
ekhugen_altso they could bring that back, make it a bit more formal like speed mentoring20:20
*** raildo has quit IRC20:21
NicoleHAh, got it20:21
NicoleHWhat are your thoughts?20:22
NicoleHI really liked the mini panel discussion, with a separate speed mentoring session. Just my 2 cents.20:22
*** annabelleB has joined #openstack-meeting20:22
*** radeks has quit IRC20:23
ekhugen_altI did too, but with the smaller size of sydney, if they're looking to cut the number of sponsored sessions, it would be easy and I don't think we'd lose too much content20:23
NicoleHtrue, particularly for sydney :)20:26
*** annegentle has quit IRC20:26
diablo_rojoHello20:27
diablo_rojoSorry I'm late20:27
ekhugen_altI think maybe next Monday women of openstack meeting we'll discuss that more?20:27
ekhugen_altHi Kendall, no worries20:27
diablo_rojoBeen trying to register for Grace Hopper for 4+ hours..20:27
diablo_rojoI like the separate Speed Mentoring if we can get the people to do it again.20:28
diablo_rojoI will definitely be there to help.20:28
diablo_rojoOr if we do condense it should only be for Sydney20:29
* amrith lurks in the background 20:29
* diablo_rojo waves to amrith :)20:30
amrithhi diablo_rojo20:30
amrithsorry about being late (again)20:30
*** annegentle has joined #openstack-meeting20:30
amriththis meeting overlaps another (work meeting)20:30
diablo_rojoamrith, no worries :)20:30
* amrith speed-reads the story so far20:30
amrithok, happy to do the speed mentoring thing again.20:31
amrithit was fun (for me) but I never got to hear what the feedback from attendees was. was it valuable to them, woudl they recommend it to friends.20:31
amrithwhere are my manners, hi ekhugen_alt20:32
ekhugen_altsorry I'm getting interrupted by phone calls, hi amrith20:33
*** cloudrancher has quit IRC20:33
ekhugen_altbut yes, I think diablo_rojo we're still missing a sponsor for the sydney speed mentoring session, right?20:35
diablo_rojoekhugen_alt, let me double check20:35
*** annegentle has quit IRC20:35
* diablo_rojo waits for the other Kendall at the foundation to reply :) 20:36
*** jkilpatr has joined #openstack-meeting20:36
*** ansmith has quit IRC20:36
diablo_rojoNo one has stepped up to sponsor speed mentoring yet.20:37
diablo_rojoekhugen_alt, ^^20:37
ekhugen_altokay, thanks20:37
amrithwhat's the ask of a sponsor?20:37
diablo_rojoamrith, https://www.openstack.org/assets/sydney-summit/sponsorship/Sydney-Sponsor-Prospectus-FINAL.pdf20:38
diablo_rojopage 1620:38
ekhugen_altis there a deadline for the sponsorships, diablo_rojo?20:39
diablo_rojoekhugen_alt, I'll ask :)20:39
ekhugen_altthanks, sorry to keep you running back and forth20:40
diablo_rojoThis is why I have two monitors plus my laptop screen- easy to have multiple convos at once :)20:40
diablo_rojoNo problem btw20:40
*** jamesmcarthur has joined #openstack-meeting20:41
amrithlooking at page 1620:41
amrithone second20:41
diablo_rojoSept 27th is the official contract deadline20:42
diablo_rojoBut I think we can get a bit of an extension if need be20:42
*** sshank has quit IRC20:42
*** sshank has joined #openstack-meeting20:42
ekhugen_altah okay, so we have awhile before we have to make the call whether to combine events or not20:43
amrithok, so the networking lunch is sold out, the speed networking is still open.20:43
diablo_rojoamrith, correct :)20:43
amrithok, will poke around the cushions and see what I can find.20:43
diablo_rojoamrith, sounds good :) You have some time to search multiple couches :)20:43
* ekhugen_alt looks in her spare change drawer20:43
amrithdiablo_rojo will look. Oh, .. never mind, different topic.20:44
ekhugen_altso amrith, do you have any questions about the speed mentoring event (going on the assumption we'll have one) and how it's run?20:45
*** jamesmcarthur has quit IRC20:45
amrithi have one question ekhugen_alt , is it like the last one (in Boston)? if it is, I'm fine with it, if it is different, please let me know what it is. the earlier question was about feedback on the event.20:46
*** dtroyer has joined #openstack-meeting20:46
ekhugen_altwell I think the proposal in the prospectus was for an event like the last one in Boston20:46
diablo_rojoI dont think there is anything we need to change- I think it went really well.20:47
ekhugen_altthe feedback from that one was positive, usually we don't hear a ton from mentees afterward (not all of them sign up ahead of time, so it's hard to follow up)20:47
diablo_rojoMore attendees would have been great, but I think as far as format and number of mentors we had it was good.20:48
ekhugen_altbut the comments here were overwhelmingly positive https://etherpad.openstack.org/p/BOS-speed-mentoring20:48
*** timburke has joined #openstack-meeting20:48
ekhugen_altit was a good amount of people for the room, I think20:48
ekhugen_altprevious events we had a larger room20:49
ekhugen_altand probably could've taken more people20:49
amrithok, thanks ekhugen_alt diablo_rojo, my #action is to look behind the cushions20:51
ekhugen_altthanks amrith!20:51
ekhugen_altso I think the other topic was the survey that diablo_rojo sent out20:51
ekhugen_altnot survey, signup sheet https://openstackfoundation.formstack.com/forms/mentoring_pike_queens20:52
ekhugen_altdid people have other suggestions of what questions could be eliminated/added?20:52
*** qiangcao has joined #openstack-meeting20:53
diablo_rojoDid we ever match people based on location before?20:55
diablo_rojoOr more just interest?20:55
ekhugen_altin some of the early times, we tried based on location, but it's next to impossible really20:55
ekhugen_altthere are so many projects, the chances of getting someone in your project and in your geography are slim20:56
ekhugen_altI think more we had un-matches based on that.  People who said the relationship didn't work out because they couldn't find a time to meet.20:56
diablo_rojoKnowing that, we can take those questions out I think20:57
ekhugen_altbut that's so dependent on personal working style, etc, I don't know if we can reliably identify those issues ahead of time20:57
ekhugen_alt+1 diablo_rojo20:57
diablo_rojoAnd I agree with all of the ones you said in the email we could remove20:57
diablo_rojoekhugen_alt,20:57
*** m_kazuhiro has joined #openstack-meeting20:58
*** torgomatic has joined #openstack-meeting20:58
*** acoles has joined #openstack-meeting20:58
ekhugen_altokay, we're almost out of time, so any further discussion on this, can we move to email?20:58
ekhugen_altthanks everyone!20:59
*** patchbot has joined #openstack-meeting20:59
ekhugen_alt#endmeeting20:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:59
openstackMeeting ended Wed Jul 19 20:59:26 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/wos_mentoring/2017/wos_mentoring.2017-07-19-20.00.html20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/wos_mentoring/2017/wos_mentoring.2017-07-19-20.00.txt20:59
openstackLog:            http://eavesdrop.openstack.org/meetings/wos_mentoring/2017/wos_mentoring.2017-07-19-20.00.log.html20:59
*** jrichli has joined #openstack-meeting20:59
notmynameswift team meeting time20:59
notmyname#startmeeting swift21:00
openstackMeeting started Wed Jul 19 21:00:02 2017 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** ekhugen_alt has left #openstack-meeting21:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
openstackThe meeting name has been set to 'swift'21:00
*** kota_ has joined #openstack-meeting21:00
notmynamewho's here for the swift team meeting?21:00
kota_hi21:00
m_kazuhiroo/21:00
jrichlio/21:00
mathiasbo/21:00
tdasilvao/21:00
timburkeo/21:00
torgomatichi21:00
acoleshello21:00
notmynamewelcome everyone21:01
notmynamemeeting agenda is at21:01
notmyname#link https://wiki.openstack.org/wiki/Meetings/Swift21:01
notmyname#topic denver ptg21:01
*** openstack changes topic to "denver ptg (Meeting topic: swift)"21:01
notmynamereminder that the PTG is coming up21:01
notmynameyou should have already registered for your ticket and hotel :-)21:01
*** jamesmcarthur has joined #openstack-meeting21:01
notmyname#link https://etherpad.openstack.org/p/swift-ptg-queens21:01
*** kylek3h has quit IRC21:02
notmynamethat's the topic etherpad where we're collecting the things we want to discuss in person21:02
*** esberglu has quit IRC21:02
notmynameplease encourage everyone to be at the PTG, especially ops. getting the devs and ops together is crucial21:02
*** frank_young has joined #openstack-meeting21:03
notmynameif you're still planning your week, monday and tuesday will be for cross project sessions (scheduled) and any ad-hoc conversations we may have. wed-fri will have a reserved room for swift21:03
mattoliverauo/ (sorry for being late)21:03
notmynameare there any questions about the PTG that we can answer in here or that I can hunt down for you?21:03
notmynamegreat! no questions21:04
notmyname(please feel free to ask at any time in -swift if you do have questions)21:05
notmyname#topic bug triage work21:05
*** openstack changes topic to "bug triage work (Meeting topic: swift)"21:05
*** Manuel_112 has joined #openstack-meeting21:05
notmynameso we're one week in to this (or a little longer, depending on how you count). how are we doing?21:05
*** anilvenkata has joined #openstack-meeting21:05
notmyname#link https://etherpad.openstack.org/p/swift-bug-triage-list21:05
*** jamesmcarthur has quit IRC21:06
notmynameI see that tdasilva had put his name on several and they're mostly crossed off now. great job!21:06
*** Manuel_112 has quit IRC21:06
acoleslooks like tdasilva is the champ!21:07
tdasilvahonestly, i've been picking the low hanging fruit just to make progress21:07
tdasilvacross stuff out21:07
notmynameheh21:07
*** Manuel_112 has joined #openstack-meeting21:08
tdasilvahopefully make the list more manageable21:08
notmynamesee! go do stuff now, and you get all the easy ones!21:08
*** frank_young has quit IRC21:08
*** Manuel_112 has quit IRC21:08
tdasilvai'd like to think there's lots of that21:08
notmynameeveryone else should go do bug triage today so tdasilva doesn't get all the low-hanging-fruit :-)21:08
*** Manuel_112 has joined #openstack-meeting21:08
notmynameplease put your names on bugs, go triage them, and cross them off after updating the status in LP (see the notes at the top of the etherpad)21:09
notmyname(I'm speaking to myself, too)21:09
notmyname(maybe literally since it doesn't seem like anyone else is talking in here) ;-)21:10
*** julim has quit IRC21:10
*** andreas-f has quit IRC21:10
tdasilvaheh...I was playing with tags a big, but would like to get feedback and see what people think21:10
*** galstrom is now known as galstrom_zzz21:10
*** anilvenkata has quit IRC21:11
tdasilvaI created a few that maybe in the future can help us just to see where most bugs go?21:11
timburkei wish the graphs on http://status.openstack.org/bugday/ went back more than 3 days...21:11
notmynameinstead of trying to evaluate a bug based on the title listed (to decide if you're going to sign up for it), just sign up and then take a look :-)21:11
notmynametdasilva: those look great21:11
acolestdasilva: I think the service tags could be useful21:11
*** Manuel_112 has quit IRC21:11
notmynametdasilva: like a "bugweek" or something?! crazytalk21:12
tdasilvanotmyname: acoles and I thought of the same idea of maybe utilizing the first two days at PTG21:13
*** sambetts is now known as sambetts|afk21:13
tdasilvaif time allows21:13
notmynamethat's a great idea21:13
timburkei'm in :-)21:13
*** tobberydberg has joined #openstack-meeting21:13
tdasilvaif we plan it maybe even folks not going to PTG can participate21:13
notmynamewhat would be in the plan?21:14
* jungleboyj walks in late21:14
tdasilvaI guess to start is to announce that we are going going to do that ;)21:14
*** thorst has joined #openstack-meeting21:14
*** esberglu has joined #openstack-meeting21:14
tdasilvathen maybe get everybody to sign up for some number of bugs...idk never done this before... :D21:15
notmyname:-)21:15
acoleswe'll need to be flexible to allow us to attend useful stuff that may be happening on those days, but I like the idea21:15
tdasilvayep!21:15
notmynameok, I can imagine what that looks like (the announcement and organization)21:15
notmynameyeah21:16
notmynameI think we need to add a little bit of description to the top of the bug etherpad for people to come up to speed without having to have followed these meetings and the other IRC conversations21:17
notmynameI can work on that21:17
tdasilvasounds good21:17
*** tobberydberg has quit IRC21:18
notmynameis there anything more that needs to be brought up in this meeting about bug triage work?21:18
tdasilvathanks to Christian for getting that list up21:18
acoles+1 ^^21:18
notmynameyes! his work has been invaluable21:18
notmyname#topic upcoming releases, priority reviews21:19
*** openstack changes topic to "upcoming releases, priority reviews (Meeting topic: swift)"21:19
notmynameas I've talked about recently, I'd like to do releases asap21:19
notmyname#link https://wiki.openstack.org/wiki/Swift/PriorityReviews21:19
*** thorst has quit IRC21:19
notmynamethe priority reviews page has some important things listed21:19
notmynamehttps://review.openstack.org/#/c/448480 and https://review.openstack.org/#/c/478416/ and https://review.openstack.org/#/c/475038/ need reviews21:20
patchbotpatch 448480 - swift - DB replicator cleanup21:20
patchbotpatch 478416 - swift - Add multiple worker processes strategy to reconstr...21:20
patchbotpatch 475038 - python-swiftclient - Allow for uploads from standard input.21:20
notmynameI believe timburke and acoles are looking at the ec reconstructor one (right?)21:20
acolesnotmyname: yes21:20
notmynameone question I have is about acoles's composite replicated rings patch. where are we with it? could it get in? should it be added to the list?21:21
acolesyo mean https://review.openstack.org/#/c/47700021:22
patchbotpatch 477000 - swift - Ring rebalance respects co-builders' last_part_moves21:22
notmynamethe stdin swiftclient patch is something that will really help a lot of use cases21:22
notmynameacoles: maybe I do21:22
*** makowals has quit IRC21:22
acolesnotmyname: I'd love to have 477000 in next release, kota_ has been looking at it and i did have clayg's +221:22
mattoliverauI've been looking at the db replication one, not as much as I'd like.. just want to test on a my SAIO a little. Bec comes back soon so will have more time, but if others want to look feel free :)21:23
notmynamethanks mattoliverau21:23
kota_it looks acoles update the patch since i reviewed, so i should circle back to there21:23
notmynameI'd like to have a volunteer for the stdin swiftclient patch21:23
notmynamekota_: thanks21:24
*** abishop has quit IRC21:24
acoleskota_: thanks, I'll try to catch up with you at end of your day if you have any queries21:24
*** sshank has quit IRC21:25
*** thorst has joined #openstack-meeting21:25
notmynamecan someone volunteer to review https://review.openstack.org/#/c/475038/ please?21:26
patchbotpatch 475038 - python-swiftclient - Allow for uploads from standard input.21:26
jrichliI'll try to carve out some time to take a look this week21:26
tdasilvao/21:26
notmynamethanks jrichli and tdasilva21:27
notmynamethat's the last patch needed for a swiftclient release (aside from the boilerplate authors/changelog update)21:27
notmynameIthink that covers the stuff on priority reviews21:28
notmynameany questions/comments/concerns over upcoming releases?21:28
*** makowals has joined #openstack-meeting21:28
notmynamenote that the docs migration stuff is still in progress (most of the big stuff is done, but there's a little more to do yet)21:29
notmynameoh, the swiftclient docs migration has a little bit to do, IIRC. that should be done before a release. i'll work on that21:29
*** ihrachys has quit IRC21:29
notmyname#topic barbica/castellan dependency21:30
*** openstack changes topic to "barbica/castellan dependency (Meeting topic: swift)"21:30
notmynametdasilva: this is your topic. what's up?21:30
notmynamehttps://review.openstack.org/#/c/364878/2821:30
patchbotpatch 364878 - swift - Retrieve encryption root secret from Barbican21:30
tdasilvaso i've been reviewing mathiasb patch and noticed that it depends on castellan, but the patch does not update requirements.txt21:30
tdasilvatalked to mathiasb a bit and it seems that is still up in the air on whether we want to add that dependency or not21:31
tdasilvaso I just wanted to hear from folks what they think are the pros and cons21:31
*** martial has joined #openstack-meeting21:31
notmynamewhat if we added the functionality without the requirements update (for now) and added the requirements update later, in part depending on it's usage21:32
notmyname(yes I know there's a catch-22 there)21:32
*** sshank has joined #openstack-meeting21:32
acolestdasilva: is it similar scenario to keystonemiddleware which is also not in requirements.txt?21:32
jrichliI think I had given mathiasb the advice to shy away from the dependency.  so as not to require that unless you used that middleware21:32
timburkeadd it to [extras] in setup.cfg?21:33
tdasilvatimburke: hmm...interesting, had not heard of that before21:33
timburkeacoles: there's a slight difference, in that we don't *import* from keystonemiddleware21:33
tdasilvaand that's what i was thinking, how do we at least point users to these other dependencies that they might need21:33
tdasilvaextra-requirements.txt ??21:33
mathiasbwe've discussed it in person and in the patch comments, and imho the consensus has been not to add the dependencies at this time in requirements.txt21:33
timburkethen you can do things like `pip install swift[castellan]` or w/e21:34
timburkewe currently do something like that for swiftclient: https://github.com/openstack/python-swiftclient/blob/master/setup.cfg#L35-L3721:34
notmynameI'm not very familiar with that mechanic, but it seems like a simple solution21:35
*** priteau has quit IRC21:35
notmynamemathiasb: tdasilva: what do you think?21:35
tdasilvayep, then we can just document it21:35
timburkehttps://www.python.org/dev/peps/pep-0426/#extras-optional-dependencies21:35
acolestimburke: that's interesting, had not noticed that mechanism before21:35
mathiasbi'm not familiat with that either, but i can definitely look into it21:35
notmynamecool! a way forward!21:36
*** ansmith has joined #openstack-meeting21:36
*** bobh has quit IRC21:36
mathiasbwe do mention the requirements in the docs21:36
notmynametdasilva: mathiasb: were there other things to bring up on this topic here in the meeting?21:36
tdasilvaalso, the patch already has a +2 and I've been reviewing and think it looks pretty good, but it would be nice to get other folks to review before I give my +221:37
tdasilvaespecially folks that have been playing with encryption before :D21:37
notmynamejrichli: would you have any time to look?21:37
tdasilvamaybe we can have barbican support in Pike! :D21:38
*** christian1110 has quit IRC21:38
notmynamethat would be really great!21:38
jrichlinotmyname: its on my list to review - i had started, but got interupted21:38
notmynamethanks21:38
notmynametdasilva: but please don't let jrichli's review hold up your review. go ahead and put your vote down too :-)21:39
tdasilvaok, i think we will need another patchset, but mostly around 'smaller' items like we just discussed and docs21:39
acoleslast time I looked it seemed in good shape21:39
tdasilvacode is very small21:39
notmyname:-)21:40
*** makowals has quit IRC21:40
notmynameanything else on this patch?21:40
mathiasbthere's a related barbicanclient bug that tdasilva discovered that people actually running the code might bump into21:40
notmynameshould it block this patch?21:41
tdasilvablocks testing :D21:41
notmynamehmmm. that's not good21:41
*** boris-42___ has quit IRC21:41
mathiasbtdasilva: do you have the link? typing on my phone atm :/21:41
tdasilvayeah, you kinda have to go manually21:41
tdasilvasmall change21:41
tdasilvahttps://review.openstack.org/#/c/484926/221:41
patchbotpatch 484926 - python-barbicanclient - fix default version21:41
tdasilvai think barbican client had a big refactor a few days ago and it introduced a small regression21:42
notmynameshould the swift patch have a depends-on?21:42
*** Sukhdev has quit IRC21:42
tdasilvathe patch itself doesn't depend on it21:42
notmynameoh. yeah, I was noticing that the gate passes21:42
tdasilvait's mathiasb script to set the env up that depends on it21:42
*** Sukhdev has joined #openstack-meeting21:43
tdasilvabtw: mathiasb script and Vagrantfile are very useful, thank you mathiasb!21:43
mathiasbyw, anything to make testing and reviewing easier!21:44
jrichli+121:44
notmynamedo you have any concerns about landing our patch before the barbican client patch?21:45
notmynameor we should land ours and encourage them to land theirs and everything is good?21:45
notmyname(ie no defined order)21:45
tdasilvanotmyname: no, but honestly i don't think it will happend. the barbican patch is small and I'd say "high priority" for them. client is broken, can't use it21:45
notmynameok21:46
notmynameso it's likely theirs will land first anyway :-)21:46
tdasilvai *think* so21:46
jrichlibut i guess that means we can't successfully run mathias's script currently?21:46
notmynamejrichli: you hear that? you're now in a race with the barbican team. go, go, go!21:46
jrichlilol21:47
*** baoli has joined #openstack-meeting21:47
*** Daisy_ has joined #openstack-meeting21:47
notmynameok, let' move on21:47
*** NicoleH has quit IRC21:47
tdasilvajrichli: no, it fails at the very end when setting up the barbican secret, but it is not hard to fix the client manually and then create the secret manually21:47
notmyname#topic open discussion21:47
*** VW_ has joined #openstack-meeting21:47
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:47
notmynameI was just looking at the openstack release dates. looks like we need a swift release by the week of august 21. that's not too far away. in part meaning that if we cut a swift release now, we'll have a fast-follow for another right before pike21:47
notmynamealso that when we cut swiftclient, that will very very likely be what's in pike21:48
*** baoli has quit IRC21:48
notmynamedoes anyone else have anything to bring up in today's meeting?21:48
*** marst_ has joined #openstack-meeting21:48
notmynamereminder that the 0700 meeting is happening next week. thanks kota_ for chairing21:48
kota_o/21:48
kota_will do my best21:49
notmynamethen it will be fantastic21:49
*** gouthamr has quit IRC21:49
*** baoli has joined #openstack-meeting21:50
notmynamejust as an FYI, I'll be out for the first two weeks of august on a family trip. I'll have limited time online21:50
notmynamethank you for your work on swift this week!21:50
*** VW has quit IRC21:50
notmynamethanks for coming to the meeting21:50
notmyname#endmeeting21:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:50
openstackMeeting ended Wed Jul 19 21:50:37 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2017/swift.2017-07-19-21.00.html21:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2017/swift.2017-07-19-21.00.txt21:50
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2017/swift.2017-07-19-21.00.log.html21:50
*** patchbot has left #openstack-meeting21:50
jungleboyjThanks all!21:51
*** acoles has left #openstack-meeting21:51
*** Daisy_ has quit IRC21:51
*** VW_ has quit IRC21:51
*** marst has quit IRC21:52
*** kota_ has left #openstack-meeting21:52
*** martial has quit IRC21:53
*** galstrom_zzz is now known as galstrom21:54
*** timburke has left #openstack-meeting21:55
*** annabelleB has quit IRC21:55
*** jrichli has left #openstack-meeting21:56
*** marst_ has quit IRC21:57
*** martial has joined #openstack-meeting21:57
*** martial has quit IRC21:57
*** imcsk8 has quit IRC21:58
*** imcsk8 has joined #openstack-meeting21:58
*** lpetrut_ has quit IRC22:04
*** Manuel_112 has joined #openstack-meeting22:09
*** ykatabam has joined #openstack-meeting22:10
*** frank_young has joined #openstack-meeting22:12
*** annabelleB has joined #openstack-meeting22:14
*** Manuel_112 has quit IRC22:14
*** felipemonteiro_ has quit IRC22:15
*** frank_young has quit IRC22:16
*** rwsu has quit IRC22:17
*** rbudden has quit IRC22:18
*** gouthamr has joined #openstack-meeting22:18
*** rossella__ has joined #openstack-meeting22:19
*** Apoorva has quit IRC22:21
*** Apoorva has joined #openstack-meeting22:22
*** rossella_ has quit IRC22:22
*** sshank has quit IRC22:25
*** baoli has quit IRC22:26
*** makowals has joined #openstack-meeting22:28
*** annabelleB has quit IRC22:30
*** m_kazuhiro has quit IRC22:30
*** annabelleB has joined #openstack-meeting22:31
*** julim has joined #openstack-meeting22:31
*** sdague has quit IRC22:33
*** baoli has joined #openstack-meeting22:36
*** annabelleB has quit IRC22:37
*** edmondsw has quit IRC22:40
*** galstrom is now known as galstrom_zzz22:41
*** sshank has joined #openstack-meeting22:44
*** thorst has quit IRC22:56
*** vishwana_ has quit IRC22:58
*** vishwanathj has joined #openstack-meeting22:58
*** frank_young has joined #openstack-meeting22:59
*** annabelleB has joined #openstack-meeting23:03
*** yamamoto has joined #openstack-meeting23:04
*** rbudden has joined #openstack-meeting23:06
*** Manuel_112 has joined #openstack-meeting23:11
*** tobberydberg has joined #openstack-meeting23:15
*** Manuel_112 has quit IRC23:15
*** jaypipes has quit IRC23:16
*** yamamoto has quit IRC23:18
*** tobberydberg has quit IRC23:19
*** Patifa has quit IRC23:20
*** frank_young has quit IRC23:27
*** hongbin has quit IRC23:30
*** esberglu has quit IRC23:33
*** esberglu has joined #openstack-meeting23:33
*** esberglu has quit IRC23:33
*** rcernin has quit IRC23:34
*** sshank has quit IRC23:34
*** eharney has quit IRC23:35
*** chyka has quit IRC23:37
*** frank_young has joined #openstack-meeting23:37
*** frank_young has quit IRC23:41
*** annabelleB has quit IRC23:41
*** Swami has quit IRC23:44
*** rbudden has quit IRC23:46
*** rossella__ has quit IRC23:50
*** makowals has quit IRC23:51
*** thinrichs has joined #openstack-meeting23:52
*** ykatabam1 has joined #openstack-meeting23:52
*** rossella__ has joined #openstack-meeting23:52
*** mtanino_ has quit IRC23:53
*** ykatabam has quit IRC23:53
*** ttrifonov has quit IRC23:57
*** edmondsw has joined #openstack-meeting23:59

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