Tuesday, 2017-10-17

*** emagana has quit IRC00:02
*** emagana has joined #openstack-meeting00:03
*** emagana_ has joined #openstack-meeting00:04
*** emagana has quit IRC00:04
*** chyka has quit IRC00:04
*** janzian has quit IRC00:05
*** yangyapeng has quit IRC00:07
*** yangyapeng has joined #openstack-meeting00:07
*** baoli has quit IRC00:08
*** yangyapeng has quit IRC00:08
*** emagana_ has quit IRC00:08
*** yangyapeng has joined #openstack-meeting00:08
*** sshank has quit IRC00:12
*** yangyapeng has quit IRC00:13
*** edmondsw has joined #openstack-meeting00:13
*** rossella_s has quit IRC00:16
*** salv-orlando has joined #openstack-meeting00:17
*** markvoelker_ has quit IRC00:17
*** edmondsw has quit IRC00:18
*** rossella_s has joined #openstack-meeting00:19
*** salv-orlando has quit IRC00:22
*** yamamoto has joined #openstack-meeting00:24
*** markvoelker has joined #openstack-meeting00:25
*** shintaro has joined #openstack-meeting00:28
*** yamamoto has quit IRC00:29
*** markvoelker has quit IRC00:29
*** esberglu has joined #openstack-meeting00:30
*** markvoelker has joined #openstack-meeting00:34
*** rossella_s has quit IRC00:36
*** psachin has joined #openstack-meeting00:38
*** rossella_s has joined #openstack-meeting00:39
*** markvoelker has quit IRC00:39
*** mguiney has joined #openstack-meeting00:40
*** markvoelker has joined #openstack-meeting00:43
*** Swami has quit IRC00:43
*** Apoorva_ has joined #openstack-meeting00:44
*** esberglu has quit IRC00:45
*** markvoelker has quit IRC00:48
*** Apoorva has quit IRC00:48
*** Apoorva_ has quit IRC00:48
*** tovin07__ has joined #openstack-meeting00:49
*** ekcs has quit IRC00:50
*** rossella_s has quit IRC00:52
*** markvoelker has joined #openstack-meeting00:52
*** caowei has joined #openstack-meeting00:53
*** mriedem1 has joined #openstack-meeting00:54
*** mriedem has quit IRC00:55
*** rossella_s has joined #openstack-meeting00:55
*** mriedem1 is now known as mriedem00:55
*** markvoelker has quit IRC00:57
*** edmondsw has joined #openstack-meeting01:00
*** markvoelker has joined #openstack-meeting01:01
*** markvoelker has quit IRC01:06
*** JudeC has quit IRC01:06
*** markvoelker has joined #openstack-meeting01:11
*** markvoelker has quit IRC01:15
*** bzhao has joined #openstack-meeting01:16
*** yangyapeng has joined #openstack-meeting01:17
*** aeng has quit IRC01:17
*** salv-orlando has joined #openstack-meeting01:18
*** julim has joined #openstack-meeting01:19
*** markvoelker has joined #openstack-meeting01:20
*** iyamahat has quit IRC01:21
*** salv-orlando has quit IRC01:22
*** yamahata has quit IRC01:23
*** yamamoto has joined #openstack-meeting01:24
*** JudeC has joined #openstack-meeting01:24
*** ijw has joined #openstack-meeting01:25
*** ijw has quit IRC01:25
*** ijw has joined #openstack-meeting01:27
*** kaisers_ has joined #openstack-meeting01:28
*** kaisers has quit IRC01:31
*** aeng has joined #openstack-meeting01:34
*** jkilpatr_ has quit IRC01:37
*** aeng has quit IRC01:39
*** links has joined #openstack-meeting01:44
*** mriedem has quit IRC01:45
*** links is now known as Jaison|away01:45
*** hongbin has joined #openstack-meeting01:49
*** aeng has joined #openstack-meeting01:52
*** markvoelker has quit IRC01:53
*** deikiyoch has joined #openstack-meeting01:55
*** deikiyoch has left #openstack-meeting01:55
*** unicell has quit IRC01:57
*** bobh has quit IRC01:58
*** markvoelker has joined #openstack-meeting01:59
*** VW has joined #openstack-meeting02:02
*** markvoelker has quit IRC02:03
*** hongbin_ has joined #openstack-meeting02:04
*** kiennt26 has joined #openstack-meeting02:06
*** masber has quit IRC02:07
*** markvoelker has joined #openstack-meeting02:08
*** markvoelker has quit IRC02:12
*** bkopilov_ has quit IRC02:12
*** bkopilov has quit IRC02:13
*** markvoelker has joined #openstack-meeting02:17
*** shu-mutou has joined #openstack-meeting02:17
*** salv-orlando has joined #openstack-meeting02:18
*** emagana has joined #openstack-meeting02:20
*** markvoelker has quit IRC02:21
*** salv-orlando has quit IRC02:23
*** markvoelker has joined #openstack-meeting02:26
*** wanghao has joined #openstack-meeting02:30
*** markvoelker has quit IRC02:30
*** ijw has quit IRC02:31
*** wanghao has quit IRC02:32
*** wanghao has joined #openstack-meeting02:33
*** kevzha01 has joined #openstack-meeting02:34
*** dteselkin has quit IRC02:34
*** markvoelker has joined #openstack-meeting02:35
*** wanghao has quit IRC02:35
*** jhesketh has quit IRC02:35
*** kevzha01 is now known as kevinz02:36
*** wanghao has joined #openstack-meeting02:36
*** tonyb has quit IRC02:36
*** tris has quit IRC02:36
*** cinerama has quit IRC02:36
*** tonyb has joined #openstack-meeting02:37
*** wanghao has quit IRC02:38
*** jhesketh has joined #openstack-meeting02:38
*** wanghao has joined #openstack-meeting02:38
*** dteselkin has joined #openstack-meeting02:39
*** markvoelker has quit IRC02:40
*** cinerama has joined #openstack-meeting02:41
*** liuyulong has joined #openstack-meeting02:41
*** wanghao has quit IRC02:41
*** tris has joined #openstack-meeting02:42
*** wanghao has joined #openstack-meeting02:44
*** markvoelker has joined #openstack-meeting02:44
*** lbragstad has joined #openstack-meeting02:45
*** wanghao has quit IRC02:45
*** wanghao has joined #openstack-meeting02:45
*** masber has joined #openstack-meeting02:49
*** markvoelker has quit IRC02:49
*** wanghao has quit IRC02:50
*** hongbin_ has quit IRC02:51
*** wanghao has joined #openstack-meeting02:51
*** VW has quit IRC02:52
*** VW has joined #openstack-meeting02:52
*** Namrata has joined #openstack-meeting02:52
*** wanghao has quit IRC02:52
*** markvoelker has joined #openstack-meeting02:53
*** Tom_ has joined #openstack-meeting02:55
*** VW has quit IRC02:57
hongbin#startmeeting zun03:00
openstackMeeting started Tue Oct 17 03:00:14 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
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#link https://wiki.openstack.org/wiki/Zun#Agenda_for_2017-10-17_0300_UTC Today's agenda03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
hongbinthanks for joining Namrata kevinz kiennt2603:01
hongbinwe could have a short meeting today if not too much people is able to join03:02
*** zsli_ has joined #openstack-meeting03:02
hongbinhi zsli_03:02
*** FengShengqin has joined #openstack-meeting03:02
hongbinlet's get started03:02
hongbin#topic Announcements03:02
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:02
hongbinhi FengShengqin03:02
*** zsli_ is now known as Shunli03:03
FengShengqinsorry for later03:03
hongbini have an announcement, i and lakerzhou will have a presentation in sydney summit03:03
hongbinthe topic is about Zun SR-IOV support03:03
hongbinthis is the announcement i want to make03:03
hongbinanyone else has an announcement ?03:03
hongbinFengShengqin: np, thanks for joining03:04
hongbin#topic Cinder integration (hongbin)03:04
*** openstack changes topic to "Cinder integration (hongbin) (Meeting topic: zun)"03:04
hongbin#link https://blueprints.launchpad.net/zun/+spec/direct-cinder-integration Direct Cinder integration03:04
hongbinthere are a few patches under reviews for this BP03:04
*** emagana has quit IRC03:04
hongbin#link https://review.openstack.org/#/q/status:open+project:openstack/zun+branch:master+topic:bp/direct-cinder-integration03:05
hongbinin particular, we need reviews for these two patches:03:05
hongbin1. https://review.openstack.org/#/c/499381/03:05
*** emagana has joined #openstack-meeting03:05
hongbin2. https://review.openstack.org/#/c/499374/03:05
hongbinwelcome feedback if you have a chance to review03:05
hongbinthat is all from me about this bp03:06
hongbinany question?03:06
kevinzI'm just reviewing the 499374 now03:06
hongbinkevinz: thx, look forward to your feedback03:06
kevinz499374 is the base for the next few pathes?03:07
hongbinyes, it is03:07
kiennt26kevinz: yes03:07
kevinzthis is a workflow patch so that I can use it to mount the volume?03:07
*** wanghao has joined #openstack-meeting03:08
kevinzOr it need more patches to realize the function?03:08
hongbinyes, it provides the API for later patches to mount the cinder volume to compute host03:08
kevinzhongbin: OK03:08
hongbinthe major api is the two methods: attach_volume, and detach_volume03:09
hongbinall the codes are for implementing these two methods03:09
*** wanghao has quit IRC03:09
*** emagana has quit IRC03:09
kevinzhongbin: thanks for the information.03:09
hongbinkevinz: np03:09
*** wanghao has joined #openstack-meeting03:10
Namratai have a question03:10
hongbinNamrata: go ahead03:10
Namratacan I downloaad this and run and attach the volume03:10
Namrataor some work is pending03:10
hongbini think you need to download all the patches to get it work03:11
Namrataokay want to test it will download all patches03:11
hongbinsupposet you downloaded all the patches, the way to test it is: docker --mount source=<my_cinder_volume>,destination=/data <image> ...03:11
*** wanghao has quit IRC03:12
Namrataokay got it03:12
hongbinNamrata: thanks03:12
Namratathanks hongbin03:12
hongbinok, let's move on to the next topic03:12
hongbin#topic Introduce container composition (kevinz)03:12
*** openstack changes topic to "Introduce container composition (kevinz) (Meeting topic: zun)"03:12
*** wanghao has joined #openstack-meeting03:12
hongbin#link https://blueprints.launchpad.net/zun/+spec/introduce-compose03:12
hongbinkevinz: ^^03:12
kevinzLast week I've tried to register a node in K8s with the kubernetes python client called "client-python"03:13
kevinzThe register node process is easy to finish03:14
kevinzclient-python is the official kubernetes client03:14
hongbin#link https://github.com/kubernetes-incubator/client-python03:14
kevinzYes, this one03:14
*** wanghao has quit IRC03:14
hongbinalmost official, it is incubating03:14
kevinzI see dims also contribute some code in this project03:15
hongbinbut i think this is the right choice as a pything binding03:15
*** wanghao has joined #openstack-meeting03:15
hongbini assume the capsule coding is almost finish ?03:16
kevinzremain one features "upgrade" and a document03:17
kevinzDocument I've submitted to gerrit and will modified this week03:17
*** wanghao has quit IRC03:17
kevinzupgrade features is not implemented.03:17
*** wanghao has joined #openstack-meeting03:18
kevinzThis need container upgrade first03:18
hongbinin overall, i think this is a good progress03:18
hongbinthanks kevinz for getting the capsule implemented03:19
hongbinand we are almost there03:19
*** salv-orlando has joined #openstack-meeting03:19
*** wanghao has quit IRC03:19
kevinzhongbin: My pleasure:-)03:19
hongbinthanks kevinz03:20
hongbinany other comment about this topic?03:20
*** wanghao has joined #openstack-meeting03:20
hongbin#topic Add support for clear container (mkrai)03:20
*** openstack changes topic to "Add support for clear container (mkrai) (Meeting topic: zun)"03:21
hongbinmkrai: you there?03:21
Namratano she will not attend the meeting03:21
hongbinNamrata: ack03:21
Namratathere is festival in india03:21
hongbinlet's skip this one03:21
*** wanghao has quit IRC03:21
hongbini see03:21
hongbinNamrata: hope you guys enjoy the festival03:21
Namratathanks hongbin03:22
hongbin#topic NFV use cases (lakerzhou, Shunli)03:22
*** openstack changes topic to "NFV use cases (lakerzhou, Shunli) (Meeting topic: zun)"03:22
*** wanghao has joined #openstack-meeting03:22
hongbinShunli: ^^03:22
Shunlithe pci tracker is under reviewing.03:23
*** Jaison|away is now known as links03:23
hongbin#link https://review.openstack.org/#/c/508025/03:23
ShunliThe pci devcie of compute node can be collected now.03:23
hongbinsounds great !03:23
Shunlia new patch for pci request has submitted, WIP.03:23
*** wanghao has quit IRC03:24
Shunli@hongbin, are you working on the pci request patch?03:24
*** salv-orlando has quit IRC03:24
*** wanghao has joined #openstack-meeting03:24
hongbinShunli: i might borrwo your patch to do a hack03:24
Shunli@hongbin, what port info does kuryr need?03:24
*** coolsvap has joined #openstack-meeting03:25
hongbinShunli: i would say you can continue to finish your patch if you want, i might hack your patch for a demo only03:25
hongbinShunli: kuryr needs some information, but i didn't remember them right now03:25
Shunlifrom my investigation of nova code, seem i just set the binding_type=direct, port profile, mac.03:26
*** wanghao has quit IRC03:26
hongbinShunli: yes, all those need to be set03:26
Shunlido these info enough to connect a port to docker container、03:26
hongbin#link https://review.openstack.org/#/c/500436/15/doc/source/config-sriov.rst03:26
hongbinShunli: i am working on a WIP patch in kuryr-libnetwork side, it contains a docs about the detailed information03:27
*** wanghao has joined #openstack-meeting03:27
*** markvoelker has quit IRC03:27
hongbinShunli: please check out the link above03:27
ShunliOK, i will go through the doc.03:27
hongbinhowever, it is a WIP, so expect it to break :)03:28
hongbinShunli: ack, thanks for your work on this feature, we will demo your work in sydney03:28
*** wanghao has quit IRC03:28
Shunli@hongbin, since zun has no flavor, seems we can only support pre-created SRIOV port use case.03:28
hongbinShunli: if you don't mind, we can put your name on the presentation03:28
hongbinShunli: yes03:29
ShunliNo problem. but i seems cannot join the submmit.03:29
*** wanghao has joined #openstack-meeting03:29
hongbinShunli: yes, we can still mention you even you cannot join03:29
Shunli@hongbin, the pci request patch, i didn't implement zun scheduler filter.03:30
Shunlisuppose any host can support pci request.03:30
hongbini see03:31
hongbinnp, i can hack the scheduler for demo purpose03:31
*** wanghao has quit IRC03:31
Shunliok, ack.03:31
hongbinShunli: for the non-pre-created SRIOV port use case, i am open for proposal if you have one03:32
hongbinwe can revisit it later03:32
Shunliwill work on pci request today, hope it will be ready for review this weekend.03:32
hongbinok, that would be great03:32
Shunlithat's all for me03:32
hongbinthanks Shunli03:33
hongbin#topic Open Discussion03:33
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:33
hongbinanyone has a topic to bring up ?03:33
kiennt26none from me.03:33
hongbinkiennt26: btw, thanks for your work on the zuul v3 migration03:34
Namrata not from my side too03:34
*** wanghao has joined #openstack-meeting03:34
hongbinall, thanks for joining the meeting, see you next time03:34
kiennt26hongbin: my pleasure!03:34
kevinzkiennt26: Thanks +103:34
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"03:34
openstackMeeting ended Tue Oct 17 03:34:53 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-10-17-03.00.html03:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-10-17-03.00.txt03:34
*** wanghao has quit IRC03:34
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-10-17-03.00.log.html03:34
*** FengShengqin has quit IRC03:35
*** wanghao has joined #openstack-meeting03:35
*** hongbin has quit IRC03:37
*** sridharg has joined #openstack-meeting03:38
*** bkopilov has joined #openstack-meeting03:39
*** wanghao has quit IRC03:39
*** bkopilov_ has joined #openstack-meeting03:40
*** wanghao has joined #openstack-meeting03:40
*** mtreinish has quit IRC03:42
*** mtreinish has joined #openstack-meeting03:42
*** wanghao has quit IRC03:44
*** kiennt26 has quit IRC03:45
*** tovin07__ has quit IRC03:45
*** yamahata has joined #openstack-meeting03:45
*** wanghao has joined #openstack-meeting03:45
*** tovin07__ has joined #openstack-meeting03:46
*** kiennt26 has joined #openstack-meeting03:46
*** masber has quit IRC03:46
*** kevinz has quit IRC03:48
*** wanghao has quit IRC03:48
*** wanghao has joined #openstack-meeting03:49
*** yangyapeng has quit IRC03:49
*** yangyapeng has joined #openstack-meeting03:50
*** epico has joined #openstack-meeting03:50
*** wanghao has quit IRC03:52
*** wanghao has joined #openstack-meeting03:52
*** samP has joined #openstack-meeting03:54
*** abhishekk has joined #openstack-meeting03:55
*** wanghao has quit IRC03:57
*** tpatil has joined #openstack-meeting03:58
*** wanghao has joined #openstack-meeting03:58
*** lbragstad has quit IRC03:58
*** gouthamr has quit IRC03:59
samP#startmeeting masakari04:00
openstackMeeting started Tue Oct 17 04:00:01 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
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
*** wanghao has quit IRC04:00
samPhi all for masakari04:00
*** rkmrHonjo has joined #openstack-meeting04:00
Dinesh_Bhorhi all04:00
*** wanghao has joined #openstack-meeting04:00
samPlet's start04:00
samP#info Got room for project onboarding in AUS summit04:01
tpatilThat's good news04:01
samPplease let me know if you are available to speak on this session04:01
tpatillet's decide what sessions to be held04:02
samPIt was in hurry, so I ask the session with me as a speaker04:02
*** wanghao has quit IRC04:02
samPI cloud ask to add other as speakers04:03
*** wanghao has joined #openstack-meeting04:03
samPtpatil: sure, lets talk about this in ML.04:03
tpatilsamP: Ok04:03
*** rbudden has quit IRC04:03
samP#topic critical bugs04:03
*** openstack changes topic to "critical bugs (Meeting topic: masakari)"04:03
samP#link https://bugs.launchpad.net/masakari/+bug/172174204:04
openstackLaunchpad bug 1721742 in masakari "Masakari will fail to recovery instances on failure host if instance's task_state is not none" [Undecided,New] - Assigned to takahara.kengo (takahara.kengo)04:04
*** wanghao has quit IRC04:04
*** sagara has joined #openstack-meeting04:04
*** wanghao has joined #openstack-meeting04:04
rkmrHonjoI heard that Takahara is creating a patch for it.04:04
samPKengo has confirmed that reset set the VM_STATE to error and tast_state to none04:05
samPrkmrHonjo: thanks04:05
rkmrHonjosorry for interrupting.04:05
samPrkmrHonjo: np04:05
samPrkmrHonjo: you may proceed with original proposal04:05
samPAny other bugs?04:06
*** wanghao has quit IRC04:06
*** sridharg has quit IRC04:06
*** wanghao has joined #openstack-meeting04:06
samPIf any, please bring them on AOB at the end of the meeting04:06
samP#topic Discussion Points04:07
*** openstack changes topic to "Discussion Points (Meeting topic: masakari)"04:07
samP(1) Horizon Plugin (Dashboard)04:07
tpatilsamP: Need your approval04:07
samPI read the BP, LGTM04:08
samPare you plan to implement all at once?04:08
*** wanghao has quit IRC04:08
tpatilYes, Niraj has already completed POC, we will manage to implement failover segment and hosts in Queens Release04:09
tpatilIf something remains, can by postponed to the next release04:10
samPtpatil: niraj_singh: great, thanks. Approved04:10
samPtpatil: sure04:10
niraj_singhsamP: Thanks04:10
tpatilwe might need some help from you to get the new repo for masakari-dashboard04:10
samPtpatil: sure04:10
samPtpatil: would you like me to create it?04:11
tpatilsamP: we will ask for your help on ML or IRC04:11
samPtpatil: sure, np04:11
*** claudiub has joined #openstack-meeting04:11
tpatilAny idea, how many patches we need to submit to create a new repo?04:12
samP let me know when you need me04:12
samPtpatil: just one patch to project config04:12
tpatilsamP: OK04:12
tpatilOnce the blueprint is approved, we will submit a patch to project config04:13
samPthen infra team will create the repo. Then we have to init it with cookie cutter and start to fill it with code04:13
tpatilsamP: Ok, Thanks04:14
tpatilsamP: You have approved the blueprint, Thanks04:15
samP#link Project creates guide https://docs.openstack.org/infra/manual/creators.html04:15
samPtpatil: ^^ will help you04:15
tpatilsamP: Ok, We will refer this guide04:15
samPtpatil: thanks04:16
samP(2) Install guide document (in progress)04:16
tpatilwhat should be the repo name?04:16
samPtpatil: good question04:16
*** markvoelker has joined #openstack-meeting04:17
Dinesh_BhorAccording to the convention like "mistral-dashboard", "congress-dashboard" I think "masakari-dashboard" seems good to me.04:17
samPmost people named as [project name]-dashboard04:18
samPDinesh_Bhor: correct04:18
*** bobh has joined #openstack-meeting04:18
tpatilsamP: we will mention this as a project name04:18
samPyou may find this info on openstack-infra/project-config/gerrit/projects.yaml04:19
tpatilsecondly, are we going to manage all tasks of dashboard in the same masakari Launchpad project?04:19
*** wanghao has joined #openstack-meeting04:19
samPtpatil: I prefer to have it separate, but what would you think?04:20
*** salv-orlando has joined #openstack-meeting04:20
samPnormally, one project one bug tracker04:20
tpatilsamP: I don't see any problems if it's managed in a single project04:21
*** wanghao has quit IRC04:21
tpatilsamP: do you see any problems from release management perspective?04:22
*** dbecker has quit IRC04:22
*** bobh has quit IRC04:22
*** markvoelker has quit IRC04:22
*** wanghao has joined #openstack-meeting04:22
samPtpatil: Not from release management. However, let me look around and decide04:23
samPIf you some one want to get the packages from LP, then it would be a problem04:23
tpatilsamP: Sure, In the mean time ,we will go through the guide04:23
samPtpatil: sure, I will put more details in ML for this04:24
tpatilsamP: Ok, Thanks04:24
samPtpatil: thanks04:24
*** wanghao has quit IRC04:25
*** salv-orlando has quit IRC04:25
samPAny other questions on this^^?04:25
tpatilsamP: I'm good for now04:25
samPtpatil: thanks, ping me if you need smt04:26
samP(2) Install guide document (in progress)04:26
*** wanghao has joined #openstack-meeting04:26
samPI will review these docs today. In the meantime please update the schema04:26
abhishekkI will finish this in current week04:26
samPabhishekk: sure, that would be great04:27
*** markvoelker has joined #openstack-meeting04:27
*** wanghao has quit IRC04:27
samPabhishekk: thanks04:27
abhishekksamP: NP04:27
rkmrHonjoSorry, monitor document is not updated yet.04:27
rkmrHonjoBut, I and Takahara try it.04:28
samPrkmrHonjo: np, I only review the details in the doc. you may update it any time04:28
rkmrHonjosamP: thanks.04:28
*** wanghao has joined #openstack-meeting04:28
*** sridharg has joined #openstack-meeting04:28
samPrkmrHonjo: abhishekk: thanks again for doc work04:28
samP(3) recovery method customization04:29
samPI think spec update in progress now..04:29
samPDinesh_Bhor: great, thanks04:30
tpatilsamP: correct, we are planning to make each notification type configurable04:30
*** wanghao has quit IRC04:30
tpatilsamP: for example, host failure, you can use mistral workflow driver and for instance failure it should be possible to use the existing task flow driver04:30
samPtpatil: for each notification type, user may configure different work flow driver04:31
tpatilsamP: correct04:31
samPAnd this will be a config option, right?04:31
tpatilsamP: correct, adding all these logic may take more time though04:32
*** sridharg has quit IRC04:32
*** unicell has joined #openstack-meeting04:32
*** wanghao has joined #openstack-meeting04:32
samPtpatil: understand.04:32
tpatilas in the current code, it can only load one driver for all notification types04:32
*** markvoelker has quit IRC04:33
samPtpatil: correct, we need to start form there,04:33
*** markvoelker has joined #openstack-meeting04:34
samPallow load multiple drivers according to config values04:34
*** wanghao has quit IRC04:34
tpatilsamP: We will upload specs in couple of days04:34
tpatilsamP: Sure04:34
samPtpatil: sure04:34
*** wanghao has joined #openstack-meeting04:35
*** dbecker has joined #openstack-meeting04:35
samPtpatil: Dinesh_Bhor: abhishekk: Thank you for the proposal and all the work04:35
*** unicell has quit IRC04:35
samP(4) Find hosts without specifying segments04:36
samP#link sepc and code https://review.openstack.org/#/q/topic:bp/find-segment-by-host+(status:open+OR+status:merged)04:36
samPI put a comment on the spec, about creating a another command for this04:37
*** wanghao has quit IRC04:37
samPI prefer to add this feature in to host show command04:37
rkmrHonjosamP: Thanks. I and Takahara check it and reply.04:37
*** wanghao has joined #openstack-meeting04:37
samPrkmrHonjo: sure, I put -1 to patch, just to hold it till we fix the spec.04:38
rkmrHonjosamP: ok.04:38
*** sridharg has joined #openstack-meeting04:38
samPrkmrHonjo: please consider my comment and let me know what would you think04:38
*** unicell has joined #openstack-meeting04:39
rkmrHonjosamP: Sure. In my understanding, this spec says that new sub-command requires only host id or name.04:39
rkmrHonjo> Create a subcommand in masakariclient to find segment by specifying host name or id.04:39
*** wanghao has quit IRC04:39
samPrkmrHonjo: true04:39
samPchason: hi04:39
*** wanghao has joined #openstack-meeting04:40
rkmrHonjosamP: But, your comment said that "In your current proposal, if user wants to execute segment_host_show, user need to input host name/id and segment name/id.".04:40
rkmrHonjosamP: I think this comment is based on misunderstanding. Do you think about it?04:41
*** kiennt26 has quit IRC04:41
rkmrHonjoIf this new sub-command doesn't exist, user should run host-list for each segments to know the relation of host and segment.04:41
samPrkmrHonjo: even if you implement this, user still need to input host name and segment name to host show.04:41
samPrkmrHonjo: My proposal is to, include this feature into host show command04:42
rkmrHonjosamP: Ah...I understand your purpose.04:42
*** wanghao has quit IRC04:42
samPrkmrHonjo: sorry, my comment in the spec is not bit messy04:42
rkmrHonjosamP: OK, I and Takahara rethink about your idea.04:42
*** wanghao has joined #openstack-meeting04:43
samPrkmrHonjo: sure, if you need more info or help, please let me know04:43
rkmrHonjosamP: thanks.04:43
tpatilsamP: So what you are asking is to make failover segment id or name optional in case of host show command, correct?04:43
samPtpatil: correct04:43
tpatilsamP: Ok, it makes sense to me04:44
*** unicell1 has joined #openstack-meeting04:45
samPwith this feature, we can make segment id/name optional for host show command, and remove in future04:45
*** wanghao has quit IRC04:45
rkmrHonjosamP: I got it.04:45
*** unicell has quit IRC04:46
*** wanghao has joined #openstack-meeting04:46
samP(5) Queens Work items04:46
samPI think no update on this. right?04:46
rkmrHonjoYes, from my side.04:46
tpatilssl item is complete04:46
samPtpatil: thanks04:47
samPrkmrHonjo: thanks04:47
tpatilsamP: I will make this item as completed in the etherpad04:47
*** wanghao has quit IRC04:47
samPtpatil: Thanks, that would be nice04:47
*** wanghao has joined #openstack-meeting04:48
samP(6) BMHA04:48
samPno update on Masakari side04:48
*** marios has joined #openstack-meeting04:48
samPnova spec in review04:48
samP#link nova spec for BM node migrate/resize https://review.openstack.org/#/c/449155/04:49
*** kota_ has left #openstack-meeting04:49
*** wanghao has quit IRC04:49
samPonce it fixed, lets reconsider on this.04:49
samP#topic AOB04:49
*** openstack changes topic to "AOB (Meeting topic: masakari)"04:49
samPchason: Hi04:49
Dinesh_Bhorwelcome chason04:50
samPchason: welcome to Masakari04:50
samPchason: would you like to introduce your self?04:50
samPin the meantime, anyone have AOB items?04:51
samPtpatil: go ahead04:51
tpatilEnable-openstack-proposal-bot and ha-enabled-config-options blueprints are already released in Pike.04:51
tpatil# link : https://blueprints.launchpad.net/masakari/+spec/enable-openstack-proposal-bot04:52
tpatil#link : https://blueprints.launchpad.net/masakari/+spec/enable-openstack-proposal-bot04:52
*** wanghao has joined #openstack-meeting04:52
tpatilWe will update the status of these blueprints from our side. sam04:53
*** rbartal has quit IRC04:53
chasonI am a core of openstack-manuals and have an interest on Masakari project. I can work on our project's documentation. :D04:53
samPtpatil: sure, it seems some problem with bot04:53
tpatilsamP: Thanks04:53
samPchason: That is great.04:54
tpatilchason: That will be great, We need documentation experts in our project04:54
*** wanghao has quit IRC04:54
rkmrHonjochason: Thank you for attending!04:54
samPcurrently we are creating some docs,04:55
samP#link https://review.openstack.org/#/q/topic:docs/operators04:55
*** wanghao has joined #openstack-meeting04:55
samP#link https://review.openstack.org/#/q/topic:operators_guide04:55
chasonAha, looking forward to working together with you guys. :P04:55
abhishekkchason: as we are now official, we are modifying above patches to use openstackdocs theme04:55
chasonsamP checking04:56
samPchason: I would really appreciate it if you could review those doc and give us some feed back04:56
chasonabhishekk Oh, I can do something for it.04:56
samPchason: if you need any help on masakari, you may find us in #openstack-masakari or ML04:57
*** wanghao has quit IRC04:57
abhishekkchason: I will let you know04:57
samPchason: Thanks you in advance04:57
abhishekkchason: right now it will be great if you help in review :D04:57
abhishekkchason: as I have already started working on it :D04:57
*** wanghao has joined #openstack-meeting04:57
samPtpatil: I will update the status in LP BPs04:58
chasonsamP It's OK.04:58
samPI think we are running out of time here04:58
tpatilsamP: Thanks04:58
samPFor further discussions, please use #openstack-masakari or ML04:58
samPlet's finish this meeting04:59
abhishekkthank you04:59
*** wanghao has quit IRC04:59
samPThank you all.......04:59
Dinesh_BhorThank you all04:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"04:59
openstackMeeting ended Tue Oct 17 04:59:27 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-10-17-04.00.html04:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-10-17-04.00.txt04:59
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-10-17-04.00.log.html04:59
*** rkmrHonjo has quit IRC04:59
*** wanghao has joined #openstack-meeting04:59
*** samP has left #openstack-meeting05:00
*** emagana has joined #openstack-meeting05:03
*** wanghao has quit IRC05:03
*** wanghao has joined #openstack-meeting05:03
*** claudiub has quit IRC05:05
*** sagara has quit IRC05:05
*** wanghao has quit IRC05:09
*** wanghao has joined #openstack-meeting05:09
*** esberglu has joined #openstack-meeting05:09
*** esberglu has quit IRC05:09
*** emagana has quit IRC05:11
*** wanghao has quit IRC05:15
*** wanghao has joined #openstack-meeting05:16
*** edmondsw has quit IRC05:17
*** bobh has joined #openstack-meeting05:19
*** wanghao has quit IRC05:21
*** salv-orlando has joined #openstack-meeting05:21
*** bobh has quit IRC05:23
*** salv-orlando has quit IRC05:25
*** wanghao has joined #openstack-meeting05:26
*** tovin07__ has quit IRC05:30
*** wanghao has quit IRC05:30
*** wanghao has joined #openstack-meeting05:31
*** salv-orlando has joined #openstack-meeting05:34
*** JudeC has joined #openstack-meeting05:35
*** slaweq has joined #openstack-meeting05:35
*** wanghao has quit IRC05:35
*** rbudden has joined #openstack-meeting05:36
*** wanghao has joined #openstack-meeting05:36
*** janki has joined #openstack-meeting05:40
*** wanghao has quit IRC05:41
*** JudeC has quit IRC05:43
*** wanghao has joined #openstack-meeting05:44
*** slaweq has quit IRC05:47
*** yangyapeng has quit IRC05:49
*** wanghao has quit IRC05:49
*** liusheng has quit IRC05:49
*** bzhao has quit IRC05:50
*** dfflanders has joined #openstack-meeting05:50
*** lbrune has joined #openstack-meeting05:50
*** Tom__ has joined #openstack-meeting05:52
*** wanghao has joined #openstack-meeting05:52
*** slaweq has joined #openstack-meeting05:52
*** slaweq has quit IRC05:54
*** markvoelker has quit IRC05:54
*** wanghao has quit IRC05:55
*** wanghao has joined #openstack-meeting05:55
*** Tom_ has quit IRC05:56
*** janki has quit IRC05:57
*** janki has joined #openstack-meeting05:57
*** tpatil has quit IRC05:58
*** wanghao has quit IRC05:58
*** yangyapeng has joined #openstack-meeting05:59
*** wanghao has joined #openstack-meeting06:00
*** kiennt26 has joined #openstack-meeting06:04
*** wanghao has quit IRC06:04
*** wanghao has joined #openstack-meeting06:04
*** e0ne has joined #openstack-meeting06:07
*** wanghao has quit IRC06:08
*** wanghao has joined #openstack-meeting06:09
*** rbudden has quit IRC06:11
*** bcafarel has quit IRC06:14
*** wanghao has quit IRC06:14
*** wanghao has joined #openstack-meeting06:15
*** rbudden has joined #openstack-meeting06:16
*** aeng has quit IRC06:16
*** bcafarel has joined #openstack-meeting06:16
*** gcb has joined #openstack-meeting06:18
*** wanghao has quit IRC06:19
*** bobh has joined #openstack-meeting06:20
*** chyka has joined #openstack-meeting06:20
*** wanghao_ has joined #openstack-meeting06:21
*** liusheng has joined #openstack-meeting06:21
*** masber has joined #openstack-meeting06:21
*** wanghao_ has quit IRC06:22
*** wanghao_ has joined #openstack-meeting06:23
*** unicell1 has quit IRC06:23
*** bobh has quit IRC06:24
*** wanghao_ has quit IRC06:24
*** armax has quit IRC06:25
*** wanghao has joined #openstack-meeting06:25
*** chyka has quit IRC06:25
*** armax has joined #openstack-meeting06:25
*** armax has quit IRC06:25
*** wanghao has quit IRC06:29
*** wanghao has joined #openstack-meeting06:31
*** martinkopec has joined #openstack-meeting06:34
*** lbrune has quit IRC06:36
*** slaweq has joined #openstack-meeting06:37
*** slaweq_ has joined #openstack-meeting06:38
*** wanghao has quit IRC06:38
*** psachin has quit IRC06:38
*** Alex_Staf_ has quit IRC06:41
*** slaweq has quit IRC06:41
*** andreas_s has joined #openstack-meeting06:42
*** simon-AS559 has joined #openstack-meeting06:44
*** pcaruana has joined #openstack-meeting06:44
*** andreas_s has quit IRC06:45
*** e0ne has quit IRC06:45
*** claudiub has joined #openstack-meeting06:46
*** simon-AS5591 has joined #openstack-meeting06:47
*** andreas_s has joined #openstack-meeting06:47
*** lbrune has joined #openstack-meeting06:48
*** simon-AS559 has quit IRC06:48
*** andreas_s has quit IRC06:50
*** markvoelker has joined #openstack-meeting06:50
*** psachin has joined #openstack-meeting06:51
*** andreas__ has joined #openstack-meeting06:52
*** rbartal has joined #openstack-meeting06:52
*** edmondsw has joined #openstack-meeting07:01
*** andreas_s has joined #openstack-meeting07:02
*** bkopilov_ has quit IRC07:02
*** simon-AS5591 has quit IRC07:03
*** epico has quit IRC07:04
*** simon-AS559 has joined #openstack-meeting07:05
*** andreas__ has quit IRC07:05
*** edmondsw has quit IRC07:06
*** zhhuabj has quit IRC07:09
*** slaweq has joined #openstack-meeting07:11
*** kiennt26 has quit IRC07:12
*** kiennt26 has joined #openstack-meeting07:13
*** slaweq has quit IRC07:15
*** tesseract has joined #openstack-meeting07:16
*** dasanind has quit IRC07:17
*** dasanind has joined #openstack-meeting07:17
*** epico has joined #openstack-meeting07:17
*** zhhuabj has joined #openstack-meeting07:18
*** bobh has joined #openstack-meeting07:20
*** bobh has quit IRC07:25
*** phil_ has joined #openstack-meeting07:32
*** phil_ is now known as Guest8715207:32
*** wanghao has joined #openstack-meeting07:34
*** wanghao has quit IRC07:38
*** wanghao has joined #openstack-meeting07:38
*** wanghao has quit IRC07:45
*** wanghao has joined #openstack-meeting07:46
*** mhenkel has quit IRC07:47
*** ralonsoh has joined #openstack-meeting07:49
*** ralonsoh_ has joined #openstack-meeting07:50
*** wanghao has quit IRC07:50
*** wanghao has joined #openstack-meeting07:51
*** chenying has joined #openstack-meeting07:52
*** mhenkel has joined #openstack-meeting07:53
*** ralonsoh has quit IRC07:54
*** ralonsoh_ is now known as ralonsoh07:55
*** wanghao has quit IRC07:56
*** wanghao has joined #openstack-meeting07:56
*** wanghao has quit IRC08:00
*** wanghao has joined #openstack-meeting08:00
*** Fouad_Benamrane has joined #openstack-meeting08:02
*** wanghao has quit IRC08:03
*** wanghao has joined #openstack-meeting08:04
*** salv-orlando has quit IRC08:05
*** salv-orlando has joined #openstack-meeting08:05
*** chyka has joined #openstack-meeting08:10
*** wanghao has quit IRC08:10
*** iyamahat has joined #openstack-meeting08:10
*** toscalix has joined #openstack-meeting08:11
*** wanghao has joined #openstack-meeting08:11
*** iyamahat_ has joined #openstack-meeting08:11
*** bobmel_ has joined #openstack-meeting08:14
*** iyamahat has quit IRC08:14
*** chyka has quit IRC08:14
*** wanghao has quit IRC08:14
*** jgu has quit IRC08:15
*** jgu has joined #openstack-meeting08:15
*** wanghao has joined #openstack-meeting08:15
*** bobmel has quit IRC08:18
*** jgu has quit IRC08:19
*** wanghao has quit IRC08:19
*** jgu has joined #openstack-meeting08:20
*** iyamahat_ has quit IRC08:20
*** egallen has quit IRC08:20
*** iyamahat_ has joined #openstack-meeting08:21
*** bobh has joined #openstack-meeting08:21
*** jgu has quit IRC08:23
*** jgu has joined #openstack-meeting08:24
*** wanghao has joined #openstack-meeting08:24
*** iyamahat_ has quit IRC08:25
*** bobmel has joined #openstack-meeting08:25
*** yamahata has quit IRC08:26
*** bobh has quit IRC08:27
*** jgu has quit IRC08:28
*** wanghao has quit IRC08:28
*** jgu has joined #openstack-meeting08:28
*** wanghao has joined #openstack-meeting08:28
*** bobmel_ has quit IRC08:29
*** egallen has joined #openstack-meeting08:30
*** Alex_Staf_ has joined #openstack-meeting08:31
*** wanghao has quit IRC08:31
*** wanghao has joined #openstack-meeting08:32
*** jgu has quit IRC08:32
*** jgu has joined #openstack-meeting08:32
*** jgu has quit IRC08:36
*** wanghao has quit IRC08:36
*** jgu has joined #openstack-meeting08:36
*** wanghao has joined #openstack-meeting08:37
*** jgu has quit IRC08:40
*** jgu has joined #openstack-meeting08:41
*** wanghao has quit IRC08:42
*** priteau has joined #openstack-meeting08:43
*** zhhuabj has quit IRC08:44
*** jgu has quit IRC08:45
*** jgu has joined #openstack-meeting08:45
*** sridharg has quit IRC08:45
*** yamamoto has quit IRC08:47
*** jgu has quit IRC08:49
*** coolsvap has quit IRC08:49
*** jgu has joined #openstack-meeting08:49
*** wanghao has joined #openstack-meeting08:49
*** edmondsw has joined #openstack-meeting08:50
*** electrofelix has joined #openstack-meeting08:51
*** jgu has quit IRC08:53
*** jgu has joined #openstack-meeting08:53
*** wanghao has quit IRC08:54
*** edmondsw has quit IRC08:54
*** yamamoto has joined #openstack-meeting08:55
*** yamamoto has quit IRC08:55
*** jgu has quit IRC08:57
*** wanghao has joined #openstack-meeting08:57
*** zhhuabj has joined #openstack-meeting08:57
*** jgu has joined #openstack-meeting08:57
*** jgu has quit IRC09:01
*** wanghao has quit IRC09:01
*** jgu has joined #openstack-meeting09:01
*** wanghao has joined #openstack-meeting09:02
*** markvoelker has quit IRC09:03
*** simon-AS559 has quit IRC09:03
*** wanghao has quit IRC09:03
*** markvoelker has joined #openstack-meeting09:04
*** wanghao has joined #openstack-meeting09:04
*** esberglu has joined #openstack-meeting09:04
*** jgu has quit IRC09:05
*** jgu has joined #openstack-meeting09:06
*** wanghao has quit IRC09:06
*** lbrune1 has joined #openstack-meeting09:08
*** wanghao has joined #openstack-meeting09:08
*** esberglu has quit IRC09:09
*** jgu has quit IRC09:09
*** lbrune has quit IRC09:09
*** wanghao has quit IRC09:10
*** jgu has joined #openstack-meeting09:10
*** wanghao has joined #openstack-meeting09:10
*** e0ne has joined #openstack-meeting09:13
*** wanghao has quit IRC09:13
*** wanghao has joined #openstack-meeting09:13
*** jgu has quit IRC09:13
*** jgu has joined #openstack-meeting09:14
*** yamamoto has joined #openstack-meeting09:15
*** wanghao has quit IRC09:15
*** bobmel_ has joined #openstack-meeting09:15
*** wanghao has joined #openstack-meeting09:16
*** sdague has joined #openstack-meeting09:17
*** jgu has quit IRC09:18
*** jgu has joined #openstack-meeting09:18
*** wanghao has quit IRC09:18
*** bobmel has quit IRC09:19
*** bobmel has joined #openstack-meeting09:19
*** wanghao has joined #openstack-meeting09:19
*** sambetts|afk is now known as sambetts09:20
*** andreas_s has quit IRC09:21
*** bobmel_ has quit IRC09:22
*** jgu has quit IRC09:22
*** wanghao has quit IRC09:22
*** jgu has joined #openstack-meeting09:22
*** liusheng has quit IRC09:22
*** wanghao has joined #openstack-meeting09:23
*** liusheng has joined #openstack-meeting09:23
*** simon-AS559 has joined #openstack-meeting09:23
*** bobh has joined #openstack-meeting09:24
*** jgu has quit IRC09:26
*** wanghao has quit IRC09:26
*** jgu has joined #openstack-meeting09:26
*** bobmel has quit IRC09:26
*** bobmel has joined #openstack-meeting09:27
*** wanghao has joined #openstack-meeting09:27
*** simon-AS559 has quit IRC09:27
*** wanghao has quit IRC09:27
*** Tom__ has quit IRC09:28
*** liusheng has quit IRC09:28
*** wanghao has joined #openstack-meeting09:28
*** wanghao has quit IRC09:28
*** liusheng has joined #openstack-meeting09:28
*** Shunli has quit IRC09:29
*** bobh has quit IRC09:29
*** jgu has quit IRC09:30
*** andreas_s has joined #openstack-meeting09:30
*** slaweq has joined #openstack-meeting09:30
*** jgu has joined #openstack-meeting09:30
*** bobmel has quit IRC09:32
*** jchhatbar has joined #openstack-meeting09:34
*** jgu has quit IRC09:34
*** jgu has joined #openstack-meeting09:34
*** slaweq has quit IRC09:35
*** janki has quit IRC09:37
*** jgu has quit IRC09:38
*** jgu has joined #openstack-meeting09:39
*** jgu has quit IRC09:42
*** jgu has joined #openstack-meeting09:43
*** zhhuabj has quit IRC09:44
*** jgu has quit IRC09:47
*** jgu has joined #openstack-meeting09:47
*** salv-orlando has quit IRC09:50
*** ociuhandu has quit IRC09:50
*** salv-orlando has joined #openstack-meeting09:50
*** jgu has quit IRC09:51
*** jgu has joined #openstack-meeting09:51
*** simon-AS559 has joined #openstack-meeting09:51
*** jgu has quit IRC09:55
*** salv-orlando has quit IRC09:55
*** jgu has joined #openstack-meeting09:55
*** chenying_ has quit IRC09:56
*** simon-AS559 has quit IRC09:56
*** simon-AS559 has joined #openstack-meeting09:57
*** shintaro has quit IRC09:58
*** esberglu has joined #openstack-meeting09:59
*** jgu has quit IRC09:59
*** esberglu has quit IRC09:59
*** jgu has joined #openstack-meeting09:59
*** andreas_s has quit IRC10:02
*** zhhuabj has joined #openstack-meeting10:02
*** jgu has quit IRC10:03
*** jgu has joined #openstack-meeting10:03
*** dmacpher has quit IRC10:05
*** gmann is now known as gmann_afk10:09
*** jgu has quit IRC10:09
*** jgu has joined #openstack-meeting10:09
*** jgu has quit IRC10:13
*** jgu has joined #openstack-meeting10:13
*** bobmel has joined #openstack-meeting10:15
*** jgu has quit IRC10:17
*** jgu has joined #openstack-meeting10:18
*** yamamoto has quit IRC10:18
*** priteau has quit IRC10:19
*** priteau has joined #openstack-meeting10:21
*** jgu has quit IRC10:22
*** jgu has joined #openstack-meeting10:22
*** yamamoto has joined #openstack-meeting10:25
*** bobh has joined #openstack-meeting10:25
*** jgu has quit IRC10:26
*** jgu has joined #openstack-meeting10:26
*** ociuhandu has joined #openstack-meeting10:27
*** bobmel has quit IRC10:28
*** bobmel has joined #openstack-meeting10:28
*** yamamoto has quit IRC10:30
*** jgu has quit IRC10:30
*** bobh has quit IRC10:30
*** jgu has joined #openstack-meeting10:30
*** liusheng has quit IRC10:32
*** salv-orlando has joined #openstack-meeting10:32
*** chenying has quit IRC10:32
*** chenying has joined #openstack-meeting10:32
*** liusheng has joined #openstack-meeting10:32
*** slaweq has joined #openstack-meeting10:32
*** jgu has quit IRC10:34
*** jgu has joined #openstack-meeting10:34
*** andreas_s has joined #openstack-meeting10:35
*** slaweq has quit IRC10:37
*** lbrune1 has quit IRC10:38
*** edmondsw has joined #openstack-meeting10:38
*** jgu has quit IRC10:38
*** jgu has joined #openstack-meeting10:39
*** caowei has quit IRC10:39
*** toscalix has quit IRC10:40
*** dprince has joined #openstack-meeting10:42
*** edmondsw has quit IRC10:42
*** jgu has quit IRC10:42
*** dprince has quit IRC10:42
*** lbrune has joined #openstack-meeting10:43
*** jgu has joined #openstack-meeting10:43
*** tesseract has quit IRC10:43
*** tesseract has joined #openstack-meeting10:43
*** bkopilov has quit IRC10:46
*** jgu has quit IRC10:46
*** jgu has joined #openstack-meeting10:47
*** bobmel_ has joined #openstack-meeting10:47
*** rbudden_ has joined #openstack-meeting10:48
*** rbudden has quit IRC10:50
*** rbudden_ is now known as rbudden10:50
*** jgu has quit IRC10:51
*** jgu has joined #openstack-meeting10:51
*** bobmel has quit IRC10:51
*** priteau has quit IRC10:52
*** esberglu has joined #openstack-meeting10:52
*** dmacpher has joined #openstack-meeting10:53
*** jgu has quit IRC10:55
*** jgu has joined #openstack-meeting10:55
*** yangyapeng has quit IRC10:55
*** esberglu has quit IRC10:57
*** jgu has quit IRC10:59
*** jgu has joined #openstack-meeting10:59
*** bobmel has joined #openstack-meeting11:00
*** jgu has quit IRC11:03
*** jgu has joined #openstack-meeting11:03
*** bobmel_ has quit IRC11:04
*** jkilpatr has joined #openstack-meeting11:06
*** jgu has quit IRC11:07
*** lbrune has quit IRC11:07
*** jgu has joined #openstack-meeting11:07
*** simon-AS5591 has joined #openstack-meeting11:08
*** simon-AS559 has quit IRC11:09
*** simon-AS559 has joined #openstack-meeting11:11
*** jgu has quit IRC11:11
*** jgu has joined #openstack-meeting11:12
*** sridharg has joined #openstack-meeting11:12
*** simon-AS5592 has joined #openstack-meeting11:13
*** raildo has joined #openstack-meeting11:14
*** simon-AS5591 has quit IRC11:15
*** simon-AS559 has quit IRC11:15
*** jgu has quit IRC11:15
*** jgu has joined #openstack-meeting11:16
*** jgu has quit IRC11:20
*** jgu has joined #openstack-meeting11:20
*** lbrune has joined #openstack-meeting11:20
*** jgu has quit IRC11:24
*** jgu has joined #openstack-meeting11:24
*** lbrune has quit IRC11:25
*** yamamoto has joined #openstack-meeting11:26
*** bobh has joined #openstack-meeting11:26
*** jkilpatr has quit IRC11:27
*** jkilpatr has joined #openstack-meeting11:27
*** jgu has quit IRC11:28
*** jgu has joined #openstack-meeting11:28
*** bobmel_ has joined #openstack-meeting11:29
*** bobh has quit IRC11:31
*** lbrune has joined #openstack-meeting11:31
*** bobmel has quit IRC11:32
*** yamamoto has quit IRC11:32
*** jgu has quit IRC11:32
*** jgu has joined #openstack-meeting11:32
*** Tom_ has joined #openstack-meeting11:34
*** jgu has quit IRC11:36
*** jgu has joined #openstack-meeting11:37
*** Tom_ has quit IRC11:39
*** jgu has quit IRC11:40
*** jgu has joined #openstack-meeting11:41
*** yamamoto has joined #openstack-meeting11:41
*** yamamoto_ has joined #openstack-meeting11:42
*** jgu has quit IRC11:44
*** jgu has joined #openstack-meeting11:45
*** yamamoto has quit IRC11:46
*** chyka has joined #openstack-meeting11:46
*** bobmel has joined #openstack-meeting11:48
*** jgu has quit IRC11:49
*** jgu has joined #openstack-meeting11:49
*** chyka has quit IRC11:51
*** bobmel_ has quit IRC11:51
*** bobmel_ has joined #openstack-meeting11:51
*** tpsilva has joined #openstack-meeting11:53
*** jgu has quit IRC11:53
*** jgu has joined #openstack-meeting11:53
*** salv-orlando has quit IRC11:54
*** bobmel has quit IRC11:55
*** yamamoto_ has quit IRC11:56
*** bobmel_ has quit IRC11:57
*** jgu has quit IRC11:57
*** jgu has joined #openstack-meeting11:57
*** bobmel has joined #openstack-meeting11:58
*** epico has quit IRC12:01
*** jgu has quit IRC12:01
*** lbrune has quit IRC12:01
*** jgu has joined #openstack-meeting12:01
*** chenying has quit IRC12:02
*** liusheng has quit IRC12:02
*** liusheng has joined #openstack-meeting12:03
*** chenying has joined #openstack-meeting12:03
*** jgu has quit IRC12:05
*** jgu has joined #openstack-meeting12:06
*** dmacpher has quit IRC12:06
*** dmacpher has joined #openstack-meeting12:07
*** Tom__ has joined #openstack-meeting12:08
*** Guest87152 has quit IRC12:09
*** edmondsw has joined #openstack-meeting12:09
*** jgu has quit IRC12:09
*** jgu has joined #openstack-meeting12:10
*** chenying has quit IRC12:11
*** bobmel has quit IRC12:12
*** bobmel has joined #openstack-meeting12:12
*** lbrune has joined #openstack-meeting12:13
*** jgu has quit IRC12:14
*** jgu has joined #openstack-meeting12:14
*** pchavva has joined #openstack-meeting12:15
*** phil_ has joined #openstack-meeting12:17
*** dprince has joined #openstack-meeting12:17
*** phil_ is now known as Guest5427112:17
*** jgu has quit IRC12:18
*** jgu has joined #openstack-meeting12:18
*** yamamoto has joined #openstack-meeting12:19
*** bkopilov has joined #openstack-meeting12:20
*** jgu has quit IRC12:22
*** jgu has joined #openstack-meeting12:22
*** dustins has joined #openstack-meeting12:24
*** jgu has quit IRC12:26
*** jgu has joined #openstack-meeting12:26
*** dustins has quit IRC12:28
*** dustins has joined #openstack-meeting12:29
*** abhishekk has quit IRC12:30
*** jgu has quit IRC12:30
*** jgu has joined #openstack-meeting12:30
*** jgu has quit IRC12:34
*** jgu has joined #openstack-meeting12:35
*** gongysh has joined #openstack-meeting12:35
*** gongysh has quit IRC12:35
*** bobmel_ has joined #openstack-meeting12:38
*** bobmel has quit IRC12:38
*** jgu has quit IRC12:38
*** jgu has joined #openstack-meeting12:39
*** salv-orlando has joined #openstack-meeting12:40
*** chenybd has joined #openstack-meeting12:41
*** jgu has quit IRC12:43
*** jgu has joined #openstack-meeting12:43
*** julim has quit IRC12:45
*** bobmel_ has quit IRC12:45
*** bobmel has joined #openstack-meeting12:45
*** caboucha has joined #openstack-meeting12:45
*** jgu has quit IRC12:47
*** jgu has joined #openstack-meeting12:47
*** gongysh has joined #openstack-meeting12:48
*** gongysh has quit IRC12:48
*** mriedem has joined #openstack-meeting12:49
*** jgu has quit IRC12:51
*** jgu has joined #openstack-meeting12:51
*** esberglu has joined #openstack-meeting12:52
*** yangyapeng has joined #openstack-meeting12:53
*** rbudden has quit IRC12:53
*** mjturek has joined #openstack-meeting12:54
*** yamamoto has quit IRC12:54
*** jgu has quit IRC12:55
*** bobh has joined #openstack-meeting12:55
*** jgu has joined #openstack-meeting12:55
*** jgu has quit IRC12:59
*** jgu has joined #openstack-meeting13:00
*** ruijie has joined #openstack-meeting13:00
ruijie#startmeeting senlin13:00
openstackMeeting started Tue Oct 17 13:00:21 2017 UTC and is due to finish in 60 minutes.  The chair is ruijie. 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
Qiminghi, ruijie13:01
ruijiehi Qiming13:01
ruijiehere is the agenda13:01
*** pabelanger has quit IRC13:01
*** pabelanger has joined #openstack-meeting13:01
*** jgu has quit IRC13:03
*** jgu has joined #openstack-meeting13:04
ruijiethe work item I am following on are: https://review.openstack.org/#/c/504870/ and https://review.openstack.org/#/c/506550/13:04
ruijiethey have migrated the zuul to zuul V3, so we may need another patches to add the job templates for senlin-tempest-plugin project13:05
Qiminglooks like both are on track13:05
Qimingokay, I believe we may need to adjust the CI scripts for gate jobs to run correctly13:06
ruijieyes Qiming13:06
ruijieanother question is about the dead lock ..13:07
*** andreas_s has quit IRC13:07
ruijieit came up again, and as I talked with chenyb4, they met the problem too13:07
*** andreas_s has joined #openstack-meeting13:07
*** jgu has quit IRC13:07
*** jgu has joined #openstack-meeting13:08
Qimingis there a bug report on this?13:09
ruijienot yet Qiming, I am still looking at it, looks like still the problem of DB side13:10
ruijiethe cluster lock was not released correctly13:10
Qimingnot released?13:10
*** jgu has quit IRC13:12
ruijieyes Qiming, triggered cluster_delete, but the action failed. The current situation is: 3 of the node_delete action are still in "RUNNING" state, the cluster action is in "FAILED" state, and the cluster lock is still there13:12
*** jgu has joined #openstack-meeting13:12
*** liuyulong has quit IRC13:12
Qimingnode deletion running13:13
Qimingbut cluster action failed?13:13
ruijieyes .. strange13:13
*** thorst has joined #openstack-meeting13:14
Qimingthat could not happen13:14
Qimingit sounds not like a cluster lock problem13:14
Qimingthe question is why cluster action failed?13:15
ruijiethe profile layer raised exceptions, some of the node deletion actions failed13:16
Qimingthen node delete actions should fail13:16
*** jgu has quit IRC13:16
*** jgu has joined #openstack-meeting13:16
ruijieyes Qiming, none of the node actions shoule be in "RUNNING" state ..13:16
Qimingso ... a bug report with detailed status of locks would be helpful13:17
ruijiesure Qiming, I will draft an bug with the details13:18
Qimingdo we need some tooling support for better debugging?13:18
ruijieQiming you have any suggestions, I am using log and pdb now ..:(13:19
Qimingthe sqlalchemy layer is very annoying ...13:19
Qimingand oslo.db layer is masking some of the parameters13:20
*** jgu has quit IRC13:20
*** baoli has joined #openstack-meeting13:20
*** jgu has joined #openstack-meeting13:20
*** andreas_s has quit IRC13:21
*** lbragstad has joined #openstack-meeting13:22
ruijiemaybe we can find some methods to reduce the dependency on DB?13:22
QimingI don't think so13:22
QimingDB concurrency is a mature technology13:23
Qiminghowever, sqlalchemy and oslo.db is making things a lot difficult to diagnose13:23
Qimingif we manage locks in python ... that is gonna be a reinvention of the wheel ... even if we managed to get it done right13:24
*** wanghao has joined #openstack-meeting13:24
*** jgu has quit IRC13:24
*** jgu has joined #openstack-meeting13:25
ruijieokay Qiming, that makes sense13:26
*** andreas_s has joined #openstack-meeting13:26
Qimingso .. back to the problem mentioned, I think we need to solve the problem in several steps13:27
*** jgu has quit IRC13:28
*** jgu has joined #openstack-meeting13:29
*** lhx_ has joined #openstack-meeting13:32
*** jgu has quit IRC13:32
*** jgu has joined #openstack-meeting13:33
ruijiesir ?13:33
ruijieI thought you will talk about the stops13:33
*** egallen has quit IRC13:35
ruijielet's moving on?13:35
*** andreas_s has quit IRC13:36
*** jgu has quit IRC13:37
*** jgu has joined #openstack-meeting13:37
ruijieabout the meetup, I talked with people, liyi and elynn are okay for 28th Oct. and xuefeng will not be available at that time13:37
ruijieI didn't cache xinhui yet :) will send her another e-mail to check the schedule13:38
ruijiemaybe we can share the window in the meeting, so that people who cannot make it can still join the online meeting13:39
*** wanghao has quit IRC13:39
Qiminggood idea13:40
*** davidsha has joined #openstack-meeting13:40
Qimingpls let me know if there are things I can help13:40
*** xyang1 has joined #openstack-meeting13:40
*** andreas_s has joined #openstack-meeting13:41
*** jgu has quit IRC13:41
*** andreas_s has quit IRC13:41
*** jgu has joined #openstack-meeting13:41
*** andreas_s has joined #openstack-meeting13:41
*** cdub has joined #openstack-meeting13:41
ruijiesure Qiming :) will update the link on etherpad https://etherpad.openstack.org/p/senlin-queens-meetup13:41
ruijienext topic is yours Qiming13:43
Qimingsummit prep?13:43
ruijiesummit prep13:43
*** gouthamr has joined #openstack-meeting13:43
*** felipemonteiro_ has joined #openstack-meeting13:43
Qimingmy trip request was rejected13:43
ruijieyes Qiming .. we have a light talk?13:43
ruijieme too :)13:43
*** felipemonteiro__ has joined #openstack-meeting13:44
QimingI applied for trip sponor program but failed13:44
ruijieme either :(13:44
ruijienot sure what happend this summit13:44
*** gcb has quit IRC13:45
Qimingtrip to australia is expensive13:45
*** jgu has quit IRC13:45
*** jgu has joined #openstack-meeting13:45
*** julim has joined #openstack-meeting13:45
Qimingsome money has been allocated to PTG by the foundation I guess13:45
*** gcb has joined #openstack-meeting13:47
*** felipemonteiro_ has quit IRC13:48
Qimingelynn pinged me today, about his talk13:48
Qiminghis installation of k8s was smooth13:48
ruijiewith senlin?13:49
Qimingalthough he had to regenerate the server cert so that the floating IP of the master node can be used13:49
*** jgu has quit IRC13:49
*** jgu has joined #openstack-meeting13:49
Qimingother than that, I am not aware of other topics acception13:51
*** psachin has quit IRC13:52
ruijieokay Qiming, we may end the meeting a little bit early13:52
ruijiethanks for joining Qiming13:52
ruijieGoog night13:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:53
openstackMeeting ended Tue Oct 17 13:53:15 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-10-17-13.00.html13:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-10-17-13.00.txt13:53
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-10-17-13.00.log.html13:53
*** jgu has quit IRC13:53
*** jgu has joined #openstack-meeting13:53
*** esberglu has quit IRC13:54
*** esberglu has joined #openstack-meeting13:54
*** yamamoto has joined #openstack-meeting13:55
*** jgu has quit IRC13:57
*** VW has joined #openstack-meeting13:57
*** VW has quit IRC13:57
*** shintaro has joined #openstack-meeting13:58
*** jgu has joined #openstack-meeting13:58
*** VW has joined #openstack-meeting13:58
*** armax has joined #openstack-meeting13:58
*** awaugama has joined #openstack-meeting13:58
*** tmorin has joined #openstack-meeting13:59
*** esberglu has quit IRC13:59
*** chenybd has quit IRC14:00
davidsha#startmeeting network_common_flow_classifier14:00
openstackMeeting started Tue Oct 17 14:00:38 2017 UTC and is due to finish in 60 minutes.  The chair is davidsha. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: network_common_flow_classifier)"14:00
openstackThe meeting name has been set to 'network_common_flow_classifier'14:00
davidshaHey everyone!14:00
bcafarelhowdy davidsha14:01
davidshanot too bad, you bcafarel?14:01
*** jgu has quit IRC14:01
*** jgu has joined #openstack-meeting14:02
*** cleong has joined #openstack-meeting14:02
bcafarelnice summer weather here, I'm not complaining :)14:02
*** jchhatbar has quit IRC14:03
davidshaI'll wait 2 mins for the others then we'll start, It's nice weather here now as well, we had a Hurricane yesterday...14:04
*** e0ne_ has joined #openstack-meeting14:04
*** e0ne has quit IRC14:04
davidshaAnd meant to have another big storm on Friday.14:04
bcafarelyeah I saw that, looks like it was not a good day to visit Connemara14:05
*** yamamoto has quit IRC14:05
*** jgu has quit IRC14:06
*** ruijie has quit IRC14:06
davidshaYup, looking at the power lines that are down, the damage looks very spread out though14:06
*** jgu has joined #openstack-meeting14:06
davidshatmorin reedip: ping14:06
tmorindavidsha: hi everyone14:06
*** slaweq has joined #openstack-meeting14:06
bcafarelhi tmorin14:07
tmorinhi bcafarel !14:07
davidshaWe'll start now14:07
igordchello all14:07
*** thingee has quit IRC14:07
davidshaAgenda is here: https://wiki.openstack.org/wiki/Neutron/CommonClassificationFramework#All_Meetings.27_Agendas14:07
davidsha#topic CCF v0 - Update14:08
*** openstack changes topic to "CCF v0 - Update (Meeting topic: network_common_flow_classifier)"14:08
*** marios has quit IRC14:08
davidshaSo The database migration patch looks ready14:08
*** marios has joined #openstack-meeting14:08
davidsha#link https://review.openstack.org/#/c/498471/14:08
*** esberglu has joined #openstack-meeting14:09
davidshaWill I can merge the patch or will I ask a neutron core to have a look and have the final approval?14:09
bcafarelloosk so, and if needed it can be fixed/updated until there is an "official" v014:09
davidsha+1 for neutron core or me?14:11
*** slaweq has quit IRC14:11
igordcthe non-question :p14:11
*** thingee has joined #openstack-meeting14:11
igordcso bcafarel14:11
davidshaSo I'll merge it then and we can modify going forward14:11
*** jgu has quit IRC14:12
*** Nil_ has joined #openstack-meeting14:12
davidshaI'm almost finished updating the follow up patch https://review.openstack.org/#/c/499571/14:12
*** jgu has joined #openstack-meeting14:12
davidshaI'm going to draft the functional tests separate and submit a patch to infra to enable functional testing and py3514:13
davidshatmorin: have you any tips?14:13
*** emagana has joined #openstack-meeting14:14
tmorindavidsha: I haven't looked at this one for a while14:14
*** galstrom_zzz is now known as galstrom14:15
tmorindavidsha: I assume I'd better wait for you to finish the udpate first14:15
*** bobmel_ has joined #openstack-meeting14:15
tmorindavidsha: are you asking me about functional testing specifically ?14:15
davidshaTrue, are there any questions?14:15
davidshatmorin: yup functional test14:15
*** cdub has quit IRC14:16
davidshaWe'll wait for next topic14:16
tmorindavidsha: I think that now that you can have in-repo zuulv3 test job definition, this is perhaps what you should target14:16
tmorinpy35 is a standard job and should be enabled via a change in project-config14:16
davidshatmorin: ack14:17
*** bobmel has quit IRC14:17
davidshaIf there are no questions we'll move on14:17
*** cdub has joined #openstack-meeting14:17
*** jgu has quit IRC14:17
davidsha#topic Functional tests14:17
*** openstack changes topic to "Functional tests (Meeting topic: network_common_flow_classifier)"14:17
*** jgu has joined #openstack-meeting14:18
davidshaSo we've kind of covered this, I should have waited till this topic before I brought it up.14:18
bcafarelany feedback on OVOs by iharchys? (sorry catching up)14:18
davidshabcafarel: I haven't asked yet, wanted to have the patch updated first.14:19
*** yamahata has joined #openstack-meeting14:20
davidshaIt should be up within the next 2 hours, I just caught somethings that needed to be changed.14:20
*** gongysh has joined #openstack-meeting14:20
*** gongysh has quit IRC14:20
davidshaI'll add some unit tests for it now and have it up soon.14:21
*** gongysh has joined #openstack-meeting14:21
davidshaIf there's nothing on functional tests I'll move this to open discussion.14:21
tmorinabout OVO: to allow the push/pull RPC framework to work on  objects defined outside neutron, I think that https://review.openstack.org/#/c/512336/ will be needed14:21
*** jgu has quit IRC14:22
tmorinthis is at least what I concluded when working on OVO for BGPVPN14:22
davidsha#topic Open discussion14:22
*** openstack changes topic to "Open discussion (Meeting topic: network_common_flow_classifier)"14:22
*** jgu has joined #openstack-meeting14:22
tmorinthere is one topic that I want to bring up related to DB, foreign keys and projects consuming CCF14:23
*** cdub has quit IRC14:23
*** cdub has joined #openstack-meeting14:23
davidshatmorin: ok, sorry just looking at the patch14:23
*** reed has quit IRC14:23
* bcafarel gets the coffee ready in the meantime14:23
davidshatmorin: go ahead, sorry14:24
tmorinideally we would like consuming projects to have foreign keys to cg or classifications14:24
*** reed has joined #openstack-meeting14:25
davidshatmorin: yes14:25
davidshaWell, it would cause an issue for DB migration though wouldn't it?14:25
tmorinbut there is I think one obstacle: I haven't found anything that would guarantee that the DB migration scripts creating the CCF tables will be run *before* the DB migration script of the project consuming CCF which would have foreign keys to CCF tables14:25
tmorindavidsha: yes :)14:26
*** jgu has quit IRC14:26
*** jgu has joined #openstack-meeting14:26
davidshatmorin: Ya, they would need to just be normal strings then.14:27
igordctmorin: "DB migration scripts creating the CCF tables" - do you mean the initial migration?14:28
davidshaigordc: yes.14:28
*** jgu has quit IRC14:30
tmorindavidsha: yes, not having a foreign key is a solution, but it means we will possibly need more "book-keeping" code to preserve consistency14:30
*** jgu has joined #openstack-meeting14:30
*** gongysh has quit IRC14:31
*** slaweq_ has quit IRC14:32
igordctmorin: what if ccf was under core neutron?14:32
davidshatmorin: True, you mean similar to how QoS does it with policies in the L2 - extension14:32
*** reedip_ has joined #openstack-meeting14:32
tmorinigordc: that would be better I think14:32
tmorinwe've discussed this briefly in Denver in fact14:33
bcafarelmoving the ccf in neutron itself?14:33
davidshatmorin: outside of the live stream?14:33
*** rbartal has quit IRC14:33
tmorindavidsha: yes, with FWaaS guys during lunch14:33
davidshatmorin: Oh yes, you mentioned that.14:34
*** jgu has quit IRC14:34
*** hongbin has joined #openstack-meeting14:34
davidshabcafarel: yes, it was on the books, but it was later after it had been established and stable.14:34
*** jgu has joined #openstack-meeting14:34
tmorindavidsha: well, we discussed how to check with consuming project whether we could delete a CCF resource, but we assumed we would have foreign keys14:35
igordctmorin: is the migration sequence tighly coupled to which repo the code belongs to?14:35
igordctmorin: atm14:35
davidshatmorin: We could add the classification base table into core neutron...14:35
*** yangyapeng has quit IRC14:35
*** noslzzp has quit IRC14:36
*** yangyapeng has joined #openstack-meeting14:36
igordcdavidsha: the group*14:36
davidshaigordc: Was just about to correct it!14:37
tmorinigordc: each repo can define one (or more, but usually one) entry point for neutron-db-manage14:37
tmorinon installaion/upgrade neutron-db-manage needs to be called for each neutron-related project14:38
*** artom has quit IRC14:38
tmorinneutron-db-manager --subproject  foo14:38
*** jgu has quit IRC14:38
*** jgu has joined #openstack-meeting14:38
tmorinI don't know if there is a short cut to tell neutron-db-manage to do this for all subprojects14:38
tmorinI haven't investigated deeply yet, but I don't know how to control the order in which subprojects db migration is trigger for the various subprojects14:39
tmorinin devstack14:39
davidshatmorin: Are you proposing ordering the set up to put classifier first?14:39
tmorinthis would be a solution yes14:40
igordcif that was possible it would be nice14:40
tmorinbut this is a topic/question that needs to be shared with the rest of neutron community14:40
davidshatmorin: I don't think this will work, the QoS extension is in neutron's main repo, the neutron repo needs to go first doesn't it?14:40
*** iyamahat has joined #openstack-meeting14:41
*** links has quit IRC14:41
davidshaI think asking if we can add the classification group table to neutron's database migrations is probably the best solution.14:42
*** jgu has quit IRC14:42
*** jgu has joined #openstack-meeting14:43
tmorinsince this table has FK to other CCF tables, this would apply to all tables I think14:43
*** simon-AS5592 has quit IRC14:43
davidshaFor the moment though, we'll keep going with the patch we have and we can change it when we're ready14:44
davidshatmorin: I don't think classification groups do14:44
davidshaNo foreign keys in classification groups: https://review.openstack.org/#/c/498471/12/neutron_classifier/db/migration/alembic_migrations/versions/queens/expand/4e97d48da530_initial_ccf_database_.py14:44
tmorindavidsha: we need to look closely to have an idea if FK are needed, really-better or sugar-on-top14:44
*** iyamahat has quit IRC14:45
tmorindavidsha: ah, ok, indeed the FK with the other is in the other direction14:45
davidshatmorin: ack, you think it's the best way to know if a CG or classification can be deleted though correct?14:46
*** jgu has quit IRC14:46
*** jgu has joined #openstack-meeting14:47
*** fnaval has joined #openstack-meeting14:47
*** yamamoto has joined #openstack-meeting14:47
*** yamamoto has quit IRC14:47
tmorindavidsha: I'm not 100% sure, but it seems hard to prevent races if we don't have FKs: we can have code to check if a consuming project using CG X, and if not then delete,  but in the intermediate time between check&delete, the consuming project may be using it again14:48
davidshatmorin: kk14:49
tmorintmorin: but there may be a way to do without FKs that I haven't thought about14:49
davidshaI'm trying to think of a similar resource and how they do it.14:50
davidshamaybe QoS policies?14:50
*** jgu has quit IRC14:51
tmorinso the thinking was: have FKs to be raceproof, then add hooks so that on failure to delete CG X (because one of the consuming project is using CG X), ask all consuming projects whether and why they use CG X to provide the user with useful feedback on why the CG can't be deleted14:51
*** jgu has joined #openstack-meeting14:51
tmorindavidsha: all QoS stuff is in neutron repo, so they're likely to use FKs14:51
tmorinthe issue is a foreign key to a resource defined outside neutron repo14:52
*** toscalix has joined #openstack-meeting14:55
*** jgu has quit IRC14:55
*** bobmel_ has quit IRC14:55
davidshaI was going to suggest asking mlavalle to join but he isn't in the channel.14:55
*** jgu has joined #openstack-meeting14:55
*** bobmel has joined #openstack-meeting14:55
*** Alex_Staf_ has quit IRC14:56
davidshaIf we have Classification Groups in the core Neutron migration, does this avoid the race condition of neutron-db-manage?14:57
*** VW_ has joined #openstack-meeting14:58
*** cdub has quit IRC14:58
*** janki has joined #openstack-meeting14:58
*** sdague has quit IRC14:59
davidshaWe're going to have to wrap this up14:59
*** jgu has quit IRC14:59
reedip_30 seconds left ...14:59
davidshaThanks everyone for attending!14:59
igordcbye all14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Tue Oct 17 14:59:45 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-10-17-14.00.html14:59
*** jgu has joined #openstack-meeting14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-10-17-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-10-17-14.00.log.html14:59
*** shintaro has quit IRC15:00
*** cdub has joined #openstack-meeting15:00
tmorinbye everyone!15:01
*** VW_ has quit IRC15:01
*** VW_ has joined #openstack-meeting15:01
*** VW has quit IRC15:02
*** bobmel_ has joined #openstack-meeting15:02
*** jgu has quit IRC15:03
*** jgu has joined #openstack-meeting15:03
*** aloga has quit IRC15:04
*** aloga has joined #openstack-meeting15:04
*** bobmel has quit IRC15:05
*** lbrune has quit IRC15:06
*** jgu has quit IRC15:07
*** jgu has joined #openstack-meeting15:08
*** artom has joined #openstack-meeting15:10
*** galstrom is now known as galstrom_zzz15:11
*** edleafe- is now known as edleafe15:14
*** tssurya has quit IRC15:15
*** bollig has quit IRC15:17
*** markvoelker has quit IRC15:17
*** bollig has joined #openstack-meeting15:17
*** markvoelker has joined #openstack-meeting15:18
*** iyamahat has joined #openstack-meeting15:20
*** gongysh has joined #openstack-meeting15:20
*** gongysh has quit IRC15:20
*** markvoelker has quit IRC15:22
*** chyka has joined #openstack-meeting15:23
*** noslzzp has joined #openstack-meeting15:27
*** tssurya has joined #openstack-meeting15:27
*** psachin has joined #openstack-meeting15:29
*** SamYaple has joined #openstack-meeting15:30
*** simon-AS559 has joined #openstack-meeting15:42
*** simon-AS559 has quit IRC15:43
*** wanghao has joined #openstack-meeting15:43
*** mlavalle has joined #openstack-meeting15:43
*** sdague has joined #openstack-meeting15:44
*** chyka_ has joined #openstack-meeting15:45
*** e0ne_ has quit IRC15:46
*** chyka has quit IRC15:47
*** yamamoto has joined #openstack-meeting15:48
*** sdague has quit IRC15:48
*** sridharg has quit IRC15:49
*** fzdarsky has joined #openstack-meeting15:50
*** andreas_s has quit IRC15:52
*** gouthamr has quit IRC15:54
*** gouthamr_ has joined #openstack-meeting15:55
*** yamamoto has quit IRC15:55
*** jlibosva has joined #openstack-meeting15:56
*** lbrune has joined #openstack-meeting15:56
*** toscalix has quit IRC15:56
*** gagehugo has joined #openstack-meeting15:57
*** galstrom_zzz is now known as galstrom15:58
*** slaweq has joined #openstack-meeting15:59
*** boden has joined #openstack-meeting15:59
*** Guest54271 has quit IRC16:00
*** ihrachys has joined #openstack-meeting16:00
ihrachys#startmeeting neutron_ci16:00
openstackMeeting started Tue Oct 17 16:00:41 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
*** pcaruana has quit IRC16:01
ihrachyslots of hands, I love it16:01
ihrachys#topic Actions from prev meeting16:01
*** openstack changes topic to "Actions from prev meeting (Meeting topic: neutron_ci)"16:01
ihrachys"jlibosva to expand grafana window for periodics"16:01
ihrachysstill in review16:01
jlibosvaafaik grafana now doesn't show anything16:02
jlibosvaafter zuul316:02
jlibosvaso maybe we'll need to rebase16:02
ihrachysriiight. I believe haleyb was going to have a look at producing a new one, but there were no data in grafite?16:02
mlavalleyeah, haleyb mentioned it yesterday16:02
haleybihrachys: i don't see any, and have been busy with something else16:03
jlibosvaI accidentally switched topic, sorry :)16:03
haleybdamn customers16:03
ihrachyshaleyb, should someone take it over?16:03
*** VW has joined #openstack-meeting16:04
haleybihrachys: i will ping someone in infra today after my meetings, customer issue not hot any more16:04
haleybunless someone else wants it :)16:04
ihrachysif you can find time for that, keep it. I am only concerned if you don't.16:05
*** sdague has joined #openstack-meeting16:05
ihrachys*if you can't16:05
ihrachys#action haleyb to follow up with infra on missing grafite data for zuulv3 jobs16:06
ihrachysjlibosva, I guess your patch will need to wait for that to resolve16:06
jlibosvathat's what I wanted to point out at the very beginning16:06
ihrachysok, next item was "ihrachys to report bug for trunk scenario failure"16:07
*** VW_ has quit IRC16:08
ihrachysthere is this bug that I believe captures the trunk scenario failures: https://bugs.launchpad.net/neutron/+bug/167696616:08
openstackLaunchpad bug 1676966 in neutron "TrunkManagerTestCase.test_connectivity failed to spawn ping" [Medium,Confirmed]16:08
ihrachysthere is also https://bugs.launchpad.net/neutron/+bug/1722644 but I believe it's different16:08
openstackLaunchpad bug 1722644 in neutron "TrunkTest fails for OVS/DVR scenario job" [High,Confirmed]16:08
jlibosvathe first one is for fullstack?16:09
ihrachyseh, sorry, nevermind, the first is in functional tests16:09
jlibosvaah, no functoinal16:09
ihrachysyeah. I think we had another one.. wait.16:09
jlibosvaihrachys: the second seems legit :)16:09
jlibosvathen somebody opened https://bugs.launchpad.net/neutron/+bug/172296716:09
openstackLaunchpad bug 1722967 in neutron "init_handler argument error in ovs agent" [High,In progress] - Assigned to Jakub Libosvar (libosvar)16:09
ihrachysoh yeah, I mixed things. the first is the legit one, and then there is that init_handler one16:10
jlibosvawhich solves the traces seen in the bug you reported16:10
jlibosvabut then it still fails on SSH issue afaik16:10
ihrachysbtw I haven't seen the error from the init_handler one in logs16:10
ihrachysdoes it happen all the time?16:10
jlibosvaihrachys: perhaps you need to check the other node?16:10
jlibosvaoh, it should happen on both16:11
jlibosvait's there: http://logs.openstack.org/13/474213/7/check/gate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv/752030f/logs/screen-q-agt.txt.gz?level=ERROR#_Oct_10_17_35_10_78787116:11
*** Apoorva has joined #openstack-meeting16:11
jlibosvathat's from the link in 172264416:11
ihrachysI will check again. but anyway, the connectivity failure is still a different one. we had this failure long before.16:11
mlavallefor 1722967, the fix is in the gate: https://review.openstack.org/#/c/511428/16:12
jlibosvaso maybe we could just refresh the info on the 172644 with new traceback :)16:12
ihrachysjlibosva, right. but I haven't seen it in other logs from other runs.16:12
jlibosvamlavalle: thanks for +W :)16:12
mlavallethanks for fixing!16:12
jlibosvaihrachys: anyways, it's fixed by now :) but as far as I can tell it was 100% reproducible as there were wrong parameter passed during initialization of ovs agent16:13
ihrachysok. but we still have connectivity issue on top correct?16:14
jlibosvaI saw those, yes16:14
ihrachysif someone has cycles to have a look at scenario trunk failure, welcome. it's the last failure that keeps the job at 100% failure rate.16:14
ihrachysnext item was "jlibosva to look how failing tests can not affect results"16:15
ihrachysI believe it's about exploring how to "disable" some fullstack tests16:15
ihrachysto make the job voting16:15
jlibosvaI don't have any patch yet but I went through testtools code and found they have a way to set "expected failure" on result16:16
jlibosvabut I think the easiest way would be to decorate test methods and in case they raise an exception, log it and swallow16:16
*** marios has quit IRC16:16
jlibosvaas expected failure means that if the test passes, the final result will be negative16:16
jlibosvaand btw I haven't found any docs on how to set result object for testtools test runner anyways :)16:17
ihrachysjlibosva, so you mean, those test cases will always successful?16:18
*** tmorin has quit IRC16:18
jlibosvaor skipped16:19
jlibosvaso we know if they failed or not16:19
ihrachysjlibosva, you mean the decorator will call self.skip?16:19
ihrachysok that probably makes sense16:19
ihrachysI guess first step is producing the decorator, and then we can go one by one and disable them.16:20
jlibosvaI can craft a patch to try it out16:20
jlibosvayeah, we could disable one test case along with the decorator to see that it works :)16:20
ihrachys#action jlibosva to post a patch for decorator that skips test case results if they failed.16:20
ihrachysok, sorry16:23
ihrachys#topic Grafana16:23
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:23
ihrachyssince we can't use grafana to understand if there are gate issues, is anyone aware of critical gate failures that we may want to discuss?16:24
haleybjust that i broke networking-bgpvpn16:24
ihrachysthe review queue doesn't seem too red, so probably fine16:24
ihrachyshaleyb, how so16:24
jlibosvathere was this bug reported: https://bugs.launchpad.net/neutron/+bug/172425316:24
openstackLaunchpad bug 1724253 in neutron "error in netns privsep wrapper: ImportError: No module named agent.linux.ip_lib" [Undecided,New]16:24
jlibosvait sounds severe :)16:25
haleybthe pyroute2 network namespace changes in neutron broke it, i'm working with tmorin to help get it fixed16:25
slaweqhaleyb: and Heat gate but it's not related :)16:25
jlibosvasounds like that's the bug I just pasted16:25
haleybhttps://review.openstack.org/#/c/503280 and https://review.openstack.org/#/c/500109/16:25
haleybjlibosva: yes, that's the bug16:25
*** sambetts is now known as sambetts|afk16:26
haleybthat's all i had on that16:26
*** psachin has quit IRC16:27
ihrachyshm, ok. which part of the script do they need for privsep?16:27
haleybi'm not exactly sure, but tmorin mentioned the bgpvpn fullstack tests ran as root, and that's the issue16:28
*** simon-AS559 has joined #openstack-meeting16:28
*** VW has quit IRC16:29
*** salv-orl_ has joined #openstack-meeting16:29
ihrachys#topic Scenarios16:30
*** openstack changes topic to "Scenarios (Meeting topic: neutron_ci)"16:30
*** martinkopec has quit IRC16:30
ihrachysin addition to trunk, we had router migration tests that failed, but I think we fixed those with Anil's patches16:30
*** simon-AS5591 has joined #openstack-meeting16:30
ihrachysthe late failed runs look like: http://logs.openstack.org/56/509156/8/check/legacy-tempest-dsvm-neutron-dvr-multinode-scenario/32b6e45/logs/testr_results.html.gz16:30
ihrachystest_floatingip scenarios fail rather often16:31
ihrachyshaleyb, mlavalle is it something that's on radar of l3 team?16:31
haleybbug 1717302 is for that, swami was going to look at it16:31
openstackbug 1717302 in neutron "Tempest floatingip scenario tests failing on DVR Multinode setup with HA" [High,Confirmed] https://launchpad.net/bugs/171730216:31
ihrachysoh nice. I marked it with gate-failure tag16:32
mlavalleand there is another patchset here: https://review.openstack.org/#/c/512179/16:32
ihrachysit's not exactly gate failure since it's non-voting but easier to track16:32
mlavallenot completely sure it is stricty related to this conversation16:32
*** salv-orlando has quit IRC16:32
*** simon-AS559 has quit IRC16:33
*** egallen has joined #openstack-meeting16:33
*** ralonsoh has quit IRC16:33
ihrachysprobably not for scenarios, but worth a look16:33
*** yamahata has quit IRC16:34
*** iyamahat has quit IRC16:34
ihrachysok, seems like we at least track all of failures.16:34
ihrachys#topic Fullstack16:34
*** openstack changes topic to "Fullstack (Meeting topic: neutron_ci)"16:34
ihrachysexcept the idea of skipping some test cases, we also had this patch from jlibosva to isolate fullstack services in namespaces.16:35
ihrachysit's in conflict/wip16:35
jlibosvayeah, I suck16:35
mlavalleno, you don't... lol16:36
jlibosvaI need to continue working on that, I see a big benefit in it16:36
ihrachysif you do, then what do I do?..16:36
ihrachysin other news, armax was looking at the trunk failure for fullstack: https://review.openstack.org/#/c/504186/16:36
ihrachysseems like armax is swamped and may need a helping hand16:37
slaweqI can help with that if it would be fine16:37
ihrachysslaweq, I think it would be fine. I asked him in gerrit just in case.16:37
ihrachysif he doesn't reply in next days nor posts new stuff, I think it's fair to take over.16:38
slaweqok, I will take a look at this16:38
ihrachysslaweq, thanks a lot!16:38
ihrachys#action slaweq to take over https://review.openstack.org/#/c/504186/ from armax16:38
ihrachys#topic Gate setup16:39
*** openstack changes topic to "Gate setup (Meeting topic: neutron_ci)"16:39
slaweqone more thing about fullstack16:39
openstackRemoving item from minutes: #topic Gate setup16:39
ihrachysslaweq, shoot16:39
slaweqI was talking with jlibosva yesterday and I want also to try to run execute with privsep instead of RWD16:39
slaweqjust FYI :)16:39
mlavalleI also have a question16:40
jlibosvawe talked about that in one of previous meetings16:40
jlibosvait's related to one bug16:40
jlibosvathat I'm just searching for :)16:40
slaweqthx jlibosva - I don't have it right now16:40
openstackLaunchpad bug 1721796 in neutron "wait_until_true is not rootwrap daemon friendly" [Medium,In progress] - Assigned to Jakub Libosvar (libosvar)16:40
openstackLaunchpad bug 1654287 in oslo.rootwrap "rootwrap daemon may return output of previous command" [Critical,New]16:40
ihrachysslaweq, that's fine, though wasn't it the idea of privsep to separate privileges (meaning, use different caps per external call?)16:40
*** boden has left #openstack-meeting16:41
jlibosvaif that would be used in tests executor only, does it matter?16:41
ihrachysI thought you meant making execute() somehow grab all caps via privsep and run the command with effective root16:42
slaweqbut as I looked quickly today some other projects are doing something like that with privsep (e.g. os-brick)16:42
slaweqihrachys: I don't know yet how exactly should it be done16:43
ihrachysdoes it mean we will get rid of RWD completely?16:43
slaweqI don't know for now16:43
jlibosvaI was thinking we should use it just to avoid using rwd in wait_until_true16:43
jlibosvaso in fullstack, whenever we're waiting for some resource to be ready16:44
*** jchhatbar has joined #openstack-meeting16:44
*** abalutoiu has joined #openstack-meeting16:44
jlibosvawhich is like a whitebox test thing that is not provided via API16:44
*** VW has joined #openstack-meeting16:44
*** jchhatbar has quit IRC16:45
*** VW_ has joined #openstack-meeting16:45
*** jchhatbar has joined #openstack-meeting16:45
ihrachysok. though it sounds like an uphill battle16:45
ihrachyswhat happened to https://review.openstack.org/#/c/510161/ ?16:45
ihrachyswouldn't it tackle the issue for fullstack?16:46
*** janki has quit IRC16:47
jlibosvahard to say, there are good points about "what if the predicate gets stuck"16:47
ihrachyswe have per test case timeout16:47
jlibosvausing eventlet? :)16:47
ihrachysbut then, we are back to the original problem?16:47
ihrachysthat some state is in buffer16:47
ihrachyson relevant note, anyone talked to oslo folks?16:48
jlibosvaI just had an idea16:48
ihrachysabout the rootwrap behavior16:48
*** VW has quit IRC16:48
jlibosvaIt looks like nobody did16:49
jlibosvaor maybe dalvarez16:49
ihrachysI wonder if it's possible to flush the state somehow before each call to RWD16:49
ihrachysI will follow up with oslo16:50
jlibosvaIIRC he attempted to do that in rwd16:50
ihrachys#action ihrachys to talk to oslo folks about RWD garbage data in the socket on call interrupted16:50
jlibosvaah, he probably didn't send a patch to gerrit16:50
ihrachysI will reach out to him too16:51
ihrachysanything else for fullstack?16:51
mlavallelet's move on16:52
ihrachys#topic Gate setup16:52
*** openstack changes topic to "Gate setup (Meeting topic: neutron_ci)"16:52
ihrachysI had a question on what's next steps for legacy- zuulv3 jobs16:52
ihrachysdo we stick to those for the time being, or should we start moving them to neutron repo/transform into ansible16:53
mlavalleI'd rather start doing it now16:53
mlavalleat least one by one16:53
ihrachysdo we have someone with spare cycles to start exploring that?16:53
*** iyamahat has joined #openstack-meeting16:53
mlavalleI was going to look at it myself16:54
ihrachysI guess once first job is cleared, it should be easier to do next16:54
ihrachys#action mlavalle to explore how to move legacy jobs to new style16:54
mlavallesince it doesn't seem we are under pressure right now16:54
ihrachysyeah, that's good. enough balls to juggle already16:54
haleybyeah, once one patch works can split it up since should be similar16:54
mlavalleyeah, once we do one, the rest should be easy16:54
ihrachysanother thing I had in mind is the dvr-ha job that never became voting16:55
mlavallebut remember, I'll do it slowly16:55
ihrachyshaleyb, is it fair to say that we need fresh grafana data before we assess if the job is ready for primetime?16:55
ihrachysand also with the zuulv3 deal, I suspect we'll need to first move it to new style, only then flip the switch16:56
haleybihrachys: yes, and i'd assume each job change would require a grafana change, and then some waiting to look at falire rates16:56
*** jchhatbar has quit IRC16:56
mlavallelet's do it independently of the job changes16:57
ihrachysmlavalle, not sure infra would love to give us path forward without first moving to new style16:57
mlavalleahhhh, ok16:57
ihrachysbut we'll see16:57
ihrachysanother thing to note is we are stuck at tempest plugin split.16:58
ihrachysthe last patch that was going to introduce new jobs to the tempest plugin repo was: https://review.openstack.org/#/c/507038/16:58
ihrachysand it needs zuulv3 refinement16:58
ihrachysthe concern here is that the longer it takes to switch to test classes from the plugin, the more we diverge from the base that is in-tree16:59
ihrachyssince we continue landing new tests16:59
ihrachysgotta revisit it quick and see if Chandan needs help16:59
ihrachysthe sync later will be a PITA16:59
ihrachyswe are sadly out of time16:59
haleybwe also had a plan to make the multinode job the default and voting, which will have to wait i guess16:59
ihrachysbut I will sync with Chandan16:59
ihrachysyeah, lots of initiatives stalled17:00
ihrachysthat's why it's important to move forward with zuulv3 migration, it's not just for the love of ansible17:00
ihrachysthanks everyone17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Tue Oct 17 17:00:38 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-10-17-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-10-17-16.00.txt17:00
jlibosvathanks, bye17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-10-17-16.00.log.html17:00
slaweqthx, bye17:00
*** tobiash has joined #openstack-meeting17:01
*** tesseract has quit IRC17:02
*** julim_ has joined #openstack-meeting17:03
*** davidsha has quit IRC17:03
*** slaweq has quit IRC17:04
*** julim has quit IRC17:04
*** emagana has quit IRC17:05
*** emagana has joined #openstack-meeting17:05
*** emagana has quit IRC17:07
*** simon-AS5591 has quit IRC17:10
*** yamahata has joined #openstack-meeting17:11
*** ociuhandu has quit IRC17:11
*** jlibosva has quit IRC17:12
*** emagana has joined #openstack-meeting17:13
*** weshay|ruck is now known as weshay|afk_see_r17:14
*** sshank has joined #openstack-meeting17:22
*** dustins has quit IRC17:27
*** bastimalo has joined #openstack-meeting17:28
*** salv-orlando has joined #openstack-meeting17:28
*** sshank has quit IRC17:28
*** bastimalo has left #openstack-meeting17:30
*** anilvenkata has quit IRC17:30
*** salv-orl_ has quit IRC17:32
*** salv-orlando has quit IRC17:32
*** imcsk8 has quit IRC17:34
*** imcsk8 has joined #openstack-meeting17:35
*** ekcs has joined #openstack-meeting17:35
*** mike92 has joined #openstack-meeting17:35
*** ricolin has quit IRC17:37
*** cdub has quit IRC17:39
*** ociuhandu has joined #openstack-meeting17:39
*** ijw has joined #openstack-meeting17:41
*** rwsu has quit IRC17:41
*** mike92 has quit IRC17:44
*** ijw has quit IRC17:45
*** ijw has joined #openstack-meeting17:48
*** bobmel has joined #openstack-meeting17:48
*** caboucha_ has joined #openstack-meeting17:49
*** mike92 has joined #openstack-meeting17:49
*** ijw has quit IRC17:50
*** ijw has joined #openstack-meeting17:50
*** dfflanders has quit IRC17:50
*** caboucha has quit IRC17:50
*** spilla has joined #openstack-meeting17:51
*** gouthamr_ is now known as gouthamr17:52
*** bobmel_ has quit IRC17:52
*** bobmel has quit IRC17:53
*** reedip_ has quit IRC17:53
*** fzdarsky has quit IRC17:53
*** caboucha_ has quit IRC17:54
*** lhx_ has quit IRC17:57
*** imcsk8 has quit IRC17:57
*** imcsk8 has joined #openstack-meeting17:57
*** slaweq has joined #openstack-meeting17:57
lbragstad#startmeeting keystone18:00
openstackMeeting started Tue Oct 17 18:00:02 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
*** 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
lbragstadping ayoung, breton, cmurphy, dstanek, edmondsw, gagehugo, henrynash, hrybacki, knikolla, lamt, lbragstad, lwanderley, kmalloc, rderose, rodrigods, samueldmq, spilla, aselius, dpar, SamYaple18:00
*** baoli has quit IRC18:00
*** baoli has joined #openstack-meeting18:01
*** fzdarsky has joined #openstack-meeting18:01
*** rwsu has joined #openstack-meeting18:02
*** slaweq has quit IRC18:02
*** Apoorva_ has joined #openstack-meeting18:02
lbragstad#topic announcements18:03
*** openstack changes topic to "announcements (Meeting topic: keystone)"18:03
lbragstad#info queens-1 is this week18:03
lbragstadas a result - i'll be looking to schedule a retrospective within the next two weeks to recap queens-118:03
lbragstadi'm thinking we'll just hold it during office hours since folks are used to that time18:03
lbragstad#info specification proposal freeze is this week18:04
lbragstadif there is a spec you're working on that hasn't made it to review yet, be sure to at least push it by the end of the week18:04
lbragstadremember this is only proposal freeze18:04
lbragstadspecification freeze will be queens-218:05
lbragstadwe also have a bunch of trello cards coming due this week18:05
hrybackilbragstad: do we have any proposals we are expecting that haven't appeared yet?18:05
samueldmqlbragstad: is ther eanything on the top of your head we had planned and did not propose a spec for yet?18:05
*** ayoung has joined #openstack-meeting18:05
samueldmqhmm .. .maybe the flask stuff18:05
hrybackisamueldmq +118:05
*** Apoorva has quit IRC18:05
lbragstadhrybacki: samueldmq not that i know of18:05
* samueldmq nods18:06
lbragstadas far as i know, everything we discussed at the ptg has been recorded in trello18:06
lbragstadwe do need to make those changes consistent with the keystone-specs repository18:06
*** jamesmcarthur has joined #openstack-meeting18:06
lbragstad(there are things we've committed to in trello that don't reflect that status in our specs repo)18:07
*** bobmel has joined #openstack-meeting18:07
lbragstadwe have a bunch of things due this week, according to the dates we set in trello18:08
lbragstad#link https://trello.com/c/b5ovuvqG/1-project-tags18:08
lbragstadthe project tags implementation is looking good, imo18:08
*** jamesmcarthur has quit IRC18:09
lbragstadi feel like we can get the server bits merged by queens-1, and all the client bits by queens-218:09
*** jamesmcarthur has joined #openstack-meeting18:09
lbragstadif you have spare review cycles - reviewing the project tags work would be awesome18:09
lbragstad#link https://trello.com/c/25sBHXcM/14-write-up-a-specification-for-json-web-tokens18:10
lbragstadthanks cmurphy for writing up the spec for ^18:10
cmurphyreviews appreciated for that too18:10
lbragstadi think that looks really good18:10
*** jamesmcarthur has quit IRC18:10
lbragstadit'd be awesome to get that targeted for this release, but bandwidth is going to be hard18:11
gagehugoyeah that's on my todo reading list18:11
*** jamesmcarthur has joined #openstack-meeting18:11
lbragstadeither way - the spec does a great job of capturing the information and it should be an easy reproposal18:11
lbragstad#link https://trello.com/c/XTkAiqaB/21-remove-v20-apis18:11
lbragstadthe last thing needed for ^ is a patch to tempest18:12
lbragstadthe v2.0 documentation removal is being tracked in #link https://trello.com/c/5WCMxrLg/12-docs-goals-organization18:12
*** Tom__ has quit IRC18:12
lbragstadbut the removal card should be in Done by EOW so long as #link https://review.openstack.org/#/c/506751/ merges18:12
lbragstad#link https://trello.com/c/Z6pUPEJu/3-oslopolicy-deprecation is getting close - i spent more time than i expected on that last week18:13
cmurphyi also noticed the keystoneclient tests need to be updated after the v2 removal https://review.openstack.org/#/c/512509/18:13
lbragstadcmurphy: aha - i assume there is more cleanup in ksc, too?18:14
lbragstad(cleaning up v2.0 paths, etc...)18:14
*** imcsk8 has quit IRC18:15
lbragstadwhen should we focus on removing those bits?18:15
*** imcsk8 has joined #openstack-meeting18:15
gagehugothat would make removing keystoneclient.session easier18:15
gagehugoremoving the v2 bits18:15
*** abalutoiu_ has joined #openstack-meeting18:15
lbragstadimmediately? or should we allow for a grace period?18:16
lbragstad(if someone still wants to use v2.0 should we force them to use an older client?)18:16
cmurphyactually i don't think it makes sense to remove that from ksc right away18:17
cmurphypeople are more likely to update their clients than their services18:17
lbragstadshould we table v2.0 removal from ksc and ksa for Rocky then?18:17
*** abalutoiu has quit IRC18:19
lbragstadok - i'll create a card in backlog18:19
lbragstad#action lbragstad to create a trello card in backlog to slate v2.0 removal paths from ksa and ksc for Rocky18:19
lbragstad#link https://trello.com/c/ZjsNk84y/4-oslopolicy-scope18:20
lbragstadthis one is iffy18:20
lbragstadi'm going to be working on it today/tonight18:20
lbragstadit's pretty straight forward - but it needs reviews18:20
lbragstadI'm hoping to get it landed in oslo by queens-1 or very shortly after18:20
*** fnaval_ has joined #openstack-meeting18:21
lbragstad#link https://trello.com/c/XzM8IXy4/10-cross-project-policy-work18:21
lbragstadthis isn't necessarily due this week - but using it as a check point18:21
lbragstadlots of patches are in review18:21
lbragstad#link https://www.lbragstad.com/policy-burndown/18:22
lbragstadonly a few projects haven't started18:22
hrybackiwonderful to see more repos in progress than not18:22
lbragstadyeah - i was pretty stoked to see us get through 50%18:22
lbragstadfor folks interested in that - the reviews are super helpful18:23
*** fnaval has quit IRC18:23
lbragstadok - that's all i had for trello status18:23
lbragstadis there anything i missed that folks want to mention?18:23
lbragstad(with regard to what you're working on?)18:24
gagehugocan you filter cards by due dates?18:24
cmurphyit's not committed to in the trello board but i reproposed the app creds spec to queens just to get it in the queue18:24
lbragstadcmurphy: nice - i'll put that in progress18:25
hrybackigagehugo: you can filter by labels18:25
hrybackiso we could make milestone labels and that would allow you to filter properly18:25
gagehugoah ok18:26
gagehugowas just curious18:26
hrybackiohhh you can actually. on the Trello menu, click 'Filter cards' and on the bottom you can pick some premade filters for date ranges18:26
hrybackithat's a new feature to me :)18:26
lbragstad#link https://trello.com/b/5F0h9Hoe/keystone?menu=filter&filter=due:month18:26
lbragstad#topic IAM session scheduling18:27
*** openstack changes topic to "IAM session scheduling (Meeting topic: keystone)"18:27
*** baoli has quit IRC18:27
lbragstad#link https://beta.doodle.com/poll/ntkpzgmcv3k6v5qu18:28
lbragstadbesure to fill that out if you plan to attend18:28
lbragstadi'll propose the session soon - but it will be next week sometime18:28
lbragstadi still haven't heard from zaneb18:28
* samueldmq will make sure to review project-tags again. and jwt18:28
lbragstadso - be on the lookout of that if that's something you want to participate in18:29
lbragstad#topic openstack/loci CI and images18:29
*** openstack changes topic to "openstack/loci CI and images (Meeting topic: keystone)"18:29
lbragstadSamYaple: o/18:29
SamYaplehey all. so a few months back i popped in talking about possibly putting dockerfiles in project repos18:30
SamYaplewe scraped that idea and went with a new project called LOCI18:30
SamYaplegreat success has been made there, and with zuulv3 we now push directly to dockerhub on each commit to openstack/loci18:30
SamYapleour next step is to push images when projects commit themselves18:30
SamYaplewe have done this with cinder already18:31
SamYaple#link https://review.openstack.org/#/c/512398/18:31
lbragstadSamYaple: so you'll bake a new image with each commit to keystone?18:31
SamYapleand push!18:31
lbragstad#link https://github.com/openstack/loci18:31
SamYaplenow, keystone doesnt actually need to do anything here, this is a request from infra that we talk with all the projects before we add a job to thier post pipeline18:32
SamYaplebut because its in the post pipeline, it wont affect keystone gating in anyway18:32
SamYapleso this is more of a social question than a technical one, is keystone ok with a loci job in the post pipeline?18:32
*** rwsu has quit IRC18:32
lbragstadi don't have an issue with it - the post pipeline seems like the appropriate place for something like this18:33
SamYapledoes anyone have any questions or concerns about this?18:33
*** hemna_ has quit IRC18:34
samueldmqseems awesome18:34
lbragstadSamYaple: how is keystone setup in the container?18:34
samueldmqwhat's the ultimate goal of this?18:34
SamYaplesamueldmq: better CICD18:34
SamYaplelbragstad: pip installed18:34
samueldmqrun devstack in containers ? and then run the tests?18:35
lbragstadrunning with Apache?18:35
SamYaplelbragstad: you can optionally install apache218:35
SamYaplewe actually use bindep to select profiles18:35
samueldmqlike, create an image of keystoen each time dependencies change. ci can be: install lastest image (with deps preinstalled), just put the code in18:35
samueldmqand run the tests18:35
*** baoli has joined #openstack-meeting18:36
SamYaplesamueldmq: we were just talking about that in the channel. i would love to get devstack using loci images, optionally,18:36
SamYaplethere is a time delay between merge and post job that might make it bad for gates, but it should be fine for general dev18:36
lbragstadsounds interesting18:37
knikollathat sounds very cool18:38
cmurphywhere does it publish to? tarballs.o.o?18:38
SamYaplelbragstad: we only install uwsgi by default, but `docker build https://github.com/openstack/loci.git --build-arg PROJECT=keystone --build-arg PROFILES="apache"`18:38
SamYaplecmurphy: dockerhub18:38
lbragstadSamYaple: aha - nice18:38
cmurphySamYaple: so what if dockerhub is down? does that delay the gate job?18:38
SamYaplewe actually had to get some new syntax into bindep to get this to work but https://review.openstack.org/#/c/512063/3/bindep.txt18:38
SamYaplecmurphy: not at all. this is post pipeline18:39
*** electrofelix has quit IRC18:39
cmurphyokay, no objections from me :)18:39
SamYapletechnically the post job can fail and we wont push for that commit, so there is a small risk of not pushing, same with not publishing tarballs18:39
lbragstadso you only push what you bless through testing18:40
SamYapleunfortunately, zuulv3 doesnt have that part figured out yet18:40
SamYapleso no matter what we test, what we push is "build only"18:40
SamYapleonce zuulv3 lets us share artifacts across jobs then testing and pushing can work18:40
lbragstadyeah - i'm good with this then18:41
lbragstadlet us know if you need signoff on a commit18:41
SamYapleok i will submit the patch to project-config and ask for a signoff in the channel18:41
*** dustins has joined #openstack-meeting18:41
lbragstadawesome - thanks SamYaple18:41
*** vishwanathj has joined #openstack-meeting18:41
SamYaplethanks all! and if you ahve more questions, #openstack-loci18:41
lbragstadwill do!18:41
lbragstad#topic open discussion18:42
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:42
lbragstadfloor is open18:42
lbragstadgentle reminder that office hours will be happening today18:42
*** cleong has quit IRC18:42
*** imcsk8 has quit IRC18:42
*** imcsk8 has joined #openstack-meeting18:43
lbragstadwe can focus on bugs or use the time to crush some spec reviews together18:43
*** Apoorva_ has quit IRC18:43
*** VW_ is now known as VW18:43
*** Apoorva has joined #openstack-meeting18:43
*** rwsu has joined #openstack-meeting18:45
lbragstadif there is nothing else - we can break for a bit before office-hours18:45
lbragstadthanks for coming!18:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:46
openstackMeeting ended Tue Oct 17 18:46:15 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-10-17-18.00.html18:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-10-17-18.00.txt18:46
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-10-17-18.00.log.html18:46
*** gagehugo has left #openstack-meeting18:47
*** emagana has quit IRC18:51
*** AJaeger has joined #openstack-meeting18:54
*** VW has quit IRC18:55
*** VW has joined #openstack-meeting18:55
*** imcsk8 has quit IRC18:58
clarkbhello infra18:59
*** imcsk8 has joined #openstack-meeting18:59
*** Namrata has quit IRC18:59
*** spilla has left #openstack-meeting18:59
zaneblbragstad: done18:59
clarkb#startmeeting infra19:00
openstackMeeting started Tue Oct 17 19:00:13 2017 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: infra)"19:00
openstackThe meeting name has been set to 'infra'19:00
clarkb#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:00
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
clarkbTC election is happening now. Don't forget to vote19:02
*** slaweq has joined #openstack-meeting19:02
clarkbAnd late Sunday we put zuulv3 back into production (where it has been since)19:02
AJaegerand running nicely!19:02
dmsimardIt went better than the first time :D19:02
dmsimardProps to all the hard work19:03
fungiyes, it's running amazingly!19:03
dmsimardThanks for beta testing zuul v3 so we don't run into that kind of problem when we roll it out for RDO :D19:03
clarkbyup much much happier this time around19:04
clarkbthere weren't any actions from last meeting19:05
clarkband I don't think there are any specs to talk about so skipping ahead19:06
clarkb#topic Priority Efforts19:06
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:06
clarkb#topic Zuul v319:06
*** openstack changes topic to "Zuul v3 (Meeting topic: infra)"19:06
clarkbthere were a couple items we wanted totalk about post productioning.19:06
clarkbThe first is whether or not we should be backing up secret keys for v3 secrets19:06
clarkbjeblair: ^ you added this one to the agenda19:07
clarkbbasically people are wodnering what the bus factor of their secrets in zuul is19:07
pabelangerseems like a good idea19:07
clarkbinfra roots have the ability to decrypt these secrets so that helps bus factor but if we lose the private keys we won't be able to decrypt the secrets anymore19:07
pabelangerwould that be just adding it to bup?19:08
clarkbpabelanger: ya I'm leaning towards backing them up simply because it will help avoid functionality outages if we lose them for some reason (everyone will have to rekey)19:08
tobiashI experimented a bit about deriving them from a master key (because I want to avoid a backup)19:08
jeblairsorry i'm late19:08
jeblairyeah.  we could tell folks that if we lose the server, they'll need to update their secrets.19:09
ianwit is an additional "data at rest" exposure ... but there's already interesting stuff "at rest" in there anyway?19:09
*** hemna_ has joined #openstack-meeting19:10
jeblairhowever, i think that looks kind of bad, so i lean toward us backing them up19:10
persiaDo I understand correctly that the data that is being considered for backup has already been posted to gerrit reviews when added (in encrypted form)?  If so, I would argue backing it up is no less secure.19:10
jeblairianw: that's true19:10
fungii suppose that puts infra in the (unfortunate?) position of being the keeper of everyone else's keys, in case they forget them?19:10
clarkbpersia: its the secret keys needed to decrypt the data that has already been put in git19:10
SamYaplepersia: no this would be the secret keys to decret that data19:10
jeblairtobiash: i really like that idea -- if it's just one key, that opens up more options (offline storage, etc)19:10
clarkbfungi: its already that way, zuul generates the keys not the user aiui19:10
jeblairfungi: yes; we sort of already are though.  because of what clarkb says19:10
pabelangerpersia: no, this data is just stored on HDD of zuulv3.o.o currently19:11
jeblairpersia: so it's an additional exposure.  currently the secret keys are only on the zuul server; they would additionally be in our backups19:11
tobiashI have a script which takes a private key an main.yaml and generates the keys for every repo19:11
fungiclarkb: right, i mean you have a team responsible for access to some service, they give us an encrypted copy of that, then they have a lot of team turn-over and one day they discover they need to make some adjustments to the service but no longer know the (plaintext) password/whatever19:11
persiaGiven that architecture, I think it should be backed up, as one HDD is an unreliable store.  Ideally, it is encrypted for backup, with the decryption keys more widely known (maybe infra-root private keys stored on private infra?)19:12
pabelangerwhat about moving zuul keys in to hiera, and having ansible manage them? Like any other secret we add to a server19:12
tobiashI can share it tomorrow if there is interest19:12
jeblairpabelanger: we need a new key for every project.19:12
fungithey'll end up asking the infra team to decrypt our copy and provide it to someone because they didn't keep track of it themselves well enough19:12
clarkbfungi: thats a good point19:12
clarkbit might be worth backing up the keys just to avoid zuul "outages" if we lose them forcing everyone to reencrypt but at the same time ask teams ot have some other method of data retention for their own purposes?19:13
fungii don't know that's necessarily something we can (or want to?) avoid19:13
jeblairtobiash: yeah, if you could post that, that'd be great; let's take a look at it and see if we should redesign the key generation in zuul for that.19:13
pabelangerjeblair: yah, i can also see that being a bottleneck for adding new projects19:13
dmsimardfungi mentions turn over which is an interesting bit -- if we revoke an infra-root access, do we have to rotate the key used to decrypt secrets ? How does that work ?19:13
fungibut we may still want to remind people very plainly in documentation that we're not taking on the responsibility of being the long-term storage for their account credentials in case they lose them19:13
jeblairclarkb, fungi: yes, as a matter of policy, i don't think we should decrypt anything for folks.  we don't really have a good trust path.  i think we should mostly focus on how this affects our service.  i mostly don't want egg on our faces.  :)19:14
persiaFor mass outages, decrypting from backup is nice.  For individual outages, probably best to advise the project to rekey (unless they have a really good reason not to do so), to reduce the number of times infra folk have to see project secret keys.19:14
jeblairdmsimard: only if we decide we don't trust the person any more.  that hasn't happened yet.19:14
fungiwe just happen to have copies so their jobs can use them19:14
jeblairdmsimard: however, we *do* want to be able to do key rotation eventually.  zuulv3 doesn't support that yet.19:14
pabelangerdmsimard: true, but we have that problem today with our cloud credentials too19:14
dmsimardjeblair: fair enough19:14
ianwdmsimard: i don't think we've rotated all the cloud keys etc on removal, but i don't think anyone has left in circumstances they're considered compromised19:14
*** simon-AS559 has joined #openstack-meeting19:15
clarkbok how about we make the assertion in documentation thta fungi suggests. Then also backup the keys so that we don't break people's jobs if we derp on our end19:15
ianw++ and investigate the single key thing from tobiash19:15
jeblairclarkb: ++.  then let's look at tobiash's idea and see if we want to change how we do this later.19:15
fungipersia: yes, i agree. mostly wanting to avoid the situation where they'velocked themselves out of some account and want us to help them recover from that because we have a copy of the credentials they've forgotten19:15
persiafungi: I fully support your recommendations for documentation :)19:16
SamYaplei only brought it up for the hit-by-a-bus scenario19:16
clarkb#agreed Document that we are not serving as backups for $project secrets. Backup the keys so that breakage on infra end doesn't force everyone to reencrypt their secrets.19:16
clarkbif anyone disagrees with ^ let me know and I can undo19:16
persiaIf nothing else, I suspect infra-root has no reliable way to identify whether a key requestor represents an identity that should be permitted the key.19:16
*** simon-AS5591 has joined #openstack-meeting19:17
jeblairpersia: yep, that's a substantial blocker19:17
ianwpersia: if they can't keep the key, i bet they can't keep a gpg key or something to authenticate anyway :)19:17
jeblairclarkb: ++19:17
persiaYes, hence the documentation should assert that infra-root *will not* provide secret keys to others, rather than just that this isn't the purpose of the backup.19:17
fungiSamYaple: yes, if your project lead is hit by a bus and is the only one who knew the password, that's bad (and not something you should expect us to protect you from)19:17
*** simon-AS559 has quit IRC19:18
SamYaplefungi: no argument here. it was a question of if we could rely on infra for that. the answer is "no". perfectly acceptable :)19:18
persiaIf a project is concerned about bus-factor, presumably the project lead can (securely) transmit the secret to a delegate.  Worst case, project rekeys.19:18
pabelangernot to derail, but which password are we talking about? I don't think our keys support that today, right?19:19
jeblairpabelanger: the "password" that a user has encrypted as a secret19:19
fungii'll leave myself a todo to draft up a blurb for the openstack-specific job documentation we have19:19
pabelangerjeblair: Ah, thank you19:20
clarkbfungi: thanks19:20
ianwi can look at the backups if nobody else wants too19:20
clarkbthe other topic that fungi brought up was how safe is it to modify scripts that v2 was using so that they function with v319:20
fungipabelanger: basically discouraging abusing people relying on zuul as an encrypted safe for their service credentials in case they forget them later (because we can't safely be that)19:20
jeblairianw: thanks19:20
clarkbianw: thanks, I think that would be helpful19:20
ianwok, will do19:21
pabelangerfungi: yah, I personally don't want to know what that data is :)19:21
clarkb#action fungi write up docs for secret backup policy19:21
fungithanks clarkb19:21
clarkb#action ianw look into backing up zuul secrets19:21
*** simon-AS559 has joined #openstack-meeting19:21
jeblairi think there's 2 related questions:19:21
jeblair1) when do we demolish the v2 servers19:21
jeblair2) when do we demolish the v2 config19:21
fungii think 2 happens before 119:22
fungibecause 2 is easier to undo (it's "just" a matter of git reverts)19:22
fungionce we 1, going back is _much_ harder19:22
clarkbif we want ot be ultra conservative we could say after the feedback session in sydney just in cse there is some really important thing brought up19:23
fungi(it's "just" a matter of rebuilding a bunch of servers)19:23
clarkbbut ya worst case we just rebuild servers and git revert19:23
*** simon-AS5591 has quit IRC19:23
jeblairi think the configs have diverged so much that we can't really entertain the idea of supporting both any more19:23
ianwi was finding the v2 config helpful as a comparison during initial transition, but not so much now19:23
clarkbianw: ya that was useful for the thing funig was debugging today too19:23
clarkbbut git log -p is a hammer to get that data back19:24
pabelangerwe also have new servers to build, like migrating nodepool-builders to python319:24
jeblairso honestly, i lean toward saying keep the servers up until next week, but probably within a few days, declare the config dead and remove it.  (it's in the git history for reference)19:24
fungido we really expect that if we're still on v3 by the time the forum rolls around (seems likely this time) then is there anything anyone is likely to say there to cause us to go back to v2?19:24
*** slaweq has quit IRC19:24
clarkbfungi: no19:24
pabelangerjeblair: ++19:24
jeblairi personally think we passed that point yesterday :)19:24
fungiclarkb: yes, i can easily git checkout an older commit ;)19:24
fungiif a similar question arises19:24
jeblairbut am willing to entertain the idea that something catastrophic could still happen this week that would warrant us going back19:25
pabelangerYah, I'd be shocked if we decided to rollback now19:25
dmsimardfungi: unless someone force pushes :P19:25
ianwjeblair's plan ++19:25
pabelangerlike we had a large gap in testing19:25
fungidmsimard: yeah, let's not (is my answer to that)19:25
clarkbjeblair: ya that is reasonable. We should probably send an email with those dteails to the dev list with a strong "speak up now" message if someonebelieves we need to revert19:26
pabelangernext week also works well for me, as I am traveling to conference for next 3 days19:26
fungioh, so here's one potential impact... is jjb still testing against our project-config data?19:26
jeblairfungi: you okay cutting off our retreat (or at least making it really difficult) next week?19:26
*** markvoelker has joined #openstack-meeting19:26
clarkbmostly concerned that there seemed to be more fuming than communication the last time around so want to be careful to give everyone a chance to speak up19:26
AJaegerfungi: no, not anymore19:27
dmsimardThe only thing I could see considering a rollback could be a security concern of sorts (like a nodepool or executor exploit), but it'd be hard to believe it could not be mitigated quickly or we shut things down temporarily while we address the issue19:27
fungijeblair: yes, i'm full steam ahead19:27
AJaegerfungi: jjb testing was not enabled with v3.19:27
AJaegerfungi: I can make the freeze test from non-voting to voting19:27
jeblairAJaeger: shouldn't there be a legacy job?19:27
fungiAJaeger: oh, they're not running jobs on jjb changes any longer?19:27
AJaegerAFAIK those don't run currently - but we should be able to do that...19:27
pabelangerclarkb: yah, I haven't heard of any fuming this time around19:28
AJaegerI can patch - either freeze them or gate on jjb. What's the preference?19:28
fungianyway, the jjb team may want to copy a representative sample of configuration from a pre-deletion point in the project-config history, for use in their testing (assuming they still rely on it)19:28
jeblairAJaeger: we're talking about jobs that run on the jjb repo, right?19:29
AJaegerjeblair: no, I talk about jobs running on project-config/jenkins/19:29
* fungi is specifically talking about jobs running against changes to the openstack-infra/jenkins-job-builder repo19:30
AJaegerthen ignore me...19:30
jeblairfungi: so to the original question, i think maybe avoiding changing the jenkins scripts (at least in an incompatible way) until week would be good?19:30
jeblairfungi: though of course, those jobs really just need to be replaced anyway... so maybe the v3 fix should be to copy the script into a role and iterate from there or something...19:31
AJaegerjust checked, jenkins-job-builder has jobs running - python-jobs basically19:31
fungithey did, at least at one point, test against a copy of our configuration to avoid breaking us, which if we're past the point of no return on v3 is no longer necessary for us but deleting those files could disrupt their jobs if they're still doing it that way19:31
fungibut sounds like maybe they stopped after we pinned to an old release?19:31
clarkbjeblair: the copy idea makes sense to me19:32
clarkbjeblair: as that sounds like a prereq to deleting everything anyways19:32
AJaegerfungi: I don't see such a job currently for the jjb repo19:32
fungiyeah, i don't see the old validation jobs running against jjb changes in the v3 config19:32
fungiso this is probably a moot point19:33
jeblairclarkb: indeed19:33
pabelangeryah, we could start moving jenkins scripts directly into playbooks, that worked well when then started migrating them to ansible19:34
clarkbSo keep old servers and config around for another week. Migrate scripts used from jenkins/scripts into playbooks. Send email now telling people we plan to completely delete v2 (as much as you can with git) next week and to speak up now with concerns?19:34
fungi#link https://review.openstack.org/37804619:35
fungithat's when they were removed, looks like19:35
*** awaugama has quit IRC19:35
pabelangerso, would we be moving them in to ozj? And if so, it would make iterating on them much easier19:35
clarkb#agreed Keep old servers and config around for another week. Migrate scripts used from jenkins/scripts into playbooks. Send email now telling people we plan to completely delete v2 (as much as you can with git) next week and to speak up now with concerns.19:35
pabelangeras long as they are not needed in trusted context19:36
clarkbagain let me know if you don't agree with ^ :)19:36
dmsimardclarkb: could we make a tag before deletion ?19:36
dmsimardclarkb: like jenkins-eol or something19:36
clarkbjeblair: do you want to send the its done/dead Jim email?19:36
dmsimardto make things easier if we want to look for it.19:36
jeblairheh, have we ever tagged project-config?19:36
clarkbjeblair: I don't think so, but I suppose we can, we can also tag it at any point in the future too19:37
*** rbudden has joined #openstack-meeting19:37
jeblairclarkb: sure i'll send it, but i won't be able to say "It's dead, Jim."  :(19:37
dmsimarda tag is just a friendly label on a commit sha119:37
dmsimardand easier to find :)19:37
*** slaweq has joined #openstack-meeting19:38
jeblairi'm okay having our first-even tag on project-config19:38
clarkbya makes diffing easier to have a friendly name19:38
jeblairfirst ever even19:38
clarkbgit diff HEAD..jenkins-eol19:38
* dmsimard nods19:38
dmsimardSwitching from laptop to phone for a bit, will follow along.19:39
jeblairlike 'farewell sydney monorail'19:40
clarkbok sounds like we have a plan. Any other v3 related items?19:40
*** slaweq has quit IRC19:40
clarkbwe are running out of time and there are some other things on the agenda19:40
*** slaweq has joined #openstack-meeting19:41
clarkbok moving on19:41
clarkb#topic General Topics19:41
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:41
clarkb#topic Ansible swap setup19:41
*** openstack changes topic to "Ansible swap setup (Meeting topic: infra)"19:41
clarkb#link https://review.openstack.org/#/c/499467/19:41
clarkbianw: ^ this is yours, are you just looking for reviews?19:41
ianwwell i was thinking, why does only d-g want swap?19:42
ianwis it something we should move to the base job, behind a variable flag?19:42
ianwis that a thing we are doing?19:42
*** mlavalle has left #openstack-meeting19:42
ianwwe sort of have one flag in the "generate ara on failure" atm?19:42
jeblairi think we should make it a role in one of the zuul*-jobs repos, but not put it in the base job19:42
*** weshay|afk_see_r is now known as weshay|ruck19:42
pabelangerwe'll, I've wanted to use it for launch-node.py too19:43
jeblairianw: that flag isn't meant to be user-serviceable19:43
jeblairi don't think our base jobs should end up being driven by variables; i think we should structure playbooks to use appropriate roles19:43
jeblair(in other words, try to keep things more like ansible and less like zuul magic)19:44
*** jamesmcarthur has quit IRC19:44
* fungi agrees19:44
ianwok, the only thing was didn't want people missing it, and causing skew in jobs running with and without it19:44
dmsimardI kind of want to put it in the base job19:45
dmsimardBecause it otherwise means that the config is not the same for all jobs19:45
jeblairi can see how swap is certainly in a gery area.19:45
dmsimardDepending on the provider19:45
fungii think people should only add it to jobs that need it19:45
clarkbfungi: ya for swap I think ideal is jobs never swap19:45
fungisince swap setup will add some time and i/o19:45
clarkbso we only opt jobs into it if they need it19:45
dmsimardFair, it can be opt in19:46
ianwso move it out of d-g into o-z-j seems like the plan ... and then ensure that d-g is turning it on19:46
clarkbianw: yup19:46
ianwalright, will do /eot19:47
clarkb#topic Unbound setup19:47
*** openstack changes topic to "Unbound setup (Meeting topic: infra)"19:47
clarkboh do I need to undo?19:47
openstackRemoving item from minutes: #topic Unbound setup19:47
jeblairthere's a change to move the v3-native devstack job into the devstack repo19:47
clarkbapparnetly that doesn't reset the channel topic19:47
jeblairit probably has a fork of the swap role19:47
clarkbah right19:47
jeblairor maybe not, i'm not sure19:47
ianwjeblair: it's not committed yet, and i don't think it was copied in when i looked19:48
clarkbok so also need to check if it needs to be in devstack or update devstack19:48
jeblairat any rate, i think the thing to do is to put that role into ozj, use it in v3-native devstack job in devstack repo, and ignore devstack-gate.19:48
jeblairbasically, don't spend any more time polishing ansible in devstack-gate; focus on v3-native devstack instead19:48
ianwok, that sounds like a plan19:49
fungigood plan19:49
clarkbok next topic then19:49
clarkb#topic Unbound setup19:49
*** openstack changes topic to "Unbound setup (Meeting topic: infra)"19:49
ianwjust another quick one from me19:49
clarkb#link https://review.openstack.org/#/c/512153/19:49
ianwthis *was* in base ... caused problems19:49
ianwdo we want it back?  i mean, we're running without it and is it causing issues?19:49
ianwi know there was a lot of pain figuring it out in the first place19:49
fungiunbound was added to deal with intermittent issues19:50
jeblairi think we needed it for... rax?  because of their dns blacklist?19:50
clarkbwe have had dns resolution failures in some clouds19:50
clarkbjeblair: yes that was the origination of it19:50
AJaegersorry, late to the party: https://review.openstack.org/#/c/508906/ is merged and is the change that moves devstack job into devstack19:50
clarkbI think we likely do want to make sure unbound is present on test nodes and caching19:50
ianwso this is the dynamic setup bit, the ipv6/ipv4 resolvers19:50
fungiand i think we're not yet back to a point where we have similar levels of openstack-health and elastic-recheck history on v3 to be able to say it's unneeded19:50
clarkbianw: ya that was to address problems with osic where we resolved via v4 through nat and that was flaky19:51
jeblairi don't think i've heard anything about that problem being fixed... in fact, last i heard was still "yep, that's a problem".  so we may want to assume it's still (when we least expect it) necessary.19:51
clarkbI'm not aware of any clouds with that setup today but we may have that setup in the future ?19:51
ianwok, do we want to merge it then?  i'm just wary of adding things to base jobs in this transition period19:51
clarkbI'm in favor of it since that was a really annoying dns problem to debug and fix. I think if we have a fix we should keep applying it to avoid the problem in the future19:52
ianwi've put in testing notes, if people belive them19:52
*** e0ne has joined #openstack-meeting19:52
fungithanks ianw!19:53
jeblair+2 from me19:53
clarkbI'll review that today if I have time before the dentist19:53
clarkb#topic Nominated new config cores19:53
*** openstack changes topic to "Nominated new config cores (Meeting topic: infra)"19:53
ianwi've unworkflowed it since i just wanted to discuss it, review at leisure then, thanks19:53
clarkbJust a heads up I nominated frickler jlk dmsimard and mnaser to be project-config and ozj and zuul-jobs cores19:53
AJaegerwelcome new cores. There're quite a few open reviews waiting for you ;)19:54
clarkbI'd like to give them the +2 power sooner than later so if you want please respond to that thread19:54
fungiwelcome and thanks to our new job config core reviewers!19:54
clarkbI have not yet added them to groups but response here seems to indicate I should just get that over with :)19:54
dmsimardthread is here: http://lists.openstack.org/pipermail/openstack-infra/2017-October/005613.html19:54
jeblairoh that's me.  /me sends email now19:54
AJaegerclarkb: really more time? Go for it ;)19:54
fungiclarkb: you're being so public about additions--i just added them in the past and announced it ;)19:54
clarkbfungi: ha19:55
*** jamesmcarthur has joined #openstack-meeting19:55
clarkbok I'll try to sneak that in before the dentist too19:55
clarkb#topic Project Renames19:55
*** openstack changes topic to "Project Renames (Meeting topic: infra)"19:55
AJaegerclarkb: do you want to cleanup the list as well? Some people are "retired"...19:55
clarkbAJaeger: I think fungi was working on that, I will sync up with him on that19:55
fungiahh, yeah. it's still on my to do list19:55
clarkbok last week we tentatively said lets aim for 10/20 for projects renames and see where we are at post zuulv3 deployment19:55
fungii'm still good with 10/2019:56
clarkbEven though the deployment went well I'm feeling swamped with general pre summit stuff, v3 job fixes and other fixes. I worry that I won't have to ability to get prep work done.19:56
clarkbif others are able to take that on that would be great19:56
*** fzdarsky has quit IRC19:56
ianwif we're stopping gerrit, i might try that swap-out of infra-specs repo too19:56
clarkb(also I'm told no TC meeting today so I think we'll go a few minutes long to cover all the things)19:57
ianwthe corrupt one19:57
dmsimardOh wow Sydney is Nov 6th, I didn't realize it was so soon19:57
ianwwhat time is it scheduled?19:57
clarkbianw: last meeting we said plan for 1600UTC but we can move that to accomodate you19:57
pabelanger10/20 should work for me19:58
jeblairi don't have bandwidth to drive the rename but can support it.19:58
clarkbjeblair: same here. I can be around on friday and help push buttons but worried I won't have time to help with prep19:59
clarkbdo we have volunteers to do the prep work and be ready for friday to do it?19:59
clarkbsounds like maybe fungi ianw and pabelanger ?19:59
* pabelanger checks calander20:00
ianwi can help with prep, but it's like 3am for me, but pabelanger can drive?20:00
fungiyeah, i can pick it up20:00
clarkbianw: well I think we can shift it to later in the day too (also it is your saturday)20:00
clarkbfungi: cool thanks20:00
pabelangerI don't think I'll be able to start prep until 20:00 UTC, due to flight20:00
clarkbI guess last question then is what time should we do it?20:01
*** armax has quit IRC20:01
clarkbianw: would you be around for fixing nova-specs if it was later in the day (no pressure since esaturday)20:01
ianwif it's before about 9am my time that's ok (after that i have to play taxi for kid stuff)20:02
jlvillalIf anyone is bored and wants to review: https://review.openstack.org/#/c/509670/  This allows seeing the CRITICAL log level messages, if someone selects a log level to view. Has one +2 :)20:02
clarkbianw: what is that in UTC? 20:00?20:02
* clarkb is bad at timezone math20:02
ianwyeah we just switched to daylight saving which throws me out20:03
ianwbefore 22:00UTC20:03
*** slaweq has quit IRC20:04
dmsimardAre we 4 minutes overtime ?20:04
clarkbdmsimard: we are, but no TC meeting so hping to go over a few minutes and get this done20:04
clarkbfungi: pabelanger ianw should we say 2000UTC then?20:04
clarkbon Friday 10/20?20:05
fungithat wfm20:05
dmsimardmaking sure there's no one looking through the window of the meeting room with menacing eyes :)20:05
clarkb#agreed project renaming to commence at 2200UTC Friday 10/2020:05
clarkb#topic open discussion20:05
*** openstack changes topic to "open discussion (Meeting topic: infra)"20:05
clarkbianw had an item for this20:05
ianwclarkb: 2000 right?20:05
fungiianw: yes20:06
clarkboh yes20:06
clarkbcan I double undo?20:06
openstackRemoving item from minutes: #topic open discussion20:06
openstackRemoving item from minutes: #agreed project renaming to commence at 2200UTC Friday 10/2020:06
clarkb#agreed project renaming to commence at 2000UTC Friday 10/2020:06
clarkb#topic open discussion20:06
*** openstack changes topic to "open discussion (Meeting topic: infra)"20:06
ianwit's not important, but if we're not getting kicked out20:06
fungithere's nobody waiting in the hallway20:06
ianwconference schedule seems full, but is there interest in an infra-specific evening?20:07
clarkbI think it would be nice to get out for dinner/drinks one evening20:07
dmsimardI'll take a sec to thank you for core nomination, means a lot to me :D20:07
clarkbwe can put up an etherpad and people can mark down availability20:07
clarkbianw: is that something you want to help organize being local?20:08
* fungi trusts ianw to recommend australian cuisine20:08
ianwyeah, i was thinking maybe something more on the move if people want20:08
ianwcatch a ferry, walk across the bridge, hit a pub in the rocks type thing?20:08
ianwor, i can just find a sit-down option too20:08
fungiyes please20:08
fungito either20:08
clarkbianw: I trust your judgement, that sounds awesome20:08
dmsimardnothing with venomous animals or critters :P20:09
fungii'm good with the "hit a pub" option especially, but happy to do whatever20:09
jeblairdmsimard: let's not overly limit our options!20:09
*** julim_ has quit IRC20:09
clarkbwhy don't we put up an etherpad to list availability and ianw can list options there?20:09
ianwalight, i'll do an etherpad and send something20:09
fungidmsimard: that may eliminate much of that country20:09
clarkbawesome thanks!20:09
dmsimardI unfortunately won't be at the summit, but you guys have fun :)20:09
clarkbdmsimard: we'll miss you20:09
clarkband with that our meeting is 10 minutes over and I think done20:10
clarkbthanks everyone20:10
fungithanks clarkb!20:10
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:10
openstackMeeting ended Tue Oct 17 20:10:07 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:10
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-10-17-19.00.html20:10
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-10-17-19.00.txt20:10
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-10-17-19.00.log.html20:10
*** fzdarsky has joined #openstack-meeting20:10
*** tobiash has left #openstack-meeting20:11
*** e0ne has quit IRC20:13
*** e0ne has joined #openstack-meeting20:13
*** egallen has quit IRC20:14
*** markvoelker_ has joined #openstack-meeting20:15
*** markvoelker has quit IRC20:18
*** e0ne has quit IRC20:19
*** ijw has quit IRC20:24
*** pchavva has quit IRC20:25
*** abalutoiu_ has quit IRC20:26
*** armax has joined #openstack-meeting20:36
*** raildo has quit IRC20:37
*** lbrune has quit IRC20:39
*** rbudden has quit IRC20:45
*** artom has quit IRC20:46
*** ijw has joined #openstack-meeting20:52
*** sapd__ has joined #openstack-meeting20:53
*** sapd_ has quit IRC20:53
*** emagana has joined #openstack-meeting20:54
*** xyang1 has quit IRC20:56
*** dustins has quit IRC20:56
*** david-lyle has quit IRC20:57
*** bobh has quit IRC20:59
*** oneswig has joined #openstack-meeting20:59
oneswig#startmeeting scientific-wg21:00
openstackMeeting started Tue Oct 17 21:00:28 2017 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: scientific-wg)"21:00
openstackThe meeting name has been set to 'scientific_wg'21:00
oneswig#link agenda for today https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_October_17th_201721:00
oneswigerr... hello21:01
*** ijw has quit IRC21:01
*** galstrom is now known as galstrom_zzz21:03
*** b1airo has joined #openstack-meeting21:03
oneswigb1airo: morning.21:04
oneswig#chair b1airo21:04
openstackCurrent chairs: b1airo oneswig21:04
b1airoHi oneswig21:04
oneswigQuiet one so far :-)21:04
*** simon-AS559 has quit IRC21:04
oneswigWas hoping to hear about your recent work and the RoCE tuning you've been doing.21:04
b1airoYeah and I am in Brisbane for a conference, so not all here I'm afraid21:05
oneswigNot to mention NVLink in KVM - saw your talk intro - woah there.21:05
b1airoWe hit some me MOFED bugs, always fun21:05
b1airo*new MOFED21:06
b1airo(stupid phone keyboard)21:06
oneswigWas this related to your krazy SR-IOV over a bond thingy?21:06
b1airoWell the nvlink stuff is interesting, it pretty much just works21:06
b1airoNo, we found MPI bombed out on some newer nodes (Broadwell) when getting to 28 procs21:08
*** sdague has quit IRC21:08
oneswigb1airo: I think I'll have to come along.  So if I pass through 3 GPUs, they can do NVLink for GPU-direct between them in the virtualised context?21:08
*** gouthamr has quit IRC21:08
b1airoWas due to a memory/resource exhaustion issue in the driver with FCA enabled (which is default with MXM)21:09
oneswigb1airo: 28 procs is basically 1 node, right?21:09
oneswigplus or minus a few21:09
b1airoThat's right oneswig - or even 8 GPUs if you happen to have a DGX-121:09
b1airoNice devstack platform that21:10
oneswigHey bollig21:10
bollighey all21:10
b1airooneswig: yep one e5-2680v4 node21:10
b1airoHi bollig21:11
oneswigb1airo: only the one DGX-1?  You poor guys ...21:11
b1airoIt's tough down here21:11
oneswigbox is probably full of spiders by now anyway...21:11
b1airoAnyway we confirmed the fix for the MPI issue yesterday (had to replace a NIC first)21:12
oneswigb1airo: what were the symptoms of the RoCE issue?21:12
*** VW has quit IRC21:12
b1airoHave to tune VF and PF PCI LOG BAR settings in the firmware21:13
*** david-lyle has joined #openstack-meeting21:13
*** martial has joined #openstack-meeting21:13
martialgood evening21:14
oneswigHow was it bombing out?  I need to test some new NICs with RoCE at 80 procs21:14
martial(or morning ...)21:14
oneswigHi martial21:14
oneswig#chair martial21:14
openstackCurrent chairs: b1airo martial oneswig21:14
b1airoHi martial21:14
martialHi Stig, Blair, sorry for being late21:14
b1airoIt'll just just crash on startup, let me find the error message...21:14
oneswigno worries, we were just getting going really, it's a slow one21:14
oneswigno rush b1airo, think my nodes are Haswell21:15
b1airoIf you hit it you can workaround it by setting:21:16
b1airoexport OMPI_MCA_coll_hcoll_enable=021:16
*** edmondsw has quit IRC21:16
*** rbudden has joined #openstack-meeting21:16
oneswigthanks b1airo, noted21:16
oneswigWe should go through some agenda items but first up...21:17
oneswig#topic Sydney Hackathon21:17
*** openstack changes topic to "Sydney Hackathon (Meeting topic: scientific-wg)"21:17
oneswigI think you're all aware of that21:17
oneswig#link Hackathon http://hackathon.openstack.org.au21:17
oneswigmartial: are you judging or was the travel time not convenient?21:18
*** edmondsw_ has joined #openstack-meeting21:18
martialI am mentoring and very likely judging21:18
martialI will be there on time21:18
oneswigI think I may see you there then... I'll now be travelling to Sydney on the Saturday21:19
*** dprince has quit IRC21:19
martialgood :)21:20
martialsee you there21:20
oneswig#topic Sydney SIG activities21:20
*** openstack changes topic to "Sydney SIG activities (Meeting topic: scientific-wg)"21:20
*** tssurya has quit IRC21:21
oneswigThe events are in place: a meeting and bof21:21
oneswigBoth IIRC on Monday, back-to-back21:21
b1airoLast week we started an etherpad for the lightning talk session, but I didn't get around to emailing it yet21:21
oneswigb1airo: oh great, my next question :-)21:22
b1airoWill do that right now...21:22
*** edmondsw_ has quit IRC21:22
*** rbudden has quit IRC21:22
b1airoIt's at etherpad.openstack.org/p/sydney-scientific-sig-lightning-talks21:24
oneswigah, too quick, you just pipped me21:24
*** thorst has quit IRC21:25
oneswigAh, I saw that Saverio's already put his name down - I saw him talk about that in April and was really piqued by it.21:25
*** thorst has joined #openstack-meeting21:26
oneswigShall we do a social in Sydney?21:28
b1airoEmail sent. I am still spamming both the SIGs and ops lists (I doubt the list membership has settled yet)21:28
*** jamesmcarthur has quit IRC21:29
oneswigThanks b1airo21:29
oneswig#topic ORC Update - Sydney21:30
b1airoHonestly, after the issues we've had organising it previously I was thinking it probably was not worthwhile21:30
*** openstack changes topic to "ORC Update - Sydney (Meeting topic: scientific-wg)"21:30
*** julim has joined #openstack-meeting21:30
*** thorst has quit IRC21:30
oneswigb1airo: informally, non-organised, perhaps...21:30
oneswiglike the good ol' days :-)21:30
b1airoYeah, I think maybe a non-sponsored one would be easier21:30
*** julim has quit IRC21:31
oneswigseems fair.  I think I was lucky dealing with the sponsors in Barcelona, it worked well.21:31
martialplus it makes it easier to chose on the spot (nearly :) )21:31
*** flanders_ has joined #openstack-meeting21:31
oneswigmartial: can you update us on ORC?21:31
*** jamesmca_ has joined #openstack-meeting21:32
*** tongl has joined #openstack-meeting21:32
*** armstrong has joined #openstack-meeting21:33
martialyes of course21:34
martialso so far, the ORC planning is moving forward21:34
*** jamesmca_ has quit IRC21:34
martialI am going to try to have a meeting Thursday 8pm EST (Friday 11am Sydney time) to discuss local participation and presentations21:35
martialI will email the OpenStack ML about it21:35
martialwe are not Wed/Thu full day21:35
martialwill make it is easier for people to attend both21:36
martialthere are still question of who can attend (ticket questions). Ms Vancsa started looking into that (thank you)21:36
martial(we are "now" ... Wed/Thu)21:37
oneswigAh, thanks for clarifying21:37
oneswigI can at least attend on the Thursday.  I'm talking on the Wednesday, alas21:37
martialWilfred is still looking into a place for Thursday21:37
martialso pretty much a lot of work in progress21:38
martialstill to do an basically open call for participation:21:38
martialWe need to identify panelists for the sessions -- particularly getting presenters from regional country NRENs and research clouds.21:38
martialtechnical working group and industry participation21:38
martialand discussion of working group presentations and chairs21:39
martialbut it is moving along smoothly21:39
*** ykatabam has joined #openstack-meeting21:39
martialany point in particular to discuss?21:39
martial(ie questions)21:40
martialI have been giving access to the website, so I will post information and draft agenda21:41
martialI see David is around? any update for us by any chance?21:41
oneswigWas there any further on the idea of knitting it into the forum sessions more?21:42
*** salv-orlando has joined #openstack-meeting21:42
oneswigok - move on?21:43
oneswig#topic Supercomputing21:43
*** openstack changes topic to "Supercomputing (Meeting topic: scientific-wg)"21:43
oneswigWe need a volunteer who lives in Denver, or someone with a shipping address there!21:44
*** salv-orlando has quit IRC21:44
martialyes I am now co-moderating the P2302 meeting, so we will have a forum session on Tuesday21:44
b1airoFor books?21:44
*** salv-orlando has joined #openstack-meeting21:44
oneswigThe Foundation's printing the OpenStack/HPC book and needs a shipping address21:44
oneswigwith an inexact delivery date, I believe21:45
oneswigSo a booth on the floor is good for a day or two beforehand, but they might be more vague than that.21:45
*** julim has joined #openstack-meeting21:45
b1airoI have some vendor contacts in Denver. Might be a little bit of an odd ask, so maybe only if there is no better idea...21:45
b1airoAlso, the OpenStack SC BOF is confirmed, has been on the programme a week or two now21:46
oneswigKathy says: "I can’t control when they’ll arrive, unfortunately. Can we ship the desired Supercomputing quantity to someone close to the event (drivable is ideal) so they can hand carry the boxes and distribute them at the show? Or I can ship to a hotel, hopefully they’ll hold the boxes if they arrive very early. Please send the contact name, address, phone, and if a hotel, the arrival dat21:47
martialthe go community might have some people there, I will try to contact some people I know there21:47
armstrongIs it possible for us to have the  OpenStack/HPC book?21:48
martial(gophercon is usually in Denver)21:48
armstrongi mean copy of the book21:48
b1airoIt will be updated to reflect a merge with 3 other speakers who had a submission put in for them by some vendors/analysts and will now become part of ours (there's was an OpenStack HPC storage integration focus, so works well)21:48
oneswigSomewhat hilariously, the Work of flanders_ appears in her next paragraph: "I can also send another smaller batch to one other person. Maybe this person can distribute to the contributors. This batch could also go to someone at the Sydney Summit. Maybe to Blaire? "21:48
oneswigb1airo: I can take one for the team - John's going to attend in my place so you can take me off the panel to make room21:49
b1airoGargh, damn that man!21:49
b1airooneswig: I think we'll be ok for room, but are you not coming at all now?21:49
*** erlon has quit IRC21:50
*** thorst has joined #openstack-meeting21:50
oneswigb1airo: unfortunately no.  We looked at it long and hard, it's a huge shame to miss out.21:50
martialstig: missing SC?21:50
*** edmondsw has joined #openstack-meeting21:51
oneswigmartial: alas, yes - we'll need to make the most of Sydney :-)21:51
b1airoLong time to be away from home21:51
oneswigok, it seems nobody present lives near Denver and is going to SC.21:52
flanders_Doh! What I do?21:52
oneswigflanders_: Ask Blairé21:52
b1airoAt least it isn't Blairè21:53
b1airo(would sound like a cat throwing up)21:53
flanders_I think this is my disinformation, Kathy might be calling you Blairé he he ;p21:53
oneswigflanders_ work is done here21:54
flanders_I'm so proud!21:54
flanders_Love U Blair ;D21:54
*** thorst has quit IRC21:54
b1airoMaybe I'll start a new LinkedIn and see if I get profiled differently with the é21:54
oneswigb1airo: is it a stretch too far to call up your friendly vendor in Denver?21:55
martialmaybe you can do the evil twin moustache21:55
*** edmondsw has quit IRC21:55
*** esberglu has quit IRC21:55
b1airooneswig: I'll give it a shot21:55
flanders_Btw +1 if we can get ORC sessions for the Wed listed as part of the forum schedule.  martial if so email speakersupport@OpenStack.org to suggest with Erin, Ildiko and myself Cc'd21:56
*** esberglu has joined #openstack-meeting21:56
oneswigThanks b1airo, I'll copy you in to Kathy's mail to work out details21:56
martialgood idea flanders_21:56
oneswigYou mean, flandres?21:57
martialare we Frenchicizing everybody's name?21:57
martialI win, mine is already correct then :)21:57
flanders_+1 for Flandres! Ye oldy spelling!21:58
oneswigWe should wrap up21:58
martialflanders_: re ORC, there will be a Friday 11am Sydney time call, can you join?21:58
oneswig#topic AOB21:58
*** openstack changes topic to "AOB (Meeting topic: scientific-wg)"21:58
flanders_Gotta run, can't wait to see y'all in Syd, Flandres out yo.21:58
oneswigThanks Flandres :-)21:58
oneswigAny more to add?21:59
martialI am good21:59
*** Apoorva_ has joined #openstack-meeting21:59
oneswigarmstrong: to your earlier question - will you be at Supercomputing?  The books will be given out there.21:59
b1airooneswig: I didn't find the exact error message21:59
b1airoBut it is an out of memory22:00
armstrongOH no but I will be at Syd22:00
b1airoOr perhaps "memory allocation error"22:00
*** esberglu has quit IRC22:00
*** ykatabam has quit IRC22:00
b1airoIf you run an all2all test you will hit it22:00
oneswigI have OpenMPI over TCP latencies that are insanely high.  Too high.  Like 16ms.  This is PV-OVS-VxLAN - it's meant to be slow but that's unbelievable22:00
oneswigTrying to find something to compare against RoCE and ASAP2 - but can't fit these things on the same graph!22:01
oneswigOK, time to close - thanks all22:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:02
openstackMeeting ended Tue Oct 17 22:02:09 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-10-17-21.00.html22:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-10-17-21.00.txt22:02
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-10-17-21.00.log.html22:02
armstrong@oneswig OH no but I will be at Sydney. When is ORC coming up?22:02
*** ykatabam has joined #openstack-meeting22:02
oneswigAt Sydney, Wednesday-Thursday of same week22:02
armstrongok I will be there22:02
*** Apoorva has quit IRC22:03
oneswiggreat, see you then22:03
martialarmstrong: cool22:05
*** martial has quit IRC22:05
*** VW has joined #openstack-meeting22:07
*** armstrong has quit IRC22:08
*** zhhuabj has quit IRC22:08
*** oneswig has quit IRC22:08
*** mike92 has quit IRC22:09
*** baoli has quit IRC22:10
*** zhhuabj has joined #openstack-meeting22:11
*** tpsilva has quit IRC22:13
*** VW_ has joined #openstack-meeting22:13
*** ijw has joined #openstack-meeting22:16
*** VW has quit IRC22:17
*** felipemonteiro__ has quit IRC22:17
*** VW_ has quit IRC22:18
*** ijw has quit IRC22:20
*** fzdarsky has quit IRC22:23
*** jamesmcarthur has joined #openstack-meeting22:23
*** jamesmcarthur has quit IRC22:25
*** Adri2000 has quit IRC22:25
*** jamesmcarthur has joined #openstack-meeting22:26
*** jamesmcarthur has quit IRC22:27
*** lbragstad has quit IRC22:36
*** cdub has joined #openstack-meeting22:39
*** cdub has quit IRC22:42
*** cdub has joined #openstack-meeting22:44
*** salv-orlando has quit IRC22:45
*** salv-orlando has joined #openstack-meeting22:46
*** oanson has quit IRC22:50
*** salv-orlando has quit IRC22:51
*** oanson has joined #openstack-meeting22:52
*** mjturek has quit IRC22:54
*** fnaval_ has quit IRC22:56
*** lin_yang has joined #openstack-meeting22:56
*** ssathaye has quit IRC23:10
*** chyka_ has quit IRC23:11
*** Apoorva_ has quit IRC23:11
*** ssathaye has joined #openstack-meeting23:11
*** Apoorva has joined #openstack-meeting23:11
*** cdub has quit IRC23:13
*** ijw has joined #openstack-meeting23:17
*** ijw has quit IRC23:22
*** gmann_afk is now known as gmann23:24
*** emagana has quit IRC23:26
*** emagana has joined #openstack-meeting23:27
*** emagana has quit IRC23:31
*** esberglu has joined #openstack-meeting23:31
*** hongbin has quit IRC23:32
*** bobh has joined #openstack-meeting23:33
*** claudiub has quit IRC23:36
*** rbudden has joined #openstack-meeting23:39
*** bobh has quit IRC23:44
*** tongl has quit IRC23:44
*** salv-orlando has joined #openstack-meeting23:46
*** artom has joined #openstack-meeting23:49
*** salv-orlando has quit IRC23:52
*** wanghao has quit IRC23:57
*** ijw has joined #openstack-meeting23:59

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