Tuesday, 2017-01-31

*** baoli has quit IRC00:00
*** lamt has quit IRC00:01
*** Patifa has quit IRC00:01
*** rbak_ has quit IRC00:01
*** jrist has quit IRC00:02
*** ykatabam1 has joined #openstack-meeting00:02
*** ykatabam has quit IRC00:03
*** abhiraut has quit IRC00:05
*** aeng has joined #openstack-meeting00:06
*** unicell has quit IRC00:07
*** abhiraut has joined #openstack-meeting00:15
*** mriedem has joined #openstack-meeting00:16
*** unicell has joined #openstack-meeting00:19
*** hongbin has quit IRC00:19
*** Swami_ has joined #openstack-meeting00:20
*** rajinir has quit IRC00:26
*** mtanino_ has joined #openstack-meeting00:29
*** unicell has quit IRC00:29
*** mtanino has quit IRC00:30
*** fnaval has quit IRC00:30
*** rbrady has quit IRC00:31
*** bobmel has joined #openstack-meeting00:31
*** bobmel has quit IRC00:36
*** askb has joined #openstack-meeting00:36
*** Julien-zte has joined #openstack-meeting00:36
*** rbrady has joined #openstack-meeting00:45
*** rbrady has quit IRC00:45
*** rbrady has joined #openstack-meeting00:45
*** jamesdenton has quit IRC00:47
*** gouthamr has joined #openstack-meeting00:48
*** unicell has joined #openstack-meeting00:52
*** galstrom is now known as galstrom_zzz00:56
*** abhiraut has quit IRC00:56
*** baoli has joined #openstack-meeting01:02
*** baoli has quit IRC01:02
*** jamesdenton has joined #openstack-meeting01:03
*** m1dev has quit IRC01:07
*** unicell has quit IRC01:07
*** yamahata has quit IRC01:11
*** unicell has joined #openstack-meeting01:11
*** iyamahat has quit IRC01:11
*** thorst_ has joined #openstack-meeting01:16
*** Julien-zte has quit IRC01:20
*** ykatabam1 has quit IRC01:24
*** rbrady has quit IRC01:34
*** dims has quit IRC01:35
*** dims_ has joined #openstack-meeting01:35
*** baoli has joined #openstack-meeting01:38
*** prameswar has joined #openstack-meeting01:39
*** ykatabam has joined #openstack-meeting01:40
*** rfolco has quit IRC01:42
*** dims_ has quit IRC01:42
*** baoli has quit IRC01:42
*** dims has joined #openstack-meeting01:42
*** s3wong has quit IRC01:43
*** newmember has joined #openstack-meeting01:45
*** jamesdenton has quit IRC01:46
*** rfolco has joined #openstack-meeting01:49
*** rfolco has quit IRC01:49
*** dmacpher has joined #openstack-meeting02:07
*** ijw has quit IRC02:08
*** pradk has quit IRC02:15
*** mtanino has joined #openstack-meeting02:17
*** mtanino_ has quit IRC02:19
*** baoli has joined #openstack-meeting02:20
*** armax has quit IRC02:22
*** unicell has quit IRC02:22
*** Apoorva has quit IRC02:26
*** Sukhdev has quit IRC02:27
*** absubram has quit IRC02:27
*** dmorita has joined #openstack-meeting02:28
*** fzdarsky_ has joined #openstack-meeting02:32
*** mtanino has quit IRC02:34
*** rfolco has joined #openstack-meeting02:35
*** rfolco has quit IRC02:35
*** rfolco has joined #openstack-meeting02:35
*** fzdarsky|afk has quit IRC02:35
*** rfolco has quit IRC02:36
*** rfolco has joined #openstack-meeting02:36
*** rfolco has quit IRC02:37
*** rfolco has joined #openstack-meeting02:37
*** rfolco has quit IRC02:38
*** thorst_ has quit IRC02:39
*** rfolco has joined #openstack-meeting02:41
*** rfolco has quit IRC02:41
*** rfolco has joined #openstack-meeting02:41
*** rfolco has quit IRC02:42
*** Apoorva has joined #openstack-meeting02:42
*** jamesdenton has joined #openstack-meeting02:43
*** masayukig has quit IRC02:47
*** VW has joined #openstack-meeting02:52
*** Apoorva has quit IRC02:52
*** kaisers_ has joined #openstack-meeting02:55
*** Bluebell_ has joined #openstack-meeting02:55
*** zz_dimtruck is now known as dimtruck02:55
*** hongbin has joined #openstack-meeting02:55
*** shubhams has joined #openstack-meeting02:56
*** Swami_ has quit IRC02:56
*** VW has quit IRC02:56
*** kaisers has quit IRC02:58
*** bobmel has joined #openstack-meeting02:58
*** Swami_ has joined #openstack-meeting02:59
*** Namrata has joined #openstack-meeting02:59
hongbin#startmeeting zun03:00
openstackMeeting started Tue Jan 31 03:00:04 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-01-31_0300_UTC Today's agenda03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
*** lakerzhou has joined #openstack-meeting03:00
*** ijw has joined #openstack-meeting03:00
hongbinthanks for joining the meeting Namrata shubhams03:01
hongbinthese weeks are chinese new year, so a lot of folks are vacation right now03:01
shubhamshongbin:  seems we 3 only. Lets wait for a minute or two for others to join .03:02
lakerzhouHongbin, I am here also03:02
hongbinhey lakerzhou03:02
hongbinyes, let's wait for a minute03:02
*** diga has joined #openstack-meeting03:02
hongbindiga: hi03:02
digahongbin: Hi03:03
*** Swami__ has quit IRC03:03
hongbinok, let's have a short meeting this week03:03
*** Swami has quit IRC03:03
*** Swami_ has quit IRC03:03
hongbin#topic Announcements03:03
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:03
hongbin1. Welcome Kevin to the core team03:03
*** bobmel has quit IRC03:03
hongbin#topic Review Action Items03:03
*** openstack changes topic to "Review Action Items (Meeting topic: zun)"03:03
mkraiSorry I am late03:03
hongbin1. hongbin create a bp for exposing container cpu resource (N/A, a BP was already created)03:03
mkraiWelcome kevin03:03
hongbinmkrai: hi mkrai , thanks for joining the meeting03:03
hongbin#link https://blueprints.launchpad.net/zun/+spec/cpuset-container Support pinning container to CPU cores03:03
hongbin2. hongbin create a bp to add support for expose container port (DONE)03:04
hongbin#link https://blueprints.launchpad.net/zun/+spec/expose-containerized-app03:04
hongbinany question about these two action items?03:04
*** ijw has quit IRC03:04
hongbinseems not. next topic03:05
hongbin#topic Cinder integration (diga)03:05
*** openstack changes topic to "Cinder integration (diga) (Meeting topic: zun)"03:05
hongbin#link https://blueprints.launchpad.net/zun/+spec/cinder-zun-integration The BP03:05
hongbin#link https://review.openstack.org/#/c/417747/ The design spec03:05
hongbindiga: ^^03:05
*** newmember has quit IRC03:05
hongbindiga: any update from your side about hte cinder integration?03:05
digahongbin: I am working on it, but last week i was busy product release so couldn't get time03:05
*** newmember has joined #openstack-meeting03:05
hongbindiga: np03:06
digaI am starting today on it, as yesterday we shipped the release03:06
hongbindiga: thanks diga03:06
*** sudswas__ has joined #openstack-meeting03:06
*** sudipto_ has joined #openstack-meeting03:06
digahongbin: one more thing, I got official support from my company to contribute to OpenStack03:06
hongbindiga: good to hear03:06
digahongbin: I think today onward I can spend at least 2 hours03:07
hongbinsudipto_: hey03:07
sudipto_sorry a little late today.03:07
hongbindiga: great03:07
hongbinsudipto_: np03:07
digahongbin: just one question on driver03:07
hongbindiga: go ahead03:07
digahongbin: as we are writing driver for image, storage, networking etc03:08
digahongbin: can we have center driver folder & under that we can create multiple drivers03:08
digadrivers/images driver/volumes  drivers/networks etc03:09
digato keep the design simple03:09
mkraiI think that can be done03:09
hongbini think nova is using this structure03:09
hongbinimages/driver volumes/driver networks/driver03:10
lakerzhouI started reading code. It sounds a good idea to me.03:10
*** Bluebell_ has left #openstack-meeting03:10
digaI think this design structure we should follow going ahead03:11
hongbindiga: however, i think container driver is the only important driver for us03:11
digahongbin: okay03:11
hongbindiga: we are not writting drivers for network and volume (kuryr does)03:12
hongbindiga: but feel free to propose the folder change if you think it is better03:12
digahongbin: okay03:12
digahongbin: Sure03:12
digahongbin: Thanks03:12
hongbindiga: any other question from you?03:13
digahongbin: No, I am done!03:13
hongbinthanks diga03:13
hongbin#topic Kuryr integration (hongbin)03:13
*** openstack changes topic to "Kuryr integration (hongbin) (Meeting topic: zun)"03:13
hongbin#link https://blueprints.launchpad.net/zun/+spec/kuryr-integration The BP03:13
hongbini give a short update of this one03:13
hongbini have wrote down the spec, and needs a few patch from kuryr side to merge03:13
hongbinall, feel free to comment on the spec if you like03:14
digawill go through the spec03:14
hongbin#link https://review.openstack.org/#/c/425883/03:14
mkraiWhat patches from Kuryr side?03:14
hongbin#link https://review.openstack.org/#/c/426595/03:15
hongbinabove is the kuryr patch03:15
mkraiOk got it03:15
digamkrai: I think idea is same as we have proposed for volume integration, we are not going to call kuryr API03:15
digahongbin: am i correct ?03:16
hongbindiga: i think you are03:16
*** VW has joined #openstack-meeting03:17
hongbinok, advance topic03:17
hongbin#topic Support interactive mode (kevinz)03:17
*** openstack changes topic to "Support interactive mode (kevinz) (Meeting topic: zun)"03:17
hongbinit looks kevin is on vacation03:17
hongbinskip this one03:17
hongbin#topic The image API (prameswar)03:17
*** openstack changes topic to "The image API (prameswar) (Meeting topic: zun)"03:17
hongbin#link https://review.openstack.org/#/c/425249/03:17
prameswarCurrently, we are storing image data in db. instead of db we can use storage driver for that as we discussed before.03:17
prameswarwe can support multiple image driver03:18
prameswarto store image03:18
prameswarwhat you guys think ?03:18
mkraiprameswar: By storage driver, you mean?03:18
prameswarsorry image driver03:19
prameswarlike docker store images03:19
digaprameswar: you mean you want to store image in object store ??03:19
prameswarkind of03:19
prameswari am not sure what exactly but db not seems good03:20
prameswarto me03:20
mkraiWe are just storing the image info in db03:20
mkraiWe have glance/docker to store images03:20
prameswarbut i think docker store image info in some json format03:21
prameswarif i am not wrong03:21
prameswarit don't use database03:21
digathis is good thing to store in glance03:21
*** alexpilotti has joined #openstack-meeting03:22
hongbinprameswar: right now, image API has list/show/pull/search03:22
shubhamsprameswar:  Any pitfalls or disadvantages you see having info stored in db? asking as only basic info is stored in db as of now03:22
hongbinprameswar: if we skip the db, than all these operations are got from dockerhub/glance, is that correct?03:23
prameswari think so03:23
sudipto_prameswar, yes docker stores them in json blob, but why do we have to change for that?03:23
*** bkopilov has quit IRC03:24
digaI dont see any problem in storing image url info in db03:24
hongbini think the problem right now is that the image api is not able to handle the multi-host senario03:24
mkraihongbin: Yes that is a valid point03:24
hongbine.g. zun image-search : it search image in one host03:25
shubhamshongbin:  correct03:25
hongbini guess this is a motivation mentioned in the review03:25
hongbinit seems prameswar 's proposal could solve the problem (although i haven't think about it carefully)03:26
*** alexpilotti has quit IRC03:26
hongbinprameswar: i think you can propose a spec if you want to do that03:26
prameswarlet me spend some time on this . i will collect some more info then will let you know03:26
prameswaryes , sure03:27
mkrai+1 for spec03:27
hongbinyes, then we can discuss on the spec03:27
digaI will go through the spec today03:27
hongbinany other comment about this topic?03:28
hongbinok, next topic03:28
hongbin#topic Discuss BPs that are pending approval03:28
*** openstack changes topic to "Discuss BPs that are pending approval (Meeting topic: zun)"03:28
hongbin#link https://blueprints.launchpad.net/zun/+spec/support-blkio Support blkio03:28
hongbini didn't get a chance to study the blkio option yet03:29
hongbinanyone else has a comment on this one?03:29
mkraiIt seems that it will be good to support03:30
hongbinmkrai: ack03:30
sudipto_Doesn't have much details?03:30
*** diablo_rojo_phon has quit IRC03:30
hongbinsudipto_: no, it doesn't03:30
*** amotoki has joined #openstack-meeting03:30
digawhat use case we solve using this BP ?03:30
hongbini am not sure exactly what was proposed....03:31
*** ijw has joined #openstack-meeting03:31
*** ijw has quit IRC03:31
mkrailimit the IO operation per container03:31
*** ijw has joined #openstack-meeting03:31
hongbinok, let me ask for clarification in the bp before approving it03:31
digawe should explore more on this03:31
hongbinany other comment?03:32
*** ijw has quit IRC03:32
hongbin#link https://blueprints.launchpad.net/zun/+spec/support-zun-stats Support stats03:32
sudipto_IMO, this is a good addition.03:32
hongbinsudipto_: ack03:33
mkraiThere is patch already for this03:33
hongbinsudipto_: do you know the docker stats command well?03:33
hongbinsudipto_: what this command is going to do?03:33
mkraiNo that is for top. Sorry03:33
sudipto_hongbin, yeah sort of. This should you the top command equivalent data of sorts.03:33
sudipto_but for each docker container.03:34
hongbinsudipto_: is the data streaming from server to client?03:34
sudipto_hongbin, yes.03:34
hongbinsudipto_: i see03:34
sudipto_it does not give you a snapshot, rather a continuous stream.03:35
*** mtanino has joined #openstack-meeting03:35
sudipto_i guess that's what you asked.03:35
hongbinsudipto_: yes03:35
hongbini am not sure how to implement it then, since it is streaming03:35
hongbinalso, i am not sure how to handle the multi-host senario03:36
digadoes docker expose stats API ?03:36
hongbindoes the data streaming from multiple hosts?03:36
mkraidiga: Yes03:36
hongbinsudipto_: ^^03:36
sudipto_hongbin, I haven't tried this on multiple hosts.03:36
lakerzhouWho will consume the stats data? Apps such as ceilometer?03:37
hongbinlakerzhou: i don't know that as well03:37
sudipto_lakerzhou, i guess yes. But that way zun command line may not be needed to support it.03:37
*** jrobinson is now known as jrobinson-afk03:37
digain that case, if docker shows stats for one docker endpoint, so in this case, we can accept docker host & for the first time, we should accept one docker host to display stats03:38
digastreaming from multiple hosts we can think more03:38
mkraistats is per container03:38
hongbindiga: host should be an admin-only api (at least in nova)03:38
*** yangyape_ has joined #openstack-meeting03:38
digahongbin: okay03:39
sudipto_Maybe this is a better fit in Ceilometer?03:39
hongbinmkrai: i think top is per container?03:39
hongbinsudipto_: not sure03:39
mkraihongbin: Display a live stream of container(s) resource usage statistics03:40
hongbinmkrai: ok03:40
*** Apoorva has joined #openstack-meeting03:40
hongbinall, should this bp be approved/disapproved, or table it?03:40
mkraiThen the multiple host issue is not valid I guess03:41
hongbini see03:41
mkraiI think we need to look how do we handle the live streaming?03:41
*** yangyapeng has quit IRC03:41
mkraifrom docker daemon to zun03:41
hongbinthis would not be easy, might be something similar to what kevin was doing (interactive mode)03:42
digathere are other libraries support live streaming we can use those, but it will be dependancy in zun03:42
mkraiWe can ask the author of bp to see the feasibility of doing this in zun03:43
hongbinthen, let's table this bp03:43
hongbinuntil we get the answer from the author03:43
hongbin#topic Open Discussion03:43
digathis is good addition to Zun03:43
shubhamshongbin: +103:43
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:43
hongbinall, any other topic to discuss03:44
digahongbin: are we planning for PTG ?03:44
sudipto_I just posted a spec here: https://review.openstack.org/#/c/427007/2/specs/cpuset-container.rst (It's pretty much out of my head atm) - please take a look when you can.03:44
hongbindiga: no, zun won't attend the ptg03:44
digahongbin: okay03:45
hongbinsudipto_: cool03:45
Namratai have posted a patch to add zun resources https://review.openstack.org/#/c/426210/03:45
sudipto_This is an attempt to build host capabilities in zun as well. I will keep refining the spec as we  go. Let me know if there' sa need for a separate BP all together for host capabilities.03:45
hongbinNamrata: awesome!03:46
Namratathanks.it is up for review03:46
hongbinsudipto_: i think the host capabilities worth a separated spec, it would be a lot of work03:46
sudipto_yeah i have wrote down very minimalistic things, I am guessing you'd have to help me out co-authoring some of the stuff hongbin03:47
hongbinsudipto_: for sure03:47
hongbin#action hongbin create a spec for host capability03:47
*** abhishekk has joined #openstack-meeting03:47
hongbini guess a lot of code will be copied from nova :)03:48
sudipto_hongbin, yeah maybe, we probably wouldn't need many things as well.03:48
hongbinok, any other topic?03:48
hongbintoday, many chinese folks are not able to come due to the chinese new year03:49
mkraiHappy chinese new year hongbin :)03:49
hongbinthen, let's end the meeting a bit earlier03:49
hongbinmkrai: thank you :)03:49
sudipto_Happy new year hongbin :)03:49
digahongbin: Happy New year!03:50
hongbinall, thanks for joining hte meeting03:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"03:50
openstackMeeting ended Tue Jan 31 03:50:12 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-01-31-03.00.html03:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-01-31-03.00.txt03:50
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-01-31-03.00.log.html03:50
*** shubhams has quit IRC03:50
*** diga has quit IRC03:52
*** samP has joined #openstack-meeting03:52
*** newmember has quit IRC03:55
*** newmember has joined #openstack-meeting03:56
*** ekcs has joined #openstack-meeting03:58
*** tpatil has joined #openstack-meeting03:59
*** lakerzhou has quit IRC03:59
*** takashi has joined #openstack-meeting03:59
*** sdake has quit IRC04:00
samPhi all o/04:00
*** Dinesh_Bhor has joined #openstack-meeting04:00
*** sagara has joined #openstack-meeting04:00
Dinesh_BhorHi all04:00
samPtpatil: hi..04:00
samPDinesh_Bhor: hi..04:00
samPlets start04:00
samPsagara: hi04:00
samP#startmeeting masakari04:00
openstackMeeting started Tue Jan 31 04:00:46 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
samPtakashi: hi04:01
samPsince no critical bugs lets move to discussion..04:01
samP#topic Discussion points04:01
*** openstack changes topic to "Discussion points (Meeting topic: masakari)"04:01
tpatilThere is one issue reported in masakari04:01
samP1st one, Who will set ha_enabled?04:01
tpatil#link : https://bugs.launchpad.net/masakari/+bug/165949504:02
openstackLaunchpad bug 1659495 in masakari "taskflow version is not compatible with latest engine code" [Undecided,New]04:02
samPtpatil: sorry,04:02
tpatilDinesh will fix this issue04:02
samPThis is taskflow version issue, right?04:03
tpatilsamP: correct04:03
takashiCan we just bump up required taskflow version?04:03
tpatilyes, that's what we will need to do to fix this issue04:04
takashiI'm just wondering this issue happens because the requreiemt.txt is not synced with global-requirements.txt04:04
samPwhat is the globel req version for taskflow?04:04
takashiour requreiemtns.txt in masakari04:04
*** anilvenkata has joined #openstack-meeting04:04
*** Rockyg has quit IRC04:05
Dinesh_Bhortakashi: makes sense to me, masakari requirements are not getting bumped by bot jobs04:05
abhishekkyes, but why it was not caught by jenkins? IMO we should have a test case to check fail formaters04:05
*** VW has quit IRC04:05
samPtakashi: thanks, upper is set to taskflow===2.9.004:05
*** VW has joined #openstack-meeting04:05
takashifyi: https://github.com/openstack/requirements/blob/master/global-requirements.txt#L28004:05
takashiMaybe we should manually sync requirement.txt before we relase Ocata...04:06
takashiat least04:06
takashiand at workst04:06
*** iyamahat has joined #openstack-meeting04:06
samPtakashi: agree04:06
*** gouthamr has quit IRC04:07
samPafter Ocata relase, we may use bot to do this.04:07
tpatilDinesh_Bhor: Please bump the taskflow version to 2.7.0 in requirements.txt and upload the patch for review04:08
*** hongbin has quit IRC04:08
Dinesh_Bhortpatil: yes04:08
tpatilDinesh_Bhor: Thanks04:09
samPDinesh_Bhor: tpatil thanks04:09
samP#action Dinesh_Bhor Fix https://bugs.launchpad.net/masakari/+bug/165949504:09
openstackLaunchpad bug 1659495 in masakari "taskflow version is not compatible with latest engine code" [Undecided,New]04:09
samPOk then, any other bugs to discuss?04:10
tpatilsamP: No04:12
samPtpatil: thanks04:12
samPlets move to the discussion04:12
takashiyes :-)04:12
samP1st one, Who will set the ha_enabled tag?04:12
abhishekkI have added that in agenda04:13
samPabhishekk: thanks04:13
samPIn previous masakari, only operator set this tag to each VM04:13
abhishekkso how to rstrict normal user from setting this flag?04:14
abhishekkin glance there is a property protection which we can set using policy.json04:14
tpatilsamP: HA_Enabled will be set as a tag or metadata?04:14
samPtpatil: sorry, in meta data04:15
tpatilsamP: Ok04:15
samPabhishekk: I have to check, but I think we did not expose metadata API to end user.04:16
samPabhishekk: so, end user can not set metadata to server04:16
abhishekkok, I need to check about that04:17
Dinesh_BhorIt can be set at the time of boot as well and normal user can do that04:17
samPanyway, in normal openstack env, end user can add the metadata04:17
samPDinesh_Bhor: correct04:18
samPI am not sure nova policy does support this kind of restrections on metadata04:18
*** mtanino has quit IRC04:19
samPas abhishekk said, I remember we set simillar setting for glance04:19
*** jrobinson-afk is now known as jrobinson04:20
samPabhishekk: thanks, we can controll it.04:21
abhishekkbut IMO thiese policies are for meta api04:21
*** sshnaidm|off has quit IRC04:21
samPabhishekk: seems you are right.04:21
*** yamahata has joined #openstack-meeting04:22
abhishekkwe can set or remove metadata using meta set/delete, need to check whether this will work for boot as well04:22
*** sshnaidm|off has joined #openstack-meeting04:22
*** sdake has joined #openstack-meeting04:23
samPabhishekk: Do you mean, set metadata at boot?04:23
abhishekkwhile using boot command we can pass --metadat key=value04:23
samPabhishekk: yep.. got it04:24
*** jamesdenton has quit IRC04:25
samPso, is this an implementation related issue or operation related issue?04:26
abhishekknope as Dinesh says normal user can set this while booting the instance04:26
*** sdake_ has joined #openstack-meeting04:26
abhishekkIMO operation related issue04:26
tpatilsamP: since you haven't exposed metadata api for normal users, there will be no issues, but for other operators there is an issue04:26
samPabhishekk: thanks04:27
samPtpatil: correct04:27
tpatilsamP: Maybe we can add a support in Nova to restrict adding certain metadata keys to an instance using policy04:27
samPIMO, we cannot fix this from masakari side, need to do some work in nova04:28
samPtpatil: yes04:28
takashitpatil: makes sense04:28
*** sdake has quit IRC04:28
*** dmorita has quit IRC04:28
samPtpatil: somwhat simillar thing we did in "license metadata" in nova..04:29
abhishekksamP: in glance04:29
samPI think abhishekk mentionted part of it, in glance04:29
samPabhishekk: yes04:29
tpatilsamP: similar to glance, we can add this support in Nova as abhishekk has pointed out04:30
*** csomerville has quit IRC04:31
*** csomerville has joined #openstack-meeting04:31
samPIf we propose this to nova, it will be in Pike (at best) right?04:31
tpatilsamP: correct04:31
abhishekksamP: yes04:31
takashisamP: yus. IMO I think we should propose spec as soon as nova spec repo for Pike is opened04:33
samPgot it. what would be the best way to approach?04:33
samPI can discuss this in PTG.04:34
samPbut first I think we need some pre-discussion with nova04:34
samPtakashi: sorry, your comment came late..04:35
takashisamP: np. as you say, we need some discussion in nova project04:35
*** baoli has quit IRC04:36
samPtakashi: OK then, lets propse to Pike spec.04:36
*** ayogi has joined #openstack-meeting04:37
takashisamP: yes04:38
tpatilsamP: I have noted down this point, we will submit a spec in Nov to address this use case.04:38
samPtpatil: thanks04:38
takashisamP: maybe we can discuss our usecase with nova team, and confirm this is the best solution04:38
takashitpatil: yes, thanks!04:38
*** adisky_ has joined #openstack-meeting04:38
samPDo they set a specific date for pike spec start?04:39
takashi#link https://releases.openstack.org/pike/schedule.html04:39
*** thorst_ has joined #openstack-meeting04:40
takashiso may TBDs...04:40
samPtakashi: thanks, seems TBD04:40
takashisamP: AFAIK, nova spec freeze happens at the same time as *-1 milestone04:40
*** kenji-i has quit IRC04:41
takashisamP: so we should get the spec approved before Pike-1 milestone04:41
samPtpatil: may I assign this task to you for now?04:41
tpatilsamP: Yes04:41
samPtakashi: got it04:41
samP#action tpatil Propse Nova spec for matadata controll policy04:42
samPtpatil: thanks04:42
samPabhishekk: thanks for adding this point04:43
samPshall we move to next topic?04:43
abhishekksamP: no problem04:43
samP#link https://review.openstack.org/#/c/423072/04:44
samPabhishekk: thanks for the nice idea. but I have some operation related issues (pls see my comment on gerrit)04:44
abhishekksamP: I have seen your comments04:45
*** thorst_ has quit IRC04:45
samPabhishekk: Those are just my comments, but other may have different opinion on this04:46
abhishekkIMO it makes sense to balance the pool of reserved hosts failed node can be reassigned as a reserved host04:46
*** bkopilov has joined #openstack-meeting04:47
*** dimtruck is now known as zz_dimtruck04:48
*** Namrata has quit IRC04:49
*** ayogi has quit IRC04:50
*** Sukhdev has joined #openstack-meeting04:50
samPabhishekk: Are you in favour of add reserved_host=False once we evacuate VM? or wait for other failures?04:51
*** ayogi has joined #openstack-meeting04:51
abhishekksamP: yes, because once we enable compute service on reserved host we cannot restrict nova to launch instance on that host04:52
tpatilabhishekk: We should set reserved=False immediately after all instances are evacuated from a failed compute node.04:52
abhishekktushar san makes sense04:52
samPabhishekk: correct04:52
samPtakashi: agree04:53
abhishekkI think we have 6 minutes now04:55
samPabhishekk: could you please update the spec whit this info?04:55
samPabhishekk: yes, just 5 mins left04:55
abhishekksaaP: yes04:55
samPabhishekk: thanks04:55
samP#topic AOB04:56
*** openstack changes topic to "AOB (Meeting topic: masakari)"04:56
abhishekkset reserved_host to false as soon as all instances are evacuated from the failed node, right?04:56
samPabhishekk: correct04:56
abhishekksamP: ok, it's already there in the specs, I just need to rephrase it04:57
*** masayukig has joined #openstack-meeting04:57
*** anilvenkata has quit IRC04:57
samPabhishekk: yes.. sorry it is there.. my bad04:58
Dinesh_BhorMay I ask a question related to the new requirement to add the reserved_host to the same aggregate in which the failed_host is?04:58
samPDinesh_Bhor: sure04:58
Dinesh_BhorSo my question is: A failed_host can be associated with multiple aggregates, so to which aggregate the reserved_host should be added?04:58
samPDinesh_Bhor: all the aggregates of failed host04:59
takashisamP, Dinesh_Bhor: Can we move to #openstack-maskari?04:59
tpatilDinesh_Bhor: in nova, there is unique constraint applied for host, aggregate uuid, delete column04:59
takashibecause we run out all meeting time...05:00
Dinesh_BhorsamP: ok05:00
samPtakashi: sure05:00
tpatilDinesh_Bhor: so this situation will never arise05:00
samPOK, then, lets move to openstack-masakari for further discussions..05:00
samPLets end this meeting...05:00
samPthank you all05:00
abhishekkthank you05:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:01
openstackMeeting ended Tue Jan 31 05:01:15 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-01-31-04.00.html05:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-01-31-04.00.txt05:01
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-01-31-04.00.log.html05:01
*** tpatil has quit IRC05:02
*** unicell has joined #openstack-meeting05:10
*** VW has quit IRC05:13
*** sdake_ has quit IRC05:14
*** ykatabam has quit IRC05:16
*** jrist has joined #openstack-meeting05:19
*** unicell has quit IRC05:21
*** unicell has joined #openstack-meeting05:21
*** bobmel has joined #openstack-meeting05:25
*** takashi has quit IRC05:30
*** bobmel has quit IRC05:30
*** nkrinner_afk is now known as nkrinner05:31
*** zz_dimtruck is now known as dimtruck05:39
*** dimtruck is now known as zz_dimtruck05:49
*** zz_dimtruck is now known as dimtruck05:50
*** jrobinson has quit IRC05:53
*** trinaths has joined #openstack-meeting06:00
*** dimtruck is now known as zz_dimtruck06:00
*** hichihara has joined #openstack-meeting06:05
*** rwsu has joined #openstack-meeting06:10
*** claudiub has joined #openstack-meeting06:11
*** amotoki has quit IRC06:12
*** amotoki has joined #openstack-meeting06:13
*** cody-somerville has joined #openstack-meeting06:16
*** cody-somerville has quit IRC06:16
*** cody-somerville has joined #openstack-meeting06:16
*** csomerville has quit IRC06:18
*** Dinesh_Bhor has left #openstack-meeting06:21
*** Alex_Staf has joined #openstack-meeting06:27
*** csomerville has joined #openstack-meeting06:27
*** iyamahat has quit IRC06:28
*** dmorita has joined #openstack-meeting06:28
*** cody-somerville has quit IRC06:30
*** anilvenkata has joined #openstack-meeting06:32
*** dmorita has quit IRC06:33
*** nadya has joined #openstack-meeting06:34
*** nadya has quit IRC06:35
*** csomerville has quit IRC06:37
*** lpetrut has joined #openstack-meeting06:38
*** thorst_ has joined #openstack-meeting06:41
*** thorst_ has quit IRC06:46
*** spotz is now known as spotz_zzz06:46
*** takashi has joined #openstack-meeting06:48
*** janki has joined #openstack-meeting06:49
*** Sukhdev has quit IRC06:49
*** zz_dimtruck is now known as dimtruck06:51
*** spotz_zzz is now known as spotz06:52
*** sridharg has joined #openstack-meeting07:00
*** dimtruck is now known as zz_dimtruck07:01
*** adiantum has quit IRC07:07
*** ekuris__ has joined #openstack-meeting07:09
*** rcernin has joined #openstack-meeting07:12
*** zz_dimtruck is now known as dimtruck07:12
*** hichihara has quit IRC07:16
*** Alex_Staf has quit IRC07:17
*** lpetrut has quit IRC07:20
*** Alex_Staf has joined #openstack-meeting07:21
*** dimtruck is now known as zz_dimtruck07:22
*** jtomasek_ has joined #openstack-meeting07:26
*** ayogi has quit IRC07:26
*** takashi has quit IRC07:26
*** ayogi has joined #openstack-meeting07:26
*** ykatabam has joined #openstack-meeting07:27
*** ekcs has quit IRC07:28
*** Apoorva has quit IRC07:29
*** lpetrut has joined #openstack-meeting07:30
*** yamamoto has quit IRC07:34
*** andreas_s has joined #openstack-meeting07:36
*** cartik has joined #openstack-meeting07:37
*** rasca has joined #openstack-meeting07:39
*** nadya has joined #openstack-meeting07:40
*** prameswar has quit IRC07:44
*** nadya has quit IRC07:44
*** abalutoiu has quit IRC07:47
*** iyamahat has joined #openstack-meeting07:49
*** yamahata has quit IRC07:50
*** eranrom has joined #openstack-meeting07:52
*** tesseract has joined #openstack-meeting07:54
*** jchhatbar has joined #openstack-meeting07:54
*** fzdarsky_ is now known as fzdarsky07:55
*** Julien-zte has joined #openstack-meeting07:55
*** nadya has joined #openstack-meeting07:56
*** prameswar has joined #openstack-meeting07:57
*** janki has quit IRC07:57
*** takashi has joined #openstack-meeting07:59
*** unicell has quit IRC07:59
*** akihito has joined #openstack-meeting08:00
*** kota_ has joined #openstack-meeting08:00
eranrom#start-meeting storlets08:00
*** simon-AS559 has joined #openstack-meeting08:00
eranromkota_: Hi08:00
eranrom#startmeeting storlets08:00
openstackMeeting started Tue Jan 31 08:00:32 2017 UTC and is due to finish in 60 minutes.  The chair is eranrom. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: storlets)"08:00
eranromakihito: Hi08:00
openstackThe meeting name has been set to 'storlets'08:00
eranromtakashi: Hi.08:00
eranromagenda: https://wiki.openstack.org/wiki/Meetings/Storlets#Agenda:08:01
*** rbartal has joined #openstack-meeting08:01
eranrom#topic review-priorities08:02
*** openstack changes topic to "review-priorities (Meeting topic: storlets)"08:02
eranromany comments?08:02
kota_can i make sure current stats on review-priorities08:03
eranromkota_: sure@08:03
kota_are we.... using that etherpad?08:04
eranromWell, that is the suggestion.08:04
kota_sorry, not remember in detail, how it works08:04
eranromIt was only put up yesterday - I think08:04
kota_probably because of my flu08:04
*** abalutoiu has joined #openstack-meeting08:05
eranromIt started off with me asking Takashi to list his own patchers priorities08:05
eranromso he created this pad, and I added my patches there08:05
eranromand now I suggest that we use this, so that each author will prioritize his own patches08:05
kota_er, ok08:06
eranromso we know as reviewers what to look at first.08:06
kota_makse sense08:06
kota_sagara: hi08:06
eranromsagara: Hi. agenda is here: https://wiki.openstack.org/wiki/Meetings/Storlets#Agenda:08:06
eranromkota_: So you are more then welcome to add your stuff :-)08:06
sagaraeranrom: thanks08:06
kota_to add08:07
eranromWe can always decide to use something else in the future08:07
eranromkota_: Great! thanks!08:07
takashikota_: :-)08:07
takashias we don't have so much time before Ocata release, we should be careful what we can/should land in this cycle08:08
kota_takashi: good point08:08
kota_the release should be...08:08
takashiand I think that listing can help us, because we can find items with high priorities.08:08
kota_the week since 13th Feb?08:08
eranromtakashi: right, perhaps this is another subject to discuss. Let me add it to the agenda08:09
eranromkota_: I need to check it...08:09
takashi#link https://releases.openstack.org/ocata/schedule.html08:09
takashieranrom, kota_: ^^^^^ fyi08:09
takashibut we can talk about this later08:09
*** dmacpher has quit IRC08:10
eranromtakashi: yep! thanks!08:10
eranromnext topic?08:10
*** priteau has joined #openstack-meeting08:10
*** yamamoto has joined #openstack-meeting08:10
eranrom#topic What should land for Ocata?08:11
*** openstack changes topic to "What should land for Ocata? (Meeting topic: storlets)"08:11
*** rbartal has quit IRC08:11
eranromHere is a suggestion:08:12
eranrom1. functional tests08:12
*** zz_dimtruck is now known as dimtruck08:13
*** rbartal has joined #openstack-meeting08:13
eranrom2. Some of the refactoring work - need to choose.08:13
eranrom3. IPython integration08:13
takashieranrom: Do you plan to have rc in this week?08:14
*** rbartal has quit IRC08:14
takashieranrom: or should we?08:14
takashiI think that depends on schedule to release rc08:14
eranromtakashi: only of you think its important08:15
takashiAs we are currently a part of official project, so I suppose it is automatically cut off by current release manager08:16
eranromsince we do not have any dependencies on our repo (e.g. devstack gateway jobs) I am not sure its important08:16
*** rbartal has joined #openstack-meeting08:16
*** Cibo_ has quit IRC08:16
eranromtakashi: In that case not sure it matters, but I may be missing something08:16
takashieranrom: For me it is not so important, but I'm a little concerned a basic rule in OpenStack project08:16
takashias we are now officially a part of it08:17
eranromtakashi: ok, I will look into it.08:17
*** Cibo_ has joined #openstack-meeting08:17
*** Alex_Staf has quit IRC08:17
takashiFor me, it looks better if we can land all func tests work, as we can confirm current behavior by testing08:18
eranromtakashi: +108:18
kota_+1, tests is always great08:18
takashias we find some bugs by adding functional tests, like https://review.openstack.org/#/c/426586/08:18
eranromAnything beyond the tests?08:19
takashitalking about my refactoring work around storlet agents, it is not so critical change because they are just improvoments08:19
takashiit is still better, but it is not urgent, I think08:20
eranromtakashi: ok.08:20
takashiI'll keep working about that, but in some point we need to take a dicision or selection08:21
takashiI think08:21
takashiand about IPython integration, is there anything remaining? I'm afraid I'm missing some patches.08:21
eranromtakashi: There is one patch I did not put yet in the e-pad.08:22
eranromIt adds the ability to invoke on get08:22
eranromLet me add it08:22
takashieranrom: this one? https://review.openstack.org/#/c/416089/08:22
*** dimtruck is now known as zz_dimtruck08:23
kota_eranrom: you're doing great pach08:23
kota_i'd prefer to review it08:23
eranromkota_: Thanks!08:23
*** ralonsoh has joined #openstack-meeting08:23
kota_but not yet, sorry :/08:23
kota_just walk through drafting08:23
eranromI take it that you have a backlog08:23
takashiI'll review it, too08:24
kota_AFAIK, it had merge conflicts right?08:24
kota_ah, and you already rebased08:24
kota_that's what I know right now08:24
kota_about the patch08:24
kota_and also  https://review.openstack.org/#/c/422511/ (i added as high priority)08:25
kota_is preparing ipython work08:25
kota_for sort of dry-run08:25
eranromkota_: sure.08:26
kota_but imo, it won't happen Ocata timeframe so... in pike?08:26
eranromkota_: yep.08:26
eranromI also added the IPython work but as a low priority :-)08:27
*** aloga has quit IRC08:27
*** jrobinson has joined #openstack-meeting08:27
eranromLets keep high what we want to put in Ocata.08:27
*** newmember has quit IRC08:27
eranromI will move the tests to high08:27
eranrommake sense?08:27
kota_sounds nice08:28
eranromit was good? why did you delete?08:29
eranrom:-) thanks08:29
*** Apoorva has joined #openstack-meeting08:30
eranromtakashi: Thanks@08:30
takashijust added one bug fix: Fixing tenant container id problems08:30
eranromataraday: yep saw this, thanks!08:30
takashiI'll recheck all my patches, and update the list if needed08:31
takashimy patches and existing patches08:31
eranromok great!08:31
eranromtakashi: thanks!08:31
takashibut currently we can review patches according to it08:31
eranromok, anythong else on review priorities towards Ocata?08:32
takashinothing else from me08:32
*** ykatabam has quit IRC08:32
kota_current list looks great08:33
eranromok, that was good thanks!08:33
eranromtopic: func tests refactoring thoughts08:33
eranrom#topic func tests refactoring thoughts08:33
*** openstack changes topic to "func tests refactoring thoughts (Meeting topic: storlets)"08:33
*** sshnaidm|off is now known as sshnaidm08:34
eranromThese are just suggestions...08:34
eranromor thoughts08:34
takashiLet me reply to each of your comments.08:35
takashifor 1, about temp container usage, I don't know whether we should use temporally container08:37
*** yamamoto has quit IRC08:37
takashiWhat we would like to care by temporal resource usage is to avoid collisions between multiple test cases08:38
takashiespecially paralell test execution, which is currently realized by testr08:38
takashi(though we are using it in only one thread, currently)08:38
takashis/especially/in especially/08:39
eranromtakashi: agree. I guess another question is whether we care about the func test leaving stuff behind...08:39
takashieranrom: Ideally, we should use resources which has unique name, and clean up all things created in test cases08:39
takashis/has unique name/have unique names/08:40
eranromtakashi: Agree! It does not have to be done with temp containers.08:40
takashiIn my func test refactoring, I added some cleaning up about objects created in test cases: https://review.openstack.org/#/c/420419/41/tests/functional/__init__.py@4408:41
*** prameswar has quit IRC08:41
eranromtakashi: yep. seen that :-)08:42
*** iyamahat has quit IRC08:42
*** thorst_ has joined #openstack-meeting08:42
takashiI think it can work if we use temporal container for test cases, but it is not so urgently requied, because collision between containers used in some test cases does not cause so big impart now08:42
eranromtakashi: agree.08:42
*** Apoorva has quit IRC08:43
takashiSo first step is to use temporal object, and the second step is to clean up all resources created in test execution, I think08:43
takashiDoes it make sense?08:43
openstackkota_: Error: "?" is not a valid command.08:43
eranromtakashi: absolutely08:43
takashikota_: Do you find any problems?08:44
*** Apoorva has joined #openstack-meeting08:44
*** rossella_s has joined #openstack-meeting08:44
kota_i just was seeing the code a bit08:45
kota_but ....08:45
kota_i couldn't get why we need *re-implement* methods swift client does08:45
kota_it blankets what progress there08:46
kota_almost casess08:46
takashikota_: but The reason why I'm *re-implementing* them is that I don't get why we need to get self.url and self.token and pass it to client either08:47
*** julim has quit IRC08:47
*** thorst_ has quit IRC08:48
*** electrofelix has joined #openstack-meeting08:50
kota_takashi: why not using swiftclient.Client instance?08:50
*** julim has joined #openstack-meeting08:50
kota_makking Client instance in setUp, set self.swift_client = Client(brah blah)08:50
kota_and at least, it's not a TestClass but sort of Client class IMHO.08:52
takashikota_: it is still in WIP, so I still need some re-desgin about cleasses08:53
takashiand yeah using Client instance makes sense to me. thanks!08:53
*** prameswar has joined #openstack-meeting08:53
eranromWe are running out of time and I wanted to spend few minutes on the PTG.08:53
kota_ah, it's WIP08:53
eranromperhaps we should discuss more during the PTG itself :-)08:54
kota_just was jumping by the url pasted above :P08:54
takashikota_: yes08:54
takashishortly for 2. yes. it is ideal goal to have same test cases (which inherits same base class which implements common test cases)08:54
takashibut still in WIP :-)08:54
eranromtakashi: sure!08:55
eranromok, PTG.08:55
kota_takashi: https://review.openstack.org/#/c/422470/08:55
kota_takashi: maybe we're going same way08:55
takashieranrom: ok08:55
kota_eranrom: sorry, go ahead08:55
takashikota_: I think so08:55
eranromThanks! dorry for the interruption08:56
eranrom#topic PTG08:56
*** openstack changes topic to "PTG (Meeting topic: storlets)"08:56
eranromI think it would be good to define goals for Pike08:56
eranromI added two of mine, please add more, and we can discuss durng the PTG08:57
*** Apoorva has quit IRC08:57
takashieranrom: ok08:57
*** lpetrut has quit IRC08:57
eranromOtherwise, feel free to add more topics for discussion.08:57
*** Apoorva has joined #openstack-meeting08:58
kota_eranrom: ok08:58
eranromanything else for the last 2 mins?08:58
*** toscalix has joined #openstack-meeting08:58
kota_that's all, great discussion08:59
eranromall thanks very much for joining!08:59
kota_thanks eranrom!08:59
eranromtalk to you later08:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:59
openstackMeeting ended Tue Jan 31 08:59:32 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-01-31-08.00.html08:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-01-31-08.00.txt08:59
openstackLog:            http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-01-31-08.00.log.html08:59
*** sagara has quit IRC08:59
*** yamamoto has joined #openstack-meeting08:59
*** kota_ has left #openstack-meeting09:00
*** r-mibu has joined #openstack-meeting09:01
*** aloga has joined #openstack-meeting09:04
*** yamamoto has quit IRC09:06
*** Apoorva has quit IRC09:06
*** Apoorva has joined #openstack-meeting09:07
*** yamamoto has joined #openstack-meeting09:09
*** sudipto has joined #openstack-meeting09:12
*** sudipto_ has quit IRC09:12
*** sudipto_ has joined #openstack-meeting09:13
*** zz_dimtruck is now known as dimtruck09:14
*** e0ne has joined #openstack-meeting09:14
*** sudswas__ has quit IRC09:14
*** rbartal_ has joined #openstack-meeting09:15
*** kota_ has joined #openstack-meeting09:16
saggi#startmeeting karbor09:17
openstackMeeting started Tue Jan 31 09:17:23 2017 UTC and is due to finish in 60 minutes.  The chair is saggi. Information about MeetBot at http://wiki.debian.org/MeetBot.09:17
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:17
*** openstack changes topic to " (Meeting topic: karbor)"09:17
openstackThe meeting name has been set to 'karbor'09:17
saggiSorry for being a bit late09:17
saggiIs anyone here?09:17
saggiHappy new year everyone09:19
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:19
openstackMeeting ended Tue Jan 31 09:19:30 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:19
openstackMinutes:        http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-01-31-09.17.html09:19
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-01-31-09.17.txt09:19
openstackLog:            http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-01-31-09.17.log.html09:19
*** Apoorva has quit IRC09:21
*** dimtruck is now known as zz_dimtruck09:23
*** jrobinson has quit IRC09:25
*** Apoorva has joined #openstack-meeting09:26
*** yamamoto has quit IRC09:27
*** bobmel has joined #openstack-meeting09:28
*** phil has joined #openstack-meeting09:38
*** phil is now known as Guest9135209:39
*** Apoorva has quit IRC09:39
*** yamamoto has joined #openstack-meeting09:39
*** abhishekk has left #openstack-meeting09:43
*** Apoorva has joined #openstack-meeting09:44
*** yamamoto has quit IRC09:45
*** nadya has quit IRC09:48
*** mickeys has quit IRC09:48
*** Alex_Staf has joined #openstack-meeting09:49
*** acoles_ is now known as acoles09:50
*** gcb has joined #openstack-meeting09:52
*** takashi has quit IRC09:53
*** Julien-zte has quit IRC09:54
*** nadya has joined #openstack-meeting09:55
*** Apoorva has quit IRC09:57
*** ykatabam has joined #openstack-meeting09:58
*** lennyb has quit IRC10:02
*** Apoorva has joined #openstack-meeting10:02
*** lennyb has joined #openstack-meeting10:03
*** lpetrut has joined #openstack-meeting10:04
*** jtomasek_ has quit IRC10:06
*** jchhatbar is now known as janki10:08
*** prameswar has quit IRC10:10
*** sambetts|afk is now known as sambetts10:12
*** zz_dimtruck is now known as dimtruck10:14
*** efried has quit IRC10:15
*** dimtruck is now known as zz_dimtruck10:24
*** efried has joined #openstack-meeting10:24
*** Apoorva has quit IRC10:25
*** Apoorva has joined #openstack-meeting10:30
*** neiljerram has joined #openstack-meeting10:31
*** nadya has quit IRC10:32
*** Cibo_ has quit IRC10:34
*** prameswar has joined #openstack-meeting10:34
*** Cibo_ has joined #openstack-meeting10:38
*** Apoorva has quit IRC10:39
*** adiantum has joined #openstack-meeting10:40
*** yamamoto has joined #openstack-meeting10:42
*** alexpilotti has joined #openstack-meeting10:42
*** thorst_ has joined #openstack-meeting10:44
*** alexpilotti has quit IRC10:44
*** alexpilotti has joined #openstack-meeting10:45
*** efried has quit IRC10:45
*** thorst_ has quit IRC10:49
*** mickeys has joined #openstack-meeting10:49
*** mickeys has quit IRC10:54
*** efried has joined #openstack-meeting10:58
*** geguileo has quit IRC11:00
*** ltomasbo has quit IRC11:00
*** dmellado has quit IRC11:00
*** akihito has quit IRC11:00
*** dmellado has joined #openstack-meeting11:03
*** ltomasbo has joined #openstack-meeting11:07
*** Apoorva has joined #openstack-meeting11:08
*** yamamoto has quit IRC11:08
*** ionutbalutoiu has quit IRC11:14
*** zz_dimtruck is now known as dimtruck11:15
*** ionutbalutoiu has joined #openstack-meeting11:16
*** Apoorva has quit IRC11:21
*** newmember has joined #openstack-meeting11:24
*** dimtruck is now known as zz_dimtruck11:25
*** Apoorva has joined #openstack-meeting11:26
*** adisky_ has quit IRC11:29
*** newmember has quit IRC11:30
*** bobmel has quit IRC11:31
*** Apoorva has quit IRC11:35
*** nadya has joined #openstack-meeting11:38
*** Apoorva has joined #openstack-meeting11:40
*** yamamoto has joined #openstack-meeting11:45
*** yamamoto has quit IRC11:45
*** Apoorva has quit IRC11:49
*** mickeys has joined #openstack-meeting11:50
*** yamamoto has joined #openstack-meeting11:53
*** mickeys has quit IRC11:54
*** prameswar has left #openstack-meeting11:56
*** jkilpatr has joined #openstack-meeting11:56
*** sdague has joined #openstack-meeting11:58
*** janki has quit IRC11:58
*** sdague_ has joined #openstack-meeting12:00
*** yamamoto has quit IRC12:00
*** fzdarsky is now known as fzdarsky|lunch12:02
*** simon-AS559 has quit IRC12:02
*** Apoorva has joined #openstack-meeting12:03
*** jtomasek_ has joined #openstack-meeting12:08
*** bobmel has joined #openstack-meeting12:10
*** bkopilov has quit IRC12:11
*** yamamoto has joined #openstack-meeting12:11
*** yamamoto has quit IRC12:15
*** zz_dimtruck is now known as dimtruck12:16
*** bobmel has quit IRC12:17
*** sdake has joined #openstack-meeting12:17
*** palexster has quit IRC12:18
*** bobmel has joined #openstack-meeting12:18
*** bobmel has quit IRC12:18
*** bobmel has joined #openstack-meeting12:19
*** Cibo_ has quit IRC12:21
*** Apoorva has quit IRC12:21
*** rfolco has joined #openstack-meeting12:25
*** rfolco has quit IRC12:26
*** dimtruck is now known as zz_dimtruck12:26
*** Apoorva has joined #openstack-meeting12:26
*** rfolco has joined #openstack-meeting12:26
*** palexster has joined #openstack-meeting12:27
*** rbartal__ has joined #openstack-meeting12:28
*** ayogi has quit IRC12:28
*** jtomasek_ has quit IRC12:28
*** ayogi has joined #openstack-meeting12:29
*** sdake_ has joined #openstack-meeting12:31
*** jtomasek_ has joined #openstack-meeting12:32
*** rossella_s has quit IRC12:33
*** rossella_s has joined #openstack-meeting12:34
*** sdake has quit IRC12:34
*** thorst_ has joined #openstack-meeting12:35
*** baoli has joined #openstack-meeting12:37
*** Apoorva has quit IRC12:40
*** baoli has quit IRC12:42
*** yamamoto has joined #openstack-meeting12:42
*** Apoorva has joined #openstack-meeting12:44
*** VW has joined #openstack-meeting12:45
*** ayogi has quit IRC12:48
*** Hosam has joined #openstack-meeting12:50
*** jaypipes has joined #openstack-meeting12:50
*** mickeys has joined #openstack-meeting12:51
*** palexster has quit IRC12:52
*** egallen has joined #openstack-meeting12:52
*** trinaths has quit IRC12:55
*** nadya has quit IRC12:55
*** mickeys has quit IRC12:55
*** palexster has joined #openstack-meeting12:57
*** Apoorva has quit IRC12:58
*** jtomasek_ has quit IRC13:01
*** rbrady has joined #openstack-meeting13:03
*** rbrady has quit IRC13:03
*** rbrady has joined #openstack-meeting13:03
*** kylek3h has quit IRC13:07
*** Apoorva has joined #openstack-meeting13:08
*** jmckind has joined #openstack-meeting13:09
*** askb has quit IRC13:12
*** trevormc has joined #openstack-meeting13:12
*** Hosam has quit IRC13:14
*** zz_dimtruck is now known as dimtruck13:17
*** Apoorva has quit IRC13:17
*** Apoorva has joined #openstack-meeting13:17
*** Apoorva has quit IRC13:22
*** yamamoto has quit IRC13:24
*** VW has quit IRC13:25
*** dimtruck is now known as zz_dimtruck13:26
*** Apoorva has joined #openstack-meeting13:26
*** trevormc has left #openstack-meeting13:29
*** dmorita has joined #openstack-meeting13:29
*** arxcruz has quit IRC13:29
*** fzdarsky|lunch is now known as fzdarsky13:33
*** Julien-zte has joined #openstack-meeting13:33
*** dmorita has quit IRC13:33
*** ricolin has joined #openstack-meeting13:33
*** Apoorva has quit IRC13:35
*** armstrong has joined #openstack-meeting13:39
*** kylek3h has joined #openstack-meeting13:40
*** hichihara has joined #openstack-meeting13:40
*** Apoorva has joined #openstack-meeting13:40
*** armstrong has quit IRC13:41
*** armstrong has joined #openstack-meeting13:41
*** davidsha has joined #openstack-meeting13:43
*** pradk has joined #openstack-meeting13:44
*** samP has quit IRC13:46
*** dprince has joined #openstack-meeting13:46
*** cburgess has quit IRC13:48
*** Apoorva has quit IRC13:49
*** Apoorva has joined #openstack-meeting13:49
*** cburgess has joined #openstack-meeting13:49
*** baoli has joined #openstack-meeting13:50
*** jlibosva has joined #openstack-meeting13:50
*** mickeys has joined #openstack-meeting13:52
*** ricolin has quit IRC13:52
*** ricolin has joined #openstack-meeting13:52
*** janzian has joined #openstack-meeting13:55
*** john-davidge has joined #openstack-meeting13:55
*** cleong has joined #openstack-meeting13:56
*** cartik has quit IRC13:56
*** gouthamr has joined #openstack-meeting13:56
*** mickeys has quit IRC13:57
*** lamt has joined #openstack-meeting13:58
*** shardy has joined #openstack-meeting13:59
*** shardy has left #openstack-meeting13:59
jlibosvaLet's get the party started14:00
jlibosva#startmeeting networking14:00
openstackMeeting started Tue Jan 31 14:00:02 2017 UTC and is due to finish in 60 minutes.  The chair is jlibosva. 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: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
*** boden has joined #openstack-meeting14:00
jlibosvaHello friends!14:00
*** korzen has joined #openstack-meeting14:00
jlibosva#topic Announcements14:00
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:00
*** haleyb_ has joined #openstack-meeting14:00
*** ihrachys has joined #openstack-meeting14:01
jlibosvaWe got some release related announcements14:01
jlibosvaWe're now in the release candidate phase this week14:01
jlibosva#link http://lists.openstack.org/pipermail/openstack-dev/2017-January/111074.html14:01
jlibosvaWhich means14:01
jlibosvaWe can't merge more features - unless it's been granted with feature freeze exception (FFE)14:01
jlibosva#link http://lists.openstack.org/pipermail/openstack-dev/2017-January/111083.html14:01
ajomakes sense14:02
jlibosvaWe'll talk more about Ocata in other topic14:02
*** Apoorva has quit IRC14:02
jlibosvanext version will be Pike and in order to make it awesome, as you know, there will be a project gathering in middle Feb14:02
jlibosva#link http://lists.openstack.org/pipermail/openstack-dev/2017-January/110040.html14:02
jlibosvaWe already have some topics but still feel free to add more items to the etherpad https://etherpad.openstack.org/p/neutron-ptg-pike14:03
jlibosvaI'm looking forward to see you there :)14:03
jlibosvaLast week was the week of PTL candidacy nomination14:03
*** Apoorva has joined #openstack-meeting14:03
jlibosvaWe have two briliant candidates :)14:03
jlibosvaThe elections are supposed to be this week14:04
jlibosvaDon't forget to use your ballot, you should get an email once elections are started14:04
*** ricolin has quit IRC14:04
jlibosvaAnybody has anything else to announce?14:04
*** ricolin has joined #openstack-meeting14:04
jlibosvalet's move on then14:04
jlibosva#topic Blueprints14:04
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:05
jlibosvaAs already advertised, we're in release candidate phase so we should be focusing on bugfixes scheduled to this milestone14:05
jlibosva#link https://launchpad.net/neutron/+milestone/ocata-rc114:05
*** sdague_ has quit IRC14:05
jlibosvaAs usual, blueprints that didn't make it to Ocata can be proposed/deferred to Pike.14:05
jlibosvaihrachys: korzen do you want OVO topic?14:05
ihrachysjlibosva: nah, I think it's better to skip since we are in freeze14:06
jlibosva#topic Bugs and gate failures14:06
*** openstack changes topic to "Bugs and gate failures (Meeting topic: networking)"14:06
jlibosvaWe had two major gate breakages in functional job last week14:06
jlibosvaBoth are solved by now14:06
jlibosvabut we'd like to get a better visibility of failures in gate14:06
jlibosva#link http://lists.openstack.org/pipermail/openstack-dev/2017-January/111214.html14:07
jlibosvaPlease read the above and please keep in mind to look at failures before issuing recheck on your patches14:07
ihrachysoh have we solved ovs native one?14:07
jlibosvaihrachys: no, that was not considered major by me :)14:07
*** raildo has joined #openstack-meeting14:07
*** lblanchard has joined #openstack-meeting14:07
jlibosvaihrachys: the functional is now about 10% in check queue14:07
jlibosvaif it would stay it like this, it would be awesome14:07
haleyb_there is a privsep fix working its way through that will help in gate as well14:08
jlibosvahaleyb_: do you have a link?14:08
haleyb_bug 166030514:08
openstackbug 1660305 in neutron "DVR multinode job fails over 20 tests" [High,In progress] https://launchpad.net/bugs/1660305 - Assigned to Oleg Bondarev (obondarev)14:08
ajothis reminds me (about ovs native) that I left this half way done: https://review.openstack.org/#/c/425623/14:08
ajoI wonder if it's of any use, or if it's actually going to affect anything after latest discussions.14:09
jlibosvahaleyb_: thanks, I see it's already approved14:09
haleyb_although maybe that job isn't voting, but the privsep failures are random14:09
anilvenkatajlibosva, ajo ihrachys haleyb As you know, for DVR+HA gate job, this patch is needed https://review.openstack.org/#/c/383827/14:09
jlibosvaajo: I saw iwamoto updated the bug with some interesting findings14:10
* ajo reads14:10
*** spzala has joined #openstack-meeting14:10
anilvenkatajlibosva, ajo haleyb but it is not getting devstack-gate core reviewers attentions14:10
jlibosvaanilvenkata: yeah, we would need to go to openstack-infra and poke people there14:11
anilvenkatajlibosva, I am regularly pinging clarkb and sdague14:11
jlibosvaanilvenkata: thanks14:11
anilvenkatafor its review14:11
jlibosvawe also have some failures in other tempest jobs, one of the most critical I have seen are libvirt crashes14:12
ihrachysajo: it seems worth exploring. one thing would be first to check if we see the same failures now that a patch from kevinbenton landed that could influence things14:12
jlibosvaihrachys: which patch?14:12
ajowhich patch?14:12
*** arxcruz has joined #openstack-meeting14:13
ihrachys"It's not clear that this was a cause of the bug though, so14:13
ihrachysthis fix is only related."14:13
*** princenana has joined #openstack-meeting14:13
*** arxcruz has quit IRC14:14
jlibosvahm, merged very recently .I was wondering whether it can be the cause that functional failure rate is "so low" :)14:14
jlibosvawe'll see.14:15
ajohmmm :)14:15
jlibosvaI also wanted to leave these two bugs related to mentioned libvirt crashes14:15
jlibosvahttps://bugs.launchpad.net/openstack-gate/+bug/1638982 and https://bugs.launchpad.net/nova/+bug/164391114:15
openstackLaunchpad bug 1638982 in OpenStack-Gate "libvirtd randomly crashes on xenial nodes with "realloc(): invalid next size"" [Undecided,Confirmed]14:15
openstackLaunchpad bug 1643911 in OpenStack Compute (nova) "libvirt randomly crashes on xenial nodes with "*** Error in `/usr/sbin/libvirtd': malloc(): memory corruption:"" [Medium,Confirmed]14:15
jlibosvajust in case you get hit by those in your patches14:15
jlibosvaajo: you were a bug deputy last week, right?14:16
ajosomebody is smashing the heap :)14:16
ajojlibosva affirmative14:16
*** Apoorva has quit IRC14:16
jlibosvaajo: do you want to highlight some bugs?14:16
jlibosvahow was the week?14:17
ihrachysnot sure what we can do with libvirtd. :( crying aloud?14:17
*** sshnaidm has quit IRC14:17
ajolet me check if there is something missing beyond what you said.14:17
ajoihrachys may be get the ubuntu guys update it, or move to centos :P14:17
ajojlibosva: The memory  / OOM issues,14:17
*** zz_dimtruck is now known as dimtruck14:17
*** sshnaidm has joined #openstack-meeting14:17
openstackLaunchpad bug 1656386 in neutron "Memory leaks on Neutron jobs" [Critical,Confirmed] - Assigned to Darek Smigiel (smigiel-dariusz)14:17
ajobut not sure there's anything we could do about that14:18
*** arxcruz has joined #openstack-meeting14:18
jlibosvaihrachys: I noticed that the compute one is "Medium" importance so I cried there for bump14:18
ajokevinbenton increased swapiness, but still OOM is invoked while there's only 700k of 7G of swap used14:18
korzenI could use more reviews on https://review.openstack.org/#/c/273546 Add support for Keepalived VRRP health check to get this merged in Ocata14:18
ajothere was another one related to linuxbridge conntrack clearing, 1 sec14:19
*** lblanchard has quit IRC14:19
openstackLaunchpad bug 1657260 in neutron "Established connection don't stops when rule is removed" [Critical,In progress] - Assigned to Slawek Kaplonski (slaweq)14:19
*** anilvenkata has quit IRC14:19
*** lblanchard has joined #openstack-meeting14:19
haleyb_that was approved but failing gate14:19
ajoit's WIP by slawek, in iptables  non-hybrid firewall driver the zones aren't used, but we try to clear the entries -in a zone- so it fails14:19
jlibosvakorzen: thanks, it's scheduled to rc1 so hopefully it will get proper attention14:20
haleyb_i thikn it was approved14:20
jlibosvahmmm :(14:21
jlibosvaI see that linuxbridge tempest job is about 35% failure rate14:21
*** Apoorva has joined #openstack-meeting14:21
*** mriedem has quit IRC14:23
jlibosvaanybody has any other bug that deserves attention?14:23
jlibosvaor bugfix14:23
*** lamt has quit IRC14:23
jlibosvakorzen: thanks14:23
korzenhaleyb_, can you +W on ^ ?14:24
*** adiantum has quit IRC14:24
jlibosvahaleyb_: yep, I set the bug to rc1, so I think we're good to go14:24
*** gcb has quit IRC14:24
ihrachysyeah, and it's test only change14:24
*** adiantum has joined #openstack-meeting14:24
ajojlibosva  where did you see linuxbridge jobs on 35% failure rate?14:24
*** dmacpher has joined #openstack-meeting14:24
*** dmacpher has quit IRC14:24
jlibosvaajo: sorry, I was looking at multinode-nv14:25
*** yamamoto has joined #openstack-meeting14:25
jlibosvathe voting is at 13%, sorry :)14:25
jlibosvaajo: thanks for fixing me :)14:25
ajojlibosva np, I was looking for the specific failures, and I found a much lower rate, so I thought I was looking at the wrong place actually14:26
*** Apoorva has quit IRC14:26
jlibosvaajo: I feel like the linuxbridge job is failing only on the patches that I'm looking at. I see it failing almost the whole time, so I wasn't surprised by 35%14:26
*** adiantum has quit IRC14:26
*** Apoorva has joined #openstack-meeting14:27
jlibosvaif there are no other bugs or patches, I'd like to get to getting a new deputy for this week14:27
ajoyou were biased14:27
jlibosvaI would like to take the next week, if there are no objections :)14:27
*** adiantum has joined #openstack-meeting14:27
*** dimtruck is now known as zz_dimtruck14:27
ihrachysI don't think anyone would object...14:28
ajocome'on I offer a beer @ atlanta :P :)14:28
jlibosvabut we still need a hero for this week14:28
jlibosvabeer for this week bug deputy in atlanta from ajo. how could anyone say no to this?14:29
hichiharaThe beer is mine!14:29
jlibosvahichihara is the winner!14:29
jlibosvaI'll update the wiki after meeting :)14:29
ajohichihara you got it!! :D thanks :) Spanish or american beer? ;-)14:29
hichiharaAmerican beer please :)14:30
ajoconsider it done :D14:30
jlibosva#action ajo to buy hichihara an american beer in atlanta14:30
*** Apoorva has quit IRC14:31
jlibosva#topic Docs14:31
*** openstack changes topic to "Docs (Meeting topic: networking)"14:31
jlibosvajohn-davidge: hello!14:31
*** reedip_ has joined #openstack-meeting14:31
*** Apoorva has joined #openstack-meeting14:31
john-davidgejlibosva: Hello!14:31
jlibosvajohn-davidge: do you have any updates wrt docs14:31
*** yamamoto has quit IRC14:32
john-davidgejlibosva: Nothing specific from me on docs this week. I've been discussing some possible to changes to how we deal with the DocImpact tag with the new Docs PTL, but we don't have anything to share just yet.14:32
jlibosvajohn-davidge: ok, thanks :)14:32
*** electrocucaracha has joined #openstack-meeting14:32
jlibosvaso maybe we can move to the next topic14:33
*** jmckind_ has joined #openstack-meeting14:33
jlibosva#topic Transition to OSC14:33
*** openstack changes topic to "Transition to OSC (Meeting topic: networking)"14:33
jlibosvaamotoki: hi :) do you want to update us?14:33
amotokiI checked the current status of OSC transition. 95 of 126 are completed.14:33
*** VW has joined #openstack-meeting14:34
*** iyamahat has joined #openstack-meeting14:34
john-davidgeamotoki: Great progress!14:34
*** jmckind has quit IRC14:34
amotokiAs far as I checked, the biggest remaining one is FIP associate/disassociate.14:34
amotokithis is the progress chart https://docs.google.com/spreadsheets/d/1ueCvIKUfpUaLFm_3YTT4MkuTV-PYIdeErnt7Wleshl0/edit#gid=014:34
amotokiI think we can ship neutron CLI with deprecation notice (as we see now)14:35
jlibosvaamotoki: great news! thanks14:35
amotokiother than FIP (dis)associate, most commands are admin-specific or less used like flavor.14:35
*** Apoorva has quit IRC14:35
reedip_for the FIP , I think we have reached a conclusion14:36
amotokithanks all for folks working on OSC transition!14:36
reedip_but minor adjustments need to be done14:36
amotokireedip_: yeah, I saw it14:36
*** cloudrancher has quit IRC14:36
amotokibut I am not sure OSC team has a plan for a new release in Ocata time span.14:36
amotokireedip_: do you have any?14:37
reedip_None as of now that I know amotoki14:38
reedip_OSC has almost been finished for Ocata14:38
jlibosvaamotoki: reedip_ thanks for updates and good news :)14:38
jlibosvacan we move the next topic?14:39
jlibosva#topic Neutron-lib and planned neutron refactoring14:39
*** openstack changes topic to "Neutron-lib and planned neutron refactoring (Meeting topic: networking)"14:39
jlibosvaboden: hi, do you want to say a few things about neutron-lib?14:39
*** iyamahat has quit IRC14:40
*** armstrong has quit IRC14:40
jlibosvamaybe that means "no" :)14:40
*** armstrong has joined #openstack-meeting14:41
jlibosvawe have two things added to the on demand agenda but I feel like we've already had the "Disable security group filter refresh on DHCP port changes" one14:41
jlibosvaand I also don't see mdorman online14:41
bodenjlibosva sorry I stepped away14:42
jlibosvaboden: I'm now not sure if you stepped away from keyboard or neutron-lib :)14:43
bodenthings are pretty idle on the neutron-lib front at least in terms of landing patches. I think this is mainly beause we cut stable 1.1.0 for Ocata and folks are focusing on getting neutron out the door14:43
bodenso not much to say really. There are some “lib impact” patches, but IMO they are obviously not candidates for ocata so we can talk about them later14:44
*** galstrom_zzz is now known as galstrom14:44
jlibosvaboden: ok, thank you for updates :)14:45
jlibosvacan we move on?14:45
*** mtanino has joined #openstack-meeting14:45
bodenjlibosva yes thanks14:45
*** adiantum has quit IRC14:45
jlibosva#topic Logging API for security groups14:45
*** openstack changes topic to "Logging API for security groups (Meeting topic: networking)"14:45
jlibosvarossella_s: you added this topic, right?14:46
rossella_sjlibosva, nope14:46
*** armstrong has quit IRC14:46
jlibosvarossella_s: hmm, there is your name written on the meeting wiki page :)14:46
*** lamt has joined #openstack-meeting14:47
rossella_sjlibosva, that's probably from last week, annp wanted to talk about it14:47
jlibosvarossella_s: aha, I checked last meeting logs and didn't see the topic there14:48
jlibosvaand I don't see annp around14:48
*** armstrong has joined #openstack-meeting14:48
*** jmckind has joined #openstack-meeting14:48
jlibosvaso maybe we can defer the discussion14:48
jlibosvaanybody has anything else to bring up?14:48
rossella_she's sleeping I guess, anyway since we are discussing it, it would be good to get more eyes on  https://review.openstack.org/#/c/203509/14:49
rossella_sand see how to move that forward14:49
*** hongbin has joined #openstack-meeting14:49
*** jamesdenton has joined #openstack-meeting14:50
jlibosvaI saw the spec got some discussions lately on the gerrit14:50
*** zaneb has quit IRC14:50
*** zaneb has joined #openstack-meeting14:50
*** vj4 has joined #openstack-meeting14:50
jlibosvarossella_s: do you think starting a ML thread would help to proceed?14:51
jlibosvaor gerrit is sufficient?14:51
*** zz_dimtruck is now known as dimtruck14:51
*** armstrong has quit IRC14:52
*** jmckind_ has quit IRC14:52
*** armstrong has joined #openstack-meeting14:52
ihrachysgerrit should be fine, it get enough eyes it seems?14:52
*** mickeys has joined #openstack-meeting14:54
jlibosvamaybe more people from control plane core team could have a look too. It seems armax and yamamoto are the active ones there14:54
jlibosvaoh, I also see hichihara :)14:54
hichiharayes :) I'm active on the spec.14:55
jlibosvawe have 5 minutes. anybody has some topic to discuss?14:55
jlibosvaor we could spend those 5 minutes by telling non-political jokes :)14:55
jlibosvaor we can end earlier14:55
*** bobh has joined #openstack-meeting14:55
hichiharaI have a small topic. I'm working on https://review.openstack.org/#/c/413662/14:55
*** korzen has quit IRC14:56
hichiharaihrachys amotoki: What do you think about it?14:56
*** rbak_ has joined #openstack-meeting14:56
hichiharaihrachys amotoki: Should I skip it on Pike and discuss more?14:56
jlibosvathe bug is scheduled to mitaka rc1, I think we missed the deadline there :)14:56
ihrachysit still doesn't give a discoverable way (api level) to learn if tags for those resources are supported.14:56
ihrachyshichihara: the change itself should not be huge, but we need the empty extension14:57
*** eharney has joined #openstack-meeting14:57
amotokithe topic is about API discoverability on how we can add more resources supported by tag API.14:57
*** armstrong has quit IRC14:57
amotokiaccording to the current convention, we need to add some shim extension.14:57
hichiharaI understand14:57
hichiharaSo that's extensions/tag-ext?14:58
amotokii understand 'tag-xxx', 'tag-xxx2' .... are ugly convention, but tag-ext sounds reasonable now14:58
*** mickeys has quit IRC14:59
hichiharaIihrachys amotoki: 'm OK. I'll do. Thanks14:59
jlibosvahichihara: thanks :)14:59
jlibosvathanks everyone for showing up :)14:59
ihrachysand we have CI meeting in 1h!15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Tue Jan 31 15:00:05 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2017/networking.2017-01-31-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2017/networking.2017-01-31-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2017/networking.2017-01-31-14.00.log.html15:00
*** haleyb_ has quit IRC15:00
*** Julien-zte has quit IRC15:00
*** electrocucaracha has left #openstack-meeting15:00
*** Julien-zte has joined #openstack-meeting15:00
*** Julien-zte has quit IRC15:01
ajohi :)15:01
davidshaQoS is here right?15:02
*** Julien-zte has joined #openstack-meeting15:02
*** slaweq_ has joined #openstack-meeting15:02
ajo#startmeeting neutron_qos15:02
openstackMeeting started Tue Jan 31 15:02:22 2017 UTC and is due to finish in 60 minutes.  The chair is ajo. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
ajoHello :)15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:02
openstackThe meeting name has been set to 'neutron_qos'15:02
*** shintaro has joined #openstack-meeting15:02
ajo#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_qos)"15:02
*** phealy has joined #openstack-meeting15:02
*** john-davidge has left #openstack-meeting15:02
ajoQos driver is finally in shape and refactor merged15:02
*** john-davidge has joined #openstack-meeting15:02
davidshahi njohnston15:03
ajo#link https://review.openstack.org/#/c/396651/15:03
ajosorry for being sooooo slow :/15:03
*** john-davidge has left #openstack-meeting15:03
ajoWe shall ping the relevant people on midokura (yamamoto), ovn (russelb),15:03
ajonsx (garyk) to see if they need any help migrating to the new15:03
ajomodel, the old notification_driver support will be removed in Pike15:03
*** bkopilov has joined #openstack-meeting15:03
*** tidwellr_ has joined #openstack-meeting15:03
ajo#action ajo ping all qos-driver implementers to update their drivers in pike, change shall be easy,15:03
ajoNow slaweq_ is working on the 2nd thing: Enhanced validation15:04
ajo#link https://review.openstack.org/#/c/426946/15:04
ajofor Pike15:04
*** dimtruck is now known as zz_dimtruck15:04
slaweq_I will do my best to finish it asap15:05
ralonsohI'll review this patch tomorrow and I'll follow it15:05
ajoThe structural changes made him reboot his original patch15:05
ajoBut I hope the new interface will help15:05
slaweq_now it should be easier than it was before Your refactor15:05
*** annegentle has joined #openstack-meeting15:05
ajoyes, before it was becoming a bit too complicated, let's see how it will look now15:05
slaweq_as I was looking into it yesterday it should be easier but we will see :)15:06
*** mriedem has joined #openstack-meeting15:06
ajoMy colleagues always fear me when I say it will be easy, it never is :) right dalvarez ? :P15:06
slaweq_I know, that's why I wrote "it should be" :P15:07
ajoso... I have another point for documentation15:07
*** nkrinner is now known as nkrinner_afk15:07
ajo#topic Documentation15:07
ajoNetworking guide needs to be updated about minimum egress bandwidth15:07
*** openstack changes topic to "Documentation (Meeting topic: neutron_qos)"15:07
ajo#link https://bugs.launchpad.net/neutron/+bug/161876915:07
ajo#link https://bugs.launchpad.net/neutron/+bug/161876215:07
openstackLaunchpad bug 1618769 in openstack-manuals " SR-IOV: add agent QoS driver to support egress minimum bandwidth" [Low,Confirmed] - Assigned to Miguel Angel Ajo (mangelajo)15:07
*** jlibosva has left #openstack-meeting15:07
openstackLaunchpad bug 1618762 in openstack-manuals " Add QoS minimum bandwidth rule for instance egress traffic" [Low,Confirmed] - Assigned to Miguel Angel Ajo (mangelajo)15:07
ajoI planned to work on that15:07
ajoit shall be easy15:07
ajobut we must have it ready for the release, this was on Newton I think, but we forgot ':D15:08
ralonsohI can take one of this15:08
dalvarezajo, lol im scared now15:08
ralonsohone of these15:08
ajoX) dalvarez15:08
ajoralonsoh it's the same one I think, not sure if we need to do anything special for SR-IOV15:08
ralonsohNo, nothing special15:09
ajoone was generated for the "api changes" and the other one for docimpact on the SR-IOV15:09
ralonsohahhh I see15:09
ajoso one commit shall close it all, may by I can write, and I can ping you for reviews ralonsoh ?15:09
ajomay by->may be15:09
ajohi reedip_ I've got a point for you later ;)15:10
reedip_:D ok ajo15:10
ajo#topic Bugs15:10
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:10
*** zaneb has quit IRC15:10
ajo#link https://bugs.launchpad.net/neutron/+bug/164950315:10
openstackLaunchpad bug 1649503 in neutron "Mechanism driver can't be notified with updated network" [High,In progress] - Assigned to Hong Hui Xiao (xiaohhui)15:10
ajoWe need kevinbenton's help on this one15:10
*** zaneb has joined #openstack-meeting15:10
ajoit's related to some recent change, now when you detach a policy from a network, that's not notified properly15:10
ajothis looks like a high priority bug (in the context of QoS)15:11
slaweq_but it's waiting for action for quite long time now15:11
*** ayogi has joined #openstack-meeting15:11
*** kaisers_ has quit IRC15:11
slaweq_maybe You can ask kevinbenton to look on it? :)15:11
ajoyes, I will,15:12
ajoI started by adding him to the bug15:12
ajoI will ping him personally15:12
*** ayogi has quit IRC15:12
*** kaisers has joined #openstack-meeting15:12
ajo#action ajo ping kevinbenton about bug 164950315:12
openstackbug 1649503 in neutron "Mechanism driver can't be notified with updated network" [High,In progress] https://launchpad.net/bugs/1649503 - Assigned to Hong Hui Xiao (xiaohhui)15:12
*** ayogi has joined #openstack-meeting15:13
*** armstrong has joined #openstack-meeting15:13
ajo#link https://bugs.launchpad.net/neutron/+bug/1627749 better error handling15:13
openstackLaunchpad bug 1627749 in neutron "qos driver api can have better error handling" [Medium,Confirmed] - Assigned to Miguel Angel Ajo (mangelajo)15:13
ajothere was some work around that on the qos driver refactor, but not sure if enough15:13
* ajo looks for the link15:13
*** ayogi has quit IRC15:14
ajomay be this is not enough to close that bug15:14
*** cdelatte has joined #openstack-meeting15:14
ajoshall we probably, let all drivers be called, and then raise the exception after rpc push happens ?15:14
*** ayogi has joined #openstack-meeting15:14
*** tovin07 has joined #openstack-meeting15:14
ralonsohI don't think so15:15
ajowe don't have yamamoto here15:15
ralonsohI prefer the way is now implemented15:15
ajoralonsoh the problem with current implementation, is that if one driver fails, the others aren't called at all15:15
ajomay be some are called, some are not15:15
ralonsohI know15:15
ajodepending on the order15:16
ralonsohbut no driver should fail15:16
ajoit's very undeterministic15:16
ajothat is true15:16
*** fnaval has joined #openstack-meeting15:16
ajoif a driver fails it's it's responsibility to retry later, and resync...15:16
ajoa bad implementation of one, should not affect the others, or the rpc15:16
ajoit's not bad if we are more robust in the face of external errors15:16
*** jmckind has quit IRC15:17
ajounless we find a good reason why that would be problematic15:17
ralonsohok, that's a new patch!15:17
*** kaisers has quit IRC15:17
ajo(code being more complex can be a good reason against it, but I believe it shouldn't be very complicated *warning on perceived complexity O:)* )15:17
ajoralonsoh I will try to put a new patch for this, see how it looks, code goes weird I'm ok to drop it15:18
* ajo looks at https://bugs.launchpad.net/neutron/+bugs?field.tag=qos15:19
ajo#link https://bugs.launchpad.net/neutron/+bug/165738115:19
openstackLaunchpad bug 1657381 in neutron "QoS drivers need to implement a precommit for the actions" [Medium,In progress] - Assigned to Miguel Angel Ajo (mangelajo)15:19
ajoThis one, after a thought, is not very clear to me that it's necessary15:19
*** nadya has joined #openstack-meeting15:19
*** rbartal__ has quit IRC15:19
ajosince in the end, drivers are not supposed to fail on any policy modification15:19
ajomay be what's bad for them is good for other drivers15:20
*** rbartal has quit IRC15:20
ajoand that will be handled by the enhanced validation15:20
*** rbartal_ has quit IRC15:20
ajobad for them = "the specific driver can't handle it"15:20
ajoso, the fact that ODL for example writes to a log, and then sends the log, is implementation detail, they can do that in the one existing call15:21
ajoand if they fail, it's their responsibility, again, to retry to sync it later15:21
ajoralonsoh thoughts?15:21
ajoI wish I had an ODL'r here :D15:21
*** nadya has quit IRC15:21
ralonsohthe point is why they need those calls?15:21
ralonsohthey don't implement any action for them15:22
ajoralonsoh exactly, and, even if they need them, if we're not goint to allow exceptions happening to stop the db transactions I see no benefit15:22
slaweq_I think that maybe we should make it working with any plugin, not only ML2 which not uses such precommit15:22
ralonsohbuy I'll review ODL code15:22
*** kaisers has joined #openstack-meeting15:22
slaweq_so maybe it's worth to do it if some plugins needs it15:22
ajoslaweq_ if there's good justification, right15:23
ajobut they still failed to justify the need15:23
ajoor may be they did, but I didn't got it15:23
ajo#link https://bugs.launchpad.net/neutron/+bug/163918615:24
openstackLaunchpad bug 1639186 in neutron "qos max bandwidth rules not working for neutron trunk ports" [Low,Confirmed] - Assigned to Luis Tomas Bolivar (ltomasbo)15:24
ajoltomasbo  ^15:24
ajoany advance on this? did you look at russellb comments  here https://bugs.launchpad.net/neutron/+bug/1639186/comments/11 ?15:24
ajoI'm pinging him15:25
ajoralonsoh russellb says they use queues, and they steer the traffic using OF rules15:25
ltomasbohi ajo15:25
ajohi ltomasbo  :)15:25
ltomasbono, I did not take any further action on that15:25
*** edtubill has joined #openstack-meeting15:26
*** janzian has left #openstack-meeting15:26
ajoralonsoh : so may be that will be doable when we have min bw and queues in OVS. ?15:26
*** jmckind has joined #openstack-meeting15:26
ajoltomasbo may be I should detach you from the bug for now for just in case anyone else wants to step up for it?15:26
*** iyamahat has joined #openstack-meeting15:26
ralonsohbut we still don't have min in OVS15:26
*** kaisers has quit IRC15:26
ltomasboajo: sure! please do15:27
ajoralonsoh correct, but, it would be similar to what you did in LB, and then we could get rid of this bug with trunk ports15:27
*** boden has left #openstack-meeting15:27
ralonsohajo: I tried to do this, but we don't have the IFB like in Linux Bridge15:27
ralonsohajo: I tried to figure out how to implement this, without any luck...15:28
ajoralonsoh yes, we'd need to rely on queues, etc... all the thing we talked about, *not easy*15:28
ajolet's revisit it on pike and try to get it going. Will you be around on the PTG?15:28
ralonsohyes, we can talk about his in the PTG15:29
ajoralonsoh we also have the one related to router GW ports15:30
ajoI can't find it now15:30
ralonsohthis one?15:30
ajo#link https://review.openstack.org/#/c/425218/15:31
*** jaugustine has joined #openstack-meeting15:31
ajooh, I must review it again15:31
ralonsohyes, I know. kevinbenton told us to implement it15:31
*** ayogi has quit IRC15:31
ralonsohand https://review.openstack.org/#/c/425280/15:32
*** iyamahat has quit IRC15:32
*** armax has joined #openstack-meeting15:32
ajo#link https://review.openstack.org/#/c/425280/15:32
ajoplease folks review those two ^15:33
ajothanks ralonsoh !!15:33
ajoany bug I'm missing?15:33
*** armstrong has quit IRC15:34
ajo#topic RFEs15:34
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:34
ajoSo, after the validation, for pike, we have in pipeline:15:34
ajo* instance ingress bw limiting,15:34
slaweq_yes, it waits for improved validation :)15:35
ajo* strict minimum bw (integration with nova placement api)15:35
*** kaisers has joined #openstack-meeting15:35
ajoI believe bits are in place for those two15:35
*** Leom has joined #openstack-meeting15:35
ajowe can think of VLAN 802.1p if somebody is willing to take it, it shall be easy15:36
reedip_ajo : link ?15:36
ralonsohdo you mean ECN?15:37
ajo#link https://bugs.launchpad.net/neutron/+bug/1560961. instance-ingress15:37
openstackLaunchpad bug 1560961 in neutron "[RFE] Allow instance-ingress bandwidth limiting" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)15:37
ajo#link https://bugs.launchpad.net/neutron/+bug/1578989 strict minimum bw15:37
reedip_neverming, got it : https://bugs.launchpad.net/neutron/+bug/150563115:37
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:37
openstackLaunchpad bug 1505631 in neutron "[RFE] QoS VLAN 802.1p Support" [Wishlist,Confirmed] - Assigned to Kannan Raman (kannanrc20)15:37
ajo#link https://bugs.launchpad.net/neutron/+bug/150563115:37
davidsharalonsoh: There is another for mapping dscp to v-lan pcp15:37
ajoyes, we need to talk about that one15:37
ajobut I wanted to talk about reedip's ECN proposal again15:38
ajohe updated the etherpad and I couldn't look at it until today15:38
ajo#link https://etherpad.openstack.org/p/QoS_ECN15:38
*** jprovazn has joined #openstack-meeting15:38
ajoreedip_ : most details make sense, but we can't control the VM internal settings15:38
reedip_ajo : hmm, okay15:39
*** mtanino_ has joined #openstack-meeting15:39
ajoreedip_ it will be OS dependant, etc... and it's no business of neutron or nova to tweak anything inside the VMs15:39
ajowe can provide documentation, or heat templates for that15:39
*** shintaro has quit IRC15:39
ajoin linux I believe it's on by default15:39
ajomay be I'm wrong15:39
reedip_ajo : in linux. no , ECN has to be enabled15:39
*** mtanino has quit IRC15:40
ajoaha, so we may want to provide documentation to let people do that15:40
reedip_I think yes, we can provide heat templates for that / documentation if required15:40
ajoI thought It was on by default15:40
ajothe proposal, has an API that is a bit out of how we handle everything else in QoS plugin now15:40
ajoIt'd be great if we can find a way to fit it in the current model15:40
reedip_ajo : yes, I saw that comment, would try to integrate it , but need to look more into it .15:41
ajomay be, if the change to routers is not invasive,15:41
ajo(or changes performance)15:41
ajowe could just implement that in the l3 agent15:41
ajoand have it enabled by default15:41
davidshaSo if the ECN bit is set and its not enabled, the packet isn't echo'ed with the receive bit set right??15:41
ajoI believe that what reedip_ proposes is that our routers will set the flag on the outgoing packet, that then will be echoed by the receiving machine back to the sender15:42
reedip_davidsha : you mean if one router has detected COngestion, but one of the End points ( a VM for example ) doesnt have ECN enabled, then YES, the ACK packet back to the sender wont have the ECN receievd bit set15:42
ajoVM1 sends packet15:43
ajopacket crosses router (congested one)15:43
davidshareedip_: ack, thanks!15:43
ajorouter sets flag on packet15:43
ajopacket arrives VM215:43
ajoVM2 sends the echo bit on next TCP frame to sender15:43
ajomissing details for this proposal are:15:43
ajo1) how to do it in the neutron routers15:43
ajo2) ways to fit this on the current model15:44
ajofor 2, may be we don't even need it, but if we need conditional enablement of ECN on the routers, we could, for example:15:44
ajolet admins set policies with an ECN rule in the external and internal networks of the router15:44
ajoand when at least one internal network, and the external network provide ECN, we ECN-enable the router15:44
reedip_ajo : ack15:45
ajothis would require integration of QoS in l3, but now l3 has a framework to add extensions, it should be doable15:45
ajothanks njohnston !! ;)15:45
* njohnston bows15:45
reedip_thanks njohnston :D15:45
ajoreedip_ I don't know about 1, if you show me a viable POC of how to do it in the low level (qrouter), then we can formalize this RFE properly15:46
reedip_ajo : yep, this is an Action Item for me before the next meeting15:46
ajo#action reedip ECN RFE refinement :)15:46
ajodavidsha did you want to talk about the DSCP/VLAN mapping ?15:47
ajomay be we should cover first the basic VLAN rules15:47
ajoI asked the submitter for more details and never answered15:47
reedip_ajo : meanwhile , I think I can voluteer  on the 802.1p if its available15:47
davidshaajo: kk, it wan't my rfe I'd just read it previously ;)15:47
*** kaisers has quit IRC15:48
ajoreedip_ https://bugs.launchpad.net/neutron/+bug/1505631 It seems like you could revive it in Pike, it's postponed15:49
openstackLaunchpad bug 1505631 in neutron "[RFE] QoS VLAN 802.1p Support" [Wishlist,Confirmed] - Assigned to Kannan Raman (kannanrc20)15:49
ajowhich means, it was approved, but we were waiting on other stuff, or we had no hands :)15:49
davidshaJust for clarity on this going forward, this would mean we'd have the dscp marking rule, a pcp marking rule and a "traffic class" marking rule correct?15:49
reedip_Yes, I will take it up ajo  for Pike15:50
ajodavidsha what was pcp? %)15:50
davidshaajo: the vlan version of dscp it stands for Priority Code Point15:51
ajothat would be then 2 ?15:51
ajo1) DSCP15:51
ajo2) VLAN15:51
davidshaThere was another RFE for mapping over DSCP and PCP if I recall15:52
davidshaso Pcp is a 0-7 values and dscp is mapped to 0-7 traffic classes.15:52
ajodavidsha, let's look at that when we have vlan, but ye15:53
ajoat that point, DSCP marking rules would be incompatible with mapping rules15:53
ajoor am I getting it wrong?15:53
ajodo you mean15:53
ajomapping the DSCP flags when going over vlan? or what ?15:54
ajothat RFE we mentioned before?15:54
davidshaajo: kk, I'm not sure who proposed it but I recall reading the RFE.15:54
*** mickeys has joined #openstack-meeting15:54
ajodavidsha link, or bring it to next meeting :)15:55
davidshaajo: It was a while since I read it so I'm not entirely sure.15:55
ajoanyway, unless of it being of special interest to you, or anyone willing to code it, I suspect we have enough in our plate for Pike already :)15:55
*** haleyb_ has joined #openstack-meeting15:55
*** bobh has quit IRC15:55
ajowe have the openflow pipeline in the queue too, which could be cool to fix for Pike too :)15:56
ralonsohone more: https://bugs.launchpad.net/neutron/+bug/163922015:56
openstackLaunchpad bug 1639220 in neutron "[RFE] Default action for RBAC" [Undecided,New] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:56
ralonsohthis one is very short15:56
ajooh right15:56
*** VW has quit IRC15:56
ralonsohjust waiting your reply15:56
* ajo reads15:57
ajoyes, having an api to set a per-tenant default could make sense15:58
ajoa lot of sense actually15:58
ajoI'm trying to add tags, but it ignores me15:58
ajoralonsoh can you add #qos and #rfe tags?15:58
*** mickeys has quit IRC15:59
ajoralonsoh we would need that triaged by the drivers meeting15:59
ajobut, makes sense to me, I'm going to comment15:59
ajoand close the meeting, we have 30 secs15:59
ralonsohajo: done15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Tue Jan 31 15:59:54 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-01-31-15.02.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-01-31-15.02.txt15:59
ajothank you folks :)16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-01-31-15.02.log.html16:00
*** bobh has joined #openstack-meeting16:00
*** haleyb_ has quit IRC16:00
ihrachys#startmeeting neutron_ci16:00
openstackMeeting started Tue Jan 31 16:00:42 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
*** hichihara has quit IRC16:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
*** slaweq_ has left #openstack-meeting16:00
*** jlibosva has joined #openstack-meeting16:01
*** VW has joined #openstack-meeting16:01
ihrachyshello everyone, assuming there is anyone :)16:01
*** jdurgin1 has joined #openstack-meeting16:01
ihrachysarmax: kevinbenton: jlibosva: ding ding16:01
*** iyamahat has joined #openstack-meeting16:01
*** cathrichardson has joined #openstack-meeting16:02
*** absubram has joined #openstack-meeting16:02
ihrachysjlibosva: looks more like it's you and me :)16:02
*** cody-somerville has joined #openstack-meeting16:02
*** cody-somerville has quit IRC16:02
*** cody-somerville has joined #openstack-meeting16:02
jlibosvaihrachys: what is the agenda?16:02
ihrachyswell I was going to present the initiative and go through the etherpad that we already have, listing patches up for review and such.16:03
ihrachysand maybe later brain storming on current issues16:03
jlibosvaok, I looked at the etherpad and put some comments to the ovs failure16:03
ihrachysif it's just me and you, it may not make much sense16:04
*** Drago1 has joined #openstack-meeting16:04
*** Drago1 has left #openstack-meeting16:04
jlibosvaat least we would have a meeting minutes16:04
*** rcernin has quit IRC16:04
jlibosvaif we come up with any action items16:04
ihrachysright. ok. so, this is the first CI team meeting, that spurred by latest issues in gate16:04
ihrachysthere was a discussion before on the issues that was captured in https://etherpad.openstack.org/p/neutron-upstream-ci16:05
*** cathrichardson has left #openstack-meeting16:05
ihrachyswe will use the etherpad to capture new details on gate problems in the future16:05
*** VW has quit IRC16:05
*** cathrichardson has joined #openstack-meeting16:05
ihrachysthere were several things to follow up on, so let's walk through the list16:05
*** VW has joined #openstack-meeting16:05
ihrachys1. checking all things around elastic-recheck, whether queries can target check queue and such. I am still to follow up on that with e-r cores, but it looks like they accepted a query targeting functional tests yesterday, so we hopefully should be able to classify func test failures.16:06
*** nadya has joined #openstack-meeting16:06
*** absubram_ has joined #openstack-meeting16:07
*** absubram has quit IRC16:07
*** absubram_ is now known as absubram16:07
ihrachys2. "banning rechecks without bug number" again, I am to check with infra on that point16:07
ihrachys3. armax added func tests periodic job to grafana: https://review.openstack.org/#/c/426308/16:07
ihrachyssadly, I don't see it showing up in periodic dashboard, see http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=4&fullscreen16:08
ihrachysI see 3 trend lines while there are supposed to be 5 of those as per dashboard definition16:08
ihrachysthis will need a revisit I guess16:09
jlibosvawas there a run already?16:09
*** cathrichardson has left #openstack-meeting16:09
ihrachysthe patch was landed 32 hours ago, and it's supposed to trigger daily (?)16:09
ihrachysI guess we can give it some time and see if it heals itself16:09
*** trinaths has joined #openstack-meeting16:09
ihrachysbut the fact that another job in the dashboard does not show up too is suspicious16:09
jlibosvaoh, sorry :D I thought it's still 30th Jan today16:10
*** csomerville has joined #openstack-meeting16:10
ihrachys#action armax to make sure periodic functional test job shows up in grafana16:10
*** ekuris__ has quit IRC16:10
ihrachys#action ihrachys to follow up on elastic-recheck with e-r cores16:10
ihrachys#action ihrachys to follow up with infra on forbidding bare gerrit rechecks16:11
*** nadya has quit IRC16:11
ihrachysthere is an action item on adding a CI deputy role, but I believe it's not critical and should be decided on by the next ptl16:11
*** trinaths1 has joined #openstack-meeting16:12
ihrachysalso, I was going to map all late functional test failures, I did (the report is line 21+ in the pad)16:12
ihrachysthe short story is though there are different tests failing, most of them turn out to be the same ovs native failure16:12
*** cody-somerville has quit IRC16:13
ihrachysseems like bug 1627106 is our sole enemy right now in terms of func tests16:13
openstackbug 1627106 in neutron "TimeoutException while executing test_post_commit_vswitchd_completed_no_failures" [High,In progress] https://launchpad.net/bugs/1627106 - Assigned to Miguel Angel Ajo (mangelajo)16:13
ihrachyskevinbenton landed a related patch for the bug: https://review.openstack.org/426032 We will need to track some more to see if that fixes anything16:14
armaxihrachys: I think it’s because it might not have a failure yet16:14
*** trinaths has quit IRC16:14
ihrachysarmax: wouldn't we see 0% failure rate?16:14
armaxihrachys: it’s getting built here: http://logs.openstack.org/periodic/periodic-neutron-dsvm-functional-ubuntu-xenial/16:14
armaxihrachys: strangely I see that postgres is missing too16:14
armaxbut I have yet to find the time to bug infra about seeing what is actually happening16:15
ihrachysaye, sure16:15
armaxbut two builds so far16:15
armaxno errorr16:15
ihrachysback to ovsdb native, ajo also has a patch bumping ovs timeout: https://review.openstack.org/#/c/425623/ though afaiu otherwiseguy has reservations about the direction16:16
jlibosvathere are some interesting findings from this morning by iwamoto16:16
jlibosvahe claims the whole system freezes16:16
jlibosvaas dstat doesn't give any outputs by the time probe times out16:16
*** d0ugal has quit IRC16:16
jlibosvait's supposed to update every second16:17
ihrachysvm progress locked by hypervisor?16:17
*** d0ugal has joined #openstack-meeting16:17
*** d0ugal has quit IRC16:17
*** d0ugal has joined #openstack-meeting16:17
jlibosvacould be the reason why noone is able to reproduce it locally16:18
ihrachysbut do we see 10sec hangs?16:18
ihrachysor shorter?16:18
jlibosvalet's have a look16:19
ihrachysbtw speaking of timeouts, another class of functional test failures that I saw in late runs could be described as 'random tests failing with test case timeout', even those not touching ovs, like test_migration16:19
ihrachysbut per test case timeout is a lot longer than ovsdb 10secs16:20
*** verdurin has quit IRC16:20
*** jmckind has quit IRC16:20
*** zz_dimtruck is now known as dimtruck16:20
ihrachysI see 5sec lock in dstat output that Iwamoto linked to16:21
*** tovin07 has quit IRC16:22
*** verdurin has joined #openstack-meeting16:22
*** yamahata has joined #openstack-meeting16:22
*** tovin07 has joined #openstack-meeting16:22
ihrachysinterestingly, we see functional job at ~10% failure rate at the moment, which is a drastic reduce from what we saw even on Friday16:23
ihrachysnot sure what could be the reason16:24
*** vishnoianil has quit IRC16:26
*** baoli has quit IRC16:26
*** newmember has joined #openstack-meeting16:26
ihrachyswe don't have dstat in functional job, so it's hard to say if we see same hypervisor locks16:27
ihrachysthe logs that Iwamoto linked to are for neutron-full16:27
*** reedip_ has left #openstack-meeting16:27
ihrachysI will check if we can easily collect those in scope of functional tests16:27
jlibosvainteresting is that it didn't cause any harm in those tests16:28
ihrachys#action ihrachys check if we can enable dstat logs for functional job16:28
ihrachysotherwiseguy: so what's your take on bumping timeout for test env?16:29
*** dmacpher has joined #openstack-meeting16:29
*** antwash has joined #openstack-meeting16:29
otherwiseguyihrachys, i wouldn't hurt, but I have no idea if it would help.16:30
*** sridharg has quit IRC16:30
ihrachysok I guess it's worth a try then. though the latest reduce in failure rate may relax the severity of the issue and also make it harder to spot if it's the fix that helps.16:31
ihrachysotherwiseguy: apart from that, any other ideas how we could help debug or fix the situation from ovs library side?16:31
*** xinli has joined #openstack-meeting16:31
*** tovin07 has left #openstack-meeting16:31
*** VW has quit IRC16:32
*** Leom has quit IRC16:32
jlibosvaihrachys: During xenial switch, I noticed ovs 2.6 is more prone to reproduce the issue16:32
*** VW has joined #openstack-meeting16:32
otherwiseguyihrachys, right now I'm writing some scripts that spawn multiple processes and just create and delete a bunch of bridges. adding occasionally restarting the ovsdb-server, etc.16:33
jlibosvaso maybe having a patch that disables ovs compilation for functional and leave the one that's packaged for ubuntu could improve the repro rate16:33
ihrachysjlibosva: ovs python library 2.6, or openvswitch service 2.6?16:33
*** antwash has left #openstack-meeting16:33
*** rossella_s has quit IRC16:33
otherwiseguyjust trying to reproduce.16:33
jlibosvaihrachys: service16:33
jlibosvathe ovsdb server itself probably16:33
*** rossella_s has joined #openstack-meeting16:34
ihrachysjlibosva: improve rate as in 'raise' or as in 'lower'?16:34
jlibosvaihrachys: raise :) so we can test patches or add more debug message etc16:34
ihrachysjust to understand, xenial is 2.5 or 2.6?16:34
jlibosvaIIRC it should be 2.616:34
jlibosvalet me check16:34
ihrachysoh and we compile 2.6.1?16:34
*** tidwellr_ has quit IRC16:35
* jlibosva is confused16:35
jlibosvamaybe it's vice-versa. 2.5 is worse and we compile 2.6.116:36
jlibosvayeah, so xenial contains packages 2.5 but we compile to 2.6.1 on xenial nodes16:37
ihrachysok, I guess it should not be hard to spin up the patch and see how it fails16:37
*** sudswas__ has joined #openstack-meeting16:37
ihrachys#action jlibosva to spin up a test-only patch to disable ovs compilation to improve reproduce rate16:37
*** baoli has joined #openstack-meeting16:38
jlibosvadone :)16:38
*** vishnoianil has joined #openstack-meeting16:38
jlibosva... some network issues with sending :-/16:39
*** sudipto has quit IRC16:39
ihrachysnevermind, let's move on16:39
*** sudipto_ has quit IRC16:39
ihrachysI mentioned several tests failing with test case timeouts before16:39
ihrachyswhen they do, they fail with AttributeError on __str__ call for WaitTimeout16:40
*** Leom has joined #openstack-meeting16:40
ihrachysthere is a patch by tmorin to fix the error: https://review.openstack.org/#/c/425924/216:40
ihrachyswhile it won't fix the timeout root cause, it's still worth attention16:40
jlibosvayeah, gate is giving the patch hard times16:41
*** sudipto has joined #openstack-meeting16:41
ihrachysclosing the topic of func tests, I see jlibosva added https://bugs.launchpad.net/neutron/+bug/1659965 to the etherpad16:41
openstackLaunchpad bug 1659965 in neutron "test_get_root_helper_child_pid_returns_first_child gate failure" [Undecided,In progress] - Assigned to Jakub Libosvar (libosvar)16:41
ihrachysjlibosva: is it some high impact failure?16:42
jlibosvaihrachys: no, I don't think so16:42
ihrachysor you just have the patch in place that would benefit from review attention16:42
jlibosvaI added it there as it's a legitimate functional failure. It's kinda new so I don't know how burning that is16:43
jlibosvathe cause is pstree segfaulting16:43
ihrachysok, still seems like something to look at, thanks for pointing out16:43
ihrachysthat's it for functional tests. as for other jobs, we had oom-killers that we hoped to be fixed by the swappiness tweak: https://review.openstack.org/#/c/425961/16:45
*** artom_ has joined #openstack-meeting16:45
*** Leom has quit IRC16:45
ihrachysajo mentioned though we still see the problem happening in gate.16:45
*** artom has quit IRC16:45
*** artom_ is now known as artom16:46
ihrachysyeah, I see that mentioned in https://bugs.launchpad.net/neutron/+bug/1656386 comments16:47
openstackLaunchpad bug 1656386 in neutron "Memory leaks on Neutron jobs" [Critical,Confirmed] - Assigned to Darek Smigiel (smigiel-dariusz)16:47
*** unicell has joined #openstack-meeting16:47
*** spzala has quit IRC16:47
ihrachysarmax: I see the strawman patch proposing putting mysql on a diet was abandoned. was there any discussion before that?16:48
*** spzala has joined #openstack-meeting16:48
armaxihrachys: not that I am aware16:48
armaxihrachys: we should check the openstack-qa channel16:48
ihrachysI don't see anything relevant there, probably worth talking to Monty16:50
ihrachysas for libvirtd malloc crashes, it's also not fixed, and I don't think we can help it16:50
jlibosvawe also have a new issue with linuxbridge job: https://bugs.launchpad.net/neutron/+bug/166061216:51
openstackLaunchpad bug 1660612 in neutron "gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial times out on execution" [Undecided,New]16:51
jlibosvathe global timeout kills the test run as it runs more than an hour16:51
*** spzala has quit IRC16:52
ihrachysand how long does it generally take?16:52
*** lblanchard has quit IRC16:53
jlibosvaI don't think we have an equivalent with ovs so it's hard to compare16:53
ihrachysin another job, I see 40m for all tests16:53
ihrachyscould be a slowdown, hard to say. I guess we have a single data point?16:53
*** Leom has joined #openstack-meeting16:54
jlibosvawith successful linuxbridge job, the whole job takes around an hour16:54
jlibosvaso it's around 43mins in successful linuxbridge job16:54
*** liangy has joined #openstack-meeting16:55
ihrachysweird, ok let's monitor and see if it shows more impact16:55
*** jungleboyj has quit IRC16:55
*** mickeys has joined #openstack-meeting16:55
ihrachysone final thing I want to touch base on before closing the meeting is gate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv16:55
ihrachys 100% failure rate16:55
ihrachysjlibosva: do you know what happens there (seems like legit connectivity issues in some tests)?16:56
jlibosvaihrachys: no, I haven't investigated it16:56
ihrachysthe trend seems to be 100% for almost a week16:56
*** kaisers has joined #openstack-meeting16:56
*** tesseract has quit IRC16:56
ihrachysI think it passed a while ago; we need to understand what broke and fix it, and have a plan to make it voting.16:56
jlibosvaihrachys: yeah, I'm working on this one. SSH fails there but we don't collect console logs16:56
jlibosvaihrachys: it might be related to ubuntu image as they update it on their site16:57
ihrachysjlibosva: oh don't we? how come? isn't it controlled by generic devstack infra code?16:57
jlibosvaihrachys: no, it's a tempest code16:57
jlibosvaihrachys: and we have our own Neutron in-tree code16:57
ihrachysjlibosva: don't we freeze a specific past version of the image?16:58
jlibosvawhich doesn't have this capability16:58
jlibosvaihrachys: that's the problem, they have 'current' dir and they don't store those with timestamps16:58
*** Guest91352 has quit IRC16:58
jlibosvathey store like maybe 4 latest but they get wiped eventually16:58
ihrachyshm, then maybe we should store it somewhere ourselves?16:58
jlibosvaanyway, even when I fetch the same as in gate, the job passes on my environment16:58
ihrachys#action jlibosva to explore what broke scenario job16:59
jlibosvathat would be best, then we would need someone to maintain the storage16:59
*** absubram has quit IRC16:59
ihrachysjlibosva: well if it's one time update per cycle, it's not like huge deal16:59
ihrachysok thanks jlibosva for joining, I would feel lonely without you :)16:59
*** mickeys has quit IRC17:00
ihrachysI hope next time we will have better presence17:00
*** VW has quit IRC17:00
*** Patifa has joined #openstack-meeting17:00
ihrachysif not maybe we will need to consider other time17:00
ihrachysthanks again17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Tue Jan 31 17:00:27 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-01-31-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-01-31-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-01-31-16.00.log.html17:00
jlibosvathanks :)17:00
*** nadya has joined #openstack-meeting17:01
*** sudswas__ has quit IRC17:03
*** sudipto has quit IRC17:03
*** nadya has quit IRC17:05
*** diablo_rojo has joined #openstack-meeting17:05
*** sshnaidm is now known as sshnaidm|afk17:06
*** VW has joined #openstack-meeting17:06
*** dprince has quit IRC17:07
*** Patifa has quit IRC17:08
*** rasca has quit IRC17:08
*** e0ne has quit IRC17:08
*** lamt has quit IRC17:08
*** sudipto_ has joined #openstack-meeting17:09
*** sudipto has joined #openstack-meeting17:09
*** Patifa has joined #openstack-meeting17:09
*** nadya has joined #openstack-meeting17:10
*** andreas_s has quit IRC17:10
*** lamt has joined #openstack-meeting17:11
*** sgordon has quit IRC17:16
*** kaisers has quit IRC17:17
*** jlibosva has quit IRC17:18
*** dmacpher is now known as dmacpher-afk17:18
*** davidsha has quit IRC17:19
*** unicell has quit IRC17:21
*** nadya has quit IRC17:22
*** unicell has joined #openstack-meeting17:23
*** diablo_rojo has quit IRC17:24
*** Leom has quit IRC17:24
*** Swami has joined #openstack-meeting17:25
*** Apoorva has joined #openstack-meeting17:27
*** princenana has left #openstack-meeting17:27
*** antwash has joined #openstack-meeting17:29
*** dprince has joined #openstack-meeting17:31
*** gagehugo has joined #openstack-meeting17:32
*** dmorita has joined #openstack-meeting17:33
*** Leom has joined #openstack-meeting17:33
*** baoli has quit IRC17:35
*** jdurgin1 has quit IRC17:36
*** dmorita has quit IRC17:38
*** trinaths1 has quit IRC17:38
*** mickeys has joined #openstack-meeting17:39
*** lamt has quit IRC17:39
*** jungleboyj has joined #openstack-meeting17:41
*** dmorita has joined #openstack-meeting17:42
*** sudipto_ has quit IRC17:43
*** sudipto has quit IRC17:43
*** liangy has quit IRC17:43
*** jmckind has joined #openstack-meeting17:43
*** vj4 has quit IRC17:44
*** vishnoianil has quit IRC17:45
*** bobh has quit IRC17:46
*** spilla has joined #openstack-meeting17:46
*** jaugustine has quit IRC17:46
*** Alex_Staf has quit IRC17:48
*** baoli has joined #openstack-meeting17:50
*** rajinir has joined #openstack-meeting17:51
*** gouthamr has quit IRC17:51
*** unicell has quit IRC17:52
*** annegentle has quit IRC17:52
*** absubram has joined #openstack-meeting17:52
*** toscalix has quit IRC17:56
*** lamt has joined #openstack-meeting17:56
*** rbowen has joined #openstack-meeting17:57
*** rbowen has quit IRC17:57
*** jaugustine has joined #openstack-meeting17:58
*** sshnaidm|afk is now known as sshnaidm17:59
*** nadya has joined #openstack-meeting18:00
stevemarping agrebennikov, amakarov, annakoppad, antwash, ayoung, bknudson, breton, browne, chrisplo, crinkle, davechen, dolphm, dstanek, edmondsw, edtubill, gagehugo, gyee, henrynash, hrybacki, jamielennox, jaugustine, jgrassler, knikolla, lamt, lbragstad, kbaikov, ktychkova, morgan, nishaYadav, nkinder, notmorgan, raildo, ravelar, rderose, rodrigods, roxanaghe, samueldmq, shaleh, spilla, srwilkers, StefanPaetowJisc,18:00
stevemar stevemar, topol, portdirect, SamYaple18:00
morganbut... but18:00
morgani was asleep18:00
stevemar#startmeeting keystone18:00
openstackMeeting started Tue Jan 31 18:00:36 2017 UTC and is due to finish in 60 minutes.  The chair is stevemar. 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
*** dmorita_ has joined #openstack-meeting18:00
*** dmorita has quit IRC18:00
morganwow, there is a bknudson here!18:01
morgana rare sighting in the wilds of IRC! :)18:01
*** jaugustine_ has joined #openstack-meeting18:02
*** lpetrut has quit IRC18:02
lbragstada bknudson!18:02
* stevemar finishes switching desks18:02
stevemar#topic announcements18:03
*** jaugustine_ has quit IRC18:03
*** openstack changes topic to "announcements (Meeting topic: keystone)"18:03
stevemarwe're in the RC week, RC must be tagged by thursday, don't expect anything to merge unless it's a priority for the release18:03
stevemaroops, agenda link!18:03
stevemar#link https://etherpad.openstack.org/p/keystone-weekly-meeting18:03
*** ravelar has joined #openstack-meeting18:03
stevemarpriorities for RC are listed here: #link https://etherpad.openstack.org/p/keystone-sprint-to-ocata18:03
stevemar#link #link https://etherpad.openstack.org/p/keystone-sprint-to-ocata18:03
*** dimtruck is now known as zz_dimtruck18:04
stevemarwe approved per-user-auth (MFA) for RC18:04
stevemarsee bp here: https://blueprints.launchpad.net/keystone/+spec/per-user-auth-plugin-reqs18:04
*** jaugustine_ has joined #openstack-meeting18:04
stevemarthanks morgan for working so hard on it18:05
stevemarits coming along really nicely18:05
*** rossella_s has quit IRC18:05
morganalso a bug in some logs found in the process https://review.openstack.org/#/c/427004/18:05
morganneeds a second +2/A18:06
*** nadya has quit IRC18:06
morganbut it is not directly related18:06
stevemaryeah, easy one to review ^18:06
morganrelease note was just pushed for MFA18:06
morganplease look for it.18:06
morgan#link https://review.openstack.org/#/c/427328/18:06
stevemaryowza, thats a heck of a release note18:07
morganmore in depth docs will come post RC likely, pending stevemar's resource option docs18:07
*** VW has quit IRC18:07
stevemarmorgan: may have to trim it, just so it doesn't differ too much from the other notes18:07
morgancurrent rendered version: http://docs-draft.openstack.org/28/427328/2/check/gate-keystone-releasenotes/ad8ed97//releasenotes/build/html/unreleased.html18:07
*** gouthamr has joined #openstack-meeting18:07
stevemari like the detail though, but i prefer consistency, if that makes sense.18:07
*** jaugustine_ has quit IRC18:07
morganstevemar: but... it's an accurate release note18:07
* morgan will leave that trimming to stevemar18:08
*** X-dark_ has joined #openstack-meeting18:08
stevemarany questions about RC? we have some identified bugs but that's the next topic, have some more announcements18:08
stevemarnext announcement18:09
stevemargyee is stepping down from core18:09
stevemardue to inactivity and a change in responsibility i asked him to step down18:09
*** X-dark has quit IRC18:09
*** X-dark_ is now known as X-dark18:09
ayoungNot a huge surprise.18:09
*** newmember has quit IRC18:10
stevemaryeah, i wanted to give the next PTL a clean slate to start from18:10
lbragstadthanks gyee for your service!18:10
* dolphm salutes gyee18:10
rodrigodsthanks gyee :)18:10
* morgan cheers for gyee and thanks him for his service18:10
morganthough... he's not here to hear it atm18:10
stevemarthe ether knows18:10
stevemaryou can email him at his personal address if you want, PM me if you want it18:11
stevemarhe responds quickly there18:11
morganyeah he typically does.18:11
*** diablo_rojo_phon has joined #openstack-meeting18:11
stevemarnot sure if hes going to write a note to the ML18:11
morganstevemar: make sure you announce the Core change to the ML sometime18:11
*** henrynash has joined #openstack-meeting18:11
morganif he doesn't write a note.18:12
stevemarwill do18:12
henrynash(sorry I’m late)18:12
*** Cibo_ has joined #openstack-meeting18:12
* morgan blinks18:12
lbragstadhenrynash o/18:12
stevemarhenrynash: heyo!18:12
*** dprince has quit IRC18:12
morganwe have a henrynash too! wow.18:12
henrynashhenrynash too! is so much better than the old one18:12
morganit is a redletter day18:12
stevemarall the rascally ibm'ers are showing up18:12
lbragstadgettin' the band back together18:12
morganstevemar: i don't see topol18:13
henrynash(dog eat my homework etc.)18:13
morganstevemar: :P18:13
stevemarmorgan: zing18:13
stevemarlast announcement18:13
samueldmqthanks gyee!18:13
stevemar19 PTG tickets left18:13
morganstevemar: or jamielennox18:13
stevemari think they started with 200?18:13
* morgan needs to book an airplane18:13
stevemarthats a huge drop from 2 weeks ago, i think they have >100 left18:13
ayoungI have one, too, that I am not going to use18:13
ayoungWas going to go to my backup, but backup is not going18:14
ayoungThink the deadline for transfer is soonish.  Let me know if you need it.18:14
* stevemar is pretty sure there are hourly flights going from toronto to atlanta, will book later18:14
*** dprince has joined #openstack-meeting18:15
stevemari'm sure the 19 will end up being bough18:15
stevemarperhaps more slowly18:15
*** VW has joined #openstack-meeting18:15
topolI will be in ATL Sunday night18:15
* morgan will be flying in on Monday night18:15
lbragstadI'll be there Wednesday morning18:15
henrynashTues night18:16
morganso i'll be missing day 118:16
henrynash(see, we all synced that so well)18:16
knikollaTuesday night18:16
lbragstadand staying until late Friday18:16
* breton will be from Sunday to Saturday18:16
*** ihrachys has quit IRC18:16
morganand i am either saying until friday mid-day or early sat18:16
morganlikely leaving midday friday18:16
gagehugoschedued for sun-sat18:16
* topol topol had to come late to this meeting. Still distraught over morgan's incredibly ugly bagels... still shaking :-)18:16
*** ricolin has quit IRC18:17
morgantopol: it's ok, i gave you a giant release note to review.18:17
stevemari'm there sunday to saturday too18:17
morgantopol: because you were late18:17
lbragstadstevemar i assume organization of everything will start soon?18:17
samueldmqI'll be there Sunday night too, in the case someone wants to hang out for food or something18:17
dstaneki'm finally here!18:18
stevemarlbragstad: yeah, as soon as we cut RC1 we can start planning18:18
lbragstadstevemar ok - cool18:18
*** ijw has joined #openstack-meeting18:18
stevemar3 weeks is plenty of time to plan it all out :P18:18
stevemarokay, next topic18:20
* topol who will join me for a tearful reunion with my Ga Tech Ph.D. advisors? Havent seen them in 18 years...18:20
*** VW has quit IRC18:20
stevemartopol: you're on your own there bud18:20
stevemar#topic bugs we can fix during RC18:20
*** openstack changes topic to "bugs we can fix during RC (Meeting topic: keystone)"18:20
stevemari plan on cutting RC1 when morgan's MFA stuff merges18:21
stevemarbut we can cut RC2 if we deem some bugs are worth backporting18:21
stevemari think these two qualify18:21
stevemarFederation: federated users can't log into Horizon - https://bugs.launchpad.net/keystoneauth/+bug/166043618:21
openstackLaunchpad bug 1660436 in python-novaclient "Federated users cannot log into horizon" [Undecided,New]18:21
stevemarFederation: cannot use Trusts with federaed users - https://bugs.launchpad.net/keystone/+bug/158999318:21
openstackLaunchpad bug 1589993 in OpenStack Identity (keystone) "cannot use trusts with federated users" [High,In progress] - Assigned to Boris Bobrov (bbobrov)18:21
bretoni can talk about the trusts issue18:22
stevemarcrinkle is working on the first, and breton is working on the second, are either of you around?18:22
bretonI was actually working on that bug downstream for some time.18:22
stevemarbreton, you first, crinkle afterwards?18:22
bretonstevemar: ok18:22
bretonThe problem with the whole thing is that with federated users we cannot really know what the user can unless they have authenticated18:22
stevemarcan.. do?18:23
bretonbecause, for example, with trusts, at the moment of trust creation the user might have already lost his group, that provided a role, because something has changed in the IDP, and we don't know about it18:23
bretoncan do, yes18:23
*** lblanchard has joined #openstack-meeting18:23
rderosebreton: you can use shadow mapping to create users18:23
bretonfor us, downstream, the solution now is to recreate user group membership for federated users each time the user authenticates. We just know that the customer will not add shadow users to groups directly and can live with the possible gap between group removal and next authentication18:24
*** rbak__ has joined #openstack-meeting18:24
dstanekrderose: that won't help with groups necessarily18:24
stevemarbreton: can you assign the role necessary to the user directly?18:24
*** bobh has joined #openstack-meeting18:24
bretonstevemar: no. There can be very many users.18:24
*** lblanchard has left #openstack-meeting18:24
stevemarah dang18:25
*** timrc has quit IRC18:25
henrynashbreton: so is the issue that A trusts B, A never logs in again (and meanwhile as lost their group in teh idp), meanwhile B can carry on usingthe trust for ever?18:25
*** jkilpatr_ has joined #openstack-meeting18:25
dstanekbreton: that's how federated mapping works by design right? re-evaluate group membership for each auth18:25
bretonhenrynash: and that sucks18:25
dstanekhenrynash: ah, that makes sense18:26
ayoungif the trust is no longer valid due to a group memebership change, they cannot use it18:26
dstanekso you have to evaluate A's group membership for each B use of a trust?18:26
lbragstadso the problem is that trusts don't have the opportunity to stay in sync with whatever is in the idp?18:26
bretondstanek: kinda. But that group membership never persists inside the database18:26
henrynashbreton: and we can’t tell from our side that the group has been lost unless A choices to reauthenticate18:26
dstanekayoung: the group membership can be ephemeral18:26
stevemarhenrynash: which may not happen18:26
ayoungdstanek, then the trust will never work18:26
henrynashstevemar: yep18:26
dstanekbreton: exactly. but you can evaluate it anyway right?18:26
bretondstanek: no18:27
*** rbak_ has quit IRC18:27
*** electrofelix has quit IRC18:27
morgani think the answer here is simple: with shadow users allow explicit group additions18:27
ayoungif the trust code cannot link the original user to the roles in the trust, they trust execution fails, no token18:27
dstanekif you know the user and the idp of the trustor can't you lookup the mapping?18:27
morganto the shadow user18:27
bretondstanek: groups might come from assertion18:27
morganit is only allowed in that case18:27
morgannot the "assertion" groups18:27
*** unicell has joined #openstack-meeting18:27
dstanekbreton: ah, right. good call18:27
morgani can't get behind supporting trusts on the values that come from an assertion18:27
*** jkilpatr has quit IRC18:27
lbragstadyou'd need the assertion, wouldn't you?18:27
ayoungwe need to record all membership information used in a trust18:27
morganayoung: ++18:27
morganayoung: therefore the shadow user, if added to a group, could explicitly be granted the values18:28
morganit's "known"18:28
henrynashmorgan, ayoung: but how would the group memberhsip info ever be deleted18:28
dstanekok, so no trusts based on federated ephemeral group membership?18:28
morganhenrynash: you'd purge the shadow user18:28
dstanekmorgan: that won't work18:28
henrynashmorgan: agreed18:28
morgandstanek: yeah, i'd -2 adding trusts based on ephemeral group membership18:28
bretonmorgan: i dislike it, because it requires operators manage users manually, not in the idp18:28
dstanekif a change in the IdP puts them in a different group then they'd get different ephemeral groups18:29
bretonand we have code that relies on it -- heat uses it for delayed operations18:29
henrynashmorgan: but an idp (or whoever is creating users in the idp) would have to know to do that18:29
morgandstanek: right, this is why we only support in the case of explicit group additions in keystone18:29
dstanekif you put that in keystone then any change in the idp would need a change in keystone18:29
*** annegentle has joined #openstack-meeting18:29
bretonwe could try fixing heat to use allow_expired though.18:29
morganaka shadow users.18:29
*** Leom has quit IRC18:29
stevemarbreton: that might be the better call here18:29
morganor the local user w/ mapped values18:29
bretonmorgan: how do we differentiate between explicit and implicit groups?18:29
bretonmorgan: a column in the db?18:29
morganoperator assigned in the db18:30
morganit is loaded from the db. vs loaded from the assertion18:30
morganwe have the ability to allow a local user to auth with federated creds, we have shadow users now18:30
morganif you grant an explicit membership in either case, that carries forward18:30
morganregardless of assertion18:30
morganthat is an explicit assignment18:30
morganimplicit from the IDP can never have trusts18:31
bretonthat was the whole point of federation -- to manage users not in openstack, but outside of it18:31
morganbecause of the issues you've outlined18:31
bretonthat is a step back to moving users around in keystone18:31
morganthe IDP provides authentication18:31
morganthe IDP never, ever, ever has provided authorization in keystone18:31
morgankeystone has done that18:31
morgantrusts are authz18:31
morgannot authn18:31
*** krtaylor has quit IRC18:32
morganif the idp is providing authz (not keystone), we have a bigger issue.18:32
henrynashmorgan: but the group mappings from teh idp ARE used to “generate” authz18:32
stevemarwe have the same issue if using trusts and LDAP users right?18:32
morganhenrynash: that is now what i mean18:32
bretonstevemar: no18:32
*** abhiraut1 has joined #openstack-meeting18:32
morganhenrynash: keystone has to explicitly map that.18:32
henrynashmorgan: agreed18:32
stevemarah the groups are mapped back, duh18:32
morganhenrynash: this is no different except an operator who wants trusts needs to explicitly add federated users.18:33
morganto a group18:33
morganno implicit based on trust18:33
morganunless the trust expiry is a known value18:33
ayounggroups are an attribute that are used to assign authz.  Those groups may come from the IdP origianlly, but must be recorded in Keystone in order to have a non-ephemeral effect18:33
*** ralonsoh has quit IRC18:33
morganaka it expires about when the assertion (or similar view) is expired18:33
stevemar13:24 stevemar: breton: can you assign the role necessary to the user directly?18:33
stevemar13:24 breton: stevemar: no. There can be very many users.18:33
stevemar13:24 stevemar: ah dang18:33
morganayoung: ++18:33
bretonmorgan: it's not the operator wants trusts. Users want.18:34
lbragstadayoung in order to have a non-ephemeral effect on users*18:34
ayounglbragstad, in order to have any non-ephemeral effect18:34
bretonmorgan: we can't make each user ask operator when they want to use a trust18:34
lbragstadayoung aha - yeah18:34
ayoungyou can create a trust, but if the info used to create that trust is not recorded, the trust is non-executable18:34
morganbreton: yes we can.18:34
morganayoung: ++18:35
stevemarayoung: so you're saying... shadow groups! :D18:35
morganbreton: i'm sorry but no creating trusts based on ephemeral idp groups18:35
*** lpetrut has joined #openstack-meeting18:35
ayoungstevemar, probably should be something explicit18:35
morganif the data is exclusively controlled by the IDP, no trusts18:35
henrynashmorgan: so the explict support is obvioulsy one approach (and we should support it imho..and I assume we do already),18:35
dstanekwould short term trusts work? something that expires at the same time as the token of the trustor18:36
morganhenrynash: i think it needs it18:36
rderoseoperators will be able to create federated users via API and can then explicitly make trusts18:36
morgandstanek: well i'd do a expiration of the assertion18:36
morgandstanek: but yes, i'd be ok with fixed life trusts18:36
ayoungstevemar, something in the mapping that indicates that users in IdP I via protocol P should be added to group G18:36
lbragstadrderose but then if something changes in the idp - the trust can still be valid18:36
morgandstanek: as an option provided we track the data from the idp18:36
bretonmorgan: this is a huge step back in federation18:36
lbragstadwhen it might not be18:36
stevemarrderose: operators could also assign roles individually. breton is saying he doesn't want his operator/admin to deal with all the requets18:36
dstanekif users have to be greated by the operator in this case them mapping buys them nothong and the are using a glorified ldap18:37
rderoselbragstad: what idp change would cause it to be invalid?18:37
morganrderose: many things.18:37
lbragstadrderose depends on the assertion/idp setup18:37
lbragstad(case-by-case problems are *so* fun!)18:37
bretonmorgan: it becomes a thing that doesn't support part of keystone functionality18:37
dstanekthe whole point of federation is that we don't have to have all the users/groups in keystone and they are dynamically provided by the IdP18:38
ayoungwe should look at what OpenIDC does here.  This is a pattern larger than Keystone and OpenStack18:38
morganbreton: the only way you're gettiing trusts based on idp info is if the trust expires at the expiry of the assertion (or something similar)18:38
rderosemorgan: lbragstad: but if you explicitly give a federated user a role, that role assignment should exist regardless of changes to the idp18:38
lbragstadrderose exactly18:38
morganayoung: they map it to a local user18:38
ayoungWe had only looked at OAUTH1a when Trusts were implemented18:38
morganayoung: then the local user is granted access18:38
rderoseif you manually provision, then you should manually deprovision18:38
morganayoung: in almost every-single-case18:38
dstanekrderose: exactly. and that;s the problem18:38
lbragstadrderose what if something in the idp changes and that trust should no longer be valid?18:38
ayoungmorgan, I mean for management of delegation18:38
bretonlets than document that trusts don't work with groups from federated token and stop advertising federation as first-class citizen18:38
morganayoung: it's checked on each authn18:38
morganayoung: or fixed life18:38
ayoungmorgan, is there an analogue to trusts there?18:38
morganayoung: no. the assertion (token?) is the trust18:39
morganayoung: so i auth with say google, to APP18:39
morgani give access to the google things for the life of the token/assertion18:39
rderosebreton: everything you can do with a local user, you should be able to do with a federated user18:39
morganif the app has specific attrs/authz it is given explicitly to the user object that google auth links to18:39
bretonrderose: i absolutely agree with that. But the reality is different.18:40
stevemarrderose: thats breton's issue, he can't right now :P18:40
dstanekmorgan: exactly what i was thinking with short term trusts18:40
ayoungrderose, you can.  The problem is that you still need to record the group membership for the Federated user.  Which gets us back into the "the user needs to log in first before they can be admin'd"18:40
morgandstanek: so ... if we do time-limited trusts and store the information, i'd be ok with it.18:40
ayoungrderose, which is why it would be better if the group memebership was triggered by the mapping process18:40
stevemargonna cut this conversation off in a minute or two18:40
morgandstanek: i just wont support indefinite trusts on ephemeral data18:40
stevemari don't think we're going to solve it here18:40
dstanekmorgan: ++18:41
lbragstadthis is interesting though - should we save it for -keystone later?18:41
rderoseayoung: or, provision your federated users via the API; deprovision when their access should change18:41
ayoungsomeone write up the use case as a spec please18:41
stevemarayoung: the bug exists :P18:41
bretonshort-lived trusts won't work for Heat18:41
morganrderose: there is a mechanism to say assertion is expired...but that feedback is not well supported in most IDPs18:41
lbragstadrderose but then we're managing federated users in the IDP and in keystone18:41
dstaneklbragstad: ++ that doesn't make sense18:42
rderoselbragstad: we're managing their authorization in keystone18:42
henrynashmorgan: I would also support the time-limiting option for a trust (which should be applicable to regualr suers or federated users)18:42
breton(because it explicitely requires long-lived trusts)18:42
morganhenrynash: we already support that feature18:42
morganhenrynash: it's implemented :).18:42
rderoselbragstad: at HP, user requests access, some system calls keystone and provisions access18:42
morganbreton: what is a long-lived trust?18:42
morganbreton: indefintie?18:42
henrynashHe’s smart, that morgan guy, ya know18:42
morgan1-day? 2-days? 16-days?18:42
*** VW has joined #openstack-meeting18:43
dstanekrderose: you are no longer using federation18:43
bretonmorgan: indefinite i guess.18:43
* antwash being the newbie sucks... 18:43
rderosedstanek: you are using federation for authentication18:43
ayoung#link https://bugs.launchpad.net/keystone/+bug/158999318:43
openstackLaunchpad bug 1589993 in OpenStack Identity (keystone) "cannot use trusts with federated users" [High,In progress] - Assigned to Boris Bobrov (bbobrov)18:43
morganbreton: that is breaking how security in federation works then18:43
lbragstadantwash :)18:43
morganbreton: this is *not* secure.18:43
dstanekrderose: you don't get any of the benefits of what federation offers18:43
lbragstadantwash patience young grass hopper, patience18:43
stevemarokay, i'm gonna cut this one off, we have a lot more on the agenda18:43
bretonmorgan: i agree. Then lets stop calling federation first-class citizen and advertise that it can everything local backend can.18:44
ayoungbreton, grab me after and we can talk through it18:44
morganbreton: works for me18:44
lbragstadI'll hang out in -keystone after the meeting to continue this discussion with folks if they want18:44
lbragstadayoung morgan ++18:44
morgananyway lets talk in -keystone18:44
ayoungsame here18:44
*** spzala has joined #openstack-meeting18:44
* topol I remember when lbragstad was the grasshopper... feelin old18:44
stevemarcrinkle: o/18:44
morganbreton: i have a fix btw... just want to be very deliberate about how we implement it18:44
stevemarFederation: federated users can't log into Horizon - https://bugs.launchpad.net/keystoneauth/+bug/166043618:45
openstackLaunchpad bug 1660436 in python-novaclient "Federated users cannot log into horizon" [Undecided,New]18:45
lbragstadtopol lol18:45
crinkleso 1660436 - what's happening is after a federated user successfully authn's, horizon then tries to load one of the nova panels with the novaclient, and it's trying to create a new token session with the federated token, and it fails because it's not persisting domain data, so keystoneauth's discovery returns a v2 endpoint, which a federated user can't use18:45
morgancrinkle: euuw.18:45
crinkleI was digging into it and more or less ran into a wall at that point because it involves multiple projects, but I put everything I found out into the bug18:45
morganwe should fix that :P18:45
crinklemorgan: yeah it is super gross18:45
*** xinli has quit IRC18:45
rodrigodsthis is unexpected side effect18:45
stevemarto me, it feels like the fix belongs in how horizon doess stuff...18:45
ayoungstevemar, probably not18:46
crinklerobcresswell said he would look into it18:46
ayoungstevemar, Horizon is pretty simple here:  get a Federated unscoped token, convert it to a scoped token18:46
morganwe could persist the domain info in the token, no?18:46
lbragstadcrinkle so it's pulling the domain from the token - but failing to look things up with it?18:46
morganand let horizon consume that?18:46
stevemarcrinkle: yeah, but we probably need to help the horizon team out here18:46
ayoungwe'd still have no groups18:46
morganayoung: oh ugh, and with fernet that becomes icky18:46
crinklelbragstad: no, it's not pulling the domain info18:46
ayoungmorgan, again, shadow all the info we need for future use18:47
crinklelbragstad: that's kind of the problem, with no domain info keystoneauth says use v218:47
ayoungperhaps we time-limit group membership?18:47
morganayoung: pretty much how other apps do it18:47
morganayoung: we can overwrite the data if the assertion is changed (from the same IDP)18:47
*** VW has quit IRC18:47
morganayoung: that is sane18:47
morganand no different than how local users work18:47
morganayoung: so a single record per-user-per-idp for that18:48
ayoungmorgan, assuming that a new assertion has the complete set of groups, then, yes, remove group membership for missing groups18:48
*** rbak__ has quit IRC18:48
ayoungis that a safe assumption?18:48
morganthe new assertion would *have* to have the value of all groups for that ID from that IDP18:48
morganit is authortitative18:48
morgani don't think you get partial assertions ;)18:48
morgani would say worth saying it's safe and have someone do a bit of research before impl18:49
ayoungmorgan, you could use different profiles, and get different sets of groups, but...I think that in that case, the profile used would be static, and should be authoritative...so still remove18:49
*** korzen has joined #openstack-meeting18:49
morganagain, per-idp-per user18:49
ayoungper protocol18:49
morganif you authed with a different idp for example FB vs Google18:49
morgani'd expect it to be different18:49
ayoungsame IdP, different protocol....18:49
ayoungdifferent groups?18:50
morganshould result in the same data?18:50
ayoungmight happen18:50
morgani'd start with per-IDP and expand if needed18:50
ayoungmapping is per protocol.  I'd do it per protocol18:50
morganok sure18:50
ayounger...per mapping, really.18:50
morganper mapping18:50
morganshadow the data,18:50
ayoungyou cabn technically reuse the mapping for different protocols, but that would be unlikely to work18:51
*** zz_dimtruck is now known as dimtruck18:51
ayoungso would still end up per protocol, I think18:51
* ayoung is done18:51
*** liangy has joined #openstack-meeting18:51
morgancrinkle: fixable we probably need to shadow the user info in keystone18:51
*** egarbade| has quit IRC18:51
*** jdurgin has quit IRC18:51
stevemarmorgan: i don't think we have time to implement all that?18:52
morgancrinkle: and we can update that as assertions come in.18:52
morganstevemar: not in Ocata18:52
stevemarmorgan: right, but right now federated users can't get into horizon18:52
morgangoing to go on record and say, it wont happen in Ocata (sadly)18:52
morganit's an architectural issue18:52
stevemarlike, any of them18:52
morganwe'd need to store groups too18:52
morganbecause the token has to be reconstructed18:52
stevemarcrinkle: can we revert the change that novaclient made?18:53
morganwe could make a temp fernet token formatter that stores a ton extra data18:53
lbragstadright now - federated fernet tokens store groups in the token itself18:53
morganlbragstad: oh ok then we should be ok18:53
morganand we can just persist domain data18:53
crinklestevemar: well not really, the bug it fixed was a pretty nasty bug too18:53
*** Leom has joined #openstack-meeting18:54
morgancrinkle: ok, so solution: persiste the domain data18:54
stevemarcrinkle: what about catching the exception on the horizon side?18:54
lbragstadmorgan https://github.com/openstack/keystone/blob/master/keystone/token/providers/fernet/token_formatters.py#L59618:54
morgancrinkle: much easier and Ocata possible if that is the issue. it's just storing the info in the fernet format18:54
morgancrinkle: it will be a new fernet formatter that is then used (we can't change the formatters we have as they are tied to specific format)18:54
*** tonytan4ever has joined #openstack-meeting18:55
morganlbragstad: ^ sound right to you?18:55
morganstevemar: ^cc18:55
ayoungdstanek, lbragstad weren't one of you working on creating resources on demand for Federated users?18:55
*** VW has joined #openstack-meeting18:55
ayoungproejcts was the big one, but also role assignments etc?18:55
morganayoung: rderose is?18:55
morganayoung: i think18:55
lbragstadmorgan i can double check - but i don't think we guarantee the format to not change18:56
lbragstadayoung yeah we worked on that18:56
lbragstadayoung it was federated auto-provisioning18:56
morganlbragstad: it's about ensuring the decoder doesn't give bogus data back passed the same id#18:56
ayounglbragstad, we'd need it for the Federated/Horizon use case, I think18:56
morganlbragstad: the design was to never change a formatter, just make a new one and use the new format id18:56
morganlbragstad: that way tokens stay interoperable in upgrades (no-down-time-upgrades, you'll break things in weird ways)18:57
stevemarlbragstad: is there a reason why domain id is not in FederatedScopedPayload ?18:57
morganlbragstad: so, new formatter. old keystones can't decode new, but new keystone can decode old18:57
stevemari guess cause that never existed until now18:57
morganunless this is ocata formatter... just you see where i am going18:57
stevemarcrinkle: not sure if you've followed the upstream changes, but we now ensure all federated users have a domain id18:58
*** baoli has quit IRC18:58
*** Leom has quit IRC18:58
crinklestevemar: yes i followed that18:58
stevemarso can add domain id stuff to https://github.com/openstack/keystone/blob/master/keystone/token/providers/fernet/token_formatters.py#L586-L63518:58
morganwe may need to just make sure that data is available to horizon18:58
stevemari think that'll solve the issue?18:58
*** AJaeger has joined #openstack-meeting18:58
*** vishnoianil has joined #openstack-meeting18:58
lbragstadayoung http://docs.openstack.org/developer/keystone/federation/federated_identity.html#auto-provisioning18:59
stevemarbah, barely got through the agenda18:59
stevemarthanks for coming y'all18:59
*** sdake_ has quit IRC18:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Jan 31 19:00:00 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
*** spilla has left #openstack-meeting19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-01-31-18.00.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-01-31-18.00.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-01-31-18.00.log.html19:00
*** sdake has joined #openstack-meeting19:00
ianwhi infra people19:00
AJaegermorning ianw19:00
jeblairhi ianw19:00
*** rbak__ has joined #openstack-meeting19:00
ianweveryone more qualified is busy, so you get me and an emacs buffer full of commands today instead of fungi19:01
*** gagehugo has left #openstack-meeting19:01
ianw#startmeeting infra19:01
openstackMeeting started Tue Jan 31 19:01:18 2017 UTC and is due to finish in 60 minutes.  The chair is ianw. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
ianw#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
ianw#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
*** Shrews has joined #openstack-meeting19:01
ianwI do not think there are any announcements19:02
ianw#topic Actions from last meeting19:02
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
*** pvaneck has joined #openstack-meeting19:02
ianw#link http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-01-03-19.02.log.html#l-919:02
ianwfungi to announce the infra ptg pike etherpad to relevant mailing lists.19:02
ianw#link http://lists.openstack.org/pipermail/openstack-dev/2017-January/110992.html19:03
ianwfungi to plumb https for docs.o.o and developer.o.o19:03
AJaegerworking nicely - done ;)19:03
ianw#link https://review.openstack.org/42489319:03
*** egarbade- has joined #openstack-meeting19:03
ianwyep, that's all nice and green-locky :)19:03
*** baoli has joined #openstack-meeting19:03
ianwclarkb to make a gerritbot release19:03
ianw#link http://git.openstack.org/cgit/openstack-infra/gerritbot/tag/?h=0.3.019:04
ianwseems fine, i'm not sure if we restarted though?  are we getting the branch in the log messages19:04
*** Cibo_ has quit IRC19:05
jeblairgerrit2   76257  0.1  0.0 396140 37816 ?        Sl   Jan26  13:34 /usr/bin/python /usr/local/bin/gerritbot /etc/gerritbot/gerritbot.config19:06
ianwmaybe no from a quick look, and i think that was the major feature.  i won't action item that but will take a look later19:06
*** zhufl has quit IRC19:06
*** jaugustine_ has joined #openstack-meeting19:06
jeblairthat seems to be 2 days after the release?19:06
jeblairso maybe hasn't upgraded on the server19:07
*** zhufl has joined #openstack-meeting19:07
*** Leom has joined #openstack-meeting19:07
ianwahh, that would explain it19:07
ianwhttps://review.openstack.org/#/c/417450/4/gerritbot/bot.py <- is the bit i'm thinking of19:07
ianwlet me add that then since we figured it out19:08
ianw#action ianw ensure gerritbot upgrade is deployed for new release (0.3.0)19:09
ianw#topic Specs approval19:09
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:09
ianw#info APPROVED "Update zuulv3 spec to include job repo information" spec19:10
ianw#link http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html#jobs19:10
*** Leom_ has joined #openstack-meeting19:10
ianwI think that is it for this week?19:10
*** jdurgin has joined #openstack-meeting19:10
*** Leom has quit IRC19:11
ianwok, moving on19:11
*** ykatabam has quit IRC19:12
ianwpriority efforts ... i don't have anything specific to say, but we can go through the topics quickly and pipe up if you do19:12
ianw#topic Priority efforts: Ansible Puppet Apply19:13
*** openstack changes topic to "Priority efforts: Ansible Puppet Apply (Meeting topic: infra)"19:13
*** Leom_ has quit IRC19:13
ianw#topic Priority efforts: A Task Tracker for OpenStack19:13
*** openstack changes topic to "Priority efforts: A Task Tracker for OpenStack (Meeting topic: infra)"19:13
*** Cibo_ has joined #openstack-meeting19:13
*** Leom has joined #openstack-meeting19:14
ianw#topic Priority efforts: Zuul v319:14
*** openstack changes topic to "Priority efforts: Zuul v3 (Meeting topic: infra)"19:14
ianwjust so everyone knows, there's a specific zuul meeting19:14
*** krtaylor has joined #openstack-meeting19:14
*** jaugustine_ has quit IRC19:14
ianw#link agenda https://wiki.openstack.org/wiki/Meetings/Zuul19:14
jeblairi don't think there's anything we need to chat about this meeting19:14
ianw#topic Priority efforts: Gerrit 2.13 Upgrade19:15
*** openstack changes topic to "Priority efforts: Gerrit 2.13 Upgrade (Meeting topic: infra)"19:15
*** fzdarsky is now known as fzdarsky|afk19:15
zaroI’ll pipe up here.19:15
*** fzdarsky|afk has quit IRC19:15
zaropabelanger: was working on making moving zuul-launcher to openstack-ci repo, so this is kinda blocked on that task19:16
*** Leom has quit IRC19:16
zaronot sure where he’s at on that.19:16
*** Leom has joined #openstack-meeting19:16
zarobut if he’s not around then maybe note to ask him next time.19:16
*** lamt has quit IRC19:17
*** kaisers has joined #openstack-meeting19:17
*** egallen has quit IRC19:17
ianwyes i think he's travelling ATM19:17
ianwjust for the record, why does that block the gerrit upgrade?19:18
zaroit allows review-dev.o.o to work with zuul-dev.o.o again.  right now it zuul isn’t communicating with review-dev.19:21
*** kaisers has quit IRC19:21
zarogerrit upgrade path is to upgrade it on review-dev and make sure it works with current version of Zuul on Zuul-dev.19:22
*** jaugustine has quit IRC19:22
ianwlet's make it an action item so we don't forget, but will follow up19:23
*** jaugustine has joined #openstack-meeting19:23
ianw#action pabelanger update on zuul-launcher to openstack-ci move and zuul-dev for gerrit upgrade19:23
zarospecifically this thing, #link https://review.openstack.org/#/c/386745/19:24
ianwah, cool19:24
ianwanything else?19:24
*** antwash has left #openstack-meeting19:24
ianw#topic General topics19:24
*** openstack changes topic to "General topics (Meeting topic: infra)"19:24
ianwi have one on our disconnects to static.o.o19:25
ianw#link http://lists.openstack.org/pipermail/openstack-infra/2017-January/005103.html19:25
ianw#link https://review.openstack.org/#/c/426639/19:25
ianwi think the first mail explains it, but i feel like switching mpm's on static.o.o will be the easiest thing19:25
ianwbut ... i'm sure plenty of people have more experience apache wrangling than me, so any input appreciated19:26
*** jaugustine has quit IRC19:27
mordredianw: yah - the explanation seems reasonable, but I don't have a ton of real useful feedback on that one19:28
*** abalutoiu has quit IRC19:29
ianwno worries, just a callout if anyone had experience since it seems a commonish issue, at least enough to make it into the apache docs19:29
ianwok, moving on19:29
ianw#topic Open Discussion19:30
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:30
ianw#link https://review.openstack.org/#/c/423904/19:30
bkeroianw: we can try to move mpms and see if the issue arises. If it does I'm sure we can tweak the settings for it.19:30
ianwwe did talk about ^ last week, that was adding bindep to the wheel builders19:31
jlvillalReview request: https://review.openstack.org/425458   gerritbot-puppet  :)19:31
*** pcaruana has quit IRC19:31
jlvillalOr puppet-gerritbot to be correct.19:32
ianwthe wheel build jobs also now output a failure log file like -> http://logs.openstack.org/periodic/wheel-build-centos-7-amd64-python2/2420b36/logs/failed.txt.gz19:33
ianwfor example that shows old branches don't like the libvirt that ships with centos7.319:34
ianwjlvillal: oh, cool, that was my action item :)19:34
jlvillalianw: :)19:35
*** ociuhandu has joined #openstack-meeting19:36
AJaegerianw: do you have logs why something fails? spec-cleaner is part of OpenStack, so could you file a bug for the failure, please?19:37
ianwAJaeger: yes, the build logs are compressed into -> http://logs.openstack.org/periodic/wheel-build-centos-7-amd64-python2/2420b36/logs/build-logs.tar.bz219:38
ianwAJaeger: i'm not sure about spec-cleaner.  the NSS related ones need libraries installed ... which are specified in the requirements bindep ... which is why i started down this path :)19:39
*** SpamapS has quit IRC19:39
ianwoh yeah, that's right, the spec-cleaner one gives a odd setup.py error : http://paste.openstack.org/show/597080/19:41
*** Leom has quit IRC19:41
*** SpamapS has joined #openstack-meeting19:41
ianwanyway, we can look into that later19:41
ianwlast call, otherwise I think we're done a little early here19:41
*** jungleboyj has quit IRC19:42
AJaegerianw: oh, spec-cleaner is not in OpenStack - let me file the bug then...19:42
*** Leom has joined #openstack-meeting19:44
ianwok, as always we'll be in #openstack-infra for your infra needs19:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:44
openstackMeeting ended Tue Jan 31 19:44:21 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-01-31-19.01.html19:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-01-31-19.01.txt19:44
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-01-31-19.01.log.html19:44
*** Shrews has left #openstack-meeting19:44
*** jaugustine has joined #openstack-meeting19:44
*** annegentle has quit IRC19:45
*** AlanClark has joined #openstack-meeting19:45
*** jungleboyj has joined #openstack-meeting19:46
*** jkilpatr_ has quit IRC19:47
*** armax has quit IRC19:48
*** Cibo_ has quit IRC19:48
*** jungleboyj_ has joined #openstack-meeting19:49
*** rbowen has joined #openstack-meeting19:52
*** jungleboyj has quit IRC19:52
*** annegentle has joined #openstack-meeting19:53
*** jungleboyj has joined #openstack-meeting19:55
*** thingee has joined #openstack-meeting19:55
*** ociuhandu has quit IRC19:56
*** jungleboyj_ has quit IRC19:58
*** jkilpatr_ has joined #openstack-meeting20:01
*** ihrachys has joined #openstack-meeting20:01
*** jaugustine has quit IRC20:02
*** lamt has joined #openstack-meeting20:02
*** jaugustine has joined #openstack-meeting20:02
*** Sukhdev has joined #openstack-meeting20:03
* bswartz wonders where ttx is20:05
dolphmtc meeting canceled today, IIRC from a thread last week20:05
*** egallen has joined #openstack-meeting20:06
*** AJaeger has left #openstack-meeting20:06
*** egallen has quit IRC20:06
*** abalutoiu has joined #openstack-meeting20:06
*** gordc has joined #openstack-meeting20:07
*** sdake has quit IRC20:14
*** gouthamr has quit IRC20:20
*** rbowen has quit IRC20:23
*** acoles is now known as acoles_20:23
*** jaugustine has quit IRC20:24
*** mtanino_ has quit IRC20:25
*** lamt has quit IRC20:30
*** gouthamr has joined #openstack-meeting20:30
*** armax has joined #openstack-meeting20:30
*** lamt has joined #openstack-meeting20:31
*** xinli has joined #openstack-meeting20:36
*** gordc has left #openstack-meeting20:36
*** jaugustine has joined #openstack-meeting20:41
*** bobh has quit IRC20:41
*** askb has joined #openstack-meeting20:43
*** jaugustine has quit IRC20:44
*** newmember has joined #openstack-meeting20:45
*** rfolco has quit IRC20:45
*** jaugustine has joined #openstack-meeting20:45
*** beekhof has quit IRC20:45
*** beekhof has joined #openstack-meeting20:46
*** henrynash has quit IRC20:46
*** xyang1 has joined #openstack-meeting20:47
*** dbecker has quit IRC20:51
*** cdelatte has quit IRC20:51
*** Patifa has quit IRC20:53
*** Rockyg has joined #openstack-meeting20:53
*** e0ne has joined #openstack-meeting20:54
*** adiantum has joined #openstack-meeting20:55
*** lamt has quit IRC20:56
*** fnaval has quit IRC20:57
*** AlanClark has quit IRC20:59
*** Patifa has joined #openstack-meeting21:00
*** jaugustine has quit IRC21:00
*** raj_singh_ has joined #openstack-meeting21:02
*** newmember has quit IRC21:05
*** raj_singh_ has quit IRC21:05
*** sdake has joined #openstack-meeting21:08
*** korzen has quit IRC21:08
*** jprovazn has quit IRC21:14
*** ravelar has quit IRC21:16
*** jaugustine has joined #openstack-meeting21:18
*** jkilpatr_ has quit IRC21:18
*** lamt has joined #openstack-meeting21:18
*** mtanino has joined #openstack-meeting21:22
*** yamamoto has joined #openstack-meeting21:23
*** henrynash has joined #openstack-meeting21:29
*** yamamoto has quit IRC21:33
*** fguillot has quit IRC21:37
*** e0ne has quit IRC21:37
*** e0ne has joined #openstack-meeting21:40
*** jungleboyj has quit IRC21:41
*** e0ne has quit IRC21:42
*** baoli has quit IRC21:43
*** cleong has quit IRC21:44
*** annegentle has quit IRC21:44
*** jrobinson has joined #openstack-meeting21:46
*** ravelar1 has joined #openstack-meeting21:47
*** VW has quit IRC21:51
*** ravelar1 has quit IRC21:51
*** VW has joined #openstack-meeting21:51
*** jkilpatr_ has joined #openstack-meeting21:53
*** ihrachys has quit IRC21:53
*** baoli has joined #openstack-meeting21:54
*** VW has quit IRC21:55
*** diablo_rojo_phon has quit IRC22:00
*** thorst_ has quit IRC22:00
*** liangy has quit IRC22:00
*** baoli has quit IRC22:01
*** VW has joined #openstack-meeting22:03
*** jmckind has quit IRC22:05
*** lamt has quit IRC22:06
*** krtaylor has quit IRC22:07
*** dprince has quit IRC22:08
*** VW has quit IRC22:08
*** beekhof has quit IRC22:09
*** VW has joined #openstack-meeting22:09
*** lamt has joined #openstack-meeting22:14
*** megm has quit IRC22:14
*** yamamoto has joined #openstack-meeting22:15
*** jeblair has quit IRC22:16
*** kaisers has joined #openstack-meeting22:17
*** beekhof has joined #openstack-meeting22:19
*** Patifa has quit IRC22:19
*** thorst_ has joined #openstack-meeting22:20
*** kaisers has quit IRC22:22
*** jamesdenton has quit IRC22:22
*** jeblair has joined #openstack-meeting22:22
*** megm has joined #openstack-meeting22:23
*** thorst_ has quit IRC22:25
*** baoli has joined #openstack-meeting22:25
*** ykatabam has joined #openstack-meeting22:25
*** jaugustine has quit IRC22:27
*** diablo_rojo has joined #openstack-meeting22:27
*** lamt has quit IRC22:33
*** lamt has joined #openstack-meeting22:34
*** annegentle has joined #openstack-meeting22:35
*** priteau has quit IRC22:35
*** Patifa has joined #openstack-meeting22:35
*** Patifa has quit IRC22:35
*** kylek3h has quit IRC22:35
*** Patifa has joined #openstack-meeting22:38
*** lpetrut has quit IRC22:39
*** eharney has quit IRC22:42
*** amotoki has quit IRC22:44
*** thorst_ has joined #openstack-meeting22:45
*** henrynash has quit IRC22:47
*** dimtruck is now known as zz_dimtruck22:49
*** krtaylor has joined #openstack-meeting22:53
*** diablo_rojo has quit IRC22:54
*** spzala has quit IRC22:56
*** markvoelker_ has joined #openstack-meeting22:58
*** markvoelker has quit IRC22:58
*** sdake has quit IRC22:59
*** Patifa has quit IRC23:00
*** edtubill has quit IRC23:02
*** xyang1 has quit IRC23:03
*** yuanying has joined #openstack-meeting23:04
*** tonytan4ever has quit IRC23:05
*** xinli has quit IRC23:06
*** rbak__ has quit IRC23:07
*** sdake has joined #openstack-meeting23:08
*** bobmel has quit IRC23:08
*** bobmel has joined #openstack-meeting23:09
*** megm has quit IRC23:12
*** sdague has quit IRC23:13
*** megm has joined #openstack-meeting23:14
*** bobmel has quit IRC23:15
*** pradk has quit IRC23:19
*** baoli has quit IRC23:21
*** mriedem has quit IRC23:25
*** absubram has quit IRC23:27
*** sdake has quit IRC23:32
*** aeng has quit IRC23:33
*** gouthamr has quit IRC23:35
*** galstrom is now known as galstrom_zzz23:36
*** Leom has quit IRC23:37
*** adiantum has quit IRC23:42
*** aeng has joined #openstack-meeting23:46
*** VW_ has joined #openstack-meeting23:46
*** lamt has quit IRC23:49
*** tdasilva has quit IRC23:49
*** VW has quit IRC23:50
*** VW_ has quit IRC23:51
*** henrynash has joined #openstack-meeting23:52
*** diablo_rojo_phon has joined #openstack-meeting23:55
*** csomerville has quit IRC23:57

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