Tuesday, 2017-03-28

*** ntpttr_ has quit IRC00:00
*** jrobinson has joined #openstack-meeting00:01
*** ntpttr_ has joined #openstack-meeting00:02
*** luyao has quit IRC00:05
*** luyao has joined #openstack-meeting00:06
*** hongbin_ has quit IRC00:07
*** thorst has joined #openstack-meeting00:12
*** thorst has quit IRC00:13
*** ntpttr_ has quit IRC00:15
*** luyao has quit IRC00:16
*** luyao has joined #openstack-meeting00:16
*** ntpttr_ has joined #openstack-meeting00:17
*** gcb has quit IRC00:18
*** oomichi has quit IRC00:19
*** pvaneck has quit IRC00:22
*** diablo_rojo has joined #openstack-meeting00:22
*** oomichi has joined #openstack-meeting00:23
*** ntpttr_ has quit IRC00:25
*** mtanino_ has joined #openstack-meeting00:26
*** luyao has quit IRC00:26
*** ntpttr_ has joined #openstack-meeting00:26
*** luyao has joined #openstack-meeting00:26
*** mtanino has quit IRC00:27
*** ntpttr_ has quit IRC00:31
*** ntpttr_ has joined #openstack-meeting00:31
*** bzhao has quit IRC00:31
*** bzhao has joined #openstack-meeting00:32
*** luyao has quit IRC00:36
*** luyao has joined #openstack-meeting00:37
*** ntpttr_ has quit IRC00:38
*** ntpttr_ has joined #openstack-meeting00:39
*** ntpttr_ has quit IRC00:43
*** thorst has joined #openstack-meeting00:43
*** ntpttr_ has joined #openstack-meeting00:45
*** luyao has quit IRC00:46
*** luyao has joined #openstack-meeting00:47
*** gyee has quit IRC00:47
*** Julien-zte has joined #openstack-meeting00:47
*** Apoorva_ has joined #openstack-meeting00:48
*** Apoorva has quit IRC00:52
*** Apoorva_ has quit IRC00:52
*** ntpttr_ has quit IRC00:55
*** ntpttr_ has joined #openstack-meeting00:57
*** luyao has quit IRC00:57
*** luyao has joined #openstack-meeting00:57
*** gongysh has joined #openstack-meeting01:01
*** ntpttr_ has quit IRC01:01
*** yangyapeng has joined #openstack-meeting01:02
*** thorst has quit IRC01:02
*** ntpttr_ has joined #openstack-meeting01:03
*** luyao has quit IRC01:07
*** luyao has joined #openstack-meeting01:07
*** epico has joined #openstack-meeting01:08
*** amotoki has joined #openstack-meeting01:08
*** ntpttr_ has quit IRC01:11
*** thorst has joined #openstack-meeting01:11
*** thorst has quit IRC01:11
*** reedip has quit IRC01:12
*** ntpttr_ has joined #openstack-meeting01:13
*** markvoelker has quit IRC01:13
*** amotoki has quit IRC01:14
*** markvoelker has joined #openstack-meeting01:14
*** ntpttr_ has quit IRC01:17
*** luyao has quit IRC01:17
*** luyao has joined #openstack-meeting01:17
*** rfolco has joined #openstack-meeting01:18
*** ntpttr_ has joined #openstack-meeting01:19
*** knangia has quit IRC01:21
*** kevinz has joined #openstack-meeting01:23
*** ntpttr_ has quit IRC01:23
*** julim has quit IRC01:23
*** rfolco_ has joined #openstack-meeting01:24
*** julim has joined #openstack-meeting01:24
*** ntpttr_ has joined #openstack-meeting01:25
*** xgerman has quit IRC01:25
*** nakul_d has quit IRC01:25
*** AndyWojo has quit IRC01:25
*** hugokuo has quit IRC01:25
*** galstrom_zzz has quit IRC01:25
*** larainema has quit IRC01:26
*** xgerman has joined #openstack-meeting01:27
*** liusheng has quit IRC01:27
*** larainema has joined #openstack-meeting01:27
*** rfolco has quit IRC01:27
*** liusheng has joined #openstack-meeting01:27
*** nakul_d has joined #openstack-meeting01:27
*** AndyWojo has joined #openstack-meeting01:27
*** rmk has quit IRC01:27
*** luyao has quit IRC01:27
*** knangia has joined #openstack-meeting01:28
*** bobh has quit IRC01:28
*** luyao has joined #openstack-meeting01:28
*** galstrom_zzz has joined #openstack-meeting01:28
*** hugokuo has joined #openstack-meeting01:28
*** ntpttr_ has quit IRC01:29
*** SerenaFeng has joined #openstack-meeting01:30
*** ntpttr_ has joined #openstack-meeting01:31
*** unicell has quit IRC01:33
*** rmk has joined #openstack-meeting01:33
*** rmk has quit IRC01:33
*** rmk has joined #openstack-meeting01:33
*** gongysh has quit IRC01:34
*** ntpttr_ has quit IRC01:35
*** wanghao has joined #openstack-meeting01:36
*** SerenaFeng has quit IRC01:36
*** ntpttr_ has joined #openstack-meeting01:37
*** luyao has quit IRC01:38
*** luyao has joined #openstack-meeting01:38
*** SerenaFeng has joined #openstack-meeting01:40
*** huanxuan has joined #openstack-meeting01:41
*** markvoelker has quit IRC01:42
*** ntpttr_ has quit IRC01:43
*** kaisers_ has joined #openstack-meeting01:44
*** markvoelker has joined #openstack-meeting01:44
*** ntpttr_ has joined #openstack-meeting01:45
*** SerenaFe_ has joined #openstack-meeting01:47
*** yamahata has quit IRC01:48
*** luyao has quit IRC01:48
*** luyao has joined #openstack-meeting01:48
*** kaisers_ has quit IRC01:49
*** SerenaFeng has quit IRC01:49
*** ntpttr_ has quit IRC01:51
*** s3wong has quit IRC01:52
*** vishnoianil has quit IRC01:52
*** iyamahat has quit IRC01:53
*** ntpttr_ has joined #openstack-meeting01:53
*** zhurong has joined #openstack-meeting01:53
*** ntpttr_ has quit IRC01:57
*** zz_dimtruck is now known as dimtruck01:58
*** luyao has quit IRC01:58
*** luyao has joined #openstack-meeting01:59
*** ntpttr_ has joined #openstack-meeting01:59
*** reedip has joined #openstack-meeting02:00
*** ntpttr_ has quit IRC02:03
*** ntpttr_ has joined #openstack-meeting02:04
*** gcb has joined #openstack-meeting02:07
*** dschultz has quit IRC02:08
*** luyao has quit IRC02:08
*** ntpttr_ has quit IRC02:09
*** luyao has joined #openstack-meeting02:09
*** dschultz has joined #openstack-meeting02:10
*** mtanino_ has quit IRC02:12
*** thorst has joined #openstack-meeting02:12
*** ntpttr_ has joined #openstack-meeting02:14
*** Shunli has joined #openstack-meeting02:14
*** thorst has quit IRC02:17
*** luyao has quit IRC02:19
*** luyao has joined #openstack-meeting02:19
*** diablo_rojo has quit IRC02:27
*** MrJoshua has joined #openstack-meeting02:27
*** oomichi has quit IRC02:28
*** luyao has quit IRC02:29
*** luyao has joined #openstack-meeting02:29
*** hongbin has joined #openstack-meeting02:30
*** oomichi has joined #openstack-meeting02:32
*** esberglu has joined #openstack-meeting02:36
*** luyao has quit IRC02:39
*** oomichi has quit IRC02:39
*** luyao has joined #openstack-meeting02:40
*** esberglu has quit IRC02:40
*** oomichi has joined #openstack-meeting02:42
*** gongysh has joined #openstack-meeting02:43
*** sncder has joined #openstack-meeting02:43
*** kaisers_ has joined #openstack-meeting02:45
*** yamahata has joined #openstack-meeting02:47
*** luyao has quit IRC02:49
*** kaisers_ has quit IRC02:49
*** luyao has joined #openstack-meeting02:50
*** litao has joined #openstack-meeting02:52
*** bobh has joined #openstack-meeting02:53
*** Namrata has joined #openstack-meeting02:53
*** markvoelker has quit IRC02:54
*** diga has joined #openstack-meeting02:54
*** markvoelker has joined #openstack-meeting02:54
*** tommylikehu_ has joined #openstack-meeting02:57
*** lakerzhou has joined #openstack-meeting02:58
*** luyao has quit IRC03:00
hongbin#startmeeting zun03:00
openstackMeeting started Tue Mar 28 03:00:25 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-03-28_0300_UTC Today's agenda03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
*** VW has joined #openstack-meeting03:00
mkraiMadhuri Kumari03:00
hongbinthanks for joining lakerzhou Namrata kevinz yuanying mkrai03:01
hongbinlet's get started03:01
hongbin#topic Cinder integration (diga)03:01
*** openstack changes topic to "Cinder integration (diga) (Meeting topic: zun)"03:01
hongbin#link https://blueprints.launchpad.net/zun/+spec/cinder-zun-integration The BP03:01
hongbindiga: hi diga03:01
hongbindiga: want to give a update about he cinder integration bp?03:02
digaI think Core implementation part is completed03:02
*** tommylikehu_ has quit IRC03:02
hongbin#link https://review.openstack.org/#/c/429943/03:02
*** luyao has joined #openstack-meeting03:02
digahongbin: Tested with client also, thanks hongbin on help fixing the issue03:02
digahongbin: I haven't added test cases yet for my patch as patch is huge03:03
digahongbin: will start adding it now as code is working03:03
hongbindiga: feel free to add test cases in follow-up patches in this case03:03
*** FengShengqin has joined #openstack-meeting03:03
digahongbin: sure03:03
digahongbin: that's it from my side03:04
hongbindiga: i have a request for you03:04
digahongbin: yes03:04
hongbindiga: could you briefly explain how your patch works in high level?03:05
digahongbin: currently we have dependency on fuxi, we need fuxi for now, there are some testing pending fuxi side also but will test it today03:05
digahongbin: we have to make sure cinder, fuxi &03:06
*** pksingh has joined #openstack-meeting03:06
diga should exist03:06
pksinghHello, sorry for being late03:06
hongbinpksingh: hey, np, thanks for joining03:06
*** guodan has joined #openstack-meeting03:06
hongbindiga: ok03:07
digahongbin: then we can run create volume call from zunclient will go to cinder first, create volume & then pass that volume to fuxi to attach it to docker volume03:07
digahongbin: I will update step by step doc in wiki03:07
digahongbin: zun volume-create -n testvol -d fuxi (cli call)03:08
hongbindiga: ok, then the request will go to zun-api03:08
digahongbin: will try to cover all the testing today & push latest changes03:08
digahongbin: yes03:08
hongbindiga: zun-api will pass the request to ?03:08
*** mkrai_ has joined #openstack-meeting03:09
digazun-api will pass to volume driver03:09
hongbinok, i saw there are two volume drivers?03:09
mkrai_volume driver here is cinder or fuxi?03:09
*** bobh has quit IRC03:10
digavolume driver will call cinder driver to create volume & then request comes back to volume driver & then volume driver will initiate docker volume03:10
*** luyao has quit IRC03:10
*** luyao has joined #openstack-meeting03:10
digaCurrently I am creating volume first in Cinder, actually docker level we are using fuxi as volume driver03:10
hongbini see03:11
digahongbin: just one question on Fuxi03:12
hongbindiga: go ahead03:12
digahongbin: does fuxi support manila also ?03:12
hongbindiga: yes03:12
digahongbin: will go through it03:13
mkrai_diga: Yes03:13
mkrai_I see it in their github page03:13
*** thorst has joined #openstack-meeting03:13
hongbindiga: i think doc and tests can be added later03:13
digahongbin: okay03:14
hongbindiga: right now, our priority is to get the gate passed03:14
digahongbin: give me today, I will do one final testing & update the patch03:14
hongbindims: sure03:14
hongbindiga: sure03:14
hongbindims: sorry, wrong person :)03:14
digahongbin: but without test, how we can pass the gate03:14
digahongbin: is it possible ?03:15
hongbindiga: we should pass03:15
digahongbin: okay03:15
hongbindiga: i will help you with that offline03:15
digahongbin: okay, gr803:15
digahongbin: will ping you after meeting03:15
hongbindiga: sure, thanks for your huge contribution on this feature03:15
*** rfolco_ has quit IRC03:16
hongbinall, any other question for diga ?03:16
digahongbin: welcome!03:16
digahongbin: i m done!03:16
hongbinthanks diga03:17
hongbin#topic Kuryr integration (hongbin)03:17
*** openstack changes topic to "Kuryr integration (hongbin) (Meeting topic: zun)"03:17
hongbin#link https://blueprints.launchpad.net/zun/+spec/kuryr-integration The BP03:17
hongbini wanted to bring up this patch03:17
hongbin#link https://review.openstack.org/#/c/447732/03:17
*** fnaval has joined #openstack-meeting03:17
hongbindo everyone have a chance to review it?03:17
pksinghwill try to review by today03:18
hongbinif no, that is fine, i can give a brief introduction of it03:18
hongbinpksingh: ack, thx03:18
digahongbin: will take a look at it today03:18
mkrai_I also take a look today03:18
hongbinthanks everyone03:18
hongbinthe general idea is to have a network abstraction in zun, that maps the "docker network" command03:19
hongbinthen, container will join/leave a network, and two containers can share a network03:20
*** ykatabam has quit IRC03:20
*** luyao has quit IRC03:20
hongbincontainers within the same network should enjoy all the features provided by libnetwork03:20
hongbini.e. they can resolve each other by hostname03:20
*** ykatabam has joined #openstack-meeting03:20
*** luyao has joined #openstack-meeting03:21
hongbinthat is the idea03:21
hongbinfor details, we can discuss in the review03:21
hongbinany question for this one?03:21
mkrai_I am interested in looking the flow, but I suppose that it will be in the spec03:22
FengShengqinwill remove scanbox-container if using kuryr ?03:22
hongbinmkrai_: yes, the flow is on hte spec03:22
mkrai_Thanks hongbin I will take a look03:22
hongbinFengShengqin: yes, if kuryr is introduced, sandbox might be removed, but we can discuss it later03:22
FengShengqini see03:23
hongbinok, one more thing, i am going to implement the spec after it is approved, but feel free to ping me if anyone interest to take over the work03:23
digahongbin: I think sandbox feature is also a good addition to zun03:24
hongbindiga: yes, i am thinking we should make it optional , and let each driver to decide to support sandbox or not03:24
hongbindiga: but that could be decided later03:25
digahongbin: okay03:25
hongbinok, advance topic03:26
hongbin#topic Introduce host capabilities and cpusets (sudipto)03:26
*** openstack changes topic to "Introduce host capabilities and cpusets (sudipto) (Meeting topic: zun)"03:26
hongbin#link https://review.openstack.org/#/c/427007/ The spec03:26
hongbinit looks sudipta is not here03:26
hongbini saw he updated a patch03:26
hongbin#link https://review.openstack.org/#/c/449699/03:26
*** rderose has quit IRC03:27
hongbinthis is good, i guess the next step is the scheduler part03:27
hongbinany comment about this topic?03:28
hongbinok, move on03:28
hongbin#topic Make "command" as positional parameter for run/create03:28
*** openstack changes topic to "Make "command" as positional parameter for run/create (Meeting topic: zun)"03:28
hongbin#link https://bugs.launchpad.net/zun/+bug/167508203:29
openstackLaunchpad bug 1675082 in Zun "Make "command" parameter as positional" [Medium,Opinion] - Assigned to <email address hidden> (feng-shengqin)03:29
hongbini can briefly explain the idea03:29
hongbinright now, the style of the cli is: zun run --command xxx cirros03:29
hongbini proposed to change it to: zun run cirros sh03:30
*** jrobinson_ has joined #openstack-meeting03:30
kevinzmake it like docker cli?03:30
hongbinthat is : zun run cirros [command [args...]]03:30
*** SerenaFe_ has quit IRC03:30
*** luyao has quit IRC03:30
mkrai_command is not a mandatory param03:31
*** luyao has joined #openstack-meeting03:31
*** artom_ has joined #openstack-meeting03:31
mkrai_So is it good idea to make it positional03:31
*** artom has quit IRC03:31
*** jrobinson has quit IRC03:31
hongbinmkrai_: i don't think command is mandatory, since image can specify the default command03:31
mkrai_yes so is it good to make it positional? Then it becomes mandatory03:32
mkrai_to pass commands03:32
*** thorst has quit IRC03:33
hongbini think it is still optional even we changed it to positional (just like docker)03:33
hongbine.g. it can be: zun run nginx03:33
*** jrobinson_ is now known as jrobinson03:33
hongbinor it can be: zun run cirros sleep 10000003:33
mkrai_If so then I am ok with it03:34
hongbinmkrai_: ack03:34
hongbinothers, any remark for this one?03:34
hongbinfeel free to bring up opposing point of view if any03:35
hongbinpksingh: what is your opinion on that?03:35
*** links has joined #openstack-meeting03:36
pksinghhongbin: i am also OK with that03:36
hongbinpksingh: ack03:36
hongbinkevinz: you?03:36
kevinzhongbin: I'm OK also :-)03:36
hongbinFengShengqin: ok, i think you are ready to go03:37
FengShengqinOK.i will update the patch03:37
hongbinFengShengqin: thanks03:37
hongbinok, next topic03:38
hongbin#topic Discuss image name at glance03:38
*** openstack changes topic to "Discuss image name at glance (Meeting topic: zun)"03:38
hongbin#link https://review.openstack.org/#/c/446710/03:38
hongbinlakerzhou: want to drive this one?03:38
*** mriedem has joined #openstack-meeting03:38
lakerzhounow, docker commit can take repository and tag as inputs, but both optional03:39
lakerzhouI propose a mandatory input, e.g. image-name for zun commit command,03:41
*** luyao has quit IRC03:41
lakerzhouthe image-name will be used for the glance image03:41
*** luyao has joined #openstack-meeting03:41
lakerzhouUser can pull the status of the glance image using the input name.03:42
lakerzhouI am extending zun glance driver to create new image03:42
*** felipemonteiro has quit IRC03:43
lakerzhouis there any comments from the team about the proposal?03:44
pksinghhow does this image name fits to docker registry?03:44
lakerzhouif we want to correlate them, we must define some new rules explicitly.03:45
pksinghhow about this 'zun commit container repo [tag]' and convert repo to image-name internally for glance03:45
lakerzhoufor example, glance image name can be used for repository03:46
*** kaisers_ has joined #openstack-meeting03:46
mkrai_pksingh: to add to it and the tag in glance would be same as in docker03:46
mkrai_+1 to use the repo name as image name as is for glance03:47
*** IRCFrEAK has joined #openstack-meeting03:48
hongbini think we all agreed on using image name as repo?03:48
*** IRCFrEAK has left #openstack-meeting03:48
pksinghhongbin: user provide image-name and internally we treat it as repo?03:49
lakerzhouthen when user make multiple snapshots, images will created in same name03:49
mkrai_lakerzhou: We can differentiate based on tags03:49
mkrai_glance create api has tags field03:50
*** jkilpatr has quit IRC03:50
hongbinpksingh: yes, i think the discussion about i) user provide image-name ii) user provide repo03:50
*** kaisers_ has quit IRC03:50
hongbinpksingh: either i) or ii) the image-name is a repo internally03:50
lakerzhouyes, but it seems tag in glance has different meaning03:50
*** ajo has quit IRC03:50
*** luyao has quit IRC03:51
*** blair has quit IRC03:51
hongbinlakerzhou: what is the meaning of tag in glance?03:51
mkrai_Copied from glance api doc :"List of tags for this image. Each tag is a string of at most 255 chars. The maximum number of tags allowed on an image is set by the operator."03:51
pksinghhongbin: but image-name word does only fit to glance03:51
*** luyao has joined #openstack-meeting03:51
*** joanna has joined #openstack-meeting03:51
hongbinpksingh: yes, i agree on that03:52
*** ntpttr_ has quit IRC03:52
lakerzhouImage tags make it easy to group images into functional units. You can retrieve a particular group of images by using the tag=<tag_value> filter on an image-list call.03:52
lakerzhoufrom rackspace doc03:52
hongbini see03:53
hongbinlakerzhou: then, how about mapping docker tag as glance image properity?03:53
*** ajo has joined #openstack-meeting03:54
lakerzhouI haven't thought that, need to think about it.03:54
pksinghfor now i think we can go ahead with image-name, but i think in future we need to change that03:54
mkrai_Yes that's was also my suggestion03:54
mkrai_lakerzhou: I can help you with the glance tag/property work if you're ok with it03:55
*** ntpttr_ has joined #openstack-meeting03:55
lakerzhouBut I don't have strong opinion on either options. We have to explicitly define a rule if we want to correlate repo/tag to image name03:55
lakerzhousure, mkrai, please let me know you comments03:55
*** vipuls has quit IRC03:56
mkrai_lakerzhou: Thanks I will ping you later03:56
hongbinok, then i tried to summary the discussion on this03:56
lakerzhougreat, thanks mkrai03:56
*** vipuls has joined #openstack-meeting03:56
hongbin1. use image-name (with a future revisit to change it to repo)03:56
hongbin2. map docker tag to glance tag/property03:57
*** zhurong has quit IRC03:57
hongbinthen, zun commit <container> cirros:latest03:57
*** blair has joined #openstack-meeting03:57
*** tpatil has joined #openstack-meeting03:57
hongbinthis will convert to a glance image with name "cirros" and with tag/property "latest"03:58
hongbinis it the agreement of everyone?03:58
*** sagara has joined #openstack-meeting03:58
hongbin(just to confirm)03:58
*** samP has joined #openstack-meeting03:59
hongbinlakerzhou: then, i think you are good to go03:59
lakerzhouthanks all for the comments03:59
hongbinlakerzhou: thanks for leading the work on this feature03:59
hongbinsorry, we run out of time, we cannot cover all topics today04:00
*** rkmrHonjo has joined #openstack-meeting04:00
hongbinoverflow is on #openstack-zun channel04:00
hongbinall, thanks for joining hte meeting04:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"04:00
openstackMeeting ended Tue Mar 28 04:00:41 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-03-28-03.00.html04:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-03-28-03.00.txt04:00
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-03-28-03.00.log.html04:00
samPHi all for masakari04:01
*** kaisers_ has joined #openstack-meeting04:01
samP#startmeeting masakari04:01
openstackMeeting started Tue Mar 28 04:01:36 2017 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:01
*** openstack changes topic to " (Meeting topic: masakari)"04:01
openstackThe meeting name has been set to 'masakari'04:01
*** luyao has quit IRC04:01
samPsorry for long absent04:01
*** luyao has joined #openstack-meeting04:01
*** kaisers_ has quit IRC04:02
samP#topic critical bugs04:02
*** openstack changes topic to "critical bugs (Meeting topic: masakari)"04:02
samPAny bugs need to discuss?04:02
rkmrHonjoI'd like to discuss about https://bugs.launchpad.net/masakari/+bug/167094004:03
openstackLaunchpad bug 1670940 in masakari "If failure host is the reserved host, the compute service of the failure host finally beccomes the enable status" [Undecided,In progress] - Assigned to takahara.kengo (takahara.kengo)04:03
samPrkmrHonjo: ok..04:03
*** armax has quit IRC04:03
rkmrHonjoThere are two solutions for this issue.04:04
samPrkmrHonjo: yep04:04
rkmrHonjoNo.1 Remove crushed node from reserved host list. Reserved flag of the crushed node will be still "True" after evacuating.04:04
rkmrHonjoNo.2 Change reserved flag of the crushed node to "False" before getting reserved host list. (As a result, crushed node will be not contained in reserved host list.)04:04
rkmrHonjoTakahara and I think that No.2 is simpler than No.1. But we can agree with No.1 if it has advantage or reasons.04:05
*** mriedem has quit IRC04:05
rkmrHonjoDo anyone have the opinion about this?04:05
*** pksingh has quit IRC04:05
samPrkmrHonjo: in both cases on_maintenance': True?04:05
rkmrHonjosamP: yes.04:06
sagaraIs there any notification to operator both cases?04:06
tpatilsagara: Notification is not implemented yet in masakari04:07
samPsagara: tpatil is correct, we dont have it yet04:07
*** Namrata has quit IRC04:07
sagaraSo can operator find that event in logs.04:07
sagaraSo can operator find that event in logs?04:07
*** ntpttr_ has quit IRC04:08
samPsagara: he may, but we have out sufficient log for that04:08
tpatilthere are no logs to indicate on_maintenance is set to True04:08
*** ntpttr_ has joined #openstack-meeting04:09
samPtpatil: yes, IMO we have to add that log msg04:09
tpatilSure, we will add logs for this purpose, as well as identify other places which needs logs04:10
samPif we use solution 2., next time when we get the reserved host list, this host will still in the list with on-maintenance= true right?04:10
tpatilsamP: correct04:11
rkmrHonjosamP: No. please wait for writing...04:11
*** luyao has quit IRC04:11
*** luyao has joined #openstack-meeting04:12
tpatilhttps://github.com/openstack/masakari/blob/master/masakari/engine/manager.py#L143, this is where on_maintenance is set to True04:12
rkmrHonjosamP: In solution 2, reserved flag will be changed to "false". Because crushed host is not contained in reserved host list at next time.04:12
samPrkmrHonjo: tpatil sorry I mean solution 1.04:13
rkmrHonjosamP: OK.04:13
samPrkmrHonjo: you are right, in sol 2. you will not get this host on the list any more04:13
tpatilrkmrHonjo: Did you check my comment which I have added today?04:15
samPso, if we can log out this issue, and set the host reserved=False, on_maintenance=True, then it will not effect further operations in masakari.04:16
samPAnd operator can take care of it later, and he may re-add this node after fix reserved=True, on_maintenance=False04:17
rkmrHonjotpatil: Yes. In my understand, your comment is telling about solution 2. and, I don't think that overwriting "false" to "false" is not a problem.04:17
*** lakerzhou has quit IRC04:17
rkmrHonjos/I don't think/I think/gc04:17
samPrkmrHonjo: I think tpatil's comment is about unnecessary logic when the node is not a reserved host04:18
rkmrHonjosamP: Yes. But, is there problem if overwriting reserved flag from false to false?04:19
tpatilI think we should not update on_maintenance and reserved for no reasons04:19
tpatilThere are no issues but I don't think that is a good thing to do either04:19
samPrkmrHonjo: no issue with overwriting same value, but why generate unnecessary call04:21
*** markvoelker has quit IRC04:21
*** luyao has quit IRC04:22
tpatilsamP: on_maintenance and reserved properties of host is updated in a single call04:22
*** luyao has joined #openstack-meeting04:22
samPtpatil: correct04:22
*** gouthamr has quit IRC04:23
rkmrHonjotpatil, samP: OK, I agree with your opinion.04:23
*** markvoelker has joined #openstack-meeting04:23
rkmrHonjoI'll tell this decision to Takahara.04:24
samPrkmrHonjo: I also prefer to add comment there, about why we doing this04:24
samPrkmrHonjo: thanks04:24
samPI will add this to gerrit04:25
rkmrHonjosamP: tanks.04:25
samPrkmrHonjo: np04:25
samPany other bugs?04:25
samP#link https://bugs.launchpad.net/masakari/+bug/166351304:26
openstackLaunchpad bug 1663513 in masakari "Masakari failed to rescue PAUSED instances" [High,Confirmed] - Assigned to Dinesh Bhor (dinesh-bhor)04:26
samPsorry, I missed this todo item..04:26
tpatilsamP: please add your suggestion and Dinesh will take it forward04:27
*** hongbin has quit IRC04:27
*** sridharg has joined #openstack-meeting04:27
samPtpatil: I will definitely do it today04:27
tpatilsamP: Thanks04:28
samPif no other bugs, let's jump in to Discussion points04:28
samP#topic Discussion points04:28
*** openstack changes topic to "Discussion points (Meeting topic: masakari)"04:28
samPAbout Pike work items:04:28
tpatilNeed your approval on BP: https://blueprints.launchpad.net/masakari/+spec/enable-openstack-proposal-bot04:28
samP#link Pike work items https://etherpad.openstack.org/p/masakari-pike-workitems04:29
*** thorst has joined #openstack-meeting04:30
samPtpatil: I think I did...04:30
*** ntpttr_ has quit IRC04:30
tpatilsamP: I missed that point. I will request Dinesh to upload patches for community review04:31
*** mkrai_ has quit IRC04:31
samPtpatil: sure, thank you04:31
tpatilNext item: Add devstack plugin for masakari-monitors04:31
*** shu-mutou has joined #openstack-meeting04:31
tpatilI will add support in devstack to install masakari_monitors only on the node where nova-compute is configured04:32
*** luyao has quit IRC04:32
*** SerenaFeng has joined #openstack-meeting04:32
*** luyao has joined #openstack-meeting04:32
samPtpatil: great..04:32
rkmrHonjotpatil: Does it support all-in-one?04:33
*** ntpttr_ has joined #openstack-meeting04:33
samPtpatil: May assign this task to you?04:34
*** thorst has quit IRC04:34
tpatilrkmrHonjo: I think it shouldn't matter, masakari-monitor should be run only on the node where nova-compute is running04:34
rkmrHonjotpatil: OK.04:34
tpatilin other words ,it will be installed on all-in-one as well as multiple nodes04:35
tpatilsamP: Dinesh will work on this item04:35
samPtpatil: sure..04:35
samPtpatil: any other items would you like to bring up?04:36
sagaraI would like to confirm who writes spec and blueprint for each Pike items. Is it OK to write bp/spec by whom suggested each items?04:36
*** jrobinson has quit IRC04:36
sagaraI am seeing https://etherpad.openstack.org/p/masakari-pike-workitems #L15-2204:37
samPsagara: yes, lest discuss that after this..04:37
samPsagara: I wrote what I thought there..04:37
*** radeks has joined #openstack-meeting04:37
samPOK, if no other items from tpatil, let's go to bp/spec discussion04:38
samP#topic BP/spec for Pike04:38
*** openstack changes topic to "BP/spec for Pike (Meeting topic: masakari)"04:38
samP#link bp/specs https://etherpad.openstack.org/p/masakari-pike-workitems #L15-2204:38
samPI wrote some items, which I think need more clarification before go to implementation04:39
samPyou may suggest otherwise.. or add items04:40
*** claudiub has joined #openstack-meeting04:40
samPI just picked up them from priority H items. Priority M and L are not there yet..04:41
samPI will add them soon..04:41
tpatilRecovery method customization: What are the things that you are expecting to customize for execution of workflow for each notification type?04:42
*** luyao has quit IRC04:42
*** adisky_ has joined #openstack-meeting04:42
*** luyao has joined #openstack-meeting04:43
*** dschultz has quit IRC04:43
samPtpatil: recovery actions should be customizable04:43
*** dschultz has joined #openstack-meeting04:44
samPtpatil: IMO, those recovery actions can be selected from pre defined action in masakari.04:45
*** iceyao has joined #openstack-meeting04:45
*** ntpttr_ has quit IRC04:46
tpatilTo cater to this requirement, we need to check if taskflow has this support in place04:46
samPtpatil: I think its better to write some sample customization scenario04:47
tpatilThis is certainly doable if we use mistral workflow04:47
*** ntpttr_ has joined #openstack-meeting04:47
samPtpatil: sure..04:47
samPtpatil: correct, since Mistral Integration is marked as M item, I thought its better not to address it here...04:48
*** dschultz has quit IRC04:49
tpatilif you can list down pre-define actions and possible recovery action customization use cases, I will check if it can be supported by Taskflow04:49
samPtpatil: sure, I will do that. then we can decide whether to use Taskflow or MIstral04:50
tpatilsamP: Thanks04:50
*** yangyapeng has quit IRC04:51
samP#action samP create customization scenarios for recovery actions04:51
*** yangyapeng has joined #openstack-meeting04:52
samPAnd for Force Stonith, I will write the spec04:52
*** luyao has quit IRC04:52
*** luyao has joined #openstack-meeting04:53
sagarasamP: thanks. please write that.04:54
*** jrobinson has joined #openstack-meeting04:54
samPCould some onw write the spec for Notifying API progress? or do we need spec for this?04:55
*** SerenaFeng has quit IRC04:55
samPcause this feature has already implemented in other projects, might not need detailed spec04:55
*** ntpttr_ has quit IRC04:56
tpatilHonjo: Are you interested to work on this item? if not, I will work on it.04:56
*** ayogi has joined #openstack-meeting04:56
*** yangyapeng has quit IRC04:56
*** zhurong has joined #openstack-meeting04:56
rkmrHonjotpatil: I interest about it.04:57
*** ntpttr_ has joined #openstack-meeting04:57
tpatilrkmrhonjo: sure04:57
samPok then, I will add rkmrHonjo for this..04:57
rkmrHonjosamP: thanks.04:57
samPrkmrHonjo: about split-brain, do you have any plans?04:58
sagarasamP, rkmrHonjo: Could you tell us any example of Notifying API progress. Is that like glance-client --progress?04:58
*** tommylikehu_ has joined #openstack-meeting04:59
rkmrHonjosagara: No. It means that sending RPC message when API process is started/completed.04:59
samPwe only have, 1 mins left...04:59
sagararkmrHonjo: thanks. OK, I understood04:59
rkmrHonjosamP: I don't have plan now. I should start to think about it.04:59
samPlets, discuss on openstack-masakari04:59
samPwe are out of time..05:00
samPlet finish here and move to openstack-masakari05:00
samPthank you all.....05:00
sagarathank you05:00
tpatilThank you, Bye05:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:00
openstackMeeting ended Tue Mar 28 05:00:57 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-03-28-04.01.html05:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-03-28-04.01.txt05:01
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-03-28-04.01.log.html05:01
rkmrHonjothank you all05:01
samPthank you all...05:01
*** kaisers_ has joined #openstack-meeting05:02
*** luyao has quit IRC05:03
*** luyao has joined #openstack-meeting05:03
*** tommylikehu_ has quit IRC05:03
*** markvoelker has quit IRC05:04
*** anilvenkata has joined #openstack-meeting05:05
*** trinaths has joined #openstack-meeting05:05
*** tpatil has quit IRC05:05
*** makowals_ has joined #openstack-meeting05:06
*** kaisers_ has quit IRC05:07
*** makowals has quit IRC05:07
*** iceyao has quit IRC05:09
*** makowals has joined #openstack-meeting05:10
*** nkrinner_afk is now known as nkrinner05:10
*** makowals_ has quit IRC05:11
*** luyao has quit IRC05:13
*** luyao has joined #openstack-meeting05:13
*** lamt has joined #openstack-meeting05:19
*** Akhil has joined #openstack-meeting05:19
*** sagara has quit IRC05:22
*** luyao has quit IRC05:23
*** luyao has joined #openstack-meeting05:24
*** ntpttr_ has quit IRC05:25
*** ntpttr_ has joined #openstack-meeting05:25
*** rkmrHonjo has quit IRC05:27
*** gjayavelu has joined #openstack-meeting05:28
*** ntpttr_ has quit IRC05:30
*** ntpttr_ has joined #openstack-meeting05:31
*** luyao has quit IRC05:33
*** SerenaFeng has joined #openstack-meeting05:34
*** luyao has joined #openstack-meeting05:34
*** vishwanathj has quit IRC05:35
*** ntpttr_ has quit IRC05:35
*** ntpttr_ has joined #openstack-meeting05:37
*** rcernin has joined #openstack-meeting05:38
*** ntpttr_ has quit IRC05:41
*** ntpttr_ has joined #openstack-meeting05:42
*** luyao has quit IRC05:44
*** luyao has joined #openstack-meeting05:44
*** ntpttr_ has quit IRC05:47
*** wxy_ has quit IRC05:48
*** wxy_ has joined #openstack-meeting05:48
*** ntpttr_ has joined #openstack-meeting05:49
*** dschultz has joined #openstack-meeting05:52
*** ykatabam has quit IRC05:52
*** ntpttr_ has quit IRC05:53
*** luyao has quit IRC05:54
*** luyao has joined #openstack-meeting05:54
*** ntpttr_ has joined #openstack-meeting05:55
*** nadya has joined #openstack-meeting06:00
*** imcsk8_ has joined #openstack-meeting06:01
*** imcsk8 has quit IRC06:01
*** ntpttr_ has quit IRC06:01
*** lamt has quit IRC06:01
*** ntpttr_ has joined #openstack-meeting06:03
*** kaisers_ has joined #openstack-meeting06:04
*** luyao has quit IRC06:04
*** luyao has joined #openstack-meeting06:05
*** lamt has joined #openstack-meeting06:05
*** nadya has quit IRC06:07
*** nadya has joined #openstack-meeting06:08
*** andreas_s has joined #openstack-meeting06:08
*** nadya has quit IRC06:08
*** kaisers_ has quit IRC06:08
*** caowei has joined #openstack-meeting06:08
*** ntpttr_ has quit IRC06:09
*** ntpttr_ has joined #openstack-meeting06:11
*** dschultz has quit IRC06:12
*** luyao has quit IRC06:14
*** luyao has joined #openstack-meeting06:15
*** bkopilov_ has quit IRC06:19
*** lamt has quit IRC06:19
*** rbartal has joined #openstack-meeting06:20
*** bkopilov has quit IRC06:20
*** ntpttr_ has quit IRC06:22
*** ntpttr_ has joined #openstack-meeting06:23
*** luyao has quit IRC06:25
*** luyao has joined #openstack-meeting06:25
*** bbbzhao has joined #openstack-meeting06:26
*** bzhao has quit IRC06:27
*** bbzhao has quit IRC06:27
*** ntpttr_ has quit IRC06:27
*** bzhao has joined #openstack-meeting06:27
*** ntpttr_ has joined #openstack-meeting06:29
*** cdub has quit IRC06:30
*** thorst has joined #openstack-meeting06:31
*** jprovazn has joined #openstack-meeting06:32
*** ntpttr_ has quit IRC06:33
*** ltomasbo|away is now known as ltomasbo06:35
*** ntpttr_ has joined #openstack-meeting06:35
*** luyao has quit IRC06:35
*** thorst has quit IRC06:35
*** sncder has quit IRC06:35
*** sncder has joined #openstack-meeting06:36
*** luyao has joined #openstack-meeting06:36
*** sncder has quit IRC06:37
*** sncder has joined #openstack-meeting06:37
*** gjayavelu has quit IRC06:38
*** ntpttr_ has quit IRC06:42
*** lamt has joined #openstack-meeting06:42
*** ntpttr_ has joined #openstack-meeting06:43
*** luyao has quit IRC06:45
*** luyao has joined #openstack-meeting06:46
*** lamt has quit IRC06:46
*** SerenaFeng has quit IRC06:47
*** oomichi has quit IRC06:48
*** sambetts|afk has quit IRC06:48
*** ntpttr_ has quit IRC06:49
*** ntpttr_ has joined #openstack-meeting06:51
*** lamt has joined #openstack-meeting06:51
*** oomichi has joined #openstack-meeting06:52
*** cdub has joined #openstack-meeting06:52
*** sambetts_ has joined #openstack-meeting06:52
*** sridharg has quit IRC06:53
*** xianghui has joined #openstack-meeting06:53
*** luyao has quit IRC06:55
*** luyao has joined #openstack-meeting06:56
*** mtreinish has quit IRC06:57
*** mtreinish has joined #openstack-meeting06:58
*** cdub has quit IRC06:58
*** matrohon has joined #openstack-meeting07:00
*** fzdarsky has joined #openstack-meeting07:00
*** tommylikehu_ has joined #openstack-meeting07:00
*** tobberydberg has joined #openstack-meeting07:01
*** kaisers_ has joined #openstack-meeting07:04
*** tommylikehu_ has quit IRC07:05
*** luyao has quit IRC07:06
*** luyao has joined #openstack-meeting07:06
*** trinaths has left #openstack-meeting07:06
*** cdub has joined #openstack-meeting07:06
*** kaisers_ has quit IRC07:08
*** lamt has quit IRC07:10
*** ntpttr_ has quit IRC07:12
*** ntpttr_ has joined #openstack-meeting07:13
*** amotoki has joined #openstack-meeting07:13
*** pcaruana has joined #openstack-meeting07:13
*** luyao has quit IRC07:16
*** luyao has joined #openstack-meeting07:16
*** tesseract has joined #openstack-meeting07:18
*** amotoki has quit IRC07:18
*** ntpttr_ has quit IRC07:19
*** jrobinson has quit IRC07:21
*** ntpttr_ has joined #openstack-meeting07:21
*** nadya has joined #openstack-meeting07:21
*** aarefiev_afk is now known as aarefiev07:24
*** luyao has quit IRC07:26
*** luyao has joined #openstack-meeting07:27
*** ntpttr_ has quit IRC07:27
*** ntpttr_ has joined #openstack-meeting07:29
*** rcernin has quit IRC07:29
*** SerenaFeng has joined #openstack-meeting07:32
*** nadya has quit IRC07:34
*** nadya has joined #openstack-meeting07:34
*** hashar has joined #openstack-meeting07:35
*** lpetrut has joined #openstack-meeting07:35
*** luyao has quit IRC07:36
*** luyao has joined #openstack-meeting07:37
*** ntpttr_ has quit IRC07:37
*** makowals has quit IRC07:37
*** ntpttr_ has joined #openstack-meeting07:39
*** martinkopec has joined #openstack-meeting07:39
*** xiaofandh12 has joined #openstack-meeting07:41
*** nadya has quit IRC07:42
*** wanghao has quit IRC07:42
*** nadya has joined #openstack-meeting07:42
*** wanghao has joined #openstack-meeting07:43
*** nadya has quit IRC07:43
*** donghao has quit IRC07:44
*** julim has quit IRC07:44
*** luyao has quit IRC07:47
*** rcernin has joined #openstack-meeting07:47
*** bbzhao has joined #openstack-meeting07:47
*** julim has joined #openstack-meeting07:47
*** luyao has joined #openstack-meeting07:47
*** sridharg has joined #openstack-meeting07:47
*** SerenaFeng has quit IRC07:49
*** makowals has joined #openstack-meeting07:49
*** bbbzhao has quit IRC07:51
*** liusheng has quit IRC07:51
*** iyamahat has joined #openstack-meeting07:51
*** liusheng has joined #openstack-meeting07:51
*** ntpttr_ has quit IRC07:55
*** ntpttr_ has joined #openstack-meeting07:57
*** iyamahat has quit IRC07:57
*** luyao has quit IRC07:57
*** luyao has joined #openstack-meeting07:57
*** sagara has joined #openstack-meeting07:58
*** eranrom has joined #openstack-meeting07:59
*** cdub has quit IRC07:59
*** rossella_s has joined #openstack-meeting07:59
*** akihito has joined #openstack-meeting08:00
eranrom#startmeeting storlets08:00
openstackMeeting started Tue Mar 28 08:00:15 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
openstackThe meeting name has been set to 'storlets'08:00
*** bkopilov_ has joined #openstack-meeting08:00
*** tommylikehu_ has joined #openstack-meeting08:01
*** bkopilov has joined #openstack-meeting08:01
eranromAgenda for today: https://wiki.openstack.org/wiki/Meetings/Storlets08:02
*** kota_ has joined #openstack-meeting08:02
*** dbecker has joined #openstack-meeting08:02
eranromkota_: hi08:03
*** tobberydberg has quit IRC08:03
kota_oops, tripled l08:03
sagarakota_: hi08:03
eranromjust posted the agenda08:03
kota_sorry for late08:03
eranromkota_: np.08:03
eranrom#topic Quick updates08:03
*** openstack changes topic to "Quick updates (Meeting topic: storlets)"08:03
*** SerenaFeng has joined #openstack-meeting08:03
kota_just concentrate some staff in my review list08:03
*** iceyao has joined #openstack-meeting08:03
*** abalutoiu__ has quit IRC08:03
eranromkota_: sure.08:03
eranromso there is a new project navigator for Openstack and we are there.08:04
eranromwhich I find very cool08:04
eranromto us!08:05
kota_i saw that status :)08:05
*** kaisers_ has joined #openstack-meeting08:05
eranromOtherwise, I assume you have seen it on the mailing list, but on Thursday I will give a web talk on storlets and deep learning08:05
*** tommylikehu_ has quit IRC08:06
*** rcernin has quit IRC08:06
kota_tweeted, https://twitter.com/bloodeagle40234/status/84653438678265446408:07
*** ntpttr_ has quit IRC08:07
sagaraI'll confirm Eran's demo details.08:07
eranromkota_: Thanks!08:07
*** luyao has quit IRC08:07
*** rcernin has joined #openstack-meeting08:07
*** luyao has joined #openstack-meeting08:08
eranromkota_: I guess I should tweet it as well.08:09
*** ntpttr_ has joined #openstack-meeting08:09
kota_good way i suppose08:09
eranromkota_: yep.08:09
*** nadya has joined #openstack-meeting08:10
*** dschultz has joined #openstack-meeting08:10
*** rcernin has quit IRC08:10
*** kaisers_ has quit IRC08:10
eranrom#topic prioritizing reviews08:10
*** openstack changes topic to "prioritizing reviews (Meeting topic: storlets)"08:10
*** rcernin has joined #openstack-meeting08:10
*** acabot has quit IRC08:11
eranromNot much as changed.08:11
*** nadya_ has joined #openstack-meeting08:11
kota_and the copy fix landed priort to priority high :P08:12
*** nadya has quit IRC08:12
eranromI added one that is important for me, and which greatly simplifies agent side development (it's number 5 on the high)08:12
*** ykatabam has joined #openstack-meeting08:12
eranromkota_: well it was superhigh08:12
eranromI also needed that for my demo on Thursdaty08:12
kota_eranrom: gotcha08:13
*** ykatabam has quit IRC08:13
eranromalso I guess that from your perspective it was higher :-)08:14
*** amotoki has joined #openstack-meeting08:14
*** ralonsoh has joined #openstack-meeting08:16
*** Shunli has quit IRC08:17
eranromanything else on reviews?08:17
kota_for now, nothing from me08:17
*** luyao has quit IRC08:17
*** ntpttr_ has quit IRC08:17
kota_I'd like to know the status on your ipython get08:18
*** luyao has joined #openstack-meeting08:18
kota_today, I tried to look at it but you set your -2 on that08:18
kota_what is going on?08:18
eranromright, there was a bug I discovered while working on the demo.08:18
kota_maybe I'd like to raise the priority up (because I want to make a custormer demo with that ;-))08:19
*** amotoki has quit IRC08:19
*** ntpttr_ has joined #openstack-meeting08:19
eranromok, I think I can fix that tomorrow.08:19
*** abalutoiu has joined #openstack-meeting08:19
eranromIf there is nothing else, we can go to the next topic.08:20
eranrom#topic Continue design discussions(?)08:20
*** openstack changes topic to "Continue design discussions(?) (Meeting topic: storlets)"08:20
eranromsagara: akihito: do you want to discuss anything?08:21
*** mickeys has quit IRC08:21
sagaraeranrom: thanks for reviewing my resource management idea, 2 week ago.08:21
sagaraI could not move it forward in this week. but I think it needs to write blueprints about that.08:21
sagarait's all of my update.08:22
eranromsagara: sure, thanks for the update08:22
sagarado I need to write spec? not only BP.08:23
kota_eranrom: I reviewed sagara's idea locally and it looks cool, that is what we want08:24
kota_i support it08:24
eranromsagara: we do not have any strict rules here.08:24
*** dgonzalez has quit IRC08:24
* kota_ still need experience with docker container though08:24
*** epico has quit IRC08:24
eranromsagara: whatever works for you. Personally I like to work with the wiki, and place stuff there.08:25
*** epico has joined #openstack-meeting08:25
*** ntpttr_ has quit IRC08:26
eranromsagara: but of you prefer BP that is fine.08:26
*** ntpttr_ has joined #openstack-meeting08:27
sagaraI haven't know Storlet/Swift way, so I'll write it to wiki as same as Eran.08:27
*** luyao has quit IRC08:28
*** luyao has joined #openstack-meeting08:28
*** dschultz has quit IRC08:29
eranromsagara: I think (not sure) this is also the way Swift works with feature planning.08:29
*** iceyao has quit IRC08:29
sagaraOK, thanks. I have learned Swift way.08:30
*** dgonzalez has joined #openstack-meeting08:30
eranromok, anything else for today?08:30
*** yamamoto has quit IRC08:31
akihitosorry. I have no updates..08:31
kota_that's all08:31
akihitoI will fix following codes. <<https://review.openstack.org/#/c/406620/>> and <<https://review.openstack.org/#/c/436263/>>08:31
*** yamahata has quit IRC08:31
eranromakihito: great, thanks!08:32
eranromok, so thanks for joining.08:32
*** tobberydberg has joined #openstack-meeting08:32
eranromTalk to you later08:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:32
openstackMeeting ended Tue Mar 28 08:32:55 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-03-28-08.00.html08:32
*** tobberydberg has quit IRC08:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-03-28-08.00.txt08:33
*** kota_ has left #openstack-meeting08:33
openstackLog:            http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-03-28-08.00.log.html08:33
*** tobberydberg has joined #openstack-meeting08:33
*** thorst has joined #openstack-meeting08:33
sagarathanks, bye08:33
*** zhhuabj has quit IRC08:33
*** e0ne has joined #openstack-meeting08:35
*** tobberydberg has quit IRC08:35
*** alexchadin has joined #openstack-meeting08:36
*** iceyao has joined #openstack-meeting08:36
*** yuvalb has quit IRC08:36
*** tobberydberg has joined #openstack-meeting08:37
*** abalutoiu_ has joined #openstack-meeting08:37
*** ntpttr_ has quit IRC08:38
*** luyao has quit IRC08:38
*** wanghao has quit IRC08:38
*** luyao has joined #openstack-meeting08:39
*** ntpttr_ has joined #openstack-meeting08:39
*** abalutoiu has quit IRC08:40
*** iceyao has quit IRC08:41
*** iceyao has joined #openstack-meeting08:42
*** tobberydberg has quit IRC08:42
*** dbecker has quit IRC08:42
*** rossella_s has quit IRC08:42
*** rossella_s has joined #openstack-meeting08:43
*** ntpttr_ has quit IRC08:43
*** bbbzhao has joined #openstack-meeting08:43
*** guodan has quit IRC08:44
*** ntpttr_ has joined #openstack-meeting08:45
*** zhhuabj has joined #openstack-meeting08:46
*** bzhao has quit IRC08:46
*** rcernin has quit IRC08:46
*** rcernin has joined #openstack-meeting08:46
*** zengchen has joined #openstack-meeting08:48
*** electrofelix has joined #openstack-meeting08:48
*** rcernin_ has joined #openstack-meeting08:48
*** luyao has quit IRC08:48
*** luyao has joined #openstack-meeting08:49
*** zhhuabj has quit IRC08:50
*** akihito has quit IRC08:51
*** thorst has quit IRC08:52
*** fnaval has quit IRC08:53
*** ntpttr_ has quit IRC08:54
*** toscalix has joined #openstack-meeting08:54
*** ntpttr_ has joined #openstack-meeting08:55
*** luyao has quit IRC08:58
*** luyao has joined #openstack-meeting08:59
*** ntpttr_ has quit IRC08:59
*** tommylikehu_ has joined #openstack-meeting09:00
*** tommylikehu_ has quit IRC09:00
*** ntpttr_ has joined #openstack-meeting09:00
yuval#startmeeting karbor09:00
openstackMeeting started Tue Mar 28 09:00:12 2017 UTC and is due to finish in 60 minutes.  The chair is yuval. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** chenhuayi_ has joined #openstack-meeting09:00
*** openstack changes topic to " (Meeting topic: karbor)"09:00
openstackThe meeting name has been set to 'karbor'09:00
yuvalHello, and welcome to Karbor's weekly meeting!09:00
yuval\ (•◡•) /09:00
yuvalwaiting a couple of minutes for more people to arrive09:01
*** zhonghua2 has joined #openstack-meeting09:01
*** tommylikehu_ has joined #openstack-meeting09:02
*** edisonxiang has joined #openstack-meeting09:02
*** tommylikehu_ has quit IRC09:02
*** tommylikehu_ has joined #openstack-meeting09:02
*** tommylikehu_ has quit IRC09:02
*** zhhuabj has joined #openstack-meeting09:02
*** zhongjun_ has joined #openstack-meeting09:02
*** abalutoiu_ is now known as abalutoiu09:02
yuval#info chenhuay, zhonghua, xiang in meeting09:03
yuvallets begin09:03
yuvalI guess chenying and zhangshuai are busy09:03
yuval#info zhongjun in meeting09:03
*** chenying__ has joined #openstack-meeting09:03
yuval#topic Task assignments09:03
*** openstack changes topic to "Task assignments (Meeting topic: karbor)"09:03
yuval#link https://ethercalc.openstack.org/karbor-pike09:04
*** zhangshuai has joined #openstack-meeting09:04
yuvalwe have assignees for most high priority tasks09:04
*** ntpttr_ has quit IRC09:04
*** tommylikehu_ has joined #openstack-meeting09:04
*** tommylikehu_ has quit IRC09:04
yuvalplease take a look and see if you can take something from high/med priority on yourselves09:04
yuvalalso, change only assignee part of the doc09:05
chenying__'Deployment Guide zhangshuai has worked on this task.09:05
*** ntpttr_ has joined #openstack-meeting09:05
zhonghua2yuval, can everyone change the documents?09:05
yuvalzhonghua2: yes, but please only change assignee, not priority or tasks09:06
zhonghua2yuval, ok, +109:07
yuvalIn this part of the cycle, we should work mainly on specs and reach concensus09:07
*** tommylikehu_ has joined #openstack-meeting09:07
yuval#topic Open Discussion09:08
*** openstack changes topic to "Open Discussion (Meeting topic: karbor)"09:08
zengchenyuval:got it09:08
yuvalNothing on the agenda right now, if you have anything you want to talk about - now is the time09:08
chenhuayi_yuval, network plugin waiting to be reviewd.09:08
*** luyao has quit IRC09:09
chenhuayi_it holds for more than one week.09:09
yuvalchenhuayi_: thanks for the notice09:09
*** luyao has joined #openstack-meeting09:09
*** iceyao has quit IRC09:09
yuvaleverybody, please take a look at chenhuayi's patches about the network plugin09:09
yuvalchenhuayi_: I hope I'll be able to get to it later this week or next week09:10
*** ntpttr_ has quit IRC09:10
chenhuayi_yuval, thanks.09:10
yuvalchenhuayi_: are you working on something else in the meantime?09:10
chenhuayi_yeah, start to work on S3.09:10
yuvalchenhuayi_: that's low priority for pike09:11
*** ntpttr_ has joined #openstack-meeting09:11
chenhuayi_we will surport S3 and OBS(huawei)09:12
chenhuayi_so I start with S3.09:12
yuvalchenhuayi_: we could use some help on high/med items, both in code and reviews09:12
chenying__yuval about the task Trove Protection/Protectable Plugin09:12
*** tommylikehu_ has quit IRC09:12
chenhuayi_yuval, which job may i start?09:13
chenying__yuval I don't think is in low priority for pike. Last time  you said we will not  integrate with freezer now. Trove plugin will be the only way to protect database like mysql.09:13
yuvalchenhuayi_: reviewing specs, writing docs guides, OpenStack Ansible, python 3.5 or WSGI goals09:15
*** amotoki has joined #openstack-meeting09:15
yuvalchenying__: freezer is low priority as well09:15
yuvalchenying__: low priority = we will do it, once we finish the rest09:15
chenying__yuval That may be the question: we don't have a solution to protect database mysql.09:15
yuvalchenying__: low priority != we will not do it09:15
*** tommylikehu_ has joined #openstack-meeting09:16
*** cdub has joined #openstack-meeting09:16
chenying__yuval  OK I know.09:16
*** alexchadin has quit IRC09:16
yuvalchenying__: trove is completely different than freezer on that09:16
*** LanceHaig has joined #openstack-meeting09:16
*** LanceHaig has quit IRC09:16
*** LanceHaig has joined #openstack-meeting09:16
chenying__yuval: Of course, I know it.09:17
chenying__yuval freezer is backup tool with agent. Trove is a database a service project.09:17
chenying__ database as a service project09:17
yuvalchenying__: from my point of view, both are important to karbor, but we have more important tasks until the end of pike09:18
*** ntpttr_ has quit IRC09:18
yuvalchenying__: what do you think?09:18
*** luyao has quit IRC09:19
*** ntpttr_ has joined #openstack-meeting09:19
*** luyao has joined #openstack-meeting09:19
*** amotoki has quit IRC09:19
chenying__yuval  OK I will focus this task later.09:20
yuvalchenying__: great09:20
yuvalanything else?09:20
*** yatinkarel has quit IRC09:20
*** tommylikehu_ has quit IRC09:20
chenhuayi_yuval, i can work on the ansible.09:20
yuvalchenhuayi_: great! :)09:21
*** knangia has quit IRC09:21
*** mickeys has joined #openstack-meeting09:22
*** sagara has quit IRC09:22
yuvalthank you all for attending09:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:24
openstackMeeting ended Tue Mar 28 09:24:04 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:24
openstackMinutes:        http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-03-28-09.00.html09:24
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-03-28-09.00.txt09:24
openstackLog:            http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-03-28-09.00.log.html09:24
*** chenhuayi has joined #openstack-meeting09:24
*** tommylikehu_ has joined #openstack-meeting09:25
*** tommylikehu_ has quit IRC09:25
*** tommylikehu_ has joined #openstack-meeting09:26
*** cdub has quit IRC09:26
*** tommylikehu_ has quit IRC09:26
*** mickeys has quit IRC09:26
*** chenhuayi has left #openstack-meeting09:27
*** leanderthal|afk is now known as leanderthal09:27
*** tommylikehu_ has joined #openstack-meeting09:27
*** tommylikehu_ has quit IRC09:27
*** ntpttr_ has quit IRC09:28
*** ntpttr_ has joined #openstack-meeting09:29
*** luyao has quit IRC09:29
*** luyao has joined #openstack-meeting09:30
*** yamamoto has joined #openstack-meeting09:31
*** tommylikehu_ has joined #openstack-meeting09:31
*** tommylikehu_ has quit IRC09:31
*** tommylikehu_ has joined #openstack-meeting09:32
*** yatinkarel has joined #openstack-meeting09:33
*** chenhuayi_ has quit IRC09:34
*** ntpttr_ has quit IRC09:36
*** tommylikehu_ has quit IRC09:36
*** ntpttr_ has joined #openstack-meeting09:37
*** gongysh has quit IRC09:39
*** luyao has quit IRC09:39
*** luyao has joined #openstack-meeting09:40
*** gongysh has joined #openstack-meeting09:41
*** ntpttr_ has quit IRC09:44
*** tommylikehu_ has joined #openstack-meeting09:45
*** tommylikehu_ has quit IRC09:45
*** ntpttr_ has joined #openstack-meeting09:45
*** sshnaidm|off is now known as sshnaidm09:45
*** tommylikehu_ has joined #openstack-meeting09:46
*** gongysh has quit IRC09:47
*** thorst has joined #openstack-meeting09:47
*** luyao has quit IRC09:50
*** luyao has joined #openstack-meeting09:50
*** tommylikehu_ has quit IRC09:50
*** reedip has quit IRC09:51
*** tommylikehu_ has joined #openstack-meeting09:52
*** tommylikehu_ has quit IRC09:52
*** ntpttr_ has quit IRC09:54
*** ntpttr_ has joined #openstack-meeting09:55
*** yamamoto has quit IRC09:56
*** xianghui has quit IRC09:59
*** zhangshuai has left #openstack-meeting09:59
*** ntpttr_ has quit IRC09:59
*** luyao has quit IRC10:00
*** epico has quit IRC10:00
*** luyao has joined #openstack-meeting10:00
*** ntpttr_ has joined #openstack-meeting10:01
*** yatinkarel has quit IRC10:02
*** kaisers_ has joined #openstack-meeting10:04
*** yamamoto has joined #openstack-meeting10:04
*** masayukig[m] has quit IRC10:04
*** mkrai has quit IRC10:04
*** voxelblob[m] has quit IRC10:04
*** nadya_ has quit IRC10:07
*** kaisers_ has quit IRC10:08
*** ntpttr_ has quit IRC10:09
*** shu-mutou is now known as shu-mutou-AWAY10:10
*** luyao has quit IRC10:10
*** ltomasbo is now known as ltomasbo|away10:10
*** luyao has joined #openstack-meeting10:11
*** ntpttr_ has joined #openstack-meeting10:11
*** fzdarsky has quit IRC10:14
*** voxelblob[m] has joined #openstack-meeting10:15
*** amotoki has joined #openstack-meeting10:16
*** yatinkarel has joined #openstack-meeting10:16
*** SerenaFeng has quit IRC10:17
*** Julien-zte has quit IRC10:17
*** thorst has quit IRC10:19
*** SerenaFeng has joined #openstack-meeting10:20
*** amotoki has quit IRC10:20
*** zhurong has quit IRC10:20
*** luyao has quit IRC10:20
*** luyao has joined #openstack-meeting10:21
*** zhhuabj has quit IRC10:22
*** Julien-zte has joined #openstack-meeting10:23
*** ntpttr_ has quit IRC10:24
*** ntpttr_ has joined #openstack-meeting10:25
*** dschultz has joined #openstack-meeting10:26
*** sdague has joined #openstack-meeting10:27
*** zhurong has joined #openstack-meeting10:28
*** nijaba has quit IRC10:29
*** ntpttr_ has quit IRC10:29
*** luyao has quit IRC10:31
*** nijaba has joined #openstack-meeting10:31
*** nijaba has joined #openstack-meeting10:31
*** xiaofandh12 has quit IRC10:31
*** luyao has joined #openstack-meeting10:31
*** kevinz has quit IRC10:33
*** ntpttr_ has joined #openstack-meeting10:35
*** bkopilov_ has quit IRC10:36
*** bkopilov has quit IRC10:36
*** tommylikehu_ has joined #openstack-meeting10:40
*** luyao has quit IRC10:41
*** alexchadin has joined #openstack-meeting10:43
*** alexchadin has quit IRC10:43
*** dschultz has quit IRC10:44
*** alexchadin has joined #openstack-meeting10:44
*** luyao has joined #openstack-meeting10:44
*** nadya has joined #openstack-meeting10:44
*** tommylikehu_ has quit IRC10:44
*** zhhuabj has joined #openstack-meeting10:46
*** alexchadin has quit IRC10:48
*** r-mibu has quit IRC10:50
*** r-mibu has joined #openstack-meeting10:51
*** luyao has quit IRC10:51
*** luyao has joined #openstack-meeting10:52
*** alexchadin has joined #openstack-meeting10:52
*** toscalix has quit IRC10:54
*** VW has quit IRC10:54
*** VW has joined #openstack-meeting10:54
*** alexpilotti has quit IRC10:55
*** yamamoto has quit IRC11:00
*** jkilpatr has joined #openstack-meeting11:00
*** luyao has quit IRC11:01
*** luyao has joined #openstack-meeting11:02
*** sambetts_ is now known as sambetts11:04
*** litao has quit IRC11:09
*** oomichi has quit IRC11:09
*** ntpttr_ has quit IRC11:09
*** tommylikehu_ has joined #openstack-meeting11:10
*** askb has quit IRC11:10
*** ntpttr_ has joined #openstack-meeting11:10
*** luyao has quit IRC11:12
*** luyao has joined #openstack-meeting11:12
*** oomichi has joined #openstack-meeting11:13
*** tommylikehu_ has quit IRC11:14
*** ntpttr_ has quit IRC11:15
*** kaisers_ has joined #openstack-meeting11:15
*** ntpttr_ has joined #openstack-meeting11:16
*** amotoki has joined #openstack-meeting11:17
*** thorst has joined #openstack-meeting11:20
*** kaisers_ has quit IRC11:20
*** amotoki has quit IRC11:21
*** luyao has quit IRC11:22
*** luyao has joined #openstack-meeting11:22
*** zhurong has quit IRC11:25
*** thorst has quit IRC11:25
*** yamamoto has joined #openstack-meeting11:25
*** masayukig[m] has joined #openstack-meeting11:25
*** mkrai has joined #openstack-meeting11:25
*** alexchadin has quit IRC11:30
*** tobberydberg has joined #openstack-meeting11:32
*** luyao has quit IRC11:32
*** luyao has joined #openstack-meeting11:33
*** ntpttr_ has quit IRC11:33
*** fzdarsky has joined #openstack-meeting11:35
*** erlon has joined #openstack-meeting11:38
*** ntpttr_ has joined #openstack-meeting11:39
*** rbartal_ has joined #openstack-meeting11:39
*** luyao has quit IRC11:42
*** luyao has joined #openstack-meeting11:43
*** ntpttr_ has quit IRC11:43
*** thorst has joined #openstack-meeting11:45
*** ltomasbo|away is now known as ltomasbo11:45
*** ntpttr_ has joined #openstack-meeting11:46
*** maeca1 has joined #openstack-meeting11:47
*** hashar is now known as hasharLunch11:47
*** dbecker has joined #openstack-meeting11:47
*** julim has quit IRC11:48
*** reedip has joined #openstack-meeting11:50
*** rfolco has joined #openstack-meeting11:51
*** maeca1 has quit IRC11:52
*** luyao has quit IRC11:53
*** luyao has joined #openstack-meeting11:53
*** ntpttr_ has quit IRC11:54
*** jaypipes has joined #openstack-meeting11:56
*** ntpttr_ has joined #openstack-meeting11:56
*** iceyao has joined #openstack-meeting11:58
*** SerenaFe_ has joined #openstack-meeting12:02
*** SerenaFe_ has quit IRC12:03
*** luyao has quit IRC12:03
*** luyao has joined #openstack-meeting12:03
*** SerenaFeng has quit IRC12:05
*** ntpttr_ has quit IRC12:05
*** Julien-zte has quit IRC12:05
*** ntpttr_ has joined #openstack-meeting12:06
*** SerenaFeng has joined #openstack-meeting12:09
*** ntpttr_ has quit IRC12:11
*** ntpttr_ has joined #openstack-meeting12:12
*** luyao has quit IRC12:13
*** luyao has joined #openstack-meeting12:14
*** ntpttr_ has quit IRC12:17
*** ntpttr_ has joined #openstack-meeting12:17
*** haleyb has joined #openstack-meeting12:17
*** tommylikehu_ has joined #openstack-meeting12:20
*** fzdarsky has quit IRC12:21
*** luyao has quit IRC12:23
*** luyao has joined #openstack-meeting12:24
*** bobi_wembley has joined #openstack-meeting12:24
*** dprince has joined #openstack-meeting12:24
*** tommylikehu_ has quit IRC12:25
*** ntpttr_ has quit IRC12:25
*** gcb has quit IRC12:25
*** ntpttr_ has joined #openstack-meeting12:26
*** gcb has joined #openstack-meeting12:26
*** kevinz has joined #openstack-meeting12:28
*** pnavarro has joined #openstack-meeting12:28
*** SerenaFeng has quit IRC12:28
*** xyang1 has joined #openstack-meeting12:30
*** ntpttr_ has quit IRC12:31
*** hasharLunch is now known as hashar12:32
*** ntpttr_ has joined #openstack-meeting12:32
*** luyao has quit IRC12:34
*** luyao has joined #openstack-meeting12:34
*** ntpttr_ has quit IRC12:37
*** kevinz has quit IRC12:38
*** kevinz has joined #openstack-meeting12:38
*** ntpttr_ has joined #openstack-meeting12:38
*** aysyd has joined #openstack-meeting12:42
*** caowei has quit IRC12:42
*** dschultz has joined #openstack-meeting12:42
*** rossella_s has quit IRC12:42
*** rossella_s has joined #openstack-meeting12:43
*** gongysh has joined #openstack-meeting12:43
*** luyao has quit IRC12:44
*** luyao has joined #openstack-meeting12:44
*** gouthamr has joined #openstack-meeting12:46
*** ntpttr_ has quit IRC12:47
*** ntpttr_ has joined #openstack-meeting12:48
*** VW has quit IRC12:50
*** VW has joined #openstack-meeting12:50
*** huanxuan has quit IRC12:51
*** esberglu has joined #openstack-meeting12:54
*** luyao has quit IRC12:54
*** luyao has joined #openstack-meeting12:55
*** ntpttr_ has quit IRC12:55
*** yanyanhu has joined #openstack-meeting12:55
*** LanceHaig has quit IRC12:56
*** ntpttr_ has joined #openstack-meeting12:56
*** iceyao has quit IRC12:57
*** Julien-zte has joined #openstack-meeting12:57
*** Ruijie has joined #openstack-meeting12:57
*** awaugama has joined #openstack-meeting12:58
*** dschultz has quit IRC13:00
*** john-davidge has joined #openstack-meeting13:00
Qiming#startmeeting senlin13:00
openstackMeeting started Tue Mar 28 13:00:52 2017 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: senlin)"13:00
openstackThe meeting name has been set to 'senlin'13:00
*** fzdarsky has joined #openstack-meeting13:01
Qiminghi, yanyan13:01
*** Ruijie_ has joined #openstack-meeting13:01
yanyanhuevening : )13:02
Qimingevening, Ruijie_13:02
*** Ruijie has quit IRC13:02
Ruijie_hi Qiming13:02
*** john-davidge has left #openstack-meeting13:02
Ruijie_hi yanyanhu13:02
Qimingethan texted me that he will join a bit later13:02
*** yangyapeng has joined #openstack-meeting13:02
yanyanhuhi, Ruijie_ :)13:03
*** rbudden has joined #openstack-meeting13:03
Qiminglet's get started13:03
Qiming#topic pike work items13:04
*** openstack changes topic to "pike work items (Meeting topic: senlin)"13:04
Qiming#link https://etherpad.openstack.org/p/senlin-pike-workitems13:04
*** ntpttr_ has quit IRC13:04
*** luyao has quit IRC13:04
Qimingnot sure we have progress in API13:04
*** luyao has joined #openstack-meeting13:05
QimingEthan is not here to give us an update on feature rich server13:05
*** fzdarsky has quit IRC13:05
QimingEngine improvement, CLUSTER_CHECK is still there for review13:06
QimingNode adopt13:06
QimingI'm still working on it13:06
*** ntpttr_ has joined #openstack-meeting13:06
Qiminggot some problems when implementing this at profile base layer13:07
yanyanhuthis one13:07
*** gcb has quit IRC13:07
*** dbecker has quit IRC13:07
Qimingright, that one is about adopting a heat stack13:07
Qiminga more trick thing is about doing this at profile base class13:08
Qimingwe will need a profile object to invoke do_adopt() method13:08
*** VW has quit IRC13:08
Qimingwe can use a fake node object for this method to work13:08
Qiminghowever, we still need a profile instance in order to invoke its do_adopt()13:09
yanyanhucan we define do_adopt as class method?13:09
Qimingwhen we create a profile object, we need a spec13:09
Qiminga class method cannot be used to hole the _computeclient ... properties13:09
yanyanhuoh, right13:09
Qimingor we can just do a class method, but we don't use the _computeclient ... instance property13:10
*** lakerzhou has joined #openstack-meeting13:10
Qimingstill trying to find a decent workaround13:10
yanyanhua little tricky here...13:11
QimingI hope we can work this out without introducing messy workarounds13:12
Qimingnext thing is about scaling improvement13:12
QimingRuijie_, do you have an update?13:12
Ruijie_yes Qiming, filed a bp13:12
Qimingoh, ... I didn't notice it13:13
Ruijie_had a plan, can we add the parameter to scaling_policy ?13:13
*** ntpttr_ has quit IRC13:13
*** baoli has joined #openstack-meeting13:13
Ruijie_I'd plan to add one parameter to scaling_policy and request obj to support health_check13:13
QimingI think so13:14
*** lamt has joined #openstack-meeting13:14
Qimingit is something optional13:14
*** baoli has quit IRC13:14
Ruijie_so we need to bump the version of scaling policy13:14
*** ntpttr_ has joined #openstack-meeting13:14
*** baoli has joined #openstack-meeting13:14
*** hichihara has joined #openstack-meeting13:14
Ruijie_okay Qiming, will start this work soon.13:15
Qimingit means a property that is only supported by a new version13:15
*** luyao has quit IRC13:15
Ruijie_np :)13:15
*** luyao has joined #openstack-meeting13:15
QimingWe don't have xuefeng online today?13:15
Ruijie_he said on wechat13:16
*** rbartal__ has joined #openstack-meeting13:16
Qimingso, we can skip rdo item13:16
Qimingno update on health13:16
Qimingpolicy one13:17
Qimingjust reviewed13:17
Qimingit looks fine to me13:17
Ruijie_thx Qiming.13:18
Ruijie_may need to revise this part when doing health check13:18
*** amotoki has joined #openstack-meeting13:18
Qimingthat's all for the etherpad13:18
*** eharney has joined #openstack-meeting13:18
Qiming#topic summit prep13:18
*** openstack changes topic to "summit prep (Meeting topic: senlin)"13:18
Qiminghave any of you confirmed your presence at the summit?13:19
yanyanhuQiming, will you join it?13:19
Qimingyes, I will13:19
Ruijie_may not be able to boston :(13:20
yanyanhuI guess xinhui and ethan will join the summit as well?13:20
*** ayogi has quit IRC13:20
QimingI believe xinhui is going and maybe also xuefeng13:20
*** julim has joined #openstack-meeting13:20
yanyanhuok, so you do have several presentations need to cover13:21
QimingI'm a little worried about the mistral integration talk, since they haven't shown up for quite a few weeks13:21
*** tommylikehu_ has joined #openstack-meeting13:21
yanyanhuhas xinhui communicated with them about the detail?13:21
*** tobberydberg has quit IRC13:21
yanyanhulike content preparation and presentation arrangement13:21
Qimingnot sure13:22
Qimingshe looks very very busy13:22
*** jkilpatr has quit IRC13:22
yanyanhuok, hope to have a meet after qingming festival13:22
*** jkilpatr has joined #openstack-meeting13:22
*** links has quit IRC13:22
Qimingwe don't have a lot time to prep13:22
*** amotoki has quit IRC13:23
Qimingvery curious about the mistral support13:23
yanyanhuonly a month13:23
*** ntpttr_ has quit IRC13:23
*** bobh has joined #openstack-meeting13:23
Qimingethan mentioned that their VNF case is in pretty good shape13:23
Qimingthat is really good news13:23
yanyanhugood to hear that13:23
Qiming#topic open discussions13:23
*** openstack changes topic to "open discussions (Meeting topic: senlin)"13:23
Qiminganything else you want to add?13:24
yanyanhunope from me13:24
Ruijie_em Qiming, I met a problem about the lock13:24
Ruijie_Cluster is already locked by action [u'b112a879-41ac-4581-97e1-a0d1e27c2cf1'], action e61586b8-8c0f-4b46-9eb8-e9c0673b9cf0 failed grabbing the lock13:24
Ruijie_this cluster had been locked for days :)13:24
*** ntpttr_ has joined #openstack-meeting13:24
Ruijie_engine will not clear the dead lock?13:25
Qimingit cannot13:25
Qimingunless the engine is dead13:25
*** luyao has quit IRC13:25
Qimingseems like a bug of action13:25
*** luyao has joined #openstack-meeting13:25
Qimingwhat's the status of the b112 action?13:25
*** tommylikehu_ has quit IRC13:25
Ruijie_let me check it13:26
Ruijie_its cluster_scale_in13:26
Ruijie_and the status reason is 'Action execution failed'13:26
Ruijie_is is possible that we provide API or anything to clear the dead lock13:27
Qimingem, ... not sure why that would happen13:27
Qimingif you have an idea, feel free to propose it13:27
Ruijie_okay Qiming, will lock forward to it :)13:28
Qimingthe thing is that we have to make sure the db is consistent13:28
Qiminglooks to me like a bug13:28
Qimingit would be helpful if you can help reproduce it13:29
Ruijie_sure Qiming13:29
Qiminganything else?13:29
*** ltomasbo is now known as ltomasbo|away13:29
Ruijie_no from me :)13:29
*** elynn has joined #openstack-meeting13:29
Qimingelynn, evening13:30
Qimingwe are about to end the meeting, :D13:30
*** ericyoung has joined #openstack-meeting13:30
Qimingyou can check the meeting minutes13:30
Qimingit is short13:30
Qimingdo you have anything to share?13:30
elynnI will~13:30
Qimingthank you for joining, :)13:31
Qimingwe can release the channel early today13:31
yanyanhuyea, looks so13:31
*** alexpilotti has joined #openstack-meeting13:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:31
openstackMeeting ended Tue Mar 28 13:31:59 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-03-28-13.00.html13:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-03-28-13.00.txt13:32
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-03-28-13.00.log.html13:32
yanyanhuhave a good night, everyone13:32
Ruijie_good night13:32
*** yanyanhu has quit IRC13:32
*** ltomasbo|away is now known as ltomasbo13:32
*** amotoki has joined #openstack-meeting13:34
*** tommylikehu_ has joined #openstack-meeting13:34
*** lpetrut has quit IRC13:35
*** bobh has quit IRC13:35
*** bobh has joined #openstack-meeting13:35
*** luyao has quit IRC13:35
*** luyao has joined #openstack-meeting13:36
*** lpetrut has joined #openstack-meeting13:37
*** ntpttr_ has quit IRC13:37
*** cleong has joined #openstack-meeting13:38
*** ntpttr_ has joined #openstack-meeting13:38
*** VW has joined #openstack-meeting13:39
*** nadya has quit IRC13:39
*** dimtruck is now known as zz_dimtruck13:41
*** FengShengqin has quit IRC13:43
*** FengShengqin has joined #openstack-meeting13:44
*** cloudrancher has joined #openstack-meeting13:44
*** luyao has quit IRC13:45
*** knangia has joined #openstack-meeting13:46
*** luyao has joined #openstack-meeting13:46
*** ntpttr_ has quit IRC13:47
*** iceyao has joined #openstack-meeting13:47
*** ntpttr_ has joined #openstack-meeting13:48
*** markvoelker has joined #openstack-meeting13:49
*** ihrachys has joined #openstack-meeting13:49
*** iceyao has quit IRC13:51
*** lamt has quit IRC13:52
*** hoangcx has joined #openstack-meeting13:53
*** ntpttr_ has quit IRC13:53
*** ntpttr_ has joined #openstack-meeting13:54
*** tommylikehu_ has quit IRC13:55
*** krtaylor has quit IRC13:56
*** tommylikehu_ has joined #openstack-meeting13:56
*** luyao has quit IRC13:56
*** annp has joined #openstack-meeting13:56
*** luyao has joined #openstack-meeting13:56
*** annp has quit IRC13:56
*** jlibosva has joined #openstack-meeting13:57
*** rbartal__ has quit IRC13:58
*** iyamahat has joined #openstack-meeting13:58
*** john-davidge has joined #openstack-meeting13:59
*** ntpttr_ has quit IRC13:59
*** boden has joined #openstack-meeting13:59
*** janzian has joined #openstack-meeting13:59
jlibosva#startmeeting networking14:00
openstackMeeting started Tue Mar 28 14:00:00 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
*** krtaylor has joined #openstack-meeting14:00
jlibosvaHello everybody14:00
*** electrocucaracha has joined #openstack-meeting14:00
*** elynn has left #openstack-meeting14:00
jlibosva#topic Announcements14:00
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:00
*** ntpttr_ has joined #openstack-meeting14:00
dasm14:00:00         jlibosva | #startmeeting networking14:01
dasmjlibosva: i envy your punctuality :)14:01
jlibosvaI don't remember this being announced anywhere - so native ovsdb interface has been pulled from Neutron and has its own repo now14:01
*** nkrinner is now known as nkrinner_afk14:01
*** annp_ has joined #openstack-meeting14:01
jlibosvadasm: :D I actually see it 59:59 :)14:01
jlibosva#link http://git.openstack.org/cgit/openstack/ovsdbapp14:01
*** hongbin has joined #openstack-meeting14:01
jlibosvaNeutron still uses in-tree code for interface but there is already a WIP: https://review.openstack.org/#/c/438087/14:01
*** alvarogroy has joined #openstack-meeting14:01
ihrachysjlibosva: what was the plan? do we switch right away or let it bake?14:02
*** yamahata has joined #openstack-meeting14:02
jlibosvaihrachys: I think the plan is to switch during pike, maybe pike-1. Don't remember. I should be able to find it in PTG summaries14:02
ihrachyspike1 would be great, though it's around the corner14:03
jlibosva3 weeks?14:03
*** yushiro has joined #openstack-meeting14:03
ihrachysyeah, around that time.14:03
dasmApr 10 - Apr 14 == Pike114:03
ihrachysso 2 weeks14:03
hichiharaThis is neutron stadium, right?14:03
*** yamahata has quit IRC14:04
jlibosvaI think it would make sense to switch early as currently we need to maintain 'almost' same thing in two places14:04
ihrachysotherwiseguy: are there obstacles to get the patch not WIP?14:04
dasmhichihara: yes, it is14:04
jlibosvahichihara: yes14:04
jlibosvaihrachys: I don't think he's online :)14:04
hichiharaI see14:04
*** annp has joined #openstack-meeting14:04
*** bzhao_ has joined #openstack-meeting14:04
ihrachysok nevermind14:04
jlibosva#action jlibosva to sync with otherwiseguy on the plan of ovsdbapp switch14:04
*** annp_ has quit IRC14:05
jlibosvaThis has been announced last week but for those who missed it: post mortem Ocata got merged: https://review.openstack.org/#/c/425990/14:05
jlibosvaBoston summit Forum sessions should be announced on April 10, deadline for proposals is April 2.14:06
*** luyao has quit IRC14:06
*** jmckind has joined #openstack-meeting14:06
*** luyao has joined #openstack-meeting14:06
jlibosvaAnything else to announce?14:07
ihrachyswhat's the fate of Monday meeting? I saw revert from armax: https://review.openstack.org/#/c/448886/ but it never got merged.14:07
*** LanceHaig has joined #openstack-meeting14:07
*** LanceHaig has quit IRC14:07
*** LanceHaig has joined #openstack-meeting14:07
jlibosvaihrachys: IIRC last week it was agreed to move monday14:07
dasmihrachys: http://lists.openstack.org/pipermail/openstack-dev/2017-March/114527.html14:07
dasm> Proposed revert in [1] to give time and opportunity to comment on whether14:08
dasmthe new time works for the majority of folks.14:08
dasmbut i didn't see any follow-up to this14:08
ihrachysjlibosva: and then armax said it was not properly discussed and proposed revert14:08
ihrachysthat's a bit of a mess :)14:08
*** mriedem has joined #openstack-meeting14:09
*** jmckind_ has joined #openstack-meeting14:09
*** zz_dimtruck is now known as dimtruck14:10
jlibosvaso maybe the revert patch would be the best place to discuss14:10
jlibosvaas I think lot of ppl who attend monday are not here14:10
john-davidgethe new earlier times are definitely better for me personally14:10
jlibosvaI can't attend neither so I deffer :)14:11
*** jmckind has quit IRC14:11
john-davidgewill look out for objections from others14:11
hichiharamaybe new time will affect East-Asia ;)14:11
ihrachysI don't think we will resolve it here, just wanted folks to be aware14:12
hichiharaI agree14:12
jlibosvaif there is nothing else to announce we shall move on14:12
*** yamamoto has quit IRC14:12
jlibosva#topic Blueprints14:12
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:12
jlibosva#link https://launchpad.net/neutron/+milestone/pike-114:12
reedipit does :)14:12
jlibosvaSo as mentioned, we're 2 weeks from p114:13
*** iceyao has joined #openstack-meeting14:13
*** fzdarsky has joined #openstack-meeting14:13
jlibosvaDoes anybody has anything to raise here regarding to work on a blueprint?14:14
jlibosvaany blockers or anything?14:14
*** jamesdenton has joined #openstack-meeting14:14
jlibosvaseems everything goes smooth then14:15
john-davidgeAny movement on approval of https://bugs.launchpad.net/neutron/+bug/1667329 ?14:15
openstackLaunchpad bug 1667329 in neutron "[RFE] Floating IP Subnets on Routed Provider Networks" [Undecided,Triaged]14:15
john-davidgeI was away last week14:15
*** andreas_s has quit IRC14:16
ihrachysjohn-davidge: that's a question to drivers team, but as you can see, there is nothing in LP, which means there was no discussion14:16
*** yamahata has joined #openstack-meeting14:16
*** LanceHaig has quit IRC14:16
ihrachysthe prev drivers meeting was cancelled I believe because of the meeting shift mess14:16
*** luyao has quit IRC14:16
jlibosvaand I can't find it mentioned in drivers meeting logs14:16
john-davidgeihrachys: Ok, hopefully the new drivers meeting time will stick so I can finally attend :)14:17
*** luyao has joined #openstack-meeting14:17
*** LanceHaig has joined #openstack-meeting14:17
*** LanceHaig has joined #openstack-meeting14:17
ihrachyspeople are advised to comment in the bug if they have thoughts, and ofc join the next drivers meeting.14:17
*** markvoelker has quit IRC14:17
*** rbartal has quit IRC14:17
*** rbartal_ has quit IRC14:17
jlibosvamaybe there could be a section in driver's meeting wiki to put a note/question when someone can't attend the meeting due to TZ14:18
reedipjlibosva : +114:18
ihrachysLP is the place where we track all info related to RFE bugs14:19
*** LanceHaig has quit IRC14:19
*** Ruijie_ has quit IRC14:20
jlibosvaihrachys: so if someone writes "Any news?" to LP, it'll get attention?14:20
*** Ruijie_ has joined #openstack-meeting14:20
*** LanceHaig has joined #openstack-meeting14:20
ihrachysno, RFEs get attention in order14:21
ihrachysofc you can vouch for special attention for specific bug, but that will need some personal communication :)14:21
*** trevormc has joined #openstack-meeting14:22
jlibosvalet's move on14:23
jlibosva#topic Bugs and gate failures14:23
*** openstack changes topic to "Bugs and gate failures (Meeting topic: networking)"14:23
ihrachysI was the deputy this week14:24
jlibosvaI see a spike in all jobs that happened yesterday. Given that it's in all jobs I assume some infra issue. I haven't seen any email nor bug report though.14:24
jlibosvaok, let's do the deputy first14:24
ihrachysnothing major happened, business as usual14:24
ihrachysI marked some bugs as needs-attention where I saw fit14:25
ihrachysalso cleaned up old needs-attention tagged bugs14:25
ihrachysthe resulting list is https://bugs.launchpad.net/neutron/+bugs?field.tag=needs-attention14:25
*** artom_ is now known as artom14:25
ihrachysmost of those still probably need some discussion, f.e. in https://bugs.launchpad.net/neutron/+bug/1585907 it's not clear the intended behaviour of availability API14:26
openstackLaunchpad bug 1585907 in neutron "'used_ips' field of 'net-ip-availability-list' command increased by 1 when subnet added into router,In fact, Before subnet added into the router ,'total_ips' of network does not contain 'gateway_ip'." [Medium,In progress] - Assigned to QunyingRan (ran-qunying)14:26
*** eharney has quit IRC14:26
*** tonytan4ever has joined #openstack-meeting14:26
ihrachysothers, like https://bugs.launchpad.net/neutron/+bug/1674889, affect other projects (this one is OVN) and will probably need champions from those communities14:26
openstackLaunchpad bug 1674889 in neutron "Fix get_schema_helper bug in some case" [Undecided,Incomplete] - Assigned to Dong Jun (dongj)14:26
ihrachysI don't think there is a huge reason to go through each of them; instead I will ask folks to eyeball the list and contribute to discussions where due14:26
*** luyao has quit IRC14:26
*** stanchan has quit IRC14:27
*** luyao has joined #openstack-meeting14:27
*** jaugustine has joined #openstack-meeting14:27
jlibosvaihrachys: good, thanks for report14:28
*** ntpttr_ has quit IRC14:28
jlibosvaas per gate failure I mentioned earlier - does anybody have any information of what happened? was that an infra issue?14:29
jlibosvathe curve went down, so we're good by now14:29
*** fzdarsky has quit IRC14:29
ihrachysno idea, I probably missed it while sleeping ;)14:30
*** VW_ has joined #openstack-meeting14:30
*** ntpttr_ has joined #openstack-meeting14:30
jlibosvaalright, we have a special price here which is a bug deputy role for this week14:30
jlibosvaany volunteers?14:30
*** VW_ has quit IRC14:31
*** VW_ has joined #openstack-meeting14:31
*** diablo_rojo has joined #openstack-meeting14:31
haleybi can volunteer, haven't done it for a bit14:31
ihrachys\o/ \o/ go go haleyb go go \o/ \o/14:32
jlibosvahaleyb: yay! thanks14:32
jlibosvahaleyb: now I feel like my car-selling skills improved too :)14:32
jlibosva#info haleyb is a bug deputy for week of Mar 2714:32
haleybi'll buy the car too :)14:33
*** fzdarsky has joined #openstack-meeting14:33
ihrachysjlibosva: see? he hasn't even asked the price14:33
amotokiI can be bug dupty next week14:33
reedipcongrats on the new car haleyb14:33
jlibosvaihrachys: the price was the role14:33
* haleyb assumes it's an older ferarri14:33
jlibosvaamotoki: thanks!14:33
john-davidgehaleyb: Congrats! Now follow me to the finance department...14:33
*** gcb has joined #openstack-meeting14:33
*** VW has quit IRC14:34
jlibosva#info amotoki is a bug deputy for a week of Apr 314:34
ihrachysthat was gold john-davidge14:34
john-davidgeihrachys: So are our interest rates! 1lb of gold per day.14:34
jlibosvaif there is nothing else to discuss beside haleyb14:36
jlibosva's car14:36
jlibosvawe can jump to docs14:36
jlibosva#topic Docs14:36
*** openstack changes topic to "Docs (Meeting topic: networking)"14:36
jlibosvajohn-davidge: yo14:36
john-davidgejlibosva: yo yo14:36
john-davidgejlibosva: Nothing significant from me actually, just returned from a week of PTO14:36
jlibosvaoh, so I hope you had a good time :)14:37
*** luyao has quit IRC14:37
john-davidgejlibosva: I notice lots of OSC conversion patches for review thought, so thanks all for those14:37
john-davidgejlibosva: Thank you, I did :)14:37
*** luyao has joined #openstack-meeting14:37
jlibosvajohn-davidge: so we can move on, right?14:37
john-davidgejlibosva: Yes, go ahead14:37
jlibosva#topic Transition to OSC14:37
*** openstack changes topic to "Transition to OSC (Meeting topic: networking)"14:37
jlibosvaamotoki: hi, do you have anything?14:37
amotokinothing to report. the progress is steady14:38
*** gongysh has quit IRC14:38
jlibosvaamotoki: cool, thanks14:38
jlibosvathat's fast today :D14:38
jlibosva#topic Neutron-lib14:38
*** openstack changes topic to "Neutron-lib (Meeting topic: networking)"14:38
jlibosvaboden: hi :)14:39
jlibosvaboden: any updates to neutron-lib14:39
*** LanceHaig has quit IRC14:39
bodenwe are still working through the rehoming patches for neutron core API resources and api attributes that I mentioned last week14:40
bodenhopefully we can have those in better shape by next week14:40
ihrachysboden: do we plan a release in next days? because I really want one to move forward with https://review.openstack.org/#/c/448671/ and https://review.openstack.org/#/c/446730/ (that will allow to kill translation markers in trees)14:40
ihrachysI need a release with 1st included (it's already merged) to proceed with cleanup14:40
ihrachysand then we will be able to land the 2nd and fix periodic jobs and finally release another one with no-log-translation enforced14:41
*** ntpttr_ has quit IRC14:41
*** eharney has joined #openstack-meeting14:41
bodenihrachys: it’ll be more than a few days for the patches I mentioned I think, but I don’t have any objections to a release in the meatime14:41
bodenobviously we need to make sure the periodic jobs are green, etc..14:42
ihrachysdasm: could you follow up on it? or should I post request myself?14:42
*** mlavalle has joined #openstack-meeting14:42
*** ntpttr_ has joined #openstack-meeting14:42
dasmihrachys: i'll prepare a release14:42
bodenthere are a few patches in neutron that consume lib updates that could use review14:43
dasmboden: ihrachys fyi, currently there are 3 jobs failing. i'll look into that and will report back to you14:43
jlibosvaboden: do you have links handy?14:43
bodendasm: ack14:43
boden#link https://review.openstack.org/#/q/status:open+message:%22NeutronLibImpact%22+project:openstack/neutron14:44
*** fzdarsky has quit IRC14:44
jlibosvaboden: thanks!14:44
bodenthe patches to use portbindings and providernet API defs from lib have been out there for awhile14:44
bodenplease have a looksee if you get a few min :)14:44
ihrachyswill do14:44
hichiharaboden: Why do some patches have branch name "bp/neutron-lib-networking-ovn"?14:45
*** fzdarsky has joined #openstack-meeting14:45
bodenhichihara: technically they are part of that effort14:45
*** rderose has joined #openstack-meeting14:45
bodenrehoming dependencies ovn has on neutron14:45
*** sneti_ has joined #openstack-meeting14:45
*** davidsha has joined #openstack-meeting14:45
hichiharaboden: I got it14:45
bodenI was trying to track the related patches in the BP, but if that’s just confusing it doesn’t matter to me14:45
*** egallen has joined #openstack-meeting14:46
bodenIf it gets confusing using that topic, just let me know and I’ll stop14:46
jlibosvaboden: thanks for updates, I hope more cores will jump on the api-def patches14:46
bodenI don’t have much else to add, unless others do14:47
jlibosvaanything else neutron-lib related?14:47
*** ntpttr_ has quit IRC14:47
mlavalleboden: the topic is useful. keep it up14:47
jlibosvalet's move on14:47
jlibosva#Disable IPv6 forwarding on backup HA routers14:47
*** luyao has quit IRC14:47
jlibosvathe stage is yours dalvarez :)14:47
dalvarezjlibosva, thanks!14:47
hichiharaboden: Don't mind my question14:47
*** luyao has joined #openstack-meeting14:47
dasmjlibosva: topic change?14:47
ihrachysjlibosva: topic missing14:47
jlibosvadasm: ihrachys thanks :)14:47
*** lamt has joined #openstack-meeting14:47
jlibosva#topic Disable IPv6 forwarding on backup HA routers14:48
*** openstack changes topic to "Disable IPv6 forwarding on backup HA routers (Meeting topic: networking)"14:48
jlibosva#link https://review.openstack.org/#/c/442518/14:48
ihrachysis it just a request for review?14:48
dalvarezi wanted to bring this up in order to move the patch forward14:48
*** ntpttr_ has joined #openstack-meeting14:48
*** jaugustine has quit IRC14:49
ihrachysoh ok. you could probably just ping some of us in irc and get the same. :)14:49
haleybdalvarez: do you want to mention the issue you saw yesterday wrt /proc entry, etc14:49
jlibosvashould we aim the bug to p1 then?14:49
dalvarezoh i was about to elaborate a bit further, but essentialy14:49
dalvarezwhat I want to bring up is that if we go ahead with this bug we'll make us dependent on the l3 agent for IPv6 failover14:50
dalvarezhaleyb, i actually found out that this is a bug on 3.10 kernels so procfs entry should still be there14:50
dalvarezihrachys, yeah thanks i have done it but it doesn't seem to get traction... I just wanted to know what you guys think about making us dependent on the l3-agent running for Ipv6 failover14:50
ihrachysdalvarez: oh you mean that data plane correctness will depend on l3 agent disabling forwarding on failover?14:51
dalvarezihrachys, that's it14:51
dalvarezihrachys, and actually re-enabling it when an instance transitions from backup to master14:51
*** jaugustine has joined #openstack-meeting14:52
*** jprovazn has quit IRC14:52
ihrachyswe already have some bits in the agent that work in sync with keepalived14:53
ihrachysf.e. we send gARPs for it14:53
*** ntpttr_ has quit IRC14:53
dalvarezbut the thing is that I can't think of any other solutions since, right now, ipv6 forwarding is enabled by default on namespaces and that makes it joining different multicast groups and thus responding to queries coming from the outside14:53
ihrachyshere https://github.com/openstack/neutron/blob/master/neutron/agent/l3/keepalived_state_change.py#L8714:53
ihrachysit would be either keepalived doing it, or smth on top14:53
*** Ruijie__ has joined #openstack-meeting14:53
ihrachysif keepalived doesn't, I don't see an alternative14:54
dalvarezihrachys, ack so you think it's not a big issue to depend on l3 agent running, right?14:54
haleybi think it's the kernel joining the mcast groups, right?14:54
dalvarezhaleyb, correct. that happens automatically when ipv6 forwarding is enabled14:54
dalvarezand those are left when disabled14:54
*** ntpttr_ has joined #openstack-meeting14:54
ihrachysdalvarez: I don't see a big difference architecturally between l3 agent doing it or a daemon under its control14:54
*** mickeys has joined #openstack-meeting14:55
dalvarezihrachys, the daemon is monitorized by the agent14:55
*** trinaths has joined #openstack-meeting14:55
ihrachysthe only issue I see is additional complexity in the agent, and the fact that it may not react to failover as quick as keepalived could14:55
ihrachysbut that sounds like keepalived bug/missing feature we try to work around14:56
ihrachyswhich is not news for the implementation :) [see the garp]14:56
haleybdalvarez: keepalived is moving the LLA, right?14:56
dalvarezhaleyb, it is14:56
*** Ruijie_ has quit IRC14:56
haleybthen maybe when it moves, forwarding moves?14:56
dalvarezihrachys, yes... i think the reaction time is not a big deal here since those changes shouldn't occur too often and the only drawback may be disrupting the traffic until l3 agent reacts14:56
haleybbtw, if we run out of time can move to other channel, or continue in L3 meeting thursday14:57
dalvarezhaleyb, that's something that keepalived doesn't do I guess14:57
*** VW_ has quit IRC14:57
dalvarezhaleyb, yes!14:57
dalvarezihrachys, haleyb thanks a lot guys :)14:57
*** fnaval has joined #openstack-meeting14:57
dalvarezi think we're good to go if we aim for p1 with this bug14:57
*** luyao has quit IRC14:57
jlibosvawe're almost out of time14:57
*** VW has joined #openstack-meeting14:57
jlibosvais there any other quick thing to discuss?14:57
*** luyao has joined #openstack-meeting14:58
jlibosvaor we could get 2 minutes back14:58
ihrachysjust a shout out for jlibosva chairing those meetings for us. kudos!14:58
dalvarezjlibosva, brought some beers?14:58
jlibosvaihrachys: and you're always here anyway :D14:58
jlibosvawhich is good!14:58
ihrachysthat was part of the plan of deceit14:58
mlavallejlibosva: yeah, thanks for chairing this meeting14:58
jlibosvaok, thanks all for showing up14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Tue Mar 28 14:59:15 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2017/networking.2017-03-28-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2017/networking.2017-03-28-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2017/networking.2017-03-28-14.00.log.html14:59
*** electrocucaracha has left #openstack-meeting14:59
*** hichihara has quit IRC14:59
ralonsoh#startmeeting neutron_qos15:00
openstackMeeting started Tue Mar 28 15:00:02 2017 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:00
openstackThe meeting name has been set to 'neutron_qos'15:00
*** janzian has left #openstack-meeting15:00
*** mickeys has quit IRC15:00
*** hoangcx has quit IRC15:00
*** boden has left #openstack-meeting15:00
ralonsohhi davidsha15:01
*** yushiro has left #openstack-meeting15:01
reediptuesday is the Networking Day !15:02
ralonsohyou are right!15:02
ralonsohok, let's start15:02
ralonsohI hope ajo and slaweq join us ASAP15:02
ralonsohand mlavalle15:02
ralonsoh#topic RFEs15:03
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:03
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/150562715:03
openstackLaunchpad bug 1505627 in neutron "[RFE] QoS Explicit Congestion Notification (ECN) Support" [Wishlist,New] - Assigned to Reedip (reedip-banerjee)15:03
ralonsohHi mlavalle15:03
*** ntpttr_ has quit IRC15:03
ralonsohreedip, I know15:03
*** jlibosva has left #openstack-meeting15:03
ralonsohwe need to review the spec15:03
ralonsohmy bad: I didn't have time last week15:03
ralonsohI'll review this spec tomorrow morning15:04
reedipralonsoh : no updates on this. Yeah awaiting your review but also trying to get the working Env up for yamamoto's comments15:04
reedipthanks ralonsoh15:04
ralonsohhow do you write a todo for someone?15:04
davidsha /action15:04
*** ntpttr_ has joined #openstack-meeting15:04
* ralonsoh ralonsoh to review https://review.openstack.org/#/c/445762/15:05
reedip#action ralonsoh will review https://bugs.launchpad.net/neutron/+bug/150562715:05
openstackLaunchpad bug 1505627 in neutron "[RFE] QoS Explicit Congestion Notification (ECN) Support" [Wishlist,New] - Assigned to Reedip (reedip-banerjee)15:05
ralonsohnext one15:05
reediplike this ... I am not the chair so my action wont work15:05
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/163479815:05
openstackLaunchpad bug 1634798 in neutron "[RFE] Qos DSCP to vlan priority mapping" [Wishlist,Incomplete]15:05
ralonsohnow is in incomplete status15:06
ralonsohno feedback from the submitter15:06
ralonsohI'll remove this one from the list until we have something15:06
ralonsohnext one15:06
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/165708915:06
openstackLaunchpad bug 1657089 in neutron "[RFE]Add bandwidth_limit to vip" [Undecided,New]15:06
ralonsohMy question here is: should we move this one to Octavia??15:07
ralonsohI'll ask this in the bug15:07
davidshaWould this not be something for lbaas repo?15:07
*** luyao has quit IRC15:07
ralonsohyes, that's the point15:08
reedipralonsoh : hi15:08
*** luyao has joined #openstack-meeting15:08
*** dasm has quit IRC15:08
reedipzhaobo and I am working on a spec for this :D15:08
ralonsohreedip: ok15:08
*** kylek3h_ has joined #openstack-meeting15:08
davidshakk, is there a link?15:08
reedipwait, lemme find the link15:08
ralonsohbut shouldn't be in lbaas?15:08
*** john-davidge has left #openstack-meeting15:08
reedipthe affected project would be octavia15:09
ralonsohso please change the project15:09
*** martinkopec has quit IRC15:10
*** kylek3h has quit IRC15:10
*** mriedem has quit IRC15:10
ralonsohdo you have the link?15:10
ralonsohYou can add it to the bug15:10
reedipthis is the link15:10
reedipdone !15:11
*** dasm has joined #openstack-meeting15:11
*** stanchan has joined #openstack-meeting15:11
*** tommylikehu_ has quit IRC15:11
ralonsohok, I updated the link in the bug15:11
ralonsohnext one15:11
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/159661115:11
openstackLaunchpad bug 1596611 in neutron "[RFE] Create L3 IPs with qos (rate limit)" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889)15:11
ralonsohThe spec is almost finished15:11
ralonsoh#link https://review.openstack.org/#/c/374506/15:12
ralonsohPlease take a last review to this spec15:12
*** yamamoto has joined #openstack-meeting15:13
reedipwill do ralonsoh15:13
ralonsohthe last one15:13
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/163922015:13
openstackLaunchpad bug 1639220 in neutron "[RFE] Introduce Network QoS policy "is_default" behaviour" [Low,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:13
ralonsohok, this one is beginning to worry me15:13
ralonsohthere is no progress at all15:13
*** slaweq has joined #openstack-meeting15:13
reedipreviews ?15:14
slaweqsorry for late15:14
ralonsohthe first patch is https://review.openstack.org/#/c/401254/15:14
ralonsohhi slaweq15:14
reedipok, I was hoping for reviews and slaweq is here :)15:14
ralonsohI would like a core to review it15:14
*** corey_ has joined #openstack-meeting15:14
reedipralonsoh : you could have asked it in the Weekly meeting of Neutron earlier15:14
reedipbut you can ping them now ...15:15
*** cleong has quit IRC15:15
ralonsohwith this we could continue and mlavalle could start doing the API to Nova15:15
ralonsohI know15:15
slaweqyes, and I will probably can start doing displaying it in port_info15:15
davidsharalonsoh: gary reviewed it yesterday and Ihar was discussing with you on the bug, ping them both to have a look.15:15
ralonsohWe have a lack of core support in this group15:15
mlavalleralonsoh: I am a core15:16
ralonsohI know15:16
mlavalleI will take a look in that review15:16
ralonsohand we need all core possible support15:16
ralonsohin all the RFE and bugs in progress15:16
ralonsohmlavalle: when are you planning to start https://review.openstack.org/#/c/396297/5/specs/pike/strict-minimum-bandwidth-support.rst15:17
ralonsohbullets 2 and 315:17
*** lamt has quit IRC15:17
*** cloudrancher has quit IRC15:17
ralonsohin work items15:17
mlavalleralonsoh: I was really waiting for the spec to merge15:17
*** cloudrancher has joined #openstack-meeting15:17
ralonsohyes... we need this first!15:18
ralonsohok, I'll try to fix this this week15:18
mlavalleI actually +2 the spec some days ago15:18
*** luyao has quit IRC15:18
ralonsohI know hehehe15:18
ralonsohok, no problem15:18
mlavalleralonsoh: but I can start right away15:18
ralonsohno rush15:18
ralonsohok, next topic15:18
ralonsoh#topic Bugs15:18
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:18
*** luyao has joined #openstack-meeting15:19
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/167687715:19
openstackLaunchpad bug 1676877 in neutron "Increase "TestQosPlugin.test_update_policy_rule" coverage" [Medium,New] - Assigned to Reedip (reedip-banerjee)15:19
reedipI JUST got it15:19
ralonsohare you ok with the tests??15:19
*** tobberydberg has joined #openstack-meeting15:19
ralonsohdo you still have problems?15:19
reedipYes ralonsoh , I have some issues but I will be working on it15:19
ralonsohI'll review your next patch15:20
reedipif you would like to increase the Importance to High, please be my guest :)15:20
*** lamt has joined #openstack-meeting15:20
ralonsohI don't think I'm allowed to do this....15:20
*** donghao has joined #openstack-meeting15:20
ralonsohnext one15:20
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/166713815:20
openstackLaunchpad bug 1667138 in neutron "Minumum bandwidth can be higher than maximum bandwidth limit in same QoS policy" [Medium,In progress] - Assigned to Reedip (reedip-banerjee)15:20
ralonsohthe patch is almost finished15:21
reediplinked with the earlier bug :)15:21
reedipactually the above bug was found by this patch :D15:21
mlavalleI have made reviws for that patchset15:21
ralonsohyes, you are right15:21
*** cloudrancher has quit IRC15:21
reedipyeah guys, thanks for your reviews15:21
mlavalleI can look again15:21
reedipnow I just hope to finish thios15:22
ralonsohwe will wait for it15:22
*** VW has quit IRC15:22
mlavallereedip: please give me the link and I'll review it today15:22
reedipsure mlavalle, though I would like to add the test case if is not yet up15:22
ralonsohthis is the link mlavalle15:22
reedipaah thanks ralonsoh :)15:22
mlavallereddahh ok, I'll star it in my gerrit and will wait for the test15:23
*** VW has joined #openstack-meeting15:23
*** yamamoto has quit IRC15:23
mlavallereedip: ^^^15:23
ralonsohnext one15:23
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/166390815:23
openstackLaunchpad bug 1663908 in neutron "Qos rules not cleaned by L2 agent" [Undecided,In progress] - Assigned to David Shaughnessy (david-shaughnessy)15:23
*** tobberydberg has quit IRC15:23
ralonsohI think the code is to be merged15:23
ralonsoh#link https://review.openstack.org/#/c/449710/15:23
reedipmlavalle : I thought you were saying yeaaah !! :D15:24
ralonsohtry to ping garyk15:24
davidshaIt had a +2 from Gark, I'll ping him and ask for a follow up when he has the time15:24
*** aarefiev is now known as aarefiev_afk15:24
ralonsohbecause this is almost done15:24
*** kevinz has quit IRC15:24
ralonsohnext one15:24
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/166210915:24
openstackLaunchpad bug 1662109 in neutron "tempest scenario test_qos fails intermittently" [High,Confirmed] - Assigned to Miguel Angel Ajo (mangelajo)15:24
mlavalleI will take also a look15:24
mlavalleI mean the previous one15:25
ralonsohajo: are you there?15:25
davidshamlavalle: Thank you!15:25
ralonsohthis bug should be closed because the patches (removing the tests) are merged15:25
ralonsohI'll ping ajo to do this15:25
ralonsohnext one15:26
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/165926515:26
openstackLaunchpad bug 1659265 in neutron "Network level QoS policies should apply to network:router_gateway" [Wishlist,In progress] - Assigned to Maxime (maxime-guyot-p)15:26
*** galstrom_zzz is now known as galstrom15:26
ralonsohalmost the same15:26
ralonsohthe code is ok and should be merged asap15:26
mlavalleI also reviewed that one15:26
mlavallegive me the link and I'll look again15:27
ralonsohmlavalle: I saw that! perfect15:27
*** alop has joined #openstack-meeting15:27
ralonsohis waiting for other core15:27
mlavalleah ok15:27
ralonsoh5 +1 and one +215:27
*** bobh has quit IRC15:27
ralonsohI'll ask in the neutron irc channel15:27
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/164951715:28
openstackLaunchpad bug 1649517 in neutron "qos policy attached to network, qos_policy_id is reflecting on neutron net-show , but not on the port with neutron port-show" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)15:28
*** luyao has quit IRC15:28
slaweqI didn't do anything on it15:28
ralonsohok, I know15:28
*** luyao has joined #openstack-meeting15:28
ralonsohthere are other patches with higher priority15:28
ralonsohno problem15:28
slaweqin fact I'm not sure if I should write specs for it15:29
slaweqor not?15:29
*** baoli has quit IRC15:29
ralonsohajo proposed to make a rfe15:29
ralonsohso I think so15:29
ralonsohchange the topic in the bug to RFE15:29
slaweqok, I will update15:29
ralonsohand I think you should write it15:29
ralonsohperfect and thanks!15:30
slaweq*update it15:30
reedipslaweq : I can take it up if the other bugs are done from my side, lemme know if thats ok ?15:30
ralonsohreedip: do you want one?15:30
slaweqok, just take it if You want15:30
ralonsohthe nex tone15:30
ralonsohnext one15:30
reedipralonsoh : which one ?15:30
ralonsohthe last bug15:30
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/164950315:30
openstackLaunchpad bug 1649503 in neutron "Mechanism driver can't be notified with updated network" [High,In progress] - Assigned to Hong Hui Xiao (xiaohhui)15:30
ralonsohThere was a patch submitted15:30
ralonsohone sec15:30
*** matrohon has quit IRC15:31
ralonsoh#link https://review.openstack.org/#/c/410101/15:31
ralonsoh3 months ago15:31
ralonsohand that's all15:31
*** rcernin has quit IRC15:31
*** rcernin_ has quit IRC15:31
ralonsohIf you can take this one, perfect!15:31
reedipralonsoh : ok , I will take this one !15:31
slaweqit's still waiting for kevinbenton opinion :)15:31
ralonsohwhich one?15:31
ralonsohslaweq: which one is waiting for kevin opinion?15:32
slaweqhttps://review.openstack.org/#/c/410101/  <-- this one15:32
ralonsohit's a joke, isn't it?15:33
reediphahahaha :)15:33
slaweqno, armax asked for kevinbenton opinion in comment in review for this patch15:33
ralonsohohhhhh yes!15:33
*** leanderthal is now known as leanderthal|afk15:33
ralonsohok, reedip15:34
ralonsohplease, take a look at this patch, the bug and ask us if you have a better alternative15:34
reedipok, I am asking for Kevin's suggestion on it15:34
ralonsohand also ask Kevin15:34
reedipand looking at a better solution if possible15:34
ralonsohand that's all15:34
ralonsohnext topic15:34
ralonsoh#topic Other Changes15:34
*** openstack changes topic to "Other Changes (Meeting topic: neutron_qos)"15:34
ralonsohthere is no agenda15:35
ralonsohany suggestion?15:35
slaweqif I can15:35
ralonsohof course15:35
slaweqI would ask for review for https://review.openstack.org/#/c/426946/15:35
slaweqit's already +2 from garyk and ralonsoh15:35
slaweqbut I need another core to review it :)15:35
*** alexpilotti has quit IRC15:36
ralonsohyes, I don't know why I didn't put this in the list....15:36
mlavalleslaweq: I will take a look15:36
slaweqmaybe mlavalle could do this? :)15:36
slaweqmlavalle: thx15:36
ralonsohThis patch has several +1 and one +215:36
mlavalleslaweq: it's a little big, so expect it to happen over the next 2 3 days15:36
slaweqmlavalle: that's fine for me15:36
slaweqbetter in 3 days than never :P15:36
ralonsohmlavalle: thanks a lot!15:36
mlavalleralonsoh: in general....15:37
mlavalleI see this team is doing a lot of work15:37
slaweqif this will be merged finally I will be able to move forward with ingress bw limits15:37
davidshaI have something as well...15:37
mlavalleso if you need core attention, I will be glad to prioritize this team15:37
ralonsohmlavalle: fantastic15:37
ralonsohdavidsha: please, go on15:37
davidshaAbout object versioning... I've been told how we use it is not how it's intended to be used, should we look into how other projects are using it?15:38
reedipslaweq : yes , thats a great addition... and thanks a lot mlavalle15:38
mlavalleThe only caveat is that I don't consider myself a QoS expert15:38
mlavalleso I will get up to speed over the next few weeks15:38
mlavalleI will go over the devref and the docs and the code15:38
ralonsohdavidsha: do you have examples?15:38
*** luyao has quit IRC15:38
mlavalledo we have an understanding where I am?15:38
*** luyao has joined #openstack-meeting15:39
ralonsohmlavalle: yes, of course15:39
*** lpetrut has quit IRC15:39
*** ntpttr_ has quit IRC15:39
*** alexpilotti has joined #openstack-meeting15:39
ralonsohdavidsha: ?15:39
davidsharalonsoh: not on hand, but what I've been told is it should be using the version to modify interal variables to conform to lower API versions, what we use it for now is micro versioning and throwing exception when the version is lower that a given qos rule is introduced15:40
ralonsohdavidsha: you are right15:40
ralonsohand we should change that15:40
*** ntpttr_ has joined #openstack-meeting15:40
ralonsohdavidsha: do you have time to open a bug for this?15:41
davidshaWill I file a bug and should we make it a priority for this release?15:41
ralonsoh(whishlist, please!)15:41
ralonsohno no15:41
*** lamt has quit IRC15:41
ralonsohwe don't have enough hands!!15:41
ralonsohand thanks for the heads up15:41
*** gjayavelu has joined #openstack-meeting15:41
ralonsohok, next topic15:42
ralonsoh#topic Open Discussion15:42
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:42
davidshano problem!15:42
ralonsohthe same: no agenda here15:42
ralonsohanyone has a new topic?15:42
*** zhonghua2 has quit IRC15:42
ralonsohthank you very much for attending15:43
ralonsohand see you in two weeks15:43
reedipanyone ot any topic selected in Boston ?15:43
ralonsoh(and IRC every day)15:43
reedipoh we are ending ??? Bye then :D15:43
ralonsohis anyone here going to Boston?15:43
reedipnever mind, ignore me15:43
ralonsohno no15:43
ralonsohno problem15:43
ralonsohI'm not going to Boston15:43
*** zhonghua has joined #openstack-meeting15:44
ralonsohand I did't take a look at the talks15:44
reedipneither am I  , but thought of asking out if any QoS presentation got selected ?15:44
slaweqme neither15:44
ralonsohI need to check this15:44
reedipI gave the ECN talk but they didnt select it15:44
ralonsohbetter luck next time!! once you have the code marged15:45
*** ntpttr_ has quit IRC15:45
mlavalleralonsoh: I'll be in Boston15:45
*** alexchadin has joined #openstack-meeting15:45
ralonsohLucky you!15:45
ralonsohsend pictures15:45
davidshaWe'll have to try a combined QoS talk for the next summit, we didn't submit one this time did we?15:45
ralonsohdavidsha: that's a very good idea!15:45
mlavalleralonsoh: LOL, will do15:45
*** alexpilotti has quit IRC15:46
ralonsohand we have enough topics and material to do this15:46
*** e0ne has quit IRC15:46
reedipdavidsha : thats in Australia , Mate !15:46
mlavalleyeah, taht is stating the obvious. Lots of activity here15:46
slaweqyeah but it will be in Sydney so can be quite expensive trip15:46
*** ntpttr_ has joined #openstack-meeting15:46
reedipslaweq : but a good QoS talk is worth a trip to Sydney !15:47
ralonsohcrowdfunding is the solution!!15:47
*** bobh has joined #openstack-meeting15:47
reedipralonsoh : we need a Big Crowd !15:47
ralonsohOK, thank you guys. See you in two weeks.15:47
slaweqreedip: for sure15:47
reedipc ya15:47
davidshaThanks guys, see ya!15:47
slaweqif You will need help I will be very happy to join such presentation :)15:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:48
openstackMeeting ended Tue Mar 28 15:48:04 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-03-28-15.00.html15:48
*** lakerzhou has left #openstack-meeting15:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-03-28-15.00.txt15:48
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-03-28-15.00.log.html15:48
*** mlavalle has left #openstack-meeting15:48
*** luyao has quit IRC15:48
*** luyao has joined #openstack-meeting15:49
*** cloudrancher has joined #openstack-meeting15:50
*** ltomasbo is now known as ltomasbo|away15:51
*** abalutoiu has quit IRC15:52
*** fnaval has quit IRC15:52
*** fzdarsky has quit IRC15:52
*** annp has quit IRC15:54
*** jlibosva has joined #openstack-meeting15:56
*** lamt has joined #openstack-meeting15:56
*** dschultz has joined #openstack-meeting15:56
*** dschultz has quit IRC15:57
*** ntpttr_ has quit IRC15:57
*** dschultz has joined #openstack-meeting15:57
*** VW has quit IRC15:58
*** trevormc has quit IRC15:58
*** iceyao has quit IRC15:58
*** ntpttr_ has joined #openstack-meeting15:58
*** luyao has quit IRC15:59
*** fnaval has joined #openstack-meeting15:59
*** luyao has joined #openstack-meeting15:59
*** mlavalle has joined #openstack-meeting15:59
*** davidsha has left #openstack-meeting16:00
ihrachys#startmeeting neutron_ci16:00
*** alexchadin has quit IRC16:00
openstackMeeting started Tue Mar 28 16:00:27 2017 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:00
* ihrachys waves at everyone16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
*** iceyao has joined #openstack-meeting16:00
ihrachyslet's review action items from the prev meeting16:01
ihrachysaka shame on ihrachys16:01
jlibosvaand jlibosva16:01
ihrachys"ihrachys fix e-r bot not reporting in irc channel"16:02
ihrachyshasn't happened; I gotta track that in my trello I guess16:02
ihrachys#action ihrachys fix e-r bot not reporting in irc channel16:02
ihrachys"ihrachys to fix the grafana board to include gate-tempest-dsvm-neutron-dvr-multinode-full-ubuntu-xenial-nv"16:02
ihrachysnope, hasn't happened16:02
ihrachyswill follow up on it after the meeting, it should not take much time :-x16:02
ihrachysactually, mlavalle maybe you could take that since you were to track dvr failure rate?16:03
ihrachysthat's a matter of editing grafana/neutron.yaml in project-config, not a huge task16:03
mlavalleihrachys: sure. I don't know how, but will find out16:03
ihrachysthat's a good learning opportunity then16:04
ihrachysyou can ask me for details in neutron channel16:04
ihrachysand thanks16:04
mlavallewill do16:04
ihrachys#action mlavalle to fix the grafana board to include gate-tempest-dsvm-neutron-dvr-multinode-full-ubuntu-xenial-nv16:04
mlavalleI spent time loking at this16:04
*** VW has joined #openstack-meeting16:04
*** erlon has quit IRC16:05
mlavalleall the failures I can see are due to hosts not available for the tests16:05
mlavalleor loosing connection with the hypervisor16:05
*** ntpttr_ has quit IRC16:05
mlavallethe other failures I see are due to the patchsets in the check queue16:05
mlavalleas a next step I'll be glad to talk to the infra team about this16:06
ihrachysok I see16:06
ihrachyswe may revisit that once we have data (grafana) back16:06
*** ntpttr_ has joined #openstack-meeting16:06
ihrachysnext was "jlibosva to figure out the plan for py3 gate transition and report back"16:07
jlibosvadidn't sync yet. Although it's quite important I won't be able to make a plan till next meeting as I'll be off most of the time. So I target for now+2 weeks :)16:07
*** llu has quit IRC16:07
clarkbmlavalle: yes please do ping us in -infra after the meeting if you can (I've been trying to get things under control failure wise want to make sure we aren't missing something)16:08
mlavalleclarkb: will do16:08
*** electrocucaracha has joined #openstack-meeting16:08
ihrachysok let's punt py3 for now till jlibosva is bcak16:08
*** sneti_ has quit IRC16:08
ihrachysunless someone want to take a pitch on writing a proposal for py3 coverage in gate16:09
*** luyao has quit IRC16:09
*** luyao has joined #openstack-meeting16:09
*** cloudrancher has quit IRC16:10
*** cloudrancher has joined #openstack-meeting16:11
ihrachys#topic State of the Gate16:11
*** openstack changes topic to "State of the Gate (Meeting topic: neutron_ci)"16:11
*** aasthad has joined #openstack-meeting16:11
*** ntpttr_ has quit IRC16:11
ihrachysgate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial is the only gate job that seem to show high failure rate16:12
ihrachysit's 8% right now16:12
ihrachysanyone aware of what happens there?16:12
* electrocucaracha is checking16:12
*** ntpttr_ has joined #openstack-meeting16:12
jlibosvaany chance it's still the echo from the spike before?16:12
*** mriedem has joined #openstack-meeting16:13
ihrachysI see this example: http://logs.openstack.org/17/412017/5/check/gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial/c2fab50/console.html#_2017-03-24_18_31_35_08782216:13
ihrachysjlibosva: looks rather flat from grafna16:13
*** Ruijie__ has quit IRC16:14
*** iceyao has quit IRC16:14
ihrachysI don't see too many patches merged lately, could be a one off16:14
*** alexpilotti has joined #openstack-meeting16:15
ihrachys#topic Fullstack voting progress16:15
*** openstack changes topic to "Fullstack voting progress (Meeting topic: neutron_ci)"16:16
ihrachysjlibosva: surely fullstack is still at 100% failure rate but do we make progress?16:16
ihrachysdo we have grasp of all failures there?16:16
*** iyamahat has quit IRC16:16
jlibosvare - linuxbridge - I found the latest failure: http://logs.openstack.org/71/450771/1/check/gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial/df0eaa2/console.html#_2017-03-28_14_05_34_66580916:17
jlibosvaihrachys: there is still the patch for iptables firewall16:17
*** ntpttr_ has quit IRC16:17
ihrachyshttps://review.openstack.org/441353 ?16:17
jlibosvayes, that one16:17
jlibosvastill probably a WIP16:18
ihrachysI see test_securitygroup failing with it as in http://logs.openstack.org/53/441353/8/check/gate-neutron-dsvm-fullstack-ubuntu-xenial/fe9f205/testr_results.html.gz16:18
ihrachysdoes it suggest it's not solving it?16:18
*** ntpttr_ has joined #openstack-meeting16:18
jlibosvait's probably introducing another regression16:19
jlibosvaas it solves the iptables driver but breaks iptables_hybrid16:19
ihrachyswhack a mole16:19
jlibosvathey are closely related and both use the conntrack manager16:19
*** luyao has quit IRC16:19
*** alexchadin has joined #openstack-meeting16:19
*** unicell has joined #openstack-meeting16:20
*** luyao has joined #openstack-meeting16:20
ihrachyskevinbenton: fyi seems like we need the conntrack patch in to move forward with fullstack16:20
ihrachysjlibosva: apart from this failure, anything pressing? or is it the last one?16:20
jlibosvano, other two :)16:20
jlibosvarather :(16:20
*** kaisers_ has joined #openstack-meeting16:20
jlibosvahttps://bugs.launchpad.net/neutron/+bug/1673531 - introduced recently16:20
openstackLaunchpad bug 1673531 in neutron "fullstack test_controller_timeout_does_not_break_connectivity_sigkill(GRE and l2pop,openflow-native_ovsdb-cli) failure" [Undecided,New]16:20
jlibosvaby merging tests for keeping data plane connectivity while agent is restart16:21
*** sneti_ has joined #openstack-meeting16:21
jlibosvaI also saw another failure in trunk test where patch ports between tbr- and br-int are not cleaned properly after trunk is deleted.16:21
*** yamahata has quit IRC16:21
jlibosvaI haven't investigated that one and I don't think I reported a LP bug yet16:22
ihrachysI should probably raise the test_controller_timeout_does_not_break_connectivity_sigkill one on upgrades meeting since it's directly related to upgrade scenarios16:22
*** abalutoiu has joined #openstack-meeting16:22
jlibosvaIt's unclear to me if it's fullstack or agent16:22
*** armstrong has joined #openstack-meeting16:24
ihrachyslooks like multiple agents trying to add same manager?16:24
ihrachyssince we don't isolate ovs, and we execute two hosts, maybe that's why16:24
*** alexpilotti has quit IRC16:24
*** kaisers_ has quit IRC16:24
ihrachysgotta get otherwiseguy looking at it. the bug may be in the code that is now in ovsdbapp.16:25
*** ntpttr_ has quit IRC16:25
jlibosvathat's weird16:25
jlibosvait has vsctl ovsdb_interface16:25
*** hashar has quit IRC16:25
jlibosvaI thought the manager is for native16:25
ihrachysit's chicken and egg16:25
*** pcaruana has quit IRC16:26
ihrachysyou can't do native before you register the poret16:26
ihrachysso if connection fails, we call CLI to add the manager port16:26
ihrachysand then repeat native attempt16:26
jlibosvabut there is no native whatsoever16:26
jlibosvait's a vsctl test16:26
*** ntpttr_ has joined #openstack-meeting16:26
*** brault has quit IRC16:27
ihrachysa reasonable question is then, why do we open the port16:27
jlibosvabut anyways, if it tries to create new manager and it's already there, it shouldn't influence the functionality, right?16:27
ihrachysdepending on what the agent will do with the failure.16:28
ihrachysnot sure if failure happens on this iteration, or somewhere later16:28
*** luyao has quit IRC16:29
*** luyao has joined #openstack-meeting16:30
ihrachysyeah, seems like the failure happens 30sec+ after that error16:30
ihrachysprobably not directly related16:30
jlibosvaI'm looking at the code right now and ovsdb monitor calls to native.helpers.enable_connection_uri16:31
*** bkopilov has joined #openstack-meeting16:31
*** bkopilov_ has joined #openstack-meeting16:31
*** ntpttr_ has quit IRC16:31
ihrachysyea, was actually looking for this exact patch16:32
jlibosvabut by that time the fullstack test wasn't in tree yet16:32
*** ntpttr_ has joined #openstack-meeting16:32
*** sridharg has quit IRC16:33
ihrachysoh so basically polling.py always passes cfg.CONF.OVS.ovsdb_connection16:34
ihrachysand since it has default value, it always triggers the command16:34
*** donghao has quit IRC16:35
ihrachysI think there are several issues here. one is - we don't need that at all for vsctl16:35
ihrachysanother being - multiple calls may probably race16:35
ihrachysneither are directly related to fullstack failure16:35
*** bobi_wembley has quit IRC16:35
ihrachys#action ihrachys to report bugs for fullstack race in ovs agent when calling to enable_connection_uri16:36
jlibosvawe could hack fullstack to filelock the call16:36
ihrachysI don't think that correct16:36
jlibosvato avoid races, it can't happen in real world16:36
ihrachysbecause we don't run multiple monitors?16:37
jlibosvawe don't run multiple ovs agents16:37
*** ntpttr_ has quit IRC16:37
*** nadya has joined #openstack-meeting16:38
ihrachysyeah seems like the only place we call the code path is in ovs agent16:38
*** ntpttr_ has joined #openstack-meeting16:38
ihrachysI would still prefer code level fix for that, but it would work if we lock too16:39
jlibosvathe only thing where it's used is vsphere at some dvs_neutron_agent ... http://codesearch.openstack.org/?q=get_polling_manager&i=nope&files=&repos=16:40
jlibosvabut dunno what that is16:40
*** claudiub has quit IRC16:40
*** luyao has quit IRC16:40
*** iyamahat has joined #openstack-meeting16:40
ihrachysthis code looks like ovs agent copy-pasted :)16:40
*** luyao has joined #openstack-meeting16:40
ihrachysbut it doesn't seem this code reimplements the agent16:41
ihrachysthe question would be whether the DVS agent can be used with OVS agent on the same node16:41
* mlavalle has to step out16:42
ihrachysok let's move to the next topic16:42
*** rossella_s has quit IRC16:42
ihrachys#topic Functional job state16:42
*** openstack changes topic to "Functional job state (Meeting topic: neutron_ci)"16:42
*** alvarogroy has quit IRC16:43
*** ntpttr_ has quit IRC16:43
ihrachysthere are still spikes in close past till 80%16:43
ihrachysnot sure what that was, I suspect some general gate breakage16:43
ihrachysnow it's at reasonable 10%16:43
ihrachys(note it's check queue so there may be valid breakages)16:43
ihrachysof all patches, I am aware of this fix for a func test stability: https://review.openstack.org/#/c/446991/16:44
ihrachysjlibosva: maybe you can have a look16:44
*** ntpttr_ has joined #openstack-meeting16:45
jlibosvaI will16:45
jlibosvaalso note that almost the whole previous week the rate was around 20% which is still not ideal16:45
*** Apoorva has joined #openstack-meeting16:45
*** mickeys has joined #openstack-meeting16:46
ihrachysyeah. sadly I am consumed this week by misc stuff so won't be able to have a look.16:46
ihrachys#topic Other gate failures16:48
*** openstack changes topic to "Other gate failures (Meeting topic: neutron_ci)"16:48
jlibosvawe could monitor the trend for next week and we'll see16:48
* ihrachys looks through the list to see if anything could benefit from review attention16:48
ihrachysthis patch may be interesting since late pecan switch: https://review.openstack.org/#/c/447781/16:49
ihrachysbut it needs dasanind to respin it with a test included16:49
*** ntpttr_ has quit IRC16:49
*** fzdarsky has joined #openstack-meeting16:49
ihrachysI think the bug hit tempest sometimes.16:49
*** luyao has quit IRC16:50
*** luyao has joined #openstack-meeting16:50
ihrachysany bugs worth raising?16:50
*** ntpttr_ has joined #openstack-meeting16:51
ihrachysoh there is one from tmorin with a fix here: https://review.openstack.org/#/c/450865/16:51
ihrachysI haven't checked the fix yet, so I am not sure if it's the right thing16:51
manjeets_he just enabled quotas explicitly and it worked16:51
*** lamt has quit IRC16:52
manjeets_need to check how quota ovo disrupted normal behavior16:52
ihrachysI don't think the change we landed was intended to break subprojects ;)16:52
ihrachysgotta find a fix on neutron side16:52
*** diga has quit IRC16:52
manjeets_yea that would be right fix16:52
ihrachysok let's move on16:53
ihrachys#topic Open discussion16:53
*** openstack changes topic to "Open discussion (Meeting topic: neutron_ci)"16:53
ihrachyshttps://review.openstack.org/#/c/439114/ from manjeets_ still waits for +W from infra16:53
ihrachysI see Clark already +2d it, nice16:53
manjeets_i asked clark yesterday for review16:54
manjeets_may be need to post once more on infra16:54
ihrachysyeah, thanks for following up on it16:54
ihrachysapart from that, anything CI related worth mentioning here?16:54
*** ntpttr_ has quit IRC16:55
jlibosvaI noticed that qos is skipped in api job16:55
jlibosvae.g. http://logs.openstack.org/91/446991/2/check/gate-neutron-dsvm-api-ubuntu-xenial/044a331/testr_results.html.gz16:55
manjeets_one question I was looking at functional tests16:55
manjeets_don't see much for qos16:55
manjeets_i see trunk is covered in functional but not qos16:56
*** ntpttr_ has joined #openstack-meeting16:57
ihrachysjlibosva: I think we had a skip somewhere there16:57
ihrachysapparently the driver (ovs?) doesn't support it16:57
jlibosvaI digged into it a bit and ended up that settings from local.conf are not propagated to the tempest.conf - but at this patch I see it works ... maybe it16:57
ihrachysjlibosva: oh there was another thing related16:57
jlibosvayeah, that's probably something else than what I saw - seems fixed by now16:57
*** dmacpher is now known as dmacpher-afk16:57
ihrachysthat should fix the issue with changes not propagated from hooks into tempest.conf16:58
ihrachysso now we have 2 skips only, and they seem to be legit16:58
jlibosvaihrachys: yeah, that's probably it :)16:58
*** VW_ has joined #openstack-meeting16:58
*** lamt has joined #openstack-meeting16:58
*** nadya has quit IRC16:59
jlibosvait was weird for me though as I actually saw crudini being called - anyways, it's solved. Thanks ihrachys :)16:59
ihrachysmanjeets_: there are func tests for qos too16:59
*** alexchadin has quit IRC16:59
ihrachysmanjeets_: I will give links in neutron channel since we are at top of the hour16:59
ihrachysthanks everyone and keep up!16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Tue Mar 28 16:59:47 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-03-28-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-03-28-16.00.txt16:59
manjeets_ihrachys, thanks16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-03-28-16.00.log.html16:59
jlibosvathanks! bye17:00
*** luyao has quit IRC17:00
*** luyao has joined #openstack-meeting17:01
*** VW__ has joined #openstack-meeting17:01
*** Swami has joined #openstack-meeting17:01
*** VW_ has quit IRC17:01
*** dulek_ has joined #openstack-meeting17:01
*** yamahata has joined #openstack-meeting17:01
*** VW has quit IRC17:02
*** julim has quit IRC17:02
*** abalutoiu_ has joined #openstack-meeting17:04
*** abalutoiu has quit IRC17:04
*** abalutoiu_ is now known as abalutoiu17:04
*** cloudrancher has quit IRC17:04
*** julim has joined #openstack-meeting17:04
*** electrocucaracha has left #openstack-meeting17:05
*** cloudrancher has joined #openstack-meeting17:05
*** ntpttr_ has quit IRC17:05
*** ntpttr_ has joined #openstack-meeting17:07
*** cloudrancher has quit IRC17:08
*** bzhao_ has quit IRC17:09
*** jmckind_ has quit IRC17:10
*** luyao has quit IRC17:10
*** luyao has joined #openstack-meeting17:11
*** mtanino has joined #openstack-meeting17:11
*** X-dark_ has joined #openstack-meeting17:11
*** baoli has joined #openstack-meeting17:12
*** mtanino has quit IRC17:13
*** jamesdenton has quit IRC17:13
*** X-dark has quit IRC17:13
*** X-dark_ is now known as X-dark17:13
*** sneti_ has quit IRC17:15
*** ntpttr_ has quit IRC17:15
*** ntpttr_ has joined #openstack-meeting17:17
*** baoli has quit IRC17:18
*** kaisers_ has joined #openstack-meeting17:21
*** luyao has quit IRC17:21
*** yangyape_ has joined #openstack-meeting17:21
*** luyao has joined #openstack-meeting17:21
*** ntpttr_ has quit IRC17:21
*** ntpttr_ has joined #openstack-meeting17:23
*** yangyapeng has quit IRC17:23
*** baoli has joined #openstack-meeting17:23
*** rbak has joined #openstack-meeting17:24
*** jamesdenton has joined #openstack-meeting17:25
*** kaisers_ has quit IRC17:25
*** rbak has quit IRC17:27
*** lamt has quit IRC17:27
*** ntpttr_ has quit IRC17:29
*** ntpttr_ has joined #openstack-meeting17:31
*** armstrong has quit IRC17:31
*** amotoki has quit IRC17:31
*** luyao has quit IRC17:31
*** luyao has joined #openstack-meeting17:31
*** nadya has joined #openstack-meeting17:33
*** nadya has quit IRC17:33
*** donghao has joined #openstack-meeting17:35
*** unicell has quit IRC17:35
*** sneti_ has joined #openstack-meeting17:37
*** ntpttr_ has quit IRC17:37
*** jlibosva has quit IRC17:38
*** ntpttr_ has joined #openstack-meeting17:39
*** donghao has quit IRC17:40
*** luyao has quit IRC17:41
*** luyao has joined #openstack-meeting17:42
*** ravelar has joined #openstack-meeting17:43
*** kaisers_ has joined #openstack-meeting17:44
*** gagehugo has joined #openstack-meeting17:47
*** baoli has quit IRC17:47
*** baoli has joined #openstack-meeting17:49
*** armstrong has joined #openstack-meeting17:49
*** ntpttr_ has quit IRC17:49
*** baoli has quit IRC17:50
*** ntpttr_ has joined #openstack-meeting17:51
*** sajeesh has joined #openstack-meeting17:51
*** luyao has quit IRC17:51
*** trinaths has quit IRC17:52
*** luyao has joined #openstack-meeting17:52
*** electrofelix has quit IRC17:53
*** sajeesh has quit IRC17:53
*** trinaths has joined #openstack-meeting17:53
*** trinaths has left #openstack-meeting17:54
*** spilla has joined #openstack-meeting17:56
*** pvaneck has joined #openstack-meeting17:58
*** baoli has joined #openstack-meeting17:59
lbragstad#startmeeting keystone18:00
openstackMeeting started Tue Mar 28 18:00:02 2017 UTC and is due to finish in 60 minutes.  The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: keystone)"18:00
openstackThe meeting name has been set to 'keystone'18:00
*** kbyrne has quit IRC18:00
lbragstadping agrebennikov, amakarov, annakoppad, antwash, ayoung, bknudson, breton, browne, chrisplo, cmurphy, davechen, dolphm, dstanek, edmondsw, edtubill, gagehugo, henrynash, hrybacki, jamielennox, jaugustine, jgrassler, knikolla, lamt, lbragstad, kbaikov, ktychkova, morgan, nishaYadav, nkinder, notmorgan, portdirect, raildo, ravelar, rderose, rodrigods, roxanaghe, samueldmq, SamYaple, shaleh, spilla, srwilkers,18:00
lbragstad StefanPaetowJisc, stevemar, topol, shardy, ricolin18:00
samueldmqhi all18:00
lbragstad#link https://etherpad.openstack.org/p/keystone-weekly-meeting18:00
*** Patifa has joined #openstack-meeting18:00
notmorganlbragstad: turns out my schedule conflict is starting at 11:30 not 1118:00
lbragstadnotmorgan sweet - so we get you for a half an hour!18:01
*** luyao has quit IRC18:02
*** luyao has joined #openstack-meeting18:02
*** henrynash has joined #openstack-meeting18:02
lbragstadour attendee list is getting a little large, and my client is showing me most of the folks aren't in the room18:02
lbragstadfigured its time for a roll call18:03
lbragstad#topic roll call18:03
*** openstack changes topic to "roll call (Meeting topic: keystone)"18:03
*** antwash has joined #openstack-meeting18:03
lbragstadI've already recorded those who've already raised their hands18:03
lbragstadis anyone else here that wants a pre-meeting ping who hasn't raised their hand yet?18:04
*** ntpttr_ has quit IRC18:04
lbragstadwe'll be doing this next week, too18:04
*** henrynash has left #openstack-meeting18:04
lbragstadi'll aggregate the list together in a couple weeks18:04
lbragstadalright - moving on18:05
lbragstad#topic Boston Forum Brainstorming18:05
*** openstack changes topic to "Boston Forum Brainstorming (Meeting topic: keystone)"18:05
lbragstad#link https://etherpad.openstack.org/p/BOS-Keystone-brainstorming18:05
*** jmckind has joined #openstack-meeting18:06
lbragstadI've started a list to see who is going to be at the forum for sure18:06
*** tesseract has quit IRC18:06
lbragstadand who is still tentative18:06
knikollathat's a sad attendance list18:06
dstanekknikolla: ++18:06
*** unicell has joined #openstack-meeting18:06
lbragstadis anyone else planning on being in Boston at this point?18:07
*** ntpttr_ has joined #openstack-meeting18:07
gagehugoI will most likely be there*18:07
rodrigodsi am18:07
lbragstadi understand a lot of this is based on corporate approval, i'm trying to get an early feel of who is going to be there18:07
spillaalso most likely there18:07
samueldmqlbragstad: I'll be there18:07
*** henrynash has joined #openstack-meeting18:08
lbragstadis there anything we specifically want to request sessions for?18:08
lbragstad(the whole concept of the proposal for projects bits is confusing to me, so i'm just kinda going with the flow based on what other projects are doing)18:09
*** jkilpatr has quit IRC18:09
*** jkilpatr has joined #openstack-meeting18:09
*** kbyrne has joined #openstack-meeting18:09
lbragstadit sounds like nova is only proposing 3 sessions that are pretty cross-project oriented, which makes me think we should do the same if there is anything cross project wise we need from other folks18:10
samueldmqlbragstad: are those sessions like in the PTG ?18:10
samueldmqlbragstad: or user/deployer focused ?18:10
lbragstadsamueldmq i have no idea18:10
lbragstadthis is the information i have18:11
lbragstad#link http://lists.openstack.org/pipermail/openstack-dev/2017-March/114456.html18:11
*** henrynash has quit IRC18:11
*** ntpttr_ has quit IRC18:11
rodrigodswe will always have something to discuss18:11
samueldmqlbragstad: looks like more general18:12
samueldmqtopics to discuss with ops, with users, with the community-at-large18:12
*** henrynash has joined #openstack-meeting18:12
lbragstadtrue - i'm more wondering what we need to know now so that we can propose sessions by April 1st18:12
*** luyao has quit IRC18:12
*** luyao has joined #openstack-meeting18:12
samueldmqlbragstad: cool, so we need to brainstorm there, right ?18:12
lbragstadone of the big ones that keeps popping up for me is the policy work18:12
lbragstadsamueldmq yeah18:13
*** ntpttr_ has joined #openstack-meeting18:13
dstaneklbragstad: can we just get a room for some amount of time and decide how to use it later?18:13
lbragstadi can follow up with the nova folks to see if they'd be interested in a policy session?18:13
*** nadya has joined #openstack-meeting18:13
samueldmqlbragstad: sounds good to me18:13
lbragstaddstanek it doesn't sound like that's is the flow, we have to use proposals18:13
dstanektopic1 - 1 hour, topic2 - 1 hour, etc.18:14
lbragstad#link http://lists.openstack.org/pipermail/openstack-dev/2017-March/114399.html18:14
notmorgani will definitely not be at the forum18:14
lbragstad#link http://lists.openstack.org/pipermail/user-committee/2017-March/001856.html18:14
lbragstadthat ^ note specifically requires abstracts18:15
*** neiljerram has quit IRC18:15
*** sneti_ has quit IRC18:15
lbragstad"We are looking for a good mix of project-specific, cross-project or18:15
lbragstadstrategic/whole-of-community discussions, and *sessions that emphasize18:15
lbragstadcollaboration between users and developers are most welcome!*"18:15
*** jmckind_ has joined #openstack-meeting18:17
*** ntpttr_ has quit IRC18:17
lbragstadis there anything other than policy that folks think we need a specific session for?18:17
henrynashanything keystone-horizon-ish?18:18
*** jmckind has quit IRC18:18
lbragstadlike domain-admin configuration?18:19
*** ntpttr_ has joined #openstack-meeting18:19
lbragstadand the support in horizon for it?18:19
henrynashyeah, as well as adminness in general (e.g. recognizing is_admin_project)18:19
lbragstadhenrynash would the intended direction be that developers from horizon and keystone are there describing it to operators?18:20
lbragstadhenrynash which sounds more informative, or do we want feedback?18:20
henrynashhorizon as the classic example of how to interprest these things18:20
henrynashyes, that’s probably true, howver18:21
*** lamt has joined #openstack-meeting18:21
lbragstadi can follow up with robcresswell to see what his thoughts are on a cross-project proposal18:21
lbragstad#action lbragstad to follow up with nova on a cross-project proposal for RBAC/policy18:22
lbragstad#action lbragstad to follow up with horizon on a cross-project proposal for Boston18:22
dstaneklbragstad: limits maybe?18:22
lbragstaddstanek oo18:22
*** luyao has quit IRC18:22
lbragstadyeah - that'd be another good cross-project one18:23
*** luyao has joined #openstack-meeting18:23
*** ntpttr_ has quit IRC18:23
lbragstad#action lbragstad to follow up on limits session18:23
lbragstadi assume we'll need nova, cinder, neutron, etc... in there too18:24
lbragstaddstanek good suggestion,18:24
lbragstadcan anything think of anything else?18:24
lbragstadrderose and samueldmq are doing talks on PCI, so i feel like that will be pretty well covered18:25
*** ntpttr_ has joined #openstack-meeting18:25
rderosejust samueldmq as I didn't get approval to go :(18:25
samueldmqlbragstad: ++ rderose won't be able to make it though18:25
samueldmq^  :(18:25
lbragstadrderose ah! :(18:25
lbragstadsamueldmq rderose thanks for the update18:25
dstanekwhat about a "beat up keystone" session? or some sort of feedback thing18:26
*** gyee has joined #openstack-meeting18:26
lbragstaddstanek yeah - have that documented in the etherpad, but I don't know if that is something that we need a proposal for?18:26
lbragstadi can check with mrhillsman though18:26
lbragstadsomething tells me he'd be the guy to ask18:26
lbragstad#action lbragstad to check and see if operator feedback sessions need proposals18:27
lbragstadok - sounds like i have some work to do18:27
lbragstadif anyone has additional ideas that fit the criteria, please ping me in -keystone18:28
dstaneka PTLs job is never done18:28
lbragstadsince we'll have to get things proposed this week18:28
lbragstaddstanek you're telling me18:28
samueldmqdstanek: ++18:28
lbragstadalrighty - i think we're good to move on18:28
lbragstad#topic pike specs18:28
*** openstack changes topic to "pike specs (Meeting topic: keystone)"18:28
lbragstad#info 2.5 weeks until Spec Proposal Freeze18:29
lbragstad#info 10 weeks until Spec Freeze18:29
*** ntpttr_ has quit IRC18:29
lbragstadwe have several specs up for review and several of them are pretty indepth18:29
lbragstad#topic pike specs: persistent group membership in federation18:29
*** openstack changes topic to "pike specs: persistent group membership in federation (Meeting topic: keystone)"18:29
lbragstadbreton o/18:30
lbragstadbreton you've been wanting to talk about this for a long time18:30
*** fzdarsky has quit IRC18:30
lbragstad#link https://review.openstack.org/#/c/437533/18:30
bretonso at the PTG we talked about federation18:30
bretonand that group membership was not persistent18:30
bretonwe decided that we are just going to document it18:31
*** ntpttr_ has joined #openstack-meeting18:31
lbragstadyup - iirc the idea was to provide better documentation for operators to handle that case18:31
bretonbut then at the next session i suggested to add an ability to make group membership persistent18:31
bretonby adding an option to a mapping18:31
bretonand we didn't really discuss it18:31
bretonso i wanted to get some feedback on the spec18:31
lbragstadbreton does the latest version of the spec include the details about using mapping?18:32
lbragstadabout using the mapping?*18:32
*** armstrong has quit IRC18:32
lbragstadlooks like the last upload was Feb 2318:32
bretonlbragstad: not sure what you mean18:32
bretonpersistent_membership is what i suggest there18:32
*** markvoelker has joined #openstack-meeting18:32
*** luyao has quit IRC18:32
*** luyao has joined #openstack-meeting18:33
dstanekbreton: was there already a patch submitted for the doc update?18:33
bretondstanek: no18:33
dstanekalthough i thought i was relatively clear on the nature of groups when i overhauled that doc18:33
lbragstadthis is the relevant bug report18:34
* lbragstad #link https://bugs.launchpad.net/keystone/+bug/158999318:34
openstackLaunchpad bug 1589993 in OpenStack Identity (keystone) "cannot use trusts with federated users" [High,In progress] - Assigned to Boris Bobrov (bbobrov)18:34
bretoni really want to have persistent membership because role assignments from https://docs.openstack.org/developer/keystone/federation/mapping_combinations.html#auto-provisioning _are persistent_18:34
*** cloudrancher has joined #openstack-meeting18:35
*** ntpttr_ has quit IRC18:35
knikollai thought they were not persistent, just the project was created. :/18:35
lbragstadknikolla it depends on the mapping18:35
lbragstadif the mapping specifies a project *in* the mapping, the project reference must contain a role18:36
lbragstadwhich is then assigned directly from the shadow user to the project18:36
*** ntpttr_ has joined #openstack-meeting18:37
lbragstadbreton in your approach - would the mapping change in order for keystone to make memberships persistent?18:38
bretonlbragstad: yes18:38
lbragstadit wouldn't be the default behavior?18:39
dstanek++ it has too for backward compatibility18:39
bretonit wouldn't be the default behavior18:39
dstaneki'm 'o' happy, it seems18:39
knikollalbragstad: did a quick check in the code. you are right about the role assignment.18:40
*** slaweq has quit IRC18:40
dstaneklbragstad: if you changed the default behavior then you break the expectations of existing mappings18:40
lbragstadknikolla if i wasn't right about it i would be worried since i wrote it ;)18:40
lbragstaddstanek right - that's one of my main concerns18:40
dstanek#action dstanek to check the mapping documentation to make sure the ephemeral nature of the groups is clear18:40
knikollalbragstad: i forgot that :p18:41
lbragstadi can also see how operators would have a *ton* of stuff to clean up if they started using this feature18:41
lbragstadsince groups is batch processing for users18:42
*** dulek_ has quit IRC18:42
dstaneklbragstad: it would be nice to know if people would use it rather than the default behavior18:42
*** luyao has quit IRC18:43
lbragstadprojects like heat would probably like it because it would require less things in order for them to consume federation18:43
*** luyao has joined #openstack-meeting18:43
*** ntpttr_ has quit IRC18:43
dstaneklbragstad: how so?18:43
lbragstadright now we are suggesting the operators place federated users in groups manually18:44
knikollaalso trusts18:44
lbragstadbefore they can use heat which uses trusts18:44
lbragstadwhich don't work with ephemeral group memberships18:44
*** ntpttr_ has joined #openstack-meeting18:45
dstaneklbragstad: ah i see. it also adds effort to their user provising systems that they have to consider18:45
lbragstadthey also have to clean things up manually18:46
lbragstadregardless, of if the mapping engine makes the group membership persistent or if they do18:46
dstanekyeah, anytime a group change in AD (or whatever) they need to "manually" make that change18:46
lbragstad(which is totally another thing we need to document if we haven't already)18:47
dstaneklbragstad: that's why it would be nice to just fix trusts so they don't have to do it at all18:47
lbragstadok - so random tangent question, would this be a problem if heat used something like oauth?18:47
lbragstadinstead of trusts18:47
dstaneki suggested in the case of a federated trust that we don't do a group lookup, but i'm not sure it that feasible18:47
dstaneklbragstad: i think with a little work on our side that would be entirely possible18:48
lbragstadis it a more appropriate solution?18:48
dstanek...or api keys?18:48
lbragstadi can ask the same question about api keys, too :)18:48
knikollai thought the underlying issue is that we can't know if the user still has that kind of group permissions. so everything persistent is sketchy18:49
*** ntpttr_ has quit IRC18:49
dstanekwe'd still need to understand the tolerance for the risk of a user no longer being in a group18:49
*** lamt has quit IRC18:49
lbragstadok - so oauth might not help us here?18:49
* lbragstad totally thought it might for some reason18:50
dstanekknikolla: that's exactly the problem. until they auth again we won't know18:50
dstaneklbragstad: it totally could. we just have to understand the tolerance for group membership changes18:50
lbragstadotherwise its a bunch of duplicated state across identity systems18:50
*** kbyrne has quit IRC18:50
*** ntpttr_ has joined #openstack-meeting18:51
lbragstadso if heat wanted to use oauth for federated users, what would that look like?18:51
*** kbyrne has joined #openstack-meeting18:52
dstaneklbragstad:  i assume the user would auth and give heat a token. that token would then have roles back on groups that we can no longer verify18:52
*** luyao has quit IRC18:53
*** luyao has joined #openstack-meeting18:53
lbragstadbreton thoughts?18:54
*** tobberydberg has joined #openstack-meeting18:54
knikolladoes an oauth idp have an api to check group mempership?18:55
dstanekno matter what we run into the same problem. the question is what side is best for the solution or can we just assme the change-group risk for some period of time18:55
*** ntpttr_ has quit IRC18:55
lbragstaddstanek i feel like that has to be a question answered by the deployer18:55
*** nadya has quit IRC18:55
lbragstadif we provide both in keystone18:56
rderoseI thought we talked about making concrete role assignments to solve this18:56
*** lamt has joined #openstack-meeting18:56
dstanekrderose: that doesn't solve group membership changes18:56
lbragstadrderose i think this is more related to concrete role assignments18:56
*** ntpttr_ has joined #openstack-meeting18:57
lbragstads/role assignment/group membership/18:57
rderosedstanek: right, but it's about the roles18:57
*** markvoelker has quit IRC18:57
knikollauntil create user with federated attributes is merged, users have to auth once before they can be assigned concrete roles. with the mapping that is automatic.18:57
knikollabut not concrete18:57
*** e0ne has joined #openstack-meeting18:58
knikollaif i understand correctly, breton wants an option in the mapping to make it concrete18:58
rderoseknikolla: right18:58
dstanekrderose: right, that causes the issue of the operator needing to cleanup18:58
*** galstrom is now known as galstrom_zzz18:58
lbragstadinformation sprawl across identity systems18:58
lbragstadi think we need more input from operators on this18:58
dstaneki'd really just like trusts to 'trust' the group membership (epheral groups) and make the operator responsible for kicking keystone when that changes18:59
dstaneklbragstad: ++18:59
knikollawe probably can have it as an option and let ops decide. it's their tradeoff to decide.18:59
lbragstadalright - we can take this to -keystone19:00
*** zara_the_lemur__ has joined #openstack-meeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Mar 28 19:00:25 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-03-28-18.00.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-03-28-18.00.txt19:00
*** ralonsoh has quit IRC19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-03-28-18.00.log.html19:00
*** gagehugo has left #openstack-meeting19:00
fungiinfra team, unite!19:00
* jeblair looks around for grub19:00
* zara_the_lemur__ lurks19:00
*** Shrews has joined #openstack-meeting19:00
*** sridharg has joined #openstack-meeting19:00
*** sridharg has quit IRC19:01
*** VW has joined #openstack-meeting19:01
*** spilla has left #openstack-meeting19:01
ianwgood morning19:02
mordredjeblair: I failed at lunch today - I wish you better success19:02
*** haleyb has quit IRC19:02
jeblairare they tater tots?  are they nachos?  does it matter?19:02
fungithis week we have action items assigned to and topics proposed by ianw, fungi, jeblair, mordred, greghaynes19:02
fungi(some proposed by me by proxy)19:02
*** nadya has joined #openstack-meeting19:03
fungifair amount on the agenda, so let's get started19:03
fungi#startmeeting infra19:03
openstackMeeting started Tue Mar 28 19:03:25 2017 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: infra)"19:03
openstackThe meeting name has been set to 'infra'19:03
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:03
*** luyao has quit IRC19:03
fungi#topic Announcements19:03
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:03
fungi#info Seeking volunteers to help present Infra "On-Boarding" at Forum19:03
*** VW has quit IRC19:03
*** galstrom_zzz is now known as galstrom19:04
*** luyao has joined #openstack-meeting19:04
fungiit looks like we're subdividing a slot with qa, relmgmt, requirements and stable19:04
fungi#link http://lists.openstack.org/pipermail/openstack-dev/2017-March/114121.html Project On-Boarding Rooms19:04
*** VW__ has quit IRC19:04
fungiwe could probably just brush up one of our overview presentations and run through that, then do question and answer for a few minutes after19:04
*** VW has joined #openstack-meeting19:04
*** henrynash has quit IRC19:04
fungi#link https://docs.openstack.org/infra/publications/19:04
*** corey__ has joined #openstack-meeting19:04
fungiif you're interested in pitching in, get in touch with me19:04
*** ravelar has quit IRC19:04
*** neiljerram has joined #openstack-meeting19:05
fungi#info Submit Forum topics before April 219:05
fungi#link http://lists.openstack.org/pipermail/openstack-dev/2017-March/114399.html19:05
*** arxcruz has quit IRC19:05
fungii think the main benefit we provide to the forum sessions is being there as high-profile users and operators19:05
fungibut if you have ideas for topics people should be discussing there please add them before sunday!19:05
*** ntpttr_ has quit IRC19:05
fungi#info Volunteer needed to chair Infra team meeting on April 1119:05
clarkbsorry am here got nerd sniped by pkg_resources19:06
fungii'll be at a leadership seminar with some other members of the community most of that week, and so unavailable to chair our meeting19:06
fungiget up with me if you want to fill in19:06
fungias always, feel free to hit me up with announcements you want included in future meetings19:06
fungi#topic Actions from last meeting19:06
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:06
fungi#link http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-03-21-19.03.html Minutes from last meeting19:06
fungiianw try booting a Xenial-based replacement for planet.openstack.org19:06
*** antwash has left #openstack-meeting19:06
fungidid you have a chance to give that a try?19:06
ianwyes, a couple of issues19:07
*** ntpttr_ has joined #openstack-meeting19:07
ianw#link https://review.openstack.org/45053419:07
ianw#link https://review.openstack.org/45052619:07
ianw#link https://review.openstack.org/45052919:07
ianwxenial hosts require python2 for ansible ... i presume that's not going to be controversial19:07
ianwi think a python3 only system is interesting but not a priority19:07
*** corey_ has quit IRC19:08
fungiyeah, not a problem as far as i'm concerned19:08
*** olaph has joined #openstack-meeting19:08
ianwthe other is just a fyi that for vexxhost, just ping mnaser for rdns as there's no interface for that yet19:08
*** radeks has quit IRC19:08
mordredI think mnaser is a wonderful API19:09
jeblairthat's not that much more difficult than the rax interface, tbh.19:09
fungithose changes all look nicely straightforward19:09
jeblairpossibly better19:09
ianwso yes, the host is up and on vexxhost, but not puppeted yet (450534)19:09
mordredjeblair: ++19:09
fungimnaser probably has as well-defined a public api ;)19:09
ianwyeah, i'll put in something to launch-node because it spews some very wrong info in the dns section19:09
jeblairianw: i bet you didn't even need an mnaser-specific virtualenv.19:09
fungii have no doubt about that19:09
fungithanks for putting that together ianw!19:10
ianwso, yeah, in progress, but good to sort out those little xenial issues now19:10
fungi#action fungi put forth proposal to flatten git namespaces19:10
mordredfungi: the one API call starts with "mnaser:" and everything after that is schemaless19:10
fungii haven't gotten started on that yet, though ttx put this awesome impact study together:19:10
fungi#link https://etherpad.openstack.org/p/repo-name-shortening-impact Impact of shortening repository names19:10
fungiif anybody thinks of anything which should also be on there, please add it!19:10
fungimordred: sounds a lot like glance tasks? ;)19:11
* fungi shouldn't poke fun19:11
fungi#topic Specs approval19:11
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:11
fungiwe don't seem to have anything new up this week19:12
fungi#topic Priority Efforts19:12
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:12
funginothing called out specifically here for this week, though for the zuulv3 topic i encourage people to attend the zuul-specific meeting on mondays:19:12
fungi#link http://eavesdrop.openstack.org/#Zuul_Meeting A weekly meeting to discuss Zuul development19:12
mordredfungi: :)19:12
fungi#topic Planning to upgrade lists.openstack.org to Ubuntu 14.04 LTS (fungi, jeblair)19:13
*** openstack changes topic to "Planning to upgrade lists.openstack.org to Ubuntu 14.04 LTS (fungi, jeblair) (Meeting topic: infra)"19:13
*** matrohon has joined #openstack-meeting19:13
fungi#link https://etherpad.openstack.org/p/lists.o.o-trusty-upgrade Trusty upgrade steps for lists.openstack.org19:13
fungijeblair ran through this last week and wrote up a very detailed maintenance plan there19:13
jeblairi think it's basically repeatable but we'll want to remove the old kernels beforehand to save time19:13
*** luyao has quit IRC19:13
fungii think you estimated a 90-minute outage we should announce as 3 hours?19:14
*** luyao has joined #openstack-meeting19:14
jeblairyeah, i'm comfortable with that19:14
fungi"messages bound for the list will queue..."19:14
fungiet cetera19:14
fungiyou suggested we pick a friday soon19:14
fungidoes anyone think this friday is "too soon"?19:14
jeblairit may be slightly more impactful than the 10-hour mailman outage previously, but only to people with bonkers MTAs which don't retry.19:15
*** baoli has quit IRC19:15
pabelangerfriday seems fine19:15
jeblairworks for me.19:15
*** ntpttr_ has quit IRC19:15
clarkbalso works for me19:16
*** nadya has quit IRC19:16
fungi20:00 start?19:16
jeblair2000 also works for me19:16
clarkbI'm fine with earlier if it helps people in more eastern timezones19:17
*** ntpttr_ has joined #openstack-meeting19:17
fungithat gets you after west coast lunch and i don't mind eating my dinner a couple hours early19:17
*** haleyb has joined #openstack-meeting19:17
fungi#info The Mailman listserv on lists.openstack.org will be offline for an upgrade19:18
fungier, i have a stray newline on that19:18
openstackRemoving item from minutes: #info The Mailman listserv on lists.openstack.org will be offline for an upgrade19:18
fungi#info The Mailman listserv on lists.openstack.org will be offline for an upgrade19:19
openstackRemoving item from minutes: #info The Mailman listserv on lists.openstack.org will be offline for an upgrade19:19
fungi#info The Mailman listserv on lists.openstack.org will be offline for an upgrade maintenance 20:00-23:00 UTC Friday, March 31; most messages bound for the lists there should queue and retry, so impact is likely minimal19:20
fungithere we go. anybody disagree with that?19:20
jeblairfungi: ^519:20
fungii can get an announcement worked up later today for that unless someone else wants to19:21
fungiprobably should go to the openstack-announce ml i guess?19:21
clarkband maybe even -ops and general?19:21
fungiseems questionable to send it to every ml we host19:21
clarkbdon't want to overspam but those likely represent a large subset of users19:21
fungii mean, -dev is by far the highest volume of list traffic19:22
fungiso i guess if we're going to cross-post to multiple lists we should include that one?19:22
* fungi worries he's taken a detour into the bikeshed19:23
jeblairi'm not sure we should include -announce?19:23
*** arxcruz has joined #openstack-meeting19:23
*** ntpttr_ has quit IRC19:23
*** luyao has quit IRC19:24
fungiyeah, i guess the -announce ml, by nature of being almost exclusively a read-only ml, has subscribers who are least impacted19:24
*** dirk has joined #openstack-meeting19:24
*** luyao has joined #openstack-meeting19:24
fungii was trying to figure out the best place to announce it without announcing to multiple lists19:24
jeblairthat's my thinking.  also, likely least interested.19:24
jeblair(different story if there were an impacting change)19:24
fungibut maybe i just accept the evils of cross-posting in this case19:24
clarkbI think -dev -ops and general represents the largest cross section. However sending to those 3 is not one :)19:25
*** ntpttr_ has joined #openstack-meeting19:25
fungiso -dev, -ops and the general list. anything else?19:25
jeblairpeople who care about the availability of infrastructure systems maybe ought to subscribe to -infra :)19:25
fungiyeah, that's a great point19:25
fungiokay, i'll send the announcement to those four19:26
*** henrynash has joined #openstack-meeting19:26
fungianything else we need to discuss on this topic?19:26
fungiit's an in-place upgrade, which is out of the ordinary for us, so everyone keep that in mind i guess19:26
fungi#topic Shade proposal for a new TC-recognized project team (fungi, mordred)19:28
*** openstack changes topic to "Shade proposal for a new TC-recognized project team (fungi, mordred) (Meeting topic: infra)"19:28
fungi#link https://review.openstack.org/446426 Move shade into its own top-level team19:28
fungiputting this on the agenda since it's also on the tc agenda immediately after this19:28
fungiand since my mention of it in last week's meeting seemed to take some people by surprise i wanted to make sure it's communicated so i can get at least some last minute feedback before i vote on it19:29
*** ntpttr_ has quit IRC19:29
mordredand I was afk for the surprise19:29
fungimainly curious if there are objections so i can weigh those19:29
fungiand yeah, mordred was absent last week so nobody had a chance to tell him he's crazy19:30
mordredI mean, like I don't already know taht19:30
* ttx waves from Berlin19:30
jeblairi think the current commit message lays out a reasonable case.19:30
* mordred has updated the commit message since last week - so it might be better/clearer than it was then19:30
jeblairi think that based on the expanding use of shade, in some cases it's becoming a "face" of openstack19:31
*** ntpttr_ has joined #openstack-meeting19:31
jeblairand that seems very appropriate to be an official openstack project19:31
*** henrynash has quit IRC19:31
fungiit's also going to be integral to oaktree, and i expect we don't want to be in the business of maintaining an openstack api service19:31
jeblairit's certainly evolved beyond "utility library for nodepool" :)19:31
clarkbI am really concerned that people think using software that is appropriately licensed and supported by its developers is not appropriate for usage in openstack19:31
clarkbI don't think thats shade's fault nor do I think shade can fix it, so not something to block this. But why does that perception exist and is it something we need to look at more broadly?19:32
*** lamt has quit IRC19:32
*** cloudrancher has quit IRC19:32
mordredclarkb: I do think it is something we shoud look more broadly19:32
clarkbthis will be an issue for dib too with the proposed move into infra btw19:33
clarkbso its not a one off thing we are running into19:33
mordredthere are definitely some very strange perceiption issues floating around out there19:33
*** zhonghua has quit IRC19:33
*** cloudrancher has joined #openstack-meeting19:33
greghaynesheh, I was just noticing how interesting the timing is there19:33
fungii wouldn't expect the actual set of developers on shade or requestsexceptions to actually change as a result of this19:33
mordredand figuring out how to address them over time would be beneficial19:33
*** zhonghua has joined #openstack-meeting19:33
mordredfungi: me neither19:33
jeblairclarkb: i agree with that concern.  and it's interesting that whatever might underly that concern, this does nothing to address that.  (as expected -- how could it)19:34
*** luyao has quit IRC19:34
fungithis is more of a means of calling them out as not infra-specific projects (as a class our repos get more latitude to use other licenses, in particular)19:34
clarkbthe only other thing that came up recently was a pull request was proposed to github which mordred/thingee then pushed up to shade. I think moving into openstack and applying the CLA potentially complicates that in the future19:34
jeblairthat's part of why i'm happier with this version of the commit message which takes a more positive tone and leaves out most of the vague (and unactionable) "there are problems" bits.19:34
*** luyao has joined #openstack-meeting19:34
clarkbbut thats more something to be aware of and not a deal breaker either19:35
fungithe github pr in question did include an agreement to the dco, which the board has agreed we can switch to19:35
mordredclarkb: yup. I agree with that - although for clarity for folks who might not have seen it, the PR in question was a one-word fix19:35
*** egallen has quit IRC19:35
*** iceyao has joined #openstack-meeting19:35
fungiwe just haven't had the cycles to finish things that need doing to be able to make that transition19:35
mordredfungi: ++19:35
fungion a mass scale i mean19:36
*** egallen has joined #openstack-meeting19:36
fungiby "we" i mean openstack as a whole (not just infra)19:36
* mordred really should start signed-off-by his patches ...19:36
*** egallen has left #openstack-meeting19:36
mordredalthough all of my patches are gpg signed, so one would hope that implies to people that they are signed-off by him too19:36
clarkbsigned off by doesn't ahve any real weight in our setup does it?19:37
clarkbbecause we don't assert the dco anywhere19:37
jeblairso yeah, in short, i think there is no legit organizational issue that should prompt this, and if folks think there are, we should talk about it.  but regardless of that, i think it makes good sense for the openstack project.19:37
mordrednot at the moment19:37
clarkb(it doesn't hurt either but doesn't mean anything)19:37
mordredjeblair: ++19:37
*** ntpttr_ has quit IRC19:38
fungiclarkb: it had weight for that commit, but it doesn't have weight in gerrit insofar as being enforced (yet)19:38
jeblairclarkb: https://docs.openstack.org/infra/manual/developers.html#using-signed-off-by19:38
jeblair(but the repos should really have that in a file too)19:38
fungiand yeah, we have russellb's excellent writeup there in the infra manual19:38
clarkboh neat didn't realize that was there19:38
*** ntpttr_ has joined #openstack-meeting19:39
russellbi do it for most of my patches now, habit19:39
russellbsince it's required for some other projects i'm contributing to19:39
*** lamt has joined #openstack-meeting19:40
*** iceyao has quit IRC19:40
clarkbthe only other thing I will say is that I think a lot of what is being said around this shade move is potentially at odds with what is said with the dib move19:40
*** cloudrancher has quit IRC19:40
clarkbwe may need to reconcile that19:41
jeblairclarkb, mordred: yes, if there are folks that only want to package "openstack" projects, then are they going to come back with "issues" regarding dib?19:41
*** VW has quit IRC19:41
clarkb(I'm happy for both moves to happen as proposed just we may need to clean up the messaging)19:41
jeblairme too19:41
*** nadya has joined #openstack-meeting19:41
fungiso anyway, this has a few rough edges... 1. it sets a precedent that if an openstack service wants to depend on an infra deliverable, we have to evict it; 2. tripleo depends on diskimage-builder, which we're about to talk about moving into infra; 3. shade and requestsexceptions may need to get git namespaces changed because this apparently might confuse some people when they're non-infra repos in19:41
fungithe openstack-infra git namespace19:41
jeblairsince i'm not focused on that -- i think from the pov of who uses/maintains them, they both make a lot of sense.19:42
*** nadya has quit IRC19:42
jeblairfungi: i catagorically deny #119:42
jeblairif someone has said that, we need to talk about it19:42
*** VW has joined #openstack-meeting19:42
clarkbjeblair: thats how I read the shade move commit message19:42
jeblair(i mean, that's ridiculous -- openstack depends on all sorts of things that aren't written by openstack)19:42
clarkbyes exactly :)19:43
jeblairclarkb: what sentence says that so we can remove it? :)19:43
fungii can sort of see it between the lines there if i squint19:43
*** ntpttr_ has quit IRC19:43
mordredyah - and I'm not thrilled with the concept of 3 - and would rather defer doing such a thing until such a time as we decide to flatten or remove namespaces19:43
clarkbthe middle of the first paragraph19:43
*** baoli has joined #openstack-meeting19:43
jeblair"to use adjacent to or as a part of OpenStack things" i guess?19:44
clarkb"people view it as 'separate' so maybe not appropriate for use adjavent to or as openstack things"19:44
clarkbjeblair: yes19:44
*** luyao has quit IRC19:44
greghaynesI'd be interested to know - has that happened already or is there just a fear of that potentially happening?19:44
*** luyao has joined #openstack-meeting19:45
*** ntpttr_ has joined #openstack-meeting19:45
greghaynes(people seeing it as not appropriate for use with openstack)19:45
greghaynesSince the big question seems to be whether that would also likely happen to dib19:45
fungii suspect a lot of the licensing concern could be fixed by being less team-specific in the governance documentation about licensing exceptions19:46
*** gordc has joined #openstack-meeting19:46
mordredI _think_ it may have something to do with the fact that shade is a) a library and b) interacts specifically with the openstack apis and at least for now also c) depends on python libraries that openstack depends on at different versions19:46
fungi#link https://governance.openstack.org/tc/reference/licensing.html19:46
*** e0ne has quit IRC19:46
jeblairi will once again mention that non-openstack projects don't have to adhere to our licensing requests -- in all cases, we have to look at the actual license used by a piece of software before we incorporate it.19:47
mordredc) is being handled by fixing code, but we've still had a couple of years of habit for folks19:47
fungithe spirit there seems to be that the community is allowed to use other free licenses for things which aren't runtime dependencies of "openstack the product" (however you define it), particularly software used for testing and development19:47
clarkbmordred: maybe rewrite the commit to specifically talk about how separately managed versions of common deps have created conflict and remove the talk about separate governance?19:48
clarkbbecause to me those two things are orthogonal and unrelated19:48
jeblairmordred: yeah, if that's the case, that's an entirely reasonable technical objection for folks to have, and a good technical solution is being implemented (and has no relationship with the openstack project team doing the work)19:48
jeblairclarkb and i say similar things i think19:48
clarkbjeblair: ya19:48
*** haleyb has quit IRC19:49
mordredyup. I agree re: c - however, a and b are the things that are still true and where I'm guessing people are getting themselves flummoxed19:49
fungii agree, the release management argument is far stronger than the licensing exceptions one19:49
*** e0ne has joined #openstack-meeting19:49
*** ntpttr_ has quit IRC19:49
jeblairfungi: what's the release management argument?19:49
fungi"separately managed versions of common deps"19:49
jeblairfungi: agreed19:50
fungiaka requirements tracking, stable branches, following the same release process as other openstack-the-product pieces19:50
mordredyah - as a thing that is related to openstack apis it's not currently participating in OpenStack Release Management like the other things are19:50
*** ntpttr_ has joined #openstack-meeting19:51
fungiokay, so seems like we're more or less in agreement that the spirit of the proposal makes sense, but the commit message might still be reinforcing misconceptions?19:51
fungii want to get to the dib topic too, since it's also up for tc vote today19:52
mordredfungi: ++19:52
clarkbyes for the sake of the dib move I think we awnt to avoid any of those misconceptions, particukarly if we move them at the same time19:52
fungicool, that makes a great segue19:53
fungi#topic Diskimage Builder proposal to join Infra (fungi, greghaynes)19:53
*** openstack changes topic to "Diskimage Builder proposal to join Infra (fungi, greghaynes) (Meeting topic: infra)"19:53
fungi#link https://review.openstack.org/445617 Move DIB from TripleO to Infra19:53
*** rockyg has joined #openstack-meeting19:53
fungithis one should be much less of a surprise. greghaynes has communicated it widely first in a lengthy discussion on the -dev ml and then later in the -infr aml19:54
fungiso far the only concern i've seen raised is that if the misconception about infra deliverables being unsuitable as openstack dependencies persists then we've got an issue19:54
*** luyao has quit IRC19:54
*** luyao has joined #openstack-meeting19:55
greghaynesYep, I've also made #link https://etherpad.openstack.org/p/dib-infra-move-deets to gather some finer grained details19:55
*** ntpttr_ has quit IRC19:55
*** alop has quit IRC19:55
fungii also just want to make absolutely 100% sure that the current dib devs are entirely disinterested in having their own separate project team. as a tc member i'd also happily support that move19:55
EmilienM(in same position as fungi fwiw)19:55
ianwpersonally i see that as a lot of overhead with no benefits i can see19:56
greghaynesRight, I've been trying to find anyone who might have a strong desire for that and was unable to19:56
greghaynesFor the same reasons as ianw says19:56
fungibut i certainly agree that the work on dib is pretty closely aligned with other things in infra and we have a fair amount of overlap on contributors, so i don't object to the current proposal and i haven't heard anyone else object19:56
*** ntpttr_ has joined #openstack-meeting19:57
fungii mainly wanted to give an opportunity for last-minute objections from the infra team19:57
* mordred welcomes our existing dib friends in remaining our dib friends19:58
fungiand seems like i'm hearing none. we can move to open discussion for the last couple minutes19:58
ianwjust join #openstack-dib as sometimes things come up in there19:58
EmilienM(indeed, we're going to vote it during the TC meeting)19:58
fungi#topic Open discussion19:58
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:58
clarkbas a heads up I think I got one of our barcelona demo clouds to donate resources19:59
clarkbonce people get back from vacation we should be able to make that concrete with proper accounts and everything (late this week, early next)19:59
pabelangerI'm looking for help with directory hashing for rubygems-mirror. I might be pinging some people19:59
cmurphyI pushed up https://review.openstack.org/#/c/450029/ to stop installing root users on nodepool nodes and so far ianw has raised hesitation, does anyone else want to discuss it?19:59
*** gjayavelu has left #openstack-meeting19:59
clarkbcmurphy: maybe we can take that over to -infra as we are running out of time?20:00
EmilienMI'm still waiting for feedback on infracloud/ocata patch https://review.openstack.org/#/c/436503/20:00
cmurphyclarkb: sure20:00
fungiokay, thanks everyone--time for teh tc meeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Mar 28 20:00:25 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-03-28-19.03.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-03-28-19.03.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-03-28-19.03.log.html20:00
*** Shrews has left #openstack-meeting20:00
EmilienMdims, dtroyer, fungi, johnthetubaguy, mordred, mtreinish, sdague, stevemar, thingee: ping20:00
* fungi changes hats and sticks around20:00
EmilienMexcused absence: dhellmann, ttx, flaper8720:00
ttxI'm here actually20:00
EmilienMoh nooooooes20:00
ttxbut probably shouldn't20:01
EmilienMI was waiting for this time in my life20:01
ttxEmilienM: so I'll let you drive20:01
EmilienMttx: floor is yours20:01
dimsgo have fun ttx !20:01
ttxno no20:01
EmilienMttx: are you here for the whole meeting?20:01
mordredttx: I apologize - white trash fast food is not currently in operation! :(20:01
thingeettx: have a cocktail and relax20:01
EmilienM#startmeeting tc20:01
openstackMeeting started Tue Mar 28 20:01:36 2017 UTC and is due to finish in 60 minutes.  The chair is EmilienM. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
openstackThe meeting name has been set to 'tc'20:01
ttxthingee: they all decide to go to bed early20:01
EmilienMAgenda at:20:01
EmilienM#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:01
EmilienMlet's start with the first topic:20:02
EmilienM#topic Update diversity tags20:02
*** openstack changes topic to "Update diversity tags (Meeting topic: tc)"20:02
EmilienM#link https://review.openstack.org/44866720:02
EmilienMsounds like we had a negative feedback a few hours ago from Michael20:02
johnsomI am here to answer questions20:02
johnsomGive comments if asked for...20:02
thingeejohnsom: do you disagree with the script we use to produce these results?20:02
* edleafe hopes no one sees him wandering in late20:03
ttxjohnsom: the ;etric at fault is core reviezs20:03
ttxoops us keyboard20:03
ttxthe metric at fault is core reviews20:03
johnsomI think it is a bit on the harsh side and penalizes a project for having the PTL at an active company.20:03
johnthetubaguyjohnsom: did you see the definition here: https://governance.openstack.org/tc/reference/tags/team_diverse-affiliation.html20:03
johnsomRight, percent of core reviews from one company.20:03
johnthetubaguyits two companies being more than 80% of something I thought?20:04
johnsomI dug into the script when I heard about this.20:04
*** haleyb has joined #openstack-meeting20:04
ttxit's not single-vendor, but it's not diverse either20:04
ttxjohnthetubaguy: single company core review > 50%20:04
*** Apoorva has quit IRC20:04
johnthetubaguyright, diverse is a high-sh bar, and for a good reason20:04
johnsomIt was only the core metric we were over.20:04
johnthetubaguyttx: ah, OK20:05
ttxjohnsom: yes true, and not by far20:05
*** luyao has quit IRC20:05
*** Apoorva has joined #openstack-meeting20:05
*** luyao has joined #openstack-meeting20:05
johnsomRight.  We of course have been impacted my the musical chairs with developers.20:05
*** ntpttr_ has quit IRC20:05
* rockyg spies a slinking edleafe20:05
sdaguejohnsom: which also means it's probably not hard to get back over that line as long as it's a team focus20:05
fungiif the script isn't measuring what we intended, then i agree we should hold off updating tag application and fix that. if it's just that we're focusing on the wrong metrics entirely that's a separate discussion we should handle through a different proposal which shouldn't block the current one20:05
ttxthe issue is, I don't think we can make the rule subjective20:05
* bswartz invokes Goodhart's Law20:06
EmilienMjohnsom: tbh, I don't think it's a terrible news to loose this tag. you're close to have it again anyway20:06
thingeefungi: ++20:06
johnsomFor those curious in the actual numbers.  (which might be nice on the commit message).20:06
EmilienMjohnsom: the most important is the health of your project and I haven't seen negative signs so far20:06
johnsomThese don't get automatically re-added right?20:06
EmilienMfungi: yes, we can wait for sure.20:06
thingeejohnsom: no20:06
EmilienMjohnsom: we have a bot called ttx  :D20:07
*** ntpttr_ has joined #openstack-meeting20:07
mordredhe's a good little bot20:07
ttxjohnsom: they get readded whenever someone runs the script again20:07
thingeecan confirm he's a robot20:07
fungibut they do get re-added without necessarily needing to request that it happen20:07
ttxI try to do that every 2months-ish20:07
sdaguettx: it would be nice if the numbers for the projects were in the commit message20:07
dimsi was just going to ask that ttx :)20:07
*** tobberydberg has quit IRC20:07
johnsomThis just seems like another thing that makes it hard for small teams to participate and grow momentum.20:07
sdaguejust to make it concrete20:07
*** tobberydberg has joined #openstack-meeting20:07
EmilienMttx: we could have a periodic job in governance (so we stop doing it manually?)20:07
thingeesdague: ++20:07
ttxsdague: aren't they ? you mean all the numbers ?20:08
johnthetubaguythe 56 and 92 are there I guess20:08
sdaguettx: yeh20:08
mordredjohnsom: well - in the past we've also talked about hopefully being able to use some of these to cajole folks in to contributing resources ...20:08
johnthetubaguyah, all20:08
ttxsdague: ok, will copy more next time20:08
sdaguettx: all of them, just as baseline20:08
johnsommordred Understand, it's a fine line I think we dance20:08
mordredjohnsom: other companies may not realize that it would be good to get more humans on a thing - I _know_ everyone is always interested in the topic of lbaas20:08
EmilienMso do we agree to postpone it a little more until we discuss more about the script?20:08
mordredjohnsom: totally agree20:09
mordredEmilienM: I'm good with postponing a bit20:09
ttxsure no urgency20:09
zanebone problem with a hard threshold is that teams right on the threshold for one of the metrics will tend to bounce in and out20:09
sdaguecan we set a time table though?20:09
dtroyerThis is an indicator, and it is doing its job in raising awareness in places not otherwise aware of the situation.20:09
zanebsome hysteresis might help here20:09
fungizaneb: sort of a hysteresis?20:09
sdaguezaneb: yeh, that's going to be true anywhere20:09
dtroyerzaneb: one reason for not running it weekly20:10
EmilienM#action postpone https://review.openstack.org/#/c/448667 and start discussion on how the script computes the diversity metrics20:10
* mordred can provide hysteresis just by running around screaming, if it would help20:10
johnsomSmall teams, the cores are likely concentrated at a few organizations (we have three).20:10
sdagueEmilienM: can we give it a date where we're going to move forward regardless20:10
zanebyeah, so once a team has the tag, maybe give them a bit more leeway before losing it again20:10
fungimordred: i think you meant hysteria?20:10
johnsomI will noodle and maybe propose something20:10
mordredjohnsom: ++20:10
ttxjohnsom: well it's sure it's harder for small teams to be diverse20:10
EmilienMsdague: in 2 weeks max?20:11
ttxdoesn't mean the tag definition is inaccurate20:11
sdagueEmilienM: ++20:11
sdaguettx: ++20:11
openstackRemoving item from minutes: #action postpone https://review.openstack.org/#/c/448667 and start discussion on how the script computes the diversity metrics20:11
johnthetubaguyttx: ++20:11
EmilienM#action postpone https://review.openstack.org/#/c/448667 and start discussion on how the script computes the diversity metrics - take decision on the patch in the next 2 weeks20:11
*** ntpttr_ has quit IRC20:11
openstackRemoving item from minutes: #action postpone https://review.openstack.org/#/c/448667 and start discussion on how the script computes the diversity metrics - take decision on the patch in the next 2 weeks20:11
EmilienM#action postpone https://review.openstack.org/#/c/44866720:11
sdagueright, part of the reason for this tag to exist it for consumers to understand how robust the contributor field is behind a project, so that if one or more orgs close shop, what is the impact on the project20:12
EmilienM#action start discussion about how we compute diversity metrics20:12
ttxI think "diverse-affiliation" is a high bar and hard to reach. Was honestly surprised to see Octavia had it in the first place20:12
EmilienM#action take decision for https://review.openstack.org/#/c/448667 in the next 2 weeks20:12
johnthetubaguysdague: +1 for keeping that in mind here20:12
sdaguebecause, we've totally had organizations actually close up shop20:12
dims++ EmilienM20:12
sdaguethat's not a theoretical20:12
*** tobberydberg has quit IRC20:12
EmilienMsdague: yes, agreed20:12
johnthetubaguyalthough small teams are had to keep the diverse tag, they are also more likely to be affected by one company walking away20:12
johnsomWe were the #1 neutron sub-project based on the April 2016 survey....20:12
sdaguejohnthetubaguy: ++20:12
sdaguejohnsom: which is fine, that's a different axis20:13
*** ntpttr_ has joined #openstack-meeting20:13
EmilienMjohnsom: again, you shouldn't take this one as a bad news tbh20:13
ttxwe could have some grace period20:13
EmilienMjohnsom: I haven't seen any sigh of octavia being in bad shape20:13
mordredor sigh20:14
johnsomIt is perceived as a path to getting booted from an official project.....20:14
sdaguejohnsom: why?20:14
mordredah - well, we should work on changing that perception20:14
EmilienMjohnsom: not at all20:14
sdagueyeh, definitely not that20:14
ttxjohnsom: fwiw most teams aren't diverse20:14
mordredthat is definitely not the _intent_20:14
sdaguemordred: ++20:14
johnsomI think it is confused with single vendor and it is part of the discussion to become a project20:14
mordredand, for the love of all that is good and holy, I think the _last_ thing any of us want to do is boot LBaaS out20:15
EmilienMwe need to send a message that this tag doesn't make you a first class citizen20:15
EmilienMit's just a number20:15
*** VW_ has joined #openstack-meeting20:15
*** luyao has quit IRC20:15
EmilienMshould we move on?20:15
*** luyao has joined #openstack-meeting20:15
mordredif anything it should be a message to member companies that maybe they need to allocate a human to work on a thing if they care about it20:15
EmilienM#topic Various repository moves20:15
*** openstack changes topic to "Various repository moves (Meeting topic: tc)"20:15
EmilienM* Move DIB from TripleO to Infra20:15
EmilienM#link https://review.openstack.org/44561720:15
EmilienMI didn't vote because I'm the author20:16
EmilienMbut with my TC hat, +1 :)20:16
*** VW_ has quit IRC20:16
EmilienM(and TripleO PTL hat)20:16
greghaynesI am guessing this is just a topic mistype but the intent is for us to not remove the repository fwiw20:16
dimswas there some discussion on this in the infra meeting earlier?20:16
fungiyeah, we just re-discussed it in the infra meeting moments ago, so i'm good20:16
sdaguethese should be pretty rote right? just let ttx slam them all in20:16
EmilienMso far we have zero negative feedback until now20:16
greghaynesnot move20:16
*** jkilpatr has quit IRC20:16
*** VW_ has joined #openstack-meeting20:16
*** rbak has joined #openstack-meeting20:17
ttxgood if both ptls are ok20:17
EmilienMttx: ship it please20:17
EmilienM* Remove Gnocchi from Telemetry20:17
EmilienM#link https://review.openstack.org/44743820:17
*** rbak has quit IRC20:17
EmilienMgordc: any last word? :)20:17
EmilienM(jd is offline)20:17
dimsgordc : are you moving out of openstack ci infra as well?20:17
*** rbak has joined #openstack-meeting20:17
EmilienMdims: AFIK yes20:18
EmilienMbut I might have missed something20:18
thingeeaccording to the email, that was eventually happening20:18
*** jkilpatr has joined #openstack-meeting20:18
fungii read it as "might eventuaklly be in the cards"20:18
dimsthanks EmilienM thingee - just curious20:18
*** VW has quit IRC20:18
fungiit didn't sound like there were any immediate plans to relocate the repo20:18
thingee"As a second step, the project will likely move out of the OpenStack infrastructure in the future."20:19
*** ntpttr_ has quit IRC20:19
fungiyeah, so no set timeline for that20:19
EmilienMttx: ship it please, no blocker afik20:19
johnthetubaguyjust for clarity, we are not requiring them to stop using infra I assume?20:20
ttxI guess the only auestion is, are we happy to see it go, or should we fork it in openstack.20:20
clarkbno they would essentially be "stackforge' at that point20:20
ttxI think I'm in the first camp20:20
mordredjohnthetubaguy: that was for you - we are certainly not requiring hem to stop20:20
dimsy happy to let go20:20
mordredttx: I am too - I do not see any need to20:20
fungifor what it's worth, we did discuss a few weeks ago in boston that we need to take action to get rid of the perception that openstack is one monolithic thing you have to run all of20:20
EmilienMwhy forking it?20:20
johnthetubaguymordred: clarkb: yeah, that was my hope, just wanted to make that clear20:20
mtreinishfungi: yeah, that's something I'd like to figure out how to fix20:21
*** ntpttr_ has joined #openstack-meeting20:21
fungiso the concern raised in that review will one day, i hope, no longer be20:21
ttxEmilienM: well, if there were some people in openstack wanting to continue it... we'd be in a bind20:21
ttxand would probably have to fork it20:21
*** annegentle has joined #openstack-meeting20:21
johnthetubaguyfungi: mtreinish: +1 talking more about constellations as sets of things that run together for particular use cases should help some, but thats a different discussion20:22
EmilienMttx: AFICT, "people in openstack" who worked / work on Gnocchi are part of Gnocchi team and are happy with this move20:22
ttx(that's due to the "leave infra" part)20:22
mordredyah, just because a team wants to go away doesn't necessarily mean OpenStack as a whole feels the same way - imagine if the nova cores decided they wanted to take nova elsewhere20:22
EmilienMttx: I never had the impression (unless I missed something) that someone wasn't happy and would eventually fork it20:22
ttxEmilienM: indeed, which is why I said, no problem in this case20:22
mordredI'm pretty sure we would _not_ just delete nova from infra and wash our hands of it - but in this case, I think there is no need for such a behavior20:22
mtreinishjohnthetubaguy: this is somewhat independent of that I think. It's more a general perception that if it's a git repo in openstack/ you can't use it outside of openstack20:23
ttxbut when am official deliverable leaves openstack infrastructure, I think it's good to check :)20:23
mordredtheir reasons for making the change all make sense20:23
mordredttx: ++20:23
EmilienMship it!20:23
mtreinishI'm not sure constellations will help with that (but they might, I really don't know)20:23
mordredmtreinish: yah - we should also work on that perception20:23
mordredmtreinish: I  mean, I do not think that I can't run statsd just because I don't work on etsy :)20:24
gordcEmilienM: sorry, you still need me?20:24
EmilienMgordc: too late :)20:24
mordredgordc: nope! you're all set20:24
EmilienM* Move castellan under Oslo governance20:24
fungijohnthetubaguy: more the thing we discussed where we should make it possible to run services independent of one another20:24
EmilienM#link https://review.openstack.org/44913720:24
johnthetubaguymtreinish: true, that is maybe wider20:24
gordcdims: i think eventually yes. this is mainly for formality right now.20:24
dimsack gordc20:24
johnthetubaguyfungi: so thats possible today, and people do it, I guess its just not talked about a whole bunch20:24
fungijohnthetubaguy: right20:24
ttxdims: looks like that one could use last-minute additions20:25
johnthetubaguyfungi: I was really suggesting we make those constellations (of maybe one), but that might be overkil20:25
*** ntpttr_ has quit IRC20:25
*** luyao has quit IRC20:25
EmilienMgcb: any thoughts you want to share?20:25
ttxdims: to please gcb20:25
*** luyao has joined #openstack-meeting20:26
EmilienMit's worth mentioning this spec in progress: https://blueprints.launchpad.net/oslo.utils/+spec/adopt-castellan20:26
dimsack ttx : will rev the patch and get ok from gcb20:26
*** e0ne has quit IRC20:26
ttxok, and with the TC approval I'll merge the result20:27
*** ntpttr_ has joined #openstack-meeting20:27
ttxwhenever it has gcb +!20:27
EmilienMttx: he already +1 fwiw20:27
dims@action Dims to follow up with Oslo PTL on Castellan review20:27
dims#action Dims to follow up with Oslo PTL on Castellan review20:27
ttxyeah, but I think it's better to fix the patch and approve it20:27
dimsagree ttx20:28
EmilienMmoving on20:28
EmilienM#topic Move shade into its own top-level team20:28
EmilienM#link https://review.openstack.org/44642620:28
*** openstack changes topic to "Move shade into its own top-level team (Meeting topic: tc)"20:28
EmilienMmordred: o/20:28
fungialso just talked through this one in the infra meeting20:28
mordredthis one has had an update to the commit message since last you voted on it20:28
mordredbased on feedback in the infra meeting20:28
EmilienMmordred: so we're moving a bug to another place? :P20:28
fungiwe're playing musical bugs20:29
EmilienMmordred: where you are the PTL of this bug?20:29
EmilienMsounds like a safe plan ;-)20:29
mordredmmm. bug orchestras20:29
mordredEmilienM: aren't I the PTL of all bugs? :)20:29
EmilienMHi, I'm PTL of a bug20:29
fungimordred: you're probably about to be at any rate20:30
mordredfungi: indeed20:30
*** e0ne has joined #openstack-meeting20:30
EmilienMfungi: is the namespace still ok?20:30
EmilienMI guess we don't want to mess with git migration?20:30
* stevemar sneaks in20:30
mordredyah - I'm concerned that would wind up breaking humans for no great reason20:30
fungiEmilienM: repo renames are painful, but also doable separately later if we really decide it's causing a problem20:30
dimsEmilienM : we can leave it to the infra team if/when they want to do the git migration20:30
EmilienMfair enough, just a random question20:31
EmilienMwe have the quorum, ship it20:31
dimsEmilienM : needed to be asked :)20:31
ttx /me ships20:31
fungiand as i mentioned in one of the review comments, it's not the first repo in the openstack-infra namespace which isn't an infra team deliverable20:31
EmilienMfungi: good to know20:31
EmilienM#topic Add tag assert:never-breaks-compat20:31
*** openstack changes topic to "Add tag assert:never-breaks-compat (Meeting topic: tc)"20:31
EmilienM#link https://review.openstack.org/44656120:31
EmilienMmordred: you again?? :)20:32
mordredyah - this one I think people had more concerns with20:32
mordredI think you all know I have extreme views on compatibility20:32
mordredthis is an attempt to create an opt-in assertion for anyone who starts sharing them with me :)20:32
EmilienMI found the name weird tbh20:32
mordredEmilienM: I'm also _very_ bad at naming things20:32
EmilienMstevemar had a great proposal I think20:33
mtreinishmordred: how does this relate to https://review.openstack.org/#/c/418010/ ?20:33
*** ntpttr_ has quit IRC20:33
mordredbasically - as I was looking at the standard-deprecation tag and applying it to shade, I was dismayed that it laid out concepts around removal that shade did not, in fact, share20:33
*** corey__ has quit IRC20:33
EmilienMI liked assert:fully-compatible20:33
mordredmtreinish: it's very very similar20:34
johnthetubaguydo we have a team to start adopting this one? was it swift?20:34
mtreinishmordred: heh, that's what I was thinking as I started reading it20:34
jrolljohnthetubaguy: probably shade :P20:34
johnthetubaguyjroll: heh20:34
fungitimely given that novaclient has just stopped supporting some nova-net features which may still be in heavy use in the wild20:35
*** ntpttr_ has joined #openstack-meeting20:35
mordredjohnthetubaguy: swift as so far not broken anything, although notmyname wasn't sure they wanted to assert it20:35
sdaguemordred: ok, so before creating a wish list tag, is any team going to assert that?20:35
mordredfungi: those, in fact, broke shade for a second20:35
mordredsdague: I mean, shade is - but I konw that's only one team20:35
notmynameI agreed with clayg's comments on the review (which in large part were due to the name)20:35
johnthetubaguymordred: do they know? the testing on this is really hard, I know you touch on that, did you want to include that20:35
*** luyao has quit IRC20:35
ttxI think we shouldn't create the tag until we want to encourage more projects to adopt it20:36
mordredjohnthetubaguy: well - there's intent and then there is perfection in reality20:36
notmynameas of this point today, the swift team is not looking to assert this tag20:36
*** luyao has joined #openstack-meeting20:36
*** askb has joined #openstack-meeting20:37
fungii feel like it's sufficient to declare that a project will try not to break backward compatibility and will consider any such breakage (even if not actively tested) an important bug worth fixing20:37
mordredfor now this is about intent - the team asserts its intent is to not release breaking changes to its api20:37
ttxbase question is, is that a behavior we ideally want all projects to have20:37
mordredfungi: ++20:37
dtroyerttx: I'm not sure we need that, it is another indicator of intent/status20:37
sdagueI also think like it's a different story between a library and service, and the challenges of the 2 mean it's a little weird to lump them in20:37
johnthetubaguysdague: thats a very good point20:38
mordredso - the reason I think they're the same, and that's it's valuable20:38
JayFI would also wonder if having a "super" we-don't-break-compatibility tag will water down the value of a project that has standard-deprecation. For instance, I could see an external force (like someone in management) wanting to push for the more impactful tag.20:38
mordredis that it's also entirely possible that teams value things like "cleaning things up" or "reducing maint burden"20:38
mordredwhich are other points of view that are held, from time to time, by various people20:38
johnthetubaguynever breaks requires basically infinite man power, at least feels that way as a service20:39
dimsnotmyname : were there any things in that review that did not sit well with the swift team?20:40
mordredjohnthetubaguy: but if the service team doesn't do it- the end user has to20:40
johnthetubaguymordred: I keep thinking about cloud pipe VPN as the example20:40
mordredthe burden exists somewhere, because we aren't a single implementation of any of our services, but are instead a collection of differently versioned points in time of each service out in the world20:40
fungidefinitely runs counter to the interest in the joint board/tc/uc meeting for dropping rarely-used options, features and backends to simplify service complexity20:40
sdaguemordred: I definitely agree with you on the slider20:40
thingeeI'm ok with the idea. I like that there is something that encourages and asserts this value of a project.20:41
mordredjohnthetubaguy: yah - I mean, I don't thikn teams should start off with this20:41
sdaguewhere there are things where either the service handles it or externalizes to all the users20:41
notmynamedims: in general, the absolute-ness of it. true, we do our best not to break clients. but sometimes it's a very fuzzy line to determine what "break" means20:41
sdaguebut *never* is a really strong word20:41
johnthetubaguysdague: +1 on the slider, I am just not right up against the far end20:41
notmynameto quote the gerrit review from clayg: 'there should be a thing here for security too - like "when faced with a mistake and given the choice that either the behavior of the api changes to include a new restriction or it's impossible to use safely prefer to fix it"'20:41
EmilienMfungi: good point20:41
dimsack notmyname20:41
sdaguenotmyname: ++20:41
thingeenotmyname: agreed20:42
mordrednotmyname: yah - I mean, I thought I had that in there already20:42
notmynameI think that's just one example where we do "break" compat, but it depends on what breaking means20:42
mordredbut I'll definitely take another stab at making that much clearer - beause I totally agree with that20:42
dimsmay be this language goes somewhere else as projects should aspire to be doing this20:42
notmynameanother is when implementation is different than RFC. who's wrong? the client? the service? it's different at different times20:42
fungimy main issue is that it doesn't seem like it can actually be meaningful. does applying it now mean the project has never broken backward compatibility in the past? or just promises not to do so from now on? and only until they choose to remove the tag? can it be re-added again after that? "247 days since last api backward-compatibility breakage"20:42
*** sc68cal has left #openstack-meeting20:42
notmynameand we've made different calls at different times (and sometimes reverted)20:42
sdaguefungi: right, past returns not indicative of future performance?20:43
mordredfungi: zomg. we need that badge20:43
johnthetubaguymordred: so that API almost never worked on any cloud, probably has worked for years, no one dare test it, we can keep that behaviour today, but removing it might actually cause less user confusion... but I am agree its all about the users.20:43
dimsfungi : if we don't make any changes in the repo :)20:43
mordredjohnthetubaguy: yah. fair point20:44
thingeemordred: badge/sticker idea for shade20:44
sdaguemordred: honestly, on the mission of helping more developers understand the cost of externalizing their API changes without compatibility, it feels like a description of the costs of that is maybe better than a tag20:44
johnthetubaguymordred: I mean I am totally on your side in terms of getting the slider in the right place though20:44
dims++ johnthetubaguy20:44
johnthetubaguysdague: thats a top idea20:44
mordredto both of you20:44
sdagueI feel like a lot of the heatedness during the API WG sessions at the PTG were because people really hadn't thought through20:44
mordredsdague: where should that go, do you think?20:45
sdaguelike "oh, then you have to make this change to ruby sdk, this go thing, this nodejs thing, etc"20:45
sdaguemordred: that's a good question... api-wg repo maybe?20:45
mordredsdague: yah - that's probablya good place20:45
* johnthetubaguy remembers the Nova v3.0 API debates... its really not obvious as it seems after you have the "ah ha moment"20:45
fungialso, time check. 15 minutes remaining with another topic before open discussion20:46
*** luyao has quit IRC20:46
EmilienMfungi: indeed20:46
EmilienMmordred: can we move on?20:46
EmilienMmordred: and re-iterate next week probably20:46
*** luyao has joined #openstack-meeting20:46
mordredEmilienM: yup20:46
EmilienM#topic Resolution on OpenStack's mission for cloud applications20:46
*** openstack changes topic to "Resolution on OpenStack's mission for cloud applications (Meeting topic: tc)"20:46
EmilienM#link https://review.openstack.org/44703120:46
johnthetubaguymordred: sdague: that new API guidelines thing probably has 80/90% of that context thinking about it20:46
*** neiljerram has quit IRC20:47
sdaguejohnthetubaguy: maybe, I think there is more context here20:47
dimskudos to zaneb20:47
*** e0ne has quit IRC20:47
EmilienMzaneb: any comment on this one?20:47
zanebdims: thanks for prompting me to do this :)20:47
johnthetubaguysdague: +1 for there being some missing, totally needs checking20:47
*** esberglu has quit IRC20:47
zanebEmilienM: not much to add really. if anyone has questions I can try to answer 'em20:48
*** esberglu has joined #openstack-meeting20:48
EmilienMI think we miss one vote to ship it20:48
dimswhen we get this in, we should promote this mission statement heavily20:48
sdaguezaneb: I guess my only question is how does paragraph 4 turn into concrete things20:49
zanebI'm also interested in how we can get the whole community on board with this, not only the TC20:49
mordredzaneb: there are other people?20:49
*** neiljerram has joined #openstack-meeting20:50
zanebsdague: it's a balancing act between getting too concrete and failing to say anything at all20:50
EmilienM(I want to keep 7 min for open discussion fyi)20:50
*** tonytan4ever has quit IRC20:50
mordredzaneb: srrsly though - even just tweeting out the link to the published doc when it lands would be a good first step in folks seeing it / reading it / ingesting it20:50
johnthetubaguyso I have been thinking about including this kind of discussion as part of the VM & BM working group thing, for the next PTG20:50
zanebsdague: feedback on the first draft was that it was too vague20:50
mordredjohnthetubaguy: ++20:51
*** raj_singh has quit IRC20:51
dimszaneb : the board and tc talked about adjacent communities which we turned around and running with it in the "go/containers" thread and actively finding people and proposals to expand on that. we need to do something similar20:51
sdaguezaneb: yeh, I guess it feels like a bunch of keystone related effort, and it would be nice to have keystone community members bought in before the TC declares this a thing20:51
sdagueI don't see any keystone folks in the the +1 list, right?20:51
mtreinishlbragstad: ^^^20:52
*** kaisers_ has quit IRC20:52
zanebjohnthetubaguy: that would be great. it might be worth discussing if there are any sessions we could organise at the Forum to get started too20:52
johnthetubaguysdague: thats a very good point, more keystone +1 around that would be good20:52
*** esberglu has quit IRC20:52
lbragstadmtreinish o/20:52
zanebsdague: I agree, although it's not _just_ keystone that needs to be on board20:52
sdaguezaneb: sure20:53
EmilienMlbragstad: we're running out of time but it would be great if your team could have a look at https://review.openstack.org/#/c/44703120:53
sdagueI just wouldn't want to land it without any keystone feedback20:53
johnthetubaguyzaneb: possibly, I was getting the vibes we wouldn't have enough of those project developers present to have a good discussion20:53
EmilienMsdague: +120:53
sdagueEmilienM: can I propose we table until next week and make sure keystone folks throw in20:53
*** dprince has quit IRC20:53
EmilienMsdague: yes please20:53
zanebmordred: https://twitter.com/zerobanana/status/84276324754364006420:53
lbragstadEmilienM sdague awesome - i'll review today20:53
dimszaneb : let's throw this into general mailing list too and ask folks to vote20:53
EmilienM#action Get Keystone team to review https://review.openstack.org/#/c/44703120:54
zanebdims: ack, will send a mail today20:54
sdaguezaneb: awesome20:54
EmilienM#topic Open discussion20:54
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:54
*** tobberydberg has joined #openstack-meeting20:54
dimsthanks zaneb20:54
*** tobberydberg has quit IRC20:54
EmilienM* Forum topics: http://forumtopics.openstack.org/20:54
*** tobberydberg has joined #openstack-meeting20:54
* dims has to run. will catch up on the meeting log20:54
EmilienMI sent an email to tc ML about the sessions I created on behalf of the authord in the etherpad we have20:54
ttxPosted details about the TC+Board+UC meeting (and dinner) in Boston around summit20:55
EmilienM#link https://etherpad.openstack.org/p/BOS-TC-brainstorming20:55
EmilienMif anyone who wrote a topic on https://etherpad.openstack.org/p/BOS-TC-brainstorming wants to change the content on http://forumtopics.openstack.org/ - please let me know20:55
*** sambetts is now known as sambetts|afk20:55
ttxI was thinking about a "should Stackalytics die" session. Does that sound like a good idea ?20:55
EmilienMfloor is open to questions and feedback or any other topic!20:55
notmynamettx: yes. also, it's a good forum topic ;-)20:56
mtreinishttx: does anyone think we shouldn't kill it?20:56
johnthetubaguyEmilienM: I did mean to reply to you, honest, just not had chance20:56
EmilienMttx: maybe not die, but evolve20:56
thingeemtreinish: you'll have to attend the session to find out!20:56
EmilienMjohnthetubaguy: you don't have to worry20:56
*** luyao has quit IRC20:56
*** luyao has joined #openstack-meeting20:56
ttxEmilienM: all metrics used to compare performance will result in gaming amd incentivize bad behavior20:57
jrollstackalytics is super nice for some quick information discovery, e.g. finding out if cores are pulling their weight and such. I do wonder if the downstream abuse outweighs those benefits20:57
ttxso that evolution would need to be very close to death20:57
fungimtreinish: it fills the gap of having some sort of central statistics so that every member company doesn't feel obliged to publish their own conflicting community involvement metrics, at least20:57
jrollI used it all the time as PTL20:57
*** baoli has quit IRC20:57
*** ntpttr_ has quit IRC20:57
EmilienMjroll: same thing. Very useful to find out who in the team makes good progress on reviews, etc20:57
thingeeI still use russellb's stats20:57
thingeeeven if it doesn't update20:58
*** VW has joined #openstack-meeting20:58
lbragstadthingee ++ same here20:58
*** e0ne has joined #openstack-meeting20:58
ttxfungi: we/Foundation would need to produce some official stats to compensate20:58
dtroyerthese are all uses that are great, but done by people who understand what they are looking at.20:58
jrollthingee: sure, stackalytics can give you different views on the data though. especially when you have lots of projects under one umbrella (neutron, ironic,e tc)20:58
*** raj_singh has joined #openstack-meeting20:58
*** VW has quit IRC20:58
JayFI'm not even sure I understand what the percieved value would be of killing Stackalytics. If downstream managers want to use bad metrics, they'll use bad metrics whether provided by stackalytics or not.20:58
ttxOK, sounds like an interesting discussion, will propose20:58
fungittx: yep. and i guess not outsource that stats collection to a third party like we tried in the past?20:58
johnthetubaguyjroll: ++20:58
sdaguefungi: ++20:58
jrollJayF: good point, I'd love to see more context20:59
clarkbJayF: there is likely an argument that we shouldn't enable it though20:59
*** ntpttr_ has joined #openstack-meeting20:59
*** VW has joined #openstack-meeting20:59
*** markvoelker has joined #openstack-meeting20:59
lbragstadjroll ++ another data point doesn't really hurt20:59
EmilienMfungi: agreed.20:59
JayFI don't think removing stackalytics would change any downstream behaviors, honestly. And there are clearly upstream use cases for it (see comments made in here already)20:59
sdagueJayF: ++20:59
ttxJayF: remove bad incentives, mostly20:59
EmilienMI'm about to close the meeting20:59
jrollit'll just make managers ask me to gather stats :P20:59
sdaguejroll: ++20:59
fungigranted, openstack doesn't officially run stackalytics (yet anyway). it's not an official project and it's provided by one company20:59
JayFttx: I promise, management is creative enough to find new bad incentives20:59
EmilienMthanks all for giving me the change to do it ;-)20:59
sdagueyeh, pretty much20:59
JayFjroll: ++++20:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Tue Mar 28 21:00:01 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-03-28-20.01.html21:00
johnthetubaguyJayF ++21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-03-28-20.01.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-03-28-20.01.log.html21:00
ttxJayF: A lot of Chinese contributors, for example, think of Stackalytics as reflecting value and do not contribute where they should21:00
jrollEmilienM: thanks for hosting!21:00
*** gordc has left #openstack-meeting21:00
ttxEmilienM: thx!21:00
JayFttx: Yeah. That's a problem, I just don't think killing stackalytics changes that.21:00
sdaguettx: yeh, but lacking stackalytics, some internal person would build tests with gitdm or random script instead21:00
EmilienMI suggest using #openstack-dev21:00
johnthetubaguysdague: ++21:00
JayFsdague: ++ exactly21:00
sdaguehaving maintained a gitdm fork before... I can guaruntee that will be the case21:01
*** rbowen has quit IRC21:01
ttxsdague: except stackalytics is now broken and nobody steps up to fix it21:01
*** VW_ has quit IRC21:01
*** e0ne has quit IRC21:01
ttxanyway, need to run21:01
*** e0ne has joined #openstack-meeting21:02
*** matrohon has quit IRC21:02
*** e0ne has quit IRC21:02
*** e0ne has joined #openstack-meeting21:02
*** e0ne has quit IRC21:03
*** ntpttr_ has quit IRC21:03
*** e0ne has joined #openstack-meeting21:04
*** markvoelker has quit IRC21:04
*** e0ne has quit IRC21:04
*** rfolco has quit IRC21:04
*** e0ne has joined #openstack-meeting21:04
*** e0ne has quit IRC21:05
*** henrynash has joined #openstack-meeting21:05
*** tobberydberg has quit IRC21:05
*** ntpttr_ has joined #openstack-meeting21:05
*** e0ne has joined #openstack-meeting21:05
*** rockyg has quit IRC21:05
*** e0ne has quit IRC21:05
*** tobberydberg has joined #openstack-meeting21:05
*** tobberydberg has quit IRC21:06
*** e0ne has joined #openstack-meeting21:06
*** e0ne has quit IRC21:06
*** luyao has quit IRC21:06
*** henrynash has quit IRC21:06
*** ianychoi has quit IRC21:07
*** jmckind_ has quit IRC21:07
*** olaph has left #openstack-meeting21:08
*** baoli has joined #openstack-meeting21:08
*** ianychoi has joined #openstack-meeting21:08
*** luyao has joined #openstack-meeting21:09
*** ntpttr_ has quit IRC21:09
*** jamesdenton has quit IRC21:09
*** dimtruck is now known as zz_dimtruck21:10
*** gouthamr has quit IRC21:10
*** ntpttr_ has joined #openstack-meeting21:11
*** julim has quit IRC21:15
*** ntpttr_ has quit IRC21:15
*** luyao has quit IRC21:16
*** ntpttr_ has joined #openstack-meeting21:17
*** luyao has joined #openstack-meeting21:17
*** rbak has quit IRC21:18
*** annegentle has quit IRC21:19
*** ntpttr_ has quit IRC21:21
*** eharney has quit IRC21:22
*** ntpttr_ has joined #openstack-meeting21:23
*** jrobinson has joined #openstack-meeting21:24
*** cloudrancher has joined #openstack-meeting21:27
*** luyao has quit IRC21:27
*** luyao has joined #openstack-meeting21:27
*** ntpttr_ has quit IRC21:27
*** sneti_ has joined #openstack-meeting21:27
*** mriedem has quit IRC21:29
*** ntpttr_ has joined #openstack-meeting21:29
*** VW_ has joined #openstack-meeting21:30
*** VW has quit IRC21:30
*** stanchan has quit IRC21:30
*** haleyb has quit IRC21:31
*** stanchan has joined #openstack-meeting21:31
*** ihrachys has quit IRC21:32
*** raj_singh has quit IRC21:33
*** VW_ has quit IRC21:35
*** VW has joined #openstack-meeting21:35
*** luyao has quit IRC21:37
*** luyao has joined #openstack-meeting21:37
*** jaugustine has quit IRC21:40
*** mriedem has joined #openstack-meeting21:40
*** donghao has joined #openstack-meeting21:41
*** ntpttr_ has quit IRC21:41
*** ntpttr_ has joined #openstack-meeting21:43
*** donghao has quit IRC21:47
*** ntpttr_ has quit IRC21:47
*** luyao has quit IRC21:47
*** luyao has joined #openstack-meeting21:48
*** henrynash has joined #openstack-meeting21:48
*** ntpttr_ has joined #openstack-meeting21:49
*** thorst has quit IRC21:51
*** kaisers_ has joined #openstack-meeting21:52
*** claudiub has joined #openstack-meeting21:54
*** ntpttr_ has quit IRC21:55
*** raj_singh has joined #openstack-meeting21:56
*** unicell has quit IRC21:56
*** annegentle has joined #openstack-meeting21:56
*** ntpttr_ has joined #openstack-meeting21:57
*** kaisers_ has quit IRC21:57
*** awaugama has quit IRC21:57
*** luyao has quit IRC21:57
*** luyao has joined #openstack-meeting21:58
*** sneti_ has quit IRC21:59
*** markvoelker has joined #openstack-meeting21:59
*** MrJoshua has quit IRC22:00
*** unicell has joined #openstack-meeting22:01
*** ntpttr_ has quit IRC22:01
*** gouthamr has joined #openstack-meeting22:01
*** ntpttr_ has joined #openstack-meeting22:03
*** mriedem has quit IRC22:04
*** bobh has quit IRC22:05
*** markvoelker has quit IRC22:06
*** ntpttr_ has quit IRC22:07
*** luyao has quit IRC22:08
*** cloudrancher has quit IRC22:08
*** cody-somerville has joined #openstack-meeting22:08
*** luyao has joined #openstack-meeting22:08
*** fnaval has quit IRC22:08
*** ntpttr_ has joined #openstack-meeting22:09
*** jamesdenton has joined #openstack-meeting22:11
*** cloudrancher has joined #openstack-meeting22:13
*** ntpttr_ has quit IRC22:15
*** iceyao has joined #openstack-meeting22:16
*** baoli has quit IRC22:16
*** armstrong has joined #openstack-meeting22:16
*** jamesden_ has joined #openstack-meeting22:16
*** ntpttr_ has joined #openstack-meeting22:17
*** jamesdenton has quit IRC22:17
*** mriedem has joined #openstack-meeting22:18
*** luyao has quit IRC22:18
*** luyao has joined #openstack-meeting22:18
*** iceyao has quit IRC22:20
*** galstrom is now known as galstrom_zzz22:24
*** ntpttr_ has quit IRC22:28
*** luyao has quit IRC22:28
*** ntpttr_ has joined #openstack-meeting22:29
*** luyao has joined #openstack-meeting22:29
*** yamamoto has joined #openstack-meeting22:30
*** xyang1 has quit IRC22:31
*** jamesden_ has quit IRC22:32
*** ntpttr_ has quit IRC22:33
*** tommylikehu_ has joined #openstack-meeting22:34
*** ntpttr_ has joined #openstack-meeting22:35
*** yamamoto has quit IRC22:37
*** luyao has quit IRC22:38
*** luyao has joined #openstack-meeting22:39
*** jaypipes has quit IRC22:39
*** ntpttr_ has quit IRC22:39
*** ntpttr_ has joined #openstack-meeting22:41
*** tommylikehu_ has quit IRC22:44
*** ihrachys has joined #openstack-meeting22:45
*** lamt has quit IRC22:46
*** luyao has quit IRC22:49
*** luyao has joined #openstack-meeting22:49
*** ykatabam has joined #openstack-meeting22:50
*** david-lyle has quit IRC22:51
*** thorst has joined #openstack-meeting22:51
*** tommylikehu_ has joined #openstack-meeting22:51
*** ntpttr_ has quit IRC22:51
*** fnaval has joined #openstack-meeting22:52
*** ntpttr_ has joined #openstack-meeting22:53
*** yamamoto has joined #openstack-meeting22:53
*** kaisers_ has joined #openstack-meeting22:54
*** ihrachys has quit IRC22:55
*** thorst has quit IRC22:55
*** annegentle has quit IRC22:55
*** tommylikehu_ has quit IRC22:56
*** yamamoto has quit IRC22:56
*** Patifa has quit IRC22:56
*** zz_dimtruck is now known as dimtruck22:56
*** kaisers_ has quit IRC22:58
*** luyao has quit IRC22:59
*** luyao has joined #openstack-meeting22:59
*** ntpttr_ has quit IRC22:59
*** lamt has joined #openstack-meeting23:00
*** tommylikehu_ has joined #openstack-meeting23:01
*** ntpttr_ has joined #openstack-meeting23:01
*** markvoelker has joined #openstack-meeting23:02
*** yamamoto has joined #openstack-meeting23:03
*** tommylikehu_ has quit IRC23:05
*** ntpttr_ has quit IRC23:05
*** markvoelker has quit IRC23:06
*** ntpttr_ has joined #openstack-meeting23:07
*** thorst has joined #openstack-meeting23:08
*** luyao has quit IRC23:09
*** luyao has joined #openstack-meeting23:10
*** ntpttr_ has quit IRC23:11
*** ntpttr_ has joined #openstack-meeting23:13
*** sdague has quit IRC23:15
*** cloudrancher has quit IRC23:15
*** lamt has quit IRC23:17
*** luyao has quit IRC23:19
*** luyao has joined #openstack-meeting23:20
*** ntpttr_ has quit IRC23:24
*** yamamoto has quit IRC23:24
*** thorst has quit IRC23:25
*** ntpttr_ has joined #openstack-meeting23:25
*** thorst has joined #openstack-meeting23:25
*** VW_ has joined #openstack-meeting23:27
*** mriedem has quit IRC23:28
*** ykatabam has quit IRC23:29
*** thorst has quit IRC23:29
*** luyao has quit IRC23:30
*** VW has quit IRC23:30
*** luyao has joined #openstack-meeting23:30
*** VW_ has quit IRC23:31
*** ntpttr_ has quit IRC23:31
*** ntpttr_ has joined #openstack-meeting23:33
*** ykatabam has joined #openstack-meeting23:33
*** mlavalle has quit IRC23:38
*** ntpttr_ has quit IRC23:39
*** cdub has joined #openstack-meeting23:40
*** luyao has quit IRC23:40
*** luyao has joined #openstack-meeting23:40
*** Fdaisuke has joined #openstack-meeting23:40
*** ntpttr_ has joined #openstack-meeting23:41
*** gyee has quit IRC23:43
*** erlon has joined #openstack-meeting23:44
*** Julien-zte has quit IRC23:44
*** ntpttr_ has quit IRC23:45
*** ntpttr_ has joined #openstack-meeting23:47
*** Swami has quit IRC23:49
*** luyao has quit IRC23:50
*** luyao has joined #openstack-meeting23:51
*** ntpttr_ has quit IRC23:51
*** ntpttr_ has joined #openstack-meeting23:52
*** kaisers_ has joined #openstack-meeting23:54
*** thorst has joined #openstack-meeting23:56
*** kaisers_ has quit IRC23:59
*** ntpttr_ has quit IRC23:59

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