Wednesday, 2018-03-14

*** kei-ichi has joined #openstack-meeting00:02
*** singlethink has quit IRC00:05
*** browny_ has quit IRC00:06
*** bobh has joined #openstack-meeting00:07
*** HeOS has quit IRC00:08
*** jamesmcarthur has quit IRC00:12
*** salv-orlando has joined #openstack-meeting00:15
*** jamesmcarthur has joined #openstack-meeting00:17
*** liyi has joined #openstack-meeting00:17
*** gouthamr has joined #openstack-meeting00:19
*** gyee has quit IRC00:20
*** claudiub has quit IRC00:20
*** salv-orlando has quit IRC00:21
*** chyka has quit IRC00:21
*** bobh has quit IRC00:22
*** pchavva has joined #openstack-meeting00:24
*** jamesmcarthur has quit IRC00:31
*** wanghao has joined #openstack-meeting00:32
*** rbudden has joined #openstack-meeting00:33
*** egallen has quit IRC00:34
*** tovin07_ has joined #openstack-meeting00:36
*** song has joined #openstack-meeting00:40
*** browny_ has joined #openstack-meeting00:42
*** Zames has joined #openstack-meeting00:44
*** browny_ has quit IRC00:47
*** Leo_m has quit IRC00:48
*** imcsk8_ has quit IRC00:48
*** imcsk8 has joined #openstack-meeting00:49
*** Yipei has joined #openstack-meeting00:49
*** yamahata_ has quit IRC00:49
*** yamahata_ has joined #openstack-meeting00:50
*** Yipei has quit IRC00:51
*** Yipei has joined #openstack-meeting00:51
*** Yipei has quit IRC00:53
*** Yipei has joined #openstack-meeting00:53
*** wanghao has quit IRC00:53
*** wanghao has joined #openstack-meeting00:54
*** xuzhuang has joined #openstack-meeting00:55
*** wanghao_ has joined #openstack-meeting00:55
*** cyg has joined #openstack-meeting00:56
*** yanxingan has joined #openstack-meeting00:58
*** wanghao has quit IRC00:59
*** zhujintao has joined #openstack-meeting01:00
zhiyuan#startmeeting tricircle01:00
openstackMeeting started Wed Mar 14 01:00:15 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
*** openstack changes topic to " (Meeting topic: tricircle)"01:00
openstackThe meeting name has been set to 'tricircle'01:00
*** jbadiapa_ has quit IRC01:00
*** fnaval has joined #openstack-meeting01:00
*** Zames has quit IRC01:01
zhiyuanI have sent out a mail to nominate song as the core reviewer of tricircle, please vote on that mail :)01:01
songthanks for zhiyuan.01:01
*** zxh has joined #openstack-meeting01:03
zhiyuanYipei, I have read your new spec, the overall proposal looks good. could you elaborate how routed network API is used to store the external network infomation in segments?01:04
Yipeiok, no problem01:05
*** aeng has quit IRC01:06
*** pchavva has quit IRC01:06
zhiyuanfine, then you can start coding01:06
zhiyuanfor the port deletion patch, I see CI fails01:08
*** yanxingan has quit IRC01:08
zxhpep8 failed01:09
zhiyuanlooking at the log, I guess that's because the handle function mistakenly processes "shadow port"01:09
*** oddzeng has joined #openstack-meeting01:10
zxhjust have to review01:11
zhiyuanthe "device_owner" of "shadow port" is "compute:shadow", so "_delete_bottom_unbond_port" will also process it01:11
*** hongbin has joined #openstack-meeting01:12
*** bobh has joined #openstack-meeting01:13
zhiyuanshadow ports will exist across regions, we don't need to delete it01:13
zhiyuanthey are deleted when the central port is deleted01:13
zxhi got it01:15
*** jbadiapa_ has joined #openstack-meeting01:16
*** salv-orlando has joined #openstack-meeting01:17
zhujintaohello, everyone~01:17
zhiyuanhi jintao01:18
zhujintaoI am dealing with this problem01:18
*** YanXing_an has joined #openstack-meeting01:19
zhujintao'oslo.config and oslo.service have implemented basic functions'01:19
zhujintaobut  Tricircle have not used these functions01:19
*** harlowja has quit IRC01:20
zhujintaoso I want to bring these functions to Tricircle01:20
zhujintaoso ,what can I get more information about it01:21
*** salv-orlando has quit IRC01:21
zhujintaoand which part of  source code I should concentrate on ?01:21
*** yangyapeng has joined #openstack-meeting01:22
zhiyuanthe goal is to make tricircle api and xmanager support configuration dynamical loading01:22
songit is the bp  enable mutable configuration in rocky?01:22
songI would like do it with zhujintao student.01:23
songi have see the rocky blueprint plan and i want to do the enable mutable configuration.01:23
songi think we have miss two bps which are in q but have not  yet finished . we should also add they to the r. how about it?01:23
songthe miss two bps are  Service function chaining   and Driver-based implementation of Trunk01:23
zhiyuanoh, please add them in the ethpad page01:24
zhiyuanso you will co-work with jintao?01:25
songthanks I will add they after meeting.01:25
*** edmondsw has joined #openstack-meeting01:25
songso we can also add the bps which are in developing to lanuchpad?01:26
*** yangyapeng has quit IRC01:26
*** gongysh has quit IRC01:27
*** rossella_s has quit IRC01:27
*** Yipei has quit IRC01:28
zhiyuanif you would like to take it, register the feature in launchpad01:28
*** Yipei has joined #openstack-meeting01:28
songyes, I would like to do it.and which we register in the launchpad will promise to finished.01:29
*** edmondsw has quit IRC01:29
*** rossella_s has joined #openstack-meeting01:30
xuzhuangHas the work item port deletion in rokcy commited by xiaohan?01:30
songyes,he is working no it now.01:30
songsorry s/no/on01:31
zhiyuani see both ProcessLauncher and ServiceLauncher have handle_signal() function01:32
zhiyuani think this can be used to catch sighup and reload configuration01:33
songyes, also kill command and so on.01:33
songi see the ceph code used the watcher and notify.01:34
songwhen the conf change the will notify the watcher.01:34
zhiyuanand page of oslo.config01:35
*** rossella_s has quit IRC01:35
songgood.thanks for zhiyuan. we will learn the doc after the meeting.01:35
*** Tom-Tom has joined #openstack-meeting01:36
zhujintaothanks for your help~01:36
songit is our pleasure.01:36
zhiyuanand for tricircle code, tricircle/cmd/ tricircle/cmd/ are the entrypoints of api and xmanager01:37
zhujintaogot it01:39
*** wanghao_ has quit IRC01:39
*** gongysh has joined #openstack-meeting01:39
*** wanghao has joined #openstack-meeting01:39
*** rossella_s has joined #openstack-meeting01:39
*** wanghao_ has joined #openstack-meeting01:40
zhiyuanok, other topics?01:40
*** yangyapeng has joined #openstack-meeting01:41
songno for me.01:41
Yipeino from me01:41
*** jamesmcarthur has joined #openstack-meeting01:41
zhujintaono for me01:42
xuzhuangno from me01:42
*** bobh has quit IRC01:42
zhiyuanok, then let's finish our meeting01:43
*** openstack changes topic to "OpenStack Meetings ||"01:43
*** aeng has joined #openstack-meeting01:43
openstackMeeting ended Wed Mar 14 01:43:29 2018 UTC.  Information about MeetBot at . (v 0.1.4)01:43
openstackMinutes (text):
*** xuzhuang has quit IRC01:43
*** kaisers_ has joined #openstack-meeting01:44
*** wanghao has quit IRC01:44
*** Yipei has quit IRC01:46
*** jamesmcarthur has quit IRC01:46
*** Yipei has joined #openstack-meeting01:46
*** kaisers has quit IRC01:47
*** rossella_s has quit IRC01:47
*** Yipei has quit IRC01:48
*** Yipei has joined #openstack-meeting01:49
*** rossella_s has joined #openstack-meeting01:49
*** Yipei has quit IRC01:50
*** Yipei has joined #openstack-meeting01:51
*** Yipei has quit IRC01:52
*** Yipei has joined #openstack-meeting01:52
*** Yipei has quit IRC01:53
*** Yipei has joined #openstack-meeting01:54
*** cyg has quit IRC01:55
*** noslzzp has joined #openstack-meeting01:55
*** Yipei has quit IRC01:56
*** Yipei has joined #openstack-meeting01:56
*** Yipei has quit IRC01:57
*** bobh has joined #openstack-meeting02:05
*** bobh has quit IRC02:07
*** bobh has joined #openstack-meeting02:07
*** aeng has quit IRC02:09
*** bobh has quit IRC02:12
*** jamesmcarthur has joined #openstack-meeting02:13
*** epico has joined #openstack-meeting02:15
*** aeng has joined #openstack-meeting02:22
*** yangyapeng has quit IRC02:25
*** kevzha01_ has quit IRC02:27
*** aeng has quit IRC02:29
*** longkb has joined #openstack-meeting02:29
*** amodi has joined #openstack-meeting02:29
*** kaisers has joined #openstack-meeting02:33
*** armstrong has joined #openstack-meeting02:33
*** yamahata_ has quit IRC02:35
*** kaisers_ has quit IRC02:36
*** mriedem has quit IRC02:37
*** YanXing_an has quit IRC02:39
*** amodi has quit IRC02:42
*** hongbin_ has joined #openstack-meeting02:42
*** hongbin has quit IRC02:43
*** psachin has joined #openstack-meeting02:47
*** YanXing_an has joined #openstack-meeting02:47
*** longkb1 has joined #openstack-meeting02:54
*** armstrong has quit IRC02:54
*** longkb has quit IRC02:55
*** psachin has quit IRC02:59
*** psachin has joined #openstack-meeting03:02
*** psachin has quit IRC03:05
*** YanXing_an has quit IRC03:07
*** psachin has joined #openstack-meeting03:08
*** YanXing_an has joined #openstack-meeting03:10
*** kevzha01_ has joined #openstack-meeting03:11
*** shu-mutou has joined #openstack-meeting03:13
*** edmondsw has joined #openstack-meeting03:14
*** gongysh has quit IRC03:17
*** psachin has quit IRC03:17
*** jamesmcarthur has quit IRC03:17
*** edmondsw has quit IRC03:18
*** salv-orlando has joined #openstack-meeting03:18
*** song has quit IRC03:20
*** YanXing_an has quit IRC03:21
*** salv-orlando has quit IRC03:23
*** epico has quit IRC03:26
*** YanXing_an has joined #openstack-meeting03:27
*** esberglu has quit IRC03:32
*** Zames has joined #openstack-meeting03:32
*** liyi has quit IRC03:33
*** psachin has joined #openstack-meeting03:35
*** liyi has joined #openstack-meeting03:35
*** liyi has quit IRC03:36
*** liyi has joined #openstack-meeting03:36
*** aeng has joined #openstack-meeting03:37
*** liyi has quit IRC03:37
*** liyi_ has joined #openstack-meeting03:38
*** YanXing_an has quit IRC03:39
*** liyi_ has quit IRC03:40
*** rbudden has quit IRC03:44
*** epico has joined #openstack-meeting03:45
*** aeng has quit IRC03:47
*** yamahata_ has joined #openstack-meeting03:51
*** Zames has quit IRC03:53
*** david-lyle has joined #openstack-meeting03:55
*** YanXing_an has joined #openstack-meeting03:57
*** gongysh has joined #openstack-meeting04:00
*** hongbin_ has quit IRC04:02
*** Zames has joined #openstack-meeting04:02
*** janki has joined #openstack-meeting04:02
*** esberglu has joined #openstack-meeting04:05
*** masaito has joined #openstack-meeting04:07
*** yanxingan has joined #openstack-meeting04:09
*** esberglu has quit IRC04:09
*** YanXing_an has quit IRC04:11
*** harlowja has joined #openstack-meeting04:12
*** ianychoi_ has joined #openstack-meeting04:12
*** aeng has joined #openstack-meeting04:13
*** ianychoi has quit IRC04:15
*** Zames has quit IRC04:16
*** zxh has quit IRC04:16
*** zxh has joined #openstack-meeting04:16
*** salv-orlando has joined #openstack-meeting04:19
*** ricolin has joined #openstack-meeting04:20
*** links has joined #openstack-meeting04:22
*** salv-orlando has quit IRC04:24
*** liyi has joined #openstack-meeting04:31
*** dmacpher has joined #openstack-meeting04:34
*** chyka has joined #openstack-meeting04:38
*** harlowja has quit IRC04:40
*** chyka has quit IRC04:43
*** Druid201 has joined #openstack-meeting04:43
*** keiko_ has joined #openstack-meeting04:44
*** Druid201 has quit IRC04:46
*** andreas_s has joined #openstack-meeting04:48
*** andreas_s has quit IRC04:52
*** liyi has quit IRC04:56
*** esberglu has joined #openstack-meeting04:59
*** alexchadin has joined #openstack-meeting05:03
*** esberglu has quit IRC05:03
*** uve has joined #openstack-meeting05:04
*** fnaval has quit IRC05:12
*** singlethink has joined #openstack-meeting05:13
*** shu-mutou is now known as shu-mutow05:16
*** salv-orlando has joined #openstack-meeting05:20
*** singlethink has quit IRC05:20
*** salv-orlando has quit IRC05:24
*** markstur has joined #openstack-meeting05:26
*** fnaval has joined #openstack-meeting05:29
*** sidx64 has joined #openstack-meeting05:32
*** fnaval has quit IRC05:33
*** esberglu has joined #openstack-meeting05:34
*** esberglu has quit IRC05:38
*** markstur has quit IRC05:44
*** aeng has quit IRC05:45
*** fnaval has joined #openstack-meeting05:45
*** anilvenkata has quit IRC05:46
*** claudiub has joined #openstack-meeting05:48
*** Spazmotic has joined #openstack-meeting05:48
*** sidx64 has quit IRC05:49
*** Spaz-Home has quit IRC05:49
*** fnaval has quit IRC05:50
*** sridharg has joined #openstack-meeting05:50
*** sidx64 has joined #openstack-meeting05:51
*** masber has quit IRC05:53
*** yanxingan has quit IRC05:55
*** sidx64 has quit IRC05:59
*** anilvenkata has joined #openstack-meeting06:00
*** sidx64 has joined #openstack-meeting06:00
*** uve has quit IRC06:00
*** yanxingan has joined #openstack-meeting06:02
*** markstur_ has joined #openstack-meeting06:03
*** e0ne has joined #openstack-meeting06:04
*** markstur_ has quit IRC06:08
*** markstur has joined #openstack-meeting06:10
*** kiennt26__ has quit IRC06:14
*** markstur has quit IRC06:14
*** kiennt26 has joined #openstack-meeting06:14
*** fnaval has joined #openstack-meeting06:16
*** anilvenkata has quit IRC06:18
*** anilvenkata has joined #openstack-meeting06:19
*** fnaval has quit IRC06:21
*** salv-orlando has joined #openstack-meeting06:21
*** salv-orlando has quit IRC06:25
*** esberglu has joined #openstack-meeting06:28
*** alexchadin has quit IRC06:28
*** dbecker has quit IRC06:28
*** alexchadin has joined #openstack-meeting06:29
*** esberglu has quit IRC06:32
*** fnaval has joined #openstack-meeting06:33
*** jbadiapa_ has quit IRC06:33
*** salv-orlando has joined #openstack-meeting06:34
*** ykatabam has quit IRC06:35
*** fnaval has quit IRC06:37
*** rossella_s has quit IRC06:38
*** radeks has joined #openstack-meeting06:38
*** rossella_s has joined #openstack-meeting06:38
*** sidx64_ has joined #openstack-meeting06:38
*** sidx64 has quit IRC06:40
*** trinaths has joined #openstack-meeting06:41
*** dims has quit IRC06:41
*** sidx64 has joined #openstack-meeting06:42
*** dims has joined #openstack-meeting06:43
*** ianychoi__ has joined #openstack-meeting06:43
*** sidx64_ has quit IRC06:45
*** samP has quit IRC06:45
*** samP_ has joined #openstack-meeting06:45
*** imcsk8_ has joined #openstack-meeting06:46
*** ianychoi_ has quit IRC06:46
*** jbadiapa_ has joined #openstack-meeting06:48
*** dims has quit IRC06:48
*** imcsk8 has quit IRC06:48
*** dims has joined #openstack-meeting06:49
*** edmondsw has joined #openstack-meeting06:50
*** ianychoi__ is now known as ianychoi06:51
*** edmondsw has quit IRC06:54
*** dmacpher has quit IRC06:56
*** liyi has joined #openstack-meeting06:57
*** markstur has joined #openstack-meeting07:00
*** liyi has quit IRC07:02
*** pcaruana has joined #openstack-meeting07:04
*** markstur has quit IRC07:04
*** thingee has joined #openstack-meeting07:06
*** fnaval has joined #openstack-meeting07:07
*** fnaval has quit IRC07:11
*** sidx64_ has joined #openstack-meeting07:12
*** sidx64 has quit IRC07:13
*** longkb1 has quit IRC07:13
*** egallen has joined #openstack-meeting07:14
*** andreas_s has joined #openstack-meeting07:14
*** alexchadin has quit IRC07:16
*** sidx64_ has quit IRC07:17
*** alexchadin has joined #openstack-meeting07:17
*** sidx64 has joined #openstack-meeting07:18
*** oddzeng has quit IRC07:19
*** marios has joined #openstack-meeting07:22
*** yanxingan has quit IRC07:27
*** dangtrinhnt has joined #openstack-meeting07:27
*** salv-orlando has quit IRC07:28
*** andreas_s has quit IRC07:31
*** andreas_s has joined #openstack-meeting07:32
*** masber has joined #openstack-meeting07:32
*** salv-orlando has joined #openstack-meeting07:34
*** armax has quit IRC07:34
*** yanxingan has joined #openstack-meeting07:35
*** trinaths has quit IRC07:38
*** alexchadin has quit IRC07:39
*** chyka has joined #openstack-meeting07:42
*** rubasov has left #openstack-meeting07:43
*** chyka has quit IRC07:47
*** alexchadin has joined #openstack-meeting07:47
*** tssurya has joined #openstack-meeting07:51
*** rossella_s has quit IRC07:51
*** longkb has joined #openstack-meeting07:51
*** rossella_s has joined #openstack-meeting07:53
*** longkb2 has quit IRC07:55
*** alexchadin has quit IRC07:57
*** alexchadin has joined #openstack-meeting07:58
*** keiko_ has quit IRC07:58
*** liyi has joined #openstack-meeting07:59
diablo_rojo#startmeeting fc_sig08:00
openstackMeeting started Wed Mar 14 08:00:14 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:00
*** openstack changes topic to " (Meeting topic: fc_sig)"08:00
openstackThe meeting name has been set to 'fc_sig'08:00
diablo_rojoHello :)08:00
diablo_rojoAlready two more people than I had even hoped for :)08:00
diablo_rojoI guess I don't need to ask if people are around we can just hop to it!08:01
*** rossella_s has quit IRC08:01
diablo_rojo#link Meeting Agenda08:01
diablo_rojoI also created a ping list spot in the agenda if you all want to get pinged when I start things next time.08:02
*** longkb1 has joined #openstack-meeting08:02
diablo_rojoLittle bit of an intro, at the PTG we discussed doing a weekly meeting to kind of just go through some standing weekly items and then go through anything new (if there are things).08:02
diablo_rojoThe two standing items being going through unmerged patches from new contributors and going through questions tag as contributor or contribution.08:03
diablo_rojo#topic New Contributor Patches08:03
*** openstack changes topic to "New Contributor Patches (Meeting topic: fc_sig)"08:03
*** dbecker has joined #openstack-meeting08:04
*** liyi has quit IRC08:04
diablo_rojo#link!+(10068)%22+is:open New Contributor and Unmerged Patches08:04
*** dangtrinhnt has quit IRC08:04
*** markstur has joined #openstack-meeting08:04
diablo_rojoThe idea is to go through this list and wherever our areas of expertise overlap, try to go and assign people to review them.08:04
diablo_rojoOr something like that.08:04
*** rossella_s has joined #openstack-meeting08:05
gmann_i can see 2 tempest patch which i can do quickly. seems pep8 error in one of them. i will help them08:05
diablo_rojoI figure for the first few weeks we can just take a chunk of the list at a time and then as the weeks progress we will be more up to date and there will be less to go through.08:05
diablo_rojogmann_, awesome :)08:06
diablo_rojoThat would be super helpful!08:06
thingeeinteresting we got patches going back to 2014. I see one that has never gotten an answer back then.08:06
thingeepatches going back to 2014 with that filter*08:06
gmann_for other projects patches, should we add core team of PTL to respond if they are stuck without review ?08:06
*** zhujintao has quit IRC08:06
diablo_rojoIf there are ones we can't cover, hopefully we have a project liaison that we can poke to look at/foster the newbie if they aren't already08:07
*** fnaval has joined #openstack-meeting08:07
gmann_ah yea project liaison08:07
diablo_rojothingee, that's super sad :( Hopefully routinely going through them will make that not a problem anymore.08:07
* diablo_rojo looks through list08:08
*** markstur has quit IRC08:08
thingeemaybe as a data point we can try to shrink this list, or the ones that have never gotten an answer.08:08
cmurphya lot of these are for the sandbox repository, we probably don't really need reach out on those?08:09
thingeeprobably some of these can be abandoned by now08:09
masayukig[m]It looks many of them are in the sandbox project08:09
diablo_rojocmurphy, yeah I would think not.08:09
diablo_rojoSeeing a lot of DNMs too.08:09
thingeeoh heh I'm not even look at projects :)08:09
gmann_yea we can clean those08:09
thingeesleepy mike08:09
diablo_rojoMaybe we can reach out to them about abandoning them?08:09
diablo_rojothingee, you and me both :)08:09
diablo_rojoOkay so maybe not getting around to assigning anything this round, but wherever we have spare time in the next week, to spend a few minutes reviewing what we can and then reaching out to those that should be abandoned.08:10
diablo_rojoTheres a lot of cleanup to do.08:10
thingeesansandbox is open, so maybe we need some periodic cleaner thing08:11
*** fnaval has quit IRC08:11
diablo_rojothingee, yeah that would be helpful08:11
diablo_rojoEasier to focus on what needs to be focused on.08:11
thingeeor our filter can ignore sandbox :)08:12
diablo_rojoYeah that totally works too08:12
diablo_rojoHow do you even filter out a certain project?08:13
*** dmacpher has joined #openstack-meeting08:13
*** dmacpher has quit IRC08:13
cmurphyadd NOT project:openstack-dev/sandbox08:13
diablo_rojoAh, all caps.08:13
diablo_rojolowercase wasn't cutting it08:13
masayukig[m]ah, NOT08:13
cmurphythe - works too08:14
diablo_rojoWay more manageable length of list when you take those out08:14
thingeeoh you can also do -project:openstack/sandbox08:14
*** tesseract has joined #openstack-meeting08:14
diablo_rojocmurphy, you so smart :)08:14
thingeeoh nvm cmurphy already mentioned that08:14
diablo_rojoSo many things I didn't know how to do.08:14
thingeetoday I learned :)08:15
diablo_rojoMe too!08:15
masayukig[m]same here!08:15
gmann_- is easy one :)08:15
*** masaito has left #openstack-meeting08:15
diablo_rojoOkay so I propose we all take an action item to like.. go respond to 3? 5? or if you can't respond, find a project liaison to cover it?08:16
thingeegood collaboration folks08:16
diablo_rojoDoes that seem reasonable?08:16
diablo_rojoI see some swiftclient ones maybe we can get mattoliverau on08:17
*** salv-orlando has quit IRC08:17
thingeealso -openstack-dev/ci-sandbox08:18
*** arnewiebalck_ has quit IRC08:19
diablo_rojoEven shorter list now.08:19
diablo_rojoOkay so I can update that link on the agenda08:21
diablo_rojofor next time08:21
*** wanghao_ has quit IRC08:21
masayukig[m]I think it should be AND? #link!+(10068)%22+is:open+-project:+openstack-dev/sandbox+AND+-project:openstack-dev/ci-sandbox08:22
diablo_rojo#Action Everyone try to review to or get a project liaison to review a min of three patches from this list for next week08:22
*** wanghao has joined #openstack-meeting08:23
diablo_rojoOnto the next standing item08:23
diablo_rojo#topic questions08:23
*** openstack changes topic to " questions (Meeting topic: fc_sig)"08:23
*** qwebirc81180 has joined #openstack-meeting08:24
diablo_rojoSo, I imagine this will be similar where we have a sizable list in the beginning and will have to slowly whittle it down.08:24
*** qwebirc81180 has quit IRC08:24
gmann_just replied on one post though that was little old -
gmann_but seems need moderator approval before answer gets posted.08:24
*** yamahata_ has quit IRC08:24
diablo_rojo#link Contribution08:24
diablo_rojoDo they always need moderator approval?08:25
diablo_rojo#link Contributor tag08:26
diablo_rojoThat one is a bit shorter08:26
diablo_rojoNeither is that bad08:26
*** liyi has joined #openstack-meeting08:27
diablo_rojoSo maybe the action item for this one is just respond to 2?08:27
gmann_this msg  - "Your post was placed on the moderation queue and will be published after the moderator approval. At least 10 karma points is required to post links"08:27
diablo_rojoDoes that work for people?08:27
diablo_rojogmann_, oh interesting08:27
gmann_after 10 karma it might work wihtout approval08:28
diablo_rojoHelps with avoiding spam and bots I would think.08:28
diablo_rojogmann_, yeah08:28
gmann_RE: respond to 2 post works fine for me.08:29
diablo_rojoSince I didn't hear objections to the proposal I will make that another action item :)08:29
diablo_rojo#action Respond to at least 2 questions on ask.openstack.org08:29
diablo_rojo#topic New Contributor of the Week08:30
*** openstack changes topic to "New Contributor of the Week (Meeting topic: fc_sig)"08:30
diablo_rojoSo this idea was brought up a while ago- I think by ttx originally. I thought since we would be sifting through code reviews and focusing on new contributors any way it would be easy enough for us to come up with a name each week and like two sentence to maybe include in the developer digest?08:31
diablo_rojothingee, thoughts on that?08:31
gmann_idea is nice.08:32
diablo_rojogmann_, I can't take credit for it, but I definitely agree.08:32
gmann_but what will be the criteria to choose? quality of code, complexity of patch, project etc?08:32
diablo_rojogmann_, I think it can vary week to week.08:32
*** electrofelix has joined #openstack-meeting08:33
diablo_rojoThose would be things to keep in mind for sure.08:33
*** egallen has quit IRC08:33
*** mdbooth has quit IRC08:33
diablo_rojo#action If one of the reviews you do is of particular note, try to remember to bring the person up during this part of the meeting next week08:34
diablo_rojoOkay, last planned agenda item!08:35
diablo_rojo#topic Rollover of #openstack-101 to #openstack-dev08:35
*** openstack changes topic to "Rollover of #openstack-101 to #openstack-dev (Meeting topic: fc_sig)"08:35
thingeesounds fine to me, anyone can contribute to the dev digest here:
diablo_rojothingee, oh yes! Thanks for the link, I had it on the agenda and forgot to actually use it lol.08:35
thingeecan make a section to mention new contributors. ok yes new topic ;)08:35
diablo_rojothingee, falling asleep? :)08:35
thingeeeh yea :D08:36
gmann_what time there for you guys? mid night?08:36
diablo_rojoSo, basically we want to roll this channel over and if I recall, we got the directions on how to do it from fungi at the PTG and its in our FC SIG etherpad.08:36
thingee1:36, but DST with a 1 year old08:36
diablo_rojogmann_, closing in on 2 AM08:36
diablo_rojoBasically my reason for bringing this up is that it doesn't have an owner :)08:37
*** e0ne has quit IRC08:37
diablo_rojoIf anyone wants to start moving this forward it would be vastly appreciated :)08:37
thingeediablo_rojo: i can figure it out08:37
diablo_rojothingee, oh cool that would be awesome.08:38
* diablo_rojo goes to get link fungi provided08:38
*** edmondsw has joined #openstack-meeting08:38
diablo_rojothingee, ^^08:38
gmann_thingee: thanks08:39
thingeeomg irc commands08:39
thingeethe worse kind too of having to talk to chanserv.08:39
diablo_rojoha ha ha yeah a lot of them08:40
thingeealways feel weird telling that person my password.08:40
diablo_rojoI guess I will owe you a woodford reserve for handling all that :)08:40
diablo_rojoThe tips on that section are also very interesting08:41
cmurphyspotz had a suggestion on the ml to direct to #openstack instead of #openstack-dev, thoughts on that?08:41
thingeeoh haha this will be interesting fun?08:41
diablo_rojocmurphy, yeah I had seen that but didn't get time to respond. I feel like in general we want to direct to #openstack-dev since the fc sig was originally formed in response to people that needed help with the contribution process?08:42
diablo_rojoOther people have thoughts?08:43
*** edmondsw has quit IRC08:43
thingeecontribution can be more than dev, so #openstack can be fine.08:43
diablo_rojoAt this point the contributor guide points #openstack-dev but that can be changed08:43
thingeeI think i just want people somewhere active that they can feel like they want to listen in and maybe contribute in discussion08:44
* diablo_rojo doesn't currently sit in the #openstack channel08:44
diablo_rojois it pretty active?08:44
cmurphyboth channels are more active than -101 so i don't have strong feelings either way08:44
diablo_rojoAll the usual suspects?08:45
diablo_rojoFair :)08:45
thingeeI sit in there, and very seldomly answer questions. I don't always feel like I have the right answer, though maybe that would trigger someone smarter to answer.08:45
diablo_rojoI agree #openstack-101 needs to go away08:45
cmurphyslightly different group of active people than in -dev08:45
diablo_rojoMaybe we can direct to both? Depending on the interest? I would hate for people to be shuffled to one and then get shuffled to the other.08:46
diablo_rojoEspecially before they are used to IRC and watching 10 channels at once.08:46
gmann_#openstack channel says "Openstack Support Channel, Development in #openstack-dev | Wiki: | Docs: | Answers: https://ask.o..."08:48
gmann_which looks more generic one to redirect people to right things08:48
diablo_rojogmann_, yeah I am seeing in the irc list that it says: 'general discussion, support '08:49
diablo_rojoI guess I still lean towards pointing people to #openstack-dev..08:50
*** kopecmartin has joined #openstack-meeting08:50
*** ykatabam has joined #openstack-meeting08:50
diablo_rojoI can respond on the ML tomorrow morning with my thoughts.08:51
diablo_rojo#topic General Discussion08:51
*** openstack changes topic to "General Discussion (Meeting topic: fc_sig)"08:51
diablo_rojoOnly other thing I have to mention is if we see someone pushing the same sort of patch in a bunch of different projects (i.e. spelling change or link updates) we should probably reach out to them? I know this was kind of why the SIG was created in the first place.08:53
diablo_rojoJust something to be mindful of I guess.08:53
* diablo_rojo is getting too tired to string words together into an actual sentence08:54
diablo_rojoSo thats all I had!08:54
diablo_rojo6 min to spare.08:54
diablo_rojoAnyone have anything else to mention?08:54
gmann_nothing from my side.08:55
thingeenothing here, thanks for leading diablo_rojo08:55
diablo_rojoThanks for staying up thingee :)08:55
*** kiennt26 has quit IRC08:55
*** rossella_s has quit IRC08:55
diablo_rojoAnd thank you everyone else for coming to our first meeting!08:55
gmann_thanks diablo_rojo for chairing.08:56
thingeewe'll have shirts printed08:56
diablo_rojoDon't forget to add yourselves to the ping list.08:56
diablo_rojothingee, I do love OpenStack T-Shirts08:56
diablo_rojoWithout further ado...08:56
*** openstack changes topic to "OpenStack Meetings ||"08:56
openstackMeeting ended Wed Mar 14 08:56:58 2018 UTC.  Information about MeetBot at . (v 0.1.4)08:57
openstackMinutes (text):
diablo_rojoHave a good morning/afternoon/sleep!08:57
gmann_thanks, have good sleep guys08:57
* diablo_rojo goes to finish baking pies and fall asleep08:57
*** rossella_s has joined #openstack-meeting08:57
*** fzdarsky has joined #openstack-meeting08:58
*** fzdarsky has quit IRC08:59
*** sidx64 has quit IRC09:03
*** salv-orlando has joined #openstack-meeting09:07
*** rossella_s has quit IRC09:07
*** fzdarsky has joined #openstack-meeting09:08
*** rossella_s has joined #openstack-meeting09:08
*** dbecker has quit IRC09:10
*** dbecker has joined #openstack-meeting09:11
*** longkb1 has quit IRC09:12
*** gema has left #openstack-meeting09:13
*** julim has quit IRC09:14
*** shu-mutow has quit IRC09:14
*** browny_ has joined #openstack-meeting09:15
*** yamamoto_ has joined #openstack-meeting09:18
*** hemna_ has quit IRC09:20
*** trinaths has joined #openstack-meeting09:21
*** yamamoto has quit IRC09:22
*** gongysh has quit IRC09:22
*** rossella_s has quit IRC09:29
*** rossella_s has joined #openstack-meeting09:30
*** lpetrut has joined #openstack-meeting09:34
*** rossella_s has quit IRC09:35
*** armax has joined #openstack-meeting09:35
*** rossella_s has joined #openstack-meeting09:36
*** wanghao has quit IRC09:36
*** browny_ has quit IRC09:37
*** wanghao has joined #openstack-meeting09:37
*** wanghao has quit IRC09:37
*** wanghao has joined #openstack-meeting09:37
*** wanghao has quit IRC09:38
*** wanghao has joined #openstack-meeting09:38
*** wanghao has quit IRC09:39
*** wanghao has joined #openstack-meeting09:39
*** wanghao has quit IRC09:39
*** wanghao has joined #openstack-meeting09:40
*** wanghao has quit IRC09:40
*** wanghao has joined #openstack-meeting09:40
*** wanghao has quit IRC09:41
*** wanghao has joined #openstack-meeting09:41
*** yanxingan has quit IRC09:42
*** wanghao has quit IRC09:42
*** wanghao has joined #openstack-meeting09:42
*** wanghao has quit IRC09:43
*** wanghao has joined #openstack-meeting09:44
*** markstur has joined #openstack-meeting09:50
*** browny_ has joined #openstack-meeting09:50
*** diman has joined #openstack-meeting09:50
*** phil has joined #openstack-meeting09:51
*** Tom-Tom has quit IRC09:52
*** phil is now known as Guest2881309:52
*** Tom-Tom has joined #openstack-meeting09:52
*** yanxingan has joined #openstack-meeting09:55
*** markstur has quit IRC09:55
*** egallen has joined #openstack-meeting09:56
*** yanxingan has quit IRC09:57
*** Tom-Tom has quit IRC09:57
*** liyi has quit IRC10:00
*** rossella_s has quit IRC10:04
*** diman has quit IRC10:04
*** rossella_s has joined #openstack-meeting10:05
*** tovin07_ has quit IRC10:06
*** fnaval has joined #openstack-meeting10:06
*** fnaval has quit IRC10:11
*** diman has joined #openstack-meeting10:12
*** rcernin has quit IRC10:13
*** sidx64 has joined #openstack-meeting10:17
*** alexchadin has quit IRC10:18
*** diman has quit IRC10:20
*** sidx64 has quit IRC10:24
*** browny_ has quit IRC10:24
*** priteau has joined #openstack-meeting10:26
*** edmondsw has joined #openstack-meeting10:26
*** browny_ has joined #openstack-meeting10:27
*** rossella_s has quit IRC10:28
*** browny_ has quit IRC10:29
*** edmondsw has quit IRC10:31
*** rossella_s has joined #openstack-meeting10:32
*** esberglu has joined #openstack-meeting10:41
*** Zames has joined #openstack-meeting10:41
*** browny_ has joined #openstack-meeting10:42
*** sidx64 has joined #openstack-meeting10:44
*** esberglu has quit IRC10:45
*** daveholland has joined #openstack-meeting10:46
*** browny_ has quit IRC10:46
*** sidx64 has quit IRC10:48
*** alexchadin has joined #openstack-meeting10:48
*** Zames has quit IRC10:49
*** trinaths has quit IRC10:49
*** browny_ has joined #openstack-meeting10:50
*** epico has quit IRC10:50
*** alexchadin has quit IRC10:51
*** mikal_ has joined #openstack-meeting10:52
*** alexchadin has joined #openstack-meeting10:53
*** mikal has quit IRC10:53
*** sidx64 has joined #openstack-meeting10:55
*** alexchadin has quit IRC10:55
*** belmoreira has joined #openstack-meeting10:56
*** Zames has joined #openstack-meeting10:56
*** HeOS has joined #openstack-meeting10:57
*** martial_ has joined #openstack-meeting10:57
*** sidx64 has quit IRC10:58
*** esberglu has joined #openstack-meeting10:58
*** oneswig has joined #openstack-meeting10:59
*** Zames has quit IRC10:59
*** Zames has joined #openstack-meeting11:00
martial_#startmeeting Scientific-SIG11:01
openstackMeeting started Wed Mar 14 11:01:27 2018 UTC and is due to finish in 60 minutes.  The chair is martial_. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.11:01
*** openstack changes topic to " (Meeting topic: Scientific-SIG)"11:01
openstackThe meeting name has been set to 'scientific_sig'11:01
*** sidx64 has joined #openstack-meeting11:01
martial_Good morning11:01
oneswigMorning martial_ thanks for driving today11:01
priteauGood morning Martial11:01
*** verdurin-alt has joined #openstack-meeting11:02
martial_hey Stig, Pierre11:02
martial_stig: sure thing11:02
davehollando/ (might get pulled to another meeting but hoping to hear/talk about hierarchical projects)11:02
martial_well let's get started with that then :)11:02
martial_#topic hierarchical projects11:02
*** openstack changes topic to "hierarchical projects (Meeting topic: Scientific-SIG)"11:02
martial_daveholland: want to give us the brief on the forum post?11:03
*** esberglu has quit IRC11:03
davehollandI haven't seen it but I have seen past proposals I think, I can outline the use case for us if you want?11:03
*** alexchadin has joined #openstack-meeting11:04
oneswig#link discussion on user-committee list
oneswigThat the one Martial?11:05
martial_The forum post contained: "[...] an enforcement model is an opinionated way of how a quota,    or limit, should behave with respect to other parent, sibling, or child    projects. It's possible to think of multiple ways in which enforcement    can be done, and it's not that there is one right way and the rest are    wrong, just a difference in how quotas might need to behave for different deployments."11:05
martial_I had this one (thanks Stig)11:05
*** zxh has quit IRC11:06
davehollandThanks, I hadn't caught up with email that far yet11:06
*** fnaval has joined #openstack-meeting11:06
martial_this one link and this one link11:06
*** ianychoi has quit IRC11:07
davehollandFWIW our users would like nested/heirarchical projects to look as much as possible like the current implementation; but to allow a higher-level project to be a reporting method for the subprojects. If it was an implementation detail that a project could only contain either projects or other resources that would be OK.11:07
daveholland(i.e. a top-level "container" project with leaf projects containing instances, volumes etc)11:08
martial_so "We'd like to see if the User Committee can help us collect more    information from users and operators about how they expect enforcement    to be done. Do your deployments use hierarchical projects? How do you    manage quota today? Do you have expectations about how quotas and limits    work across related projects (e.g. setting quota on a parent project   affects the children in X ways)?"s11:08
*** sidx64 has quit IRC11:09
davehollandwe don't do hierarchical projects today (just migrating off Liberty, to Pike) and there's frustration around having to track many different quotas11:09
belmoreiraCERN has a blog post about our use case:
*** janki has quit IRC11:10
*** sidx64 has joined #openstack-meeting11:11
*** fnaval has quit IRC11:11
martial_looking at the options section of this post helps as well, thank you belmoreira11:12
davehollandMaybe I'm getting ahead a bit, but I can imagine user desire for both absolute and proportional sub-project quota settings ("I want this CI subproject to have 10 VCPUs", vs "I want my two PhD students to each have 50% of this project's quota")11:12
*** browny_ has quit IRC11:12
martial_that is also how we would use it for our users but can this work with cpu overprovisioning for example?11:13
*** ianychoi has joined #openstack-meeting11:13
*** rossella_s has quit IRC11:14
davehollandWe are only just getting into overprovisioning/oversubscription, previously have set cpu_allocation_ratio=1 everywhere. Should a VCPU on a potentially-oversubscribed hypervisor count for 1 or 1/N VCPUs?11:14
belmoreiradaveholland cpu overprovisioning is related with the allocation that you allow. I don't see a problem11:14
*** oneswig has quit IRC11:15
martial_priteau: does this affect you as well?11:15
*** markstur has joined #openstack-meeting11:15
davehollandI see a need to distinguish, because we intend to allow users to choose oversubscribed or not, based on flavour11:15
priteaumartial_: being mostly bare-metal, we don't use overprovisioning, but we may want to use hierarchical projects for teachers who then use sub-projects for groups of students. We could work with absolute quota settings but it would surely be easier if proportional was possible.11:17
*** browny_ has joined #openstack-meeting11:17
*** rossella_s has joined #openstack-meeting11:17
martial_so both models have apllications11:18
davehollandmartial_: yes, definitely11:19
*** brault has joined #openstack-meeting11:19
*** bobh has joined #openstack-meeting11:19
martial_the picture at the end of the cern blog post and the explaination are a good example of the complexity11:19
*** markstur has quit IRC11:20
martial_we have had a couple users groups explain to us how they use the model, and both cases are represented11:21
davehollandAlso a vote from here for "It should be possible for an administrator to lower the limit on a child project below the current usage." - sometimes it's necessary to get people to tidy their rooms :)11:21
*** diman has joined #openstack-meeting11:21
martial_daveholland: or release a GPU :)11:22
martial_any other point of view on this subject?11:22
martial_because this is a conversation in an open forum, we would like to invite people to explain their use case.11:24
martial_as a reminder, the link for this topic can be found in the ML archives at11:24
martial_# link
martial_(silly fingers)11:24
verdurin-altOur users would probably be similar to daveholland11:25
martial_thank you verdurin-alt11:25
martial_thank you all for sharing your comments, this is not going to be solved this morning, but as we are trying to bring awareness to the problem, we invite all to contribute to the forum11:27
martial_any additional comment on this topic?11:27
*** lhx_ has joined #openstack-meeting11:27
martial_moving on to the next topic then11:28
martial_#topic upcoming Federated Cloud workshop11:28
*** openstack changes topic to "upcoming Federated Cloud workshop (Meeting topic: Scientific-SIG)"11:28
martial_#link https://federatedcloud.eventbrite.com11:29
martial_Some of you might be familair with the "Open Research Cloud" effort that was started at the Boston summit last yea11:29
*** diman has quit IRC11:30
*** chyka has joined #openstack-meeting11:30
*** bobh has quit IRC11:30
martial_in September 2017, the National Institute of Standards and Technology (NIST) stated a Public Working Group to bring people together to discuss cloud interoperability11:30
martial_this was an effort in collaboration with the IEEE P230211:30
martial_next week in Gaithersburg, MD, USA we are continuing this conversation with a meeting hosted by the NIST PWG to bring together people and continue our conversation on this effort11:31
martial_more details are at the link posted above11:32
martial_any question on this effort?11:33
martial_we will have remote participation for people who are interested11:33
verdurin-altmartial_ - that was going to be my question11:33
martial_and some of the members of our community are joining us11:34
*** chyka has quit IRC11:34
*** PeteC has joined #openstack-meeting11:34
martial_note that it is not openstack specific (IEEE effort)11:35
davehollandthere was some interest in ORC here but I've not heard of this event, I'll pass it on11:35
martial_daveholland: my apologies, I have posted about it in the forum but we have not followed up11:35
*** lhx_ has quit IRC11:35
*** lhx_ has joined #openstack-meeting11:35
martial_I mention it once in a while :)11:35
*** rossella_s has quit IRC11:36
*** sambetts|afk is now known as sambetts11:36
martial_but we truly welcome our community and participation, so please feel free to share the information11:36
*** Zames has quit IRC11:36
martial_the plan is so far to host the follow up meeting during the Vancouver Summit11:37
*** rossella_s has joined #openstack-meeting11:37
*** kaisers_ has joined #openstack-meeting11:37
*** diman has joined #openstack-meeting11:37
martial_Ildiko has been instrumental to help us with the effort11:37
*** noslzzp has quit IRC11:37
martial_any questions that I can answer?11:38
martial_cool :)11:39
PeteCI've not heard anything regarding spot price equivalents in OpenStack for a while. Has anyone heard anything ?11:39
*** diman has quit IRC11:40
martial_bringing us to11:40
martial_#topic AOB11:40
*** openstack changes topic to "AOB (Meeting topic: Scientific-SIG)"11:40
*** kaisers has quit IRC11:40
martial_Pete: you are talking about pricing comparison with AWS and such?11:41
PeteCThe ability to use pre-emptive instances, which may be disposable if higher priority instances are required.11:42
*** janki has joined #openstack-meeting11:43
martial_this sounds like it could be a side conversation to the nested quota we had earlier11:43
*** salv-orlando has quit IRC11:44
verdurin-altPeteC there's a summary of the Dublin PTG discussion about this here
PeteCSo this ( I think ) is slightly skewed to quotas.11:44
PeteCand ty11:44
martial_PeteC: Stig might be able to provide additional information on spot instances during a follow up meeting11:47
martial_(beyond the SIG's PTG notes)11:47
martial_PeteC: thank you for brining this up, I will follow up with Stig and have this topic added to a future conversation11:48
martial_anything else?11:49
martial_okay then, with that, I will call the meeting to an end, thank you for joining us Today11:51
davehollandthanks :)11:51
martial_and if you have quota needs, join the mailing list/forum conversation :)11:52
davehollandI will try to catch up on my email...!11:52
*** openstack changes topic to "OpenStack Meetings ||"11:52
openstackMeeting ended Wed Mar 14 11:52:56 2018 UTC.  Information about MeetBot at . (v 0.1.4)11:52
openstackMinutes (text):
priteauGood bye everyone!11:53
martial_Hoping to see people in Vancouver in a couple of months11:54
*** diman has joined #openstack-meeting11:54
davehollandyes, hope so11:54
*** markstur has joined #openstack-meeting11:58
*** kopecmartin_ has joined #openstack-meeting12:01
*** noslzzp has joined #openstack-meeting12:01
*** e0ne has joined #openstack-meeting12:01
*** browny_ has quit IRC12:02
*** markstur has quit IRC12:02
*** kopecmartin has quit IRC12:03
*** amodi has joined #openstack-meeting12:07
*** fnaval has joined #openstack-meeting12:07
*** raildo has joined #openstack-meeting12:07
*** kei-ichi has quit IRC12:08
*** kei-ichi has joined #openstack-meeting12:08
*** browny_ has joined #openstack-meeting12:09
*** kei-ichi has quit IRC12:09
*** kei-ichi has joined #openstack-meeting12:09
*** dprince has joined #openstack-meeting12:10
*** fnaval has quit IRC12:11
*** martial_ has quit IRC12:13
*** zhongjun has quit IRC12:14
*** pchavva has joined #openstack-meeting12:14
*** browny_ has quit IRC12:15
*** yamamoto_ has quit IRC12:17
*** lhx_ has quit IRC12:18
*** yamamoto has joined #openstack-meeting12:18
*** rossella_s has quit IRC12:18
*** markstur has joined #openstack-meeting12:19
*** julim has joined #openstack-meeting12:20
*** browny_ has joined #openstack-meeting12:20
*** rossella_s has joined #openstack-meeting12:21
*** verdurin-alt has left #openstack-meeting12:21
*** chyka has joined #openstack-meeting12:23
*** markstur has quit IRC12:23
*** edmondsw has joined #openstack-meeting12:24
*** julim has quit IRC12:25
*** julim has joined #openstack-meeting12:25
*** browny_ has quit IRC12:27
*** longkb1 has joined #openstack-meeting12:27
*** bobh has joined #openstack-meeting12:27
*** browny_ has joined #openstack-meeting12:27
*** chyka has quit IRC12:27
*** daveholland has quit IRC12:28
*** rossella_s has quit IRC12:34
*** rossella_s has joined #openstack-meeting12:35
*** ykatabam has quit IRC12:35
*** bobh has quit IRC12:36
*** bobh has joined #openstack-meeting12:36
*** yamamoto has quit IRC12:38
*** claudiub has quit IRC12:39
*** egallen has quit IRC12:39
*** yamamoto has joined #openstack-meeting12:39
*** bobh has quit IRC12:41
*** yamamoto has quit IRC12:44
*** salv-orlando has joined #openstack-meeting12:44
*** lhx_ has joined #openstack-meeting12:44
*** salv-orlando has quit IRC12:49
*** rosmaita has joined #openstack-meeting12:50
*** yamamoto has joined #openstack-meeting12:55
*** edmondsw_ has joined #openstack-meeting12:55
*** Guest28813 has quit IRC12:55
*** mriedem has joined #openstack-meeting12:57
*** edmondsw has quit IRC12:58
*** verdurin has joined #openstack-meeting12:58
*** verdurin has quit IRC12:58
*** SerenaFeng has joined #openstack-meeting12:58
*** yamamoto has quit IRC12:59
*** alexchadin has quit IRC13:01
*** diman has quit IRC13:01
*** markstur has joined #openstack-meeting13:01
*** artom has quit IRC13:01
*** rossella_s has quit IRC13:05
*** mjturek has joined #openstack-meeting13:05
*** browny_ has quit IRC13:06
*** markstur has quit IRC13:06
*** anilvenkata has quit IRC13:06
*** alexchadin has joined #openstack-meeting13:06
*** rossella_s has joined #openstack-meeting13:07
*** browny_ has joined #openstack-meeting13:08
*** dustins has joined #openstack-meeting13:09
*** yamamoto has joined #openstack-meeting13:10
*** HeOS has quit IRC13:10
*** rbudden has joined #openstack-meeting13:10
*** HeOS has joined #openstack-meeting13:10
*** browny_ has quit IRC13:13
*** yamamoto has quit IRC13:15
*** rossella_s has quit IRC13:15
*** rossella_s has joined #openstack-meeting13:17
*** Tom-Tom has joined #openstack-meeting13:19
*** rbudden has quit IRC13:20
*** rossella_s has quit IRC13:22
*** markstur has joined #openstack-meeting13:23
*** anilvenkata has joined #openstack-meeting13:23
*** rossella_s has joined #openstack-meeting13:23
*** felipemonteiro_ has joined #openstack-meeting13:23
*** yamamoto has joined #openstack-meeting13:25
*** e0ne has quit IRC13:25
*** eharney has joined #openstack-meeting13:25
*** browny_ has joined #openstack-meeting13:25
*** browny_ has quit IRC13:25
*** browny_ has joined #openstack-meeting13:26
*** edmondsw_ is now known as edmondsw13:27
*** markstur has quit IRC13:27
*** pchavva has quit IRC13:29
*** jamesmca_ has joined #openstack-meeting13:29
*** yamamoto has quit IRC13:29
*** sidx64 has quit IRC13:31
*** pchavva has joined #openstack-meeting13:32
*** egallen has joined #openstack-meeting13:32
*** sidx64 has joined #openstack-meeting13:32
*** yamamoto has joined #openstack-meeting13:40
*** singlethink has joined #openstack-meeting13:41
*** SerenaFeng has quit IRC13:41
*** yamamoto has quit IRC13:44
*** sridharg has quit IRC13:44
*** salv-orlando has joined #openstack-meeting13:45
*** Zames has joined #openstack-meeting13:46
*** awaugama has joined #openstack-meeting13:46
*** rossella_s has quit IRC13:47
*** salv-orlando has quit IRC13:50
*** jdandrea has joined #openstack-meeting13:50
*** rossella_s has joined #openstack-meeting13:51
*** felipemonteiro_ has quit IRC13:51
*** kiennt26 has joined #openstack-meeting13:52
*** zhongjun has joined #openstack-meeting13:53
*** Zames has quit IRC13:54
*** yamamoto has joined #openstack-meeting13:54
*** yamamoto has quit IRC13:55
*** yamamoto has joined #openstack-meeting13:55
*** yamamoto has quit IRC13:55
*** jamesmca_ is now known as jamesmcarthur_13:56
*** sridharg has joined #openstack-meeting13:57
*** esberglu has joined #openstack-meeting14:00
*** shaohe_feng has quit IRC14:04
mugsie#startmeeting Designate14:04
openstackMeeting started Wed Mar 14 14:04:39 2018 UTC and is due to finish in 60 minutes.  The chair is mugsie. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:04
*** openstack changes topic to " (Meeting topic: Designate)"14:04
openstackThe meeting name has been set to 'designate'14:04
mugsie#topic Roll Call14:04
*** openstack changes topic to "Roll Call (Meeting topic: Designate)"14:04
*** markstur has joined #openstack-meeting14:05
mugsieping frickler diman simon-AS559 bnemec browny14:05
mugsiemorning :)14:06
mugsiediman is online filing bugs, but doesn't seem to be in IRC14:07
mugsielooks like a quiet meeting then - no new bugs (apart from the TXT / SPF bug we talked about last week), and no potential backports14:08
mugsieany non agenda items?14:09
mugsieSeen last week was really busy, this week is taking the hit :D14:09
*** markstur has quit IRC14:09
*** neiljerram has joined #openstack-meeting14:10
*** sidx64 has quit IRC14:10
*** hyunsikyang has quit IRC14:11
*** aagate has joined #openstack-meeting14:11
*** bobh has joined #openstack-meeting14:11
mugsieok then, back to work it is :)14:12
*** openstack changes topic to "OpenStack Meetings ||"14:12
openstackMeeting ended Wed Mar 14 14:12:24 2018 UTC.  Information about MeetBot at . (v 0.1.4)14:12
openstackMinutes (text):
*** rbudden has joined #openstack-meeting14:12
*** SerenaFeng has joined #openstack-meeting14:12
*** sidx64 has joined #openstack-meeting14:14
*** electrofelix has quit IRC14:16
*** gouthamr has quit IRC14:16
*** rossella_s has quit IRC14:19
*** rossella_s has joined #openstack-meeting14:19
*** shaohe_feng has joined #openstack-meeting14:21
*** fnaval has joined #openstack-meeting14:24
*** rossella_s has quit IRC14:26
*** salv-orlando has joined #openstack-meeting14:27
*** rossella_s has joined #openstack-meeting14:30
*** psachin has quit IRC14:30
*** Tom-Tom has quit IRC14:32
*** alexchadin has quit IRC14:32
*** Tom-Tom has joined #openstack-meeting14:32
*** Tom-Tom has quit IRC14:37
*** browny_ has quit IRC14:38
*** Patifa has quit IRC14:43
*** browny_ has joined #openstack-meeting14:46
*** felipemonteiro_ has joined #openstack-meeting14:49
*** ansmith has joined #openstack-meeting14:50
*** dkehn has joined #openstack-meeting14:50
*** felipemonteiro__ has joined #openstack-meeting14:51
*** browny_ has quit IRC14:51
*** shaohe_feng has quit IRC14:52
*** artom has joined #openstack-meeting14:54
*** felipemonteiro_ has quit IRC14:55
*** dkehn has left #openstack-meeting14:55
*** yamamoto has joined #openstack-meeting14:55
*** hongbin has joined #openstack-meeting14:55
*** marie has joined #openstack-meeting14:56
*** avankemp_ has joined #openstack-meeting14:57
*** e0ne has joined #openstack-meeting14:58
*** chyka has joined #openstack-meeting14:59
*** parus has joined #openstack-meeting15:00
*** ad_ri3n_ has joined #openstack-meeting15:01
*** dpertin has joined #openstack-meeting15:01
ad_ri3n_Hi… sorry for being late15:01
* jdandrea waves hello15:02
*** yamamoto has quit IRC15:02
ad_ri3n_#startmeeting fog-edge-massively-distributed-clouds15:02
ad_ri3n_#chair  ad_ri3n_15:02
openstackMeeting started Wed Mar 14 15:02:58 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:03
*** openstack changes topic to " (Meeting topic: fog-edge-massively-distributed-clouds)"15:03
openstackThe meeting name has been set to 'fog_edge_massively_distributed_clouds'15:03
openstackCurrent chairs: ad_ri3n_15:03
ad_ri3n_#topic roll call15:03
ad_ri3n_Hi guys15:03
*** openstack changes topic to "roll call (Meeting topic: fog-edge-massively-distributed-clouds)"15:03
ad_ri3n_sorry for being late… I was brainstorming on OpenStack (as usual ;))15:03
ad_ri3n_so it seems that there is a couple of folks15:03
ad_ri3n_great !15:03
ad_ri3n_#info agenda15:03
ad_ri3n_#link line 260 Agenda15:03
ad_ri3n_Please put your (nick)name in the etherpad15:04
*** msimonin has joined #openstack-meeting15:04
ad_ri3n_arg.. wrong link15:04
ad_ri3n_@dpertin can you please copy/paste15:04
*** numans_ has joined #openstack-meeting15:04
ad_ri3n_thanks knikolla15:04
parusUS changed to summer time last week-end.... Lots of schedule confusion this side of the Atlantic.15:04
ad_ri3n_So there is a couple of new folks15:05
*** fzdarsky has quit IRC15:05
ad_ri3n_maybe we can take a few minutes to introduce them15:05
*** numans has quit IRC15:05
ad_ri3n_knikolla: jdandrea ?15:05
ad_ri3n_could you please introduce briefly yourself?15:05
*** SerenaFeng has quit IRC15:06
knikollao/ hi all. I'm Kristi. keystone core and leading the resource federation efforts at the Mass Open Cloud.
ad_ri3n_great to see you there knikolla15:07
jdandreaCertainly. Joe D'Andrea, working on all things cloud, previously seen around Heat stuffs.15:07
ad_ri3n_the same jdandrea15:07
ad_ri3n_thank you guys for joining the meeting15:07
jdandreaYou're welcome! Thanks for hosting it.15:07
ad_ri3n_so let's start15:07
ad_ri3n_#topic announcement15:08
*** openstack changes topic to "announcement (Meeting topic: fog-edge-massively-distributed-clouds)"15:08
*** ayoung has quit IRC15:08
ad_ri3n_so you can see the major news in the pad15:08
ad_ri3n_regarding the PTG, we have two sessions with a rather important number of participants15:08
ad_ri3n_during the monday afternoon we went through the expected features we identified previously15:08
ad_ri3n_We got a couple of previous comments and we are currently trying to consolidate all the inputs in a readable/concise document15:09
ad_ri3n_On Tuesday, the openstack foundation join the discussion and we mainly discussed concrete issues ATT is facing15:09
ad_ri3n_This enabled us to move to prototyping discussions regarding keystone and glance15:10
ad_ri3n_regarding keystone, the first discussion focused on the possibility to define roles/… on a region basis15:10
ad_ri3n_i.e. define rights according to each site for each user/project…15:10
ad_ri3n_The idea is to prepare a well described request to se whether this concept of regions/locations can be reified at the level of keystone15:11
ad_ri3n_The second part of the discussion dealt with golden services such as keystone or glance15:11
*** browny_ has joined #openstack-meeting15:11
ad_ri3n_The main idea is to be able to create for instance a new vm image through the golden glance and push the new VMI on a set of identified sites15:12
ad_ri3n_how we are going to implement those concepts has not been discussed yet15:12
msimoninpush = make the image available15:12
*** fzdarsky has joined #openstack-meeting15:13
ad_ri3n_(actually I think this is the major challenge because those new golden services would probably be stateful and thus we may have to deal with inconsistency issues)15:13
ad_ri3n_You can find further informations on the different link I put15:13
ad_ri3n_The second new from my side is related to the Openstack edge sesions but I would like to discuss that point later in the agenda15:13
ad_ri3n_so that's all from my side.15:13
ad_ri3n_Any news guys from your side?15:14
msimoninAs far as I remember the discussion it looked like an active/passive model15:14
msimoninthe golden site was active (admin task can be performed)15:14
ad_ri3n_ansmith:  msimonin do you want to add a few words regarding the presentation in the OSLO session?15:14
msimoninthe other site was passive (usable by the users to start vm  but not for admin tasks)15:14
msimoninother sites*15:14
ad_ri3n_thanks msimonin15:15
msimoninad_ri3n_: I can share some slides15:15
ansmiththe oslo members very much appreciated the update from msimonin on bus analysis15:15
ad_ri3n_yes please c/p the link if you are ok15:15
*** browny_ has quit IRC15:16
ad_ri3n_#link preliminary presentation of the bus analysis15:16
ad_ri3n_anything else?15:17
* jdandrea is perusing the slides (thank you!)15:17
ad_ri3n_maybe we can add that the framework used to perform this experiment is going to presented during the CNERT workshop soon15:17
ad_ri3n_@avankemp_ can you please c/p the link to the workshop15:18
parusMy recollection is that ONAP uses some components of Openstack. is oslo being used by ONAP? does anyone know?15:18
*** links has quit IRC15:18
ad_ri3n_thanks avankemp_15:18
*** pbressan has joined #openstack-meeting15:18
ad_ri3n_parus:  not from my side. AFAIK ONAP only use the OS API15:18
ad_ri3n_s/only use/only uses15:19
ad_ri3n_confirmed by dpertin ;)15:19
jdandreaad_ri3n_ It's possible that oslo components are being used in a few spots. I can check. Possibilities include multicloud due to plugins that interface w/OpenStack.15:19
ansmithONAP defines common services around messaging but not oslo specifically15:19
ad_ri3n_should we go on on that point?15:20
*** ayoung has joined #openstack-meeting15:20
ad_ri3n_jamemcc:  could you please refresh us a bit regarding LCCO WG?15:20
ad_ri3n_jamemcc:  still there?15:21
ad_ri3n_ok so let's start the agenda15:21
ad_ri3n_#topic ongoing-actions OpenStack edge sessions15:22
*** openstack changes topic to "ongoing-actions OpenStack edge sessions (Meeting topic: fog-edge-massively-distributed-clouds)"15:22
jamemcclooked away15:22
*** julim has quit IRC15:22
jamemccI'll update the pad15:22
ad_ri3n_(thanks jamemcc) So we (Parus and I) took part to the meeting this morning15:22
ad_ri3n_two or three additional folks coming from Asia have joined the call.15:23
ad_ri3n_Jonathan briefly summarized the work that has been done so far15:23
ad_ri3n_Prakash gave a couple of new pointers regarding new activities supported by ATT and LF15:24
ad_ri3n_in particular that one:15:24
ad_ri3n_#link https://www.akraino.org15:24
ad_ri3n_I don't know what is behing but unfortunately yet another piece of code to keep an eye on it15:24
ad_ri3n_at the end of the meeting we discussed a bit about the golden service approach.15:25
ad_ri3n_Jonathan will propose to organize a telco dedicated to discuss a bit more this architecture and try to identify possible limitations15:26
ad_ri3n_so let's keep an eye on the edge mailing list15:26
ad_ri3n_that's all from my side on that15:26
ad_ri3n_if there is no question I can switch to the next point?15:26
parusThere was a post on linked in by Kandan about this.15:26
ad_ri3n_thanks parus15:26
ad_ri3n_#topic ongoing-actions P2P/gap analysis15:28
*** openstack changes topic to "ongoing-actions P2P/gap analysis (Meeting topic: fog-edge-massively-distributed-clouds)"15:28
ad_ri3n_Simultaneously of the edge discussions, we are still working with Ericsson folks to better understand the pros/cons of top/down vs bottom/up approaches15:29
ad_ri3n_to develop the resource management system for an edge infrastructure15:29
ad_ri3n_Although the foundation seems to be in favour of a top/down approach15:30
ad_ri3n_we would like to be sure this is the right way to go (actually, I'm even not sure that they ''push'' a top/down approach to be honest. I would rather say that we agreed that a synchronisation mechanism is mandatory to synchronise the different services between the different regions but how this will be done is still unclear as discussed previously)15:31
ad_ri3n_So the goal of this ongoing action is to identify possible ''no go'' issues that prevent either one or the other approach15:32
ad_ri3n_We hope to have a short document (5 pages) to be presented soon.15:32
ad_ri3n_We also arranged an internal meeting next week at Inria to discuss this question.15:32
ad_ri3n_So more news during the next meeting hopefully15:32
*** Tom-Tom has joined #openstack-meeting15:33
*** esberglu has quit IRC15:33
ad_ri3n_ok so let's move to the next point15:33
ad_ri3n_#topic ongoing-actions keystone backend15:34
*** openstack changes topic to "ongoing-actions keystone backend (Meeting topic: fog-edge-massively-distributed-clouds)"15:34
*** kgiusti has joined #openstack-meeting15:34
ad_ri3n_is absent for a couple of days. @marie, who is an internship in our group work with rcherrueau and will update us about the current work15:34
*** felipemonteiro__ has quit IRC15:34
ad_ri3n_@marie the floor is yours  ;)15:34
mariehi :)15:35
*** felipemonteiro__ has joined #openstack-meeting15:35
ad_ri3n_so the goal is to compare from the performance viewpoint several approaches to share state accross distinct sites15:36
mariewe are testing different type of deployments for Keystone15:37
*** Tom-Tom has quit IRC15:38
mariewith a common authentication, either with one centralized Keystone or a Keystone on each region with a common state15:38
marieand also later wih a federated Keystone15:38
ad_ri3n_are you considering the federated approach15:39
ad_ri3n_ok… too late ;)15:39
ad_ri3n_knikolla:  did you already perform such evaluations from your side?15:39
knikollaad_ri3n_: not yet15:39
ad_ri3n_@marie is your experiment protocol already available or not yet?15:39
marieWe are comparing the performance for Galera and CockroachDB when we are varying the number of nodes and latency15:40
ad_ri3n_it would be great to share it to get feedbacks15:40
msimoninsomething in the performance doc would be a good place15:40
ad_ri3n_knikolla:  is it a possible interest point for keystone core devs?15:40
ad_ri3n_@msimonin +1 ;)15:40
*** browny_ has joined #openstack-meeting15:41
knikollaad_ri3n_: the performance of keystone in a multiregion setup with cockroachdb vs galera?15:41
ad_ri3n_vs federation15:41
ad_ri3n_(cockroach or any other relevant storage backend)15:42
knikollaad_ri3n_: in the case of federation, you will not have a shared database. so the defining factor will be the time it takes to exchange an assertion for a token.15:42
*** lpetrut has quit IRC15:42
knikolla(keystone to keystone federation)15:42
*** sidx64 has quit IRC15:43
ad_ri3n_the question we would like to deal with is: what is the most suited manner to get a logical global view of a keystone across distinct locations/openstack instances15:43
*** e0ne has quit IRC15:43
ad_ri3n_knikolla:  exactly15:43
ad_ri3n_moreover with the edge context we have to deal with possible network split brain issues15:44
*** aagate has quit IRC15:44
knikollawhich are tricky for databases, but work better when you don't need to share state. in the case of federation.15:44
*** kiennt26 has quit IRC15:45
ad_ri3n_but yes this is exactly the idea (either we replicate states everywhere: galera like manner, or we leverage a keystone to keystone federation or we use a locally aware no/new SQL db such as cockroach)15:45
parusI have a basic question (sorry to derail)15:45
ad_ri3n_so what is your first opinion knikolla : keystone to keystone federation should be more suited for the edge context?15:46
ad_ri3n_(parus please go on, feel free ;))15:46
parusKeystone is used to store user credentials, but also to generate tokens. Those are two very different use cases, When distributing the database, can we separate both types of content?15:46
*** cloudrancher has quit IRC15:46
knikollai probably need to do a lot of background reading for what's being discussed and aimed for here, as this is my first time joining the meeting.15:46
knikollai tend to favor the federation approach, personally. but as i just said above, I need to read more about your requirements.15:47
*** cloudrancher has joined #openstack-meeting15:47
knikollaparus: i would say you can.15:47
parusMy question is hinting on : is federation appropriate for User credentials but maybe not for token.15:47
*** esberglu has joined #openstack-meeting15:48
ad_ri3n_I was just wondering what was the current choice for the federation efforts.15:48
*** hemna_ has joined #openstack-meeting15:48
ad_ri3n_knikolla:  any pointer to share regarding current discussions on those federations' related  questions15:49
knikollaad_ri3n_: parus: depends on how you're going to handle authorization (user access to projects)15:50
ad_ri3n_ok maybe you can tell us more next time15:50
ad_ri3n_knikolla:  if you have a link toward a wiki page/some minutes of your brainstorming sessions, It would be great if you can share it.15:50
ad_ri3n_(10 minutes left, sorry we have to move to the next point)15:50
ad_ri3n_#topic ongoing-actions AMQP evaluations15:51
*** openstack changes topic to "ongoing-actions AMQP evaluations (Meeting topic: fog-edge-massively-distributed-clouds)"15:51
ad_ri3n_ansmith:  msimonin: please ?15:51
*** walshh has joined #openstack-meeting15:52
*** diman has joined #openstack-meeting15:52
*** manjeet has joined #openstack-meeting15:52
ad_ri3n_msimonin:  ansmith nothing to add regarding all the crazy work you are doing :-P ?15:52
ansmithnot much to update as kgiusti and msimonin were off last week, starting up again this week15:52
ad_ri3n_ok … next point :D15:53
msimoninyes sorry15:53
msimoninWe're scaling the framework15:53
ad_ri3n_(I was also offline last week … winter vacations here in France for most of us ;))15:53
msimoninThis should be ready soon15:53
* knikolla gotta run to another meeting. feel free to ping me on -keystone or via private message. i'd be happy to answer keystone/federation related questions or forward them to the broader keystone team.15:53
*** gman-tx has joined #openstack-meeting15:53
ad_ri3n_knikolla:  thanks15:53
ad_ri3n_if you have any pointers please feel free to share it thanks15:54
ad_ri3n_Ok thank msimonin15:54
ad_ri3n_#topic open-discussions15:54
*** openstack changes topic to "open-discussions (Meeting topic: fog-edge-massively-distributed-clouds)"15:54
ad_ri3n_4 minutes left15:54
ad_ri3n_so is there any point guys you would like to discuss?15:54
jdandreaNot at this time. Absorbing "all the things."15:55
parusVancouver plans?15:55
paruswho is going?15:55
ad_ri3n_jdandrea:  it would be great if you can share more informations regarding the work you are doing at ATT15:56
ad_ri3n_I saw your emails, in particular the ones regarding the MUSIC project15:56
*** diman has quit IRC15:56
ad_ri3n_but let's keep that for the next time (please feel free to add this to the agenda next time)15:56
jdandreaad_ri3n_ Yes! I am not working directly on music, but a colleague is. It has now been moved under ONAP.15:56
ad_ri3n_@parus yes15:56
jdandreaSounds good.15:56
ad_ri3n_so we are waiting to see which presentations have been selected15:57
ad_ri3n_if everything is ok15:57
ad_ri3n_we should come with a couple of folks from  Inria15:57
parusone of mine has been accepted... so I will be going :-)15:57
ad_ri3n_the other points to discuss is wether we want more than one slots15:57
ad_ri3n_you already received your email ?15:57
ad_ri3n_(fuck… ;) )15:58
parusIt was updated on web site.... no email yet.15:58
ad_ri3n_(maybe this mean none from Inria was accepted)15:58
*** yamamoto has joined #openstack-meeting15:58
* jdandrea crosses fingers for Inria15:58
ad_ri3n_so getting back to my first comment15:58
ad_ri3n_maybe we should ask for more than one slot if we are enough people to come15:58
*** e0ne has joined #openstack-meeting15:58
ad_ri3n_acutally I really would like to dive into details about the possible architecture with the goal of preventing us to reinvent the wheel once again15:59
ad_ri3n_so let's discuss that point next time15:59
ad_ri3n_time to conclude15:59
ad_ri3n_thanks guys for joining the meeting15:59
ad_ri3n_let's keep in touch on the pad or through the different MLs.15:59
*** abishop has joined #openstack-meeting15:59
ad_ri3n_#endmeeting 15:59
*** openstack changes topic to "OpenStack Meetings ||"15:59
openstackMeeting ended Wed Mar 14 15:59:37 2018 UTC.  Information about MeetBot at . (v 0.1.4)15:59
openstackMinutes (text):
*** parus has left #openstack-meeting15:59
jungleboyj#startmeeting cinder16:00
openstackMeeting started Wed Mar 14 16:00:01 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
*** marie has left #openstack-meeting16: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
*** pbressan has quit IRC16:00
_pewp_jungleboyj ( ・_・)ノ16:00
*** arnewiebalck_ has joined #openstack-meeting16:00
_pewp_jungleboyj (╯°□°)╯︵ ┻━┻ ︵ ╯(°□° ╯)16:00
*** msimonin has left #openstack-meeting16:00
*** ad_ri3n_ has left #openstack-meeting16:00
jungleboyjwalshh:  Welcome!16:00
jungleboyjHas the snow melted yet?16:01
*** felipemonteiro_ has joined #openstack-meeting16:01
walshhyes it has, back to 10 celsius again16:01
* jungleboyj shakes my head16:01
*** manjeets_ has joined #openstack-meeting16:01
*** dpertin has quit IRC16:01
jungleboyjCertainly timed that wrong.16:01
*** SerenaFeng has joined #openstack-meeting16:01
*** jdandrea has left #openstack-meeting16:02
DuncanTjungleboyj: Still a few traces around Dublin airport yesterday16:02
geguileohi o/16:02
amitohello o/16:02
jungleboyjDuncanT:  Interesting.  Still knee deep in my front yard here.  Should get some melting this week though.16:02
*** felipemonteiro_ has quit IRC16:02
walshhWe may have more for St. Patricks day!!!!16:02
*** avankemp_ has quit IRC16:02
jungleboyjwalshh: Well, the bars better stock up on beer and food then.16:02
jungleboyjOk, looks like we have a decent number here.  Lets get started.16:03
*** yamahata has joined #openstack-meeting16:03
jungleboyj#topic announcements16:03
*** openstack changes topic to "announcements (Meeting topic: cinder)"16:03
*** felipemonteiro_ has joined #openstack-meeting16:03
jungleboyjSo, I have started targeting patches as we discussed at the PTG.16:03
*** yamamoto has quit IRC16:04
jungleboyjI am using the format 'target-rocky-<milestone number>'16:04
jungleboyjIf you have a patch you are submitting that you feel should be targetted, please add it.16:04
* jungleboyj marks smcginnis tardy16:04
*** kgiusti has left #openstack-meeting16:04
jungleboyjCore reviewers, please add the tag where appropriate.16:04
*** felipemonteiro__ has quit IRC16:04
*** dougsz has joined #openstack-meeting16:05
*** manjeet has quit IRC16:05
jungleboyjYou can then search for target-rocky- comments and get a start on review priorities.16:05
jungleboyjI have also added notes to our 'Contributor Guide' on how to use the tag.  I think that patch merged.16:05
*** dougsz has left #openstack-meeting16:05
jungleboyjNo, it didn't.  Need review.
*** felipemonteiro__ has joined #openstack-meeting16:06
*** Tom-Tom has joined #openstack-meeting16:06
jungleboyjNext announcement is that we have started our move to Storyboard ... in a small way.16:07
jungleboyjA test migration for os-brick has been run:16:07
amitoouch, self-signed cert?16:07
eharneywill the official location of os-brick when it's done for real be "/23"?16:07
jungleboyjI haven't looked through the full result and how it maps from Launchpad to Storyboard but I would encourage everyone to take a look at that result and make sure it looks good.16:08
jungleboyjIt is also a place for us to start familiarizing ourselves with it.16:08
jungleboyjamito:  This is just a development location that infra was nice enough to set up for us.  Not the final location.16:08
jungleboyjeharney:  I am not sure about that.16:08
smcginnisI think it may change when imported into the official instance.16:09
jungleboyjsmcginnis:  That is my thought too.16:09
*** felipemonteiro_ has quit IRC16:09
jungleboyjsmcginnis:  Actually no, other ones that are out in use that format:!/project_group/7316:10
geguileothat's quite bad  :-(16:10
jungleboyjSuppose we could open an item on that and see if it can be fixed?16:10
*** masber has quit IRC16:10
*** gman-tx has quit IRC16:10
jungleboyjdiablo_rojo:  diablo_rojo_phon ^^^16:10
*** lhx_ has quit IRC16:10
eharneyyeah, having random numbers in the url instead of a name is terrible16:11
*** Tom-Tom has quit IRC16:11
jungleboyjI will follow up on that question.16:11
e0neeharney: +116:11
eharneywill this handle bugs that span multiple projects?16:12
jungleboyjeharney:  Yes.16:12
jungleboyjsmcginnis:  Was asking about that yesterday I believe.16:12
smcginnisWhy is our number bad?16:13
*** gman-tx has joined #openstack-meeting16:13
*** dprince has quit IRC16:13
jungleboyjsmcginnis:  I think the comment is more that it is numerical.  You can't do
smcginnisCould probably request aliases, but that's just how storyboard works. Each group has a number.16:14
*** browny_ has quit IRC16:14
eharneyyeah... odd16:14
smcginnisSwanson: Could see if /24 is taken. Then it would be even. :P16:14
_pewp_jungleboyj (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. )16:14
* jungleboyj hates odd numbers16:14
smcginnisAt least it's a prime.16:15
Swansonsmcginnis, If /24 isn't taken up my a dummy Kiefer Sutherland page I don't know what you're doing.16:15
jungleboyjSo, please take a look at the os-brick migration.  If there are questions or concerns please raise them so we can't make an informed decision about moving os-brick in the next few weeks.16:16
*** diman has joined #openstack-meeting16:16
jungleboyj:-)  / 24 ...16:16
eharneyi think the import didn't work right with large blocks of text16:16
eharneycompare!/story/1754303 to launchpad16:16
* jungleboyj pictures Keifer riding our Cinder horse.16:16
eharneyit's missing line breaks and therefore unreadable?16:16
jungleboyjYeah, that isn't good.16:17
smcginnisOh yeah, that's not good.16:17
*** manjeets_ is now known as manjeet16:17
eharneyat least part of it is... in bold16:17
eharneyi guess **kwargs got markdown'd16:17
jungleboyjWe should open a story for that.16:18
*** radeks has quit IRC16:18
persiaYes.  LP interprets things as text by default, Storyboard interprets things as markdown by default.  The importer could presumably block things, if that seems better.16:18
jungleboyj#action jungleboyj to open a story to address missing newlines in stories migrated.16:18
jungleboyjHi persia ...16:18
*** kopecmartin_ has quit IRC16:18
jungleboyjpersia:  Can it fix the missing newlines in traceback output, etc?16:19
persiajungleboyj: Theoretically, it can do anything.  Creating a parser that comprehends tracebacks and does the right markdown thing may be a challenge.16:20
eharneyare all new bug reports going to be written in markdown?16:20
*** felipemonteiro__ has quit IRC16:20
geguileothat will be problematic for sure16:20
eharneyer, "story" reports?16:20
*** diman has quit IRC16:21
jungleboyjOk, so we should get a story opened for this as when it comes to migrating Cinder, Nova, etc.  That is going to be an issue.16:21
eharneymigration is not that hard, you can just shove all imported fields into a markdown plain-text block etc...16:21
jungleboyjstory == bug ??? novel16:21
eharneybut what happens for people filing bug reports expecting it to be plain text like every other bug tracker?16:21
*** manjeets_ has joined #openstack-meeting16:21
*** fzdarsky has quit IRC16:21
persiaeharney: There is a "preview" button during story creation that may help with that, but yeah, it is a transition.16:22
smcginnisYeah, seems like a good idea that maybe wasn't fully thought through for implications.16:22
jungleboyjSo, I don't want to get wrapped around the axel on this today.16:23
*** erlon has joined #openstack-meeting16:23
*** Tom-Tom has joined #openstack-meeting16:23
geguileoIs there no way to set the default to text instead of markdown?16:23
persiajungleboyj: If you create stories about problems with migration, please add the "blocking-storyboard-migration" tag to make them easy to find.16:24
*** manjeet has quit IRC16:24
jungleboyjI will get a bug opened.  Please take a look at what is out there and put together concerns and we can raise them to the storyboard team.16:24
jungleboyjpersia:  Cool.  Will do.16:24
*** cloudrancher has quit IRC16:25
SotK at least fixes the "missing newlines" part :)16:25
jungleboyjSotK:  Oh, so that has been resolved?16:25
*** rossella_s has quit IRC16:26
*** cloudrancher has joined #openstack-meeting16:26
SotKsomewhat yes16:26
jungleboyjI will have diablo_rojo or fungi  Rerun the os-brick test migration after that has merged then.16:26
eharneythe imports will still be a mess due to ** being translated to bold16:26
SotKthat patch at least makes pasted logs mostly readable, but as eharney says there are other issues it doesn't address16:26
*** tpsilva has joined #openstack-meeting16:27
DuncanTJIRA does non-standard markdown parsing, and it's a giant pain in the proverbial16:27
SotKjungleboyj: you won't need to re-run the migration, the text is rendered by the webclient when its viewed16:27
jungleboyjSotK:  Oh, interesting.  Ok.16:27
smcginnisDuncanT: Not just their parsing. :)16:27
DuncanTsmcginnis: No, but it is one (of many) annoyances that we should possibly not copy16:28
*** manjeets_ has quit IRC16:28
jungleboyjAnyway, this will be an ongoing discussion and transition.  We ahve a lot more to talk about so I would like to move on.16:28
smcginnisDuncanT: Very true.16:28
*** Tom-Tom has quit IRC16:28
smcginnisjungleboyj: ++16:28
jungleboyj#topic Rocky Priorities Review16:28
*** openstack changes topic to "Rocky Priorities Review (Meeting topic: cinder)"16:28
*** rossella_s has joined #openstack-meeting16:29
jungleboyjSo, this is me being more leaderly and annoying.16:29
*** masber has joined #openstack-meeting16:29
*** andreas_s has quit IRC16:29
jungleboyjI have all the info from the PTG in our approved/specs work section here and the specs we are working on approving below.16:29
*** andreas_s has joined #openstack-meeting16:30
jungleboyjPlease add your reviews here as we go.16:30
jungleboyjI don't think we are missing anything at the moment based on the reviews I ahve seen.16:30
jungleboyjI have updated the new drivers at the bottom.16:30
jungleboyjI have targeted them to target-rocky-216:30
jungleboyjThe Lustre driver was removed.  They abandoned it when we talked.16:31
*** PeteC has quit IRC16:31
jungleboyjI am going to be bringing this up weekly and asking about it, so help keep it curated please.16:31
jungleboyjAny comments or concerns on that?16:32
jungleboyj#topic HA development progress16:32
*** openstack changes topic to "HA development progress (Meeting topic: cinder)"16:32
eharneyi suspect generic backup needs spec updates after the PTG, since it was already merged16:32
*** dprince has joined #openstack-meeting16:32
jungleboyjgeguileo:   We talked about the fact we would touch on this weekly to keep it moving along.16:33
*** SerenaFe_ has joined #openstack-meeting16:33
jungleboyjgeguileo:  Any progress with HA documentation development, etc?16:33
geguileojungleboyj: not really  :-(16:33
geguileoI'll try to get something started on the documentation16:33
geguileothis week16:33
jungleboyjgeguileo:  Ok, sounds good.16:34
jungleboyjeharney:  Good point.  Should take a look at that spec again and make sure it is still accurate.16:34
jungleboyje0ne:  ?16:34
eharneyit needs a lot of details added based on the discussion we had at PTG afaict16:34
e0neeharney, jungleboyj: I'll update both a  spec  and a patch early next week16:35
jungleboyjPaging e0ne  ... Dr. e0ne  to openstack-meeting stat16:35
*** SerenaFeng has quit IRC16:35
jungleboyj#action e0ne to update the spec and associated patch(es) .16:35
jungleboyjeharney: e0ne  Thank you.16:36
e0nejungleboyj: np16:36
jungleboyjAny other comments on those general topics?16:36
jungleboyj#topic On-boarding session in Vancouver.16:37
*** openstack changes topic to "On-boarding session in Vancouver. (Meeting topic: cinder)"16:37
jungleboyjWe will be doing this again for Cinder.16:37
jungleboyjHope to have it co-scheduled with our project update.16:37
jungleboyjI have asked for a double (80 minute) session as we have fully used the time in the past.16:37
jungleboyjWill see what happens.16:37
jungleboyjIs there anyone will/able to co-present with me?16:38
*** dustins has quit IRC16:38
*** diman has joined #openstack-meeting16:38
jungleboyjLet me know if you are.  Just want to make people aware of this now.16:38
smcginnisjungleboyj: So you're thinking having an update followed immediately by onboarding?16:38
jungleboyjsmcginnis:  Yeah, that is an idea we have had to try to draw more people in.16:39
smcginnisjungleboyj: I wonder how much of an overlap there actually is between those audiences.16:39
jungleboyjGive the project update.  You have people there and let them know what you are doing next ... onboarding.  Hope you might get a few more people to stick around.16:39
jungleboyjsmcginnis:  Good question.16:39
smcginnisYeah, might be a way to pick up a few extra people maybe.16:39
jungleboyjsmcginnis:  Think it is worth a try.16:39
smcginnisjungleboyj: It at least makes it easier for you as presenter, so there's at least that. ;)16:40
jungleboyj:-)  Until my voice dies.16:40
jungleboyj#topic forum topic proposals16:41
*** openstack changes topic to "forum topic proposals (Meeting topic: cinder)"16:41
*** browny_ has joined #openstack-meeting16:41
*** arxcruz is now known as arxcruz|off16:42
jungleboyjI have started our etherpad.  We need to official submit topics in a week or two.16:42
*** yamahata has quit IRC16:42
jungleboyjPlease add topics that might be appropriate for the forum.16:42
*** diman has quit IRC16:42
jungleboyjRemembering this is a chance to interact with consumers/operators.16:42
smcginnisThat tempest one might be good to try to get QA involved and have a more general cross-project discussion.16:42
smcginnisBut still good if it's just Cinder.16:42
jungleboyjsmcginnis:  ++16:43
e0nesmcginnis: +116:44
jungleboyj#action Team to add topic ideas16:44
*** masber has quit IRC16:44
jungleboyjOk, final topic.16:44
jungleboyj#topic Policy checking conerns.16:44
*** openstack changes topic to "Policy checking conerns. (Meeting topic: cinder)"16:44
jungleboyjWe have a bug:16:44
*** mjturek has quit IRC16:45
openstackLaunchpad bug 1714858 in Cinder "Some APIs doesn't check the owner policy" [Critical,In progress] - Assigned to TommyLike (hu-husheng)16:45
jungleboyjand a proposed patch16:45
*** mjturek has joined #openstack-meeting16:45
*** browny_ has quit IRC16:45
jungleboyjeharney:  Has concerns about the security aspect of this bug and the fact that no one really fully understands it or how to resolve it.16:45
jungleboyjWe need to address this and figure out how we move forward.16:46
jungleboyjtommylikehu: Thoughts?16:46
tommylikehuI think the thing that we are not sure about this is how many APIs are affected16:46
tommylikehuand which one is really have security issue16:46
*** janki has quit IRC16:47
e0netommylikehu: you we have a list of affected APIs now?16:47
e0ne*do we have16:47
tommylikehue0ne:  all I found are in the patches16:48
*** andreas_s has quit IRC16:48
jungleboyjIs there any way to ensure that we have found all the places where we have an issue?16:49
tommylikehuI agree with smcginnis we can fix this progressively and maybe that's the reason eharney  pointed it out I should remove the close bug tag.16:49
jungleboyjtommylikehu:  ++16:49
jungleboyjI would like to start getting patches for this in.16:49
smcginnisI'd rather see most cases fixed now, and we can watch for other instances going forwarded.16:49
*** andreas_s has joined #openstack-meeting16:50
jungleboyjMake it a Partial-Bug and then continue to fix isses as we find them.16:50
jungleboyjsmcginnis:  ++16:50
eharneyfixing it progressively is maybe ok, if we know the full list of issues... but we, at some point, have to be able to write a statement of what the impact is on people who deployed this code16:50
smcginnisjungleboyj: That sounds good. And maybe add notes to the bug that we've addressed the list of calls we found in the one patch and note that we are just not sure all cases are addressed.16:50
*** masber has joined #openstack-meeting16:51
smcginnisIf we go a year or something without seeing any more, then we can just close the bug with a note saying we think it's addressed and new bugs will be filed if we find any more cases.16:51
tommylikehujungleboyj: it's more complicated than we thought as some of the API resource or part of the policy enforcement code do not need this change because they can not have owner policys.16:51
eharneythe commit message calls out an issue with reset_status but doesn't really explain what it is16:51
*** SerenaFe_ has quit IRC16:52
tommylikehueharney:  the issue for that one is I can reset any volume's status if the corrsponding policy has been changed into admin_or_owner16:52
jungleboyjtommylikehu:  That is fixed with the patch?16:53
eharneythen that info needs to be provided in the bug for an ossa/ossn, even if it's a lower priority vulnerability16:53
geguileotommylikehu: can you really change it? won't the get method fail based on the project/user filtering on the DB?16:53
*** radeks has joined #openstack-meeting16:54
tommylikehugeguileo:  where16:54
geguileotommylikehu: don't we do a get of the volume?16:54
*** andreas_s has quit IRC16:54
tommylikehujungleboyj:  I guess so.16:54
* jungleboyj would like a more confident response.16:55
jungleboyjThat seems like a problem that we need to get fixed.16:55
*** marios has quit IRC16:56
eharneyso, we're now at about two weeks of a public security bug report for this16:56
eharneywe need to really close in on describing the problem adequately at least16:56
jungleboyjeharney:  ++16:57
jungleboyjWe only have 3 minutes left here.16:57
jungleboyjCan we at least agree on a plan going forward in that time?16:57
*** iyamahat has joined #openstack-meeting16:57
jungleboyjI agree with getting the patch that is out there merged with it marked as 'Partial-Bug;.16:58
tommylikehuI should update the commit message and the bug fix tag before going forward?16:58
jungleboyjtommylikehu:  Yes.16:58
*** iyamahat has quit IRC16:58
eharneywhat about the whole claim that some issues predated the changes in queens?  i'm not sure if we should merge the current patch without understanding that part too16:58
jungleboyjI also think we need to be confident that the reset status problem is fixed.16:59
eharneyand that it's the only one...16:59
*** yamamoto has joined #openstack-meeting16:59
*** hyunsikyang has joined #openstack-meeting16:59
*** iyamahat has joined #openstack-meeting16:59
eharneysnapshot reset state didn't have a similar issue?17:00
jungleboyjWe are out of time.  Lets take this over to the Cinder channel while we have tommylikehu17:00
jungleboyjThanks everyone for a good meeting and for your work on Cinder!17:00
*** openstack changes topic to "OpenStack Meetings ||"17:00
openstackMeeting ended Wed Mar 14 17:00:43 2018 UTC.  Information about MeetBot at . (v 0.1.4)17:00
openstackMinutes (text):
*** sapd_ has joined #openstack-meeting17:01
*** markstur has joined #openstack-meeting17:02
*** Tom-Tom has joined #openstack-meeting17:03
*** abishop has left #openstack-meeting17:04
*** sapd has quit IRC17:05
*** yamamoto has quit IRC17:05
*** radeks has quit IRC17:06
*** julim has joined #openstack-meeting17:06
*** radeks has joined #openstack-meeting17:07
*** Tom-Tom has quit IRC17:08
*** markstur has quit IRC17:08
*** radeks has quit IRC17:08
*** radek_ has joined #openstack-meeting17:09
*** radek_ has quit IRC17:10
*** walshh has quit IRC17:10
*** radeks has joined #openstack-meeting17:10
*** rosmaita has left #openstack-meeting17:10
*** markstur has joined #openstack-meeting17:13
*** claudiub has joined #openstack-meeting17:14
*** yamahata has joined #openstack-meeting17:15
*** pcaruana has quit IRC17:18
*** markstur has quit IRC17:18
*** e0ne has quit IRC17:20
*** ayoung has quit IRC17:21
*** Swami has joined #openstack-meeting17:25
*** awaugama_ has joined #openstack-meeting17:29
*** rossella_s has quit IRC17:30
*** browny_ has joined #openstack-meeting17:31
*** awaugama has quit IRC17:32
*** jamesmcarthur_ has quit IRC17:32
*** rossella_s has joined #openstack-meeting17:32
*** browny_ has quit IRC17:36
*** jamesmcarthur has joined #openstack-meeting17:36
*** Tom-Tom has joined #openstack-meeting17:37
*** jamesmcarthur has quit IRC17:40
*** Tom-Tom has quit IRC17:41
*** jamesmcarthur has joined #openstack-meeting17:42
*** dustins has joined #openstack-meeting17:45
*** awaugama has joined #openstack-meeting17:48
*** tssurya has quit IRC17:48
*** manjeet has joined #openstack-meeting17:50
*** awaugama_ has quit IRC17:50
*** rbowen has joined #openstack-meeting17:51
*** diman has joined #openstack-meeting17:52
*** claudiub|2 has joined #openstack-meeting17:53
*** e0ne has joined #openstack-meeting17:53
*** claudiub has quit IRC17:55
*** diman has quit IRC17:56
*** links has joined #openstack-meeting17:57
*** diman has joined #openstack-meeting17:59
*** yamamoto has joined #openstack-meeting18:01
*** sshank has joined #openstack-meeting18:01
*** diman has quit IRC18:04
*** manjeets_ has joined #openstack-meeting18:05
*** manjeet has quit IRC18:05
*** gyee has joined #openstack-meeting18:05
*** yamamoto has quit IRC18:06
*** sshank has quit IRC18:07
*** diman has joined #openstack-meeting18:08
*** browny_ has joined #openstack-meeting18:10
*** markstur has joined #openstack-meeting18:10
*** harlowja has joined #openstack-meeting18:11
*** arnewiebalck_ has quit IRC18:11
*** cloudrancher has quit IRC18:11
*** cloudrancher has joined #openstack-meeting18:12
*** felipemonteiro_ has joined #openstack-meeting18:12
*** diman has quit IRC18:12
*** browny_ has quit IRC18:14
*** felipemonteiro__ has joined #openstack-meeting18:15
*** e0ne has quit IRC18:16
*** felipemonteiro_ has quit IRC18:19
*** markstur has quit IRC18:19
*** markstur has joined #openstack-meeting18:20
*** dustins_ has joined #openstack-meeting18:24
*** dustins has quit IRC18:24
*** radeks has quit IRC18:24
*** markstur has quit IRC18:26
*** lpetrut has joined #openstack-meeting18:28
*** felipemonteiro__ has quit IRC18:30
*** felipemonteiro__ has joined #openstack-meeting18:30
*** neiljerram has quit IRC18:30
*** browny_ has joined #openstack-meeting18:39
*** kaisers_ has quit IRC18:40
*** kaisers has joined #openstack-meeting18:40
*** browny_ has quit IRC18:44
*** kaisers has quit IRC18:45
*** abalutoiu_ has joined #openstack-meeting18:46
*** abalutoiu__ has joined #openstack-meeting18:47
*** abalutoiu has quit IRC18:48
*** abalutoiu has joined #openstack-meeting18:49
*** abalutoiu_ has quit IRC18:50
*** Tom-Tom has joined #openstack-meeting18:51
*** abalutoiu__ has quit IRC18:52
*** diman has joined #openstack-meeting18:52
*** tobiash has joined #openstack-meeting18:54
*** e0ne has joined #openstack-meeting18:54
*** Tom-Tom has quit IRC18:56
*** diman has quit IRC18:57
*** longkb1 has quit IRC18:57
*** ociuhandu has joined #openstack-meeting18:57
SotK#startmeeting storyboard19:00
openstackMeeting started Wed Mar 14 19:00:27 2018 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: storyboard)"19:00
openstackThe meeting name has been set to 'storyboard'19:00
SotK#link Agenda19:00
diablo_rojoI was just excited for the meeting I wanted to start an hour earlier.19:00
*** salv-orlando has quit IRC19:00
*** salv-orl_ has joined #openstack-meeting19:01
SotKI don't think we have any announcements today19:01
SotK#topic In Progress Work19:01
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)"19:01
diablo_rojoRelease Management migrated?19:01
*** yamamoto has joined #openstack-meeting19:02
*** ociuhandu has quit IRC19:03
diablo_rojoI have the migration script change to handle suspended users in LP up for review.19:03
fungi#link!/project_group/73 release management team project group19:03
SotKI'm glad the migrations seem to be building up a head of steam19:04
diablo_rojoIndeed :)19:04
diablo_rojoGetting attention19:04
persiaI think the more that migrate, the more people get frustrated with not using Storyboard.19:04
SotKwe just need to get that frustration to outweigh the frustration of having to change tools :)19:05
diablo_rojoEither way, I am happy we are making more and more progress.19:05
SotKme too19:05
*** manjeets_ is now known as manjeets_lp19:05
*** egallen has quit IRC19:05
diablo_rojoSo in progress work? I have the migration script change and one small webclient change to make VMT/ Security things more verbose19:06
diablo_rojoWould love some reviews :)19:06
SotKI sent a big wall of patches at PTG, most of which are making the UI feel nicer to me in various ways, but some of which address actual issues other people have raised19:06
SotKdiablo_rojo: I'll try to find some time to review things soon, I've been busy with various things since PTG so far19:07
persiaThe name vs. number and new lines in markdown issues came up in the cinder meeting.  Both have patches needing reviews.19:07
*** yamamoto has quit IRC19:07
diablo_rojoSotK, I think I have reviewed basically all of them, but will double check. I know there are a lot of things sitting in storyboard with one +2 on them.19:07
diablo_rojoSotK, no worries.19:07
*** salv-orl_ has quit IRC19:08
SotKpersia: I noticed that discussion, that also made me think that I should send a similar name vs number patch for project groups19:08
*** salv-orlando has joined #openstack-meeting19:08
diablo_rojoI will go through storyboard + webclient today and make sure everything I havent already looked at gets some attention before I go do anything else.19:08
persiaSotK: good idea19:08
fungiwhen creating a new project group it prompts for a "url stub" but it's not entirely apprent to me what that gets used for19:09
SotKfungi: off the top of my head I also have no memory of what that is used for19:10
persiaI think that might have been an incomplete feature to do project group overviews, mostly abandoned before the last DtoryBoard meeting in Vancouver.19:10
*** andreas_s has joined #openstack-meeting19:11
diablo_rojoSo something we could remove then?19:11
persiaI think if StoryBoard is part of a bigger thing (like OpenStack Infra or Software Factory), it could be removed.19:11
persiaI have not heard of anyone trying to build a do-everything system with StoryBoard as central in several years, so I think so.19:12
*** markstur has joined #openstack-meeting19:12
persiaIf someone is doing that, they should be more visible :)19:12
SotKif that is the case I agree we should remove it19:13
SotKif anyone is secretly vehemently opposed to that they can complain19:13
diablo_rojoOther ongoing things, fungi how is the investigation about why gerrit stopped posting links on stories?19:14
fungii just didn't know whether the url stub it was an incomplete solution to human-readable project group names19:14
*** kaisers has joined #openstack-meeting19:15
persiaI could misremember.  We should check the code before removing:)19:15
fungidiablo_rojo: best hope at the moment is that the reason its-storyboard stopped commenting on stories is related to changes we may have made to the commentlinks settings in gerrit around the time we upgraded to 2.13, or that the its-base framework changed what it expects out of those commentlinks/gerrit configuration in general19:16
fungii haven't had time to test that hypothesis yet19:16
diablo_rojoNo worries :) Just wondered if there were updates.19:16
*** tssurya has joined #openstack-meeting19:17
fungiworse reasons may include regressions in gerrit or its-base between 2.11 and 2.1319:17
fungiwhich is likely going to require deeper grokking of java than i can manage19:17
diablo_rojo*fingers crossed its not that*19:17
*** markstur has quit IRC19:17
fungiyeah, tell me about it19:17
fungii also haven't had time to do the utf8mb4 table conversions on storyboard-dev yet19:18
diablo_rojoI suppose we will cross that bridge if we get to it.19:18
*** salv-orl_ has joined #openstack-meeting19:18
fungito make sure i have the process down for subsequently doing the same on production19:18
diablo_rojofungi, its okay- the main reason for that is a few projects have users with emojis in their names19:18
fungii'd like to couple those with moves to newer mysql versions for the trove instances we're using19:19
SotKyep, I'm sure we can find a Java fan somewhere if we have to19:19
diablo_rojoso we need to support it to migrate them or handle them some other way19:19
*** salv-orlando has quit IRC19:19
diablo_rojoBut we have plenty of other projects to handle migrating right now :)19:19
SotKI think that brings us nicely to the next topic19:19
SotK#topic Migration Updates19:20
*** openstack changes topic to "Migration Updates (Meeting topic: storyboard)"19:20
*** esberglu has quit IRC19:20
diablo_rojoIronic has been test migrated.19:20
*** tesseract has quit IRC19:20
diablo_rojoMigration will be announced at their meeting Monday for the following week I think.19:21
*** browny_ has joined #openstack-meeting19:21
diablo_rojoI am so excited to migrate them I can hardly stand it :)19:21
*** Tom-Tom has joined #openstack-meeting19:21
diablo_rojoManila also just finished migrating locally without issue so I will let tbarron know and he can decide how/when they want to proceed as well.19:21
SotKyeah, it is very exciting19:21
SotKI guess we probably want to get the "click this box for security bugs too" patch merged before then?19:22
fungii've already +2'd it19:22
diablo_rojoYeah that would be great19:22
diablo_rojoCause then Glance would be onboard to go too19:23
*** esberglu has joined #openstack-meeting19:23
SotKassuming they are happy trusting that people can follow clear instructions rather than the team automatically being added I guess19:23
fungion a related note, i'm working on drafting the zuul team's vulnerability management process, from which the storyboard specifics will likely inform the openstack vmt's support of projects using sb for their task tracking as well19:23
fungiand we'll have some nice boilerplate prose explaining to users how to properly report suspected security vulnerbailities19:24
diablo_rojoSotK, talked to the ex-PTL yesterday and he seemed to think it should be fine- will verify with the current PTL though19:24
diablo_rojofungi, that will be SUPER handy19:24
SotKfungi: that sounds good :)19:25
*** andreas_s has quit IRC19:25
SotKdiablo_rojo: oh, nice19:25
persiaProbably still worth being able to configure per-project-group security teams, but maybe at lower priority.19:26
diablo_rojoI was in like 10 channels talking storyboard over the last two days19:26
*** browny_ has quit IRC19:26
diablo_rojopersia, yeah each team will want to set up their own $project coresec group19:26
fungiyeah, i mean we _can_ configure per-project-group security teams now19:26
fungiit just requires them to get a storyboard admin to do that for them19:26
*** Tom-Tom has quit IRC19:26
SotKpersia: yep, I definitely agree19:26
SotKbut "good enough" is a good place to start19:27
diablo_rojofungi, you were talking yesterday about that being something we could maybe define in project config and get imported into storyboard that way?19:27
fungiwhich is not entirely ideal, but we have time to come up with some sort of automation for that before our sb admins are overrun with sb team change requests19:27
persiaOh, I missed that.  Is it just the UI integration that is missing?19:27
diablo_rojoSo it doesn't have to be done by admins19:27
fungiyeah, i was thinking just a piece of automation using an administrative-privilege account which queries the api for groups, compares them to a set of files in a git repo, and then adjusts the groups in sb to match19:28
fungier, s/groups/teams/19:28
diablo_rojoThat would be super awesome. Easy way for teams to control changes to the groups without needing us to make changes.19:29
persiaOh, interesting.  I was thinking a config option that would be a default for a security checkbox.19:29
fungioh, gotcha. different needs there right19:29
SotKpersia: me too, I think being able to control team membership is one half of the issue, being able to mark a team as "coresec for $project" is the other half19:30
fungiso making teh default security team choice a per-project-group setting would probably not work19:30
fungiwould need to be per-project i think19:30
fungibecause a single project can be in multiple groups19:30
fungiso it may get confusing if your project belongs to groups with different default securit settings (unless we just merge the default and add them all?)19:31
*** browny_ has joined #openstack-meeting19:31
fungii suppose that's a reasonable alternative as long as everyone (or at least the sb admins) understands how that works19:31
SotKis there a good reason for going per-group rather than per-project?19:33
fungias an alternative to maintaining group membership in revision control and writing some sort of sync-up automation, i wonder if we could add a setting to a team which allowed anyone who is a member of that team to be able to see and modify its membership? that's basically how we treat self-managed teams in gerrit today for access control19:33
*** ricolin has quit IRC19:33
*** sridharg has quit IRC19:33
fungiand probably easier than having team owner accounts which gets into more explicit role-based access control19:33
SotKyeah I think that makes sense to have19:34
*** links has quit IRC19:34
SotKand certainly would be part of any "anyone can make a team and add folk to it" implementation in future anyway19:34
*** egallen has joined #openstack-meeting19:35
*** e0ne has quit IRC19:36
fungifrom a burden-to-the-admins perspective, i think being able to rely on admins to create groups and add an initial member to them is acceptable for now (again, we're doing that with gerrit anyway)19:36
*** browny_ has quit IRC19:36
fungier, s/groups/teams/19:36
fungigerrit calls them groups, so i keep confusing the terms19:36
SotKI will make a story for this stuff after the meeting then19:36
fungifor setting the default subscriber team for a project, i think we can probably manage that through revision control in the same place we put other project settings now (openstack-infra/project-config gerrit/projects.yaml) and just modify our manage-projects script to set that through the sb api (once such a setting exists)19:37
*** Tom-Tom has joined #openstack-meeting19:39
SotKthat seems sensible to me19:39
diablo_rojoThat sounds like a good approach to me19:39
fungiwe already use that today to say what project groups a project should belong to19:40
*** browny_ has joined #openstack-meeting19:41
SotKdiablo_rojo: do we know when sahara and tripleo intend to begin migrating yet ooi?19:41
diablo_rojoSotK, not currently. Reaching out to them to start doing that was on my todo list now that the script change has merged.19:42
*** hemna_ has quit IRC19:43
*** Tom-Tom has quit IRC19:43
*** pchavva has quit IRC19:44
SotKcool, I'm looking forward to it happening19:44
diablo_rojoMe too.19:44
diablo_rojoSo many migrations!19:44
SotKanything else on the migration front?19:45
diablo_rojoDon't think so19:45
SotK#topic Outreachy intern?19:45
*** openstack changes topic to "Outreachy intern? (Meeting topic: storyboard)"19:45
diablo_rojoYeah, so I know there is a call out for intern proposals19:46
diablo_rojoAnd I know we have a lot of work to be done and most of it is small projects.19:46
*** browny_ has quit IRC19:46
diablo_rojoI thought proposing some of the work- unit tests maybe would be a good idea for an internship?19:46
diablo_rojoThe only issue is that we need to commit like 5 hours of mentorship a week.19:46
diablo_rojoWhich is a lot for any one of us to handle.19:47
*** e0ne has joined #openstack-meeting19:48
SotKindeed, I certainly wouldn't want to commit to having 5 hours available myself for mentoring atm19:48
diablo_rojoMe neither.19:48
diablo_rojoBut we could REAALLY use the extra hands on work.19:48
diablo_rojoThere is info about doing like co-mentorship19:49
diablo_rojolike multiple people mentoring the same person19:49
SotKthat sounds more possible19:49
SotKthough most of my free time is at the weekends19:49
*** rbudden has quit IRC19:49
*** browny_ has joined #openstack-meeting19:49
diablo_rojoSotK, yeah and we have no way of knowing what tz the intern would be in19:49
*** salv-orl_ has quit IRC19:50
diablo_rojoweekends might not be an issue19:50
diablo_rojovkmc, around?19:50
*** salv-orlando has joined #openstack-meeting19:50
diablo_rojo(she is organizing outreachy the intern program)19:50
diablo_rojoHey :)19:50
vkmchey :)19:50
diablo_rojoTalking about a possible proposal for outreachy internship19:50
vkmcthat's great!19:51
diablo_rojoSo co-mentoring..19:51
diablo_rojothats cool?19:51
vkmcmain organizers put a deadline on internship ideas proposals19:51
vkmcso... unless the idea is proposed today19:51
vkmcI'm afraid we will need to wait til next round19:51
diablo_rojoCause we have like twoish + people that could all lend a little time, but no specific one that could dedicate 5 hours19:51
vkmcI can help convincing them19:51
diablo_rojoI miiiight be able to get something together- depending on the details needed.19:52
vkmcis there people interested on working on the idea?19:52
*** jamesmcarthur has quit IRC19:52
diablo_rojoLike mentees?19:52
diablo_rojoor mentors?19:52
vkmclike mentees19:52
*** awaugama has quit IRC19:52
vkmcI'm understanding you have an internship idea and mentors19:52
vkmcand that you would like to propose the idea19:52
diablo_rojoAh yeah no prospective mentees currently that I know of19:53
vkmcbut maybe you have people interested already19:53
vkmcoh ok19:53
SotKnone that I am aware of either19:53
vkmcso... we can try to get the idea accepted19:53
vkmcdeadline for applications is 29th March19:53
*** sambetts is now known as sambetts|afk19:53
*** browny_ has quit IRC19:53
vkmc(extended one, the real one is the 22nd March)19:53
*** jamesmcarthur has joined #openstack-meeting19:53
vkmcso we have time for people to apply19:53
*** browny_ has joined #openstack-meeting19:53
diablo_rojoOkay so need a prospective intern for it by then?19:53
*** salv-orlando has quit IRC19:54
*** diman has joined #openstack-meeting19:54
fungigo bang on empty kegs near the local university campuses and see who comes running19:54
diablo_rojoHa ha ha ha19:55
diablo_rojoThanks for the info vkmc :)19:55
diablo_rojoSo based on all of we want to go for it? or wait till next round and maybe try then?19:56
vkmcno need... we can spread the word and cross fingers to get mentees19:56
vkmcthanks to you!19:56
vkmclet me know if I can be of any help19:56
diablo_rojovkmc, I will let you know in a bit if I am throwing together a proposal today :)19:56
diablo_rojoWill do!19:56
SotKdiablo_rojo: feel free to ping me if you decide to try and need any input :)19:57
fungithe up side is any proposal you write up for this round will probably still be mostly viable for the next round too if we don't manage to get one now19:57
fungiso not necessarily wasted effort even if we're turned down or can't find a suitable victim^H^H^H^H^H^Hmentee19:58
diablo_rojoSo sounds like I should try..?19:58
*** diman has quit IRC19:58
diablo_rojoWould you two have an hour or two to donate to comentoriship with me?19:59
SotKif you have time I think it would be good to try19:59
SotKI can find an hour or two, yeah19:59
diablo_rojoOkay cool.19:59
SotKright we are about out of time19:59
diablo_rojoToday turns into a writing day. I already had a super user post I had to write, but I will do this one first :)19:59
SotKif anyone has anything else to chat about, come to #storyboard20:00
SotKdiablo_rojo: thanks!20:00
diablo_rojoLet me start an etherpad and start throwing stuff in- if you both want to help that would be super awesome20:00
SotK#endmeeting storyboard20:00
*** openstack changes topic to "OpenStack Meetings ||"20:00
openstackMeeting ended Wed Mar 14 20:00:25 2018 UTC.  Information about MeetBot at . (v 0.1.4)20:00
diablo_rojoI'll throw it in #storyboard in a sec20:00
openstackMinutes (text):
fungii can try to help, but i have a lot of trouble finding time already20:00
*** tobiash has left #openstack-meeting20:00
*** artom has quit IRC20:01
*** yamamoto has joined #openstack-meeting20:03
*** browny_ has quit IRC20:03
*** yamamoto has quit IRC20:08
*** ayoung has joined #openstack-meeting20:08
*** jamesmcarthur has quit IRC20:09
*** sidx64 has joined #openstack-meeting20:10
*** longkb has quit IRC20:13
*** Tom-Tom has joined #openstack-meeting20:14
*** sidx64 has quit IRC20:15
*** sidx64 has joined #openstack-meeting20:17
*** Tom-Tom has quit IRC20:18
*** jamesmcarthur has joined #openstack-meeting20:27
*** e0ne has quit IRC20:27
*** jamesmca_ has joined #openstack-meeting20:29
*** jamesmcarthur has quit IRC20:29
*** egallen has quit IRC20:29
*** awaugama has joined #openstack-meeting20:35
*** ansmith has quit IRC20:36
*** diman has joined #openstack-meeting20:37
*** diman has quit IRC20:37
*** m_kazuhiro has joined #openstack-meeting20:37
*** diman has joined #openstack-meeting20:37
*** raildo has quit IRC20:38
*** browny_ has joined #openstack-meeting20:39
*** diman has quit IRC20:41
*** salv-orlando has joined #openstack-meeting20:43
*** rbudden has joined #openstack-meeting20:46
*** pchavva has joined #openstack-meeting20:48
*** eharney has quit IRC20:49
*** Tom-Tom has joined #openstack-meeting20:50
*** torgomatic has joined #openstack-meeting20:52
*** esberglu has quit IRC20:52
*** dprince has quit IRC20:52
*** _jbadiapa has joined #openstack-meeting20:54
*** mathiasb has joined #openstack-meeting20:54
*** Tom-Tom has quit IRC20:55
*** esberglu_ has joined #openstack-meeting20:55
*** esberglu_ has quit IRC20:56
*** esberglu_ has joined #openstack-meeting20:56
*** jbadiapa_ has quit IRC20:57
*** timburke has joined #openstack-meeting20:57
*** patchbot has joined #openstack-meeting20:57
*** rossella_s has quit IRC20:58
*** zaitcev has joined #openstack-meeting20:59
notmynameswift team meeting time21:00
notmyname#startmeeting swift21:00
openstackMeeting started Wed Mar 14 21:00:13 2018 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
openstackThe meeting name has been set to 'swift'21:00
notmynamewho's here for the swift team meeting?21:00
*** acoles has joined #openstack-meeting21:01
rledisezhi o/21:01
notmynametdasilva: clayg: ping21:01
claygyup, sorry - i'm here21:01
notmynamegood morning, afternoon, and evening to everyone21:02
notmynameagenda this week is at21:02
*** TxGirlGeek has joined #openstack-meeting21:02
notmynamethere's a few things that have been added, so let's get going21:02
*** rossella_s has joined #openstack-meeting21:02
notmyname#topic s3api21:02
*** openstack changes topic to "s3api (Meeting topic: swift)"21:02
kota_my turn21:02
notmynamekota_: yep. what's going on with this feature branch21:03
kota_in this week, I've been started to work around cleanup/docs updates to get ready to propose it to the master21:03
notmynamekota_: when do you expect to have the merge proposal ready?21:04
kota_I categorize the tasks to backlog and future works21:04
*** cloudrancher has quit IRC21:04
kota_notmyname: i'm still trying to get my effort in a month since the ptg.21:04
*** yamamoto has joined #openstack-meeting21:04
*** cloudrancher has joined #openstack-meeting21:05
notmynameno worries. I understand21:05
notmynamein dublin, we agreed that the feature/s3api merge would be to only bring in the existing swift3 codebase. all tests will pass and it will work if enabled, but no changes to any architecture or enabling anything by default21:05
kota_talking on trello board21:05
*** TxGirlGeek has quit IRC21:05
notmynameis that still the same plan you're working towards?21:05
kota_i'm thinking, I put the items that we don't want to develop on feature/s3api immediately (i.e. will do after merged to the master) in the future work groups21:06
kota_so please checkout if my collection is correct (or not)21:06
kota_notmyname: yes21:06
*** TxGirlGeek has joined #openstack-meeting21:07
kota_so the remaining tasks in the backlog/in-progress are what I'd like to resolve for a monce.21:07
notmynameok. it doesn't look like a lot. (and that's good)21:07
kota_that is a summary for the updates21:08
*** rcernin has joined #openstack-meeting21:08
kota_and then, one thing I'd like to get your help21:08
notmynamewe're getting closer to when feature/deep will land something in master, so the biggest concern will be to make sure those two merges don't happen at the same time21:08
kota_I had 3 outstanding patches for the work now21:08
*** ykatabam has joined #openstack-meeting21:08
kota_oic, nice to hear for feature/deep21:09
kota_the patches are21:09
patchbotpatch 552853 - swift (feature/s3api) - Update S3api Docs21:09
*** TxGirlGeek has quit IRC21:09
patchbotpatch 552854 - swift (feature/s3api) - Cleanup swift/common/middleware/s3api/test dir21:09
patchbotpatch 551273 - swift (feature/s3api) - Avoid global CONF instance21:09
*** gman-tx has quit IRC21:10
kota_in particular, I'd like to hear advice on the first one (docs)21:10
kota_what's needed there.21:10
*** yamamoto has quit IRC21:10
notmynameI'll take a look21:10
kota_because probably I know everything other than you all about s3api so I may be missing something.21:10
notmynameanything else for an update on this work?21:11
kota_if you don't have any questions :)21:11
tdasilvakota_: thanks for driving this work!21:12
*** rossella_s has quit IRC21:12
notmyname#topic add force_auth_retry mode to python-swiftclient when got errors other than 40121:12
*** openstack changes topic to "add force_auth_retry mode to python-swiftclient when got errors other than 401 (Meeting topic: swift)"21:12
patchbotpatch 551956 - python-swiftclient - Add force auth retry mode in swiftclient21:12
notmynamekota_: this is your topic too21:12
notmynamekota_: what is the question we need to answer in this meeting?21:13
kota_ah, short answer on the conflict with feature/deep, i don't think it's not so big matter because basically s3api touches on only middleware or docs.21:13
kota_the python-client thing21:13
kota_I'd like to hear the feels it's better to have on swift community upstream21:13
kota_let me describe short history of that.21:13
kota_mainly described at the commit message.21:14
*** gman-tx has joined #openstack-meeting21:14
kota_the problem I'd like to resolve is the case using sort of reverse proxy(e.g. nginx/Load balancer) between the python-swiftclient - swift-proxy-server.21:14
*** rossella_s has joined #openstack-meeting21:15
kota_the reverse proxy can close the connected socket when it gets error response from swift-proxy.21:15
kota_and it causes broken pipe (socket error, EPIPE) in the python-swiftclient, if python-swift client is still attempts to put the http body (e.g. put object)21:16
notmynameso the proxy is hiding the 401 response by simply closing the socket, and swiftclient doesn't reauth because it never saw the 40121:17
kota_the best way to resolve it, is supporting expext: 100-continue header in the client but it seems to be hard to get in immediately .21:17
kota_notmyname: yes21:17
timburkei think the 401 gets sent, *but the client hasn't read it*21:17
kota_timburke: correct21:18
kota_but i don't think we have the way to read it after the socket was closed... right?21:18
kota_so the proposal on the patch is to add a mode to force the re-auth on any errors.21:18
*** TxGirlGeek has joined #openstack-meeting21:19
kota_i know, it's not straight forward to resolve the problem, just mitigation.21:19
timburkenot sure -- i haven't had a chance to play around with it...21:19
notmynameok, that seems reasonable21:19
notmynamesounds like it was a fun issue to debug21:19
notmynameclayg already has a +2 on it21:20
kota_so my point is that.21:20
claygheck yeah!21:20
kota_thanks clayg!21:20
notmynamematt left an earlier review, but he's not hear right now. perhaps he'll be able to pick it up again and give another review?21:20
kota_I'll poke him later again21:21
notmynameI said something to him in -swift about it, too21:21
notmynamekota_: thanks21:21
*** lpetrut has quit IRC21:22
notmynameok, on the theme of bugs, I'm going to skip around just briefly... bear with me kei-ichi21:22
*** sidx64 has quit IRC21:22
notmyname#topic multiple or bad url quoting21:22
*** openstack changes topic to "multiple or bad url quoting (Meeting topic: swift)"21:22
openstackLaunchpad bug 1755554 in OpenStack Object Storage (swift) "Percent signs in object names cause trouble for versioned_writes" [High,Confirmed]21:22
notmynamewe found this bug yesterday21:22
*** noslzzp has quit IRC21:23
notmynametimburke gave a good summary of the issue21:23
timburke"we suck at URL quoting"21:23
notmynameI wanted to bring it up in the meeting because (1) I'd love to find someone who will volunteer to work on a fix and (2) ask if it should be "critical" instead of "high"21:23
notmynametimburke: perfect summary :-)21:24
claygidk, it's not a regression - it's just always been this way hasn't it?21:24
notmynameI don't know. perhaps the rewrite to versioned_middleware broke it?21:24
*** TxGirlGeek has quit IRC21:25
timburkei still have torgomatic's up in a tab... in case i ever find myself with a surplus of time...21:25
*** TxGirlGeek has joined #openstack-meeting21:25
timburkethe big bad (imo) is that versioning flat out *doesn't work* for some objects21:25
timburkeyou think you've got versioning enabled, go overwrite an object *and it's gone*21:26
claygnot great21:26
kota_too bad21:26
notmynameyeah, that's where I get the question of "critical"21:26
notmynamereally, if we've got someone working on a patch, the difference between high and critical is holding a release for the critical patch to land. and, to be fair, we don't have a release scheduled soon (just lots of other stuff going on)21:27
*** Tom-Tom has joined #openstack-meeting21:28
*** rossella_s has quit IRC21:28
notmynameso the most important question is this: "can someone volunteer to work on a patch for this bug?"21:28
notmyname(please, not everyone at once)21:29
timburkei might be able to? but almost certainly not this week21:29
kota_me too, it might be able to.21:29
notmynameok. timburke and kota_, thank you21:30
notmynameI'll leave it on the agenda for next week, and we'll see if you've had a chance to look at it21:30
*** tssurya has quit IRC21:30
notmyname#topic slogging21:30
*** openstack changes topic to "slogging (Meeting topic: swift)"21:30
notmynamelast topic on the agenda21:31
kei-ichiThis is mine.21:31
kei-ichiI would like to confirm that which channel should I use to inform slogging event.21:31
kei-ichiFirstly I plan to create new channel named "#openstack-slogging" and sent patch to project-config repository. --> plan-121:31
kei-ichiNow infra-team give me a comment that is it really mandatory.(send to swift channel --> plan-2)21:31
*** andreas_s has joined #openstack-meeting21:31
notmynameif you remember from dublin, we talked with kei-ichi about him moving slogging into an openstack namespace21:31
kei-ichithis is my patch to openstack-infra/project-config
patchbotpatch 552282 - openstack-infra/project-config - Add slogging projects21:32
notmynamehere's a question to everyone: would anyone object to having slogging patches reported in the #openstack-swift channel? this implies that discussion about those patches may also happen in the -swift channel21:32
*** rossella_s has joined #openstack-meeting21:32
*** kaisers has quit IRC21:32
acolesno objection I mean21:32
kei-ichiI think, this time slogging will be created as separate repository from swift so I think IRC channel should also be separated. (means plan-1)21:33
*** Tom-Tom has quit IRC21:33
*** awaugama has quit IRC21:33
kei-ichiI would like to hear about this point to swift team prior to fixing patch.21:33
*** ansmith has joined #openstack-meeting21:33
notmynamekei-ichi: I believe the -infra team has concerns about the number of channels that they manage and that are supported by the IRC server and that's why the like to consolidate when possible21:33
notmynameeg a bot can only be in a certain number of channels at a time21:34
*** pchavva has quit IRC21:34
kei-ichiI understood.21:34
tdasilvai think it makes sense to have it in the -swift channel21:34
timburkeit seems like the target audiences would be similar, as well. i know we've gotten a fair number of swift3 questions in #openstack-swift, despite there being a separate #swift3 channel21:34
notmynameI agree that slogging should be separate from swift in governance (eg not relying on swift-core for patches or releases), but I would almost prefer to have slogging updates in -swift instead of separate21:35
kota_timburke: +121:35
notmyname...base on exactly what timburke just said21:35
kei-ichiOK, so same as liberasurecode, can I use -swift channel to inform ?21:35
tdasilvawhich means we should shutdown swift3 channel at some point??21:35
claygtdasilva: +121:35
notmynametdasilva: we should do that anyway because of feature/s3api21:36
kota_tdasilva: after, we get merged feature/s3api21:36
*** andreas_s has quit IRC21:36
notmynamekei-ichi: are you ok with having your updates go to -swift?21:36
* tdasilva has considered shutting down swiftonfile too21:36
notmynametdasilva: there's a swiftonfile? ;-)21:36
claygi think more traffic in openstack-swift is generally a good thing - I don't mind a variety of topics.21:36
*** aeng has joined #openstack-meeting21:36
notmynameclayg: yes!!21:36
kei-ichiyes, patch is really simple, so it is easy to fix.21:36
notmynameI don't expect slogging to have enough activity to overwhelm us in -swift21:36
kei-ichiI think so. So I'll fix patch so that information will be sent to  -swift channel21:37
kei-ichiwould that be okay?21:37
notmynamekei-ichi: so what I'm hearing from everyone, not only are we happy to see you work on a project related to swift so that more people can use it, we want you to do it with us!21:37
notmynamekei-ichi: yes!21:37
kei-ichiThank you notmyname !21:38
notmyname#topic open discussion21:38
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:38
notmynameanything else to cover this week?21:38
*** esberglu_ has quit IRC21:38
notmynameI take that as a "no"21:39
timburkei've said it repeatedly already, but just wanted to give another thank you to acoles for getting sharding probe tests going in zuul v3!21:39
notmynamethank you everyone for your work on swift21:39
*** openstack changes topic to "OpenStack Meetings ||"21:39
openstackMeeting ended Wed Mar 14 21:39:35 2018 UTC.  Information about MeetBot at . (v 0.1.4)21:39
openstackMinutes (text):
*** timburke has left #openstack-meeting21:39
*** patchbot has left #openstack-meeting21:40
*** m_kazuhiro has quit IRC21:40
*** edmondsw has quit IRC21:41
*** dustins_ has quit IRC21:42
*** erlon has quit IRC21:43
*** belmoreira has quit IRC21:45
*** jamesmca_ has quit IRC21:45
*** ykatabam has quit IRC21:46
*** dmorita has joined #openstack-meeting21:50
*** dmorita has quit IRC21:51
*** dmorita has joined #openstack-meeting21:51
*** dmorita has quit IRC21:52
*** esberglu has joined #openstack-meeting21:52
*** kaisers has joined #openstack-meeting21:53
*** kaisers has quit IRC21:56
*** manjeets_lp has quit IRC21:58
*** iyamahat has quit IRC21:59
*** kaisers has joined #openstack-meeting22:00
*** Tom-Tom has joined #openstack-meeting22:01
*** iyamahat has joined #openstack-meeting22:03
*** chyka has quit IRC22:03
*** ykatabam has joined #openstack-meeting22:05
*** bobh has quit IRC22:06
*** Tom-Tom has quit IRC22:06
*** yamamoto has joined #openstack-meeting22:06
*** singlethink has quit IRC22:08
*** yamamoto has quit IRC22:12
*** priteau has quit IRC22:15
*** felipemonteiro_ has joined #openstack-meeting22:20
*** e0ne has joined #openstack-meeting22:21
*** zaitcev has left #openstack-meeting22:21
*** TxGirlGeek has quit IRC22:21
*** dmorita has joined #openstack-meeting22:22
*** e0ne has quit IRC22:22
*** felipemonteiro__ has quit IRC22:23
*** dmorita has quit IRC22:24
*** dmorita has joined #openstack-meeting22:24
*** dmorita has quit IRC22:29
*** TxGirlGeek has joined #openstack-meeting22:31
*** Tom-Tom has joined #openstack-meeting22:38
*** gman-tx has quit IRC22:39
*** dmorita has joined #openstack-meeting22:39
*** jamesmcarthur has joined #openstack-meeting22:40
*** Tom-Tom has quit IRC22:43
*** jamesmcarthur has quit IRC22:45
*** Tom-Tom has joined #openstack-meeting22:47
*** felipemonteiro_ has quit IRC22:49
*** kaisers has quit IRC22:51
*** Tom-Tom has quit IRC22:52
*** diman has joined #openstack-meeting22:52
*** iyamahat has quit IRC22:54
*** diman has quit IRC22:56
*** masber has quit IRC22:57
*** shaohe_feng has joined #openstack-meeting22:57
*** hongbin has quit IRC22:59
*** kaisers has joined #openstack-meeting23:00
*** iyamahat has joined #openstack-meeting23:00
*** masber has joined #openstack-meeting23:00
*** yamamoto has joined #openstack-meeting23:07
*** yamamoto has quit IRC23:12
*** rbudden has quit IRC23:12
*** artom has joined #openstack-meeting23:17
*** fnaval has quit IRC23:18
*** Tom-Tom has joined #openstack-meeting23:19
*** david-lyle has quit IRC23:21
*** rossella_s has quit IRC23:21
*** rossella_s has joined #openstack-meeting23:22
*** Tom-Tom has quit IRC23:24
*** david-lyle has joined #openstack-meeting23:26
*** rossella_s has quit IRC23:28
*** david-lyle has quit IRC23:28
*** rossella_s has joined #openstack-meeting23:30
*** david-lyle has joined #openstack-meeting23:30
*** shaohe_feng has quit IRC23:33
*** jamesmcarthur has joined #openstack-meeting23:36
*** TxGirlGeek has quit IRC23:37
*** kmalloc has quit IRC23:38
*** TxGirlGeek has joined #openstack-meeting23:41
*** TxGirlGeek has quit IRC23:43
*** TxGirlGeek has joined #openstack-meeting23:44
*** esberglu has quit IRC23:50
*** dprince has joined #openstack-meeting23:51
*** Tom-Tom has joined #openstack-meeting23:51
*** Tom-Tom has quit IRC23:56
*** diman has joined #openstack-meeting23:57
*** ykatabam has quit IRC23:59

Generated by 2.15.3 by Marius Gedminas - find it at!