Wednesday, 2017-06-21

*** slaweq has quit IRC00:00
*** aeng has quit IRC00:02
*** sshank has quit IRC00:03
*** jamesmcarthur has joined #openstack-meeting00:06
*** gmann has quit IRC00:06
*** gmann has joined #openstack-meeting00:06
*** ijw has joined #openstack-meeting00:07
*** makowals has quit IRC00:10
*** jamesmcarthur has quit IRC00:10
*** ijw has quit IRC00:12
*** ijw has joined #openstack-meeting00:12
*** TxGirlGeek has quit IRC00:14
*** Swami has quit IRC00:15
*** yangyape_ has quit IRC00:17
*** aeng has joined #openstack-meeting00:20
*** yangyapeng has joined #openstack-meeting00:20
*** amotoki_away is now known as amotoki00:23
*** yangyapeng has quit IRC00:25
*** makowals has joined #openstack-meeting00:25
*** slaweq has joined #openstack-meeting00:32
*** wanghao_ has joined #openstack-meeting00:36
*** Julien-zte has joined #openstack-meeting00:36
*** slaweq has quit IRC00:37
*** wanghao has quit IRC00:39
*** dongfeng1 has joined #openstack-meeting00:41
*** ssalagame has quit IRC00:45
*** Yipei has joined #openstack-meeting00:46
*** makowals has quit IRC00:47
*** ayoung has quit IRC00:49
*** zhhuabj has quit IRC00:52
*** zhhuabj has joined #openstack-meeting00:52
*** slaweq has joined #openstack-meeting00:53
*** rfolco has joined #openstack-meeting00:53
*** ijw has quit IRC00:54
*** yantarou has quit IRC00:56
*** ijw has joined #openstack-meeting00:57
*** slaweq has quit IRC00:57
*** ayoung has joined #openstack-meeting00:57
*** yantarou has joined #openstack-meeting00:57
*** yinxiulin has joined #openstack-meeting00:58
*** zhiyuan has joined #openstack-meeting00:59
*** ubuntu_ is now known as rongHui01:00
*** joehuang has joined #openstack-meeting01:00
zhiyuanhi joe01:00
joehuang#startmeeting tricircle01:01
openstackMeeting started Wed Jun 21 01:01:04 2017 UTC and is due to finish in 60 minutes.  The chair is joehuang. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:01
*** openstack changes topic to " (Meeting topic: tricircle)"01:01
openstackThe meeting name has been set to 'tricircle'01:01
*** dongfeng1 is now known as dongfeng01:01
*** armstrong has quit IRC01:01
joehuang#topic rollcall01:01
*** openstack changes topic to "rollcall (Meeting topic: tricircle)"01:01
joehuang#info  joehuang01:01
dongfeng#info dongfeng01:01
*** fredli__ has joined #openstack-meeting01:01
*** hejiawei has joined #openstack-meeting01:01
Yipei#info Yipei01:01
yinxiulin#info xiulin01:01
zhiyuan#info zhiyuan01:02
fredli__Hi all, I am Liyongle01:02
joehuanghello, fred, welcome to join01:02
joehuang#topic summary of tricircle demo in OPNFV summit01:03
*** openstack changes topic to "summary of tricircle demo in OPNFV summit (Meeting topic: tricircle)"01:03
joehuangbefore the summary of the summit01:03
*** bobmel has joined #openstack-meeting01:03
joehuangone info about storyboard01:03
joehuangthe launchpad will be switched to storyboard in recent future01:04
*** artom has joined #openstack-meeting01:04
joehuangso please try storyboard and community is collecting feedback01:04
*** kevzha01 has joined #openstack-meeting01:05
joehuangthe migration has not been started yet, but we have to be prepared for this01:05
joehuangthat means all blueprint and bug management will be migrated to storyboard01:05
joehuang#info feedback for the storyboard https://storyboard.openstack.org01:06
rongHui#info Ronghui01:06
*** hongbin has quit IRC01:07
joehuangfor opnfv tricircle demo, it's quite successful01:07
diablo_rojo_phonAs soon as I get the okay from you I can set a date to migrate Tricircle.01:07
*** abramley has joined #openstack-meeting01:07
joehuangto diablo_rojo_phon: ok, will let you know when we are ready01:07
*** bobmel has quit IRC01:08
joehuangshall we submit a patch to open a space for Tricircle in storyboard?01:08
*** makowals has joined #openstack-meeting01:08
zhiyuanfeedback from me: storyboard is convenient for tracking blueprint, since we can create several tasks for one blueprint.01:08
zhiyuanin launchpad, we have to put the tasks in the single white board01:09
joehuangok, I'll dive into storyboard in more detail and check to see if a patch is needed for tricircle01:10
joehuangfor the opnfv tricricle demo, video and slides are available01:11
*** rfolco has quit IRC01:11
joehuang#info opnfv tricircle and demo video:
joehuang#info slides is available here
joehuangand video conference demo is recorded at
joehuangBoucherV will record vIMS video this week, once the link is available I'll share to you01:13
*** slaweq has joined #openstack-meeting01:14
joehuangthere are several groups showed interest to integrate tricircle in OPNFV01:14
*** fzdarsky_ has joined #openstack-meeting01:14
*** zhhuabj has quit IRC01:14
joehuangand several guys told me they would like to contribute in tricircle, hope that they will join soon01:15
*** SerenaFeng has joined #openstack-meeting01:15
*** zhhuabj has joined #openstack-meeting01:15
joehuangthat's the major info from tricircle demo in OPNFV summit01:15
joehuangany questions01:15
*** ubuntu_ has joined #openstack-meeting01:16
*** ubuntu_ has left #openstack-meeting01:16
*** ubuntu_ has joined #openstack-meeting01:17
joehuangok, next topic01:17
joehuang#topic feature implementation review01:17
*** openstack changes topic to "feature implementation review (Meeting topic: tricircle)"01:17
*** fzdarsky|afk has quit IRC01:18
joehuangbefore the feature implementation discussion, the milestone 3 of pike will be July 2801:18
*** slaweq has quit IRC01:18
joehuang#info milestone 3 on July 2801:18
joehuangso if you want your features to be landed, please submit your patch ASAP01:18
joehuangplease share your feature implementation and challenge to be discussed here01:19
*** rongHui has quit IRC01:19
dongfengfor me, 1) a patch for resource routing pagination has been committed.  2) job cli feature is under development.01:20
*** yangyapeng has joined #openstack-meeting01:21
Yipeifor labs, have some problems with plugging vip via the AmphoraAPIClient. it responses with 500 status code. still working on it01:21
*** jamesmcarthur has joined #openstack-meeting01:21
joehuangthanks dongfeng, will review the patch soon01:21
zhiyuanoh, I see "merge conflict" for the resource routing pagination patch01:21
dongfengI base this patch on your previous patch01:22
zhiyuanto dongfeng, rebasing is needed I think01:23
dongfenglocal repo has been rebased, I am waitting your comment and then update the next version01:23
zhiyuani see01:24
joehuangfor Tricircle can work with cells v2 now01:24
*** yangyape_ has joined #openstack-meeting01:25
yinxiulini'am modify sfc's patch according to yesterday's discussion01:25
*** ijw has quit IRC01:25
joehuangit's good to update the term of "cross OpenStack L2 network" to "cross Neutron L2 network", can someone help to update this in all document?01:25
Yipeito joehuang, i would like to do it01:26
dongfengit's easy, I can do it.01:26
dongfenggot it.01:26
joehuangok, please submit a patch, because Nova support cells V2 in pike01:26
ubuntu_for Qos, we will update all the patch today and submit the last patch ASAP01:26
joehuangif Tricricle can support cells V2 in networking side, it'll bring lots of value to cloud operators01:27
ubuntu_and metering spec has passed the test, so other guys can continue to review01:28
*** yangyapeng has quit IRC01:28
zhiyuanto ronghui, since you are going to update all the patches, please change to title of the patches to reflect to correct order. in fact, the current part2 needs to be merged first01:28
zhiyuans/to correct/the correct01:29
ubuntu_ok  just like we talk before01:29
ubuntu_part 2 is the base01:30
zhiyuandoes QoS require some special configuration to make it work?01:30
joehuangpart 2 is the base? are you using  reverse order01:30
zhiyuanif so, we need to document them01:31
ubuntu_to zhiyuan: just like openstack qos configuration01:31
joehuangyes, documentation for the guide is need01:31
fredli__ubuntu_: have you responded all the comments zhiyuan01:31
*** ubuntu_ is now known as ronghui01:32
ronghuito joe: yes01:33
zhiyuanto fred, yes, we have discussed the patch in the review page yesterday afternoon01:33
*** kaisers_ has quit IRC01:33
ronghuipart 2 is the base01:33
zhiyuanso I am waiting for the update01:33
ronghuiwe need to adjust the order of merge01:33
ronghuiXiongqiu is try to update the patch and solve the problem you submit and will update the patch today01:34
joehuangwho is updating the patch, I am confused01:35
joehuangok, hope that xiongqiu can talk to us directly01:36
*** Julien-zte has quit IRC01:36
ronghuithere is some problem with his network01:36
joehuangseems that we have reviewed all features in queue, next topic01:36
joehuangok, I see01:36
joehuang#topic open discussion01:37
*** openstack changes topic to "open discussion (Meeting topic: tricircle)"01:37
joehuangany topic to discuss01:37
fredli__nothing more from my side.01:37
*** abramley has quit IRC01:37
joehuangone topic from mine is tricircle integration support01:38
*** gongysh has joined #openstack-meeting01:38
joehuangjust as what I mentioned in the first topic, there are several installer showed interest to integrate tricircle, and Vikram also said whether it's possible to integrate Tricricle with OVN01:39
joehuangso if there are lots of integration, some one may ask help, how can we help?01:40
*** markvoelker has quit IRC01:40
*** abramley has joined #openstack-meeting01:40
*** markvoelker has joined #openstack-meeting01:41
zhiyuanfirstly I think we need to investigate that if it's easy to integrate Tricircle with other components. Is there any required patches to be implemented for that intergration.01:42
fredli__what actions do we need to do if we support?01:43
joehuangcurrently passive reaction is good enough I think01:43
fredli__is it possible to provide one document/script so that partners can do it by themselves?01:43
zhiyuanas I know, if the component is not using l2pop, we need some works to support sdn/l2 gateway mode for vxlan networking01:43
zhiyuanthis part is not tested01:44
joehuangfor OVN if it can recognize the shadow agent/port, I think it can deal with itself01:45
*** markvoelker has quit IRC01:45
joehuangand seems that cells V2 also have its own devstack plugin for multi-cells installation01:46
joehuangTricricle plugin multi-cells installation may not work well with cells V2 multi-cell installation, though function works01:47
zhiyuanthat script has been already merged? if so, we can write our own script to integrate cell V2 based on that script01:47
joehuangonly use Tricricle plugin?01:47
zhiyuanI am thinking that cell V2 script may provide some functions that we can call01:48
joehuangnot merged yet, but I am sure it'll merge soon01:48
zhiyuanah, lib/nova is updated in that patch01:49
joehuangso except feature implementation, lots of engineering work is needed after more and more integration will be done, and bugs will be reported01:49
*** slaweq has joined #openstack-meeting01:50
joehuangtricricle provides documentation for installation/configuration/networking,
joehuanghave you found that it's not clear enough? does it work according to the guide?01:53
joehuangwhat's missing in the guide?01:53
joehuangI remembered that the transport URL configuration is missing in configuration or manual installation guide01:53
*** slaweq has quit IRC01:54
joehuangcould some one update this guide01:54
zhiyuanin the configuration guide, we just mention that "Logging, messaging, database, keystonemiddleware etc configuration which are generated from OpenStack Oslo library, will not be described here"01:55
zhiyuanso transport URL is not covered in the guide01:55
*** yamahata_ has quit IRC01:56
zhiyuantransport_url is discussed in the manual installation guide01:56
joehuangok, any other topic?01:57
zhiyuanno from me01:57
dongfengno from me01:57
Yipeino for me01:57
ronghuino for me01:57
joehuangok, thank you for attending the meeting01:58
*** openstack changes topic to "OpenStack Meetings ||"01:58
openstackMeeting ended Wed Jun 21 01:58:18 2017 UTC.  Information about MeetBot at . (v 0.1.4)01:58
openstackMinutes (text):
*** bkopilov has quit IRC01:59
*** dmacpher has joined #openstack-meeting01:59
*** gyee has quit IRC02:00
*** fredli__ has quit IRC02:02
*** onovy has quit IRC02:02
*** esberglu has joined #openstack-meeting02:02
*** adisky__ has quit IRC02:03
*** onovy has joined #openstack-meeting02:05
*** esberglu has quit IRC02:07
*** dongfeng has quit IRC02:10
*** joehuang has left #openstack-meeting02:17
*** aeng has quit IRC02:17
*** epico has joined #openstack-meeting02:23
*** mriedem has quit IRC02:24
*** unicell has quit IRC02:25
*** vishnoianil has quit IRC02:26
*** slaweq has joined #openstack-meeting02:26
*** aeng has joined #openstack-meeting02:30
*** slaweq has quit IRC02:30
*** Yipei has quit IRC02:35
*** zhiyuan has quit IRC02:35
*** bobh has quit IRC02:38
*** bobh has joined #openstack-meeting02:38
*** baoli has joined #openstack-meeting02:38
*** makowals has quit IRC02:40
*** caowei has joined #openstack-meeting02:44
*** ssalagame has joined #openstack-meeting02:47
*** zz_dimtruck is now known as dimtruck02:54
*** baoli has quit IRC02:56
*** yamahata_ has joined #openstack-meeting03:01
*** slaweq has joined #openstack-meeting03:01
*** bobmel has joined #openstack-meeting03:04
*** SerenaFeng has quit IRC03:05
*** hongbin has joined #openstack-meeting03:05
*** slaweq has quit IRC03:06
*** bobmel has quit IRC03:09
*** bobh has quit IRC03:11
*** dimtruck is now known as zz_dimtruck03:14
*** thorst has joined #openstack-meeting03:15
*** mikal_ is now known as mikal03:15
*** baoli has joined #openstack-meeting03:16
*** ekcs has joined #openstack-meeting03:17
*** bkopilov has joined #openstack-meeting03:17
*** makowals has joined #openstack-meeting03:19
*** baoli has quit IRC03:21
*** SerenaFeng has joined #openstack-meeting03:21
*** ekcs has quit IRC03:28
*** markvoelker has joined #openstack-meeting03:29
*** artom has quit IRC03:31
*** aeng has quit IRC03:34
*** slaweq has joined #openstack-meeting03:38
*** yinxiulin has quit IRC03:38
*** galstrom_zzz is now known as galstrom03:41
*** slaweq has quit IRC03:42
*** tbh has joined #openstack-meeting03:43
*** Julien-zte has joined #openstack-meeting03:43
*** tung_doan has joined #openstack-meeting03:50
*** aeng has joined #openstack-meeting03:50
*** esberglu has joined #openstack-meeting03:51
*** thorst has quit IRC03:54
*** esberglu has quit IRC03:55
*** galstrom is now known as galstrom_zzz03:56
*** yamamoto has joined #openstack-meeting03:57
*** kaisers_ has joined #openstack-meeting04:00
*** frickler_ is now known as frickler04:00
*** ssalagame has quit IRC04:00
*** SerenaFeng has quit IRC04:02
*** bobmel has joined #openstack-meeting04:05
*** tinwood has quit IRC04:05
*** tinwood has joined #openstack-meeting04:06
*** sridharg has joined #openstack-meeting04:06
*** epico has quit IRC04:06
*** links has joined #openstack-meeting04:07
*** bobmel has quit IRC04:09
*** oidgar has quit IRC04:12
*** salv-orlando has joined #openstack-meeting04:12
*** salv-orlando has quit IRC04:13
*** makowals has quit IRC04:14
*** Liuqing has joined #openstack-meeting04:15
*** jamesmcarthur has quit IRC04:20
*** makowals has joined #openstack-meeting04:21
*** salv-orlando has joined #openstack-meeting04:22
*** YanXing_an has joined #openstack-meeting04:26
*** salv-orlando has quit IRC04:27
*** armax has joined #openstack-meeting04:28
*** janki has joined #openstack-meeting04:28
*** hongbin has quit IRC04:30
*** epico has joined #openstack-meeting04:30
gongysh#startmeeting tacker04:31
*** dkushwaha has joined #openstack-meeting04:31
openstackMeeting started Wed Jun 21 04:31:00 2017 UTC and is due to finish in 60 minutes.  The chair is gongysh. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:31
*** openstack changes topic to " (Meeting topic: tacker)"04:31
openstackThe meeting name has been set to 'tacker'04:31
gongysh#topic roll call04:31
*** openstack changes topic to "roll call (Meeting topic: tacker)"04:31
gongyshdkushwaha, tbh weclome04:31
gongyshLiuqing, welcome to join us.04:31
gongyshtung_doan, nice to see you.04:31
Liuqinggongysh, thanks04:32
gongyshYanXing_an, welcome our patch producer.04:32
YanXing_angongysh, haha:)04:33
tung_doangongysh: me too.. get stuck in a hard project :)04:33
gongyshchinamobile is ranking 2nd at
gongyshYanXing_an, thanks04:33
* gongysh is wondering where sridar_ram is.04:34
YanXing_angongysh, we will work hard to be 1st :)04:34
*** anilvenkata has joined #openstack-meeting04:34
gongyshYanXing_an, glad to see that.04:35
gongyshif you can keep that, I will consider to give over PTL role.04:35
gongyshto give -> giving04:35
gongyshok, 5 mins passed. we will start without sridar_ram.04:36
gongysh#topic release04:36
*** openstack changes topic to "release (Meeting topic: tacker)"04:36
gongyshthanks sridar_ram, who reminds me the release email.04:37
*** cody-somerville has quit IRC04:37
*** cody-somerville has joined #openstack-meeting04:37
gongyshif you guys see this email, we can feel the time is running low.04:38
gongyshso please keep up reviewing activity and coding.04:38
gongysh#topic bp04:39
*** openstack changes topic to "bp (Meeting topic: tacker)"04:39
gongyshtung_doan, do you think your bp can be finished at this short time?04:39
tung_doangongysh: sure, I thibk both vnffg-autoscaling and vnffg-autohealing can do04:40
*** adisky__ has joined #openstack-meeting04:40
gongyshtung_doan,  ok. but you bp spec update is kind of slow.04:41
gongyshso keep up, and you can code side by sie.04:41
tung_doangongysh: I had some code locally. will push it in parallel04:41
gongyshsie -> side.04:41
tung_doangongysh: I got stuck in some urgent works until last week04:42
*** armax has quit IRC04:42
gongyshtung_doan, fine, make each patch testable,  if it does not break CI, we can trust manual test first.04:42
gongyshbut FT is favorable and must be made up sometime.04:43
tung_doangongysh: got it. thanks04:43
*** gouthamr has quit IRC04:43
gongyshdkushwaha, you NS with vnffg status?04:43
dkushwahagongysh: no any update in last week04:43
gongyshhave you implemented it in your mind, then?04:44
dkushwahagongysh: will update spec by tomorrow.04:44
gongyshdkushwaha, if you have no time for it, we can leave it to next cycle.04:45
gongyshdkushwaha, you can help to review other bps and patches.04:45
dkushwahagongysh: i will try to finish it, but yes, i will give 100% in review and other04:46
*** ssalagame has joined #openstack-meeting04:46
gongyshdkushwaha, thanks.04:46
gongysh#topic coding04:46
*** openstack changes topic to "coding (Meeting topic: tacker)"04:46
gongyshfirst code patch is the blueprint refactor-vim-monitor patches.04:46
gongyshthese are from Liuqing, who is from 99cloud too. I have invited him to do contribution.04:47
gongyshLiuqing, thanks.04:47
tung_doanLiuqing: welcome04:47
dkushwahaLiuqing: welcome04:48
gongyshdkushwaha, to verify the patches are working as expected. I have tested it.04:48
gongyshyou can see it.04:48
Liuqingtung_doan, dkushwaha , thanks04:48
YanXing_anLiuqing, welcome, nice job.04:48
gongyshif you have no time to do testing, you can trust it.04:48
dkushwahagongysh: yup sure. i checked it.04:49
dkushwahagongysh: i will merge the patch04:49
gongyshdkushwaha, thanks04:49
Liuqingdkushwaha, thanks04:50
dkushwahagongysh: done04:50
gongyshLiuqing, next after, please add a patch to write devref doc and a function test.04:50
gongyshand also I will help you to start the monitor policy BP code.04:51
Liuqingsure, and in next patch i will add doc and test04:51
gongyshwith blueprint refactor-vim-monitor is framework, we have good foundation.04:52
tbhI have to drop, travelling to office04:52
gongyshwith blueprint refactor-vim-monitor's framework04:52
gongyshtbh, see you.04:52
gongyshtbh, storage patch, if you have time.04:53
*** tbh has quit IRC04:53
gongyshnext code patch is from YanXing_an04:53
Liuqingyep, gongysh and thanks04:53
gongyshLiuqing welcome04:54
*** jamesmcarthur has joined #openstack-meeting04:54
gongyshYanXing_an, I thing you have the solution for the CI failure.04:54
gongyshthing -> think04:54
YanXing_anyes, I have known the reason of failure, will update the patch04:55
gongyshYanXing_an, good to know it.04:55
*** ekcs has joined #openstack-meeting04:56
gongyshmore things I want to say is the kolla installation of tacker MANO system.04:56
gongyshI want use kolla way to do tacker installation. devstack is too weak for non tacker developer to install tacker.04:58
gongyshsecond stuff is the doc -> user guide.04:58
*** jamesmcarthur has quit IRC04:59
gongyshYanXing_an, if you want to rank 1st, the user guide is the place to produce patch.04:59
tung_doangongysh: nice to see that04:59
*** Yipei has joined #openstack-meeting04:59
*** ssalagame has quit IRC04:59
gongyshwe can write it in tacker repo first, and then move to openstack document team.04:59
gongysh#topic open discussion05:00
*** openstack changes topic to "open discussion (Meeting topic: tacker)"05:01
*** Yipei has left #openstack-meeting05:01
gongyshdo you guys want to say something?05:01
dkushwahagongysh: any updates from OPNFV summit05:01
gongyshtriant is not here. he is there, I am not.05:02
*** salv-orlando has joined #openstack-meeting05:02
Liuqingwiil we Angularize tacker-horizon dashboard?05:02
dkushwahagongysh: oh05:02
tung_doandkushwaha: gongysh: yeah.. i also want to know05:02
gongyshLiuqing,  I want the visual digram for VNFD, VNFFGD05:03
*** makowals has quit IRC05:03
dkushwahatung_doan yup, i think there should be many input points from opnfv summit05:03
dkushwahafor Tacker05:04
*** emagana has joined #openstack-meeting05:04
Liuqinggongysh, we can use d3 to draw the digram05:04
gongyshLiuqing, if you are interested in it, that is great.05:04
tung_doanYanXing_an: thanks for caring my patch: . I already emailed to Heat Translator team. Good news is that they may release Heat Translator 0.8.1 this week05:04
gongyshtung_doan, have it on my plate.05:05
tung_doandkushwaha: agree05:06
gongyshonce the CI is happy, I will do the reviewing.05:06
tung_doangongysh: great! thanks05:06
gongyshtung_doan, dkushwaha , it seems triant is still touring tiananmen square and Great Wall.05:06
*** links has quit IRC05:07
tung_doangongysh: hahaha05:07
dkushwahagongysh: hahahaha05:07
gongyshand Forbidden city is large too. he has asked me for those sites.05:07
dkushwahagongysh: i also love to visit Great wall some day :)05:07
gongyshdkushwaha, welcome anytime.05:08
Liuqinggongysh: hahahaha05:08
*** adreznec has quit IRC05:08
*** unicell has joined #openstack-meeting05:08
gongyshdkushwaha, you can install a WeChat client on your phone so that can chat me anytime.05:08
*** bobmel has joined #openstack-meeting05:08
*** bnemec has quit IRC05:08
dkushwahagongysh: sure, will try it05:09
*** makowals has joined #openstack-meeting05:09
gongyshmy wechat number is my telephone number.05:09
Liuqingdkushwaha, welcome05:09
dkushwahagongysh: and what is your telephone number ?05:10
dkushwahagongysh: thanks05:10
gongyshYanXing_an, don't forget your state transition diagram.05:11
gongyshwe need it.05:11
*** unicell1 has joined #openstack-meeting05:11
gongyshto narrate  what action is ok at each state.05:12
openstackLaunchpad bug 1697818 in tacker "We can create vims with same name in same tenant." [Critical,New] - Assigned to Yan Xing'an (yanxingan)05:12
YanXing_angongysh, ok05:12
gongyshwhat do you think of this bug?05:12
*** unicell has quit IRC05:13
*** bobmel has quit IRC05:13
gongyshdkushwaha, after you update the unique index to include deleted_at, we can have the duplicated name for not deleted resources.05:13
dkushwahagongysh: it should not be occurred, i will check it05:14
gongyshdkushwaha, thanks.05:15
Liuqinggongysh, duplicated name is not nice for end user, and we can raise a duplicatedNameException.05:15
gongysh#action dkushwaha  to check 169781805:15
gongyshLiuqing, yes, we have constrain it via mysql unique index.05:16
gongyshconstrain -> constrained05:16
Liuqinggongysh, ok05:16
*** emagana has quit IRC05:17
gongyshif you guys have no more thing to talk, we can end meeting earlier.05:17
gongyshone more news, YanXing_an and me have got a topic to talk about tacker at openstack china days05:18
gongyshthe day is at July 24th.05:18
gongyshthanks everyone.05:19
gongyshhave a good night or day.05:19
*** openstack changes topic to "OpenStack Meetings ||"05:19
openstackMeeting ended Wed Jun 21 05:19:58 2017 UTC.  Information about MeetBot at . (v 0.1.4)05:20
openstackMinutes (text):
*** gongysh has quit IRC05:21
*** links has joined #openstack-meeting05:23
*** tung_doan has quit IRC05:23
*** armax has joined #openstack-meeting05:24
*** SerenaFeng has joined #openstack-meeting05:25
*** aeng has quit IRC05:26
*** tobberydberg has joined #openstack-meeting05:29
*** ekcs has quit IRC05:29
*** jbadiapa_ has joined #openstack-meeting05:29
*** abhishekk has left #openstack-meeting05:32
*** ssalagame has joined #openstack-meeting05:35
*** ssalagame has quit IRC05:35
*** ekcs has joined #openstack-meeting05:36
*** esberglu has joined #openstack-meeting05:39
*** salv-orlando has quit IRC05:39
*** salv-orlando has joined #openstack-meeting05:39
*** aeng has joined #openstack-meeting05:39
*** pewp has quit IRC05:40
*** prateek has joined #openstack-meeting05:42
*** e0ne has joined #openstack-meeting05:43
*** oidgar has joined #openstack-meeting05:43
*** esberglu has quit IRC05:44
*** csomerville has joined #openstack-meeting05:44
*** salv-orlando has quit IRC05:44
*** pewp has joined #openstack-meeting05:44
*** Julien-zte has quit IRC05:44
*** bnemec has joined #openstack-meeting05:46
*** e0ne has quit IRC05:47
*** cody-somerville has quit IRC05:47
*** Julien-zte has joined #openstack-meeting05:48
*** Julien-zte has quit IRC05:50
*** Julien-zte has joined #openstack-meeting05:52
*** ekcs has quit IRC05:53
*** Julien-zte has quit IRC05:54
*** armax has quit IRC05:55
*** diablo_rojo has quit IRC05:57
*** andreas_s has joined #openstack-meeting05:58
*** kylek3h has quit IRC05:58
*** adreznec has joined #openstack-meeting06:00
*** slaweq has joined #openstack-meeting06:01
*** ltomasbo|away is now known as ltomasbo06:03
*** slaweq has quit IRC06:05
*** bkopilov has quit IRC06:06
*** wanghao_ has quit IRC06:07
*** bobmel has joined #openstack-meeting06:09
*** bobmel has quit IRC06:14
*** Julien-zte has joined #openstack-meeting06:22
*** Liuqing has quit IRC06:25
*** aeng has quit IRC06:26
*** jtomasek_ has joined #openstack-meeting06:28
*** pcaruana has joined #openstack-meeting06:31
*** ykatabam has quit IRC06:35
*** dkushwaha has quit IRC06:36
*** wanghao has joined #openstack-meeting06:36
*** dkushwaha has joined #openstack-meeting06:36
*** kylek3h has joined #openstack-meeting06:37
*** slaweq has joined #openstack-meeting06:37
*** elynn has joined #openstack-meeting06:38
*** slaweq has quit IRC06:41
*** bkopilov has joined #openstack-meeting06:42
*** jtomasek_ has quit IRC06:45
*** artom has joined #openstack-meeting06:56
*** rcernin has joined #openstack-meeting06:59
*** markvoelker has quit IRC07:00
*** markvoelker has joined #openstack-meeting07:00
*** markvoelker has quit IRC07:01
*** markvoelker has joined #openstack-meeting07:01
*** markvoelker has quit IRC07:01
*** slaweq has joined #openstack-meeting07:03
*** edmondsw has joined #openstack-meeting07:03
*** armax has joined #openstack-meeting07:04
*** oidgar has quit IRC07:05
*** SerenaFeng has quit IRC07:06
*** markvoelker has joined #openstack-meeting07:07
*** slaweq has quit IRC07:07
*** tmorin has joined #openstack-meeting07:07
*** edmondsw has quit IRC07:08
*** SerenaFeng has joined #openstack-meeting07:11
*** tesseract has joined #openstack-meeting07:15
*** ralonsoh has joined #openstack-meeting07:15
*** andreas-f has joined #openstack-meeting07:16
*** jgrassle1 is now known as jgrassler07:19
*** elynn has quit IRC07:20
*** caowei has quit IRC07:22
*** SerenaFeng has quit IRC07:22
*** caowei has joined #openstack-meeting07:23
*** f13o has joined #openstack-meeting07:23
*** ykatabam has joined #openstack-meeting07:26
*** esberglu has joined #openstack-meeting07:27
*** caowei_ has joined #openstack-meeting07:27
*** caowei has quit IRC07:27
*** caowei_ is now known as caowei07:27
*** ricolin has joined #openstack-meeting07:28
*** emagana has joined #openstack-meeting07:29
*** mrunge_ has joined #openstack-meeting07:30
*** mrunge has quit IRC07:30
*** links has quit IRC07:31
*** ubuntu_ has joined #openstack-meeting07:31
*** esberglu has quit IRC07:31
*** alexchadin has joined #openstack-meeting07:32
*** emagana has quit IRC07:33
*** ronghui has quit IRC07:35
*** ubuntu_ has quit IRC07:36
*** fzdarsky_ is now known as fzdarsky07:37
*** wanghao has quit IRC07:37
*** esberglu has joined #openstack-meeting07:37
*** janki has quit IRC07:38
*** slaweq has joined #openstack-meeting07:38
*** ubuntu_ has joined #openstack-meeting07:38
*** wanghao has joined #openstack-meeting07:39
*** esberglu has quit IRC07:42
*** slaweq has quit IRC07:43
*** links has joined #openstack-meeting07:44
*** SerenaFeng has joined #openstack-meeting07:45
*** henrynash has joined #openstack-meeting07:52
*** salv-orlando has joined #openstack-meeting07:54
*** RonghUI has joined #openstack-meeting07:58
*** ubuntu_ has quit IRC07:58
*** ubuntu_ has joined #openstack-meeting08:01
*** slaweq has joined #openstack-meeting08:04
*** RonghUI has quit IRC08:04
*** RonghUI has joined #openstack-meeting08:07
*** ubuntu_ has quit IRC08:08
*** slaweq has quit IRC08:08
*** rossella__ has joined #openstack-meeting08:09
*** e0ne has joined #openstack-meeting08:10
*** bobmel has joined #openstack-meeting08:10
*** e0ne has quit IRC08:13
*** verdurin has joined #openstack-meeting08:13
*** bobmel has quit IRC08:15
*** esberglu has joined #openstack-meeting08:23
*** lpetrut has joined #openstack-meeting08:25
*** e0ne has joined #openstack-meeting08:27
*** esberglu has quit IRC08:28
*** slaweq has joined #openstack-meeting08:30
*** hashar has joined #openstack-meeting08:31
*** e0ne has quit IRC08:33
*** slaweq has quit IRC08:35
*** rossella_ has joined #openstack-meeting08:36
*** rossella__ has quit IRC08:37
*** gongysh has joined #openstack-meeting08:39
*** rbergero1 is now known as rbergeron08:43
*** rbergeron has quit IRC08:43
*** rbergeron has joined #openstack-meeting08:43
*** rcernin has quit IRC08:45
*** neiljerram has joined #openstack-meeting08:45
*** pnavarro has joined #openstack-meeting08:47
*** edmondsw has joined #openstack-meeting08:51
*** rcernin has joined #openstack-meeting08:51
*** wanghao has quit IRC08:53
*** rossella_ has quit IRC08:54
*** wanghao has joined #openstack-meeting08:54
*** electrofelix has joined #openstack-meeting08:55
*** edmondsw has quit IRC08:56
*** Julien-zte has quit IRC08:56
*** yamahata_ has quit IRC08:57
*** Julien-zte has joined #openstack-meeting08:58
*** priteau has joined #openstack-meeting08:58
*** oneswig has joined #openstack-meeting08:58
*** rossella_ has joined #openstack-meeting08:58
*** dmacpher has quit IRC08:59
oneswig#startmeeting scientific-wg09:00
openstackMeeting started Wed Jun 21 09:00:23 2017 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: scientific-wg)"09:00
openstackThe meeting name has been set to 'scientific_wg'09:00
verdurinMorning, oneswig, all09:00
*** henrynash has quit IRC09:00
oneswigGood morning...09:00
oneswigBlair mentioned a dinner appointment, is hoping to be along09:01
oneswig#link agenda for today
oneswigHi priteau09:01
priteauGood morning oneswig09:02
priteauHello verdurin09:02
*** b1airo has joined #openstack-meeting09:02
verdurinHi priteau09:02
b1airoHi gang09:02
oneswig#topic Optimal meeting time09:02
*** openstack changes topic to "Optimal meeting time (Meeting topic: scientific-wg)"09:02
oneswigHi b1airo09:02
oneswig#chair b1airo09:02
openstackCurrent chairs: b1airo oneswig09:02
*** salv-orlando has quit IRC09:02
oneswiggood evening09:02
*** dbecker has joined #openstack-meeting09:02
oneswigI was just about to quote some Shakespeare - "when shall we three meet again", but now we're four :-)09:03
*** salv-orlando has joined #openstack-meeting09:03
*** salv-orlando has quit IRC09:03
b1airoNote that I'm presently walking to a restaurant for a work thing, so will be a bit patchy this meeting I'm afraid09:03
priteauGood evening b1airo09:04
oneswigOn that theme, there was some list discussion on more convenient times to meet for EMEA and APAC.09:04
verdurinoneswig: has someone complained about the current time?09:04
b1airoHi priteau09:04
*** YanXing_an has quit IRC09:04
oneswigb1airo: proposes 0700 UTC or 1100 UTC09:04
b1airoverdurin: mainly me - bedtime clash09:04
oneswig1100 UTC is good for me, 0700 less so...09:05
priteauditto, especially when we're out of DST09:05
verdurin1100 UTC okay for me - 0900 was the problematic one09:05
*** daveholland has joined #openstack-meeting09:06
oneswigI think then, we have unanimous approval for 1100 UTC?09:06
daveholland(late vote for 1100UTC from me)09:06
*** salv-orlando has joined #openstack-meeting09:06
oneswig#agreed We'll request a move to 1100 UTC (if available)09:07
b1airoGreat, I'll follow that up later then. Shall we chat about scientific software/apps etc on cloud?09:07
oneswigHi daveholland that's excellent09:07
davehollandsorry, previous meeting ran a bit late09:07
oneswig#action b1airo to investigate 1100 UTC09:07
oneswig#topic Scientific app catalogues on OpenStack09:07
*** openstack changes topic to "Scientific app catalogues on OpenStack (Meeting topic: scientific-wg)"09:07
verdurinHi daveholland09:07
*** salmantoor has joined #openstack-meeting09:08
oneswigOK so this topic came about because there appear to be several groups around the world who want to get started on making app catalogues for their users09:08
b1airoSo I suggested we have a bit of a chat/survey on this prompted by some work we recently completed in the Nectar cloud to launch a new category of glance images contributed by our community09:08
*** salv-orlando has quit IRC09:08
verdurinoneswig: could you define what "app" refers to in this context?09:08
oneswigI'm aware of prior work from the NSF gang (Jetstream and Bridges)09:08
davehollandare thinking of e.g. an image with Rstudio built/configured?09:09
daveholland(we have done that)09:09
oneswigverdurin: my definition is, someone using a tool rather than compiling it.  Eg, ISV applications, or Spark, or similar.09:09
*** salv-orlando has joined #openstack-meeting09:09
oneswigdaveholland: sounds right to me.09:09
b1airoI'm interested in looking at this broadly, figuring out everything that this might mean and then looking at recommendations for particular use cases09:10
verdurinoneswig: I suppose my point is whether we're covering something like Broad sequencing pipeline, or just the component programs, or both?09:10
b1airoA machine image is probably the most base form09:11
*** caowei has quit IRC09:11
*** caowei has joined #openstack-meeting09:11
b1airoverdurin: I would say whatever is useful at the level of the scientist09:11
oneswigverdurin: I'm thinking of the unit, a combination of services, allocated together09:11
*** dmacpher has joined #openstack-meeting09:12
davehollandso we've done various "applications" e.g. an ELK stack; Docker (to make sure the bridge IP range is set to avoid clashing with our internal network range); an openlava cluster; an NFS server. Some of these are aimed at minimising the "sysadmin speed bump" for a developer. Some have CloudForms orchestration on top09:12
b1airoThe point of distributing "apps" is to make them easy to consume for a particular purpose, so for e.g. genomics a whole pipeline is probably a suitable unit to distribute in some way09:12
oneswigThe way the compute is typically consumed, I guess, makes it easier for users to consume09:13
oneswigdaveholland: how have you gone about that?09:13
priteauOrchestration templates (Heat or CloudFormation or something else) should be handled as well as disk images09:13
davehollandoneswig: we pointed the intern in the right direction and let him go :) Seriously, we're using Packer (so, image definition as code) and building on a base OS image. There's no concept of combining functions (e.g. openlava with docker) which is something I don't know how to address09:15
oneswigpriteau: on chameleon, do you have a feel for how many people use the appliances as a proportion?09:15
verdurinYes, I think we need the recipes as well, or references to upstream support cf. definitions in elasticluster09:15
priteauoneswig: you mean what we call "complex appliances", which are orchestrated templates?09:15
*** rossella_ has quit IRC09:16
b1airoAnyone else using Murano? We have it on Nectar also and have some members contributing new packages quite steadily, but they are mostly typical app stacks rather than science/research specific at the moment09:16
oneswigpriteau: things like the hadoop appliance09:16
*** SerenaFeng has quit IRC09:17
b1airoI need to pay attention here now, pls mention me if there's anything to answer09:17
oneswigWe don't have Murano but are interested generally in it as a solution.  One issue IIRC is that it's not supported by Red Hat OSP09:17
oneswigWhich makes it tricky for quite a lot of deployments out there.09:18
*** e0ne has joined #openstack-meeting09:18
daveholland@blairo we're not using Murano mostly because it's not in RHOSP. but it looks potentially interesting09:18
*** zz9pzza has joined #openstack-meeting09:18
b1airoDoes RH have a viable alternative?09:18
priteauoneswig: I haven't run the numbers recently but IIRC some months ago, most usage was with basic CentOS or Ubuntu images, then images for specialized hardware (GPU, FPGA), then OpenStack deployments09:19
b1airoThings like Juju seem like a reasonable agnostic alternative09:19
oneswigdaveholland: Am I right in thinking that RH will still support OSP if a customer integrates other services - just not the extra non-supported services?09:19
davehollandI'm not sure if OpenShift fits that gap (maybe if you push hard)09:19
priteauThe Hadoop appliance wasn't used much, I assume because it targets a very specific community of people interested by high-performance networking in VMs09:19
oneswigb1airo: I think RH would like people to use OpenShift or CloudForms perhaps?09:19
oneswigok thanks priteau09:20
daveholland@oneswig yes, we have done various customizations (e.g. ml2 drivers) and still get support, we haven't added other OpenStack services though09:20
verdurindaveholland: Openshift leans more towards developers09:20
verdurinRH may have Murano as a Tech. Preview soon, if they don't already09:20
priteauoneswig: but we are a special testbed with a lot of users building their own systems for research. I expect domain scientists would use pre-packaged appliances much more.09:21
oneswigFrom this discussion, I think if somebody was to deploy Murano and make a good fist of it, we've got enough content for another section of the book on this.09:21
davehollandMurano isn't tech preview in RHOSP11 FWIW (we're only just about to deploy RHOSP10 as our next iteration...)09:21
*** yamamoto has quit IRC09:22
b1airoYeah I think Nectar generally would be interested in contributing and collaborating on that09:22
verdurindaveholland: okay, once more my optimism is dashed09:22
davehollandsorry :) :(09:22
oneswigb1airo: jmlowe and rbudden I'm sure would also be interested.09:22
verdurinoneswig: we would be happy to contribute09:22
b1airoYes, this conversation actually started with them09:23
oneswigverdurin: daveholland: I expect it can be done within TripleO + RDO (gut instinct)09:23
oneswigAnd would then transfer direct to OSP09:23
oneswigI can do some research on that.09:24
verdurinoneswig: sure - that's how I would test it anyway09:24
oneswigb1airo: Is there anything online about Nectar's work with Murano so far?09:24
*** SerenaFeng has joined #openstack-meeting09:24
oneswigverdurin: testing Murano on tripleo - that would be great, lets try to work out how09:25
davehollanddo I understand right that Murano uses heat? Is that to assemble components in an instance deployed from a bare OS image? (sounds like say using CloudForms to inject cloud-init script to install/configure packages)09:26
*** egallen has joined #openstack-meeting09:26
b1airooneswig: a little, e.g.,
oneswigdaveholland: I believe so, yes.  Particularly good for managing a multi-node application topology as a single addressable thing09:27
priteaudaveholland: yes, Murano can store Heat templates:
davehollandOK, and that does address how to combine components/applications in a single instance (assuming they don't tread on each other) thanks09:27
oneswigI wonder how portable Murano apps are from one cloud to another.  Probably quite easy to include site-specific assumptions.09:28
*** rossella_ has joined #openstack-meeting09:29
oneswigdaveholland: b1airo's suggestion of juju earlier covers very similar ground - but even less likely to be on RH's roadmap09:29
zz9pzzaIf you used something like packer with openstack and aws to generate images that would help to reduce site specific issues.09:30
b1airoThough doesn't need to be on RH's roadmap to use it against a RHOSP cloud09:30
verdurinYes, I'd go that way rather than Juju, about which I'm a bit of a sceptic09:31
*** wanghao has quit IRC09:31
oneswigzz9pzza: agreed, building for two different targets does help remove assumptions09:31
*** slaweq has joined #openstack-meeting09:31
*** henrynash has joined #openstack-meeting09:32
oneswigOK, how can we make progress here?  I think there's some investigation and reporting back.  Like everyone I can't be certain if I'll get the time at this end but I'd like to try it too.09:33
davehollandit's a trade-off though: build images and you have (potentially exponential) image sprawl and the size requirements; but an image is quicker to deploy the app than installing it on a bare OS every time09:33
zz9pzzaI prefer images, as it reduces launch time and they can have functional tests via a ci09:34
verdurinoneswig: happy to coordinate with you separately about Murano testing with TripleO09:34
b1airoI'll have a think about a way to survey what people are going/seeing today09:34
oneswigI guess with images you lose the opportunity to easily parameterise, eg scale of resource allocated09:34
oneswigverdurin: great, lets do that.09:35
zz9pzzaYou can put some customisation in cloud init09:35
b1airoCan still use cloud-init to customise behaviour oneswig09:35
*** slaweq has quit IRC09:35
oneswigzz9pzza: but not things like the number of worker nodes?09:35
zz9pzzaBut that is at a different layer eg heat09:35
zz9pzzaor auto scaling from the first machine09:36
oneswigtrue.  Heat + images would get you a long way09:36
oneswigthat is was we do for cluster-as-a-service currently, with ansible as the icing on the cake :-)09:36
b1airoThe biggest issue we see with Heat templates is that the original dev assumes some feature of their local cloud, e.g., tenant networks or floating IPs09:37
b1airoOften those things are not necessary dependencies, but it's hard to untangle them09:37
priteauMy dream would be one unified way of defining customization at image-build time or at deployment-time, and the infrastructure would decide which is best to use09:37
oneswigb1airo: My heat templates certainly have that stuff in them.09:37
priteauBut I suppose that's more for a PaaS than for IaaS09:38
davehollandheat input parameters (+ defaults) could paper over that09:38
b1airoYes priteau , reminds me of when I was programming against Azure many years back09:38
oneswigpriteau: In this discussion I see the application catalogue in that layer, or above it09:38
oneswigOK, final actions?  I can start a review for a new section of the book.  When people's research comes back, we can start to gather findings there.  b1airo it would be particularly interesting if there's evidence of Nectar's Murano serving science/HPC apps.  GPUs, SRIOV - bonus material.09:42
b1airoShall we have a quick chat on security oneswig ? I have one eye on my phone still...09:43
oneswigWe should also roll over this topic for the Americas09:43
oneswigOK, here it comes09:43
oneswig#topic Security of research computing instances09:43
b1airoYes agreed re. rollover09:43
*** openstack changes topic to "Security of research computing instances (Meeting topic: scientific-wg)"09:43
oneswigAnother week, another kernel patch.09:43
oneswigI'm not sure cloud helps to the extent that it could with these things - so easy to have user machines going rotten09:44
oneswigAny good practice out there?09:44
b1airoWe are looking at ways to integrate FW into our OpenStack in an opt-in manner (it's otherwise a DMZ)09:44
davehollandturn on unattended-upgrades (or similar) in base images? maybe controversial for repeatable/reproducible09:44
zz9pzzaI note that cloudforms can do security scans by taking a snapshot of a machine and run scripts against that image however we havn't tried using it yet.09:44
verdurinShould be possible to reuse some of the work people are doing to vet container images/definition files?09:45
davehollandor accept that the soft centre is going to remain soft, and check that security groups keep the outside relatively hard?09:45
priteauWe run a vulnerability scanner against instances, but that only covers issues that can be detected remotely (mostly SSL security problems)09:45
b1airoCurrently seems like a routed solution where FW is the default gateway on certain provider nets might be the simplest option. So no direct OpenStack Integra09:45
oneswigI've heard of the friendly probing service for that - both against infra and instances09:45
b1airoverdurin: any links on that?09:46
*** yamamoto has joined #openstack-meeting09:46
oneswigb1airo: is that an instance serving as firewall & gateway, or FWaaS?09:46
verdurinb1airo: e.g.
davehollandalso the location of the security responsibility boundary. If the OpenStack admin is purely providing hosting (indeed might be contractually forbidden from looking inside instances) that makes a difference09:47
b1airoThe image catalog work I mentioned earlier includes a static security scan of the image as one of the criteria to pass before we put the image in the "Contributed" category09:47
oneswigb1airo: sounds good.  Is that on nectar's github?09:48
b1airooneswig: the FW could be in an instance but we already have physical Palo Altos that we can probably integrate like that09:48
*** krenczewski has joined #openstack-meeting09:48
*** oidgar has joined #openstack-meeting09:48
priteauThere was a related talk in Barcelona, still on my watch list though09:49
oneswigIs there an equivalent of something like tripwire/electricfence that can run within a VTN, or is that under the firewall remit?09:49
oneswigThanks priteau, looks interesting09:49
b1airooneswig: yes, it's in our CI somewhere09:50
b1airoI can take that as an action to share09:50
zz9pzzaBut that kind of thing will not catch new issues that arise.09:50
oneswigb1airo: sure that would be helpful09:50
*** e0ne has quit IRC09:50
verdurinzz9pzza: yes, that was my thought09:51
zz9pzzaWhich cloudforms could in theory09:51
b1airozz9pzza: true, but we require "Contributed" images to be updated on a rolling basis09:51
*** e0ne has joined #openstack-meeting09:52
oneswigzz9pzza: I guess the hope is to catch the misuse of a compromised system.  The university network watches for this.  I guess it's all layers09:52
zz9pzzabut if I have a system that has been up for a month...09:52
daveholland@b1airo do you expire or time-limit instances made from one of those images? can imagine a long-lived instance being vulnerable to a newly-announced bug09:53
b1airoOh sure. We do vulnerability scanning too09:53
davehollandJOOI what is the time limit? we are looking to host "pets" which could be around for months09:53
oneswigdaveholland: indeed.  If the managed infrastructure is updated immediately, what equivalent can be done to shore up user cloud instances09:54
*** sambetts|afk is now known as sambetts09:55
*** Julien-zte has quit IRC09:55
oneswigAh, we are short on time.  Any more to add here?09:56
oneswigI think the different strategies are all valuable, great suggestions thanks everyone09:57
davehollandjust a quick comment about user education :) this week I found someone who thought he had to enable ssh inbound to make ssh outbound work09:57
verdurinWorth talking to CERN people - when I was active in CMS, there was a lot of discussions about these sorts of security issues, e.g. with long lasting instances09:57
daveholland(actually it wasn't ssh in particular but a misunderstanding about port number at each end of a TCP connection)09:58
priteauoneswig: unrelated to the current topic, but any news about
b1airoThanks all. I think all this warrants some ML threads too...10:00
oneswigverdurin: good point, and it's a general issue not just for research computing10:00
verdurinBye all10:00
oneswigpriteau: no, oddly - I'll make a note to chase10:00
oneswigthanks everyone, out of time10:00
*** openstack changes topic to "OpenStack Meetings ||"10:01
openstackMeeting ended Wed Jun 21 10:01:00 2017 UTC.  Information about MeetBot at . (v 0.1.4)10:01
openstackMinutes (text):
priteauThanks everyone, bye!10:01
*** dbecker has quit IRC10:01
oneswigbon appetite b1airo!10:02
*** rossella_ has quit IRC10:02
*** alexchadin has quit IRC10:02
*** nidhi has joined #openstack-meeting10:05
*** henrynash has quit IRC10:06
*** slaweq has joined #openstack-meeting10:06
*** nidhi has quit IRC10:08
*** esberglu has joined #openstack-meeting10:08
*** f13o has quit IRC10:09
*** yamamoto_ has joined #openstack-meeting10:09
*** toscalix has joined #openstack-meeting10:11
*** slaweq has quit IRC10:11
*** bobmel has joined #openstack-meeting10:11
*** salv-orl_ has joined #openstack-meeting10:12
*** yamamoto has quit IRC10:13
*** esberglu has quit IRC10:13
*** salv-orlando has quit IRC10:14
*** caowei has quit IRC10:15
*** bobmel has quit IRC10:16
*** gongysh has quit IRC10:16
*** rossella_ has joined #openstack-meeting10:17
*** f13o has joined #openstack-meeting10:23
*** salmantoor has quit IRC10:23
*** oneswig has quit IRC10:26
*** raildo has joined #openstack-meeting10:27
*** daveholland has quit IRC10:28
*** toscalix_ has joined #openstack-meeting10:28
*** toscalix_ has quit IRC10:29
*** toscalix has quit IRC10:30
*** yangyape_ has quit IRC10:30
*** yamamoto_ has quit IRC10:30
*** yamamoto has joined #openstack-meeting10:32
*** slaweq has joined #openstack-meeting10:32
*** yamamoto has quit IRC10:33
*** SerenaFeng has quit IRC10:36
*** slaweq has quit IRC10:37
*** raildo has quit IRC10:38
*** SerenaFeng has joined #openstack-meeting10:38
*** edmondsw has joined #openstack-meeting10:39
*** zhonghua has quit IRC10:40
*** zhonghua has joined #openstack-meeting10:41
*** epico has quit IRC10:41
*** yamamoto has joined #openstack-meeting10:43
*** edmondsw has quit IRC10:45
*** slaweq has joined #openstack-meeting10:48
*** jkilpatr has quit IRC10:49
*** SerenaFeng has quit IRC10:50
*** yangyapeng has joined #openstack-meeting10:51
*** SerenaFeng has joined #openstack-meeting10:51
*** e0ne has quit IRC10:52
*** slaweq has quit IRC10:52
*** yamamoto has quit IRC10:54
*** bkopilov has quit IRC10:56
*** ericyoung has joined #openstack-meeting10:57
*** yangyapeng has quit IRC10:59
*** janki has joined #openstack-meeting10:59
*** pnavarro has quit IRC11:01
*** torgomatic has quit IRC11:01
*** slaweq has joined #openstack-meeting11:03
*** bobmel has joined #openstack-meeting11:04
*** andreas_s has quit IRC11:07
*** rossella__ has joined #openstack-meeting11:07
*** f13o has quit IRC11:07
*** jkilpatr has joined #openstack-meeting11:08
*** slaweq has quit IRC11:08
*** bobmel has quit IRC11:08
*** rossella_ has quit IRC11:10
*** beekhof has joined #openstack-meeting11:12
*** SerenaFeng has quit IRC11:14
*** gongysh has joined #openstack-meeting11:17
*** jbadiapa_ has quit IRC11:19
*** f13o has joined #openstack-meeting11:20
*** yamamoto has joined #openstack-meeting11:24
*** yamamoto has quit IRC11:28
*** jbadiapa_ has joined #openstack-meeting11:33
*** yangyapeng has joined #openstack-meeting11:36
*** yangyapeng has quit IRC11:41
*** yangyapeng has joined #openstack-meeting11:41
*** bzhao has quit IRC11:47
*** dmacpher has quit IRC11:48
*** bzhao has joined #openstack-meeting11:48
*** yamamoto has joined #openstack-meeting11:54
*** slaweq has joined #openstack-meeting11:55
*** e0ne has joined #openstack-meeting11:56
*** slaweq has quit IRC11:59
*** zz_dimtruck is now known as dimtruck12:00
*** dmacpher has joined #openstack-meeting12:02
*** litao__ has quit IRC12:04
*** rfolco has joined #openstack-meeting12:04
*** bobmel has joined #openstack-meeting12:05
*** noslzzp has joined #openstack-meeting12:05
*** ssalagame has joined #openstack-meeting12:05
*** kylek3h has quit IRC12:07
*** bobmel has quit IRC12:09
*** dimtruck is now known as zz_dimtruck12:10
*** edmondsw has joined #openstack-meeting12:21
*** dmacpher has quit IRC12:23
*** bauzas has quit IRC12:26
*** alexchadin has joined #openstack-meeting12:30
*** b1airo has quit IRC12:31
*** bkopilov has joined #openstack-meeting12:32
*** zz9pzza has quit IRC12:33
*** zz9pzza has joined #openstack-meeting12:34
*** jamesdenton has joined #openstack-meeting12:34
*** efried has joined #openstack-meeting12:34
*** dmacpher has joined #openstack-meeting12:35
*** dprince has joined #openstack-meeting12:35
*** zhhuabj has quit IRC12:39
*** efried has quit IRC12:39
*** kylek3h has joined #openstack-meeting12:40
*** ssalagame has quit IRC12:49
*** eharney has joined #openstack-meeting12:51
*** zhhuabj_ has joined #openstack-meeting12:52
*** dbecker has joined #openstack-meeting12:54
*** salv-orl_ has quit IRC12:54
*** mriedem has joined #openstack-meeting12:56
*** mdovgal has quit IRC12:56
*** salv-orlando has joined #openstack-meeting12:56
*** andreas-f has quit IRC12:57
*** salv-orlando has quit IRC12:57
*** pewp has quit IRC12:57
*** zhhuabj_ has quit IRC12:58
*** salv-orlando has joined #openstack-meeting12:58
*** jprovazn has joined #openstack-meeting12:59
*** jamesdenton has quit IRC13:00
*** trozet_ is now known as trozet13:00
*** jamesdenton has joined #openstack-meeting13:01
*** andreas-f has joined #openstack-meeting13:02
*** pewp has joined #openstack-meeting13:04
*** f13o has quit IRC13:06
*** slaweq has joined #openstack-meeting13:06
*** gouthamr has joined #openstack-meeting13:07
*** salv-orlando has quit IRC13:08
*** askb has quit IRC13:10
*** slaweq has quit IRC13:11
*** salv-orlando has joined #openstack-meeting13:12
*** baoli has joined #openstack-meeting13:12
*** pradk has quit IRC13:12
*** dane_ has joined #openstack-meeting13:12
*** dmacpher has quit IRC13:13
*** baoli has quit IRC13:16
*** thorst has joined #openstack-meeting13:16
*** zhhuabj_ has joined #openstack-meeting13:17
*** f13o has joined #openstack-meeting13:18
*** haruki has joined #openstack-meeting13:19
*** esberglu has joined #openstack-meeting13:19
*** haruki has quit IRC13:19
*** baoli has joined #openstack-meeting13:20
*** thorst has quit IRC13:22
*** VW has quit IRC13:23
*** VW has joined #openstack-meeting13:24
*** bauzas has joined #openstack-meeting13:24
*** esberglu has quit IRC13:24
*** dmacpher has joined #openstack-meeting13:25
*** VW has quit IRC13:28
*** dbecker has quit IRC13:31
*** eric_young has joined #openstack-meeting13:31
*** slaweq has joined #openstack-meeting13:32
*** rossella__ has quit IRC13:32
*** thorst has joined #openstack-meeting13:32
*** ericyoung has quit IRC13:33
*** cleong has joined #openstack-meeting13:34
*** esberglu has joined #openstack-meeting13:35
*** slaweq has quit IRC13:36
*** lhx has joined #openstack-meeting13:38
*** lhx is now known as Guest7924213:38
*** xyang1 has joined #openstack-meeting13:38
*** pnavarro has joined #openstack-meeting13:38
*** gongysh has quit IRC13:39
*** Fdaisuke has joined #openstack-meeting13:40
*** bobh has joined #openstack-meeting13:41
*** sgrasley1_ has joined #openstack-meeting13:42
*** abramley has quit IRC13:43
*** abramley has joined #openstack-meeting13:44
*** bobh has quit IRC13:45
*** dbecker has joined #openstack-meeting13:45
*** abramley has quit IRC13:46
*** diablo_rojo has joined #openstack-meeting13:47
*** abramley has joined #openstack-meeting13:47
*** rossella__ has joined #openstack-meeting13:48
*** salv-orlando has quit IRC13:49
*** pnavarro has quit IRC13:49
*** VW has joined #openstack-meeting13:50
*** awaugama has joined #openstack-meeting13:51
*** VW has quit IRC13:51
*** VW has joined #openstack-meeting13:51
*** VW has quit IRC13:51
*** VW has joined #openstack-meeting13:52
*** lhx_ has joined #openstack-meeting13:54
*** kgiusti has joined #openstack-meeting13:54
*** zz_dimtruck is now known as dimtruck13:54
*** pchavva has joined #openstack-meeting13:55
*** Guest79242 has quit IRC13:57
*** rossella__ has quit IRC13:59
*** rhochmuth has joined #openstack-meeting13:59
*** adisky__ has quit IRC13:59
*** jgu has joined #openstack-meeting13:59
*** witek has joined #openstack-meeting14:00
rhochmuth#startmeeting monasca14:00
openstackMeeting started Wed Jun 21 14:00:34 2017 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: monasca)"14:00
openstackThe meeting name has been set to 'monasca'14:00
*** haruki has joined #openstack-meeting14:00
*** toscalix has joined #openstack-meeting14:01
rhochmuthhi witek14:01
*** henrynash has joined #openstack-meeting14:01
rhochmuthagenda for todaty is posted at,
*** abramley has quit IRC14:01
rhochmuthanyone at today's meeting14:01
rhochmuthlooks like you made it back from vacation, witek14:02
*** shinya_kwbt has joined #openstack-meeting14:02
*** henrynash has quit IRC14:02
witekyes, full of energy :)14:02
*** henrynash has joined #openstack-meeting14:03
rhochmuthAgenda for Wednesday June 21 2017 (14:00 UTC)14:03
rhochmuth1.2nd opinion needed -> [tomasz: everything looks ok from my POV, tested successfully and just need 2nd pair of eyes to confirm and accept or just +1]14:03
rhochmuth2. - is it acceptable to have gate tests against python-monascaclient@master or monascaclient change ?14:03
rhochmuth3. - needs reviews and opinion. This is a the same aproach to install monasca-api in devstack just like in monasca-log-api.  Current installation has a problems because monasca-api is not starting locally. wrong change is installed inside of the virtualenv.14:03
rhochmuth2.Should we disable bug tracking with Launchpad?14:03
*** abramley has joined #openstack-meeting14:03
*** koji has joined #openstack-meeting14:03
rhochmuth#topic Ceph cluster plugin14:04
*** openstack changes topic to "Ceph cluster plugin (Meeting topic: monasca)"14:04
witekTomasz has tested it, looks OK for him14:05
rhochmuthso, should we merge now14:05
witekwould be nice to have someone else to have a look14:05
rhochmuthi can take a quick look and merge if that works for you14:05
*** alexchadin has quit IRC14:05
*** bobmel has joined #openstack-meeting14:06
*** pnavarro has joined #openstack-meeting14:06
*** henrynash has quit IRC14:06
rhochmuth#topic Integrate with newer client14:06
*** openstack changes topic to "Integrate with newer client (Meeting topic: monasca)"14:06
rhochmuthSame on this one too i guess14:06
witekthere is more14:06
witekthe function install_client_depends_on changes the constraints of installed package14:07
*** slaweq has joined #openstack-meeting14:07
witekit allows to take the master of let say, pyton-monascaclient in that case, instead of the last tag14:08
witekit also allows to use Depends-On: tag for unit tests14:09
*** toscalix has quit IRC14:09
witektill now, always last tag was used, and Depends-On tag was neglected14:09
witekstandard OpenStack procedure is to take the last tag, but we have many cross-deps between repos14:10
witekso I think the change goes in right direction14:11
rhochmuthok, sounds like a good improvement14:11
*** bobmel has quit IRC14:11
rhochmuth#topic Adjust monasca-api installation14:11
*** openstack changes topic to "Adjust monasca-api installation (Meeting topic: monasca)"14:11
*** toscalix has joined #openstack-meeting14:12
witekthe previous change should be merged together with other osc-lib changes14:12
*** samP has joined #openstack-meeting14:12
*** slaweq has quit IRC14:12
*** dimtruck is now known as zz_dimtruck14:12
*** litao__ has joined #openstack-meeting14:13
witekto the next one, Artur has refactored installing monasca-api in devstack14:13
*** sridharg has quit IRC14:13
*** toscalix has quit IRC14:13
witekmost importantly, service configuration files are generated by devstack14:14
witekand monasca-api is installed without virtualenv14:14
rhochmuthok, i'll look at that one too14:14
*** felipemonteiro has joined #openstack-meeting14:14
rhochmuththese all seem like good changes to me14:15
witekwe have observed that sometimes old version of the package has been installed in venv14:15
rhochmuthalthough, we are spending a lot of time refactoring stuff, rather than developing new features14:15
witekand couldn't really tell why14:15
*** felipemonteiro_ has joined #openstack-meeting14:15
rhochmuthi feel like the last 4-5 months has been on polishing stuff14:16
rhochmuthmeanwhile the core is being neglected14:16
rhochmuthbut, i guess that is another topic14:16
*** pradk has joined #openstack-meeting14:16
rhochmuth#topic Should we disable bug tracking with Launchpad?14:17
*** openstack changes topic to "Should we disable bug tracking with Launchpad? (Meeting topic: monasca)"14:17
witekI have noticed that there are still new bugs being filed to LP14:17
witekI have talked to SB team and they have run migration script again today to update the stuff14:18
*** Julien-zte has joined #openstack-meeting14:18
rhochmuthif we can shut it down14:19
witekthere are still some cross-project bugs which we will kind of 'lose' if we switch of LP14:19
rhochmuththen now would be a good time14:19
*** felipemonteiro has quit IRC14:19
witekI also think it is a good idea14:19
*** dmacpher has quit IRC14:20
*** hongbin has joined #openstack-meeting14:20
witekand we should update/add information about bug tracking location14:20
rhochmuthin the wiki and landing page14:21
witekwhich is the landing page? :)14:21
rhochmuthi was thinking
witekwe could also add it to README in repos14:22
rhochmuththat would be good too14:22
rhochmuthso, i can update the launchpad and wiki14:24
rhochmuthand we can get the repos updated14:24
witekcool, thanks14:24
rhochmuthso, i guess that is it for today14:25
rhochmuthjust you and me i guess14:25
witekprivate session14:25
rhochmuthnot exactly standing room only14:25
rhochmuthunless you are standing right now14:25
rhochmuthshould we call it a day14:25
*** jamesmcarthur has joined #openstack-meeting14:25
witekI don't have anything else14:26
rhochmuthok, i'll look into those reviews and update the wiki and launchpad14:26
rhochmuthif you can look into shutting launchpad bugs down that woudl be great14:26
*** prateek has quit IRC14:26
witekthank you, bye14:26
rhochmuthok, thanks, see you next week14:27
*** f13o has quit IRC14:27
witekyes, I can do it right now14:27
harukithx, bye14:27
*** openstack changes topic to "OpenStack Meetings ||"14:27
openstackMeeting ended Wed Jun 21 14:27:35 2017 UTC.  Information about MeetBot at . (v 0.1.4)14:27
openstackMinutes (text):
*** haruki has quit IRC14:27
*** koji has quit IRC14:27
*** zz_dimtruck is now known as dimtruck14:28
*** sgrasley1_ has quit IRC14:29
*** shinya_kwbt has left #openstack-meeting14:31
*** rfolco has quit IRC14:31
*** Julien-zte has quit IRC14:32
*** Julien-z_ has joined #openstack-meeting14:32
*** dbecker has quit IRC14:33
*** slaweq has joined #openstack-meeting14:33
*** dmacpher has joined #openstack-meeting14:33
*** Fdaisuke has quit IRC14:34
*** dbecker has joined #openstack-meeting14:36
*** qwebirc29439 has joined #openstack-meeting14:36
*** Julien-z_ has quit IRC14:37
*** gouthamr has quit IRC14:37
*** rfolco has joined #openstack-meeting14:37
*** qwebirc29439 has quit IRC14:37
*** gouthamr has joined #openstack-meeting14:37
*** slaweq has quit IRC14:38
*** ralonsoh has quit IRC14:40
*** markvoelker has quit IRC14:40
*** anilvenkata has quit IRC14:40
*** f13o has joined #openstack-meeting14:40
*** jamesmcarthur has quit IRC14:41
*** jamesmcarthur has joined #openstack-meeting14:41
*** emagana has joined #openstack-meeting14:42
*** janki has quit IRC14:43
*** Julien-zte has joined #openstack-meeting14:44
*** hieulq_ has joined #openstack-meeting14:44
*** jamesmcarthur has quit IRC14:46
*** bastafidli_ has joined #openstack-meeting14:46
*** msimonin has joined #openstack-meeting14:53
*** ansmith has joined #openstack-meeting14:54
*** marst has joined #openstack-meeting14:55
*** bklei_ has joined #openstack-meeting14:56
*** awaugama has quit IRC14:56
*** markvoelker has joined #openstack-meeting14:57
*** ykatabam has quit IRC14:57
*** bklei__ has joined #openstack-meeting14:58
*** bklei_ has quit IRC14:58
*** rcherrueau has joined #openstack-meeting14:59
*** slaweq has joined #openstack-meeting14:59
*** awaugama has joined #openstack-meeting14:59
*** lucas_ has joined #openstack-meeting14:59
*** pbressan has joined #openstack-meeting15:00
*** armstrong has joined #openstack-meeting15:01
*** parnexius has joined #openstack-meeting15:01
*** Adadzd has joined #openstack-meeting15:02
msimonin#startmeeting fog-edge-massively-distributed-clouds15:02
openstackMeeting started Wed Jun 21 15:02:05 2017 UTC and is due to finish in 60 minutes.  The chair is msimonin. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: fog-edge-massively-distributed-clouds)"15:02
openstackThe meeting name has been set to 'fog_edge_massively_distributed_clouds'15:02
msimonin#chair parnexius15:02
openstackCurrent chairs: msimonin parnexius15:02
msimonin#topic roll call15:02
*** openstack changes topic to "roll call (Meeting topic: fog-edge-massively-distributed-clouds)"15:02
parnexiusHello everyone15:02
msimoninHello folks !15:02
msimoninLet's see who's around :)15:03
*** emagana has quit IRC15:03
*** slaweq has quit IRC15:03
parnexiusAdrien has posted an Agenda for the meeting but will not be joining us. Mat and I will chair today15:04
msimonintoday we are at line 81015:04
msimoninFeel free to add your name15:05
msimoninIt Seems we can start15:05
*** thorst has quit IRC15:05
msimonin#topic announcements15:05
*** openstack changes topic to "announcements (Meeting topic: fog-edge-massively-distributed-clouds)"15:05
*** efried has joined #openstack-meeting15:06
msimoninAs parnexius said _ad_rien_ is not available today15:06
*** Adadzd has quit IRC15:06
msimoninso I'll try to transmit his announcements :)15:06
*** bobmel has joined #openstack-meeting15:06
*** tiger_lily has joined #openstack-meeting15:07
msimoninFirst thing is that we are in touch wit ESTI MEC15:07
*** rcernin has quit IRC15:07
*** ralonsoh has joined #openstack-meeting15:07
msimoninThey have some architecture work done there15:07
msimoninand we are now currently discussing with them to see if OpenStack can be used in their architecture15:08
msimoninat least identify some building blocks15:08
parnexiusGreat idea. I have started using some of their material in the use case development.15:09
parnexiusMore on that later.15:09
msimonincool !15:09
*** yamahata_ has joined #openstack-meeting15:09
msimoninI think we can move to the next topic15:10
*** jamesmcarthur has joined #openstack-meeting15:10
*** banhgao has joined #openstack-meeting15:10
*** david-lyle has joined #openstack-meeting15:10
msimonin#topic AMQP alternatives15:10
*** openstack changes topic to "AMQP alternatives (Meeting topic: fog-edge-massively-distributed-clouds)"15:10
*** oidgar has quit IRC15:10
msimoninkgiusti ansmith any updates ?15:10
*** unicell has joined #openstack-meeting15:11
kgiustikolla work is progressing nicely15:11
kgiustiandy and I have started an epad to define tests of the messaging bus15:11
*** bobmel has quit IRC15:11
kgiustilink in epad15:11
*** thorst has joined #openstack-meeting15:12
kgiustimostly focused on messaging testing15:12
msimoninthanks for this proposal kgiusti15:12
kgiustiat this point.15:12
*** unicell1 has quit IRC15:12
*** pnavarro has quit IRC15:12
kgiusticloud level messaging test tools explored a bit15:12
*** pcaruana has quit IRC15:12
kgiustibut really need help with defining the openstack cloud deployment arch to help define the best messaging topology to tests15:13
kgiustierr - "most appropriate messaging topology" for the cloud deployment15:13
msimoninby topology: you mean where to put the router and what links between them ?15:14
kgiustiso please weigh in if you have any suggestions for messaging-oriented tests, failure scenarios, etc.15:14
kgiustimsimonin: yeah - the optimal distribution of routers "under" the cloud15:14
parnexiuskgiusti: which link is that in the epad (the one on strawman proposal)15:14
kgiustiparnexius: line 83415:15
*** henrynash has joined #openstack-meeting15:15
parnexiuskgiusti: by router, you mean message router (like rabbitmq instances).15:15
*** Sukhdev has joined #openstack-meeting15:16
*** thorst has quit IRC15:16
rcherrueaukgiusti: I guess, we should test several topologies15:16
kgiustiparnexius: in general yes, but that really depends on the tech used (rabbitmq/zeromq/router)15:16
rcherrueauI mean, putting router on all physical nodes vs router on one leader node15:16
kgiustifor example: rabbitmq would be limited to clustering for scale15:16
parnexiuskgiusti: so if I understand the point right a router topology would include whether the router is deployed in the edge node, or only in a central location.15:17
kgiustircherrueau: that's one scenario for the router, yes15:17
*** dbecker has quit IRC15:17
kgiustiparnexius: yes - the router model is the most flexible,15:17
rcherrueaumeshing is also important I guess. Going with a full mesh between rooters is not the same thing than going with a star mesh15:17
kgiustiand thus most complex - we need to consider redundancy, locality of traffic, etc15:17
kgiustircherrueau: right - for example, how many network or router failures should be tolerated?15:18
parnexiusIs Dynamic routing available in these solutions?15:18
rcherrueauI don't know, I much as OpenStack tolerate no :)15:19
rcherrueauas much as*15:19
parnexiusSo High-Availability would need to be provided by the solution (RabbitMQ, ZeroMQ, ....)15:19
kgiustiparnexius: yes - all routing is dynamic15:19
parnexiuskgiusti: can you please elaborate?15:20
*** emagana has joined #openstack-meeting15:20
parnexiusWhat would happen if a router on a node becomes unreachable?15:20
*** bklei__ has quit IRC15:20
kgiustiparnexius: sure - regarding dynamic routing I'm assuming you mean re-routing around network failures15:20
kgiustiparnexius: if the clients have a fail-over router configured, that will be tried in recovery.15:21
parnexiusOK! I would call that static. but you are right it is a little dynamic.15:21
kgiustiparnexius: if there are redundant routers on the node (hot standby) that would take over (assuming redundant network paths)15:22
*** bklei has joined #openstack-meeting15:22
kgiustiparnexius: topology is one factor, the other is over-provisioning for throughput15:23
*** fnaval_ has joined #openstack-meeting15:23
kgiustiparnexius: eg, if we lose a rabbit in a cluster, how does that reduce overall capacity?15:23
msimoninI think we need time to get through what is written on the epad15:23
kgiustimsimonin: yep15:24
msimoninand give you feedback15:24
kgiustimsimonin: and questions! :)15:24
*** slaweq has joined #openstack-meeting15:24
msimonin#info kgiusti share a premilinary "message plane load testing"15:24
*** emagana has quit IRC15:25
msimonin(just recording some stuffs :) )15:25
msimoninCan we iterate on the mailing list ?15:25
*** Adadzd has joined #openstack-meeting15:25
msimoninand/or direclty on the document until next meeting15:25
kgiustimsimonin: yes - I did send an email just before the meeting regarding this15:25
parnexiusmsimonin: Good Point. We shoudl all take action to be more active outside of IRC sessions.15:26
kgiustimsimonin: so folks not present can get the epad15:26
*** Adadzd has quit IRC15:27
*** emagana has joined #openstack-meeting15:27
msimoninkgiusti ansmith anything else on qpid dispatch router ?15:27
kgiustiI'm good - andy?15:27
parnexiusShould we move to next topic then15:28
*** slaweq has quit IRC15:29
msimoninright parnexius :)15:29
msimonin*was reading the ml :) *15:29
msimoninnext topic15:29
msimonin#topic cockroachdb15:29
*** openstack changes topic to "cockroachdb (Meeting topic: fog-edge-massively-distributed-clouds)"15:29
msimoninSo I would say that similarly to the work on the messaging layer15:30
msimoninthere has been a mail on the ml about using cockroadb as an alternative backend for keystone15:30
msimoninCockroachDB could be very interesting also in the context of a massively distributed cloud15:31
*** sudipto has joined #openstack-meeting15:31
*** sudipto_ has joined #openstack-meeting15:31
parnexiusWould that mean the database is replicated to all edge nodes?15:32
serverascodecool will have to read through those notes15:32
*** f13o has quit IRC15:32
msimoninwe had a meeting with some cockroachdb folks last week15:32
msimonina very first contact15:32
msimoninparnexius:  the same as qpid the topology will need to be defined15:33
rcherrueauparnexius: not necessarily. With cockroachdb, you can tell which tuples should be replicated and which should not.15:33
parnexiusBut this is not an opensource solution!15:34
rcherrueauno, this is15:34
rcherrueauSpanner is proprietary, CockroachDB is opensource15:35
* rcherrueau check the licence 15:35
parnexiusOK. I see it now.15:35
msimoninSo at Inria we are very much interesting in evaluating this15:35
msimoninbut we'll need support !15:36
*** lpetrut has quit IRC15:36
*** thorst has joined #openstack-meeting15:36
rcherrueauparnexius: Apache License, Version 2.0, for community15:36
msimoninChanging the DB backend here we'll require to resurect the postgresql driver, choose a service (keystone, nova, glance …) to make primary evaluation15:37
msimoninand so on15:37
parnexiusCeilometer ?15:37
msimoninparnexius:  yes it could be as well15:38
*** felipemonteiro_ has quit IRC15:38
msimoninso there's a lot of exciting stuff to do15:38
msimoninso my question is15:38
msimoninhow to make people as excited as I am about this ?15:38
serverascodethat's a good question, there will be a fair amount of pushback on using cockroachdb15:39
parnexiusmsimonin: why are you excited?15:39
serverascodemostly I think around who will actually do the work in terms of the openstack testing system15:40
msimoninparnexius: to speak roughly cockroach is noSQL with ACID properties15:40
*** thorst has quit IRC15:40
parnexiusand Why is ACID important to our usecases? would performance be more important?15:41
*** awaugama has quit IRC15:41
*** Rockyg has joined #openstack-meeting15:41
serverascodeI would imagine a lot of code would have to be rewritten if the db were not ACID15:42
msimoninI should add that cockroach is compatible with sqlalchemy15:43
rcherrueauparnexius: ACID or not, Cockroach speaks Postgres protocol. That means -- in principle -- using it would be as simple as configuring oslo.db to connect to Cockroach15:43
*** artom has quit IRC15:43
*** awaugama has joined #openstack-meeting15:43
rcherrueauparnexius: The thing is, you have to implement ACID properties to implement pgsql protocol15:44
*** ad_rien_ has joined #openstack-meeting15:45
msimoninTo conclude here15:45
parnexiusGreat discussion: some requirements are popping up here.15:45
*** caboucha has joined #openstack-meeting15:45
*** jamesdenton has quit IRC15:45
msimoninparnexius: yes ?15:46
parnexiusPerformance, ACID, noSQL, pgsql15:46
*** zengchen has quit IRC15:46
*** zengchen has joined #openstack-meeting15:47
parnexiuswe need to get our heads together and define what is important to massively distributed.15:47
*** jamesdenton has joined #openstack-meeting15:47
*** vishnoianil has joined #openstack-meeting15:47
msimoninright parnexius15:47
parnexiusplease conclude.15:48
rcherrueauparnexius: It would be cool is someone can look at Keystone db API/db requests and says which parts require string consistency (ACID)15:48
rcherrueaustrong consistency*15:49
*** gyee has joined #openstack-meeting15:49
msimoninI'll take an action on this15:49
msimoninI'll ping keystone guys15:49
msimonin#action msimonin get in touch with keystone about cockroach15:49
*** dane_leblanc has joined #openstack-meeting15:49
parnexiusyou should look at Nova too.15:49
*** tmorin has quit IRC15:49
rcherrueauIf none require strong consistency, then we can go with NoSQL -- but this means, we have to rewrite the db part of Keystone15:50
parnexiuskeystone db tends to be centralized... while nova can be distributed.15:50
msimoninthe step after will be nova15:50
msimoninthe initial idea was from keystone15:50
parnexiusMy point is we should focus on the aspects that are more relevant to Massively distributed.15:50
serverascodehow can nova be distributed? you mean cells?15:51
*** wewe0901 has joined #openstack-meeting15:51
msimonin#topic use-case definitions/dicussions15:51
*** openstack changes topic to "use-case definitions/dicussions (Meeting topic: fog-edge-massively-distributed-clouds)"15:51
parnexiusI mean that nova has components in each cells or edge nodes..... While keystone is usually central to a region ar the master cell.15:51
parnexiusGreat transition.15:51
msimoninparnexius: serverascode: let's see what keystone guy had in mind when proposing cockroach15:52
parnexiusAbout Use cases.15:52
msimoninyes go on :)15:52
rcherrueauparnexius: In multi-region scenarios, some also put keystone in each region and make it consistent using galera15:52
parnexiusI have uploaded some slides on goold doc. They touch on this very topic.15:52
Nil_very bad experience with galera cluster. MySQL nbd better experience but requiere very services and complicated.15:53
*** dane_ has quit IRC15:53
parnexiusI will follow kgiusi example and send in an email.15:54
serverascodemany people have run galera sucessfully, and that is where some pushback will come from15:54
rcherrueauNil_: I have no doubt on that :)15:54
msimoninparnexius:  +1 for the ml15:54
serverascodebut the most I've seen anyone mention is 12 regions with a shared galera over all of them15:54
*** salv-orlando has joined #openstack-meeting15:55
serverascodewhere was hopefully with something like cockroachdb we could do many more regions15:55
parnexiusI was hoping that I could get some input from the team. and the discussion on galera and coackroach is relevant.15:55
*** henrynash has quit IRC15:55
*** gyee has quit IRC15:55
msimonintoo many interesting topics here :)15:55
parnexiusLet's move this discussion to the mailing list.15:55
Nil_maybe CockroachDB, i read gitup and very interesting...15:55
rcherrueauserverascode: Galera is not an option in our usecases because of the WAN latency15:55
*** henrynash has joined #openstack-meeting15:56
*** artom has joined #openstack-meeting15:56
msimoninparnexius: ok15:56
serverascodeI'm just letting you know the pushback we will get :)15:56
*** salv-orlando has quit IRC15:56
parnexiusis everyone interested in this discussion, or should we create a subteam.15:56
*** salv-orlando has joined #openstack-meeting15:57
msimoninactually I think we should move this discussion in the beginning next time :)15:57
*** Sukhdev_ has joined #openstack-meeting15:57
*** ralonsoh has quit IRC15:57
*** henrynash has quit IRC15:57
parnexiusMsimonin: please give me action to take discussion to ML and let's move to close the meeting.15:57
msimonin#action parnexius starts a thread on the ml about massively distributed use cases15:57
*** henrynash has joined #openstack-meeting15:58
msimoninWe have 2 min left :(15:58
msimonin#topic open discussion15:58
*** openstack changes topic to "open discussion (Meeting topic: fog-edge-massively-distributed-clouds)"15:58
pbressanjust leaving a question for next session, is discussion about how implement distributed UCs in terms of networking ?15:58
*** guyk has joined #openstack-meeting15:58
msimoninUCs ?15:58
pbressanml2/3, tricircle, etc ?15:58
*** markvoelker has quit IRC15:58
samPjust a quick intro.. from LCOO15:58
parnexiusUC = Use cases.15:58
msimoninkk :)15:59
samPHi, I’m Sampath from NTT, one of the persons driving Ext ream testing (Destructive Testing) in LCOO with  jamemcc15:59
*** markvoelker has joined #openstack-meeting15:59
msimoninsorry guys15:59
msimoninlet's try to iterate as much as possible between meetings15:59
msimoninon the ml for example15:59
*** diablo_rojo has quit IRC16:00
*** openstack changes topic to "OpenStack Meetings ||"16:00 time..+116:00
openstackMeeting ended Wed Jun 21 16:00:01 2017 UTC.  Information about MeetBot at . (v 0.1.4)16:00
openstackMinutes (text):
*** pbressan has quit IRC16:00
msimoninthanks all !16:00
jungleboyj#startmeeting Cinder16:00
openstackMeeting started Wed Jun 21 16:00:27 2017 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
*** slaweq has joined #openstack-meeting16:00
jungleboyjping dulek duncant eharney geguileo winston-d e0ne jungleboyj jgriffith thingee smcginnis hemna xyang1 tbarron scottda erlon rhedlind jbernard _alastor_ bluex karthikp_ patrickeast dongwenjuan JaniceLee cFouts Thelo vivekd adrianofr mtanino karlamrhein diablo_rojo jay.xu jgregor lhx_ baumann rajinir wilson-l reduxio wanghao thrawn01 chris_morrell watanabe.isao,tommylikehu mdovgal ildikov wxy viks ketonne abishop16:00
*** Apoorva has joined #openstack-meeting16:00
*** diablo_rojo has joined #openstack-meeting16:01
*** parnexius has quit IRC16:01
jungleboyjSean  has asked me to cover today.  :-)16:01
* smcginnis is not really here, will catch up later16:01
*** gnarld_ is now known as cFouts16:01
*** xyang2 has joined #openstack-meeting16:01
jungleboyjsmcginnis:  Is more here than expected.  ;-)16:02
jungleboyjOk, so it looks like we have a good group here to start with.16:02
jungleboyj#topic Announcements16:02
*** openstack changes topic to "Announcements (Meeting topic: Cinder)"16:02
*** tesseract has quit IRC16:03
jungleboyjThe usual reminder to please take a look at the review priority for the release:
*** rderose has joined #openstack-meeting16:03
jungleboyjsmcginnis:  and I went through the reviews from last month's bug smash and worked to get as many things merged as possible.16:04
*** gyee has joined #openstack-meeting16:04
*** msimonin has left #openstack-meeting16:04
*** rcherrueau has quit IRC16:04
diablo_rojojungleboyj, did our tagging bugs ahead of time help them out?16:04
*** kgiusti has left #openstack-meeting16:04
jungleboyjAlso went through all the spec tracking items and got them updated.16:05
jungleboyjdiablo_rojo:  I think that worked well.16:05
*** slaweq has quit IRC16:05
*** makowals has quit IRC16:05
jungleboyjdiablo_rojo:  I think it is a practice we should continue to do.  It looked like that was used as a starting point and then some other items were added.16:05
diablo_rojoCool, we will have to keep that in mind for tagging bugs. Might even want to consider a monthly bugsmash day like other projects do. I16:05
jungleboyjLast time I checked there were about 19 bugs that were addressed and closed.16:06
diablo_rojojungleboyj, jinx16:06
jungleboyjdiablo_rojo:  Jinx.  ;-)16:06
jungleboyjI have been trying to coordinate with smcginnis  once a month to go through and clean up bugs, etc.  So, yeah, we are on the same page there.16:06
jungleboyjI think people have been doing a good job of looking at reviews from what I have seen.  Thank you.16:07
*** aarefiev is now known as aarefiev_afk16:07
jungleboyjAlso, one other announcement, I marked all the proposed drivers that missed the Pike deadline with a -2 just so we don't accidentally merge anything there.16:08
* jungleboyj wasn't very popular for that.16:08
pewpjungleboyj (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. )16:08
jungleboyjSo, I think that was all I had for announcements.16:08
jungleboyj#topic Add new config option in volume driver class16:09
*** openstack changes topic to "Add new config option in volume driver class (Meeting topic: Cinder)"16:09
jungleboyjguyk:  You here?16:09
*** felipemonteiro has joined #openstack-meeting16:09
guykjungleboyj: yes16:09
jungleboyjTake it away.16:09
*** felipemonteiro_ has joined #openstack-meeting16:10
*** yamamoto_ has joined #openstack-meeting16:10
guykthis idea was proposed by Mike Perez in one of my patch. It is to create and use generic variable in the volume driver.16:10
geguileowhat kind of generic variable? r:-??16:11
guykAnd replace current and different config options used in the drivers16:11
lhx_guyk, what's the patch?16:11
geguileoso consolidation of configuration variables16:11
guykgeguileo: set the ip address and the port of the volume backend16:11
lhx_thx :)16:11
jungleboyjOh yes, we have had this discussion before.16:12
e0nein general, I like this idea16:12
*** hieulq_ has quit IRC16:12
*** salv-orl_ has joined #openstack-meeting16:12
geguileowouldn't it be better to support a list16:12
jgriffithgeguileo +116:13
e0negeguileo: +116:13
tommylikehuaddress list?16:13
*** banhgao has quit IRC16:13
geguileoproblem is that each address could have a different port16:13
geguileounlikely, but possible16:13
*** yamamoto has quit IRC16:13
*** felipemonteiro has quit IRC16:14
jungleboyjgeguileo:  So that is concern with the specific patch.16:14
jgriffithguyk just to be clear, we do already have this option FWIW16:14
jgriffithjust some don't use it16:14
jungleboyjI think we want to first address consolidation?16:14
*** bobmel has joined #openstack-meeting16:14
jungleboyjjgriffith:  ++16:14
jgriffithI'm sort of leary about introducing yet another "common" config option that people choose to not use16:14
*** thorst has joined #openstack-meeting16:14
*** abishop has joined #openstack-meeting16:14
guykjgriffith: yes some of the drivers don't use it because their backend doesn't use the san protocol so they rename it16:15
jgriffithif we do want a better name that's totally cool with me, but we should deprecate the old one and make it clear we expect it to be used16:15
jgriffithguyk there's no such thing as a 'san' protocol16:15
*** salv-orlando has quit IRC16:15
jgriffithguyk san just means it's an external device16:15
e0nejgriffith: +116:15
xyang2we have some "common" config options in that some drivers have been using:
jgriffithguyk and that you're accessing it via API on the 'san_ip' address16:15
guykjgriffith: yes, made a mistake16:16
jgriffithIn other words, it's the name game IMO; and if people want to play the name game that's fine by me; but be very clear that we already have a generic config option, this change should be a proposal to rename the existing san_ip16:17
*** artom has quit IRC16:17
*** winston-d has joined #openstack-meeting16:17
jgriffithwe'll still have the problem we have now of 1/2 the devices not using it though :)16:17
geguileojgriffith: I agree that we have 2 topics: name game and adoption16:18
geguileoFor adoption we could go through deprecating all individual configuration options16:18
geguileoto force drivers to update and consolidate16:18
geguileothough it may not be a very nice thing to do  :-16:18
jgriffithgeguileo yeah16:18
jgriffithgeguileo there's a broader effort there if we wanted to consider it16:19
*** thorst has quit IRC16:19
jgriffithgeguileo there's pretty extensive duplication of config options and exception classes...16:19
jgriffithanyway; that's a bit of a rat-hole probably :)16:19
diablo_rojoI think consolidation is a good idea16:19
jgriffithand geguileo yes, it's sort of not nice to do probably16:19
*** bzhao has quit IRC16:19
jgriffithbut I'm not a nice person.. so... there's that :)16:20
geguileoIt would be best if we could consolidate all/most of the common options16:20
jgriffithback to guyk 's patch though16:20
*** bzhao has joined #openstack-meeting16:20
geguileobut then we would really need to make sure they are adopted16:20
jgriffiththere is a broader question, but what do we want to do with his proposal to start with?16:20
jgriffithgeguileo +116:20
*** Julien-zte has quit IRC16:21
jgriffithbueller.... bueller....16:21
jungleboyjgeguileo:  I agree but that is going to require a large commitment and planning to implement it.16:21
geguileoshould we decide if we want to go with the deprecation of other options?16:21
*** egallen has quit IRC16:22
diablo_rojogeguileo, do it in waves? A few at a time?16:22
geguileobecause as I see it, without adoption this will be another san_ip16:22
jungleboyjgeguileo: Agreed.16:22
jgriffithdiablo_rojo the problem is that never seems to work for us :(16:22
jungleboyjjgriffith: ++16:22
jgriffithdiablo_rojo we set out to do things that way rather often and never finish16:22
geguileodiablo_rojo: yeah, but the only way to force it is if we deprecate the options16:22
diablo_rojojgriffith, touche16:22
jungleboyjI think it would need to be all at once.16:22
*** henrynash has quit IRC16:22
geguileodiablo_rojo: and then remove them16:22
jgriffithdiablo_rojo although it is an optimal approach (when it works)16:23
*** henrynash has joined #openstack-meeting16:23
diablo_rojoSo deprecating  few at a time is not a good idea?16:23
jgriffithkeep in mind you have to deal with upgrades too16:23
winston-dit's migration from individual cfg opts to common opts instead of adoption16:23
geguileodiablo_rojo: I would go with deprecating them all in one patch16:23
diablo_rojoHow many approx need to be deprecated?16:23
diablo_rojogeguileo, that works too :)16:23
winston-dadoptions sounds like you had a choice of not to16:23
jgriffithwinston-d good point!16:23
winston-dbut it seems not adopting is not allowed here.16:24
jungleboyjgeguileo:  ++16:24
jgriffithso here's an excercise for folks that are interested... generate a current sample.conf16:24
geguileowinston-d: if we want this to be really usefull yeah, it wouldn't be optional16:24
jungleboyjgeguileo:  Agreed.16:24
*** jamesmcarthur has quit IRC16:25
diablo_rojogeguileo, +116:25
geguileoso we agree to force the migration to common config options?16:25
cFoutsDoes the upgrade mean that currently installed cinder.conf files will need to be updated manually?16:25
jungleboyjjgriffith:  I think I know where you are going.16:25
*** jamesmcarthur has joined #openstack-meeting16:25
jgriffithjungleboyj :)16:25
jungleboyjcFouts: I think it might.16:25
diablo_rojogeguileo, yes?16:25
winston-dgeguileo: i agree.16:25
jgriffithcFouts yup, that's the problem16:25
xyang2to support backward compatibility, the old options will have to be supported for many releases16:26
cFoutsyeah, it is16:26
jungleboyjgeguileo:  I don't want to go that far yet.16:26
*** egallen has joined #openstack-meeting16:26
jungleboyjLet me make a proposal before we charge forward.16:26
winston-dxyang2: yeah, :(16:26
jungleboyjI think we need to do what jgriffith started to propose.16:26
jungleboyjGenerate a config file and take inventory of the options.16:27
xyang2so we'll end up with more options than we wanted16:27
jungleboyjSee how many options this may actually impact.16:27
winston-dcfg opts is also considered as  user-facing interface16:27
*** henrynash has quit IRC16:27
jungleboyjOnce we have an idea of the impact we can make a plan going forward.16:27
*** thorst has joined #openstack-meeting16:27
*** thorst has quit IRC16:27
xyang2winston-d: +116:27
jungleboyjDeprecate the old ones.  Do a release accordingly.16:28
*** henrynash has joined #openstack-meeting16:28
jungleboyjDocument the upgrade path to help people.16:28
Nil_this metting , today it's running...16:28
*** sambetts is now known as sambetts|afk16:28
jungleboyjThoughts on this proposal?16:28
*** yamahata_ has quit IRC16:28
*** henrynash has quit IRC16:28
*** ricolin has quit IRC16:28
xyang2jungleboyj: do you think people read document?:)16:28
xyang2jungleboyj: you'll get a support call first:)16:29
*** unicell1 has joined #openstack-meeting16:29
e0nexyang2: the will once something will fail16:29
lhx_so all san options will be deprecate too?16:29
jungleboyjxyang2:  True enough.16:29
jungleboyjlhx_:  That scares me.  A lot of people use that.16:29
*** jamesmcarthur has quit IRC16:29
*** unicell has quit IRC16:30
jungleboyjWell, that stopped the discussion.16:31
jungleboyjEveryone is looking through the sample config?16:31
*** rbak has quit IRC16:31
jgriffithjungleboyj :)16:31
diablo_rojojungleboyj, I think people lost interest when it started seeming less imminent16:32
diablo_rojoLol :)16:32
* jungleboyj is suddenly very lonely16:32
jgriffithso I think if this is an approach we want to take the starting point would be to use what we have first16:32
jungleboyjjgriffith:  Can you say more about that?16:32
jgriffithie consolidate on the existing things like san_ip etc, find as many as we can without introducing new ones16:32
jungleboyjjgriffith: ++16:32
winston-dyesterday I tried 'tox -egenconfig' on master branch tip, it's not working. :( but probably that's just me.16:32
jgriffithif we just go in and introduce a whole new set of "new" options we're just making the problem worse16:33
jungleboyjwinston-d:  :-(  Yikes.16:33
jungleboyjjgriffith: Totally agree.16:33
jgriffitheven if it's temporary.. and remember temporary is like at least 2 releases16:33
xyang2jgriffith: +116:33
lhx_is there a user survey of new options? not sure user care about the new ones.16:34
*** sshank has joined #openstack-meeting16:34
jgriffithwinston-d I just ran it succesfully.. so maybe refresh on your tox env?16:34
*** thorst has joined #openstack-meeting16:34
xyang2lhx_: my guess is user wants the existing options they've already configured to continue to work:)16:34
jgriffithLook.. here's the thing; our config file is 4,859 lines!!!!16:34
jgriffithThat's stupid16:35
jungleboyjdiablo_rojo:  This can't be an imminent thing as it directly impacts users.16:35
winston-djgriffith: yup, i should try with new virtual env.16:35
jungleboyjNeed to be careful here.16:35
xyang2lhx_:  if an existing option stops working, they will get upset16:35
jgriffithgranted that's all the blank-lines and comments, but still16:35
jgriffithit's not exactly consumable16:35
*** slaweq has joined #openstack-meeting16:36
diablo_rojojungleboyj, I wasn't saying go for it :) I just mean people are less interested when its not a threat.16:36
* jgriffith hands folks a copy of War and Peach and says.. "here's your example, all the answers are in there"16:36
jgriffithgood luck16:36
diablo_rojojgriffith, lol16:36
jungleboyjI would like to know how much consolidation will change that.16:36
jgriffithhaha... "Peach"16:36
diablo_rojo'May the odds be ever in your favor'16:36
lhx_xyang2, haha, +116:36
jungleboyjjgriffith:  *Laughing*16:36
jungleboyjI love War and Peach16:37
jungleboyjSo we agree we have a problem here.16:37
* jungleboyj wonders if there is support group for config option addiction.16:37
lbragstado/ My name's Lance and it's been 187 days since I've added a configuration option to my project16:38
jungleboyjHi Lance ...16:39
jungleboyjo/ My name's Jay and I cried while writing a config file once.16:39
*** thorst has quit IRC16:39
bswartzgrep -v '^$\|^\s*\#' /etc/cinder/cinder.conf16:39
bswartzthat's not profanity it does something useful16:40
jungleboyjAnyway, so, it has gotten quiet again.  Do we have anyone who would be willing to take the config file and get an idea of how many options could  be consolidated to use existing options.16:40
jgriffithbswartz thanks for that regex foo16:40
*** slaweq has quit IRC16:41
jungleboyjI think that would be the first step and then re-address discussion in the next meeting.16:41
diablo_rojoI can put it on my backlog to take a look.16:41
jungleboyjdiablo_rojo:  Would be good to have someone familiar with config options do it.16:41
jungleboyjWill you have a chance to at least get an idea of how many duplicates there are before next week?16:42
diablo_rojoMaybe, I can do an introductory foray to get a general idea of a lot- little, etc.16:43
jungleboyjdiablo_rojo:  Ok, cool.16:43
jungleboyj#agreed We need to look at our crazy list of config options.16:44
diablo_rojoI will see if I can get a more exact number, but I suspect it will be tedious and time consuming as hell.16:44
jgriffithdiablo_rojo you're suspicion is correct :)16:44
jungleboyj#action diablo_rojo  will try to get an idea of how many options could possibly be consolidated to existing items16:44
jgriffithwhich is why we have the sprawl we have16:44
jungleboyj#agreed We should start by using existing options rather than adding new ones.16:44
jungleboyjThose agreements and action look good?16:45
*** rbowen has joined #openstack-meeting16:45
diablo_rojojgriffith, hence my unease at accepting the task lol16:45
diablo_rojojungleboyj, yeah looks fine to me16:45
jungleboyj#action Jay to add to agenda for an update next week.16:46
xyang2diablo_rojo: I usually ask driver author to use options in, but sometimes they argue that they need to use a different option in their driver for some reason.  Just FYI16:46
jgriffithdiablo_rojo too late, it's been registered in IRC.... you're DOOOOMED16:46
jungleboyjWith a number/impact in mind we can put together a plan.16:46
e0ne15 mins reminder16:46
winston-dI guess cinder only cfg opts are only < 50% of all 4,859 lines?16:46
diablo_rojojgriffith, thanks for the vote of confidence ;)16:46
jungleboyjdiablo_rojo:  You are good at those details.16:46
diablo_rojojungleboyj, not sure if that is a compliment or not lol16:47
*** thorst has joined #openstack-meeting16:47
jungleboyjOk.  Lets wrap this up for this meeting.16:47
diablo_rojoxyang2, noted :)16:47
jungleboyjdiablo_rojo:  :-)16:47
winston-dmany shall be library introduced opts.16:47
*** henrynash has joined #openstack-meeting16:47
jungleboyjguyk: Sorry, we kind of hijacked things here.16:47
jgriffithdiablo_rojo I have confidence in you, I just feel bad for you :)16:47
*** zhhuabj_ has quit IRC16:47
*** yamamoto_ has quit IRC16:47
*** rbowen has left #openstack-meeting16:47
diablo_rojojgriffith, can't be any worse than standing in front of thousands of people and a demo not working ;)16:48
jungleboyjguyk: So, I think we want to hold on your patch at the moment and look at this before going forward.  That ok?16:48
*** rderose has quit IRC16:48
guykjungleboyj: it is ok16:48
jungleboyjOuch ...16:48
jungleboyjguyk:  Ok.  Thanks.16:48
*** zhhuabj_ has joined #openstack-meeting16:48
jungleboyj#topic Dynamic Reconfiguration16:49
*** openstack changes topic to "Dynamic Reconfiguration (Meeting topic: Cinder)"16:49
jungleboyjdiablo_rojo: More config discussion.16:49
*** yamamoto has joined #openstack-meeting16:49
diablo_rojoIt appears that there is a nontrivial section of Cinder cores that think this is a bad idea- especially for multinode setups16:50
*** henrynash has quit IRC16:50
diablo_rojoAnd I am gravitating towards that school of thought16:50
e0nediablo_rojo: could you please share a link to the patch?16:50
diablo_rojoe0ne, sure one sec16:50
*** jamesmcarthur has joined #openstack-meeting16:50
eharneyis there a short summary of the reason it's tough for multinode/HA?16:50
*** henrynash has joined #openstack-meeting16:50
*** henrynash has quit IRC16:51
jungleboyjeharney:  ++16:51
*** thorst has quit IRC16:51
e0nediablo_rojo: thanks16:51
*** henrynash has joined #openstack-meeting16:51
*** henrynash has quit IRC16:51
jungleboyjSad to see the discussion go this way.16:51
diablo_rojoeharney, basically it gets messy fast because processes don't end all at the same time.16:51
winston-deharney: synchronziation between multi-nodes is hard?16:51
jungleboyjbswartz:  Manila supports this, doesn't it?16:51
* e0ne still thinks that SIGHUP signal will be always a good potion16:51
*** joeljwright has joined #openstack-meeting16:52
*** Sukhdev_ has quit IRC16:52
*** joeljwright has left #openstack-meeting16:52
diablo_rojoe0ne, agreed, especially if CInder actually inherits from oslo's services and its handled how it looks to be written.16:52
bswartzjungleboyj: not yet, we want it16:52
jungleboyjbswartz:  Ah, ok.  I had been told you have it.16:52
*** egallen has quit IRC16:52
winston-de0ne: potion is better, we need magic here.16:53
*** efried has quit IRC16:53
* diablo_rojo votes to wait till Manila has solved it like we do with most our problems ;)16:53
geguileodiablo_rojo: afaik current SIGHUP will shutdown everything in Cinder afaik16:53
bswartzjungleboyj: maybe we inherited it?16:53
e0newinston-d: :)16:53
bswartzor maybe I'm less informed than you >_<16:53
xyang2bswartz: it's not in cinder yet:)16:53
* jungleboyj is confused. I though the point of this work was to get SIGHUP working.16:53
e0negeguileo: yes, but we can implement graceful shutdown if it's not implemented yet16:53
jungleboyjbswartz:  I doubt it.16:53
geguileoe0ne: we have graceful shutdown implemented there16:54
xyang2bswartz: I remember we talked about this in some manila meetings, referencing cinder16:54
geguileoe0ne: but it still needs to shutdown, which may take a loooong time16:54
e0negeguileo: it's another issue we should care about16:54
geguileothe long time?16:55
eharneyso what's the core reason that we can't implement this?  it's hard?16:55
tbarronwinston-d: diablo_rojo I'm trying to understand what is different in the multi-node case than when one shuts down service on a single node, changes config, and brings it up while other nodes are running.16:56
*** unicell1 has quit IRC16:56
jungleboyjeharney:  That is my fear.16:56
tbarronwinston-d: diablo_rojo are we contrasting this with:16:56
tbarronshut down service on all nodes, update config, start on all nodes?16:56
jungleboyjtbarron: Yeah, I don't understand why that is more dangerous that what we currently do.16:56
diablo_rojoeharney, well yes, but from looking through the code, it looks like it should work already. Some people have said it works for them and others have said it does not. I personally haven't been able to figure out why that is.16:57
tbarronthat last is probably safest, but ...16:57
tbarronjust trying to understand the issue16:57
*** andreas-f has quit IRC16:57
tbarronand some config options would be safe, whereas some may have problems w/o synchronization across nodes I guess.16:58
geguileoIf we are talking about using SIGHUP to make cinder restart itself and reload the new config options16:58
geguileothat's been working for a long time16:58
smcginnisJust shuts down for me.16:58
*** ad_rien_1 has joined #openstack-meeting16:58
diablo_rojogeguileo, right, that should work but some people say it doesn't?16:58
jungleboyjdiablo_rojo:  I think that had to do with whether you were running Cinder in Devstack/screen vs. using systemd16:58
*** ad_rien_ has quit IRC16:59
geguileosmcginnis: on which env? devstack? r:-??16:59
tbarrondevstack tests don't count :)16:59
jungleboyjsmcginnis: In devstack ?16:59
*** jamesdenton has quit IRC16:59
geguileosmcginnis: did you send SIGHUP to the parent process or to all of them?16:59
diablo_rojojungleboyj, that was part of the confusion, but I thought some people also ran it with their own drivers too16:59
smcginnisgeguileo: I thought I tried on actual deployment, but can't remember for sure now. Parent process.16:59
tbarronfor multinode unless you have a better multinode devstack than I've been able to do16:59
e0negeguileo, smcginnis: SIGHUP doesn't work on devstack with screen17:00
eharneythere was some difference in how services behave when running on a terminal (i.e. in screen) that i looked into a while back, so yeah, devstack tests may not behave like normal services17:00
*** vishnoianil has quit IRC17:00
jungleboyjAnyway, we have run out of time.17:00
geguileosmcginnis: I tried it while preparing for my Barcelona presentation and it worked for me back then17:00
tbarronscreen is dead for devstck anyways17:00
jungleboyjI think we need to finish this discussion.17:00
geguileoe0ne: devstack doesn't use devstack anymore, right?17:00
smcginnisgeguileo: OK, could be why I was having issues with this too:
smcginnisTimes up.17:00
bswartzscreen is dead, long live screen!17:00
diablo_rojojungleboyj, yes, cause we have had this part of the discussion several times and made no progress :)17:00
tbarronbut there's a good question about incompatability across nodes17:00
e0negeguileo: yes, it switched to systemd by default17:01
jungleboyjCan we get people to verify what they see working or not and we cna wrap up discussion next week?17:01
diablo_rojoYes please17:01
eharneyi think we need to do another round on the spec...17:01
jungleboyjdiablo_rojo:  Ok.  We will go that way.17:01
diablo_rojoeharney, :P17:01
*** jamesdenton has joined #openstack-meeting17:01
geguileosmcginnis: that's something I haven't explored but could be interesting17:01
tbarronacross three apis running concurrently, or if an option affects the rpc between services17:01
*** Apoorva_ has joined #openstack-meeting17:02
jungleboyj#action Cores to try using sighup this week and then we will decide what to do in next week's meeting.17:02
jungleboyjOk, we need to free up the meeting room.17:02
* tbarron watches jungleboyj SIGTERM this meeting17:02
winston-dtbarron: got disconnected just now, will catch up with you in cinder17:02
jungleboyjThanks for the good discussion!17:02
e0nesee you next week!17:02
*** openstack changes topic to "OpenStack Meetings ||"17:02
openstackMeeting ended Wed Jun 21 17:02:52 2017 UTC.  Information about MeetBot at . (v 0.1.4)17:02
openstackMinutes (text):
*** winston-d has left #openstack-meeting17:02
lhx_thanks :D17:03
jungleboyjThanks everyone.17:03
*** guyk has quit IRC17:03
pewpjungleboyj (=゚ω゚)ノ17:04
*** chyka has joined #openstack-meeting17:04
*** ad_rien_1 has quit IRC17:05
*** Apoorva has quit IRC17:05
*** lhx_ has quit IRC17:06
*** harlowja has joined #openstack-meeting17:07
*** mguiney has joined #openstack-meeting17:07
*** hashar has quit IRC17:08
*** xyang2 has quit IRC17:09
*** yamahata_ has joined #openstack-meeting17:10
*** abishop has left #openstack-meeting17:10
*** jamesmcarthur has quit IRC17:10
*** armstrong has quit IRC17:10
*** e0ne has quit IRC17:11
*** jamesmcarthur has joined #openstack-meeting17:12
*** andreas-f has joined #openstack-meeting17:12
*** links has quit IRC17:15
*** makowals has joined #openstack-meeting17:16
*** jamesmcarthur has quit IRC17:17
*** ltomasbo is now known as ltomasbo|away17:19
*** thorst has joined #openstack-meeting17:19
*** sshank has quit IRC17:20
*** _alastor1 is now known as _alastor_17:21
*** thorst has quit IRC17:24
*** Sukhdev has quit IRC17:25
*** emagana has quit IRC17:27
*** sshank has joined #openstack-meeting17:27
*** thorst has joined #openstack-meeting17:28
*** ijw has joined #openstack-meeting17:28
*** unicell has joined #openstack-meeting17:28
*** armax has quit IRC17:29
*** sudipto_ has quit IRC17:30
*** sudipto has quit IRC17:30
*** thorst has quit IRC17:34
*** bobmel_ has joined #openstack-meeting17:36
*** slaweq has joined #openstack-meeting17:37
*** thorst has joined #openstack-meeting17:38
*** ekcs has joined #openstack-meeting17:39
*** makowals has quit IRC17:39
*** thorst has quit IRC17:40
*** emagana has joined #openstack-meeting17:40
*** bobmel has quit IRC17:40
*** Adadzd has joined #openstack-meeting17:41
*** slaweq has quit IRC17:41
*** yamamoto has quit IRC17:42
*** cody-somerville has joined #openstack-meeting17:44
*** csomerville has quit IRC17:44
*** electrofelix has quit IRC17:45
*** pnavarro has joined #openstack-meeting17:47
*** yamamoto has joined #openstack-meeting17:51
*** krenczew1 has joined #openstack-meeting17:52
*** thorst has joined #openstack-meeting17:53
*** yamamoto has quit IRC17:56
*** krenczewski has quit IRC17:56
*** krenczewski has joined #openstack-meeting17:56
*** thorst has quit IRC17:57
*** bh526r has joined #openstack-meeting17:59
*** thorst has joined #openstack-meeting18:00
bh526r#startmeeting gluon18:00
openstackMeeting started Wed Jun 21 18:00:34 2017 UTC and is due to finish in 60 minutes.  The chair is bh526r. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: gluon)"18:00
openstackThe meeting name has been set to 'gluon'18:00
bh526r#topic Roll Call18:00
*** openstack changes topic to "Roll Call (Meeting topic: gluon)"18:00
bh526r#info Bin Hu18:01
jinli#info JinLi18:01
jinliHi Bin18:01
jinliHello all18:01
bh526rHi Jin18:02
bh526rHow are you?18:02
*** csomerville has joined #openstack-meeting18:02
krenczewski#info Kamil Renczewski18:02
bh526rI am multitasking, because I am taking another internal conference call now18:02
bh526rHi Kamil18:02
bh526rSo forgive me if I respond to you late, or not seem active from while to while18:03
*** slaweq has joined #openstack-meeting18:03
bh526r#topic Status Update18:03
*** openstack changes topic to "Status Update (Meeting topic: gluon)"18:03
bh526rLet's start with Kamil, because it is night for Kamil18:03
krenczewskiGive me 15 more minutes, please18:04
*** hashar has joined #openstack-meeting18:05
*** thorst has quit IRC18:05
*** cody-somerville has quit IRC18:05
bh526rMaybe Jin can give an update first?18:07
*** pewp has quit IRC18:08
*** slaweq has quit IRC18:08
jinliI am continue working on reviewing and also some updating on Kamal's code for integrating keystone with gluon18:08
jinliI am able to set up the system so that I can use keystone for authentication18:09
bh526r#info Jin continues working on reviewing and also some updating on Kamal's code for integrating keystone with gluon18:09
*** Apoorva_ has quit IRC18:09
jinlistill not able to add port or view port which has to do with the policies18:09
bh526r#info Jin sets up the system and uses keystone for authentication18:09
jinlineed to look deeper into that18:09
*** Apoorva has joined #openstack-meeting18:10
jinliI have a patch that updates the instructions for setting up keystone18:10
bh526r#info The issue now is not able to add port or view port which has to do with the policies18:10
bh526r#info Jin is looking deeper into that18:11
bh526r#info Jin also submitted a patch that updates the instructions for setting up keystone18:11
*** pewp has joined #openstack-meeting18:11
bh526r#info It's been reviewed, and comments were received18:12
bh526r#info Jin will address those comments and provide new patchset as needed18:13
jinlii will respond to their comments and make updates if needed18:13
bh526rgreat, thank you Jin18:14
*** ijw has quit IRC18:14
*** vishnoianil has joined #openstack-meeting18:15
*** yamamoto has joined #openstack-meeting18:15
*** salv-orl_ has quit IRC18:17
*** Rockyg has quit IRC18:17
*** ijw has joined #openstack-meeting18:18
*** kornica has joined #openstack-meeting18:18
*** bklei has quit IRC18:19
*** kbyrne has quit IRC18:22
*** ijw has quit IRC18:23
*** kbyrne has joined #openstack-meeting18:23
*** hugokuo has joined #openstack-meeting18:24
*** ijw has joined #openstack-meeting18:24
*** marst has quit IRC18:27
*** marst has joined #openstack-meeting18:28
*** awaugama has quit IRC18:29
*** samP has quit IRC18:31
*** awaugama has joined #openstack-meeting18:31
*** hashar has quit IRC18:35
krenczewskiNot much from me18:37
bh526rOk, no problem.18:38
krenczewskiReviewed documentation and I need to update it18:38
*** Swami has joined #openstack-meeting18:38
bh526rThank you18:38
krenczewskibut in my repository18:38
bh526r#info Kamil reviewed documentation, and will update it in his repo18:38
*** slaweq has joined #openstack-meeting18:38
krenczewskiI'll start a review tomorrow18:38
bh526ranything else from anyone?18:38
bh526rgreat, and thank you Kamil18:39
krenczewskisince Pauld didn't chech the procedure18:39
bh526rHe is very busy. So he won't check the procedure in near future18:39
krenczewskiThanks for info18:39
bh526rif nothing else, we can adjourn the meeting18:40
bh526r#info Nothing else. Meeting adjourned18:41
*** krenczewski has quit IRC18:41
*** bobmel has joined #openstack-meeting18:41
bh526rBye all18:41
*** openstack changes topic to "OpenStack Meetings ||"18:41
openstackMeeting ended Wed Jun 21 18:41:56 2017 UTC.  Information about MeetBot at . (v 0.1.4)18:41
openstackMinutes (text):
*** slaweq has quit IRC18:43
*** Sukhdev has joined #openstack-meeting18:43
*** yamamoto has quit IRC18:44
*** bobmel_ has quit IRC18:45
*** abramley has quit IRC18:45
*** abramley has joined #openstack-meeting18:45
*** hashar has joined #openstack-meeting18:47
*** awaugama has quit IRC18:51
*** awaugama has joined #openstack-meeting18:53
*** ijw has quit IRC18:55
*** ijw has joined #openstack-meeting18:55
zara_the_lemur__anybody about for the all-singing, all-dancing storyboard meeting?18:59
* zara_the_lemur__ will give it a couple of minutes18:59
*** ijw has quit IRC18:59
*** sshank has quit IRC19:00
*** emagana has quit IRC19:02
*** emagana has joined #openstack-meeting19:02
*** bh526r has quit IRC19:03
fungii'm around but willing to skip19:03
*** slaweq has joined #openstack-meeting19:04
zara_the_lemur__heh, I have no strong feelings either way so that would also work for me19:04
zara_the_lemur__and I think SotK is travelling so is probably not too attached either19:04
*** wewe0901 has quit IRC19:05
fungia significant chunk of the infra team is at a conference right now too19:05
diablo_rojoI am around19:05
zara_the_lemur__diablo_rojo: CONGRATULATIONS, YOU ARE THE LUCKY #OPENSTACK-MEETING VISITOR. you get to decide if you want a meeting I guess (I have nothing to report personally)19:06
*** priteau has quit IRC19:07
*** emagana has quit IRC19:07
*** priteau has joined #openstack-meeting19:07
zara_the_lemur__I was only gonna run it so people could come in and ask questions if they'd made a note to attend, but I think we've probably given it long enough for that19:07
zara_the_lemur__folk seem to be finding their way to #storyboard, which I'm happy about19:08
diablo_rojozara_the_lemur__, ha ha if SotK is out and we have no questions I don't think we need a meeting19:08
*** sshank has joined #openstack-meeting19:08
zara_the_lemur__my goodness, software developers who don't want meetings for the sake of meetings?19:08
diablo_rojoI've never been one to have useless meetings :)19:09
*** slaweq has quit IRC19:09
*** sshank has quit IRC19:10
*** priteau has quit IRC19:12
*** rbak has joined #openstack-meeting19:13
*** emagana has joined #openstack-meeting19:17
*** thorst has joined #openstack-meeting19:19
*** patriciadomin has quit IRC19:22
*** ijw has joined #openstack-meeting19:23
*** pnavarro has quit IRC19:24
*** pnavarro has joined #openstack-meeting19:25
*** makowals has joined #openstack-meeting19:27
*** thorst has quit IRC19:27
*** slaweq has joined #openstack-meeting19:29
*** slaweq has quit IRC19:32
*** bklei has joined #openstack-meeting19:33
*** slaweq has joined #openstack-meeting19:35
*** kaisers_ has quit IRC19:36
*** ijw has quit IRC19:36
*** dmacpher has quit IRC19:41
*** yamamoto has joined #openstack-meeting19:45
*** patriciadomin has joined #openstack-meeting19:47
*** awaugama has quit IRC19:48
*** benj_ has quit IRC19:49
*** jprovazn has quit IRC19:50
*** benj_ has joined #openstack-meeting19:51
*** armstrong has joined #openstack-meeting19:51
*** efried has joined #openstack-meeting19:52
*** yamamoto has quit IRC19:52
*** makowals has quit IRC19:53
*** dmacpher has joined #openstack-meeting19:54
*** bklei has quit IRC19:54
*** bklei has joined #openstack-meeting19:55
*** rhochmuth has quit IRC19:58
*** ekhugen_alt has joined #openstack-meeting19:58
ekhugen_alt#startmeeting wos_mentoring20:00
openstackMeeting started Wed Jun 21 20:00:12 2017 UTC and is due to finish in 60 minutes.  The chair is ekhugen_alt. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: wos_mentoring)"20:00
openstackThe meeting name has been set to 'wos_mentoring'20:00
ekhugen_altHi, who's here for women of openstack mentoring?20:00
*** pnavarro has quit IRC20:01
ekhugen_althm, anyone here for wos_mentoring?20:03
*** salv-orlando has joined #openstack-meeting20:04
smcginnisekhugen_alt: When is the mentoring going to be? During the summit?20:04
*** NicoleH has joined #openstack-meeting20:04
* smcginnis isn't really here for the meeting, but was curious :)20:04
NicoleHhi there!20:04
ekhugen_altsmcginnis we have the meeting to talk about the Speed Mentoring sessions during the summit and also the long term mentoring (which has been languishing a bit lately)20:05
ekhugen_altHi NicoleH20:05
*** slaweq has quit IRC20:05
diablo_rojoHello :)20:05
ekhugen_altHi Kendall!20:05
*** kaisers_ has joined #openstack-meeting20:05
NicoleHhi smcginnis!20:05
ekhugen_altare aimeeu and amrith also hear for the meeting?20:05
NicoleHhi diablo_rojo!20:05
*** slaweq has joined #openstack-meeting20:06
diablo_rojoHello NicoleH and ekhugen_alt :)20:06
*** Sukhdev has quit IRC20:06
aimeeui'm swamped and in multi-meetings right now already. aack!20:06
NicoleHyikes, aimeeu!20:06
ekhugen_alts /hear/here/20:06
ekhugen_altyeesh, good luck Aimee!20:07
*** dmacpher has quit IRC20:07
ekhugen_altokay, well first topic any other wrapup from boston?20:08
ekhugen_altpointer to feedback
ekhugen_alt#topic Boston final wrapup20:08
*** openstack changes topic to "Boston final wrapup (Meeting topic: wos_mentoring)"20:08
NicoleHthanks for the link to the feedback.20:08
*** gouthamr has quit IRC20:09
*** pchavva has quit IRC20:09
NicoleHi think the feedback from boston looks really solid, and can be applied to future summits!20:10
diablo_rojoNicoleH, +120:10
ekhugen_altyep, I think so too!20:10
ekhugen_altokay, so speaking of future summits20:10
ekhugen_alt#topic sydney planning20:10
*** openstack changes topic to "sydney planning (Meeting topic: wos_mentoring)"20:10
ekhugen_altthere was some discussion about this in the last women of openstack meeting20:10
ekhugen_altthey talked about combining the speed mentoring and women of openstack lunch20:11
ekhugen_altand asking if we could do it sans sponsors and just ask people to pick up a box lunch outside the room20:11
ekhugen_altany thoughts on that?20:11
diablo_rojoIs that going to be enough time to do everything?20:12
diablo_rojoOr would we be completely changing the schedule?20:12
ekhugen_altI think they'd be completely changing the schedule, and  maybe making it less speed mentoring and more speed networking20:13
ekhugen_altI guess, diablo_rojo, do you know if we have sponsors for both the WOS lunch and speed mentoring at  Sydney20:13
diablo_rojoI think both events are int the prospectus20:13
diablo_rojoNot sure about any takers yet, I will ask.20:13
* smcginnis would be sad to see no one willing to sponsor these events20:14
NicoleHi'd be interested in thoughts about combining the two.20:14
NicoleHi think there's enough meat in each to continue to make them 2 separate activities.20:14
*** priteau has joined #openstack-meeting20:14
smcginnisNicoleH: +120:14
NicoleHi can see intel continuing to sponsor the speed mentoring session.20:15
ekhugen_altI think the discussion too was centered around whether there would be enough mentors/mentees at Sydney20:16
NicoleHand i think we've started to make the wos luncheon meaty enough with a mini-panel discussion hosted during the lunch.20:16
ekhugen_altI think someone mentioned the Sydney summit is going to be smaller, and if we only had half or less the participants, would that still be enough to call it a separate session?20:16
ekhugen_alt(not that we need to make a decision here, they were just some discussion points)20:17
NicoleHoh, i see -- so, different approaches based on US vs international summits?20:17
diablo_rojoIf we dont do full on speed mentoring for Sydney we definitely need to in Vancouver20:17
NicoleHmeaning -- for U.S. summits, they would remain separate, and for international summits, they may be combined?20:17
*** bklei has quit IRC20:18
*** emagana has quit IRC20:18
ekhugen_altright, particularly the Sydney summit, people were talking about that being much, much smaller (2500?)20:18
ekhugen_altI have no idea if that's really true or not20:18
NicoleHi think our experience in barcelona was that, although the speed mentoring session was smaller, it allowed time/opportunity for more interaction.20:18
diablo_rojoThere's a sponsor for the networking lunch- Intel20:18
diablo_rojoNone for speed mentoring yet20:19
*** bklei has joined #openstack-meeting20:19
NicoleHoh, interesting -- i'll check with our events team.20:19
ekhugen_alt+1 NicoleH on the Barcelona experience20:21
*** dmacpher has joined #openstack-meeting20:21
*** ad_rien_ has joined #openstack-meeting20:21
*** hashar has quit IRC20:22
diablo_rojoSmaller more personal experience was good20:23
ekhugen_altanyway, any other thoughts on sydney or what we should/shouldn't do (I know Amrith and Swami volunteered to run the session there and I don't think they're on)20:23
NicoleH+1 diablo_rojo20:23
*** pnavarro has joined #openstack-meeting20:23
NicoleHperhaps focus one of our future calls on sydney, when they're here?20:23
*** emagana has joined #openstack-meeting20:24
ekhugen_altyes, I think so20:24
ekhugen_altany other topics?  do we want to talk any more about long term mentoring?  We haven't done a match in awhile, do we want to think about doing another push to get mentors and mentees?20:25
ekhugen_alt#topic open20:25
*** openstack changes topic to "open (Meeting topic: wos_mentoring)"20:25
diablo_rojoI think we should look at doing another round of longer term mentoring20:26
NicoleH+1 diablo_rojo20:27
ekhugen_altwould we want to use the same form?
NicoleHlet me know how i can help / get more involved!20:27
diablo_rojoThat or I can make a new one20:27
diablo_rojoIts pretty easy.20:27
*** emagana has quit IRC20:28
ekhugen_altwell I mean, do we like the questions on the existing form?20:28
ekhugen_altwe could cut out some of them like how often they like to meet, preferred working style, since we don't really match on those20:30
diablo_rojoIt would be nice if we could make it shorter.. Maybe take out the communication style one- they can figure that out on their own.20:30
*** slaweq has quit IRC20:30
diablo_rojoekhugen_alt, ha ha :)20:30
*** slaweq has joined #openstack-meeting20:31
ekhugen_altI mean, I think part of our thoughts with some of those questions had been to try to weed people out who were just randomly filling out the form20:32
*** dprince has quit IRC20:32
*** ijw has joined #openstack-meeting20:32
ekhugen_altand didn't really have time, but the increased checkins that we did with the last round of matches is probably a better way to weed those out, I think20:32
*** cleong has quit IRC20:32
*** henrynash has joined #openstack-meeting20:34
diablo_rojoI think if we can, we should opt for a bi monthly check in? and then at 6 months we say they've graduated?20:35
*** bklei has quit IRC20:35
diablo_rojoOr do quarterly for a year?20:35
ekhugen_altI think we were leaning 6 months20:35
*** slaweq has quit IRC20:35
*** galstrom_zzz is now known as galstrom20:35
ekhugen_altby bimonthly, did you mean twice a month or once every two months?20:36
*** bklei has joined #openstack-meeting20:36
*** shadow-x has joined #openstack-meeting20:37
NicoleHquarterly seems like it would be a good interval.20:37
*** shadow-x has quit IRC20:37
ekhugen_altso NicoleH you like the yearlong mentoring relationship better than 6 months?20:38
NicoleHah, i see ... with the quarterly check-ins, it's a year-long mentoring time period.20:39
NicoleHand with a 6-mo mentoring time period, how often are the check-ins?20:39
*** pnavarro has quit IRC20:39
ekhugen_altI think diablo_rojo was suggesting every other month?20:39
NicoleHok, i see.20:39
*** pnavarro has joined #openstack-meeting20:40
NicoleHit feels like, with a 6-mo time period, perhaps the check-ins should be once per month.20:40
*** bklei has quit IRC20:40
NicoleHto keep the relationships active.20:40
diablo_rojoOnce per month would be ideal, but thats a big commitment for us ;)20:41
diablo_rojoUnless we rotate the job20:41
NicoleHi like the idea of rotations.20:41
ekhugen_altit is a lot, we do have the shared gmail address, so we could rotate it20:41
NicoleHhas that been tried before?20:41
NicoleHi mean, has the idea of rotations been tried before?20:42
ekhugen_altI think that the thing we might run into is it's hard to keep things active every month20:42
*** X-dark_ has joined #openstack-meeting20:42
ekhugen_altlike it hasn't seemed unusual that people would have conflicts for a month and need to postpone things20:43
NicoleHso, given a 6-mo time period, if we do check-ins every other month, then it would essentially be 2 check-ins & a final check-in before they're "graduated"?20:43
*** X-dark has quit IRC20:44
*** X-dark_ is now known as X-dark20:44
*** dmacpher has quit IRC20:44
ekhugen_altwell I guess maybe we should quantify check-ins20:44
ekhugen_altpreviously check-ins had just been an email "let us know if things aren't going okay"20:44
ekhugen_alt(longer than that, but that's the basic idea)20:45
NicoleHah, ok20:45
ekhugen_altand then if we didn't get responses to the emails, we'd start putting people on warning, and then eventually unmatch them20:45
NicoleHi thought it was something more like a call. but i get it now.20:46
ekhugen_altso a lot of the work was in the people who didn't respond, like making sure you followed up again in 2 weeks, 3 weeks, then unmatching20:46
NicoleHok, i understand.20:46
ekhugen_altbut we could change the check-ins to be more of a support for the relationship20:46
NicoleH+1 emily20:47
NicoleHwe could talk about what that might look like, and then pilot the approach?20:47
ekhugen_altyes, maybe that's a good thing to think about for next week?20:48
*** gouthamr has joined #openstack-meeting20:48
diablo_rojoekhugen_alt, +120:48
*** ad_rien_ has quit IRC20:48
*** X-dark has quit IRC20:49
ekhugen_altI would say there's probably 2 sides to it:  how can we structure the program so we have fewer no-shows and how we can restructure the checkins to help mentors/mentees more20:49
*** fnaval_ has quit IRC20:50
ekhugen_altany other topics for today?20:50
*** X-dark has joined #openstack-meeting20:50
diablo_rojoThings to ponder for next week :)20:51
*** NicoleH_ has joined #openstack-meeting20:51
*** ansmith has quit IRC20:51
NicoleH_+1 emily20:51
NicoleH_great discussion for next week!20:52
diablo_rojoGood chat everyone :)20:52
ekhugen_altthanks everyone!  have a good day and happy summer!20:52
*** NicoleH has quit IRC20:52
*** amotoki is now known as amotoki_away20:52
*** openstack changes topic to "OpenStack Meetings ||"20:52
openstackMeeting ended Wed Jun 21 20:52:53 2017 UTC.  Information about MeetBot at . (v 0.1.4)20:52
openstackMinutes (text):
*** henrynash has quit IRC20:53
*** NicoleH_ has quit IRC20:53
*** ekhugen_alt has left #openstack-meeting20:53
*** ad_rien_ has joined #openstack-meeting20:54
*** timburke has joined #openstack-meeting20:55
*** priteau has quit IRC20:56
*** ttrifonov has quit IRC20:57
*** dmacpher has joined #openstack-meeting20:58
*** patchbot has joined #openstack-meeting20:59
*** acoles has joined #openstack-meeting20:59
*** kota_ has joined #openstack-meeting20:59
notmynameswift team meeting time21:00
notmyname#startmeeting swift21:00
openstackMeeting started Wed Jun 21 21:00:12 2017 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
*** ykatabam has joined #openstack-meeting21:00
mattoliverauo/ (kinda)21:00
notmynamebig crowd ;-)21:01
*** joeljwright1 has joined #openstack-meeting21:01
notmynamelooks like a short agenda today, so let's get started so people can get breakfast/to bed21:02
*** m_kazuhiro has joined #openstack-meeting21:02
notmyname#topic boilerplate announcements21:02
*** openstack changes topic to "boilerplate announcements (Meeting topic: swift)"21:02
notmynamenote the PTG and summit links on the agenda21:02
notmynameplease encourage any ops you know to go to the PTG21:03
notmyname#topic deprecate known-bad EC config21:03
*** openstack changes topic to "deprecate known-bad EC config (Meeting topic: swift)"21:03
notmynamepatch 46810521:03
patchbot - swift - Require that known-bad EC schemes be deprecated21:03
notmynamewe've got 2 +2 on it21:03
notmynamewe've emailed different ML21:03
*** jamesdenton has quit IRC21:03
notmynamewe've talked about it for a long time21:03
notmynameis there any reason to not +A it right now?21:04
mattoliverauNope, do it!21:04
*** ad_rien_ has quit IRC21:04
*** rhochmuth has joined #openstack-meeting21:04
notmynamekota_: acoles: ok with you for me to +A it right now?21:04
notmynametimburke: thanks for pushing this one21:05
notmynamekota_: thanks for setting this whole thing off by finding the bug :-)21:05
notmyname#topic previous meeting follow-ups21:05
*** openstack changes topic to "previous meeting follow-ups (Meeting topic: swift)"21:05
notmynamenot much here21:06
timburkeall i did was write a patch :-) sorry for a bit of a fire drill at work clayg/acoles21:06
notmynameromain isn't here this week21:06
notmynamealthough I saw the email ovh sent about LOSF21:06
notmynameif you didn't read it, please do21:06
acolestimburke: lol21:06
*** fnaval has joined #openstack-meeting21:06
notmynameno progress on py3 work afaik21:06
acolestimburke: thanks for updating the patch with doc21:06
notmyname#topic priority patches21:07
*** openstack changes topic to "priority patches (Meeting topic: swift)"21:07
notmynameI updated that wiki page21:07
*** baoli has quit IRC21:07
notmynamethere's 10 patches there, but I have a question about one or two of them21:07
patchbotpatch 455488 - python-swiftclient - Tolerate RFC-compliant ETags21:07
*** jamesdenton has joined #openstack-meeting21:07
notmynamehas +2 from joeljwright1 and timburke, but timburke is also the author21:08
joeljwright1reviewed that today21:08
notmynameso what needs to happen there?21:08
notmynametimburke: ?21:08
joeljwright1it's a simple patch, but more eyes couldn't hurt…21:08
timburkemerge it! there was some hesitance since i'm also the author21:08
*** jamesdenton has quit IRC21:08
joeljwright1(I'm the hesitant one)21:08
joeljwright1I'll go merge it21:09
notmynamejoeljwright1: ack21:09
claygi clicked +A on the etag one - I had comments from last week - my bad21:09
notmynameah! thanks clayg21:09
joeljwright1dammit clayg beat me to it!21:09
claygsort of - would have been better to do that last week!21:09
*** ad_rien_ has joined #openstack-meeting21:10
notmynameok, any other patches to call out or that need discussion during this meeting?21:10
mattoliverauThe tpool one looks good now, with a fixed SAIO, you can easily test and use servers_per_port21:11
*** pnavarro has quit IRC21:11
patchbotpatch 289664 - swift - Make eventlet.tpool's thread count configurable in...21:11
notmynamethat one?21:11
timburke seems like a good idea... haven't actually demonstrated a socket leak, but fairly certain there is one21:12
patchbotpatch 307937 - swift - Close all versioned_writes subrequests' app_iters21:12
*** dmacpher has quit IRC21:12
mattoliverauSo someone go play. Also merged in clays thoughts and using auto config21:12
notmynameah right. thanks timburke. I wanted to track the socket leak ones. didn't you have another?21:12
timburkeRomain's merged already21:13
patchbotpatch 474767 - swift - Fix a socket leak in copy middleware (MERGED)21:13
acolesrledisez fixed one last week21:13
acolestimburke: beta me21:13
notmynametim as a beta version of al?21:14
timburkeoh, ? i forget whether that actually full fixes the problem21:14
patchbotpatch 471993 - swift - Send Connection:close headers when we haven't read...21:14
joeljwright1It also seems like more people need to weigh in on whether we want to add & expose pre/postambles to the SLO API…
patchbotpatch 365371 - swift - Add Preamble and Postamble to SLO and SegmentedIte...21:14
notmynamejoeljwright1: ah, right. you and i talked in irc about it21:15
timburkei haven't played around with a bad client on it yet -- see if eventlet closes the connection even if the client tries to hold it open21:15
clayg@timburke I've been growing increasingly convinced sending connection: close to eventlet won't do the trick (because of the EC connection: close backend header leaking bug)21:15
clayglp bug #168073121:15
openstackLaunchpad bug 1680731 in OpenStack Object Storage (swift) "GET EC policy object includes connection:close header which causes external LB returns 502 bad gateway to client" [Medium,Fix released]
claygalso when I looked at the code in patch 471993 I remember being totally confused - but never tested if the pipelined request with 413 acctually broke21:16
patchbot - swift - Send Connection:close headers when we haven't read...21:16
*** ad_rien_ has quit IRC21:17
notmynameso... more testing is warranted21:18
*** caboucha has quit IRC21:18
*** ad_rien_ has joined #openstack-meeting21:19
notmynamejoeljwright1: when did we talk about the TLO stuff? I want to find the link. what day was it?21:19
notmynameyesterday? or monday?21:19
timburke would be nice (particularly, i feel, if tdasilva is still working on that release)21:20
patchbotpatch 459023 - liberasurecode - Consistently use zlib for crc3221:20
notmynameah yes. easy to search logs when not much has been said in them ;-)21:20
*** torgomatic has joined #openstack-meeting21:20
notmynamejoel's pre/post amble addition to SLO is for enabling tarfiles. and potentially other archive formats21:21
notmynameand while I've heard some bit of discussion about it, there's not a lot of record of that in gerrit21:21
notmynamesee the above IRC log link for monday's conversation we had. gives a little more detail on the goals for after this patch21:21
notmynamebut it's a change that, if we add, we'll have to support, so now's the time to speak up about it21:22
notmyname#topic open discussion21:22
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:22
notmynameanything else from anyone to bring up in today's meeting?21:22
timburke and are interesting things that kinda popped out of reviewing sharding and symlinks... wouldn't mind getting opinions on them21:23
patchbotpatch 465776 - swift - Increase name-length limits for internal accounts21:23
patchbotpatch 449394 - swift - WIP: Move listing formatting out to proxy middleware21:23
mattoliverauI'm kinda busy (yes even tho unemployed) until Friday, but will try and have a look at em then21:25
mattoliverauThe first one would be needed and awesome for Sharding name edgecases21:25
*** dmacpher has joined #openstack-meeting21:26
timburkemattoliverau: i think the second one would be useful too -- we're splicing listing results across shards in the proxy, right?21:26
*** dimtruck is now known as zz_dimtruck21:26
timburkeonly having one format to deal with could be handy21:27
mattoliverauOh yeah, I like that idea too :)21:27
notmynametimburke: thanks for mentioning those21:27
mattoliverauAnd so we always ask for json21:27
notmynameno need to sit around in here for another 30 minutes if theres not a pressing topic... last call?21:28
*** eric_young has quit IRC21:28
notmynamethis is easier in person when i can look at your faces :-)21:28
*** emagana has joined #openstack-meeting21:28
notmynamethanks for the work you do on swift, and thanks for coming to the meeting21:28
timburkesomeone (zaitcev?) should go land
patchbotpatch 337297 - swift - Add support to increase object ring partition power21:28
tdasilvahello! sorry i'm late21:29
timburkenotmyname: see, this is why we can't end early :P21:29
notmynamewell, exciting things happen in what was going to be the last 5 seconds of the meeting...21:29
notmynameseriously, i had #endmeeting already about to hit return21:29
notmynametdasilva: anything to bring up this week?21:30
notmynametdasilva: otherwise, I'm gonna call it :-)21:30
tdasilvano, sorry, i'm going to read up on what was said and am happy to follow up on the channel21:30
*** openstack changes topic to "OpenStack Meetings ||"21:30
openstackMeeting ended Wed Jun 21 21:30:54 2017 UTC.  Information about MeetBot at . (v 0.1.4)21:30
notmynameta da!21:30
openstackMinutes (text):
*** timburke has left #openstack-meeting21:31
*** patchbot has left #openstack-meeting21:31
*** joeljwright1 has left #openstack-meeting21:31
*** aeng has joined #openstack-meeting21:34
*** m_kazuhiro has quit IRC21:38
*** esberglu has quit IRC21:41
*** VW_ has joined #openstack-meeting21:41
*** makowals has joined #openstack-meeting21:43
*** andreas-f has quit IRC21:44
*** VW has quit IRC21:44
*** ad_rien_ has quit IRC21:44
*** VW_ has quit IRC21:45
*** ad_rien_ has joined #openstack-meeting21:46
*** efried has quit IRC21:48
*** zz_dimtruck is now known as dimtruck21:50
*** ansmith has joined #openstack-meeting21:52
*** galstrom is now known as galstrom_zzz21:54
*** galstrom_zzz is now known as galstrom21:54
*** hagridaaron has joined #openstack-meeting21:55
*** esberglu has joined #openstack-meeting21:55
*** galstrom is now known as galstrom_zzz21:55
*** jkilpatr has quit IRC21:56
*** hagridaaron has quit IRC21:57
*** henrynash has joined #openstack-meeting21:58
*** ad_rien_ has quit IRC22:00
*** esberglu has quit IRC22:00
*** ad_rien_ has joined #openstack-meeting22:01
*** armstrong has quit IRC22:01
*** ijw has quit IRC22:03
*** armax has joined #openstack-meeting22:03
*** ijw has joined #openstack-meeting22:03
*** ad_rien_1 has joined #openstack-meeting22:04
*** markvoelker has quit IRC22:04
*** ad_rien_ has quit IRC22:05
*** markvoelker_ has joined #openstack-meeting22:06
*** rfolco has quit IRC22:06
*** pradk has quit IRC22:07
*** kylek3h has quit IRC22:08
*** henrynash has quit IRC22:09
*** makowals has quit IRC22:10
*** markvoelker_ has quit IRC22:11
*** felipemonteiro_ has quit IRC22:12
*** bastafidli_ has quit IRC22:12
*** salv-orl_ has joined #openstack-meeting22:12
*** salv-orlando has quit IRC22:15
*** salv-orl_ has quit IRC22:15
*** Julien-zte has joined #openstack-meeting22:15
*** salv-orlando has joined #openstack-meeting22:16
*** ad_rien_ has joined #openstack-meeting22:17
*** ad_rien_1 has quit IRC22:17
*** markvoelker has joined #openstack-meeting22:17
*** julim has quit IRC22:17
*** xyang1 has quit IRC22:18
*** jamesmcarthur has joined #openstack-meeting22:18
*** salv-orlando has quit IRC22:21
*** ad_rien_ has quit IRC22:21
*** dmacpher has quit IRC22:21
*** jamesmcarthur has quit IRC22:23
*** Sukhdev has joined #openstack-meeting22:28
*** marst has quit IRC22:33
*** emagana has quit IRC22:34
*** dmacpher has joined #openstack-meeting22:35
*** sshank has joined #openstack-meeting22:50
*** Julien-zte has quit IRC22:50
*** brault has quit IRC22:51
*** jamesmcarthur has joined #openstack-meeting22:51
*** Julien-zte has joined #openstack-meeting22:51
*** armax has quit IRC22:52
*** armax has joined #openstack-meeting22:53
*** dane_leblanc has quit IRC22:56
*** bklei has joined #openstack-meeting22:56
*** gongysh has joined #openstack-meeting23:01
*** Apoorva_ has joined #openstack-meeting23:01
*** gongysh has quit IRC23:03
*** kornica has quit IRC23:03
*** Apoorva has quit IRC23:05
*** rhochmuth has quit IRC23:07
*** armax has quit IRC23:10
*** sdague has quit IRC23:11
*** jamesmcarthur has quit IRC23:16
*** jamesmcarthur has joined #openstack-meeting23:17
*** ykatabam has quit IRC23:22
*** ykatabam has joined #openstack-meeting23:22
*** slaweq has joined #openstack-meeting23:31
*** Julien-zte has quit IRC23:32
*** diablo_rojo has quit IRC23:33
*** Apoorva_ has quit IRC23:33
*** Apoorva has joined #openstack-meeting23:34
*** slaweq has quit IRC23:36
*** chyka has quit IRC23:38
*** chyka has joined #openstack-meeting23:39
*** chyka has quit IRC23:44
*** jamesmcarthur has quit IRC23:45
*** salv-orlando has joined #openstack-meeting23:47
*** sshank has quit IRC23:47
*** sshank has joined #openstack-meeting23:47
*** sshank has quit IRC23:48
*** makowals has joined #openstack-meeting23:48
*** salv-orlando has quit IRC23:52

Generated by 2.15.3 by Marius Gedminas - find it at!