Wednesday, 2017-09-27

*** noslzzp has joined #openstack-meeting00:01
*** mriedem1 has joined #openstack-meeting00:05
*** mriedem has quit IRC00:05
*** mriedem1 is now known as mriedem00:08
*** thorst has joined #openstack-meeting00:08
*** thorst has quit IRC00:09
*** yangyapeng has quit IRC00:11
*** yangyapeng has joined #openstack-meeting00:12
*** noslzzp_ has joined #openstack-meeting00:14
*** noslzzp has quit IRC00:14
*** noslzzp_ has quit IRC00:17
*** noslzzp has joined #openstack-meeting00:21
*** noslzzp has quit IRC00:30
*** hemna_ has joined #openstack-meeting00:34
*** yamahata has quit IRC00:36
*** Apoorva_ has joined #openstack-meeting00:40
*** noslzzp has joined #openstack-meeting00:41
*** Apoorva has quit IRC00:43
*** RongHui11 has joined #openstack-meeting00:44
*** markstur has quit IRC00:46
*** markstur has joined #openstack-meeting00:47
*** tongl has joined #openstack-meeting00:49
*** markstur has quit IRC00:51
*** mugsie has quit IRC00:51
*** song has joined #openstack-meeting00:54
*** noslzzp has quit IRC00:54
*** Apoorva_ has quit IRC00:54
*** fnaval has quit IRC00:56
*** ztang has joined #openstack-meeting00:57
*** esberglu has joined #openstack-meeting00:59
songgood morning everyone!01:00
zhiyuanmorning, song01:00
*** mohankumar has quit IRC01:01
ztangSong, pls introduce whole works of our team in TriCircle in the past week.01:01
songhello I am song from szzt. last week we join the openstack tricircle project.and we are right now working on the tricircle qos test case01:01
zhiyuanshall we wait for joe and yipei a bit?01:02
*** Yipei has joined #openstack-meeting01:02
*** yamamoto has quit IRC01:03
*** yamamoto_ has joined #openstack-meeting01:03
*** esberglu has quit IRC01:03
*** Sukhdev has quit IRC01:03
zhiyuanyipei has joined01:04
Yipeihi zhiyuan01:04
zhiyuanhi yipei01:04
zhiyuan#startmeeting tricircle01:04
openstackMeeting started Wed Sep 27 01:04:41 2017 UTC and is due to finish in 60 minutes.  The chair is zhiyuan. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:04
*** openstack changes topic to " (Meeting topic: tricircle)"01:04
openstackThe meeting name has been set to 'tricircle'01:04
zhiyuanat first, just to remind that we have merged an urgent patch for the smoke test:
patchbotpatch 507340 - tricircle - [Urgent] Add domain infor in smoke test (MERGED)01:05
*** zxh has joined #openstack-meeting01:05
*** YanXing_an has joined #openstack-meeting01:05
*** thorst has joined #openstack-meeting01:06
*** thorst has quit IRC01:06
*** litao__ has joined #openstack-meeting01:06
ztangLast week, Song, zeng you, Yaguang, Xiaohai have join TriCircle. They have finished the compile of the source code in their local envionment.01:06
zhiyuanif your patch failed to pass the smoke test, please do a rebase or recheck01:06
RongHui11got it and thank zhiyuan so much for fix this problem01:07
*** noslzzp has joined #openstack-meeting01:07
zhiyuanto ztang, so they have started the devstack environment with tricircle?01:08
songour szzt  team are working on the qos test01:08
zhiyuancool, any problem found during the environment setup?01:09
RongHui11help to complete the qos smoke test :)01:09
songbecause of the fire wall it not ease to environment setup01:09
ztangSong, please introduce the whole works of our team in TriCircle in the past week. I hope everyone can have a specific module division in this project.01:09
zxhhi,I am xiaohan zhang from szzt,nice to meet everyone!01:09
*** joehuang has joined #openstack-meeting01:10
songwe have set up the dev environment and plan to finish all the qos test case this week.01:10
*** Yoyang has joined #openstack-meeting01:10
ztangVery well01:12
zhiyuanto song, there are two parts of works for the smoke test. (1) modify devstack/ to automatically setup the environment with qos enabled (2) write a yaml file to define the test01:12
songyes,thank you for help. we have read the source code of the tricircle test.01:13
*** xuzhuang has joined #openstack-meeting01:13
*** Tom_ has joined #openstack-meeting01:13
songbut we have a little question about the test environment.01:14
songit is the test environment have fix machine.01:14
ztangto zhiyuan, four new developers have joined to finish the QoS module.01:14
ztangSong is in the Top 50 contributors for CEPH in the world.01:16
xuzhuangsorry for late, (can't connet to freenode this morning)01:16
zhiyuangreat, this can significantly speed up the development!01:16
songwe do not clear about the test environment such as the ip and net,are these all changeless.01:17
songto ztang yes i am working on ceph in before new to openstack.01:17
zhiyuanopenstack CI will schedule some virtual machines to run the test01:18
songbut out team have other peoples all good at in openstack.01:18
songto zhiyuan oh got it.thank you !01:18
songwe found the doc for tricircle devlop is a little few, do we plan to add more doc for develop01:20
zhiyuanyou can refer to tricircle/tempestplugin/ to see how to obtain the IP, if necessary01:20
*** ztang has quit IRC01:21
songto zhiyuan i will set if after the meeting. thanks again.01:21
zhiyuanyes, we lack a doc for how to write yaml definition, but we have a spec:
zhiyuanwhich can be linked somewhere in our doc01:22
songi have read the write yaml it is really a good idea.01:22
*** noslzzp has quit IRC01:25
*** Tom_ has quit IRC01:25
zhiyuanone thing to mention, currently the smoke test only validate whether the resources have been correctly created in local neutron, we don't login the VM to ping other VMs, to test real data plane connectiviry01:25
*** Tom_ has joined #openstack-meeting01:25
RongHui11got it01:26
zhiyuanso you can see that the "validate" task just list resources in local neutron then check their attributes01:27
*** hoangcx has left #openstack-meeting01:28
*** caowei has joined #openstack-meeting01:28
songdo we have the test interface to do that? if not add one for all the test case to use.01:29
*** Tom_ has quit IRC01:30
zhiyuanno, currently we don't have such interface. need to see how this is implemented in tempest01:30
songoh,got it. i think the interface it is need to add. maybe in the local neuron is ok. but it is not really ok.01:32
*** dimak has quit IRC01:32
*** dimak has joined #openstack-meeting01:33
zhiyuanyes, that's possible01:33
*** ijw has quit IRC01:33
*** kiennt26 has joined #openstack-meeting01:35
*** noslzzp has joined #openstack-meeting01:36
songi also have a little question about the is that ok to put the test code and source code in diff pr?01:37
zhiyuan?? tricircle repos contains both source and test01:38
songoh got it because we have diff people to finish the work.01:39
*** bzhao has joined #openstack-meeting01:39
zhiyuanyou can put the feature implementation in one patch, and test in another patch that depends on the former one01:40
zhiyuanhow about the lbaas feature, yipei? I see your reply in the mail list, so michael's reply doesn't solve your problem?01:41
songto zhiyuan oh thank it.01:41
Yipeino, it doesn't01:41
Yipeii tried his solution to verify whether the route table is correct01:42
Yipeiit is correct in my env01:43
*** julim has joined #openstack-meeting01:45
zhiyuanhow the amphorae image is generated?01:45
*** chyka has quit IRC01:46
Yipeiit is generated by octavia itself during installation01:46
*** bbzhao has joined #openstack-meeting01:48
zhiyuanhmm, seems like the problem of haproxy01:49
*** myoung has joined #openstack-meeting01:49
zhiyuanvery strange01:49
johnsomYipei maybe I mis-understood the scenario.  Can you reply with a set of reproduction instructions?01:49
*** myoung has quit IRC01:49
*** markstur has joined #openstack-meeting01:49
johnsomI will try to reproduce it again01:50
Yipeiok, sure01:50
*** VW has joined #openstack-meeting01:50
*** Douhet has quit IRC01:51
Yipeito johnsom, in the mailing-list or here?01:51
johnsomMailing list would be best, or etherpad and post the link in the lbaas channel01:52
*** chyka has joined #openstack-meeting01:52
*** Douhet has joined #openstack-meeting01:52
Yipeiok, got it, thank you, johnsom01:52
johnsomSure, I will try to help01:52
*** markstur has quit IRC01:54
Yipeii will send a mail in the mailing list01:54
*** Apoorva has joined #openstack-meeting01:54
zhiyuanany other topics to discuss?01:55
xuzhuangfor default security group update, i have write the first version code(not test). But I'm01:55
xuzhuangpuzzled about how to test xjob, i'm looking a solution.01:55
zhiyuanif the job fails, you can stop xjob, do some midification, then restart xjob01:57
zhiyuanxjob will re-run the failed job01:57
xuzhuangfor default sg update, could you give me some advice(or some example) about how to use xjob and how to test01:57
*** hongbin has joined #openstack-meeting01:58
zhiyuanconfigure_security_group_rules in is used to sync security group rules01:58
zhiyuanafter sg update, you can call the rpc api in common/xrpcapi.py01:59
zhiyuanthere is a function with the same name02:00
xuzhuangyeah, I am using this solution02:01
*** Yoyang has quit IRC02:01
zhiyuanthen xjob can be informed to run the job02:01
zhiyuanoh, time's up02:02
xuzhuangyeah, thanks02:02
zhiyuanlet's end our meeting, thanks for attending02:03
*** openstack changes topic to "OpenStack Meetings ||"02:03
openstackMeeting ended Wed Sep 27 02:03:45 2017 UTC.  Information about MeetBot at . (v 0.1.4)02:03
openstackMinutes (text):
*** thorst has joined #openstack-meeting02:07
*** xuzhuang has quit IRC02:09
*** RongHui11 has quit IRC02:11
*** unicell has quit IRC02:15
*** song has quit IRC02:15
*** aeng has quit IRC02:16
*** SumitNaiksatam has joined #openstack-meeting02:18
*** epico has joined #openstack-meeting02:20
*** Tom_ has joined #openstack-meeting02:24
*** Tom__ has joined #openstack-meeting02:27
*** Tom___ has joined #openstack-meeting02:29
*** Tom_ has quit IRC02:29
*** Tom__ has quit IRC02:31
*** VW has quit IRC02:36
*** gongysh has joined #openstack-meeting02:38
*** esberglu has joined #openstack-meeting02:42
*** unicell has joined #openstack-meeting02:43
*** VW has joined #openstack-meeting02:45
*** esberglu has quit IRC02:47
*** unicell has quit IRC02:48
*** erlon has quit IRC02:48
*** kevzha01 has quit IRC02:48
*** thorst has quit IRC02:48
*** unicell has joined #openstack-meeting02:56
*** unicell has quit IRC03:00
*** kevzha01 has joined #openstack-meeting03:00
*** unicell has joined #openstack-meeting03:08
*** unicell has quit IRC03:12
*** ijw has joined #openstack-meeting03:12
*** rakhmerov has quit IRC03:14
*** akuznetsova has quit IRC03:16
*** ijw has quit IRC03:17
*** dtrainor has quit IRC03:20
*** akuznetsova has joined #openstack-meeting03:24
*** rakhmerov has joined #openstack-meeting03:28
*** yangyapeng has quit IRC03:32
*** yangyapeng has joined #openstack-meeting03:32
*** gyee has quit IRC03:33
*** VW has quit IRC03:35
*** yangyapeng has quit IRC03:37
*** epico has quit IRC03:42
*** thorst has joined #openstack-meeting03:45
*** Sukhdev has joined #openstack-meeting03:46
*** gongysh has quit IRC03:48
*** Tom___ has quit IRC03:49
*** Tom has joined #openstack-meeting03:50
*** ad_rien_ has quit IRC03:51
*** epico has joined #openstack-meeting03:53
*** dbecker has quit IRC03:53
*** diga has joined #openstack-meeting03:53
*** aeng has joined #openstack-meeting03:53
*** Tom has quit IRC03:55
*** krtaylor has quit IRC04:00
*** coolsvap has joined #openstack-meeting04:01
*** krtaylor has joined #openstack-meeting04:01
*** krtaylor has quit IRC04:08
*** dbecker has joined #openstack-meeting04:08
*** markstur has joined #openstack-meeting04:08
*** mahatic has joined #openstack-meeting04:08
*** MinWookKim has joined #openstack-meeting04:09
*** markstur has quit IRC04:13
*** thorst has quit IRC04:16
*** ianychoi_ has joined #openstack-meeting04:20
*** Apoorva_ has joined #openstack-meeting04:21
*** hongbin has quit IRC04:21
*** reedip_ has joined #openstack-meeting04:21
*** peterlisak_ has joined #openstack-meeting04:22
*** zhonghua has joined #openstack-meeting04:22
*** manjeets_ has joined #openstack-meeting04:22
*** mfranc213_ has joined #openstack-meeting04:22
*** gongysh has joined #openstack-meeting04:22
*** X-dark_ has joined #openstack-meeting04:22
*** korzen__ has joined #openstack-meeting04:22
*** mhenkel_ has joined #openstack-meeting04:23
*** spotz_ has joined #openstack-meeting04:24
*** colettecello has joined #openstack-meeting04:25
*** phuoc_ has joined #openstack-meeting04:27
*** Sukhdev has quit IRC04:29
*** Apoorva has quit IRC04:29
*** hemna_ has quit IRC04:29
*** mriedem has quit IRC04:29
*** zhonghua2 has quit IRC04:29
*** X-dark has quit IRC04:29
*** cburgess has quit IRC04:29
*** spotz has quit IRC04:29
*** ianychoi has quit IRC04:29
*** jrist has quit IRC04:29
*** haleyb has quit IRC04:29
*** palexster has quit IRC04:29
*** flaper87 has quit IRC04:29
*** sambetts|afk has quit IRC04:29
*** mhenkel has quit IRC04:29
*** korzen_ has quit IRC04:29
*** manjeets has quit IRC04:29
*** peterlisak has quit IRC04:29
*** number80 has quit IRC04:29
*** mfranc213 has quit IRC04:29
*** ericyoung has quit IRC04:29
*** stephenfin has quit IRC04:29
*** honza has quit IRC04:29
*** dmsimard has quit IRC04:29
*** gothicmindfood has quit IRC04:29
*** X-dark_ is now known as X-dark04:29
*** peterlisak_ is now known as peterlisak04:29
*** honza has joined #openstack-meeting04:29
*** kiennt26 has quit IRC04:30
*** stephenfin has joined #openstack-meeting04:30
*** honza is now known as Guest8588804:30
*** sambetts_ has joined #openstack-meeting04:30
*** cburgess has joined #openstack-meeting04:30
*** ericyoung has joined #openstack-meeting04:30
*** claudiub has joined #openstack-meeting04:30
*** palexster has joined #openstack-meeting04:31
gongysh#startmeeing tacker04:32
*** edwarnicke has quit IRC04:32
*** m-greene_ has quit IRC04:32
gongysh#startmeeing tacker04:32
gongyshwhere is the meeting robot?04:33
*** haleyb has joined #openstack-meeting04:33
gongysh#startmeeing tacker04:33
*** radez has quit IRC04:33
digagongysh: startmeeting spelling04:33
*** edwarnicke has joined #openstack-meeting04:33
gongysh#startmeeting tacker04:33
openstackMeeting started Wed Sep 27 04:33:59 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:34
*** openstack changes topic to " (Meeting topic: tacker)"04:34
openstackThe meeting name has been set to 'tacker'04:34
*** slagle has quit IRC04:34
gongyshdiga, thanks04:34
digagongysh: :) NP04:34
gongyshthe new mac pro's keyboard is wierd.04:34
*** m-greene_ has joined #openstack-meeting04:35
gongyshToday, we will have a short meeting.04:35
gongysh#topic bp04:35
*** openstack changes topic to "bp (Meeting topic: tacker)"04:35
patchbotpatch 501792 - tacker-specs - Support Kubernetes as VIM in Tacker04:36
gongyshphuoc_, hi04:36
*** jrist has joined #openstack-meeting04:36
phuoc_gongysh, hi04:36
gongyshI have a comment about the NFV resource template using k8s template.04:36
*** flaper87 has joined #openstack-meeting04:36
*** Yipei has left #openstack-meeting04:36
phuoc_I saw it04:36
*** hemna_ has joined #openstack-meeting04:37
gongyshI think we should still use previous nfv resource template, and do k8s translator.04:37
gongyshso that we can have a unified tosca template for both vnf and c-vnf.04:37
*** dmsimard has joined #openstack-meeting04:37
phuoc_but currently, K8s translator is not implemented04:37
gongyshphuoc_, we should have it in our own project.04:38
phuoc_and there are some problems04:38
gongyshI mean implement the translator our own at tacker repo.04:38
phuoc_example Kubernetes have many templates for their resources04:38
*** reedip_ has quit IRC04:38
*** number80 has joined #openstack-meeting04:38
phuoc_I want to do it but it have many issues need to figure out04:38
*** reedip_ has joined #openstack-meeting04:39
*** radez has joined #openstack-meeting04:39
phuoc_I will contact to mr Sidhar and find the good solution for it04:39
gongyshphuoc_, this is the way we should do. please consider refactoring the spec.04:39
phuoc_gongysh, I got it04:39
*** Apoorva_ has quit IRC04:40
phuoc_IMO, Tacker should implement c-VNFM for managing c-VNF04:40
longkb_Hi, about the bp
patchbotpatch 502216 - tacker-specs - Enabling VNF high availability deployment and  man...04:40
gongyshlongkb_, welcome to tacker meeting04:40
*** tovin07_ has joined #openstack-meeting04:40
longkb_I and xuan0802 want to enable HA for VNF deployment04:40
gongyshto promote the spec,  you need active involvement.04:40
longkb_We make a comparision between some direction
*** slagle has joined #openstack-meeting04:41
longkb_could you guy put a comment on the Google docs file :)04:41
gongyshand do you have any idea about how to implement it?04:41
*** armax has joined #openstack-meeting04:42
longkb_I plant to deploy the VNF as Active-Active or Active-standby redundancy model :)04:43
gongyshlongkb_,  even with your proposal, you will need a poc implement to get the spec merged.04:44
*** xuan0802 has joined #openstack-meeting04:44
*** markstur has joined #openstack-meeting04:46
gongyshlongkb_, It is good to have it implemented in tacker repo which will allow us to have great control.04:46
longkb_Ok. I will try to make a code for review ASAP.04:46
gongyshlongkb_, the spec's idea is itself fine.04:46
longkb_Thanks gongysh :)04:47
MinWookKimHello, Please could you see a comment on my blueprint?
patchbotpatch 505466 - tacker-specs - Zabbix Plugin for Application Monitoring in Tacker...04:47
*** psachin has joined #openstack-meeting04:47
*** xuan0802 has quit IRC04:47
gongyshMinWookKim, hi04:48
gongyshwelcome into tacker04:48
MinWookKimgongysh, Hello :)04:49
YanXing_anMinWookKim, welcome04:49
gongyshYanXing_an,  could you track this spec?04:49
MinWookKimYanXing_an, Hello :)04:49
longkb_Welcome to Tacker, MinwooKim :)04:49
MinWookKimlongkb_, Hello Nice to meet you :)04:50
gongyshYanXing_an, helo04:50
YanXing_angongsh, ok, i will review this patch these days04:50
digaMinWookKim: Welcome to Tacker!04:50
*** markstur has quit IRC04:50
MinWookKimdiga, Hello thanks a lot :)04:50
gongysh#topic document04:51
*** openstack changes topic to "document (Meeting topic: tacker)"04:51
gongyshas you know, we will have to manage our document since the refactor of openstack doc.04:51
gongyshso you guys can find time to write document about tacker.04:52
gongyshI have two patched merged: 1. to install tacker via kolla, 2. separate tacker with target vim.04:52
YanXing_anMinWookKim, it's useful to monitor vnf at app level04:53
gongyshnext will be 1. openstack target vim installation in kolla way.04:53
*** reedip_ has quit IRC04:53
gongysh2.  tacker horizon usage04:53
gongyshif you guys are interested in these tasks, you can pick.04:54
MinWookKimYanXing_an, Thanks a lot. I will improve this proposal04:54
*** Alex_Staf has joined #openstack-meeting04:54
gongysh#topic open discussion04:55
*** openstack changes topic to "open discussion (Meeting topic: tacker)"04:55
gongyshYanXing_an, I forgot your bp: ns with vnffg04:55
phuoc_gongysh: for, I think we should merge it soon04:56
patchbotpatch 505602 - tacker - Index block_storage_usage_guide doc04:56
YanXing_angongysh, i am writing the specs about indirect mode vnf and VeVnfm reference point, ns-vnffg is still coding04:56
digagongysh: we need sometime for writing spec, because there is lot of study involved in indirect vnf feature04:58
gongyshYanXing_an, diga yes04:58
digagongysh: i believe we will cordinate in between and will come up with base spec till next meeting04:58
digagongysh: because there are lot of thing are unclear yet, need to investigate more04:59
digagongysh: this is large feature05:00
digagongysh: I appreciate YanXing_an for his thought to proposing this feature05:01
gongyshYanXing_an, but please make the essential feature work first. ns vnffg05:02
YanXing_angongysh, ok, got it05:03
gongyshanything else?05:03
gongysh30 secs count down05:04
diganothing from my side05:04
phuoc_we should check it
patchbotpatch 505602 - tacker - Index block_storage_usage_guide doc05:04
gongyshphuoc_, have commented.05:05
phuoc_user can have doc and use block storage in Tacker :)05:05
phuoc_gongysh, my mistake :)05:05
gongyshok. if nothing, we can end today's meeting. please make active contribution. thanks05:06
*** openstack changes topic to "OpenStack Meetings ||"05:06
openstackMeeting ended Wed Sep 27 05:06:20 2017 UTC.  Information about MeetBot at . (v 0.1.4)05:06
*** MinWookKim has left #openstack-meeting05:06
openstackMinutes (text):
*** chyka has quit IRC05:11
*** janki has joined #openstack-meeting05:11
*** marios has joined #openstack-meeting05:12
*** zhurong has joined #openstack-meeting05:13
*** thorst has joined #openstack-meeting05:13
*** caowei has quit IRC05:15
*** lbrune has joined #openstack-meeting05:18
*** phuoc_ has left #openstack-meeting05:20
*** sridharg has joined #openstack-meeting05:21
*** markstur has joined #openstack-meeting05:23
*** esberglu has joined #openstack-meeting05:25
*** markstur has quit IRC05:28
*** Tom has joined #openstack-meeting05:28
*** esberglu has quit IRC05:29
*** caowei has joined #openstack-meeting05:45
*** thorst has quit IRC05:47
*** Tom has quit IRC05:49
*** dalvarez has quit IRC05:49
*** Tom has joined #openstack-meeting05:51
*** radez has quit IRC05:52
*** jamesmcarthur has joined #openstack-meeting05:53
*** radeks has joined #openstack-meeting05:57
*** jamesmcarthur has quit IRC05:58
*** markstur has joined #openstack-meeting06:00
*** markstur has quit IRC06:04
*** aeng has quit IRC06:06
*** kevzha01 has quit IRC06:07
*** liuyulong has joined #openstack-meeting06:16
*** armax has quit IRC06:19
*** Alex_Staf has quit IRC06:20
*** radeks has quit IRC06:21
*** Tom has quit IRC06:26
*** dalvarez has joined #openstack-meeting06:30
*** hashar has joined #openstack-meeting06:33
*** markstur has joined #openstack-meeting06:36
*** rcernin has joined #openstack-meeting06:39
*** rossella_s has joined #openstack-meeting06:40
*** e0ne has joined #openstack-meeting06:40
*** armax has joined #openstack-meeting06:41
*** yamamoto_ has quit IRC06:41
*** markstur has quit IRC06:41
*** thorst has joined #openstack-meeting06:45
*** yamamoto has joined #openstack-meeting06:45
*** Tom has joined #openstack-meeting06:47
*** armax has quit IRC06:50
*** lbrune has quit IRC06:55
*** rossella_s has quit IRC06:56
*** YanXing_an has quit IRC06:57
*** YanXing_an has joined #openstack-meeting06:58
*** tobiajo has joined #openstack-meeting07:02
*** yamamoto_ has joined #openstack-meeting07:04
*** yamamoto has quit IRC07:04
*** rledisez has joined #openstack-meeting07:05
*** iyamahat has joined #openstack-meeting07:05
*** iyamahat has quit IRC07:06
*** iyamahat has joined #openstack-meeting07:06
*** fzdarsky has joined #openstack-meeting07:06
*** rledisez has left #openstack-meeting07:07
*** e0ne has quit IRC07:08
*** lbrune has joined #openstack-meeting07:10
*** yamamoto_ has quit IRC07:10
*** tongl has quit IRC07:12
*** tssurya has joined #openstack-meeting07:13
*** esberglu has joined #openstack-meeting07:13
*** markstur has joined #openstack-meeting07:14
*** treiz has joined #openstack-meeting07:16
*** lamt has quit IRC07:16
*** Dinesh_Bhor has quit IRC07:17
*** thorst has quit IRC07:17
*** esberglu has quit IRC07:17
*** markstur has quit IRC07:18
*** tdasilva has quit IRC07:18
*** yamamoto has joined #openstack-meeting07:18
*** rbartal has joined #openstack-meeting07:19
*** Dinesh_Bhor has joined #openstack-meeting07:21
*** tesseract has joined #openstack-meeting07:21
*** oidgar has joined #openstack-meeting07:33
*** Alex_Staf has joined #openstack-meeting07:41
*** tdasilva has joined #openstack-meeting07:42
*** iyamahat has quit IRC07:46
*** ijw has joined #openstack-meeting07:47
*** markstur has joined #openstack-meeting07:51
*** alexchadin has joined #openstack-meeting07:53
*** markstur has quit IRC07:55
*** ad_rien_ has joined #openstack-meeting07:57
*** radeks has joined #openstack-meeting07:58
*** hashar has quit IRC07:58
*** ijw has quit IRC08:02
*** yamahata has joined #openstack-meeting08:03
*** ralonsoh has joined #openstack-meeting08:04
*** hashar has joined #openstack-meeting08:04
*** Tom has quit IRC08:06
*** ad_rien_ has quit IRC08:06
*** efried has quit IRC08:08
*** ad_rien_ has joined #openstack-meeting08:10
*** kevzha01 has joined #openstack-meeting08:10
*** zhurong has quit IRC08:11
*** thorst has joined #openstack-meeting08:14
*** noslzzp_ has joined #openstack-meeting08:15
*** noslzzp has quit IRC08:15
*** kevzha01 has quit IRC08:15
*** Tom has joined #openstack-meeting08:16
*** makowals has quit IRC08:17
*** noslzzp_ has quit IRC08:19
*** efried has joined #openstack-meeting08:19
*** Tom has quit IRC08:20
*** noslzzp has joined #openstack-meeting08:20
*** noslzzp has quit IRC08:23
*** brault has quit IRC08:24
*** noslzzp has joined #openstack-meeting08:24
*** noslzzp has quit IRC08:27
*** baoli has joined #openstack-meeting08:28
*** markstur has joined #openstack-meeting08:28
*** yamahata has quit IRC08:29
*** Tom has joined #openstack-meeting08:29
*** noslzzp has joined #openstack-meeting08:29
*** zhurong has joined #openstack-meeting08:30
*** XueFeng has quit IRC08:31
*** XueFeng has joined #openstack-meeting08:32
*** makowals has joined #openstack-meeting08:32
*** markstur has quit IRC08:32
*** baoli has quit IRC08:32
*** noslzzp has quit IRC08:33
*** noslzzp has joined #openstack-meeting08:33
*** noslzzp_ has joined #openstack-meeting08:39
*** noslzzp has quit IRC08:39
*** alexchadin has quit IRC08:41
*** iyamahat has joined #openstack-meeting08:42
*** alexchadin has joined #openstack-meeting08:42
*** iyamahat has quit IRC08:43
*** iyamahat has joined #openstack-meeting08:43
*** noslzzp_ has quit IRC08:45
*** noslzzp has joined #openstack-meeting08:45
*** alexchadin has quit IRC08:48
*** thorst has quit IRC08:50
*** iyamahat has quit IRC08:53
*** noslzzp has quit IRC08:53
*** jamesmcarthur has joined #openstack-meeting08:53
*** noslzzp has joined #openstack-meeting08:55
*** jamesmcarthur has quit IRC08:58
*** noslzzp has quit IRC08:59
*** esberglu has joined #openstack-meeting09:01
*** noslzzp has joined #openstack-meeting09:02
*** lbrune has left #openstack-meeting09:02
*** joehuang has quit IRC09:03
*** noslzzp has quit IRC09:04
*** markstur has joined #openstack-meeting09:05
*** noslzzp has joined #openstack-meeting09:05
*** claudiub|2 has joined #openstack-meeting09:05
*** esberglu has quit IRC09:06
*** claudiub|3 has joined #openstack-meeting09:06
*** makowals has quit IRC09:07
*** alexchadin has joined #openstack-meeting09:07
*** alexchadin has quit IRC09:08
*** claudiub has quit IRC09:08
*** alexchadin has joined #openstack-meeting09:08
*** markstur has quit IRC09:09
*** claudiub|2 has quit IRC09:10
*** alexchadin has quit IRC09:11
*** toscalix has joined #openstack-meeting09:15
*** noslzzp has quit IRC09:15
*** electrofelix has joined #openstack-meeting09:15
*** makowals has joined #openstack-meeting09:16
*** e0ne has joined #openstack-meeting09:16
*** noslzzp has joined #openstack-meeting09:16
*** noslzzp has quit IRC09:19
*** yamamoto has quit IRC09:19
*** radeks has quit IRC09:19
*** radeks has joined #openstack-meeting09:20
*** tssurya has quit IRC09:22
*** noslzzp has joined #openstack-meeting09:22
*** Guest85888 is now known as honza09:22
*** noslzzp has quit IRC09:25
*** numans has quit IRC09:25
*** iyamahat has joined #openstack-meeting09:26
*** askb has quit IRC09:26
*** noslzzp has joined #openstack-meeting09:26
*** askb has joined #openstack-meeting09:27
*** sambetts_ is now known as sambetts09:27
*** numans has joined #openstack-meeting09:28
*** radeks has quit IRC09:30
*** fzdarsky has quit IRC09:30
*** noslzzp has quit IRC09:31
*** iyamahat has quit IRC09:31
*** askb has quit IRC09:32
*** radeks has joined #openstack-meeting09:32
*** brault has joined #openstack-meeting09:33
*** noslzzp has joined #openstack-meeting09:33
*** askb has joined #openstack-meeting09:33
*** noslzzp has quit IRC09:37
*** noslzzp has joined #openstack-meeting09:40
*** markstur has joined #openstack-meeting09:41
*** noslzzp has quit IRC09:43
*** noslzzp has joined #openstack-meeting09:44
*** markstur has quit IRC09:46
*** electrofelix has quit IRC09:46
*** thorst has joined #openstack-meeting09:47
*** radeks has quit IRC09:48
*** afazekas is now known as afazekas|seek4fo09:48
*** noslzzp has quit IRC09:49
*** noslzzp has joined #openstack-meeting09:49
*** hashar is now known as hasharAway09:50
*** sdague has joined #openstack-meeting09:50
*** ad_rien_ has quit IRC09:51
*** noslzzp has quit IRC09:55
*** diga has quit IRC09:55
*** noslzzp has joined #openstack-meeting09:57
*** radeks has joined #openstack-meeting09:58
*** esberglu has joined #openstack-meeting10:00
*** noslzzp has quit IRC10:00
*** noslzzp has joined #openstack-meeting10:00
*** korzen__ is now known as korzen_10:01
*** noslzzp has quit IRC10:03
*** d0ugal has joined #openstack-meeting10:03
*** YanXing_an has quit IRC10:03
*** esberglu has quit IRC10:04
*** tovin07_ has quit IRC10:05
*** noslzzp has joined #openstack-meeting10:06
*** b1airo has joined #openstack-meeting10:10
*** noslzzp has quit IRC10:13
*** noslzzp has joined #openstack-meeting10:15
*** thorst has quit IRC10:18
*** markstur has joined #openstack-meeting10:18
*** Tom has quit IRC10:19
*** gongysh has quit IRC10:19
*** zhurong has quit IRC10:20
*** Tom has joined #openstack-meeting10:20
*** yamamoto has joined #openstack-meeting10:20
*** Tom has quit IRC10:21
*** zxh has quit IRC10:22
*** markstur has quit IRC10:23
*** noslzzp has quit IRC10:23
*** noslzzp has joined #openstack-meeting10:24
*** noslzzp has quit IRC10:27
*** yamahata has joined #openstack-meeting10:27
*** noslzzp has joined #openstack-meeting10:30
*** jkilpatr has quit IRC10:34
*** noslzzp has quit IRC10:39
*** noslzzp has joined #openstack-meeting10:40
*** fzdarsky has joined #openstack-meeting10:42
*** noslzzp has quit IRC10:43
*** noslzzp has joined #openstack-meeting10:44
*** caowei has quit IRC10:45
*** d0ugal has quit IRC10:48
*** noslzzp has quit IRC10:49
*** noslzzp has joined #openstack-meeting10:49
*** daveholland has joined #openstack-meeting10:53
*** rbudden has joined #openstack-meeting10:54
*** noslzzp has quit IRC10:55
*** markstur has joined #openstack-meeting10:56
*** hemna_ has quit IRC10:57
*** noslzzp has joined #openstack-meeting10:57
*** oneswig has joined #openstack-meeting10:58
oneswig#startmeeting scientific-wg11:00
openstackMeeting started Wed Sep 27 11:00:54 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.11:00
*** openstack changes topic to " (Meeting topic: scientific-wg)"11:00
openstackThe meeting name has been set to 'scientific_wg'11:00
oneswigahoy there11:01
oneswig#link Agenda for today
*** martial_ has joined #openstack-meeting11:01
oneswigHi daveholland, thought you were on holiday?11:01
*** markstur has quit IRC11:01
oneswigbtw what is your job title, for attribution purposes?11:01
davehollandI wish ;)11:01
martial_good morning11:01
oneswigHi martial_11:02
oneswig#chair martial_11:02
openstackCurrent chairs: martial_ oneswig11:02
daveholland"Principal Systems Administrator" (I think that's an anagram of "dogsbody")11:02
oneswigOK, thanks, noted11:02
martial_#chair b1airo11:02
openstackCurrent chairs: b1airo martial_ oneswig11:02
*** d0ugal has joined #openstack-meeting11:02
martial_morning Blair11:02
oneswighi b1airo, morning11:02
oneswigHi johnthetubaguy :-)11:02
* johnthetubaguy waves back at oneswig 11:02
b1airoevening :-)11:02
*** jkilpatr has joined #openstack-meeting11:02
martial_b1airo: we will get to play in your timezone sandbox soon hopefully :)11:03
oneswigOK - on which subject....11:03
b1airooneswig, johnthetubaguy - are you guys waving at each other from opposite desks now?11:03
*** epico has quit IRC11:03
oneswig#topic Sydney hackathon11:03
*** openstack changes topic to "Sydney hackathon (Meeting topic: scientific-wg)"11:03
oneswigb1airo: only virtually :-)11:03
martial_oneswig: what about the hackaton? :)11:04
johnthetubaguyyeah, multiple chat tools maybe11:04
oneswigSaw him yesterday at OpenStack UK though!11:04
oneswigAh, yes. The hackathon.  Is looking for mentors and supporters.  Its the weekend before the summit, starting Friday 3pm (in Sydney)11:04
b1airoICQ 4eva!11:04
oneswigAlso seems to mention "Mentors will also receive a free pass to the Sydney OpenStack Summit"11:05
oneswigjust leaving that htere11:05
martial_oneswig: yes I confirm11:05
oneswigmartial_: are you a mentor?11:06
b1airoheh, i'll ping a couple of people that might be good candidates if they are in the country at the time11:06
b1airounfortunately it won't work for me, can't get to Sydney until Sunday evening11:06
oneswigYou and Wojciech too! :-)11:07
martial_oneswig: I registered to be one, and David put me in contact with the lead mentor11:07
*** jkilpatr has quit IRC11:07
martial_oneswig: are you still judging?11:07
oneswigI have not heard confirmation on that but am assuming I'll be involved somewhere11:08
oneswigShould be fun :-)11:08
martial_sounds fun to me, indeed :)11:09
oneswigOK, move on?11:09
oneswig#topic Open Research Cloud11:09
*** openstack changes topic to "Open Research Cloud (Meeting topic: scientific-wg)"11:09
oneswignext ORC meeting starts about now in Amsterdam.11:09
martial_well they are still setting up, I am on the GoToMeeting :11:10
oneswigAhah, multi-tasking!11:10
martial_well I can listen onto one and type in this one :)11:10
b1airowow, you can live-IRC it for us11:10
oneswigIt's almost like we are in the room :-)11:10
martial_should start in 20 minutes11:10
martial_the video feed is already up ...11:11
oneswigTomorrow there is a technical session, in which there is a section designated "Scientific WG perspectives"11:11
b1airooneswig, martial_ - are you across any of the plans/intentions/pie-in-the-sky ideas for ORC meeting in Sydney ?11:11
*** timothyb89 has quit IRC11:11
oneswigI saw some meeting invites that's all11:11
b1airooh really? do we need to come up with a perspective then!?11:11
oneswigWell this is it, I've got writers block11:12
oneswigMartial are you covering the NIST project?11:12
martial_b1airo: it will be a panel I believe more than anything else11:13
martial_oneswig: the IEEE / NIST P2302?11:13
davehollandthe only perspective we have to offer is "please don't invent another standard" (for auth etc)11:13
oneswigmartial_: are there others?11:13
martial_b1airo: if there are slides to be had, it might not be crazy :)11:13
oneswigdaveholland: seconded...11:14
martial_oneswig: now that I think, likely no :)11:14
martial_oneswig: Craig Lee from IEEE will be there so they are covered11:14
martial_I will cover the P2302 for the foundation for now11:14
martial_(per my conversation with David)11:14
oneswigOK.  We are joining remotely for that session and I was thinking of summarising the new book chapter, however it's written by Enol who's hosting this session so he's probably already got it well covered...11:15
*** radeks has quit IRC11:15
*** thorst has joined #openstack-meeting11:15
hogepodgeSpeaking of the book11:16
oneswigHi hogepodge - welcome and good morning!11:16
martial_Ildiko Vancsa from the Foundation is at the ORC, so she is covering for OpenStack11:16
hogepodgeIt's due this Friday no exceptions all content and finished diagrams11:16
martial_hogepodge: good morning, and yes we confirm11:16
martial_hogepodge: what timezone on Friday? :)11:17
oneswigit is.  I believe I only have the new federation chapter to review11:17
hogepodgeLet's say noon central time for Kathy's sake11:17
oneswighogepodge: works for me.  Did you see, we gathered some proposals for cover art?11:18
martial_oneswig: Mike is finishing his "Research in Production" chapter and I am reviewing it to add11:18
oneswig#link down here somewhere
oneswigmartial_: is that a chapter or a case study?11:18
hogepodgeThey need to verify that they license is good for the cover, I'll forward it to the team11:18
oneswighogepodge: the images have been offered on the terms previously described, I think they are clear on that.11:19
martial_oneswig: a little of both, it is a longer version of his lighting talk from Boston11:19
b1airoon the cover art...11:20
*** jkilpatr has joined #openstack-meeting11:21
oneswigmartial_: to fit as a chapter it'd want a broad range of case studies11:21
b1airoi like the SKA idea, though i do wonder whether it might raise a few eyebrows to have pics of SKA antennae in Australia given that so far the Aus contingent seems to be traditionally HPC focused...11:21
oneswigb1airo: a good observation11:22
oneswigI gave them access to our OpenStack SKA system just last week however11:23
martial_oneswig: good observation, I am passing along this information11:23
b1airocertainly the Pawsey Supercomputing centre still uses OpenStack, but at this point I understand it to be a side-show (i could be wrong/out-of-date here though)11:23
oneswigthey are now tainted with the corruption of software-defiend infrastructure11:23
*** strigazi has quit IRC11:23
*** strigazi has joined #openstack-meeting11:24
b1airohaha, good work11:24
oneswigb1airo: specifically this was a team from UWA, might be connected, might not11:24
*** _pewp_ has quit IRC11:24
oneswigThe SKA Organisation contributed the images, I don't think there's any perceived issue from them11:25
*** noslzzp has quit IRC11:25
b1airocool, no probs then11:25
martial_#topic Book11:26
*** openstack changes topic to "Book (Meeting topic: scientific-wg)"11:26
martial_(totally forgot to change the topic :) )11:26
oneswigI think the main body of work is ready, the additions appear close and one schedule11:27
*** thorst has quit IRC11:27
oneswighogepodge: would it help to have access to get started on the next stage for the completed sections?11:27
*** pcaruana has joined #openstack-meeting11:27
*** noslzzp has joined #openstack-meeting11:28
*** _alastor__ has quit IRC11:28
oneswigWell I think we are on schedule, anyway, providing the sky doesn't fall in in the meantime...11:30
oneswigmove on?11:30
*** _alastor__ has joined #openstack-meeting11:30
oneswig#topic Sydney Forum11:30
*** openstack changes topic to "Sydney Forum (Meeting topic: scientific-wg)"11:30
oneswigI must confess I have not been keeping up with this11:30
*** liuyulong has quit IRC11:30
*** _pewp_ has joined #openstack-meeting11:31
b1airome either11:31
b1airothe close date for Forum topic submissions is 29th11:31
martial_unless I misunderstood, they request from us a list of the talks/sessions we intend to have?11:31
*** ad_rien_ has joined #openstack-meeting11:32
oneswigWhich ML is it discussed on?11:32
b1airomartial_, not quite - the idea for the process is that the community (including WGs/SIGs) first brainstorm internally and that provides a way to shake out duplicates and form up ideas, then session leaders go ahead and put the proposals in11:33
b1airothat brainstorming phase is more-or-less over already, so i think we need to figure out whether we have any good ideas for Forum sessions between now and tomorrow and then go ahead and then get someone to submit an abstract11:34
*** noslzzp has quit IRC11:34
martial_oneswig: I got an email from the "User-committee" ML11:34
*** markstur has joined #openstack-meeting11:34
oneswigthanks martial_ b1airo, now I recall the process.11:34
martial_our plan is to propose a BoF and lighting talk sessions so far11:35
oneswigSo what to advocate..11:35
johnthetubaguythe sessions are certainly picked by representatives from both the UC and TC based on the submitted ideas, so that sounds right11:35
b1airoi would like to have another session on "opportunistic" instances, but i feel a bit phoney doing so given i never properly followed up on the same session from last Forum11:35
johnthetubaguyhonestly, no one seems to be working on much of that right now, I wrote up the spec from the discussions11:35
johnthetubaguysimilar issues with quotas right now11:35
b1airomartial_, no we already have a BOF and lightening talk session in the main Summit's Working Group agenda11:35
martial_b1airo: so oneswig is not the only one confused I confess :)11:36
oneswigb1airo: I think it's a missing piece. It would be surprising if the public cloud wg weren't already onto this too11:36
*** noslzzp has joined #openstack-meeting11:36
martial_@oneswig: re ORC "slides would be good"11:37
oneswigOK thanks martial_, noted.11:37
b1airojohnthetubaguy, yeah and i meant to try and continue that conversation with you on the draft spec11:37
johnthetubaguyI think something useful is expressing the relative importance of a top few efforts, and agreeing that with other SIGs and WGs11:38
oneswigjohnthetubaguy: would it be worthwhile to add an item on Ironic resources and traits11:38
b1airolately i have been wondering if there might be a simple way to get 80% of what i want by just writing an external service that arbitrated access to some defined free capacity11:38
*** markstur has quit IRC11:39
*** rbowen has quit IRC11:39
johnthetubaguyoneswig: unsure who would be there, but possibly on cross project scheduling requirements in general, just making sure everyone is happy with the placement plan overall?11:39
zioprotosorry I am late, but I arrived11:39
oneswigHi zioproto!11:39
oneswigJust talking forum topics11:40
martial_@stig: agenda has shifted to 13:15 to 14:15 for "Technical Perspectives from the SWGs"11:40
b1airoo/ zioproto11:40
martial_(Amsterdam time)11:40
johnthetubaguyb1airo: thats a lot of what blazar is doing, there was PTG discussion that ended with just increase the quota for folks who request the feature for now11:40
oneswigOK thanks martial_11:40
*** radeks has joined #openstack-meeting11:40
zioprotoguys for Sidney we are looking for moderators for the Forum11:40
zioprotoanyone wants to jump in ?11:40
zioprotoModerators should propose the sessions they sign up for to
b1airojohnthetubaguy, as in have Blazar increase the quota?11:41
*** rossella_s has joined #openstack-meeting11:41
martial_zioproto: good timing and welcome11:42
johnthetubaguyb1airo: I think I just confused things, I mean something like blazar would do the increase in quota, use tags on instances to manage the reaping of instances, etc (i.e. build a prototype outside Nova for now, quota is the main sticking point)11:42
martial_so I am still confused about what you need from us related to our forum proposals. I apologize in advance, but clarification on the purpose and example of topics would be appreciated11:43
martial_^ zioproto11:43
*** noslzzp has quit IRC11:43
b1airojohnthetubaguy, yep thanks, think i have a vague picture of what you're talking about - would have to be quota plus aggregates for reservation of some kind though, for us quota is fairly useless as we have *way* more quota allocated than we have actual capacity11:43
*** noslzzp has joined #openstack-meeting11:44
johnthetubaguyb1airo: OK, so yours must be a different use case to the one in the spec, needs more follow up another time I guess11:44
zioprotomartial_: I am looking for moderators for the sessions that appear at After you login with your openstack account you should be able to see the session names11:44
b1airomartial_, you could look at the Boston Forum agenda11:44
johnthetubaguyfor me the forum is all about getting Users and Developers together agreeing the priorities and requirements for the next cycle, keeping in sync with what has happened so far, etc11:45
johnthetubaguythe sessions that connection on going efforts with interested folks, worked really well in Boston11:45
oneswigDo we know the scheduling of forum sessions yet?11:46
johnthetubaguysome of the relative priority setting stuff seemed to work quite well in Boston too11:46
johnthetubaguylike ignore all these things, this is the one thing that is blocking everything (application credentials came out of that sort of discussion)11:46
johnthetubaguynot sure if that helps with context11:47
oneswigthanks johnthetubaguy I think it does.11:47
b1airoactually looking at the list of topics already suggested and hearing johnthetubaguy mention getting Ops & Users & Devs together reminded me that we no longer seem to have things like the Ops sessions of old11:47
*** rossella_s has quit IRC11:47
johnthetubaguythere is more context here:
martial_maybe an HPC Ops then?11:48
johnthetubaguythe idea is to work together to come up with join sessions11:48
johnthetubaguyrather than have ops come to dev sessions, and v.v.11:48
oneswigjohnthetubaguy: seen this one?
b1airoyeah i understand the motivation to jointly get the agenda together, but in the process we seem to have lost what were some very well attended sessions previously, e.g., "Ceph Operators"11:49
johnthetubaguyoneswig: I haven't reviewed any of them honestly, mostly as I am not choosing and not attending11:49
b1airoseems important to have a home for those things too11:49
*** noslzzp has quit IRC11:49
johnthetubaguyoneswig: that sounds like pre-ptg speak11:49
johnthetubaguyoneswig: I guess its more a follow on11:50
*** noslzzp has joined #openstack-meeting11:50
*** bobh has joined #openstack-meeting11:50
oneswigjohnthetubaguy: right, it does read like that.11:50
oneswigb1airo: Is there not a Ceph BoF?  Really ought to be, I agree11:51
b1airoyeah i will propose and see what happens11:51
johnthetubaguyso looping back, I like that session because it is getting feedback around existing ongoing work, which is good11:51
oneswigWould love to share our current weirdness with the room :-)11:51
martial_so "HPC Ops Unite" & "Ceph BoF" ?11:52
oneswigIsn't HPC Ops Unite the tagline for our SIG?11:52
martial_oneswig: yes but we do not have a WG meeting anymore, just BoF and Lighting Talk11:53
b1airojohnthetubaguy, one observation from Ops land is that it seems like some of those sessions can be hamstrung because there are so few operators with experience of current releases - so they haven't even hit the beginning of the features you want feedback on11:53
martial_so using the forum to give people a place to meet the community is still a good opportunity I think11:53
johnthetubaguyb1airo: very true11:53
martial_ie shifting from a "planned work" toward a "come and join us"11:54
oneswigwell volunteered martial_ :-)11:54
martial_oneswig: I will take the "HPC Ops Unite" if somebody else take the "Ceph BoF" ?11:54
b1airomight be a point worth throwing into the current "Simplification" thread on os-dev, and certainly makes an argument for closing the gap toward less dev reliance on devstack11:55
oneswigI am already speaking every day of the summit and will blow a gasket if I take on anything more11:55
*** thorst has joined #openstack-meeting11:55
b1airomartial_, yep just checking the agenda to ensure there is not already such a Ceph session (i know there is a CephFS panel, because we are on it...)11:55
*** dprince has joined #openstack-meeting11:56
martial_oneswig: added it to b1airo
martial_b1airo: thanks as well11:56
oneswigOK, thanks martial_ b1airo - anything more to add on proposals?11:56
b1airobloody google, searching for "openstack sydney ceph bof", all i get is spinics links to ML posts of me asking about this a couple of months ago11:57
johnthetubaguya feedback from a dev side of things, it was really hard with lots of WG meeting in Boston11:57
oneswigIn a silent room, echoes...11:57
johnthetubaguyI had no idea which I should attend11:57
martial_johnthetubaguy: what do you mean exactly?11:57
johnthetubaguythe ones I did often spoke about the things that were mentioned in lots of the other rooms, I can't remember which topic that was11:57
martial_oh wait that is not a topic reques :)11:58
johnthetubaguyso lets be specific on quotas11:58
b1airomaybe we could suggest a "top pain points for scientific openstack" session ?11:58
johnthetubaguylots of folks spoke about quota problems in different rooms11:58
martial_b1airo +111:58
b1airojohnthetubaguy, yep good idea11:58
johnthetubaguythe problem as dev is I didn't know what room to go to talk about quotas, beyond the quota session11:58
johnthetubaguyso we fragment the discussions11:59
johnthetubaguyI think it would be better if the sessions broke out of all our silos11:59
b1airoget out ahead of the game on that one and make sure there is something on the agenda to point people at where that will (at least) all get collected on a single etherpad11:59
oneswigsounds good b1airo11:59
johnthetubaguynow that is crazy hard... its just the sorts of sessions that seemed to most successful in Boston11:59
b1airothe successful ones also really need to have at least draft blueprints that attendees can study up on prior12:00
oneswigOK we are out of time12:00
johnthetubaguyto be clear the etherpads doesn't really too much here, you still get three fragmented discussions instead of getting everyone interested in the same room12:00
johnthetubaguyoops, we are over12:00
oneswigI had one piece of AOB to mention12:01
b1airono one is waiting for the room oneswig so may as well go ahead :-)12:01
zioprotoplease keep in mind if you want to moderate a session to add yourself up into the web tool !12:01
oneswigpriteau and his wife had a healthy baby girl last week, all going well12:01
b1airogreat news12:02
zioprotocongrats !12:02
johnthetubaguyI like ending on good news, congrats to priteau12:02
oneswigI shall pass that on!12:02
b1airogood news unless you like sleeping ;-)12:02
oneswigCould continue the forum disucussion in #scientific-wg12:02
*** radeks has quit IRC12:03
martial_oneswig +112:03
b1airoyep i will hang around a while - got cable lengths to figure out...12:03
oneswigooh, shopping...12:03
oneswigok, lets clear the channel here12:03
*** openstack changes topic to "OpenStack Meetings ||"12:03
openstackMeeting ended Wed Sep 27 12:03:44 2017 UTC.  Information about MeetBot at . (v 0.1.4)12:03
openstackMinutes (text):
*** tssurya has joined #openstack-meeting12:04
*** litao__ has quit IRC12:04
*** daveholland has quit IRC12:06
*** chyka has joined #openstack-meeting12:07
*** noslzzp has quit IRC12:07
*** noslzzp has joined #openstack-meeting12:09
*** afazekas|seek4fo is now known as afazekas12:09
*** bobh has quit IRC12:10
*** markstur has joined #openstack-meeting12:11
*** chyka has quit IRC12:11
*** oneswig has quit IRC12:13
*** raildo has joined #openstack-meeting12:13
*** markstur has quit IRC12:16
*** alexchadin has joined #openstack-meeting12:16
*** edmondsw has joined #openstack-meeting12:17
*** bobmel_ has joined #openstack-meeting12:18
*** bobmel has quit IRC12:21
*** spn has quit IRC12:24
*** cdub has joined #openstack-meeting12:25
*** gouthamr has joined #openstack-meeting12:30
*** yangyapeng has joined #openstack-meeting12:34
*** gouthamr_ has joined #openstack-meeting12:37
*** pchavva has joined #openstack-meeting12:37
*** yangyapeng has quit IRC12:38
*** cgoncalves has quit IRC12:38
*** gouthamr has quit IRC12:38
*** gcb has quit IRC12:45
*** alexchadin has quit IRC12:55
*** pabelanger_ is now known as pabelanger12:56
*** alexchadin has joined #openstack-meeting12:56
*** esberglu has joined #openstack-meeting12:58
*** s3wong has joined #openstack-meeting12:58
*** oidgar has quit IRC12:58
*** eharney has joined #openstack-meeting13:01
*** fzdarsky has quit IRC13:02
*** tpsilva has joined #openstack-meeting13:03
*** mriedem has joined #openstack-meeting13:09
*** krtaylor has joined #openstack-meeting13:13
*** ad_rien_ has quit IRC13:14
*** oidgar has joined #openstack-meeting13:15
*** chyka has joined #openstack-meeting13:18
*** chyka has quit IRC13:22
*** baoli has joined #openstack-meeting13:26
*** noslzzp has quit IRC13:26
*** lbragstad has joined #openstack-meeting13:27
*** joadavis1 has joined #openstack-meeting13:30
*** ad_rien_ has joined #openstack-meeting13:32
*** sridharg has quit IRC13:33
*** janki has quit IRC13:34
*** bobmel has joined #openstack-meeting13:36
*** Alex_Staf has quit IRC13:36
*** anilvenkata is now known as anilvenkata|AFK13:37
*** bobmel_ has quit IRC13:39
*** cleong has joined #openstack-meeting13:41
*** VW has joined #openstack-meeting13:42
*** VW has quit IRC13:42
*** VW has joined #openstack-meeting13:43
*** ayoung has quit IRC13:44
*** jprovazn has joined #openstack-meeting13:46
*** lifeless has quit IRC13:46
*** noslzzp has joined #openstack-meeting13:46
*** awaugama has joined #openstack-meeting13:48
*** alexchadin has quit IRC13:51
*** jamesmcarthur has joined #openstack-meeting13:54
*** lifeless has joined #openstack-meeting13:54
*** nseyvet has joined #openstack-meeting13:54
*** Tom_ has joined #openstack-meeting13:54
*** donghao has joined #openstack-meeting13:56
*** witek has joined #openstack-meeting13:58
*** Tom_ has quit IRC13:58
*** hemna_ has joined #openstack-meeting13:58
*** Tom_ has joined #openstack-meeting13:58
*** jgr has joined #openstack-meeting13:58
*** rtjure has quit IRC13:58
*** baoli has quit IRC13:58
*** baoli has joined #openstack-meeting13:59
*** akiraYo has joined #openstack-meeting14:00
witek#startmeeting monasca14:00
openstackMeeting started Wed Sep 27 14:00:10 2017 UTC and is due to finish in 60 minutes.  The chair is witek. 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
witekhello everyone14:00
witekagenda is as usual here14:01
witek#topic Queens Priorities14:01
*** openstack changes topic to "Queens Priorities (Meeting topic: monasca)"14:01
witekthanks for submitting your votes to the google sheet14:02
*** rhochmuth has joined #openstack-meeting14:02
witekhello rhochmuth14:02
rhochmuthran a little late this morning14:03
witekwe just started14:03
*** rtjure has joined #openstack-meeting14:03
witekI have tried to sort the priorities14:04
*** jgu_ has joined #openstack-meeting14:04
witekthe first version is here14:04
patchbotpatch 507534 - monasca-specs - Add Queens priorities14:04
joadavis12 quick questions about Queens priorities (at least the top ones). Should each priority also have a spec?  Should be spec be written in Launchpad, Storyboard, or the new specs repo?14:04
witeknot every prio is suitable for the spec14:05
witekalso, some efforts have already been started and documented in other way14:06
witekbut as a minimum we should have a short description on priorities page14:06
akiraYohi, all14:06
joadavis1Fair enough.  Things like python3 I assume already have some sort of doc.14:06
witekand a story in StoryBoard would be nice14:06
witekI guess we won't use Launchpad any more14:07
*** koji has joined #openstack-meeting14:07
witeknew changes affecting the API or otherwise strongly impacting the project should have a spec14:08
*** chyka has joined #openstack-meeting14:08
witekhi akiraYo14:08
joadavis1My follow-up question was going to be if we keep using Storyboard or focus more on the specs repo (and maybe migrate some of the stories we think are still relevant from Launchpad or Storyboard over to the repo)?14:08
witekjoadavis1: yes, python 3 is documented as community goal14:08
witekwe should use StoryBoard for all changes affecting the code14:10
witekfeatures and bugs14:10
*** yamamoto has quit IRC14:10
rhochmuthi know the api was looking a little involved to add python3 support14:10
witekmore complicated stuff should additionally has spec14:10
rhochmuthhas anyone taken a look at that recently14:10
*** felipemonteiro has joined #openstack-meeting14:10
rhochmuthi started on it, and thought, this will be quick and easy, and then realized, it was more involved14:11
rhochmuthi believe there was another review that was inflight for the conversion too14:11
witekrhochmuth: kornica has come up to the same conclusion14:11
*** oidgar has quit IRC14:12
*** felipemonteiro_ has joined #openstack-meeting14:12
*** aagate has joined #openstack-meeting14:12
joadavis1Thanks. I'm starting to think about work to submit the Monasca Publisher to ceilometer, so I'll write something14:12
witekjoadavis1: nice, could I assign you as the owner?14:13
joadavis1you can put myself and Ashwin Agate as owners (I'm happy to share)14:13
witekit would be good to have someone for Python 3 stuff14:14
witekwill check myself with the team14:14
*** dtrainor has joined #openstack-meeting14:15
*** yamamoto has joined #openstack-meeting14:15
witekdo we have any other items to add to prios?14:15
*** felipemonteiro has quit IRC14:16
*** galstrom_zzz is now known as galstrom14:16
jgrWhat about the documented policy thing we spoke about at the midcycle?14:16
jgr(I don't see it anywhere in the list of priorities)14:16
witekService Domain for Self Service Agent Users14:17
witekI guess it's what you mean, right?14:17
witekshould I rename?14:18
jgrNo, that's a different one14:18
jgrIt's somewhat related since I'll need to modify policy enforcement as well14:18
*** alex_xu has quit IRC14:18
witekoh, you mean the community goal14:19
jgrBut we talked about OpenStack projects being mandated to have in-code policy rather than policy.json14:19
witekI wasn't sure if we're affected14:19
jgrWell, we're not even using oslo.policy right now...14:20
*** yamamoto has quit IRC14:20
witekOK, will add it to 'essentials'14:21
scjgr: and do you see a good use case to add oslo.policy?14:21
*** alex_xu has joined #openstack-meeting14:21
jgrsc: well, we're kind of supposed to under the Openstack umbrella.14:21
*** s3wong has quit IRC14:22
scso forced to use14:22
jgrI for one would be happy to put it off until later myself, because it will either block the agent user thing or force a refactoring (not much refactoring, though) of the agent user code once the oslo.policy integration is merged.14:23
jgrYes, forced to use.14:24
jgrI think there's a bit of an agenda behind the in-code policy thing.14:24
witekjgr: can you elaborate?14:24
jgrKeystone were making noises about surveying policy rules last year around December and they need this in-code policy thing in all projects to be able to do a proper survey.14:25
*** jamesmcarthur has quit IRC14:25
*** hemna_ has quit IRC14:25
*** oidgar has joined #openstack-meeting14:26
witekrhochmuth: can I put you and me as Grafana thing owners?14:27
*** hongbin has joined #openstack-meeting14:27
*** tongl has joined #openstack-meeting14:27
*** julim has quit IRC14:28
witekit would be nice when the owners could add a short description of the prio to the document14:29
witekanything else to this topic?14:30
*** tongl has quit IRC14:30
witek#topic Service Domain for Self Service Agent Users14:30
*** openstack changes topic to "Service Domain for Self Service Agent Users (Meeting topic: monasca)"14:30
witekjgr has submitted the spec14:31
patchbotpatch 507110 - monasca-specs - Add Service Domain Spec14:31
witekone key question is if we should use Keystone for storing credentials, or should API handle it14:32
jgrI for one prefer the Keystone approach.14:32
jgrAPI keys are pretty messy and essentially amount to creating our own authentication/authorization infrastructure.14:33
witekyour comment in review is misleading then :)14:34
*** hemna_ has joined #openstack-meeting14:34
jgrIn the Alternatives section, you mean?14:34
nseyvetIn the monasca agent, one can specify the Keystone url to discover the monasca API endpoint. Would this change affect that as well?14:34
jgrNo, not at all.14:34
*** rbartal has quit IRC14:35
jgrThis change is transparent as far as monasca-agent is concerned.14:35
nseyvetok. need to read this more.14:35
jgrThe only change on the monasca-agent side is that one needs to specify a user domain in the configuration.14:36
witekthe old mechanism with authorized roles in API would still be available?14:36
jgrI plan on making this configurable.14:37
*** ramineni_ has joined #openstack-meeting14:37
witekI also prefer storing credentials in Keystone14:38
jgrOk, good. Then I'll change that bit in the Alternatives section to make it appear less viable :-)14:39
witekthanks for the document14:40
witeknice job14:40
jgrThanks :-)14:40
witek#topic open stage14:40
*** openstack changes topic to "open stage (Meeting topic: monasca)"14:40
*** makowals has quit IRC14:40
witekdo we have anything else to discuss?14:41
nseyvetone more question: the "domain" is equivalent to a tenant?14:41
jgrKind of.14:41
nseyvetie there is a one-to-one relation?14:41
jgrOne can abuse a domain as a tenant.14:41
nseyvetso with the current spec one tenant could have multiple domains and thus "user-agent"s14:41
jgrThere's only one domain.14:42
jgrA domain is a container for users and tenants.14:42
jgrAdditionally, it can be abused as a tenant (one can create OpenStack resources in a domain, unfortunately).14:42
jgrBut that's not really its purpose.14:43
witekI found this description useful:14:43
nseyvetok. But then is it OK that all users/projects share the same "user-agent" credentials?14:43
*** radeks has joined #openstack-meeting14:43
jgrAs far as the spec is concerned that domain is a secluded corner in Keystone where Monasca can create its own users that are entirely separate from Keystone users in the Default domain.14:43
akiraYocan we share a service domain with other services like heat?14:43
jgrNo, absolutely not!14:43
nseyvetor would some expect a separation b/w projects?14:44
jgrEvery user can create one or more agent user credentials.14:44
*** alex_xu has quit IRC14:44
jgrThere's nothing shared anymore, which is the whole point of the spec.14:44
nseyvetOK, and it is the user responsibility to insert those credentials in the agent?14:44
*** rasca has quit IRC14:44
jgrAlso, sharing a domain with Heat or Magnum is technically possibly but it would be a stupid admin who actually configured their cloud that way...14:44
jgrYes, that's the user's responsibility14:45
jgrWe could at some stage add a little plugin to Heat that generates an agent.yaml and a cloud-config snippet to deploy it to Heat, but first of all we need the capability to create agent users.14:46
jgrs/deploy it/deploy it on an instance/14:46
*** lhx_ has joined #openstack-meeting14:47
witekI guess we can further discuss in review14:49
*** jaypipes has joined #openstack-meeting14:49
witekwould be great to have your opinions14:49
*** alex_xu has joined #openstack-meeting14:49
witekif there's nothing else, I'll be closing the meeting14:50
nseyvetthank you for the links.  Will go through them.14:50
witekthanks nseyvet14:50
*** kgiusti has joined #openstack-meeting14:51
witekbye everyone, see you next week14:51
akiraYosee you.14:51
jgrSee you!14:51
joadavis1thanks again14:51
scbye now14:51
*** openstack changes topic to "OpenStack Meetings ||"14:52
openstackMeeting ended Wed Sep 27 14:52:00 2017 UTC.  Information about MeetBot at . (v 0.1.4)14:52
openstackMinutes (text):
*** akiraYo has quit IRC14:52
*** koji has quit IRC14:52
*** rhochmuth has left #openstack-meeting14:52
*** ad_rien_ has quit IRC14:53
*** parus has joined #openstack-meeting14:53
*** joadavis1 has left #openstack-meeting14:53
*** markstur has joined #openstack-meeting14:54
*** gongysh has joined #openstack-meeting14:55
*** baoli has quit IRC14:56
*** radeks has quit IRC14:56
*** ansmith has joined #openstack-meeting14:57
*** caboucha has joined #openstack-meeting14:58
*** baoli has joined #openstack-meeting14:59
*** dp4n has joined #openstack-meeting14:59
*** dp4n has left #openstack-meeting14:59
*** dpertin has joined #openstack-meeting14:59
*** jamemcc_ has joined #openstack-meeting15:00
*** rbowen has joined #openstack-meeting15:00
parus#startmeeting FEMDC15:00
openstackMeeting started Wed Sep 27 15:00:20 2017 UTC and is due to finish in 60 minutes.  The chair is parus. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: FEMDC)"15:00
openstackThe meeting name has been set to 'femdc'15:00
*** pbressan has joined #openstack-meeting15:00
parusGood morning/Afternoon to all!15:00
*** lhx_ has quit IRC15:01
*** dayou has quit IRC15:01
pbressanGood morning15:01
parusI tried to send the link to the etherpad through mailing list but I think it bounced.15:01
parusso here is the link15:02
parusit seems we may a have quorum. So lets' get started.15:02
*** bbzhao has quit IRC15:03
parusAd_rien_ excused himself for today. So I will try to chair. Please be patient with me.15:03
jamemcc_thank you15:03
*** bbzhao has joined #openstack-meeting15:03
parusFirst topic:15:04
parus#topic Announcements15:04
*** openstack changes topic to "Announcements (Meeting topic: FEMDC)"15:04
*** gyee has joined #openstack-meeting15:05
*** zhipeng has joined #openstack-meeting15:05
parusabout Sydney: our timeslot for the f2f is fixed. you will find the link in the etherpad.15:05
parusAre any additional people confirmed to attend.15:05
parusI know that dpertin and myself are.15:05
dpertinglad to share the session with you parus15:06
kgiustiI can't make Sydney15:06
jamemcc_I don't think I will be going, some outside chance I'd send myself but my organization will not15:06
parusso it will be a smaller meeting I guess, if there are any topics that you feel should be discussed, please let us know.15:07
parusnext topic is cross wg chair.15:08
parus#topic CrossWGChairSessions15:08
*** openstack changes topic to "CrossWGChairSessions (Meeting topic: FEMDC)"15:08
*** yangyapeng has joined #openstack-meeting15:08
*** nseyvet has quit IRC15:08
parusThis topic was added by ad_rien_. I am affraid I do not now much about it. Anyone can comment?15:09
jamemcc_I missed the announcement and the actual attempted session for Cross WG chairs which was Sept 1415:09
*** yamamoto has joined #openstack-meeting15:10
jamemcc_I think ad_rien was the only one to join at least at the start15:10
*** makowals has joined #openstack-meeting15:10
parusThen we will have him report on the next meeting.15:10
parusI see he has put some links to an event announcement that is happening today.15:11
jamemcc_In this last Monday UC meeting tHere was an agreement made by User Committee and a few others including me to try again15:11
jamemcc_I'll include the relevant links and next proposed date in Etherpad as I find them15:11
parusThank you jamemcc_15:11
parus#topic SIG15:12
*** openstack changes topic to "SIG (Meeting topic: FEMDC)"15:12
parusfollowing the change of status between team and workgroup.15:13
*** makowals has quit IRC15:13
*** martial_ has quit IRC15:13
parusI understand that a new change is being discussed that might give us more flebility and autonomy.15:13
parusThe concept of a Special Interest Group is being discussed and this team's name has been mentionned as a candidate.15:14
*** rasca has joined #openstack-meeting15:14
parusMore on this will follow as it unfolds. There was some exchange in the last couple of weeks, and it seems there may be only benefits to the change.15:14
jamemcc_I agree that we shoudl volunteer and take the minor actions required to be listed as a SIG, it should help us to be a larger group and attract engineers15:15
jamemcc_I think we/you are already a good model for how one would operate15:15
parusAny other opinions?15:16
*** zhipeng has quit IRC15:16
*** zhipeng has joined #openstack-meeting15:16
parusLet's wait for the larger group to be here before we make a decision. Maybe we can have that as a topic for next meeting.15:17
*** sc has left #openstack-meeting15:18
*** tobiajo has quit IRC15:18
*** ayoung has joined #openstack-meeting15:19
parusthanks for adding the link to the follow-up on Etherpad... Definitely, if we make the change there will be opportunities to better define what we do.15:20
parusnext topic15:20
parusThe forum in sydney.15:20
parusWe have an opportunity to propose topics to be discussed at the forum in sydney.15:21
parusThese will be cross workgroup discussion.15:21
parusWe would have to put forward those proposals in the next day or so.15:22
parusSee Link on etherpad.15:22
parusAny one has suggestions?15:22
*** gongysh has quit IRC15:23
*** julim has joined #openstack-meeting15:23
parusThanks jamemcc_15:25
jamemcc_Not sure if anyone else (I know I'm not) is very versed on the next steps from the Open-Dev15:25
parusThat is a good point!15:26
jamemcc_But seems to me some of that should become Forum topics15:26
*** gouthamr_ has quit IRC15:26
parusI may be guilty there. One thing that came out of opendev was the need for a follow-up session on edge.15:26
parusbut I have not seen any announcement on that. Beth was certainly one of the leads.15:27
parusI will take an action to reach out to her.15:27
*** lpetrut has joined #openstack-meeting15:27
parus#action parus to reach out to Beth/Kandan about follow-ups from opendev.15:27
parusmy recollection is that we were suppose to have separate sessions to prepare for Sydney.15:28
*** ricolin has quit IRC15:28
*** toscalix has quit IRC15:28
parusOne more announcement.15:29
*** lhx_ has joined #openstack-meeting15:29
*** rasca has quit IRC15:29
parusin the margins of opendev we had meetings with openedge15:29
*** Sukhdev has joined #openstack-meeting15:30
*** rasca has joined #openstack-meeting15:30
parusOne key member of that group is Sathia from CMU.15:30
parusHe is organizing a meeting to give us more details about their extension openstack.15:30
parusthis is a project called openstack++15:31
parusMeeting is scheduled for october 3rd.15:31
*** treiz has quit IRC15:31
parusIf anyone has an interest, I do not think there would be a problem adding a few more people to the invite.15:31
parusany comment?15:32
parusLet's move on.15:33
parus#topic ONAP15:33
*** openstack changes topic to "ONAP (Meeting topic: FEMDC)"15:33
parusad_rien_ added this topic to the agenda.15:33
parusthis was a major outcome from opendev from my perspective.15:33
*** dprince has quit IRC15:34
parusThe question is about what functionality falls under openstack15:34
parusvs what functionality is left to a layer above.15:34
parusThe layer above can be the application itself .... or it could be ONAP.15:34
parusDid anyone have a different perspective on what the topic is?15:35
*** dprince has joined #openstack-meeting15:35
jamemcc_From my quick read of the OpenDev Key findings. I agree15:36
parusAnything we can do to dig further?15:37
*** zhipeng has quit IRC15:37
*** zhipeng has joined #openstack-meeting15:37
*** tongl has joined #openstack-meeting15:37
jamemcc_FYI - those are #url
parusjamecc_ : do you have any insight on what ONAP is doing for Edge?15:38
jamemcc_just level setting - for the Telco and NFV use case - ONAP is the Design and Orchestrate and Manage oversight layer15:39
*** electrofelix has joined #openstack-meeting15:39
jamemcc_But I think it being Junior in that task had not exactly agreed to take on the Fog Edge for all applciations/use cases15:39
*** psachin has quit IRC15:40
parusSo it may be further out in their roadmap?15:40
jamemcc_I think to some extent - that purpose of the OpenDev from ONAP perspetive would be to see if there are other Open ways to handle15:40
jamemcc_ANd if not to try to gather the interested resources to put more work into ONAP15:41
parusI suspect this means for us that we should keep monitoring.15:41
jamemcc_Just trying to add tot he conversation - I dont' have any more detailed knowledge of strategy from the ONAP effort15:42
parusthanks. Let's move on.15:42
parus#topic AMQP15:43
*** openstack changes topic to "AMQP (Meeting topic: FEMDC)"15:43
*** rcernin has quit IRC15:43
kgiustiMatthieu has done excellent work on the testplan - see epad for link (linke 1284)15:43
kgiustiAdmittedly I've been the slow horse in that effort, but I think the tests and metrics are fairly complete15:44
kgiustiNext is to update the test tool (ombt2) to capture the defined metrics - I hope to have that done by end of week15:44
kgiustiAnd the kolla/ansilbe patch still hasn't landed, but the reviews have given us some feedback since last meeting15:45
*** yamahata has quit IRC15:45
kgiustiand that's about it from AMQP land15:45
parusThanks for the good work!15:45
kgiustiour pleasure!15:46
parusWhat is the next step on Kolla?15:46
kgiustiTo get the patch fixed up and landed.15:46
kgiustiansmith: how is the feedback so far?15:47
ansmithfeedback very strong, just need a few +2's15:47
ansmithwill keep engaging the kolla team15:47
parusThank you guys. Let's move .15:48
kgiustiansmith: would it help if others in femdc added to the comments (like +1's)?15:48
ansmithit nevers hurts, Matthieu has done so15:48
parusSend us the link and I can certainly take an action on my side.15:48
ansmithit is in etherpad as well =>
patchbotpatch 468966 - kolla-ansible - Add support for hybrid messaging backends15:49
parus#action parus to review kolla patch and support.15:49
parus#topic CockroadDB15:50
*** openstack changes topic to "CockroadDB (Meeting topic: FEMDC)"15:50
parussorry for the typo15:50
parus#topic CockroachDB15:50
*** openstack changes topic to "CockroachDB (Meeting topic: FEMDC)"15:50
parusanyone can comment on updates?15:51
parusif not let's move on.15:51
parusFBK excused themselves today, so we can defer the discussion on use cases to next time.15:52
parusLet's open up for discussions.15:52
parus#topic open discussion15:52
*** openstack changes topic to "open discussion (Meeting topic: FEMDC)"15:52
parusad_rien was suggesting a follow-up meeting at the end of this week.15:53
parusAny takers?15:53
jamemcc_Yes - I'm glad to attend15:53
*** oidgar has quit IRC15:54
parusPlease add your name to the etherpad15:54
parusany other comments?15:55
*** erlon has joined #openstack-meeting15:55
parusAm I the only one who took some actions?15:55
*** xyang1 has joined #openstack-meeting15:56
kgiusti#action kgiusti to release update to ombt2115:56
jamemcc_Sorry about that - thanks again for facilitating15:56
*** iyamahat has joined #openstack-meeting15:56
*** rossella_s has joined #openstack-meeting15:57
parusthank you all for being so patient with me.15:57
parusand we get to finish three minutes early :-)15:57
kgiustiparus: thanks for the good leadership! :)15:57
*** openstack changes topic to "OpenStack Meetings ||"15:57
openstackMeeting ended Wed Sep 27 15:57:49 2017 UTC.  Information about MeetBot at . (v 0.1.4)15:57
openstackMinutes (text):
*** iyamahat has quit IRC15:58
*** pbressan has quit IRC15:58
*** parus has left #openstack-meeting15:58
*** markstur_ has joined #openstack-meeting15:59
jungleboyj#startmeeting Cinder16:00
openstackMeeting started Wed Sep 27 16:00:02 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
*** kgiusti has left #openstack-meeting16:00
*** openstack changes topic to " (Meeting topic: Cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
jungleboyjCourtesy ping:  jungleboyj DuncanT diablo_rojo, diablo_rojo_phon, rajinir tbarron xyang xyang1 e0ne gouthamr thingee erlon patrickeast tommylikehu eharney geguileo16:00
geguileohi! o/16:00
*** bswartz has joined #openstack-meeting16:01
jungleboyjHey everyone.  Will give people another minute to join.16:01
jungleboyjHave a short agenda so I am sure things will spiral out of control and take the whole hour.  ;-)16:01
*** zhipeng has quit IRC16:01
*** yamahata has joined #openstack-meeting16:02
*** markstur has quit IRC16:02
*** abishop has joined #openstack-meeting16:02
jungleboyjGoing to ping jgriffith  just for fun as well.16:02
jungleboyjEven though he hasn't added his name to the list.  Glad to see you joined again smcginnis16:02
*** timothyb89 has joined #openstack-meeting16:03
jungleboyjOk, I guess we will get started.16:03
*** Rockyg has joined #openstack-meeting16:03
jungleboyj#topic Announcements16:03
*** openstack changes topic to "Announcements (Meeting topic: Cinder)"16:03
smcginnisjungleboyj: What? My name is on there. You even pinged me. :)16:03
jungleboyjsmcginnis:  I know, but it wasn't there yesterday.  Thought maybe you had given up.  ;-)16:04
jungleboyjThe usual reminder to please keep an eye on the Review Tracking priorities.16:04
*** Apoorva has joined #openstack-meeting16:04
jungleboyjI am trying to get updates in there as I see them.  If you have reviews coming in that you know we talked about at the PTG, please feel free to add them to the etherpad.16:05
jungleboyjAlso, I have the notes from the PTG summarized in our wiki.16:05
jungleboyjThe items we are greed upon and the associated actions are all summarized there.16:06
tommylikehujungleboyj:  great, thanks!16:06
jungleboyjDo not have the video links organized in there yet.  Hoping to get some help on that.16:06
jungleboyjtommylikehu:  You are welcome!16:06
jungleboyjAlso, I need to review specs this week as we are already coming up on Pike 1 soon.  Need to get things approved.  Appreciate any help with that.16:07
jungleboyjThat was all I had for announcements.16:07
jungleboyj#topic Sydney Forum Topics16:07
*** openstack changes topic to "Sydney Forum Topics (Meeting topic: Cinder)"16:07
jungleboyjSo, my etherpad is lonely.16:08
jungleboyjHas no one taken the time to update it or do we not have any topics?16:08
smcginnisI couldn't think of anything we needed. Other than maybe more cross project with nova.16:09
jungleboyjsmcginnis:  Ok, I can coordinate with Matt and submit that as a proposal in the case that he hasn't scheduled anything.16:10
jungleboyjHave any projects scheduled just like an 'office hours' type of time to get feedback from operators/users?16:10
SwansonCould add "Pedantic coding practices: Or PEP8 is your code thug friend."16:11
jungleboyj:-)  That sounds like PTG topics.16:11
jungleboyjSo, I will see if it would be appropriate to schedule a time for people to stop and ask questions about Cinder.  That seems like something other teams have done in a virtual format.16:13
smcginnisOh yeah, are they doing the onboarding rooms again?16:13
jungleboyj#action Jay to coordinate with mriedem to set up a cross-project session to continue API/multi-attach work.16:14
jungleboyjsmcginnis:  Yes they are.  They are scheduling them.  diablo_rojo_phon  is in charge of that.16:14
jungleboyjsmcginnis:  I am planning on doing our on-boarding presentation again.  Would like to get it recorded this time.16:14
jungleboyjHave some changes/improvements I hope to make.16:15
* jgriffith yawns and stretches16:15
*** hemna_ has quit IRC16:15
jungleboyjSo, the deadline for the submission of forum topics is Friday.16:15
smcginnisWakey wakey.16:15
jgriffithsmcginnis: :)16:16
*** iyamahat has joined #openstack-meeting16:16
jungleboyj#action Team to add ideas to etherpad by Friday is there is anything they want to propose.16:16
jungleboyj#topic Driver Removal Patches16:16
*** openstack changes topic to "Driver Removal Patches (Meeting topic: Cinder)"16:16
jungleboyjSo, smcginnis  Has proposed to remove the drivers that do not meet our CI requirements.16:17
smcginnisIf folks are behind our driver policy - please review! :)16:17
jungleboyjI have +2'd .16:17
jungleboyjIf anyone else is willing to go review and maybe push the button, it would be appreciated.16:17
smcginnisIf there's any reason not to do it, please speak up.16:18
jungleboyjsmcginnis: ++16:18
jungleboyjWe have been doing this for a couple of releases now and think it is good to continue to follow our policy.16:19
jungleboyj#action Team to review the proposed patches and vote.16:19
e0nejungleboyj: +116:19
e0nejungleboyj: I put some +2 on them before meeting. looks like we're OK to approve them16:19
*** b1airo has quit IRC16:20
jungleboyjsmcginnis:  Thank you for continuing to watch the CI's and push up patches.16:20
jungleboyje0ne:  I saw that.  Thank you.16:20
e0nejungleboyj: I just waited for meeting if we want to hold on on them or something like it16:20
jungleboyjOk, well, there don't seem to be objections, so we will move on unless you have anything else there smcginnis .16:20
smcginnisNope, that's good.16:20
jungleboyje0ne:  Makes sense.16:21
jungleboyj#topic Update backup's size when backup is created16:21
*** openstack changes topic to "Update backup's size when backup is created (Meeting topic: Cinder)"16:21
patchbotpatch 506141 - cinder-specs - Update backup's size when backup is created16:21
jungleboyjtommylikehu:  Over to you16:21
e0neI like this idea but I think jgriffith could have some input on it16:21
tommylikehuI think this one is kind of bug, because we use volume's size for backup now.16:21
tommylikehue0ne:  oh?16:22
e0netommylikehu: we discussed it some time (years?) ago, but I don't remember why we didn't change it16:22
tommylikehujgriffith:  any update?16:22
smcginnisI don't remember that. Must have been a long time ago.16:22
e0neI could be wrong, but maybe jgriffith had some objections. I don't remember, TBH16:23
jgriffithI'm not sure what I think honestly16:23
*** iyamahat has quit IRC16:23
jgriffithe0ne: might have been a *different* do some magic thing :)16:23
e0neI just remember that we'd got such bug from our customer in the past16:23
* jungleboyj needs to read the spec16:23
e0nejgriffith: :)16:23
tommylikehujgriffith:  so I am proposing we can have backup driver to report the real size of the backup when backup object is created at backend16:23
jgriffithI had some concerns about how this all works in reality16:24
*** tesseract has quit IRC16:24
*** rossella_s has quit IRC16:24
jungleboyjtommylikehu:  In what cases does the backup not have the size of what is backed up?16:24
jgriffithit leads us to your next request which will be to report only the actual size of a volume instead of the allocated size :)16:24
jungleboyjAre you talking about like with thin provisioning or something?16:25
* jgriffith is being humorous with that16:25
tommylikehujungleboyj:  mostly the incremental  backup16:25
jungleboyjtommylikehu:  Oh.16:25
jgriffithtommylikehu: I think what you propose here makes sense16:25
*** marios has quit IRC16:25
tommylikehujgriffith:  thanks16:25
jgriffithtommylikehu: I am a little unsure when you throw in compresses vs uncompressed16:26
*** rbowen has quit IRC16:26
jgriffithtommylikehu: honestly I think you would need to use either the *actual* size of the data or provide both16:26
jgriffithuse actual for things like restoring, and if a provider wants, they an use *compressed/on-disk* for billing16:27
tommylikehujgriffith:  both?16:27
jungleboyjjgriffith:  oooh, that makes sense.16:27
jgriffithtommylikehu: yes, I can't tell based on your spec what you're actually proposing to use for the *size*16:28
tommylikehujgriffith:  that's right16:28
jgriffithbut they're very different things and both are important16:28
*** Tom_ has quit IRC16:28
*** lpetrut has quit IRC16:28
*** Tom_ has joined #openstack-meeting16:29
jungleboyjtommylikehu:  Any concerns with going that path?16:29
tommylikehujungleboyj:  agreed with jgriffith , I can update my spec16:29
*** yamahata has quit IRC16:30
jungleboyjtommylikehu:  Cool.16:30
e0nejgriffith, jungleboyj: I remembered, we discussed a bit different issue in the past: it was about renaming backup.size to backup.volume_size and there were concerns about original volume resizing16:30
jungleboyj#action tommylikehu to update the spec to cover including both the total data size and the amount of space used on disk by the backup.16:31
jungleboyje0ne:  What is currently in backup.size ?16:32
tommylikehuequal to volume's size at that time when backed up16:33
e0nejungleboyj: original volume size16:33
jungleboyje0ne:  Ok, so, as far as resizing goes, if the user resizes their volume and then doesn't back it up to update that info ... well, oops.16:33
*** Tom_ has quit IRC16:34
jgriffithjungleboyj: it's fine16:34
e0nejungleboyj: yes. but it's a bit different and could be fixed out of scope of the proposed spec16:34
jungleboyje0ne:  Ok, won't get off track.16:34
e0nejungleboyj: +116:35
jgriffithe0ne: I'm not sure I recall... but I say it "should be fine" because you can only extend a volumes size16:35
jgriffithso I'm not sure that would be problematic16:35
tommylikehujgriffith:  +116:35
e0nejungleboyj: I agree. It's a bit confusing for users who don't know what is it, but not a big deal16:35
e0nejgriffith: ^16:36
jungleboyje0ne:  Ok.16:36
jungleboyjSo, lets work this in the spec and make sure that we don't make things more confusing in the process.16:36
jungleboyj#action Team to review the spec after tommylikehu  updates it.16:37
*** b1airo has joined #openstack-meeting16:37
jungleboyjAnything else on that topic ?16:38
jungleboyjtommylikehu:  Ok, thank you.16:38
jungleboyj#topic Open Discussion16:38
*** openstack changes topic to "Open Discussion (Meeting topic: Cinder)"16:38
jungleboyjAnything else we need to discuss today?16:38
jungleboyjAre people actually awake out there?16:38
smcginnisI have on thing...16:38
*** spn has joined #openstack-meeting16:38
jungleboyjsmcginnis:  Go for it.16:39
smcginnisNot sure if folks noticed, but ostestr swapped out using testr internally for stestr.16:39
smcginnisNot confusing at all, right?16:39
lhx_jungleboyj, a small issue
* jungleboyj head explodes16:39
smcginnisSo minor thing, but we get warning output in test runs because of that.16:39
*** sshank has joined #openstack-meeting16:39
smcginnisThese take care of that:
*** david-lyle has quit IRC16:40
jgriffithsmcginnis: there seems to be something else with that change that I haven't been able to nail down...16:40
e0nelhx_: do we have patch for it16:40
smcginnisjgriffith: With the stestr change?16:40
*** SumitNaiksatam has quit IRC16:40
*** rossella_s has joined #openstack-meeting16:40
jgriffithsmcginnis: yeah, but don't want to derail....  and need to try your patch first :)16:41
lhx_e0ne, I think just add the __init__ file is ok, not sure if it's worthy16:41
jgriffithsmcginnis: To Be Continued....16:41
smcginnislhx_: No bug needed IMO, but that could be addressed with the move to separate repos for tempest plugins.16:42
smcginnisOr after that move is complete.16:42
jungleboyjsmcginnis:  Thanks for chasing that.16:42
smcginnisThat's all I've got for today.16:42
lhx_smcginnis, yep, make sense16:43
jungleboyjsmcginnis:  For lhx_  problem you are saying he doesn't need to submit a patch or that the patch doesn't need to have a bug created?16:43
*** gouthamr has joined #openstack-meeting16:43
*** dpertin has quit IRC16:44
lhx_jungleboyj, I think it's the latter16:44
lhx_smcginnis, right?16:44
smcginnisRight, no bug.16:44
jungleboyjlhx_:  Ok, just making sure that was clear.  :-)  I agree, just fix it.16:44
*** hemna_ has joined #openstack-meeting16:45
lhx_jungleboyj, sure :)16:45
jungleboyjlhx_:  Thanks!16:45
jungleboyjOk ... anything else?16:45
lhx_you're welcome16:45
*** gouthamr_ has joined #openstack-meeting16:46
_pewp_jungleboyj (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. )16:46
jungleboyjSince no one has anything else to share I guess we can wrap up and everyone get 14 minutes back.  :-)16:46
jungleboyjThank you for working on Cinder!16:47
jungleboyjTalk to you all next week.16:47
_pewp_jungleboyj ( ^_^)/16:47
*** bobh has joined #openstack-meeting16:47
*** openstack changes topic to "OpenStack Meetings ||"16:47
openstackMeeting ended Wed Sep 27 16:47:28 2017 UTC.  Information about MeetBot at . (v 0.1.4)16:47
openstackMinutes (text):
*** jgu_ has left #openstack-meeting16:48
e0nesee you next week16:48
*** abishop has left #openstack-meeting16:48
*** donghao has quit IRC16:48
*** gouthamr has quit IRC16:49
*** d0ugal has quit IRC16:50
*** e0ne has quit IRC16:52
*** lbrune has joined #openstack-meeting16:52
*** xyang1 has quit IRC16:52
*** JudeC has joined #openstack-meeting16:53
*** lbrune1 has joined #openstack-meeting16:53
*** yamamoto has quit IRC16:55
*** lbrune has quit IRC16:56
*** dayou has joined #openstack-meeting16:57
*** pksingh has joined #openstack-meeting16:58
*** gans has joined #openstack-meeting16:59
*** sanfern has joined #openstack-meeting16:59
*** rm_mobile has joined #openstack-meeting16:59
*** yamamoto has joined #openstack-meeting16:59
*** longstaff has joined #openstack-meeting17:00
*** lbrune has joined #openstack-meeting17:01
johnsom#startmeeting Octavia17:01
*** cgoncalves has joined #openstack-meeting17:01
openstackMeeting started Wed Sep 27 17:01:43 2017 UTC and is due to finish in 60 minutes.  The chair is johnsom. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: Octavia)"17:01
openstackThe meeting name has been set to 'octavia'17:01
johnsomHi folks17:01
rm_mobileThere we go17:01
sanfernHi  johnsom17:02
johnsomSorry, talking with nova guys about the 404 I just reproduced local.  NIC is not showing up in the instance17:02
johnsom#topic Announcements17:02
*** openstack changes topic to "Announcements (Meeting topic: Octavia)"17:02
johnsomJust a heads up, Zuul v3 is rolling out.17:03
*** oidgar has joined #openstack-meeting17:03
*** Apoorva_ has joined #openstack-meeting17:03
johnsomThis will likely mean some turbulence in our gates for a bit.17:03
*** lbrune1 has quit IRC17:03
rm_mobileI thought it did already17:04
johnsomThat is the link for more details on zuul v3.17:04
johnsomIt's been dragging out as they keep finding bugs.  As of last night it was still not fully deployed17:04
rm_mobileSeemed like the pep8 job I looked at the other day was run with v317:04
johnsomQuote: We've pretty much run out of daylight though for the majority of the team and there is a tricky zuul-cloner related issue to deal with, so we're not going to push things further tonight. We're leaving most of today's work in place, having gotten far enough that we feel comfortable not rolling back.17:05
johnsomFrom Monty's email last night17:05
*** spn has quit IRC17:05
johnsomAnyway, just a heads up that this is happening and may impact us.17:05
*** Apoorva has quit IRC17:06
johnsomIn the end it will be a good thing as it will be much easier to update our gates17:06
*** spn has joined #openstack-meeting17:06
*** spn has quit IRC17:06
*** spn has joined #openstack-meeting17:06
johnsomAny other announcements today?17:06
johnsom#topic Meeting time revisit17:06
*** openstack changes topic to "Meeting time revisit (Meeting topic: Octavia)"17:06
*** longstaff has quit IRC17:07
johnsomI have got a lot of feedback that the new meeting time is not working out.17:07
rm_mobileI'm dieing right now17:07
johnsomSome active contributors cannot make this time, plus that ^^^ ha17:07
rm_mobileIt's too early for me to read words17:07
johnsomSo, due to multiple requests I have put up another doodle to re-evaluate the time for the meetings17:08
johnsomI have put two times in, but we can add others.  I also picked the same day, but we have flexibility there too17:08
johnsomRecently the TC approved that we can host our meetings in the lbaas channel, so we are no longer stuck with what slots are available on the main meeting channels17:09
*** longstaff has joined #openstack-meeting17:10
johnsomAny questions/comments about meeting times?  other proposals?17:10
tonglWhen are we starting to use lbaas channel?17:10
*** lbrune has quit IRC17:10
johnsomI will send out an e-mail and we will have at least one more meeting at this time/channel where I will announce it.17:11
tonglsounds good17:11
*** jniesz has joined #openstack-meeting17:11
johnsom#topic Brief progress reports / bugs needing review17:12
*** openstack changes topic to "Brief progress reports / bugs needing review (Meeting topic: Octavia)"17:12
johnsomOk, how are things going?17:12
*** krenczewski has joined #openstack-meeting17:12
johnsomtongl Is this patch still being worked on?
patchbotpatch 323645 - neutron-lbaas - Add status in VMware driver17:12
rm_mobileCouple of patches waiting to go in that are the results of the PTG17:12
johnsomIt has a -1 comment17:12
*** treiz has joined #openstack-meeting17:13
johnsomYeah, we have a bunch of patches with one +2 on them17:13
*** david-lyle has joined #openstack-meeting17:13
*** rbowen has joined #openstack-meeting17:13
tongljohnsom: Let me have a look at it to resolve the comments. It is nsxv driver.17:13
johnsomSome great stuff coming in fixing octavia-dashboard issues17:14
*** pcaruana has quit IRC17:14
johnsomI have been trying to catch up on patch reviews. A number have failed when I go to test them out.17:14
johnsomIf you have open patches check to see if I have commented.17:15
johnsomAny other patches/bugs to discuss today?17:15
patchbotpatch 486499 - octavia - Add flavor, flavor_profile table and their APIs17:16
*** bh526r has joined #openstack-meeting17:16
pksinghrecently submitted my first patch to octavia, although one gate job is failing but seems unrelated to code17:16
pksinghplease submit your reviews17:17
johnsomLooks like that gate failure was the OVH bug with qemu crashing17:17
johnsomYeah, that one is a infra host issue and not your code.17:17
johnsomcirros doesn't even boot there17:17
pksinghok, thanks :)17:18
johnsomCool, glad to see that is ready for review!17:18
tonglIs this the flavor support we discussed during PTG?17:18
pksinghimplmentation of
patchbotpatch 392485 - octavia - Spec detailing Octavia service flavors support (MERGED)17:19
pksinghi got to know by jniesz that someone is working on provider support17:20
pksinghi would like to help there too if any needed17:20
johnsomI think some folks are working on writing up the spec.17:21
johnsomlongstaff Do you have an update on how that is going?17:21
longstaffWe've been delayed a bit but will be working on it next week17:21
*** rossella_s has quit IRC17:22
pksinghjohnsom: should we wait for that spec to come up, or we should add flavor_profile metadat to current octavia handler?17:22
johnsomOk, feel free to post what you have and let some of us hack on it too....17:22
pksinghi did the same in
patchbotpatch 484325 - octavia - [WIP] Add provider Implementation17:23
johnsompksingh Well, we know it will change, but as long as we are ok re-working it17:23
johnsomIt might flush out any issues we missed, etc.17:23
rm_mobileThe spec says it's dependent on providers, is that not really the case?17:24
pksinghyes it dependes on the providers for validating the metadata part of flavor_profile17:25
pksinghi have left that step17:25
johnsomIt is, but the octavia driver handler is kind of like a provider (will need to be moved over)17:25
pksinghjohnsom: can i move ahead with treating handler as provider?17:26
*** lbrune has joined #openstack-meeting17:26
johnsomWell, the interface is totally going to change when we do providers17:26
pksinghok, then i will wait for provider spec to be merged17:28
johnsomI would not spend too much time on the octavia handlers until we get farther with the provider spec17:28
johnsomOk, so I will work on reviewing the flavors work.  Thanks!17:29
johnsom#topic Open Discussion17:29
*** openstack changes topic to "Open Discussion (Meeting topic: Octavia)"17:29
johnsomOther topics today?17:29
rm_workAdmin API stuff17:30
rm_workI have a couple of Admin API type things that I'm going to look at tackling very soon (like, starting today or tomorrow probably)17:31
rm_workNot sure if we want specs or if I should just show up with code17:31
*** yamamoto has quit IRC17:31
rm_workthe Amphora Info endpoint is up and ready to merge:
patchbotpatch 505404 - octavia - Add admin endpoint for amphora info17:31
rm_workthe next couple I want to do are:17:31
*** yamamoto has joined #openstack-meeting17:31
*** gans has quit IRC17:32
rm_work1) A patch to clear out the spares pool, so when we push a new image, we can get rid of the old spares quickly / easily)17:32
johnsomSpares pool is pretty straight forward, just an rfe is probably good for that17:32
rm_work2) Something to SYNC / retry LBs that are in bad states (ERROR, and possibly PENDING) because I have seen a number of LBs go to these states recently and it is ridiculous that there is no way to get a LB out of ERROR once it goes there17:33
rm_workI think there are some things we could at least *try*17:33
johnsomLet's talk about that one17:34
rm_workalso I'm tempted to have Housekeeping pop things from PENDING to ERROR if they've exceeded some timeout since last update17:35
rm_workbecause when a LB has been in PENDING_UPDATE for 30 minutes, it's obviously stuck17:35
rm_workand that state is immutable17:35
jnieszWe have been hit with a couple of lb's going into error, like when amphora fails to get DHCP on boot17:35
johnsomSo, I take it there are not others.17:36
rm_workyeah, I think possibly the correct approach for that is just to trigger failovers17:36
rm_workjohnsom: not off the top of my head yet17:36
jnieszalso when lb is in error, how can we be sure it cleans up all resources?17:37
johnsomSo, have you run to ground how these are getting stuck in PENDING_UPDATE?  That should not be happening.  Is it the controller process being restarted?17:37
rm_workso in that case, should the "failover API call" just ... be the "sync" or should there be more logic?17:37
rm_workjohnsom: in at least one case i've seen, yeah, the worker restarts and leaves it hanging17:37
*** unicell has joined #openstack-meeting17:38
johnsomYeah, ok, so the whole job board thing.  Did we break the graceful shutdown of the process or is this a host failed situation?17:38
rm_workjniesz: yeah, what i am thinking is we add an "attempt cleanup" method that tries to intelligently remove every piece (starting with VMs, then ports, then SGs) assuming it'll see a lot of 404s, and when it seems like everything is good, then do the failover path17:39
rm_workor just fix the failover path to accept 404s in more places17:39
rm_workjohnsom: i think the graceful shutdown is borked17:39
jnieszrm_work agreed that would make cleanup much better17:39
johnsomjniesz That is exactly why the current state machine is ERROR->DELETED17:39
rm_workyeah, because it was "easy" to start17:40
rm_workbut telling users "ah, i see your LB randomly went into error for you... time to delete it and start over!" is entirely unacceptable17:40
rm_workthe thing i've seen cause ERROR states the most often is actually failovers17:40
johnsomYeah, I agree with that.  I would really like to run to ground WHY they are going into provisioning state ERROR (we are not talking operation status here)17:41
rm_workusually when something dumb happens like a network blip17:41
jnieszor some other openstack component is having issues glance, neutron, etc...17:41
rm_workright, yes17:41
johnsomI'm hearing two things:17:41
*** lbrune has quit IRC17:42
rm_workit's "access to external services" mostly17:42
rm_workso again, is the answer to this maybe "to sync, trigger a failover"?17:42
johnsom1. We need to figure out why the worker is not gracefully shutting down (not finishing a workflow before exiting)17:42
rm_workbecause we do have the failover API17:42
*** aagate has left #openstack-meeting17:42
johnsom2. We need to evaluate adding more retry logic to the flows/tasks17:42
rm_workyes, but also:17:42
rm_work3. We need to provide some way to clean up stuff that still manages to get into an undefined state17:43
rm_workBecause we are awesome but not awesome enough that I predict everything will always be bug-free17:43
johnsomYeah.  Sadly failing over an ERROR object could mean you get into a worse state17:43
rm_workand us saying "well, we really should figure out *why*" when an operator has stuck LBs is not useful17:44
rm_workso the ability to clean up PENDING state stuff (as an operator, like, FORCE-DELETE) would be nice17:44
johnsomLike losing the VIP IP or having half an LB updated (one amp failover)17:44
rm_workyes, these things are bad17:45
rm_workand sometimes it happens17:45
rm_workand our delete flows also need to be improved a bit I think, because about 50% of the time something goes to ERROR, a delete is just going to ERROR-loop17:45
johnsomThat is bad.  Delete should be able to clean up ERROR cleanly17:46
rm_workthings like the "security group in use" issue still bite us even in the gate sometimes17:46
rm_worki've tried to fix that in my own driver17:46
rm_workbut it's tricky17:46
johnsomReally?  I have ONLY seen that in the gate when the main process failed due to coding bugs17:46
tonglI once had that ERROR-loop issue and ending up clean up the data to remove the lb resources.17:46
*** electrofelix has quit IRC17:47
rm_workyeah i have to dig into the DB17:47
rm_workquite often17:47
jnieszsame here17:47
*** oidgar has quit IRC17:47
johnsomYeah, so what I hope we can do is capture these as bugs, with logs, so we can understand the failure mechanism and work on good mitigation options.17:47
rm_workso, my plan would be a call that: A) ignores the state, so you can do a delete in any state; B) tries to first catalogue every possible object that we need to clean up; C) attempts to carefully clean up all of them17:48
johnsomIt also let's us discuss the pro/cons as some of these solutions have some really dangerous side effects17:48
*** Swami has joined #openstack-meeting17:48
*** rm_mobile has quit IRC17:49
*** e0ne has joined #openstack-meeting17:49
johnsomLike this one, if it's used while a controller is still working on the objects (still has the lock) you get into cases where your force-delete command cleans up parts, but controller goes and creates more orphaned objects.17:50
*** pksingh has quit IRC17:50
johnsomIt's like it would need to check with the controllers to see if they are still "active" with that object17:50
rm_workthen what about the suggestion that HK flips things to ERROR after a configured timeout?17:51
johnsomOur original plan for this was the job board implementation, where it passes the flow token to different controllers if one fails to check in and move it forward.17:51
rm_workand we just assume you need to wait until that, and at that point anything is done17:51
rm_workyeah i mean, jobboard would be great, we've been talking about it for 3 years17:52
johnsomTrue.  Act/Act for 2ish17:52
*** sambetts is now known as sambetts|afk17:52
johnsomAre we ok with starting by capturing these scenarios in bugs (stories)?17:53
johnsomI think we need to be capturing these and discussing solutions.17:53
tonglI am ok with that17:53
jnieszyes, I think looking at the specific use cases is a good start17:53
jnieszspecific issues17:54
*** sshank has quit IRC17:54
johnsomrm_work ?17:55
rm_workok. probably I will make this API in the meantime, but only use it downstream17:55
rm_workand when we figure out what we need, i can tweak and push it up17:55
*** spn has quit IRC17:55
johnsomYeah, I just think it's going to get abused by folks not thinking about the situation enough.17:55
johnsomThat is the concern.17:56
rm_workprobably, but meanwhile i need runbooks to give to people who don't know octavia much, and will keep me out of 24/7 on-call17:56
johnsomBig red buttons are shiny17:56
rm_workand as long as I design the big red button, i'd rather have them press that than the "call me at 2am on a weekend" button17:56
*** manjeets has joined #openstack-meeting17:57
johnsomYeah, I just don't like spending days deleting orphaned objects, corrupt DBs17:57
rm_worki'm already DOING that17:57
rm_workbut I think I can find the orphaned stuff17:57
rm_workwith code17:57
johnsomOk, so looking forward to some bugs so we can understand the problems17:58
johnsomWe have two minutes, any other quick topics?17:58
*** treiz has quit IRC17:58
jnieszis the plan to use failover api for changing flavors?17:59
johnsomOye, that is a topic isn't it17:59
johnsomCan I put it on the agenda for next week?17:59
johnsomOr in the channel.17:59
johnsomWe are out of time.18:00
bh526r#startmeeting gluon18:00
openstackbh526r: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.18:00
*** openstack changes topic to "OpenStack Meetings ||"18:00
openstackMeeting ended Wed Sep 27 18:00:15 2017 UTC.  Information about MeetBot at . (v 0.1.4)18:00
openstackMinutes (text):
bh526r#startmeeting gluon18:00
openstackMeeting started Wed Sep 27 18:00:31 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:00
jinli#info JinLi18:01
bh526rHi Jin, good morning?18:01
jinlihi Bin18:01
krenczewski#info Kamil Renczewski18:01
bh526rHi Kamil18:01
jinliHi Kamil18:01
krenczewskiHi Bin and Jin18:01
*** pksingh has joined #openstack-meeting18:01
*** lbrune has joined #openstack-meeting18:01
*** bobh has quit IRC18:01
bh526r#topic Admin update18:02
*** openstack changes topic to "Admin update (Meeting topic: gluon)"18:02
bh526r#info Nothing from my side18:02
bh526r#topic Planning for PoC in OpenStack Summit in Sydney18:02
*** openstack changes topic to "Planning for PoC in OpenStack Summit in Sydney (Meeting topic: gluon)"18:02
*** spn has joined #openstack-meeting18:02
*** spn has quit IRC18:02
*** spn has joined #openstack-meeting18:02
bh526rLooks like Huawei has backed off18:03
bh526rSo we may have to put it on hold18:04
*** reedip_ has joined #openstack-meeting18:04
bh526rI assume no update from Kamil as well, right?18:04
krenczewskiNot yet18:04
krenczewskiJust reviewing and merging old patches18:05
krenczewskiI mean patches since Sukhdev was on vacation18:05
bh526rsounds good18:05
*** longstaff has left #openstack-meeting18:05
*** ralonsoh has quit IRC18:06
bh526r#info No update. Kamil has been focusing on reviewing and merging the old patches18:06
*** oidgar has joined #openstack-meeting18:06
bh526r#topic Planning for Gluon Queens Release18:06
*** openstack changes topic to "Planning for Gluon Queens Release (Meeting topic: gluon)"18:06
bh526r#info 1. Refactor Gluon as Neutron Service Plugin18:07
bh526r#info Sukhdev created a new repo for Neutron service plugin - networking-gluon18:07
bh526r#info 2. Jin has pushed a patch to fix a bug at backend18:07
*** lhx_ has quit IRC18:07
patchbotpatch 507299 - gluon - Change status code to 200 (MERGED)18:07
*** pksingh has quit IRC18:08
bh526r#info It was approved and merged, anc cherrypicked to stable/pike18:08
jinliHi Bin, i will schedule a meeting with you tomorrow to discuss the backend18:08
bh526rSure, thank you Jin18:08
bh526rnothing else from my side18:08
jinlitomorrow 1pm work for you?18:08
bh526rHow about 12:30pm? I have a hard stop at 1:30pm.18:09
jinliwill do it18:09
bh526rThank you Jin18:09
*** jkilpatr has quit IRC18:10
bh526ranything else from either of you?18:10
krenczewskiI am good18:10
jinlithat's all from me, I will send out meeting invitation18:10
bh526rGreat. So we always keep our meeting short, and focus on real work, which is good :)18:10
bh526rWe can adjourn, and Kamil can enjoy a good night :)18:11
bh526r#info Nothing else, meeting is adjourned18:11
*** dpertin has joined #openstack-meeting18:11
*** openstack changes topic to "OpenStack Meetings ||"18:11
openstackMeeting ended Wed Sep 27 18:11:27 2017 UTC.  Information about MeetBot at . (v 0.1.4)18:11
jinlibye bin and kamil18:11
krenczewskiGreat, thanks and bye18:11
openstackMinutes (text):
*** krenczewski has quit IRC18:11
bh526rThank you Kamil and Jin, and bye all18:11
*** XueFeng has quit IRC18:12
*** bh526r has quit IRC18:12
*** XueFeng has joined #openstack-meeting18:12
*** bobmel has quit IRC18:14
*** pcaruana has joined #openstack-meeting18:15
*** ramineni_ has quit IRC18:16
*** Sukhdev has quit IRC18:17
*** rbowen has quit IRC18:17
*** yamahata has joined #openstack-meeting18:23
*** jkilpatr has joined #openstack-meeting18:23
*** radez has joined #openstack-meeting18:29
*** galstrom is now known as galstrom_zzz18:32
*** sshank has joined #openstack-meeting18:32
*** sshank has quit IRC18:33
*** sshank has joined #openstack-meeting18:33
*** sshank has quit IRC18:35
*** reedip_ has quit IRC18:35
*** jniesz has left #openstack-meeting18:37
*** rwsu has quit IRC18:38
*** sshank has joined #openstack-meeting18:44
*** lpetrut has joined #openstack-meeting18:47
*** lpetrut has quit IRC18:50
*** lpetrut has joined #openstack-meeting18:51
*** Rockyg has quit IRC18:53
*** rbowen has joined #openstack-meeting18:54
*** spn has quit IRC18:55
*** spn has joined #openstack-meeting18:55
*** spn has quit IRC18:55
*** spn has joined #openstack-meeting18:55
*** dprince has quit IRC18:56
*** sshank has quit IRC18:56
Zaraanyone about for the storyboard meeting?18:56
* Zara will give it a minute or two18:57
*** cleong has quit IRC18:58
*** JudeC has quit IRC18:59
Zaraa minute or two has passed, I get the impression nobody else wants a meeting :D18:59
Zarafair enough, no meeting this week!19:00
*** slaweq_ has joined #openstack-meeting19:00
Zarawe're always available in #storyboard for any questions etc19:00
*** pcaruana has quit IRC19:00
SotKtoo late xD19:00
ZaraTOO LATE19:01
fungiclearly i should set my meeting reminder to be _before_ the meeting time ;)19:02
*** hemna_ has quit IRC19:02
Zarawell if people want one we can still have one, but I get the impression nobody's fussed19:02
*** sanfern has left #openstack-meeting19:03
funginope, just wanted to make sure i was around _in case_ there was a meeting19:04
*** mrunge_ has joined #openstack-meeting19:04
SotKI have no urgent need for one19:04
*** mrunge has quit IRC19:06
*** e0ne has quit IRC19:08
*** Swanson has quit IRC19:08
*** hasharAway is now known as hashar19:09
*** coolsvap has quit IRC19:11
*** manjeets has quit IRC19:14
*** edmondsw has quit IRC19:15
*** dbecker has quit IRC19:17
*** edmondsw has joined #openstack-meeting19:18
*** dprince has joined #openstack-meeting19:20
*** jamemcc_ has quit IRC19:22
*** edmondsw has quit IRC19:23
*** bobh has joined #openstack-meeting19:26
*** Patifa has joined #openstack-meeting19:30
*** rwsu has joined #openstack-meeting19:32
*** rbowen has quit IRC19:35
*** eharney has quit IRC19:44
*** colettecello has quit IRC19:47
*** b1airo has quit IRC19:47
*** gothicmindfood has joined #openstack-meeting19:47
*** edmondsw has joined #openstack-meeting19:47
*** edmondsw has quit IRC19:48
*** b1airo has joined #openstack-meeting19:48
*** edmondsw has joined #openstack-meeting19:48
*** markvoelker has quit IRC19:48
*** jprovazn has quit IRC19:48
*** markvoelker has joined #openstack-meeting19:49
*** dbecker has joined #openstack-meeting19:53
*** martial has joined #openstack-meeting19:56
*** chyka has quit IRC20:02
*** chyka has joined #openstack-meeting20:02
*** sshank has joined #openstack-meeting20:05
*** dayou has quit IRC20:07
*** bobmel has joined #openstack-meeting20:07
*** yamamoto has quit IRC20:08
*** dbecker has quit IRC20:11
*** dbecker has joined #openstack-meeting20:11
*** jkilpatr has quit IRC20:14
*** bobmel has quit IRC20:15
*** bobmel has joined #openstack-meeting20:15
*** martial has quit IRC20:20
*** sshank has quit IRC20:24
*** sshank has joined #openstack-meeting20:24
*** yamamoto has joined #openstack-meeting20:27
*** yamamoto has quit IRC20:31
*** gouthamr_ has quit IRC20:32
*** belmoreira has joined #openstack-meeting20:32
*** ansmith has quit IRC20:33
*** dbecker has quit IRC20:34
*** gouthamr has joined #openstack-meeting20:35
*** radez has quit IRC20:35
*** dalvarez has quit IRC20:35
*** julim has quit IRC20:36
*** julim has joined #openstack-meeting20:37
*** radez has joined #openstack-meeting20:37
*** dalvarez has joined #openstack-meeting20:37
*** gouthamr has quit IRC20:39
*** gouthamr has joined #openstack-meeting20:42
*** belmoreira has quit IRC20:44
*** gouthamr has quit IRC20:45
*** lbrune has quit IRC20:46
*** esberglu has quit IRC20:47
*** esberglu has joined #openstack-meeting20:48
*** rwsu has quit IRC20:52
*** esberglu has quit IRC20:52
*** Patifa has quit IRC20:55
*** Patifa has joined #openstack-meeting20:56
*** VW_ has joined #openstack-meeting20:56
*** VW_ has quit IRC20:57
*** VW_ has joined #openstack-meeting20:57
*** oidgar has quit IRC20:57
*** pchavva has quit IRC20:58
*** kota_ has joined #openstack-meeting20:59
*** acoles has joined #openstack-meeting21:00
*** VW has quit IRC21:00
*** e0ne has joined #openstack-meeting21:00
*** timburke has joined #openstack-meeting21:00
notmyname#startmeeting swift21:01
openstackMeeting started Wed Sep 27 21:01:08 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:01
*** openstack changes topic to " (Meeting topic: swift)"21:01
openstackThe meeting name has been set to 'swift'21:01
notmynamewho's here for the swift meeting?21:01
*** iyamahat has joined #openstack-meeting21:01
*** Alex_Staf has joined #openstack-meeting21:02
acoleshappy triage day21:02
_pewp_jungleboyj ( ^_^)/21:02
*** m_kazuhiro has joined #openstack-meeting21:02
notmyname#topic bug triage day21:02
*** openstack changes topic to "bug triage day (Meeting topic: swift)"21:02
notmynamethe only topic today is bug triage day21:02
*** Swanson has joined #openstack-meeting21:02
notmynameso how is it going?21:03
notmynameI've been in meetings all day21:03
kota_me too, in fact.21:03
notmyname(speaking of which, a quick summary from the put/post meeting earlier would be nice as the next topic)21:03
*** e0ne has quit IRC21:04
*** eharney has joined #openstack-meeting21:04
timburkeit goes. i'm currently stuck trying to remove swift from a bug without getting a 503 though21:05
*** e0ne has joined #openstack-meeting21:05
notmynameany questions that have come up related to open bugs? anything we need to discuss?21:05
notmynamethis may be a very short meeting ;-)21:05
*** zaitcev has joined #openstack-meeting21:05
tdasilvasame as goes...21:06
timburke is reasonably interesting/worth discussing -- should we be more opinionated about what gets counted in our error stats?21:06
openstackLaunchpad bug 1695273 in OpenStack Object Storage (swift) "Subrequests from ratelimit for /auth/v1.0 considered as proxy-server errors" [Undecided,New]21:06
mattoliverauI haven't started yet, as I'm triaging on meeting day21:06
mattoliverauBut looking at the graphs, do we need track new (or untriaged) bugs21:07
mattoliverauI don't see em21:07
mattoliverauOr maybe I need to zoom in21:07
tdasilvanotmyname: I was thinking that maybe it would have been better to have like a goal in mind. 'let's commit to triage 5 bugs today'21:07
notmynamemattoliverau: I think tdasilva made some updates to the code. tdasilva can I redeploy it?21:07
timburkei still don't even see graphs :-)21:07
acolesI got though a few. having the day marked on my calendar definitely forced me to make give some time to it.21:07
notmynametimburke: yeah, reload it. sometimes works for me21:07
tdasilvanotmyname: nothing new to deploy yet, sorry...was just starting to play with it21:07
*** galstrom_zzz is now known as galstrom21:08
*** esberglu has joined #openstack-meeting21:08
*** bobh has quit IRC21:08
tdasilvamattoliverau: I'd go by the etherpad21:08
tdasilvaacoles: yeah, me too :)21:08
notmynametimburke: IMO about that error, there was another bug about ratelimit + auth and RL+s3, so it may all be related to rl just not checkign the right thing?21:08
*** torgomatic has joined #openstack-meeting21:08
notmynametdasilva: acoles: good to hear (about the calendar day prompting you to look at more)21:09
mattoliverauOh yeah, I plan too.. just looking at graphs cause graphs are cool21:09
*** thorst has quit IRC21:09
acolesI found myself setting some Wishlist bugs to Confirmed just to get them out of New status. does that make sense? I suppose we might reject a wishlist bug.21:09
notmynameacoles: yeah, that sounds fine21:09
timburkeyeah, there are three parts to it -- i was about to just close it because the first two were better written up as separate (and referenced!) bugs when i noticed the ask about proxy-logging21:09
notmynameand yes I can totally imagine rejecting a wishlist bug :-)21:10
*** ayoung has quit IRC21:10
tdasilvaI just rejected a wishlist bug as 'won't fix' :/21:10
*** thorst has joined #openstack-meeting21:11
notmynameok, doesn't sound like a lot of questions about bug triage...21:12
notmynamekeep up the good work :-)21:12
notmyname#topic put/post meeting summary21:12
*** rwsu has joined #openstack-meeting21:12
*** openstack changes topic to "put/post meeting summary (Meeting topic: swift)"21:12
notmynamezaitcev: would you like to give a summary of this morning's meeting?21:12
notmynametdasilva: do you have the recording link?21:12
notmyname(anyone else can give a summary too)21:13
zaitcevnotmyname: sure21:13
tdasilvalooking for link21:13
*** LeoBud has joined #openstack-meeting21:13
acolesis zaitcev  here?21:14
*** bnemec has quit IRC21:14
mattoliverauWell we said 'sure' so yeah21:14
zaitcevWe considered what was done and found that I didn't realize that our commit protocol had 3 distinct phases. Instead, I only implemented 2, by squishing metadata write and the commit to durable together. So this needs to change.21:14
*** rossella_s has joined #openstack-meeting21:14
*** thorst has quit IRC21:15
patchbotpatch 427911 - swift - PUT+POST and its development test21:15
patchbotpatch 427911 - swift - PUT+POST and its development test21:15
*** radez has quit IRC21:16
zaitcevOtherwise, there weren't any major concerns raised. Nobody objected to 20-minute timeouts for re-probing servers, or to the protocol detection tricks.21:16
*** dalvarez has quit IRC21:16
notmynamefrom the high level, this patch zaitcev is working on is very important because it unblocks a few other things going on (clay removing evently, alex doing LOSF, eventually a golang storage server)21:17
*** galstrom is now known as galstrom_zzz21:17
notmynamethis patch means that the object server is back to being "real" http instead of relying on features that we implemented in eventlet's https server21:17
notmynameacoles: tdasilva: timburke: anything else to add about the meeting this mroning?21:17
notmynamezaitcev: what's the next step?21:18
*** radez has joined #openstack-meeting21:18
*** dalvarez has joined #openstack-meeting21:18
zaitcevOh, and also! I managed to complain about our unit tests that are so insanely complex that I could not adapt them to the new code, so when you run .unittests on that thing, it just forces old EC.21:18
tdasilvanotmyname, zaitcev: i think we also need to look at the solution torgomatic had for the linkat path, right?21:19
notmynameah, right21:19
torgomaticyeah, I need to get that cleaned up enough that I can post it somewhere without too much shame21:19
zaitcevnotmyname: I'm going to create PUT+POST+POST that has 3 phases, run "git review', hope I'm not wasting your time with this.21:19
acoleszaitcev: you are not wasting time21:20
zaitcevoh, yeah, the linkat(2)21:20
notmynamenot at all21:20
*** LeoBud has quit IRC21:20
tdasilvatorgomatic: is this patch still desired as part of this exercise:
patchbotpatch 340526 - swift - Unify Putter and MIMEPutter into a single class.21:20
acoleswe need PUT->temp file, POST ->non-durable .data file, POST -> durable data file21:20
*** caboucha has quit IRC21:20
claygso many verbs!21:20
acolesfirst post carries the metadata, second post is the commit21:21
zaitcevacoles: thanks for clarification, that's how I understood the necessary change.21:21
torgomatictdasilva: I mean, I think it's good to have, otherwise crypto or other footer-using things are going to end up still having MIME in their protocol21:21
timburkei wonder if we might be able to still use 100-continue to collapse the two POSTs... i don't think we'd need to send any headers with it, then21:22
zaitcevI have looked at that unified thing and was indiffirent to it... It does not hurt PUT+POST, although currently it's convenient to use a whole new class (DoublePutter) and flip it over. But it can be done with some kind of argument to .connect() as well.21:22
*** raildo has quit IRC21:23
*** e0ne has quit IRC21:24
*** aeng has joined #openstack-meeting21:24
clayg@timburke you just blew my mind!21:25
claygI would expect any request would a body *could* send expect: 100-continue21:25
notmynamewhat's the next step? zaitcev will push a new patch and we review it, expecting it to land? or is there more obvious work to do? (ie are we including all this in the first patch or doing that later?)21:26
timburkeclayg: and we could just have that body be a 0-byte chunk like what i'm doing in
patchbotpatch 476992 - swift - Make If-None-Match:* work properly with 0-byte PUTs21:27
acolesnotmyname: we need to address the unit test issue21:28
claygtimburke: hrm... 100-continue chunked transfer... yes...21:28
*** yamamoto has joined #openstack-meeting21:28
notmynameunless we have more logistics or something like that to cover, I think details of implementation could be discussed in -swift (and we can end this one earlier or allow for other things)21:29
notmyname#topic open discussion21:29
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:29
notmynameanything else to bring up this week?21:29
*** thorst has joined #openstack-meeting21:29
mattoliverauI just wanted to thank acoles and timburke  on all the awesome sharding cleanup patches21:29
timburkeand thanks torgomatic and zaitcev for landing !21:30
patchbotpatch 506410 - swift - Stop reloading swift.common.utils in test_daemon (MERGED)21:30
timburkeit'll unblock mattoliverau's
patchbotpatch 506002 - swift (feature/deep) - Use temp db and a rename for set_sharding_state21:30
acolesmattoliverau: you did the hard work21:30
notmynametdasilva: can you give a quick summary of the swift3 call we had last week?21:32
*** slaweq_ has quit IRC21:32
notmynamenotes from the swift3 meeting are at21:32
tdasilvasure, we had another meeting to discuss how we should go about adding the swift3 middleware to swift tree21:32
tdasilvawe listed some of the patches that should be merged before doing a last release on swift321:33
tdasilvaand also came up with a list of work that would need to get done on the feature branch before the new s3api middleware lands on master21:33
mattoliverauSorry that was the toddler on my lap21:33
tdasilvait's all on the etherpad ^^^21:33
*** beekhof_mb has quit IRC21:33
*** thorst has quit IRC21:34
kota_nice tdasilva thanks21:34
notmynameanything else going on that needs a status update?21:34
m_kazuhiroI think symlink patch #232162 is ready for review and it looks good to me. So please review it.21:34
patchbot - swift - Symlink implementation.21:34
notmynameI think we covered the big stuff I know of21:34
*** yamamoto has quit IRC21:34
tdasilvayes, please help review symlink patch, i know it's a bit on the fringe of everybody work, but it would be nice if we could finally merge it21:35
tdasilvaas it would unblock m_kazuhiro tiering work21:35
mattoliverauFor those of us in Australia.. day light savings changes this weekend (I think)21:35
notmynameyeah, unfortunately on the fringe, but definitely something that is needed21:35
notmynamemattoliverau: ah, ok. so you'll be one more hour apart21:36
notmyname(I think)21:36
mattoliverauYeah, I go forward an hour21:36
*** yamahata has quit IRC21:36
notmynameoh, you'll be closer then21:36
mattoliverauSo this will be an hour later21:36
notmyname(to CA)21:36
claygjust came up in a meeting here a few minutes ago - well more like "tiering" - but symlinks was explicitly called out as an important primitive regardless.21:36
mattoliverauWhich isn't bad for this meeting :)21:36
*** yamahata has joined #openstack-meeting21:37
notmynameI think we're good for this meeting this week :-)21:38
notmynamethanks for coming21:38
notmynamekeep up the good work on bug triaging21:38
notmynameand thanks for working on swift21:38
*** openstack changes topic to "OpenStack Meetings ||"21:38
openstackMeeting ended Wed Sep 27 21:38:40 2017 UTC.  Information about MeetBot at . (v 0.1.4)21:38
openstackMinutes (text):
*** timburke has left #openstack-meeting21:39
*** kota_ has left #openstack-meeting21:39
*** m_kazuhiro has quit IRC21:40
*** dprince has quit IRC21:42
*** VW_ has quit IRC21:42
*** VW has joined #openstack-meeting21:43
*** awaugama has quit IRC21:43
*** gyee has quit IRC21:44
*** VW has quit IRC21:47
*** sshank has quit IRC21:47
*** baoli has quit IRC21:54
*** jkilpatr has joined #openstack-meeting21:56
*** yamamoto has joined #openstack-meeting21:57
*** mriedem is now known as mriedem_away21:57
*** yamamoto has quit IRC21:57
*** thorst has joined #openstack-meeting21:58
*** lpetrut has quit IRC21:59
*** hashar has quit IRC22:00
*** kbyrne has quit IRC22:00
*** slaweq_ has joined #openstack-meeting22:03
*** kbyrne has joined #openstack-meeting22:03
*** tongl has left #openstack-meeting22:03
*** rwsu has quit IRC22:07
*** Patifa has quit IRC22:08
*** rossella_s has quit IRC22:10
*** b1airo has quit IRC22:11
*** Patifa has joined #openstack-meeting22:15
*** galstrom_zzz is now known as galstrom22:21
*** edmondsw has quit IRC22:23
*** rossella_s has joined #openstack-meeting22:23
*** rbudden has quit IRC22:24
*** dpertin has quit IRC22:27
*** sshank has joined #openstack-meeting22:29
*** markstur_ has quit IRC22:29
*** markstur has joined #openstack-meeting22:29
*** markstur has quit IRC22:29
*** krtaylor has quit IRC22:30
*** slaweq_ has quit IRC22:36
*** oidgar has joined #openstack-meeting22:36
*** sshank has quit IRC22:37
*** rbudden has joined #openstack-meeting22:38
*** iyamahat has quit IRC22:39
*** ansmith has joined #openstack-meeting22:39
*** slaweq_ has joined #openstack-meeting22:39
*** krtaylor has joined #openstack-meeting22:43
*** cdub has quit IRC22:44
*** sshank has joined #openstack-meeting22:45
*** oidgar has quit IRC22:46
*** b1airo has joined #openstack-meeting22:47
*** jaypipes has quit IRC22:48
*** rossella_s has quit IRC22:56
*** bobh has joined #openstack-meeting22:57
*** yamamoto has joined #openstack-meeting22:58
*** rtjure has quit IRC23:01
*** bobh has quit IRC23:02
*** claudiub|3 has quit IRC23:03
*** bcafarel has quit IRC23:03
*** yamamoto has quit IRC23:05
*** ricolin has joined #openstack-meeting23:06
*** b1airo has quit IRC23:10
*** Patifa has quit IRC23:12
*** slaweq_ has quit IRC23:13
*** bcafarel has joined #openstack-meeting23:16
*** baoli has joined #openstack-meeting23:18
*** slaweq_ has joined #openstack-meeting23:18
*** baoli_ has joined #openstack-meeting23:22
*** baoli has quit IRC23:22
*** hongbin has quit IRC23:25
*** rbowen has joined #openstack-meeting23:28
*** galstrom is now known as galstrom_zzz23:29
*** felipemonteiro_ has quit IRC23:29
*** thorst has quit IRC23:30
*** mriedem_away is now known as mriedem23:31
*** Sukhdev has joined #openstack-meeting23:32
*** rbowen has quit IRC23:33
*** b1airo has joined #openstack-meeting23:35
*** ssathaye has quit IRC23:35
*** ssathaye has joined #openstack-meeting23:35
*** krtaylor has quit IRC23:35
*** edmondsw has joined #openstack-meeting23:40
*** ijw has joined #openstack-meeting23:43
*** edmondsw has quit IRC23:44
*** ijw has quit IRC23:45
*** ijw has joined #openstack-meeting23:45
*** tpsilva has quit IRC23:46
*** sshank has quit IRC23:47
*** slaweq_ has quit IRC23:48
*** markstur has joined #openstack-meeting23:49
*** krtaylor has joined #openstack-meeting23:51
*** krtaylor has quit IRC23:51
*** slaweq_ has joined #openstack-meeting23:52
*** bnemec has joined #openstack-meeting23:52
*** sshank has joined #openstack-meeting23:52
*** sshank has quit IRC23:53
*** iyamahat has joined #openstack-meeting23:56
*** lhx_ has joined #openstack-meeting23:57
*** yamahata has quit IRC23:58

Generated by 2.15.3 by Marius Gedminas - find it at!