Wednesday, 2018-04-11

*** priteau has joined #openstack-meeting00:03
*** priteau has quit IRC00:03
*** yamahata has joined #openstack-meeting00:07
*** annabelleB has quit IRC00:08
*** aeng has joined #openstack-meeting00:09
*** fnaval has quit IRC00:16
*** cloudrancher has quit IRC00:17
*** cloudrancher has joined #openstack-meeting00:18
*** zhurong has joined #openstack-meeting00:21
*** liuzz has joined #openstack-meeting00:25
*** song has joined #openstack-meeting00:26
*** annabelleB has joined #openstack-meeting00:27
*** wanghao has joined #openstack-meeting00:29
*** Dinesh_Bhor has joined #openstack-meeting00:33
*** wanghao has quit IRC00:33
*** gyee has quit IRC00:33
*** wanghao has joined #openstack-meeting00:34
*** wanghao has quit IRC00:38
*** wanghao has joined #openstack-meeting00:38
*** yamamoto has joined #openstack-meeting00:43
*** wanghao has quit IRC00:43
*** wanghao has joined #openstack-meeting00:44
*** artom has joined #openstack-meeting00:45
*** zhujintao has joined #openstack-meeting00:47
*** wanghao has quit IRC00:47
*** wanghao has joined #openstack-meeting00:48
*** yamamoto has quit IRC00:48
*** mriedem has quit IRC00:49
*** aeng has quit IRC00:49
*** felipemonteiro__ has joined #openstack-meeting00:50
*** dmacpher has joined #openstack-meeting00:50
*** wanghao has quit IRC00:50
*** annabelleB has quit IRC00:50
*** wanghao has joined #openstack-meeting00:50
*** Yipei has joined #openstack-meeting00:51
*** Yipei has quit IRC00:54
*** Yipei has joined #openstack-meeting00:54
*** wanghao has quit IRC00:54
*** wanghao has joined #openstack-meeting00:55
*** AndroUser has joined #openstack-meeting00:56
*** zhiyuan has quit IRC00:57
*** xuzhuang has joined #openstack-meeting00:58
*** Dinesh__Bhor has joined #openstack-meeting00:58
*** wanghao has quit IRC00:58
*** zhiyuan has joined #openstack-meeting00:58
*** wanghao has joined #openstack-meeting00:58
zhiyuan#startmeeting tricircle01:00
openstackMeeting started Wed Apr 11 01:00:18 2018 UTC and is due to finish in 60 minutes.  The chair is zhiyuan. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:00
*** wanghao has quit IRC01:00
*** Dinesh_Bhor has quit IRC01:00
*** openstack changes topic to " (Meeting topic: tricircle)"01:00
openstackThe meeting name has been set to 'tricircle'01:00
*** wanghao has joined #openstack-meeting01:00
zhiyuanhello, AndroUser01:01
*** cyg has joined #openstack-meeting01:01
zhiyuanYipei, how's the investigation about routed network? is it possible to attach a router to it in central neutron?01:02
*** shu-mutow-AWAY is now known as shu-mutow01:02
xuzhuangsorry for late01:03
*** AndroUser has quit IRC01:03
*** wanghao has quit IRC01:03
zhiyuanxuzhuang, it's fine01:03
*** zxh has joined #openstack-meeting01:03
*** wanghao has joined #openstack-meeting01:03
*** fzdarsky_ has joined #openstack-meeting01:04
Yipeii think maybe we need to add a gateway port to the routed network, but we do not allocate IP to the port01:05
zhiyuanso when user queries the router, he/she will see a gateway port without IP?01:06
*** wanghao has quit IRC01:07
*** wanghao has joined #openstack-meeting01:08
*** fzdarsky has quit IRC01:08
*** fzdarsky_ has quit IRC01:09
*** wanghao has quit IRC01:11
Yipeinot test yet. if the port do not have an IP, i can get the info by cli01:11
*** wanghao has joined #openstack-meeting01:11
zhiyuanfloating ip allocation will be another problem. I guess routed network also doesn't support allocation a floating ip from it01:12
*** kaisers_ has joined #openstack-meeting01:12
Yipeithe field of ip_allocation is deferred. I can test it this week01:13
*** wanghao has quit IRC01:13
zhiyuanone question, when booting a VM in a routed network, what kind of port will be created?01:14
*** harlowja has quit IRC01:14
*** salv-orl_ has joined #openstack-meeting01:14
zhiyuana port with IP in both segment?01:14
Yipeijust a port without IP01:14
*** wanghao has joined #openstack-meeting01:14
*** fzdarsky_ has joined #openstack-meeting01:14
Yipeithe IP will be allocated based on the placement of the vm01:14
*** kaisers has quit IRC01:15
zhiyuanso after the placement of the VM, nova updates the ip of the port?01:15
Yipeiit is allocated by the dhcp agent in the compute node01:15
zhiyuanthen at least the port should belong to a subnet01:16
*** wanghao has quit IRC01:16
*** cyg_ has joined #openstack-meeting01:17
*** salv-orlando has quit IRC01:17
*** wanghao has joined #openstack-meeting01:17
*** oddzeng has joined #openstack-meeting01:17
Yipeino, when the port is created, it does not belong to any subnet, it just belong to the routed network01:17
Yipeiif the port is plugged to a vm, then the port is allocated to a subent01:18
*** wanghao has quit IRC01:19
zhiyuanand from API, the port is still without IP after VM booted?01:19
*** cyg has quit IRC01:19
Yipeisorry, not01:19
*** wanghao has joined #openstack-meeting01:19
Yipeiafter vm booted, an IP will be allocated01:19
zhiyuanso I think nova tells neutron which segment to allocate IP01:20
*** wanghao has quit IRC01:23
*** wanghao has joined #openstack-meeting01:23
*** iyamahat has quit IRC01:24
*** iyamahat has joined #openstack-meeting01:24
*** felipemonteiro__ has quit IRC01:25
*** wanghao has quit IRC01:25
*** wanghao has joined #openstack-meeting01:26
*** Yipei has quit IRC01:27
*** Yipei has joined #openstack-meeting01:28
*** wanghao has quit IRC01:29
*** wanghao has joined #openstack-meeting01:29
zhiyuanso after xmanager finishes the local router setup, we can get both the gateway IP, the question is where to store these IPs so user can query via the central gateway port01:29
zhiyuanif I am correct, port can only contain IPv4 and IPv6 address, not several IPv4 addresses01:30
Yipeiyes, i know your concern.01:32
*** ihrachys has quit IRC01:33
*** wanghao has quit IRC01:33
*** wanghao has joined #openstack-meeting01:34
zhiyuanis it hard to break such constraint for central gateway port?01:34
zhiyuanI guess we need to disable some validation in central plugin01:34
Yipeiyou mean we can add multiple IPs to a central gateway port?01:35
zhiyuanyes, since it's only a data container01:35
*** wanghao has quit IRC01:35
zhiyuanor we put the IPs info in description??01:35
*** dangtrinhnt has joined #openstack-meeting01:36
Yipeior tag?01:36
*** wanghao has joined #openstack-meeting01:36
zhiyuantag is also fine01:36
*** markstur has quit IRC01:38
Yipeiok, so let's put the IPs info in tag?01:38
*** wanghao has quit IRC01:39
*** wanghao has joined #openstack-meeting01:40
zhiyuanwill tag be showed by default when running "openstack port show"?\01:40
Yipeiyes, i tested01:40
*** hongbin has joined #openstack-meeting01:40
Yipeihold on01:40
*** wanghao has quit IRC01:40
*** wanghao has joined #openstack-meeting01:41
Yipeiyes, tested01:41
Yipeitag is shown01:41
zhiyuanfine :)01:41
zhiyuanso floating ip follows the same way. when created, it's a port without ip, after the local FIP is created and bound to VM, we update the central FIP01:42
zhiyuanthis time, we can directly update the IP, not via tag01:42
*** wanghao has quit IRC01:42
*** wanghao has joined #openstack-meeting01:43
*** yamamoto has joined #openstack-meeting01:44
zhiyuanso much for new l3 model, other topic?01:45
*** wanghao has quit IRC01:45
song  Use top_name plus top_id to set the name of bottom resource01:45
song    DB api reconstruction (to support different db access abstration tool, currently we are using SQLAlchemy)01:45
song    Upgradable(RPC message, db), support OVO01:45
song    Support different version of neutron API(different Region's Neutron may work in different version) compatibity01:45
songhi,zhiyuan. these fours works,which one do you think is the most import for us to do?01:45
*** wanghao has joined #openstack-meeting01:45
*** cyg__ has joined #openstack-meeting01:46
zhiyuanthe first and the forth01:46
songthanks I will do the first one.:)01:47
zhiyuanthat will make user easily to get the relation between central and local resource01:47
*** wanghao has quit IRC01:47
*** wanghao has joined #openstack-meeting01:48
songdoes it need a spec? or just write the code?01:48
*** cyg_ has quit IRC01:48
zhiyuanI think just code is fine01:49
zhiyuanif no other topic, let's end our meeting01:50
songno from me.01:50
*** yamamoto has quit IRC01:50
*** wanghao has quit IRC01:50
Yipeino from me01:50
xuzhuangno from me01:50
*** openstack changes topic to "OpenStack Meetings ||"01:51
openstackMeeting ended Wed Apr 11 01:51:02 2018 UTC.  Information about MeetBot at . (v 0.1.4)01:51
openstackMinutes (text):
*** wanghao has joined #openstack-meeting01:51
*** zhiyuan has quit IRC01:51
*** zxh has quit IRC01:51
*** xuzhuang has quit IRC01:52
*** wanghao has quit IRC01:52
*** wanghao has joined #openstack-meeting01:52
*** markstur has joined #openstack-meeting01:53
*** Yipei has quit IRC01:54
*** wanghao has quit IRC01:55
*** wanghao has joined #openstack-meeting01:56
*** zhurong has quit IRC02:00
*** wanghao has quit IRC02:00
*** wanghao has joined #openstack-meeting02:01
*** wanghao has quit IRC02:07
*** wanghao has joined #openstack-meeting02:07
*** wanghao has quit IRC02:13
*** wanghao has joined #openstack-meeting02:13
*** epico has joined #openstack-meeting02:17
*** cyg__ has quit IRC02:18
*** wanghao has quit IRC02:18
*** song has quit IRC02:18
*** Dinesh__Bhor has quit IRC02:18
*** wanghao has joined #openstack-meeting02:18
*** claudiub has quit IRC02:19
*** Dinesh__Bhor has joined #openstack-meeting02:20
*** wanghao has quit IRC02:20
*** wanghao has joined #openstack-meeting02:21
*** wanghao has quit IRC02:27
*** wanghao has joined #openstack-meeting02:27
*** oddzeng has quit IRC02:28
*** markstur has quit IRC02:30
*** wanghao has quit IRC02:32
*** wanghao has joined #openstack-meeting02:33
*** ricolin has joined #openstack-meeting02:34
*** ianychoi has quit IRC02:35
*** wanghao has quit IRC02:38
*** wanghao has joined #openstack-meeting02:38
*** armax has quit IRC02:40
*** wanghao has quit IRC02:43
*** wanghao has joined #openstack-meeting02:43
*** yamamoto has joined #openstack-meeting02:47
*** wanghao has quit IRC02:48
*** andreas_s has joined #openstack-meeting02:49
*** wanghao has joined #openstack-meeting02:50
*** yamamoto has quit IRC02:52
*** wanghao has quit IRC02:52
*** dangtrinhnt has quit IRC02:52
*** wanghao has joined #openstack-meeting02:53
*** sambetts|afk has quit IRC02:53
*** andreas_s has quit IRC02:54
*** sambetts_ has joined #openstack-meeting02:54
*** wanghao has quit IRC02:56
*** wanghao has joined #openstack-meeting02:57
*** ayoung has quit IRC02:58
*** psachin has joined #openstack-meeting03:00
*** wanghao has quit IRC03:01
*** wanghao has joined #openstack-meeting03:02
*** gongysh has joined #openstack-meeting03:06
*** wanghao has quit IRC03:08
*** wanghao has joined #openstack-meeting03:09
*** psachin has quit IRC03:09
*** dmacpher has quit IRC03:10
*** armax has joined #openstack-meeting03:10
*** wanghao has quit IRC03:13
*** wanghao has joined #openstack-meeting03:13
*** wanghao has quit IRC03:19
*** ianychoi has joined #openstack-meeting03:19
*** wanghao has joined #openstack-meeting03:20
*** wanghao has quit IRC03:24
*** wanghao has joined #openstack-meeting03:25
*** psachin has joined #openstack-meeting03:26
*** wanghao has quit IRC03:27
*** kei-ichi has quit IRC03:28
*** kei-ichi has joined #openstack-meeting03:28
*** caowei has joined #openstack-meeting03:33
*** vipul has quit IRC03:33
*** kaisers has joined #openstack-meeting03:37
*** kaisers_ has quit IRC03:37
*** yamamoto has joined #openstack-meeting03:48
*** VW has quit IRC03:50
*** yamamoto has quit IRC03:53
*** hongbin has quit IRC03:59
*** Qiming_ is now known as Qiming04:02
*** browny has quit IRC04:03
*** felipemonteiro__ has joined #openstack-meeting04:13
*** epico has quit IRC04:22
*** harlowja has joined #openstack-meeting04:23
*** browny has joined #openstack-meeting04:31
*** epico has joined #openstack-meeting04:45
*** yamamoto has joined #openstack-meeting04:50
*** felipemonteiro_ has joined #openstack-meeting04:51
*** felipemonteiro__ has quit IRC04:54
*** trinaths has joined #openstack-meeting04:55
*** yamamoto has quit IRC04:55
*** dineshbhor__ has joined #openstack-meeting04:58
*** Dinesh__Bhor has quit IRC04:59
*** felipemonteiro_ has quit IRC05:02
*** anilvenkata has joined #openstack-meeting05:11
*** dineshbhor__ has quit IRC05:12
*** gongysh has quit IRC05:12
*** sridharg has joined #openstack-meeting05:15
*** d0ugal has quit IRC05:16
*** marios has joined #openstack-meeting05:20
*** armax has quit IRC05:20
*** aeng has joined #openstack-meeting05:24
*** d0ugal has joined #openstack-meeting05:26
*** links has joined #openstack-meeting05:29
*** Alex_Staf has joined #openstack-meeting05:33
*** harlowja has quit IRC05:35
*** sidx64 has joined #openstack-meeting05:36
*** markvoelker_ has quit IRC05:39
*** trinaths has quit IRC05:46
*** gongysh has joined #openstack-meeting05:48
*** yamamoto has joined #openstack-meeting05:52
*** armax has joined #openstack-meeting05:54
*** yamamoto has quit IRC05:57
*** mardim has joined #openstack-meeting06:00
*** janzian has quit IRC06:01
*** kopecmartin has joined #openstack-meeting06:03
*** rubasov has left #openstack-meeting06:17
*** trinaths has joined #openstack-meeting06:18
*** armax has quit IRC06:20
*** armax has joined #openstack-meeting06:20
*** ad_ri3n_ has joined #openstack-meeting06:24
*** armax has quit IRC06:25
*** hemna_ has quit IRC06:29
*** jhesketh_ is now known as jhesketh06:29
*** dbecker has quit IRC06:32
*** priteau has joined #openstack-meeting06:32
*** belmoreira has joined #openstack-meeting06:33
*** radeks has joined #openstack-meeting06:33
*** ad_ri3n_ has quit IRC06:36
*** sidx64_ has joined #openstack-meeting06:39
*** sidx64 has quit IRC06:40
*** trinaths has quit IRC06:40
*** dmacpher has joined #openstack-meeting06:40
*** sidx64 has joined #openstack-meeting06:43
*** sidx64_ has quit IRC06:43
*** dbecker has joined #openstack-meeting06:44
*** slaweq has joined #openstack-meeting06:47
*** yamamoto has joined #openstack-meeting06:53
*** alexchadin has joined #openstack-meeting06:53
*** janki has joined #openstack-meeting06:54
*** yamamoto has quit IRC06:59
*** krenczew1 has quit IRC07:01
*** ad_ri3n_ has joined #openstack-meeting07:02
*** kaisers has quit IRC07:06
*** trinaths has joined #openstack-meeting07:06
*** rcernin has quit IRC07:06
*** trinaths has quit IRC07:06
*** yamamoto has joined #openstack-meeting07:08
*** trinaths has joined #openstack-meeting07:10
*** zhurong has joined #openstack-meeting07:11
*** HeOS has joined #openstack-meeting07:14
*** rbartal has joined #openstack-meeting07:17
*** trinaths has quit IRC07:25
*** dangtrinhnt has joined #openstack-meeting07:27
*** tesseract has joined #openstack-meeting07:28
*** claudiub has joined #openstack-meeting07:29
*** iyamahat has quit IRC07:29
*** gcb has joined #openstack-meeting07:30
*** dmacpher has quit IRC07:33
*** andreas_s has joined #openstack-meeting07:34
*** liuzz_ has joined #openstack-meeting07:35
*** liuzz has quit IRC07:35
*** belmoreira has quit IRC07:42
*** phil_ has joined #openstack-meeting07:45
*** lhx_ has joined #openstack-meeting07:46
*** belmoreira has joined #openstack-meeting07:46
*** yamamoto has quit IRC07:49
*** tssurya has joined #openstack-meeting07:54
*** markvoelker has joined #openstack-meeting08:01
*** rossella_s has joined #openstack-meeting08:02
*** arxcruz|off is now known as arxcruz|ruck08:04
diablo_rojo#startmeeting fc_sig08:04
openstackMeeting started Wed Apr 11 08:04:25 2018 UTC and is due to finish in 60 minutes.  The chair is diablo_rojo. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:04
*** openstack changes topic to " (Meeting topic: fc_sig)"08:04
openstackThe meeting name has been set to 'fc_sig'08:04
diablo_rojoSorry I'm late!08:04
diablo_rojodistracted by youtube08:04
mattoliveraulol, well at least you weren't asleep08:04
diablo_rojocmurphy, around?08:05
diablo_rojomattoliverau, nope not sleeping yet08:05
diablo_rojoSurprisingly not that tired.08:05
mattoliverauI haven't seen her say morning on the internal Suse chat.. so maybe running late08:05
diablo_rojoWe can give it another five minutes or so.08:05
diablo_rojoI'm in no rush.08:05
mattoliveraudiablo_rojo: sure, just make sure your next youtube vid is less then 5 mins :P08:06
diablo_rojo4 min and 16 seconds08:06
diablo_rojo#link Agenda for everyone's perusal :)08:08
*** zhurong has quit IRC08:08
*** trinaths has joined #openstack-meeting08:09
diablo_rojoWell I suppose we can get rolling08:10
diablo_rojo#topic New Contributor Patches!08:10
*** openstack changes topic to "New Contributor Patches! (Meeting topic: fc_sig)"08:10
diablo_rojoEveryone do their homework?08:10
diablo_rojoI think we are actually making solid progress.08:11
gmannyea, i just finished review part 5 min ago08:11
mattoliveraukinda.. I looked. and opened the openstack ansible one.. but that's as far as I got today.. was a little busier then I expected08:11
mattoliveraugmann: nice work :)08:11
diablo_rojoI've just been keeping up with the new StoryBoard ones.08:11
diablo_rojogmann, nice :)08:11
mattoliverauSo dunce hat for me this week then :)08:12
gmannmanaged to get one of the tempest patch in from new contributor who did not show up and fixed trivial things by myself. once he saw his patch merge then may be he come back :)08:12
diablo_rojomattoliverau, demerit on this topic, but you'll get part of a gold star later for other things so it should balance out.08:12
mattoliveraugmann: lol, now that they're a contributor :)08:12
diablo_rojogmann, that would be cool08:12
gmannyea :)08:12
*** pcaruana has joined #openstack-meeting08:13
*** yamamoto has joined #openstack-meeting08:13
diablo_rojoAnyone got anything else for this?08:13
gmannnothing from me.08:14
mattoliverauso whats the best way to ping a liason.. in channel or add them to the review.. or both? ;)08:14
diablo_rojomattoliverau, I would say ping them directly08:14
diablo_rojoand maybe also add them as a reviewer after you ping them so they don't forget08:15
mattoliveraucool, was wondering if I could be lazy :P08:15
*** yamamoto has quit IRC08:15
mattoliverauthat's all I have :)08:16
diablo_rojoJust how lazy did you want to be? :)08:16
mattoliverauI was just in a hurry today. And wondered.. but everyone should be in #openstack-dev so really a ping is easier as otherwise I have to look them up via gerrit08:17
*** belmoreira has quit IRC08:17
* mattoliverau assumes they all would be with bouncers etc anyway08:18
diablo_rojoMakes sense. A ping I think works well.08:18
diablo_rojoYeah that would be my assumption as well08:18
diablo_rojoFor most people anyway08:18
diablo_rojoNext topic?08:18
*** yamamoto has joined #openstack-meeting08:19
diablo_rojo#topic New Contributor of the Month08:19
*** openstack changes topic to "New Contributor of the Month (Meeting topic: fc_sig)"08:19
diablo_rojoSo I was dragging my feet on this for two reasons08:19
diablo_rojo1. I couldn't remember exactly where we decided to give this person attention (dev digest doesn't seem to be a thing here lately)08:20
diablo_rojo2. Wanted to wait for her to get her first patch merged, but she hasn't had much time to get comments addressed.08:20
diablo_rojoSo. Yeah.08:20
mattoliveraucool, fair enough. Wait for the merge08:20
*** belmoreira has joined #openstack-meeting08:21
mattoliverauas for 1. we should have a small blog post08:21
diablo_rojoJust the regular openstack blog? Like where the dev digest goes?08:21
mattoliverauthat can happen as frequently or as infrequently as required.08:21
diablo_rojoMakes sense to me.08:21
diablo_rojoSo that's all I had to say about that topic.08:22
mattoliverauif we can find a contributor every month.. great. we can call it "of the month"08:22
gmannyea, whenever we have its good to appraise08:22
mattoliverauotherwise, if it's only as frequent as we can. maybe we think of a different name08:22
*** aloga_ has joined #openstack-meeting08:22
diablo_rojoHa ha yeah or they can just be 'of the month' and then it can be 'of the month two months later'08:23
mattoliveraulol true08:23
mattoliverauwe never said the cadence would be montly :P08:23
mattoliverauits just of the month :P08:23
gmann"Emerging contributors" :)08:23
mattoliverauohh not bad08:24
mattoliverauhold on need to carry the toddler upstairs from her bath08:24
diablo_rojoThat is a good one08:24
diablo_rojoHa ha ha08:24
gmann:) mattoliverau  hehe08:24
diablo_rojoI suppose we can move onto the next topic as there won't be much to say there either.08:25
diablo_rojo#topic Ask.o.o08:25
*** openstack changes topic to "Ask.o.o (Meeting topic: fc_sig)"08:25
diablo_rojoNot seeing much new in the way of questions there08:26
gmannnothing new there in this week too.08:26
mattoliverausorry, toddler was wet, stairs are slippery and wife is pregnant so can't pick her up.08:26
mattoliverauyeah, I didn't see anything new.08:27
diablo_rojoThat sounds like a scary combo for any human let along a pregnant one.08:27
mattoliverauits true08:27
diablo_rojoOne noteable thing on this topic was that Jimmy (at the foundation) was asking about getting help watch it and was pleased when I told him we were.08:27
gmanni just answered the additional info in one of the question. otherwise no new things there08:27
diablo_rojoAlso asked if he wanted us to watch any other tags related to new contributors but haven't gotten any yet.08:27
diablo_rojomattoliverau, just saw this old one:
mattoliverauahh good question. good cause so far it feels quiet08:28
diablo_rojoYeah maybe there are tags we are missing that we should be looking at.08:28
diablo_rojoI just went for the obvious two08:28
mattoliverauin the past I just vulenteered asettle for that :P08:29
diablo_rojobut if either of you have new ideas for tags I am all for adding to our list08:29
diablo_rojomattoliverau, lol08:29
diablo_rojoI am sure she appreciated that.08:29
mattoliveraushe loved it, ask her about it next time ;)08:29
diablo_rojoHa ha will do.08:30
diablo_rojoAnywho, other tags?08:30
*** anilvenkata has quit IRC08:30
mattoliverauhmm, going to tags is a big wall of text that my brain can't handle right now.08:31
diablo_rojomattoliverau, I was about to say the same08:31
diablo_rojo#link ask.o.o wall of tags08:31
mattoliverauduring the week I'll try and parse the list and see if any others pop up08:32
diablo_rojoAnd they get so teeny towards the bottom08:32
diablo_rojoSounds good. I will try to do the same.08:32
diablo_rojoNext topic?08:32
mattoliverauyeah, I assume that means there not used as much. So anything bigger would be more useful08:32
diablo_rojoMy assumption as well08:32
mattoliveraumaybe even copy and paste and get thing in one column or something08:33
gmannis it all pre approved tag or they are being added whatever author tag?08:33
diablo_rojoConcerning that Juno and Icehouse are so close to the top for how old they are08:33
diablo_rojogmann, I think they are just whatever the author added08:33
* diablo_rojo tries to recall when I set up my dummy question08:33
mattoliveraumaybe there are still people out there using them. or maybe there also updated when topics are visited?08:34
diablo_rojowhen *she set up08:34
gmannthen we should restrict those and allow only pre approvd tag like LP ?08:34
mattoliverauyeah, emoting language can be hard :P08:34
* diablo_rojo is normally pretty good at it08:34
diablo_rojogmann, yeah that would be helpful08:34
diablo_rojotoday I learned that TripleO has all their tags documented and its in their repo even08:35
mattoliverauouch sort by name is worse08:35
diablo_rojoIts beautiful.08:35
mattoliverausizes don't change08:35
mattoliverauoh cool08:35
diablo_rojoI think size corresponds to usage.08:35
diablo_rojoLarger means more uses08:35
gmanni will check that part sometime if we can have allowed tag only there.08:35
diablo_rojoLove how Nova is first lol08:36
diablo_rojoOh if you hover over the word you can see how many times its used.08:36
diablo_rojoSwift has 128208:36
mattoliverauahh cool. Maybe I should go look at those questions and make sure there answers are up to date08:37
mattoliverauover time of course.. 1282 is too much for me in one go :P08:37
diablo_rojoYeah I would take that a few at a time.08:37
*** trinaths has quit IRC08:38
diablo_rojoAnything else here?08:38
diablo_rojoOr shall I move on?08:38
gmannmattoliverau: may be last 6 months are good to take, older one might be not seen by author now :)08:38
diablo_rojoAttainable goals :)08:38
diablo_rojo#topic rollover of #openstack-10108:39
*** openstack changes topic to "rollover of #openstack-101 (Meeting topic: fc_sig)"08:39
mattoliverautrue but peolpe looking for answers will look at old answers08:39
diablo_rojomattoliverau, you're up :)08:39
mattoliverauCool, so I've gone and raised 2 patches to remove #openstack-101 from the irc bots08:40
mattoliverauBoth have at least 1 +2 each.08:40
mattoliverauthanks you two for given them a +1 :)08:40
*** electrofelix has joined #openstack-meeting08:40
diablo_rojoNo problem :)08:41
gmannthanks :)08:41
mattoliverauonce they land, we can do the next step. Which is getting up the redirect from #openstack-101 to #openstack-dev08:41
gmannthanks :)08:41
*** radeks has quit IRC08:41
mattoliveraufungi: said that there is no problem doing the redirect afterwards.. so lets do that08:41
*** ianychoi has quit IRC08:42
*** radeks has joined #openstack-meeting08:42
mattoliverauSo really I'm waiting for them to land. And then I'll go pester an infra-core/root to finish it off08:42
diablo_rojoI suppose I should have mentioned them in the infra meeting today08:42
gmannmattoliverau: nice.  +108:43
mattoliverauthe documentation says, to wait (in channel before the redirect, cause otherwise you can't get back in) and remind people to leave and ofter some time week/month? they could be kicked08:43
diablo_rojoI think a week is fine08:43
diablo_rojogiven how few people watch the channel anyway08:43
mattoliveraudiablo_rojo: well if you could go back in time please, that would be great08:43
mattoliverauyeah +108:43
mattoliverauFor those playing along at home ^ there are the instructions for the redirect08:44
mattoliverauThe #openstack-101 channel topic has already been updated warning people it will be removed soon.08:45
diablo_rojoI might be talented but I am not so talented- or fortunate enough to have a tardis.08:45
gmannyea, show that.08:45
mattoliveraudiablo_rojo: no stress then :)08:45
mattoliverauthat's all the update I have there.08:45
diablo_rojoWorks for me. Thanks for doing all of that!08:46
mattoliveraus/there/on that topic/08:46
diablo_rojoI appreciate it mattoliverau :)08:46
gmannmattoliverau: yea, thanks.08:47
diablo_rojo#topic Forum Discussion Planning08:47
*** openstack changes topic to "Forum Discussion Planning (Meeting topic: fc_sig)"08:47
diablo_rojoCan't remember when I submitted them- was that before last meeting?08:47
* gmann thanks diablo_rojo and thsi topic which reminds to add QA forum topic before 15th 08:48
gmanndiablo_rojo: yea, 2 you submitted i think08:48
diablo_rojogmann, no problem :)08:49
diablo_rojoYes I did- for this group at least.08:49
diablo_rojoMore to come for other things I am working on.08:49
mattoliveraucool, and thanks again for summitting them!08:49
diablo_rojoFeel free to go make comments on them in support of the topics if you feel so compelled08:49
gmannyea nice idea08:50
*** zhurong has joined #openstack-meeting08:50
*** aeng has quit IRC08:50
diablo_rojo#link Forum Topic Submission Tool08:50
diablo_rojoHopefully one or both are selected08:50
diablo_rojoI think they are super important conversations to be had08:51
diablo_rojoBut we shall see how many more equally or more important get submitted :)08:51
diablo_rojoThat's all I had there :)08:52
diablo_rojoWas just to mention them if I hadn't08:52
diablo_rojoand ask for comments08:52
mattoliverauit's also good to remind us so we remember to make comments and keep thinking about/organising them :)08:53
diablo_rojoThat too08:53
mattoliverauuntil the summit it should be a sticky topic IMHO08:53
diablo_rojoHappy to leave it on the agenda08:53
*** yamamoto has quit IRC08:54
diablo_rojo#topic Open Discussion08:54
*** openstack changes topic to "Open Discussion (Meeting topic: fc_sig)"08:54
diablo_rojo6 min left :)08:54
*** yamamoto has joined #openstack-meeting08:56
diablo_rojoAnyone got anything else? :)08:56
gmannnothing from my side.08:56
diablo_rojoEveryone got summit hotels booked?08:57
mattoliveraudiablo_rojo: you can go watch more youtube.. or slepp :P08:57
gmannyea hotel and flight done, waiting for visa to come though08:57
diablo_rojomattoliverau, been watching youtube for the last few minutes off and on lol08:57
mattoliverauumm, not yet, but apparently someone from Suse is doing that as group or something sometihing08:57
diablo_rojoOkay that works :)08:57
diablo_rojoJust wanted to make sure everyone got the deal if they hadn't already08:58
*** yamamoto has quit IRC08:58
*** yamamoto has joined #openstack-meeting08:58
mattoliveraucool, well have a great night then all08:59
diablo_rojoThanks for coming!08:59
gmannthanks, gn08:59
*** openstack changes topic to "OpenStack Meetings ||"08:59
openstackMeeting ended Wed Apr 11 08:59:43 2018 UTC.  Information about MeetBot at . (v 0.1.4)08:59
openstackMinutes (text):
*** ttsiouts has joined #openstack-meeting09:00
*** shu-mutow is now known as shu-mutow-AWAY09:07
*** Alex_Staf has quit IRC09:10
*** Alex_Staf has joined #openstack-meeting09:12
*** lpetrut has joined #openstack-meeting09:16
*** beekhof has quit IRC09:17
*** armax has joined #openstack-meeting09:18
*** aloga_ has quit IRC09:20
*** armax has quit IRC09:23
*** anilvenkata has joined #openstack-meeting09:38
*** yamamoto has quit IRC09:43
*** yamamoto has joined #openstack-meeting09:44
*** ianychoi has joined #openstack-meeting09:46
*** alexchadin has quit IRC09:47
*** alexchadin has joined #openstack-meeting09:48
*** alexchadin has quit IRC09:48
*** alexchadin has joined #openstack-meeting09:49
*** alexchadin has quit IRC09:49
*** alexchadin has joined #openstack-meeting09:50
*** alexchadin has quit IRC09:50
*** alexchadin has joined #openstack-meeting09:50
*** alexchadin has quit IRC09:51
*** alexchadin has joined #openstack-meeting09:51
*** alexchadin has quit IRC09:51
*** alexchadin has joined #openstack-meeting09:52
*** alexchadin has quit IRC09:56
*** hyunsikyang has quit IRC10:06
*** verdurin has joined #openstack-meeting10:08
*** alexchadin has joined #openstack-meeting10:23
*** rajinir has quit IRC10:25
*** lpetrut has quit IRC10:27
*** lpetrut has joined #openstack-meeting10:30
*** alexchadin has quit IRC10:45
*** alexchadin has joined #openstack-meeting10:50
*** e0ne has joined #openstack-meeting10:54
*** alexchadin has quit IRC11:03
*** e0ne has quit IRC11:04
*** beekhof has joined #openstack-meeting11:07
*** yamamoto has quit IRC11:18
*** e0ne has joined #openstack-meeting11:20
*** armax has joined #openstack-meeting11:20
*** epico has quit IRC11:21
*** armax has quit IRC11:24
*** yamamoto has joined #openstack-meeting11:25
*** sambetts_ is now known as sambetts11:28
*** yamamoto has quit IRC11:30
*** yamamoto has joined #openstack-meeting11:34
*** yamamoto has quit IRC11:39
*** phil_ has quit IRC11:41
*** rfolco|off is now known as rfolco|rover11:44
*** raildo has joined #openstack-meeting11:58
*** erlon has quit IRC12:03
*** edmondsw has joined #openstack-meeting12:08
*** cloudran_ has joined #openstack-meeting12:11
*** erlon has joined #openstack-meeting12:12
*** cloudrancher has quit IRC12:13
*** alexchadin has joined #openstack-meeting12:15
*** tpsilva has joined #openstack-meeting12:16
*** yamamoto has joined #openstack-meeting12:21
*** yamamoto has quit IRC12:25
*** rbartal has quit IRC12:27
*** gcb has quit IRC12:27
*** yamamoto has joined #openstack-meeting12:34
*** rbudden has joined #openstack-meeting12:37
*** dustins has joined #openstack-meeting12:49
*** VW has joined #openstack-meeting12:50
*** VW has quit IRC12:51
*** VW has joined #openstack-meeting12:52
*** rbudden has quit IRC12:53
*** pchavva has joined #openstack-meeting12:54
*** salv-orl_ has quit IRC12:54
*** felipemonteiro has joined #openstack-meeting12:54
*** gman-tx has joined #openstack-meeting12:56
*** VW has quit IRC12:56
*** jaypipes has joined #openstack-meeting12:59
*** bobh has joined #openstack-meeting13:01
*** psachin has quit IRC13:05
*** mriedem has joined #openstack-meeting13:06
*** felipemonteiro_ has joined #openstack-meeting13:07
*** kgiusti has joined #openstack-meeting13:08
*** felipemonteiro has quit IRC13:10
*** cloudran_ has quit IRC13:14
*** cloudrancher has joined #openstack-meeting13:15
*** felipemonteiro_ has quit IRC13:15
*** felipemonteiro__ has joined #openstack-meeting13:15
*** cdub has joined #openstack-meeting13:16
*** hyunsikyang has joined #openstack-meeting13:21
*** armax has joined #openstack-meeting13:21
*** radeks has quit IRC13:21
*** radeks has joined #openstack-meeting13:22
*** armax has quit IRC13:26
*** julim has joined #openstack-meeting13:29
*** zhujintao has left #openstack-meeting13:30
*** sidx64 has quit IRC13:30
*** cdub has quit IRC13:32
*** fnaval has joined #openstack-meeting13:32
*** gcb has joined #openstack-meeting13:33
*** esberglu has joined #openstack-meeting13:35
*** sidx64 has joined #openstack-meeting13:35
*** lhx_ has quit IRC13:36
*** Alex_Staf has quit IRC13:36
*** jamesmcarthur has joined #openstack-meeting13:37
*** VW has joined #openstack-meeting13:38
*** VW has quit IRC13:40
*** mjturek has joined #openstack-meeting13:40
*** VW has joined #openstack-meeting13:41
*** david-lyle has joined #openstack-meeting13:41
*** stakeda has joined #openstack-meeting13:43
*** alexchadin has quit IRC13:44
*** dklyle has quit IRC13:45
*** hongbin has joined #openstack-meeting13:47
*** david-lyle has quit IRC13:47
*** zz9pzza has quit IRC13:48
*** fzdarsky_ is now known as fzdarsky13:48
*** erlon has quit IRC13:48
*** nmagnezi has joined #openstack-meeting13:49
*** rbartal has joined #openstack-meeting13:52
*** felipemonteiro_ has joined #openstack-meeting13:54
*** javier_ has joined #openstack-meeting13:54
*** javier_ has joined #openstack-meeting13:54
*** javier_ has joined #openstack-meeting13:54
*** ttx has quit IRC13:55
*** ttx has joined #openstack-meeting13:57
*** links has quit IRC13:58
*** zhipeng has joined #openstack-meeting13:58
*** felipemonteiro__ has quit IRC13:58
*** rbudden has joined #openstack-meeting13:58
*** eharney has joined #openstack-meeting14:00
*** rbudden has quit IRC14:01
*** lseki has joined #openstack-meeting14:01
*** julim_ has joined #openstack-meeting14:02
*** daidv has joined #openstack-meeting14:03
*** julim has quit IRC14:04
*** simon-AS559 has joined #openstack-meeting14:10
*** gongysh has quit IRC14:12
*** kiennt26 has joined #openstack-meeting14:12
*** salv-orlando has joined #openstack-meeting14:13
*** rbartal has quit IRC14:13
*** lseki has quit IRC14:13
*** daidv has quit IRC14:15
*** gman-tx has quit IRC14:18
*** iyamahat has joined #openstack-meeting14:19
*** kaisers has joined #openstack-meeting14:23
*** bobh has quit IRC14:25
*** kongwei has joined #openstack-meeting14:28
*** iyamahat has quit IRC14:29
*** iyamahat has joined #openstack-meeting14:30
*** dklyle has joined #openstack-meeting14:35
*** anilvenkata has quit IRC14:35
*** dklyle has quit IRC14:36
*** david-lyle has joined #openstack-meeting14:36
*** hemna_ has joined #openstack-meeting14:39
*** amodi has joined #openstack-meeting14:44
*** annabelleB has joined #openstack-meeting14:45
*** dklyle has joined #openstack-meeting14:47
*** david-lyle has quit IRC14:47
*** rbudden has joined #openstack-meeting14:47
*** javier_ has quit IRC14:48
*** felipemonteiro_ has quit IRC14:50
*** felipemonteiro_ has joined #openstack-meeting14:50
*** rajinir has joined #openstack-meeting14:51
*** aagate has joined #openstack-meeting14:51
*** cloudrancher has quit IRC14:52
*** cloudrancher has joined #openstack-meeting14:53
*** ansmith has joined #openstack-meeting14:55
*** markvoelker has quit IRC14:55
*** marie_ has joined #openstack-meeting14:55
*** dpertin has joined #openstack-meeting14:56
*** markvoelker has joined #openstack-meeting14:56
*** eeiden has joined #openstack-meeting14:57
*** bobh has joined #openstack-meeting14:57
*** zz9pzza has joined #openstack-meeting14:58
*** jdandrea has joined #openstack-meeting14:58
*** walshh has joined #openstack-meeting15:00
ad_ri3n_#startmeeting fog-edge-massively-distributed-clouds15:00
openstackMeeting started Wed Apr 11 15:00:32 2018 UTC and is due to finish in 60 minutes.  The chair is ad_ri3n_. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: fog-edge-massively-distributed-clouds)"15:00
openstackThe meeting name has been set to 'fog_edge_massively_distributed_clouds'15:00
*** markvoelker has quit IRC15:00
ad_ri3n_#chair  ad_ri3n_15:00
openstackCurrent chairs: ad_ri3n_15:00
ad_ri3n_#topic roll call15:00
*** openstack changes topic to "roll call (Meeting topic: fog-edge-massively-distributed-clouds)"15:00
ad_ri3n_Hi guys ?15:00
*** armax has joined #openstack-meeting15:01
ad_ri3n_ansmith:  kgiusti ?15:02
ad_ri3n_parus ?15:02
ad_ri3n_hi jamemcc15:02
ad_ri3n_I just read parus might be late15:03
*** joadavis has joined #openstack-meeting15:03
ad_ri3n_so let's start15:03
ad_ri3n_#info agenda15:03
ad_ri3n_#link (line 391)15:03
*** joadavis has left #openstack-meeting15:03
*** gman-tx has joined #openstack-meeting15:03
*** walshh has quit IRC15:04
ad_ri3n_#topic news15:04
*** openstack changes topic to "news (Meeting topic: fog-edge-massively-distributed-clouds)"15:04
*** rbudden_ has joined #openstack-meeting15:05
ad_ri3n_so not so much from my side to be honest (attending a summer school last week on experimental testbeds for edge infrastructures:
csatariThe correct #link
*** hwalsh has joined #openstack-meeting15:06
ad_ri3n_so I was expecting parus would give us a brief summary of what has been achieved during these two last weeks15:06
ad_ri3n_thanks csatari  (I can fix the link at the top of the etherpad).15:06
*** rbudden has quit IRC15:06
*** rbudden_ is now known as rbudden15:06
ad_ri3n_Thanks dpertin for the fix ;)15:06
ad_ri3n_so as I wrote, not so much from my side.15:07
ad_ri3n_Just that there will be a new SIG in the K8S community that will also discuss edge related challenges15:07
ad_ri3n_and I didn't unfortunately attend the edge session meeting this morning (1 UTC)15:08
ad_ri3n_csatari:  did you attend it?15:09
eeidenso sorry15:09
ad_ri3n_maybe you can update us a bit regarding the different action?15:09
csatariNope, it was 4AM for me.15:09
ad_ri3n_csatari:  any news regarding the current discussion and the wiki page you consolidated?15:09
csatariAny comments are welcome :) We will have a specific meeting on #edge-computing-group to discuss comments and questions.15:11
eeidenHey all -- just as a quick FYI I'm Elise Eiden, I'm transitioning into @jamemcc 's LCOO chair position. I've been working in the open source space for about four years, and as a developer on our OpenStack team for about two years.15:11
ad_ri3n_actually we should propose a slot15:11
eeidenLooking forward to working with you all :)15:11
ad_ri3n_thanks eeiden and welcome ;)15:11
csatariMy main aim with this was 1) to summarize what happened for myself 2) have a place where we store the things what we agreed on. Something what is more stable than a bunch of etherpads.15:12
ad_ri3n_csatari:  +115:12
ad_ri3n_I have a couple of comments/questions  I would like to discuss15:12
ad_ri3n_it is still not clear from my side what is the main target15:12
ad_ri3n_from our side, we (in particular dpertin) tries to identify what are the missing features in each key service (Keystone, Nova, Glance and Neutron)15:13
ad_ri3n_based on the requirements/information we have gathered15:13
csatariI think there are 2 targets:15:14
ad_ri3n_The simplest ones: should keystone be revised/extended to be able to define different rights per region/site?15:14
ad_ri3n_more complex: you want to boot a VM on site A but using a VMI stored on site B15:14
csatariCollect the high level features of an edge cloud infrastructure.15:14
ad_ri3n_the second feature may require more important changes on both Nova and Glance where as the simplest ones are only one single service based.15:14
csatariAnd to collect  the requirements of the actual components of different open source projects to implement these features.15:15
ad_ri3n_not sure I correctly understand your second point.15:15
ad_ri3n_the first one is clear15:15
csatariThat is the same what you wrote.15:15
csatariLike things what we need to implement in Keystone for example.15:16
ad_ri3n_so the second is diving into a particular components and try to identify what is missing?15:16
ad_ri3n_so do you think there is a third step15:16
ad_ri3n_identify what is not in the available components and that should be implemented outside15:16
ad_ri3n_because it is not related to the components.15:17
csatariYes: The component specific design (blueprint creation in case of OpenStack) and implementaiton.15:17
csatariTo decide the components relates to the 2nd step I believe.15:17
ad_ri3n_On the ML I was a bit lost as I didn't know whether the two first steps were completed15:17
ad_ri3n_from our side, not15:17
csatariNot perfectly.15:18
csatariBut we have something achieved in both steps.15:18
ad_ri3n_i.e. the gap analysis of the current mechanisms (at least major ones; keystone/Glance/Nova/Neutron) is not achieved yet15:18
csatariYes, we should work on that and extend the requrements part of the wiki.15:19
ad_ri3n_#action organize a dedicated meeting to go through the dublin wiki pge15:19
ad_ri3n_can you take the action csatari?15:19
ad_ri3n_parus is still not there so I propose to go on15:20
ad_ri3n_#topic ongoing-action-gapanalysis15:20
*** openstack changes topic to "ongoing-action-gapanalysis (Meeting topic: fog-edge-massively-distributed-clouds)"15:20
ad_ri3n_from our side, we are still waiting for the hotEdge notification15:20
ad_ri3n_@dpertin date?15:20
dpertinend of april i think15:20
ad_ri3n_(by end of april if I'm corect)15:20
ad_ri3n_ok thanks15:20
ad_ri3n_so keep fingers crossed15:20
ad_ri3n_maybe we can add the discussion regarding the page csatari consolidated on the wiki inside this action15:21
ad_ri3n_it looks relevant15:21
ad_ri3n_(at least from my side), unless someone disagrees I will take some notes in the pad15:21
csatariok for me15:22
ad_ri3n_ok done15:23
ad_ri3n_nothing more on that point15:23
ad_ri3n_if there is no question, let's move to the next one15:23
*** parus has joined #openstack-meeting15:23
ad_ri3n_ok so maybe let's go back just a bit15:23
ad_ri3n_hi parus15:23
ad_ri3n_#chair parus15:23
openstackCurrent chairs: ad_ri3n_ parus15:23
*** belmoreira has quit IRC15:23
parusSorry to be late.15:24
ad_ri3n_The floor is yours ;)15:24
dpertinhey parus15:24
*** andreas_s has quit IRC15:24
ad_ri3n_we already discussed news and gap analysis discussions15:24
parusWell I put some updates on the etherpad.15:24
parusOne was about the edgecomputing meeting yesterday night.15:24
ad_ri3n_but it would be great if you can give us a short update regarding the current discussions (in particular none attended the meeting this morning)??15:24
*** andreas_s has joined #openstack-meeting15:24
parusThe bulk of the discussion was around Prakash' proposal.15:25
*** gongysh has joined #openstack-meeting15:25
*** gongysh has quit IRC15:25
*** netapp has joined #openstack-meeting15:26
parusHe has rounded up a group of 4, 5 people to help with some proof of concept around cloudtle15:26
parusHe is looking for more help.15:26
ad_ri3n_I know people form inwinstack are porting some codes15:26
ad_ri3n_but it is related to live migration specifis15:26
ad_ri3n_if I'm right15:26
ad_ri3n_isn't it?15:26
parusIt is .15:26
parusLive migrations of VMs that are stateful.15:26
*** zhipeng has quit IRC15:27
parushe had a diagram, where an application can request storage for state and get it allocated on the edge node.15:27
ad_ri3n_I think we should give a look to this document15:27
ad_ri3n_do you a link toward such a diagram?15:27
*** eeiden_ has joined #openstack-meeting15:28
parusHe was building on that, and he was building on the ETSI MEC architecture.15:28
ad_ri3n_they are implementing the OEC proposal15:28
parusHe is talking about creating a new API, for the application to request storage.15:28
ad_ri3n_Rolf introduced to us15:28
ad_ri3n_at SF (during the opendev event)15:29
ad_ri3n_good to see things are progressing15:29
ad_ri3n_If I'm right they are complementaries15:29
parusThe issue I see is that his proposal goes beyond Openstack.15:29
*** iyamahat has quit IRC15:29
parusbut it includes some openstack features that extend openstack++ further.15:29
*** simon-AS559 has left #openstack-meeting15:29
parusSo expect a session on that when we are in Vancouver.15:30
parusThat is my update on the meeting this morning.15:30
ad_ri3n_maybe this should be written somewhere here15:30
ad_ri3n_can you please add something on that ?15:30
parus11:30 <ad_ri3n_> can you please add something on that ?15:30
parusI did.15:30
ad_ri3n_I would like to come back later15:30
ad_ri3n_ok I just saw it now15:31
parusline 1415:31
ad_ri3n_so if there is nothing more let's go back to the ongoing actions?15:31
parusThe other updates were related to ONS and the followups. Let me know if you hvave queestions.15:31
*** sridharg has quit IRC15:31
ad_ri3n_ok thanks15:31
ad_ri3n_I propose to go on and come back later (just to be sure we can discuss all aspects)15:32
ad_ri3n_#topic ongoing-action-cockroach15:32
*** openstack changes topic to "ongoing-action-cockroach (Meeting topic: fog-edge-massively-distributed-clouds)"15:32
ad_ri3n_not sure Marie is there15:33
ad_ri3n_(rcherreau is still on holidays, he will be back next monday)15:33
ad_ri3n_ok sorry15:33
*** yamahata has quit IRC15:33
ad_ri3n_so can you please let us know the current status of your experiments15:33
marie_there is not much to say, still gathering results15:34
* ad_ri3n_ is reading the pad15:34
ad_ri3n_maybe we can have first numbers for the next meeting ;)15:34
*** lpetrut_ has joined #openstack-meeting15:34
marie_yep !15:34
ad_ri3n_#topic ongoing-action-AMQP15:35
*** openstack changes topic to "ongoing-action-AMQP (Meeting topic: fog-edge-massively-distributed-clouds)"15:35
ad_ri3n_kgiusti: ansmith ?15:35
kgiustiI've been investigating a reported slow memory creep on both the router and the ombt2 clients15:35
kgiustibut have been unable to duplicate the issue as observed by msimonin15:36
*** bobh has quit IRC15:36
*** bobh_ has joined #openstack-meeting15:36
*** lpetrut has quit IRC15:36
kgiustiwe have a meeting tomorrow which we'll discuss this further15:36
kgiustithat's about it for me this week.15:37
kgiustimsimonin doesn't appear to be here today.15:37
kgiustiand I don't have the latest news from the testing effort.15:37
ad_ri3n_javier should be there also15:38
ad_ri3n_ok let's open this point15:38
*** msimonin has joined #openstack-meeting15:38
ad_ri3n_ah msimonin ;)15:38
kgiustispeak of the devil :)15:38
*** sanjay-redhat has joined #openstack-meeting15:38
*** andreas_s has quit IRC15:38
kgiustiHi msimonin!15:38
msimoninI heard some voices15:38
ad_ri3n_ok so I think we are done with AMQP15:38
msimoninHi kgiusti15:38
ad_ri3n_let's move to the next point :D15:38
ad_ri3n_msimonin:  please ;)15:38
*** edmondsw has quit IRC15:39
msimoninWhat's next (sorry) ?15:39
ad_ri3n_(BTW please let us know what is ombt-orchestrator with enoslib inside ;))15:39
ad_ri3n_we are discussing AMQP evaluations15:39
ad_ri3n_kgiusti just explained that he didn't succeed to reproduce the memory leaks you are facing15:40
msimoninoh I see15:40
msimoninkgiusti: are you able to use the orchestrator ?15:40
msimoninjavier made many changes lately15:40
msimoninrelated to packaging the tool properly15:41
*** kongwei has quit IRC15:41
kgiustimsimonin: not successful atm - tried some new hw today - see line 43615:41
kgiustimsimonin: yes I've gotten much further today with the latest oo15:41
*** kiennt26 has quit IRC15:41
ad_ri3n_msimonin:  kgiusti a few words on what is ombt-orchestrator please :-p?15:42
*** andreas_s has joined #openstack-meeting15:43
kgiustisorry - see line 438 - a tool for orchestrating the oslo.messaging scale tests15:43
msimoninthe orchestrator is an evaluation tool for testing oslo.messaging against various message bus15:43
msimoninkgiusti: First time I see this error15:44
msimoninCould you provide the the configuration ?15:44
kgiustimsimonin: yeah - we should probably take this off line to discuss the details15:44
kgiustimsimonin: I'll IM you15:45
msimoninkgiusti:  cool thanks15:45
*** annabelleB has quit IRC15:45
*** iyamahat has joined #openstack-meeting15:45
ad_ri3n_if there is no more information on that point I think we can move forward (I remind you that you have a few information on current results msimonin got a few lines above, please see the notes of the last discussion)15:46
msimoninI'm ok from my side, I'll try to help kgiusti15:46
ad_ri3n_#topic vancouver-summit15:47
*** openstack changes topic to "vancouver-summit (Meeting topic: fog-edge-massively-distributed-clouds)"15:47
ad_ri3n_so we created a dedicated etherpad to prepare the vancouver summit15:47
*** marios has quit IRC15:48
ad_ri3n_and add topics you would like to discuss15:48
ad_ri3n_brainstorming sessions you would like to propose to the forum.15:48
ad_ri3n_for the moment parus and I added some contents15:48
ad_ri3n_(and I added BTW a csatari proposal he pushed on the glance pad)15:49
ad_ri3n_see line 25.15:49
parusI think I saw an email for csatari about Keystone as well.15:49
ad_ri3n_so please don't be shy15:49
parusShould we add that here?15:49
ad_ri3n_csatari:  maybe I miss your keystone email?15:49
ad_ri3n_(I think it would be great if we can keep an eye of what has been proposed so far)15:50
csatariIn Keystone I'm not sure.15:50
csatariI mean if we need the feature. Maybe a Forum session could clarify the fog in my head....15:51
parusThere was an exchange between Ildyko and you and setting a meeting with Keystone and reviewing NKB prosposals.15:51
csatariparus: :)15:51
parus"Maybe we can share our two architecture alternatives (1) syncronise Keystone data with the New Kingbird 2) Multi region Keystone) with Keystone people. And ask feedback."15:51
parusWas that about Vancouver15:52
csatariNow I remember. Yes, I can add it to the Keystone etherpad, however it is not clear for me how the proposals get to the tool from the etherpads....15:53
ad_ri3n_the same15:54
ad_ri3n_ok I will send an email on the ML to try to make progress on that point too15:54
parusAbout my point on line 18 on the Vancouver Etherpad.15:54
ad_ri3n_yes ?15:55
parusI would like to have a whiteboard session maybe with a group.15:55
parusThere are architecture options emerging.15:55
ad_ri3n_I know there will be one or two panels dealing with security aspects on edge infrastructures15:55
ad_ri3n_parus :15:55
parusIt was not about security.15:55
parusMy bad.15:55
ad_ri3n_Maybe it is a formatting15:55
parusLet me update formatting.15:56
ad_ri3n_it is a formatting issue15:56
*** gyee has joined #openstack-meeting15:56
ad_ri3n_4 min lefts15:56
ad_ri3n_I propose to move to open-discussions15:56
ad_ri3n_#topic open-discussions15:56
*** openstack changes topic to "open-discussions (Meeting topic: fog-edge-massively-distributed-clouds)"15:56
*** ganso has joined #openstack-meeting15:56
ad_ri3n_ansmith:  kgiusti thanks15:56
ad_ri3n_first of all15:57
ad_ri3n_so if I correctly understood : let's wait and see15:57
ansmithevery chance we get, we provide an overview of this wg and the analysis going on15:57
ad_ri3n_ok regarding the pu/sub item?15:57
*** lseki has joined #openstack-meeting15:57
ad_ri3n_ansmith:  great15:57
*** andreas_s has quit IRC15:57
ad_ri3n_and thanks15:57
parusHas Pubnub ever been evaluated by this group?15:58
ad_ri3n_AFAIK no?15:58
parusIs there something clever they are doing that we could learn from?15:58
ad_ri3n_msimonin:  javier maybe you can give it a look15:58
ad_ri3n_to see theoretically speaking this may make sense?15:59
kgiustino - haven't heard of them b4 :)15:59
ad_ri3n_ok one minute left15:59
ad_ri3n_thanks you guys15:59
ad_ri3n_if you have comments, please feel free to add them into the pad15:59
ad_ri3n_#endmeeting 15:59
*** openstack changes topic to "OpenStack Meetings ||"15:59
openstackMeeting ended Wed Apr 11 15:59:46 2018 UTC.  Information about MeetBot at . (v 0.1.4)15:59
openstackMinutes (text):
*** sanjay-redhat has quit IRC16:00
jungleboyj#startmeeting cinder16:00
openstackMeeting started Wed Apr 11 16:00:04 2018 UTC and is due to finish in 60 minutes.  The chair is jungleboyj. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
*** jdandrea has left #openstack-meeting16:00
*** patriciadomin has quit IRC16:00
jungleboyjCourtesy ping:  jungleboyj DuncanT diablo_rojo, diablo_rojo_phon, rajinir tbarron xyang xyang1 e0ne gouthamr thingee erlontpsilva patrickeast tommylikehu eharney geguileo smcginnis lhx_ lhx__ aspiers jgriffith moshele hwalsh felipemonteiro lpetrut16:00
*** parus has left #openstack-meeting16:00
*** sgrasley1 has quit IRC16:00
_pewp_jungleboyj (¬_¬)ノ16:00
*** patriciadomin has joined #openstack-meeting16:01
*** geguileor is now known as geguileo16:01
*** kgiusti has left #openstack-meeting16:01
*** marie_ has quit IRC16:01
jungleboyjCool.  Looks like we have a good crowd here.16:02
jungleboyjLets get started.16:02
*** geguileo is now known as Guest4414916:02
jungleboyj#topic announcements16:02
*** openstack changes topic to "announcements (Meeting topic: cinder)"16:02
*** Guest44149 is now known as geguileor16:02
jungleboyjThank you to smcginnis for running the meeting last week.16:02
*** annabelleB has joined #openstack-meeting16:02
jungleboyjIan thanks you for freeing me up for his birthday lunch.  :-)16:02
jungleboyjI don't have a lot announcement wise.16:02
jungleboyjHopefully you all saw the tweets and e-mails about the reduced hotel prices for the Summit.16:03
*** ad_ri3n_ has quit IRC16:03
jungleboyjHope to see some of you there.16:03
jungleboyjAlso, the TC nomination period is open.  Have seen notes on the ML about that including the fact that smcginnis  will be running again.16:04
*** kaisers has quit IRC16:04
e0nejungleboyj: +116:04
*** yamahata has joined #openstack-meeting16:05
smcginnisEveryone has a week if they'd like to put in their name too. :)16:05
jungleboyjAlso just to make people aware that Rocky-1 is already coming up quickly.16:05
*** harlowja has joined #openstack-meeting16:05
jungleboyjDoesn't close anything down for Cinder, but bring it up for awareness.16:05
smcginnisjungleboyj: So no Cinder-specific deadlines for Rocky-1?16:06
jungleboyjOk, moving on.16:06
jungleboyjLet me look.  I don't think we have anything for Rocky-116:06
e0neat least, we don't have anything at
jungleboyjNope, Nothing until  .... oops, I thought I had put up the patch for that.16:07
*** ad_ri3n_ has joined #openstack-meeting16:07
* jungleboyj needs to do that after the meeting.16:07
jungleboyj#action jungleboyj  to update the rocky release schedule16:08
jungleboyjIt will look the same as Queens:16:08
*** msimonin has quit IRC16:08
*** dpertin has quit IRC16:09
*** bobh_ has quit IRC16:09
jungleboyj#topic Rocky Priorities Review16:09
*** openstack changes topic to "Rocky Priorities Review (Meeting topic: cinder)"16:09
jungleboyjI didn't get a chance to go through this before the meeting.16:10
e0nenothing from me on this topic16:10
jungleboyjAnyone have any updates to note in here?  I think the FCZM update is done now.16:10
jungleboyjOh, but the merge failed.16:10
e0neI started rebase my backup-related patches16:10
e0nethey'll be on gerrit this week16:11
jungleboyjhemna:  hemna_  You need to rebase the FCZM patch.16:11
jungleboyje0ne:  Good.16:11
*** andreas_s has joined #openstack-meeting16:12
jungleboyjI will try to find some time to go through the list and get things updated.16:12
jungleboyjNeed to do some spec reviews and try to get those wrapped up.16:12
jungleboyj#topic HA Development Progress.16:13
*** openstack changes topic to "HA Development Progress. (Meeting topic: cinder)"16:13
jungleboyjgeguileor:  Any updates here?16:13
jungleboyj:-(  Ok16:13
jungleboyje0ne: Where are things left on the scheduler/database discussion?16:14
e0nejungleboyj: looks like we moved to placement discussion there16:15
jungleboyjOk, so that is on hold until after we talk about it at the Forum?16:15
e0neI need to sync with tommylikehu on this to get our specs up to date16:15
tommylikehuthis one?
e0nejungleboyj: sounds readonable16:16
e0netommylikehu: yep. maybe we need to merge our specs intro the one. I'll check it16:16
jungleboyjOk.  Cool.16:16
jungleboyjtommylikehu:  Will you be in Vancouver?16:17
*** dpertin has joined #openstack-meeting16:17
tommylikehusean will be there16:17
smcginnisI plan to be in the placement discussion.16:17
smcginnisBut if there is anything we can work on before then, that would be good.16:17
e0neI hope so16:17
*** luizbag has joined #openstack-meeting16:17
jungleboyje0ne:  Ok. Good.16:17
jungleboyjsmcginnis:  ++16:17
e0neI should get visa in the end of April16:17
jungleboyjWould be good for us to all go into the discussion prepared.16:18
jungleboyje0ne:  and tommylikehu  Can you guys work on getting the new spec better outlined and we can have a discussion before the forum based on that?16:19
e0nejungleboyj: sure, we'll do it16:19
jungleboyj#action e0ne and tommylikehu to work on new Placement Service spec .  Team to review and discuss before Vancouver.16:19
jungleboyjOk, that leads nicely into the next topic:16:20
jungleboyj#topic Vancouver Forum Topic Proposals16:20
*** openstack changes topic to "Vancouver Forum Topic Proposals (Meeting topic: cinder)"16:20
jungleboyjSo, that is the list we currently have.16:20
jungleboyjDoes anyone have concerns with me submitting those topics?16:21
eharneyi'm not attending, so don't list me on the tempest thing16:21
jungleboyjeharney:  :-(16:22
jungleboyjDo we want to still propose that then?16:22
smcginniseharney: :(16:22
_pewp_jungleboyj (╯°□°)╯︵ ┻━┻ ︵ ╯(°□° ╯)16:22
eharneyi'm skeptical that it's of user interest anyway, but it may be good to talk about it somewhere16:22
smcginnisYeah, wasn't sure on the tempest one in the first place. I think we need to work with some -QA folks to prep for something like that.16:23
smcginnisMaybe better as a ML discussion?16:23
*** kaisers has joined #openstack-meeting16:23
jungleboyjsmcginnis:  ++ or set time for it at the next PTG and see if we can do it cross-project?16:23
*** janki has quit IRC16:23
smcginnisYeah, that would be good too.16:23
jungleboyjjgriffith:  Is going to be there and I think his topics are good.16:24
jungleboyjChris is going to submit the last one.16:24
jungleboyjSo, I will put the other 4 in.16:24
jungleboyj#action jungleboyj to submit 4 topics for the forum in Vancouver.16:25
*** andreas_s has quit IRC16:25
jungleboyjAny other concerns there?16:25
jungleboyjOther than :-( over eharney not coming16:25
*** eeiden_ has quit IRC16:26
jungleboyj#topic stable/branch policy changes discussion16:26
*** openstack changes topic to "stable/branch policy changes discussion (Meeting topic: cinder)"16:26
jungleboyjLet the fun begin.16:26
eharneyi'm a little unsure on what we still need to figure out here16:27
*** eeiden has quit IRC16:27
eharneybut i do get the feeling that everyone hasn't landed in the same place on this yet16:27
jungleboyjeharney:  Right.16:27
eharney  being a good example i was just looking at...16:27
jungleboyjsmcginnis:  Is it safe to say that the community has moved to keeping branches longer?16:28
*** msimonin has joined #openstack-meeting16:28
jungleboyjeharney:  Now, that looks like a feature backport rather than a fix.16:28
smcginnisYep, they will now be kept around.16:29
jungleboyjWhat am I missing?16:29
eharneyjungleboyj: that making SSL work correctly between Cinder and the backend is not a feature :)16:29
*** masayukig has joined #openstack-meeting16:29
smcginnisI wouldn't really consider actually verifying SSL connections to be a feature.16:29
eharneyespecially when we already have an option that says it does that...16:30
eharneywhich just silently fails to work in this case16:30
jungleboyjeharney:  Ok, fair enough.  It is addressing a security issue.16:30
*** andreas_s has joined #openstack-meeting16:30
jungleboyjI will change my vote on that one.16:31
jungleboyjSo, at this point we will take anything that is appropriate for backport to /stable/queens back to pike and ocata as well?16:32
eharneyit's about risk vs benefit delivered by the fix16:32
smcginnisI think as long as it's fixing an issue that an end user or operator might run in to and it's not a new feature, we should get it backported.16:33
jungleboyjeharney:  Well, you are the one benefitting most from fixes ... so ...16:33
eharneywell, sorta, but i mean...16:33
eharneyi just end up backporting them downstream if they don't land in stable anyway, so i do this risk assessment constantly16:34
smcginniseharney: Do you have a set of patches we should get backported upstream so you don't have to carry them downstream?16:34
eharneyit's more about benefiting deployers who try to use cinder for more than a few months16:34
jungleboyjsmcginnis:  Good question.16:35
hemna_smcginnis, +116:35
eharneywell most of them are going to newton etc, which can't be backported or even proposed for backport upstream -- in general we try to push anything we backport downstream toward stable branches as part of the process16:35
hemna_eharney, so are you suggesting we allow new features to get backported?16:35
* e0ne is happy because there is no custom patches in downstream cinder 16:36
hemna_ok cool :)16:36
hemna_so...what's the issue then really?16:36
*** felipemonteiro_ has quit IRC16:36
e0neeharney: we've got the same workflow for our downstream too16:37
eharneywe've trended toward being very conservative when looking at backports, and to be useful, especially with a longer-lived stable release, we need to make sure we are getting the right fixes in16:37
jungleboyjOk ... So, I think the answer is that we let people backport back to Ocata if it fixes something a user/operator may see.16:37
eharneynot sure there's a particular issue, just that it's an adjustment from the previous idea of "nothing lands after 6 months"16:37
*** guyr-infinidat has quit IRC16:38
eharneyalso -- reviewers should be thinking about things like "should this also go to stable" when reviewing patches on master16:38
jungleboyjSo what do we do with driverfixes/ branches?16:38
jungleboyjDo we still do that for n-3 ?16:38
smcginnisjungleboyj: I'd say leave the ones that are there, there.16:38
jungleboyjsmcginnis:  ++16:38
eharneykeep the current driverfixes branches running... don't make new ones until we have to16:38
smcginnisjungleboyj: I plan on going through and proposing things that went into driverfixes/ocata into stable/ocata16:38
e0neeharney: +116:39
jungleboyjsmcginnis:  That would be great.  Thank you!16:39
smcginnisIf we do anything with them, I think we should maybe delete driverfixes/ocata (once patches are merged over to stable) just so there's no confusion between the two since stable/ isn't going away.16:39
gansosmcginnis: wouldn't we be re-creating driverfixes/ocata on the next 6 months?16:40
gansosmcginnis: as it will be older than 18 months16:40
smcginnisganso: No, we are not deleting them anymore starting with ocata.16:40
tbarronit's only driverfixes/ocata that overlaps16:41
tbarronif we support stable back to ocata16:41
jungleboyjtbarron:  Right.16:41
smcginnistbarron: Yep. The stable policy change starts with ocata, so anything older is already gone.16:41
smcginnisAnd we haven't created newer driverfixes branches.16:41
jungleboyjBut once we get beyond 18 months we may have to recreate driverfixes/ocata .16:41
tbarronso i'm thinking of moving everything from driverfixes/ocata to stable/ocata16:42
jungleboyjThough we would rather not.16:42
jungleboyjtbarron:  ++16:42
*** dpertin has quit IRC16:42
smcginnistbarron: That's my plan for Cinder, so would be good if Manila did the same.16:42
hemna_moving forward driverfixes would only be needed after 18 months out for an older release.16:42
jungleboyjsmcginnis:  What I am trying to understand is what we do once Ocata goes beyond the 18 month point ...16:42
jungleboyjhemna_:  Right16:43
smcginnisThe stable/ocata branch will not be deleted anymore.16:43
*** ad_ri3n_ has quit IRC16:43
*** sgrasley1 has joined #openstack-meeting16:43
jungleboyjsmcginnis:  Right, but will we just keep taking patches then?16:43
smcginnisIt's there, and as long as someone is willing to backport and merge fixes, it's in "extended maintenance"/16:43
jungleboyjsmcginnis:  Ahhhh.16:43
smcginnisIt's up to teams how long they want to care about older branches, but there will not be a stable policy enforcing that they must die.16:44
gansoso there will be no need for driverfixes branches ever again?16:44
smcginnisThey'll be allowed a "natural death" :)16:44
smcginnisganso: I don't believe there will be.16:44
jungleboyjsmcginnis:  I understand now.16:44
tbarronsmcginnis: yup16:44
jungleboyjOk, so I agree that we should get stable/ocata sync'ed up and then we should get rid of that driverfixes branch.16:45
hemna_smcginnis, not even for after 18+ months is up?16:45
hemna_18 months isn't that long for deployments IMHO16:45
jungleboyjEventually *fingers crossed* people will move beyond using that branch.16:45
tbarronit's up to teams if / when they want to retire stable branches starting with ocata16:45
e0nehemna_: +116:45
smcginnisIt's only after a branch goes into unmaintained state due to no one doing anything with it for an extended period of time that it will go to EOL, but the branch will still be kept around.16:46
hemna_tbarron, so we can still push driver fixes for stable/newton ?16:46
eharneyjungleboyj: sure, eventually... but i think about branches living 5+ years ;)16:46
tbarronhemna_: no, "starting with stable/ocata"16:46
jungleboyjtbarron:  ++16:46
hemna_I guess what I'm asking is, how/where do we push driver fixes for a branch that's > 18 months old.  because we will still have customers that want them.16:46
jungleboyjeharney:  You poor devil16:46
tbarronhemna_: you'll stiil have driverfixes/newton16:46
smcginnisif release <- newton: patch driverfixes; else: patch stable16:47
tbarronhemna_: if < ocata, driverfixes; else, stable16:47
smcginnistbarron: Hah16:47
* jungleboyj laughs16:47
tbarronsmcginnis: has better syntax16:47
jungleboyjDid you two seriously just do that?16:48
smcginniss/<-/<=/ :)16:48
tbarronternary form now16:48
* tbarron stops16:48
jungleboyjOk.  So, I think we are all at a point of understanding an agreement.16:48
*** andreas_s has quit IRC16:49
smcginnisWe're at least a little less confused. ;)16:49
e0nesmcginnis: :)16:49
jungleboyj#action for smcginnis is make sure that stable/ocata and driverfixes/ocata are in sync.16:49
*** jamesmcarthur has quit IRC16:50
jungleboyj#action smcginnis or jungleboyj delete driverfixes/ocata once things are sync'ed up.16:50
smcginnisSounds good.16:50
jungleboyj#action jungleboyj  Document Cinder's interpretation of extended maintenance for backports.16:50
*** lpetrut has joined #openstack-meeting16:51
Swansonjungleboyj, got if for you. "If the branch exists then go nuts."16:51
jungleboyjSwanson:  :-)16:51
*** lpetrut_ has quit IRC16:51
jungleboyjOk, lets move on to the final topic with 9 minutes.16:52
jungleboyj#topic ``volume:extend_attached_volume`` policy rule mechanism does not allow backends that do not support this feature to be handled separetely, creating a bad user experience16:52
*** openstack changes topic to "``volume:extend_attached_volume`` policy rule mechanism does not allow backends that do not support this feature to be handled separetely, creating a bad user experience (Meeting topic: cinder)"16:52
lsekiso, there's this feature
lsekiAdd ability to extend 'in-use' volume16:52
lsekiAdministrator can disable this ability by updating the volume:extend_attached_volume policy rule16:53
lsekiif the admin has some backends that support in-use extend, and others that doesn't16:53
*** electrofelix has quit IRC16:53
*** andreas_s has joined #openstack-meeting16:54
*** dtroyer_zz has left #openstack-meeting16:54
lsekiwhen he uses a policy rule, it will enable/disable everything16:54
e0nelseki: why don't use capabilities for this?16:54
lsekie0ne: that's the idea16:54
lsekiit could be rather an extra-spec/capability16:54
tommylikehuwe can ask driver to report this capability then add the extra spec before scheduling to the schedulr16:55
gansoe0ne: AFAWK there is no way to do that currently, as extra-specs/capabilities for this do not exist16:55
e0netommylikehu: +116:55
gansowe should make it an official one instead of "extra_capabilities", IMO16:55
e0neIMO, policy shouldn't depend on drivers and backends16:56
jungleboyjganso:  Yeah, kind of sounds that way.16:56
gansoas it maps to a feature in the API16:56
*** _pewp_ has quit IRC16:56
gansoe0ne: +1, policies shouldn't do this kind of thing16:56
*** lpetrut has quit IRC16:57
gansoso is there agreement that an extra-spec and respective capability should be created to address this?16:57
tommylikehuwhat is the difference if we filter this out in the scheduler or let it failed in the backend16:57
jungleboyj2 minutes.16:58
jungleboyjtommylikehu:  If it fails in the scheduler can we get a better error back to the user?16:58
*** iyamahat has quit IRC16:59
gansoif it fails in the backend and there is no way to tell the manager that's because this feature is not supported it would go into extending_error16:59
*** tesseract has quit IRC16:59
*** iyamahat has joined #openstack-meeting16:59
jungleboyjganso:  Yuck.16:59
gansothat would be a not very good user experience IMO, as the backend probably didn't even try to extend the volume16:59
smcginnis1 minute16:59
*** e0ne has quit IRC16:59
jungleboyjSo, it sounds like we have something to fix here.16:59
gansook we might need to table this discussion16:59
jungleboyjlseki:  Can you work with ganso and e0ne to propose a solution?17:00
jungleboyjOr we can finish this discussion in channel?17:00
lsekiI think this needs further discussion17:01
*** _pewp_ has joined #openstack-meeting17:01
lsekinot sure if it's a bug or a feature17:01
jungleboyjOk lets pick this up next week then.17:01
jungleboyjThanks everyone!17:01
*** openstack changes topic to "OpenStack Meetings ||"17:01
openstackMeeting ended Wed Apr 11 17:01:37 2018 UTC.  Information about MeetBot at . (v 0.1.4)17:01
openstackMinutes (text):
*** lseki has quit IRC17:02
*** andreas_s has quit IRC17:03
*** dpertin has joined #openstack-meeting17:04
*** harlowja has quit IRC17:07
*** tssurya has quit IRC17:07
*** imcsk8 has quit IRC17:07
*** andreas_s has joined #openstack-meeting17:08
*** aagate has quit IRC17:09
*** gman-tx has quit IRC17:09
*** sidx64 has quit IRC17:14
*** kopecmartin has quit IRC17:16
*** annabelleB has quit IRC17:19
*** andreas_s has quit IRC17:22
*** annabelleB has joined #openstack-meeting17:24
*** hemna_ has quit IRC17:25
*** hemna_ has joined #openstack-meeting17:25
*** ekcs has joined #openstack-meeting17:25
*** andreas_s has joined #openstack-meeting17:27
*** jamesmcarthur has joined #openstack-meeting17:28
*** hemna__ has joined #openstack-meeting17:29
*** hemna__ has quit IRC17:29
*** yamamoto has quit IRC17:29
*** hwalsh has quit IRC17:32
*** jamesmcarthur has quit IRC17:33
*** XueFeng has quit IRC17:38
*** dpertin has quit IRC17:39
*** lpetrut has joined #openstack-meeting17:40
*** andreas_s has quit IRC17:42
*** imcsk8 has joined #openstack-meeting17:42
*** dtruong_ has joined #openstack-meeting17:45
*** dtruong_ has quit IRC17:45
*** dtruong_ has joined #openstack-meeting17:46
*** dtruong_ has quit IRC17:46
*** dtruong_ has joined #openstack-meeting17:47
*** dtruong_ has quit IRC17:47
*** dtruong_ has joined #openstack-meeting17:48
*** dtruong has quit IRC17:48
*** ad_ri3n_ has joined #openstack-meeting17:48
*** yamamoto has joined #openstack-meeting17:49
*** e0ne has joined #openstack-meeting17:50
*** yamamoto has quit IRC17:50
*** yamamoto has joined #openstack-meeting17:50
*** arxcruz|ruck is now known as arxcruz17:50
*** harlowja has joined #openstack-meeting17:52
*** cdub has joined #openstack-meeting17:52
*** andreas_s has joined #openstack-meeting17:55
*** sambetts is now known as sambetts|afk17:55
*** yamamoto has quit IRC17:57
*** edmondsw has joined #openstack-meeting17:59
*** cdub has quit IRC18:00
*** dklyle has quit IRC18:06
*** sgrasley1 has quit IRC18:08
*** andreas_s has quit IRC18:10
*** cburgess_ is now known as cburgess18:13
*** andreas_s has joined #openstack-meeting18:14
*** annabelleB has quit IRC18:14
*** iyamahat has quit IRC18:14
*** anilvenkata has joined #openstack-meeting18:15
*** yamamoto has joined #openstack-meeting18:16
*** iyamahat has joined #openstack-meeting18:16
*** annabelleB has joined #openstack-meeting18:17
*** yamamoto has quit IRC18:18
*** felipemonteiro_ has joined #openstack-meeting18:18
*** radeks has quit IRC18:21
*** radeks has joined #openstack-meeting18:22
*** ricolin has quit IRC18:24
*** yamamoto has joined #openstack-meeting18:25
*** andreas_s has quit IRC18:28
*** claudiub has quit IRC18:31
*** jamesmcarthur has joined #openstack-meeting18:33
*** yamamoto has quit IRC18:34
*** yamamoto has joined #openstack-meeting18:38
*** annabelleB has quit IRC18:39
*** yamamoto has quit IRC18:40
*** rbudden has quit IRC18:42
*** annabelleB has joined #openstack-meeting18:45
*** dklyle has joined #openstack-meeting18:55
*** pcaruana has quit IRC18:55
*** priteau has quit IRC19:00
* fungi peers around for storyboard folk19:00
* diablo_rojo arrives19:01
*** jamesmcarthur has quit IRC19:01
diablo_rojo#startmeeting storyboard19:01
openstackMeeting started Wed Apr 11 19:01:55 2018 UTC and is due to finish in 60 minutes.  The chair is diablo_rojo. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: storyboard)"19:01
openstackThe meeting name has been set to 'storyboard'19:01
diablo_rojoI'll give running things a go since SotK said he couldn't make it today :(19:02
diablo_rojo#link Agenda19:02
diablo_rojo#topic Announcements19:02
*** openstack changes topic to "Announcements (Meeting topic: storyboard)"19:02
diablo_rojoCyborg has migrated!19:03
* diablo_rojo cues applause19:03
fungibetter than queuing applause i suppose19:03
diablo_rojoHa ha19:04
diablo_rojoOther announcement: Forum submissions are open till the 15th!19:04
diablo_rojoSo if you have ideas please submit them!19:04
diablo_rojoI have one I drafted for StoryBoard in this etherpad:19:05
diablo_rojo#link Kendall's SB Forum Proposal19:05
diablo_rojoI would love comments and edits19:05
diablo_rojoAny other announcements before I move on?19:06
funginothing from the peanut gallery here19:06
dhellmannno announcements here19:06
*** salv-orlando has quit IRC19:07
*** salv-orlando has joined #openstack-meeting19:07
diablo_rojo#topic Migration Updates!19:07
*** tssurya has joined #openstack-meeting19:07
*** openstack changes topic to "Migration Updates! (Meeting topic: storyboard)"19:07
*** julim_ has quit IRC19:07
*** dpertin has joined #openstack-meeting19:08
diablo_rojoSo! Sounds like we have OpenStackSDK and OpenStackClient scheduled for Friday.19:08
*** julim has joined #openstack-meeting19:08
diablo_rojoWhich is super awesome. I love this having migrations every week business.19:08
diablo_rojo#link!/board/45 Board Tracking Migration Progress19:08
fungiyeah, happy to take care of them19:08
fungisetting myself a reminder now19:08
fungido we have changes proposed for those?19:09
diablo_rojofungi, much appreciated! I owe you so many beers.19:09
diablo_rojofungi, not yet, but I can do that today.19:09
fungitripleo's ui squad also requested migrating the validations tags to openstack/tripleo-validations19:09
fungii have a change up for that and can merge it whenever they're ready for me to run it19:09
diablo_rojo#action diablo_rojo will create project-config changes for OSDK and OSC19:10
fungi#link Track tripleo-validations tasks on StoryBoard19:10
diablo_rojofungi, excellent I will check it out and I can poke EmilienM to look too if you want19:10
diablo_rojoAnything else I can do to help there?19:10
* EmilienM hides19:10
diablo_rojoLast update is that we also started talking about migrating the TripleO security squad19:11
EmilienMit becomes tricky though19:11
EmilienMbecause they don't have specific repos19:11
fungiyeah, i replied on that thread because i'm confused as to what they're looking for19:11
EmilienMthey use most of tripleo repos19:11
*** salv-orlando has quit IRC19:11
EmilienMI guess we want to create the tripleo project and migrate bugs with certain tags maybe?19:12
diablo_rojoI feel like it would be fine if we created the repos and then just migrate the relevant tags19:12
diablo_rojoEmilienM, exactly :)19:12
fungithat would probably work, but i'm trying to think about what problems it might cause19:13
diablo_rojoAnd then migrate other tags later then finally, once all the squads are over, run the last time for all of TripleO to make sure the rest is migrated and things are all up to date before disabling the tracker.19:13
fungiare you expecting tripleo users to start reporting suspected vulnerabilities into sb but keep reporting all other bugs in lp?19:13
diablo_rojofungi, it would be hard not being able to disable bug reporting for certain cases- things might continue to get filed there19:13
fungialso keep in mind that any currently private bugs don't get migrated. we'd have to manually summarize them in new private stories if they need to remain private due to an in-progress embargo at the time of migration19:15
diablo_rojoYes, important to note.19:15
dhellmannsplitting the bugs for repos up like that seems like it's going to make the migration more complicated than just waiting to do that team until the others are done19:16
diablo_rojoEmilienM, how far behind are the rest of the squads from being willing to migrate?19:16
fungiright. splitting tripleo bugs along repository boundaries is a bit easier since you basically used bugtags to indicate which repository you were targeting with them19:17
diablo_rojodhellmann, yeah for the first few squads it was fine as they had their own repos, but for others that share..19:17
fungiand the repository-specific task concept aligns perfectly with storyboard's model19:17
EmilienMdiablo_rojo: not easy answer19:17
*** rpioso|afk is now known as rpioso19:17
diablo_rojoEmilienM, I didn't expect it would be lol19:17
EmilienMtripleo project is really big, lot of repos, lot of teams, lot of people :)19:17
EmilienMwhich why I suggested we do baby steps here19:18
diablo_rojoAre there others that have specific repos we can do first?19:18
diablo_rojoOr were UI and validation the only ones?19:18
EmilienMthey were the only ones19:18
fungiso anyway, sounds like the security squad would probably actually straddle lp and sb if they're handling security issues in parts of tripleo which are in sb and parts which are still in lp19:19
EmilienMcould we have "tripleo" project in SB19:21
diablo_rojoI think continuing to do a squad at a time is doable, though it might get messy. Coming up with a more concrete timeline for the rest of them to minimize lag would be best before we split the repo would be a good idea I think.19:21
diablo_rojoThat was a terribly worded sentence lol19:21
EmilienMand we migrate some bugs but only some tags19:21
EmilienMif we move all bugs all in once and ask everyone to switch it's going to be messy19:22
EmilienMwe can TRY! but only if you have a time machine in case things go south19:22
diablo_rojoEmilienM, yeah we can do that- its just going to get messy I think as people could still report bugs with the tags in lp instead of where they should be in storyboard.19:22
diablo_rojoEmilienM, sadly I have no Tardis.19:23
*** ganso has left #openstack-meeting19:23
EmilienMwhat??? pfftt :)19:23
fungiwell, "projects" in sb correspond to individual git repositories. i suppose we could migrate them to have initial tasks in the openstack/tripleo-common project19:23
*** rmaciel has joined #openstack-meeting19:23
*** rmaciel has left #openstack-meeting19:24
diablo_rojoSo 10 squads. 1 is already migrated. validation is set to go. Security after, then maybe one or two each following week?19:24
EmilienMyeah we can try19:24
*** dpertin has quit IRC19:24
fungiand create projects in sb for all the tripleo team's other deliverable repositories too and then active stories could get new tasks manually (or scripted through the api based on some determined characteristics) created for the relevant projects19:24
diablo_rojoLet me know what meetings I need to attend to rally the people EmilienM19:25
*** mattia has quit IRC19:25
diablo_rojofungi, so is this feasible?19:25
fungimigrating (public) tripleo security squad bugs to specific repository projects in sb based on one or more lp bugtags is feasible, but it's the workflow i'm mostly worried about19:27
EmilienMdiablo_rojo: tuesday at your 7am (yes sorry)19:28
EmilienMdiablo_rojo: on #tripleo19:28
EmilienMdiablo_rojo: but really you can join the channel at anytime19:28
diablo_rojoworkflow for people filing bugs or for the team fungi ?19:28
diablo_rojoEmilienM, I'll add it to my calendar.19:28
*** annabelleB has quit IRC19:29
diablo_rojoOh man. FC SIG at 1 AM. TripleO at 7AM.19:29
fungia little of both. main concerns are 1. if users are filing security bugs will they know to do so in sb, and 2. when users are filing security bugs do they know in advance they're security bugs or do they get triaged as such later (and will someone then need to tell the reporter to copy that into sb or perhaps do so themselves)?19:29
*** jamesmcarthur has joined #openstack-meeting19:29
diablo_rojolhinds, might be able to share thoughts on that? ^^19:30
fungiit's a little easier at least when the users can expect to file security and normal bugs in the same system19:30
*** jamesmcarthur has quit IRC19:31
*** jamesmcarthur has joined #openstack-meeting19:31
fungiknowing to use different bug trackers to report bugs for different subsystems/repositories is one thing, but deciding which tracker to use based on more subtle characteristics like "is this maybe security-related" could be a lot harder to figure out19:31
diablo_rojoI suppose they can note that in their list of bug tags and in the lp project description and any other documentation they have19:32
diablo_rojoWhat goes where19:32
fungiat least from my (vmt) perspective, it's a lot more common to see bugs originally reported as security bugs turn out not to be and vice versa than it is to see bugs reported against the wrong subsystem19:32
diablo_rojoYeah I suppose if its reported as security but itsnt then its already in sb but the regular squad dealing with it wouldnt see it unless they are already looking at both places.19:34
dhellmannwhy are we going team-by-team instead of repo-by-repo?19:34
fungiand if it's reported as a not-security bug but then turns out to be security related, it needs to get moved into sb somehow19:34
fungidhellmann: tripleo didn't track bugs by repo19:34
fungithey just used one big tripleo bucket in lp19:35
fungiat least for the most part19:35
diablo_rojoYes thats my understanding19:35
*** iyamahat has quit IRC19:35
fungiand then augmented some of that by using bugtags to identify different responsible subteams which in some cases roughly corresponded to one or a set of repositories19:36
*** annabelleB has joined #openstack-meeting19:36
diablo_rojobut there is a lot of intersection with squads and repos19:36
fungibut the concern is that tripleo is so huge and has so many subteams that convincing them all to switch from lp to sb at once would be hard19:36
dhellmannmy inclination would be to just move it all at once, but if you have ways to not do that I guess it's probably fine and since I'm not doing the work I should probably just stay out of it19:36
fungifrom the infrastructure side of things, yes moving them all at once would be way easier19:37
diablo_rojoAll at once would certainly be preferable..19:37
dhellmannmaybe they're not good candidates to go early, then, if they're a special case or need extra encouragement19:37
diablo_rojoI can talk to the team Tuesday during their meeting and beg :)19:37
fungiwe invented a way to fan out bugs to different repositories based on tag filtering specifically for tripleo in fact19:38
dhellmannoh, wow19:38
diablo_rojoMore for sahara, but TripleO had a vested interest19:38
fungioh, right, thanks for the correction19:38
fungiwe did use it on sahara first for similar reasons19:38
diablo_rojoOne big lp projects that covered a lot of repos19:39
diablo_rojoIt was a super cool migration script addition in my opinion19:39
fungifor sure, it's handy19:39
diablo_rojoThere are enough other irons in the fire that if we can't do TripleO now it wont stop progress.19:39
* dhellmann nods19:40
fungiand also, the more high-profile migrations we get behind us, the easier it is to convince some of the teams who are still on the fence19:40
*** annabelleB_ has joined #openstack-meeting19:40
diablo_rojoI have like 15 projects ready to move that I have been casually chatting with PTLs about migration with19:40
dhellmannI presume that means we no longer have any feature blockers?19:41
dhellmannwith storyboard itself, that is19:41
diablo_rojodhellmann, the last big blocker was the private stories and I believe all that has been implemented19:41
fungithere are a few i'm personally prioritizing19:41
*** annabelleB has quit IRC19:41
*** annabelleB_ is now known as annabelleB19:41
diablo_rojoThere are some things people have filed but I think a lot of them are 'nice to have' rather than actually blocking issues19:42
fungibut they're more like irritations/inconveniences to projects who have already moved to sb which we need to fix19:42
dhellmannthat all sounds good19:42
diablo_rojoWe will get to that in the agenda if we are good to move on?19:42
fungithe ones i'm focusing on at least19:42
fungiyup, i'm all set19:42
diablo_rojo#topic In Progress Work19:42
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)"19:42
diablo_rojofungi? gerrit posting on stories?19:42
fungiyeah, i'm in the process of diagnosing that one today19:43
*** mattia has joined #openstack-meeting19:43
fungithen there are a couple further down the list i plan to look at once i have that settled19:43
*** sidx64 has joined #openstack-meeting19:43
diablo_rojoI think that getting fixed will unblock another team or two19:44
diablo_rojoNot sure what I can do to help, but I'm here if you need a rubber duck at the very least.19:44
*** iyamahat has joined #openstack-meeting19:44
diablo_rojo#link Open Storyboard Reviews19:45
diablo_rojo#link Open Webclient Reviews19:45
fungione of the bigger issues further down my list is that private stories don't generate e-mail notifications to subscribers who are able to see them19:45
fungibefore fixing that we want to be able to test that it doesn't regress again19:46
diablo_rojo#link Open Pythonclient reviews19:46
fungibut corvus has been having some difficulty wrangling the testsuite to get a test for that added19:46
diablo_rojoAh yes I recall him having issues and needing SotK to explain some things.19:46
*** sidx64_ has joined #openstack-meeting19:47
*** edmondsw has quit IRC19:47
*** ad_ri3n_ has quit IRC19:47
fungito the point where it may just be easier (sadly) to create an external periodic cron job to query the sb api and send e-mails19:47
*** sidx64 has quit IRC19:49
*** eharney has quit IRC19:49
dhellmannthis feels like a good use case for something like celery19:49
dhellmannSB would start a task to send email instead of blocking on talking to the sendmail daemon19:50
fungithe other one i'm tracking as a priority (which is a sort-of-blocker for some teams) is that due to the webclient doing all content querying and rendering browser-side, search engines are unable to easily index stories19:50
*** julim has quit IRC19:50
*** tssurya has quit IRC19:51
dhellmannoh, yeah, I would consider that a blocker19:51
fungiusers are going to want to be able to find stories when they plug error messages into web search engines19:51
diablo_rojoOh yes, for sure.19:52
dhellmannI suppose that means we need some sort of index page that can be crawled to find all of the bugs, too19:52
fungiso we probably need some indexible content returned in indexible "flat" pages which use something like a meta refresh redirect to bounce browser clients to the dynamic versions19:52
fungiand yeah, an index too19:53
dhellmannmakes sense19:53 or something19:53
diablo_rojoAhh okay. Similar to the bug indicies in lp.19:53
dhellmannyeah, if you want the crawler to crawl your site, you have to give it a place to start19:54
*** dbecker has quit IRC19:54
*** julim has joined #openstack-meeting19:54
diablo_rojoMakes sense. So..thats something we need to implement in the webclient then I suppose.19:54
dhellmannor maybe as a separate tool19:55
fungigiven i'm not really a webapp designer, i have to assume there are standard/conventional solutions to this problem and i just don't know what they are19:55
diablo_rojoseparate tool would be nicer.19:55
dhellmannyeah, I don't know the state of the art either19:55
dhellmannI mean I would have thought the URL to load a story would produce HTML that includes the story19:55
dhellmannrather than JS to fetch the story details after loading19:56
fungii mean, we could easily(?) just periodically dump the whole data set and render static versions with the redirecting juice embedded19:56
dhellmannright, that's what I was thinking, too19:56
diablo_rojoWe had been tentatively planning making a new repo storyboard-tools19:56
diablo_rojoThis could live there?19:56
fungiseems reasonable19:56
*** salv-orlando has joined #openstack-meeting19:56
*** tssurya has joined #openstack-meeting19:57
diablo_rojo3 min left heads up19:57
fungithat "dump the content to flat files" feels really inelegant though. i have a hard time believing that's how, say, forum apps which are browser-side rendered accomplish things19:57
* diablo_rojo will move the creation of that repo higher on her todo list19:57
dhellmannI wonder if they're doing agent-string identification19:57
diablo_rojofungi, yeah I would agree19:57
fungibut maybe i'll pull a mordred and implement the ugly solution so that it will anger someone enough they ragecode the right one19:57
*** luizbag has quit IRC19:58
diablo_rojo++ :)19:58
dhellmannget it working; get it working right; get it working fast19:58
fungiit's a viable tactic19:58
*** bobh has joined #openstack-meeting19:58
* fungi did not mean to insult but rather compliment mordred's sensibilities in these matters ;)19:59
diablo_rojoOut of time to go through other blocking things this week.20:00
*** gman-tx has joined #openstack-meeting20:00
diablo_rojoBut I think we all have enough things to work on for now.20:00
diablo_rojoThanks for coming fungi and dhellmann :)20:00
*** openstack changes topic to "OpenStack Meetings ||"20:00
openstackMeeting ended Wed Apr 11 20:00:38 2018 UTC.  Information about MeetBot at . (v 0.1.4)20:00
openstackMinutes (text):
fungiit was a great meeting. thanks diablo_rojo!20:00
*** gman-tx has quit IRC20:00
* diablo_rojo goes to nap a little more- pattern has been meeting sleep meeting meeting sleep meeting20:01
*** claudiub has joined #openstack-meeting20:02
diablo_rojoNow that I've said that I might just eat and work more instead20:02
fungiright, i mean, who needs sleep, really?20:02
*** nmagnezi has left #openstack-meeting20:05
diablo_rojofungi, cumulatively I've gotten like 7 hours I think20:05
*** acoles has joined #openstack-meeting20:10
*** mattia has quit IRC20:15
*** mattia has joined #openstack-meeting20:19
*** markvoelker has joined #openstack-meeting20:20
*** margaret_ has joined #openstack-meeting20:20
*** lsell___ has joined #openstack-meeting20:21
*** zioproto_ has joined #openstack-meeting20:21
*** amito_ has joined #openstack-meeting20:21
*** sweston_ has joined #openstack-meeting20:21
*** ameade_ has joined #openstack-meeting20:21
*** kmalloc_ has joined #openstack-meeting20:21
*** ansmith has quit IRC20:23
*** toanster has joined #openstack-meeting20:24
*** dtruong_ has quit IRC20:24
*** dtruong has joined #openstack-meeting20:25
*** kmalloc_ has quit IRC20:25
*** kmalloc_ has joined #openstack-meeting20:25
*** leader716 has joined #openstack-meeting20:25
*** kmalloc_ is now known as notmorgan20:26
*** notmorgan has quit IRC20:26
*** notmorgan has joined #openstack-meeting20:26
*** notmorgan has quit IRC20:26
*** notmorgan has joined #openstack-meeting20:26
*** acoles_ has joined #openstack-meeting20:26
*** kmalloc has quit IRC20:27
*** andreaf_ has joined #openstack-meeting20:27
*** tobberydberg_ has joined #openstack-meeting20:27
*** notmorgan is now known as kmalloc20:27
*** johnthetubaguy_ has joined #openstack-meeting20:28
*** mordred has quit IRC20:28
*** galstrom_zzz has quit IRC20:28
*** vkmc has quit IRC20:28
*** toan has quit IRC20:28
*** andreaf has quit IRC20:28
*** acoles has quit IRC20:28
*** lsell__ has quit IRC20:28
*** zioproto has quit IRC20:28
*** johnsom has quit IRC20:28
*** ameade has quit IRC20:28
*** amito has quit IRC20:28
*** sweston has quit IRC20:28
*** margaret has quit IRC20:28
*** jpward has quit IRC20:28
*** tobberydberg has quit IRC20:28
*** johnthetubaguy has quit IRC20:28
*** acoles_ is now known as acoles20:28
*** lsell___ is now known as lsell__20:28
*** margaret_ is now known as margaret20:28
*** amito_ is now known as amito20:28
*** zioproto_ is now known as zioproto20:28
*** sweston_ is now known as sweston20:28
*** ameade_ is now known as ameade20:28
*** galstrom_zzz has joined #openstack-meeting20:29
*** johnsom has joined #openstack-meeting20:29
*** imcsk8_ has joined #openstack-meeting20:29
*** andreaf_ is now known as andreaf20:29
*** mordred has joined #openstack-meeting20:30
*** vkmc has joined #openstack-meeting20:31
*** imcsk8 has quit IRC20:32
*** ad_ri3n_ has joined #openstack-meeting20:36
*** annabelleB has quit IRC20:40
*** julim has quit IRC20:42
*** kaisers has quit IRC20:44
*** kaisers has joined #openstack-meeting20:45
*** annabelleB has joined #openstack-meeting20:45
*** raildo has quit IRC20:47
*** kaisers has quit IRC20:50
*** yamamoto has joined #openstack-meeting20:52
*** pchavva has quit IRC20:52
*** HeOS has quit IRC20:53
*** HeOS has joined #openstack-meeting20:53
*** rbowen has quit IRC20:53
*** edmondsw has joined #openstack-meeting20:54
*** yamamoto has quit IRC20:56
*** torgomatic has joined #openstack-meeting20:57
*** m_kazuhiro has joined #openstack-meeting20:58
*** patchbot has joined #openstack-meeting20:59
*** timburke has joined #openstack-meeting20:59
*** edmondsw has quit IRC20:59
notmynameswift meeting time21:00
notmyname#starmeeting swift21:00
notmynamewho's here for the swift meeting?21:00
timburke#startmeeting swift21:01
openstackMeeting started Wed Apr 11 21:01:24 2018 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: swift)"21:01
openstackThe meeting name has been set to 'swift'21:01
notmynamelol, thanks21:01
rledisez_hi o/21:01
timburkeoh dear, wait... now *i'm* the chair... i don't know that i'm ready for the responsibility!21:02
notmynameagenda this week is just a bit of catch-up of ongoing work21:02
notmynametimburke: I think it just means you're the only one who can endmeeting. maybe topics, too. but I don't think we need those this week21:02
notmynamefirst up, is still open and has an unreviewed patch at patch 55524521:03
openstackLaunchpad bug 1755554 in OpenStack Object Storage (swift) "Percent signs in object names cause trouble for versioned_writes" [High,In progress] - Assigned to Kota Tsuyuzaki (tsuyuzaki-kota)21:03
patchbot - swift - Fix versioned writes error with url-encoded object...21:03
notmynamethere's not a particular question associated with that right now. just something that needs to be landed by the time we do a release21:03
notmynameif you have some time to do a review, that's a good one to do21:03
notmynamekota_: how's feature/s3api looking? seems to me that all the patches have landed!21:04
kota_notmyname: true21:04
notmynamethat's great news21:04
kota_i just push +A on the last patch yesterday21:04
notmynameso, from your perspective, it's ready to be merged to master?21:04
kota_yes. if i don't forget anything needed.21:05
notmynameheh, ok :-)21:05
notmynamehere's what I want to do about that...21:05
notmynamefor now, kota_ please do not make the merge commit proposal. I will do that21:05
notmynameI talked to tdasilva about it earlier today (he's not available during the meeting today)21:05
notmynameand I talked with you, kota_, about it some last week21:06
notmynameI want to talk to several other people first, about how we can land this and when we should, given the oncoming feature/deep merge plans21:06
notmynamekota_: I'll do all this before the end of this week, and I'll let you know what everyone thinks21:07
notmynamethen we'll make the merge commit (or not) and have the appropriate people lined up to review21:07
*** slaweq has quit IRC21:08
notmynameso for everyone who's not kota_, I'll likely be asking you about the feature/s3api merge sometime in the next couple of days :-)21:08
*** slaweq has joined #openstack-meeting21:09
notmynamenext up... torgomatic has been doing some good work improving the performance of the reconstructor and replicators21:09
notmynamehis work is a patch tree rooted at patch 55556321:09
patchbot - swift - Multiprocess object replicator21:09
notmynameafter talking with acoles and timburke this week, turns out that this work could really benefit the feature/deep work21:09
notmynameif not for pure performance reasons, at least to reduct merge conflicts21:10
notmynameand I believe clayg has reviewed some21:10
notmynameplease help torgomatic with some reviews there. and please start at the beginning of the patch chain instead of somewhere in the middle :-)21:10
mattoliverauSo have i21:10
notmynametorgomatic: anything to add there?21:10
torgomaticjust that there's a follow-up commit to clean up a few things, so also look at ...21:10
patchbotpatch 559872 - swift - Cleanups for multiprocess object replicator21:11
notmynamemattoliverau: thanks! I didn't mean to forget you :-)21:11
*** sidx64_ has quit IRC21:11
mattoliverauNah that's ok. There some good improvements.21:11
torgomaticI'm fine with combining the patches or merging both. There's nothing badly broken in the first one, just some minor issues.21:11
notmynameacoles: timburke: what's the good word with feature/deep this week?21:12
timburkeit takes a while to work with large containers :-/21:13
*** slaweq has quit IRC21:13
*** rfolco|rover is now known as rfolco|off21:13
notmynameI think acoles is stubling over the word "good" in my question :-)21:13
*** ad_ri3n_ has quit IRC21:14
timburkei had a 145M row db i was identifying shard ranges in. with no swift processes running, it took ~12 minutes21:14
acolesnotmyname: lots of progress, lots of patches21:14
mattoliverauFaster then the last poc :p21:14
timburkewith container server and all background processes running, it was ~90 minutes21:14
timburke...and then swift-manage-shard-ranges failed to insert them (or even create a shard ranges table) because the db was locked. so i need to get something going for that21:15
*** tssurya has quit IRC21:16
acolesnotmyname: the stated plan is to propose to master soon - I assume we'll follow previous pattern of using a final review branch?21:16
notmynameoriginally, we'd planned to propose a merge commit next week21:16
mattoliverauIf we can skip the offset some more it might speed things up... But that isn't easy. Or at least obvious for me.21:16
notmynameacoles: yes, same pattern21:17
notmynameI'll handle the branch as needed21:18
notmynameI don't want to press you too much on a "is it ready" question, but how are you feeling about it?21:19
notmynameyour not-so-rapid response worries me :-)21:20
acolesit's not ready yet. I've been wittling down the high priority items on backlog, there's a few still there, plus whatever we learn from timburke's expereinces21:20
notmynamemy perspective is that while we have dates imposed on us at times by our employers (for this or other features), we should not release something that isn't ready. if it's not ready, that's ok, and we'll make sure it's ready before we release it21:21
acolesI'm trying to focus on stuff that is best to be settled and stable before proposing21:21
notmynameit's better to know that sooner than later, and I can handle any fallout that happens because we missed a date we ourselves set for ourselves21:22
acolesvs 'minor' stuff that we can add in during review21:22
notmynameacoles: and this week I'll try to balance the two sides of "is it done yet?" and "leave me alone john, or it will never get done" :-)21:23
*** dustins has quit IRC21:23
acolesnotmyname: the goal was that April 16th would be the *earliest* and I'm confident we'll satisfy that goal :)21:23
notmynamegreat! good news, everyone!21:23
notmynamerledisez_: I saw a golang patch from alex today21:24
notmynamerledisez_: anything to share on LOSF?21:24
rledisez_this patch, it's not useful on its own, but the python code should follow in one or two weeks. alex want to do some clean up before pushing python21:25
patchbotpatch 560480 - swift - Initial LOSF RPC commit21:25
rledisez_we are converting right now a complete cluster. should be done in about 20 days21:25
*** kaisers has joined #openstack-meeting21:25
rledisez_so we will have real prod result on 3 weeks :)21:25
torgomaticyeah, I took a look at the LOSF one, and it'll be a lot more interesting with some Python code21:25
torgomaticright now it's like "here's a bunch of RPC methods you could call if you want to"21:26
rledisez_torgomatic: exactly. not much fun ;)21:26
notmynameI know how much every one here loves meetings, so I'm sorry to say I've got to stop in 3 minutes. but is there anything else to bring up from anyone?21:27
notmynameah ha! but it's timburke who's the chair and has to do the endmeeting thing! so he can go All. Day. Long.21:27
mattoliverauThe chair times out after some time then anyone can end it.. just can't remember the time limit... 30mins? An hour?21:29
notmynamenice failsafe21:29
mattoliverauLearnt that from all the spam start meetings a few months ago21:29
notmynamesounds like that's about it. thank you all for your work on swift21:29
notmynamenope. not me. not yet21:30
mattoliverauNo not 30mins then :)21:30
*** kaisers has quit IRC21:30
mattoliverautimburke: would you do the honours?21:30
*** openstack changes topic to "OpenStack Meetings ||"21:31
openstackMeeting ended Wed Apr 11 21:31:02 2018 UTC.  Information about MeetBot at . (v 0.1.4)21:31
openstackMinutes (text):
notmynamethansk :-)21:31
*** acoles has left #openstack-meeting21:31
*** timburke has left #openstack-meeting21:31
*** m_kazuhiro has quit IRC21:32
*** ansmith has joined #openstack-meeting21:37
*** salv-orlando has quit IRC21:38
*** salv-orlando has joined #openstack-meeting21:38
*** sgrasley1 has joined #openstack-meeting21:42
*** salv-orlando has quit IRC21:43
*** esberglu has quit IRC21:47
*** rcernin has joined #openstack-meeting21:49
*** lpetrut has quit IRC21:56
*** felipemonteiro_ has quit IRC22:02
*** radeks has quit IRC22:10
*** VW_ has joined #openstack-meeting22:10
*** noslzzp has quit IRC22:10
*** VW has quit IRC22:13
*** VW_ has quit IRC22:14
*** e0ne has quit IRC22:20
*** tpsilva has quit IRC22:24
*** hagridaaron has joined #openstack-meeting22:26
*** qwebirc11456 has joined #openstack-meeting22:26
*** andreas_s has joined #openstack-meeting22:26
*** qwebirc11456 has left #openstack-meeting22:27
*** andreas_s has quit IRC22:31
*** annabelleB has quit IRC22:31
*** jamesmcarthur has quit IRC22:35
*** mriedem is now known as mriedem_afk22:36
*** salv-orlando has joined #openstack-meeting22:39
*** bobh has quit IRC22:40
*** bobh has joined #openstack-meeting22:42
*** felipemonteiro_ has joined #openstack-meeting22:42
*** edmondsw has joined #openstack-meeting22:43
*** d0ugal has quit IRC22:43
*** salv-orlando has quit IRC22:43
*** yamamoto has joined #openstack-meeting22:46
*** d0ugal has joined #openstack-meeting22:48
*** edmondsw has quit IRC22:48
*** yamamoto has quit IRC22:50
*** yamamoto has joined #openstack-meeting22:51
*** hongbin has quit IRC22:53
*** yamamoto has quit IRC22:56
*** yamamoto has joined #openstack-meeting22:57
*** yamamoto has quit IRC23:01
*** yamamoto has joined #openstack-meeting23:03
*** julim has joined #openstack-meeting23:03
*** jamesmcarthur has joined #openstack-meeting23:04
*** sgrasley1 has quit IRC23:04
*** jamesmcarthur has quit IRC23:09
*** slaweq has joined #openstack-meeting23:09
*** _alastor_ has quit IRC23:12
*** slaweq has quit IRC23:14
*** pchavva has joined #openstack-meeting23:19
*** kaisers has joined #openstack-meeting23:26
*** fnaval has quit IRC23:28
*** kaisers has quit IRC23:30
*** pchavva has quit IRC23:31
*** mjturek has quit IRC23:32
*** fnaval has joined #openstack-meeting23:33
*** hagridaaron has quit IRC23:34
*** claudiub has quit IRC23:35
*** _alastor_ has joined #openstack-meeting23:37
*** hagridaaron has joined #openstack-meeting23:37
*** salv-orlando has joined #openstack-meeting23:40
*** _alastor_ has quit IRC23:42
*** felipemonteiro_ has quit IRC23:42
*** hagridaaron has quit IRC23:44
*** salv-orlando has quit IRC23:45
*** yamamoto has quit IRC23:47
*** cloudrancher has quit IRC23:50
*** cloudrancher has joined #openstack-meeting23:51
*** rpioso is now known as rpioso|afk23:54
*** _alastor_ has joined #openstack-meeting23:54

Generated by 2.15.3 by Marius Gedminas - find it at!