Tuesday, 2017-04-18

*** egallen has quit IRC00:00
*** Apoorva_ has quit IRC00:01
*** jamesdenton has quit IRC00:01
*** Apoorva has joined #openstack-meeting00:01
*** egallen has joined #openstack-meeting00:02
*** ntpttr has quit IRC00:02
*** jamesdenton has joined #openstack-meeting00:03
*** ntpttr has joined #openstack-meeting00:03
*** aeng has quit IRC00:03
*** mickeys has joined #openstack-meeting00:04
*** galstrom_zzz is now known as galstrom00:06
*** mickeys has quit IRC00:09
*** ntpttr has quit IRC00:10
*** ntpttr has joined #openstack-meeting00:11
*** jamesdenton has quit IRC00:13
*** rderose has quit IRC00:14
*** hongbin has quit IRC00:15
*** jamesdenton has joined #openstack-meeting00:15
*** ntpttr has quit IRC00:16
*** aeng has joined #openstack-meeting00:16
*** ntpttr has joined #openstack-meeting00:17
*** jamesdenton has quit IRC00:19
*** kambiz has joined #openstack-meeting00:21
*** jamesdenton has joined #openstack-meeting00:22
*** ntpttr has quit IRC00:24
*** galstrom is now known as galstrom_zzz00:24
*** ntpttr has joined #openstack-meeting00:25
*** thorst has quit IRC00:27
*** cloudrancher has quit IRC00:29
*** xingchao has joined #openstack-meeting00:32
*** ntpttr has quit IRC00:32
*** ntpttr has joined #openstack-meeting00:32
*** jamesdenton has quit IRC00:34
*** reedip_ has joined #openstack-meeting00:36
*** ihrachys has joined #openstack-meeting00:37
*** wanghao has joined #openstack-meeting00:37
*** ihrachys has quit IRC00:37
*** ntpttr has quit IRC00:40
*** Julien-zte has joined #openstack-meeting00:41
*** ntpttr has joined #openstack-meeting00:41
*** xingchao has quit IRC00:41
*** zhurong has joined #openstack-meeting00:42
*** ntpttr has quit IRC00:46
*** ntpttr has joined #openstack-meeting00:47
*** jamesdenton has joined #openstack-meeting00:49
*** donghao has joined #openstack-meeting00:49
*** ntpttr has quit IRC00:51
*** ntpttr has joined #openstack-meeting00:52
*** newmember has quit IRC00:53
*** mriedem has quit IRC00:53
*** newmember has joined #openstack-meeting00:54
*** donghao has quit IRC00:54
*** wanghao has quit IRC00:55
*** wanghao has joined #openstack-meeting00:56
*** ntpttr has quit IRC00:57
*** ntpttr has joined #openstack-meeting00:59
*** ykatabam has quit IRC00:59
*** Swami has quit IRC01:00
*** Apoorva_ has joined #openstack-meeting01:00
*** ntpttr has quit IRC01:03
*** Apoorva has quit IRC01:04
*** wanghao_ has joined #openstack-meeting01:04
*** Apoorva_ has quit IRC01:04
*** mickeys has joined #openstack-meeting01:05
*** ntpttr has joined #openstack-meeting01:05
*** xingchao has joined #openstack-meeting01:06
*** wanghao has quit IRC01:07
*** mickeys has quit IRC01:09
*** ijw has joined #openstack-meeting01:09
*** ntpttr has quit IRC01:12
*** thorst has joined #openstack-meeting01:12
*** thorst has quit IRC01:12
*** ntpttr has joined #openstack-meeting01:13
*** kevinz has joined #openstack-meeting01:13
*** armstrong has quit IRC01:13
*** wanghao has joined #openstack-meeting01:13
*** ijw has quit IRC01:14
*** guoshan has joined #openstack-meeting01:14
*** wanghao_ has quit IRC01:16
*** ntpttr has quit IRC01:17
*** ntpttr has joined #openstack-meeting01:19
*** ykatabam has joined #openstack-meeting01:19
*** jamesdenton has quit IRC01:22
*** ntpttr has quit IRC01:24
*** ntpttr has joined #openstack-meeting01:25
*** dmacpher has quit IRC01:27
*** ijw has joined #openstack-meeting01:27
*** esberglu has joined #openstack-meeting01:29
*** ricolin__ has joined #openstack-meeting01:29
*** ntpttr has quit IRC01:29
*** esberglu has quit IRC01:29
*** esberglu has joined #openstack-meeting01:29
*** huanxuan has joined #openstack-meeting01:29
*** galstrom_zzz is now known as galstrom01:29
*** esberglu has quit IRC01:29
*** esberglu has joined #openstack-meeting01:30
*** ntpttr has joined #openstack-meeting01:31
*** esberglu has quit IRC01:34
*** wanghao has quit IRC01:36
*** wanghao has joined #openstack-meeting01:37
*** ntpttr has quit IRC01:38
*** gcb has joined #openstack-meeting01:39
*** ntpttr has joined #openstack-meeting01:39
*** jamesdenton has joined #openstack-meeting01:42
*** ijw has quit IRC01:44
*** scottda has quit IRC01:45
*** hongbin has joined #openstack-meeting01:45
*** ntpttr has quit IRC01:46
*** ntpttr has joined #openstack-meeting01:47
*** s3wong has quit IRC01:47
*** ijw has joined #openstack-meeting01:48
*** zhongjun_ has quit IRC01:51
*** donghao has joined #openstack-meeting01:51
*** iceyao has joined #openstack-meeting01:51
*** ricolin has joined #openstack-meeting01:52
*** ijw has quit IRC01:52
*** jkilpatr has quit IRC01:53
*** jamesdenton has quit IRC01:54
*** donghao has quit IRC01:55
*** vishwanathj has joined #openstack-meeting01:56
*** vishwanathj has quit IRC01:58
*** vishwanathj has joined #openstack-meeting01:58
*** ykatabam has quit IRC02:00
*** epico has joined #openstack-meeting02:01
*** jkilpatr has joined #openstack-meeting02:02
*** vishwanathj has quit IRC02:03
*** iceyao has quit IRC02:03
*** vishwanathj has joined #openstack-meeting02:04
*** iceyao has joined #openstack-meeting02:04
*** mickeys has joined #openstack-meeting02:05
*** egallen has quit IRC02:07
*** unicell has quit IRC02:08
*** ykatabam has joined #openstack-meeting02:09
*** mickeys has quit IRC02:10
*** julim has quit IRC02:12
*** julim has joined #openstack-meeting02:12
*** julim has quit IRC02:12
*** bobh has joined #openstack-meeting02:12
*** thorst has joined #openstack-meeting02:13
*** yamahata has quit IRC02:14
*** jamesdenton has joined #openstack-meeting02:14
*** jamesdenton has quit IRC02:16
*** thorst has quit IRC02:18
*** vishnoianil has quit IRC02:19
*** jamesdenton has joined #openstack-meeting02:21
*** taowuwen has joined #openstack-meeting02:21
*** VW has joined #openstack-meeting02:22
*** VW has quit IRC02:24
*** VW has joined #openstack-meeting02:25
*** TheJulia has quit IRC02:26
*** gouthamr has quit IRC02:27
*** khappone_ has quit IRC02:27
*** iyamahat has quit IRC02:27
*** khappone has joined #openstack-meeting02:27
*** zhongjun has quit IRC02:27
*** rajinir has quit IRC02:28
*** TheJulia has joined #openstack-meeting02:29
*** zhongjun has joined #openstack-meeting02:29
*** strigazi has quit IRC02:30
*** rajinir has joined #openstack-meeting02:31
*** strigazi has joined #openstack-meeting02:31
*** cloudrancher has joined #openstack-meeting02:32
*** hongbin_ has joined #openstack-meeting02:34
*** hongbin_ has quit IRC02:36
*** hongbin has quit IRC02:36
*** cloudrancher has quit IRC02:37
*** hongbin has joined #openstack-meeting02:37
*** reedip_ has quit IRC02:42
*** ricolin__ has quit IRC02:43
*** jamesdenton has quit IRC02:46
*** eliqiao has joined #openstack-meeting02:48
*** iceyao has quit IRC02:49
*** FengShengqin has joined #openstack-meeting02:55
*** FengShengqin has quit IRC02:55
*** shu-mutou-AWAY is now known as shu-mutou02:55
*** lakerzhou has joined #openstack-meeting02:57
*** FengShengqin has joined #openstack-meeting02:57
*** galstrom is now known as galstrom_zzz02:57
*** shubhams has joined #openstack-meeting02:58
hongbin#startmeeting zun03:00
openstackMeeting started Tue Apr 18 03:00:08 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-04-18_0300_UTC Today's agenda03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
kevinzkevinz03:00
shubhamsShubham03:00
mkraiMadhuri Kumari03:00
* eliqiao eli lurk03:00
FengShengqinFengShengqin03:00
hongbinthanks for joining kevinz shubhams mkrai eliqiao FengShengqin03:01
shu-mutouShu Muto03:01
hongbinthanks for joining shu-mutou03:01
lakerzhoulakerzhou03:01
hongbinlakerzhou: thanks for joining03:01
hongbinok, let's get started03:01
*** diga has joined #openstack-meeting03:01
hongbin#topic Announcements03:01
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:01
digao/03:01
hongbin1. We will have a "Boston Summit" release by the end of April03:01
hongbinthere are several patches i want to include in this release03:02
hongbin1. the interactive execute feature03:02
hongbin#link https://review.openstack.org/#/c/445234/03:02
hongbin2. the kuryr integration patch03:02
hongbin#linkhttps://review.openstack.org/#/c/453387/03:02
hongbinwould appreciate reviews on those two patches (although they are both big patches)03:03
*** zhurong has quit IRC03:03
hongbinanything else that you want to be included?03:03
mkraihongbin: can we get through all the patches for kuryr integration?03:03
digawe can include cinder-integration patch also03:03
*** pksingh has joined #openstack-meeting03:04
hongbinmkrai: this is the kuryr integration patch: https://review.openstack.org/#/c/453387/03:04
pksinghHello All03:04
*** lamt has joined #openstack-meeting03:04
hongbinpksingh: hey, welcome back03:04
*** tonyb has quit IRC03:04
pksingh:)03:04
hongbinmkrai: from my point of view, merge this patch would be good enough: https://review.openstack.org/#/c/453387/03:05
mkraihongbin: I see, will review it03:05
hongbinmkrai: there should be a few network api patches that are optional IMO03:05
hongbinmkrai: and i rely on you for the network api design :)03:05
*** iceyao has joined #openstack-meeting03:06
mkraiSure will start working on it03:06
hongbindiga: for the cinder integration, we can include it if it can make it before the release03:06
digahongbin: yeah, I need your time to bypass the gate, let me know so that we can work on it03:07
hongbinmkrai: thanks03:07
digahongbin: may be today/tomorrow, anytime03:07
mkrai+1 for cinder integration if we can make it03:07
hongbindiga: sure, i will help you for that03:07
hongbinok, any other announccement from you guys?03:08
*** sudipto has joined #openstack-meeting03:08
hongbinok, advance topic03:08
digahongbin: thank you03:08
*** sudipto_ has joined #openstack-meeting03:08
hongbin#topic Review Action Items03:08
*** openstack changes topic to "Review Action Items (Meeting topic: zun)"03:08
hongbin1. Hongbin help diga to get the cinder integration patch passed the gate (PENDING)03:09
hongbin#link https://review.openstack.org/#/c/429943/03:09
*** tonyb has joined #openstack-meeting03:09
hongbin#action hongbin help diga to get the cinder integration patch passed the gate03:09
hongbinwill do that this week03:09
hongbin2. Everyone review the zun ui ehterpad03:09
hongbin#link https://etherpad.openstack.org/p/pike-zun-ui03:09
digahongbin: I will update the PS in sometime, so that we can work gate job process03:09
hongbindo everyone have a chance to look at the etherpad?03:10
hongbindiga: ack03:10
pksinghlooking the etherpad03:10
mkraiLooking at it now03:10
hongbinok, let's pause for a minute03:11
hongbinthanks shu-mutou for fixing the two high priority item03:11
*** tonyb has quit IRC03:12
shu-mutousure!03:12
hongbini will figure out how to fix the third one03:12
mkraishu-mutou: after we support the image panel, will it show up the available images in drop down menu?03:13
*** zhurong has joined #openstack-meeting03:13
*** tonyb has joined #openstack-meeting03:13
*** emagana has joined #openstack-meeting03:13
shu-mutoumkrai: yes.03:13
*** himani has joined #openstack-meeting03:13
mkraiOk03:14
mkraiRest looks good to me. Thanks shu-mutou03:14
pksinghi need to install latest UI in my devstack03:14
*** thorst has joined #openstack-meeting03:14
hongbinok, are everyone happy with the list in the etherpad03:14
shu-mutouthanks everyone!03:14
pksingh+103:14
mkrai+103:14
shubhams+!03:15
shubhams+103:15
hongbinok03:15
hongbinseems the etherpad is good for everyone03:15
diga+103:15
hongbin3. Shunli created a bp for descriping anti-infinity scheduling use cases (DONE)03:15
hongbin#link https://blueprints.launchpad.net/zun/+spec/container-anti-affinity-policy03:15
hongbinthat conclude the action items03:16
hongbin#topic Cinder integration (diga)03:16
*** openstack changes topic to "Cinder integration (diga) (Meeting topic: zun)"03:16
hongbin#link https://blueprints.launchpad.net/zun/+spec/cinder-zun-integration The BP03:16
*** cody-somerville has joined #openstack-meeting03:16
*** noslzzp has quit IRC03:16
hongbindiga: seems we already talk about this bp, anything else you want to add?03:16
diganothing from my side03:16
hongbinok03:17
hongbinthen, let's advance topic03: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
hongbinhere is the first patch: https://review.openstack.org/#/c/453387/03:17
*** emagana has quit IRC03:17
hongbin#link https://review.openstack.org/#/c/453387/03:17
hongbinthis patch is big, let me explain what it does03:17
*** lamt has quit IRC03:18
hongbinbasically, when a user create a container, this patch will try to find an available neutron network (i.e. private)03:18
*** thorst has quit IRC03:18
hongbinthen, find its subnets/gateway/cidr etc03:18
hongbinuse all the information to compile a list of parameter for a api call to docker to create a docker network03:19
hongbinwhen the container is joining the network, zun will create a neutron port03:20
*** lamt has joined #openstack-meeting03:20
*** iceyao has quit IRC03:20
hongbinthen, pass the ip address of the port on the container creation03:20
hongbinas a result, kuryr will pick up the pre-created neutron port and plug the container to it03:20
*** iceyao has joined #openstack-meeting03:21
hongbinso far, everything is done in the backgroup, the api is the same as before03:21
hongbinin the future, we might need an option to specify the neutron network to create the container (right now, it is auto-select)03:21
hongbinthen, it might need a network api to manage the created docker network03:22
*** amotoki has joined #openstack-meeting03:22
hongbinhowever, that is optional for the demo in boston summit03:22
hongbinthat is everything from my side03:23
hongbinquestions?03:23
pksinghhongbin, so each container may be created in different network?03:23
mkraiHow is the private network selected in case of multiple network?03:24
hongbinpksingh: it will be created in the same network if they are in the same tenant03:24
pksinghok, my next question would be same as mkrai :)03:24
hongbinmkrai: it will choose the first available network03:24
hongbinthe logic is in the method: _get_available_network03:25
hongbinat here: https://review.openstack.org/#/c/453387/9/zun/container/docker/driver.py , line #50003:25
*** wanghao_ has joined #openstack-meeting03:26
hongbinthe chosen network don't have to be 'private'03:26
hongbinhowever, it will be a usable network03:26
hongbin(the network selection logic was copied from nova)03:26
*** wanghao_ has quit IRC03:27
hongbinhowever, it would be nice if there is an option to select the network03:27
hongbinwhich is a future work03:27
mkraiThen we would end up to land all the containers in only one network03:27
mkraiYes I also think so03:27
hongbinmkrai: yes, if auto-select, all containers will be on the same network03:27
pksinghnets[0] would be same for all containers?03:28
*** tonyb has quit IRC03:28
hongbinpksingh: what is nets[0]?03:28
pksinghwhat if some networrks are added?03:28
*** tonyb has joined #openstack-meeting03:28
pksinghline #507  in same file03:28
mkraithat is the first available network as you said03:29
hongbinpksingh: i see, if some networks are added, it might pick another network03:29
*** emagana has joined #openstack-meeting03:29
*** wanghao has quit IRC03:29
hongbinit just pick the first network at the time the container is created03:29
pksinghso it may be different for different containers, do we need to fix it or it is not necessary as of now?03:30
digapksingh: we can keep same network for host containers03:31
hongbini think the fix would be adding an option like "zun run --net=xxx nginx ..."03:31
digayeah03:31
pksinghfor time being in auto select can we sort by creation time?03:32
eliqiaohongbin: what if the container have more than 1 nics/network?03:32
hongbinpksingh: yes, that is an option03:32
hongbinpksingh: however, the first created network will be deleted later03:32
hongbinpksingh: so there is no way to pick the same network as before03:32
pksinghok03:33
shu-mutouhongbin: does it not use kuryr for now?03:33
hongbineliqiao: right now, container can have only 1 nic03:33
eliqiaook.03:33
hongbineliqiao: containers with multiple nics is future work03:33
eliqiaogood to know, thx hongbin03:33
*** emagana has quit IRC03:34
hongbinshu-mutou: it use kuryr as a docker network driver03:34
pksinghhongbin: will look into PS today, will put my thoughts there03:34
hongbinpksingh: thx03:34
mkraihongbin: Also do we go and use the next available network, if we have used up all the ips in one network?03:35
shu-mutoudo you mean that available nets are using kuryr?03:35
hongbinmkrai: that might be a good idea, i would leave it as future work03:35
*** iceyao has quit IRC03:35
mkraihongbin: Ok03:36
*** iceyao has joined #openstack-meeting03:36
*** bzhao has quit IRC03:36
hongbinshu-mutou: the available net is a neutron net03:36
hongbinshu-mutou: however, zun passes it to docker and docker calls kuryr-libnetwork to create the container network03:37
shu-mutouhongbin: are they bridged to kuryr nets?03:37
hongbinshu-mutou: kuryr doesn't have network03:37
hongbinshu-mutou: i guess you mean docker net?03:37
shu-mutouah, yes. created by kuryr.03:37
hongbinshu-mutou: docker-net is basically a wrapper of neutron net (if powered by kuryr)03:37
hongbinfrom end-users point of view, they only see the neutron network03:38
hongbindocker network is somehow internal to zun03:38
hongbinok, we need to advance topic for new03:39
hongbinnow03:39
shu-mutouhongbin: thanks. I'll be proceeding more to investigate kuryr.03:39
hongbinplease leave your comments in the review if you have further question03:39
hongbinshu-mutou: ack03:39
hongbin#topic Introduce container composition03:39
*** openstack changes topic to "Introduce container composition (Meeting topic: zun)"03:39
hongbin#link https://review.openstack.org/#/c/437759/03:39
hongbinkevinz: ^^03:39
kevinzHi all03:40
*** links has joined #openstack-meeting03:40
kevinzI've upload all the info (about capsule yaml format, API) to this spec.03:40
kevinzSo it will be great if you can give a review about this :-)03:41
kevinzThe capsule format is mostly like Pod in K8s.03:41
*** iceyao has quit IRC03:42
hongbinyes, the sample yaml file explains the format very well03:43
hongbini like that03:43
*** ekcs has quit IRC03:43
pksinghkevinz: i will try to review by today03:43
kevinzpksingh: Thx a lot03:43
hongbinyes, another big patch to review, i could imagine zun cores will be very busy these weeks :)03:43
mkrai:)03:44
kevinzHaHa03:44
hongbinok, any further question about bp ?03:44
*** Dinesh_Bhor has joined #openstack-meeting03:44
hongbinok, next topic03:45
hongbin#topic Reset the state of container03:45
*** openstack changes topic to "Reset the state of container (Meeting topic: zun)"03:45
hongbin#link https://review.openstack.org/#/c/456172/03:45
*** lamt has quit IRC03:45
hongbini am not sure about this one, want to bring it up to discuss03:45
pksinghi looked into the issue,03:46
hongbinbasically, this patch proposed a command to set the state of the container directly into the db03:46
pksinghas much i know, we can delete any container with force option?03:46
hongbinyes03:46
*** Julien-zte has quit IRC03:47
hongbinpksingh: what do you think about the idea03:48
hongbinpksingh: good idea? bad idea?03:48
pksinghhongbin: i was thinking now we can start/restart container in error state, and we can delete any container using force option03:48
*** Julien-zte has joined #openstack-meeting03:48
pksinghhongbin: i think its not necessary03:48
hongbinpksingh: ack03:48
hongbinmkrai: kevinz what do you think?03:49
mkraihongbin: this sets the state to ?03:49
mkraiI didn't get the use case properly03:49
*** kaisers has joined #openstack-meeting03:49
hongbinbasically, this command can set the container to any state03:49
mkraiI need to look into the spec and will post my thoughts there03:49
hongbinok03:50
*** eliqiao has quit IRC03:50
hongbinthen, let's table this one03:50
kevinzhongbin: if just set status in db, I think I agree with pksingh03:50
hongbinkevinz: ack03:50
hongbinok03:51
pksinghhongbin: why PAUSED state is not there in force delete https://github.com/openstack/zun/blob/master/zun/common/utils.py#L4003:51
*** sridharg has joined #openstack-meeting03:51
pksinghany specific reasons03:51
hongbinpksingh: because docker doesn't allow it03:51
*** mickeys has joined #openstack-meeting03:51
pksinghhongbin: ok03:51
*** lamt has joined #openstack-meeting03:51
mkraiFrom the discussion, it seems it is not making much sense03:52
hongbinok, then i will comment on the patch about that03:52
hongbini am not sure why nova has the reset-state command03:53
*** trinaths has joined #openstack-meeting03:53
*** donghao has joined #openstack-meeting03:53
pksinghhongbin: may we can ask from them and then we take action on our patch03:53
hongbinpksingh: sure03:54
hongbini will ask the nova core i know03:54
pksinghhongbin: that would be great :)03:54
hongbin#topic Open Discussion03:54
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:54
FengShengqinhttps://bugs.launchpad.net/zun/+bug/168201103:55
openstackLaunchpad bug 1682011 in Zun "Check the status of sandbox container" [Undecided,New] - Assigned to <email address hidden> (feng-shengqin)03:55
hongbinall, any other topic that needs a team discussion?03:55
hongbinFengShengqin: reading the bug03:56
FengShengqinneed  check sandbox when check the state of container?03:56
*** lakerzhou has quit IRC03:56
*** mickeys has quit IRC03:58
hongbinthis is odd03:58
*** abhishek_k has joined #openstack-meeting03:58
hongbinif the sandbox is stopped, the real container is supposed to be stopped03:58
hongbinno idea why it still alive03:58
*** donghao has quit IRC03:59
hongbinanyway03:59
hongbinFengShengqin: i need to give it more thoughts03:59
*** sagara has joined #openstack-meeting03:59
*** tpatil has joined #openstack-meeting04:00
hongbinFengShengqin: let's continue the discussion at openstack-zun channel04:00
FengShengqinOK04:00
hongbinall, thanks for joining04:00
*** zhurong has quit IRC04:00
hongbinsee you04:00
hongbin#endmeeting04:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"04:00
*** lamt has quit IRC04:00
openstackMeeting ended Tue Apr 18 04:00:18 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-04-18-03.00.html04:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-04-18-03.00.txt04:00
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-04-18-03.00.log.html04:00
*** himani has left #openstack-meeting04:00
*** shubhams has left #openstack-meeting04:00
*** Julien-zte has quit IRC04:01
*** ykatabam has quit IRC04:01
*** Julien-zte has joined #openstack-meeting04:02
*** tobberydberg has joined #openstack-meeting04:02
*** samP_ has joined #openstack-meeting04:02
*** kaisers has quit IRC04:02
sagarahi04:02
*** samP_ has quit IRC04:03
Dinesh_BhorHi all04:03
tpatilHi04:03
*** ykatabam has joined #openstack-meeting04:03
abhishek_ko/04:03
*** iceyao has joined #openstack-meeting04:03
*** guoshan has quit IRC04:04
*** rkmrHonjo has joined #openstack-meeting04:04
*** aeng has quit IRC04:04
*** samP__ has joined #openstack-meeting04:04
samP__hi..o/04:05
tpatilo/04:05
Dinesh_Bhorhi04:05
rkmrHonjohi04:05
sagaraih04:05
sagarahi04:05
samP__sorry.. I will be bit late.. could some one please start the meeting?04:05
samP__hi all..04:05
samP__for python-masakariclients, pip package versions are fixed..04:06
*** hongbin has quit IRC04:06
rkmrHonjosamP: thanks.04:06
*** tobberydberg has quit IRC04:06
tpatilrkmrHonjo: Do you want to chair today's Masakari meeting?04:07
*** lamt has joined #openstack-meeting04:07
rkmrHonjotpatil: OK, I do it.04:07
*** iceyao has quit IRC04:08
rkmrHonjo#topic High priority items04:08
tpatil#startmeeting masakari04:08
openstackMeeting started Tue Apr 18 04:08:44 2017 UTC and is due to finish in 60 minutes.  The chair is tpatil. Information about MeetBot at http://wiki.debian.org/MeetBot.04:08
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:08
*** openstack changes topic to " (Meeting topic: masakari)"04:08
openstackThe meeting name has been set to 'masakari'04:08
rkmrHonjoOh, sorry...04:08
rkmrHonjo#topic High priority items04:09
rkmrHonjoDo you have high priority items?04:09
tpatilhttps://bugs.launchpad.net/masakari/+bug/166351304:09
openstackLaunchpad bug 1663513 in masakari "Masakari failed to rescue PAUSED instances" [High,In progress] - Assigned to Dinesh Bhor (dinesh-bhor)04:09
*** samP__ has quit IRC04:09
tpatilThere is one minor comment from you on patch https://review.openstack.org/#/c/454721/04:09
rkmrHonjotpatil: yes.04:10
tpatilI don't see that's a big issue, I think Dinesh intention to put instance uuid in single quote is to highlight uuid in the log message which looks good to me04:10
rkmrHonjotpatil: hm...OK, I add +1 to that patch.04:11
*** knangia has quit IRC04:11
tpatilThank you04:11
Dinesh_BhorrkmrHonjo: thanks04:11
*** esberglu has joined #openstack-meeting04:11
rkmrHonjoCan we go to next topic?04:12
tpatilyes04:12
sagarayes04:12
rkmrHonjothanks.04:12
rkmrHonjo#topic Bugs (stuck/critical)04:12
*** lamt has quit IRC04:13
rkmrHonjoThere are some patches that aren't reviewed. Please review if you can. https://review.openstack.org/#/q/project:openstack/masakari04:14
*** lamt has joined #openstack-meeting04:14
rkmrHonjoe.g. Use DDT to reduce test code duplication https://review.openstack.org/#/c/424549/04:14
tpatilSure04:14
*** thorst has joined #openstack-meeting04:15
rkmrHonjotpatil: Thank you.04:15
*** unicell has joined #openstack-meeting04:15
*** lamt has quit IRC04:15
*** esberglu has quit IRC04:15
rkmrHonjoany other bugs?04:15
*** unicell has quit IRC04:16
sagarano04:16
*** gyee has quit IRC04:17
rkmrHonjo#topic Discussion points04:17
rkmrHonjo"recovery method customization" and "Pike work Items" are written on wiki, but wiki was not updated sicne last week.04:17
rkmrHonjoDo you want to discuss about those items?04:17
*** aeng has joined #openstack-meeting04:17
sagaralast week, Sampath-san created a draft version of it.04:18
*** zhurong has joined #openstack-meeting04:18
sagara#link https://etherpad.openstack.org/p/masakari-recovery-method-customization04:18
sagaraI will add it to masakari-spec repo later.04:18
*** unicell has joined #openstack-meeting04:19
*** thorst has quit IRC04:19
tpatilAbhishek has completed a POC to read YAML file in which actions will be added by Operator for each notification type04:19
tpatilthis YAML information will be used to create task workflow04:19
rkmrHonjo#action sagara add masakari-recovery-method-customization spec to masakari-spec repo04:19
rkmrHonjotpatil: Great. Will Abhishek push it to gerrit?04:20
sagararkmrHonjo: thanks04:20
tpatilrkmrHonjo: yes04:20
tpatilHe will cover the specs for the existing workflow in the master code.04:21
tpatilThere are several new action added in the above etherpad url which needs discussion04:21
*** kongwei has joined #openstack-meeting04:21
*** dmacpher has joined #openstack-meeting04:22
tpatilHe will cover all actions added in "Current recovery action in Masakari" section04:23
tpatilSome of the action added "Other possiable recovery actions" are self-explanatory, except last one "triggering crash dump in a server"04:24
rkmrHonjoIs changing host aggregate unnecessary?04:24
*** FengShengqin has quit IRC04:24
*** kongwei has quit IRC04:24
abhishek_ktpatil, rkmrhonjo: As this workflow is configurable, so when operator changes the workflow in configuration file then he needs to restart the engine servuce04:25
*** zhurong has quit IRC04:25
abhishek_ks/servuce/service04:25
tpatilThat can be handled in SIGHUP signal, we can reload the config file by handing this signal04:26
abhishek_ktptil: ok04:27
*** markstur has quit IRC04:27
tpatilrkmrHonjo: host Aggregate code will remain as it is04:27
rkmrHonjotpatil: Is it configurable?04:28
tpatilyes using add_reserved_host_to_aggregate option04:28
rkmrHonjotpatil: ok. thank you for explaining.04:28
*** pksingh has quit IRC04:28
*** ijw has joined #openstack-meeting04:29
rkmrHonjoany other discussions?04:29
*** ricolin_ has joined #openstack-meeting04:31
*** ricolin has quit IRC04:31
tpatiltriggering crash dump in a server: does that mean we should take kernel crash dump of the specified server04:31
rkmrHonjotpatil: Sorry, what is that topic...?04:33
tpatilhttps://etherpad.openstack.org/p/masakari-recovery-method-customization, Line #2404:33
rkmrHonjoAh, I find it in Other possiable recovery actions section.04:33
rkmrHonjotpatil: thanks.04:34
sagaratpatil: I think so, but I think we had better confirming it Sampath-san04:34
*** unicell has quit IRC04:34
tpatilsagara: Ok04:34
*** unicell has joined #openstack-meeting04:35
*** ricolin__ has joined #openstack-meeting04:36
*** yogesh_ has joined #openstack-meeting04:36
rkmrHonjook, let's go to next topic. Please talk in AOB if you have other topics.04:37
rkmrHonjo#topic AOB04:37
*** yogesh_ has quit IRC04:37
rkmrHonjoDo you want to finish this meeting? Or wait for samP until UTC 5:00(=JST 14:00)?04:37
*** ayogi has joined #openstack-meeting04:38
*** ricolin_ has quit IRC04:38
*** bzhao_ has joined #openstack-meeting04:39
*** diga has quit IRC04:40
tpatilWe will discuss with samP on openstack-masakari channel about recovery_method_customization topic04:40
rkmrHonjotpatil: OK. Then can we finish this meeting?04:41
sagarayes04:41
Dinesh_Bhoryes04:42
rkmrHonjoThanks. I finish this meeting after that. Let's go to openstack-masakari channel.04:42
Dinesh_Bhorthank you all04:42
sagarathanks04:42
tpatilThanks04:42
rkmrHonjothanks.04:42
rkmrHonjo#endmeeting04:43
*** mrunge_ is now known as mrunge04:44
*** pksingh has joined #openstack-meeting04:44
tpatilI have to end this meeting as I had started it04:44
tpatil#endmeeting04:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"04:44
openstackMeeting ended Tue Apr 18 04:44:42 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-04-18-04.08.html04:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-04-18-04.08.txt04:44
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-04-18-04.08.log.html04:44
rkmrHonjotpatil: Oh, thank you...04:45
sagaratpatil, rkmrHonjo: I've learned it, thank you04:46
*** ntpttr has quit IRC04:47
*** sagara has quit IRC04:47
*** ntpttr has joined #openstack-meeting04:50
*** lpeer has joined #openstack-meeting04:54
*** mickeys has joined #openstack-meeting04:54
*** bobh has quit IRC04:54
*** mickeys has quit IRC04:59
*** zhurong has joined #openstack-meeting05:01
*** kaisers has joined #openstack-meeting05:03
*** aeng has quit IRC05:07
*** nadya has joined #openstack-meeting05:07
*** tpatil has quit IRC05:08
*** esberglu has joined #openstack-meeting05:08
*** esberglu has quit IRC05:08
*** esberglu has joined #openstack-meeting05:08
*** iyamahat has joined #openstack-meeting05:09
*** esberglu has quit IRC05:13
*** ijw has quit IRC05:14
*** thorst has joined #openstack-meeting05:15
*** rkmrHonjo has quit IRC05:16
*** rkmrHonjo has joined #openstack-meeting05:17
*** sudipto_ has quit IRC05:18
*** sudipto has quit IRC05:18
*** sudipto_ has joined #openstack-meeting05:19
*** sudipto has joined #openstack-meeting05:19
*** jrobinson has quit IRC05:19
*** sudipto_ has quit IRC05:19
*** sudipto has quit IRC05:19
*** nadya has quit IRC05:20
*** thorst has quit IRC05:20
*** aeng has joined #openstack-meeting05:22
*** padkrish has joined #openstack-meeting05:23
*** prateek has joined #openstack-meeting05:23
*** cody-somerville has quit IRC05:26
*** ykatabam has quit IRC05:27
*** ykatabam has joined #openstack-meeting05:27
*** markstur has joined #openstack-meeting05:29
*** markstur has quit IRC05:33
*** gcb has quit IRC05:33
*** huanxuan has quit IRC05:34
*** ricolin__ has quit IRC05:35
*** ricolin has joined #openstack-meeting05:35
*** emagana has joined #openstack-meeting05:41
*** chandankumar has quit IRC05:44
*** emagana has quit IRC05:46
*** gcb has joined #openstack-meeting05:46
*** iyamahat has quit IRC05:46
*** iceyao has joined #openstack-meeting05:47
*** janki has joined #openstack-meeting05:48
*** ntpttr has quit IRC05:50
*** pksingh has quit IRC05:50
*** ntpttr has joined #openstack-meeting05:51
*** VW has quit IRC05:53
*** donghao has joined #openstack-meeting05:57
*** rbartal has joined #openstack-meeting05:57
*** Julien-zte has quit IRC06:00
*** donghao has quit IRC06:02
*** Julien-zte has joined #openstack-meeting06:02
*** rcernin has joined #openstack-meeting06:07
*** sridharg has quit IRC06:07
*** mickeys has joined #openstack-meeting06:10
*** VW has joined #openstack-meeting06:10
*** VW has quit IRC06:11
*** jchhatbar has joined #openstack-meeting06:11
*** janki has quit IRC06:11
*** ntpttr has quit IRC06:11
*** pksingh has joined #openstack-meeting06:11
*** VW has joined #openstack-meeting06:11
*** ricolin_ has joined #openstack-meeting06:11
*** ntpttr has joined #openstack-meeting06:13
*** ricolin has quit IRC06:13
*** mickeys has quit IRC06:14
*** ijw has joined #openstack-meeting06:14
*** ricolin__ has joined #openstack-meeting06:16
*** thorst has joined #openstack-meeting06:16
*** janki has joined #openstack-meeting06:17
*** ntpttr has quit IRC06:18
*** sandanar has joined #openstack-meeting06:18
*** sandanar__ has joined #openstack-meeting06:18
*** jchhatbar has quit IRC06:18
*** ricolin_ has quit IRC06:18
*** matrohon has joined #openstack-meeting06:19
*** reedip_afk has quit IRC06:19
*** swapnil-nilangek has joined #openstack-meeting06:19
*** sandanar__ has quit IRC06:20
*** ntpttr has joined #openstack-meeting06:20
*** adisky_ has joined #openstack-meeting06:20
*** vishnoianil has joined #openstack-meeting06:20
*** cloudrancher has joined #openstack-meeting06:21
*** ijw has quit IRC06:21
*** iceyao has quit IRC06:22
*** cloudrancher has quit IRC06:25
*** sudipto_ has joined #openstack-meeting06:26
*** sudipto has joined #openstack-meeting06:26
*** bkopilov has joined #openstack-meeting06:30
*** jtomasek has joined #openstack-meeting06:30
*** imcsk8 has quit IRC06:31
*** reedip_afk has joined #openstack-meeting06:31
*** Julien-zte has quit IRC06:32
*** jkilpatr has quit IRC06:33
*** ykatabam has quit IRC06:33
*** ykatabam has joined #openstack-meeting06:33
*** Julien-zte has joined #openstack-meeting06:34
*** vishwanathj has quit IRC06:34
*** vishwana_ has joined #openstack-meeting06:34
*** ykatabam1 has joined #openstack-meeting06:34
*** iceyao has joined #openstack-meeting06:35
*** thorst has quit IRC06:36
*** ykatabam has quit IRC06:38
*** pksingh has quit IRC06:38
*** jkilpatr has joined #openstack-meeting06:39
*** makowals has joined #openstack-meeting06:39
*** tesseract has joined #openstack-meeting06:40
*** ltomasbo has joined #openstack-meeting06:42
*** lin_yang has quit IRC06:43
*** bzhao_ has quit IRC06:49
*** ntpttr has quit IRC06:49
*** ntpttr has joined #openstack-meeting06:51
*** mickeys has joined #openstack-meeting06:57
*** pcaruana has joined #openstack-meeting06:59
*** brault has joined #openstack-meeting07:00
*** padkrish has quit IRC07:00
*** ntpttr has quit IRC07:05
*** sridharg has joined #openstack-meeting07:06
*** ntpttr has joined #openstack-meeting07:07
*** treiz has joined #openstack-meeting07:14
*** lpeer has quit IRC07:14
*** pewp has quit IRC07:14
*** ntpttr has quit IRC07:17
*** ntpttr has joined #openstack-meeting07:17
*** pksingh has joined #openstack-meeting07:18
*** ijw has joined #openstack-meeting07:18
*** msimonin has joined #openstack-meeting07:19
*** tobberydberg has joined #openstack-meeting07:20
*** ricolin_ has joined #openstack-meeting07:21
*** ricolin__ has quit IRC07:23
*** ijw has quit IRC07:23
*** ntpttr has quit IRC07:24
*** msimonin has quit IRC07:24
*** ntpttr has joined #openstack-meeting07:25
*** lpeer has joined #openstack-meeting07:26
*** ad_rien_ has joined #openstack-meeting07:27
*** ad_rien_ has joined #openstack-meeting07:27
*** mlakat has joined #openstack-meeting07:27
*** ricolin_ has quit IRC07:28
*** ricolin has joined #openstack-meeting07:28
*** dmacpher has quit IRC07:31
*** ntpttr has quit IRC07:32
*** thorst has joined #openstack-meeting07:32
*** ntpttr has joined #openstack-meeting07:33
*** nadya has joined #openstack-meeting07:34
*** alexchadin has joined #openstack-meeting07:36
*** thorst has quit IRC07:37
*** ntpttr has quit IRC07:38
*** ntpttr has joined #openstack-meeting07:39
*** phil has joined #openstack-meeting07:40
*** phil is now known as Guest6433307:40
*** rkmrHonjo has quit IRC07:42
*** ntpttr has quit IRC07:44
*** ntpttr has joined #openstack-meeting07:45
*** ralonsoh has joined #openstack-meeting07:46
*** ykatabam1 has quit IRC07:49
*** ntpttr has quit IRC07:50
*** swapnil-nilangek has quit IRC07:50
*** ntpttr has joined #openstack-meeting07:51
*** number80 has quit IRC07:52
*** rossella_s has joined #openstack-meeting07:54
*** priteau has joined #openstack-meeting07:55
*** SerenaFeng has joined #openstack-meeting07:56
*** egallen has joined #openstack-meeting07:57
*** donghao has joined #openstack-meeting07:59
*** Julien-zte has quit IRC08:01
*** cody-somerville has joined #openstack-meeting08:03
*** sagara has joined #openstack-meeting08:03
*** ntpttr has quit IRC08:03
*** toscalix has joined #openstack-meeting08:03
*** ntpttr has joined #openstack-meeting08:03
*** donghao has quit IRC08:04
*** ntpttr has quit IRC08:08
*** zhurong has quit IRC08:09
*** ntpttr has joined #openstack-meeting08:09
*** bauwser is now known as bauzas08:12
*** number80 has joined #openstack-meeting08:13
*** iceyao has quit IRC08:13
*** abalutoiu has joined #openstack-meeting08:13
*** iceyao has joined #openstack-meeting08:15
*** dbecker has joined #openstack-meeting08:15
*** iceyao has quit IRC08:17
*** Julien-zte has joined #openstack-meeting08:17
*** litao has joined #openstack-meeting08:17
*** pksingh has quit IRC08:17
*** ntpttr has quit IRC08:17
*** iceyao has joined #openstack-meeting08:18
*** ntpttr has joined #openstack-meeting08:19
*** ijw has joined #openstack-meeting08:20
*** tobberydberg has quit IRC08:20
*** tobberydberg has joined #openstack-meeting08:21
*** epico has quit IRC08:22
*** ijw has quit IRC08:25
*** iceyao has quit IRC08:26
*** zhurong has joined #openstack-meeting08:26
*** sandanar_ has joined #openstack-meeting08:30
*** ntpttr has quit IRC08:33
*** zhhuabj has quit IRC08:33
*** ntpttr has joined #openstack-meeting08:34
*** sandanar has quit IRC08:34
*** baoli has joined #openstack-meeting08:35
*** neiljerram has joined #openstack-meeting08:38
*** ntpttr has quit IRC08:38
*** ntpttr has joined #openstack-meeting08:39
*** baoli has quit IRC08:39
*** litao has quit IRC08:40
*** tobberydberg has quit IRC08:40
*** tobberydberg has joined #openstack-meeting08:41
*** epico has joined #openstack-meeting08:41
*** litao has joined #openstack-meeting08:41
*** tobberydberg has quit IRC08:41
*** tobberydberg has joined #openstack-meeting08:41
*** tobberydberg has quit IRC08:46
*** esberglu has joined #openstack-meeting08:46
*** esberglu has quit IRC08:46
*** zhhuabj has joined #openstack-meeting08:46
*** esberglu has joined #openstack-meeting08:46
*** ntpttr has quit IRC08:48
*** ntpttr has joined #openstack-meeting08:50
*** esberglu has quit IRC08:51
*** newmember has quit IRC08:53
*** newmember has joined #openstack-meeting08:54
*** ntpttr has quit IRC08:56
*** cody-somerville has quit IRC08:57
*** ntpttr has joined #openstack-meeting08:58
*** huanxuan has joined #openstack-meeting08:59
*** janki has quit IRC08:59
*** derekjhyang has quit IRC09:03
*** rossella_s has quit IRC09:03
*** rossella_s has joined #openstack-meeting09:03
*** ykatabam has joined #openstack-meeting09:04
*** kaisers has quit IRC09:07
*** mickeys has quit IRC09:08
*** shintaro has joined #openstack-meeting09:11
*** ntpttr has quit IRC09:11
*** swapnil-nilangek has joined #openstack-meeting09:11
*** ad_rien_ has quit IRC09:12
*** r-mibu has quit IRC09:12
*** ad_rien_ has joined #openstack-meeting09:12
*** janki has joined #openstack-meeting09:12
*** ntpttr has joined #openstack-meeting09:13
*** electrofelix has joined #openstack-meeting09:15
*** sambetts|afk is now known as sambetts09:19
*** ntpttr has quit IRC09:20
*** HeOS has joined #openstack-meeting09:20
*** ijw has joined #openstack-meeting09:21
*** ntpttr has joined #openstack-meeting09:22
*** e0ne has joined #openstack-meeting09:24
*** ijw has quit IRC09:26
*** SerenaFeng has quit IRC09:27
*** sandanar__ has joined #openstack-meeting09:32
*** r-mibu has joined #openstack-meeting09:33
*** Julien-zte has quit IRC09:33
*** thorst has joined #openstack-meeting09:34
*** Julien-zte has joined #openstack-meeting09:34
*** sandanar_ has quit IRC09:36
*** gongysh has joined #openstack-meeting09:37
*** thorst has quit IRC09:38
*** egallen_ has joined #openstack-meeting09:39
*** egallen has quit IRC09:39
*** egallen_ is now known as egallen09:39
*** kiltzman has quit IRC09:41
*** zhurong has quit IRC09:42
*** kiltzman has joined #openstack-meeting09:42
*** kiltzman has joined #openstack-meeting09:43
*** kiltzman has joined #openstack-meeting09:45
*** epico has quit IRC09:45
*** kiltzman has joined #openstack-meeting09:47
*** kiltzman has joined #openstack-meeting09:48
*** kiltzman has joined #openstack-meeting09:49
*** xingchao has quit IRC09:50
*** xingchao has joined #openstack-meeting09:50
*** xingchao has quit IRC09:50
*** egallen has quit IRC09:51
*** vishnoianil has quit IRC09:51
*** epico has joined #openstack-meeting09:54
*** iyamahat has joined #openstack-meeting09:55
*** swapnil-nilangek has quit IRC09:56
*** nadya has quit IRC09:58
*** iyamahat has quit IRC10:00
*** donghao has joined #openstack-meeting10:01
*** VW has quit IRC10:01
*** trinaths has left #openstack-meeting10:03
*** kaisers has joined #openstack-meeting10:03
*** donghao has quit IRC10:06
*** mickeys has joined #openstack-meeting10:08
*** shintaro has quit IRC10:10
*** mickeys has quit IRC10:14
*** huanxuan has quit IRC10:19
*** zhhuabj has quit IRC10:22
*** ijw has joined #openstack-meeting10:23
*** sagara has quit IRC10:23
*** yangyapeng has joined #openstack-meeting10:24
*** kevinz has quit IRC10:25
*** sdague has joined #openstack-meeting10:26
*** ijw has quit IRC10:27
*** nadya has joined #openstack-meeting10:29
*** taowuwen has quit IRC10:31
*** gongysh has quit IRC10:31
*** ntpttr has quit IRC10:32
*** esberglu has joined #openstack-meeting10:34
*** thorst has joined #openstack-meeting10:34
*** alexchadin has quit IRC10:36
*** esberglu has quit IRC10:38
*** ntpttr has joined #openstack-meeting10:39
*** vishnoianil has joined #openstack-meeting10:39
*** thorst has quit IRC10:39
*** zhhuabj has joined #openstack-meeting10:39
*** jkilpatr has quit IRC10:40
*** dasm has left #openstack-meeting10:46
*** nadya has quit IRC10:50
*** nadya has joined #openstack-meeting10:50
*** msimonin has joined #openstack-meeting10:54
*** VW has joined #openstack-meeting10:54
*** VW_ has joined #openstack-meeting10:56
*** jchhatbar has joined #openstack-meeting10:56
*** pksingh has joined #openstack-meeting10:57
*** janki has quit IRC10:59
*** msimonin has quit IRC11:00
*** kaisers has quit IRC11:00
*** VW has quit IRC11:00
*** egallen has joined #openstack-meeting11:00
*** pksingh has quit IRC11:01
*** reedip_ has joined #openstack-meeting11:02
*** arxcruz has quit IRC11:09
*** mugsie has joined #openstack-meeting11:10
*** mugsie has quit IRC11:10
*** mugsie has joined #openstack-meeting11:10
*** mickeys has joined #openstack-meeting11:11
*** zhurong has joined #openstack-meeting11:12
*** jkilpatr has joined #openstack-meeting11:14
*** egallen has quit IRC11:14
*** mickeys has quit IRC11:15
*** janki has joined #openstack-meeting11:23
*** ijw has joined #openstack-meeting11:24
*** arxcruz has joined #openstack-meeting11:24
*** hashar has joined #openstack-meeting11:25
*** Xinran has quit IRC11:25
*** jchhatbar has quit IRC11:25
*** kiltzman has joined #openstack-meeting11:26
*** med_ has quit IRC11:28
*** baoli has joined #openstack-meeting11:28
*** ijw has quit IRC11:29
*** med_ has joined #openstack-meeting11:30
*** med_ is now known as Guest4551211:30
*** epico has quit IRC11:31
*** bkopilov has quit IRC11:33
*** baoli has quit IRC11:34
*** ntpttr has quit IRC11:34
*** baoli has joined #openstack-meeting11:37
*** ntpttr has joined #openstack-meeting11:39
*** ricolin_ has joined #openstack-meeting11:43
*** thorst has joined #openstack-meeting11:43
*** alexchadin has joined #openstack-meeting11:44
*** guoshan has joined #openstack-meeting11:46
*** ricolin has quit IRC11:46
*** tlaxkit has joined #openstack-meeting11:48
*** ricolin__ has joined #openstack-meeting11:50
*** egallen has joined #openstack-meeting11:51
*** ricolin_ has quit IRC11:52
*** kaisers has joined #openstack-meeting11:55
*** bobmel_ has joined #openstack-meeting11:59
*** bobmel has quit IRC12:02
*** mickeys has joined #openstack-meeting12:11
*** mickeys has quit IRC12:16
*** noslzzp has joined #openstack-meeting12:17
*** bobmel has joined #openstack-meeting12:18
*** salv-orlando has joined #openstack-meeting12:19
*** bobmel_ has quit IRC12:21
*** esberglu has joined #openstack-meeting12:24
*** esberglu has quit IRC12:24
*** guoshan has quit IRC12:24
*** guoshan has joined #openstack-meeting12:25
*** ijw has joined #openstack-meeting12:26
*** xingchao has joined #openstack-meeting12:27
*** guoshan has quit IRC12:29
*** guoshan has joined #openstack-meeting12:30
*** gouthamr has joined #openstack-meeting12:31
*** ijw has quit IRC12:31
*** Julien-zte has quit IRC12:33
*** dmacpher has joined #openstack-meeting12:37
*** gongysh has joined #openstack-meeting12:37
*** gongysh has quit IRC12:38
*** rfolco has joined #openstack-meeting12:38
*** gongysh has joined #openstack-meeting12:39
*** gongysh has quit IRC12:40
*** julim has joined #openstack-meeting12:41
*** ayogi has quit IRC12:41
*** pchavva has joined #openstack-meeting12:43
*** lamt has joined #openstack-meeting12:44
*** guoshan has quit IRC12:45
*** xingchao has quit IRC12:45
*** zhurong has quit IRC12:45
*** lamt has quit IRC12:46
*** dimtruck is now known as zz_dimtruck12:49
*** kylek3h has joined #openstack-meeting12:50
*** askb has quit IRC12:51
*** baoli has quit IRC12:54
*** timello has joined #openstack-meeting12:56
*** egallen has quit IRC12:56
*** egallen has joined #openstack-meeting12:58
*** gcb has quit IRC13:00
Qiming#startmeeting senlin13:01
openstackMeeting started Tue Apr 18 13:01:00 2017 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: senlin)"13:01
openstackThe meeting name has been set to 'senlin'13:01
*** esberglu has joined #openstack-meeting13:01
*** XueFeng has joined #openstack-meeting13:01
*** egallen_ has joined #openstack-meeting13:01
*** elynn has joined #openstack-meeting13:02
XueFenghi,all13:03
elynno/13:03
Qiminghi13:04
*** egallen has quit IRC13:04
*** egallen_ is now known as egallen13:04
Qimingyanyan just texted me that he won't be able to join us today13:04
XueFengok13:04
*** sudipto has quit IRC13:04
*** sudipto_ has quit IRC13:04
*** xyang1 has joined #openstack-meeting13:04
Qiming#topic pike work items13:05
*** openstack changes topic to "pike work items (Meeting topic: senlin)"13:05
Qiminglet's get started13:05
Qiming#link https://etherpad.openstack.org/p/senlin-pike-workitems13:05
*** cloudrancher has joined #openstack-meeting13:05
XueFengok13:05
QimingAPI version conversion bug has been fixed13:05
Qimingso .. I'm removing that item13:06
QimingVDU profile i.e. feature rich server13:06
Qimingany update, elynn ?13:06
elynnNo update...13:06
elynnhaven't got time to do it...13:06
Qimingokay13:06
elynnI will try to upload patches before summit13:07
Qimingcluster check redesign, no progress afaik13:07
XueFengyes, Qiming13:07
XueFengdebug tacker+senlin13:07
XueFengthese day13:07
Qimingnode adopt, two patches for review13:07
XueFengwith xuhaiwei13:08
XueFengok, will review13:08
Qiminggood, you may want to write another article when the integration is done, :)13:08
*** VW_ has quit IRC13:08
XueFengand CMCC yaofenghua send a mail to me13:08
XueFengabout node adopt the also need13:09
Qimingfrom suzhou or beijing?13:09
XueFenghaha,Qiming, yes13:09
XueFengWe will write13:09
Qimingcool, will be good news for NFV users13:09
XueFengMaybe suzhou13:09
*** jamesdenton has joined #openstack-meeting13:10
Qimingalright, pls help review the two patches13:10
XueFengok, I will:)13:10
*** mriedem has joined #openstack-meeting13:10
Qimingthen I'll proceed on the api level changes13:10
Qimingscaling improvements, mostly by ruijie13:10
*** lixinhui has joined #openstack-meeting13:11
lixinhuihi13:11
Qiminghaven't heard a thing from him13:11
XueFenghi,xinhui13:11
Qimingoh, our godess finally shows up13:11
lixinhuiSorry for the late dail in13:11
elynnhaha13:11
lixinhui:)13:11
XueFengruijie also have serval patches need to be review13:12
Qimingwe are on senlin pike work items, https://etherpad.openstack.org/p/senlin-pike-workitems13:12
*** mickeys has joined #openstack-meeting13:12
*** xingchao has joined #openstack-meeting13:13
QimingI think I have left comments to most of his patches if not all13:13
*** baoli has joined #openstack-meeting13:13
XueFengyes13:13
XueFengI also reviewed some of them:)13:14
*** egallen has quit IRC13:14
Qimingabout adding health check before deletion or scaling, I think we have reached a common understanding13:14
XueFengYes, the cluster.health_check has been merged13:15
Qiminghe was tring to do the invocation from policy side, while I am more inclined to make them part of the node logics13:15
Qimingyes13:15
*** ykatabam has quit IRC13:15
Qimingthe policy decides whether health should be checked, but the actual check logic still should be part of cluster_action or node_action13:16
Qimingthat was something we have spent time digging into13:16
QimingI believe he is still on it these days13:16
*** mickeys has quit IRC13:16
Qimingmoving on13:16
Qimingnext thing is about RDO13:17
XueFengSo this pathch still need updte https://review.openstack.org/#/c/456453/13:17
XueFengNo update for RDO this week13:17
* Qiming is looking13:17
Qimingright, XueFeng, that one should be reworked13:17
XueFengOk, I got the point you mentioned13:18
QimingI believe he was more affected by the load-balancing policy, where we embedded many operations into the policy itself13:18
XueFengyes13:18
Qiminghowever, our design philosophy for polices are just some rules to be checked/enforced before/after action execution13:19
Qimingit doesn't mean policies should intiate some operations on physical resources unless the policy is owning that resource, e.g. lb policy13:19
Qimingnext thing13:20
Qiminghealth management13:20
Qimingtwo patches about workflow support are in now13:20
Qimingneed to enable them in health policy and recover action13:20
QimingI have moved the logic from nova server up, to the general node level13:21
Qimingbecause I think workflows are generic enough to invoke many openstack services13:21
XueFengok13:22
Qimingxinhui approved that change13:22
XueFeng:)13:22
*** lakerzhou has joined #openstack-meeting13:22
*** prateek has quit IRC13:22
*** egallen has joined #openstack-meeting13:22
QimingI have moved the load-balancer check and event emitting work back to FEATURES.rst, if you haven't noticed13:22
Qimingthis is a sad move13:22
Qimingwe hoped that Octavia is open to such a change13:23
XueFengI know that13:23
Qiminghowever, ... things didn't go smooth although I know xinhui and friends have tried hard on that13:23
Qimingthe whole thing has been there for one year, no comment to the BP, no comment to the patch13:23
XueFengMaybe we can have another choice to do this thing13:24
*** davidsha has joined #openstack-meeting13:24
Qimingif BP is not approved, patch won't be reviewed, (according to one of the reviewers)13:24
Qimingwe really don't want to do ping or HTTP get by ourselves13:24
XueFengen13:24
Qimingit is not a big deal from implementation's perspective13:24
Qimingjust we don't want to reinvent the wheel, let the right service do the right thing13:25
Qimingwe want to be good citizen13:25
XueFengright13:25
Qiminganyway, we can live with it13:25
Qimingwhen we get more urgent requests, we can quickly stand up our own version of health checking13:26
lixinhuiyes, Qiming13:26
Qimingthe only barrier is that we need a place to issue the ping or HTTP GET call13:27
Qimingthat 'place' must be on the external subnet13:27
*** pcaruana has quit IRC13:27
*** ijw has joined #openstack-meeting13:27
*** haleyb has joined #openstack-meeting13:27
Qimingping the nodes from private subnet is not optimal, but it is better than nothing13:28
Qimingmoving on13:28
XueFengok13:28
Qimingtempest test13:28
Qimingthe local test for non-admin account is done, XueFeng ?13:28
XueFengYes13:29
Qimingcool13:29
XueFengI think so13:29
XueFeng:)13:29
QimingI'm seeing that the whole patch is not breaking the gate13:29
XueFengYes13:29
Qimingbravo13:29
XueFengWe also can pass in local13:29
*** cloudrancher has quit IRC13:29
Qimingwe have not yet started senlinclient functional tests13:29
XueFengfor 21:25 < Qiming> just we don't want to reinvent the wheel, let the right service do the right thing13:29
XueFengyes13:30
XueFengno13:30
*** eharney has quit IRC13:30
XueFengno time to to it now13:30
Qiming?13:30
XueFengto do13:30
XueFengIt's priority is low13:31
XueFengAbout senlinclinet I think13:31
Qimingquestions on my previous sentence?13:31
XueFengSo we need do senlin+tacker firslty13:31
Qimingokay13:31
Qimingjust from service/client stability's point of view13:32
*** ijw has quit IRC13:32
Qiminghaving functional tests there will ensure that any breaking changes between the server/client will bubble up quickly13:32
XueFengyes13:32
Qiminge.g. changes to sdk13:32
*** bkopilov has joined #openstack-meeting13:33
*** tobberydberg has joined #openstack-meeting13:33
Qimingsometimes break us in an unnoticeable way13:33
XueFengYes, it is necesary13:33
Qimingnext thing is about cluster-recover improvement for lb policy13:34
QimingI know ruijie still have some ideas to improve it13:34
Qimingso we'd better leave that item there13:34
Qimingbesides items on the etherpad13:34
QimingI'm looking into the performance overhead problem13:34
XueFengWe can add to etherpad13:34
*** links has quit IRC13:35
XueFengSome patches about these need review as well13:35
*** cloudrancher has joined #openstack-meeting13:35
XueFengThis one13:35
Qimingelynn previously reported that scaling a cluster takes time13:35
XueFenghttps://review.openstack.org/#/c/455151/13:35
Qimingit is mostly related to the cluster.rt and node.rt13:36
elynnyes13:36
*** Jeffrey4l has joined #openstack-meeting13:36
Qimingwe instantiate Cluster and Node instances13:36
Qimingeach instantiation of a Node in turn instantiates a Profile ...13:36
Qimingwhen revisiting the code, my feeling is that we can avoid db calls in many places13:37
XueFengelynn, give a bug link13:37
*** egallen has quit IRC13:37
*** cloudrancher has quit IRC13:37
Qimingwe can even avoid instantiate nodes and still break nothing13:37
Qimingjust populate cluster.rt['nodes'] with senlin.objects.node.Node instance is enough13:37
elynnhttps://bugs.launchpad.net/senlin/+bug/167726813:38
openstackLaunchpad bug 1677268 in senlin "scale-out API will take a long time to response when too many nodes in a cluster" [High,Triaged] - Assigned to Ethan Lynn (ethanlynn)13:38
Qimingand that operation takes only one ovo call13:38
Qimingif we still have performance problems, we can take a further step, recording only node ids in the runtime data13:38
QimingI'm not referencing that bug number in my patches13:39
Qimingalthough ... they are actually remotely related13:39
Qiminge.g. https://review.openstack.org/#/c/457493/13:40
elynn:) I concern if these series of patches can back port to ccata...13:40
Qimingthis one: https://review.openstack.org/#/c/457508/13:40
Qimingpatch 457508 directly exposes profile.created_at into node dict, so that we don't need to visit node.rt['profile'] when searching nodes with the oldest profile13:41
Qimingwe can use ovo Node object in cluster.rt['nodes']13:42
Qimingwill propose related patches to get this whole thing done13:42
*** tobberydberg has quit IRC13:43
Qimingem, I self appoved #45749313:43
Qiming:P13:43
Qimingit is in now13:43
XueFenghh13:43
elynngreat13:43
lixinhuicool13:43
Qimingthat's all for pike work items so far13:43
Qimingmoving on13:43
Qiming#topic boston summit prep13:44
*** openstack changes topic to "boston summit prep (Meeting topic: senlin)"13:44
Qimingwhere are we?13:44
Qimingour godess?13:44
*** tobberydberg has joined #openstack-meeting13:45
QimingXueFeng, yours?13:45
XueFengMay 1113:45
XueFengafternoon13:45
QimingI mean how are the preparation now?13:46
Qimingdo you need any help?13:46
*** cleong has joined #openstack-meeting13:46
XueFenghttps://review.openstack.org/#/c/449471/13:46
*** iceyao has joined #openstack-meeting13:47
XueFengIn tacker ,this patch is in review13:47
Qimingyes?13:47
*** tobberydberg has quit IRC13:47
XueFengAnd about demo13:47
XueFengdebuging13:47
Qimingokay13:48
*** emagana has joined #openstack-meeting13:48
*** VW has joined #openstack-meeting13:48
XueFengWe can deploy VNF from tacker+heat+senlin13:48
Qimingdo you guys think it necessary to spend some time together, maybe later this week or early next week for a face to face discussion?13:48
XueFengAnd now we change to the real image13:49
*** lamt has joined #openstack-meeting13:49
Qimingya, an imporant step13:49
*** jprovazn has joined #openstack-meeting13:49
*** zhonghua has quit IRC13:50
XueFengI can come13:50
Qimingby the way, yanyan is being relocated to Singapore13:50
lixinhuiI am on-site service these days13:50
lixinhuiI heard about that13:50
lixinhuihappy for him13:50
*** zhonghua has joined #openstack-meeting13:50
Qimingwe are "cheaping hime away"13:50
*** hongbin has joined #openstack-meeting13:50
Qimingjian4 xing213:51
lixinhuiwe should dinner together before his leaving13:51
*** ntpttr has quit IRC13:51
XueFenghaha13:51
Qimingem, he told us not to mention this to anyone, and he at the same time has already told everyone, :D13:51
elynnglad he have a better future13:52
*** zhonghua has quit IRC13:52
elynnhaha13:52
*** ntpttr has joined #openstack-meeting13:52
XueFengwhat is jian4 xing2?13:52
*** zhonghua has joined #openstack-meeting13:53
Qiming贱行, in Chinese13:53
XueFengoh:)13:53
Qiming#topic open discussion13:54
lixinhui豁出去了13:54
*** openstack changes topic to "open discussion (Meeting topic: senlin)"13:54
lixinhui不减肥了13:54
*** Julien-zte has joined #openstack-meeting13:54
Qimingif you need any helps on preparing the talks, you can reach out to the team13:54
elynn13:54
Qimingyou were never on that direction as far as I know it13:54
lixinhui...13:55
Qiming*never*13:55
elynnNice job13:55
lixinhuiWill send out a draft agenda for your comments13:55
Qimingtop priorities in life: 1 eat, 2 eat, 3 goto 113:56
Qimingokay13:56
QimingI'm mostly stuck by Go and k8s these days13:56
Qimingit is a bigger ... mess13:56
XueFenghhh13:56
lixinhuiyou need more coffee13:56
XueFengQiming13:57
Qimingno .... I need more sleep, seriously13:57
*** hoangcx has joined #openstack-meeting13:57
XueFengAnother thing13:57
Qimingmy girl is too naughty13:57
* Qiming listening13:57
XueFengCan senlin run in openstak K version13:58
Qimingnot quite sure, but we did successfully get it up in Juno13:58
*** ataraday_ has joined #openstack-meeting13:58
Qimingyou need to mind the sdk version used13:58
lixinhuiXueFeng13:58
lixinhuiSenlin can13:58
XueFengok13:59
XueFenggood news13:59
lixinhuiI once tried and ran up senlin with VIO K version13:59
Qimingwe are not bound to any specific version of any services, except for sdk13:59
Qimingthanks for the confirmation, xinhui13:59
lixinhuimy pleasure13:59
Qimingwe are running out of time, thanks for joining, boys and girls13:59
Qiminggood night13:59
XueFengOk, if need in K version, will ask you guys13:59
Qimingsure14:00
Qiming#endmeeting14:00
XueFenggood night14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Tue Apr 18 14:00:08 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-04-18-13.01.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-04-18-13.01.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-04-18-13.01.log.html14:00
*** abhishek_k has left #openstack-meeting14:00
igordcard#startmeeting network_common_flow_classifier14:00
openstackMeeting started Tue Apr 18 14:00:16 2017 UTC and is due to finish in 60 minutes.  The chair is igordcard. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: network_common_flow_classifier)"14:00
openstackThe meeting name has been set to 'network_common_flow_classifier'14:00
davidshaHey14:00
igordcardhey davidsha14:00
igordcardhi all14:00
*** VW has quit IRC14:00
*** VW has joined #openstack-meeting14:00
bcafarelhowdy14:00
*** lixinhui has quit IRC14:01
igordcardwhat's up bcafarel14:01
*** sandanar__ has quit IRC14:01
*** dprince has joined #openstack-meeting14:01
igordcardagenda:14:01
igordcard#link https://wiki.openstack.org/wiki/Neutron/CommonClassificationFramework#Discussion_Topic_18_April_201714:01
reedip_o/14:01
*** kevinz has joined #openstack-meeting14:01
igordcardhi reedip_14:02
davidshahey14:02
*** elynn has quit IRC14:02
igordcardlet's dive in14:02
*** VW has quit IRC14:02
igordcard#topic Closing the spec14:02
*** openstack changes topic to "Closing the spec (Meeting topic: network_common_flow_classifier)"14:02
*** lamt has quit IRC14:02
igordcarda new spec was uploaded:14:02
*** VW has joined #openstack-meeting14:02
igordcard#link https://review.openstack.org/#/c/333993/1414:02
*** pksingh has joined #openstack-meeting14:03
igordcardbut I've set W-1 recently to rework the database schema again14:03
*** nadya has quit IRC14:04
igordcardit has come to my attention that the AND/ORing of classifications isn't particularly easy for some basic scenarios, and that the fixed nature of the qos-inspired model makes it difficult to make that easy or make changes in the future14:04
*** priteau has quit IRC14:04
*** eharney has joined #openstack-meeting14:05
igordcardI'm interested in knowing more about what makes base/child classifications create problems when using OVO14:05
*** lamt has joined #openstack-meeting14:05
*** Guest45512 is now known as med_14:05
*** med_ has quit IRC14:05
*** med_ has joined #openstack-meeting14:05
igordcardsee comment at line 236 of:14:06
igordcard#link https://review.openstack.org/#/c/333993/13/specs/pike/common-classification-framework.rst14:06
davidshaIhar seems to be offline and he'd be the expert.14:06
igordcarddavidsha: yep probably the best is to reach out to him and ask for more details - I don't want us to commit to a model that will bring us deep trouble with OVO, but would like to have this flexible enough14:07
*** reedip_ has quit IRC14:07
igordcardapart from that, after the change regarding the schema (that will be up today), I believe the spec is essentially done14:07
*** ntpttr has quit IRC14:07
*** sudipto_ has joined #openstack-meeting14:08
*** sudipto has joined #openstack-meeting14:08
*** reedip has joined #openstack-meeting14:08
*** cloudrancher has joined #openstack-meeting14:08
davidshathat's good.14:08
*** ntpttr has joined #openstack-meeting14:08
*** pcaruana has joined #openstack-meeting14:10
bcafarelkind of same comment as the db, in REST api I did not see how to get the sub groups for a CG14:10
igordcardbcafarel: there are no "sub groups", what do you expect them to be?14:10
*** cloudran_ has joined #openstack-meeting14:11
*** zz_dimtruck is now known as dimtruck14:11
bcafareligordcard: sorry I may still be catching up on these, the terminology says a CG is a grouping Classifications, or other Classification Groups14:12
*** kevinz has quit IRC14:13
bcafarelso I was seeing it as visible in the group itself (as "sub groups")14:13
bcafarelor is it just up to the service to implement the logic?14:13
*** cloudran_ has quit IRC14:13
*** tobberydberg has joined #openstack-meeting14:13
*** kevinz has joined #openstack-meeting14:14
*** jaugustine has joined #openstack-meeting14:14
igordcardbcafarel: nice catch!14:14
*** cloudran_ has joined #openstack-meeting14:14
igordcardbcafarel: seems I wrote that while I still a different model in mind (which I will likely bring back on the next patchet)14:14
igordcard* while I still had a14:15
*** cloudrancher has quit IRC14:15
*** ricolin__ has quit IRC14:15
igordcardwhat I'm thinking is that groups can include other groups14:15
igordcardthat way, you can indeed mix and match ORs and ANDs14:15
*** ntpttr has quit IRC14:15
*** number80 has quit IRC14:16
*** dandruta has joined #openstack-meeting14:16
igordcardso you can say "match on this ip address, OR that ip address, AND make sure either is tcp port 80 traffic"14:16
igordcardthis would be an AND-group made of 1 classification and 1 OR-group14:17
igordcardwith the OR-group having 2 classifications inside14:18
*** kjw3 has joined #openstack-meeting14:18
*** awaugama has joined #openstack-meeting14:18
*** ntpttr has joined #openstack-meeting14:18
bcafarelack, that was what I had in mind14:19
bcafarelif that is for a later patchset no problem then :)14:19
igordcardin terms of the database schema this should be neat and easy to model, but I have to investigate a bit more the API and OVO consequences14:19
igordcardbcafarel: yeah I'll post something today14:20
igordcardbcafarel: but the current patchset only has single-level grouping of either all-AND or all-OR14:21
igordcardand if a CS wanted, it could consume multiple groups to create complex expressions14:21
igordcardseems I don't have a topic for the PoC, so I will integrate it14:22
igordcarddavidsha: how's it going?14:22
igordcardintegrate it *here14:22
davidshaigordcard: Going well, I'm just filling out the PoC at the moment. I'm starting looking into the classification groups as well but only very early stuff.14:23
davidshaLess Pep8 fails for sure anyways :P14:23
igordcardgreat14:24
igordcardthe classification groups is the core open debate right now14:24
igordcardwe start implemeting too early and we'll end up wasting effort if we can't get enough agreement on the spec14:24
*** number80 has joined #openstack-meeting14:25
*** felipemonteiro has joined #openstack-meeting14:25
*** tobberydberg has quit IRC14:25
igordcardso please, all review the spec after the next patchset (due today) so we can more confidently implement a grouping model14:25
davidshaack14:26
igordcardI'll talk to Ihar about the OVO issue14:26
reedipack14:26
igordcardmoving on14:26
igordcard#topic Rights to the/a repo14:26
*** openstack changes topic to "Rights to the/a repo (Meeting topic: network_common_flow_classifier)"14:26
igordcardfor context:14:26
igordcard#link https://bugs.launchpad.net/neutron/+bug/147652714:26
openstackLaunchpad bug 1476527 in neutron "[RFE] Add common classifier resource" [Wishlist,Triaged] - Assigned to Igor Duarte Cardoso (igordcard)14:26
*** tobberydberg has joined #openstack-meeting14:26
igordcardso with agreement on the spec we can be given a repo and a subteam to work on and merge the code14:28
*** lakerzhou has quit IRC14:28
*** tobberydberg has quit IRC14:28
*** ijw has joined #openstack-meeting14:29
igordcardit's probably going to be neutron/classifier and me + davidsha  as the initial team (spec and poc authors respectively), we can then grow the team as other dedicated contributors arrive14:29
davidshaack14:29
*** fnaval has joined #openstack-meeting14:29
igordcardwhile there's no clear agreement on the spec, I'll simply wait until any of the cores review the spec and decide to give us the repo/rights14:31
igordcardonce we have agreement I will actively ping them to set this up14:31
reedipigordcard : subteam is a good idea14:31
*** baoli has quit IRC14:32
igordcardgood good14:33
*** baoli has joined #openstack-meeting14:33
igordcardalright, moving on..14:33
igordcard#topic Open discussion14:33
*** rossella_s has quit IRC14:33
*** openstack changes topic to "Open discussion (Meeting topic: network_common_flow_classifier)"14:33
igordcardwhatever you folks want to chat about14:34
*** rossella_s has joined #openstack-meeting14:34
*** ijw has quit IRC14:34
*** unicell1 has joined #openstack-meeting14:34
*** unicell has quit IRC14:34
bcafarelexcept the weather14:34
davidshaNaturally :P14:35
bcafarelI still have to look at the poc (now that I am back up to date on the spec), sorry been busy elsewhere14:35
igordcardwhere's free speech? :'(14:35
*** janki has quit IRC14:35
bcafarelok weather topics allowed then :)14:35
*** fnaval has quit IRC14:35
*** kaisers has quit IRC14:36
davidshaI was hoping to have another PS for the classifier up by the end of the week, but It will probably be a bit off while I wait for the dust to settle around classification_groups.14:36
igordcarddavidsha: yeah... I might ping the most prominent voices around classification grouping after I submit my new PS14:37
davidshaigordcard: ack14:37
*** baoli has quit IRC14:38
igordcardwe'll never totally agree on the grouping, but I'm hoping we can at least have a solution with no major drawbacks14:38
davidshak14:38
*** sudipto_ has quit IRC14:38
*** sudipto has quit IRC14:38
igordcardhaving said that my biggest concern is really the OVO issue at this point14:38
*** eharney has quit IRC14:38
*** lpeer has quit IRC14:38
*** zhonghuali has joined #openstack-meeting14:39
*** tobberydberg has joined #openstack-meeting14:39
*** dprince has quit IRC14:39
igordcardbcafarel: any plans on turning networking-sfc into a CS?14:40
*** baoli has joined #openstack-meeting14:40
*** zhonghuali has quit IRC14:40
bcafareligordcard: climbing up the todo list, I'd like to get at least some minimal poc up soon14:41
igordcardbcafarel: oh great!14:41
bcafarel(when the unit tests stop breaking during the week-ends)14:41
*** alexchad_ has joined #openstack-meeting14:41
igordcardbcafarel: one of the things I forgot in the spec was to add ip/mac addr masks.. possibly there are other gaps there (when comparing to the Flow Classifier)14:42
*** chenhuayi has joined #openstack-meeting14:43
igordcardbcafarel: if I don't fix all the gaps, please leave a comment there14:43
*** alexchadin has quit IRC14:43
*** markstur has joined #openstack-meeting14:43
bcafareligordcard: oh ok noted, I did not check thoroughly the details in the type tables14:45
igordcardbtw, stealing the topic from the fwaas meeting - who is going to the summit?14:45
igordcardI wasn't originally going to, but am now14:45
*** alexchadin has joined #openstack-meeting14:45
davidshaI'm not, good luck with the trip!14:46
*** noslzzp has quit IRC14:46
*** nadya has joined #openstack-meeting14:46
*** iceyao has quit IRC14:47
*** alexchad_ has quit IRC14:47
bcafarelI won't go either, we count on you to market the CCF concept!14:48
*** fnaval has joined #openstack-meeting14:49
igordcard:(14:49
*** alexchadin has quit IRC14:50
bcafarelI wonder how many engineers will turn up at the summit in the end (it is the first one after the PTG split)14:50
reediplol igordcard :)14:50
igordcardare you reedip ?14:51
reedipNOPE ...14:51
reedipI have more dangerous missions to go through :)14:51
*** tobberydberg has quit IRC14:51
*** anilvenkata has quit IRC14:53
*** eharney has joined #openstack-meeting14:53
*** markstur has quit IRC14:54
*** mickeys has joined #openstack-meeting14:54
*** chenying_ has joined #openstack-meeting14:55
*** zhonghuali has joined #openstack-meeting14:58
*** mickeys_ has joined #openstack-meeting14:58
igordcardalright dear contributors, let's finish the meeting14:58
igordcardbye all14:58
igordcard#endmeeting14:59
*** mickeys has quit IRC14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Tue Apr 18 14:59:07 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-04-18-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-04-18-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2017/network_common_flow_classifier.2017-04-18-14.00.log.html14:59
*** tobberydberg has joined #openstack-meeting14:59
*** kevinz has quit IRC15:00
*** ianychoi has quit IRC15:00
*** hoangcx has quit IRC15:00
*** baoli has quit IRC15:00
chenying_#startmeeting karbor15:01
openstackMeeting started Tue Apr 18 15:01:02 2017 UTC and is due to finish in 60 minutes.  The chair is chenying_. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: karbor)"15:01
openstackThe meeting name has been set to 'karbor'15:01
*** shintaro has joined #openstack-meeting15:01
chenying_hi15:01
zhonghualihi15:01
chenhuayihi15:01
chenying_Hi all, welcome to Karbor's weekly meeting15:01
*** baoli has joined #openstack-meeting15:01
chenying_#topic Open Discussion15:02
*** openstack changes topic to "Open Discussion (Meeting topic: karbor)"15:02
*** tobberydberg has quit IRC15:02
chenying_There is no topic on the agenda right now, Do you have anything want to talk about ?15:02
*** lpeer has joined #openstack-meeting15:02
zhonghualinothing to me15:03
chenying_chenhuayi  about th work OpenStack Ansible15:03
chenying_, do you have any progress?15:03
*** timello has quit IRC15:04
*** noslzzp has joined #openstack-meeting15:04
chenying_ping chenhuayi15:05
*** tobberydberg has joined #openstack-meeting15:05
chenhuayichenying_, proxy setting still have problem.15:05
*** davidsha has left #openstack-meeting15:06
*** iyamahat has joined #openstack-meeting15:06
*** donghao has joined #openstack-meeting15:06
chenying_If the work can not continued because of the network, we can suggest that yuval could do this wokr.15:06
zhonghualithat may be a trouble15:06
*** pksingh has quit IRC15:06
chenhuayiI will have another shoot tommorow.15:06
chenying_S/wokr/work.15:06
chenhuayihttps://blog.christophersmart.com/2016/08/09/setting-up-openstack-ansible-all-in-one-behind-a-proxy/15:06
chenhuayifollow this link, hope will work tommorow.15:07
chenying_It can not be installed without proxy?15:07
chenhuayithe proxy setting need some changes.15:07
*** tobberydberg has quit IRC15:07
chenhuayiyeah, proxy is needed.15:08
zhonghualichenhuayi, what's the main question, it does not work or it works slowly15:08
chenhuayiit does not wor15:08
*** jiaopengju has joined #openstack-meeting15:08
chenhuayik15:08
chenhuayiit can't reach the resource.15:08
*** rcernin has quit IRC15:09
zhonghualiohh15:09
chenying_oh I know.15:09
chenying_the config of proxy is not ok?15:09
chenhuayimay it will work well next time.15:09
chenhuayitoday i had try once. but the proxy setting is some diff from the link told.15:10
*** edtubill has joined #openstack-meeting15:11
*** iyamahat has quit IRC15:11
*** tobberydberg has joined #openstack-meeting15:11
jiaopengjuhi15:11
*** iyamahat has joined #openstack-meeting15:11
chenying_hi jiaopengju  welcome.15:12
*** donghao has quit IRC15:12
chenying_Do you have anything want to talk about - now is the time15:12
jiaopengjuhow about file backup in vm?15:13
chenying_I am thinking about this scene.15:14
*** iceyao has joined #openstack-meeting15:14
chenying_The common scene about the file in vm, we think that the file is writed in the manila share.15:15
zhonghualichenying_,do you mean share?15:15
*** bobmel_ has joined #openstack-meeting15:16
chenying_Yes in the above scenem we can consider backup the share.15:16
*** kevinz has joined #openstack-meeting15:16
zhonghualijiaopengju, could you please explain more case from you here?15:16
jiaopengjuI think manila share is one use case15:16
*** ntpttr has quit IRC15:17
*** tobberydberg has quit IRC15:17
zhonghualiwhat's your case15:17
jiaopengjucurrently, most openstack environment do not use manila15:18
chenying_if the file is writed in mounted volume in the vm, this scene only backup this file, that mean we may need a backup tool(like a agent in the vm) to backup this file.15:18
*** tobberyd_ has joined #openstack-meeting15:18
*** ntpttr has joined #openstack-meeting15:19
*** eharney has quit IRC15:19
*** iceyao has quit IRC15:19
*** bobmel has quit IRC15:19
*** tobberyd_ has quit IRC15:20
jiaopengjuyes15:20
*** tobberydberg has joined #openstack-meeting15:20
*** kevinz has quit IRC15:21
chenying_one solution introducing a opensource backup software, deploy the agent to this vm to backup the file. what's your opinion about it?15:21
zhonghualichenying_, do you think the agent is one part of Karbor?15:21
chenying_zhonghuali I don't think so.15:22
jiaopengjuit's a solution, but it is difficult to manage the file uniformly as volumes or nova instances15:22
*** pksingh has joined #openstack-meeting15:22
chenying_jiaopengju  that may be the quesiton. The file is not managed my openstack directly like the volume or share.15:23
chenying_S/my/by15:23
zhonghualiso karbor only contains the plugin of open source backup,am I right?15:23
jiaopengjuI guess you are right.15:24
*** xingchao has quit IRC15:25
chenying_introducing a opensource backup software to karbor to backup the file is one optional  solution, but we also need think carefully about it.15:25
*** ntpttr has quit IRC15:25
zhonghualiwhat's yuval's opinion on this?15:26
chenying_If use  this one, that mean evey vm need deply the agent one by one to backup the file, it may be unacceptable.15:26
jiaopengjuIt's difficult to choice about using open source backup software directly or using karbor to manage the backups uniformly.15:27
chenying_yuval suppose one use case, restore the file from the backup of volume.15:28
*** ataraday_ has quit IRC15:28
chenying_But we may talk about this use case about backuping file in vm with him next time.15:28
zhonghualianother question is who will do the deployment work? user or manager?15:28
*** ntpttr has joined #openstack-meeting15:29
zhonghualichenying_, +115:29
jiaopengjuI think the vm user will do the deployment work.15:29
chenying_using karbor to manage the backups uniformly---- the file is not managed by openstack, it may be difficult for karbor.15:30
*** Guest64333 has quit IRC15:30
jiaopengjuI means the backups, not file in vm15:30
*** scottda has joined #openstack-meeting15:30
*** ijw has joined #openstack-meeting15:30
*** cloudran_ has quit IRC15:31
*** donghao has joined #openstack-meeting15:31
*** felipemonteiro has quit IRC15:31
*** nadya has quit IRC15:32
*** kaisers has joined #openstack-meeting15:32
*** cloudrancher has joined #openstack-meeting15:32
chenying_we can manage the backups of file like the volume, when backup a file and produce a checkpoint records.15:32
*** abalutoiu has quit IRC15:32
*** kaisers has quit IRC15:34
*** kaisers has joined #openstack-meeting15:34
zhonghualiwhat i am thinking about is where to find the backup targets?15:35
*** ijw has quit IRC15:35
chenying_you mean that get the file list resouces want to backup?15:36
chenying_ how to get the file resouces in the vm?15:36
zhonghualiit is the same question as chenying_ said. the files don't manage by OpenStack15:36
zhonghualichenying_, yes15:37
chenying_jiaopengju can you give some use case about backuping the file in the vm from the view of user?15:38
jiaopengjuI think the targets is the vms with open source backup software deployed. When users using file backup, he should configure the backup path or some ohter info?15:38
*** eharney has joined #openstack-meeting15:38
*** swapnil-nilangek has joined #openstack-meeting15:39
jiaopengjuA simple scene, A vm user want to backup the config files in his vm of some software.15:39
zhonghualijiaopengju, so, the user choose the vm first, then give an address for file location in this vm, right?15:41
jiaopengjuyes15:41
*** tobberydberg has quit IRC15:41
*** tobberydberg has joined #openstack-meeting15:41
*** pcaruana has quit IRC15:41
*** e0ne has quit IRC15:42
zhonghualimake sense15:42
*** xingchao has joined #openstack-meeting15:42
zhonghualijiaopengju, what kind of guess os do you want to use in your case?15:43
zhonghualiwindows or kinux?15:43
jiaopengjulinux prefer15:43
zhonghualiok15:43
chenying_Usually karbor backup the resources managed by openstack, about this usecase file in the vm, we may need think carefully about it.15:45
*** ad_rien_ has quit IRC15:45
chenying_how the get the file resouces in the vm, how the backup them, how to managed the backups of files.15:46
zhonghualijiaopengju,could you please give more detailed description of the use case so that we can discuss further next time?15:46
zhonghualichenying_, +115:46
*** swapnil-nilangek has quit IRC15:46
jiaopengjuIt's not difficult to implement the file backup with open source bakcup software,  the difficult point is how to mange the backups in openstack15:47
*** swapnil-nilangek has joined #openstack-meeting15:47
*** matrohon has quit IRC15:47
jiaopengjuI think the backups management is the key point15:47
chenying_yuval is not online today, Can you write some detail info about this use case, so we can talk about it with him next time. in the karbor's irc channcel or irc meeting.15:48
chenying_https://wiki.openstack.org/wiki/Meetings/Karbor15:48
zhonghualiwhat's the backups management real meaning?15:48
*** salv-orl_ has joined #openstack-meeting15:49
chenying_you can add this use case description to this page.15:49
jiaopengjuA tenant to manage all his backups15:49
*** ataraday_ has joined #openstack-meeting15:49
*** fnaval has quit IRC15:49
jiaopengjuok15:49
zhonghualido you mean how to manage the records?15:49
jiaopengjuyes15:49
*** ntpttr has quit IRC15:49
*** tobberydberg has quit IRC15:50
*** tobberydberg has joined #openstack-meeting15:50
*** rfolco has quit IRC15:50
zhonghualiI do not think that is a question. please let know if I misunderstand something15:50
*** ntpttr has joined #openstack-meeting15:51
zhonghualilet me15:51
jiaopengjuok , I will write the detailed requirements, so we can talk about it next time15:51
chenying_do you mean how to manage the records? --- using the checkpoint records like volumes backups15:51
chenying_jiaopengju +1 thanks15:51
zhonghualijiaopengju, thanks so much15:51
*** salv-orlando has quit IRC15:51
jiaopengjuyou are welcome15:52
zhonghuali:)15:52
chenying_So If we don't have any topic to talk about, this meeting will be ended.15:52
*** fnaval has joined #openstack-meeting15:53
jiaopengjuok15:53
chenying_Thanks, all.15:53
zhonghualithank you all,see you15:53
chenying_#endmeeting15:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:53
openstackMeeting ended Tue Apr 18 15:53:30 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-04-18-15.01.html15:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-04-18-15.01.txt15:53
openstackLog:            http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-04-18-15.01.log.html15:53
*** swapnil-nilangek has quit IRC15:53
*** swapnil-nilangek has joined #openstack-meeting15:54
*** jiaopengju has quit IRC15:54
*** rfolco has joined #openstack-meeting15:54
*** iceyao has joined #openstack-meeting15:54
*** chyka has joined #openstack-meeting15:54
*** fnaval_ has joined #openstack-meeting15:54
*** shintaro has quit IRC15:55
*** vishwana_ has quit IRC15:56
*** cloudrancher has quit IRC15:56
*** cloudrancher has joined #openstack-meeting15:56
*** Kevin_Zheng has quit IRC15:57
*** ntpttr has quit IRC15:57
*** fnaval has quit IRC15:57
*** jlibosva has joined #openstack-meeting15:58
*** ntpttr has joined #openstack-meeting15:59
*** iceyao has quit IRC15:59
*** swapnil-nilangek has quit IRC15:59
jlibosvao/16:00
*** ihrachys has joined #openstack-meeting16:01
ihrachys#startmeeting neutron_ci16:01
openstackMeeting started Tue Apr 18 16:01:08 2017 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
jlibosvao/16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:01
openstackThe meeting name has been set to 'neutron_ci'16:01
haleybhi16:01
*** VW_ has joined #openstack-meeting16:01
*** nadya has joined #openstack-meeting16:01
ihrachyshi everyone16:01
ihrachys#topic Action items from prev meeting16:02
*** openstack changes topic to "Action items from prev meeting (Meeting topic: neutron_ci)"16:02
ihrachys"ihrachys to report bugs for fullstack race in ovs agent when calling to enable_connection_uri"16:02
ihrachysI did, just need to find a link16:02
*** swapnil-nilangek has joined #openstack-meeting16:02
ihrachyshttps://bugs.launchpad.net/neutron/+bug/168220216:03
openstackLaunchpad bug 1681945 in neutron "duplicate for #1682202 Neutron Agent error "constraint violation"" [Undecided,Confirmed]16:03
*** chenhuayi has quit IRC16:03
ihrachysoh and I see it's a dup :)16:03
ihrachysthe right one is then https://bugs.launchpad.net/neutron/+bug/168194516:03
openstackLaunchpad bug 1681945 in neutron "Neutron Agent error "constraint violation"" [Undecided,Confirmed]16:03
*** VW_ has quit IRC16:04
ihrachysotherwiseguy, were there any plans/patches to make ovs agent gracefully handle existing manager?16:04
*** noslzzp has quit IRC16:04
*** VW_ has joined #openstack-meeting16:04
*** swapnil-nilangek has quit IRC16:05
*** rossella_s has quit IRC16:05
*** knangia has joined #openstack-meeting16:05
*** swapnil-nilangek has joined #openstack-meeting16:05
*** VW has quit IRC16:05
ihrachysok, I guess he is not avail16:05
ihrachysso folks, if someone wants to pick it up, you're welcome16:06
otherwiseguyihrachys, what do you mean?16:06
*** sridharg has quit IRC16:06
ihrachysotherwiseguy, hi! https://bugs.launchpad.net/neutron/+bug/168194516:06
openstackLaunchpad bug 1681945 in neutron "Neutron Agent error "constraint violation"" [Undecided,Confirmed]16:06
otherwiseguyThat *is* graceful.16:06
ihrachysmultiple agents trying to add same manager, clashing on constraint16:06
otherwiseguyIt is supposed to fail.16:06
ihrachysit says ERROR16:06
ihrachysit shouldn't16:06
*** Apoorva has joined #openstack-meeting16:07
*** electrofelix has quit IRC16:07
ihrachysotherwiseguy, does it bubble up anywhere, or it's contained?16:07
*** Apoorva has quit IRC16:07
otherwiseguyProbably possible to adust the log message by doing log_errors=False, but check_error=False so no exception raised.16:07
*** Apoorva has joined #openstack-meeting16:08
ihrachysok makes sense16:08
ihrachysso it should probably be Low and not gate-failure tagged16:08
otherwiseguyIn truth, I'd rather we didn't even attempt it. But, that's just my preference in general--let installers do the right thing. :p16:08
*** gyee has joined #openstack-meeting16:09
otherwiseguyI can also see the value in less ideological approaches. :)16:09
otherwiseguyBut yes, not a gate failure. Just a logging issue.16:09
ihrachysotherwiseguy, thanks for clarification, I updated the bug so that it's not tracked as CI issue16:09
ihrachysnext item was "jlibosva to follow up on py3 plan for pike"16:10
jlibosvaargh16:10
ihrachyswe have this ether: https://etherpad.openstack.org/p/py3-neutron-pike16:10
jlibosvaI didn't get any time though I saw kevinbenton reporting a tracker bug16:10
ihrachysand I think kevinbenton acknowledged the goal at https://review.openstack.org/#/c/457200/16:10
ihrachysjlibosva, do you think you will have time for that next weeks, or we should find someone to take over?16:11
*** tlaxkit has quit IRC16:11
*** hashar has quit IRC16:12
jlibosvaihrachys: I will sync with kevinbenton, I hope I'll have time. I forgot that I was working only 3 out of 5 working days since last mtg16:12
ihrachysok makes sense. keep us in the loop.16:12
ihrachyswe will revisit the goal later in the run but for the time being it seems like we should not raise it every mtg :)16:13
ihrachysnext was "ihrachys to update wiki with the link to gerrit CI dashboard"16:13
ihrachysI did16:13
ihrachysmoving on :)16:13
ihrachysnext was "jlibosva document current openvswitch requirements for fullstack/functional in TESTING.rst"16:13
ihrachysjlibosva, I think there was a patch?16:13
jlibosvayes, I sent something16:13
jlibosvalet me find link16:13
ihrachyshttps://review.openstack.org/#/c/456219/16:13
ihrachysmerged, good16:14
*** salv-orl_ has quit IRC16:14
jlibosvahttps://review.openstack.org/#/c/456219/16:14
jlibosvayep16:14
*** nadya has quit IRC16:14
ihrachysjlibosva, btw we also switched to ubuntu cloud archive in master16:14
ihrachysjlibosva, does it change anything for us?16:14
ihrachysI think we can e.g. enable the func tests?16:14
jlibosvaihrachys: afaik it doesn't have the newer kernel, right?16:14
ihrachyswasn't that an issue in userspace?16:15
ihrachysappctl16:15
*** ntpttr has quit IRC16:15
ihrachysI talk about test_install_flood_to_tun16:16
jlibosvaihrachys: it should be triggered automatically if the version meets the requirement16:16
ihrachysoh right16:16
ihrachyslet's check16:16
jlibosvaihrachys: yep, it passes16:16
*** nadya has joined #openstack-meeting16:16
jlibosvae.g. here: http://logs.openstack.org/22/457422/1/check/gate-neutron-dsvm-functional-ubuntu-xenial/41dd5db/testr_results.html.gz16:17
*** ntpttr has joined #openstack-meeting16:17
jlibosvaOVSFlowTestCase16:17
ihrachysyeah, executed16:17
ihrachysnice16:17
ihrachysthen we should probably revise the doc again?16:17
jlibosvayep :)16:18
*** sudipto_ has joined #openstack-meeting16:18
*** sudipto has joined #openstack-meeting16:18
ihrachysshould we leave the skip check, or we can also kill it now?16:18
jlibosvaI would leave it16:18
ihrachysok ok, maybe someone sticks to stock ubuntu16:18
jlibosvait can produce false negative results to those who run with 2.5.016:18
ihrachysok16:18
*** VW has joined #openstack-meeting16:18
*** VW_ has quit IRC16:18
jlibosvaand the error is not in produciton, it's just the test16:18
ihrachys#action jlibosva to revise TESTING doc to update about test_install_flood_to_tun gate status with UCA used for Pike16:19
ihrachysnext was "ihrachys to figure out why gerrit dashboard seems to not show some gate-failure fixes"16:19
ihrachysI did not :-x16:19
ihrachyslemme follow up after the mtg16:19
ihrachys#action ihrachys to figure out why gerrit dashboard seems to not show some gate-failure fixes16:19
ihrachyslast item was "ihrachys to review fullstack and scenario health before next meeting"16:20
*** dandruta has quit IRC16:20
ihrachysI checked fullstack, it's 100% failure mode, example http://logs.openstack.org/65/404265/15/check/gate-neutron-dsvm-fullstack-ubuntu-xenial/a48bd9f/testr_results.html.gz16:20
ihrachysit seems like the same issue for all failures16:21
ihrachyssome connectivity breakage16:21
ihrachyswe need a volunteer to report a bug for that and ideally dig it to a fix16:21
ihrachysbut at least a bug report16:21
ihrachysI see lots of volunteers, but I will probably take it myself!16:23
ihrachys#action ihrachys to report a bug for fullstack connectivity failures16:23
*** swebster_ has joined #openstack-meeting16:23
ihrachysas for scenarios, they are not 100% but close.16:23
ihrachysboth flavours16:23
*** ntpttr has quit IRC16:23
*** swebster has quit IRC16:23
ihrachysan example of the failure16:24
ihrachyshttp://logs.openstack.org/65/404265/15/check/gate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv/8f457d5/logs/testr_results.html.gz16:24
ihrachysit seems like it's always the same test (test_subport_connectivity for trunks)16:24
*** swapnil-nilangek has quit IRC16:24
ihrachysjlibosva, I think you were looking at that one in the past. any lead?16:24
jlibosvait seems that vlan interface doesn't get any address16:24
*** swapnil-nilangek has joined #openstack-meeting16:25
*** ntpttr has joined #openstack-meeting16:25
ihrachysor could it be that the timed out command breaks connectivity?16:25
jlibosvait could be caused by https://bugs.launchpad.net/neutron/+bug/162601016:25
openstackLaunchpad bug 1626010 in neutron "OVS Firewall cannot handle non unique MACs" [High,In progress] - Assigned to Thomas Morin (tmmorin-orange)16:25
jlibosvaI have a fix here: https://review.openstack.org/#/c/385085/16:26
jlibosvathere is still one scenario that ovs fw won't work with vlan and local network types16:26
ihrachysjlibosva, I see the test failing with the patch16:26
jlibosvaehm16:27
* jlibosva scratches his head16:28
jlibosvait shouldn't be :)16:28
ihrachysbad, bad test!16:28
ihrachyswe probably should start at least with reporting a bug for the failure16:28
jlibosvaI'll have a closer look16:28
ihrachysjlibosva, can you take that?16:28
jlibosvaI will16:28
*** donghao has quit IRC16:29
ihrachys#action jlibosva to report a bug for scenario failures16:29
ihrachysthanks16:29
ihrachysok we can now take a look at patches in review16:29
ihrachys#topic #topic Patches in review16:29
*** openstack changes topic to "#topic Patches in review (Meeting topic: neutron_ci)"16:29
ihrachys#topic Patches in review16:29
*** openstack changes topic to "Patches in review (Meeting topic: neutron_ci)"16:29
*** bobh has joined #openstack-meeting16:29
ihrachysthe review dashboard has an issue that I need to look at (discussed before), so I am gonna look through my queue that hopefully captures some fixes16:30
ihrachysthere were quite some gate bugs in last days, but most are squashed now16:31
ihrachysmost of the most pressing I mean16:31
ihrachysone standing right now is https://bugs.launchpad.net/neutron/+bug/167977516:31
openstackLaunchpad bug 1679775 in neutron "test_network_list_queries_constant fails with testtools.matchers._impl.MismatchError: 28 != 13" [Critical,In progress] - Assigned to Kevin Benton (kevinbenton)16:31
ihrachysthis should be solved by https://review.openstack.org/#/c/457515/16:31
ihrachysit's a test only fix16:32
*** ijw has joined #openstack-meeting16:32
ihrachysjlibosva, please have a look16:32
jlibosvawill do16:32
*** nadya has quit IRC16:33
ihrachysI am also cleaning up subunit forks that allowed to slip some test coverage degradation in branches: https://review.openstack.org/#/q/status:open++topic:remove-subunit-trace-fork16:33
*** ntpttr has quit IRC16:33
ihrachyssome are stadium projects there so have a look16:33
ihrachyswe will also need to land https://review.openstack.org/#/q/Icef59a03184473476e0657334bcc30dc7bf4f9ff,n,z to fix periodic neutron-lib jobs for stadium projects16:34
*** ntpttr has joined #openstack-meeting16:35
*** cloudrancher has quit IRC16:35
ihrachysthere is https://review.openstack.org/447781 but I need to have a look why it still fails.16:36
ihrachysI know that jlibosva was working on fixing dhcp agent deployment for fullstack at https://review.openstack.org/#/c/455790/16:37
*** jaugustine has quit IRC16:37
*** ijw has quit IRC16:37
jlibosvathis one doesn't cause much failures16:37
ihrachysyeah, but we need that to unblock work on provisioning blocks16:37
jlibosvayep16:38
*** emagana has quit IRC16:39
*** ntpttr has quit IRC16:39
ihrachysI am not aware of other pressing fixes16:39
*** tobberydberg has quit IRC16:39
ihrachysI gotta do another cleanup round of gate-failure tagged bugs16:39
*** strigazi is now known as strigazi_AFK16:39
*** emagana has joined #openstack-meeting16:39
ihrachys#action ihrachys to clean up gate-failure tagged bugs list16:39
ihrachysseems like some should now go since we landed fixes16:40
ihrachysalso seems like kevinbenton has a lead on linuxbridge multinode instability: https://bugs.launchpad.net/neutron/+bug/168325616:40
openstackLaunchpad bug 1683256 in neutron "linuxbridge multinode depending on multicast support of provider" [Critical,New]16:40
*** ntpttr has joined #openstack-meeting16:40
ihrachys(no patch so far)16:40
*** strigazi_AFK is now known as strigazi16:41
ihrachysany other patches you are aware that may need attention?16:41
jlibosvanot from me16:41
ihrachysok16:41
ihrachys#topic Grafana16:41
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:41
ihrachysnothing major there that we haven't discussed16:42
ihrachysexcept one thing that I wanted to run16:42
ihrachysI see that functional job is now on par with e.g. -api job in terms of stability16:42
ihrachyshttp://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=7&fullscreen16:42
ihrachysit leads it pretty close16:42
ihrachysI wonder if we are close to the time where we could pull the trigger16:42
ihrachysI see that at least 2 weeks in the past16:43
*** xingchao has quit IRC16:43
ihrachysI am keen to just post a patch against project-config and spur discussion :)16:43
ihrachysthoughts?16:44
jlibosvathere is small a functional peak yesterday16:44
*** emagana has quit IRC16:44
*** ntpttr has quit IRC16:44
ihrachysyeah, I don't recollect what was that16:45
ihrachyswas busy with other gate breakages yesterday :)16:45
ihrachysmaybe I should look first16:45
ihrachys#action ihrachys to look at what the functional spike yesterday was16:45
jlibosvaI agree with the patch tho :) we'll see what others say as I think this meeting attendance doesn't belong to the highest16:45
*** baoli has quit IRC16:45
ihrachysjlibosva, agreed. (it doesn't, but it helps to have it right?)16:45
*** swapnil-nilangek has quit IRC16:45
ihrachys#action ihrachys to propose voting for functional job16:46
jlibosvasure, I'm just saying that we will get more voices there16:46
ihrachysI will ofc WIP it and ask for comments during a team meeting and ML16:46
ihrachysok I have nothing else16:46
ihrachysjlibosva, do you?16:46
jlibosvanopes16:47
*** ntpttr has joined #openstack-meeting16:47
ihrachysgreat, then ciao! :)16:47
ihrachys#endmeeting16:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:47
openstackMeeting ended Tue Apr 18 16:47:11 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-04-18-16.01.html16:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-04-18-16.01.txt16:47
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-04-18-16.01.log.html16:47
*** iyamahat has quit IRC16:48
*** litao has quit IRC16:49
*** harlowja_ has joined #openstack-meeting16:50
*** harlowja has quit IRC16:52
*** ntpttr has quit IRC16:53
*** jlibosva has quit IRC16:54
*** ntpttr has joined #openstack-meeting16:54
*** unicell1 has quit IRC16:55
*** felipemonteiro has joined #openstack-meeting16:56
*** amotoki has quit IRC16:57
*** zhonghuali has quit IRC16:57
*** ntpttr has quit IRC16:58
*** jaugustine has joined #openstack-meeting17:00
*** baoli has joined #openstack-meeting17:00
*** ntpttr has joined #openstack-meeting17:01
*** ralonsoh has quit IRC17:01
*** baoli has quit IRC17:01
*** baoli has joined #openstack-meeting17:02
*** ntpttr has quit IRC17:07
*** ataraday_ has quit IRC17:08
*** ataraday_ has joined #openstack-meeting17:08
*** iyamahat has joined #openstack-meeting17:08
*** ntpttr has joined #openstack-meeting17:09
*** wanghao has joined #openstack-meeting17:09
*** yamahata has joined #openstack-meeting17:10
*** markstur has joined #openstack-meeting17:12
*** ntpttr has quit IRC17:13
*** ociuhandu has joined #openstack-meeting17:13
*** ntpttr has joined #openstack-meeting17:15
*** ltomasbo is now known as ltomasbo|away17:15
*** rderose has joined #openstack-meeting17:15
*** ociuhandu has quit IRC17:16
*** zara_the_lemur__ has quit IRC17:16
*** gnarld_ is now known as cFouts17:17
*** kaisers has quit IRC17:19
*** ntpttr has quit IRC17:19
*** ntpttr has joined #openstack-meeting17:21
*** jkilpatr has quit IRC17:22
*** ihrachys_ has joined #openstack-meeting17:23
*** zara_the_lemur__ has joined #openstack-meeting17:23
*** ataraday_ has quit IRC17:24
*** ntpttr has quit IRC17:25
*** ihrachys has quit IRC17:25
*** pksingh has quit IRC17:26
*** cloudrancher has joined #openstack-meeting17:26
*** ntpttr has joined #openstack-meeting17:27
*** baoli has quit IRC17:27
*** cody-somerville has joined #openstack-meeting17:28
*** cody-somerville has quit IRC17:28
*** cody-somerville has joined #openstack-meeting17:28
*** baoli has joined #openstack-meeting17:28
*** donghao has joined #openstack-meeting17:29
*** ntpttr has quit IRC17:31
*** ntpttr has joined #openstack-meeting17:33
*** cloudrancher has quit IRC17:33
*** ijw has joined #openstack-meeting17:33
*** cloudrancher has joined #openstack-meeting17:34
*** donghao has quit IRC17:34
*** edmondsw has joined #openstack-meeting17:34
*** ntpttr has quit IRC17:37
*** unicell has joined #openstack-meeting17:37
*** jkilpatr has joined #openstack-meeting17:38
*** ijw has quit IRC17:38
*** ntpttr has joined #openstack-meeting17:39
*** cloudrancher has quit IRC17:40
*** s3wong has joined #openstack-meeting17:41
*** emagana has joined #openstack-meeting17:41
*** wanghao has quit IRC17:41
*** wanghao has joined #openstack-meeting17:42
*** ntpttr has quit IRC17:43
*** cloudrancher has joined #openstack-meeting17:43
*** ntpttr has joined #openstack-meeting17:45
*** edmondsw has left #openstack-meeting17:46
*** ociuhandu has joined #openstack-meeting17:46
*** wanghao has quit IRC17:46
*** arxcruz has quit IRC17:47
*** ntpttr has quit IRC17:49
*** ociuhandu has quit IRC17:50
*** ntpttr has joined #openstack-meeting17:51
*** ociuhandu has joined #openstack-meeting17:53
*** ociuhandu has quit IRC17:55
*** VW has quit IRC17:57
*** ntpttr has quit IRC17:57
*** ociuhandu has joined #openstack-meeting17:57
*** VW has joined #openstack-meeting17:57
*** patriciadomin has quit IRC17:58
*** gagehugo has joined #openstack-meeting17:58
*** ntpttr has joined #openstack-meeting17:59
*** baoli has quit IRC17:59
bretonhi keystone18:00
lbragstad#startmeeting keystone18:00
openstackMeeting started Tue Apr 18 18:00:25 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
lbragstadping antwash, ayoung, breton, cmurphy, dstanek, gagehugo, henrynash, hrybacki, knikolla, lamt, lbragstad, notmorgan, ravelar, rderose, rodrigods, samueldmq, spilla18:00
cmurphyo/18:00
knikollao/18:00
lbragstad#link https://etherpad.openstack.org/p/keystone-weekly-meeting18:00
rderoseo/18:00
lamto/18:00
lbragstadagenda ^18:00
gagehugoo/18:00
bretonping list is so small18:00
lbragstadnot much on the agenda, so we can have a quick meeting to give people some time back18:01
lbragstad#topic announcements18:01
*** openstack changes topic to "announcements (Meeting topic: keystone)"18:01
lbragstad#info we are in spec proposal freeze - but spec reviews are still wide open, let's continue firming those up18:01
lbragstad#info Boston is only 20 days away18:01
lbragstadif you need anything for Boston that I can be of help with, please let me know18:02
lbragstad#topic VMT coverage18:02
*** openstack changes topic to "VMT coverage (Meeting topic: keystone)"18:02
lbragstadgagehugo knikolla o/18:02
samueldmqhey all! \o/18:02
*** baoli has joined #openstack-meeting18:02
gagehugoJust an update with the VMT coverage stuff18:02
gagehugogonna talk about it at the OSSP meeting thursday @ 1700 UTC18:03
ayoungOh yeah18:03
samueldmqwhat is VMT ?18:03
*** ntpttr has quit IRC18:03
lbragstadvulnerability management18:03
gagehugo^18:03
gagehugoI don't have the etherpad link on me atm from Atlanta18:04
gagehugobut there is more details on there samueldmq18:04
ayoungTHe T is there just to make it into a TLA18:04
*** ntpttr has joined #openstack-meeting18:05
gagehugohttps://review.openstack.org/#/c/447139/ please feel free to look at that and let us know if anything needs fixed18:05
gagehugoI think most of it is ok, just gonna figure out what the next steps are for getting it reviewed by security18:05
gagehugoI think that's it18:05
*** Julien-zte has quit IRC18:06
*** sudipto has quit IRC18:07
*** sudipto_ has quit IRC18:07
knikollathanks gagehugo for keeping a tab on this while i was busy with other things.18:07
*** sambetts is now known as sambetts|afk18:08
samueldmqlbragstad: gagehugo thanks18:08
*** ntpttr has quit IRC18:09
*** patriciadomin has joined #openstack-meeting18:09
gagehugo:)18:09
lbragstad#topic open discussion18:10
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:10
lbragstadanyone have anything?18:11
*** ntpttr has joined #openstack-meeting18:11
ayoungReminder that tomorrow's policy meeting is a video chat.  Max 10 people until we need to bump to a bigger tool than Google Hangout18:14
gagehugoyeah I need to put a note on my calender for that18:15
lbragstadI'll send out a note for sure today18:15
lbragstadthanks folks18:15
lbragstad#endmeeting18:15
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:15
openstackMeeting ended Tue Apr 18 18:15:42 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-04-18-18.00.html18:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-04-18-18.00.txt18:15
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-04-18-18.00.log.html18:15
*** bkopilov has quit IRC18:22
*** tesseract has quit IRC18:22
*** felipemonteiro has quit IRC18:23
*** ntpttr has quit IRC18:25
*** felipemonteiro has joined #openstack-meeting18:25
*** ntpttr has joined #openstack-meeting18:26
*** pvaneck has joined #openstack-meeting18:29
*** toscalix has quit IRC18:29
*** edtubill has quit IRC18:30
*** ntpttr has quit IRC18:33
*** felipemonteiro has quit IRC18:34
*** cloudrancher has quit IRC18:34
*** ntpttr has joined #openstack-meeting18:35
*** ijw has joined #openstack-meeting18:35
*** jkilpatr_ has joined #openstack-meeting18:36
*** jkilpatr has quit IRC18:36
*** ntpttr has quit IRC18:39
*** lpeer has quit IRC18:39
*** Douhet has quit IRC18:39
*** tobberydberg has joined #openstack-meeting18:40
*** Douhet has joined #openstack-meeting18:40
*** ntpttr has joined #openstack-meeting18:41
*** ijw has quit IRC18:41
*** abalutoiu_ has joined #openstack-meeting18:42
*** tobberydberg has quit IRC18:44
*** ntpttr has quit IRC18:45
*** Sukhdev has joined #openstack-meeting18:46
*** AJaeger has joined #openstack-meeting18:46
*** ntpttr has joined #openstack-meeting18:47
*** adisky_ has quit IRC18:49
clarkbfwiw the infra pbx server's only limit to users is what the cpu can handle18:49
*** ad_rien_ has joined #openstack-meeting18:51
*** ntpttr has quit IRC18:51
*** asselin_ has joined #openstack-meeting18:51
*** HeOS has quit IRC18:51
*** asselin__ has joined #openstack-meeting18:52
fungi(and whether we've topped up the account for its dial-in trunk)18:52
*** ntpttr has joined #openstack-meeting18:53
fungi(also, it's not a video chat, in case people are concerned some participants may be talking dogs)18:53
*** asselin has quit IRC18:53
*** asselin_ has quit IRC18:55
mordredfungi: concerned - that sounds amazing18:56
*** matrohon has joined #openstack-meeting18:57
*** asselin has joined #openstack-meeting18:57
*** asselin__ has quit IRC18:59
*** ntpttr has quit IRC18:59
*** olaph has joined #openstack-meeting19:00
fungiinfra team, concatenate!19:00
fungithis week we have action items assigned to and topics proposed by SpamapS, AJaeger and fungi19:00
jeblair#startsandwich fried chicken19:01
cmurphyo/19:01
AJaegero/19:01
*** ntpttr has joined #openstack-meeting19:01
fungi(also maybe pabelanger if he adds one in the next few minutes)19:01
olapho/19:01
clarkbcons clarkb infra19:01
mordredo/19:01
fungijeblair: traditional bone-in fried chicken sandwich?19:01
mordredjeblair: let me know how that command works!19:01
SotKo/19:01
pabelangero/19:01
zara_the_lemur__o/19:01
jeblairfungi, mordred: mmmrphmmmm19:01
fungi#startmeeting infra19:02
openstackMeeting started Tue Apr 18 19:02:32 2017 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:02
fungi#topic Announcements19:02
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:02
fungi#info Infra contributor bootstrapping intro 16:40pm EDT Monday at the OpenStack Forum in Boston19:02
fungi90-minute window shared with some other horizontal teams, so we have about 15 minutes for a quick intro and some questions from the audience19:03
*** JayF has left #openstack-meeting19:03
*** VW has quit IRC19:03
*** dmsimard has joined #openstack-meeting19:03
fungii could use some volunteers to help out with our section of that19:03
*** VW has joined #openstack-meeting19:03
*** VW has quit IRC19:04
fungiget up with me if you're interested, we'll probably just rehash a few slides we have from our infra overview and talk about systems administration as code for a bit19:04
*** VW_ has joined #openstack-meeting19:04
*** Shrews has joined #openstack-meeting19:04
*** egallen has joined #openstack-meeting19:04
fungialso worth noting, in case you're torn between the two, it overlaps with the session about getting rid of stackalytics19:04
pabelangerhah19:04
fungiso, um, choose wisely19:05
fungias always, feel free to hit me up with announcements you want included in future meetings19:05
*** VW_ has quit IRC19:05
fungi#topic Actions from last meeting19:05
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:05
*** VW has joined #openstack-meeting19:05
fungi#link http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-04-11-19.01.html Minutes from last meeting19:05
fungi#action fungi put forth proposal to flatten git namespaces19:06
fungii'm still pondering this one, but will likely take the form of an infra spec19:06
fungipabelanger Open an Ubuntu SRU for bug 125149519:07
openstackbug 1251495 in mailman (Ubuntu Trusty) "Lists with topics enabled can throw unexpected keyword argument 'Delete' exception." [High,Triaged] https://launchpad.net/bugs/125149519:07
*** VW has quit IRC19:07
pabelangeryes! I hope to have this created this week. I've started on packaging already19:07
fungicool, i was not seeing it in the bug19:07
*** VW has joined #openstack-meeting19:07
fungi#action pabelanger Open an Ubuntu SRU for bug 125149519:07
pabelangeryes, no bug yet. Was going to do it all in one shot19:07
fungiclarkb to add citycloud to nodepool19:08
fungii know you're working on that one, though i'm guessing no config change proposed yet19:08
clarkbI've made an account and have sent its info back to citycloud so they can "verify" the account and set quotas19:08
fungioh, right, you cc'd me on that19:08
clarkbno config change proposed yet beause I can't create the two infra users in the account until after it gets verified19:08
fungiyep, makes total sense19:08
fungi#action clarkb to add citycloud to nodepool19:09
*** VW has quit IRC19:09
clarkbbasically the we aren't spammers step19:09
*** VW has joined #openstack-meeting19:09
fungi(speak for yourself!)19:09
* fungi is kidding, of course ;)19:09
clarkbpasswords file is up to date with current info and I will add the users once we have them19:10
fungi#topic Specs approval: PROPOSED: Zuulv3 Executor Security Enhancement (SpamapS)19:10
*** openstack changes topic to "Specs approval: PROPOSED: Zuulv3 Executor Security Enhancement (SpamapS) (Meeting topic: infra)"19:10
fungi#link https://review.openstack.org/444495 Zuulv3 Executor Security Enhancement19:10
*** VW has quit IRC19:10
*** VW has joined #openstack-meeting19:11
fungithis was discussed at last week's meeting with a council voting deadline of about 12 minutes ago19:11
fungiso i'm approving it now19:11
*** bollig has quit IRC19:11
fungi#info APPROVED: "Zuulv3 Executor Security Enhancement" spec19:12
fungi#topic Priority Efforts19:12
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:12
*** VW has quit IRC19:12
*** VW has joined #openstack-meeting19:12
funginothing called out specifically here this week, though the above approved spec is certainly associated with the Zuul v3 priority effort19:12
clarkbI haven't had time to work on gerrit upgrade stuff in the last week unfortunately19:13
fungiyep, lots of people are spread thin19:13
fungi#topic Mitaka EOL: When to remove which changes? (AJaeger)19:13
*** openstack changes topic to "Mitaka EOL: When to remove which changes? (AJaeger) (Meeting topic: infra)"19:13
*** VW has quit IRC19:13
fungi#link https://review.openstack.org/#/q/status:open+project:openstack-infra/project-config+branch:master+topic:mitaka-eol Current list of changes19:13
*** rockyg has joined #openstack-meeting19:14
fungilooks like there are two pending19:14
*** VW has joined #openstack-meeting19:14
AJaegerJust want to know how to move forward - we have some changes proposed and merged already like https://review.openstack.org/#/c/455637/ (twice proposed) and others proposing changes19:14
* AJaeger started with those two19:14
fungifor python 3.4 job removal (mitaka was the last release before we switched to 2.5) and stable/mitaka bitrot job removal19:14
fungis/2.5/3.5/19:15
AJaegerDo we want to wait for tagging the branches - or start with some cleanups slowly?19:15
clarkbwe can also drop trusty jobs19:15
*** VW has quit IRC19:15
AJaegerAnd what to do with projects that still have mitaka branches and use trusty jobs?19:15
fungiwell, except for infra's testing on trusty since we still deploy things on trusty at the moment19:15
pabelangerall or them?19:15
pabelangerof*19:15
*** VW has joined #openstack-meeting19:16
AJaegerwe need trusty for grenade from mitaka to newton, so cannot retire it completely19:16
clarkbAJaeger: we stop testing mitaka to newton when we drop mitaka19:16
* AJaeger already -1s all changes that add new trusty jobs19:16
AJaegerclarkb: ah, good19:16
clarkbso that shouldn't be an issue. Guessing its just going to be deployment related thigns that will have trusty (infra, maybe osa?)19:16
fungiAJaeger: i think openstack-ansible at least expressed a concern because their plan (up until the ptg when we discussed it anyway) had been to perform upgrade tests of stable/newton on trusty servers (they apparently test in-place upgrades of the distro along with openstack)19:17
*** VW has quit IRC19:17
pabelangerclarkb: ya, I think deployment jobs might still want trusty.19:17
*** VW has joined #openstack-meeting19:17
pabelangerI'm personally not in a rush to remove trusty, I feel nodepool-builder is now working great and current breakages have been minimal19:18
mordredyah - as long as it's not difficult to keep around, I don't feel a strong urge to remove it19:18
clarkbthat certainly helps. I mostly want it gone because upstart19:18
*** VW has quit IRC19:18
mordredyah. much as I hate systemd, I prefer _one_ init system to multiple19:19
clarkbeventually I won't have to think about multiple init systems19:19
*** VW has joined #openstack-meeting19:19
mordredI will also admit that sdague's systemd logging changes in devstack are nice19:19
fungiwell, what i told them is that we'll be stuck keeping trusty around for a while due to the infra team's needs19:19
mordredwe've got another year until there is a new lts to replace xenial, right? so we can tweak the policy between now and then based on what we learn from trusty perhaps?19:20
*** bollig has joined #openstack-meeting19:20
fungibut that 1. it's possible stable/newton of some projects may cease working on trusty at any time because they don't gate on it any longer, and 2. wait times for trusty nodes could be long under heavy ci load19:20
*** xiaohhui has quit IRC19:20
*** VW has quit IRC19:20
*** VW has joined #openstack-meeting19:21
pabelangerright19:21
mordred++19:21
fungialso i strongly encouraged them to consider the qa team's distro alignment where grenade is concerned (i.e., stop testing upgrades for the oldest stable branch)19:21
AJaegerSo, if we keep trusty jobs for deployment projects what are we doing for non-deployment projects that won't EOL directly?19:22
*** VW has quit IRC19:22
clarkbAJaeger: I think we remoev all instances of trusty tied to mitaka which is teh vast majority of them19:22
*** VW has joined #openstack-meeting19:22
pabelanger++19:23
fungii guess the hard part of that is probably figuring out which ones aren't running trusty because of mitaka19:23
*** egallen has quit IRC19:23
fungiso that they don't get removed19:23
clarkbya you'll have to check against the regex in layout.yaml that specifies based on branch19:24
*** VW_ has joined #openstack-meeting19:24
clarkbanything that matches the mitaka side can be removed19:24
*** VW_ has quit IRC19:24
*** VW_ has joined #openstack-meeting19:25
*** VW has quit IRC19:25
*** VW_ has quit IRC19:25
*** jamesdenton has quit IRC19:25
*** fnaval_ has quit IRC19:25
AJaegerwe have a default regex for trusty jobs to run only on mitaka, so unless that's overwritten for a specific job...19:25
fungido we have enough info/consensus to be able to move forward? i mean, we should still wait to drop jobs until the bulk of the eol tags are pushed i think19:28
AJaegerso, shall I WIP my two changes?19:28
fungifor example, i saw a thread where teh glance team (i think it was glance) was requesting a delay because they had a stable/mitaka fix they want to land19:28
*** fnaval has joined #openstack-meeting19:29
clarkbya I think we wait for eol then make our changes19:29
*** jamesdenton has joined #openstack-meeting19:29
pabelangerwfm19:29
clarkbbecause once eol happens no more changes can come in so safe to remove jobs19:29
*** VW has joined #openstack-meeting19:29
fungi#link http://lists.openstack.org/pipermail/openstack-dev/2017-April/115529.html Tagging mitaka as EOL19:29
fungiyeah, it was indeed glance19:29
*** VW has quit IRC19:29
*** VW has joined #openstack-meeting19:30
fungithere's some question as to whether it's a valid stable branch change, but i don't think discussion has concluded19:30
*** egallen has joined #openstack-meeting19:30
fungimy point being, if we drop their jobs, it'll be hard for them to test and land that  (if they do wind up moving forward pre-eol)19:31
clarkbnote that it will be hard for them to test if everyone eols and they don't19:31
*** VW has quit IRC19:31
clarkbas devstack won't do things19:31
fungiright19:31
AJaegerso far the jobs proposed, will not block merging any changes - but at one might that might indeed happen...19:31
fungibut it looks like eol hasn't happened anywhere _yet_19:31
fungiat least nova, for example, doesn't have a mitaka-eol tag that i can see19:32
*** VW has joined #openstack-meeting19:32
AJaegerfungi, indeed, tags are not done yet.19:32
*** donghao has joined #openstack-meeting19:32
pabelangerya, I think our move is wait for the moment19:32
AJaegerfungi, we can move on to next topic and discuss further once the first tags have been done...19:33
*** VW has quit IRC19:33
*** VW has joined #openstack-meeting19:33
fungi#agreed Wait for the main batch of EOL tagging/branch deletion, then remove mitaka-specific jobs (including some trusty-specific or Python 3.4-based jobs if only needed by stable/mitaka branches)19:33
fungithat sum it up?19:34
AJaeger+119:34
fungithanks for bringing it up~19:34
fungi!19:34
fungi#topic Scheduling proposed project renames (fungi)19:34
*** openstack changes topic to "Scheduling proposed project renames (fungi) (Meeting topic: infra)"19:34
*** VW has quit IRC19:35
*** jamesdenton has quit IRC19:35
*** fnaval has quit IRC19:35
fungithe defcore working group changed their name to the interop working group a while ago and wants to rename their repo19:35
fungii also have a change to push for renaming a couple of infra repos specific to the user story dashboard (now the feature tracker)19:35
*** e0ne has joined #openstack-meeting19:36
fungiany infra-root planning to be around, say, this friday and interested in helping rename a handful of repos?19:36
clarkbI'm free19:37
pabelangeras am I19:37
fungii'm happy to do the bulk of the work and announcing, just want to make sure i'm not flying solo in case things go terribly wrong and we need some extra hands19:37
*** donghao has quit IRC19:37
jeblairi'll be around19:37
fungishall we say 20:00 utc?19:38
*** gagehugo has left #openstack-meeting19:38
fungia one hour window (with the gerrit/zuul outage expected to conclude early in the window)?19:38
*** rderose has quit IRC19:38
mordredI'll be around19:39
clarkbwfm19:39
fungii'll whip up the task tracker change in the next day or so19:39
fungi#info Gerrit and Zuul will be offline for project renaming maintenance Friday, April 21, 20:00-21:00 UTC.19:40
*** cloudrancher has joined #openstack-meeting19:40
fungilook right?19:40
*** awaugama has quit IRC19:40
*** gordc has joined #openstack-meeting19:40
jeblairare we doing online reindexes now?19:41
clarkbyes19:41
clarkb(upgrade to 2.13 is special case where we can't but general rename project should be fine)19:41
fungiyep19:41
jeblairneat.  then lgtm.  :)19:41
*** e0ne has quit IRC19:42
fungiso, for example, we can bring gerrit and probably zuul back online right away, but some jobs may get incorrect results due to git replication delays (so we'd want to avoid tagging releases during that window)19:42
* fungi consults release schedule real quick19:42
*** e0ne has joined #openstack-meeting19:43
fungiyeah, milestone 1 was last week. this is a dead week on the schedule from what i can see19:43
fungi#link https://releases.openstack.org/pike/schedule.html Pike Release Schedule19:43
*** jprovazn has quit IRC19:43
fungittx: dhellmann: dims: ^ heads up, lmk if that's a no-go for a maintenance window and i can readjust19:44
* dhellmann looks at scrollback19:44
dhellmannthis week or next seems fine to me, but maybe get ttx to sign off19:45
fungino problem, it's never etched in stone ;)19:45
* jeblair puts chisel down19:45
dhellmannthis is r-19, next is r-18, and r-17 is the week before summit so it's probably best not to do it then19:45
fungi#topic Attending September 2017 PTG in Denver, CO, USA (fungi)19:45
*** openstack changes topic to "Attending September 2017 PTG in Denver, CO, USA (fungi) (Meeting topic: infra)"19:45
ttxfungi: sounds good to me19:46
fungii've been asked by the ptg organizers to attempt to gauge how many infra team members want to attend the ptg in denver this september (week of september 11 i believe)19:46
*** rockyg has quit IRC19:46
fungireally just trying to get a rough count so they can start planning sizing for our room and whatnot19:47
*** felipemonteiro has joined #openstack-meeting19:47
* mordred will be there - although would like to complain now that he'll miss opening night of the symphony season19:47
*** jdurgin has quit IRC19:47
jeblairo/19:47
clarkbI'll be there19:47
pabelangertravel budget pending, plan on attending19:47
fungiso even if you don't think you have funding from your employer to attend but might want to take advantage of travel support or something, that's fine19:48
fungislight overestimation is better than significant underestimation19:48
*** cloudrancher has quit IRC19:49
fungimordred: should we plan a group outing to see the colorado state symphony or something?19:49
* olaph hopes to attend19:49
* cmurphy will try to be there19:49
* zara_the_lemur__ is also hoping19:49
mordredfungi: :) maybe so19:50
*** iceyao has joined #openstack-meeting19:50
*** cloudrancher has joined #openstack-meeting19:50
*** cloudrancher has quit IRC19:50
fungiokay, so including me and those speaking up in the meeting, that's at least 8 so far19:50
fungi#info Let fungi know if you hope to attend the PTG in Denver this September so he can get a rough head count19:51
*** cloudrancher has joined #openstack-meeting19:51
fungii'll reach out a few other ways, i don't need to have numbers back to diablo_rojo just yet19:51
fungiglad so many people might be coming!19:51
fungii love hanging out with all of you and getting things done together19:52
fungiand seeing no other last-minute topics on the agenda...19:52
fungi#topic Open discussion19:52
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:52
fungipabelanger: you had something to bring up during open discussion, you said19:52
pabelangerAh, just wanted to gauge interested about starting infracloud upgrades, we'd likely bring down a region at a time to rebuild everything19:53
*** david-lyle has joined #openstack-meeting19:53
pabelangeralso, wouldn't mind trying to land https://review.openstack.org/455480/  today. Adds infra-root-keys to nodepool (we need a stop / start first on nodepool.o.o)19:53
clarkbwould be a good time to make sure we don't ahve the same kernel issue that baremetal had on the other servers19:54
clarkblinux-image-generic needs to be installed19:54
pabelangershould be able to fix that19:54
*** iceyao has quit IRC19:54
*** cdent has joined #openstack-meeting19:54
fungiwe should probably start with whichever region is smaller (chocolate?)19:55
pabelangerif we do chocolate first, it will be a good time to split strawberry too19:55
fungitiming might also coincide with bringing osic offline... i assume everyone's heard the news about osic wrapping up a year ahead of schedule... so not taking the larger of the two offline right when that happens might help us better gauge the impact19:56
clarkband maybe see if we can't get citycloud up first just to offset19:56
pabelangerRight, this would depend on OSIC timing also19:56
fungiyes, that19:56
pabelangernot a rush, just something we've talked about19:56
fungias i said earlier in #openstack-infra, if it's something you want to work on then let's do it19:57
mordred++19:57
fungihas to happen sometime, after all19:57
clarkbonce I get citycloud account verified and quota'd it shouldn't take more than a day to get it running so that will be quick once ready19:59
clarkbso shouldn't be a big speedbump here19:59
fungia the a the a the a that's all folks!20:00
fungithanks everyone20:00
fungi#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Apr 18 20:00:22 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-04-18-19.02.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-04-18-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-04-18-19.02.log.html20:00
*** AJaeger has left #openstack-meeting20:00
*** jdurgin has joined #openstack-meeting20:00
ttxalright!20:00
flaper87o/20:00
mordredo/20:00
*** rockyg has joined #openstack-meeting20:00
dhellmanno/20:00
ttxdhellmann, dims, dtroyer, fungi, johnthetubaguy, mtreinish, sdague, stevemar: around ?20:00
* fungi unsurprised to find tc members in this channel20:00
* mordred waves at flaper87 in meatspace20:00
ttxEmilienM and thingee are excused20:00
fungidockercon?20:01
mtreinisho/20:01
mordredttx: I don't know that we voted to approve that excusal20:01
* edleafe hangs out on the side20:01
sdagueo/20:01
ttx#startmeeting tc20:01
* rockyg takes usual spot in back20:01
openstackMeeting started Tue Apr 18 20:01:31 2017 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
* flaper87 hands mordred some actual steak20: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
mordredmmmm20:01
ttxHi everyone!20:01
ttxLast meeting for the current membership before the election results Friday20:01
ttxOur agenda for today is at:20:01
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:01
* mordred has enjoyed all of these humans20:01
ttx#topic Add TC repo project-navigator-data20:02
cdentmordred: are you eating humans?20:02
*** openstack changes topic to "Add TC repo project-navigator-data (Meeting topic: tc)"20:02
ttx#link https://review.openstack.org/45386720:02
dtroyer_zzo/20:02
* ttx checks there were no last-minute objections before approving20:02
mordredcdent: yup20:02
ttxthere were none, so approving now20:02
flaper87ship it20:02
ttx#topic Resolution on OpenStack's mission for cloud applications20:02
mordredttx: while we're on that - I'm about to send out an email requesting people add information to the repo20:02
*** openstack changes topic to "Resolution on OpenStack's mission for cloud applications (Meeting topic: tc)"20:02
zanebo/20:02
ttx#undo20:02
openstackRemoving item from minutes: #topic Resolution on OpenStack's mission for cloud applications20:02
ttxmordred: oh right, want to say more on that ?20:03
mordredttx: I'm assuming "just send it" is fine with everyone?20:03
ttxmordred: fine by me20:03
flaper87yup20:03
mordredtl;dr "hey everybody, send patches with versions"20:03
mordredcool20:03
ttxthe sooner the better20:03
*** Apoorva_ has joined #openstack-meeting20:03
* johnthetubaguy finally gets connected and joins in20:03
mordredbombs away20:03
ttx#topic Resolution on OpenStack's mission for cloud applications20:03
*** openstack changes topic to "Resolution on OpenStack's mission for cloud applications (Meeting topic: tc)"20:03
ttxzaneb: sorry for false start20:03
ttx#link https://review.openstack.org/44703120:03
zanebno worries :)20:03
ttxthis one seems to have passed the community RFC bar20:03
ttxI think we can finally approve it now ?20:04
mordredzaneb: thanks for writing that zaneb20:04
mordredgah20:04
flaper87ship it20:04
dhellmannwhat's the next step after this resolution? what change are we hoping to trigger?20:04
mordredzaneb: I'm going to refer to you by name twice in all sentences now zaneb20:04
flaper87also, yeah, thanks zaneb20:04
zanebmordred: no worries mordred20:04
* ttx approves before discussing the next move20:05
*** e0ne has quit IRC20:05
zanebthanks everyone!20:05
ttxdhellmann: I read it more as a statement to clarify the direction, rather than an action plan20:05
ttxbut maybe zaneb has more up his sleeves20:06
mtreinishttx: yeah, ditto20:06
flaper87ttx: that's how I read it too20:06
*** eharney has quit IRC20:06
zanebdhellmann: stuff in the footnote would be a good start20:06
*** Apoorva has quit IRC20:06
zanebI believe johnthetubaguy already has some discussions set up for the forum20:06
johnthetubaguyI was hoping the VM & BM working group session at the forum would be a great place to continue the conversation about making progress on that20:06
dhellmannok. I thought maybe it was tied to some specific feature requests, like -- ok, cool, thanks zaneb20:06
johnthetubaguyyeah, I should dig out the link20:07
ttxI think it will facilitate a number of discussions, by providing a reference20:07
dhellmannI believe we may also have some free session slots, if we want a session devoted to this20:07
mordredjohnthetubaguy, zaneb I think I have that on my calendar already, but link would be nice20:07
*** Shrews has left #openstack-meeting20:07
* ttx waits for link before moving to next topic20:07
ttxhttps://www.openstack.org/summit/boston-2017/summit-schedule/events/18749/writing-applications-for-the-vm-and-baremetal-platform maybe20:08
zanebdhellmann: I'd be happy to help facilitate a session like that20:08
johnthetubaguythats the one20:08
ttxor is it https://www.openstack.org/summit/boston-2017/summit-schedule/events/18750/operating-the-vm-and-baremetal-platform-1220:08
johnthetubaguyttx: thank you!20:08
johnthetubaguyits writing applications ones20:08
mordredyes! on my schedule already20:08
johnthetubaguyat least, that was my intention with those20:08
ttx#link https://www.openstack.org/summit/boston-2017/summit-schedule/events/18749/writing-applications-for-the-vm-and-baremetal-platform20:09
dhellmannzaneb : great, maybe you can check in with Tom F?20:09
mordredpossibly also related I have a"Exposing deployer choices to end users without death" on Tuesday20:09
zanebdhellmann: ack20:09
ttx#topic Add a "docs:install-guide-verified" tag20:09
*** openstack changes topic to "Add a "docs:install-guide-verified" tag (Meeting topic: tc)"20:09
dhellmannzaneb : feel free to cc me20:09
ttx#link https://review.openstack.org/44553620:09
ttxAlexandra and Doug worked on this new version which should avoid most of the objections imho20:09
sdaguettx: well, it's now docs:follow-policy20:09
dhellmannyes, the idea here was to structure this tag similar to the other policy tags defined by teams like stable and vmt20:10
fungi(with an s)20:10
sdaguefungi: yep, my typo20:10
ttxsdague: I think it's clearer now yes20:10
dhellmannwhere the general stuff is here, and the details are defined in the doc team contributor guide20:10
johnthetubaguyzaneb: I am struggling to work out if I can still get to the summit, but I would love to help with the prep either way20:11
ttxso any last-minute objection before we approve ?20:11
* flaper87 likes this version better20:11
sdaguenope, I did kind of find the other name more meaningful, but I get why this matches the other pattern20:11
fungii can get behind the name on the grounds that it indicates a deliverable's documentation is developed and released following the docs team's policy20:12
ttxpretty much yes20:12
ttxOK, let's approve it now then20:12
sdaguefungi: yeh, just policy is one of the most overloaded terms in openstack land :)20:12
johnthetubaguyyeah, seem really useful to tell folks, whatever we call it20:12
ttx30 revs should be enough20:12
dhellmannsdague, fungi: I think asettle and I would be happy with a name change if you have an alternative to suggest20:12
dhellmannwe could do that as a separate patch20:13
sdaguedhellmann: yeh, I'm fine with moving forward20:13
dhellmannttx, there's a typo patch on top of this one that I think we can probably fast-approve20:13
* ttx pushes the blue button20:13
fungisuggesting new names violates my personal no-bikeshed policy ;)20:13
ttxtypo patch approved too20:13
flaper87fungi: ++20:13
dhellmannthanks, everyone20:13
dhellmannwe'll probably have one of these from the i18n team, soon, too (I need to talk with Ian)20:14
flaper87dhellmann: thank you and thanks asettle20:14
mtreinishfungi: just suggest  docs:not-a-bikeshed :)20:14
ttxdhellmann: thanks to you for helping push it through the finish mine20:14
ttxand thanks asettle for driving it20:14
mordredfungi: what color do you think the bikeshed would be if it existed?20:14
ttxfinish line. finish line. Not mine.20:14
ttxfinish mine sounds dangerous20:14
mordredfinish mine seems like a thing20:14
ttx#topic Remove App Catalog from official projects20:14
*** openstack changes topic to "Remove App Catalog from official projects (Meeting topic: tc)"20:14
ttx#link https://review.openstack.org/45208620:15
ttxThis seems to have gathered enough approvals from the current membership20:15
ttxBut since it is a first for a project team that is still alive, I was wondering if we should throw it on the ML again before pushing the button20:15
fungione thing that feels missing here (and why i haven't rollcall-voted yet) is that it's missing input from the ptl (either for or against)20:15
ttxThere was a thread already, which quickly went off-topic20:15
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2017-March/113362.html20:15
mordredolaph: ^^20:16
mtreinisholaph: ^^^20:16
mtreinishmordred: err, you win20:16
flaper87ttx: for the sake of openness and over-communication, I'd send one more email20:16
mordredmtreinish: you used more carets than I did, I think you win this one20:16
olaphi've abstained because of conflict of intrest :)20:16
ttxyeah, I understand how it can be difficult to vote on that for olaph20:16
mordredindeed20:16
fungiyou're willing to defer to the tc's judgement in this matter and have no input into it?20:16
ttxI think it's more, "I understand why you're doing it", based on past discussions with olaph and doaceado20:17
fungii mean, that is also a position20:17
fungiand nice to have recorded (now it is, i suppose!)20:17
olaphsure, I can at least put something to that affect in the patch20:18
ttxWe could also wait for the next membership to confirm this, and/or start a new thread20:18
fungicertainly doesn't need a -1 or +1 if you don't feel like adding one20:18
ttxBut then it's not as if it was hard to reverse it20:18
fungibut a sentence in a comment would be helpful to me at least20:18
dhellmannyeah, it would be nice to have the abstention recorded formally20:19
fungimostly just so there's a record that someone representing that team is aware of the proposed change20:19
ttxWould you rather approve it now, and let it simmer for one more week and get the next membership to approve it ?20:19
fungiif nothing else20:19
dhellmannttx: I don't really see significant objections from any of the folks running for the TC. Do we need to wait?20:19
ttxdhellmann: I'm fine with approving now, just checking the rest of the TC's view20:20
dhellmannI'm not opposed, just wondering.20:20
ttxif all approvers are fine with approving this week (once olaph's comment is posted), I'm fine too20:20
fungiand only ~half the tc's up for reelection20:20
* flaper87 is fine w/ approving20:20
*** eharney has joined #openstack-meeting20:21
ttxAlright, let's give some time to olaph and revisit at end of meeting20:21
ttx#topic Propose the addition of an status:maintenance-mode20:21
*** openstack changes topic to "Propose the addition of an status:maintenance-mode (Meeting topic: tc)"20:21
ttx#link https://review.openstack.org/44992520:21
ttxamrith: around ?20:21
*** HeOS has joined #openstack-meeting20:22
amrithyup20:22
ttxLast time we discussed this, and in mtreinish's recent review, the objection is that it conflates two different cases20:22
amrithhello20:22
ttx1/ being under maintenance mode because the team is struggling and can't really add features20:22
ttx2/ being under maintenance mode because the deliverable is feature-complete20:22
ttxIn (1) the tag communicates the need for more contributors, while in (2) it communicates that the project is done20:22
ttxwhich is arguably two different things20:22
*** ildikov is now known as hypothermic_cat20:22
dhellmannif I can break fungi's bike-shedding rule, I think this name should be reserved for case 220:22
ttxmtreinish: you would rather have this one explicitly targetr only (1) ?20:23
dhellmannit seems that amrith's need is to cover case 120:23
amrithdhellmann, help me understand this please.20:23
fungidhellmann: it's just my personal policy for not involving myself in bikeshed discussions. feel free to adopt it yourself or not as you see fit ;)20:23
mtreinishttx: yeah, the way everything is worded in the tag it definitely seems to be targetted to #120:23
amrithwhat would you like the proposal to state? that the reason for this state (to-be-named) is because we need more contributors?20:23
mtreinishdhellmann: yeah and I think maintenance should be reserved for #220:24
ttxstatus:dying-please-help20:24
amrithsure, works for me, just tell me what you want. Personally, I think the distinction being made here is highly academic. We are making the perfect be the enemy of the good (IMHO).20:24
*** ijw has joined #openstack-meeting20:24
sdagueI kind of feel like it's a bit of an artificial distinction20:24
johnthetubaguyright, I was going to ask, where is the action different, I guess is the contributor side, one project is asking for help, the other is saying "we are done"20:24
dhellmannyeah, if you're looking for more help I don't think this tag name is going to get it20:25
sdaguejust based on motivation. Everything could get more features with more people.20:25
ttxsdague: yeah, me too, was fine with conflating the two. For /users/, the end result is the same20:25
sdagueyep20:25
johnthetubaguyyeah, for users it seems the same20:25
amrithdhellmann, we're not looking for the tag to suggest that more help is needed; more that people shouldn't expect too much20:25
* dhellmann shrugs20:25
fungiso the suggestion is to make it more obviously a help-wanted sign?20:25
johnthetubaguyits the contributor side I wasn't so sure about20:25
ttxand tags are for users20:25
*** xingchao has joined #openstack-meeting20:25
mtreinishfor users it might be the same. But it depends on the audience, because one is actually looking for contributors to step up20:25
ttxpersonally I would keep it as is, and create a priority list of help wanted20:26
amrithagain, let me reiterate, my desire is to communicate what Mad TV called "lowered expectations".20:26
dhellmannamrith : I guess it's the difference between "don't expect too much" and "we wish we could do more"20:26
sdagueI think the only other thing I might suggest is that the TC membership is added as core to any project that ends up in this state, so that critical stuff has someone around to make sure things get through20:26
ttxi.e. we could put a project in maintenance-mode *and* on the priority list of things needing urgent help20:26
amrithYes, I intend "don't expect too much". of course the corollary is "if you expect more, step up".20:26
mtreinishand as a random person looking to contribute if I saw maint-mode, I wouldn't even try to contribute20:26
sdaguebecause we've definitely gotten into weird states where litterally there was no one around that could approve on a project like sqlalchemy-migrate20:26
amrithmtreinish, we aren't looking for random people20:26
johnthetubaguysdague: as apposed to just doing self-approvals, which I presume is the alternative? thats interesting20:26
amrithto contribute20:26
sdaguejohnthetubaguy: there might not even be a self20:27
johnthetubaguysdague: good point20:27
amrithbut to a person interested in trove; who sees the maintenance mode, it would mean "if I want more, I have to step up"20:27
*** dimtruck is now known as zz_dimtruck20:27
dhellmannI don't feel that strongly about it,  but it's not clear to me what outcome you want from having the tag so I'm trying to weigh the various possible interpretations.20:27
amrithdhellmann, I'm looking for the tag to be an acknowledgement of "lowered expectatins"20:27
ttxamrith: ++20:27
sdagueamrith: ++20:27
dtroyer_zzI see the reason for wanting the distinction, and it may make a different to the user if they can sort out _why_ this tag was added.20:28
ttxI think the right place to put that distinction is in a help wanted list, not in a tag20:28
sdaguedtroyer_zz: maybe, but we have a commit message on the tag add20:28
ttxjust because tags are mainly for users, while help wanted lists are mainly for contributors20:28
dtroyer_zzsdague: yes, how many users will now how to find that?20:28
mtreinishsdague: that assumes someone goes and digs it up from the log20:28
sdaguemtreinish: it does20:28
edleafefwiw, "maintenance" suggests to me being complete, not in need of help20:28
fungii have a dream that users will become our contributors, but i understand the concern20:29
dtroyer_zzedleafe: ++20:29
amrithedleafe, let's leave the name out of it; let's call it 'tag-whose-name-is-tbd'20:29
dhellmannI do think there's a difference between saying expectations are low and will stay there, and expectations can go up with more help, and I'm not sure that this tag description clearly says the latter as it seems to do for some of the rest of you.20:29
rockygdtroyer_zz, ++ you need to say somewhere for the guy who wants more, how to step up20:29
ttxfungi: not saying those are not highly-overlapping groups. But it's still two different hats20:29
amrithstatus:lowered-expectations20:29
dtroyer_zzameade: the name matters because it carries connotation, which may be different from what you intend20:29
*** ijw has quit IRC20:29
amrithagreed dtroyer_zz20:29
amrithhence I'm un-entangling the name conversation from the intent20:30
amrithonce we agree on intent, we can bikeshed the name20:30
*** xyang1 has quit IRC20:30
sdagueso, having become accidental maintainer of a number of projects, inside and outside of openstack, I totally think tagging them as maintenance mode only is a good idea20:30
dhellmannthat said, the current description is better than having no tag at all20:30
sdaguebecause people do have expectactions20:30
sdaguedhellmann: ++20:30
johnthetubaguy++20:30
*** xingchao has quit IRC20:30
sdaguelike, sqlalchemy-migrate and grenade would be great candidates for this tag20:30
*** ihrachys_ is now known as ihrachys20:30
mordredsdague: ++ ... people don't really always know that mox3 was intended for transition, for instance20:30
ttxI think it's fine to merge this and refine20:30
mordredyah. and sqlalchemy-migrate20:30
sdaguemordred: ++ on mox320:31
ttxas dhellmann said, something is better than nothing here20:31
fungiand we get tons of drive-by feature additions for git-review as another example20:31
sdaguethere is a whole lot of stuff that people assume there is a much deeper bench than there really is20:31
*** xyang1 has joined #openstack-meeting20:31
mordredfungi: ++20:31
smcginnismordred: mox3 info later?20:31
amrithsdague, ++20:31
dhellmannttx: though once the tag is applied we have to be careful with redefining it20:31
*** julim has quit IRC20:31
dtroyer_zzI'm onboard with this tag, but want to be clear since we're talking about expectations that it may not set the intended ones all the way around20:31
*** iceyao has joined #openstack-meeting20:31
flaper87dhellmann: ++20:31
mtreinishsdague: but in most of those cases we don't intend this to be a transient state20:31
sdaguemtreinish: some times20:31
fungigranted, the people who are submitting features to a repo and aren't aware of its development status aren't likely to know to look for our governance tags either20:32
amrithttx, and others, if we are ok with the intent of the tag (lowered expectations), can we now discuss names?20:32
*** askb has joined #openstack-meeting20:32
mtreinishlike sqlalchemy-migrate is always in maint-mode20:32
dhellmannmtreinish : ++20:32
dhellmannmaybe we can take that transient part out20:32
dhellmannin a revision20:32
*** Apoorva_ has quit IRC20:32
ttxstatus:currently-in-maintenance-only-mode20:32
sdaguemaybe, I think projects get to this state for a lot of reasons20:32
amrithdhellmann, I don't follow the take out transient part in a revision comment20:32
dhellmannfungi : we could have a bot automatically comment on patches when a repo has this tag20:33
sdagueand I think it's fine to suggest that more contributors could move things out of there, it's definitely a case by case basis20:33
mtreinishsdague: that's my point, but the tag is clearly written with a very specific case20:33
dhellmannamrith : if we're going to apply this to projects that we want to stay in maintenance mode, then we don't want to say the tag is always transient20:33
fungidhellmann: yep, or a gerrit hook20:33
*** Apoorva has joined #openstack-meeting20:33
dhellmannfungi : tomato, tomato :-)20:33
*** jkilpatr_ has quit IRC20:34
ttxamrith: I'm fine with it the way it stands20:34
ttxwaiting for alternate proposals20:34
fungithere is plenty of negative sentiment expressed when we have automation reply to patches contributed on github saying nobody's going to look at them, but not getting any feedback at all is definitely worse20:34
sdagueyeh, I feel like this is fine as is, I think the coming out of it is more implied, and I think this is better than just silently dropping things20:35
dhellmannyeah, let's move ahead with this and we can propose updates to address the issues we've raised here20:35
dtroyer_zz++20:35
ttxyes, nobody said a lowered-expectations tag was a bad idea. Just details on how to phrase it20:35
amrithto a point raised in an earlier discussion, do we want to give the new TC a voice here?20:35
*** pchavva has quit IRC20:35
* flaper87 already voted on the tag20:35
*** iceyao has quit IRC20:36
ttxI'm fine waiting for one more week20:36
dtroyer_zzIf we want the new TC to handle things today, we should have just deferred them20:36
ttxbut at this point, simpler to amend it after it landed20:36
fungithe new tc always has a voice. they (well, we for those not up for reelection) can always modify this20:36
sdagueamrith: I can propose that as a follow on20:36
edleafeI think postponing sets a bad precedent20:36
ttxfungi: exactly20:36
edleafeYou guys are the TC today20:36
ttxok, I'll approve it now20:37
flaper87edleafe: yup20:37
mordrededleafe: I feel like that's a t-shirt20:37
flaper87we've postponed approvals in the past but for some specific cases20:37
mordred"TC (today)"20:37
fungideferring a decision to the next leadership can be an attractive means of avoiding making decisions20:37
amrithok, thx sdague fungi ttx dhellmann dtroyer_zz mtreinish flaper87 smcginnis ...20:37
ttxand done20:37
amrithheads-up folks, trove gets this tag (patch being proposed)20:37
ttx#topic Remove App Catalog from official projects (final discussion)20:38
dhellmannsdague: I'm working on a follow-up right now with some of the things we said20:38
*** openstack changes topic to "Remove App Catalog from official projects (final discussion) (Meeting topic: tc)"20:38
edleafeflaper87: sure, but there should be specific reasons, and not just as a matter of informal policy20:38
sdaguedhellmann: ok20:38
ttxWe got the comment from olaph20:38
mtreinishdhellmann: heh, I'll close my editor then :)20:38
olaphyep, i've recorded my abstention20:38
ttxso i'm ready to approve https://review.openstack.org/#/c/452086/20:38
sdaguedhellmann: the tc with commit is maybe specific enough to want to debate that on it's own, your call20:38
ttxsince <edleafe> You guys are the TC today20:38
flaper87ttx: go20:38
ttxand done20:39
dhellmannsdague: maybe you want to add that one?20:39
sdaguedhellmann: yeh, I'll do it as a dedicated add on patch, we'll see how it goes20:39
fungithanks olaph!20:39
ttxolaph: thanks20:39
ttx#topic Stalled reviews20:39
*** openstack changes topic to "Stalled reviews (Meeting topic: tc)"20:39
ttxOK, stalled reviews... We had a few more on the agenda, but those were unblocked and merged since then20:40
ttx* Add monitorstack to OpenStack-Ansible (https://review.openstack.org/444325)20:40
ttxThis one is blocked waiting for clarification on what monitorstack is (as it sounds a bit orthogonal to OSA's goals)20:40
ttxI'm concerned about scope creep here, I like teams dedicated to one specific goal/scope20:40
ttxIf the same group of people wants to tackle another goal, that's fine, they can just create another team with roughly the same people in it20:40
ttxBut maybe I don't understand what monitorstack is20:40
fungican even have the same ptl if they want ;)20:40
ttx(which is why I left an open question there)20:40
johnthetubaguyseems a good question to ask20:41
ttxNext step there is to chase down the PTL for an answer20:41
ttx* Add tag assert:never-breaks-compat (https://review.openstack.org/446561)20:41
ttxmordred: what's the next step here ?20:41
mordredttx: I should probably make a new version at some point20:41
ttxok :)20:42
mordredttx: otoh - in general people seemed fairly skeptical about it - so I'll likely wait until after the summit at the very earliest20:42
ttxI'll keep it in the pressure cooker until then20:42
ttx#topic Open discussion20:42
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:42
*** matrohon has quit IRC20:42
mordredthat'll maybe give some facetime to socialize the thoughleader synergy20:42
ttxA few things I wanted to cover... and rosmaita posted one to the -tc list recently20:42
ttxFirst quick reminder that the TC election is going on, last days to vote20:42
ttx#info TC election is going on, last days to vote20:42
mordred(also the release naming election for r)20:42
ttxyes, some people were still complaining of not having received the R naming poll stuff20:43
* smcginnis waves20:43
ttxmordred: you on those ^20:43
mordredoh - awesome. well, they've all gone out as far as I'm concerned20:43
flaper87ttx: and one person that I know of about the TC election email20:43
ttxmordred: see complaints on the ml20:43
mordredoh - neat20:43
flaper87not sure if that was a corner case but diablo_rojo_phon was on it20:43
ttxflaper87: ask them to contact election officials20:43
flaper87ttx: I did :)20:43
*** cleong has quit IRC20:43
ttxSecond, due to unfortunate timing I'm on family vacation next week20:43
mtreinishmordred: it's probably time we start working on deploying are own civs...20:44
ttxSo if I end up being elected I'll very likely miss the first meeting on the new membership20:44
mtreinishs/are/our/20:44
ttxI'll push all the regular administrative stuff to be ready for review, and prepare the usual welcome package content20:44
ttxAnyone up for chairing that meeting ?20:44
mordredmtreinish: yes. I believe we do want to discuss that20:44
flaper87ttx: I can help20:44
* rockyg waves too20:44
fungittx: happened to me last election. i was on a boat in the middle of the atlantic with no internet access when the election concluded20:44
ttx(someone not standing for reelection ideally)20:44
dhellmannmordred : I have not received any email about that poll20:44
flaper87oh wait20:44
flaper87I'm up for election20:44
flaper87ROFL20:44
mordredanybody know what the subject is on the list?20:44
flaper87if I'm elected, I can help, I guess.20:44
flaper87well, I could help even if not but20:44
* flaper87 stfu20:44
*** jdurgin has quit IRC20:45
ttxmordred: it's your thread20:45
dhellmannttx: I should be able to do it20:45
ttx"Emails for OpenStack R Release Name voting going out - please be patient"20:45
sdaguemordred: http://lists.openstack.org/pipermail/openstack-dev/2017-April/115077.html20:45
sdagueand follows20:45
mordredthanks20:45
ttxdhellmann: OK, you're around on Friday ? I'll pass the package to you then20:45
fungithanks dhellmann! (you saved me from having to volunteer to chair two meetings back-to-back next tuesday)20:45
flaper87dhellmann: thanks20:45
dhellmannttx: yeah, we can talk friday20:45
ttxsdague: wanted to discuss TC vision feedback & next steps ?20:45
*** salv-orlando has joined #openstack-meeting20:45
ttxthen rosmaita wanted to talk glance20:46
sdagueright, the vision has been out for 2 weeks now, we've definitely been getting some feedback via various channels20:46
flaper87ttx: I don't see rosmaita around20:46
flaper87:(20:46
ttxI feel like a lot of it were complaints around the format20:46
sdagueone thing I noticed was there was definitely some confusion on framing of it, I've had a few conversations with folks where until I explained the process it didn't click20:46
ttxflaper87: I can parrot the email he just sent, once we are done with vision20:46
dhellmannmaybe we should amend with a preamble explaining the format20:47
fungii was thinking about the framing... if it just started out with a "picture this, if you will..."20:47
sdaguedhellmann: yeh, or a blog post on the TC blog around it20:47
johnthetubaguyyeah, seems we need a preamble20:47
johnthetubaguysdague: maybe both?20:47
dhellmannsdague : if we're going to send people to this document, it probably makes sense to do it inline where they'll see it20:47
mtreinishjohnthetubaguy: ++ to both20:47
sdaguedhellmann: maybe, I found the explaination that I gave was nearly as long as the vision itself20:48
*** zz_dimtruck is now known as dimtruck20:48
johnthetubaguyso there is a summit presentation with ttx gothicmindfood and I think me, I guess that needs to cover that explaination20:48
dhellmannsdague : ok. maybe something in the repo we can link to from this page, then? I just don't like the context being hosted separately.20:48
rockygagree with dhellmann20:49
fungii think we could probably find ways to make the intent of the choice of format more explicit without adding too much prose to the start of the existing narrative20:49
*** david-lyle has quit IRC20:49
fungidoesn't have to be a painfully verbose description of the reasons and process for it (which i agree is also necessary but can be somewhere separate/parallel)20:50
ttxok, anything else on the feedback, beyond format confusion ?20:50
sdaguewell, I think there is the more general next steps question20:50
sdaguewe're collecting various feedback now20:50
fungithe "after it's approved, what now?"20:50
sdaguewe're going to get some in Boston20:50
ttxsdague: next step after Boston is formal approval20:51
*** trandles has joined #openstack-meeting20:51
dhellmannsomewhere in there we should look at the feedback and decide if we want to make changes based on it :-)20:51
sdaguedhellmann: yeh ++20:51
ttxthen starting to do things, yes20:51
ttxah, yes :)20:51
ttxI included that in formal approval. Obviously iterate on the review and contact back people that had given specific feedback20:52
dhellmannso maybe that's the next step, after the forum, to have all of the feedback gathered in one place to make reviewing it easier?20:52
sdagueI think there are some interesting bits that have popped up that demonstrate need for clarity. I guess I wonder if it makes sense to try to gather in some way in boston to discuss that feedback that we've gotten thus far to figure out if there are any major things we need to move forward20:52
sdagueor at least have a subteam assessing that20:52
ttxI'll be around20:52
ttxWe could do a late Thursday Forum discussion on the rev220:53
dhellmannsure, at the forum makes sense, too20:53
* flaper87 will be there20:53
dhellmannwill we have the feedback collected in one place by then?20:53
ttxmostly meant as a workgroup thing but fine if people join too20:53
* mtreinish has both his talks thurs. afternoon :(20:53
ttxmtreinish: what time ?20:53
mtreinisherr, one sec20:53
fungimtreinish: our firehose talk is 4:10pm-4:50pm20:54
* ttx doesn't have anythign yet on Thu afternoon20:54
ttxit's a weird feeling20:54
mtreinishmy laundrycloud talk is at 2:20-3:00p20:54
ttxok, so the 5:00pm slot is available20:54
sdaguewhen is the feedback seesion?20:55
ttxgeneral feedback ? Thursday noon20:55
ttxWould like to go through rosmaita's email before we close20:55
mtreinishttx: heh, last session of the week :)20:55
*** jkilpatr has joined #openstack-meeting20:55
sdaguettx: ok, I ceed the floor20:56
ttx#link http://lists.openstack.org/pipermail/openstack-tc/2017-April/001362.html20:56
*** csomerville has joined #openstack-meeting20:56
ttxBasically most of the remaining Glance contributors were wiped out by the recent events20:56
ttxincluding the PTL20:56
ttxWe might need to put it in status:maintenance-mode and appoint a PTL20:57
ttxto cover the basic stuff20:57
amrithouch20:57
ttxWe'll see how that goes, but it's a good hedas-up20:58
ttxheads-up20:58
flaper87ttx: fwiw, jokke will still be around. maintenance-mode might make sense but I could ask him if he's up for the job and see if we can find a "solution"20:58
flaper87but yeah, that's a terrible hit20:58
ttxoh sure. I'm not saying we'll have to do it. But we might20:58
*** oneswig has joined #openstack-meeting20:58
ttxAnd thanks to Brian for keeping us in the loop20:58
*** jmlowe has joined #openstack-meeting20:59
flaper87++20:59
*** bryang has joined #openstack-meeting20:59
*** cody-somerville has quit IRC20:59
ttxOn this sad note we'll close the last meeting of this membership20:59
flaper87thanks everyone20:59
fungirough stuff20:59
ttxFor the next membership we'll probably reconsider the need for a meeting20:59
flaper87and good luck to all the candidates20:59
rockygDang!  I'm sad.  But thanks, everyone.  See the next team next week!21:00
amrith./21:00
*** jdurgin has joined #openstack-meeting21:00
amrith\.21:00
amrithbye bye all (for now)21:00
ttxThanks everyone! It was a pleasure working with all of you these last 6 months21:00
ttx#endmeeting21:00
fungilikewise21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Tue Apr 18 21:00:46 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-04-18-20.01.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-04-18-20.01.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-04-18-20.01.log.html21:00
*** gordc has left #openstack-meeting21:01
oneswigThanks ttx21:01
oneswig#startmeeting scientific_wg21:01
openstackMeeting started Tue Apr 18 21:01:22 2017 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: scientific_wg)"21:01
openstackThe meeting name has been set to 'scientific_wg'21:01
oneswigGreetings all21:01
trandleshello21:01
*** noslzzp has joined #openstack-meeting21:01
oneswig#link Agenda for today is https://wiki.openstack.org/wiki/Scientific_working_group#IRC_Meeting_April_18th_201721:01
oneswigHi trandles21:02
oneswigMartial is at DockerCon and will join intermittently21:02
trandlesI presume b1airo is on a bus ;)21:02
*** olaph has left #openstack-meeting21:02
oneswigWe've heard of stranger things!21:03
oneswigtrandles: should we jump to the evening social while people gather?21:04
trandlessure, I can update21:04
*** sdague has quit IRC21:04
*** ntpttr has quit IRC21:04
trandlesA contract has been signed and a deposit paid for The Chart House21:05
trandles70 person attendance is no problem21:05
trandlesWe've got the space from 7:00-10:00 pm21:05
oneswigtrandles: can you share a link to the Chart House?21:05
trandles#link http://www.chart-house.com/locations/boston/21:06
*** cdent has left #openstack-meeting21:06
oneswigAha, thanks21:06
oneswigDo we get the outside space too?21:06
*** ntpttr has joined #openstack-meeting21:07
*** flanders_ has joined #openstack-meeting21:07
trandlesWe have several "levels" of menu available based on $/person.  From those levels we have to do something like "pick 3 of the following 4 entrees."  I was planning to put the entrees up for a vote.21:07
trandlesNot sure about the outside space.  I have an email in to their coordinator already and will follow-up with that.21:08
oneswigtrandles: might be one of those times when democracy is not the optimal outcome.  I might consider choosing a balance yourself as nobody's going to put the salad as #1, you may otherwise end up with 3x dishes of fried stuff21:09
trandleslol, ok21:09
trandlesI think we'll end up with 1 vegetarian option (pasta) and 2 others21:09
trandlesThe menu has to be set by April 2621:10
oneswigThanks BTW for doing so much legwork on this. An inclusive spread of options like that seems good21:10
*** david-lyle has joined #openstack-meeting21:10
trandlesno problem21:10
oneswigflanders_: are you there David?21:10
flanders_Hi21:11
trandlesHeyo21:11
oneswigHi Flanders!21:11
oneswigTop of the morning to ya21:11
trandlesI've asked their coordinator if the sponsors can send the money straight to the Chart House.  Waiting to hear back on that.21:11
flanders_G'Day to all yoos21:11
*** ntpttr has quit IRC21:11
*** thorst has quit IRC21:11
oneswigtrandles: great idea that.  Much much simpler.  I really hope they can21:11
trandlesIt would be easier if it went straight to them and we worked out the menu, etc. before hand and didn't have to muck about with it the night of21:12
trandlesSo long as no one in our group starts smashing up the place. :P  Which I think is highly unlikely.21:12
*** rfolco has quit IRC21:12
*** rfolco has joined #openstack-meeting21:13
*** ntpttr has joined #openstack-meeting21:13
oneswigtrandles: with this approach there's the question of rounding error.  Say we get 65 tickets but budget for 70.  That's money that ought not have gone to the venue.  Could get tricky21:13
*** rfolco has quit IRC21:13
*** dbecker has quit IRC21:14
trandlesTrue.  And I was wondering what we'd do with leftover funds if that happened.21:14
oneswigIn Barcelona Colin picked up the rest of the tab, which worked out (mostly by luck) to be about $4 within budget.21:14
oneswigtrandles: best avoided by design21:14
trandlesindeed21:14
*** iceyao has joined #openstack-meeting21:14
trandlesI'm not positive that all sponsors will have someone present either21:15
*** haleyb has quit IRC21:15
*** Sukhdev has quit IRC21:15
oneswigtrandles: and miss the chance to make an after-dinner speech?  Unthinkable :-)21:15
trandlesI'd like to have the financials worked out ASAP and go back and request what we need within their offers21:15
*** cloudrancher has quit IRC21:15
trandlesBut that's waiting on hearing back from the coordinator...21:16
trandlesAnyway, I'll get some marketing logos in the next day or two and get the eventbrite page up and going21:16
*** cloudrancher has joined #openstack-meeting21:16
oneswigme too, makes sense to work it out in advance.  Ideally I'd keep >=1 vendor present and paying on the night.  Helps with taking up any slack21:17
oneswiglet me know what I can do to help21:17
*** ntpttr has quit IRC21:17
*** Sukhdev has joined #openstack-meeting21:17
oneswigOK, we should cover the rest of the summit too...21:18
trandlesI'll email RE: vendor reps.  My vendor isn't sure who is attending from his company...21:18
oneswigtrandles: I'm pretty sure there will be staff present from the other two21:18
trandlesthx...that's all I have...21:19
oneswigOK, let's move on.  Thanks Tim21:19
*** jamesdenton has joined #openstack-meeting21:19
*** ntpttr has joined #openstack-meeting21:19
*** iceyao has quit IRC21:19
oneswig#topic Meeting agenda21:19
*** openstack changes topic to "Meeting agenda (Meeting topic: scientific_wg)"21:19
oneswigOK so we also have business to discuss and ought to start thinking about what to put into the meeting agenda.21:20
oneswig#link All summit planning goes under here https://etherpad.openstack.org/p/Scientific-WG-boston21:20
*** msimonin has joined #openstack-meeting21:21
*** egallen has quit IRC21:21
oneswigI think it's a good idea to start from the previous summit agenda and adapt21:22
oneswigI'll see if I can dig it up21:22
*** martial has joined #openstack-meeting21:23
oneswig#link last summit agenda here: https://etherpad.openstack.org/p/scientific-wg-barcelona-agenda21:23
*** jamesdenton has quit IRC21:23
*** jpr has joined #openstack-meeting21:23
oneswigHi Martial, you there?21:24
*** egallen has joined #openstack-meeting21:24
martialHi stig, yes, I am here21:24
oneswigWe are just looking at agenda items for Boston21:24
oneswig#chair martial21:24
openstackCurrent chairs: martial oneswig21:24
martialwill be a little distracted likely, but will be around21:24
*** newmember has quit IRC21:25
*** ntpttr has quit IRC21:25
*** rderose has joined #openstack-meeting21:26
*** xingchao has joined #openstack-meeting21:26
*** ntpttr has joined #openstack-meeting21:27
*** b1airo has joined #openstack-meeting21:27
martial#chair b1airo21:27
openstackCurrent chairs: b1airo martial oneswig21:27
oneswigOK I added 3 core items21:27
*** msimonin has quit IRC21:27
oneswigHi b1airo21:27
trandlesoneswig: do you want to ask if there is any activity/resolution to the follow-up to Austin items or are they "ancient history?"  In particular I was thinking of Tim's accounting/quota stuff.21:28
b1airoHi all, apologies - this is proving a difficult time for skool mornings21:28
oneswigUnderstandable.  Agenda item for new time slots perhaps?21:28
oneswigtrandles: I think that's a good idea for completeness21:29
oneswigI just fouled up the formatting, will fix..21:29
b1airotrandles: yes perhaps we can link to the specs / user-stories (or whatever we are calling them now)?21:29
trandlesthat topic has received some attention lately on the mailing list21:30
*** eharney has quit IRC21:30
trandlesI'll look for the thread21:30
oneswiger... do you  remember what our activity areas were back then??21:30
trandlesthey were listed on the Barca etherpad21:31
martialI think Tim had his own slot in the forum at this point on that topic21:31
*** xingchao has quit IRC21:31
oneswigAh, quite so!21:31
*** ntpttr has quit IRC21:31
martialI remember seeing an email thread from speaker support on this21:31
jmloweI actually had to start reporting usage since Austin, I can let people know what I did21:31
b1airoAustin? That's where we set them for the first time? Federation, HPFS, high-performance networking, ... ?21:32
*** thorst has joined #openstack-meeting21:32
trandlesI linked his forum session on the agenda21:32
*** jpr has quit IRC21:33
*** ntpttr has joined #openstack-meeting21:33
oneswigb1airo: User stories21:33
jmlowerbudden sends his regrets for not being able to make today's meeting, btw21:33
oneswigAh, too bad21:34
*** donghao has joined #openstack-meeting21:34
oneswigOK, what more to add on the etherpad for the Boston meeting agenda?21:35
*** tobberydberg has joined #openstack-meeting21:35
jmlowelooks kind of full for 40 minutes to me21:35
oneswigI think so too...21:36
oneswig#topic Boston lightning talks21:37
*** openstack changes topic to "Boston lightning talks (Meeting topic: scientific_wg)"21:37
*** msimonin has joined #openstack-meeting21:37
*** ntpttr has quit IRC21:37
oneswigOK so we ought to start casting the net for talks, right?21:37
*** thorst has quit IRC21:37
oneswigIs it too early?21:37
*** Apoorva_ has joined #openstack-meeting21:38
martialoneswig: can you please reshare the link for the etherpad21:38
*** esberglu has quit IRC21:38
b1airoOnly 3 weeks away!21:38
oneswigmartial: https://etherpad.openstack.org/p/Scientific-WG-boston21:38
oneswigb1airo: as soon as that?  OK, lets go for it.21:39
oneswigIs the best plan a mail to openstack-operators for this?21:39
*** donghao has quit IRC21:39
*** ntpttr has joined #openstack-meeting21:39
martialoneswig thanks21:39
oneswigAnd should we see about a small prize to sharpen the interest21:39
*** msimonin has joined #openstack-meeting21:39
martialfti, I will also have the cyborg team make a small 5 minute into so that the few of us that want to talk to them can do so on their own time21:40
martialfyi21:40
*** cloudrancher has quit IRC21:40
*** tobberydberg has quit IRC21:40
*** ijw has joined #openstack-meeting21:40
oneswigI think it'll take several channels of publicity to raise awareness but mailing list is a start21:40
oneswigmartial: sounds useful to me21:40
*** cloudrancher has joined #openstack-meeting21:41
jmloweI did very well the last time I went up for a small prize21:41
b1airoSo long as it doesn't require any branding21:41
oneswigaha, think your luck's still in, eh?21:41
*** rderose has quit IRC21:41
martialjmlowe: what my line ... ah yes "poster" :)21:41
*** Apoorva has quit IRC21:42
b1airooneswig: u could present remotely!?21:42
oneswig"and now, by live satellite linkup, through at least seven openstack clouds ... ... ... and next ..."21:42
jmlowesecond time he's been asked that today21:42
oneswigI perfect this, and I get to live on a desert island - deal?21:43
*** baoli has quit IRC21:43
*** ntpttr has quit IRC21:43
oneswigI'm not sure it'd work for a lightning talk, although the consequences could be hilarious21:43
b1airoCould pre record if u have material21:44
oneswigb1airo: will consider it...21:44
martialoneswig: do a demo :)21:44
*** ntpttr has joined #openstack-meeting21:44
oneswigI can take the task to mail on the lists, and ask around re: prize21:45
oneswigjmlowe: I've heard one should have three watches to truly know the time, right?21:46
jmloweI'll let you know when I get the third21:46
*** Sukhdev has quit IRC21:47
oneswig(for the rest of the room, jmlowe attends a conference in Switzerland, and wins a watch - he's lucky it wasn't a cuckoo clock)21:47
jmloweAlthough I could offer it up a la stanley cup, winner of the best talk keeps it till the next summit21:47
*** Sukhdev has joined #openstack-meeting21:48
jmlowemuch easier to pack than the second prize drone21:48
*** salv-orl_ has joined #openstack-meeting21:48
trandlescongrats jmlowe21:48
oneswigindeed!21:48
trandlesI'm sure you declared it to customs ;)21:48
jmloweI was just under the limit21:48
trandles\o/21:49
trandlesit's a free-for-all!21:49
*** ntpttr has quit IRC21:49
oneswigOK, I'll take an action on that.  More for lightning talks?21:49
b1airoHow many?21:49
*** gouthamr has quit IRC21:50
oneswig5 minutes apiece? 10?21:50
b1airo4... 10mins each?21:50
oneswigOh hang on, it's 40 mins...21:50
oneswig10 mins is on the long side I'd say21:50
jmlowe5 @ 8 min would be my vote21:50
*** salv-orlando has quit IRC21:50
b1airoGoing by last time, 6 mins was problematicly short I recall?21:51
*** ntpttr has joined #openstack-meeting21:51
martialbeing on those presenters, 6 minutes was short :)21:51
b1airoQuestion time?21:51
oneswig8 mins looks good to me.21:51
oneswigQuestions in the BoF?21:51
jmlowespeaking of short, we are almost out of time today if there is anything pressing21:52
oneswiggood grief you're right21:52
b1airoMaybe 4x 8mins then, to leave question/discussion time at the end and house keeping21:52
jmlowealso I hear my children have arrived21:52
oneswig#topic cloud congress21:52
*** openstack changes topic to "cloud congress (Meeting topic: scientific_wg)"21:52
oneswigOK, couple of quick points here:21:52
oneswig#link do register on Eventbrite: https://www.eventbrite.com/e/boston-open-research-cloud-workshop-tickets-3189325658921:53
*** thorst has joined #openstack-meeting21:53
oneswig#link do review the agenda taking shape: https://drive.google.com/drive/folders/0B4Y7flFgUgf9dElkaFkwbUhKblU?usp=sharing21:53
oneswigAny updates on the cloud congress?21:54
martialnothing that I saw21:54
oneswigOK, let's wrap up21:54
oneswig#topic AOB21:54
*** openstack changes topic to "AOB (Meeting topic: scientific_wg)"21:54
oneswigI saw this - http://intel.cmail20.com/t/ViewEmail/d/C316287F828160FA/21:55
oneswigIntel are open-sourcing all their lustre work and discontinuing commercial support21:55
trandlesI read last week's logs.  +1 a scientific-wg IRC channel.  Any updates on that?21:55
oneswigA good thing?21:55
*** ntpttr has quit IRC21:55
jmlowetrandles beat me to it21:55
oneswigtrandles: ah, forgot, whoopsy21:55
*** david-lyle has quit IRC21:55
oneswigapologies, will follow up for next time21:55
martialtrandles: like that21:56
*** iceyao has joined #openstack-meeting21:56
b1airoIf it makes their support better then it's a good thing21:56
*** rderose has joined #openstack-meeting21:56
trandlesb1airo: +1 support21:56
b1airoSeems to suck at the moment21:56
*** ntpttr has joined #openstack-meeting21:56
*** ykatabam has joined #openstack-meeting21:56
b1airoIn APAC anyway21:57
trandlesif it's going to be opensource I'm probably not going to fry for saying that we're working to get lustre 2.9+ on linux version 4 kernels21:57
oneswigI think they are withdrawing the enterprise support, not sure where that leaves their subscribers21:57
jmlowebring on the ceph?21:57
oneswigtrandles: with CentOS 5 run time?21:57
*** rderose has quit IRC21:57
b1airoCeph FTW21:57
martial:)21:57
*** HeOS has quit IRC21:57
*** cloudrancher has quit IRC21:57
trandlesoneswig: nothing before CentOS 6 unfortunately21:57
*** thorst has quit IRC21:58
trandlesalthough my need is for CentOS 721:58
oneswigphew...21:58
oneswigthere was also this, did you see they are pulling the plug on OSIC: http://fortune.com/2017/04/14/intel-openstack-project-rackspace/21:58
*** cloudrancher has joined #openstack-meeting21:58
oneswigAnd no IDF: https://www-ssl.intel.com/content/www/us/en/intel-developer-forum-idf/san-francisco/2017/idf-2017-san-francisco.html21:59
oneswigThe new broom sweeps clean at Intel...21:59
trandlesindeed21:59
flanders_http://lists.openstack.org/pipermail/foundation/2017-April/002484.html21:59
trandlesflanders_: thanks for that, had been wondering...22:00
martialwhen should I tell the cyborg team that they should be availble btw?22:00
martial(which of our 3 slots?)22:00
oneswigmartial: for the lightning talks I'd say22:00
*** iceyao has quit IRC22:00
martialokay22:00
oneswigflanders_: thanks22:01
*** ntpttr has quit IRC22:01
flanders_Intel and Rax are divorcing, both are committed to Openstack still FTR22:01
oneswigAh, out of time.  It's going to be an interesting summit!22:01
b1airomartial: probably also the BoF22:01
flanders_+122:01
oneswiggotta close up22:02
oneswigThanks everyone22:02
oneswig#endmeeting22:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:02
openstackMeeting ended Tue Apr 18 22:02:17 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-04-18-21.01.html22:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-04-18-21.01.txt22:02
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-04-18-21.01.log.html22:02
martialso both time slots?22:02
martialokay will let teh team know22:02
trandlesttfn  o/22:03
*** ntpttr has joined #openstack-meeting22:03
oneswigcheers y'all22:03
*** oneswig has quit IRC22:03
*** trandles has left #openstack-meeting22:04
*** abalutoiu_ has quit IRC22:04
*** cloudrancher has quit IRC22:04
*** abalutoiu_ has joined #openstack-meeting22:04
*** bryang has left #openstack-meeting22:04
*** cloudrancher has joined #openstack-meeting22:05
*** ntpttr has quit IRC22:07
*** martial has quit IRC22:08
*** ntpttr has joined #openstack-meeting22:09
*** ianw_pto is now known as ianw22:12
*** amotoki has joined #openstack-meeting22:13
*** xyang1 has quit IRC22:14
*** ntpttr has quit IRC22:15
*** ntpttr has joined #openstack-meeting22:16
*** bobh has quit IRC22:17
*** cloudrancher has quit IRC22:17
*** Sukhdev has quit IRC22:17
*** Julien-zte has joined #openstack-meeting22:20
*** ijw has quit IRC22:21
*** jaugustine has quit IRC22:22
*** vishnoianil has quit IRC22:23
*** Julien-z_ has joined #openstack-meeting22:23
*** ntpttr has quit IRC22:23
*** Apoorva_ has quit IRC22:24
*** ntpttr has joined #openstack-meeting22:24
*** Apoorva has joined #openstack-meeting22:24
*** Julien-zte has quit IRC22:25
*** xingchao has joined #openstack-meeting22:27
*** ntpttr has quit IRC22:28
*** cloudrancher has joined #openstack-meeting22:30
*** felipemonteiro has quit IRC22:30
*** cloudrancher has quit IRC22:30
*** ntpttr has joined #openstack-meeting22:30
*** cloudrancher has joined #openstack-meeting22:31
*** kjw3 has quit IRC22:32
*** xingchao has quit IRC22:32
*** rockyg has quit IRC22:32
*** vishnoianil has joined #openstack-meeting22:34
*** ntpttr has quit IRC22:34
*** ntpttr has joined #openstack-meeting22:37
*** kjw3 has joined #openstack-meeting22:40
*** thorst has joined #openstack-meeting22:41
*** thorst has quit IRC22:43
*** thorst has joined #openstack-meeting22:43
*** ntpttr has quit IRC22:43
*** msimonin has quit IRC22:44
*** ntpttr has joined #openstack-meeting22:44
*** msimonin has joined #openstack-meeting22:46
*** jaypipes has quit IRC22:46
*** thorst has quit IRC22:47
*** dtrainor has quit IRC22:48
*** salv-orl_ has quit IRC22:48
*** dtrainor has joined #openstack-meeting22:49
*** vishnoianil has quit IRC22:50
*** pewp has joined #openstack-meeting22:50
*** pewp has quit IRC22:51
*** ntpttr has quit IRC22:51
*** ntpttr has joined #openstack-meeting22:52
*** artom has quit IRC22:53
*** artom has joined #openstack-meeting22:53
*** david-lyle has joined #openstack-meeting22:53
*** dtrainor has quit IRC22:54
*** dmacpher has quit IRC22:56
*** david-lyle has quit IRC22:56
*** dtrainor has joined #openstack-meeting22:56
*** aloga has quit IRC22:57
*** ijw has joined #openstack-meeting22:59
*** ntpttr has quit IRC22:59
*** ntpttr has joined #openstack-meeting23:01
*** aloga has joined #openstack-meeting23:03
*** vishnoianil has joined #openstack-meeting23:03
*** ijw has quit IRC23:03
*** emagana has quit IRC23:03
*** emagana has joined #openstack-meeting23:04
*** rbak has quit IRC23:04
*** ntpttr has quit IRC23:05
*** ntpttr has joined #openstack-meeting23:07
*** aeng has quit IRC23:07
*** zhonghua2 has joined #openstack-meeting23:08
*** dmacpher has joined #openstack-meeting23:09
*** aeng has joined #openstack-meeting23:09
*** zhonghua has quit IRC23:10
*** ntpttr has quit IRC23:11
*** ntpttr has joined #openstack-meeting23:12
*** egallen has quit IRC23:12
*** ianychoi has joined #openstack-meeting23:14
*** pewp has joined #openstack-meeting23:14
*** thorst has joined #openstack-meeting23:15
*** cloudrancher has quit IRC23:16
*** ntpttr has quit IRC23:16
*** cloudrancher has joined #openstack-meeting23:17
*** ntpttr has joined #openstack-meeting23:19
*** cloudrancher has quit IRC23:20
*** cloudrancher has joined #openstack-meeting23:21
*** ntpttr has quit IRC23:23
*** ntpttr has joined #openstack-meeting23:24
*** cloudrancher has quit IRC23:27
*** cloudrancher has joined #openstack-meeting23:27
*** xingchao has joined #openstack-meeting23:28
*** ntpttr has quit IRC23:28
*** ntpttr has joined #openstack-meeting23:30
*** cloudrancher has quit IRC23:30
*** cloudrancher has joined #openstack-meeting23:30
*** cloudrancher has quit IRC23:31
*** pewp has joined #openstack-meeting23:31
*** d0ugal has quit IRC23:32
*** pewp has quit IRC23:32
*** xingchao has quit IRC23:32
*** arxcruz has joined #openstack-meeting23:33
*** chyka has quit IRC23:33
*** gouthamr has joined #openstack-meeting23:33
*** Sukhdev has joined #openstack-meeting23:35
*** VW has joined #openstack-meeting23:36
*** fnaval has joined #openstack-meeting23:36
*** ntpttr has quit IRC23:36
*** amotoki has quit IRC23:37
*** aloga has quit IRC23:37
*** ntpttr has joined #openstack-meeting23:37
*** tobberydberg has joined #openstack-meeting23:38
*** baoli has joined #openstack-meeting23:38
*** lamt has quit IRC23:40
*** Julien-z_ has quit IRC23:40
*** d0ugal has joined #openstack-meeting23:41
*** ntpttr has quit IRC23:41
*** aloga has joined #openstack-meeting23:41
*** Julien-zte has joined #openstack-meeting23:42
*** tobberydberg has quit IRC23:42
*** cloudrancher has joined #openstack-meeting23:43
*** ntpttr has joined #openstack-meeting23:43
*** Julien-zte has quit IRC23:44
*** Nakato has quit IRC23:45
*** Nakato has joined #openstack-meeting23:46
*** artom has quit IRC23:49
*** ntpttr has quit IRC23:49
*** artom has joined #openstack-meeting23:50
*** amotoki has joined #openstack-meeting23:50
*** ntpttr has joined #openstack-meeting23:51
*** artom has quit IRC23:52
*** artom has joined #openstack-meeting23:52
*** hichihara has joined #openstack-meeting23:53
*** hongbin has quit IRC23:55
*** reedip has quit IRC23:55
*** yangyapeng has quit IRC23:55
*** ntpttr has quit IRC23:55
*** rfolco has joined #openstack-meeting23:56
*** rfolco has quit IRC23:56
*** ntpttr has joined #openstack-meeting23:57
*** ijw has joined #openstack-meeting23:59

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