Tuesday, 2017-01-10

*** ansmith has joined #openstack-meeting00:00
*** diablo_rojo has joined #openstack-meeting00:01
*** ykatabam has quit IRC00:01
*** armax has quit IRC00:02
*** claudiub has joined #openstack-meeting00:03
*** claudiub|2 has quit IRC00:06
*** yangyape_ has quit IRC00:11
*** hongbin has quit IRC00:14
*** bzhao_ has quit IRC00:14
*** ansmith has quit IRC00:15
*** oomichi has quit IRC00:17
*** oomichi has joined #openstack-meeting00:19
*** jrobinson_ has joined #openstack-meeting00:20
*** jrobinson has quit IRC00:21
*** ykatabam1 has quit IRC00:23
*** sdague has quit IRC00:26
*** rbudden has quit IRC00:27
*** jaugustine_ has quit IRC00:27
*** beekhof_mb has joined #openstack-meeting00:27
*** ansmith has joined #openstack-meeting00:28
*** jaugustine has quit IRC00:28
*** Julien-zte has joined #openstack-meeting00:31
*** mtanino_ has joined #openstack-meeting00:33
*** guoshan has joined #openstack-meeting00:34
*** jrobinson_ is now known as jrobinson-afk00:34
*** mtanino has quit IRC00:34
*** VW has quit IRC00:35
*** ykatabam has joined #openstack-meeting00:37
*** ykatabam has quit IRC00:37
*** ykatabam has joined #openstack-meeting00:37
*** guoshan has quit IRC00:38
*** s3wong has joined #openstack-meeting00:40
*** aeng has quit IRC00:41
*** claudiub has quit IRC00:48
*** mriedem has joined #openstack-meeting00:49
*** salv-orlando has joined #openstack-meeting00:49
*** salv-orlando has quit IRC00:53
*** lhx_ has quit IRC00:54
*** jrobinson-afk is now known as jrobinson00:55
*** aeng has joined #openstack-meeting00:55
*** jrobinson has quit IRC00:57
*** Wenzhi has joined #openstack-meeting00:58
*** thorst has joined #openstack-meeting01:01
*** spzala has quit IRC01:01
*** beekhof_mb has quit IRC01:05
*** Leo_ has joined #openstack-meeting01:06
*** joehuang has joined #openstack-meeting01:06
*** oomichi has quit IRC01:07
*** oomichi has joined #openstack-meeting01:08
*** Swami__ has joined #openstack-meeting01:09
*** rfolco has quit IRC01:11
*** lindycoder has joined #openstack-meeting01:11
*** Swami_ has quit IRC01:12
*** Swami has quit IRC01:12
*** Swami has joined #openstack-meeting01:12
*** huanxuan has joined #openstack-meeting01:13
*** yangyapeng has joined #openstack-meeting01:16
*** thorst has quit IRC01:17
*** Swami has quit IRC01:18
*** Swami__ has quit IRC01:18
*** thorst has joined #openstack-meeting01:20
*** aerwin3 has joined #openstack-meeting01:22
*** huanxuan has quit IRC01:24
*** gyee has quit IRC01:24
*** kevinz has joined #openstack-meeting01:25
*** Dmitrii-Sh has quit IRC01:26
*** sdake has quit IRC01:29
*** rbudden has joined #openstack-meeting01:30
*** flwang has left #openstack-meeting01:30
*** david-lyle has joined #openstack-meeting01:31
*** thorst has quit IRC01:32
*** david-lyle has quit IRC01:37
*** Leo_ has quit IRC01:38
*** unicell has quit IRC01:46
*** ansmith has quit IRC01:48
*** markvoelker has quit IRC01:48
*** guoshan has joined #openstack-meeting01:49
*** salv-orlando has joined #openstack-meeting01:50
*** ruijie has left #openstack-meeting01:54
*** salv-orlando has quit IRC01:54
*** lhx__ has joined #openstack-meeting01:56
*** lhx__ has quit IRC01:56
*** lhx__ has joined #openstack-meeting01:57
*** ljxiash has quit IRC01:59
*** ekcs has quit IRC02:03
*** mtanino has joined #openstack-meeting02:05
*** mtanino_ has quit IRC02:07
*** lindycoder has quit IRC02:10
*** galstrom_zzz is now known as galstrom02:13
*** ijw has joined #openstack-meeting02:16
*** noslzzp has quit IRC02:18
*** ijw_ has quit IRC02:18
*** ljxiash has joined #openstack-meeting02:20
*** zhurong has joined #openstack-meeting02:23
*** lennyb has quit IRC02:23
*** yonglihe has joined #openstack-meeting02:23
*** lennyb has joined #openstack-meeting02:24
*** kjorgens_ has quit IRC02:24
*** rbudden has quit IRC02:25
*** VW has joined #openstack-meeting02:26
*** khushbu_ has joined #openstack-meeting02:28
*** VW has quit IRC02:31
*** zhurong has quit IRC02:35
*** mtanino has quit IRC02:42
*** bzhao has quit IRC02:43
*** bkopilov has quit IRC02:45
*** s3wong has quit IRC02:49
*** gcb has joined #openstack-meeting02:50
*** salv-orlando has joined #openstack-meeting02:51
*** pksingh has joined #openstack-meeting02:53
*** hongbin has joined #openstack-meeting02:54
*** epico has joined #openstack-meeting02:55
*** salv-orlando has quit IRC02:55
*** Namrata has joined #openstack-meeting02:57
*** wxy_ has quit IRC02:57
*** sudipto_ has joined #openstack-meeting02:58
*** lakerzhou has joined #openstack-meeting02:59
*** zhangjl has joined #openstack-meeting02:59
hongbin#startmeeting zun03:00
openstackMeeting started Tue Jan 10 03:00:05 2017 UTC and is due to finish in 60 minutes.  The chair is hongbin. Information about MeetBot at http://wiki.debian.org/MeetBot.03:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:00
*** openstack changes topic to " (Meeting topic: zun)"03:00
openstackThe meeting name has been set to 'zun'03:00
hongbin#link https://wiki.openstack.org/wiki/Zun#Agenda_for_2017-01-10_0300_UTC Today's agenda03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
hongbinThanks for joining hte meeting sudipto_ Namrata pksingh kevinz lakerzhou Wenzhi03:01
hongbinLet's start03:01
*** rkmrHonjo has joined #openstack-meeting03:01
hongbin#topic Announcements03:01
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:01
hongbini have no announcement, anyone else has?03:01
hongbin#topic Review Action Items03:01
*** openstack changes topic to "Review Action Items (Meeting topic: zun)"03:01
hongbin#topic Support multi-host deployment (hongbin)03:01
*** openstack changes topic to "Support multi-host deployment (hongbin) (Meeting topic: zun)"03:01
hongbin#link https://blueprints.launchpad.net/zun/+spec/support-multiple-hosts The BP03:02
hongbin#link https://review.openstack.org/#/c/415554/ The patch03:02
hongbini have been working on this bp last week.03:02
hongbinright now, all the patches were submitted03:02
hongbinand they are under review03:02
hongbinthat is all from me03:02
*** t-izumi has joined #openstack-meeting03:03
hongbinany comment?03:03
*** jrobinson has joined #openstack-meeting03:03
hongbinok, then next topic03:03
*** t-izumi has left #openstack-meeting03:03
hongbin#topic Cinder integration (diga)03:03
*** openstack changes topic to "Cinder integration (diga) (Meeting topic: zun)"03:03
pksinghhongbin: will look into it today03:03
*** joehuang has quit IRC03:03
hongbinpksingh: ack. thx03:03
hongbin#link https://blueprints.launchpad.net/zun/+spec/cinder-zun-integration The BP03:04
hongbin#link https://review.openstack.org/#/c/417747/ The design spec03:04
hongbinit looks diga is not here03:04
hongbinlet's table this one03:04
hongbinbtw, i saw he submitted a spec for that03:04
*** anilvenkata has joined #openstack-meeting03:04
hongbinoh, it is the link above03:04
*** csomerville has quit IRC03:04
hongbinanyone is welcomed to review his patch03:05
hongbinok, next one03:05
*** csomerville has joined #openstack-meeting03:05
hongbin#topic Support interactive mode (kevinz)03:05
*** openstack changes topic to "Support interactive mode (kevinz) (Meeting topic: zun)"03:05
hongbin#link https://blueprints.launchpad.net/zun/+spec/support-interactive-mode The BP03:05
*** woodster_ has quit IRC03:05
hongbin#link https://review.openstack.org/#/c/396841/ The design spec03:05
hongbinkevinz: ^^03:05
kevinzHi Hongbin03:05
kevinzI have a question about zun-api talk to docker daemon03:06
hongbingo ahead03:06
kevinzNeed to use "resize" command to Docker, will it implement by zun-api--> docker daemon   or  zun-api -->zun-compute -->docker daemon03:07
hongbini don't have a good answer for that03:07
hongbinneed to do some investigation, will work with you after the meeting03:07
kevinzIf use "zun-api --> docker daemon", in zun-api side need to add a httpclient for it03:08
*** zhurong has joined #openstack-meeting03:08
sudipto_is re-size relevant to the interactive mode discussion?03:08
kevinzsudioto_: yeah03:08
*** xuao has joined #openstack-meeting03:08
kevinzresize the tty session size so that it can change according to users' local terminal03:09
sudipto_imho, the zun-api never should talk to the docker daemon directly because the driver abstraction is done at the compute layer...not at the API layer. So compute is the gateway to the runtime.03:10
hongbini guess interactive mode doesn't have to use the driver abstraction?03:11
hongbinnot sure right now, need to look into it03:12
kevinzright I use zun-api talk to docker daemon directly to get the websocket link,03:12
sudipto_typically the API would run on the controller node, so are you suggesting contacting a docker daemon on a remote machine via http in that case? Also - does the API become aware of various drivers eventually?03:12
sudipto_like today it's docker, tomorrow it could be something else.03:13
hongbingood point03:13
hongbinperhaps, make a call to zun-compute to get the connection information first, then use hte connection info to connect interactively03:14
*** rbudden has joined #openstack-meeting03:14
kevinzYeah that may be a good solutions for this03:15
*** lindycoder has joined #openstack-meeting03:15
hongbinthere might be other options03:15
kevinzSo  CLIS--> Zun-api --> zun-compute to get he websocket link?03:16
*** diablo_rojo has quit IRC03:16
kevinzAnd CLIS--> Zun-api --> zun-compute to resize tty03:16
*** lblanchard has joined #openstack-meeting03:16
kevinzThat will be easy for tty to resize:-)03:17
hongbinok, let's discuss it later03:17
hongbinmove on03:17
hongbin#topic Make Zunclient an OpenStackClient plugin (Namrata)03:17
*** openstack changes topic to "Make Zunclient an OpenStackClient plugin (Namrata) (Meeting topic: zun)"03:17
hongbin#link https://blueprints.launchpad.net/zun/+spec/zun-osc-plugin The BP03:17
hongbinNamrata: ^^03:18
Namratahi all..03:18
Namratai have added the patches for container API endpoints :Commands support03:18
Namrataand they are up for review03:19
hongbinyes, i saw a serious of patches03:19
hongbinall are great work!03:19
*** mtanino has joined #openstack-meeting03:19
NamrataFurthermore I will be working on Image Api endpoint commands03:19
Namratathanks hongbin03:19
*** yamamoto_ has joined #openstack-meeting03:20
hongbinNamrata: ack03:20
*** epico has quit IRC03:20
*** lblanchard has quit IRC03:20
Namratathanks hongbin.Nothing to add more from my side03:20
hongbinNamrata: i think the image api hasn't been fully implemented yet...03:21
Namrataso what do you suggest03:21
hongbinNamrata: perhaps skip the image api for now, and consider this bp as implemented03:22
Namrataokay sounds good03:22
hongbinNamrata: i think all the container api are implemented, right?03:22
hongbinNamrata: if you are looking for next task, you can ping me after03:23
Namratayes the etherpad which I created03:23
Namratathe listed commands are implemented03:23
Namratayeah sure hongbin03:23
hongbinall, any comment about the osc bp?03:23
pksinghits good work :)03:24
Namratathanks pksingh03:24
*** ljxiash has quit IRC03:24
*** epico has joined #openstack-meeting03:24
hongbin#topic Open Discussion03:24
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:24
hongbinanyone has topics to discuss?03:25
*** ljxiash has joined #openstack-meeting03:25
pksinghhongbin: i just wanted to discuss about fuxi work by diga03:25
pksinghcant be introduce an api for volume create and then attacha that volume to conatiner03:25
hongbinpksingh: it looks diga is not here, but we can have a pre-discussion now03:26
hongbinpksingh: i think docker has api to create/attach volumes03:26
pksinghyes, just using that API and fuxi driver, can we expose our own rest API for volume create03:27
hongbinpksingh: fuxi doesn't have any api, it is just a docker plugin, so that when you call api in docker, it translate it to api calls to cinder03:27
sudipto_fuxi intends to be a docker only broker?03:28
pksinghhongbin: yes, i understand that03:28
hongbinsudipto_: right now, it is docker only,03:28
sudipto_pksingh, the api should be in cinder though isn't it?03:28
hongbinsudipto_: in the future, i am not sure yet, the roadmap is under discuss03:28
sudipto_adding another API layer in fuxi, would mean we have two different APIs...03:29
pksinghhongbin: i think this is the same way other drivers like flocker work,03:29
sudipto_isn't zun going to be interacting with cinder eventually? which would talk to docker?03:29
sudipto_via fuji.03:29
*** ljxiash has quit IRC03:29
*** mtanino has quit IRC03:29
* sudipto_ did not read the spec yet03:29
hongbinsudipto_: both options are under consideration03:29
hongbinwhat diga proposed is to using fuxi, which is the second option03:30
*** galstrom is now known as galstrom_zzz03:30
sudipto_cinder already has a lot of storage vendor support, so i thought the flow could be something like : 1. Ask cinder for volumes from zun. Cinder creates the volume in the backend 2. Cinder gives the volumes to fuxi . 3. Fuxi does the attachment.03:31
hongbinsudipto_: yes, that is totally possible03:31
pksinghsudipto_: but we need to maintain the multitenancy too03:32
*** reedip_outofmemo has joined #openstack-meeting03:32
sudipto_multi-tenancy is maintained at cinder for the volumes...03:32
hongbinyes, one thing to note is that fuxi doesn't have multi-tenancy (too bad)03:32
hongbinhow fuxi works is writing down the admin credential to a config file, then all the volumes were created in the admin tenant03:33
pksinghthats why i asked too maintain the volume records with tenants in our db03:33
pksinghhongbin: ohh, then i think this will not work03:33
hongbinyes, that means we need to skip fuxi if we wanted multi-tenancy03:33
sudipto_I am not sure why fuxi is aware of multi-tenancy, or has to be aware of it.03:34
sudipto_to me it appears to be low level in comparison to zun or cinder (sorry i have to read more maybe)03:34
hongbinsudipto_: well, if you create a volume, you have to specify the tenant of the volume?03:34
sudipto_hongbin, that happens at the cinder layer...03:34
hongbinsudipto_: but zun need to use a tenant credential to interact with cinder?03:35
*** gcb has quit IRC03:36
hongbinsudipto_: but zun can pass down the user's context to cinder, that is fine03:36
sudipto_hongbin, yeah something like that.03:36
hongbinsudipto_: but docker doesn't pass down the user's contex to its plugin (fuxi), that is hte problem03:36
*** Leo_ has joined #openstack-meeting03:37
*** gcb has joined #openstack-meeting03:37
*** bzhao has joined #openstack-meeting03:37
*** yamahata has quit IRC03:37
sudipto_ok need to understand this better...will talk to you about this.03:37
*** iyamahat has quit IRC03:37
hongbinthe problem is fuxi doesn't get any context passed from docker, so it has to use the admin credential in config file03:37
*** zhurong has quit IRC03:37
pksinghthanks hongbin for clarifying :)03:37
hongbinsudipto_: pksingh : frankly, we can just skip fuxi if we wanted multi-tenancy03:38
hongbinthat is the same problem with kuryr right now (kuryr doesn't support multi-tenancy as well)03:39
hongbinwe can discuss that further later03:39
*** Leo_ has quit IRC03:39
pksinghhongbin: right now it seems so03:39
hongbinpksingh: ?03:39
pksinghhongbin: yes sure03:39
pksinghwe can discuss later03:39
pksinghthanks for explaining03:39
hongbinany other topic to be discuss?03:40
hongbinok, all. thanks for joining the meeting03:40
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"03:40
openstackMeeting ended Tue Jan 10 03:40:38 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-01-10-03.00.html03:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-01-10-03.00.txt03:40
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-01-10-03.00.log.html03:40
*** pksingh has quit IRC03:43
*** zhangjl has left #openstack-meeting03:43
*** mtanino has joined #openstack-meeting03:43
*** VW has joined #openstack-meeting03:43
*** khushbu_ has quit IRC03:46
*** diga has joined #openstack-meeting03:46
*** Wenzhi has quit IRC03:47
*** Wenzhi has joined #openstack-meeting03:47
*** markvoelker has joined #openstack-meeting03:48
*** liuyulong has quit IRC03:50
*** Wenzhi has quit IRC03:51
*** salv-orlando has joined #openstack-meeting03:52
*** r-mibu has quit IRC03:52
*** r-mibu has joined #openstack-meeting03:52
*** abhishekk has joined #openstack-meeting03:53
*** Dinesh_Bhor has joined #openstack-meeting03:53
*** links has joined #openstack-meeting03:54
*** yamamoto_ has quit IRC03:56
*** diablo_rojo has joined #openstack-meeting03:56
*** salv-orlando has quit IRC03:57
*** sneti has quit IRC03:57
*** tpatil has joined #openstack-meeting03:59
*** takashi has joined #openstack-meeting04:00
takashi#startmeeting masakari04:00
openstackMeeting started Tue Jan 10 04:00:29 2017 UTC and is due to finish in 60 minutes.  The chair is takashi. Information about MeetBot at http://wiki.debian.org/MeetBot.04:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** openstack changes topic to " (Meeting topic: masakari)"04:00
openstackThe meeting name has been set to 'masakari'04:00
takashiAs samP is not available, so I'll host the meeting today.04:01
takashiCan we proceed based on the agenda? https://wiki.openstack.org/wiki/Meetings/Masakari04:01
*** vishnoianil has quit IRC04:02
*** t-izumi has joined #openstack-meeting04:02
takashi#topic bugs04:03
*** openstack changes topic to "bugs (Meeting topic: masakari)"04:03
takashicurrently there are no critical bugs04:04
*** liuyulong has joined #openstack-meeting04:04
takashitpatil: Do you need some dicsussions about https://review.openstack.org/#/c/397064/ ?04:04
*** lhx__ has quit IRC04:04
rkmrHonjotpatil: Takahara replied to your comment in this gerrit page. Please check Takahara's comment.04:05
*** sagara has joined #openstack-meeting04:05
*** guoshan has quit IRC04:05
takashisagara: hi04:05
tpatilAbhishek is working on that bugs from our side04:05
tpatilAbhishek, do you want to talk about it?04:05
abhishekkI have figure out that due to while True loop, child thread is waiting forever04:06
*** lindycoder has quit IRC04:06
*** lindycoder has joined #openstack-meeting04:07
abhishekkIf i move this code in a daemon thread then when I send sigterm, sigkill and sigint signal then parent and child processes are exiting correctly04:07
abhishekkonly problem with this is that it will not exit gracefully04:08
abhishekkIMO as it is just a monitoring service, we should not care about exiting gracefully04:08
abhishekkplease provide your opinions on the same04:08
tpatilif there are already some requests in progress and if you send SIGTERM signal to parent process, do you want child process to wait until all requests are processed or not?04:09
tpatilIMO, it should04:09
tpatilI have checked Takahara's comment04:10
takashitpatil: I think it is better to keep on-going request. At least, if masakari-api recieves uncomplete request, it should record error04:10
*** anilvenkata_ has joined #openstack-meeting04:10
rkmrHonjoI think that exiting gracefully is needed, too.04:10
takashito let operators to find incomplete evacuate request04:10
tpatilAbhishek is working on exiting child process gracefully04:11
tpatilHe will propose that patch sometime this week04:11
takashitpatil: ok04:11
*** yamamoto_ has joined #openstack-meeting04:11
takashirkmrHonjo: Can I ask you to have a look at that patch?04:11
takashionce it is proposed to gerrit04:12
rkmrHonjotpatil: Is the patch for masakari?04:12
*** anilvenkata has quit IRC04:12
takashifor masakari-monitors, right?04:12
tpatilno, masakari-monitors04:12
*** hongbin has quit IRC04:12
tpatiltakashi: yes04:13
*** lhx__ has joined #openstack-meeting04:13
rkmrHonjotpatil: OK, I understood.04:13
takashirkmrHonjo: thx04:13
takashirkmrHonjo: there is another patch for masakari monitors https://review.openstack.org/#/c/417303/04:15
*** anilvenkata_ has quit IRC04:15
*** anilvenkata_ has joined #openstack-meeting04:16
rkmrHonjotakashi: Oh, I didn't check it yet.04:16
takashirkmrHonjo: I'd like to ask your review about masakari monitor/client stuffs, as you created a most of them04:16
rkmrHonjotakashi: Sure. I review it as soon as fast.04:17
takashirkmrHonjo: thanks!04:17
takashiDoes anybody have discussion topics related to bug stuffs?04:17
takashi#topic spec proposal04:20
*** openstack changes topic to "spec proposal (Meeting topic: masakari)"04:20
takashiBefore moving to open discussion, I'd like to discuss about spec related things04:20
takashiIt seems that samP proposed a patch to create basic files for spec repo https://review.openstack.org/#/c/418176/04:21
*** samP_ has joined #openstack-meeting04:21
takashisamP_: Hi04:21
samP_takashi: hi..04:21
*** links has quit IRC04:21
*** Wenzhi has joined #openstack-meeting04:21
tpatilI will review that patch tomorrow. Abhishek, can you take a look at it today?04:22
samP_I thought I couldn't attend..04:22
abhishekkonce it is merged, I will propose specs for implementing reserved_host recovery method and specs-lite for periodic tasks04:22
*** beekhof_mb has joined #openstack-meeting04:22
*** links has joined #openstack-meeting04:22
takashisamP_: np. We are just talking about spec related works.04:23
*** sdake has joined #openstack-meeting04:23
samP_takashi: great.. thanks04:23
takashisamP_: Can I ask one question about your patch? https://review.openstack.org/#/c/418176/04:23
samP_takashi: sure04:24
*** galstrom_zzz is now known as galstrom04:25
*** cburgess has quit IRC04:25
takashisamP_: It seems that unit tests for spec still remains as a to-do item. Will you add it soon, or need some help for that?04:25
*** cburgess has joined #openstack-meeting04:25
samP_takashi: I will add them soon.04:26
tpatilsamP_: Are you planning to add it in the same patch or in a followup patch?04:27
samP_takashi: Im working on it now. I have just push it without them. so, others can push sepcs04:27
*** rmk has quit IRC04:27
samP_takashi: It will be a separate patch04:27
tpatilsamP_: Ok04:28
takashiOK. So let's land the basic files patch first, and add unit tests in a follow-up.04:28
takashiwill have a look :-)04:28
samP_takashi: thanks04:28
rkmrHonjosamP_: I'm reviewing the patch. I add point(+1 or -1) after this meeting.04:29
*** yamamoto_ has quit IRC04:29
samP_rkmrHonjo: thanks04:29
*** yamamoto_ has joined #openstack-meeting04:30
takashi#topic open discussion04:30
*** openstack changes topic to "open discussion (Meeting topic: masakari)"04:30
tpatil# link: https://blueprints.launchpad.net/masakari/+spec/ha-enabled-config-options04:30
*** lindycoder has quit IRC04:31
tpatilsamP_: can you please approve this blueprint?04:31
*** sharatss has left #openstack-meeting04:31
*** bkopilov has joined #openstack-meeting04:31
takashitpatil: this is a kind of specless blueprint, right?04:31
samP_tpatil: sure04:31
tpatilsamP_: Thanks04:32
samP_we agreed not to write spec on this.04:32
*** rmk has joined #openstack-meeting04:32
*** rmk has quit IRC04:32
*** rmk has joined #openstack-meeting04:32
takashiand the other items which require specs, we can start submitting specs after we land the basic files patch to spec repo04:33
tpatilas agreed in the last meeting, Abhishek will propose the required blueprints and life-specs once masakari-specs patch is merged.04:33
*** VW has quit IRC04:33
takashitpatil: I see, thanks04:34
tpatil1) Add periodic tasks04:34
*** VW has joined #openstack-meeting04:34
tpatil2) Implement remaining recovery methods04:34
*** yamamoto_ has quit IRC04:34
*** iyamahat has joined #openstack-meeting04:34
takashitpatil: thanks04:35
takashiIs there any other topics for today?04:37
*** adisky_ has joined #openstack-meeting04:38
*** VW has quit IRC04:38
samP_any updates from Sachin@platform9?04:39
takashisamP: I also find some blueprints about monitor/client stuffs still in new status. Can I ask you to also check them and change their status?04:39
*** Namrata has quit IRC04:39
samP_takashi: sure, I will do04:39
*** jrobinson is now known as jrobinson-afk04:39
*** adiantum1 has joined #openstack-meeting04:39
*** galstrom is now known as galstrom_zzz04:39
tpatilsamP_: He has shared talk proposal on google docs, I think he is interested to know more the roadmap04:40
tpatilmore about the roadmap04:40
rkmrHonjotakashi, samP_:Sorry, I forgot to change status...04:40
*** adiantum has quit IRC04:40
*** adiantum1 is now known as adiantum04:40
samP_tpatil: thanks, I saw your replay on email. Its nice we can do a presentation on summit with them04:42
tpatilsamP: Do you have more use cases that you want to implement in Masakari?04:42
*** iyamahat has quit IRC04:42
*** lakerzhou has quit IRC04:42
samP_tpatil: for huge topics, Bare metal HA, and container HA04:43
samP_for ironic(bare metal HA) I can share some basic idea.04:44
tpatilsamP_: I would like to know more about these use cases04:45
samP_for container HA, I still thinking about a usecases.04:45
tpatilsamP: Is it possible for you to describe these use cases in etherpad?04:46
samP_tpatil: yes, sure. I will write them down. so, we can discuss them.04:46
tpatilsamP: Thanks04:46
tpatilwe can also implement HA for Cinder volume service similar to compute node failure?04:46
*** sudipto_ has quit IRC04:46
*** mtanino has quit IRC04:46
samP_tpatil: I thought about it. but they already have inbuild solution for that. right?04:47
samP_tpatil: about cinder HA04:47
samP_same goes for neutron04:48
takashisamP_: are you talking about cinder-volume act/act?04:48
samP_takashi: yes04:48
tpatilIf that's already there, no need to worry then04:48
tpatilI'm not sure whether all volume will be migrated automatically upon cinder volume node failure.04:49
tpatilI will confirm about this point later04:49
rkmrHonjoIn my understanding, migrating is unnecessary if we use cinder-volume act/act.04:49
samP_tpatil: volumes will not migrate, but other cinder-vol node will handle them insted04:49
samP_guys.. really sorry.. I have to leave now04:50
tpatilsamP: Ok04:50
takashiI think we already have capability for that (I mean ha for cinder service), as we can define process name or host type04:51
samP_please put any actions items for me under samP04:51
*** nadya has joined #openstack-meeting04:51
samP_thank you all...bye04:51
takashisamP_: ok. thank you for your time04:51
*** samP_ has quit IRC04:51
takashisamP: bye04:51
rkmrHonjosamP: bye04:51
tpatil#action: samP to review and approve ha-enabled-config-options blueprint04:52
*** salv-orlando has joined #openstack-meeting04:53
abhishekksampath san has approved blueprint04:53
tpatilOk, great04:53
*** ijw_ has joined #openstack-meeting04:54
*** wxy_ has joined #openstack-meeting04:54
takashiwill have a look about implementation patch04:54
takashiwe have about 5 minutes left04:54
takashido we have any other topics?04:55
tpatilNothing from my side for now04:55
rkmrHonjoI don't have other topics.04:55
takashithanks for joining!04:56
*** Namrata has joined #openstack-meeting04:56
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"04:56
openstackMeeting ended Tue Jan 10 04:56:41 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:56
Dinesh_Bhorthank you all04:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-01-10-04.00.html04:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-01-10-04.00.txt04:56
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-01-10-04.00.log.html04:56
*** ijw has quit IRC04:57
*** tpatil has quit IRC04:57
*** nadya has quit IRC04:57
*** salv-orlando has quit IRC04:57
*** rkmrHonjo has quit IRC04:57
*** sacharya has quit IRC04:58
*** t-izumi has left #openstack-meeting05:02
*** diga has quit IRC05:03
*** reedip_outofmemo has quit IRC05:06
*** yamamot__ has joined #openstack-meeting05:06
*** nadya has joined #openstack-meeting05:07
*** ljxiash has joined #openstack-meeting05:08
*** adiantum has quit IRC05:08
*** ljxiash has quit IRC05:10
*** ljxiash has joined #openstack-meeting05:10
*** takahara has joined #openstack-meeting05:11
*** markvoelker_ has joined #openstack-meeting05:12
*** takahara has quit IRC05:12
*** chenying has quit IRC05:13
*** chenying has joined #openstack-meeting05:14
*** markvoelker has quit IRC05:15
*** markvoelker has joined #openstack-meeting05:17
*** jrobinson-afk is now known as jrobinson05:18
*** nadya has quit IRC05:20
*** markvoelker_ has quit IRC05:20
*** guoshan has joined #openstack-meeting05:21
*** qwebirc99835 has joined #openstack-meeting05:21
*** qwebirc99835 has quit IRC05:21
*** guoshan has quit IRC05:27
*** sudipto has joined #openstack-meeting05:28
*** sudipto_ has joined #openstack-meeting05:28
*** Cibo_ has joined #openstack-meeting05:28
*** sdake_ has joined #openstack-meeting05:30
*** janki has joined #openstack-meeting05:31
*** sdake has quit IRC05:32
*** sagara has left #openstack-meeting05:35
*** sudipto has quit IRC05:40
*** sudipto_ has quit IRC05:40
*** pradk has quit IRC05:42
*** yamahata has joined #openstack-meeting05:48
*** ljxiash has quit IRC05:53
*** salv-orlando has joined #openstack-meeting05:53
*** pradk has joined #openstack-meeting05:56
*** yangyape_ has joined #openstack-meeting05:56
*** diablo_rojo has quit IRC05:56
*** salv-orlando has quit IRC05:58
*** yangyapeng has quit IRC05:58
*** sacharya has joined #openstack-meeting05:59
*** sacharya has quit IRC06:03
*** guoshan has joined #openstack-meeting06:03
*** sdake has joined #openstack-meeting06:07
*** ljxiash has joined #openstack-meeting06:09
*** sdake_ has quit IRC06:09
*** wxy_ has quit IRC06:09
*** beekhof_mb has quit IRC06:09
*** lpetrut has joined #openstack-meeting06:10
*** Namrata has quit IRC06:15
*** salv-orlando has joined #openstack-meeting06:18
*** zhurong has joined #openstack-meeting06:24
*** pcaruana has quit IRC06:26
*** ykatabam has quit IRC06:30
*** rbudden has quit IRC06:34
*** armax has joined #openstack-meeting06:39
*** sridharg has joined #openstack-meeting06:39
*** yangyape_ has quit IRC06:39
*** yangyapeng has joined #openstack-meeting06:40
*** claudiub has joined #openstack-meeting06:45
*** unicell has joined #openstack-meeting06:46
*** csomerville has quit IRC06:48
*** lpetrut has quit IRC06:51
*** lpetrut has joined #openstack-meeting06:51
*** armax has quit IRC06:53
*** rbartal has joined #openstack-meeting06:55
*** mminesh has quit IRC06:57
*** ningliu has quit IRC06:57
*** bkeller` has quit IRC06:58
*** ober37 has quit IRC06:58
*** pradk has quit IRC07:02
*** unicell has quit IRC07:02
*** unicell has joined #openstack-meeting07:02
*** sdake_ has joined #openstack-meeting07:03
*** sdake has quit IRC07:06
*** qwebirc27012 has joined #openstack-meeting07:09
*** qwebirc27012 has quit IRC07:11
*** andreas_s has joined #openstack-meeting07:12
*** tesseract has joined #openstack-meeting07:13
*** unicell has quit IRC07:16
*** lpetrut has quit IRC07:16
*** unicell has joined #openstack-meeting07:17
*** rcernin has joined #openstack-meeting07:17
*** salv-orlando has quit IRC07:18
*** pradk has joined #openstack-meeting07:18
*** nkrinner_afk is now known as nkrinner07:20
*** makowals has quit IRC07:20
*** amotoki has joined #openstack-meeting07:24
*** yangyapeng has quit IRC07:24
*** makowals has joined #openstack-meeting07:26
*** Dinesh_Bhor has left #openstack-meeting07:26
*** rasca has joined #openstack-meeting07:27
*** csomerville has joined #openstack-meeting07:27
*** iyamahat has joined #openstack-meeting07:27
*** yuval has joined #openstack-meeting07:27
*** lhx__ has quit IRC07:28
*** lpetrut has joined #openstack-meeting07:28
*** yamahata has quit IRC07:28
*** lhx__ has joined #openstack-meeting07:30
*** sdake has joined #openstack-meeting07:30
*** sdake_ has quit IRC07:32
*** jprovazn has joined #openstack-meeting07:32
*** cody-somerville has joined #openstack-meeting07:32
*** csomerville has quit IRC07:35
*** lpetrut has quit IRC07:42
*** aloga has quit IRC07:42
*** aloga has joined #openstack-meeting07:42
*** yangyapeng has joined #openstack-meeting07:43
*** dtrainor has quit IRC07:43
*** egallen has joined #openstack-meeting07:47
*** eranrom has joined #openstack-meeting07:59
*** Dmitrii-Sh has joined #openstack-meeting07:59
eranrom#startmeeting storlets07:59
openstackMeeting started Tue Jan 10 07:59:44 2017 UTC and is due to finish in 60 minutes.  The chair is eranrom. Information about MeetBot at http://wiki.debian.org/MeetBot.07:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:59
*** openstack changes topic to " (Meeting topic: storlets)"07:59
openstackThe meeting name has been set to 'storlets'07:59
*** abhishekk has left #openstack-meeting08:00
*** sacharya has joined #openstack-meeting08:00
*** akihito has joined #openstack-meeting08:00
*** sridharg has quit IRC08:00
*** anilvenkata_ has quit IRC08:00
*** kota_ has joined #openstack-meeting08:01
eranromHi kota_08:01
kota_eranrom: happy new year08:01
eranromHappy new year & apologies for last week's cacellation08:01
*** sridharg has joined #openstack-meeting08:01
*** anilvenkata has joined #openstack-meeting08:02
*** sagara has joined #openstack-meeting08:02
akihitoHi! happy new year!08:02
kota_eranrom: np08:02
kota_akihito: hi happy new year08:02
eranromakihito: Hi08:02
eranromtakashi: Hi08:02
kota_takashi: hi!08:02
eranromsagara: Hi. Welcome08:02
kota_sagara: welcome!08:02
takashieranrom, kota_: Hi :-)08:02
eranromtakashi: Hi08:03
eranromok. Lets start our very first meeting for 2017 :-)08:03
takashiyes! :-)08:03
eranromI have a short agenda here: https://wiki.openstack.org/wiki/Meetings/Storlets#Agenda:08:03
eranrombut do feel free to add items.08:04
eranromYou do not need to edit, just type whatever subject you have.08:04
eranromThat is type it here in IRC :-)08:04
*** sacharya has quit IRC08:05
takashithanks for adding my items :-)08:05
eranromThe list is not all the items, just those few that I have picked from the bottom going up08:06
eranromThe idea is to look at all the list and prioritize08:06
eranromHere is the query to see all the list https://review.openstack.org/#/q/project:openstack/storlets+status:open08:06
kota_eranrom: that's same with me which is usually used.08:07
eranromkota_: right.08:08
*** wxy_ has joined #openstack-meeting08:08
*** pcaruana has joined #openstack-meeting08:09
takashiPersonally I would like to land https://review.openstack.org/#/c/406620/ first, because it fixes broken unittests, which caused by my packaging work maybe08:09
*** kevinz has quit IRC08:09
takashinot first, but asap08:09
kota_takashi: so you're waiting on me :P08:10
*** e0ne has joined #openstack-meeting08:11
eranromok from me this is https://review.openstack.org/#/c/395152/08:11
*** salv-orlando has joined #openstack-meeting08:11
eranromI kinda want to land this before I continue with taking out the storlets code from the container and complete the migration to devstack08:12
takashieranrom: I like that idea, but my only concern is that I'm not sure that (having process management script) is consistent with devstack-ish way08:12
*** korzen has joined #openstack-meeting08:13
kota_eranrom: cool, let me know what can be available on `s2aio.sh start` and `s2aio.sh stop`?08:13
eranromtakashi: right. The reason I have used it is that stack/unstack takes a long time08:13
takashiwhen using devstack, we use unstack.sh or rejoin-stack.sh for stop/restart08:14
kota_eranrom: something like cleanup/reinstall? or restarting daemon?08:14
kota_not yet looking at the actual code though08:14
takashikota_: just for stopping/restarting daemon, AFAIK08:14
kota_takashi: thx08:14
eranromkota_: what it does is basically stop/start Keystone & swift_init all restart08:14
eranromTakashi is right that there is the devstack way of doing so, but as far as I recall it is so slow08:15
eranromand I need something quick to allow me test changes to the storlets code when running functional tests08:15
takashieranrom: I see08:16
eranromtakashi: I think that the unstack code is more of a cleanup code - is that right?08:16
takashiAFAIK, they have different code for cleanup, clean.sh08:17
takashieranrom ^^^08:17
eranromtakashi: I see.08:17
takashieranrom: and unstack.sh is juse stopping all services running in devstack env08:17
*** ralonsoh has joined #openstack-meeting08:17
eranromtakashi: ok. gotcha08:17
takashiCurrently we are doing a little bit different way for process running. I mean, in devstack we totally use virtualenv for each services, but in our devstack usage we don't run swift in virtualenv.08:19
takashiSo I notice that it can be difficult for us to use unstack/rejoin-stack in current state...08:19
eranromtakashi: ok, 2 comments:08:20
takashibut when we totally adopt to devstack, I think it is better to use ordinal things (unstack,resoin-stack).08:20
takashieranrom: ok08:20
eranrom1. I have made a mistake and used stack.sh instead of rejoin-stack and this is why I thought it takes forever08:20
eranrom2. According to your last comment, I should first run swift the devstack way, and probably abandon the start/stop patch08:21
takashieranrom: I think so08:22
eranromtakashi: ok. thanks08:22
eranromAnything else on the pending patches?08:23
takashieranrom: but at the same time, having temporal script (s2aio.sh start/stop) also makes sense to me, because it is surely useful08:23
takashidoes it make sense to land your patch first, and record todo to remove that script?08:23
takashiif it takes some time to totally adopt to devstack-way.08:24
takashi(and I expect so)08:24
eranromtakashi: IMO would be good, and then we can fix it so that stop==unstack, start==rejoin08:24
takashieranrom: yes08:24
eranromtakashi: ok great. thanks08:24
eranromanything else on the patches? I think there are some long pending python functional tests patches08:25
akihitoMy functional test items are currently being fixed.08:25
akihitoSorry for the delay in fix..08:25
eranromakihito: no worries.08:25
kota_akihito: np08:25
akihitoI will fix it this week.08:25
eranromgreat. thanks08:26
eranromnext topic?08:26
takashieranrom: yes08:26
*** strigazi_AFK is now known as strigazi08:26
eranrom#topic PTG08:26
*** openstack changes topic to "PTG (Meeting topic: storlets)"08:26
eranromI guess it would be good time to start planning.08:27
eranromI will create an Etherpad and post the URL in our channel08:27
*** xek has joined #openstack-meeting08:27
*** adiantum has joined #openstack-meeting08:28
eranromIf there is nothing else on PTG, we can probably move to open discussion08:29
kota_eranrom: https://etherpad.openstack.org/p/storlets-otaca-design-summit <- this one?08:29
eranromkota_: Do you want to reuse it?08:30
takashikota_: maybe we need 'pike' version08:30
kota_i picked it up from today's agenda08:30
eranromkota_: Good that you have mentioned it, we can look for a reference at all the things we still want to do08:30
eranromkota_: I will update the meeting page with the new one :)08:31
kota_eranrom: thx!08:31
eranromonce I create it.08:31
eranromok. open discussion?08:31
kota_i might create the brand new page at etherpad08:31
eranromkota_: thanks, that was fast08:31
kota_was attempting to check the existence08:31
*** hashar has joined #openstack-meeting08:32
kota_nothing added yet though08:32
eranromkota_: no worries. It will get filled :)08:32
kota_eranrom: yes please ;-)08:33
eranromkota_: BTW do you want to bring IPython integration to Swift?08:33
*** phil has joined #openstack-meeting08:34
kota_eranrom: not sure for now, it could be nice but swift may be less interested in the ipython extension because swift is not designed to store coding cells iirc08:34
*** phil is now known as Guest9183208:34
kota_designed to storle blob rather than code08:35
eranromkota_: right. I was mainly thinking about GET/PUT08:35
eranrombut worse case we can add it in ours if we find it useful08:36
kota_i may introduce the feasibility in the design session but i think just related project would be good for swift.08:36
eranromkota_: sure.08:36
kota_thinking of storlet, i think it should be in upstream repo because it's useful to deploy storlet apps into swift08:37
kota_eranrom: and I'm waiting you to resolve your get line extension ;-)08:37
kota_resolve merge conflict08:37
eranromkota_: np. sure, I will resolve + make some changes08:38
eranromits on the top of my list :-)08:38
kota_eranrom: yeah, the point that we can get the response content as a variable is super useful.08:38
eranromkota_: indeed.08:39
takashikota_, eranrom: For me, it is very good chance to learn about iPython. :-)08:39
*** Guest91832 has quit IRC08:39
takashiand I love the idea08:39
kota_takashi: me too. I just was starting to learn in the last Dec.08:39
eranromI am working on machine learning integration with storlets, and IPython is tool many data sciuentists use08:39
*** e0ne has quit IRC08:40
eranromKota's patch came exactly at the right time for me08:40
takashieranrom: great!08:40
*** wxy_ has quit IRC08:40
kota_eranrom: yeah, to be honest, I had a chance to talk with some data scientists too.08:40
eranromkota_: any interesting insights?08:41
kota_eranrom: who uses ipython/jupyter notebook ;-)08:41
eranromkota_: Was this the reason you have added it?08:41
kota_eranrom: they said something like dry-run should be useful to test their programs before deploying08:41
kota_eranrom: sure08:42
eranroma-ha! nice!08:42
eranromok, so if we talk about it, I think the next steps could be making life easier by creating templates that automat the loading of the dataset08:43
*** phil_ has joined #openstack-meeting08:43
kota_sounds cool08:43
*** timothyb89 has quit IRC08:43
eranrome.g. instead of the data scientist needing to take the in_stream and load it, add some magic code that adds this for her08:44
eranromor him08:44
*** timothyb89 has joined #openstack-meeting08:44
eranromI will post this sometime...08:44
eranromanything else for today?08:46
*** nishaYadav has joined #openstack-meeting08:46
*** jprovazn has quit IRC08:46
akihitoI'm nothing.08:46
kota_that's full08:47
*** e0ne has joined #openstack-meeting08:47
*** ataraday has quit IRC08:47
takashinothing from my side08:47
eranromsagara: ?08:48
eranromok all so thank very much for joining!08:48
eranromtalk to you later!08:49
kota_thanks eranrom leading the meeting!08:49
akihitothank you!08:49
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"08:49
openstackMeeting ended Tue Jan 10 08:49:18 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-01-10-07.59.html08:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-01-10-07.59.txt08:49
openstackLog:            http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-01-10-07.59.log.html08:49
*** dimtruck is now known as zz_dimtruck08:50
*** eranrom has quit IRC08:52
*** jrobinson has quit IRC08:52
*** neiljerram has quit IRC08:53
*** nmagnezi has joined #openstack-meeting08:54
*** rcernin has quit IRC08:54
*** tesseract has quit IRC08:54
*** priteau has joined #openstack-meeting08:55
*** pcaruana has quit IRC08:55
*** ayogi has joined #openstack-meeting08:55
*** jrobinson has joined #openstack-meeting08:56
*** Wenzhi has quit IRC08:56
*** rossella_s has joined #openstack-meeting08:57
*** toscalix has joined #openstack-meeting08:59
*** iyamahat has quit IRC08:59
*** rossella_ has joined #openstack-meeting09:02
*** kota_ has left #openstack-meeting09:02
*** mickeys has quit IRC09:03
*** rossella_s has quit IRC09:03
*** tesseract has joined #openstack-meeting09:07
*** pcaruana has joined #openstack-meeting09:08
*** rcernin has joined #openstack-meeting09:08
*** nishaYadav has quit IRC09:15
*** lyarwood is now known as lyarwood_09:18
*** kota_ has joined #openstack-meeting09:23
*** nadya has joined #openstack-meeting09:31
*** lindycoder has joined #openstack-meeting09:32
*** lindycoder has quit IRC09:32
*** rcernin has quit IRC09:34
*** sagara has quit IRC09:34
*** pabelanger has quit IRC09:35
*** wznoinsk has quit IRC09:35
*** njohnston has quit IRC09:35
*** mmedvede has quit IRC09:35
*** abramley has quit IRC09:35
*** abramley has joined #openstack-meeting09:35
*** wznoinsk has joined #openstack-meeting09:35
*** pcaruana has quit IRC09:35
*** tesseract has quit IRC09:35
*** pabelanger has joined #openstack-meeting09:35
*** mmedvede has joined #openstack-meeting09:36
*** njohnston has joined #openstack-meeting09:36
*** lpetrut has joined #openstack-meeting09:36
*** Douhet has quit IRC09:37
*** ntpttr has quit IRC09:37
*** edleafe has quit IRC09:37
*** rderose has quit IRC09:37
*** otherwiseguy has quit IRC09:37
*** weshay has quit IRC09:37
*** rbergeron has quit IRC09:37
*** denaitre_ has quit IRC09:37
*** beisner has quit IRC09:37
*** slagle has quit IRC09:37
*** dalvarez has quit IRC09:37
*** cgoncalves has quit IRC09:37
*** _alastor_ has quit IRC09:37
*** swifterdarrell has quit IRC09:37
*** ityaptin has quit IRC09:37
*** bapalm has quit IRC09:37
*** notmyname has quit IRC09:37
*** dewanee has quit IRC09:37
*** _matthias_ has quit IRC09:37
*** stevemar has quit IRC09:37
*** honza has quit IRC09:37
*** freerunner has quit IRC09:37
*** rakhmerov has quit IRC09:37
*** IgorYozhikov has quit IRC09:37
*** tnarg has quit IRC09:37
*** sigmavirus has quit IRC09:37
*** alpha_ori has quit IRC09:37
*** andreykurilin has quit IRC09:37
*** sshank has quit IRC09:37
*** kencjohnston has quit IRC09:37
*** clayg has quit IRC09:37
*** rakhmerov has joined #openstack-meeting09:37
*** ntpttr has joined #openstack-meeting09:37
*** andreykurilin has joined #openstack-meeting09:37
*** dewanee has joined #openstack-meeting09:37
*** honza has joined #openstack-meeting09:37
*** stevemar has joined #openstack-meeting09:37
*** tnarg has joined #openstack-meeting09:37
*** clayg has joined #openstack-meeting09:37
*** denaitre has joined #openstack-meeting09:37
*** _matthias_ has joined #openstack-meeting09:37
*** slagle has joined #openstack-meeting09:37
*** _alastor_ has joined #openstack-meeting09:37
*** rbergeron has joined #openstack-meeting09:37
*** cgoncalves has joined #openstack-meeting09:37
*** kencjohnston has joined #openstack-meeting09:37
*** ityaptin has joined #openstack-meeting09:37
*** freerunner has joined #openstack-meeting09:37
*** honza is now known as Guest4895509:37
*** _sigmavirus24 has joined #openstack-meeting09:37
*** Douhet has joined #openstack-meeting09:37
*** otherwiseguy has joined #openstack-meeting09:37
*** dalvarez has joined #openstack-meeting09:38
*** weshay has joined #openstack-meeting09:38
*** bapalm has joined #openstack-meeting09:38
*** rderose has joined #openstack-meeting09:38
*** alpha_ori has joined #openstack-meeting09:38
*** beisner has joined #openstack-meeting09:38
*** swifterdarrell has joined #openstack-meeting09:38
*** dulek has quit IRC09:38
*** bdperkin has quit IRC09:38
*** hogepodge has quit IRC09:38
*** netapp has quit IRC09:38
*** strigazi has quit IRC09:38
*** sgordon has quit IRC09:38
*** cebruns has quit IRC09:38
*** SpamapS has quit IRC09:38
*** jdurgin has quit IRC09:38
*** cardeois has quit IRC09:38
*** egarbade- has quit IRC09:38
*** edleafe has joined #openstack-meeting09:38
*** notmyname has joined #openstack-meeting09:39
*** hogepodge has joined #openstack-meeting09:39
*** strigazi has joined #openstack-meeting09:39
*** openstack has joined #openstack-meeting14:27
*** ChanServ sets mode: +o openstack14:27
*** bswartz has joined #openstack-meeting14:29
*** khushbu has quit IRC14:30
*** joanna has joined #openstack-meeting14:31
*** annp has joined #openstack-meeting14:31
*** tonytan4ever has joined #openstack-meeting14:31
*** mmotiani has joined #openstack-meeting14:32
*** markvoelker has quit IRC14:34
*** ntata has joined #openstack-meeting14:36
*** egallen has quit IRC14:37
*** sacharya has joined #openstack-meeting14:37
*** sindhude has joined #openstack-meeting14:39
*** annp_ has joined #openstack-meeting14:42
*** annp has quit IRC14:42
*** annp_ has quit IRC14:42
*** makowals_ has joined #openstack-meeting14:42
*** lamt has joined #openstack-meeting14:43
*** makowals has quit IRC14:44
*** mriedem has quit IRC14:44
*** makowal__ has joined #openstack-meeting14:44
*** nishaYadav has joined #openstack-meeting14:45
*** nishaYadav is now known as Guest3357314:45
*** egallen has joined #openstack-meeting14:45
*** makowals_ has quit IRC14:47
*** ralonsoh_ has joined #openstack-meeting14:47
*** markvoelker has joined #openstack-meeting14:48
*** beagles_ is now known as beagles14:49
*** absubram has joined #openstack-meeting14:49
*** salv-orlando has quit IRC14:49
*** egallen has quit IRC14:51
*** ralonsoh__ has quit IRC14:51
*** nadya has quit IRC14:51
*** makowal__ has quit IRC14:53
*** lennyb has joined #openstack-meeting14:53
*** makowals has joined #openstack-meeting14:53
*** links has quit IRC14:54
*** pradk- has quit IRC14:56
*** nadya has joined #openstack-meeting14:56
*** pradk- has joined #openstack-meeting14:56
*** egallen has joined #openstack-meeting14:57
*** fnaval has joined #openstack-meeting14:57
*** reedip_outofmemo has joined #openstack-meeting14:57
*** shintaro has joined #openstack-meeting14:59
*** Leo_ has joined #openstack-meeting15:00
*** Cibo_ has quit IRC15:00
*** mcunietti has joined #openstack-meeting15:01
saggi#startmeeting karbor15:01
openstackMeeting started Tue Jan 10 15:01:35 2017 UTC and is due to finish in 60 minutes.  The chair is saggi. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
*** rbak has joined #openstack-meeting15: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
saggiHi everyone15:01
yuvalhey o/15:01
saggiHow is everyone15:02
yuvalvery well15:02
*** cdelatte has joined #openstack-meeting15:03
saggiNothing in the agenda15:03
chenyingIt seam that only us now?15:03
saggi#topic bug progress report15:03
*** openstack changes topic to "bug progress report (Meeting topic: karbor)"15:03
*** jgrassler has quit IRC15:03
*** ljxiash has quit IRC15:03
*** pradk- has quit IRC15:03
*** mcunietti has left #openstack-meeting15:03
yuvala few bugs still open in dashboard15:03
*** annilai has joined #openstack-meeting15:04
chenyingI am working on this bug https://bugs.launchpad.net/karbor/+bug/1574980.15:04
openstackLaunchpad bug 1574980 in Karbor "need a mechanism to check resource status in plan" [Medium,Triaged]15:04
chenyingannilai  Hi :D15:04
yuvalhey annilai15:05
yuvalsaggi: yes, assigned to xiang, he is working on them15:05
saggiIt looks like things are shaping up15:05
chenyingdashboard Zhangshuai and xinyong are working on the bugs about dashboard.15:05
*** zhonghua1 has joined #openstack-meeting15:07
*** mickeys has joined #openstack-meeting15:08
saggiWe need to start planning things for the PTG15:08
saggispecifically things we want to coordinate with other projects15:08
saggi#topic PTG15:08
*** openstack changes topic to "PTG (Meeting topic: karbor)"15:08
saggiand things we want to show off15:09
*** markvoelker has quit IRC15:09
yuvalanyone from China coming to PTG?15:09
saggiany suggestions?15:09
*** zz_dimtruck is now known as dimtruck15:09
chenying the protection plugins about freezer. We may need think about it.15:10
*** tovin07 has quit IRC15:11
zhonghua1I will not be there :)15:11
*** tovin07 has joined #openstack-meeting15:11
chenyingyuval Husheng will come to PTG.15:11
yuvaltiramiso is scheduled to pike, we should be there for discussions15:11
*** Julien-zte has joined #openstack-meeting15:12
*** markvoelker has joined #openstack-meeting15:12
*** raj_singh has joined #openstack-meeting15:13
*** mickeys has quit IRC15:13
*** edtubill has joined #openstack-meeting15:14
chenyingGood idea. To discuss the solution about replication in cinder.15:14
*** bobh has joined #openstack-meeting15:14
*** pcarver_ is now known as pcarver15:15
*** johndperkins has left #openstack-meeting15:15
smcginnisyuval: Yes please. I really want to make sure we consider Karbor needs with any further replication design.15:15
*** lxinhui_ has quit IRC15:16
zhonghua1yuval, +115:16
*** zhonghua1 has quit IRC15:16
yuvalsmcginnis: saggi and myself will be there15:17
*** sheel has quit IRC15:17
*** egallen has quit IRC15:17
*** tommylikehu_ has quit IRC15:18
saggiWe should also talk with Manila. See how close they are to having a backup API.15:18
*** egallen has joined #openstack-meeting15:19
*** zhonghua1 has joined #openstack-meeting15:20
chenyingsaggi  I will pay close attention to the spec about share backup in manila.15:20
saggiAnything to report?15:20
saggican you link it here?15:20
chenyingwait a moment15:21
*** markvoelker has quit IRC15:21
saggiI'll check it out later15:22
*** hongbin has quit IRC15:23
saggiin any case yvual will open an etherpad for us to list talk ideas.15:23
saggi#topic open discussion15:24
*** openstack changes topic to "open discussion (Meeting topic: karbor)"15:24
saggianything else?15:24
chenyingI have submitted the patches about refactor plugins. It seem that there is a problom about vm fullstack tests. I am working on it.15:24
yuvalthere is an issue with openstack client which might cause that15:25
yuvalsee here: https://review.openstack.org/#/c/418190/15:25
*** haleyb_ has quit IRC15:25
chenyingyuval: Good job, I will check it later.15:25
yuvaland https://bugs.launchpad.net/python-novaclient/+bug/165480615:25
openstackLaunchpad bug 1654806 in python-novaclient "Functional tests (with neutron) failing with "ERROR (Conflict): Multiple possible networks found, use a Network ID to be more specific. (HTTP 409)" since 1/6" [High,In progress] - Assigned to Matt Riedemann (mriedem)15:25
*** haleyb_ has joined #openstack-meeting15:25
yuvalI think it is supposed to be fixed now15:26
*** yamamoto has joined #openstack-meeting15:26
*** zhonghua1 has quit IRC15:26
chenyingsaggi  The patches about the spec '15:27
chenyingAdd extra_info field to the response of instances API' have been rebased. Do you have time to review it?15:27
*** juzuluag has joined #openstack-meeting15:27
*** rossella_ has quit IRC15:28
saggichenying: I will try and review it today. If not tomorrow morning15:28
*** rossella_ has joined #openstack-meeting15:28
chenyingsaggi: Thanks.15:28
*** egallen has quit IRC15:30
saggiAnything else?15:30
*** bobmel has joined #openstack-meeting15:30
*** galstrom_zzz is now known as galstrom15:30
saggiOK, good job everyone. I'm glad to see the bug count going down.15:30
*** lhx__ has quit IRC15:30
saggiAt this rate we could start working on spec files for P very soon15:31
chenyingsaggi +115:31
*** salv-orlando has joined #openstack-meeting15:31
*** eharney has quit IRC15:32
*** juzuluag has quit IRC15:32
saggiThanks everybody15:32
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"15:32
openstackMeeting ended Tue Jan 10 15:32:49 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-01-10-15.01.html15:32
*** egallen has joined #openstack-meeting15:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-01-10-15.01.txt15:32
openstackLog:            http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-01-10-15.01.log.html15:32
*** nmagnezi has joined #openstack-meeting15:34
*** sneti has joined #openstack-meeting15:34
*** links has joined #openstack-meeting15:35
*** jprovazn has joined #openstack-meeting15:35
*** spzala has joined #openstack-meeting15:38
*** yamamoto has quit IRC15:38
*** belmoreira has quit IRC15:40
*** bobmel has quit IRC15:41
*** egallen has quit IRC15:41
*** hieulq_ has joined #openstack-meeting15:42
*** aslezil has joined #openstack-meeting15:42
*** mtanino has joined #openstack-meeting15:44
*** Ruijie_ has quit IRC15:45
*** egallen has joined #openstack-meeting15:46
*** lhx__ has joined #openstack-meeting15:46
*** eharney has joined #openstack-meeting15:47
*** raj_singh_ has joined #openstack-meeting15:49
*** lpetrut1 has joined #openstack-meeting15:49
*** amotoki has quit IRC15:50
*** lpetrut has quit IRC15:50
*** lpetrut1 is now known as lpetrut15:50
*** egallen has quit IRC15:51
*** dtrainor has joined #openstack-meeting15:52
*** nadya has quit IRC15:52
*** anilvenkata has quit IRC15:53
*** Guest33573 is now known as nishaYadav15:54
*** markvoelker has joined #openstack-meeting15:58
*** rbudden has joined #openstack-meeting15:58
*** hongbin has joined #openstack-meeting15:59
*** diablo_rojo_phon has quit IRC16:00
*** shintaro has quit IRC16:01
*** rbak has quit IRC16:01
*** yuval has quit IRC16:01
*** amotoki has joined #openstack-meeting16:02
*** gouthamr has joined #openstack-meeting16:03
*** donghao has joined #openstack-meeting16:03
*** claudiub has joined #openstack-meeting16:04
*** beagles is now known as beagles_brb16:04
*** rbak has joined #openstack-meeting16:04
*** mtanino has quit IRC16:05
*** sneti_ has joined #openstack-meeting16:05
*** sneti_ has quit IRC16:05
*** claudiub|2 has quit IRC16:06
*** sshank_ has joined #openstack-meeting16:08
*** bobmel has joined #openstack-meeting16:08
*** sneti_ has joined #openstack-meeting16:09
*** jaugustine has joined #openstack-meeting16:09
*** sneti has quit IRC16:09
*** mickeys has joined #openstack-meeting16:10
*** sneti has joined #openstack-meeting16:10
*** sneti has quit IRC16:10
*** sshank_ has quit IRC16:11
*** smurke- has joined #openstack-meeting16:11
*** sshank_ has joined #openstack-meeting16:12
*** vgadiraj has joined #openstack-meeting16:12
*** yarkot has joined #openstack-meeting16:13
*** mickeys has quit IRC16:14
*** hieulq_ has quit IRC16:16
*** aunnam has joined #openstack-meeting16:16
*** rtheis has joined #openstack-meeting16:17
*** iyamahat has joined #openstack-meeting16:18
*** rcernin has quit IRC16:18
*** baoli has quit IRC16:21
*** vishnoianil has joined #openstack-meeting16:21
*** salv-orl_ has joined #openstack-meeting16:22
*** fguillot has joined #openstack-meeting16:22
*** lhx__ has quit IRC16:23
*** amotoki has quit IRC16:24
*** yamahata has joined #openstack-meeting16:24
*** salv-orlando has quit IRC16:25
*** dougwig has left #openstack-meeting16:25
*** kjorgensen has joined #openstack-meeting16:28
*** absubram has quit IRC16:29
*** bobmel has quit IRC16:29
*** absubram has joined #openstack-meeting16:29
*** spotz_zzz has quit IRC16:29
*** sridharg has quit IRC16:32
*** egallen has joined #openstack-meeting16:32
*** jaypipes has joined #openstack-meeting16:35
*** amotoki has joined #openstack-meeting16:37
*** jaugustine has quit IRC16:39
*** diablo_rojo has joined #openstack-meeting16:39
*** sdake has joined #openstack-meeting16:41
*** sdake_ has quit IRC16:43
*** mpaolino has joined #openstack-meeting16:43
*** andreas_s has quit IRC16:44
*** rbartal has quit IRC16:45
*** Julien-zte has quit IRC16:46
*** jaypipes has quit IRC16:47
*** tovin07 has left #openstack-meeting16:48
*** phil_ has quit IRC16:49
*** jaypipes has joined #openstack-meeting16:52
*** links has quit IRC16:52
*** jpr has joined #openstack-meeting16:55
*** nadya has joined #openstack-meeting16:55
*** haleyb_ has quit IRC16:57
*** reedip_outofmemo has quit IRC16:57
*** ygbo has quit IRC16:57
*** jpr has left #openstack-meeting17:00
*** nkrinner is now known as nkrinner_afk17:01
*** strigazi is now known as strigazi_AFK17:02
*** rtheis has quit IRC17:02
*** rfolco has quit IRC17:03
*** rfolco has joined #openstack-meeting17:04
*** ansmith has quit IRC17:05
*** nadya has quit IRC17:06
*** beagles_brb is now known as beagles17:09
*** mickeys has joined #openstack-meeting17:10
*** chyka has joined #openstack-meeting17:12
*** rbudden has quit IRC17:13
*** gyee has joined #openstack-meeting17:13
*** david-lyle has joined #openstack-meeting17:13
*** iyamahat has quit IRC17:13
*** iyamahat has joined #openstack-meeting17:14
*** vishwanathj has joined #openstack-meeting17:14
*** mickeys has quit IRC17:15
*** nishaYadav has quit IRC17:16
*** Swami has joined #openstack-meeting17:16
*** mickeys has joined #openstack-meeting17:18
*** e0ne has quit IRC17:20
*** ociuhandu has quit IRC17:20
*** morgabra_ is now known as morgabra17:21
*** morgabra has joined #openstack-meeting17:21
*** ansmith has joined #openstack-meeting17:23
*** ijw_ has quit IRC17:23
*** pcaruana has quit IRC17:25
*** krtaylor has quit IRC17:28
*** tesseract has quit IRC17:31
*** rreimberg has joined #openstack-meeting17:32
*** baoli has joined #openstack-meeting17:33
*** vishwanathj has quit IRC17:35
*** unicell has quit IRC17:35
*** ociuhandu has joined #openstack-meeting17:36
*** vishwanathj has joined #openstack-meeting17:38
*** russellb has quit IRC17:40
*** lekha has quit IRC17:40
*** cFouts has quit IRC17:41
*** jaypipes has quit IRC17:41
*** jaypipes has joined #openstack-meeting17:43
*** russellb has joined #openstack-meeting17:45
*** adiantum has quit IRC17:45
*** vishwanathj has quit IRC17:46
*** claudiub|2 has joined #openstack-meeting17:47
*** nug- has joined #openstack-meeting17:47
*** claudiub has quit IRC17:49
*** nadya has joined #openstack-meeting17:49
*** nadya has quit IRC17:50
*** lpetrut has quit IRC17:51
*** skraynev_ has joined #openstack-meeting17:54
*** spilla has joined #openstack-meeting17:56
*** diablo_rojo has quit IRC17:57
*** thingee has quit IRC17:58
*** abalutoiu has joined #openstack-meeting17:58
*** browne has joined #openstack-meeting17:58
*** diablo_rojo has joined #openstack-meeting17:58
*** chrisplo has joined #openstack-meeting17:59
*** gagehugo has joined #openstack-meeting18:00
*** unicell has joined #openstack-meeting18:00
*** unicell has quit IRC18:00
stevemarping for meeting agrebennikov, amakarov, annakoppad, ayoung, bknudson, breton, browne, chrisplo, crinkle, davechen, dolphm, dstanek, edmondsw, edtubill, gagehugo, gyee, henrynash, hrybacki, jamielennox, jaugustine, jgrassler, knikolla, lamt, lbragstad, kbaikov, ktychkova, morgan, nisha, nkinder, notmorgan, raildo, ravelar, rderose, rodrigods, roxanaghe, samueldmq, shaleh, spilla, srwilkers, StefanPaetowJisc, s18:00
stevemartevemar, topol18:00
*** thingee has joined #openstack-meeting18:00
stevemar#startmeeting keystone18:00
openstackMeeting started Tue Jan 10 18:00:50 2017 UTC and is due to finish in 60 minutes.  The chair is stevemar. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: keystone)"18:00
openstackThe meeting name has been set to 'keystone'18:00
*** jaugustine has joined #openstack-meeting18:01
stevemarhi everyone18:01
*** edmondsw has joined #openstack-meeting18:01
*** ijw has joined #openstack-meeting18:01
jaugustine \o/18:01
stevemar#link agenda for today https://etherpad.openstack.org/p/keystone-weekly-meeting18:01
stevemarhey bknudson18:02
stevemarlets get going18:02
*** krtaylor has joined #openstack-meeting18:02
stevemar#topic Announcements18:02
*** openstack changes topic to "Announcements (Meeting topic: keystone)"18:02
stevemarCurrent week is R-6 -- 6 weeks until we release!18:02
*** nug- is now known as cFouts18:02
*** hashar has quit IRC18:02
stevemarthat means everything has to be done *well* before that :)18:02
stevemarGame plan for library releases is the following...18:03
stevemarR5 (next week) is the last week for client libs (keystoneauth, keystoneclient, keystonemiddleware, and pycadf)18:03
stevemarI will release new versions of these libraries this week and only re-release if necessary.18:03
stevemarso basically, if you don't have your patch merged into ksc/ksa/ksm by EOD, don't bet on it becoming part of the O release18:04
*** Guest34220 is now known as medberry18:04
*** ralonsoh_ has quit IRC18:04
*** medberry has quit IRC18:04
*** medberry has joined #openstack-meeting18:04
*** medberry is now known as med_18:04
stevemarthe re-release part is only if we muck up and another project is hurt18:04
stevemar(or a requirements bump)18:04
*** annilai has quit IRC18:04
stevemarGame plan for feature work is the following...18:04
stevemarR4 (week after next -- Jan 23-27) is the last week of Ocata-3, all features must be implemented by mid-week.18:05
stevemarDon't anticipate getting huge changes into the RC period18:05
stevemarwe bumped "role check in middleware" to Pike18:05
*** thingee has quit IRC18:05
stevemarthere is only "shadow mapping" and "query for users with expired passwords" left to implement18:05
stevemari think those are do-able by next week18:05
*** thingee has joined #openstack-meeting18:05
stevemarspilla / lbragstad you are the owners of those bps, do you agree?18:06
lbragstadstevemar for sure - i'll have a new patchset up for shadow mapping today18:06
dstanekshort cycle during a holiday period. i sortof expected some delays18:06
*** ansmith has quit IRC18:06
stevemardstanek: yes, we definitely over-committed :)18:06
rderosestevemar: also, extending user api to support federated attributes18:06
rderose(left to implemented, but well underway18:06
spillaI should be able to finish by next week18:07
lbragstadstevemar dstanek and I broke that work into two separate pieces, the implementation should be finished with my patch but dstanek's patch has the magic that allows for getting projects into the mapped properties18:07
stevemarrderose: get as much of that complete as you can, but theres a lot to do, we need to figure out what the criteria is for marking that complete, i expect some spill over into Pike18:07
lbragstaddstanek's patch is really close, and I wouldn't be surprised if we couldn't get that merged within the next 48 hours18:07
*** thingee has quit IRC18:07
stevemarspilla: rgr, your stuff is close anyway18:07
stevemarso if folks are looking to review things, review those BPs, bug rderose / lbragstad / spilla for links18:08
stevemaror better yet18:08
stevemar#link https://review.openstack.org/#/q/topic:bp/shadow-mapping18:08
*** egallen_ has joined #openstack-meeting18:08
*** thingee has joined #openstack-meeting18:08
lbragstadyep ^18:08
stevemar#link https://review.openstack.org/#/c/403898/18:09
*** mpaolino has quit IRC18:09
stevemar#link https://review.openstack.org/#/q/topic:bp/support-federated-attr18:09
stevemar(the second one is query users for expired passwords)18:09
*** iyamahat has quit IRC18:09
spillastevemar: ty18:09
stevemarlast of my game plans :)18:10
stevemarGame plan for stable releases is the following...18:10
stevemarWill be releasing mitaka and newton versions for: keystone, keystoneclient, keystonemiddleware, and keystoneauth either this week or next.18:10
stevemarI had to fix the gate for KSA and KSM so that slowed me down18:10
dstaneklbragstad:  is there anything left to do to it?18:10
stevemarbut to everyone else: Propose any backports that you would like to see included! Otherwise I will propose to release from whatever is the latest commit.18:10
lbragstaddstanek not sure - i need to follow up with you and samueldmq about your conversation from earlier, but we can do that after the meeting18:10
stevemarthis is for stable/mitaka and stable/newton18:10
*** yamahata has quit IRC18:10
stevemarbackports to stable/mitaka should only be security or performance related18:11
samueldmqlbragstad: ++18:11
samueldmqlbragstad: just some differences from the spec, like creating the roles that do not exist18:11
stevemarmitaka will be going EOL in a few weeks ~ months18:11
samueldmqlbragstad: but they're minor things, looking great overall18:11
stevemarmitaka EOL is 2017-04-1018:11
*** egallen has quit IRC18:12
*** egallen_ is now known as egallen18:12
stevemarlast announcement18:12
stevemar#topic PTG18:12
*** openstack changes topic to "PTG (Meeting topic: keystone)"18:12
*** jprovazn has quit IRC18:12
stevemarPike PTG etherpad is here:18:12
stevemar#link  https://etherpad.openstack.org/p/keystone-pike-ptg18:12
*** toscalix has quit IRC18:12
stevemara full list for all projects is here:18:13
stevemar#link https://wiki.openstack.org/wiki/PTG/Pike/Etherpads18:13
*** nadya has joined #openstack-meeting18:13
stevemar(the eventbrite page isn't loading for me)18:14
stevemarbut its here: https://www.eventbrite.com/e/project-teams-gathering-tickets-2754929869418:14
stevemari'll be buying my ticket today18:14
stevemarhave my hotel booked18:14
gagehugonot loading for me either18:15
stevemarit was a bit slow, loaded now18:15
stevemar146 tickets left18:15
dstanek146 remaining tickets18:15
knikollaworth noting is that for the boston summit, there will be no ATC codes distributed. but you'll get a code through your PTG ticket.18:15
dstanekthey've been going slow18:15
stevemarknikolla: that is correct18:15
topolThat RDU to ATL flight is brutal.  Sometimes you dont even have time get a drink on the plane18:16
stevemargoing to the PTG will get you free pass for the boston summit18:16
stevemartopol: my movie may not even finish in time18:16
lbragstadalso - i got a note in my personal mailbox about booking hotels at a discounted rate for the Atlanta PTG18:16
dolphmtopol: sounds like a challenge18:16
stevemaranyone else know if they going / not going?18:17
knikollagoing. still need to book travel/accomodation. where are y'all staying?18:17
dolphmyou'll also only get a code for the summit/forum through your PTG ticket IF you actually show up to the PTG18:17
stevemarknikolla: at the conference hotel18:17
stevemardolphm: that is also true18:17
stevemarhopefully not too many people don't think they can abuse that :)18:18
*** nadya has quit IRC18:18
*** korzen has quit IRC18:19
dstanekstevemar: going..but not sure about hotel just yet18:19
*** cFouts is now known as nug18:19
morgansorry a little late18:19
stevemarmorgan: 5 demerit points18:19
knikollastevemar: conference hotel was on the expensive side18:19
*** VW has quit IRC18:19
morgan5 points from gryffindor18:19
topol10. he's like 20 mintues late18:19
*** nug is now known as Guest3117618:19
morganwith the sheraton discount it was about avg for atl "big" hotels18:19
morgantopol: shush18:19
*** ravelar has joined #openstack-meeting18:19
topolare folks getting rental cars?18:20
*** ravelar has joined #openstack-meeting18:20
knikollai'll probably end up on an airbnb as usual18:20
*** VW has joined #openstack-meeting18:20
lbragstadi was just planning getting an Uber if required18:20
gagehugouber ++18:20
morgani'm just going to carpool with topol everywhere18:20
stevemartopol: not really much point since the hotel and conference are at the same place18:20
morganthe keystone uber driver18:20
dolphmmorgan: ++18:20
topolI may just uber then18:20
dolphmtopol: uber will pay you, you know18:21
morgandolphm: ++18:21
stevemaralright, let's switch gears, the ptg will be very fun, everyone should come18:21
samueldmqI haven't got travel approval yet18:21
morgani mean, we wont pay you18:21
samueldmqbut I heard at least the ticket is refundable18:21
stevemarif you need reasoning for a manager, i'm here for you18:21
dolphm*someone* will18:21
lbragstadsamueldmq ++18:21
morganthere is still money from the foundation i hear18:21
morganif you apply soon18:21
*** tonytan4ever has quit IRC18:21
morganfor financial assitance18:21
morganbut that is a rumor i've heard through the grapevine18:21
dolphmfor foundation travel funding: https://wiki.openstack.org/wiki/Travel_Support_Program18:22
* topol Lived in ATL for 9 years. Know some great restaurants18:22
rderosetopol: sweet!18:22
lbragstadI totally wanna go back to Max's18:22
dstanektopol: roscos chickena and waffles doesn't count18:22
morgandstanek: ++18:22
stevemaralrighty, really switching to next topic this time :)18:22
stevemar#topic invalid query parameters [lamt]18:23
dolphm#link apply for travel funding https://openstackfoundation.formstack.com/forms/travelsupportptg_atlanta18:23
*** openstack changes topic to "invalid query parameters [lamt] (Meeting topic: keystone)"18:23
stevemarlamt: you're up18:23
lbragstad#link https://launchpad.net/bugs/165408418:23
openstackLaunchpad bug 1654084 in openstack-api-wg "Listing resources with invalid filters should result in a 400" [Medium,In progress] - Assigned to Ed Leafe (ed-leafe)18:23
lamtthanks - stevemar. #link https://review.openstack.org/#/c/417315/518:23
*** rasca has quit IRC18:23
*** tonytan4ever has joined #openstack-meeting18:24
lamtThe bug is to correct the behavior when a user specifies an invalid parameter in the URL18:24
morgani like this change but it is an API contract break18:24
lamtright now the code silently ignores the bad parameter, instead of returning 40018:24
*** mmalik4 has joined #openstack-meeting18:24
morganso... without something like microversions or otherwise18:25
morgani have to be a -2 on this.18:25
*** rbudden has joined #openstack-meeting18:25
morganit is a contract (implicit) break18:25
morgansince we have historically ignored it18:25
morgansorry :(18:25
bknudsonI think the server should ignore invalid parameters since then new clients can work well enough with older servers18:25
morgani really do like being more explicit18:25
*** ansmith has joined #openstack-meeting18:26
*** neiljerram has quit IRC18:26
morganbut if you can convince mr PTL is isn't really a contract break, I'll just continue on my way and not be against it18:26
stevemaroh it is, i thought we were allowed to if fixing behaviour?18:26
morganlikewise, if we add a simple param all clients can send "&strict_query" and that causes the 40018:26
* lbragstad #link https://bugs.launchpad.net/keystone/+bug/1654084/comments/418:27
openstackLaunchpad bug 1654084 in openstack-api-wg "Listing resources with invalid filters should result in a 400" [Medium,In progress] - Assigned to Ed Leafe (ed-leafe)18:27
morganstevemar: imo not really, we are allowed to do things like 400 -> better 4xx error18:27
morganor 500 -> proper non-500 error18:27
morganbut changing a 200 to a 400 is not good.18:27
lbragstadmorgan aha - that makes sense18:27
stevemarThe change is the only way to fix a security bug.18:27
stevemarFixing a bug so that a request which resulted in an error response before is now successful.18:27
stevemarAdding a new response header.18:27
stevemarChanging an error response code to be more accurate.18:27
*** Swami has quit IRC18:28
gagehugo"unless the success reported previously was hiding an existing error condition"18:28
morganand this isn't hiding an error condition18:28
gagehugobut then that's up in the air if it's really an "error"18:28
bknudsonthis isn't saying we can't fix it. just that we can't change the behavior without a microversion.18:28
morganit's just ignoring input that is invalid18:28
morganbknudson: ++18:28
*** egallen has quit IRC18:28
morgani am -2 on the change as is. with a api version (microversion or otherwise) we can totally move forward18:28
stevemarsounds fair, sorry lamt, i got my rules mixed up18:29
morganalso, it's about 50/50 on if an API rejects or ignores query params18:29
morganin the wild18:29
stevemarmorgan: yaeh, its pretty weird18:29
stevemarfor web searches it's pretty much always ignore18:29
morganso i'm going to toss a -2 on it and comment on the bug again.18:29
lamt:( okay - perhaps it builds a case for microversioning18:29
stevemarlamt: definitely18:29
lbragstadmorgan the "strict" case is interesting18:29
morganlbragstad: yep possibly18:30
morganthere are ways to slice this18:30
morganand i'm open to that18:31
lbragstadbut - would that make us one of the only projects that supports both?18:31
bknudsonwhat's the problem with microversioning?18:31
*** unicell has joined #openstack-meeting18:31
stevemarbknudson: nothing, no one has done it yet :)18:31
stevemarbknudson: but i think lamt is going to do it :P18:32
bknudsonI don't even see this as a bug.18:32
bknudsonwhat problem is it causing?18:32
lamtstevemar : the spec is approved, perhaps something for Pike?18:32
stevemarits for correctness i guess, HTTP spec (and the API working group) say it should be a 40018:32
stevemarbknudson: ^18:33
stevemarlamt: totally, but ask whoever is PTL then :P18:33
lbragstadstevemar ++18:33
bknudsonok, if the goal is to be consistent.18:33
morgancommented on the bug and -2 on the review18:33
stevemarthanks morgan18:33
lbragstadif we're aiming for consistency, then i'd opt for the microversion18:33
bknudsonmy understanding is that nova solved API consistency changes through microversioning18:33
*** lyarwood_ is now known as lyarwood18:33
morganhappy to remove the -2 once we have a path forward that isn't breaking contract18:33
morganand i am 100% for a path forward (ftr) :)18:34
morganbknudson: yep18:34
stevemarbknudson: you going to give up microversions? :)18:34
morganthat is the plan.18:34
stevemargive us*18:34
*** iyamahat has joined #openstack-meeting18:34
*** Leo_ has quit IRC18:34
morgani'm fine with microversions, it's a lot of work, but would make some changes much easier18:34
morganwith a monotonic increase and clear support paths.18:34
stevemarsomething to think about for Pike18:35
morganbut i don't want half-assed impl.18:35
morgani'll be very critical of the spec fwiw.18:35
morganand code.18:35
stevemarmorgan: the spec is already approved18:35
*** iyamahat has quit IRC18:35
morganoh hah right18:35
bknudsonhalf-assed impl is a good description of keystone.18:35
morganthen the code18:35
morgani think i helped approve the spec now that i think about it18:35
morganbknudson: half-assed key-value store via REST API that sortof manages identity information for openstack18:36
* morgan stops being too snarky18:36
stevemarbknudson: you need to fix it all18:36
morganstevemar: rm -rf18:36
morganstevemar: done18:36
stevemarmorgan: i think you mean rm -rf stevemar18:36
bknudsonjust rewite it in go.18:36
morganbknudson: i hear we should do it in erlang18:37
morganbknudson: it's clearly the right choice.18:37
stevemaralright, someone mentioned go, that means topic change18:37
bknudsonnice, then we could replace running code.18:37
lbragstadjust *go* rewrite it...18:37
* lbragstad slaps knee18:37
morganbknudson: and it needs to use toml instead of json (*glances around to see if anyone barfs*)18:37
stevemar#topic Adding domain_id to the user table [ rderose ]18:37
*** openstack changes topic to "Adding domain_id to the user table [ rderose ] (Meeting topic: keystone)"18:37
rderosethis may be a little early, but wanted to get this in front of you now18:37
morganrderose: is this instead of a FK-like implement?18:38
rderoseproblem: need to add the domain for federated users18:38
stevemar#link  https://review.openstack.org/#/c/409874/18:38
rderosemorgan: ?18:38
morgani mean... don't we already have domain_id in the user tablre?18:38
bknudsonI thought it was protocol buffers.18:38
morganbknudson: shush18:38
rderosecurrently domain_id is in the local_user table and federated users don't have a domain defined18:38
rderosethe domain will now come from the idp domain, but we need to properly set it for federated users18:38
morganmakes sense to me.18:39
rderosesolution: move domain_id up to the user table and create a foreign key relationship to the local user table, so that:18:39
rderose"user.id, user.domain_id -> local_user.user_id, local_user.domain_id" (1:1)18:39
*** e0ne has joined #openstack-meeting18:39
rderosehttps://drive.google.com/file/d/0BxjKpg1oYSKRVXFPQXlWT2tDYzQ/view?usp=sharing (only before and after, ignore last 2 pages)18:39
stevemarthat line makes sense to me18:39
morgani wouldn't bother with the FK. just do it as a straight orm relationship18:39
*** skraynev_ has quit IRC18:39
rderosethe domain_id is still needed in the local_user table to ensure that the domain_id-name is unique18:39
morganit doesn't need to be a FK18:39
morganoh it does..18:39
*** iyamahat has joined #openstack-meeting18:39
rderosemorgan: the fk constraint will ensure that the user will belong to a single domain and that the domain is in sync between the 2 tables.18:40
morganyou can'd do FK(local_user || non_localuser) can you?18:40
morganin SQL18:40
rderosemorgan: why?18:40
*** yamahata has joined #openstack-meeting18:40
*** VW has quit IRC18:40
morganjust curious18:40
morgannot syaing it's better18:40
lbragstadthat way we wouldn't need to duplicate it across tables18:40
morganit could make the FK from whichever is authoritative for the user object (local or non)18:41
*** lpetrut has joined #openstack-meeting18:41
lbragstadand domain_id would always come from the user table, but be used in the localuser table for uniqueness18:41
morganbut i mean thqt might be stupic complex18:41
rderoselbragstad: it's not duplicate (well sort of), but it's needed in the tables to ensure domain/name uniqueness18:41
lbragstadrderose right18:41
*** VW has joined #openstack-meeting18:42
morganok i don't see an issue with moving it around.18:42
stevemarrderose: yeah, do what you gotta do18:42
morganwould non-local user also get the same FK entry?18:42
*** acoles is now known as acoles_18:42
stevemarrderose: you're the expert on all things shadow related now18:42
morganso you would see the data in either table18:43
*** VW has quit IRC18:43
morgani ask because that might be just convinent18:43
rderoseI should have the patch ready in a day or 2 for review18:43
*** VW has joined #openstack-meeting18:43
rderosebut just wanted to get it in front of folks in case there were any strong objections18:43
rderosemorgan: yes18:43
morganthen i think this makes a lot of sense18:43
rderosestevemar: cool18:43
rderosethat's it then18:43
stevemar#topic open discussion18:44
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:44
morganother stupid question... cna you have nonlocal user and local user for the same <user> record?18:44
stevemarany takers?18:44
morgani think i saw code preventing that18:44
rderosemorgan: account linking18:44
morganok cool18:44
morganjust making sure.18:44
lbragstadi don't think we've implemented account linking, but that sounds like it would make it possible to have a nonlocal user and a local user link to the same user reference18:45
morganstevemar: please give the backport stable link?18:45
*** Swami has joined #openstack-meeting18:45
morgananyone who wants to review stable, please look at the reviews18:45
stevemarmorgan: to what? open reviews?18:45
morganthe one you gave me yesterday18:45
morgani'm going to sweep through today18:45
rderoselbragstad: we haven't implemented account linking, but part of the shadow user goals was to build a data model that would support it18:45
morganbut if you have concerns, please take a look18:45
stevemarhttps://review.openstack.org/#/q/project:openstack/keystone+branch:stable/newton https://review.openstack.org/#/q/project:openstack/keystone+branch:stable/mitaka18:46
lbragstadrderose ++18:46
stevemarhttps://review.openstack.org/#/q/project:openstack/keystoneauth+branch:stable/newton and https://review.openstack.org/#/q/project:openstack/keystoneauth+branch:stable/mitaka18:46
stevemarwe need more people proposing backports to stable, keeping an eye on the gates, and reviewing patches18:46
morganonly a couple of us have stable +2 rights. (mostly us crazy pendantic folks)18:46
lbragstadstevemar i'll make a note to look through today18:47
*** rbak has quit IRC18:47
morganplease propose the backports so us stable reviewes have an easier time landing18:47
* dolphm needs to make a dashboard dedicated to stable branches18:47
*** rbak has joined #openstack-meeting18:47
morganif you have code that is indended to backport, please propose it yourself to the stable branches :)18:47
stevemarits pretty easy to query...18:47
morganit really does make the few of us more capable of landing. if stevemar, dolphm, or I propose the backport, you're limiting who can review18:47
stevemaryeah, theres a "cherry-pick" button in gerrit that makes it stupid easy18:47
dolphmmorgan: ++18:48
lbragstaddolphm i started using https://github.com/lbragstad/dotfiles/blob/master/dashboards/keystone-stable.ini18:48
dolphmlbragstad: i'll share mine when it's ready :P18:48
*** pvaneck has joined #openstack-meeting18:48
stevemar#link https://review.openstack.org/#/q/project:"^openstack/@keystone@" -project:openstack/charm-keystone is:open branch:"^stable/@" -project:openstack/puppet-keystone18:48
dolphmnot quite how that works ^18:49
stevemaroh we also need someone to make this same change in keystoneclient: https://review.openstack.org/#/c/418194/18:49
stevemarif someone is looking for easy work18:49
*** qwebirc69042 has joined #openstack-meeting18:50
stevemaralright, i think we're done here18:50
samueldmqstevemar: I can change that in the ksc18:50
samueldmqstevemar: that and backports, right ?18:51
stevemaroh also Pike PTL nomination is from Jan 23 - Jan 2718:51
*** ekcs has joined #openstack-meeting18:51
stevemarsamueldmq: yeah, the backports need love too18:51
* samueldmq nods18:51
morganin short, don't make dolphm or myself come out of retirement... we like where we are18:51
morganand since stevemar is not running...18:52
morganstep up :)18:52
samueldmqmorgan: ++18:52
morgandolphm: right?!18:52
*** AJaeger has joined #openstack-meeting18:52
stevemaralrighty, hope to see everyone at the PTG in a few weeks!18:52
lbragstadstevemar ++ i'm looking forward to it :)18:52
dolphmgo go nominations #notPTL18:53
morgani gotta book a planeflight.18:53
morganalso #notPTL18:53
lbragstaddolphm morgan stevemar y'all sell the job so well!18:53
stevemarits a lot of fun!18:53
* stevemar ends meeting before he's caught in his lie18:54
samueldmqyeah, very inspiring18:54
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"18:54
openstackMeeting ended Tue Jan 10 18:54:06 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-01-10-18.00.html18:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-01-10-18.00.txt18:54
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-01-10-18.00.log.html18:54
*** zara_the_lemur__ has joined #openstack-meeting18:56
*** browne has left #openstack-meeting18:56
*** bobmel has joined #openstack-meeting18:57
*** qwebirc69042 has quit IRC18:58
*** olaph has joined #openstack-meeting18:59
*** ianychoi has quit IRC19:00
*** ravelar has left #openstack-meeting19:00
fungiinfra team, assemble!19:00
* zara_the_lemur__ assembles19:00
jeblairfungi: a whole HOUR?19:00
fungimight not be the _whole_ hour19:01
*** jaypipes has quit IRC19:01
fungilooks like i have the only topics on the agenda this week anyway19:01
jeblair[or portion thereof]19:01
fungiso probably can cut it short19:01
fungiso slack i only put one of my two topics on the agenda, and it's a hold-over from last week19:01
jeblairi probably should have put 'nodepool release' on the agenda19:01
fungithere's still time19:01
fungii'll add it. i'm editing now19:02
*** sneti has joined #openstack-meeting19:02
jeblairfungi: okay, thx.  i'm not logged in, so... you know... it'd take a few minutes19:02
fungiokay, now we have topics from fungi, jeblair and (by proxy) AJaeger19:04
*** ekcs has quit IRC19:04
*** d0ugal has quit IRC19:04
*** jamesdenton has joined #openstack-meeting19:04
fungi#startmeeting infra19:04
openstackMeeting started Tue Jan 10 19:04:15 2017 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:04
*** openstack changes topic to " (Meeting topic: infra)"19:04
openstackThe meeting name has been set to 'infra'19:04
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:04
fungi#topic Announcements19:04
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:04
*** sneti has quit IRC19:04
fungii don't have any for this week, which is pretty sad19:04
fungias always, feel free to hit me up with announcements you want included in future meetings19:04
fungi#topic Actions from last meeting19:05
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:05
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-12-20-19.03.html19:05
fungi"1. (none)"19:05
fungi#topic Specs approval19:06
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:06
*** galstrom is now known as galstrom_zzz19:06
fungiwe don't seem to have anything new up this week19:06
fungi#topic Priority Efforts: Nodepool: Use Zookeeper for Workers (jeblair)19:06
*** openstack changes topic to "Priority Efforts: Nodepool: Use Zookeeper for Workers (jeblair) (Meeting topic: infra)"19:06
fungisomething something release something something19:06
*** galstrom_zzz is now known as galstrom19:06
fungiis this spec effectively implemented now, btw?19:07
morganfungi: orly19:07
jeblairfungi: huh, i reckon it is19:07
jeblaircause the next phase of nodepool work is covered in the zuulv3 spec19:08
*** gagehugo has left #openstack-meeting19:08
fungii like crossing things off the priority efforts list, so feel free to propose a change marking this spec implemented19:08
jeblair#action jeblair mark http://specs.openstack.org/openstack-infra/infra-specs/specs/nodepool-zookeeper-workers.html implemented19:08
jeblairto celebrate that, we also want to make a release19:09
fungiearly and often19:09
jeblairwe'll be asking people to upgrade to it and use the new zookeeper-based nodepool image builders19:09
jeblairso it will require some action on the part of nodepool operators19:09
fungiwill this be a major version bump for nodepool?19:10
jeblairand i think once the release is out, we should start moving openstackci's default configuration to it19:10
*** jamesden_ has joined #openstack-meeting19:10
*** jamesdenton has quit IRC19:10
jeblairfungi: i think we wanted to hold version 1.0 for the zuulv3 implementation?19:11
fungiassuming puppet-openstackci takes care of setting up zk accordingly, that seems fine to me. though it's a disruptive upgrade insofar as state tracking will be lost right?19:11
pabelangerit doesn't today. But it is a simple install using an upstream puppet-zookeeper module19:12
*** electrofelix has quit IRC19:12
fungiprobably qualifies as a minor version bump then, especially considering semver only really starts with your 1.0.0 release anyway and 0.x.x releases are a bit of an anything-goes scenario19:12
clarkbfungi: its disruptive beacuse we haven't written a data migraion between zk and mysql19:12
jeblairfungi: yes, we don't have an automatic migration; however, it's okay to lose this data though, nodepool will just start building new images19:12
*** ociuhandu has quit IRC19:13
fungiokay, so planning for this as nodepool 0.4.0?19:13
fungiworks for me19:13
jeblairwe're looking to land one more change (deprecating the --no-builder cli option)19:14
*** guitarza1 is now known as guitarzan19:14
jeblairand then i'll write up a release announcement to make sure people know about the differences19:14
fungiis --no-deletes already deprecates?19:14
*** nadya has joined #openstack-meeting19:14
jeblairi'll poke people in #openstack-infra to help review a draft19:14
*** jaypipes has joined #openstack-meeting19:14
*** sacharya_ has joined #openstack-meeting19:14
jeblairfungi: the --no-deletes, --no-launches, --no-images, and --no-webapp were never documented because they were added due to our instance of nodepool being overwhelmed by capacity19:15
jeblair(--no-builder, otoh, was a real option)19:15
jeblairfungi: the others will be silently removed as part of the v3 effort19:15
*** chrisplo_ has joined #openstack-meeting19:15
fungiso non-public features don't really need deprecating19:16
jeblairi think --no-images is arleady gone19:16
jeblairthat's my feeling19:16
*** sacharya has quit IRC19:16
pabelangeryes, it has been removed19:16
*** AlanClark has joined #openstack-meeting19:17
fungicool, so we'll review the --no-builder deprecation, then 0.4.0 will be tagged and after that we can mark this priority spec implemented and focus on the zuul v3 spec for remaining nodepool-related bits?19:17
*** chrisplo has quit IRC19:17
jeblairfungi: yep19:17
jeblair(and work on that has started in the zuulv3 branch)19:18
fungi#info Once the --no-builder deprecation merges, nodepool 0.4.0 will be tagged; after that we can mark this priority spec implemented and focus on the zuulv3 branch for remaining nodepool-related bits.19:18
fungianything else for this we need to cover in-meeting?19:19
*** e0ne has quit IRC19:19
jeblairfungi: eot from me19:19
*** d0ugal has joined #openstack-meeting19:20
fungi#topic Priority Efforts: Docs Publishing via AFS (jeblair, pabelanger, AJaeger)19:20
*** openstack changes topic to "Priority Efforts: Docs Publishing via AFS (jeblair, pabelanger, AJaeger) (Meeting topic: infra)"19:20
fungiseems like we're close to being ready to switch dns now?19:20
AJaegerLooking at http://lists.openstack.org/pipermail/openstack-docs/2017-January/009440.html, only one point is missing:19:20
AJaegerSwitching DNS!19:20
fungii'd call that close to ready ;)19:21
AJaeger(and then testing that everything works)19:21
*** strigazi_AFK is now known as strigazi19:21
pabelangerYa, I was just looking at DNS19:21
pabelangerwant to confirm our vhost was correct19:21
AJaegerso, anytime somebody wants to change DNS, go ahead and tell all of us ;)19:21
jeblairoh neat!19:21
pabelangerbut can pull the trigger after the meeting19:21
AJaegergreat, pabelanger !19:22
jeblairfungi: looks like we might be about ready to strike another off the list ;)19:22
fungi#action pabelanger Switch DNS for docs.openstack.org from CloudSites to files01.openstack.org.19:22
fungithat look right?19:22
jeblairthe docs traffic should be significantly higher than the developer docs traffic, so it's worth keeping an eye on performance19:22
* AJaeger will sent an email as followup to their request from August - could somebody update the Racksapce ticket as well, please?19:22
AJaegerSee http://lists.openstack.org/pipermail/openstack-infra/2016-August/004690.html19:22
pabelangerfungi: WFM19:23
AJaegertheir= Cloudsites operators19:23
jeblairi recommend making the new ttl small (5 mins) at first so we can switch back quickly19:23
fungiahh, yep. they'll want to know they can delete things19:23
pabelangerjeblair: agree19:23
jeblair(and if there are performance problems, we can either tune the files01 server or add files02 fairly quickly)19:23
AJaegerwe still publish to *both*, so not directly deleting - but we should give them a heads up19:23
clarkbAJaeger: after about a week or so we can stop publishing to both?19:24
jeblairyeah, we should let this stabilize, then remove cloudsites publishing, then tell them we're done19:24
fungi#action AJaeger follow up to http://lists.openstack.org/pipermail/openstack-infra/2016-August/004690.html letting them know we're ready for site deletion.19:24
AJaegerclarkb: yes, one week should be enough.19:24
jeblair1week sounds good to me19:24
pabelangerTTL dropped to 5mins on docs.o.o19:25
AJaegerok, then let's do it ;)19:25
fungithanks pabelanger19:25
jeblairpabelanger: you mean you just dropped the current ttl?19:26
pabelangerjeblair: yes, from 60 to 519:26
pabelangerstill confirming vhost settings on files.o.o19:26
jeblairi would have recommended keeping 60 on the current address19:26
funginot strictly necessary, just increases the rate at which people will hit the new ip address once we switch that19:26
*** jamesden_ has quit IRC19:27
fungiso yes we may see a much more rapid adoption of the new server19:27
pabelangerokay, I can revert here19:27
jeblairby doing that, and then switching to a shorter ttl for the new address, we get the luxury of slowly ramping up traffic over 1 hour, but being able to switch back in 5 minutes.  now we will get all of the new traffic within 5 minutes, so if things go bad, they will go bad quickly.19:27
pabelangerack, I have reverted to 60 TTL. IP address has not changed yet19:29
*** ansmith has quit IRC19:30
*** galstrom is now known as galstrom_zzz19:30
fungianything else we need to cover on this priority effort?19:30
fungihopefully next week we can discuss marking it implemented19:31
AJaegerand then I'll ask for https ;)19:31
AJaegerbut yes, let's move on.19:31
*** cody-somerville has quit IRC19:31
*** kebray has joined #openstack-meeting19:31
fungiAJaeger: i have a couple certs i need to renew within the next few weeks and a couple more from a few months ago i need to expense, so happy to tack docs.o.o on while i'm at it ;)19:31
fungi#action fungi Obtain docs.openstack.org X.509 certificate.19:32
AJaegerfungi, please do! A week or two longer does not hurt19:32
*** strigazi is now known as strigazi_AFK19:32
AJaegerfungi: and developer.openstack.org a swell, please19:32
*** csomerville has joined #openstack-meeting19:32
*** salv-orl_ has quit IRC19:32
fungiadded both to my to do list19:32
jeblairalso, ipv6?19:32
fungi#action fungi Obtain developer.openstack.org X.509 certificate.19:32
*** spilla has left #openstack-meeting19:33
fungiwe'll have ipv6 from files01.o.o automatically right?19:33
jlvillalI'm guessing don't use letsencrypt then.19:33
jeblairderp, yes.19:33
fungijlvillal: not until it stabilizes, no19:33
clarkbif its a cname yes19:33
jlvillalAh, okay19:33
AJaegerfiles01 has IPv619:33
* jlvillal likes the dns-01 auth method with the dehydrated client19:34
fungijlvillal: worth revisiting next year though, maybe19:34
fungicatch me outside the meeting for various reasons we've shied away from le so far19:34
fungiany other docs-on-afs issues need discussing today?19:35
AJaegernot that I know19:35
fungi#topic PTG planning (fungi)19:36
*** openstack changes topic to "PTG planning (fungi) (Meeting topic: infra)"19:36
fungi#link https://wiki.openstack.org/wiki/PTG/Pike/Etherpads19:36
fungi#link https://etherpad.openstack.org/p/infra-ptg-pike19:36
*** pcaruana has joined #openstack-meeting19:37
fungii primed it with the infra priority specs i don't expect to drop off the list in the next couple weeks19:37
*** ijw has quit IRC19:37
fungibut anyone who expects to attend at least monday/tuesday of the pike ptg in atlanta next month feel free to add ideas19:37
fungii expect to handle this in a mostly unconference fashion like we've done with design summit fridays previously19:38
jeblairi'm pushing to get zuulv3 runnable by then with the hope that we can start alpha-testing it against the zuul project during the ptg19:38
clarkbI would like to have a semi scheduled braindumping on debugging test failures and openstack19:38
jeblairso, hoping that we are able to do some installation/configuration work on it19:38
fungii personally expect to spend a lot of those two days on zuul v3 mainly because it's our highest-priority ongoing effort right now19:39
clarkbwith the idea that devs from other projects can drop in and hopefully learn some useful things about how we go about that19:39
fungibut there's room to do other stuff too, obviously19:39
*** Leo_ has joined #openstack-meeting19:39
fungiclarkb: that offers a great catch-all for vertical contributors who show up early in the week, so good addition19:39
fungiworth noting the qa team is running in parallel to us on monday/tuesday19:40
*** rossella_ has quit IRC19:40
clarkbya I brought it up with them too and they liked the idea. Probably we just need to set a rough time for when a subset of both groups convere in a place that is advertised to toehr devs to drop in19:40
fungiso anything that needs their coordination should probably be scheduled with oomichi19:41
*** jaugustine has quit IRC19:41
fungiif it's time-bounded then the fishbowl venue seems appropriate19:42
clarkbI think its less about being time bound and more like office hours. Let people know that others interested in helping with such things are going to be around and willing to help with it19:42
fungittx: not sure how you planned to schedule slots for the fishbowl, but maybe linking from the ptg etherpads list would be a good idea?19:42
clarkbbut maybe fishbowl is best fit for that?19:43
jeblairclarkb: maybe talk with some horizontal ptls to try to get them on board and push people to the session; we've not had great success with people just dropping into infra sessions at summits at least.19:43
ttxI was thinking setting up an ethercalc instance19:43
fungi(also entirely likely the scheduling mechanics for the fishbowl are already defined and i wasn't paying enough attention)19:43
fungittx: excellent excuse to start running ethercalc! ;)19:43
ttxI know, right :)19:43
clarkbjeblair: good point, I can do that19:43
jeblairttx: ++19:44
* fungi has been looking for an excuse for having ethercalc.o.o19:44
ttxThat will definitely help to keep that etherpad under control19:44
fungii'm happy to help puppeting that, seems like we can mostly just crib from our puppet-etherpad repo19:44
*** gordc has joined #openstack-meeting19:45
*** jaugustine has joined #openstack-meeting19:45
*** odyssey4me has quit IRC19:46
fungiprobably showing my age, but i like that the name reminds me somewhat of visicalc19:46
*** odyssey4me has joined #openstack-meeting19:46
fungiokay, so anyway, people seem to be adding to the pad. that's what i was looking for. i'll also announce it to the ml right after the meeting19:47
*** dmorita has joined #openstack-meeting19:47
fungi#action fungi announce the infra ptg pike etherpad to relevant mailing lists19:48
*** nmagnezi has quit IRC19:49
fungi#topic Repo renaming (fungi)19:49
*** openstack changes topic to "Repo renaming (fungi) (Meeting topic: infra)"19:49
fungicarried over from last week where everyone seemed to be asleep19:49
*** rossella_ has joined #openstack-meeting19:50
fungiwe have four repos up for renaming, split across two project-config cganges19:50
*** ociuhandu has joined #openstack-meeting19:50
fungithis week is a dead week in the release schedule19:50
fungi#link https://releases.openstack.org/ocata/schedule.html19:51
fungianybody up for a repo renaming maintenance, say... friday?19:51
clarkbI will be around, Friday is fine with me19:51
pabelangeras will I19:51
fungi20:00 utc?19:51
*** ansmith has joined #openstack-meeting19:51
fungimaybe that overlaps lunch for west-coasters19:52
fungi21:00 utc?19:52
pabelangereither is fine for me19:52
ianwthu i could help, but fri puts it in sat morning, but looks like enough anyway19:52
clarkbboth times are good for me ( will just eat early or late)19:52
jeblairi'll be around as backup but would prefer not to drive19:52
fungiianw: happy to have your help if a little later is better19:52
fungiianw: or earlier so you can do it on friday? we could do north american thursday afternoon19:53
fungidhellmann: ^ would that be painful this week, to have a brief gerrit outage and maybe a couple hours (your) thursday afternoon where you should avoid approving new releases?19:54
ianwthat works for me19:54
dhellmannfungi : this is probably the best time to do it before the ptg, so we can make it work19:54
ttxdhellmann: +119:55
fungidhellmann: that was my thinking too. it's teh last dead week in the schedule other than r-219:55
*** ociuhandu has quit IRC19:55
dhellmanngiven the compressed rc period this cycle, we're not going to have a lot of dead time until march19:55
dhellmannyeah, r-2 is during the rc period, so not a great time to take things offline19:56
fungiany objections to, say, 20:00 utc thursday (apac friday morning)?19:56
dhellmannthat time works for me19:56
fungii don't know how zomg-early that is for you ianw, feel free to tell me if it should be later19:56
ianw6am, all good19:57
clarkbsounds good19:57
fungiianw: you want to send a maintenance announcement to the -dev ml this morning?19:57
ianwcan do19:57
*** ekcs has joined #openstack-meeting19:57
fungibrief outage between 20:00-20:30 utc19:57
*** ijw has joined #openstack-meeting19:57
fungi#info The Gerrit service on review.openstack.org will be offline briefly for project renaming between 20:00 and 20:30 UTC this Thursday, January 12, 2017.19:58
fungithanks ianw!19:58
fungi#topic Open Discussion19:58
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:59
jlvillalReview request for gerritbot patch to add the branch name to the IRC message that announces submitted and merged patches: https://review.openstack.org/#/c/417450/19:59
fungiwe have a minute left ;)19:59
olaphI am hoping an additional core can find the time to review https://review.openstack.org/#/c/407100/19:59
pabelangerI'm still working on the zuul-launcher patch for openstackci.... I promise this week19:59
*** rossella_ has quit IRC19:59
*** makowals has quit IRC19:59
clarkbzaro: you need more reviews on gerrit things for the upgrade?19:59
*** spzala has quit IRC20:00
fungiaaaaaaand, we're out of time. thanks everyone! discussions can continue in #openstack-infra, or stay tuned for the tc meeting up next here in #openstack meeting!20:00
clarkbzaro: maybe reping people in #openstack-infra for that so we make sure it doesn't get lost in the busyness20:00
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"20:00
openstackMeeting ended Tue Jan 10 20:00:13 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-01-10-19.04.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-01-10-19.04.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-01-10-19.04.log.html20:00
*** olaph has left #openstack-meeting20:00
ttxanyone here for TC meeting ?20:00
ttxdims, dtroyer, flaper87, fungi, mordred, mtreinish, sdague: around ?20:01
ttxjohnthetubaguy and stevemar will miss this one IIRC20:01
fungiooh, yep. still around ;)20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Jan 10 20:01:23 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
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
ttxHi everyone!20:01
ttxOur agenda for today is at:20:01
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:01
* edleafe slinks to the side of the room20:01
ttx#topic Add extra-atc nominations for Trove20:01
*** openstack changes topic to "Add extra-atc nominations for Trove (Meeting topic: tc)"20:01
ttx#link https://review.openstack.org/41476420:01
ttxThe latest rev looks good to me20:01
ttxIf you pile up approvals we can merge it now20:02
* amrith is happy to answer questions about that if required20:02
ttxSounds like it has majority support and no more objections now20:02
* ttx approved and moves on20:02
EmilienMship it!20:02
amriththat was easy!20:03
ttxflaper87: yt?20:03
dimsamrith : thanks for being a mentor20:03
ttx#topic Reference doc for new language additions20:03
*** openstack changes topic to "Reference doc for new language additions (Meeting topic: tc)"20:03
amriththx dims20:03
ttx#link https://review.openstack.org/39887520:03
ttxWas counting on flaper87 to present this20:03
ttxlooks good enough to me for an initial version of the requirements20:04
ttxwe can discuss the merits of subsequent improvements as separate changes20:04
ttxhere he is20:04
flaper87sorry, couple of mins late20:04
ttxflaper87: floor is yours20:04
flaper87yeah, so, I've updated the patch and addressed the latest comments20:04
flaper87I've submitted another patch to fix the last comments from yday20:04
ttxsaw a subsequent patch already, which is good -- shall be a living document anyway20:04
flaper87(or was that today?)20:04
flaper87I just noticed Graham's last comment and I can address that20:05
EmilienMflaper87: excellent work on this first draft20:05
fungicool, i wanted to see the in-meeting discussion covering the most recent inline comments before adding my rc vote20:05
flaper87but sounds like something we can fix in subsequent patches, unless I missed something20:06
ttxcomments, remaining objections ?20:06
thingeefungi +120:06
dims+1 to living document + patches20:06
fungii still feel like it's a bit proscriptive/rigorous, but i guess it could be a lot worse so happy with this as a starting point20:06
flaper87EmilienM: danke20:06
mordredo/ (sorry I'm late - in an all-day offsite, but am lurking)20:07
flaper87flaper87: yeah, FWIW (this was part of the very first patch) I intentionally started with a higher bar20:07
thingeeflaper87 please enlighten us with regards to mugsie's comments20:07
fungii like to also consider it as compliment/counterpoint to dtroyer's cti patch for go20:07
dtroyerre Graham's comment, I think the working from earlier regarding ensuring the user/operators consistency of experience is what is important here...20:07
flaper87yeah, I think there might be a missunderstanding with my wording20:07
ttxI read it as we need to provide equivalents, that doesn't mean everyone needs to use them20:07
flaper87the crux of that section is guaranteeing the ocmpatibility from an ops perspective20:07
ttx(but they probably need a good reason not to)20:08
flaper87either by the support of already existing language features20:08
mugsie_My point about the requirements was that we may need more than just these 2 libs to get the operator consitancy20:08
flaper87or by implementing the required libs20:08
*** galstrom_zzz is now known as galstrom20:08
dtroyerfungi: I see this as the prereq/enabler for the CTI doc20:08
flaper87mugsie_: if we need more, we might need to add them there20:08
fungidtroyer: so you see this as compatible (at least in spirit) with your end of the effort?20:08
fungiseemed that way to me, but wanted to be sure it's not at odds20:08
flaper87The goal is to not break ops or other compatibility by introducing a new language20:08
dtroyerfungi: I wrote the golang cti doc with this in mind, and think it is already pretty close20:08
ttxsounds like it's at a stage where it's simpler to propose improvements as separate changes20:09
*** AndChat388401 has joined #openstack-meeting20:09
dtroyerttx ++20:09
flaper87mugsie_: would you agree with this not being a blocker ?20:09
mugsie_Not a blocker - we can amend it20:10
*** AndChat388401 is now known as stevemar_droid20:10
flaper87mugsie_: awesome, thanks. I appreciate your input on this20:10
mugsie_It's not the concept, just how it is stated right now20:10
ttxok cool20:10
ttxlook! a stevemar20:10
stevemar_droidHere-ish, mostly lurking.20:10
thingeeoh no stevemar_droid turned into a droid!20:10
flaper87ttx: a droid stevemar20:11
fungiwe haven't added a second general-purpose language (nodejs aside i don't consider js a general-purpose language) before, so i fully expect this will still need a lot of fine-tuning to meet reality20:11
ttxthis is not the droid we are looking for20:11
flaper87fungi: it will need for sure20:11
ttxAlright, we have enough votes... Any last minute objection ?20:11
* fungi just wants to see the "tc hates go" crowd eat their hats20:12
*** efried has quit IRC20:12
flaper87fungi: ++20:12
dimsLOL +1 fungi20:12
ttxI just want to get the constructive effort started20:12
*** bobmel has quit IRC20:12
mtreinishfungi: heh, we can still hate go and approve this :)20:12
smcginnismtreinish: :)20:13
flaper87yeah, I'm happy to work with ppl interested in go in this process20:13
dtroyerflaper87: that work is underway...20:13
ttxOK, last minute to object before I approve20:13
flaper87I'm not saying I'm going to code in go but I'd like to walk through this process20:13
stevemar_droidflaper87, I'm sure dtroyer will help20:13
flaper87dtroyer: yup20:13
flaper87dtroyer: by all means, feel free to ping me and keep me in the loop20:13
*** askb has joined #openstack-meeting20:13
*** dmorita has quit IRC20:13
ttxok, it's in20:14
ttxthanks for driving this flaper8720:14
flaper87go go go20:14
flaper87my pleasure20:14
EmilienMflaper87: thx again :)20:14
dtroyerThanks flaper8720:14
dimsflaper87 burning up karma :)20:14
*** sacharya_ has quit IRC20:14
ttx#topic Driver teams: establish new "driver team" concept (or not)20:14
*** openstack changes topic to "Driver teams: establish new "driver team" concept (or not) (Meeting topic: tc)"20:14
ttxstevemar posted the results of the survey question we asked driver maintainers:20:14
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2017-January/109855.html20:15
*** sacharya has joined #openstack-meeting20:15
ttxLet's use the voice-turn system to avoid speaking over one another.20:15
dimsnice work on that stevemar20:15
fungiunsurprisingly, everyone wants everything ;)20:15
ttxI can summarize my position first20:15
ttxAt this stage pretty much everyone agrees that we need to fix driver visibility on openstack website properties20:15
ttxAnd that it is the main and urgent issue to solve20:15
ttxThere is still much disagreement on whether we /also/ need to change governance to consider driver teams as official OpenStack teams20:15
ttxOn one side people wanting to be inclusive and welcoming of all forms of contributing to OpenStack success20:15
ttxOn the other side people seeing it as unnecessary, potentially diluting openness values and difficult to reverse20:16
ttxI feel like the continuing debate between the two distracts us from starting (and fully focusing on) fixing the main and urgent issue20:16
* fungi raises hand to retort at some point20:16
ttxOnce we fix that main and urgent issue, we'll be in a much better position to assess whether we still need a governance change or not20:16
ttxSo I'd like to add a third option. We have:20:16
ttx1/ Add driver teams now: https://review.openstack.org/40382920:16
*** dmorita has joined #openstack-meeting20:16
ttx2/ Clearly exclude driver teams (unless developed as a level playing field) now: https://review.openstack.org/40383620:16
ttxI'd add:20:16
ttx3/ Fix driver visibility first, table the governance choice until that's done, and see what's still needed then20:16
ttxIn the indicative vote last week neither (1) nor (2) had a clear majority, so I feel like making a call now either way would be a bad decision20:17
ttxDiscussing it again next week would just delay starting to work on fixing the main issue20:17
ttxwhich is why at this point I support (3)20:17
ttxfungi: your turn20:17
ttxnext flaper87, dtroyer20:17
*** ociuhandu has joined #openstack-meeting20:18
fungijust wanted to interject that i'm happy to liaise with the marketplace devs on improvements on that end20:18
fungithere were some indications in the survey results of improvement people wanted to see20:18
fungiwe should probably try to gather more20:18
ttxok, flaper87 ?20:19
flaper87yup, writing20:19
*** dmorita has quit IRC20:19
ttxremember to raise your hand if you want voice20:19
* ttx pipes some interlude music while flaper87 types20:20
flaper87So, as I've stated elsewhere, I believe including the drivers team is important. Drivers *are* an important part of our community. While I think we should fix the discoverability, I also think we can work on these 2 things in parallel. Therefore, I'd prefer us to take option 120:20
flaper87if people happen to not like that, then I guess I can live by #320:20
* flaper87 done20:20
ttxok, dtroyer now20:20
* dims just listens20:20
ttxnext sdague stevemar thingee20:20
dtroyerThe survey stevemar sent highlighted something for me, namely that the visibility and horizontal team access is what appears to be the highest priority.  It also highlighted how everything that appears on an OpenStack site reflects on the project, independant of actual status.20:20
* edleafe sits on his hands20:20
dtroyerI think it is very important for us to include the measure of confidence and quality for those things that appear, namely that regualt CI comparable with offical projects is performed for everything that we endorse, even unofficially, by posting it to an openstack.org site.20:21
dtroyerI would now prefer to persue #3, followed by #1 if we do not feel we can enforce our quality requirements without a governance action.20:21
* dtroyer done20:21
ttxnext stevemar, thingee20:22
*** ociuhandu has quit IRC20:22
sdagueI think I'm largely with dtroyer on this. #3 seems very reasonable way to address the major current friction points20:22
sdagueI would like to figure out if we can manage to do discovery with some kind of quality assurance without inventing new governance, because that gives more flexibility20:23
*** spzala has joined #openstack-meeting20:23
sdagueespecially because otherwise it seems like TC is going to be evaluating lots of driver team applications20:23
sdague</end> for now20:23
ttxstevemar: you're on20:23
ttxnext thingee20:23
stevemar_droidEven if we have a consistent place to list the drivers, there are many questions about what to include and the criteria for inclusion20:24
stevemar_droidAnd that seems like the same questions we'll have about what makes them official20:24
stevemar_droidI like sdagues last point though20:24
* stevemar_droid done20:24
ttxthingee now20:24
ttxnext dhellmann20:24
thingeeflaper87 as I mentioned in the review, I found your position vague of it not being enough to fix discoverability. Can you please elaborate why it's not enough.20:25
* fungi has a response for stevemar_droid's question when the floor is available20:25
ttxflaper87: feel free to interject20:25
flaper87thingee: sure, so, I believe that doesn't answer the question of whether we believe drivers are important or not20:25
flaper87discoverability is a critical thing but it doesn't solve the issue of including drivers20:25
thingeewhy? it's making them visible. Highlighting them in a way of being compatible.20:26
flaper87Based on stevemar_droid's summary, there's a feeling that drivers should be included in openstack20:26
*** efried has joined #openstack-meeting20:26
flaper87I personally feel they should be part of the openstack community, officially20:26
thingeeagain I view your position purely from a development perspective. These developers are motivated because of a paycheck from a company that is happy they have that compatibility stamp20:26
ttxdhellmann: your turn20:26
dhellmannI’m disappointed that the discussion about this issue detoured from the concern about community membership and devolved into concerns about companies somehow taking advantage of the community and orthogonal issues like discoverability that could be solved independently.20:27
ttxnext dims20:27
flaper87thingee: I prefer not to think about "these developers" that way, fwiw. They are still contributing20:27
dhellmannI’m especially disappointed that we’re keeping a rule that enables project teams to exclude contributors from participating fully in the community by stripping them of ATC status.20:27
dhellmannI don’t like the image that projects of our community.20:27
ttxerr next fungi then dims20:27
dhellmannBut I want to thank the project teams that recognize the importance of drivers and have constructive relationships with their driver authors for setting a good example.20:27
* flaper87 agrees with dhellmann20:27
ttxfungi: ?20:28
ttxthen dims20:28
fungijust wanted to respond to stevemar_droid's concern about identifying supported drivers: that should be up to individual project teams. just as definitions of what a "deiver" is differ from project to project, so should standards for support20:28
fungiwe (openstack as a whole) just need to make sure we provide a place where they can be registered and maintained with support information in a consistent and discoverable manner20:29
stevemar_droidfungi something like whether or not we require CI should be consistent though, I think?20:30
*** jmckind has quit IRC20:30
fungiit hasn't been in the past20:30
*** annegentle has joined #openstack-meeting20:30
mtreinishfungi: well it's a per project thing now20:30
mtreinishsome projects require it, others don't20:30
*** ansmith has quit IRC20:31
ttxdims: your turn, then ttx20:31
fungineutron and cinder and ironic and manila have had distinctly differing opinions on what is needed for driver support20:31
dimswho is going to gate-keep the discoverability aspects? (which drivers pass a minimum bar for being included in docs etc, when to nuke things when things go south)? is that the foundation staff? i second dhellmann 's sentiment as well20:31
thingeestevemar https://etherpad.openstack.org/p/driverlog-validation20:31
dims3/ is obviously an easy choice, but prefer 1/ and 3/20:31
thingeedims currently it's the docs team rule. that needs to be addressed as I've repeated numerously20:32
thingeethe market place is driven by a community repo that has a yaml file today.20:32
dimsthingee : understood20:32
dimsback to you ttx20:33
*** ociuhandu has joined #openstack-meeting20:33
ttxSo the reason why I proposed #3 is that we passed 7-6 votes in the past and that never stood the test of time. If we can't get a stronger majority to support one option, it's probably a bad idea to choose at that precise moment20:33
*** salv-orlando has joined #openstack-meeting20:33
*** bobmel has joined #openstack-meeting20:33
ttxand I don't want us to discuss this question every week for the next two months20:33
ttxbut not answering is not that much better, I admit20:34
stevemar_droidDeciding to not make a decision counts as making a decision, right? :)20:34
*** jmckind has joined #openstack-meeting20:34
ttxWhat do you propose to make progress ? Another indicative vote with the 3 options in ?20:34
flaper87If we go with 3, I'd like there to be a commitment to review this once the discoverability issue is fixed20:35
ttx(as time passes I don't see the lines changing, I actually see the lines strengthening)20:35
*** ansmith has joined #openstack-meeting20:35
ttx(And I still sit firmly on the fence)20:35
dhellmannI would like to hear a proposal from the folks who object to driver teams that solves the community membership issue.20:36
* dims notes that /3 does not really need a vote from us. it can be implemented right away20:36
ttxflaper87: oh, definitely. That is what #3 is about20:36
fungithe resolution option with no special driver team provisions is basically equivalent to not making a decision, as it's the current status quo20:36
thingeedims it does need a vote. it means we table this conversation and wait for results20:36
fungi(if you develop drivers in a level and open fashion, you can apply as a normal project team)20:36
dtroyerttx: can we break down other bits that might be individually solvable like the discoverability, such as handling ATC status?20:36
flaper87so, do we have volunteers to work on the discoverability issue ?20:37
thingeeflaper87 me20:37
stevemar_droid++ dtroyer20:37
*** ociuhandu has quit IRC20:37
ttxdhellmann: I guess the POV of that group is taht there is no community membership issue to be solved ?20:37
dimsthingee : talking about what's visible to folks outside of TC20:37
flaper87thingee: so, are you against #1 entirely or just against #1 before the discoverability issue is fixed ?20:37
ttxdtroyer: by default ATC status would be handled through extra-atc mechanism20:37
fungiatc status is generally solvable already if project teams want to list driver devs as "extra atcs" in governance. though it merits repeating that being an atc just means you get to vote in elections. it's not "free passes to conferences"20:38
*** bobmel has quit IRC20:38
*** bkopilov has quit IRC20:38
dhellmannttx: I don't understand that. These folks are part of the electorate today. When the status expires because their repo is no longer "official" they may not be. Am I really the only one who considers that an issue?20:38
flaper87dhellmann: no, I do20:38
dhellmannfungi : I have serious doubts that teams that already can't work with driver authors are going to go that route.20:38
flaper87hence my strong preference for #1 and addressing this issue right away20:38
fungidhellmann: well, that is in part oslved by the deletions list in governance. if they continue not contributing to official projects for a year they cease being atcs20:38
dtroyerdhellmann: no.  but driver teams as first-class status doesn't make sense to me at all and is not the right solution20:38
jrollit's odd to me, to think that a project team would spend the time to mark a driver as supported, and to give those folks extra ATCs, but not allow those drivers in tree20:39
thingeedtroyer +120:39
jrollthe time spent to vet those drivers as supported is most of the effort to keep them in tree20:39
thingeejroll so to clear something up, some won't today. That's a whole other issue though20:39
*** jpr has joined #openstack-meeting20:39
mtreinishjroll: yeah, that's what I was thinking. Although there is the longer term maint. commitment20:39
dhellmannfungi : yes, that's right. We're telling them their contributions don't count unless they work on "common" aspects of the parent project. I don't think that's a reasonable position for us to take, as a community. We expect too many contributors to spend too much time on things. I don't think it's realistic.20:40
jrollright, so I'm not sure that those things will help20:40
*** salv-orlando has quit IRC20:40
johnsomOur issue with drivers in tree is we don't have the licenses/equipment to fully validate and maintain them.20:40
thingeejroll I think for some projects it's because no one wants to step up to begin with to setup the validation to say what is compatible20:40
thingeejroll it's my belief once we help projects with a system that this will continue to be a solution to be taken over20:40
*** edmondsw has left #openstack-meeting20:41
ttxdhellmann: if you take the position of who has control over the driver development, it makes some sense though. Would those driver teams really defer to the TC ? Do we want them to ?20:41
thingeethis comes from my perspective of spending time on this issue since the summit in tokyo20:41
*** mickeys has quit IRC20:41
jrollthingee: I guess my point is: for ironic, I'm not willing to call something supported unless they have CI running. which means they can be in tree. so this changes nothing for ironic drivers.20:41
dhellmannttx: I don't care about their motivation. I care about giving them a choice. They have no choice today.20:41
sdaguestevemar_droid: did we get a sense from the survey about how many folks that were only working on drivers were concerned about ATC status?20:41
jrolls/point/perspective/ maybe20:41
ttxhmm, too many parallel discussions, we'll return back to voicing20:41
*** lpetrut has quit IRC20:41
flaper87dhellmann: ++20:41
* jroll shuts up20:41
*** kebray has quit IRC20:42
flaper87dhellmann: ttx fwiw, I also care about us having a clear stand on this20:42
ttxdhellmann: it is a good point20:42
jgriffithsdague +120:42
dimssdague : i asked that question before. but then i think that we should do the right thing ...20:42
stevemar_droidsdagues not really20:42
jrollstevemar_droid: sdague: my take on the survey was that very few driver maintainers chimed in. it was mostly (ex-)ptls20:42
thingeejroll no it's fine to discuss this. so I think the next step is highlighting these vendors in the market place. I'm not even sure if you recommend to driver maintainers to take advantage of docs.o.o20:42
fungistevemar_droid: sdague: and while i consider being able to vote in elections very important, any idea if the people who expressed an interest in atc merely saw it as a way to get other unrelated perks (like conference registration discounts, which have already gone away)?20:43
*** galstrom is now known as galstrom_zzz20:43
ttxok, one question at a time, first that one from fungi20:43
jrollthingee: I do, for the drivers in tree. the ones out of tree can't use docs.o.o, no matter what they do, which makes me sad.20:43
*** bobmel has joined #openstack-meeting20:43
jrollsorry ttx20:43
thingeejroll right so option 3 is to fix those out-of-tree drivers to be included in docs20:44
ttxnext I have one for dhellmann20:44
stevemar_droidfungi, I suspect that was the initial reasoning for it. We already have low turn out rate for some elections I believe?20:44
fungimy question was mostly rhetorical. i doubt we have statistics to support any answer20:44
*** lpetrut has joined #openstack-meeting20:44
fungibut thanks stevemar_droid20:44
* dhellmann awaits the question from ttx20:45
stevemar_droidfungi, sorry20:45
*** trandles has joined #openstack-meeting20:45
ttxdhellmann: my question would be -- what do you propose we do now ? Try to pass the driver teams proposal using a weak majority ?20:45
ttxI proposed #3 because it's been a few weeks now and the split doesn't fix itself, only gets worse20:46
sdagueo/ (for when voicing comes around)20:46
*** goldenfri has joined #openstack-meeting20:46
*** gordc has left #openstack-meeting20:46
ttxI'm happy to defer to any strong majority on this topic, but we don't have one20:46
ttxand I don't see the lines moving. So...  what now?20:47
dhellmannttx: I would like to see a real proposal that addresses the membership issue from someone who opposes it. Because if there isn't another way to do that, then I want people to reconsider the motivation for making the rule change and reconsider their positions in light of that, which seems to not have been on anyone's mind during this discussion.20:47
ttxto be clear, the membership issue being, people currently voting that won't be able to vote in the near future20:47
ttx(due to a decision outside of their reach about team membership)20:48
*** egallen has joined #openstack-meeting20:48
*** ociuhandu has joined #openstack-meeting20:48
*** egallen has quit IRC20:48
*** raildo has quit IRC20:48
dtroyerwhich IIUC we alrady have a mechanism, if non-ideal, to handle that20:48
*** bobmel has quit IRC20:48
dhellmannI have no expectation of the neutron team exercising that option, so I don't consider it a serious solution.20:48
jrolldhellmann: +120:48
ttxNote: doesn't have to be the neutron team20:48
jroll(the ironic team likely wouldn't either)20:48
fungia related example is the fuel team retiring repos which had contributors that weren't contributing to other repos (even other parts of fuel)20:49
ttxcan be the TC itself20:49
dtroyeris that the only option for networking-* comtributors to get extra-ATC status?20:49
sdaguebut the voting question doesn't seem to be in the top #3 list of concerns by existing driver teams20:49
dtroyerttx: that's what I though20:49
*** salv-orlando has joined #openstack-meeting20:49
sdagueThe docs thing keeps coming up, it would be interesting to fix that as a concrete issue20:49
ttxyes, nobody ever said 'I want to be able to continue to vote'20:49
jrollhow would the TC decide which drivers should get extra-atc? all? ones that 'work'?20:49
dhellmannsdague : I honestly didn't ask them. I think our governance is broken right now, because a team can kick out members of the community who have been active contributors.20:49
flaper87mtreinish: sdague was checking the patch and noticed your votes are missing. Is that because you're on the fence or just wanted to have this discussion first ? (I know ttx is on the fence)20:50
ttxdhellmann: and we can recover them if we want20:50
fungidhellmann: to take jroll's point, ironic may remove drivers from the orinic project (for legitimate reasons) which will strip their ability to vote in ironic ptl or tc elections (assuming they don't contribute to any other repos). should we be trying to "solve" that?20:50
* flaper87 was not around last week and can't remember the voting from the logs20:50
dtroyerjroll: we currently have expectations of other projects as official, I think we would have similar there…ie, quality (CI) and so on20:50
thingeejroll as fungi said earlier, whatever the team sets as the validation. as I've pointed to this etherpad earlier there's a clear trend https://etherpad.openstack.org/p/driverlog-validation20:50
mtreinishflaper87: which patch?20:50
mtreinishthere were 220:50
dhellmannfungi : ironic has a set of policies for driver authors to follow to stay in. The authors get to choose. Neutron has not provided a similar mechanism.20:50
flaper87mtreinish: https://review.openstack.org/#/c/403829/ (sorry)20:51
jrollhonestly, I'd like to throw out steve's survey. there were four emails in that thread, from two people that are driver maintainers. the rest were (ex-)ptl/tc members or cinder cores20:51
jrolldtroyer: sounds like a driver team :)20:51
smcginnisjroll: I was hoping for more non-core responses there.20:51
jrollsmcginnis: me too :(20:51
sdagueflaper87: yeh, I zeroed out my vote yesterday, because this doesn't feel like concensus20:51
mtreinishflaper87: oh I was -1 on that in the irc vote20:51
sdagueand fix the docs situation does feel like a common first step which can be done20:52
*** ociuhandu has quit IRC20:52
fungismcginnis: lack of responses from driver authors on a thread to the mailing list where official openstack development is coordinated strikes me as a sort of result20:52
jrollthingee: and if we expect project teams won't validate out of tree drivers, as doug and I mentioned, then nobody will get extra-atc, is my point20:52
stevemar_droidjroll, that sounds fine to me. I wish there were more people replying.20:52
jrollfungi: this was a private thread fwiw20:52
thingeedhellmann agreed sort of. I see armax attempting to set validation points for plugins https://review.openstack.org/#/c/391594/120:52
ttxdhellmann: so the answer to your question seems to be: "it's not that much of a problem, but the TC can use teh extra-atc mechanism to propose and add ATC status to drivers that fall in the cracks"20:53
AJaegersdague: regarding docs: If somebody writes up a rule on what that means, I'm fine (note I'm a docs member but don't speak for the team).20:53
fungijroll: yeah, more projecting to the followup thread to the -dev ml about the private thread20:53
ttxI think I had sdague in the queue with a question20:53
jrollfungi: nod20:53
thingeedhellmann in terms for the system to be policed, I don't see neutron taking that up until A system is in place20:53
sdaguettx: well, I just jumped out there with it20:53
ttxTired, long day20:53
sdaguebasically, it seems like the discoverability and docs question as the primary concerns20:53
*** annegentle has quit IRC20:53
*** Lizhong has joined #openstack-meeting20:53
sdaguefixing them moves the ball forward, lets the dust settle, and we can then ask the next question about what is needed20:54
thingeejroll if I work on a random repo outside of openstack, should I get extra-atc status?20:54
*** annegentle has joined #openstack-meeting20:54
*** adiantum has joined #openstack-meeting20:54
thingeeif I read what you typed correctly20:54
ttxthingee: if an extra-atc change is proposed, the TC will evaluate it20:54
AJaegerthingee: and the other question: Should that random repo publish to docs.o.o?20:54
ttx(if the repo is too random, probably will say no)20:54
*** dfflanders has joined #openstack-meeting20:54
dhellmannttx: do we have an extra-atcs list that is not attached to a project team?20:55
ttxAJaeger: if the TC says it can, probably yes20:55
jrollthingee: I'm not talking about random repos, I'm talking about the out of tree drivers that might apply for official status like we're talking about here20:55
dimswe should be welcoming people with open arms given where we are on the maturity curve ...20:55
ttxWe have TC repos, I don't see why we couldn't have TC's extra-atcs20:55
thingeeAJaeger for cases like neutron, if there is a system in place that validates that a driver out of tree is compatible and working by whatever means in tempest, yes they should have a right to be docs.o.o20:55
dhellmannttx: ok20:55
flaper87ttx: at that point, wouldn't it be better for the repo to be just part of openstack?20:55
*** oneswig has joined #openstack-meeting20:55
thingeejroll see my last message to AJaeger20:55
stevemar_droidjroll, dhellmann, if maintainers don't bother to show up to meetings or reply to ml or surveys, then what are the odds they are voting?20:56
flaper87time check, 10 mins (or less)20:56
thingeejroll however, you made the choice to not validate out of tree drivers. which I don't understand why20:56
ttxflaper87: well that would mean compromising on what "an openstack project" is20:56
dhellmannstevemar_droid : I would still rather give them the choice.20:56
jrollthingee: if the project team is going to spend the effort to do that, they would make the driver repo part of the project team20:56
ttxflaper87: with extra-atcs we can recognize that driver work is essentail to thee success of openstack20:56
ttxwithout making it openstack proper20:56
stevemar_droiddhellmann, true20:56
thingeejroll to put it simply, I wouldn't do both out of tree and in-tree drivers. I would pick one or the other.20:57
flaper87anyway, just to recap. I really think we should do #1 since that gives drivers a choice20:57
dimsttx : how far away is extra-atcs and driver-team in that case?20:57
flaper87I can live by #3 if we set a checkpoint date to revisit #120:57
jrollthingee: you can't "not do" out of tree drivers, people can just write them. unless you block it in code which just leads to forks.20:57
ttxdims: it's different in my opinion. In one case you say that a driver team is an openstack team, even if it does not openly collaborate20:58
thingeejroll I mean to say recognize one or the other20:58
ttxon the other you say people working on drivers should have a voice in elections20:58
*** bkopilov has joined #openstack-meeting20:58
flaper87but, to be really honest, going with #3 would be a bit disappointing but it's better than #220:58
stevemar_droidDoesn't extra-acts have a stigma around it? We've only used it once in Keystone. Seems like we're using it as a convenience20:58
dimsttx : ack20:58
jrollthingee: if a project team spends the effort to validate out-of-tree drivers, they should just accept those drivers under the project20:58
jrollthingee: maybe we should s/tree/project/ in these discussions20:59
jrollas in, a project can be many repos20:59
stevemar_droidTo solve the problem of giving people ATC properly20:59
ttxOK, I propose we pause this discussion for a couple of weeks, start the discovery work, let the water calm down20:59
persiaTo support dhellmann's point: if there is a mechanism by which members of the polity can have franchise removed due to changes beyond their control, those members are unlikely to expect to seek redress of any other concern within the same goernance mechanisms that enable them to be disenfranchised.  This can affect more than just voting, and the disenfranchised folk may have a poor relation with their host project (or they would be less20:59
persialikely to lose franchise).20:59
EmilienM(no open discussion today :-/)20:59
jgriffithjroll or base with a driver repo :)20:59
thingeetake cinder for example. it recognizes only in-tree. that's what's in docs.o.o and that's what it's in the market place. Neutron it would be out of tree, but they would only recognize out of tree drivers that meet the validation they set. thus what will be in docs and market place.20:59
jrolljgriffith: that too :)20:59
ttxWe don't wait until discovery work is complete to revisit it, just a couple meetings without discussing it20:59
jbrycechiming in late, but i think we need to do #3 regardless and i want to figure out how to fix the data side of that. it’s definitely a question i hear ALL the time (usually in the form of “which products work with project y?”)20:59
ttxsee where that puts us21:00
jrollthingee: in my world, neutron would either allow those in the stadium, or we would have driver teams. the former isn't happening.21:00
ttxEmilienM: you had something ?21:00
dimsjbryce : for sure21:00
jbrycebut i think the core issue does need to get resolved because, just from a practical perspective, most of openstack is not super useful without drivers21:00
EmilienMttx: no but maybe some folks had something21:00
flaper87jbryce: #3 is basically # giving priority to the discoverability issue, though.21:00
thingeejroll I don't understand why the stadium matters. Projects have this solved without having a "stadium"21:00
flaper87nothing we can't do if we go with #121:00
ttxok, time is up21:00
jbryceand the ambiguity is something that i hear is confusing for companies who are trying to integrate with us21:01
fungifor me it mostly comes down to this question: are we in a position where we need to encourage people/companies to write drivers, or do they already have plenty of incentive to do so?21:01
ttxThanks everyone, even if little progress here21:01
fungi(noting i don't know the answer_21:01
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"21:01
openstackMeeting ended Tue Jan 10 21:01:40 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
jbryceflaper87: i just mean doing the discoverability fix of #321:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-01-10-20.01.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-01-10-20.01.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-01-10-20.01.log.html21:01
ttx(need to clear the room for next meeting)21:01
*** stevemar_droid has quit IRC21:02
oneswigready to go/21:02
*** sambetts is now known as sambetts|afk21:02
oneswigthanks ttx21:02
*** AJaeger has left #openstack-meeting21:02
*** b1airo has joined #openstack-meeting21:02
oneswig#startmeeting scientific_wg21:02
openstackMeeting started Tue Jan 10 21:02:45 2017 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: scientific_wg)"21:02
openstackThe meeting name has been set to 'scientific_wg'21:02
oneswig#chair b1airo21:02
openstackCurrent chairs: b1airo oneswig21:02
oneswigSpelled the meeting name correctly again - awesome start to 201721:03
*** ociuhandu has joined #openstack-meeting21:03
oneswigHi Lizhong21:03
oneswigHi priteau21:03
oneswigLizhong: Martial coming today?21:03
b1airooneswig, off to a flying start21:03
oneswig#link agenda for today is https://wiki.openstack.org/wiki/Scientific_working_group#IRC_Meeting_January_10th_201721:03
LizhongYes, he will21:03
Lizhonghe's in a meeting now21:04
oneswigShould we make you chair in his absence? :-)21:04
*** powerd has joined #openstack-meeting21:04
b1airohi powerd21:04
*** bobmel has joined #openstack-meeting21:04
oneswighi powerd21:04
oneswigReminds me, did you guys see this blog post from Bright21:05
*** bkopilov has quit IRC21:05
oneswig#link GPU article from Bright blog http://www.brightcomputing.com/blog/setting-up-gpu-hypervisors-on-bright-openstack21:05
Lizhong@oneswig I am quite new with the meeting format. maybe in the future. thanks :-)21:05
oneswigNo problem, lets get the ball rolling21:06
*** tonytan4ever has quit IRC21:06
powerdjust checking it now - pretty specific to cmsh though.21:06
oneswigSo there was some housekeeping to get started with first21:06
oneswigthanks powerd - be interesting to see you cast your eye over it21:06
*** tonytan4ever has joined #openstack-meeting21:06
*** ociuhandu has quit IRC21:07
oneswigThe Boston summit needs nominees for judging the talks for the HPC/Research speaker track.  If anyone is interested in volunteering, nominations are due by IIRC Jan 18th21:07
b1airooneswig, haven't seen it, but i'm scratching my head at the need to hack code21:07
*** laurelm has quit IRC21:08
*** htruta has quit IRC21:08
oneswig#link track chair nominations https://openstackfoundation.formstack.com/forms/openstack_summit_boston2017_track_chair_nominations21:08
*** htruta` has joined #openstack-meeting21:08
*** eglute has quit IRC21:08
*** laurelm_ has joined #openstack-meeting21:08
*** eglute has joined #openstack-meeting21:08
*** laurelm_ is now known as laurelm21:08
*** dmorita has joined #openstack-meeting21:08
*** haleyb has quit IRC21:09
*** HenryG has quit IRC21:09
oneswigtbh I hadn't read it in any depth as I'm busy enough with the stuff in front of me...21:09
*** haleyb has joined #openstack-meeting21:09
oneswig(wrt gpus that is)21:09
*** bobmel has quit IRC21:09
b1airowhat are you working on in that department?21:10
oneswigme - nothing on gpus right now21:10
oneswigmostly on deployment, monitoring and nvm-over-fabric currently21:10
priteauoneswig: thanks for the link, I didn't know this process21:10
*** bkopilov has joined #openstack-meeting21:10
b1airoah cool, so you took the bait on that one ;-)21:10
b1airopriteau, actually when i put my nomination in i suggested you :-)21:11
*** mgoddard has joined #openstack-meeting21:11
priteauMaybe I can nominate you to cancel out? ;-)21:11
*** HenryG has joined #openstack-meeting21:12
oneswigmutual assured destruction!?21:12
oneswig(by committee)21:12
b1airowhat could go wrong!21:12
b1airoso regarding Boston...21:13
b1airoit's been a while since I chatted to dfflanders21:13
oneswigyou were right, the cloud declaration thing is the following week - my mistake21:13
b1airobut last time we spoke he was suggesting the scientific-wg would be called upon to suggest several sessions21:13
oneswigdo you think we can manage a session per activity area, if people come forward for it?  Or something more general?21:14
b1airogiven how things went in Barcelona i think we could propose 3 working group sessions: a meeting, a BoF, lightning talks21:14
*** adiantum1 has joined #openstack-meeting21:14
b1airoyeah that's probably an option21:15
*** adiantum has quit IRC21:15
oneswigwhat is the structure of a Bof if not lightning talks - is any structure needed other than breaking the ice for discussion?21:15
b1airobut the foundation staff are keen on us also proposing cross-over sessions with TC teams21:16
*** nadya has quit IRC21:16
oneswigb1airo: what would that mean?21:16
b1airooneswig, i see the BoF as mainly open discussion and a forum to shake out new activity areas21:16
b1airoe.g. maybe we'd suggest a session on quota management for science clouds21:17
priteaub1airo: how do you structure the open discussion though? free for all is hard to manage with a big audience21:17
b1airopriteau, yes that's true but you have a moderator and a structure already brainstormed on etherpad21:18
oneswigToo bad I can't make this one - I'm a master at making a small audience (out of a big one)21:18
*** dimtruck is now known as zz_dimtruck21:18
b1airoi didn't see anyone leave the keynote when you were speaking21:18
oneswigIt was dark!21:19
*** adiantum1 has quit IRC21:19
oneswigb1airo: What happens in a cross-over session?21:19
b1airooneswig, i think the idea is to attempt to bring devs, ops, etc to a common understanding of a problem as the first goal21:20
b1airothat's half the battle21:20
oneswigIs our role then to state the problem as clearly as possible?21:21
b1airoand in some cases the process to get there might shake out solutions/workarounds that don't require any extra work, but if not then the idea would be to collect enough detail to go forward to specs and/or user stories21:21
b1airoyes, i believe so21:21
trandlesAre there any WG topics/use cases fully-formed enough to bring in another group/TC for discussion?21:22
oneswigFor example, one issue I'd like to see resolved is how to reconfigure RAID depending on whether a node was for compute or for big data (in which case it would prefer 6 non-RAID disks) - that kind of thing?21:23
*** adiantum has joined #openstack-meeting21:24
b1airotrandles, i think there are lots of things that WG members are keen on but we're probably looking for broad issues that may already be fairly well known yet have not had any dev commitment or are waiting on TC to prioritise21:24
oneswigb1airo: items from our activity areas from this cycle perhaps?  We ought to have had a few group discussions about those by now21:24
b1airothe nested quota (with delegated management) issues that Tim Bell has explained in blog form come to mind21:25
*** bobmel has joined #openstack-meeting21:25
b1airoyes, i imagine something on federation would be good - honestly for me that would be a 101 on current technical state from keystone et al21:26
oneswigWould be useful to keep that in people's minds, on the nested quotas21:26
trandlesA strength of the WG would be to present a unified use case with broad applicability to the WG members to a project or set of projects.  Tim Bell's quotas or accounting comes to mind as a good example of that.21:26
*** Leo_ has quit IRC21:26
oneswigtrandles: good point, can we cite a gang of related overlapping use case needs21:27
powerdid like to propose a talk on the gpu work being done - by the time the summit comes around i should be in a more advanced stage with performance numbers and guidance on setup optimisations21:27
trandlesMonitoring is another topic21:27
b1aironot sure about GPUs though, i think powerd and i just need to finish drafting and then propose it as an addition to the admin guide21:27
priteauWe should identify who would be the other group for each potential topic (e.g. Keystone devs for federation, Nova and/or Ironic for resource management)21:27
b1airoother than that it's about awareness, so talks etc21:27
*** eharney has quit IRC21:27
oneswigpowerd: a talk's a separate thing, if it goes into the main conference track21:27
powerds/talk/anything appropriate/g21:28
oneswigThat's better :-)21:28
b1airopriteau, yes that's probably the primary concern in the short-term so that the other parties can prioritise the proposals21:28
*** jrobinson has joined #openstack-meeting21:28
b1airoanyway, i think there is an action for me to catch up with dfflanders and report back - or twist his ear to make sure he attends next week21:29
oneswigHow can we generate a short list - have the activity leads generate one per area for next session?21:30
*** bobmel has quit IRC21:30
oneswigOr throw it open on an etherpad?21:30
oneswigbit of both?21:30
b1airo#action b1airo to chase up dfflanders re. boston forum format / proposals / expectations21:30
b1airoi'd go with open, if the leads are engaged then they'll suggest things on that area, no point restricting21:30
trandlesI prefer etherpad, easier to deal with timezones21:31
*** mickeys has joined #openstack-meeting21:31
oneswigtrandles: b1airo: sounds good to me21:31
*** rbudden has quit IRC21:31
oneswigI'll put together 4 etherpads21:31
b1airoi'll roll that into my action and can put a preface in about what we're trying to do21:31
oneswigaha - b1airo is going to put together 4 etherpads - even better :-)21:32
b1airolet's just have one oneswig - gets hard to track them all21:32
oneswigOK b1airo - agreed21:32
b1airoi already over 200 browser tabs open...21:32
b1airo*have over21:32
b1airo(and that's just on *this* laptop)21:33
oneswigMy desk is the phyiscal manifestation of that21:33
b1airoheh, that's a funny image21:33
oneswigOK, should we make an early indication of interest on rooms?  Edgar was asking21:34
b1airodid you see my reply on that thread?21:34
*** gouthamr has quit IRC21:34
*** martial has joined #openstack-meeting21:35
oneswigFrom last week?21:35
*** abalutoiu has quit IRC21:35
b1airowe just need to propose the sessions we want along with the main call, then once it closes the organisers will get back to us about time and space options21:35
martial(sorry, the meeting that would not end)21:35
*** zz_dimtruck is now known as dimtruck21:36
oneswig#chair martial21:36
openstackCurrent chairs: b1airo martial oneswig21:36
oneswigHi Martial21:36
martialHello all21:36
*** Leo_ has joined #openstack-meeting21:36
jprare there any recommended qualifications for track chair nominations (deep expertise or more a willingness to contribute?)21:36
b1airowelcome martial - believe me, i know the feeling, last friday i had a meeting that went 10am->4.30pm o_021:36
oneswigOK so we don't need to worry about earliest indications21:36
b1airojpr, willingness mainly but expertise is of course useful21:37
oneswigjpr: don't know.  Keenness to participate is a big plus21:37
jprk thx21:37
b1airoso on the session proposals...21:37
b1airothat circles back to what i was saying earlier21:38
oneswigmany people have said the committee meeting needs to be in a bigger room21:38
b1airo1) meeting, 2) lightning talks, 3) BoF and/or activity breakouts ?21:38
oneswigAnd I think the lightning talks were a good success21:38
b1airoyes, perhaps just one or two fewer this time though :-D21:38
oneswigI think something more's needed to make a separate BoF a success - perhaps have it run immediately after the lightning talks in the hope they stimulate discussion21:39
b1airoactually here's an idea: have a BoF session, but structured by activity breakouts with each of those moderated by a respective lead21:40
oneswigb1airo: that'd do it21:40
*** cebruns has quit IRC21:40
b1airothat keeps everybody across and able to participate in the different areas but moves us through them in a structured manner so we don't get stuck anywhere too long21:41
martialthat might mean a few BoF sessions then ?21:41
oneswigserially then not concurrently?21:41
b1airoyep i was think serially21:42
dfflandersblairo, sorry I was here just got pulled away21:42
* dfflanders reading up21:42
b1airoso a double-session BoF with 5 areas (4 current activity areas and time at the end for raising others)21:43
b1airothat'd be about 15 mins for each21:43
martial15 minutes seems short21:43
*** s3wong has joined #openstack-meeting21:43
b1airoand sweet! ;-)21:44
trandles15 minutes disappears in a blink if anyone goes long21:44
martialif my memory of how much we like to speak of our topic of interest is that is :)21:44
trandlesmoderator will have to be draconian ;)21:44
b1airomartial, it's not a lightning talk though - it'd be the lead for a particular activity area coordinating discussion on that area from an etherpad they've pre-prepared21:45
*** ansmith has quit IRC21:45
b1airowe could try asking for individual sessions for each area but then we're looking at a minimum of 6 - and that seems a lot21:45
oneswig... etherpads seeded with the gaps they've identified through discussions this cycle21:46
*** Lizhong has quit IRC21:46
b1airoshall we talk about the Boston Declaration a little?21:46
*** bobmel has joined #openstack-meeting21:46
martialsure, which means that we ask people to come prepared and with pre-discussion ready ... feasible21:46
*** VW has quit IRC21:46
dfflandersre expectations for forum, there is this blog post http://superuser.openstack.org/articles/openstack-forum/21:47
oneswigtime keeping - whoever said it must be strict was right.  I've been in some of those discussions21:47
*** krtaylor has quit IRC21:47
*** cebruns has joined #openstack-meeting21:47
dfflandershowever, I would suggest the forum as an open ended event is wide open for interpretation and the scientific-wg should make it work for your purposes and request the time/space needed to achieve those aims/goals21:48
b1airodfflanders, yes i saw that, but it's general rather than talking about the specifics of how it will come together21:48
*** pcaruana has quit IRC21:48
b1airolast time we spoke on this you suggested we should be thinking about cross-over sessions...?21:48
dfflandersif it suits your purposes21:48
*** pradk has quit IRC21:49
b1airook, i'll read that again and we can circle back next week after mulling it over21:49
dfflandersmost importantly scope the event you want to do which will enable your WG to achieve its aims for that cycle21:50
dfflandersthe foundation is flexible and want the community to own and craft the forum as their event.21:50
*** bobmel has quit IRC21:50
*** adiantum has quit IRC21:50
*** annegentle has quit IRC21:50
*** adiantum1 has joined #openstack-meeting21:51
b1airomakes sense21:52
*** annegentle has joined #openstack-meeting21:52
dfflandersPoster session, lightning talks, goldfish bowls, and/or any other open space event is encouraged... I particularly liked the idea of a poster session you had for Barcelona last time.21:52
*** zara_the_lemur__ has left #openstack-meeting21:52
oneswigI think our aims are generally more vague than can be solved by a discussion with PTLs, other than to detail use cases they may not envisage21:53
*** adiantum1 is now known as adiantum21:53
b1airomartial, it's your moment :-)21:53
martialb1airo how so ? :)21:53
oneswigposters martial!21:53
b1airoyour poster didn't really get a proper airing in barcelona21:54
martialwell I can bring it back :)21:54
martial by popular demand and all21:54
*** fguillot has quit IRC21:55
*** ociuhandu has joined #openstack-meeting21:55
martial(although I guess I should extend it with the new work we are involved with)21:55
oneswigWould this be an alternative format for a BoF or a separate event by itself?21:56
b1airothe PTLs are probably interested in hearing about pain points but yes, would be best to have them engaged in something bigger21:56
b1airoseparate i think...?21:56
martialseparate sounds like a better plan to me too21:57
martialand non overlapping if possible ?21:57
b1airopowerd, before we finish - did you do any P100 testing yet?21:57
oneswigThat sounds like plenty of content for the summit, along with the speaker track21:57
*** VW has joined #openstack-meeting21:58
b1airocoming up on time21:58
b1airoAOB or is everyone still in holiday mode :-)21:58
oneswigA bit of resurfacing old news - people were asking about ansible-managed bios settings - finally got to writing it up21:58
oneswig#link http://www.stackhpc.com/ansible-drac.html21:58
powerdP100 testing: not yet21:58
oneswigshare and enjoy21:58
powerdbut its in the lab now21:59
martialoneswig: interesting, thanks for sharing21:59
priteauoneswig: I saw your tweet today, I will read!21:59
oneswigHa, thanks priteau!21:59
oneswigOK, that's it for this week.22:00
trandlesoneswig: very interested...my production testbed is dell hardware and I've been looking for an ansible-based solution so timely ;)22:00
oneswigThanks all, until next time22:00
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"22:00
openstackMeeting ended Tue Jan 10 22:00:31 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-01-10-21.02.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-01-10-21.02.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-01-10-21.02.log.html22:00
b1airotill next week!22:00
priteauHave a good week!22:00
*** trandles has quit IRC22:01
*** b1airo has quit IRC22:01
*** dprince has quit IRC22:01
*** oneswig has quit IRC22:01
*** powerd has quit IRC22:01
*** cleong has quit IRC22:03
*** jpr has left #openstack-meeting22:05
*** martial has quit IRC22:06
*** unicell has quit IRC22:07
*** bobmel has joined #openstack-meeting22:07
*** fzdarsky has quit IRC22:07
*** tonytan4ever has quit IRC22:07
*** priteau has quit IRC22:08
*** jmckind has quit IRC22:09
*** bobmel has quit IRC22:11
*** bkopilov has quit IRC22:12
*** lblanchard has quit IRC22:13
*** mmalik4 has quit IRC22:13
*** nadya has joined #openstack-meeting22:16
*** GaToR has joined #openstack-meeting22:18
*** Sukhdev has joined #openstack-meeting22:19
*** GaToR has left #openstack-meeting22:20
*** goldenfri has left #openstack-meeting22:20
*** fzdarsky has joined #openstack-meeting22:20
*** nadya has quit IRC22:21
*** salv-orl_ has joined #openstack-meeting22:23
*** edtubill has quit IRC22:23
*** salv-orlando has quit IRC22:25
*** annegent_ has joined #openstack-meeting22:27
*** annegentle has quit IRC22:27
*** bobmel has joined #openstack-meeting22:28
*** bkopilov has joined #openstack-meeting22:28
*** bobh has quit IRC22:29
*** bobmel has quit IRC22:32
*** krtaylor has joined #openstack-meeting22:33
*** Dmitrii-Sh has quit IRC22:34
*** mriedem has joined #openstack-meeting22:37
*** ykatabam has joined #openstack-meeting22:38
*** Dmitrii-Sh has joined #openstack-meeting22:40
*** saju_m has joined #openstack-meeting22:40
*** fzdarsky has quit IRC22:41
*** thorst has quit IRC22:45
*** edtubill has joined #openstack-meeting22:46
*** albiteponcho has quit IRC22:47
*** gouthamr has joined #openstack-meeting22:47
*** bobmel has joined #openstack-meeting22:49
*** Dmitrii-Sh has quit IRC22:49
*** bkopilov has quit IRC22:50
*** lpetrut has quit IRC22:50
*** spotz is now known as spotz_zzz22:52
*** bobmel has quit IRC22:53
*** Sukhdev has quit IRC22:58
*** xyang1 has quit IRC23:00
*** Leo_ has quit IRC23:00
*** saju_m has quit IRC23:00
*** Swami has quit IRC23:01
*** efried has quit IRC23:01
*** Dmitrii-Sh has joined #openstack-meeting23:02
*** mriedem has quit IRC23:03
*** mriedem has joined #openstack-meeting23:04
*** jaugustine has quit IRC23:08
*** bobmel has joined #openstack-meeting23:10
*** annegent_ has quit IRC23:10
*** ociuhandu has quit IRC23:10
*** efried has joined #openstack-meeting23:11
*** mickeys has quit IRC23:13
*** bobmel has quit IRC23:14
*** rbudden has joined #openstack-meeting23:16
*** mickeys has joined #openstack-meeting23:17
*** mriedem has quit IRC23:20
*** mgoddard has quit IRC23:20
*** etoews has quit IRC23:21
*** aweeks has quit IRC23:21
*** larainema has quit IRC23:21
*** dpyzhov has quit IRC23:21
*** sparkycollier has quit IRC23:21
*** amitry has quit IRC23:21
*** xgerman has quit IRC23:22
*** carl_baldwin has quit IRC23:22
*** dpyzhov has joined #openstack-meeting23:22
*** jraim has quit IRC23:22
*** margaret has quit IRC23:22
*** briancurtin has quit IRC23:22
*** nick-ma_ has quit IRC23:23
*** skath has quit IRC23:23
*** morgan has quit IRC23:23
*** kmARC has quit IRC23:23
*** sdague has quit IRC23:23
*** etoews has joined #openstack-meeting23:24
*** amitry has joined #openstack-meeting23:24
*** larainema has joined #openstack-meeting23:25
*** carl_baldwin has joined #openstack-meeting23:25
*** kmARC has joined #openstack-meeting23:25
*** nick-ma_ has joined #openstack-meeting23:26
*** margaret has joined #openstack-meeting23:26
*** jraim has joined #openstack-meeting23:26
*** skath has joined #openstack-meeting23:26
*** adiantum has quit IRC23:29
*** bobmel has joined #openstack-meeting23:30
*** thorst has joined #openstack-meeting23:31
*** bobmel has quit IRC23:35
*** thorst has quit IRC23:35
*** dimtruck is now known as zz_dimtruck23:37
*** unicell has joined #openstack-meeting23:37
*** sparkycollier has joined #openstack-meeting23:38
*** morgan_ has joined #openstack-meeting23:38
*** lamt has quit IRC23:49
*** nadya has joined #openstack-meeting23:50
*** bobmel has joined #openstack-meeting23:51
*** rfolco has quit IRC23:53
*** raj_singh_ has quit IRC23:53
*** nadya has quit IRC23:54
*** ianychoi has joined #openstack-meeting23:56
*** bobmel has quit IRC23:58
*** efried has quit IRC23:58

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