Tuesday, 2017-08-22

*** sshank has quit IRC00:01
*** diablo_rojo has quit IRC00:02
*** thorst has quit IRC00:02
*** Apoorva_ has joined #openstack-meeting00:04
*** palexster has quit IRC00:04
*** Apoorva has quit IRC00:06
*** palexster has joined #openstack-meeting00:07
*** yangyapeng has joined #openstack-meeting00:11
*** yangyapeng has quit IRC00:11
*** wanghao_ has quit IRC00:13
*** wanghao has joined #openstack-meeting00:13
*** baojg has quit IRC00:16
*** Swami has quit IRC00:17
*** baojg has joined #openstack-meeting00:17
*** yamamoto_ has joined #openstack-meeting00:18
*** felipemonteiro has quit IRC00:18
*** emagana has quit IRC00:21
*** baojg has quit IRC00:21
*** yamamoto_ has quit IRC00:24
*** thorst has joined #openstack-meeting00:25
*** thorst has quit IRC00:26
*** Manuel_112 has joined #openstack-meeting00:28
*** felipemonteiro has joined #openstack-meeting00:29
*** rbudden has quit IRC00:30
*** Manuel_112 has quit IRC00:33
*** esberglu has quit IRC00:33
*** kiennt has joined #openstack-meeting00:36
*** anilvenkata|AFK has quit IRC00:37
*** zhurong has joined #openstack-meeting00:45
*** JudeC has quit IRC00:50
*** wanghao_ has joined #openstack-meeting00:51
*** unicell1 has quit IRC00:51
*** litao__ has joined #openstack-meeting00:52
*** wanghao has quit IRC00:54
*** gmann has joined #openstack-meeting01:01
*** mtanino has quit IRC01:03
*** fzdarsky_ has joined #openstack-meeting01:07
*** fzdarsky has quit IRC01:10
*** _pewp_ has quit IRC01:13
*** hoangcx has left #openstack-meeting01:14
*** yangyapeng has joined #openstack-meeting01:15
*** _pewp_ has joined #openstack-meeting01:16
*** kevzha01 has joined #openstack-meeting01:19
*** yangyape_ has joined #openstack-meeting01:20
*** yangyapeng has quit IRC01:20
*** yamamoto_ has joined #openstack-meeting01:21
*** anilvenkata|AFK has joined #openstack-meeting01:21
*** yamamoto_ has quit IRC01:26
*** thorst has joined #openstack-meeting01:26
*** Julien-zte has quit IRC01:28
*** Manuel_112 has joined #openstack-meeting01:29
*** caowei has joined #openstack-meeting01:30
*** kevzha01 is now known as kevinz01:31
*** anilvenkata|AFK has quit IRC01:31
*** thorst has quit IRC01:31
*** Julien-zte has joined #openstack-meeting01:31
*** bobh has quit IRC01:32
*** Manuel_112 has quit IRC01:34
*** hongbin has joined #openstack-meeting01:34
*** gcb has joined #openstack-meeting01:36
*** guoshan has joined #openstack-meeting01:39
*** thorst has joined #openstack-meeting01:51
*** thorst has quit IRC01:51
*** iyamahat has quit IRC02:03
*** cloudrancher has quit IRC02:05
*** cloudrancher has joined #openstack-meeting02:05
*** yamahata has quit IRC02:10
*** julim has joined #openstack-meeting02:10
*** gcb has quit IRC02:12
*** bkopilov has quit IRC02:13
*** gcb has joined #openstack-meeting02:15
*** yamamoto_ has joined #openstack-meeting02:22
*** shu-mutou has joined #openstack-meeting02:22
*** baojg has joined #openstack-meeting02:23
*** baojg has quit IRC02:28
*** yamamoto_ has quit IRC02:28
*** wanghao_ has quit IRC02:29
*** Manuel_112 has joined #openstack-meeting02:30
*** wanghao has joined #openstack-meeting02:31
*** Manuel_112 has quit IRC02:35
*** Apoorva_ has quit IRC02:38
*** Apoorva has joined #openstack-meeting02:38
*** Apoorva has quit IRC02:42
*** hongbin has quit IRC02:48
*** thorst has joined #openstack-meeting02:52
*** pksingh has joined #openstack-meeting02:52
*** spn has quit IRC02:53
*** spn has joined #openstack-meeting02:53
*** hongbin has joined #openstack-meeting02:54
*** Namrata has joined #openstack-meeting02:54
*** yamamoto has joined #openstack-meeting02:56
*** thorst has quit IRC02:57
hongbin#startmeeting zun03:00
openstackMeeting started Tue Aug 22 03:00:01 2017 UTC and is due to finish in 60 minutes.  The chair is hongbin. Information about MeetBot at http://wiki.debian.org/MeetBot.03:00
hongbin#link https://wiki.openstack.org/wiki/Zun#Agenda_for_2017-08-22_0300_UTC Today's agenda03:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:00
*** openstack changes topic to " (Meeting topic: zun)"03:00
openstackThe meeting name has been set to 'zun'03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
*** Shunli has joined #openstack-meeting03:00
hongbinthanks for joining the meeting spn Namrata mkrai pksingh kevinz Shunli03:00
hongbinok, let's get started03:01
hongbin#topic Announcements03:01
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:01
hongbin1. Zun 0.2.0 release03:01
hongbin#link https://review.openstack.org/#/c/494541/03:01
hongbinthe stable/pike branch is cute based on this release03:01
hongbinso this is the official pike release03:01
hongbinthanks all for working hard in this cycle to deliver it03:01
hongbinfrom now no, bug fixes could be back port to stable/pike branch03:02
*** yamamoto has quit IRC03:02
hongbinhowever, it needs to be fixed in master branch first03:02
hongbinany comment on this ?03:02
*** wanghao has quit IRC03:03
mkraiThank you for your efforts03:03
hongbinmkrai: np, thanks all to deliver this release :)03:03
*** wanghao has joined #openstack-meeting03:03
hongbinseems no more comment, continue03:04
pksinghi could not contribute much in this release, hope to contribute much in next one :)03:04
hongbinpksingh: ack, thanks for your contribution :)03:04
hongbin#topic Review Action Items03:04
*** openstack changes topic to "Review Action Items (Meeting topic: zun)"03:04
hongbin1. hongin create a bp for api version negoiation (DONE)03:04
hongbin#link https://blueprints.launchpad.net/zun/+spec/api-version-negotiation03:04
hongbini tried to outline the requirements in the bp03:05
hongbinplease feel free to review this bp and take it if you interest03:05
hongbinnote: you can ask a core to assign a bp to you if you couldn't assign it yourself03:05
hongbinok, move on03:06
hongbin#topic Cinder integration03:06
*** openstack changes topic to "Cinder integration (Meeting topic: zun)"03:06
hongbinfor this one, i got a WIP patch up for review03:06
hongbin#link https://review.openstack.org/#/c/473115/03:06
hongbinit is a huge patch, i am going to break it down into several smaller patches03:07
pksinghhuge patch :)03:07
hongbinthe idea is to call cinder API to connect to the volume, them bindmount it to the container03:07
hongbinthe cinder attach workflow is a bit complicated, and needs to handle a lot of exceptions03:08
hongbini tried to break everything into module, hope it is more clear03:09
mkraiis the patch functional?03:09
hongbinmkrai: not yet, just for a preview03:09
mkraiOk wanted to try out before reviewing03:09
hongbinmkrai: if i removed the WIP, then the patch is funtional03:09
mkraihongbin: Ok03:10
hongbinmkrai: will let you know once it is ready to try03:10
mkraihongbin: Thank you03:10
hongbinmkrai: np03:10
hongbini will continue to work on the patch this week03:10
hongbinthat is all from me03:10
hongbinany other question/comment?03:11
hongbinseems no, move on to the next item in agenda03:12
hongbin#topic Introduce container composition (kevinz)03:12
*** openstack changes topic to "Introduce container composition (kevinz) (Meeting topic: zun)"03:12
hongbin#link https://blueprints.launchpad.net/zun/+spec/introduce-compose03:12
hongbinkevinz: ^^03:12
*** apetrich has quit IRC03:12
kevinzThis week I'm struggling with capsule test case in API side.03:12
kevinzBecause it introduce the experimental endpoint, so thing not very easy to write test case. However, I will continue to finish this today or tomorrow03:13
hongbinkevinz: unit tests ? or tempest tests?03:14
kevinzUnit test03:14
hongbini see03:15
kevinzI will ping you for some help offline if possible :-)03:15
hongbinkevinz: sure03:16
hongbinkevinz: in addition, i wanted to mention that there are progress for this bp last week03:16
pksinghkevinz feel free to ping me too, if i can help you somehow03:16
hongbinkevinz: because we just merged a (huge) patch for capsule-create03:16
kevinzhongbin: pksingh: Thanks a lot03:16
*** apetrich has joined #openstack-meeting03:17
kevinzhongbin: Yes, a good progress03:17
hongbin#link https://review.openstack.org/48460203:17
hongbinthere are several other patches are merged as well03:17
*** iyamahat has joined #openstack-meeting03:17
hongbinthere is one to configure the devstack script to add the experimental endpoint03:18
hongbinthere is a client patch that add support for the capsule api03:18
hongbinthose are great patches :)03:18
hongbinkevinz: thanks for your hard work on this feature :)03:18
*** _pewp_ has quit IRC03:19
mkraikevinz: Thank you :)03:19
kevinzhongbin: mkrai: My pleasure03:19
kevinzBTW, this patch need another review https://review.openstack.org/#/c/480455/03:19
kevinzSo that it can be merge in client side03:19
hongbinack, thanks kevinz03:20
NamrataI will  go through it and review03:20
kevinzNamrata: Thx in advance:-)03:20
hongbinok, move on03:21
hongbin#topic NFV use cases (lakerzhou)03:21
*** openstack changes topic to "NFV use cases (lakerzhou) (Meeting topic: zun)"03:21
hongbinlakerzhou seems not here today03:21
hongbinfor this bp, shunli has several pci patches that are merged last week03:21
Shunliwill go on working on the database and objects03:22
hongbinShunli: ack03:22
*** _pewp_ has joined #openstack-meeting03:23
hongbinShunli: after the databae and objects is done, what will be the next step, the scheduler?03:23
hongbinor the compute?03:23
hongbini see03:24
Shunlioh, sorry.maybe the compute first03:24
Shunlifirst need the pci tracker to collect the pci info03:24
*** artom has quit IRC03:24
hongbinsecond, report the pci info to the scheduler (i guess)03:25
hongbinget it03:25
hongbinsounds like a plan03:25
hongbinShunli: thanks shunli for working on this03:25
Shunlinp. my pleasure03:26
hongbinall, any comment on this topic?03:26
hongbinok, next topic03:27
hongbin#topic Zun connector for k8s03:27
*** openstack changes topic to "Zun connector for k8s (Meeting topic: zun)"03:27
hongbin#link https://blueprints.launchpad.net/zun/+spec/zun-connector-for-k8s03:27
hongbinwe have an etherpad up for this one03:27
hongbin#link https://etherpad.openstack.org/p/zun-connector-k8s03:27
* hongbin is reviewing the etherpad03:28
Shunlihongbin: I refered last team meeting is about https://kubernetes.io/docs/concepts/api-extension/apiserver-aggregation/03:29
*** luyao_ has joined #openstack-meeting03:29
hongbinShunli: go ahead03:29
Shunliis it possible to integrate zun with k8s like integrate zun with heat, define some customed resource type in k8s for zun.03:29
Shunliprovide zun api as k8s's third party api using the apiserver-aggregation.03:30
hongbini think this is possible technically03:31
*** Manuel_112 has joined #openstack-meeting03:31
*** bkopilov has joined #openstack-meeting03:31
ShunliI just think it's a easy and feasible way to integrate zun with k8s03:31
mkraiI think the intention is not to implement anything in k8s03:32
mkraibut provide a similar implementation in zun so that it can be consumed by k8s03:32
mkraiShunli: hongbin WDYT?03:33
pksinghand i think we discussed that idea in past too03:33
kevinzAs I see, modify code in K8S is very hard and out of control03:33
hongbinmkrai: i agree with you comment in general03:33
mkraikevinz: Right, that's my point as well :)03:33
Shunliyes, modify code in k8s is some kinds of out of control.03:34
*** Manuel_112 has quit IRC03:35
hongbinin addition, i see it this way:03:35
hongbinShunli's idea is about extend k8s API to implement a Zun API03:35
hongbinThe ACI connector is about bridge k8s to Zun (with k8s API)03:36
hongbinthe intention are very different03:36
kevinzI will check it. That's a new idea03:37
mkraiSorry I didn't get the first point03:38
mkraiDoes it mean we extend the k8s API in Zun?03:38
mkraiuser -> zun -> k8s ?03:39
hongbinno, shunli proposal is a k8s api extension for zun03:39
hongbinso in k8s api, there will be pod, service , ... , then there is an extension that provide "container", which is a zun container03:40
mkraiuser->k8s->zun. Right?03:40
*** baoli has joined #openstack-meeting03:40
mkraihongbin: That seems very difficult to get through k8s community :)03:40
hongbinmkrai: yes, it is03:40
hongbinpossibly, it needs to be out-of-tree03:41
hongbinfrankly, i am not sure if k8s users interest in a "container" api if there is already a "pod" that they are familiar with03:41
mkraihongbin: I agree completely03:41
mkraicontainer endpoint in k8s wouldn't make sense03:42
hongbinShunli: i see the idea, but not sure if it will work , that is my comment :)03:42
Shunlii'm creating the paste, maybe we can discuss if it possible03:43
hongbinShunli: sure03:43
hongbinShunli: in addition, feel free to list your idea in the etherpad (as option #3 in design): https://etherpad.openstack.org/p/zun-connector-k8s03:43
Shunliok, thx.03:44
hongbin#topic Open Discussion03:44
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:44
hongbinany other topic to bring up ?03:44
mkraihongbin: Can I go ahead with the clear container patches?03:44
hongbinmkrai: feel free03:45
mkraihongbin: Thank you03:45
kevinzmkrai: I have a question about clear container03:45
mkraikevinz: sure03:45
hongbinmkrai: if you feel like, i can allocate a topic for clear container in the meeting03:45
kevinzmkrai: does it mature to commercial use case?03:45
mkraihongbin: Sure03:46
hongbinmkrai: ack03:46
mkraikevinz: I guess yes :)03:46
mkraiIt is integrated with k8s, swarm as well03:46
kevinzmkrai: ACK03:46
spnIn fact it makes more sense using CC with all its security around container03:46
hongbinspn: ++03:46
mkraispn: yes :)03:47
hongbinfor example, in public cloud, strong-isolated container like CC is a must03:47
*** baoli has quit IRC03:47
*** jamesmcarthur has joined #openstack-meeting03:47
hongbinso clear container integration is very import for zun03:48
spnbut definately we should have an option of running regular containers and clear containers on same computes03:48
hongbini see03:48
mkraispn: We will have that support03:49
spnmkrai: great :)03:49
hongbinhave both in the same compute node is a bit challenging, but i believe it can be done03:50
mkraiBdw I and spn will have a session at sydney on clear container, if interested please join :)03:50
mkraihongbin: can you tell the issues if possible?03:51
hongbinmkrai: i don't know what will be the issues, the challenging is like to ask nova to support two hypervisors in the same node :)03:51
*** links has joined #openstack-meeting03:51
spnprobably run multiple docker daemons on different port numbers one with coe runtime03:51
hongbinperhaps , it will be easy, i am just not sure03:51
*** jamesmcarthur has quit IRC03:52
mkraihongbin: ack. I will note this point and see if there's any issue03:52
hongbini see03:53
*** baoli has joined #openstack-meeting03:53
mkraispn: I am not sure of that now. But seems that can be an option.03:53
*** thorst has joined #openstack-meeting03:53
spnmkrai: yup!03:53
mkraihongbin: spn Thanks03:54
hongbinall, any other topic or question?03:54
mkraiNone from me03:55
hongbinall, thanks for joining the meeting, see you next time :)03:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"03:55
openstackMeeting ended Tue Aug 22 03:55:58 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-08-22-03.00.html03:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-08-22-03.00.txt03:56
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-08-22-03.00.log.html03:56
spnbye all03:56
*** afanti has joined #openstack-meeting03:56
*** hongbin has quit IRC03:56
*** samP has joined #openstack-meeting03:58
*** baoli has quit IRC03:58
*** hongbin has joined #openstack-meeting03:58
*** thorst has quit IRC03:59
*** tpatil has joined #openstack-meeting03:59
*** baoli has joined #openstack-meeting03:59
*** rkmrHonjo has joined #openstack-meeting04:00
samPHi all for masakari meeting04:00
samP#startmeeting masakari04:00
openstackMeeting started Tue Aug 22 04:00:55 2017 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:00
*** abhishekk has joined #openstack-meeting04:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** openstack changes topic to " (Meeting topic: masakari)"04:00
openstackThe meeting name has been set to 'masakari'04:00
samPHi all o/04:01
Dinesh_BhorHi all04:01
*** pksingh has left #openstack-meeting04:01
samP#link agenda https://wiki.openstack.org/wiki/Meetings/Masakari04:01
samPLet's start04:02
samPFirst; about the release04:02
samPThanks to all, we were able to do the on 8/1804:02
samPNext tag would be, will be on 8/2504:03
*** yamamoto has joined #openstack-meeting04:03
*** jamesmcarthur has joined #openstack-meeting04:03
samPFinal release 4.0.0 will be on 8/3004:04
*** baoli has quit IRC04:04
*** Takahara has joined #openstack-meeting04:04
samPNow we have stable/pike in a separate branch, we can continue work on master for Queens04:04
*** hongbin has quit IRC04:04
*** abhishekk has quit IRC04:04
*** abhishek_k has joined #openstack-meeting04:04
*** abhishek_k is now known as abhishekk04:05
*** baoli has joined #openstack-meeting04:05
samPIf you have any critical updates for stable/pike please raise them before 8/2504:05
tpatilsamP: Sure04:06
samP8/29 Masakari IRC team meeting would be the last place to discuss such things04:06
samP#topic Bugs04:06
*** openstack changes topic to "Bugs (Meeting topic: masakari)"04:06
samPany bugs to discuss?04:07
*** jamesmcarthur has quit IRC04:08
samPSince we released last week, not much to discuss here. If you have any, please use AOB to discuss them04:08
samPLet's goto next item04:08
samP#topic Discussion points04:08
*** openstack changes topic to "Discussion points (Meeting topic: masakari)"04:08
samP(1) Application for become OpenStack oficial project04:09
*** yamamoto has quit IRC04:09
samPCouldn't finish it. definitely do it today04:09
*** baoli has quit IRC04:09
samP(2) Install guide document04:09
samPI think patches are up for all documentations. Need to review them.04:10
samPThis include masakari-monitors documentations04:10
*** baoli has joined #openstack-meeting04:11
samPI will and please review them if you have spare time04:11
samP(3) recovery method customization04:11
samPwe need to clarify discussion points with Mistral team at PTG04:12
tpatilMistral etherpad is not open to add this item in the Queen PTG agenda04:12
samPtpatil: Thanks.04:12
tpatilIMO, For our case, there is no need to restart mistral service04:12
tpatilbut in future, if we add few actions which might requires you to restart mistral service, then that could be a problem.04:13
samPtpatil: you said, some actions would need to restart it.04:13
tpatilwe will discuss with Mistral community to understand in what instances you need to restart mistral service04:13
tpatilsamP: For our POC, no need to restart mistral service04:14
samPtpatil: great.04:14
samPtpatil: But we dont know what will happen future, if some one add new action.04:15
samPtpatil: as you said ^^04:15
*** baoli has quit IRC04:15
samPtpatil: let's make those clear, So, we could avoid using them.04:16
tpatilsamP: correct, so we will discuss this point with Mistral community04:16
samPtpatil: thanks.04:16
samPtpatil: May I ask you to add this item to Mistarl etherpad, when it opens04:17
tpatilsamP: Will do04:17
samP#action tpatil Add item to Mistral PTG etherpad for discuss when we should restart mistral service04:18
samPtpatil: thanks04:18
samP(4) Find hosts without specifying segments04:19
*** jamesmcarthur has joined #openstack-meeting04:19
samPrkmrHonjo: any updates on this?04:19
rkmrHonjoI have thought about CLI way.(This was my homework in previous meeting.) In my idea...04:19
rkmrHonjoIf user run "masakari get-host-by-segment <host name>", masakariCLI will do below processes:04:19
rkmrHonjo1. Call segment list API.04:20
rkmrHonjo 2. Call host list API for each segments.04:20
rkmrHonjo3. If there is the specified host, masakariCLI will show following columns: segment id, segment name, host id, host name04:20
rkmrHonjoFor example, "neutron net-list" uses multiple APIs.(Network list API & Subnet list API)04:20
rkmrHonjoSo, I think that CLI way is not impossible.04:21
samPrkmrHonjo: thanks04:21
*** esberglu has joined #openstack-meeting04:21
samPAre there any need for get singe host details in masakari?04:22
samPI mean without segments?04:22
samPFor an Ex, monitoring masakari itself04:22
tpatilsamP: Yes, when you process notification, we get hostname from notification request04:23
*** Namrata has quit IRC04:23
*** jamesmcarthur has quit IRC04:23
tpatilsamP: but we get the host details using db apis04:23
tpatilDinesh: Please confirm ^^04:24
samPtpatil: yes, correct04:24
Dinesh_Bhortpatil: yes correct04:24
*** anilvenkata has joined #openstack-meeting04:24
Dinesh_Bhorit is internal and not the user specific requirement04:24
samPbut my question is, do we need that on APIs?04:24
Dinesh_BhorI think, No04:24
tpatilsamP: No04:24
samPfor an ex, if we want to setup a horizon UI for masakari :)04:25
samPprobably not..04:25
samPOK, then can we agree to go with CLI based solution for this?04:25
samPwhich is proposed by rkmrHonjo04:26
rkmrHonjosamP: OK. Should I write bp?04:26
rkmrHonjoAh, I'll write bp. sorry.04:27
samPrkmrHonjo: this is a new feature for python-masakariclient, please write a bp04:28
samPfor this04:28
rkmrHonjosamP: Sure.04:28
samPif no objection; rkmrHonjo please proceed with CLI based solution.04:28
tpatilsamP: adding this support in CLI is simplest way to solve this problem04:29
samPyou will have another chance to raise your objections in BP or code review.04:29
samPtpatil: sure.04:29
samP#action rkmrHonjo crate BP and process with CLI based solution for "Find hosts without specifying segments"04:30
*** esberglu has quit IRC04:31
samPrkmrHonjo: I assigned this item to you, is it OK?04:31
rkmrHonjosamP: No problem.04:32
samPrkmrHonjo: thanks04:32
*** Manuel_112 has joined #openstack-meeting04:32
samP(5) Queens Work Items04:32
samPI created a etherpad for this/04:32
samP#link Queens Work Items https://etherpad.openstack.org/p/masakari-queens-workitems04:33
samPPlease add new items before 8/2804:34
samPWe could review them on 8/29 meeting04:34
tpatilsamP: Ok04:34
*** Takahara_ has joined #openstack-meeting04:34
rkmrHonjosamP: Sure.04:34
*** jamesmcarthur has joined #openstack-meeting04:34
samPsecond round would be on 9/5 meeting04:34
samP(6) Pike work Items04:35
*** Takahara has quit IRC04:36
*** Manuel_112 has quit IRC04:36
samPwe need to re arrange these items04:37
samPLet's mark things done with [done] tag and not completed ones with [uncomplete] and skipped to queens ones with [skipped]04:38
rkmrHonjosamP: ok.04:38
samPI will put those tags, and let's do a review on our next IRC meeting04:38
*** jamesmcarthur has quit IRC04:38
samPI will import skipped and uncomplete items to new Queens etherpad04:39
samPLet's have a review on 8/2904:39
samP#topic AOB04:40
*** openstack changes topic to "AOB (Meeting topic: masakari)"04:40
samPif nothing, we could finish meeting bit early...04:40
rkmrHonjoI don't have AOB items.04:41
tpatilsamP: Nothing from my side too04:41
samPOK then, thank you all for attending to this meeting..04:42
Dinesh_Bhorthank you all04:42
samPhave a good day..04:42
rkmrHonjothank you.04:42
tpatilThank you all04:42
*** abhishekk has left #openstack-meeting04:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"04:42
openstackMeeting ended Tue Aug 22 04:42:36 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-08-22-04.00.html04:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-08-22-04.00.txt04:42
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-08-22-04.00.log.html04:42
*** rkmrHonjo has quit IRC04:42
*** Takahara_ has quit IRC04:45
*** tpatil has quit IRC04:47
*** jamesmcarthur has joined #openstack-meeting04:50
*** trinaths has joined #openstack-meeting04:51
*** caowei has quit IRC04:51
*** thorst has joined #openstack-meeting04:54
*** markvoelker has quit IRC04:54
*** jamesmcarthur has quit IRC04:54
*** epico has joined #openstack-meeting04:56
*** thorst has quit IRC04:58
*** baoli has joined #openstack-meeting05:00
*** masber has quit IRC05:02
*** samP has quit IRC05:03
*** baoli has quit IRC05:04
*** baoli has joined #openstack-meeting05:04
*** yamamoto has joined #openstack-meeting05:05
*** jamesmcarthur has joined #openstack-meeting05:05
*** jamesmcarthur has quit IRC05:10
*** yamamoto has quit IRC05:10
*** unicell has joined #openstack-meeting05:11
*** epico has quit IRC05:16
*** tovin07_ has joined #openstack-meeting05:18
*** jamesmcarthur has joined #openstack-meeting05:21
*** gcb has quit IRC05:21
*** gcb has joined #openstack-meeting05:23
*** psachin has joined #openstack-meeting05:24
*** jamesmcarthur has quit IRC05:25
*** claudiub has joined #openstack-meeting05:27
*** epico has joined #openstack-meeting05:28
*** links has quit IRC05:30
*** ricolin_ has quit IRC05:31
*** ricolin has joined #openstack-meeting05:31
*** Manuel_112 has joined #openstack-meeting05:32
*** links has joined #openstack-meeting05:33
*** jamesmcarthur has joined #openstack-meeting05:36
*** lpetrut has joined #openstack-meeting05:36
*** Manuel_112 has quit IRC05:37
*** baoli has quit IRC05:37
*** markstur has quit IRC05:38
*** markstur has joined #openstack-meeting05:39
*** jamesmcarthur has quit IRC05:41
*** edmondsw has joined #openstack-meeting05:42
*** markstur has quit IRC05:44
*** caowei has joined #openstack-meeting05:44
*** JudeC has joined #openstack-meeting05:46
*** edmondsw has quit IRC05:47
*** yangyape_ has quit IRC05:48
*** yangyapeng has joined #openstack-meeting05:49
*** jamesmcarthur has joined #openstack-meeting05:52
*** chyka has joined #openstack-meeting05:54
*** masber has joined #openstack-meeting05:55
*** thorst has joined #openstack-meeting05:55
*** jamesmcarthur has quit IRC05:56
*** kiennt has quit IRC05:58
*** chyka has quit IRC05:59
*** thorst has quit IRC05:59
*** Manuel_112 has joined #openstack-meeting06:02
*** yamamoto has joined #openstack-meeting06:06
*** jamesmcarthur has joined #openstack-meeting06:07
*** tobiajo has joined #openstack-meeting06:08
*** kiennt has joined #openstack-meeting06:09
*** yamamoto has quit IRC06:12
*** jamesmcarthur has quit IRC06:12
*** sridharg has joined #openstack-meeting06:14
*** lpetrut has quit IRC06:14
*** lpetrut has joined #openstack-meeting06:18
*** kiennt has quit IRC06:22
*** jamesmcarthur has joined #openstack-meeting06:23
*** jamesmcarthur has quit IRC06:27
*** lpetrut has quit IRC06:29
*** abhishekk has joined #openstack-meeting06:31
*** yamahata has joined #openstack-meeting06:33
*** _jbadiapa has joined #openstack-meeting06:38
*** jamesmcarthur has joined #openstack-meeting06:38
*** jbadiapa_ has quit IRC06:38
*** armax has quit IRC06:39
*** jprovazn has joined #openstack-meeting06:40
*** eusherek has joined #openstack-meeting06:42
*** jamesmcarthur has quit IRC06:43
*** rcernin has joined #openstack-meeting06:45
*** pcaruana has joined #openstack-meeting06:45
*** slaweq_ has joined #openstack-meeting06:46
*** slaweq_ has quit IRC06:50
*** markvoelker has joined #openstack-meeting06:55
*** coolsvap has joined #openstack-meeting06:55
*** ykatabam has joined #openstack-meeting06:55
*** thorst has joined #openstack-meeting06:56
*** ircuser-1 has joined #openstack-meeting06:57
*** kiennt has joined #openstack-meeting06:59
*** thorst has quit IRC07:00
*** unicell has quit IRC07:01
*** unicell has joined #openstack-meeting07:01
*** abhishekk has quit IRC07:03
*** csomerville has joined #openstack-meeting07:05
*** cody-somerville has quit IRC07:05
*** jamesmcarthur has joined #openstack-meeting07:09
*** jamesmcarthur has quit IRC07:14
*** iyamahat has quit IRC07:18
*** dmellado has joined #openstack-meeting07:18
*** tesseract has joined #openstack-meeting07:20
*** unicell has quit IRC07:23
*** rbartal has joined #openstack-meeting07:26
*** belmoreira has joined #openstack-meeting07:29
*** markvoelker has quit IRC07:29
*** edmondsw has joined #openstack-meeting07:30
*** yamahata has quit IRC07:31
*** psachin has quit IRC07:34
*** phil_ has joined #openstack-meeting07:35
*** edmondsw has quit IRC07:35
*** phil_ is now known as Guest2938507:35
*** jamesmcarthur has joined #openstack-meeting07:40
*** chyka has joined #openstack-meeting07:44
*** jamesmcarthur has quit IRC07:44
*** jbadiapa_ has joined #openstack-meeting07:46
*** eusherek has quit IRC07:47
*** priteau has joined #openstack-meeting07:47
*** _jbadiapa has quit IRC07:48
*** chyka has quit IRC07:48
*** VW_ has joined #openstack-meeting07:54
*** VW has quit IRC07:54
*** iyamahat has joined #openstack-meeting07:54
*** jamesmcarthur has joined #openstack-meeting07:56
*** thorst has joined #openstack-meeting07:57
*** jamesmcarthur has quit IRC08:00
*** thorst has quit IRC08:01
*** toscalix has joined #openstack-meeting08:03
*** makowals has quit IRC08:06
*** makowals has joined #openstack-meeting08:06
*** alexchadin has joined #openstack-meeting08:09
*** jamesmcarthur has joined #openstack-meeting08:11
*** Guest29385 is now known as preisner08:14
*** jamesmcarthur has quit IRC08:16
*** iyamahat has quit IRC08:25
*** markvoelker has joined #openstack-meeting08:26
*** jamesmcarthur has joined #openstack-meeting08:27
*** lpetrut has joined #openstack-meeting08:28
*** jamesmcarthur has quit IRC08:31
*** yamamoto has joined #openstack-meeting08:35
*** jamesmcarthur has joined #openstack-meeting08:42
*** jbadiapa_ has quit IRC08:45
*** jamesmcarthur has quit IRC08:47
*** tobiajo_ has joined #openstack-meeting08:49
*** makowals has quit IRC08:49
*** makowals_ has joined #openstack-meeting08:50
*** tobiajo has quit IRC08:51
*** tobiajo_ has quit IRC08:54
*** thorst has joined #openstack-meeting08:57
*** jamesmcarthur has joined #openstack-meeting08:58
*** yamamoto has quit IRC08:59
*** tobiajo_ has joined #openstack-meeting08:59
*** yamamoto has joined #openstack-meeting08:59
*** yamamoto has quit IRC08:59
*** mahatic has joined #openstack-meeting08:59
*** ociuhandu has quit IRC08:59
*** JudeC has quit IRC09:00
*** markvoelker has quit IRC09:00
*** jbadiapa_ has joined #openstack-meeting09:01
*** thorst has quit IRC09:02
*** jamesmcarthur has quit IRC09:02
*** electrofelix has joined #openstack-meeting09:03
*** sapd has joined #openstack-meeting09:03
*** mahatic has quit IRC09:07
*** mahatic has joined #openstack-meeting09:08
*** chyka has joined #openstack-meeting09:10
*** apetrich has quit IRC09:13
*** apetrich has joined #openstack-meeting09:13
*** jamesmcarthur has joined #openstack-meeting09:13
*** chyka has quit IRC09:15
*** brault has quit IRC09:16
*** brault_ has joined #openstack-meeting09:16
*** ykatabam has quit IRC09:17
*** jamesmcarthur has quit IRC09:17
*** sambetts|afk is now known as sambetts09:21
*** apetrich has quit IRC09:23
*** arnewiebalck has joined #openstack-meeting09:24
*** jamesmcarthur has joined #openstack-meeting09:29
*** baojg has joined #openstack-meeting09:30
*** Shunli has quit IRC09:30
*** e0ne has joined #openstack-meeting09:33
*** shu-mutou is now known as shu-mutou-AWAY09:33
*** jamesmcarthur has quit IRC09:33
*** baojg has quit IRC09:34
*** wanghao has quit IRC09:34
*** wanghao has joined #openstack-meeting09:35
*** apetrich has joined #openstack-meeting09:35
*** wanghao has quit IRC09:35
*** wanghao has joined #openstack-meeting09:35
*** wanghao has quit IRC09:36
*** wanghao has joined #openstack-meeting09:36
*** wanghao has quit IRC09:37
*** wanghao has joined #openstack-meeting09:37
*** wanghao has quit IRC09:38
*** markstur has joined #openstack-meeting09:38
*** wanghao has joined #openstack-meeting09:38
*** wanghao has quit IRC09:38
*** wanghao has joined #openstack-meeting09:39
*** wanghao has quit IRC09:39
*** wanghao has joined #openstack-meeting09:40
*** markstur has quit IRC09:42
*** jamesmcarthur has joined #openstack-meeting09:45
*** Manuel_112 has quit IRC09:45
*** jamesmcarthur has quit IRC09:48
*** csomerville has quit IRC09:50
*** jbadiapa_ has quit IRC09:52
*** jbadiapa_ has joined #openstack-meeting09:52
*** markvoelker has joined #openstack-meeting09:57
*** thorst has joined #openstack-meeting09:58
*** makowals_ has quit IRC09:58
*** caowei has quit IRC09:59
*** makowals has joined #openstack-meeting09:59
*** yamamoto has joined #openstack-meeting10:00
*** tovin07_ has quit IRC10:00
*** makowals_ has joined #openstack-meeting10:02
*** Manuel_112 has joined #openstack-meeting10:02
*** thorst has quit IRC10:03
*** yangyapeng has quit IRC10:04
*** kiennt has quit IRC10:05
*** makowals has quit IRC10:05
*** yamamoto has quit IRC10:05
*** alexchadin has quit IRC10:05
*** alexchadin has joined #openstack-meeting10:07
*** alexchadin has quit IRC10:10
*** alexchadin has joined #openstack-meeting10:11
*** alexchadin has quit IRC10:13
*** markstur has joined #openstack-meeting10:15
*** jamesmcarthur has joined #openstack-meeting10:15
*** zhurong has quit IRC10:17
*** caowei has joined #openstack-meeting10:18
*** markstur has quit IRC10:19
*** jamesmcarthur has quit IRC10:20
*** caowei has quit IRC10:20
*** apetrich has quit IRC10:23
*** yamamoto has joined #openstack-meeting10:30
*** markvoelker has quit IRC10:31
*** jamesmcarthur has joined #openstack-meeting10:31
*** rossella_s has joined #openstack-meeting10:31
*** rossella_s has quit IRC10:31
*** guoshan has quit IRC10:33
*** jamesmcarthur has quit IRC10:35
*** baoli has joined #openstack-meeting10:45
*** jamesmcarthur has joined #openstack-meeting10:46
*** jkilpatr has quit IRC10:48
*** baoli has quit IRC10:49
*** markstur has joined #openstack-meeting10:51
*** jamesmcarthur has quit IRC10:52
*** tobberydberg has quit IRC10:53
*** tobberydberg has joined #openstack-meeting10:53
*** fzdarsky_ is now known as fzdarsky|afk10:55
*** markstur has quit IRC10:55
*** bkopilov has quit IRC10:56
*** DinaBelova has quit IRC11:00
*** aignatov has quit IRC11:00
*** freerunner has quit IRC11:00
*** DinaBelova has joined #openstack-meeting11:00
*** htruta has quit IRC11:00
*** kambiz has quit IRC11:00
*** njohnston has quit IRC11:00
*** htruta has joined #openstack-meeting11:00
*** _alastor- has quit IRC11:00
*** junbo has quit IRC11:01
*** e0ne has quit IRC11:01
*** fzdarsky|afk has quit IRC11:01
*** ansmith has quit IRC11:01
*** bkero has quit IRC11:01
*** Dinesh_Bhor has quit IRC11:01
*** aignatov has joined #openstack-meeting11:01
*** zerick has quit IRC11:01
*** stephenfin has quit IRC11:01
*** toabctl has quit IRC11:01
*** zerick has joined #openstack-meeting11:02
*** e0ne has joined #openstack-meeting11:02
*** alex_xu has quit IRC11:02
*** toabctl has joined #openstack-meeting11:04
*** vryzhenkin has joined #openstack-meeting11:04
*** fzdarsky|afk has joined #openstack-meeting11:04
*** Dinesh_Bhor has joined #openstack-meeting11:05
*** junbo has joined #openstack-meeting11:05
*** kambiz has joined #openstack-meeting11:05
*** _alastor__ has joined #openstack-meeting11:05
*** stephenfin has joined #openstack-meeting11:05
*** alex_xu has joined #openstack-meeting11:06
*** njohnston has joined #openstack-meeting11:06
*** bkero has joined #openstack-meeting11:06
*** edmondsw has joined #openstack-meeting11:06
*** ansmith has joined #openstack-meeting11:06
*** thorst has joined #openstack-meeting11:07
*** jkilpatr has joined #openstack-meeting11:07
*** edmondsw has quit IRC11:10
*** thorst has quit IRC11:11
*** alexchadin has joined #openstack-meeting11:13
*** yamamoto has quit IRC11:18
*** rbudden has joined #openstack-meeting11:25
*** epico has quit IRC11:25
*** markvoelker has joined #openstack-meeting11:28
*** markstur has joined #openstack-meeting11:28
*** VW_ has quit IRC11:29
*** VW has joined #openstack-meeting11:29
*** yamamoto has joined #openstack-meeting11:30
*** markstur has quit IRC11:33
*** VW has quit IRC11:34
*** raildo has joined #openstack-meeting11:34
*** fnaval has quit IRC11:41
*** ociuhandu has joined #openstack-meeting11:43
*** edmondsw has joined #openstack-meeting11:45
*** yamamoto has quit IRC11:46
*** abhishekk has joined #openstack-meeting11:48
*** yamamoto has joined #openstack-meeting11:48
*** apetrich has joined #openstack-meeting11:52
*** litao__ has quit IRC11:58
*** VW has joined #openstack-meeting11:59
*** VW has quit IRC11:59
*** markvoelker has quit IRC12:01
*** yamamoto has quit IRC12:03
*** VW has joined #openstack-meeting12:03
*** yamamoto has joined #openstack-meeting12:04
*** markstur has joined #openstack-meeting12:05
*** artom has joined #openstack-meeting12:06
*** baoli has joined #openstack-meeting12:08
*** yamamoto has quit IRC12:10
*** markstur has quit IRC12:10
*** Julien-zte has quit IRC12:11
*** thorst has joined #openstack-meeting12:11
*** yamamoto has joined #openstack-meeting12:12
*** julim has quit IRC12:12
*** baoli has quit IRC12:12
*** Julien-zte has joined #openstack-meeting12:14
*** tobiajo_ has quit IRC12:17
*** dprince has joined #openstack-meeting12:25
*** markvoelker has joined #openstack-meeting12:32
*** psachin has joined #openstack-meeting12:35
*** psachin has quit IRC12:39
*** psachin has joined #openstack-meeting12:39
*** tobiajo_ has joined #openstack-meeting12:39
*** rmascena has joined #openstack-meeting12:40
*** raildo has quit IRC12:42
*** markstur has joined #openstack-meeting12:42
*** felipemonteiro has quit IRC12:43
*** felipemonteiro has joined #openstack-meeting12:43
*** pchavva has joined #openstack-meeting12:44
*** markstur has quit IRC12:47
*** thorst is now known as thorst_afk12:49
*** bkopilov has joined #openstack-meeting12:49
*** kylek3h has joined #openstack-meeting12:50
*** ruijie has joined #openstack-meeting12:50
*** pchavva has quit IRC12:51
*** alexchadin has quit IRC12:51
*** trinaths has left #openstack-meeting12:51
*** alexchadin has joined #openstack-meeting12:51
*** esberglu has joined #openstack-meeting12:53
*** mtanino has joined #openstack-meeting12:55
*** baojg has joined #openstack-meeting12:56
*** zhurong has joined #openstack-meeting12:57
Qiming#startmeeting senlin13:00
openstackMeeting started Tue Aug 22 13:00:15 2017 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: senlin)"13:00
openstackThe meeting name has been set to 'senlin'13:00
ruijieevening Qiming13:02
Qimingdon't know if there are others joining today13:04
Qimingand I don't have many items for discussion13:04
Qimingjust one thing about senlin-dashboard13:05
Qimingwe are supposed to cut a release this week13:05
*** awaugama has joined #openstack-meeting13:05
ruijieme neither. the DB change had beed merged13:05
Qimingit needs a stable/pike branch13:05
Qimingnot sure if there still things to be done at rdo release side13:06
ruijieXueFeng is not here?13:07
*** felipemonteiro_ has joined #openstack-meeting13:07
*** mtanino has quit IRC13:07
Qimingseems no13:07
Qimingwe also have two community wide goals to claim13:08
Qimingit was long due13:08
QimingI believe senlin can be deployed using wsgi a long time ago and its support to py35 has been completed last year13:09
*** julim has joined #openstack-meeting13:09
Qimingjsut need to double confirm this and propose an update13:10
ruijiewhere to propose the proposal to update it?13:10
Qimingexample: https://review.openstack.org/#/c/491754/13:12
*** yamamoto has quit IRC13:12
*** yamamoto has joined #openstack-meeting13:14
ruijiethanks Qiming, will look at the governance project :)13:15
QimingI'm searching for Queens goals13:15
*** baoli has joined #openstack-meeting13:18
Qimingboth queens goals need some effort13:19
*** markstur has joined #openstack-meeting13:19
ruijieem.. still try to understand it13:19
Qimingthese two goals ... sigh13:20
QimingI don't understand the benefits13:20
Qimingbtw, https://docs.openstack.org/project-team-guide/ptl.html13:21
*** yamamoto has quit IRC13:22
*** baoli has quit IRC13:22
*** markstur has quit IRC13:23
QimingI have added liyi to the core team13:24
ruijieyes Qiming, noticed the mail from mail list13:24
*** hoangcx_ has joined #openstack-meeting13:25
*** palexster has quit IRC13:27
*** felipemonteiro__ has joined #openstack-meeting13:29
*** VW_ has joined #openstack-meeting13:29
*** fnaval has joined #openstack-meeting13:30
Qimingfinally, found this: https://governance.openstack.org/tc/reference/tags/index.html13:31
*** ruijie has quit IRC13:32
*** Julien-zte has quit IRC13:32
*** felipemonteiro_ has quit IRC13:32
Qimingwe may want to consider some of the tags we should apply13:32
*** VW has quit IRC13:32
*** VW__ has joined #openstack-meeting13:32
*** VW_ has quit IRC13:32
*** pchavva has joined #openstack-meeting13:33
*** bobh has joined #openstack-meeting13:35
*** ruijie has joined #openstack-meeting13:36
ruijiesorry, just lost connection ..13:36
Qimingfinally, found this: https://governance.openstack.org/tc/reference/tags/index.html13:36
Qimingwe may want to consider some of the tags we should apply during queens13:37
Qimingif we are not qualified, find the problem and solve it13:37
*** xyang1 has joined #openstack-meeting13:37
Qimingother than that, I don't have more to discuss13:37
ruijieokay, Qiming. Will have a look at these stuffs.13:38
*** eharney has joined #openstack-meeting13:38
*** Julien-zte has joined #openstack-meeting13:39
Qimingwe can end this today?13:39
ruijieyes Qiming :) talk to you in #senlin for just 1 min?13:39
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:39
openstackMeeting ended Tue Aug 22 13:39:57 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-08-22-13.00.html13:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-08-22-13.00.txt13:40
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-08-22-13.00.log.html13:40
*** davidsha has joined #openstack-meeting13:40
*** lhx has joined #openstack-meeting13:43
*** jbadiapa_ has quit IRC13:43
*** lhx is now known as Guest5772813:44
*** chenyb4_ has joined #openstack-meeting13:47
*** apetrich has quit IRC13:48
*** XueFengLiu has joined #openstack-meeting13:49
*** VW__ has quit IRC13:49
*** VW has joined #openstack-meeting13:50
*** XueFengLiu has quit IRC13:51
*** noslzzp has joined #openstack-meeting13:53
*** alexchadin has quit IRC13:55
*** markstur has joined #openstack-meeting13:56
*** alexchadin has joined #openstack-meeting13:56
*** fzdarsky|afk is now known as fzdarsky13:56
*** yamahata has joined #openstack-meeting13:57
*** XueFengLiu has joined #openstack-meeting13:57
*** julim has quit IRC13:58
*** XueFengLiu has quit IRC13:59
*** hongbin has joined #openstack-meeting13:59
*** jbadiapa_ has joined #openstack-meeting13:59
*** markstur has quit IRC14:00
*** julim has joined #openstack-meeting14:00
*** igordc has joined #openstack-meeting14:02
*** felipemonteiro__ has quit IRC14:02
igordc#startmeeting network_common_flow_classifier14:02
openstackMeeting started Tue Aug 22 14:02:40 2017 UTC and is due to finish in 60 minutes.  The chair is igordc. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: network_common_flow_classifier)"14:02
openstackThe meeting name has been set to 'network_common_flow_classifier'14:02
igordchi davidsha, all14:04
igordc#topic CCF v0 - first wave of code (update)14:04
*** openstack changes topic to "CCF v0 - first wave of code (update) (Meeting topic: network_common_flow_classifier)"14:04
davidshaMyself and Thaynara are working on Unit tests for the Service plugin at the moment.14:05
*** Thaynara has joined #openstack-meeting14:05
*** bcafarel has quit IRC14:05
*** reedip_ has joined #openstack-meeting14:06
davidshaWe're also working on addressing bcafarel comments on the patchset about tenant_id problems.14:06
*** cdub has joined #openstack-meeting14:06
igordcdavidsha: great14:06
*** iyamahat has joined #openstack-meeting14:07
davidshaigordc: Thats the one, We're also going to break off some pieces of this patch into other patches to make it more digestible and easier to review.14:08
davidshaThe Database migration code will be the first to be moved into it's own patch.14:09
igordcgood stuff14:09
*** tmorin has joined #openstack-meeting14:09
igordcdavidsha: can we still make it before pike is released? (not that it's too important, but would be a good milestone to sync with)14:10
tmorinhi everyone, sorry for joining late14:10
igordchey tmorin, long time no see!14:10
davidshatmorin: welcome, no problem.14:10
davidshaigordc: I'm hoping the smaller patches will help make that milestone.14:11
igordcgreat, tmorin any questions about the state of the code?14:11
*** marst has joined #openstack-meeting14:11
tmorinI just came to catch up14:12
igordcvery well, let's mve on14:12
igordc#topic PTG update14:12
*** openstack changes topic to "PTG update (Meeting topic: network_common_flow_classifier)"14:12
tmorinI saw the v0 patch, haven't had time to have a look yet14:12
igordcThaynara and davidsha will push a new patch soon14:12
igordcso about the PTG... davidsha you're likely not going there either correct?14:13
*** armax has joined #openstack-meeting14:14
davidshaigordc: Ya, my travel approval was rejected unfortunately, I'm going to see if there is an appeal, but we're too close now for that to be viable.14:14
igordcdavidsha: right, so neither of us going, so it will be a bit more difficult to engage on brainstorming discussions14:15
igordctmorin are you going to the PTG?14:15
igordcI had a CCF topic for the PTG, mainly to talk about what v1 has to have and to start/accelerate dev of consuming services14:17
tmorinigordc: yes, I'll be in Denver14:17
igordcI say we can still do a good deal of the work via the mailing list14:18
tmorinI can put it on my list and be there to talk CCF with whoever would like to14:18
igordcthe most important part is that the CCF provides the plugging points and supports the protocols/fields that consuming services want14:18
igordcI'll be on vacation but might join the etherpads just to follow and ask questions14:19
*** zhurong has quit IRC14:19
*** links has quit IRC14:20
reedip_I added FwaaS team, and I think xgerman or SridarK would be discussin the same with you. I will also ping yushiro for this14:20
davidshatmorin: If you could that would be great, as igordc mentioned it's the protocols services need and make sure the plug points work14:20
tmorinI can take the action of starting this discussion in Denver14:20
*** bcafarel has joined #openstack-meeting14:20
tmorinwe need to identify who of "consuming services" will be there14:21
reedip_I wont be there so I will check virtually14:21
davidshatmorin: Thanks.14:21
tmorinreedip_: so that would be these three and someone from fwaas ?14:21
reedip_all three are from fwaas tmorin14:21
davidshapcarver from SFC was heavily involved back in Atlanta if I remember correctly.14:22
igordcgreat tmorin thanks14:22
*** yamamoto has joined #openstack-meeting14:23
igordcdavidsha: yes, I don't see his name on the etherpad but he might go, I'll check with him on the sfc meeting14:23
igordcand hi reedip_14:23
reedip_hi igordc14:23
tmorinreedip_: ok!14:24
*** chenyb4_ has quit IRC14:24
igordccool if you all can please socialize the ccf, and write down all the missing gaps and proposed directions, that would be awesome... I'll try to check the etherpad and IRC14:25
*** _pewp_ has quit IRC14:26
davidshaI have seen the drivers propose the use of CCF for a few RFEs already, so I can try and find the RFE authors and sync with them.14:26
igordcawesome davidsha, that's great14:27
davidshaOne was for Security groups and the other may have been DragonFlow, I'll talk to mlavelle about it and see what they were planning.14:28
*** yamamoto has quit IRC14:28
igordcdavidsha: the dragonflow one was related to fwaas wasn't it?14:29
davidshaigordc: I can't recall off the top of my head.14:29
davidshatmorin: you mentioned at the PTG about using BGP resources as classifications to be consumed by SFC or am I mistaken?14:30
*** _pewp_ has joined #openstack-meeting14:30
tmorindavidsha: yes, but the good solution to the target problem may end up being different14:31
tmorinthe problem is : how to specify in some API that we want the traffic from a given BGPVPN and matching a given classifier, to be put into an SFC port chain14:31
*** VW has quit IRC14:31
tmorinhaving a "source BGPVPN" in the classifier could have been a solution, but we ended up concluding it was not a good one when discussing the CCF spec14:32
igordctmorin: as a source bgpvpn it looks OK to be put in a classification14:33
tmorinmy current thinking is that the best would be to extend the BGPVPN API to associate a (Common Flow Classifier ID, SFC port-chain ID) tuple to indicate that the traffic from this BGPVPN matching the classifier should go into the chain.14:33
*** markstur has joined #openstack-meeting14:33
igordctmorin: as a destination, not really14:33
*** alexchadin has quit IRC14:34
tmorinigordc: right for source vs. dest, but we (you, me, ihar) ended up concluding we should add that and rely instead on the consuming service API to combine a CCF with its own resources14:34
*** VW has joined #openstack-meeting14:34
*** eharney has quit IRC14:34
igordctmorin: OK so in your current thinking, bgpvpn's users would still use the CCF but no changes in SFC would be needed (only in bgpvpn)14:35
tmorinigordc: yes, and only the port-chain and CCF APIs would be used (not the current SFC classifier API, nor an extension of it)14:36
igordctmorin: the problem is that networking-sfc manages classifying the traffic... and port-chains require classifications14:36
*** VW has quit IRC14:37
*** VW has joined #openstack-meeting14:37
igordctmorin: this could be done, but look like a workaround from networking-sfc's perspective14:37
tmorin(for ref, the discussion I'm referring to was: https://review.openstack.org/#/c/333993/15/specs/pike/common-classification-framework.rst@319 )14:37
igordclet me just switch topic btw14:37
igordc#topic Open discussion14:38
*** openstack changes topic to "Open discussion (Meeting topic: network_common_flow_classifier)"14:38
tmorinigordc: ok, perhaps this needs more thinking14:38
*** markstur has quit IRC14:38
*** palexster has joined #openstack-meeting14:38
igordctmorin: I have to re-read the flow of arguments, including mine, but one thing is still clear I think: that the CCF doesn't actually classify14:39
igordctmorin: so either bgpvpn or sfc will14:39
*** tobiajo_ has quit IRC14:40
igordcwe then have the 2 options you mentioned today: sfc classifies based on 2+ classification types from the CCF (while bgpvpn only instantiates the bgpvpns)14:40
tmorinigordc: yes (to be exact in the case of bgpvpn, we delegate the actual classifiction of packet to BGP VPN routers thanks to BGP FlowSpec VPN routes)14:40
*** mtanino has joined #openstack-meeting14:40
igordcor sfc classification is bypassed and instead executed by bgpvpn (plus instantiating the bgpvpns and consuming from the CCF)14:41
tmoringiven the delegation mentioned above, the second option would be natural (I think)14:41
tmorinthe bgpvpn driver then simply needs to push the classified traffic to the ports of the first ingress port-pair14:42
igordctmorin: and you'd then be able to route the matching packets to the first SF of the port chain right?14:42
tmorinyes :)14:42
igordcI think this is a discussion between bgpvpn and sfc then14:43
igordcand from the conclusions we can know whether bgpvpn classication type is required14:44
tmorinthat makes sense14:44
*** bobmel has quit IRC14:44
igordcyour last option also looks better to my own subjective perception, but am just a bit concerned with the scope of networking-sfc then, seeing as the classification-part is bypassed14:45
davidshareedip_: you linked this before I think, this is the list of protocols for security groups correct? https://github.com/openstack/neutron-lib/blob/99d4f1f35f8d915f48bfaa677f690b29bc4b0dbe/neutron_lib/constants.py#L20214:46
reedip_davidsha : yep14:46
reedip_but I found that this is only for the iptables implementation14:46
reedip_But if we have nftables or any other implementation, then the protocol list might change, isnt it?14:47
igordcreedip_: not sure14:48
davidshareedip_: Well the backend doesn't really matter to us, it's just supporting the classification definitions that already exist in  Security Groups is what I'm thinking.14:48
igordcreedip_: do you know if SCTP is actually used in neutron?14:48
reedip_igordc : its in the neutron_lib/constants, right ?14:49
*** Guest57728 is now known as lhx__14:49
davidshaYup, It's there14:49
*** eharney has joined #openstack-meeting14:49
igordcreedip_: yes, but I don't see any actual use either there or in /neutron14:49
igordcreedip_: perhaps some stadium project14:49
igordcsame goes for DCCP14:49
*** markstur has joined #openstack-meeting14:50
reedip_well : https://github.com/openstack/neutron/blob/7c1e21a3f35e80e176dfc025eb6f4a0024cb137c/neutron/agent/linux/iptables_firewall.py#L64314:50
igordcreedip_: alright indirectly via IPTABLES_PROTOCOL_MAP14:50
reedip_yes ...14:50
igordcreedip_: but I still don't see protocol-specific work14:51
davidshaSo there are 22 in that list of protocols and we have 5 of them in Version 014:51
*** trevormc has joined #openstack-meeting14:51
igordcreedip_: at least for classification purposes14:52
reedip_igordc : I can only find the implementation and usage of the protocols in 5 places14:52
reedip_seems that it is only used in iptables_firewall.py14:52
igordcreedip_: yep got the same in github14:52
reedip_so unless we have a separate agent, iptables will work well with the following 5 protocols14:52
reedip_But yes, DCCP and SCTP wont be useful in generic terms14:53
reedip_so you can avoid it. Maybe you can keep a list of Necessary protocols and additional protocols14:53
reedip_the Necessary Protocols may have TCP, UDP , ICMP  ICMPv614:53
reedip_while the additional protocols can be dependent on the consumer of the CCF14:54
tmorinigordc: people are using protocols other than UDP or TCP out there, hence protos such as SCTP just need to be supported14:54
igordcright, I'd like to have more information about the need of certain protocols before anyone commits to work on their support in the CCF, otherwise we might just be wasting time14:54
igordcunless someone really wants to contribute those protocols, I'm fine with that14:54
*** VW_ has joined #openstack-meeting14:54
igordctmorin: but are they compatible with any neutron API extension?14:55
tmorinI know that at least SCTP is important for Telco NFV application related to the historic phone system (SS7)14:55
igordctmorin: or do they just have to be compatible with the backends that might be receiving, as an example, SCTP and DCCP traffic from VMs14:55
igordctmorin: ohh that :p14:56
tmorinigordc: I don't get your question14:56
tmorinigordc:  :D14:56
*** felipemonteiro_ has joined #openstack-meeting14:56
reedip_now I amm confused14:56
igordctmorin: in other words, are these protocols actually going to be object of a consumed Classification?14:56
*** felipemonteiro__ has joined #openstack-meeting14:57
tmorinyes, they can: for instance,  you could want to open only a given SCTP port range14:57
igordc+ reedip_14:57
igordcwe can continue offline, time's about to run out14:57
igordcI'd just like to introduce you to Thaynara , who's been co-authoring the code with David14:57
reedip_hi Thaynara14:58
reedip_saw the patch 0 version14:58
tmorinsimilarly: direct a given SCPT port range into a chain, apply QoS profiles distinctively depending on SCTP port, etc.14:58
ThaynaraHi guys14:58
tmorinhi !14:58
igordctmorin: I understand, do you know of any neutron project doing it?14:58
*** VW_ has quit IRC14:59
*** gouthamr has joined #openstack-meeting14:59
*** VW_ has joined #openstack-meeting14:59
igordcI am fortunate enough to hear daily discussions about the CCF from these 2 hehe14:59
*** VW has quit IRC14:59
tmorinI haven't checked14:59
reedip_FWaaS would be using it soon ... but otherswise not enough consumers14:59
igordcreedip_: hmm OK so some potential there15:00
igordcaright, time's up15:00
igordcbye all!15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Tue Aug 22 15:00:09 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-08-22-14.02.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-08-22-14.02.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-08-22-14.02.log.html15:00
reedip_Lets continue on the ML or #neutron ?15:00
tmorinbye everyone, thanks15:00
*** chyka has joined #openstack-meeting15:00
davidsha#neutron sounds good15:00
*** felipemonteiro_ has quit IRC15:01
*** ruijie has quit IRC15:02
*** Manuel_112 has quit IRC15:05
*** cody-somerville has joined #openstack-meeting15:06
*** cody-somerville has quit IRC15:06
*** cody-somerville has joined #openstack-meeting15:06
*** hoangcx_ has quit IRC15:07
*** jamesmcarthur has joined #openstack-meeting15:08
*** baoli has joined #openstack-meeting15:09
*** brault_ has quit IRC15:09
*** brault has joined #openstack-meeting15:09
*** trevormc has quit IRC15:10
*** gyee has joined #openstack-meeting15:11
*** felipemonteiro has quit IRC15:12
*** cdub has quit IRC15:13
*** rbartal has quit IRC15:13
*** baoli has quit IRC15:13
*** baoli has joined #openstack-meeting15:14
*** Thaynara has quit IRC15:15
*** rcernin has quit IRC15:15
*** yangyapeng has joined #openstack-meeting15:15
*** baoli has quit IRC15:18
*** kylek3h has quit IRC15:20
*** Apoorva has joined #openstack-meeting15:22
*** tmorin has quit IRC15:23
*** felipemonteiro has joined #openstack-meeting15:24
*** yamamoto has joined #openstack-meeting15:25
*** rderose has joined #openstack-meeting15:25
*** julim has quit IRC15:26
*** preisner has quit IRC15:26
*** julim has joined #openstack-meeting15:28
*** yamamoto has quit IRC15:30
*** jamesmcarthur has quit IRC15:32
*** bobmel has joined #openstack-meeting15:32
*** cdub has joined #openstack-meeting15:34
*** jamesmcarthur has joined #openstack-meeting15:34
*** jamesmcarthur has quit IRC15:35
*** jamesmcarthur has joined #openstack-meeting15:35
*** apetrich has joined #openstack-meeting15:38
*** kylek3h has joined #openstack-meeting15:39
*** VW_ has quit IRC15:39
*** csomerville has joined #openstack-meeting15:39
*** hemna_ has joined #openstack-meeting15:40
*** e0ne has quit IRC15:43
*** cody-somerville has quit IRC15:43
*** abhishekk has quit IRC15:45
*** jproulx has left #openstack-meeting15:53
*** belmoreira has quit IRC15:55
*** yangyapeng has quit IRC15:55
*** afanti has quit IRC15:55
*** thorst_afk has quit IRC15:55
*** yangyapeng has joined #openstack-meeting15:55
*** thorst_afk has joined #openstack-meeting15:57
*** manjeets has joined #openstack-meeting15:57
*** lpetrut has quit IRC15:59
*** yangyapeng has quit IRC15:59
*** jlibosva has joined #openstack-meeting16:00
*** ihrachys has joined #openstack-meeting16:00
ihrachys#startmeeting neutron_ci16:00
openstackMeeting started Tue Aug 22 16:00:27 2017 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
ihrachysjlibosva, o/16:00
ihrachys#topic Actions from prev week16:00
*** openstack changes topic to "Actions from prev week (Meeting topic: neutron_ci)"16:00
ihrachys"jlibosva to look through uncategorized/latest gate tempest failures (15% failure rate atm)"16:01
*** thorst_afk has quit IRC16:01
* jlibosva slacked, didn't happen16:01
ihrachysok, we will revisit whether it's still needed in Grafana section16:01
ihrachys"ihrachys to capture os.kill calls in func tests and see if any of those kill test threads"16:01
ihrachysI haven't done THAT but since last kernel update we don't see to see the failure16:02
ihrachysjlibosva, right?16:02
*** bollig has joined #openstack-meeting16:02
jlibosvaright, and also at the end of last meeting we confirmed it's kernel who kills the process16:02
ihrachysI haven't seen it personally for a week + grafana board is very clean16:02
jlibosvaI haven't checked via logstash16:03
jlibosvabut I'm able to reproduce that failure on my ubuntu box with the -83 kernel16:03
ihrachys-83, is it the old or new?16:03
jlibosvaI can update and confirm it not reproducible16:03
jlibosvaah, sorry. 83 is hte old one16:03
jlibosvaI think :)16:03
*** cloudrancher has quit IRC16:03
ihrachyslet's close https://bugs.launchpad.net/neutron/+bug/1707933 if/when it's confirmed (I personally feel ok doing it without additional step, but you decide)16:04
openstackLaunchpad bug 1707933 in neutron "functional tests timeout after a test worker killed" [Critical,Confirmed] - Assigned to Jakub Libosvar (libosvar)16:04
ihrachys"jlibosva to tweak gate not to create default subnetpool and enable test_convert_default_subnetpool_to_non_default"16:04
*** donghao has joined #openstack-meeting16:04
*** tesseract has quit IRC16:04
jlibosvadidn't do either :(16:04
*** reedip_ has quit IRC16:04
*** cloudrancher has joined #openstack-meeting16:04
ihrachys#action jlibosva to tweak gate not to create default subnetpool and enable test_convert_default_subnetpool_to_non_default16:05
*** thorst_afk has joined #openstack-meeting16:05
ihrachys#topic Grafana16:05
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:05
*** Manuel_112 has joined #openstack-meeting16:06
ihrachysof gating jobs, the only one that stands out is gate-grenade-dsvm-neutron-multinode-ubuntu-xenial16:07
ihrachysnot a catastrophe, ~10%16:07
ihrachysapart from that, usual check queue violators - fullstack and scenarios - are at 100%16:08
ihrachysfor fullstack, I still suck16:08
ihrachysfor scenarios, I believe jlibosva tried to gather troops to triage/fix remaining known failures16:09
ihrachysjlibosva, was there success in that?16:09
jlibosvaAnil is looking at the router migration tests - but no outcome yet16:09
ihrachysI also see dvr-ha job failing at 100%. I don't think that was the case a while ago.16:10
*** Manuel_112 has quit IRC16:10
ihrachyswe may need Brian back to have a look at it closer16:11
ihrachyshe was working on making it voting16:12
anilvenkatajlibosva, ihrachys migration tests are failing intermittently16:12
anilvenkatajlibosva, ihrachys If consistently failing then it would be easier to fix16:12
jlibosvaanilvenkata: are you able to reproduce it?16:12
ihrachysanilvenkata, ok. any ideas how can we make them not fail? what's missing to understand what happens there?16:12
anilvenkatamay be I need to add more checks before the test try to ssh16:13
anilvenkatachecks like HA port is active, etc16:13
anilvenkatathat will make sure the dataplane path is properly configured, before the test try to ssh16:14
ihrachysyeah. another thing to look at would be, whether any helpful info is missing in agent logs.16:14
anilvenkataI Will also look at that16:15
anilvenkatathanks Ihar16:15
ihrachys#topic anilvenkata to add more control plane checks for migrated router ports tests before ssh'ing16:15
*** openstack changes topic to "anilvenkata to add more control plane checks for migrated router ports tests before ssh'ing (Meeting topic: neutron_ci)"16:15
openstackRemoving item from minutes: #topic anilvenkata to add more control plane checks for migrated router ports tests before ssh'ing16:15
ihrachys#action anilvenkata to add more control plane checks for migrated router ports tests before ssh'ing16:15
*** iyamahat has quit IRC16:15
*** yamahata has quit IRC16:16
ihrachysI also noticed today that we still keep linuxbridge grenade job in dashboard even though it's experimental now16:17
ihrachyspatch to remove it from there: https://review.openstack.org/#/c/496287/16:17
ihrachysjlibosva, back to the earlier action item you had, it doesn't seem it's a pressing need right now to classify tempest failures.16:17
ihrachys#topic Bugs16:18
*** openstack changes topic to "Bugs (Meeting topic: neutron_ci)"16:18
ihrachysI started cleaning up the list: https://bugs.launchpad.net/neutron/+bugs?field.tag=gate-failure16:18
ihrachysclosed a bunch of those that no longer reproduce / no logs16:18
ihrachyswe can reopen if they happen again16:18
openstackLaunchpad bug 1687709 in neutron "fullstack: ovs-agents remove trunk bridges that don't belong to them" [High,Confirmed] - Assigned to Jakub Libosvar (libosvar)16:19
ihrachysjlibosva, is it correct that ovs isolation work should help with that?16:19
jlibosvaI'm gonna close the functional killer bug, no hits in last week16:19
ihrachysjlibosva, yep, go for it16:19
jlibosvaihrachys: yes, that's still something I'd like to implement but can't find spare time16:19
ihrachysjlibosva, is everything ready on ovsdbapp side for that?16:20
jlibosvamy plan is not to use the sandbox ovs, so ovsdbapp is no longer a requirement16:20
jlibosvathe isolation will use normal ovsdb-server process running in namespace instead16:20
jlibosvaas we need an actual access to kernel datapath, which sandbox mocks16:21
ihrachysoh ok16:21
ihrachysI haven't walked through all bugs yet; I am going to continue cleaning up the gate-failure list this week16:22
ihrachys#action ihrachys to complete gate-failure cleanup16:22
openstackLaunchpad bug 1712278 in neutron "Default qos policy doesn't work when creating network" [High,In progress] - Assigned to Hirofumi Ichihara (ichihara-hirofumi)16:23
ihrachyswe seem to have a patch here: https://review.openstack.org/#/c/496139/16:23
ihrachysI am not sure how it happened. don't we have test coverage for that?16:23
jlibosvaon higher level, maybe tempest or fullstack - but both are non-voting16:24
ihrachysoh right.16:25
*** vryzhenkin is now known as freerunner16:25
jlibosvahmm, actually api tests should be able to catch that16:25
ihrachysfor some reason, logstash shows osc functional test failures only16:26
*** yamamoto has joined #openstack-meeting16:26
jlibosvaand api tests don't test default qos policy16:27
jlibosvaonly fullstack16:27
ihrachysI don't see fullstack hits in logstash16:28
jlibosvado we collect server logs for fullstack?16:28
ihrachysoh; we probably collect but don't index16:29
ihrachyswe index test runner logs only16:29
ihrachysthat explains then16:29
ihrachyswould probably make sense to ask to add api tests to the fix16:29
ihrachysoh you did already16:30
jlibosvayeah :)16:30
jlibosvaalso looking at the post-gate hook, if I understand the find correctly, we should index also the server and agent logs16:30
*** lpetrut has joined #openstack-meeting16:30
jlibosvafor fullstack16:30
*** ociuhandu has quit IRC16:31
ihrachyshm, right. so which test do you think covers the functionality?16:32
jlibosvayep, so maybe it doesn't hit that specific16:32
*** yamamoto has quit IRC16:32
ihrachysoh I see TestQoSPolicyIsDefault16:32
jlibosvaI checked the index file and server and agents are included16:32
jlibosvaihrachys++ :)16:32
*** Apoorva has quit IRC16:33
jlibosvaso we probably don't create a network after we have the default policy16:33
ihrachysI don't think we create a network using default policy in any of those test cases16:33
*** Apoorva has joined #openstack-meeting16:34
ihrachysok, that makes sense16:34
ihrachys#topic Other patches16:34
*** openstack changes topic to "Other patches (Meeting topic: neutron_ci)"16:34
ihrachysjlibosva, anything of interest not mentioned already?16:35
*** iyamahat has joined #openstack-meeting16:35
jlibosvajust that if you look at functional gate failures in the last 7 days, it draws a batman :)16:35
jlibosvanothing else from me16:35
*** yamahata has joined #openstack-meeting16:36
ihrachysok, I will note that I noticed some time ago that grenade failures don't always trigger corresponding elastic patterns, and I think I came up with the fix here: https://review.openstack.org/#/c/493987/16:36
ihrachyselastic bot doesn't wait for all service logs to upload if it's grenade16:37
*** pcaruana has quit IRC16:37
ihrachysI have nothing else16:37
jlibosvaoh, one more thing I have16:37
jlibosvaI noticed that bot now reports elastic rechecks at the upstream channel :) it was discussed in this meeting a while ago16:37
ihrachysyeah. it doesn't seem very consistent though, I failed to grasp when it does and when it doesn't16:38
*** Apoorva has quit IRC16:38
ihrachys(same feeling I have for gerrit comments from the bot)16:38
ihrachysok, we can close the session I guess16:39
ihrachysthanks jlibosva16:39
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:39
openstackMeeting ended Tue Aug 22 16:39:09 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:39
*** jlibosva has left #openstack-meeting16:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-08-22-16.00.html16:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-08-22-16.00.txt16:39
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-08-22-16.00.log.html16:39
*** davidsha has quit IRC16:39
*** cdub has quit IRC16:40
*** rbowen has quit IRC16:40
*** rbowen has joined #openstack-meeting16:41
*** julim has quit IRC16:42
*** toscalix has quit IRC16:50
*** lhx__ has quit IRC16:51
*** JudeC has joined #openstack-meeting16:56
*** abalutoiu has joined #openstack-meeting16:56
*** felipemonteiro__ has quit IRC16:58
*** VW has joined #openstack-meeting17:04
*** VW has quit IRC17:04
*** VW has joined #openstack-meeting17:06
*** Manuel_112 has joined #openstack-meeting17:07
*** apetrich has quit IRC17:11
*** Manuel_112 has quit IRC17:11
*** electrofelix has quit IRC17:12
*** thorst_afk has quit IRC17:13
*** cloudrancher has quit IRC17:13
*** apetrich has joined #openstack-meeting17:14
*** cloudrancher has joined #openstack-meeting17:14
*** lpetrut has quit IRC17:18
*** lpetrut has joined #openstack-meeting17:19
*** unicell has joined #openstack-meeting17:19
*** sambetts is now known as sambetts|afk17:22
*** Swami has joined #openstack-meeting17:23
*** anilvenkata has quit IRC17:23
*** diablo_rojo has joined #openstack-meeting17:23
*** Swami has quit IRC17:23
*** Swami has joined #openstack-meeting17:24
*** abalutoiu has quit IRC17:25
*** yamamoto has joined #openstack-meeting17:28
*** donghao has quit IRC17:33
*** yamamoto has quit IRC17:35
*** baojg has quit IRC17:37
*** julim has joined #openstack-meeting17:37
*** baojg has joined #openstack-meeting17:38
*** coolsvap has quit IRC17:45
*** spilla has joined #openstack-meeting17:45
*** spilla has quit IRC17:45
*** jamesmcarthur has quit IRC17:45
*** spilla has joined #openstack-meeting17:46
*** jamesmcarthur has joined #openstack-meeting17:46
*** cdub has joined #openstack-meeting17:47
*** thorst_afk has joined #openstack-meeting17:49
*** jamesmcarthur has quit IRC17:50
*** cdub has quit IRC17:55
*** cdub has joined #openstack-meeting17:56
*** yangyapeng has joined #openstack-meeting17:56
*** rmascena is now known as raildo17:58
*** sjain_ has joined #openstack-meeting17:58
*** gagehugo has joined #openstack-meeting17:58
*** rha has joined #openstack-meeting17:59
lbragstad#startmeeting keystone18:00
openstackMeeting started Tue Aug 22 18:00:16 2017 UTC and is due to finish in 60 minutes.  The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
lbragstadping ayoung, breton, cmurphy, dstanek, edmondsw, gagehugo, henrynash, hrybacki, knikolla, lamt, lbragstad, lwanderley, notmorgan, rderose, rodrigods, samueldmq, spilla, aselius, dpar18:00
*** openstack changes topic to " (Meeting topic: keystone)"18:00
openstackThe meeting name has been set to 'keystone'18:00
lbragstad#link https://etherpad.openstack.org/p/keystone-weekly-meeting18:00
lbragstadagenda ^18:00
*** JudeC has quit IRC18:01
*** yangyapeng has quit IRC18:01
*** bobmel has quit IRC18:01
lbragstadok - let's get started18:01
lbragstad#topic announcements18:01
*** openstack changes topic to "announcements (Meeting topic: keystone)"18:01
lbragstadkinda of a fire going on today18:01
lbragstadi was going through our release notes for pike today and notices a bunch of old release notes were rendering18:02
lbragstad#link https://docs.openstack.org/releasenotes/keystone/pike.html18:02
lbragstadstuff that was fixed in ocata or newton18:02
lbragstadturns out release notes are generated based on when they are touched18:02
kmalloclbragstad: +2/a on the last one18:02
lbragstadand we had a change come through to update a bunch of the release notes to point to the right documentation after the great docs migration18:03
lbragstadkmalloc: thnaks18:03
lbragstadso - after talking to the release team - we have a couple action itmes18:03
samueldmqlbragstad: aha, it'd useful to have a release: pike thing in the rns18:03
lbragstadwhich will result in us having to cut an rc318:03
lbragstad1.) we need to backport all doc patches to release notes to affected branches18:04
lbragstadthose patches can be found here18:04
lbragstad#link https://review.openstack.org/#/q/topic:bug/171057218:04
lbragstad2.) update any false positives in the current release notes18:05
lbragstadso - stuff like this18:05
lbragstad#link https://review.openstack.org/#/c/496322/18:05
*** cdub has quit IRC18:05
lbragstadgagehugo: has a patch on the way to fix another one18:05
lbragstad#link https://review.openstack.org/#/c/496342/18:05
lbragstadactually - it's right there ^18:05
lbragstadin addition to that - reno provides a way to blacklist specific release notes from rendering for a release18:06
lbragstadvery similar to what horizon did here - https://github.com/openstack/horizon/commit/85fe8f3b5fdf526302831107aee0c372ac5a9fec18:06
lbragstadI have a patch up that addresses this for pike18:06
lbragstad#link https://review.openstack.org/#/c/496343/18:07
lbragstadlooks like everything is approved - so i'll monitor the gate until they merge18:07
*** Manuel_112 has joined #openstack-meeting18:07
*** eharney has quit IRC18:07
lbragstadif anyone notices something wrong in our release notes between now and then, please let me know18:08
edmondswgood catch18:08
lbragstadwe might also need patches similar to https://review.openstack.org/#/c/496343/ for stable/ocata18:08
lbragstadmaybe just double checking that https://docs.openstack.org/releasenotes/keystone/ocata.html is accurate18:08
*** jamesmcarthur has joined #openstack-meeting18:08
kmallocsolution: never touch/fix a release note from previous releases18:09
kmalloc(going forward)18:09
lbragstadkmalloc: yeah - this totally slipped the radar18:09
kmallocwe can't always keep links in shape, and knowing the limitation, we do our best but roll with it knowing 1yr out the docs don't matter18:09
kmallocso, policy: don't "update" reno once a release is cut.18:09
kmallocfollowing this round of "whelp, we're there" or we revert the changes18:10
kmallocfrom this round18:10
kmallocwhich is also valid18:10
lbragstadhowever we decide to handle it - we should document the process in out release notes docs18:10
* kmalloc votes for revert.18:10
kmallocand document no change-y going forward18:11
lbragstad#link https://docs.openstack.org/keystone/latest/contributor/release-notes.html18:11
kmallocespecially for ocata/newton18:11
kmallocpike... less of a concern since we're cutting rc3 anyway18:12
*** Manuel_112 has quit IRC18:12
samueldmqlbragstad: yes we definitely need to update that doc18:12
*** cdub has joined #openstack-meeting18:13
kmalloctl;dr lets halt the patches for Ocata/Newton and just revert18:13
lbragstadi noticed a couple other nits when parsing the release notes that i'll include in an update18:13
kmallocand with pike *either* revert or roll forward but policy fixed.18:13
samueldmqkmalloc: the patches that touched the rns?18:13
samueldmqdo they just make some corrections to the rns or something else?18:13
lbragstadwe also have to think about the backport process18:13
lbragstadif a fix needs to go to stable/pike and it has a release note18:14
samueldmqlbragstad: yeah, how is that included in the stable branch's RNs?18:14
samueldmqsince it's based on dates?18:14
kmalloclbragstad: i just switched the stable branch fixes for the links to a -218:15
lbragstadkmalloc: except for stable/pike, right?18:15
kmalloclbragstad: backport the release note.18:15
kmallocyeah stable pike is still +2/+A, but i would vote a revert over rolling forward18:15
lbragstadsamueldmq: release notes from stable are rendered from the stable/branch18:15
kmallocyou can backport a clean reno to stable as it will be redered sanely18:15
kmallocjust don't ever "update" a reno that has been released18:15
kmallocbasically don't change release notes once merged18:16
samueldmqlbragstad: I was wondering specifically the new RNs we backport18:16
kmallocif it hasn't been merged to a stable/* branch, it is fine to do so.18:16
kmallocit will render sanely18:16
samueldmqif they get included in stable/*18:16
kmallocon the next stable release18:16
knikollakmalloc: this one's for pike https://review.openstack.org/#/c/496323/18:16
lbragstadthat seems somewhat counter-intuitive to keep the release note in source control... but i don't have much of an alternative18:16
dhellmannkmalloc : no, don't change release notes anywhere other than the branch on which they apply.18:17
dhellmannkmalloc : changing it on the same branch works fine.18:17
kmallocdhellmann: except if the reno was originally in say ocata18:17
kmallocdon't change it in pike18:17
kmallocit will then render as a pike change in docs18:17
dhellmannkmalloc : right, change it in stable/ocata18:17
kmallocw/o a lot of extra work18:17
samueldmqdhellmann: aha, makes sense.18:17
samueldmqchange in stable/ocata18:17
samueldmqand leave it "unfixed" in master18:17
dhellmannchange the note in the branch where the note applies18:17
kmalloc"fixing links" is counter-intuative though18:18
*** JudeC has joined #openstack-meeting18:18
kmalloci'd vote don't bother fixing on stable/ocata unless the reno is really b0rked18:18
lbragstadi wonder if sorting release notes by dir would be more helpful?18:18
dhellmannthe real right way to fix those links would have been to set up redirects for them, rather than editing the old content18:18
kmallocnot for things like updated links18:18
*** pvaneck has joined #openstack-meeting18:18
*** thorst_a_ has joined #openstack-meeting18:18
lbragstaddhellmann: well - the redirects were in place18:18
kmallocdhellmann: welcome to bad doc migration with no redirects18:18
kmallocdhellmann: or so i understand18:18
dhellmannyou have in-tree redirects set up?18:19
kmalloclbragstad: ok so revert pike changes plz18:19
*** rmcall has joined #openstack-meeting18:19
kmallocdhellmann: no for things like o.o/developer -> o.o./keystone18:19
kmallocit wasn't docs in our tree18:19
lbragstaddhellmann: https://github.com/openstack/keystone/commit/77500b3615ae94ea45837f3fc0d503c8aadcc46218:19
kmallocit was external links18:19
lbragstadit was stuff like https://docs.openstack.org/developer/devstack/plugins.html -> https://docs.openstack.org/devstack/latest/plugins.html18:19
dhellmannok. that would have meant updating the docs in the devstack repo18:20
*** thorst_afk has quit IRC18:20
kmallocagain not in our tree18:20
lbragstadwhich does make sense because the old link drops you at the wrong spot with the redirect18:20
kmallocso, lbragstad revert pike18:20
lbragstadkmalloc: well - my previous statment is true for some links in our tree too18:20
lbragstadlet me find another example that applies to keystone18:20
kmallocif it's 100% in our tree, what dhellmann pointed out for the .htaccess is fine, right?18:21
kmalloci was looking strictly at the external links18:21
dhellmannyeah, if it's in a different repo the redirects need to be set up over there, but the process is the same18:21
*** Apoorva has joined #openstack-meeting18:21
lbragstadso we need a redirect for https://docs.openstack.org/developer/keystone/event_notifications.html18:22
lbragstadto https://docs.openstack.org/keystone/latest/advanced-topics/event_notifications.html18:22
kmalloclbragstad: ok i've swapped everything to -2 except the link for the pike-specific bug18:22
dhellmannthe global htaccess file would redirect https://docs.openstack.org/developer/keystone/event_notifications.html to https://docs.openstack.org/keystone/latest/event_notifications.html18:23
dhellmannso you need in the keystone tree a redirect from that 2nd url to the real new location18:23
*** eharney has joined #openstack-meeting18:23
kmallochttps://review.openstack.org/#/c/496322/1/releasenotes/notes/bug_1698900-f195125bf341d887.yaml is the only one not -2 now18:23
kmallocthat one looks to be legitimately a pike thing18:23
lbragstadkmalloc: and the patch gagehugo has up18:24
kmallocwhich is from gagehugo18:24
lbragstadit was a by-hand revert that didn't catch the release note18:24
lbragstad#link https://review.openstack.org/#/c/496342/18:24
kmallocok cool that one is being left alone18:25
lbragstadalright - so it looks like i need to investigate the .htaccess change18:25
kmallocthough, if it was a revert of code...18:25
lbragstadand get that done sometime today18:25
kmallocwas the code across releases?18:25
lbragstadkmalloc: no18:25
kmallocif so, don't remove the release note, add a new one18:25
kmallocsaying the code was reverted18:25
lbragstadok - so to recap18:25
lbragstad#info don't modify release notes across releases18:26
kmallocdon't modify release notes once they are merged*18:26
lbragstad#action propose an .htaccess file for keystone doc redirects18:26
kmallocreally. just don't18:26
kmallocunless it is a within-release revert18:26
kmallocdhellmann: thanks for stepping in and helping18:26
lbragstad#action update release notes to reflect the outcomes and reasoning discussed in this meeting18:27
lbragstadand - we still need a new rc because of the following:18:27
samueldmqdhellmann: thanks18:27
lbragstad#link https://review.openstack.org/49634218:28
lbragstadand we need to revert #link https://github.com/openstack/keystone/commit/77500b3615ae94ea45837f3fc0d503c8aadcc46218:28
lbragstadin order to render release notes properly - right?18:29
lbragstador do we still need the patch that ignore specific release notes18:29
lbragstad#link https://review.openstack.org/#/c/496343/18:29
*** dmsimard has joined #openstack-meeting18:30
*** armstrong has joined #openstack-meeting18:30
*** bobh has quit IRC18:31
samueldmqfixing things for pike and reverting for other stable/ seems fine18:31
*** yamamoto has joined #openstack-meeting18:31
samueldmqI'm fine either way. reverting things in pike would work too18:31
*** Adri2000 has quit IRC18:31
dhellmannkmalloc, samueldmq: sure. let me know if you need help with reviews on those redirect patches18:31
kmallocsamueldmq: revert anything that isn't explicitly a pike bug in the pike release18:32
*** raildo has quit IRC18:32
kmalloci don't think anything landed, but if it did...18:32
*** raildo has joined #openstack-meeting18:32
lbragstaddhellmann: on last quick question - if we revert https://github.com/openstack/keystone/commit/77500b3615ae94ea45837f3fc0d503c8aadcc462 do we still need the ignore-notes patch https://review.openstack.org/#/c/496343/?18:33
*** Adri2000 has joined #openstack-meeting18:33
*** Adri2000 has quit IRC18:33
*** Adri2000 has joined #openstack-meeting18:33
*** cdub has quit IRC18:33
dhellmannlbragstad : I think unfortunately you will, because the file will still be "touched" in the master branch18:33
lbragstaddhellmann: ack - that's what i was curious about18:33
dhellmannyou might as well not revert, actually18:33
lbragstadlol - since we're two steps away :)18:33
*** cdub has joined #openstack-meeting18:34
lbragstadkmalloc: ^18:34
* kmalloc still is of the opinion revert.18:34
kmallocrevert should not make the file touched18:34
kmallocunless reno is looking at git history18:35
lbragstadwell - regardless of what we do - we're still going to need https://review.openstack.org/#/c/496343/18:35
kmallocwhich case i have other complaints.18:35
lbragstadwith or without the htaccess file18:35
kmallocbut that is not here or later.18:35
dhellmannkmalloc : yes, reno looks at the git history. It reads content out of the git commits, not from the files in the working tree.18:35
kmalloccan we just disable that and instead make it render based upon release note directory structure18:36
kmallocthat feels like it's being too clever18:36
dhellmannthere isn't a "disable" -- that's just how it works18:36
* lbragstad wondered that same thing a few months ago18:36
* kmalloc wants reno to stop being used in keystone then. but that aside. *sigh*18:36
lbragstadi think it was when stevemar was refactoring a bunch of the release notes for stable/newton18:36
lbragstadyeah - let me grab an example18:37
*** yamamoto has quit IRC18:37
kmallocpeople not understanding (me included) reno.18:37
kmallocand making bad decisions based on lack of understanding18:37
knikollareno really wants release notes to be immutable18:39
*** chyka has quit IRC18:39
dhellmannno, making them mutable was one of the design requirements18:39
lbragstad#link https://review.openstack.org/#/c/429179/18:39
lbragstad#link https://review.openstack.org/#/c/429143/18:40
knikollai see. across deliverables at least.18:40
lbragstad#link https://review.openstack.org/#/c/429145/18:40
lbragstad#link https://review.openstack.org/#/c/429177/18:40
*** sjain_ has quit IRC18:40
lbragstadstevemar: had a bunch of patches proposed to the stable branchs to cleanup release notes after we started establishing conventions18:40
dhellmannah, yeah18:40
dhellmannrenaming should work, too18:40
*** lin_yang has joined #openstack-meeting18:41
dhellmannwith the same caveat: do it on the branch where the note appears18:41
lbragstadi want to say the majority if that was a change to master that was attempted to be backported?18:42
lbragstadthey were massive changes, and no one really understood them18:42
*** slaweq has joined #openstack-meeting18:42
dhellmannah, yeah, so that would cause the same sort of issues18:42
lbragstador specifically - how reno would interpret them18:42
*** cdub has quit IRC18:43
dhellmannif you wanted to rename those, the way to do it would be to start with the oldest stable branch and rename the files there18:44
dhellmannthen forward port that patch to the next branch and rename any others18:44
dhellmannlather, rinse, repeat18:44
dhellmannhrm, no, not quite18:44
dhellmannyou wouldn't want to forward port18:44
*** diablo_rojo has quit IRC18:44
lbragstadi was gonna saw18:44
dhellmannyou'd want to rename the files in each branch that didn't exist in the older branches18:44
kmallocit feels like that is a case that reno doesn't handle well?18:45
*** slaweq has quit IRC18:45
dhellmannyes, it was not designed for a wholesale renaming18:45
lbragstadi started trying to think about how that would work and my ears started smoking18:45
dhellmannit was designed to let you fix broken things18:45
dhellmannbut "I don't like the naming convention we used" wasn't really on the list of potential breaks :-)18:45
lbragstadso - that's another point that once a release note merges - it shouldn't be updated18:45
lbragstaddhellmann: sure - that was something we came up with later18:46
*** sridharg has quit IRC18:46
kmalloci like the policy of just not updating release notes in tree once it merges18:46
lbragstadin the case - i'd be fine letting older branches bit rot18:46
dhellmannyou can safely make changes on the stable branch where the note applies, including editing the content, renaming the file, and even deleting the note18:46
kmallocas long as we're using reno in this case.18:46
*** markstur has quit IRC18:46
dhellmannbut you should probably minimize the amount you do it18:46
dhellmannconsider the fact that the source distribution won't include the update18:46
kmallocfair, but it would be much easier to just let people know to not change things.18:47
*** markstur has joined #openstack-meeting18:47
kmallocless headaches18:47
dhellmannwell, that's up to the keystone team to set as a policy18:47
kmallocsource distribution and otherwise18:47
lbragstadso - if a patch merges in master (which is under pike development) we have up to the release of pike to make changes without messing this up18:47
kmallocwas speaking for us18:47
kmallocnot openstack as a whole ;)18:47
dhellmannlbragstad : and after the stable/pike branch is created, you can continue to update the file on that branch safely18:47
dhellmannbut yeah, if you want a simple rule, just don't change things :-)18:47
kmalloci like the simple rule18:47
lbragstadman - thinking about writing patches to stable branches without backporting to master feels weird :)18:48
lbragstadbackporting from master*18:48
lbragstadok - so it sounds like we have to document this process18:49
lbragstadi can do that18:49
lbragstadthen we're going to revert https://github.com/openstack/keystone/commit/77500b3615ae94ea45837f3fc0d503c8aadcc46218:49
dhellmannlbragstad : https://review.openstack.org/#/c/496318/18:49
lbragstaddhellmann: oh - nice18:49
lbragstadkmalloc: and we'll still need https://review.openstack.org/#/c/496343/ based on how reno works, at least for this release because of the doc migration18:50
lbragstads/because of the doc migration//18:50
gagehugoshould I abandon https://review.openstack.org/#/c/496342/ then?18:51
*** markstur has quit IRC18:51
lbragstadwell - that should still go into master i think18:51
lbragstadbecause it was missed in a previous revert18:51
lbragstadbut we also need to remove it from stable/pike *or* ignore it18:52
lbragstadsince the release note is advertising false information18:52
lbragstad(since the patch was reverted)18:52
*** amotoki has quit IRC18:53
kmallocdelete sounds like it always works18:53
*** diablo_rojo has joined #openstack-meeting18:55
knikollalbragstad: should we exclude this specific file from the revert? it's not a release note https://review.openstack.org/#/c/496367/1/devstack/plugin.sh18:55
lbragstadknikolla: yeah - let's update that separately though?18:55
knikollalbragstad: ok, ++18:56
lbragstad#link https://review.openstack.org/#/c/496367/1 reverts the links18:56
lbragstaddoes anyone have any questions?18:56
lbragstadabout the process or what we need to do for rc3?18:57
cmurphyare there any patches that non-stable-cores can help with atm?18:57
*** Shrews has joined #openstack-meeting18:57
*** yangyapeng has joined #openstack-meeting18:57
lbragstadwe need to document things so we don't end up here again :)18:57
knikollalbragstad: this needs to go to master too right?18:58
lbragstadknikolla: what needs to go to master?18:58
knikollaerrr.. copy pasta fail. https://review.openstack.org/#/c/496343/18:58
lbragstadknikolla: according to dhellmann it should go directly to pike18:59
lbragstadsorry for burning the whole hour here18:59
*** trandles has joined #openstack-meeting19:00
lbragstadhead to #openstack-keystone and we can continue there19:00
lbragstadthanks all19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Aug 22 19:00:16 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-08-22-18.00.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-08-22-18.00.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-08-22-18.00.log.html19:00
clarkbanyone here for the infra meeting?19:00
* jeblair eats sandwich19:00
*** spilla has left #openstack-meeting19:01
clarkbI think fungi mentioned he was doing post eclipse traveling and isn't around today19:01
jeblairwe live in a post-eclipse world19:01
*** bobmel has joined #openstack-meeting19:01
* clarkb waits another minute or two before starting.19:02
*** yangyapeng has quit IRC19:02
*** VW_ has joined #openstack-meeting19:02
clarkb#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:03
clarkber derp19:03
clarkb#startmeeting infra19:03
openstackMeeting started Tue Aug 22 19:03:42 2017 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: infra)"19:03
openstackThe meeting name has been set to 'infra'19:03
clarkb#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:03
clarkb#topic Announcements19:04
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:04
clarkbPTG is quickly approaching.19:04
*** VW_ has quit IRC19:04
*** VW_ has joined #openstack-meeting19:04
*** markstur has joined #openstack-meeting19:04
*** gagehugo has left #openstack-meeting19:04
clarkbPike is right in the middle of release fun as release candidates come out and all that (so we should be careful to be slushy and avoid breaking things)19:05
clarkbThat is all I had. Anyone have anything to add?19:05
*** VW has quit IRC19:05
ianwclarkb: just that mirror nodes should be Xenial now, so if anyone has issues we're not aware of, let us know19:06
clarkbya I've added that to general discussion so that we can talk about it a bit more19:06
clarkb#topic Actions from last meeting19:06
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:06
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-08-15-19.03.txt Minutes from last meeting19:06
clarkbianw: I'm guessing that mirror update hasn't been updated to xenial yet. Have you heard from the release team on whether or not we can move forward on that?19:07
*** Manuel_112 has joined #openstack-meeting19:08
clarkbI completely failed to send the gerrit upgrade email last week so shoudl get that done nowish. And I haven't seen word of infracloud switchport counts19:08
clarkb#action fungi get switchport counts for infra-cloud19:08
clarkb#action clarkb send reminder of Gerrit upgrade after the PTG to the dev mailing list19:09
ianwi also completely failed on that, sorry19:09
clarkb#action ianw upgrade mirror-update server and bandersnatch19:09
clarkbthat is all we had from last meeting. So moving on19:10
clarkb#topic Specs approval19:10
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:10
clarkb#link https://review.openstack.org/#/c/462207/ is an update to the zuulv3 spec around zuul's handling of ssh keys19:10
clarkbjeblair: SpamapS ^ is that generally ready for approval?19:10
jeblairclarkb: yes, sorry!19:11
clarkbI think we may also want to add in the way we switch out the ifnra key for the job key?19:11
clarkbaiui pre playbook removes infra key from agent and adds in a per job key? Not sure if you want that to be a separate spec update though. In any case I think getting that updated as necessary would be good19:12
jeblairclarkb: we could -- though that's already implemented so we don't really need to drive consensus on it.  may be better to find a good place to document that for posterity.19:12
jeblairmaybe expand our base job documentation19:12
clarkbThe other spec I wanted to bring up was mentioned last week.19:13
clarkb#link https://review.openstack.org/#/c/492287/ mark gerrit contact store spec as completed19:13
clarkbIt has a couple depends on that could use reviews from infra-roots19:13
*** Manuel_112 has quit IRC19:13
clarkbbasically all cleanup at this point, pretty straightforward.19:14
clarkbAre there any other specs that we should bring up today?19:14
clarkbsounds like not. Would be great to get 462207 reviewed and I expect that fungi will merge that when he gets back (I don't have approval bits in that repo yet). And reviews to finish up the contact store priority effort much appreciated as well19:16
clarkb#topic Priority Efforts19:16
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:16
*** raildo has quit IRC19:16
clarkbI don't think there is much else to add on the gerrit upgrade or contact store front.19:16
*** slaweq has joined #openstack-meeting19:16
clarkbjeblair: anything from zuulv3?19:17
jeblairnope, still chugging along19:17
*** rbowen has quit IRC19:17
clarkb#topic General topics19:18
*** openstack changes topic to "General topics (Meeting topic: infra)"19:18
clarkbOne of the big things that happened last week was we upgraded our region local mirror instances to xenial from trusty in an effort to get more reliable http servers and afs19:18
clarkbWe weren't sure if it would fix all the problems but ianw pointed out debugging a current lts is far more beneficial than the last one19:19
pabelangerYa, switching to xenial has been an improvement from what I see19:19
pabelangeralso the patch for htcacheclean 4096 directories is also working great19:19
ianwclarkb: only one in the list still is OVS, is that ready?19:19
clarkbyup I agree. Though I did notice that yesterday we had 4 cases of pip hash mismatches in rax-dfw all within a minute of each other so I think we may still have some minor issues around afs (assuming it was an afs problem in the first place)19:20
ianw"the list" being https://etherpad.openstack.org/p/mirror-xenial for reference19:20
clarkb#link http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22THESE%20PACKAGES%20DO%20NOT%20MATCH%20THE%20HASHES%20FROM%20THE%20REQUIREMENTS%20FILE.%5C%22%20AND%20tags:%5C%22console%5C%22%20AND%20voting:1&from=864000s for query on pip hash mismatch19:20
clarkb#link https://etherpad.openstack.org/p/mirror-xenial for finishing up mirror upgrades19:20
*** bobmel_ has joined #openstack-meeting19:20
clarkbianw: I didn't really want to touch them until we got the account situation sorted out there just to avoid potentially causing more problems19:21
ianwhmm, i'll look into that, because a cluster is consistent with the segfaults we saw19:21
pabelangerianw: clarkb: the ttl for proxypass also seems to be an improvement for 502 proxy errors. I haven't see any issues from buildlogs.centos.org today19:21
cmurphyhmm i noticed that pycrypto doesn't build properly when using the mirrors, possibly related to the mirror update? https://review.openstack.org/#/c/496027/119:21
ianwcmurphy: hmm, that shouldn't be different ...looking19:22
clarkbpabelanger: that is good to know thanks.19:22
clarkbjeblair: you haven't heard anything back from jean daniel have you? Checking my email I don't have anything19:23
*** diablo_rojo has quit IRC19:23
cmurphyianw: those tests try and fail to install gerritbot which fails building pycrypto, but it seems to work fine on the same vm without the pip.conf changes19:23
*** bobmel has quit IRC19:23
jeblairclarkb: negative19:24
mordredwhoops. /me waves19:24
ianwcmurphy: that seems to be a problem with the host side, rather than the mirror side?19:24
clarkb#action clarkb follow up on ovh account situation and make sure mirrors get rebuilt there as xenial19:25
ianwcmurphy: ill comment19:25
clarkbI'll go ahead and try to track that down now that we expect people to be back from vacation aiui19:25
clarkbThe other bigish thing that happened recently was we no longer allow glean to update dns resolvers based on dhcp content in our images19:26
clarkbwe were having dns resolution problems in clouds like rax and it turned out we weren't using our local unbound install, we were hitting the cloud resolvers instead19:26
pabelangerYes! That has helped bigtime for centos19:26
clarkbpabelanger did a bunch of work in glean to fix that.19:26
pabelangernow that we are using unbound, DNS failures are basically gone19:26
clarkbexcept for on suse where we now have the problem of using unbound :)19:27
clarkb#link https://review.openstack.org/#/c/496310/ should fix unbound for suse if people can review that today19:27
Shrewsgit branch19:27
clarkb#link https://review.openstack.org/#/c/496341/1 is alternate suse fix19:27
Shrewsoops. sorry19:27
clarkbthere ended up being two changes pushed for that, if we prefer one more than the other I will be sure to abandoned the second one19:27
pabelangerk, I'll look at suse fixes after meeting19:28
clarkbOverall I think these changes are doing quite a bit to make test jobs more reliable so thank you to everyone that helped get them in place19:28
pabelangerYa, tripleo gate pipeline hasn't reset in 24 hours now19:29
clarkbThe last item I had for general discussion was something that happened this morning. nose-html-output is still in use by a couple projects (horizon and swift I think?) Its basically unsupported by us due nose being highly discouraged as a test runner and lack of subunit. As a result I have added amotoki to the core list as they have an interest in keeping the tool running at least for the short19:30
clarkbif there are other individuals interested in supporting that project I think we should just go ahead and add them to the core group19:30
clarkb(good news is sounds like there will be new investigation of getting horizon to emit subunit so yay)19:30
*** raildo has joined #openstack-meeting19:31
clarkb#topic Open discussion19:31
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:31
clarkbAnything else?19:32
ianwanyone mind if i get to a bindep release today?19:32
*** rbowen has joined #openstack-meeting19:32
ianwthere's some rpm changes that will be helpful for testing python3.619:32
pabelangercan we remove fedora-25 DIB?19:32
clarkbre bindep any concern about that affecting the release? IIRC the unittest are pretty robust since its basically just a language parser so probably fine19:33
pabelangeralso, somebody asked if we could remove debian-jessie too. Since openstack-deb team is getting disbanded19:33
ianwpabelanger: not quite, but i can do some cleanup today to get us there.  fedora-26 is ok with devstack now19:33
*** yamamoto has joined #openstack-meeting19:33
clarkbpabelanger: ya I had asked about debian but fungi pointed out projects like dib are using the image so I think we can keep it around19:33
dmsimardFor open discussion, just wanted to mention I officially got the green light from Red Hat to spend time on upstream/infra and help you guys out. My first work item is to improve devstack-gate bash/ansible things.19:34
ianwclarkb: i think, looking at the changes, low risk, mostly just the changes to add "--whatprovides" to rpm calls19:34
cmurphyi have a mass approval request if anyone wants some internet points https://review.openstack.org/#/q/status:open+topic:refactor-infra-beaker the idea is to hopefully reduce the need for mass updates19:34
pabelangerk, the reason I ask, is we only have 100Mbps link on nb03.o.o, so it does take some time for new images to upload.19:34
pabelangerrackspace is crazy fast, like 30mins to upload 80GB19:34
ianwi don't think dib is testing on debian19:34
jeblairdmsimard: yay!  thanks!19:34
*** cloudrancher has quit IRC19:34
clarkbdmsimard: nice! and thank you19:34
pabelangerdmsimard: ^519:35
clarkbianw: did that change to add the output of all deps get merged? I +2'd it but I think the submitter would like it if it was in the next release19:35
*** cloudrancher has joined #openstack-meeting19:35
clarkbit did merge so thats good19:35
clarkb#link https://review.openstack.org/#/q/status:open+topic:refactor-infra-beaker mass approval revuest to reduce the need for mass updates19:36
*** pchavva has quit IRC19:36
ianwclarkb: https://review.openstack.org/#/c/492693/ ? yep19:36
clarkbianw: ya19:36
ianwthe only outstanding changes are refactor ones ... bit iffy on code motion without other reasons for it19:37
clarkbpabelanger: probably the next step is do a job listing for the debian image and see if its just our bindep fallback test and the debian packaging jobs19:37
*** VW_ has quit IRC19:38
pabelangerclarkb: agree19:38
*** yamamoto has quit IRC19:38
*** VW has joined #openstack-meeting19:38
clarkbcmurphy: I'll try to review that after lunch19:39
cmurphyty clarkb19:39
clarkbfor those of us going to the ptg is there interest in trying to have a team dinner again? anyone interested in lining that up?19:41
clarkbthat might be better off as a ml thread19:42
clarkbI'll give it to 19:45UTC before ending the meeting but beginning to sound like that is it19:43
*** rha has left #openstack-meeting19:44
*** rbowen has quit IRC19:44
clarkbok thank you everyone. You can find us in #openstack-infra if we missed anything or you remember something important19:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:45
openstackMeeting ended Tue Aug 22 19:45:32 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-08-22-19.03.html19:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-08-22-19.03.txt19:45
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-08-22-19.03.log.html19:45
*** Shrews has left #openstack-meeting19:46
*** chyka has joined #openstack-meeting19:50
*** armax has quit IRC19:52
*** jkilpatr has quit IRC19:55
*** e0ne has joined #openstack-meeting19:55
*** fnaval has quit IRC19:56
*** slaweq has quit IRC19:56
*** yangyapeng has joined #openstack-meeting19:58
*** VW has quit IRC20:01
*** rbowen has joined #openstack-meeting20:01
*** yangyapeng has quit IRC20:03
*** sshank has joined #openstack-meeting20:03
*** portdirect is now known as tintin20:03
*** tintin is now known as portdirect20:04
*** baojg has quit IRC20:09
*** baojg has joined #openstack-meeting20:09
*** Manuel_112 has joined #openstack-meeting20:10
*** Manuel_112 has quit IRC20:14
*** jprovazn has quit IRC20:14
*** dprince has quit IRC20:14
*** rderose has quit IRC20:14
*** jkilpatr has joined #openstack-meeting20:15
*** makowals_ has quit IRC20:16
*** e0ne has quit IRC20:18
*** fnaval has joined #openstack-meeting20:22
*** fnaval has quit IRC20:22
*** fnaval has joined #openstack-meeting20:23
*** igordc has quit IRC20:23
*** cschwede_ has quit IRC20:27
*** gouthamr has quit IRC20:29
*** claudiub has quit IRC20:30
*** rmcall has quit IRC20:30
*** rmcall has joined #openstack-meeting20:31
*** Douhet has quit IRC20:32
*** Douhet has joined #openstack-meeting20:32
*** psachin has quit IRC20:34
*** yamamoto has joined #openstack-meeting20:35
*** baojg has quit IRC20:38
*** yamamoto has quit IRC20:38
*** yamamoto has joined #openstack-meeting20:38
*** baojg has joined #openstack-meeting20:38
*** yamamoto has quit IRC20:39
*** jamesmcarthur has quit IRC20:41
*** slaweq has joined #openstack-meeting20:43
*** mikal has quit IRC20:44
*** makowals has joined #openstack-meeting20:44
*** jamesmcarthur has joined #openstack-meeting20:45
*** diablo_rojo has joined #openstack-meeting20:45
*** mikal has joined #openstack-meeting20:45
*** julim has quit IRC20:48
*** Apoorva_ has joined #openstack-meeting20:49
*** jamesmcarthur has quit IRC20:49
*** rcernin has joined #openstack-meeting20:50
*** abalutoiu has joined #openstack-meeting20:51
*** makowals has quit IRC20:52
*** Apoorva has quit IRC20:52
*** gouthamr has joined #openstack-meeting20:52
*** jamesmcarthur has joined #openstack-meeting20:53
*** jamesmcarthur has quit IRC20:54
*** jamesmcarthur has joined #openstack-meeting20:54
*** slaweq has quit IRC20:56
*** slaweq has joined #openstack-meeting20:58
*** yangyapeng has joined #openstack-meeting20:59
*** StefanPaetowJisc has joined #openstack-meeting20:59
*** martial has joined #openstack-meeting21:00
zioprotois the Scientific WG meeting here now ?21:00
martialhello zioproto, yes21:00
zioprotohi :)21:01
martial#startmeeting scientific_wg21:01
openstackMeeting started Tue Aug 22 21:01:18 2017 UTC and is due to finish in 60 minutes.  The chair is martial. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** priteau has quit IRC21:01
*** openstack changes topic to " (Meeting topic: scientific_wg)"21:01
openstackThe meeting name has been set to 'scientific_wg'21:01
martialHello everybody21:01
martialI hope everybody is doing fine21:01
StefanPaetowJiscBuonasera, @zioproto. ;-)21:01
*** eharney has quit IRC21:01
StefanPaetowJiscEvening folks!21:02
martialBlair and Stig are on well deserved vacations without internet :)21:02
StefanPaetowJisc*slackjawed* You mean someone actually managed to persuade them to go on holiday?21:02
martialI "blame" significant others21:03
martialHi Tim21:03
*** zz9pzza_ has joined #openstack-meeting21:03
martialso we have a short list of topics today, so we can add extra items at the end21:03
*** yangyapeng has quit IRC21:03
martialbut basically21:03
martial#topic Updated edition of the Scientific OpenStack book21:04
*** openstack changes topic to "Updated edition of the Scientific OpenStack book (Meeting topic: scientific_wg)"21:04
*** fnaval has quit IRC21:04
hogepodge#link https://etherpad.openstack.org/p/scientific-computing-book-update-201721:04
martialAnd it looks like Mr Hoge is here :)21:04
*** jmlowe has joined #openstack-meeting21:04
hogepodgeYes, new information from the last week, I'll update the etherpad21:04
*** armax has joined #openstack-meeting21:04
hogepodgeWe're switching format, so editing should be easier21:05
hogepodgeDiagrams need to be in AI format, we need an expert in that21:06
hogepodgeReminder that we're one month away from the HARD deadline of September 2221:06
hogepodgeAre there any updates from the content side?21:06
hogepodgeDo we need to schedule a meeting to organize that?21:06
*** slaweq has quit IRC21:06
martialwell Today's meeting was another call for volunteers21:07
martialbut you can see the list --so far-- at the bottom of the Etherpad21:07
trandlesWe should probably have a draft deadline in a couple weeks.  I hate getting feedback then having to rush to integrate it.21:07
jmloweI need to do the globus auth federation work before I can add the piece I said I would21:07
martialjim: we need to think of a hard deadline for review21:08
martialat least a week before21:08
martialjim: do you think this is possible?21:09
hogepodgecool :-D I'm playing very much a deadline enforcer role here.21:09
*** slaweq has joined #openstack-meeting21:09
jmloweMaybe, pushing it here21:09
StefanPaetowJiscWill try to get my hands on this...21:09
hogepodgeI'm happy to facilitate in any other way you can direct me to21:09
trandleshogepodge: just to clarify, Sept. 22 deadline means whatever Kathy has on Sept. 22 is set in stone?21:09
martialJim: we can help by doing iterative review21:10
*** yamamoto has joined #openstack-meeting21:10
martialstefan: please do21:10
jmloweput we actually need to get it done Sept. 15 to review21:10
martialHello Robert21:10
hogepodgeYeah, the real real deadline is the 29th, but I'm saying the 22nd to emphasize that it _has_ to be ready by the 29th, no exceptions whatsoever, so the 22nd for final copy editing.21:10
*** Manuel_112 has joined #openstack-meeting21:11
martialMr Hoge, if you think we need a phone conversation to discuss content with possible content publishers, I am sure we can accommodate this21:11
martialit is more a matter of getting volunteers for now21:12
*** Manuel_112 has quit IRC21:12
*** Manuel_112 has joined #openstack-meeting21:12
martialthe people present here today is mostly our regular team21:12
hogepodgemartial: ok21:12
*** makowals has joined #openstack-meeting21:13
martialcrowd ... I think if we want/need to outreach it, we should21:13
*** slaweq has quit IRC21:13
martialmaybe a post on the mailing list (although I believe it was done already)21:14
martialand maybe our friends here can reach out to some of their colleagues and get some content21:14
*** yamamoto has quit IRC21:15
martialwe do not have a hard deadline on pages I believe21:15
hogepodgemartial: probably a good idea, plus a good plan and assignment of content :-D21:15
StefanPaetowJiscI'll block out some of my calendar to do some of this...21:16
hogepodgeeven if it's just mostly a content refresh with a few new stories, that's good. Reflect the current state of the art in the sc community21:16
martialokay I will send an email to the mailing list to be safe21:16
*** mtanino has quit IRC21:16
rbuddeni will have updates for Bridges and our move to Ocata Ironic and local boot21:16
*** Manuel_112 has quit IRC21:17
rbuddennot sure if just a google doc is a good place for the content or if you want it directly in the etherpad21:17
rbuddenah, I see a google doc linked in the etherpad. i’ll check that out21:17
martialthanks Robert, I was just checking that21:17
martialRobert: are you listed at the bottom of the etherpad?21:18
martialstefan: thank you as well, we appreciate your help on this matter21:18
rbuddenyes, I’m in the updates section21:19
martialPierre: any update?21:19
martialrobert: thanks21:19
martialI think we also ought to work on a reviewer process21:19
martialie assign people to review content when it is ready to do so21:20
martialscratch "assign" ... "request" ?21:20
martialokay anything else on the book chapters to share?21:21
*** thorst_a_ has quit IRC21:21
martialMr Hoge, we can have a email conversation if that is useful to you21:22
martialseems like nothing, so I am going to move to the next topic21:22
martial#topic ORC Update and planning21:22
*** openstack changes topic to "ORC Update and planning (Meeting topic: scientific_wg)"21:22
martialSo I know Tim was at the last meeting, and so was I21:23
martialthe conversation is still ongoing and we are discussing the content at this point for presentations21:23
martialthere was a request for scientific content if at all possible21:23
*** thorst_afk has joined #openstack-meeting21:24
martialany idea/comment so far?21:24
*** rbowen has quit IRC21:24
trandlesmartial: are they encouraging remote presentations or just on-site?  I can't make it to Amsterdam, but I might be able to put something together (or find someone who will)21:24
martialboth are welcome21:25
jmloweYou want scientific work being done using openstack clouds?21:25
martialthey are also trying to build the working group effort21:25
martialand have created google group to start the communication21:25
*** awaugama has quit IRC21:26
martialthere next meeting will be collocated with the Sydney meeting21:26
trandlesjmlowe: scientific use cases for open research cloud iirc21:26
martialjim: actually ... (thansks Tim)21:26
jmlowewe have a pile of that21:26
trandlessomething that sounds a lot like jetstream ;)21:26
StefanPaetowJiscHmmm... Open Research Cloud, how is this related to the EOSC project in the EU?21:28
*** thorst_afk has quit IRC21:28
martialwell they are trying to built a global model with a lot of areas to cover ... more deails on the areas https://groups.google.com/a/openresearchcloud.org/forum/?pli=1#!forumsearch/21:28
StefanPaetowJiscAhh, was about to ask for the Google Group name ;-)21:28
jmloweok, yep, we did nearly a whole day of use cases for our annual review, should be able to recycle21:30
martialYou can contact Khalil or Enol21:30
*** lpetrut has quit IRC21:30
*** kbyrne has quit IRC21:30
martialEnol Fernández <enol.fernandez@egi.eu>21:30
jmloweI was profoundly unhappy with the meeting in Boston so I've been ignoring ORC21:30
martialK Yazdi <khalilyazdi@outlook.com>21:31
martialjim: it is still an effort in progress and I expect it to be for a litlte bit of time, until they get the momentum needed21:31
*** kbyrne has joined #openstack-meeting21:32
martialbut there are a few people from Industry in particular that are interested in helping build a model21:32
martialthere was also a conversation about there being a more technical meeting right before the ORC meeting21:32
martialand the briefs from that meeting being presented at the ORC one21:33
martialI expect we will get more content as the weeks progress21:34
zioprotomartial: you mean https://wiki.geant.org/display/CISS/1st+SIG-CISS+meeting ?21:34
martialyes thank you, I was looking for that21:35
martialso that is that for the ORC update for now21:36
StefanPaetowJiscAhhh... was not aware of the second congress... Will run this past my management to see if I can attend21:36
martialTim and Jim, if you have content to provide and are willing to do so, feel free to contact Enol or Khalil21:36
martial#topic Community Voting21:37
*** openstack changes topic to "Community Voting (Meeting topic: scientific_wg)"21:37
martialso I understand that the vote is completed (I voted)21:37
martialand unless I misread the results... congratulations Saverio21:37
*** makowals has quit IRC21:38
zioprotomartial: thanks !21:38
martialcan you tell us a litlte bit more about what it means, for you and the SWG?21:38
trandlesyeah, congrats zioproto !21:38
StefanPaetowJiscCongrats, Saverio! :-)21:39
zioprotoso I will be in the User Committee for a 1 year term21:39
zioprotoThe user committee is led by a core group five individuals, who provide oversight and guidance to a number of working groups that target specific areas for improvement.21:39
zioprotoIt is still a lot to learn also for me, I had my first meeting with those folks yesterday21:40
zioprotoThe user committee mission is to:21:40
zioprotoConsolidate user requirements and present these to the management board and technical committee21:41
zioprotoProvide guidance for the development teams where user feedback is requested21:41
zioprotoTrack OpenStack deployments and usage, helping to share user stories and experiences21:41
zioprotoWork with the user groups worldwide to keep the OpenStack community vibrant and informed21:41
zioprotoI have done some cut and paste from https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Working_Groups21:41
martialso when do you sleep in all that? :)21:42
zioprotoyes it is a lot of work :) Lets see :)21:42
martialIt looks to me that it will be a very rewarding position21:43
trandleszioproto: are there any changes with the User Committee and the new SIGs?21:43
zioprototrandles: I understood the User Committee is something that stays. The Working Groups (WG) are going to be replaces by SIGs in the long term. That is what I understood.21:44
trandlesok, good... :)21:45
zioprototrandles: User Committee is at the governance level https://governance.openstack.org/21:45
martialSaverio, this looks to me that you will have a lot of good opportunities to make a significant impact, congratulations21:47
zioprotoThanks. The experience running Openstack is that the gap between devs and operators is still big. I hope to make this gap smaller.21:48
martialIf we are okay, after we are done, I would like to give the floor to Tim21:48
martialSaverio: I look forward to your oversight and influence, Sir21:48
martialand now before AOB21:49
martial#topic SC1721:49
*** openstack changes topic to "SC17 (Meeting topic: scientific_wg)"21:49
martialsorry Jim21:49
jmloweI have the green light for a round of lightning talks in the IU booth just like last year21:49
jmloweso, probably time to gather volunteers and start planning21:50
martialthat is great news21:50
martialhow "lightning are we talking about"21:51
jmloweI'll have 1 to 1.5 hours, so divide by volunteers and...21:51
rbuddeni believe last year they were 10-15 min each?21:51
martialI am planning to be there, so I will be happy to contribute21:51
*** xyang1 has quit IRC21:51
rbuddeni’m happy to give a short lightning talk as well21:51
trandlescount me in if there's space21:52
jmloweexcellent, surely there's an etherpad somewhere for this?21:52
jmloweThat's two21:52
martialwe had one for SC17 did we not?21:52
martiallet me check the meeting notes21:52
jmloweIt was the best attended and best received thing at our booth last year, so well done21:53
hogepodgeWe're happy to help promote anything from SC21:53
jmloweWe are all set to distribute updated books as well21:53
hogepodgeIf you reach out to me I can be sure our marketing team tweets out  and blogs timely info21:53
jmloweI know PSC is in for books21:53
rbuddenI can still ask about booth space for talks if we have too many for one slot of want a second go around21:54
rbudden*or want*21:54
rbuddenw/e people would like21:54
jmloweok, marking you two down on the etherpad21:55
martialI know GWU is going to be at SC17, I was going to go talk to them early september21:55
martialjim: added myself as well21:56
martialJim: thank you very much for sharing this piece of information21:57
martialwell we are running close to the clock21:58
martial#topic AOB21:58
*** openstack changes topic to "AOB (Meeting topic: scientific_wg)"21:58
martialanything short that we need to discuss?21:58
zioprotothanks for the meeting ! see you guys in Amsterdam at SIG-CISS for who will be there :)21:59
*** JudeC has quit IRC21:59
*** zz9pzza_ has quit IRC21:59
StefanPaetowJiscI hope to be there (and actually be mentally present)21:59
StefanPaetowJiscSee ya!21:59
*** yangyapeng has joined #openstack-meeting21:59
martialif not, thank you kindly for coming. Once again congratulations to Saverio and Sorry tim/jim -> John21:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
openstackMeeting ended Tue Aug 22 22:00:22 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-08-22-21.01.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-08-22-21.01.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-08-22-21.01.log.html22:00
*** jamesmcarthur has quit IRC22:01
*** StefanPaetowJisc has quit IRC22:01
*** trandles has left #openstack-meeting22:02
*** thorst_afk has joined #openstack-meeting22:02
*** jamesmcarthur has joined #openstack-meeting22:03
*** yangyapeng has quit IRC22:04
*** thorst_afk has quit IRC22:06
*** thorst_afk has joined #openstack-meeting22:08
*** baojg has quit IRC22:11
*** martial has quit IRC22:11
*** yamamoto_ has joined #openstack-meeting22:11
*** baojg has joined #openstack-meeting22:12
*** Manuel_112 has joined #openstack-meeting22:13
*** hemna_ has quit IRC22:13
*** JudeC has joined #openstack-meeting22:14
*** abalutoiu has quit IRC22:14
*** yamamoto_ has quit IRC22:17
*** edmondsw has quit IRC22:17
*** thorst_afk has quit IRC22:18
*** Manuel_112 has quit IRC22:18
*** mtanino has joined #openstack-meeting22:18
*** thorst_afk has joined #openstack-meeting22:18
*** sshank has quit IRC22:19
*** baojg has quit IRC22:20
*** baojg has joined #openstack-meeting22:20
*** jmlowe has left #openstack-meeting22:22
*** marst has quit IRC22:22
*** thorst_afk has quit IRC22:22
*** baojg has quit IRC22:25
*** pabelanger has quit IRC22:25
*** pabelanger has joined #openstack-meeting22:25
*** baojg has joined #openstack-meeting22:25
*** sshank has joined #openstack-meeting22:27
*** baojg has quit IRC22:30
*** baojg has joined #openstack-meeting22:30
*** rcernin has quit IRC22:32
*** _pewp_ has quit IRC22:33
*** ykatabam has joined #openstack-meeting22:33
*** _pewp_ has joined #openstack-meeting22:38
*** diablo_rojo has quit IRC22:39
*** makowals has joined #openstack-meeting22:45
*** jamesmcarthur has quit IRC22:47
*** rbowen has joined #openstack-meeting22:48
*** makowals has quit IRC22:56
*** artom has quit IRC22:59
*** ykatabam has quit IRC23:00
*** yangyapeng has joined #openstack-meeting23:00
*** thorst_afk has joined #openstack-meeting23:00
*** priteau has joined #openstack-meeting23:01
*** aeng has quit IRC23:04
*** chyka has quit IRC23:04
*** chyka has joined #openstack-meeting23:04
*** baojg has quit IRC23:05
*** yangyapeng has quit IRC23:05
*** markstur has quit IRC23:06
*** priteau has quit IRC23:06
*** baojg has joined #openstack-meeting23:06
*** markstur has joined #openstack-meeting23:07
*** artom has joined #openstack-meeting23:10
*** markstur has quit IRC23:12
*** diablo_rojo has joined #openstack-meeting23:12
*** hongbin has quit IRC23:13
*** yamamoto_ has joined #openstack-meeting23:13
*** beekhof has joined #openstack-meeting23:13
*** Manuel_112 has joined #openstack-meeting23:14
*** gouthamr has quit IRC23:16
*** julim has joined #openstack-meeting23:17
*** cloudrancher has quit IRC23:18
*** yamamoto_ has quit IRC23:18
*** Manuel_112 has quit IRC23:18
*** cloudrancher has joined #openstack-meeting23:19
*** yangyapeng has joined #openstack-meeting23:19
*** aeng has joined #openstack-meeting23:21
*** baojg has quit IRC23:22
*** makowals has joined #openstack-meeting23:22
*** baojg has joined #openstack-meeting23:23
*** yangyapeng has quit IRC23:24
*** esberglu has quit IRC23:24
*** esberglu has joined #openstack-meeting23:25
*** makowals has quit IRC23:27
*** esberglu has quit IRC23:29
*** pvaneck has quit IRC23:34
*** Julien-zte has quit IRC23:35
*** makowals has joined #openstack-meeting23:36
*** baojg has quit IRC23:40
*** baojg has joined #openstack-meeting23:41
*** efried has quit IRC23:42
*** sshank has quit IRC23:43
*** baojg has quit IRC23:45
*** baojg has joined #openstack-meeting23:46
*** chyka has quit IRC23:46
*** markstur has joined #openstack-meeting23:48
*** baojg has quit IRC23:50
*** baojg has joined #openstack-meeting23:52
*** markstur has quit IRC23:53
*** gyee has quit IRC23:53
*** diablo_rojo has quit IRC23:54
*** edmondsw has joined #openstack-meeting23:55
*** efried has joined #openstack-meeting23:56
*** gyee has joined #openstack-meeting23:57
*** baojg has quit IRC23:58
*** SpamapS has quit IRC23:59
*** SpamapS has joined #openstack-meeting23:59

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