Tuesday, 2016-06-07

*** jmckind has joined #openstack-meeting00:01
*** shaohe_feng has quit IRC00:02
*** matrohon has joined #openstack-meeting00:02
*** shaohe_feng has joined #openstack-meeting00:03
*** salv-orlando has quit IRC00:04
*** thorst has quit IRC00:04
*** mbound has quit IRC00:04
*** salv-orlando has joined #openstack-meeting00:05
*** sdake_ has quit IRC00:05
*** _sarob has quit IRC00:05
*** jamesdenton has joined #openstack-meeting00:06
*** karthikp_ has joined #openstack-meeting00:07
*** dmacpher has quit IRC00:10
*** jamesdenton has quit IRC00:11
*** shaohe_feng has quit IRC00:12
*** shaohe_feng has joined #openstack-meeting00:13
*** garthb has quit IRC00:15
*** amotoki has joined #openstack-meeting00:18
*** markvoelker has joined #openstack-meeting00:20
*** shaohe_feng has quit IRC00:23
*** karthikp_ has quit IRC00:23
*** MaxPC has quit IRC00:23
*** shaohe_feng has joined #openstack-meeting00:24
*** markvoelker has quit IRC00:25
*** leeantho_ has quit IRC00:25
*** MaxPC has joined #openstack-meeting00:25
*** sbalukoff has quit IRC00:26
*** MaxPC has quit IRC00:28
*** pvaneck has quit IRC00:30
*** ivar-lazzaro has joined #openstack-meeting00:31
*** shaohe_feng has quit IRC00:33
*** shaohe_feng has joined #openstack-meeting00:34
*** mtanino has quit IRC00:34
*** bill_az_ has joined #openstack-meeting00:35
*** ivar-lazzaro has quit IRC00:36
*** rbowen has joined #openstack-meeting00:36
*** sdake has joined #openstack-meeting00:38
*** sdake has quit IRC00:38
*** sdake has joined #openstack-meeting00:38
* krotscheck turns into a robot. LEFTPAD-TRON!00:41
*** SumitNaiksatam has left #openstack-meeting00:41
*** Sukhdev has quit IRC00:42
*** amitgandhinz has joined #openstack-meeting00:42
*** hoangcx has joined #openstack-meeting00:43
*** shaohe_feng has quit IRC00:43
*** shaohe_feng has joined #openstack-meeting00:44
*** jmckind has quit IRC00:45
*** longxiongqiu has joined #openstack-meeting00:45
*** amitgandhinz has quit IRC00:47
*** dmacpher has joined #openstack-meeting00:52
*** shaohe_feng has quit IRC00:53
*** salv-orlando has quit IRC00:53
*** rbowen has quit IRC00:54
*** salv-orlando has joined #openstack-meeting00:54
*** shaohe_feng has joined #openstack-meeting00:54
*** dneary has quit IRC00:55
*** thorst has joined #openstack-meeting00:56
*** thorst has quit IRC00:58
*** penick has joined #openstack-meeting00:58
*** thorst has joined #openstack-meeting00:58
*** sacharya has joined #openstack-meeting00:59
*** Daisy has joined #openstack-meeting01:00
*** banix has quit IRC01:02
*** zhurong has joined #openstack-meeting01:03
*** Sukhdev has joined #openstack-meeting01:03
*** Sukhdev has quit IRC01:04
*** shashank_hegde has quit IRC01:04
*** shaohe_feng has quit IRC01:04
*** jaypipes has joined #openstack-meeting01:04
*** sacharya has quit IRC01:04
*** shaohe_feng has joined #openstack-meeting01:05
*** thorst has quit IRC01:07
*** harlowja has joined #openstack-meeting01:08
*** amotoki has quit IRC01:08
*** zhangshuai has joined #openstack-meeting01:10
*** anteaya has quit IRC01:10
*** singhj has quit IRC01:11
*** ricolin has joined #openstack-meeting01:11
*** shaohe_feng has quit IRC01:14
*** singhj has joined #openstack-meeting01:14
*** shaohe_feng has joined #openstack-meeting01:15
*** piet has quit IRC01:15
*** ssalagame has quit IRC01:18
*** jasondotstar has quit IRC01:18
*** zhhuabj_ has quit IRC01:21
*** bobh has joined #openstack-meeting01:23
*** shaohe_feng has quit IRC01:24
*** bobh has quit IRC01:25
*** shaohe_feng has joined #openstack-meeting01:25
*** bill_az_ has quit IRC01:25
*** jmckind has joined #openstack-meeting01:25
*** Apoorva_ has joined #openstack-meeting01:29
*** spotz_zzz is now known as spotz01:29
*** jmckind has quit IRC01:29
*** vishwanathj has joined #openstack-meeting01:31
*** manjeets has left #openstack-meeting01:31
*** Apoorva has quit IRC01:32
*** Apoorva_ has quit IRC01:33
*** zhhuabj_ has joined #openstack-meeting01:34
*** shaohe_feng has quit IRC01:34
*** amotoki has joined #openstack-meeting01:35
*** shaohe_feng has joined #openstack-meeting01:35
*** cwolferh has quit IRC01:36
*** fitoduarte has quit IRC01:37
*** fitoduarte has joined #openstack-meeting01:38
*** cwolferh has joined #openstack-meeting01:39
*** pzchen has joined #openstack-meeting01:40
*** r-mibu has quit IRC01:42
*** SumitNaiksatam has joined #openstack-meeting01:42
*** amitgandhinz has joined #openstack-meeting01:43
*** singhj has quit IRC01:44
*** shaohe_feng has quit IRC01:45
*** zz_dimtruck is now known as dimtruck01:45
*** shaohe_feng has joined #openstack-meeting01:45
*** mickeys has quit IRC01:46
*** amitgandhinz has quit IRC01:47
*** mickeys has joined #openstack-meeting01:49
*** sdake has quit IRC01:50
*** yamahata has quit IRC01:51
*** iyamahat has quit IRC01:52
*** adrianofr has quit IRC01:52
*** bill_az has joined #openstack-meeting01:52
*** mickeys has quit IRC01:54
*** fnaval has quit IRC01:55
*** shaohe_feng has quit IRC01:55
*** s3wong has quit IRC01:55
*** bobh has joined #openstack-meeting01:55
*** rockyg has joined #openstack-meeting01:55
*** shaohe_feng has joined #openstack-meeting01:55
*** cwolferh has quit IRC01:56
*** r-mibu has joined #openstack-meeting01:57
*** banix has joined #openstack-meeting01:59
*** pzchen has quit IRC01:59
*** sacharya has joined #openstack-meeting01:59
*** bobh has quit IRC01:59
*** amotoki has quit IRC02:00
*** banix has quit IRC02:03
*** thorst has joined #openstack-meeting02:05
*** shaohe_feng has quit IRC02:05
*** banix has joined #openstack-meeting02:05
*** shaohe_feng has joined #openstack-meeting02:06
*** vishnoianil has quit IRC02:06
*** fnaval has joined #openstack-meeting02:07
*** jckasper has joined #openstack-meeting02:08
*** lblanchard has quit IRC02:08
*** penick has quit IRC02:10
*** sdake has joined #openstack-meeting02:11
*** liamji has joined #openstack-meeting02:11
*** thorst has quit IRC02:12
*** amotoki has joined #openstack-meeting02:12
*** jckasper has quit IRC02:13
*** cwolferh has joined #openstack-meeting02:15
*** shaohe_feng has quit IRC02:15
*** shaohe_feng has joined #openstack-meeting02:16
*** sdake_ has joined #openstack-meeting02:18
*** sdake has quit IRC02:20
*** markvoelker has joined #openstack-meeting02:21
*** bill_az has quit IRC02:23
*** markvoelker has quit IRC02:26
*** shaohe_feng has quit IRC02:26
*** shaohe_feng has joined #openstack-meeting02:26
*** bill_az has joined #openstack-meeting02:27
*** tellesnobrega is now known as tellesnobrega_af02:27
*** mickeys has joined #openstack-meeting02:28
*** rockyg has quit IRC02:29
*** mickeys has quit IRC02:33
*** banix has quit IRC02:34
*** shaohe_feng has quit IRC02:36
*** shaohe_feng has joined #openstack-meeting02:36
*** Wenzhi has joined #openstack-meeting02:40
*** sudipto has joined #openstack-meeting02:42
*** amitgandhinz has joined #openstack-meeting02:44
*** Namrata has joined #openstack-meeting02:45
*** zhhuabj_ has quit IRC02:46
*** jckasper has joined #openstack-meeting02:46
*** shaohe_feng has quit IRC02:46
*** mbound has joined #openstack-meeting02:47
*** shaohe_feng has joined #openstack-meeting02:47
*** amitgandhinz has quit IRC02:48
*** epico has joined #openstack-meeting02:49
*** yuanying_ has joined #openstack-meeting02:51
*** yuanying has quit IRC02:51
*** mbound has quit IRC02:51
*** matrohon has quit IRC02:51
*** sbalukoff has joined #openstack-meeting02:51
*** yamamoto_ has quit IRC02:51
*** yanyanhu has joined #openstack-meeting02:52
*** mkrai has joined #openstack-meeting02:53
*** shaohe_feng has quit IRC02:56
*** hongbin has joined #openstack-meeting02:57
*** shaohe_feng has joined #openstack-meeting02:57
*** Wang_Jian_ has joined #openstack-meeting02:58
*** bill_az has quit IRC02:58
*** Wang_Jian_ is now known as Wang__Jian02:58
*** Vivek__ has joined #openstack-meeting02:58
*** fnaval_ has joined #openstack-meeting02:58
*** haiwei_ has joined #openstack-meeting02:59
*** fnaval has quit IRC03:00
hongbin#startmeeting higgins03:00
openstackMeeting started Tue Jun  7 03:00:11 2016 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: higgins)"03:00
openstackThe meeting name has been set to 'higgins'03:00
hongbin#link https://wiki.openstack.org/wiki/Higgins#Agenda_for_2016-06-07_0300_UTC Today's agenda03:00
*** dmorita has quit IRC03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: higgins)"03:00
yuanying_OTSUKA, Yuanying03:00
sudiptoo/03:00
mkraiMadhuri Kumari03:00
WenzhiWenzhi Yu03:00
Namratao/03:00
*** adisky has joined #openstack-meeting03:00
yanyanhuhello03:00
Vivek__o/03:00
sbalukoffHello!03:00
Wang__Jiano/03:00
haiwei_hi03:01
shu-mutou(^o^)/03:01
*** Qiming has joined #openstack-meeting03:01
adiskyhii03:01
Qimingo/03:01
eliqiaoo/03:01
hongbinThanks for joining the meeting yuanying_ sudipto mkrai Wenzhi Namrata yanyanhu Vivek__ sbalukoff Wang__Jian haiwei_ shu-mutou adisky Qiming eliqiao03:01
*** sheel has joined #openstack-meeting03:01
hongbin#topic Announcements03:01
*** openstack changes topic to "Announcements (Meeting topic: higgins)"03:01
flwango/03:02
hongbinI have no annoucement03:02
hongbinhey flwang03:02
*** dmorita has joined #openstack-meeting03:02
flwanghongbin: hi03:02
hongbinAnyone has annoucement?03:02
flwangwill we talk about the new name?03:02
hongbinyes03:02
hongbin#topic Review Action Items03:02
*** openstack changes topic to "Review Action Items (Meeting topic: higgins)"03:02
hongbin1. hongbin collect a list of advanced features (DONE)03:02
hongbin#link https://blueprints.launchpad.net/python-higgins?searchtext=%5Blong-term-idea%5D03:02
*** zhhuabj_ has joined #openstack-meeting03:03
hongbinI created a few BPs for tracking long-term ideas03:03
flwangcool\03:03
hongbinIf you have any long-term ideas, please submit a BP and mark it as [long-term-idea]03:03
hongbinWe will revisit them one-by-one03:03
hongbinAny comment about that?03:04
sudiptohongbin, great!03:04
Qimingsounds good03:04
Wenzhigood03:04
hongbin2. hongbin raise a ML to collect idea of project naming (DONE)03:04
hongbin#link http://lists.openstack.org/pipermail/openstack-dev/2016-June/096318.html03:04
hongbin#link https://lists.launchpad.net/launchpad-users/msg06826.html Request for launchpad to rename03:04
hongbinI raised a ML in openstack-dev, it seems most people like the name "Zun"03:04
yanyanhuaha03:05
hongbinHowever, another thing is03:05
yanyanhuyep03:05
flwangagain, i like Zun03:05
Qimingincluding me03:05
hongbinI contacted the launchpad "higgins" owner03:05
mkrai+1 for Zun03:05
hongbinHe said he is willing to give the name "higgins" to us03:05
Wenzhihaha...03:05
sbalukoffHmmm... Zun is pronounced a lot like Xen. Just sayin' ;)03:05
hongbinIn this case, I am still OK to rename it to "Zun" if you like03:05
mkraiThat would be great03:06
*** amrith is now known as _amrith_03:06
flwanghongbin: should we vote?03:06
hongbinsure, want to vote?03:06
yanyanhu+1 for renaming :)03:06
mkraiI think we should keep it higgins then03:06
mkraiOk vote03:06
eliqiaolots of codes are hard coded as higgins03:06
*** dmorita has quit IRC03:06
*** iyamahat has joined #openstack-meeting03:06
*** jckasper has quit IRC03:06
eliqiaowe'd better to change the name as early as long03:06
flwangeliqiao: then it's good time to fix it :)03:06
hongbin#vote Project name? higgins, zun03:07
eliqiaoyeah, I agree, the earlier the better.03:07
*** shaohe_feng has quit IRC03:07
*** jckasper has joined #openstack-meeting03:07
hongbin#startvote what is project name? Higgins, Zun03:07
openstackBegin voting on: what is project name? Valid vote options are Higgins, Zun.03:07
openstackVote using '#vote OPTION'. Only your last vote counts.03:07
*** jckasper has quit IRC03:07
Qiming#vote Zun03:07
mkrai#vote Higgins03:07
yuanying_#vote Zun03:07
*** jckasper has joined #openstack-meeting03:07
yanyanhu#vote Zun03:07
Namrata#vote Zun03:07
adisky#vote Higgins03:07
Vivek__#vote Higgins03:07
fnaval_#vote Higgins03:07
sudipto#vote Higgins03:07
Wang__Jian#vote Higgins03:07
haiwei_#vote Zun03:07
*** shaohe_feng has joined #openstack-meeting03:07
eliqiao#vote Zun03:07
shu-mutou#vote Zun03:08
flwang#vote Zun03:08
hongbinI guess everyone has voted?03:08
hongbin#endvote03:08
openstackVoted on "what is project name?" Results are03:08
openstackZun (8): eliqiao, shu-mutou, Qiming, Namrata, flwang, haiwei_, yuanying_, yanyanhu03:08
openstackHiggins (6): Vivek__, mkrai, Wang__Jian, sudipto, fnaval_, adisky03:08
sheelah sorry..I missed03:08
sheelbtw, my vote is for higgins03:08
hongbinThen, Zun still win03:09
adisky:)03:09
hongbinZun has 8 votes03:09
mkraihongbin: what's your vote?03:09
hongbinHiggins has 7 votes03:09
sheel^^03:09
hongbinmkrai: I am OK with both :)03:09
sheelto save a tie, its best option :)03:09
sudipto+1 hongbin03:09
mkraiMe too but I just wanted to avoid the renaming effort03:09
hongbinThen, let't rename it to Zun03:10
hongbin#agreed rename project name to Zun03:10
hongbin#topic Drive consensus on project scope03:10
*** openstack changes topic to "Drive consensus on project scope (Meeting topic: higgins)"03:10
flwanghongbin: and i have already got the support from Monty and ttx for the name03:10
Qimingright, if we are gonna rename it, then do it NOW03:10
flwangs/i/we03:10
hongbin#link https://etherpad.openstack.org/p/container-management-service etherpad for collaborating on project requirements03:10
*** thorst has joined #openstack-meeting03:10
hongbin#action hongbin submit a request to rename the project03:10
hongbin1. Nova integration03:11
mkraiI will do it for higginsclient03:11
hongbinmkrai: thx03:11
mkraiIs there any bp for this now?03:11
*** xinwu has quit IRC03:11
hongbinOK, then let's back to the project scope discussion03:11
hongbin#link https://blueprints.launchpad.net/python-higgins/+spec/nova-integration03:11
hongbinWe discussed the idea in the last meeting03:12
hongbinThis is a continued discussion03:12
eliqiaothe plan for nova integration is in 'Zun' side?03:12
hongbineliqiao: ??03:12
hongbineliqiao: Like a Zun virt-driver for Nova03:12
eliqiaoas for as I know, nova has reached spec freeze now.03:12
sudiptoeliqiao, yup03:13
hongbinWe don't have to get it into Nova tree03:13
eliqiaoya, so in Newton, we can not nothing in nova.03:13
hongbinWe can have the driver in our repo at the beginning03:13
eliqiaohmm. and nova team doesn't support out-of-tree virt-driver.03:13
mkraiThis can live in zun repo03:13
yanyanhueliqiao, I think it's ok to keep it in zun repo in current stage03:13
yanyanhuyea03:13
hongbineliqiao: really?03:14
hongbineliqiao: ............03:14
eliqiaoya, I will find a link03:14
flwanghongbin: yep, we can have a separate project temporarily for the driver03:14
eliqiaowe may need to hack nove code.03:14
yanyanhu...03:14
hongbinHowever, Nova should be designed to be pluggable03:14
mkraiAgree hongbin03:15
flwanghongbin: +1 and we do port it in next release03:15
flwangthat's not a big deal, IMHO03:15
hongbinYes03:15
hongbinEveryone agree to have a Zun virt-driver for Nova?03:15
hongbinAny opposing point of view?03:15
mkrai+103:15
yanyanhu+103:15
Qiming+103:16
Wenzhi+103:16
Namrata+103:16
haiwei_+103:16
shu-mutou+103:16
hongbin#agreed Nova integration is in the scope of project03:16
sheel+103:16
Vivek__+103:16
hongbinOK. Next one03:16
*** Daisy has quit IRC03:16
hongbin2. Neutron/Kuryr integration03:16
*** Daisy has joined #openstack-meeting03:17
*** thorst has quit IRC03:17
eliqiao+103:17
*** shaohe_feng has quit IRC03:17
hongbinBTW, if anyone interest to work on Nova integration, we requires a spec03:17
hongbinAnd here is the BP: https://blueprints.launchpad.net/python-higgins/+spec/nova-integration03:17
hongbinI think we need a spec to clearify the design03:18
*** shaohe_feng has joined #openstack-meeting03:18
hongbinOK. That is it for the Nova integration03:18
sheelI can help in that but wont be able to take sole ownership03:18
adiskyi will also03:18
adiskyi will give spec for nova integration along with sheel03:19
hongbinadisky: thx03:19
hongbinOK. Second item03:20
adisky:)03:20
hongbin2. Neutron/Kuryr integration03:20
sudiptosheel, adisky i can help with reviews :)03:20
sheelsudipto: great03:20
adiskythnx sudipto...03:20
sudiptohongbin, +103:20
hongbinFor neutron/kuryr integration, I think it is a must do03:21
*** zhangshuai has quit IRC03:21
hongbinAt least for neutron integration, it is a must03:21
*** zhangshuai has joined #openstack-meeting03:21
sudiptohongbin, agreed!03:21
Wenzhiagreed03:21
yanyanhuyes, definitely, otherwise, we can't call zun container service "in openstack"03:21
hongbinOK, it seems everyone agree03:22
mkraiWe need expertise with networking for this03:22
Qimingdoes kuryr have a clearly defined scope?03:22
mkraiI am interested in it but not sure what it takes to work on Kuryr03:22
Qimingis it only about networking or is it about storage too?03:22
hongbinQiming: ??03:22
hongbinQiming: Kuryr will do both03:22
hongbinNetwork and stokrage03:22
hongbinstorage03:23
Qimingokay03:23
hongbin#agreed Nuetron/Kuryr integration is in scope03:23
hongbinFor our side, we agreed to use Kuryr for networking03:24
hongbinI am not sure the storage part03:24
haiwei_so Zun will integrate with kuryr for both network and storage?03:24
*** Daisy_ has joined #openstack-meeting03:24
hongbinWe can discuss hte storage part03:24
*** jaugustine has joined #openstack-meeting03:24
hongbinFor me, I cannot tell how Kuryr is going to do the storage part03:25
hongbinThe code is not there at all03:25
yanyanhuquick question, storage here only means something about "volume"?03:25
hongbinyanyanhu: Yes, it means cinder volume for container data volume03:25
yanyanhuI see03:25
sheelyanyanhu: I think yes... It seems related to Zun and cinder integratino03:25
sheelhongbin: right?03:26
hongbinsheel: yes03:26
eliqiaohongbin: should volume part, it will be a driver of Zun?03:26
hongbineliqiao: not sure, maybe it can be a driver03:26
*** bobh has joined #openstack-meeting03:27
hongbineliqiao: however, Zun will be duplicated with Cinder if we want to implement a voume driver?03:27
eliqiaofor now, we don't have any agent(maybe Kuryr) on the Host, how can we handle any driver functions03:27
hongbinWe need to implement a agent (like nova-compute)03:27
hongbinIMO03:27
*** shaohe_feng has quit IRC03:27
eliqiaohongbin: agreed03:27
Wenzhiagreed03:27
*** Daisy has quit IRC03:28
*** shaohe_feng has joined #openstack-meeting03:28
hongbinEveryone, Kuryr for storage? or pure Cinder for volume?03:28
hongbinOr decide it later?03:28
*** Daisy_ has quit IRC03:28
adiskydecide it later03:28
*** sarob has joined #openstack-meeting03:28
sheelpure cinder for volume03:28
mkraiWe need to look at Kuryr part also03:29
yanyanhuthat depends on the maturity of Kuryr I think03:29
*** Daisy has joined #openstack-meeting03:29
mkraiso I think we should decide later03:29
hongbinyanyanhu: yes03:29
Wang__Jiandecide later,03:29
haiwei_currently kuryr storage seems too far to be used03:29
yanyanhuand IMHO, maybe cinder is a better start point03:29
sheelhaiwei_: yes and cinder seems stable03:29
Wenzhinot familiar with Kuryr, but Cinder is reliable03:29
sheelyanyanhu: +103:29
*** tochi has quit IRC03:30
hongbinThen, we start with Cinder, and decide to switch to Kuryr later if it makes sense03:30
mkrai+103:30
sheelhongbin: seems right choice03:30
Wenzhihongbin: sounds like a plan03:30
sheel+103:30
adisky+103:30
shu-mutou+103:30
*** Daisy_ has joined #openstack-meeting03:30
yanyanhu+103:30
hongbin#agreed start with Cinder integration and revisit Kuryr later03:30
Wang__Jian+103:30
hongbin4. Glance integration03:31
*** jckasper has quit IRC03:31
hongbinWe discussed this in hte previous meeting03:31
*** jckasper has joined #openstack-meeting03:31
hongbinWe can use Glance for storing container images03:31
sudiptosorry i missed the last meeting but i find the support of docker fs in glance inadequate at the moment. I will talk to flwang and see if he agrees.03:31
sudiptobut unless we are looking at just storing the docker images ...it might be alright.03:32
hongbinsudipto: Glance don't support other container images?03:33
sudiptobut i feel glance could be a meta-store of docker images, then storing the binaries again via "docker save"03:33
flwanghongbin: glance doesn't support layered images for now03:33
sudiptohongbin, well it does...but only static .gz files.03:33
hongbinbummer03:33
flwangsudipto: +103:33
*** qwebirc60668 has joined #openstack-meeting03:34
*** qwebirc60668 has quit IRC03:34
*** Daisy has quit IRC03:34
sudiptoflwang, I will chat with you about this, glare might be another option...03:34
flwangsudipto: cool03:34
sudiptohowever, the support needs to be built up.03:34
*** Daisy_ has quit IRC03:35
hongbinIf we don't use glance/glare, any other options?03:35
hongbinmaybe hosting a private docker registry?03:35
sudiptohongbin, i was thinking, if we don't have an in-band (openstack based) support for image repository - that may not help us in long term? (Considering release cycles etc) ?03:35
* sudipto might be wrong03:35
flwanghongbin: though private docker registry works, but i don't think it's a good opion03:36
hongbinsudipto: flwang ack03:36
flwangsince it's a container mgmt service based on openstack03:36
sudiptoflwang, +2!03:36
mkraiAgree flwang03:36
flwangif we don't use the services of openstack, then we don't have to keep this, right?03:36
WenzhiAgree flwang03:36
hongbinyes03:36
flwangwe can push changes in openstack/glance if we need something which don't exist for now03:37
hongbinFor glance, we can use it for docker, but the drawback is it doesn't support layer of images. right?03:37
eliqiaoflwang: +1, cool03:37
sudiptohongbin, yeah - very minimal support of the docker images too.03:37
flwangif we can figure out what we need for glance/glare, i can propose a spec and push it03:37
sudiptoflwang, +103:37
sheelflwang: awesome03:37
*** shaohe_feng has quit IRC03:37
hongbinOK. Short term solution is using Glance for docker03:38
hongbinLong term solution is to contribute to Glance/Glare to get everything we want03:38
sudiptohongbin, ++03:38
*** sdake_ has quit IRC03:38
hongbinDo I summary everything correct?03:38
*** adiantum has joined #openstack-meeting03:38
flwanghongbin: good for me03:38
Wenzhi+103:38
flwanghongbin: would you mind creating a bp for glance integration?03:38
*** yamamoto_ has joined #openstack-meeting03:39
*** shaohe_feng has joined #openstack-meeting03:39
flwangso that we can use it to track the requirements03:39
flwangfor glance/glare03:39
hongbin#action hongbin create a bp for glance integration03:39
flwangand assign it to me03:39
hongbinflwang: ack03:39
flwanghongbin: thanks03:39
*** bill_az has joined #openstack-meeting03:39
hongbinOK. Sounds we have a good discussion for image management03:39
sudiptoflwang, will tag team with you on that one!03:39
hongbincool03:40
hongbinNext item03:40
hongbin5. Keystone integration03:40
hongbinThis is a must03:40
flwangsudipto: ping me later :)03:40
hongbinI guess everyone will agree on Keystone integration?03:41
sheel+103:41
mkraiYes03:41
hongbinIf no, we aren't able to join the big tent03:41
Wenzhisure thing03:41
eliqiaoI got a question, will different tenant's containers run on same Host?03:41
hongbin#agreed Keystone integration is in scope03:41
hongbineliqiao: Good question03:41
eliqiaoas we know, containers have bad isolation.03:41
mkraiSame question eliqiao03:42
flwangeliqiao: i would like to have a param to say if i want a fully isolation03:42
flwangwhen boot the container03:42
mkraiWe need to implement similar concept as "namespaces" in k8s for isolation of containers03:42
eliqiaoflwang: then, that tenant will oppuy a whole host03:42
flwangit's a little bit complicated than the VM case03:43
flwangeliqiao: yep, and the user need to pay more ;)03:43
mkraiI don't like the idea of occupying whole host for a tenant03:43
flwangwe have billing03:43
hongbinAnother option is to use the hypervisor-based container runtime03:43
hongbinLike clear container, hyper03:44
Wenzhiagree mkrai03:44
sudiptowe should be careful while choosing the option here - given clear containers/hyper might co-exist for different tenants on the same host.03:44
*** jaugustine has quit IRC03:44
*** amitgandhinz has joined #openstack-meeting03:44
hongbinIMO, we have a config for scheduler03:45
mkraihongbin: That is one container per vm03:45
mkraisudipto: Agree03:45
hongbinWe can let operator to config a scheduling policy03:45
hongbin1. Tenent per host03:46
hongbin2. Tenants share host03:46
hongbinOperators should tune the config based on their requirements03:46
sudiptohongbin, that sounds like a good optoion03:46
sheelmultiTenant03:47
sbalukoffJust a side note, I work on the Octavia project, and our use case emphasizes small container footprint over separation (since operators ought to be able to create service containers on hosts separate from standard tenants). So thank you for not insisting containers run only within a VM.03:47
eliqiaosbalukoff: haha ..03:47
hongbinsbalukoff: ack03:48
*** julenlar has joined #openstack-meeting03:48
*** jckasper has quit IRC03:48
*** shaohe_feng has quit IRC03:48
eliqiaosbalukoff: I was thinking it running containers before..03:48
*** yamada-h has joined #openstack-meeting03:48
*** jckasper has joined #openstack-meeting03:48
hongbinAny other comment for multi-tenancy?03:48
hongbin6. TLS support03:48
eliqiaoif you want a container, create a vm and that vm is fro that tenant, if vm's full of container, creat another one.03:48
*** shaohe_feng has joined #openstack-meeting03:49
*** JRobinson__ is now known as JRobinson__afk03:49
mkraieliqiao: no that is not the case with hypercontainers03:49
hongbinmkrai: could you elaborate the TLS support?03:49
*** amitgandhinz has quit IRC03:49
mkraiYes sure03:49
sbalukoffeliqiao: We specifically want to be able to run the containers on hosts, and not within a VM.03:49
mkraiWe would need TLS support for secure communication03:50
hongbineliqiao: For hyper, containers of different tenants will co-locate03:50
eliqiaosbalukoff: okay03:50
mkraiBut now I don't see any use case as we don't have any other services running outside openstack03:50
eliqiaohongbin: yes, I see. hyper and clear conatiner has better isolation.03:50
*** tochi has joined #openstack-meeting03:50
hongbinmkrai: Personally, I couldn't find how TLS fit into Zun03:51
hongbinmkrai: as we don't need to secure anything03:51
mkraiAs of now, me too03:51
mkraiSo we can leave it for now03:52
hongbinOK, then let's skip the TLS for now03:52
hongbin#topic Implement Higgins host agent03:52
*** openstack changes topic to "Implement Higgins host agent (Meeting topic: higgins)"03:52
*** jamesdenton has joined #openstack-meeting03:52
*** jckasper has quit IRC03:52
hongbin#link https://review.openstack.org/#/c/325707/ The patch03:52
hongbin#link https://blueprints.launchpad.net/python-higgins/+spec/higgins-host-agent The BP03:52
*** julenl has quit IRC03:52
*** jamesdenton has quit IRC03:52
*** shashank_hegde has joined #openstack-meeting03:52
*** jckasper has joined #openstack-meeting03:52
mkraiIs it not good to let conductor do it?03:53
*** jckasper has quit IRC03:53
*** jckasper has joined #openstack-meeting03:53
mkraiWhat additional will host-agent do?03:53
hongbinif we need that, we need to rename zun-conductor to zun-agent (or something else)03:53
hongbinHowever, that is an option03:54
*** longxiongqiu has quit IRC03:54
mkraihongbin: ^^03:54
hongbinRight now, nova has 1) api 2) conductor 3) compute03:54
hongbinZun can has #1, #2, #303:54
hongbinor Zun has #1 and #303:54
hongbinWhich option is better?03:55
sudiptoconductor is helpful for upgrades too03:55
hongbinsudipto: yes, I agreed, since conductor is the only place to access DB03:56
mkraiIt is better to follow nova design03:56
sheelI think its ok to use conductor for local operations than seperate agent..03:56
eliqiao1 2 303:56
WenzhiIMO, for better support for scheduler in the future, we should keep #1, #2, #303:56
*** links has joined #openstack-meeting03:56
*** longxiongqiu has joined #openstack-meeting03:56
Wenzhithen we can just borrow the design from nova API->Conductor->Scheduler->Compute03:56
hongbinWenzhi: ack03:57
hongbinEveryone agree to have #1 #2 #3?03:57
hongbin(might be a scheduler in future)03:57
mkraihongbin: I would like to work on scheduler part03:57
hongbinmkrai: ack03:57
mkraiSo have assigned the bp to me03:57
Wenzhimkrai: I am willing to help03:58
hongbin#topic Open Discussion03:58
*** openstack changes topic to "Open Discussion (Meeting topic: higgins)"03:58
mkraiThanks Wenzhi03:58
*** shaohe_feng has quit IRC03:58
sheelwe have only 2 more minutes..03:58
sheeldo we have any architecture diagram with us for now?03:59
*** zhangshuai_ has joined #openstack-meeting03:59
hongbingood question03:59
mkraiNot yet03:59
hongbinNo, so far03:59
mkraiDesign is not yet finalized :)03:59
hongbinHowever, it seems we agreed to borrow Nova architecture03:59
sheelI would need this for API design or I have to create one03:59
*** sshnaidm|afk has quit IRC03:59
sheelhongbin: right, It seems we can follow Nova..03:59
*** xinwu has joined #openstack-meeting04:00
hongbinOK. Time is up04:00
mkraiThanks everyone04:00
hongbinAll, thanks for joining hte meeting04:00
hongbin#endmeeting04:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"04:00
sudiptoThanks!04:00
openstackMeeting ended Tue Jun  7 04:00:19 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:00
Namrata  thanks04:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/higgins/2016/higgins.2016-06-07-03.00.html04:00
Wenzhithx04:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/higgins/2016/higgins.2016-06-07-03.00.txt04:00
openstackLog:            http://eavesdrop.openstack.org/meetings/higgins/2016/higgins.2016-06-07-03.00.log.html04:00
sheelquite good discusion today04:00
sheelthanks everyone04:00
eliqiao+1 for following nova.04:00
*** bobh has quit IRC04:00
*** hongbin has quit IRC04:01
*** shaohe_feng has joined #openstack-meeting04:01
*** zhangshuai has quit IRC04:02
*** tellesnobrega_af is now known as tellesnobrega04:02
*** yamada-h has quit IRC04:02
*** yamada-h has joined #openstack-meeting04:04
*** bobh has joined #openstack-meeting04:04
*** yamahata has joined #openstack-meeting04:04
*** zhangshuai_ has quit IRC04:04
*** bobh has quit IRC04:05
*** zhangshuai_ has joined #openstack-meeting04:05
*** ijw has quit IRC04:06
*** haiwei_ has quit IRC04:07
*** mkrai has quit IRC04:07
*** woodster_ has quit IRC04:08
*** shaohe_feng has quit IRC04:08
*** fitoduarte has quit IRC04:09
*** shaohe_feng has joined #openstack-meeting04:11
*** pcaruana has joined #openstack-meeting04:11
*** fnaval has joined #openstack-meeting04:11
*** shashank_hegde has quit IRC04:12
*** shashank_hegde has joined #openstack-meeting04:13
*** fnaval_ has quit IRC04:15
*** thorst has joined #openstack-meeting04:15
*** grassass has joined #openstack-meeting04:17
*** dimtruck is now known as zz_dimtruck04:18
*** Daisy has joined #openstack-meeting04:18
*** yuanying_ has quit IRC04:18
*** shaohe_feng has quit IRC04:18
*** shaohe_feng has joined #openstack-meeting04:19
*** yuanying has joined #openstack-meeting04:21
*** markvoelker has joined #openstack-meeting04:22
*** thorst has quit IRC04:22
*** pcaruana has quit IRC04:24
*** salv-orl_ has joined #openstack-meeting04:25
*** zhangshuai_ has quit IRC04:26
*** markvoelker has quit IRC04:26
*** zhangshuai_ has joined #openstack-meeting04:26
*** salv-orlando has quit IRC04:27
*** JRobinson__afk is now known as JRobinson__04:29
*** shashank_hegde has quit IRC04:29
*** shaohe_feng has quit IRC04:29
*** shashank_hegde has joined #openstack-meeting04:29
*** haukebruno has joined #openstack-meeting04:30
*** shaohe_feng has joined #openstack-meeting04:30
*** _sarob has joined #openstack-meeting04:30
*** Vivek__ has quit IRC04:32
*** sarob_ has joined #openstack-meeting04:32
*** sarob has quit IRC04:33
*** ivar-lazzaro has joined #openstack-meeting04:33
*** zhangshuai_ has quit IRC04:34
*** pcaruana has joined #openstack-meeting04:34
*** zhangshuai_ has joined #openstack-meeting04:34
*** _sarob has quit IRC04:35
*** sarob has joined #openstack-meeting04:35
*** sacharya has quit IRC04:36
*** numans has joined #openstack-meeting04:37
*** ivar-lazzaro has quit IRC04:37
*** sacharya has joined #openstack-meeting04:37
*** sarob_ has quit IRC04:38
*** shaohe_feng has quit IRC04:39
*** shaohe_feng has joined #openstack-meeting04:40
*** pcaruana has quit IRC04:40
*** sacharya has quit IRC04:42
*** dmacpher has quit IRC04:43
*** aeng has quit IRC04:43
*** sudipto has quit IRC04:43
*** _sarob has joined #openstack-meeting04:45
*** amitgandhinz has joined #openstack-meeting04:45
*** ljxiash has joined #openstack-meeting04:47
*** sarob_ has joined #openstack-meeting04:48
*** Namrata has quit IRC04:48
*** sarob has quit IRC04:48
*** shaohe_feng has quit IRC04:49
*** _sarob has quit IRC04:49
*** amitgandhinz has quit IRC04:50
*** shaohe_feng has joined #openstack-meeting04:50
*** Daisy has quit IRC04:52
*** yamada-h has quit IRC04:53
*** yamada-h has joined #openstack-meeting04:54
*** edtubill has joined #openstack-meeting04:58
*** ssalagame has joined #openstack-meeting04:59
*** shaohe_feng has quit IRC04:59
*** aeng has joined #openstack-meeting05:00
*** rbartal has joined #openstack-meeting05:00
*** shaohe_feng has joined #openstack-meeting05:00
*** shashank_hegde has quit IRC05:00
*** shashank_hegde has joined #openstack-meeting05:01
*** Poornima has joined #openstack-meeting05:04
*** ljxiash has quit IRC05:04
*** ljxiash has joined #openstack-meeting05:04
*** ljxiash has quit IRC05:09
*** shaohe_feng has quit IRC05:10
*** shaohe_feng has joined #openstack-meeting05:11
*** bill_az has quit IRC05:12
*** Daisy has joined #openstack-meeting05:13
*** Daisy has quit IRC05:14
*** Daisy has joined #openstack-meeting05:15
*** manikanta_ has joined #openstack-meeting05:15
*** henrynash_ has joined #openstack-meeting05:16
*** yamada-h has quit IRC05:17
*** ljxiash has joined #openstack-meeting05:17
*** lpetrut has joined #openstack-meeting05:18
*** dmacpher has joined #openstack-meeting05:19
*** shaohe_feng has quit IRC05:20
*** Sukhdev has joined #openstack-meeting05:21
*** shaohe_feng has joined #openstack-meeting05:22
*** thorst has joined #openstack-meeting05:22
*** markvoelker has joined #openstack-meeting05:23
*** katomo has joined #openstack-meeting05:24
*** jprovazn has joined #openstack-meeting05:25
*** sarob_ has quit IRC05:25
*** markvoelker has quit IRC05:27
*** moiz has joined #openstack-meeting05:27
*** thorst has quit IRC05:28
*** yamada-h has joined #openstack-meeting05:30
*** cdub has quit IRC05:30
*** obondarev has joined #openstack-meeting05:30
*** adahms has quit IRC05:30
*** shaohe_feng has quit IRC05:30
*** manikanta__ has joined #openstack-meeting05:30
*** manikanta_ has quit IRC05:31
*** enriquetaso has quit IRC05:31
*** hdaniel has joined #openstack-meeting05:31
*** shaohe_feng has joined #openstack-meeting05:31
*** Daisy_ has joined #openstack-meeting05:33
*** kaisers1 has left #openstack-meeting05:33
*** shashank_hegde has quit IRC05:33
*** edtubill has quit IRC05:36
*** rcernin has joined #openstack-meeting05:36
*** yamahata has quit IRC05:36
*** Daisy has quit IRC05:36
*** iyamahat has quit IRC05:37
*** yamahata has joined #openstack-meeting05:37
*** epico has quit IRC05:38
*** sacharya has joined #openstack-meeting05:38
*** sankarshan_away is now known as sankarshan05:39
*** salv-orl_ has quit IRC05:40
*** salv-orlando has joined #openstack-meeting05:40
*** shaohe_feng has quit IRC05:40
*** Sukhdev has quit IRC05:41
*** manikanta__ has quit IRC05:41
*** sudipto has joined #openstack-meeting05:41
*** shaohe_feng has joined #openstack-meeting05:41
*** Sukhdev has joined #openstack-meeting05:41
*** obondarev has quit IRC05:42
*** sacharya has quit IRC05:43
*** ssalagame has quit IRC05:45
*** moiz has quit IRC05:46
*** amitgandhinz has joined #openstack-meeting05:46
*** moizarif has quit IRC05:47
*** moiz has joined #openstack-meeting05:48
*** Daisy_ has quit IRC05:48
*** edtubill has joined #openstack-meeting05:48
*** moizarif has joined #openstack-meeting05:48
*** Daisy has joined #openstack-meeting05:48
*** amitgandhinz has quit IRC05:50
*** shaohe_feng has quit IRC05:51
*** toddjohn has joined #openstack-meeting05:51
*** shaohe_feng has joined #openstack-meeting05:52
*** Daisy has quit IRC05:53
loquacitiesinstall guide meeting in 5 mins, everyone05:55
*** toddjohn has quit IRC05:55
*** epico has joined #openstack-meeting05:57
*** vishnoianil has joined #openstack-meeting05:57
*** strigazi has joined #openstack-meeting05:57
*** roxanaghe has joined #openstack-meeting05:57
*** ljxiash_ has joined #openstack-meeting05:57
*** Poornima has quit IRC05:58
*** roxanaghe has quit IRC05:58
*** toddjohn has joined #openstack-meeting05:58
*** sankarshan is now known as sankarshan_away05:59
loquacities#startmeeting docinstallteam06:00
openstackMeeting started Tue Jun  7 06:00:44 2016 UTC and is due to finish in 60 minutes.  The chair is loquacities. Information about MeetBot at http://wiki.debian.org/MeetBot.06:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.06:00
*** openstack changes topic to " (Meeting topic: docinstallteam)"06:00
openstackThe meeting name has been set to 'docinstallteam'06:00
loquacitiesok, who's here?06:00
lbragstado/06:00
loquacitieshi lbragstad good to see you :)06:01
strigazio/ Spyros Trigazis (magnum)06:01
*** ljxiash has quit IRC06:01
loquacitieshi strigazi06:01
lbragstadloquacities thanks for the reminders :)06:01
*** shaohe_feng has quit IRC06:01
loquacitiesno trouble, sometimes i remember to send them ;)06:01
*** tfukushima has joined #openstack-meeting06:01
*** shaohe_feng has joined #openstack-meeting06:01
loquacitiesanyone else?06:02
*** toddjohn has quit IRC06:02
*** bmoss has joined #openstack-meeting06:02
katomo|_-)06:02
loquacitieshiya katomo06:02
*** toddjohn has joined #openstack-meeting06:02
katomohello06:02
bmosshi katomo06:03
loquacitiesoh hi bmoss :)06:03
katomohi bmoss06:03
bmosshowdy lo06:03
bmosshowdy loquacities06:03
loquacitiesok, let's kick off then06:04
loquacities#topic Action items06:04
*** openstack changes topic to "Action items (Meeting topic: docinstallteam)"06:04
loquacities#info loquacities to email CPLs about install guide meeting attendance06:04
loquacities#info i have done so, and look! people are here! :D06:04
katomo:)06:04
loquacities#info loquacities to create poll on naming06:05
*** aeng has quit IRC06:05
loquacities#info i have also done that, and we got 31 responses, and a clear winner :)06:05
*** gyee has quit IRC06:05
loquacities#link https://docs.google.com/spreadsheets/d/1VlNFebI_KFobs-XIT5oRhULRymwrqON8SV9pH4uiYIQ/pubchart?oid=2070399201&format=interactive06:06
loquacitiesi hope that link works06:06
loquacitieswe'll come back to that :)06:06
katomoI can see it06:06
*** yanyanhu has left #openstack-meeting06:06
loquacities#topic Infra setip06:06
*** openstack changes topic to "Infra setip (Meeting topic: docinstallteam)"06:06
loquacities#undo06:06
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x7fe23773ae90>06:06
loquacities#topic Infra setup06:06
*** openstack changes topic to "Infra setup (Meeting topic: docinstallteam)"06:06
*** dmacpher has quit IRC06:06
loquacities#link https://review.openstack.org/#/c/326039/06:07
*** toddjohn has quit IRC06:07
loquacities#info Andreas created this overnight06:07
bmossawesome!06:07
strigaziSo, we add our project here? https://review.openstack.org/#/c/326039/6/jenkins/jobs/projects.yaml06:07
katomogreat06:07
loquacitiesi'm hoping to have some instructions written up soon, but for now i'm still trying to get my head around it ;)06:07
*** larainema has quit IRC06:07
loquacitiesstrigazi: yes, that's my understanding06:07
*** iyamahat has joined #openstack-meeting06:08
*** lpetrut has quit IRC06:08
strigaziok, In out project of course06:08
loquacitiesstrigazi: i also saw your convo with andreas on irc overnight last night (my time), so thanks for all your help on getting this sorted :)06:08
strigazibut in this file06:08
*** obondarev has joined #openstack-meeting06:08
loquacitiesyeah, so my understanding so far is:06:08
*** larainema has joined #openstack-meeting06:08
loquacities* Project creates $repo/install-guide and puts something in it (based on the cookiecutter)06:08
loquacities* Docs (?) update the install-guide-jobs directive in the projects.yaml file with the name of the service06:08
*** sudipto has quit IRC06:10
loquacitiesok, any questions on that?06:10
katomoI'm okay.06:10
loquacitiescool06:10
loquacities#topic New title: OpenStack Installation Tutorial06:10
*** openstack changes topic to "New title: OpenStack Installation Tutorial (Meeting topic: docinstallteam)"06:10
loquacitiesnot much to say there, except we need to go ahead and do it06:11
*** shaohe_feng has quit IRC06:11
loquacitiesi'm also trying to work out what other content 'glue' we need to get this all published06:11
loquacities#topic reps for moving content06:12
*** openstack changes topic to "reps for moving content (Meeting topic: docinstallteam)"06:12
*** shaohe_feng has joined #openstack-meeting06:12
*** haukebruno has quit IRC06:12
loquacities#info We have reps for Orchestration (pkovar), Shared File Systems (gouthamr), Object Storage (pkovar), and Telemetry (ildikov) (Thanks!) 06:12
loquacities#info Still need a rep for Trove06:12
loquacities#action loquacities to reach out to reps shortly with instructions for moving content06:13
loquacitieslaurelm is listed as the CPL for trove, so i'll contact her this week to find out who we should be talking to for that content06:14
lbragstadloquacities are those the only projects listed for moving content? or are there others, too?06:14
ildikovo/06:14
* ildikov is sorry for being late, wifi issues06:14
loquacitiesthey're the ones that need to be moved out of the existing install guide and into their own repos06:14
loquacitiesthe other defcore projects will stay06:15
lbragstadgot it06:15
loquacitiesildikov: welcome :)06:15
katomohi, ildikov06:15
loquacitiesok, questions on that topic?06:15
ildikovdo we have a target finish date?06:16
loquacitiesildikov: well, not other than 'before newton'06:16
loquacitiesbut there's going to be a lot of polishing to be done, i imagine, so i want to get the content moved as soon as the infrastructure is ready to go06:16
ildikovloquacities: ok, cool tnx06:16
loquacitiesok, moving on06:17
loquacities#topic Work Items06:17
*** openstack changes topic to "Work Items (Meeting topic: docinstallteam)"06:17
loquacities#link https://wiki.openstack.org/wiki/Documentation/InstallGuideWorkItems06:17
loquacitiesi think we're in pretty good shape right now06:17
*** moizarif has quit IRC06:17
loquacitiesonce we get the infra up and running and some basic instructions, we can start moving projects from the existing install guide over to their own repos06:18
*** Daisy has joined #openstack-meeting06:18
loquacitieswe can also get the name changed, and then start working on any content for the new guide to glue it all together06:18
*** gongysh has joined #openstack-meeting06:18
loquacitiesany questions on work items?06:18
*** moizarif has joined #openstack-meeting06:18
*** aeng has joined #openstack-meeting06:18
strigaziI'm good06:19
loquacitiesyay!06:19
loquacities#topic open discussion06:20
*** openstack changes topic to "open discussion (Meeting topic: docinstallteam)"06:20
*** moizarif_ has joined #openstack-meeting06:20
strigaziabout debconf06:20
loquacitiesyep?06:20
strigaziHow we should write instructions? I mean, to be manual06:20
*** edtubill has quit IRC06:20
loquacitiesby 'manual' we really mean 'not using an automated tool'06:20
*** moiz has quit IRC06:21
loquacitiesso if it's opening config files and editing them, then it's manual06:21
*** ajiang has quit IRC06:21
loquacitiesdebconf is considered an automated tool, in this sense06:21
loquacitieswhich is why we split it out06:21
*** nadya has joined #openstack-meeting06:21
*** shaohe_feng has quit IRC06:21
*** ljxiash has joined #openstack-meeting06:22
katomoyeah06:22
*** shaohe_feng has joined #openstack-meeting06:22
*** iyamahat has quit IRC06:22
strigaziWe should pass some parameters to apt-get install to stop debconf of configuring anything?06:22
*** ijw has joined #openstack-meeting06:23
loquacitieswhich book are you talking about? the debconf book or the non-debconf book?06:23
*** ajiang has joined #openstack-meeting06:23
strigazinon-debconf06:23
loquacitieswell, it shouldn't have debconf at all in it06:23
strigaziI guess we should do DEBIAN_FRONTEND=noninteractive apt-get install openstack-<service> right?06:24
katomoby default, on installing packages on debian, debconf configuration screen automatically appears. right?06:25
strigaziby default it does appear06:25
katomostrigazi: I'm not sure, but I think so.06:25
*** thorst has joined #openstack-meeting06:25
*** shihanzhang has joined #openstack-meeting06:25
*** ljxiash_ has quit IRC06:26
*** haukebruno has joined #openstack-meeting06:26
loquacitiesthat sounds about right to me06:26
loquacitiesok, any other items?06:26
katomoI need to talk with debian master :)06:26
loquacitiesheh, yeah :)06:26
*** sudipto has joined #openstack-meeting06:26
katomonone from me06:26
loquacitiesgreat, thanks katomo06:27
loquacitieseveryone happy?06:27
strigaziyeap06:27
bmossyep06:27
*** toddjohn has joined #openstack-meeting06:27
lbragstadi think i'm good - unless there are specific keystone items needed from my end :)06:27
ildikovI'm sleepy, otherwise good :)06:27
loquacitieslbragstad: not yet, but very soon!06:27
lbragstadloquacities awesome06:27
loquacitiesildikov: time for coffee? ;)06:27
ildikovwill come back with items after starting moving the docs :)06:27
loquacitiesgreat!06:28
ildikovloquacities: in progress by now :)06:28
loquacitiesthanks everyone for coming, this will be much easier now we're all talking to each other :)06:28
loquacitiesildikov: \o/06:28
*** ljxiash has quit IRC06:28
loquacities#endmeeting06:28
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:28
openstackMeeting ended Tue Jun  7 06:28:27 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-06-07-06.00.html06:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-06-07-06.00.txt06:28
openstackLog:            http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-06-07-06.00.log.html06:28
katomothanks, all06:28
lbragstadthanks06:28
loquacitieso/06:28
lbragstado/06:28
*** liusheng has quit IRC06:28
strigazibye06:28
*** hdaniel has quit IRC06:28
*** strigazi has left #openstack-meeting06:29
*** katomo has quit IRC06:29
*** bmoss has left #openstack-meeting06:29
*** thorst has quit IRC06:32
*** shaohe_feng has quit IRC06:32
*** shaohe_feng has joined #openstack-meeting06:32
*** obondarev has quit IRC06:33
*** sudipto has quit IRC06:33
*** gpocentek has joined #openstack-meeting06:34
*** zhangshuai_ has quit IRC06:34
*** zhangshuai_ has joined #openstack-meeting06:34
*** gpocentek has left #openstack-meeting06:35
*** yuval has joined #openstack-meeting06:36
*** toddjohn has quit IRC06:39
*** nadya has quit IRC06:40
*** toddjohn has joined #openstack-meeting06:40
*** adiantum has quit IRC06:40
*** pbchekin has joined #openstack-meeting06:41
*** shaohe_feng has quit IRC06:42
*** shashank_hegde has joined #openstack-meeting06:42
*** reedip has joined #openstack-meeting06:43
*** shaohe_feng has joined #openstack-meeting06:43
*** pbchekin has quit IRC06:43
*** toddjohn has quit IRC06:44
*** reedip has quit IRC06:45
*** amitgandhinz has joined #openstack-meeting06:47
*** jtomasek has joined #openstack-meeting06:48
*** ljxiash has joined #openstack-meeting06:49
*** sudipto has joined #openstack-meeting06:49
*** ddeja has left #openstack-meeting06:50
*** amitgandhinz has quit IRC06:51
*** andreas_s has joined #openstack-meeting06:52
*** Daisy has quit IRC06:52
*** shaohe_feng has quit IRC06:52
*** fzdarsky|afk has joined #openstack-meeting06:53
*** Daisy has joined #openstack-meeting06:53
*** shaohe_feng has joined #openstack-meeting06:53
*** ljxiash has quit IRC06:54
*** fzdarsky|afk is now known as fzdarsky06:54
*** roxanaghe has joined #openstack-meeting06:58
*** nadya has joined #openstack-meeting06:59
*** sridharg has joined #openstack-meeting07:01
*** rubasov has joined #openstack-meeting07:02
*** shaohe_feng has quit IRC07:02
*** reedip has joined #openstack-meeting07:03
*** roxanaghe has quit IRC07:03
*** shaohe_feng has joined #openstack-meeting07:03
*** salv-orlando has quit IRC07:04
*** reedip has quit IRC07:05
*** salv-orlando has joined #openstack-meeting07:05
*** Sukhdev has quit IRC07:06
*** vishwanathj has quit IRC07:11
*** huangtianhua has quit IRC07:11
*** jichen has joined #openstack-meeting07:12
*** shaohe_feng has quit IRC07:13
*** bobmel has joined #openstack-meeting07:13
*** shaohe_feng has joined #openstack-meeting07:13
*** zeih has joined #openstack-meeting07:14
*** xinwu has quit IRC07:15
*** ljxiash has joined #openstack-meeting07:17
*** mickeys has joined #openstack-meeting07:20
*** reedip has joined #openstack-meeting07:21
*** ljxiash has quit IRC07:21
*** jschwarz has joined #openstack-meeting07:23
*** mickeys has quit IRC07:23
*** shaohe_feng has quit IRC07:23
*** matrohon has joined #openstack-meeting07:23
*** markvoelker has joined #openstack-meeting07:23
*** shaohe_feng has joined #openstack-meeting07:24
*** e0ne has joined #openstack-meeting07:24
*** reedip has quit IRC07:25
*** coolsvap is now known as coolsvap|lunch07:25
*** coolsvap|lunch is now known as coolsvap07:26
*** nadya has quit IRC07:26
*** Daisy_ has joined #openstack-meeting07:27
*** markvoelker has quit IRC07:28
*** zqfan has joined #openstack-meeting07:28
*** paul-carlton2 has joined #openstack-meeting07:29
*** thorst has joined #openstack-meeting07:30
*** hdaniel has joined #openstack-meeting07:30
*** yujunz has joined #openstack-meeting07:30
*** Daisy has quit IRC07:31
*** shaohe_feng has quit IRC07:33
*** shaohe_feng has joined #openstack-meeting07:34
*** jlanoux has joined #openstack-meeting07:34
*** thorst has quit IRC07:37
*** sarob has joined #openstack-meeting07:37
*** rossella_s has joined #openstack-meeting07:38
*** liusheng has joined #openstack-meeting07:40
*** nmagnezi has joined #openstack-meeting07:41
*** sarob has quit IRC07:42
*** ihrachys has joined #openstack-meeting07:42
*** reedip has joined #openstack-meeting07:42
*** dmorita has joined #openstack-meeting07:43
*** ijw has quit IRC07:43
*** shaohe_feng has quit IRC07:43
*** shaohe_feng has joined #openstack-meeting07:44
*** reedip has quit IRC07:45
*** dmorita has quit IRC07:47
*** amitgandhinz has joined #openstack-meeting07:48
*** e0ne has quit IRC07:48
*** rossella_s has quit IRC07:48
*** phil has joined #openstack-meeting07:48
*** phil is now known as Guest1442707:49
*** Guest14427 is now known as preisner07:50
*** amitgandhinz has quit IRC07:52
*** shaohe_feng has quit IRC07:54
*** shaohe_feng has joined #openstack-meeting07:54
*** toscalix has joined #openstack-meeting07:54
*** salv-orlando has quit IRC07:56
*** salv-orlando has joined #openstack-meeting07:56
*** roxanaghe has joined #openstack-meeting08:00
*** reedip has joined #openstack-meeting08:01
*** rossella_s has joined #openstack-meeting08:01
*** dbecker has joined #openstack-meeting08:01
*** rwsu has quit IRC08:02
*** e0ne has joined #openstack-meeting08:02
*** e0ne has quit IRC08:02
*** zhangshuai_ has left #openstack-meeting08:03
*** roxanaghe has quit IRC08:04
*** shaohe_feng has quit IRC08:04
*** reedip has quit IRC08:05
*** shaohe_feng has joined #openstack-meeting08:05
*** nkrinner has joined #openstack-meeting08:07
*** neil_ has joined #openstack-meeting08:08
*** flip214 has quit IRC08:08
*** bcafarel has joined #openstack-meeting08:09
*** flip214 has joined #openstack-meeting08:10
*** ljxiash has joined #openstack-meeting08:11
*** iceyao has joined #openstack-meeting08:14
*** shaohe_feng has quit IRC08:14
*** shaohe_feng has joined #openstack-meeting08:15
*** toddjohn has joined #openstack-meeting08:16
*** ljxiash has quit IRC08:17
*** hoangcx has quit IRC08:20
*** ygbo has joined #openstack-meeting08:20
*** toddjohn has quit IRC08:21
*** reedip has joined #openstack-meeting08:21
*** paul-carlton2 has quit IRC08:21
*** shaohe_feng has quit IRC08:25
*** reedip has quit IRC08:25
*** shaohe_feng has joined #openstack-meeting08:25
*** rbartal has quit IRC08:26
*** ljxiash has joined #openstack-meeting08:26
*** hashar has joined #openstack-meeting08:29
*** numans has quit IRC08:29
*** nisha has joined #openstack-meeting08:30
*** zul has quit IRC08:32
*** Julien-zte has joined #openstack-meeting08:32
*** shaohe_feng has quit IRC08:35
*** thorst has joined #openstack-meeting08:35
*** zhhuabj_ has quit IRC08:35
*** paul-carlton2 has joined #openstack-meeting08:35
*** shaohe_feng has joined #openstack-meeting08:36
*** Daisy_ has quit IRC08:36
*** Daisy has joined #openstack-meeting08:37
*** Wang__Jian has quit IRC08:39
*** reedip has joined #openstack-meeting08:41
*** Daisy has quit IRC08:41
*** thorst has quit IRC08:42
*** nisha has quit IRC08:42
*** reedip has quit IRC08:43
*** nisha has joined #openstack-meeting08:43
*** Julien-zte has quit IRC08:44
*** Daisy has joined #openstack-meeting08:45
*** shaohe_feng has quit IRC08:45
*** zul has joined #openstack-meeting08:45
*** pzchen has joined #openstack-meeting08:45
*** pzchen has left #openstack-meeting08:45
*** longxiongqiu has quit IRC08:46
*** shaohe_feng has joined #openstack-meeting08:46
*** longxiongqiu has joined #openstack-meeting08:46
*** hoangcx has joined #openstack-meeting08:46
*** zhhuabj_ has joined #openstack-meeting08:48
*** liusheng has quit IRC08:48
*** shashank_hegde has quit IRC08:48
*** liusheng has joined #openstack-meeting08:48
*** paul-carlton2 has quit IRC08:48
*** amitgandhinz has joined #openstack-meeting08:48
*** paul-carlton2 has joined #openstack-meeting08:49
*** acoles_ is now known as acoles08:50
*** tesseract has joined #openstack-meeting08:50
*** chenpengzi has joined #openstack-meeting08:51
*** yassine has joined #openstack-meeting08:52
*** yassine has quit IRC08:52
*** yassine has joined #openstack-meeting08:52
*** amitgandhinz has quit IRC08:53
*** shaohe_feng has quit IRC08:55
*** Daisy_ has joined #openstack-meeting08:56
*** nisha_ has joined #openstack-meeting08:56
*** shaohe_feng has joined #openstack-meeting08:58
*** Daisy has quit IRC08:58
*** reedip has joined #openstack-meeting08:59
*** yujunz has quit IRC08:59
*** nisha has quit IRC08:59
*** tfukushima has quit IRC09:02
*** nisha_ is now known as nisha09:02
*** tfukushima has joined #openstack-meeting09:02
*** electrofelix has joined #openstack-meeting09:03
*** dmorita has joined #openstack-meeting09:05
*** reedip has quit IRC09:05
*** vuntz_ has quit IRC09:05
*** gongysh has quit IRC09:05
*** shaohe_feng has quit IRC09:06
*** shaohe_feng has joined #openstack-meeting09:06
*** tfukushima has quit IRC09:07
*** Daisy_ has quit IRC09:07
*** Daisy has joined #openstack-meeting09:08
*** dmorita has quit IRC09:09
*** julenlar is now known as julenl09:09
*** Daisy has quit IRC09:11
*** vuntz has joined #openstack-meeting09:11
*** vuntz has joined #openstack-meeting09:11
*** Daisy_ has joined #openstack-meeting09:11
*** toddjohn has joined #openstack-meeting09:11
*** JRobinson__ has quit IRC09:11
*** fwdit has joined #openstack-meeting09:14
*** shaohe_feng has quit IRC09:16
*** toddjohn has quit IRC09:16
*** shaohe_feng has joined #openstack-meeting09:17
*** zhhuabj_ has quit IRC09:20
*** reedip has joined #openstack-meeting09:21
*** sambetts|afk is now known as sambetts09:23
*** markvoelker has joined #openstack-meeting09:24
*** reedip has quit IRC09:25
*** shaohe_feng has quit IRC09:26
*** shaohe_feng has joined #openstack-meeting09:27
*** Daisy_ has quit IRC09:28
*** e0ne has joined #openstack-meeting09:28
*** Daisy has joined #openstack-meeting09:28
*** markvoelker has quit IRC09:29
*** yamahata has quit IRC09:30
*** numans has joined #openstack-meeting09:31
*** obondarev has joined #openstack-meeting09:36
*** ricolin has quit IRC09:36
*** shaohe_feng has quit IRC09:36
*** shaohe_feng has joined #openstack-meeting09:37
*** zhhuabj_ has joined #openstack-meeting09:37
*** moizarif has quit IRC09:38
*** mbound has joined #openstack-meeting09:39
*** thorst has joined #openstack-meeting09:39
*** zhangshuai_ has joined #openstack-meeting09:39
*** julenlar has joined #openstack-meeting09:39
*** sacharya has joined #openstack-meeting09:40
*** nkrinner has quit IRC09:40
*** julenl has quit IRC09:42
*** Daisy has quit IRC09:42
*** reedip has joined #openstack-meeting09:42
*** Daisy has joined #openstack-meeting09:42
*** moizarif has joined #openstack-meeting09:44
*** bobmel_ has joined #openstack-meeting09:44
*** sacharya has quit IRC09:45
*** reedip has quit IRC09:45
*** moizarif_ has quit IRC09:45
*** moizarif_ has joined #openstack-meeting09:45
*** shaohe_feng has quit IRC09:47
*** bobmel has quit IRC09:47
*** Daisy has quit IRC09:47
*** thorst has quit IRC09:47
*** nkrinner has joined #openstack-meeting09:48
*** moizarif has quit IRC09:49
*** amitgandhinz has joined #openstack-meeting09:49
*** shaohe_feng has joined #openstack-meeting09:51
*** amitgandhinz has quit IRC09:54
*** vishwanathj has joined #openstack-meeting09:54
*** shu-mutou is now known as shu-mutou-AFK09:54
*** shaohe_feng has quit IRC09:57
*** permalac has joined #openstack-meeting09:57
*** vishwanathj has quit IRC09:57
*** vishwanathj has joined #openstack-meeting09:58
*** shaohe_feng has joined #openstack-meeting09:58
*** hoangcx has left #openstack-meeting10:00
*** reedip has joined #openstack-meeting10:02
*** chenpengzi has quit IRC10:04
*** vishwanathj has quit IRC10:04
*** reedip has quit IRC10:05
*** nkrinner has quit IRC10:05
*** shaohe_feng has quit IRC10:07
*** lpetrut has joined #openstack-meeting10:07
*** shaohe_feng has joined #openstack-meeting10:08
*** irenab has joined #openstack-meeting10:08
*** zhangshuai_ has quit IRC10:09
*** zhangshuai_ has joined #openstack-meeting10:10
*** zhurong has quit IRC10:10
*** zhangshuai_ has quit IRC10:11
*** zhangshuai_ has joined #openstack-meeting10:12
*** rwsu has joined #openstack-meeting10:15
*** rbowen has joined #openstack-meeting10:15
*** zhangshuai_ has quit IRC10:17
*** shaohe_feng has quit IRC10:17
*** zhangshuai_ has joined #openstack-meeting10:18
*** shaohe_feng has joined #openstack-meeting10:18
*** nisha_ has joined #openstack-meeting10:19
*** nisha has quit IRC10:20
*** rwsu has quit IRC10:20
*** rwsu has joined #openstack-meeting10:21
*** reedip has joined #openstack-meeting10:22
*** _amrith_ is now known as amrith10:24
*** sdague has joined #openstack-meeting10:24
*** paul-carlton2 has quit IRC10:25
*** salv-orl_ has joined #openstack-meeting10:25
*** reedip has quit IRC10:25
*** reedip has joined #openstack-meeting10:25
*** reedip has quit IRC10:26
*** yamamoto_ has quit IRC10:26
*** jlanoux_ has joined #openstack-meeting10:27
*** shaohe_feng has quit IRC10:28
*** salv-orlando has quit IRC10:28
*** jlanoux has quit IRC10:30
*** shaohe_feng has joined #openstack-meeting10:30
*** rwsu has quit IRC10:31
*** nadya has joined #openstack-meeting10:31
*** rwsu has joined #openstack-meeting10:31
*** nadya has quit IRC10:36
*** nkrinner has joined #openstack-meeting10:38
*** shaohe_feng has quit IRC10:38
*** sarob has joined #openstack-meeting10:38
*** zhangshuai_ has quit IRC10:38
*** shaohe_feng has joined #openstack-meeting10:39
*** zhangshuai has joined #openstack-meeting10:39
*** zhangshuai has left #openstack-meeting10:40
*** julim has joined #openstack-meeting10:40
*** yamada-h has quit IRC10:41
*** rbartal has joined #openstack-meeting10:41
*** kaisers has quit IRC10:42
*** reedip has joined #openstack-meeting10:42
*** jlanoux has joined #openstack-meeting10:42
*** sarob has quit IRC10:43
*** reedip has quit IRC10:44
*** kaisers has joined #openstack-meeting10:44
*** jlanoux_ has quit IRC10:45
*** thorst has joined #openstack-meeting10:47
*** shaohe_feng has quit IRC10:48
*** shaohe_feng has joined #openstack-meeting10:49
*** amitgandhinz has joined #openstack-meeting10:50
*** MaxPC has joined #openstack-meeting10:50
*** thorst has quit IRC10:53
*** nadya has joined #openstack-meeting10:54
*** amitgandhinz has quit IRC10:54
*** hashar has quit IRC10:56
*** rwsu has quit IRC10:56
*** hashar has joined #openstack-meeting10:56
*** weshay has joined #openstack-meeting10:57
*** shaohe_feng has quit IRC10:58
*** shaohe_feng has joined #openstack-meeting10:59
*** nadya has quit IRC10:59
*** amotoki has quit IRC11:00
*** ljxiash has quit IRC11:00
*** reedip has joined #openstack-meeting11:00
*** ljxiash has joined #openstack-meeting11:01
*** sudipto has quit IRC11:01
*** obondarev has quit IRC11:03
*** shihanzhang has quit IRC11:04
*** salv-orl_ has quit IRC11:04
*** salv-orlando has joined #openstack-meeting11:05
*** reedip has quit IRC11:05
*** ljxiash has quit IRC11:05
*** reedip has joined #openstack-meeting11:05
*** reedip has quit IRC11:06
*** rtheis has joined #openstack-meeting11:06
*** tellesnobrega is now known as tellesnobrega_af11:08
*** shaohe_feng has quit IRC11:09
*** Guest_84757 has joined #openstack-meeting11:09
Guest_84757Allah is doing11:09
Guest_84757sun is not doing Allah is doing11:09
Guest_84757moon is not doing Allah is doing11:10
Guest_84757stars are not doing Allah is doing11:10
Guest_84757planets are not doing Allah is doing11:10
Guest_84757galaxies are not doing Allah is doing11:10
Guest_84757oceans are not doing Allah is doing11:11
Guest_84757mountains are not doing Allah is doing11:11
Guest_84757trees are not doing Allah is doing11:11
*** shaohe_feng has joined #openstack-meeting11:11
Guest_84757mom is not doing Allah is doing11:11
Guest_84757dad is not doing Allah is doing11:12
Guest_84757boss is not doing Allah is doing11:12
*** epico has quit IRC11:12
Guest_84757job is not doing Allah is doing11:12
*** nisha_ is now known as nisha11:12
Guest_84757dollar is not doing Allah is doing11:12
Guest_84757degree is not doing Allah is doing11:13
*** MaxPC has quit IRC11:13
Guest_84757medicine is not doing Allah is doing11:13
Guest_84757customers are not doing Allah is doing11:13
Guest_84757you can not get a job without the permission of allah11:14
Guest_84757you can not get married without the permission of allah11:14
Guest_84757nobody can get angry at you without the permission of allah11:15
Guest_84757light is not doing Allah is doing11:15
Guest_84757fan is not doing Allah is doing11:15
Guest_84757businessess are not doing Allah is doing11:16
Guest_84757america is not doing Allah is doing11:16
Guest_84757fire can not burn without the permission of allah11:17
Guest_84757knife can not cut without the permission of allah11:17
Guest_84757rulers are not doing Allah is doing11:18
*** salv-orl_ has joined #openstack-meeting11:18
Guest_84757governments are not doing Allah is doing11:18
Guest_84757sleep is not doing Allah is doing11:19
*** henrynash_ has quit IRC11:19
*** shaohe_feng has quit IRC11:19
*** shaohe_feng has joined #openstack-meeting11:19
*** lezbar has quit IRC11:19
Guest_84757hunger is not doing Allah is doing11:20
*** lezbar has joined #openstack-meeting11:20
Guest_84757food does not take away the hunger Allah takes away the hunger11:20
*** amotoki has joined #openstack-meeting11:20
Guest_84757water does not take away the thirst Allah takes away the thirst11:21
Guest_84757seeing is not doing Allah is doing11:21
*** reedip has joined #openstack-meeting11:22
Guest_84757hearing is not doing Allah is doing11:22
Guest_84757seasons are not doing Allah is doing11:22
*** salv-orlando has quit IRC11:23
Guest_84757weather is not doing Allah is doing11:23
Guest_84757humans are not doing Allah is doing11:23
*** iceyao has quit IRC11:23
Guest_84757animals are not doing Allah is doing11:24
*** iceyao has joined #openstack-meeting11:24
Guest_84757the best amongst you are those who learn and teach quran11:24
*** markvoelker has joined #openstack-meeting11:25
*** reedip has quit IRC11:25
Guest_84757one letter read from book of Allah amounts to one good deed and Allah multiplies one good deed ten times11:25
Guest_84757hearts get rusted as does iron with water to remove rust from heart recitation of Quran and rememberance of death11:27
Guest_84757heart is likened to a mirror11:27
Guest_84757when a person commits one sin a black dot sustains the heart11:28
*** toddjohn has joined #openstack-meeting11:29
*** shaohe_feng has quit IRC11:29
*** markvoelker has quit IRC11:29
*** shaohe_feng has joined #openstack-meeting11:30
Guest_84757to accept Islam say that i bear witness that there is no deity worthy of worship except Allah and Muhammad peace be upon him is his slave and messenger11:30
*** Zalman{-} has joined #openstack-meeting11:30
Guest_84757read book www.fazaileamaal.com11:30
*** nisha_ has joined #openstack-meeting11:30
*** nisha has quit IRC11:31
Guest_84757read book www.muntakhabahadith.com11:31
*** nadya has joined #openstack-meeting11:31
Guest_84757need spiritual teacher visit www.alhaadi.org.za11:32
Guest_84757allah created the sky without any pillars11:32
Guest_84757allah makes the sun rise from the east and Allah sets the sun in the west11:33
*** toddjohn has quit IRC11:34
Guest_84757allah makes the day into the day and allah makes the night into the day11:34
Guest_84757allah gives life and Allah gives death11:34
Guest_84757all creation are useless,worthless,hopeless11:35
Guest_84757can not do11:35
Guest_84757can not benefit11:35
Guest_84757can not harm11:35
Guest_84757allah is the doer of each and everything11:36
Guest_84757when Allah wants us to stand we stand11:37
Guest_84757when Allah wants us to sit we sit11:37
Guest_84757i am not doing Allah is doing11:38
Guest_84757you are not doing Allah is doing11:38
Guest_84757atom bomb is not doing Allah is doing11:38
Zarawait what11:39
*** shaohe_feng has quit IRC11:39
*** rbowen has quit IRC11:40
*** shaohe_feng has joined #openstack-meeting11:40
Guest_84757rice is not doing Allah is doing11:40
*** sacharya has joined #openstack-meeting11:41
*** reedip has joined #openstack-meeting11:42
Guest_84757all creation get together can not create one grain of rice11:43
Guest_84757all humans get together can not stop rain11:44
*** coolsvap_ has joined #openstack-meeting11:44
*** sridharg has quit IRC11:45
*** reedip has quit IRC11:45
*** coolsvap has quit IRC11:45
*** obondarev has joined #openstack-meeting11:45
*** sacharya has quit IRC11:46
*** coolsvap_ has quit IRC11:46
*** thorst_ has joined #openstack-meeting11:46
*** coolsvap has joined #openstack-meeting11:46
Guest_84757all humans get together can not make anybody hungry11:47
*** shaohe_feng has quit IRC11:50
Guest_84757all humans get together can not move sun one second up or down11:50
*** shaohe_feng has joined #openstack-meeting11:50
*** amitgandhinz has joined #openstack-meeting11:51
asettleZara: spam bot. Happened last week too11:51
*** salv-orl_ has quit IRC11:51
*** gcb has quit IRC11:52
*** salv-orlando has joined #openstack-meeting11:52
*** yolanda has joined #openstack-meeting11:55
Guest_84757we can not count the hair on our head11:55
*** amitgandhinz has quit IRC11:55
Guest_84757we can not count the rain drops11:56
*** spotz is now known as spotz_zzz11:57
*** akuznetsov has joined #openstack-meeting11:57
*** salv-orlando has quit IRC11:58
Guest_84757we can not count the particles of sand11:58
*** salv-orlando has joined #openstack-meeting11:58
*** dprince has joined #openstack-meeting11:59
Guest_84757medicine has no power to cure11:59
*** shaohe_feng has quit IRC12:00
*** amotoki has quit IRC12:00
*** shaohe_feng has joined #openstack-meeting12:00
*** baoli has joined #openstack-meeting12:01
*** reedip has joined #openstack-meeting12:01
*** reedip has quit IRC12:01
*** AndyWojo has joined #openstack-meeting12:01
Guest_84757two people take same medicine one passes away and one does not12:01
*** baoli_ has joined #openstack-meeting12:02
Guest_84757degree has no power to give job12:03
Zaraasettle: sometimes I like to imagine spambots are real people, painstakingly typing out the same list of things :D12:04
asettleZara: HAHAHA you and me both.12:04
asettleI get a real kick out of this one.12:04
asettle"We can not count the particles of sand"12:04
asettleJust, inspiring.12:04
*** gcb has joined #openstack-meeting12:05
*** armax has joined #openstack-meeting12:05
ZaraI've never seen it get this far before. I also like how long it takes this one to paste the spam links.12:05
*** baoli has quit IRC12:05
Zaranormally they only do that bit...12:05
*** dmorita has joined #openstack-meeting12:06
*** markvoelker has joined #openstack-meeting12:06
*** armax has quit IRC12:06
*** coolsvap has quit IRC12:07
*** amotoki has joined #openstack-meeting12:09
*** rodrigods has quit IRC12:09
*** rodrigods has joined #openstack-meeting12:09
asettleIt's trying something different? New? Exciting? :p12:09
*** dmorita has quit IRC12:10
*** shaohe_feng has quit IRC12:10
*** shaohe_feng has joined #openstack-meeting12:11
*** dmacpher has joined #openstack-meeting12:11
*** rbowen has joined #openstack-meeting12:12
Guest_84757many people have degrees but do not have jobs12:13
*** zqfan has quit IRC12:13
*** jungleboyj has joined #openstack-meeting12:16
*** nadya has quit IRC12:17
*** paul-carlton2 has joined #openstack-meeting12:17
*** Hosam has joined #openstack-meeting12:18
*** adiantum has joined #openstack-meeting12:18
Guest_84757sustenance does not depend on effort12:19
*** nisha_ has quit IRC12:19
*** tochi has quit IRC12:19
*** nisha_ has joined #openstack-meeting12:19
Guest_84757one person is working very much but is earning very less12:20
*** shaohe_feng has quit IRC12:20
Guest_84757other person is working very less but is earning very much12:21
*** reedip has joined #openstack-meeting12:21
*** Guest_84757 has left #openstack-meeting12:22
*** neil_ has quit IRC12:22
*** piet has joined #openstack-meeting12:22
*** aysyd has joined #openstack-meeting12:23
*** shaohe_feng has joined #openstack-meeting12:23
*** reedip has quit IRC12:25
*** piet has quit IRC12:26
*** shaohe_feng has quit IRC12:31
*** thorst_ is now known as thorst12:31
*** shaohe_feng has joined #openstack-meeting12:31
*** kylek3h has joined #openstack-meeting12:32
*** zeih has quit IRC12:33
*** zeih has joined #openstack-meeting12:33
*** dneary has joined #openstack-meeting12:33
*** flip214_ has joined #openstack-meeting12:34
*** preisner has quit IRC12:34
*** amrith is now known as _amrith_12:35
*** phil has joined #openstack-meeting12:35
*** phil is now known as preisner12:35
*** flip214 has quit IRC12:35
*** MaxPC has joined #openstack-meeting12:35
*** MaxPC has quit IRC12:35
*** flip214_ is now known as flip21412:35
*** flip214 has quit IRC12:35
*** flip214 has joined #openstack-meeting12:35
*** Hosam has quit IRC12:36
Zarahaha, the spambot left of its own accord12:38
*** MaxPC has joined #openstack-meeting12:40
*** shaohe_feng has quit IRC12:41
*** shaohe_feng has joined #openstack-meeting12:41
*** reedip has joined #openstack-meeting12:41
*** annemccormick has joined #openstack-meeting12:41
*** eharney has quit IRC12:42
*** salv-orlando has quit IRC12:42
*** salv-orlando has joined #openstack-meeting12:43
*** reedip has quit IRC12:44
*** reedip_ has joined #openstack-meeting12:44
*** reedip_ has quit IRC12:45
*** iceyao has quit IRC12:45
*** dane_leblanc has joined #openstack-meeting12:46
*** numans has quit IRC12:47
*** kylek3h has quit IRC12:47
*** ljxiash has joined #openstack-meeting12:47
*** jungleboyj has quit IRC12:48
*** ljxiash_ has joined #openstack-meeting12:49
*** links has quit IRC12:51
*** shaohe_feng has quit IRC12:51
*** amitgandhinz has joined #openstack-meeting12:51
*** yanyanhu has joined #openstack-meeting12:51
*** dane_leblanc has quit IRC12:52
*** ljxiash has quit IRC12:52
*** shaohe_feng has joined #openstack-meeting12:52
*** links has joined #openstack-meeting12:52
*** ljxiash_ has quit IRC12:53
asettleZara that's kinda sad :p12:53
*** Ravikiran_K has joined #openstack-meeting12:54
Zarayeah, maybe it got paid less than another spambot and just came in here to rant about it12:54
*** amitgandhinz has quit IRC12:56
*** lixinhui_ has joined #openstack-meeting12:57
*** kylek3h has joined #openstack-meeting12:57
*** rbowen has quit IRC12:58
*** dane_leblanc has joined #openstack-meeting12:59
*** akuznetsov has quit IRC13:00
Qiming#startmeeting senlin13:00
openstackMeeting started Tue Jun  7 13:00:10 2016 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: senlin)"13:00
openstackThe meeting name has been set to 'senlin'13:00
Qiming#topic roll call13:00
*** openstack changes topic to "roll call (Meeting topic: senlin)"13:00
*** xuhaiwei__ has joined #openstack-meeting13:00
yanyanhuhello13:00
Qiminghi13:00
*** elynn has joined #openstack-meeting13:01
xuhaiwei__hi13:01
Qiminghi, haiwei13:01
lixinhui_hi13:01
yanyanhunetwork connection at home is really unstable13:01
elynno/13:01
*** gjayavelu has joined #openstack-meeting13:01
Qiming#topic newton work items13:01
*** openstack changes topic to "newton work items (Meeting topic: senlin)"13:01
*** mriedem_away is now known as mriedem13:01
Qimingtesting, where are we ?13:01
*** shaohe_feng has quit IRC13:01
*** liamji has quit IRC13:02
elynnenable tempest api on gate13:02
yanyanhu50% I think13:02
yanyanhuabout negative test cases13:02
elynnSaw some patches submitted by yanyanhu, many thanks!13:02
*** shaohe_feng has joined #openstack-meeting13:02
*** xyang1 has joined #openstack-meeting13:02
*** reedip_ has joined #openstack-meeting13:02
Qimingokay, so we did find some inconsistencies in apis13:02
yanyanhuelynn, my pleasure :)13:02
yanyanhualso found some issues about our API implementation when writing the test13:02
Qimingelynn, posted some comments to you latest patches13:03
yanyanhuQiming, yes13:03
yanyanhuthat is valuable13:03
*** rwsu has joined #openstack-meeting13:03
elynnQiming: will check :)13:03
Qimingtempest dsvm gate is not very slow, right?13:03
yanyanhuyes13:03
Qiminggreat13:04
*** fnaval has quit IRC13:04
Qimingrally side13:04
Qimingpatch 318453 was in13:04
yanyanhugate job is finally ready13:04
Qimingyou mean gate job at senlin side?13:05
*** reedip_ has quit IRC13:05
yanyanhuand the 301522 works well now13:05
yanyanhuboth side13:05
yanyanhuin rally and senlin13:05
yanyanhujust need to address rally teams question about that patch13:05
*** sarob has joined #openstack-meeting13:05
yanyanhubut no critical obstacle I think13:05
Qimingwe don't rely on 301522 to run gate at senlin side, right?13:05
yanyanhuyes13:06
yanyanhuthat is for rally repo13:06
Qimingmy question is about the gate failures we saw when doing 'check experimental' at senlin side13:06
yanyanhuactually 307170 works as well13:06
*** zhurong has joined #openstack-meeting13:07
yanyanhuyou mean this one? https://review.openstack.org/30717013:07
Qimingoh?13:07
Qimingthat is the first time we have gate-rally-dsvm-senlin-senlin working!!13:07
yanyanhusorry, I was dropped13:08
yanyanhuQiming, yes :)13:08
elynnThis name is a little weird...13:08
yanyanhuelynn, yes if you mean senlin-senlin.yaml :)13:08
Qimingyes, let's get it in and fix it later?13:08
yanyanhuthat is because we try to match gate-dsvm-rally-senlin-{name} job template13:08
yanyanhuQiming, ok, I think I may need to do some clean job before that patch become ready13:09
Qimingokay13:09
yanyanhuwill remove[WIP] when it's ok13:09
*** edtubill has joined #openstack-meeting13:09
elynndouble senlin, now we have amazon :P13:09
yanyanhu:P13:10
*** sudipto has joined #openstack-meeting13:10
yanyanhuand will discuss with eldon about their test based on rally13:10
Qimingbetter rename that... it is strange, indeed13:10
yanyanhuhope can provide some help for them13:10
*** sarob has quit IRC13:10
yanyanhuQiming, yes, I think maybe we can propose another job template in future13:11
*** shaohe_feng has quit IRC13:12
Qimingsure, we can work together on stress tests13:12
elynnAnyway, now we have many eyes on gates :)13:12
yanyanhuyes13:12
Qimingmoving on13:12
Qiminghealth management13:12
*** amotoki has quit IRC13:13
QimingI saw xinhui has taken over that lbaas bug13:13
Qimingpatch proposed now13:13
*** fnaval has joined #openstack-meeting13:13
yanyanhucool13:13
lixinhui_yes13:13
lixinhui_I am doing that13:13
Qimingmany thanks13:13
lixinhui_my pleasure13:14
lixinhui_will contribute more in next weeks13:14
Qimingthere are still some gate failures13:14
*** Julien-zte has joined #openstack-meeting13:14
lixinhui_en13:14
*** adiantum has quit IRC13:14
*** julenlar is now known as julenl13:15
*** shaohe_feng has joined #openstack-meeting13:15
QimingI have added health monitoring by listening to vm lifecycle events13:15
Qimingit took me quite some time to understand the filtering logics13:15
*** fwdit has quit IRC13:15
lixinhui_congrats!13:15
*** amotoki has joined #openstack-meeting13:15
lixinhui_you got it13:15
Qimingthere are still things unstable inside oslo.messaging, complaining that some regex matching failures13:15
lixinhui_will learn from you13:15
*** merooney has joined #openstack-meeting13:16
Qiminganyway, we can get notified when vm status was modified (reboot, start, stop, ...)13:16
Qimingnext thing is to trigger some actions13:16
lixinhui_is that reliable?13:16
Qimingwill dive into that13:16
lixinhui_I mean the lisetning13:16
Qiminglistening is reliable, just some initialization wasn't complete I guess13:17
*** dslevin has left #openstack-meeting13:17
*** jmckind has joined #openstack-meeting13:17
lixinhui_...13:17
Qimingwhen I restart the engine, the listeners are created, but not receiving events13:17
*** toddjohn has joined #openstack-meeting13:17
Qimingmaybe need to do some fuzzy delay13:17
lixinhui_ok13:18
*** zeih has quit IRC13:18
Qimingas for health threshold13:19
QimingI'm thinking of using desired_capacity13:19
lixinhui_could you explain more?13:19
*** jichen has quit IRC13:20
lixinhui_if time permits13:20
*** bobh has joined #openstack-meeting13:20
Qimingmake desired_capacity the health threshold13:20
Qiminga cluster is treated healthy if the number of active nodes >= desired_capacity13:21
*** reedip_ has joined #openstack-meeting13:21
*** fnaval has quit IRC13:21
Qimingmake sense?13:22
*** shaohe_feng has quit IRC13:22
lixinhui_okay13:22
lixinhui_too hash?13:22
*** toddjohn has quit IRC13:22
*** shaohe_feng has joined #openstack-meeting13:22
yanyanhuQiming, if so, the node number could beyond desired_capacity?13:22
Qimingyes, between max_size and desired_capacity13:22
xuhaiwei__what is the case node number bigger than desired_capacity?13:23
yanyanhuhmm, sounds a little different from our discussion in summit13:23
*** nmagnezi has quit IRC13:23
Qimingwhen you do cluster check, there are some nodes not responding13:24
Qimingwhen you do some operations later, those nodes come back to life13:24
*** doug-fish has joined #openstack-meeting13:25
*** reedip_ has quit IRC13:25
Qimingdid we have any discussion about the health threshold during summit?13:25
xuhaiwei__so the desired_capacity only contains the alive nodes?13:25
yanyanhuyes, so will the total number of health node finally match the desired_capacity13:25
Qimingdesired is always the 'desired'13:25
yanyanhuQiming, no, it's not about health threshold13:25
yanyanhuabout the scaling basement13:25
*** bobh has quit IRC13:26
Qimingit is not the number of actually active nodes, we can never assume so13:26
*** asselin_ has joined #openstack-meeting13:26
yanyanhuQiming, yes, that's what I mean. I think the case that total number of node beyond desired_capacity is kind of transient status?13:26
*** grassass has quit IRC13:27
Qimingif you don't do something, those nodes will be there13:27
yanyanhufinally, health nodes amount will be desired_capacity13:27
Qimingthere are transient status some nodes are not active when you are checking them13:27
*** sdake has joined #openstack-meeting13:27
Qimingthe question is why are we maintaining the number of healthy nodes?13:28
*** nisha has joined #openstack-meeting13:28
*** zeih has joined #openstack-meeting13:28
Qimingwe are already not so sure about the number of active nodes, considering that there are transient problems13:28
Qimingwhat we do care is "whether the cluster is healthy"13:29
Qimingwhich means there are enough nodes to share workloads13:29
Qimingby "enough" here, we mean that number of active nodes >= desired capacity13:29
Qimingyes, it is a bit hash13:30
*** nisha_ has quit IRC13:30
yanyanhuyes. I think user specifies the desired_capacity which is the number of health nodes they want to have, so we should try to match it and the actual active nodes number?13:30
Qimingbut is there any way to maintain another statistics?13:30
*** dslevin has joined #openstack-meeting13:30
Qimingassume you are the user, when you are specifying desired_capacity, what are you thinking?13:31
yanyanhuhmm, I want a cluster with this number of nodes being active13:31
yanyanhuhealthy13:31
*** banix has joined #openstack-meeting13:31
*** hdaniel has quit IRC13:32
Qimingthere could be a case where a user wants to create a cluster of 10 nodes, but 5 nodes is okay for him/her13:32
*** shaohe_feng has quit IRC13:32
*** reedip has joined #openstack-meeting13:32
yanyanhuyes, that is possible13:32
Qimingwhy is he doing that?13:32
*** shaohe_feng has joined #openstack-meeting13:33
*** eharney has joined #openstack-meeting13:33
Qimingif 5 is okay, then 5 is the min_size, right?13:33
*** lblanchard has joined #openstack-meeting13:33
yanyanhuhmm, I think that means in any cases, the cluster size should not be less than 513:34
Qimingyes, then 5 is actually the min_size13:34
yanyanhuthat is not directly related to health management13:34
*** sdake_ has joined #openstack-meeting13:34
yanyanhuyes, 5 is the min_size13:34
Qimingif the cluster is dropping below that level, the cluster is in error status13:34
yanyanhuI think that's two cases13:35
Qimingif cluster size is between min_size and desired_capacity, we can treat it as warning13:35
yanyanhuif cluster size is less than 5, that means internal error happened in senlin side13:35
*** reedip has quit IRC13:35
Qimingit is all about how we define the status of a cluster13:35
Qimingusers don't care what happened13:35
yanyanhuyes, understand what you mean, just feel we shouldn't mix health management case and scaling case13:35
Qimingmaybe some nova nodes crashed13:36
Qimingyou cannot say it is senlin's fault13:36
yanyanhuIMHO, min_size/max_size/desired is about scaling cases13:36
*** sdake has quit IRC13:36
Qimingthey are properties you specify when you create a cluster13:36
Qimingno matter you will scale that cluster or not13:36
yanyanhuyes, that's the hard limit of cluster size13:37
yanyanhuno matter the cluster has HA management support or not13:37
Qimingexactly13:37
*** gjayavelu has quit IRC13:37
Qimingso ... I'm wondering if we do want to introduce another threshold into senlin at the moment13:38
yanyanhuso I think desired_capacity is something related to HA since it's user desired13:38
Qimingand we can never make sure it matches the reality13:38
yanyanhuQiming, I agree we consider desired_capacity a health related property13:38
yanyanhubut min_size, max_size could not be13:38
*** amitgandhinz has joined #openstack-meeting13:39
*** amitgandhinz has quit IRC13:39
*** edtubill has quit IRC13:39
Qimingokay, agree to disagree13:39
Qiminglet's think about it offline13:39
yanyanhuok13:39
*** amitgandhinz has joined #openstack-meeting13:39
yanyanhuwe can have a further discussion tomorrow :)13:39
QimingI'd suggest we forget all the actions/policies we have in senlin13:39
yanyanhureally need more thinking about it13:39
Qimingjust think from a user's perspective, what makes a better sense for them13:40
yanyanhuagree with this13:40
lixinhui_jealous13:40
yanyanhua clear definition from user perspective is the most important13:40
lixinhui_you can discuss face to face13:40
Qimingwe will discuss on irc13:41
*** grassass has joined #openstack-meeting13:41
lixinhui_:)13:41
yanyanhulixinhui_, you can come here, some one will buy you coffee :P13:41
lixinhui_cool!13:41
lixinhui_or you can come to VMware13:41
lixinhui_tomorrow we have happy hour13:41
yanyanhufor free coffee :)13:41
*** hoangcx has joined #openstack-meeting13:41
*** iceyao has joined #openstack-meeting13:41
lixinhui_:P13:41
Qimingwe can define min_size, health_watermark, desired_capacity and max_size13:42
Qimingtry if you can explain all these four numbers to users13:42
yanyanhuhmm, need more thinking on it13:42
Qimingokay, let's move on13:42
*** shaohe_feng has quit IRC13:42
*** longxiongqiu has quit IRC13:43
Qimingany news from you lixinhui_ on health management?13:43
*** tfukushima has joined #openstack-meeting13:43
lixinhui_Sorry, Qiming13:43
lixinhui_I will try to contribute more in the followed weeks13:43
yanyanhulast sentence from me about this issue: maybe we should re consider why user define min_size/max_size and whether and when they really need it :)13:43
*** shaohe_feng has joined #openstack-meeting13:43
lixinhui_too distract13:43
*** tfukushima has quit IRC13:43
*** ssalagame has joined #openstack-meeting13:43
Qimingno worry, just ask questions, in case you have moving too fast13:43
*** nisha has quit IRC13:43
lixinhui_:)13:44
Qimingno update on documentation from me13:44
Qimingcontainer support13:44
xuhaiwei__I submitted a patch13:44
*** korzen has joined #openstack-meeting13:44
xuhaiwei__initialize docker driver13:45
*** longxiongqiu has joined #openstack-meeting13:45
Qimingsaw some patches from haiwei, I think we have been mixing things in a strange way13:45
Qimingwill have a closer look at the patch13:46
xuhaiwei__yes, please comment it13:46
Qimingnotification/event side, some basics are there13:46
Qimingneed some serializers and an example to encapsulate a notification into an object13:47
*** jmckind has quit IRC13:47
Qimingthen dispatch that object to oslo.messaging or db13:47
Qimingwill continue work on that13:47
Qimingzaqar work is stalled13:47
Qimingthat's all from the etherpad13:48
Qimingthings to add?13:48
*** amotoki has quit IRC13:48
yanyanhunope, really lots of work items13:48
Qiming#topic senlin cluster-do operation13:49
*** openstack changes topic to "senlin cluster-do operation (Meeting topic: senlin)"13:49
Qiminghere is the patch: https://review.openstack.org/#/c/326208/13:49
*** regXboi has joined #openstack-meeting13:49
*** longxiongqiu has quit IRC13:49
*** hichihara has joined #openstack-meeting13:49
Qimingwe are adding OPERATIONS to a profile definition13:49
Qimingit is not exposed to users for customization13:49
*** jlibosva has joined #openstack-meeting13:50
*** elynn has quit IRC13:50
Qimingbut implementation wise, we are modeling operation parameters using schemas13:50
*** jmckind has joined #openstack-meeting13:50
*** xiaohhui has quit IRC13:50
yanyanhuoh, its for this purpose13:50
*** honghuixiao_ has joined #openstack-meeting13:50
yanyanhuI didn't get it when saw it first time13:50
*** nadya has joined #openstack-meeting13:51
Qimingso an operation can be easily verified when we get a JSON containing the operation requested13:51
yanyanhuwill check it13:51
*** jckasper has quit IRC13:51
yanyanhuyep13:51
yanyanhuthat's a nice wrap13:51
Qimingan operation request could be {"reboot": {"type": "HARD"}}13:51
*** reedip has joined #openstack-meeting13:51
*** jckasper has joined #openstack-meeting13:51
Qimingwhen users input senlin cluster-do help cluster113:51
Qimingwe can iterate through the OPERATIONS dict and return a help text --- here are operations you can try13:52
*** zeih has quit IRC13:52
Qimingjust like when you do senlin profile-type-show <a-profile-type>13:52
yanyanhunice13:52
*** shaohe_feng has quit IRC13:53
Qimingin the case of a nova server cluster, you can do 'senlin cluster-do reboot --type=HARD cluster1'13:53
*** nadya has quit IRC13:53
Qimingcommand wise, we can add more parameters so that users can reboot nodes with specific roles, but those can be added later13:53
Qimingparameters are checked just like profile/policy properties, they have data types13:54
lixinhui_:)13:54
Qimingthe only difference is that they are not 'updatable'13:54
Qimingthat is why I revised the common schema module13:54
yanyanhuyes, saw that patch13:55
*** sridharg has joined #openstack-meeting13:55
*** reedip has quit IRC13:55
Qimingin future there could be some extensions to Operation schema, today it is only just a Map13:55
Qimingthat's some background about that patch13:55
Qiming#topic open discussions13:55
*** psargent has joined #openstack-meeting13:55
*** openstack changes topic to "open discussions (Meeting topic: senlin)"13:55
QimingI think we have covered the health management part13:55
*** rbak has joined #openstack-meeting13:56
*** shaohe_feng has joined #openstack-meeting13:56
lixinhui_yes13:56
*** yohoffman has joined #openstack-meeting13:56
Qimingand ... 1 hour is definitely not enough for discussion13:56
*** paul-carlton2 has quit IRC13:56
*** obondarev has quit IRC13:56
lixinhui_nod13:56
yanyanhuyes :)13:56
Qimingneed some homework before we discuss it again13:56
*** boden has joined #openstack-meeting13:56
Qimingpls think from user's perspective13:56
Qiming:)13:56
yanyanhuwill think about it as well13:57
lixinhui_:)13:57
yanyanhuyes13:57
xuhaiwei__ok13:57
*** psargent_ has joined #openstack-meeting13:57
*** john-davidge has joined #openstack-meeting13:57
*** amotoki__ has joined #openstack-meeting13:57
*** ankur-gupta-f1 has joined #openstack-meeting13:58
Qimingoh, don't know if you have noticed it13:58
Qimingwe have had senlin 2.0.0.0b1 released last Friday13:58
Qimingsenlinclient 0.5.0 released today13:58
xuhaiwei__saw it13:59
Qimingsenlinclient version jump was based on release team's suggesion13:59
*** bill_az has joined #openstack-meeting13:59
*** twm2016 has joined #openstack-meeting13:59
Qimingleave some version numbers for back-port13:59
*** rderose has joined #openstack-meeting13:59
*** manjeets has joined #openstack-meeting13:59
*** claudiub has joined #openstack-meeting13:59
Qimingem.13:59
*** hynekm has joined #openstack-meeting13:59
*** gjayavel_ has joined #openstack-meeting13:59
yanyanhuin global requirement?13:59
*** spotz_zzz is now known as spotz13:59
Qimingnot yet propsed to global requirements13:59
yanyanhuI see13:59
Qimingfeel free to do so13:59
Qiming#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Tue Jun  7 14:00:03 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-06-07-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-06-07-13.00.txt14:00
Qimingthanks for joining14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-06-07-13.00.log.html14:00
ihrachys#startmeeting networking14:00
openstackMeeting started Tue Jun  7 14:00:45 2016 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
mesteryo/14:00
njohnstono/14:00
dasmo/14:00
hichiharahi14:00
manjeetshi14:00
bodeno/    howdy14:01
andreas_so/14:01
hoangcxhi14:01
HenryGo/14:01
bloganhi14:01
bcafarelo/ hi14:01
haleybhi14:01
*** paul-carlton1 has joined #openstack-meeting14:01
john-davidgeo/14:01
*** yanyanhu has quit IRC14:01
johndperkinshi14:01
ajo_o/14:01
*** jckasper has quit IRC14:01
ihrachyswow, seems like people long for meetings14:01
jschwarzo/14:01
amotoki__hi14:01
psargenthi14:01
ihrachyshappy to see all of you :)14:01
*** paul-carlton1 has quit IRC14:01
*** janzian has joined #openstack-meeting14:01
ankur-gupta-f1\o/14:01
*** amuller has joined #openstack-meeting14:01
jlibosvahi14:01
*** lixinhui_ has quit IRC14:01
amullerhiho14:01
korzenhello14:01
njohnstonYou sraw the crowds, ihrachys.14:01
njohnstons/sraw/draw/14:02
*** jckasper has joined #openstack-meeting14:02
ajo_:D14:02
* ihrachys digs himself from under all those greetings14:02
*** _amrith_ is now known as amrith14:02
*** yamahata has joined #openstack-meeting14:02
ihrachys#link https://wiki.openstack.org/wiki/Network/Meetings Agenda14:02
ihrachys#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:02
*** hynekm has quit IRC14:03
ihrachysfirst thing first. We released Newton-1 yay!14:03
*** iyamahat has joined #openstack-meeting14:03
dasm\o/14:03
ihrachysdeliverables can be found at: http://releases.openstack.org/newton/14:03
*** shaohe_feng has quit IRC14:03
*** hynekm has joined #openstack-meeting14:03
ihrachysafaik nothing really fancy included there, but I guess it's business as usual14:03
*** gjayavel_ has quit IRC14:03
*** shaohe_feng has joined #openstack-meeting14:04
ihrachysalso, in case you haven't noticed, our PTL is on vacation14:04
ihrachysit doesn't stop him to stay online though :)14:04
mesteryHe's omniscient ihrachys :)14:04
ihrachysfinally, thanks to HenryG we have a midcycle meetup in August!14:05
ihrachysWARNING: original dates of the event changed14:05
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2016-May/096255.html14:05
ihrachysplease make sure you don't book wrong dates!14:05
*** zeih has joined #openstack-meeting14:05
ihrachysand I hope new dates are better for Europeans14:05
*** jckasper has quit IRC14:06
twm2016o/14:06
ajo_HenryG++14:06
ihrachys#topic Ongoing discussions14:06
*** openstack changes topic to "Ongoing discussions (Meeting topic: networking)"14:06
ihrachysour glorious PTL had an attempt to change release model for *aas deliverables14:07
ihrachysbut the attempt failed due to being late in the cycle, and no agreement14:07
*** asingh has joined #openstack-meeting14:07
ihrachysstill, Armando strives to revisit the governance structure for neutron deliverables a bit14:07
ihrachys#link https://review.openstack.org/#/c/323522/14:07
ihrachysplease comment, and bring your brushes14:08
*** longxiongqiu has joined #openstack-meeting14:08
ihrachysalso, I wonder whether amuller got the help he asked for at: http://lists.openstack.org/pipermail/openstack-dev/2016-May/094997.html14:08
ihrachysamuller: ?14:08
*** edtubill has joined #openstack-meeting14:09
amullerihrachys: We didn't progress as much as I wanted to14:09
*** longxiongqiu has quit IRC14:09
*** longxiongqiu has joined #openstack-meeting14:09
ihrachysok folks, something to consider ^ we can't leave our test lieutenant without soldiers :)14:09
amullerI don't like those terms =p14:09
ihrachys:) moving on...14:10
ihrachys#topic Bugs14:10
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:10
ihrachyshichihara is the deputy of the previous week, and ajo_ is this wek14:10
*** sbelous_ has joined #openstack-meeting14:10
ihrachyshichihara: would you mind giving a brief update of the prev week?14:10
hichiharaNo. Previous week is Carl or ajo?14:11
*** jamesdenton has joined #openstack-meeting14:11
*** reedip has joined #openstack-meeting14:11
ihrachysoh. it's actually kevinbenton I think14:11
*** banix has quit IRC14:11
ihrachysas per wiki page at least14:11
carl_baldwinRight, I was the week before.14:11
kevinbentonihrachys: so if i was supposed to be last week i messed up the week14:12
kevinbentonihrachys: and i have a backlog to go through :)14:12
*** toddjohn has joined #openstack-meeting14:12
ihrachysthe wiki page is confusing14:12
ajo_I also messed up, and I thought mine was next week somehow.. so I have 1 day back log at least (monday), and taking up now14:12
ajo_yes14:12
ihrachysit states kevinbenton to be the deputy14:12
ihrachyscarl_baldwin: so you run the prev week? anything worthy?14:12
ajo_that wiki page deserves a refactor (may be just two columns: date range, and who)  ?14:12
carl_baldwinihrachys: Mostly routine triaging.14:12
ihrachyskevinbenton: nah, that's ok, it seems wiki is wrong.14:12
carl_baldwinSaw one gate failure that was resolved by kevinbenton I think.14:13
ihrachysajo_: make sure we don't have bugs missed without attention from either of you14:13
*** shaohe_feng has quit IRC14:13
carl_baldwinajo_: +1 to wiki refactor.14:13
ajo_ihrachys, ack, we're syncing in private to catch up all of them14:13
*** edtubill has quit IRC14:13
ihrachys#action ajo_ to refactor wiki bug deputy section14:13
ajo_carl_baldwin, ack, handling it as we talk14:13
reedipajo_ +114:14
rossella_sajo_, thanks! I was having troubles with that too14:14
hichiharaajo_: +114:14
amotoki__for bug deputy etherpad might work14:14
carl_baldwinReduce it from O(nm) to O(n)14:14
*** shaohe_feng has joined #openstack-meeting14:14
ihrachysok thanks folks for doing the triaging14:14
ajo_who wants to be next, please tell me, I'll add as part of the refactor14:14
ihrachysright, we need next volunteers.14:14
ihrachyspreferrably two next weeks14:14
ihrachysJune 13-.. and June 20-..14:15
*** reedip has quit IRC14:15
HenryGI can do June 1314:15
ihrachysthanks HenryG! you already did it twice, it would be great to see someone with just one week served to chime in for June 20..-14:16
rossella_sI can take June 27...June 20 doesn't work for me, there's the opnfv summit14:16
*** toddjohn has quit IRC14:16
ihrachysrossella_s: sold! :)14:16
ajo_ack, I'll ad you both, we need to cover June 20- if somebody could14:17
*** tonytan4ever has joined #openstack-meeting14:17
ajo_btw, I will remove dates from old history, just the ocurrences of people in a nick list with no dates just for reference (to avoid history growing too tall)14:18
ihrachysajo_: ack14:18
ihrachysno volunteers? mestery: dasm: ? :)14:18
rossella_sajo_, I like optimization14:18
ajo_:D14:18
ihrachyshaleyb: blogan ?14:18
* ihrachys calls out people with one week served :)14:18
* ihrachys naively assumes the wiki is correct14:19
*** banix has joined #openstack-meeting14:19
ihrachysjlibosva: ?14:19
rossella_snot only cores, everyone can volunteer! it's a good way to learn14:19
* haleyb had tuned-out14:19
dasmihrachys: 13.07 can be for me14:19
john-davidgeI can do it, but it will be my first time :)14:19
dasmajo_: 13.0714:19
ihrachysjohn-davidge: that's ok, it's expected14:19
* blogan reads scrollback14:19
ihrachysdasm: if HenryG gives it to you, I am ok14:19
haleybihrachys: yes, i'm due for another14:20
john-davidgeihrachys: Then I volunteer for the 20th14:20
HenryGdasm: it's all yours14:20
HenryGdasm: thanks14:20
ihrachysok, so, June 13 is HenryG/dasm, June 20 is john-davidge and June 27 is rossella_s14:20
dasmHenryG: ++14:20
*** jungleboyj has joined #openstack-meeting14:20
ihrachysok, so we mentioned gate failures before...14:20
bloganput me down for the next one, but obviously thats too far away to put me down for14:20
ihrachys#link https://bugs.launchpad.net/neutron/+bugs?field.tag=gate-failure14:21
*** mohnish__ has joined #openstack-meeting14:21
*** irenab has quit IRC14:21
ihrachysdoesn't seem like anything critical is in the list right now, which is good14:21
ihrachysgrafana also seems calm now14:21
ihrachys#link http://grafana.openstack.org/dashboard/db/neutron-failure-rate14:21
*** asingh has quit IRC14:22
*** Leom has joined #openstack-meeting14:22
ihrachyswe had a gate failure for -api job yesterday due to fwaas tempest plugin being broken14:22
ihrachysbut the immediate fix landed into neutron-fwaas today14:22
ihrachysso it's safe to recheck14:22
HenryGIs the functional job timeout still happening sometimes? jlibosva?14:22
ajo_ack14:22
amulleralso due to devstack installing fwaas it broke the main neutron api job14:22
dasmHenryG: it seems so. i've seen timeouts couple of times14:22
ihrachysthat said, we should really decouple -api job from fwaas, which is the goal of sc68cal's set of kill patches:14:22
ihrachys#link https://review.openstack.org/#/q/status:open+topic:kill-off-fwaas-seriously14:22
ihrachysso folks please review ^14:23
jlibosvaI thought it doesn't, I'll sync with dasm14:23
amotoki__api job failure lao broke ceilometer gate.14:23
*** sshnaidm|afk has joined #openstack-meeting14:23
dasmjlibosva: ok.14:23
ihrachysamotoki__: they install fwaas too right?14:23
*** shaohe_feng has quit IRC14:23
amotoki__looks so.14:23
ihrachysthey probably do, due to devstack-gate14:23
ihrachysso, we should boost those patches of Sean.14:24
ihrachysbut for now, ceilometer can also recheck14:24
*** ssalagame has quit IRC14:24
*** hynekm has quit IRC14:24
*** hynekm has joined #openstack-meeting14:25
ihrachysok, I guess we will skip going thru newton-2 blueprints today. just a note to neutron drivers and cores and others: please make sure that neutron-specs patches get enough attention so that feature progress is not blocked due to specs.14:25
ihrachys#topic Docs14:25
*** openstack changes topic to "Docs (Meeting topic: networking)"14:25
*** ssalagame has joined #openstack-meeting14:26
* ihrachys haven't seen Sam-I-Am for a while14:26
*** shaohe_feng has joined #openstack-meeting14:26
ihrachysanyone to give an update on neutron docs?14:26
*** nisha_ has joined #openstack-meeting14:26
*** Leom_ has joined #openstack-meeting14:26
amotoki__recently some contents about dhcp has been moved from user guide.14:27
*** xuhaiwei__ has quit IRC14:27
*** mriedem is now known as mriedem_afk14:27
ihrachysamotoki__: is it good? bad?14:27
amotoki__also nwguide meeting faces low number of attendees14:27
*** irenab has joined #openstack-meeting14:27
*** zeih has quit IRC14:27
amotoki__that,s what i heard.14:27
ihrachys#link http://eavesdrop.openstack.org/#Networking_Guide_Team_Meeting14:28
ihrachysthat's the meeting event ^14:28
ihrachysamotoki__: thanks for the info14:28
*** jckasper has joined #openstack-meeting14:28
amotoki__difficult to type on smartphone :(14:28
*** bill_az has quit IRC14:29
ihrachys#topic Transition to OSC14:29
*** openstack changes topic to "Transition to OSC (Meeting topic: networking)"14:29
ihrachysdasm: wanna update the team?14:29
ajo_off band link: let me know if I broke something: https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy   :-)14:29
*** Leom has quit IRC14:29
dasmihrachys: probably amotoki__ knows better.14:29
rtheisI've updated https://etherpad.openstack.org/p/osc-neutron-support with current status for OSC 2.5.0 release14:29
*** woodster_ has joined #openstack-meeting14:30
rtheisOSC plugin patch set progress is slow14:30
amotoki__osc plugin patch got stalled. i talked with rtheis and I decided to take it.14:30
rtheisthanks amotoki__ !14:30
*** jamesdenton has quit IRC14:30
hichiharaajo_: Good!14:30
ajo_thanks amotoki__14:30
ihrachysrtheis: what's the strategy for new features?14:31
*** zz_dimtruck is now known as dimtruck14:31
rtheisihrachys: we are following strategy in devref: http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html14:31
rtheiscore resources go into OSC14:31
amotoki__one difficult point is where we should implement a patch. in general osc is the first priority.14:32
*** jlanoux has quit IRC14:32
rtheis*aaS and related go as OSC plugins within neutronclient14:32
ihrachysright. do we prioritize osc or neutronclient, and whether we should require new features to support OSC?14:32
manjeetsrtheis: i guess etherpad can be update ip availability is done14:32
manjeetsor is it updated after release ?14:32
ajo_njohnston, do you remember if we have qos support in OSC ? we may want to add it otherwise14:33
rtheismanjeets: I've been updated after release, 2.6.0 is coming soon14:33
hichiharaI thought new feature must go to OSC.14:33
njohnstonajo_: I believe it is in the list of things that still need to be done.14:33
dasmhichihara: http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html#developer-guide14:33
amotoki__neutronclient is optional14:33
*** reedip has joined #openstack-meeting14:33
ajo_njohnston, let's track it as a qos bug to make sure we don't forget or that we get help14:33
*** tonytan4ever has quit IRC14:33
*** shaohe_feng has quit IRC14:34
*** nkrinner has quit IRC14:34
hichiharadasm: Thanks14:34
rtheisno qos commands in OSC yet14:34
rtheisfor network that is, there is volume qos support14:34
ihrachysinteresting. I think we have specs in progress that talk about neutron CLI but not opentack. Maybe worth going thru them and -1? And maybe new spec template should state it more explicitly it's now a requirements...14:34
njohnstonajo_: agreed14:34
*** shaohe_feng has joined #openstack-meeting14:34
ajo_ihrachys: +114:34
dasmihrachys: makes sense.14:35
*** reedip has quit IRC14:35
ihrachys#action ihrachys to -1 all specs that don't cover OSC14:35
hichiharaihrachys: +114:35
*** nkrinner has joined #openstack-meeting14:35
*** sheel has quit IRC14:35
amotoki__ihrachys, +114:35
ihrachys#action ihrachys to update neutron-specs template to be explicit about OSC requirement14:35
*** nkrinner has quit IRC14:35
*** sdake_ has quit IRC14:36
manjeetsihrachys: +114:36
ihrachysok, I guess apart from that, it's a matter of coding and reviews that are always in shortage14:36
*** rossella_s has quit IRC14:36
ihrachysthanks amotoki__ for driving it!14:36
ihrachys#topic Moving to Keystone v3 API in Neutron14:36
*** openstack changes topic to "Moving to Keystone v3 API in Neutron (Meeting topic: networking)"14:36
ihrachysdasm: I guess that one is yours14:36
dasmihrachys: indeed.14:36
dasmcli part is merged and i believe got to n114:36
*** yuval has quit IRC14:37
dasmcurrently there are leftovers with keystoneclient: https://review.openstack.org/#/c/322268/14:37
ihrachysdasm: neutronclient is not part of milestones14:37
dasmihrachys: ack14:37
ihrachysdasm: but we may want to release client anyway. maybe let's sync on it after the meeting.14:37
*** ljxiash has joined #openstack-meeting14:37
dasmihrachys: ++14:37
*** cdub has joined #openstack-meeting14:37
dasmnext step is to update docs: especially developers14:38
*** asingh has joined #openstack-meeting14:38
dasmand two more "huge" parts left: db and codebase.14:38
dasmi'll try to finish changes for docs till end of week14:38
dasmand next one will focus on db.14:38
dasmthat's all14:38
amotoki__do we need more volunteers?14:39
ihrachysdasm: re patch for keystoneauth1 switch: how can we validate it does not break anything? we don't have coverage for designate, right?14:39
dasmwould be nice to have couple more eyes on it. esp in db.14:39
dasmihrachys: we do not have.14:39
dasmihrachys: i did the change based on keystone description, but there still could be a problem14:40
ihrachysdasm: is it covered in designate gate at least?14:40
dasmi'll check it again14:40
dasmand will talk to designate folks.14:41
*** nmagnezi has joined #openstack-meeting14:41
ihrachyslet's make sure we don't break anything for a cleanup. I hope they have some scenarios for neutron.14:42
*** otherwiseguy has quit IRC14:42
*** galstrom_zzz is now known as galstrom14:42
twm2016dasm: Are you talking about the keystone-v3 bp, that needs more help? For updating docs, and work in db and codebase.14:42
dasmtwm2016: yes.14:42
*** noslzzp has quit IRC14:42
twm2016- just clarifying, I'm going to look into it and see if i can help :)14:43
dasmtwm2016: ++14:43
*** fnaval has joined #openstack-meeting14:43
ihrachysok cool14:44
*** shaohe_feng has quit IRC14:44
ihrachyslet's make it happen14:44
ihrachysand finally...14:44
ihrachys#topic On Demand Agenda14:44
*** openstack changes topic to "On Demand Agenda (Meeting topic: networking)"14:44
*** asselin_ has quit IRC14:44
*** bryan_att has quit IRC14:44
ihrachysthe agenda is empty14:44
ihrachysbut I wanted to raise one thing14:44
*** martines has quit IRC14:44
*** shaohe_feng has joined #openstack-meeting14:45
ihrachysupgrades team works on converting db code to using objects.14:45
ihrachysand sometimes we lack core reviewers.14:45
*** xyang has joined #openstack-meeting14:45
ihrachyswe think that maybe it's due to low exposure of the work to the whole team14:45
ihrachysso we started to produce bi-weekly status updates with links to interesting patches14:46
ihrachysfirst one is:14:46
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2016-June/096512.html14:46
*** pc_m has joined #openstack-meeting14:46
ihrachysthanks to korzen for preparing it14:46
*** ankur-gupta-f1 has quit IRC14:46
korzenihrachys, np14:46
amotoki__nice idea14:46
ihrachyswould love to see people read and click thru some links there to make yourself more aware about that process.14:46
ajo_thanks, that's very helpful14:46
blogan+114:47
ihrachysok, that's all I have. anything else?14:47
carl_baldwinihrachys: That will be helpful.  I'll try to review more there.14:47
amotoki__for more background of the work, the summit video will help you much14:47
ihrachyscarl_baldwin: thanks! some of that stuff is WIP, but I think we finally got to the point where we can land more invasive patches.14:48
*** zeih has joined #openstack-meeting14:48
ihrachysI guess amotoki__ refers to https://www.youtube.com/watch?v=UQLBw1_VGcU14:48
amotoki__yeah14:48
*** amotoki__ has quit IRC14:49
ihrachysok, I guess no more topics and we can enjoy 10 mins till a next meeting :)14:49
ihrachysthanks everyone, really glad to see all of you at that early time of day (for some) :)14:49
*** amotoki__ has joined #openstack-meeting14:49
ihrachys#endmeeting14:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:49
openstackMeeting ended Tue Jun  7 14:49:23 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-06-07-14.00.html14:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-06-07-14.00.txt14:49
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-06-07-14.00.log.html14:49
dasmo/14:49
hichiharabye14:49
andreas_sbye14:49
jlibosva\o14:49
*** karthikp_ has joined #openstack-meeting14:49
*** otherwiseguy has joined #openstack-meeting14:49
*** janzian has left #openstack-meeting14:49
*** boden has left #openstack-meeting14:49
manjeets\o/14:49
amotoki__thanks14:50
*** hynekm has left #openstack-meeting14:50
*** pc_m has left #openstack-meeting14:50
*** iyamahat has quit IRC14:50
*** timcline has joined #openstack-meeting14:50
*** mickeys has joined #openstack-meeting14:50
*** hichihara has quit IRC14:51
*** reedip has joined #openstack-meeting14:51
*** twm2016 has left #openstack-meeting14:51
*** renato_r has joined #openstack-meeting14:51
*** yohoffman has quit IRC14:52
*** moshele has joined #openstack-meeting14:52
*** moshele has left #openstack-meeting14:52
*** hongbin has joined #openstack-meeting14:52
*** jlibosva has left #openstack-meeting14:52
*** zeih has quit IRC14:52
*** amotoki__ has quit IRC14:52
*** liamji has joined #openstack-meeting14:53
*** hoangcx has quit IRC14:53
*** amotoki has joined #openstack-meeting14:53
*** yuval has joined #openstack-meeting14:53
*** renato_r_ has joined #openstack-meeting14:54
*** shaohe_feng has quit IRC14:54
*** shaohe_feng has joined #openstack-meeting14:55
*** reedip has quit IRC14:55
*** sbelous_ has left #openstack-meeting14:56
*** weshay has quit IRC14:56
*** obondarev has joined #openstack-meeting14:56
*** renato_r has quit IRC14:57
*** gampel has joined #openstack-meeting14:57
*** bryan_att has joined #openstack-meeting14:57
*** arvinc_ has joined #openstack-meeting14:57
*** arvinc_ has quit IRC14:57
*** martines has joined #openstack-meeting14:57
*** arvinc_ has joined #openstack-meeting14:58
*** arvinc_ has quit IRC14:59
*** jlanoux has joined #openstack-meeting14:59
carl_baldwinHi15:00
john-davidgehi15:00
jschwarzhi15:00
*** mlavalle has joined #openstack-meeting15:00
honghuixiao_hello15:00
bloganhello15:00
*** whenry has joined #openstack-meeting15:00
mlavalleo/15:00
carl_baldwinLet's get started.15:00
haleybhi15:00
carl_baldwin#startmeeting neutron_routed_networks15:00
openstackMeeting started Tue Jun  7 15:00:49 2016 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_routed_networks)"15:00
openstackThe meeting name has been set to 'neutron_routed_networks'15:00
carl_baldwin#topic Announcements15:00
*** openstack changes topic to "Announcements (Meeting topic: neutron_routed_networks)"15:00
*** saggi has joined #openstack-meeting15:01
carl_baldwin#link https://etherpad.openstack.org/p/routed-provider-networks-notes15:01
carl_baldwinN-1 is past and I actually think we're pretty close to where I was hoping to be at this point.15:01
mlavalle++15:01
carl_baldwinAlso, is everyone aware of the mid-cycle planned?15:01
bloganyep15:02
mlavalleI am15:02
john-davidgeyep15:02
mlavalle17 - 19 August15:02
bloganyall have fun :)15:02
*** absubram has quit IRC15:02
carl_baldwin^ Please take special note of the dates as they have been changed!15:02
jschwarzyep15:02
carl_baldwinIt is going to be Wed - Fri, not Mon - Wed as was originally announced.15:03
mlavalleThis is the etherpad:15:03
*** regXboi has quit IRC15:03
mlavalle#link https://etherpad.openstack.org/p/newton-neutron-midcycle15:03
*** zhurong has quit IRC15:03
carl_baldwinmlavalle: Thanks!15:03
carl_baldwinAny other announcements?15:04
carl_baldwin#topic Devstack15:04
*** openstack changes topic to "Devstack (Meeting topic: neutron_routed_networks)"15:04
*** shaohe_feng has quit IRC15:04
carl_baldwinI got thinking yesterday that there is a fair amount of manual setup that needs to be done to get a devstack system to work with segments.15:05
carl_baldwinI started a patch to hopefully provide some help15:05
john-davidgegreat!15:05
carl_baldwin#link https://review.openstack.org/32610315:05
carl_baldwinIt isn't much yet.15:05
*** shaohe_feng has joined #openstack-meeting15:05
mlavalleI think this complements well what I've been doing with Vagrant15:06
carl_baldwinBut, hopefully it can evolve in to something helpful.15:06
*** vishwanathj has joined #openstack-meeting15:06
mlavalleI am creating a Vagrant setup to to create a multi-node devstack with segments15:06
carl_baldwinmlavalle: How's that going?  Do you want to add information about what you're doing to this section of the etherpad?15:06
blogansounds like a great idea15:06
*** ssalagame has quit IRC15:06
carl_baldwinmlavalle: Maybe we can merge these efforts.15:07
*** banix has quit IRC15:07
*** iyamahat has joined #openstack-meeting15:07
mlavallecarl_baldwin: yes I will add to the etherpad. I expect to port the product to github over the next couple of days15:07
*** rbowen has joined #openstack-meeting15:07
*** fnaval has quit IRC15:07
carl_baldwinmlavalle: Sounds good.15:07
mlavalleas always, progress is slower that originally thought :-)15:07
mlavallebut I am making steady progress15:08
mlavalleand yes, let's merge these 2 efforts. I'll leverage your patchset15:08
*** duvarenkov__ has joined #openstack-meeting15:08
carl_baldwinmlavalle: Great.  Try to add to the etherpad when you have something that can be shared.15:08
*** aarefiev_ has joined #openstack-meeting15:08
carl_baldwin#topic Associating Subnets to Segments15:08
*** openstack changes topic to "Associating Subnets to Segments (Meeting topic: neutron_routed_networks)"15:09
*** rvasilets__ has joined #openstack-meeting15:09
*** oshidoshi has joined #openstack-meeting15:09
*** e0ne_ has joined #openstack-meeting15:09
carl_baldwinThere are a couple of patches in play15:09
carl_baldwin#link https://review.openstack.org/#/c/29517315:09
carl_baldwin#link https://review.openstack.org/#/c/315573/15:09
*** rubasov has quit IRC15:10
carl_baldwinI've +2ed the first, it could use another core's eyes.15:10
carl_baldwinThe second is a client patch.15:10
carl_baldwinNeeds an update.15:10
honghuixiao_I will udpate it in the following days15:10
* honghuixiao_ is xiaohhui15:10
mlavallelol15:10
*** andreykurilin has joined #openstack-meeting15:11
*** longxiongqiu has quit IRC15:11
* carl_baldwin didn't even notice honghuixiao_ 's changed nick15:11
*** andreykurilin1 has quit IRC15:11
carl_baldwinThanks, honghuixiao_15:11
*** reedip has joined #openstack-meeting15:11
*** aarefiev has quit IRC15:12
honghuixiao_It is just a temp name, might change back in another restart :)15:12
carl_baldwin#topic Deferred  IP Allocation on Port Update with Binding Info15:12
*** openstack changes topic to "Deferred IP Allocation on Port Update with Binding Info (Meeting topic: neutron_routed_networks)"15:12
*** duvarenkov_ has quit IRC15:12
carl_baldwinThis is where I'm working lately.15:12
*** e0ne has quit IRC15:12
carl_baldwinThe IPAM work has been approved15:12
carl_baldwin#link https://review.openstack.org/32063115:12
carl_baldwinThanks blogan and haleyb for the great reviews.15:12
*** rvasilets_ has quit IRC15:13
carl_baldwinI need to work on the Nova side to allow deferred allocation.15:13
carl_baldwinAnd, there is the bug with  ML215:13
*** garthb has joined #openstack-meeting15:13
*** korzen has quit IRC15:13
carl_baldwin#link https://review.openstack.org/#/c/32115215:13
*** anteaya has joined #openstack-meeting15:13
*** rossella_s has joined #openstack-meeting15:13
carl_baldwinhonghuixiao_: Sounds like you made some progress on this but I haven't had a chance to catch up.15:13
*** tonytan4ever has joined #openstack-meeting15:14
honghuixiao_I need to make some change to it, but basically, I can run the test case successfully locally15:14
saggiSorry to barge in but if there is someone here for the Smaug meeting we are in #openstack-meeting-3 . We were sure it's an even week so we assume the room will be ours. Sorry for interrupting.15:14
*** shaohe_feng has quit IRC15:15
carl_baldwinsaggi: No worries.  Thanks.15:15
*** reedip has quit IRC15:15
carl_baldwinhonghuixiao_: Cool, let me know when you have a patch set up.15:15
*** shaohe_feng has joined #openstack-meeting15:15
carl_baldwinhonghuixiao_: Great work.15:15
*** coolsvap has joined #openstack-meeting15:15
*** jmckind has quit IRC15:16
honghuixiao_I think the code is self-explanated, it is simple15:16
carl_baldwinSo, I think this is going well.15:16
*** vdrok-afk is now known as vdrok15:16
carl_baldwinI'm also going to get started on adding a flag to the port so that Nova can know when to allow deferred ip allocation.  I think that'll be easy once I get to it.15:17
*** rcernin has quit IRC15:17
*** sheel has joined #openstack-meeting15:17
carl_baldwinThat's all from me for this.  Anyone else?15:17
carl_baldwin#topic Schedule DHCP to Segments and Create DHCP ports15:17
*** openstack changes topic to "Schedule DHCP to Segments and Create DHCP ports (Meeting topic: neutron_routed_networks)"15:17
carl_baldwinblogan: You're up.15:17
bloganso i split the original review into 215:18
blogan#link https://review.openstack.org/#/c/326261/15:18
*** e0ne_ has quit IRC15:18
bloganthat's pretty straightforward15:18
blogan#link https://review.openstack.org/#/c/31193115:18
*** e0ne has joined #openstack-meeting15:18
bloganthat one is the one where the most discussion is going to happen, as it already has :)15:19
*** dmorita has joined #openstack-meeting15:19
honghuixiao_So, for a network with multiple segments, and no segment_subnet in it, we will only have one dhcp service for the network, right?(assuming config to 1)15:19
blogani need to read honghuixiao_'s latest comments more in depth, its morning for me :)15:19
*** edtubill has joined #openstack-meeting15:19
honghuixiao_yeah, that is me adding the comments, :P15:19
bloganhonghuixiao_: you mean multiple segments and no segment has a dhcp enabled subnet?15:20
honghuixiao_yes, just the orignal muti-provider network.15:20
carl_baldwinhonghuixiao_: That sounds about right.15:21
carl_baldwinWhat distinguishes a routed network is the subnets are attached to segments.  If DHCP enabled subnets are not attached to segments, then they should work as before.15:21
*** fnaval has joined #openstack-meeting15:21
honghuixiao_So, we should not delete the dhcp port in the segment automatically. Because that will cause the dhcp service unusable for the network.15:22
*** cloudtrainme has joined #openstack-meeting15:22
bloganit'll make it unusable just for that segment15:22
blogana dhcp port should be created per segment15:22
bloganan agent per segment15:22
*** jschwarz has quit IRC15:23
carl_baldwinhonghuixiao_: Is there a comment about this already in the review?  If so, do you have a link to it?15:23
honghuixiao_1 sec15:23
honghuixiao_https://review.openstack.org/#/c/317358/4/neutron/plugins/ml2/db.py15:24
*** ivc_ has joined #openstack-meeting15:24
honghuixiao_line 34015:24
bloganit's totally possible, and probable, that i'm uninformed on some of this15:24
carl_baldwin#link https://review.openstack.org/#/c/317358/4/neutron/plugins/ml2/db.py@34015:24
*** shaohe_feng has quit IRC15:25
honghuixiao_learned, the link can be used this way15:25
*** shaohe_feng has joined #openstack-meeting15:25
carl_baldwinhonghuixiao_: I don't know why they didn't use the standard HTML anchor (e.g. #L340)15:26
* mlavalle also just learned this15:26
*** coolsvap has quit IRC15:26
*** links has quit IRC15:26
bloganso segment should be able to be deleted if there is only the dhcp port bound to it correct?15:26
*** weshay has joined #openstack-meeting15:27
honghuixiao_I think the that is the result of discussion in previous mail list15:27
bloganhonghuixiao_: and your concern is that there is only one dhcp port per network?15:27
honghuixiao_yes, that is the original logic15:27
*** annemccormick has quit IRC15:28
honghuixiao_And it is what I see when debug it15:28
carl_baldwinI think we might need to consider what kind of network it is (routed or not)15:28
*** sdake has joined #openstack-meeting15:28
*** hongbin has left #openstack-meeting15:28
honghuixiao_so a routed network, is the one with subnets associated with segments, right?15:28
bloganhonghuixiao_: if each segment gets its own dhcp port would that solve the problem? i thought that already happens, but now you have me doubting myself :)15:28
carl_baldwinhonghuixiao_: Right, that is the distinguisher.15:28
*** yuval_ has joined #openstack-meeting15:29
*** annemccormick has joined #openstack-meeting15:29
*** dmorita has quit IRC15:29
carl_baldwinblogan: I think what you're saying is right *if* the network is a routed network.15:29
*** yuval has quit IRC15:29
*** yuval_ is now known as yuval15:29
blogancarl_baldwin: yes15:29
carl_baldwinBut, if this code is also handling L2 adjacent networks, then it might need to be a little bit smarter.15:30
carl_baldwinI'd like to give the review a little more thought though before I'm sure.15:30
*** coolsvap has joined #openstack-meeting15:30
blogancarl_baldwin: what do you mean?15:30
*** dneary has quit IRC15:31
*** xinwu has joined #openstack-meeting15:31
*** ljxiash has quit IRC15:32
carl_baldwinblogan: I'm not sure this code can assume it is working with a routed network.15:32
carl_baldwinblogan: If it isn't, and that DHCP port is the only one serving a multi-segmented network, it might be bad to delete it.15:32
*** cdub has quit IRC15:32
*** reedip has joined #openstack-meeting15:32
carl_baldwinhonghuixiao_: ^ Is this kind of what you're thinking?15:32
honghuixiao_yes,15:32
mlavallethat makes sense15:32
*** sarob has joined #openstack-meeting15:33
blogancarl_baldwin: it should work the same if there are no segments15:33
blogani mean the same as before15:33
carl_baldwinblogan: Segments couldn't be deleted before.15:33
honghuixiao_yeah, we open the gate to operate segments now...15:34
bloganah15:34
reedipsorry , some problem with my IRC, gets connection intermittently15:34
*** singhj has joined #openstack-meeting15:34
*** Swami has joined #openstack-meeting15:34
*** Swami_ has joined #openstack-meeting15:34
carl_baldwinWe have to be careful because we're adding the capability to add / delete segments for both routed networks and L2 adjacent networks.15:34
*** reedip has quit IRC15:35
carl_baldwinhonghuixiao_: Is it okay if we provide feedback on that review a bit later?15:35
honghuixiao_sure,15:35
*** shaohe_feng has quit IRC15:35
carl_baldwinI, for one, would like to let it sink in a little and then comment.15:35
bloganokay i think i see where the problem might be, ill need to run through some testing of this to get a better grasp on it15:35
carl_baldwinhonghuixiao_: Thanks for bringing it up.  It will be good to think this through.15:36
blogan+115:36
honghuixiao_:)15:36
carl_baldwinblogan: honghuixiao_ : Anything else on DHCP?15:36
blogannope15:36
carl_baldwinblogan: Thanks for updating the etherpad, that will be very helpful.15:36
honghuixiao_I also leave a comment in the review, but I think it is OK to go on there15:36
manjeetsetherpad link please ?15:37
carl_baldwinmanjeets: ^^^ It is the first link in the meeting.15:37
carl_baldwin#link https://etherpad.openstack.org/p/routed-provider-networks-notes15:37
*** sarob has quit IRC15:37
*** lifeless has quit IRC15:37
manjeetsthanks carl_baldwin:15:37
carl_baldwinmanjeets: glad to help15:37
carl_baldwin#topic Integration with Nova Scheduler15:38
*** openstack changes topic to "Integration with Nova Scheduler (Meeting topic: neutron_routed_networks)"15:38
carl_baldwinI should've announced that the spec was merged!15:38
*** shaohe_feng has joined #openstack-meeting15:38
carl_baldwinmlavalle: Thanks for all of your help on that.15:38
mlavalleglad to help :-)15:38
blogangood job!15:38
carl_baldwinWe have a few dependencies.  Any way we can help there?15:39
mlavallethe challenge was not to miss the boat for Newton15:39
mlavalleThe focus shifts now from specs to tracking code15:39
mlavalleI am tracking the new placement api15:40
mlavalle#link https://review.openstack.org/#/c/293104/15:40
carl_baldwinmlavalle: Are there some gerrit topics that we could link to the etherpad.15:40
*** jmckind has joined #openstack-meeting15:41
*** mickeys has quit IRC15:41
mlavalleYes I will add them15:41
mlavalleessentially, 2 topics15:41
mlavalle#link https://review.openstack.org/#/q/topic:bp/generic-resource-pools15:41
*** hashar is now known as hasharAway15:41
mlavalleThis is for the generic resource pools15:42
*** longxiongqiu has joined #openstack-meeting15:42
mlavalleand the changes to allocate_for_instance:15:42
mlavalle#link https://review.openstack.org/#/q/topic:bp/prep-for-network-aware-scheduling,n,z15:42
*** sacharya has joined #openstack-meeting15:42
mlavallelast check, johnthetubaguy hasn't posted any code yet for this one15:42
carl_baldwinmlavalle: Excellent.  Let's stay on top of those.  I'll try to work them in to my review routine.15:42
mlavalleYes, we can help with reviews15:43
mlavalleand I have offered to johnthetubaguy to help with code if he thinks he needs it15:43
johnthetubaguyyeah, I hope to start on that ASAP15:44
mlavalleIn the meantime, as soon as I have the vagrant multinode test environment ready, I will strat playing with the code that is in gerrit15:44
*** mtanino has joined #openstack-meeting15:44
*** xyang has quit IRC15:44
carl_baldwinmlavalle: Sounds like a good plan.15:44
*** ssalagame has joined #openstack-meeting15:45
carl_baldwinmlavalle: johnthetubaguy:  Anything else for discussion?15:45
mlavallenot from me15:45
*** rbartal has quit IRC15:45
johnthetubaguynot from me either really15:45
*** shaohe_feng has quit IRC15:45
carl_baldwinThanks!15:45
carl_baldwin#topic L2 Adjacency Extension15:45
*** openstack changes topic to "L2 Adjacency Extension (Meeting topic: neutron_routed_networks)"15:45
carl_baldwinreedip doesn't seem to be around.  I'll ping him out of band.15:46
carl_baldwin#topic Enable Create / Delete of Segments on Existing Network15:46
*** openstack changes topic to "Enable Create / Delete of Segments on Existing Network (Meeting topic: neutron_routed_networks)"15:46
*** shaohe_feng has joined #openstack-meeting15:46
mlavallehe pushed a revision to his patchset15:46
carl_baldwin#undo15:47
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x7fe2376b8cd0>15:47
carl_baldwinmlavalle: He did?15:47
mlavalleyeah15:47
mlavallegive me sec15:47
*** sacharya has quit IRC15:47
carl_baldwinI guess I've already reviewed it so I didn't think it was new.  But, it has been in the last week.15:47
*** xyang has joined #openstack-meeting15:48
carl_baldwin#topic Enable Create / Delete of Segments on Existing Network15:48
*** openstack changes topic to "Enable Create / Delete of Segments on Existing Network (Meeting topic: neutron_routed_networks)"15:48
carl_baldwinhonghuixiao_: We've already started in to this a bit.  Anything else?15:49
honghuixiao_just need more reviews to it15:49
honghuixiao_https://review.openstack.org/#/c/31735815:49
*** lifeless has joined #openstack-meeting15:49
*** anilvenkata has joined #openstack-meeting15:49
honghuixiao_Then nothing else15:49
*** xyang has quit IRC15:50
*** gampel has left #openstack-meeting15:50
*** bharath has joined #openstack-meeting15:51
carl_baldwinhonghuixiao_: ack and thank you.15:51
*** ihrachys has quit IRC15:51
carl_baldwin#topic Client15:51
*** openstack changes topic to "Client (Meeting topic: neutron_routed_networks)"15:51
*** reedip has joined #openstack-meeting15:51
*** longxiongqiu has quit IRC15:52
carl_baldwinrtheis: Anything need attention?15:52
rtheishi15:52
rtheisI merged a fix to the OSC client for network segments15:52
rtheisI would like to get to create/delete later this week15:53
rtheisand look at associating subnets to segments15:53
*** andreas_s has quit IRC15:53
*** ygbo has quit IRC15:53
rtheisthat's all for now15:53
*** sripriya_ has joined #openstack-meeting15:53
carl_baldwinrtheis: Thanks, I am trying to watch the etherpad, keep it up to date as things change.15:54
*** tung_doan has joined #openstack-meeting15:54
carl_baldwin#topic OVN plugin15:54
*** openstack changes topic to "OVN plugin (Meeting topic: neutron_routed_networks)"15:54
*** Swami_ has quit IRC15:54
*** manikanta_ has joined #openstack-meeting15:54
carl_baldwinAnything to discuss here?15:54
*** Swami has quit IRC15:54
rtheisOVN is now ML2 driver as of Friday15:54
carl_baldwinAwesome!15:54
rtheisI'm working on some ML2 related fixes and enhancements now.15:54
rtheisand https://review.openstack.org/#/c/302623/ is out for review...lots of activity on it15:55
*** leeantho has joined #openstack-meeting15:55
*** reedip has quit IRC15:55
honghuixiao_yeah, that is for geting the segment_host_maping for ovn now. Kyle is helping push the code forward15:55
*** absubram has joined #openstack-meeting15:55
*** shaohe_feng has quit IRC15:56
carl_baldwinThanks, mestery !15:56
mesteryyw carl_baldwin :)15:56
mesteryThough see comments on that patch honghuixiao_ ....15:56
mesteryregXboi brough up an issue15:56
*** shaohe_feng has joined #openstack-meeting15:56
carl_baldwintime check, we're almost done.15:57
carl_baldwinAnything else needs attention here?15:57
carl_baldwin#topic Router External Gateways on Routed Networks15:58
*** openstack changes topic to "Router External Gateways on Routed Networks (Meeting topic: neutron_routed_networks)"15:58
*** armax has joined #openstack-meeting15:58
carl_baldwinjohn-davidge has shown some interest in looking in to this.15:58
john-davidgeYeah, it would be good to get some eyes back on #link https://review.openstack.org/#/c/300207 and the thread on the ML15:58
john-davidgewe have a dependency on that spec going ahead15:58
*** santoshk has joined #openstack-meeting15:59
carl_baldwinYeah, that thread kind of died.  Do you have a link to it?15:59
*** bharath is now known as tbh15:59
john-davidgei resurrected it a couple hours ago, but let me dig up the link15:59
carl_baldwinjohn-davidge: I need to get caught up on the mailing list today.15:59
*** rossella_s has quit IRC15:59
*** KanagarajM has joined #openstack-meeting16:00
carl_baldwinWe're out of time.16:00
carl_baldwinThanks!16:00
carl_baldwin#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
john-davidgehttp://lists.openstack.org/pipermail/openstack-dev/2016-May/096302.html16:00
openstackMeeting ended Tue Jun  7 16:00:17 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_routed_networks/2016/neutron_routed_networks.2016-06-07-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_routed_networks/2016/neutron_routed_networks.2016-06-07-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_routed_networks/2016/neutron_routed_networks.2016-06-07-15.00.log.html16:00
carl_baldwinjohn-davidge: Thanks.16:00
honghuixiao_Bye~16:00
*** s3wong has joined #openstack-meeting16:00
*** mickeys has joined #openstack-meeting16:00
*** bobh has joined #openstack-meeting16:01
*** redixin1 has joined #openstack-meeting16:01
*** redixin1 has left #openstack-meeting16:01
*** longxiongqiu has joined #openstack-meeting16:01
*** gokrokve has joined #openstack-meeting16:02
sridhar_ram#startmeeting tacker16:03
openstackMeeting started Tue Jun  7 16:03:13 2016 UTC and is due to finish in 60 minutes.  The chair is sridhar_ram. Information about MeetBot at http://wiki.debian.org/MeetBot.16:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:03
*** openstack changes topic to " (Meeting topic: tacker)"16:03
openstackThe meeting name has been set to 'tacker'16:03
sridhar_ram#topic Roll Call16:03
KanagarajMhi16:03
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"16:03
bobho/16:03
manikanta_o/16:03
*** sacharya has joined #openstack-meeting16:03
sripriya_o/16:04
vishwanathjo/16:04
santoshkhi16:04
tbho/16:04
s3wongo/16:04
sridhar_ramalright, lets start...16:04
*** amuller has left #openstack-meeting16:04
sridhar_ram#topic Agenda16:04
*** openstack changes topic to "Agenda (Meeting topic: tacker)"16:04
sridhar_ram#link https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_June_7.2C_201616:04
sridhar_ramanything else to discuss beyond this ?16:05
sridhar_rammoving on..16:05
sridhar_ram#topic Annoucements16:05
*** openstack changes topic to "Annoucements (Meeting topic: tacker)"16:05
sridhar_ram#link http://lists.openstack.org/pipermail/openstack-dev/2016-June/096774.html16:06
*** shaohe_feng has quit IRC16:06
sridhar_ramwe have new core team member for tacker (main) project..16:06
sridhar_ramtbh: welcome to the team!16:06
*** kebray has joined #openstack-meeting16:06
sripriya_tbh: congrats!16:06
vishwanathjtbh congrats and well deserved16:06
manikanta_Congrats tbh ...Way to go !!16:06
KanagarajMcongrats tbh !16:06
*** shaohe_feng has joined #openstack-meeting16:06
*** sridharg has quit IRC16:06
santoshkcongrats tbh16:07
*** jankihc has joined #openstack-meeting16:07
sridhar_ramtbh: thanks for all your contributions so far... we have many interesting things to accomplish !16:07
bobhtbh: congrats and welcome!16:07
sridhar_ramnext...16:07
tbhthanks all16:07
tbhsridhar_ram, sure16:07
*** saggi has quit IRC16:08
sridhar_ramTacker now has support for Reno based releasenotes management16:08
sridhar_ramPlease follow the usage guide at...16:08
sridhar_ram#link http://docs.openstack.org/developer/reno/usage.html16:08
*** yuval has quit IRC16:09
*** oshidoshi has quit IRC16:09
*** iyamahat has quit IRC16:09
sridhar_ram... please use it to capture new features , deprecation notes or any other heads up to our user community16:09
*** xinwu has quit IRC16:09
sridhar_ramthis is a best practice to pick early in our dev16:10
sridhar_rammoving on...16:10
sridhar_ram#topic Monitoring & Scaling specs16:10
*** openstack changes topic to "Monitoring & Scaling specs (Meeting topic: tacker)"16:10
*** longxiongqiu has quit IRC16:11
sripriya_sridhar_ram: should reno be updated whenever we implement a new feature?16:11
sridhar_ramsripriya_: yes16:11
*** yamahata has quit IRC16:11
KanagarajMsridhar_ram, for scaling, i think, spec is alomst ready16:11
sripriya_sridhar_ram: ok16:12
tung_doanhi all. sorry i am late16:12
KanagarajMsridhar_ram, only two of your comments to be decided16:12
*** armax has quit IRC16:12
sridhar_ramKanagarajM: okay.. i think finalizing the TOSCA parser is important..16:12
KanagarajMsridhar_ram, technically I think PATCH should be16:12
*** paul-carlton1 has joined #openstack-meeting16:12
KanagarajMsridhar_ram, yeah, on TOSCA side, saw a patch on the support for sclaing policy16:13
*** reedip has joined #openstack-meeting16:13
KanagarajMsridhar_ram, should we add that in the spec?16:13
*** tesseract has quit IRC16:13
sridhar_rambobh: any thoughts on navigating the tosca-parser dependency for scaling ?16:14
bobhsridhar_ram: if the tosca-parser side can be completed soon it can be released in the next t-p point load and pulled in16:14
*** Apoorva has joined #openstack-meeting16:14
bobhsridhar_ram: is there also a heat-translator dependency?16:14
sridhar_ramKanagarajM: bobh: do we have dep on both tosca-parser and heat-translator for our scaling needs ?16:14
*** matrohon has quit IRC16:14
sridhar_rambobh: hehe.. had the same question to you :)16:15
*** Apoorva has quit IRC16:15
*** reedip has quit IRC16:15
KanagarajMsridhar_ram, I saw a patch on the heat-translator, and i believe tosca parser alaready support the ppolicy16:15
bobhsridhar_ram: I should probably know that I guess.....16:15
sridhar_ramKanagarajM: bobh: first order of deps IMO is tosca-parser.. my understanding is heat-translator can be "managed" ?16:16
bobhsridhar_ram: I'll try to track down whats in flight on both t-p and h-t16:16
*** enriquetaso has joined #openstack-meeting16:16
*** armax has joined #openstack-meeting16:16
*** shaohe_feng has quit IRC16:16
sridhar_rambobh: that would help...!16:16
*** Apoorva has joined #openstack-meeting16:16
bobhsridhar_ram: that's one word for it :-)16:16
*** shaohe_feng has joined #openstack-meeting16:16
KanagarajMbobh, thanks. that would help !16:16
*** dprince has quit IRC16:17
sridhar_ramKanagarajM: bobh: an important deviation i see is on the way the monitoring trigger policy is captured...16:17
KanagarajMsridhar_ram, how about the specs update for the reference to that heat-translaotr pathc16:17
*** nisha_ has quit IRC16:17
*** nisha_ has joined #openstack-meeting16:18
sridhar_ramfyi, please review https://review.openstack.org/#/c/302636/ .. this is still open in heat-translator16:18
tung_doansridhar_ram: i would like to discuss monitoring policy in TOSCA template.16:19
*** asettle has quit IRC16:19
tung_doansridhar_ram:monitoring policy is embedded in Scaling poplicy16:19
KanagarajMsridhar_ram, you mean supporting to monitor across vdus.16:19
*** ajmiller_ has joined #openstack-meeting16:19
sridhar_ramKanagarajM: sure.. lets update the spec mention that we will leverage tosca-parser & heat-translator as appropriate...16:19
KanagarajMsridhar_ram, ok. thats better.16:20
sridhar_rammoving to tung_doan monitoring spec...16:20
sridhar_ramtung_doan: my understanding is you proposed a separate "tosca.policies.monitoring" node type for mon policy..16:21
tung_doansridhar_ram:right16:21
sridhar_ramtung_doan: IMO, this is a very good approach16:21
sridhar_ramthis mon policy can have 1 or more "targets" VDUs..16:22
KanagarajMyeah, that would really helps to monitor across vdus.16:22
sridhar_ramwe also have a separate "tosca.policies.scaling" node type specifically for scaling policy...16:22
*** ajmiller has quit IRC16:23
tung_doansridhar_ram: actually it is also related to some actions16:23
sridhar_ramfor auto-scaling the "tosca.policies.monitoring" should have an action triggering "tosca.policies.scaling"16:23
sridhar_ramtung_doan: agree...16:24
*** amotoki has quit IRC16:24
sridhar_ramtung_doan: KanagarajM: i don't mean to rat hole on this too much... once we have enough clarity we should wrap up the specs and move on to the implementation..16:24
tung_doansridhar_ram: that is my concern16:24
sridhar_rambobh: tung_doan: KanagarajM : what do you think ?16:24
*** armax has quit IRC16:25
*** salv-orl_ has joined #openstack-meeting16:25
sridhar_rambobh: can you help to make sure the TOSCA semantics gel well across these two specs ?16:26
KanagarajMsridhar_ram, yeah, that s good idea. I will push the patch on the spec today for scaling and start the impl by this week16:26
*** shaohe_feng has quit IRC16:26
bobhsridhar_ram: only concern is I'm on vacation for a week starting tomorrow16:26
bobhsridhar_ram: I can try to do a quick review tonight but I'll be offline after that until next Wednesday16:27
*** shaohe_feng has joined #openstack-meeting16:27
tung_doan<sridhar_ram>: IMHO, separating them is not difficult work.16:27
sridhar_rambobh: thanks16:27
*** salv-orlando has quit IRC16:27
KanagarajMbobh, by then you will have many patches to look at ;)16:27
sridhar_ramtung_doan: that's good.. it is better keep them independent in the beginning so that patchsets can keep landing16:28
bobhKanagarajM: :-)16:29
tung_doansridhar_ram: sure. I will follow Santosh's spec as well16:29
*** xinwu has joined #openstack-meeting16:29
sridhar_ramtung_doan: KanagarajM : how is callbacks (webhooks) from Ceilometer and Heat-Scaling going to be handled ?16:30
*** prashantD__ has joined #openstack-meeting16:30
sridhar_ramwill tacker-service expose a webservice to receive these call backs ?16:31
*** reedip has joined #openstack-meeting16:31
KanagarajMsridhar_ram, tung_doan i think that is the way to go .... as ceilometer needs to inform the tacker16:31
*** longxiongqiu has joined #openstack-meeting16:31
tung_doansridhar_ram: yes. it should be defined in TOSCA template.16:31
*** reedip has quit IRC16:32
tung_doansridhar_ram: we need to provide a webservice. it is way to go16:32
sridhar_ramtung_doan: this piece is not related to the TOSCA template16:32
*** iyamahat has joined #openstack-meeting16:33
*** saggi has joined #openstack-meeting16:33
*** coolsvap has quit IRC16:33
sridhar_ramtung_doan: it will be good to describe this webservice in your spec... as it is technically an external facing endpoint16:34
*** coolsvap has joined #openstack-meeting16:34
tung_doanKanagarajM: "ceilometer needs to inform the tacker". What do you mean?16:34
sridhar_ramwe also need to secure this channel16:34
*** jungleboyj has quit IRC16:34
*** yamahata has joined #openstack-meeting16:35
*** e0ne has quit IRC16:35
tung_doanKanagarajM: you mean we can use directly Ceilometer?16:35
tung_doansridhar_ram: OK///16:35
*** anteaya has quit IRC16:35
KanagarajMtung_doan, when ceilometer evaluate the alarm, it needs to invoke the tacker,16:35
*** e0ne has joined #openstack-meeting16:35
*** bcafarel has quit IRC16:36
*** longxiongqiu has quit IRC16:36
*** mriedem_afk is now known as mriedem16:36
sridhar_ramthe way i parse this .. tosca.policies.monitoring --will translate--> HOT Ceilometer resource with webhook pointing back to tacker callback webservice16:36
*** shaohe_feng has quit IRC16:37
KanagarajMsridhar_ram, +116:37
tung_doansridhar_ram: +116:37
sridhar_ramalright, we are the same page :)16:37
sridhar_ramKanagarajM: now for scaling..16:37
*** jlanoux has quit IRC16:37
*** shaohe_feng has joined #openstack-meeting16:37
*** anteaya has joined #openstack-meeting16:38
sridhar_ram.. how do you plan to keep Tacker in the loop when a scaling VM is created or deleted ?16:38
*** tellesnobrega_af is now known as tellesnobrega16:38
*** nadya has joined #openstack-meeting16:38
KanagarajMsridhar_ram, corresponding events will be generated and capture the scaling related details16:39
sridhar_ramlike i mentioned in the spec, we need to support custom scaling workflows like giving the ip addr of the new scaled out VM to the control plan vm16:39
sridhar_ramKanagarajM: again, this will need a tacker webservice to handle the callbacks ?16:39
sridhar_ramKanagarajM: is it a webhook like callback or more like a RPC event ?16:39
KanagarajMsridhar_ram, webhook is a like a callback. a16:40
*** nadya_ has joined #openstack-meeting16:40
*** e0ne has quit IRC16:40
KanagarajMsridhar_ram, i think once scling is completed, we could pull the new VMs IP from the heat16:40
sridhar_ramKanagarajM: cool, i guess then we need to have *one* tacker webservice across these two specs...16:40
*** cdub has joined #openstack-meeting16:40
*** tonytan4ever has quit IRC16:41
*** e0ne has joined #openstack-meeting16:41
*** cwolferh has quit IRC16:41
tung_doansridhar_ram: once integrating scaling and monitoring.. one tacker webservice is possible16:41
KanagarajMsridhar_ram, from heat to make it async , i.e or we could listen for scaling event from heat and then pull the IP of new VM16:41
*** nadya has quit IRC16:42
sridhar_ramKanagarajM: tung_doan: I will be great if you both can co-ordinate on this common webservice piece that be leveraged to handle both ceilometer and scaling callbacks16:42
KanagarajMsridhar_ram, for scaling , imo, callbacks does not help16:42
tung_doansridhar_ram: it is truly goo d way to gi16:42
tung_doan*gi: go16:42
sridhar_ramKanagarajM: cool, can you please desc few sentences on this in your spec16:42
KanagarajMsridhar_ram, instead, we should depends on the heat spec16:42
*** SumitNaiksatam has quit IRC16:43
KanagarajMsridhar_ram, yeah sure.16:43
sridhar_ramKanagarajM: what you mean by "depends on heat spec" ?16:43
*** haukebruno has quit IRC16:43
KanagarajMsridhar_ram, sorry typo, heat events16:43
sridhar_ramKanagarajM: okay... make sense..16:44
sridhar_ramalright, i think we are in the last legs of this specs.. i'd love to see both of these specs wrapped up by this week16:45
*** cloudtrainme has quit IRC16:45
sridhar_ramteam - please do your last call reviews!16:45
sridhar_rammoving on...16:45
sridhar_ram#topic NSD Scoping16:45
*** openstack changes topic to "NSD Scoping (Meeting topic: tacker)"16:45
sridhar_ramdkushawa: are you here ?16:45
*** johncallaghan has joined #openstack-meeting16:46
*** shaohe_feng has quit IRC16:47
sridhar_ramI don't see him here.. lets move this topic to next week16:47
*** jungleboyj has joined #openstack-meeting16:47
sridhar_ram#topic Midcycle Meetup16:47
*** openstack changes topic to "Midcycle Meetup (Meeting topic: tacker)"16:47
*** Kiall has quit IRC16:47
*** Swami has joined #openstack-meeting16:47
*** shaohe_feng has joined #openstack-meeting16:47
johncallaghantopic: appeco_wg16:48
*** Swami has quit IRC16:48
*** nadya_ has quit IRC16:48
*** reedip has joined #openstack-meeting16:48
sridhar_ramI'd like to do a quick poll here if the wider team is interested in participating in a Tacker midcycle meetup16:48
*** Swami has joined #openstack-meeting16:48
sridhar_ram... our team spread across diff TZs..16:48
*** anilvenkata has quit IRC16:49
sridhar_ramhow many of you would prefer a 2-day virtual midcycle meetup ?16:49
*** e0ne has quit IRC16:49
*** saggi has quit IRC16:49
*** nadya has joined #openstack-meeting16:49
sripriya_sridhar_ram: +116:49
sridhar_ramsripriya_: thanks...16:50
s3wongsridhar_ram: virtual is good16:50
*** preisner has quit IRC16:50
*** johncallaghan has left #openstack-meeting16:50
bobhsridhar_ram: +116:50
*** Kiall has joined #openstack-meeting16:50
sridhar_rambobh: s3wong: thanks!16:50
*** marekd has joined #openstack-meeting16:50
sridhar_rami'll also send a doodle pool out to the ML to gauge the interest..16:51
*** iceyao has quit IRC16:51
sridhar_rammoving on...16:51
sridhar_ram#topic Open Discussion16:51
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"16:51
sridhar_ramany general things to discuss ?16:51
sridhar_rambugs, docs, gate jobs...16:52
sripriya_sridhar_ram: i had one update on a rfe i'm working16:52
sridhar_ramsripriya_: sure, go ahead16:52
KanagarajMsridhar_ram, sripriya_ bobh kindly have a look at events spec https://review.openstack.org/#/c/321370/16:52
*** dprince has joined #openstack-meeting16:53
*** sripriya has joined #openstack-meeting16:54
sripriyasridhar_ram: i'm planning to remove the whole <class name>-<file path-><uuid>-<vdu name> thing for heat stack names16:54
sridhar_ramKanagarajM: will do16:54
*** sarob has joined #openstack-meeting16:54
bobhKanagarajM: will do16:54
*** mlavalle has left #openstack-meeting16:54
*** sripriya__ has joined #openstack-meeting16:55
sripriya__sridhar_ram: this will reflect on the vdu name as well16:55
*** reedip has quit IRC16:55
sridhar_ramsripriya: is there a way we can preserve <first 6 chars in uuid>-<vdu-name> ?16:55
sripriya__sridhar_ram: which uuid ar eyou referrign to?16:55
sripriya__*are you referring16:55
sridhar_ramthe current uuid .. which is the vnf uuid16:56
sripriya__sridhar_ram: is that serving any purporse now that we will make vnf names unique?16:56
sridhar_rami'm suggesting something similar to "git log --oneline"16:56
*** mohnish__ has quit IRC16:57
*** ivar-lazzaro has joined #openstack-meeting16:57
*** shaohe_feng has quit IRC16:57
*** sripriya_ has quit IRC16:57
sripriya__sridhar_ram: what does that do?16:58
sridhar_rami was thinking removing is class-name and file-path makes perfect sense.. but i do see value in a portion of uuid+vdu-name for debugging purpose16:58
*** sarob has quit IRC16:58
* sridhar_ram 2mins left16:58
*** shaohe_feng has joined #openstack-meeting16:58
*** sripriya has quit IRC16:58
sripriya__sridhar_ram: the vdu names inside vnf are also unique resource names16:58
*** ijw has joined #openstack-meeting16:59
sridhar_ramlooks we are out of time for today..16:59
*** Leom_ has quit IRC16:59
sridhar_ramsripriya__: let's take this offline ?16:59
sripriya__sridhar_ram: i will be pushing a gerrit patch soon and we can discuss on that. i just wanted to give a heads up to the broader team on the refactoring of stack and nova namrs16:59
sripriya__names*16:59
*** ivar-lazzaro has quit IRC16:59
sridhar_ramsripriya__: thanks for the heads up17:00
*** ivar-lazzaro has joined #openstack-meeting17:00
sridhar_ramthat's it folks..17:00
sridhar_rambye all17:00
sridhar_ram#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Tue Jun  7 17:00:18 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-06-07-16.03.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-06-07-16.03.txt17:00
*** bobh has quit IRC17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-06-07-16.03.log.html17:00
*** vishwanathj has quit IRC17:00
*** sripriya__ has left #openstack-meeting17:00
*** tbh has quit IRC17:00
*** lpetrut has quit IRC17:01
*** sarob has joined #openstack-meeting17:01
*** sarob has quit IRC17:01
*** jckasper has quit IRC17:01
*** gema has joined #openstack-meeting17:01
*** sarob has joined #openstack-meeting17:02
*** cwolferh has joined #openstack-meeting17:02
*** banix has joined #openstack-meeting17:03
*** nadya_ has joined #openstack-meeting17:03
*** nadya has quit IRC17:04
*** fzdarsky is now known as fzdarsky|afk17:04
*** ivc_ has quit IRC17:04
*** s3wong has quit IRC17:05
*** Apoorva_ has joined #openstack-meeting17:06
*** kebray has quit IRC17:07
*** eharney has quit IRC17:07
*** timothyb89 has quit IRC17:07
*** shaohe_feng has quit IRC17:07
*** nadya has joined #openstack-meeting17:08
*** nadya_ has quit IRC17:08
*** sarob has quit IRC17:08
*** Apoorva has quit IRC17:08
*** sarob has joined #openstack-meeting17:09
*** timothyb89 has joined #openstack-meeting17:09
*** merooney has quit IRC17:10
*** shaohe_feng has joined #openstack-meeting17:10
*** nadya_ has joined #openstack-meeting17:12
*** jckasper has joined #openstack-meeting17:12
*** reedip has joined #openstack-meeting17:12
*** nadya has quit IRC17:13
*** tonytan4ever has joined #openstack-meeting17:13
*** nadya_ has quit IRC17:14
*** reedip has quit IRC17:15
*** merooney has joined #openstack-meeting17:15
*** manikanta_ has quit IRC17:15
*** arvinc_ has joined #openstack-meeting17:16
*** arvinc_ has quit IRC17:16
*** shashank_hegde has joined #openstack-meeting17:16
*** paul-carlton1 has quit IRC17:16
*** jckasper has quit IRC17:16
*** arvinc_ has joined #openstack-meeting17:16
*** paul-carlton1 has joined #openstack-meeting17:17
*** shashank_hegde has quit IRC17:17
*** arvinc_ has quit IRC17:17
*** jankihc has quit IRC17:17
*** arvinc_ has joined #openstack-meeting17:17
*** shaohe_feng has quit IRC17:18
*** arvinc_ has quit IRC17:18
*** roxanaghe has joined #openstack-meeting17:18
*** shaohe_feng has joined #openstack-meeting17:18
*** arvinc_ has joined #openstack-meeting17:19
*** arvinc_ has quit IRC17:19
*** arvinc_ has joined #openstack-meeting17:20
*** arvinc_ has quit IRC17:20
*** arvinc_ has joined #openstack-meeting17:21
*** arvinc_ has quit IRC17:21
*** tung_doan has quit IRC17:22
*** arvinc_ has joined #openstack-meeting17:22
*** jckasper has joined #openstack-meeting17:22
*** arvinc_ has quit IRC17:22
*** ssalagame has quit IRC17:23
*** ssalagame has joined #openstack-meeting17:23
*** ssalagame has quit IRC17:23
*** amotoki has joined #openstack-meeting17:24
*** mriedem has quit IRC17:27
*** acoles is now known as acoles_17:27
*** mriedem has joined #openstack-meeting17:27
*** dmorita has joined #openstack-meeting17:28
*** shaohe_feng has quit IRC17:28
*** shaohe_feng has joined #openstack-meeting17:28
*** jmckind has quit IRC17:29
*** amotoki has quit IRC17:29
*** KanagarajM has quit IRC17:30
*** reedip has joined #openstack-meeting17:31
*** liamji has quit IRC17:32
*** cloudtrainme has joined #openstack-meeting17:32
*** reedip has quit IRC17:35
*** toscalix has quit IRC17:37
*** shaohe_feng has quit IRC17:38
*** cwolferh has quit IRC17:39
*** shaohe_feng has joined #openstack-meeting17:39
*** salv-orl_ has quit IRC17:41
*** salv-orlando has joined #openstack-meeting17:41
*** xyang has joined #openstack-meeting17:42
*** HeOS has quit IRC17:43
*** paul-carlton1 has quit IRC17:43
*** sambetts is now known as sambetts|afk17:44
*** tonytan4ever has quit IRC17:44
*** Sukhdev has joined #openstack-meeting17:46
*** amakarov has joined #openstack-meeting17:46
*** cwolferh has joined #openstack-meeting17:46
*** singhj has quit IRC17:47
*** Sukhdev has quit IRC17:48
*** shaohe_feng has quit IRC17:48
*** shaohe_feng has joined #openstack-meeting17:49
*** asettle has joined #openstack-meeting17:49
*** asettle has quit IRC17:49
*** asettle has joined #openstack-meeting17:49
*** shashank_hegde has joined #openstack-meeting17:52
*** priteau has joined #openstack-meeting17:52
*** reedip has joined #openstack-meeting17:52
*** cloudtrainme has quit IRC17:53
*** garthb_ has joined #openstack-meeting17:53
*** s3wong has joined #openstack-meeting17:53
*** garthb has quit IRC17:55
*** browne has joined #openstack-meeting17:55
*** reedip has quit IRC17:55
*** sudipto has quit IRC17:56
*** vishnoianil has quit IRC17:57
*** nk2527 has joined #openstack-meeting17:58
*** eharney has joined #openstack-meeting17:58
*** cwolferh has quit IRC17:58
*** rwsu has quit IRC17:58
*** shaohe_feng has quit IRC17:59
*** e0ne has joined #openstack-meeting17:59
*** shaohe_feng has joined #openstack-meeting18:00
*** annemccormick has quit IRC18:00
*** lhcheng has joined #openstack-meeting18:00
*** henrynash_ has joined #openstack-meeting18:00
bretonlets meet.18:00
samueldmqcourtesy ping to ajayaa, amakarov, ayoung, breton, browne, crinkle, claudiub, davechen, david8hu, dolphm, dstanek, edmondsw, gyee, henrynash, hogepodge, htruta, jamielennox, joesavak, jorge_munoz, knikolla, lbragstad, lhcheng, marekd, MaxPC, morgan, nkinder, notmorgan, raildo, rodrigods, rderose, roxanaghe, samleon, samueldmq, shaleh, stevemar, tjcocozz, tsymanczyk, topol, vivekd, wanghong, xek18:00
henrynash_meetint18:00
lbragstado/18:00
rodrigodso/18:00
browneo/18:00
*** jamielennox has joined #openstack-meeting18:00
dstaneko/18:00
roxanaghe\o18:00
lhchengo/18:00
rderoseo/18:00
*** annemccormick has joined #openstack-meeting18:00
bknudsonmeet()18:00
ayoungOYEZ OYEZ18:00
jamielennoxdo we have a stevemar this time?18:00
amakarovhi18:00
knikollahiiii o/18:01
samueldmqhi all, it's that time18:01
nk2527howdy18:01
notmorgano/18:01
ayoungsamueldmq, you running things this week?18:01
notmorgan\o18:01
notmorganayoung: he is18:01
topolo/18:01
samueldmqjamielennox: not sure, I agreed with him I will be running this time18:01
samueldmqayoung: ++18:01
jamielennoxsamueldmq: all yours then18:01
samueldmqthanks18:01
samueldmq#startmeeting keystone18:01
openstackMeeting started Tue Jun  7 18:01:55 2016 UTC and is due to finish in 60 minutes.  The chair is samueldmq. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** shaleh has joined #openstack-meeting18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:02
shaleh\o18:02
samueldmqwelcome everyone18:02
*** ivar-laz_ has joined #openstack-meeting18:02
nk2527o/18:02
*** otherwiseguy has quit IRC18:02
samueldmqwe have 4 topics to discuss today18:02
samueldmq#topic Mapping shadow users into projects and roles18:02
*** openstack changes topic to "Mapping shadow users into projects and roles (Meeting topic: keystone)"18:02
*** electrofelix has quit IRC18:02
samueldmqdolphm: o/18:02
notmorgansamueldmq: i have an open topic at the end to add18:02
notmorgansamueldmq: so just save me ~5m at the end pl18:02
notmorganz18:02
*** e0ne has quit IRC18:02
samueldmqnotmorgan: sure18:02
samueldmqis dolphm around ? otherwise we can just start with another topic and then circle back18:03
ayoungthis is autoprovisioning.18:03
dolphmyes18:03
ayoungWe've had a request for this for a long time18:03
samueldmqdolphm: nice, the floor is yours18:04
dolphm#link https://review.openstack.org/#/c/324055/18:04
dolphmso, this spec came directly out of the austin summit18:04
*** merooney has quit IRC18:04
dolphmthe gist is that it makes a lot of sense to do some basic provisioning of authorization-related things in mapping, especially for federation use cases18:05
dolphmsince we have a chicken & egg problem otherwise18:05
*** merooney has joined #openstack-meeting18:05
*** obondarev has quit IRC18:05
dolphmayoung's "Federated query APIs" specification has a pretty good illustration of that chicken & egg problem18:05
notmorgandolphm: imnsho +2.18:05
topoldolphm +++18:05
*** ivar-lazzaro has quit IRC18:06
notmorgan(imnsho = in my not so humble opinion)18:06
*** pvaneck has joined #openstack-meeting18:06
ayoungdolphm, question...is control of this going to be managed solely by the mapping file, or will we use an additional domain specific config to "gate" whether a projedct can be automatically created within a specific domain?18:06
*** paul-carlton1 has joined #openstack-meeting18:06
dolphmso, the solution here is basically to lazily provision things like projects and role assignments during the auth process - after a user has been authenticated, but before we give them a token for the first time18:06
*** ebalduf_ has joined #openstack-meeting18:06
rodrigodsayoung, there is a domain attribute18:06
dolphmso that token can actually be immediately useful, with a project, roles, and all18:06
*** nisha_ has quit IRC18:06
ayoungActually...I'd like to see a domain specific config value "allowed_idps" for mapping in general, and then autocreate is on top of that18:07
*** xyang has quit IRC18:07
*** neiljerram has joined #openstack-meeting18:07
notmorganayoung: that is a fair request.18:07
notmorganayoung: i think.18:07
dolphmayoung: as part of the spec, i'm envisioning mapping files to become a bit more domain-specific, if that makes sense. i think domain admins should be able to manage their own mapping files18:07
rodrigodsidps should be tied to domains since the beginning18:07
notmorgandolphm: ++18:07
ayoungnotmorgan, yeah, with the config options in the database, this is more practical, too18:07
rodrigodsthey are domains18:07
henrynash_dolphm: so (as you know) I support this (although have a follow up concern whcih is next on teh agenda, but that doesn’t stop the conceptual idea here)18:07
ayoungdolphm, 10000% yes18:08
dolphmso, there's a domain ID attribute in the mapping which is the key to that notion18:08
notmorganhenrynash_: and i have a very strong view on that. but i'll hold until your topic.18:08
henrynash_notmorgan: cool18:08
shalehso where is the disagreement here?18:08
dstanekdolphm: could this eventually solve the "i project 1234 here and when i federation there i also get project 1234"?18:08
samueldmqshaleh: I don't think there is one :)18:08
ayoungdolphm, I think that if we say "create the domain, create the domain specific config, specify idps for domain, allow auto provisioning"  in that order we are on the right track18:08
*** manjeets has left #openstack-meeting18:09
*** shaohe_feng has quit IRC18:09
shalehare we doing on demand creation to save DB space or something?18:09
*** jorge_munoz has joined #openstack-meeting18:09
dolphmshaleh: this spec is new since last meeting, so i was just looking for an opportunity to socialize it, and answer any questions18:09
shalehdolphm: k18:09
lbragstadi'm on board18:09
ayoungthen the mapping can be uploaded safely, as it can only map to specific domains18:09
notmorganshaleh: on demand or pre-create doesn't really change the nature of the spec.18:09
dolphmshaleh: to save space versus pre-provisioning a bunch of projects you may not need?18:10
shalehnotmorgan: agreed. I was asking about the detail18:10
ayounghenrynash_, you are the Domain specific config guru.  Does what I say make sense?  is it practical?18:10
lbragstadand also to get around the weird ux of having a user hit keystone (uselessly) in order to assign them stuff18:10
samueldmqwould it be a good idea to let admins explicitly set when a project is expected to exist ?18:10
samueldmqin the mapping ? ^ dolphm18:10
shalehsamueldmq: expand on that18:11
dolphmsamueldmq: i replied to your comment in the review18:11
rodrigodssamueldmq, good point18:11
dolphmsamueldmq: L14118:11
*** neiljerram has quit IRC18:11
* samueldmq nods, looking18:11
*** reedip has joined #openstack-meeting18:11
*** gyee has joined #openstack-meeting18:11
shalehon first read this sounds reasonable. I need to think about it some.18:11
ayoungdolphm, I'll respond to the review request with these suggestions.18:11
dolphmsamueldmq: rodrigods: the suggestion implies a lot of complexity without a well defined use case to support it18:12
henrynash_ayoung: probably…but need to dig in deeper18:12
*** shaohe_feng has joined #openstack-meeting18:12
*** santoshk has left #openstack-meeting18:12
dolphmshaleh: cool - you'll have plenty of time to digest :)18:12
rodrigodsdolphm, good point too in the reply :)18:12
*** Leo_ has joined #openstack-meeting18:12
*** Leo_ has quit IRC18:12
rodrigodsdolphm, did you consider HMT?18:12
rodrigodsi mean... the mapping is flat18:12
*** Leo_ has joined #openstack-meeting18:12
shalehrodrigods: nah, who wants that :-)18:12
dolphmrodrigods: it's a list of projects, and each project object could have a parent ID, description, etc -- the other things a project requires18:13
samueldmqdolphm: default would be true, but if it's set to create=False and it exists... mapping invalid ?18:13
rodrigodsdolphm, ++18:13
*** cwolferh has joined #openstack-meeting18:13
samueldmqdolphm: that doesn't work, I agree that just adds complexity18:13
jamielennoxstill reading but in general i like it18:13
*** jichen has joined #openstack-meeting18:13
rodrigodsdolphm, and... inherited roles? the same?18:13
dolphmjamielennox: i believe it's what you were describing on the mailing list18:13
dolphmin the thread with amakarov18:14
jamielennoxdolphm: whilst i need to think about the domain admins managing this - why does that need to be part of this spec??18:14
notmorgandolphm: this seems to cover a chunk of the provisioning concerns. so i am a fan.18:14
jamielennoxdolphm: yea, but i assumed it would be more difficult than this :)18:14
dolphmrodrigods: i imagine inherited roles could be expressed as an attribute on the role object in the project definition? so for example, inherited=True (or whatever the attribute is called in the role assignment API) on L144 for example18:14
rodrigodsdolphm, yeah, makes sense18:15
rodrigodsdolphm, suggest just to add a note about them there18:15
*** reedip has quit IRC18:15
*** doug-fis_ has joined #openstack-meeting18:15
*** reedip has joined #openstack-meeting18:15
dolphmjamielennox: good question. the constraint is not a hard requirement, but it simplifies the mapping definition (otherwise, you'd have to specify a bunch of domain IDs in the mapping, for each project and all)18:15
*** reedip has quit IRC18:16
dolphmjamielennox: doing it once at the top seems to solve everyone's use cases that i've talked to, and simplifies the security model quite a bit18:16
notmorgandolphm: ++18:16
dolphmnotmorgan: a chunk? where would you want to take it next / what does it not cover?18:16
samueldmqnice, any other concerns on this spec ? I think we seem to have an agreement on it18:17
dolphmnotmorgan: i assume you agree this is MVP for the idea18:17
notmorgandolphm: yes.18:17
notmorgandolphm: and can be built on.18:17
ayounghenrynash_, I'd be OK with, instead of them being domain specific config options, they go on the domain object in the resource backend.18:17
*** piet_ has joined #openstack-meeting18:17
* topol felt very MVP to me as well18:17
notmorgandolphm: i don't see anything clearly needing to be added now. a good starting place18:17
dolphmnotmorgan: ack18:17
dolphmsamueldmq: thanks, we can move on18:17
samueldmqdolphm: perfect18:17
notmorgandolphm: and like i said +2 :)18:17
samueldmqso please review the spec, and let's move on18:17
henrynash_ayoung: but could you write policy rule to control management?18:17
jamielennoxdolphm: yea, in general i would think it simplifies most peoples case and helps the domain admin model, but there is some additional validation i think you would want to see like if you specify a domain id for a whole mapping then you shouldn't be able to specify a different domain id for any project or role18:17
ayounghenrynash_, I don't think you need to.18:18
samueldmq#topic Should shadowing users be optional?18:18
*** openstack changes topic to "Should shadowing users be optional? (Meeting topic: keystone)"18:18
jamielennoxdolphm: to the point where it should almost be a different spec18:18
samueldmqhenrynash_: o/18:18
* notmorgan grabs soapbox.18:18
henrynash_ah oops18:18
ayounghenrynash_, it could be enforced by the rules engine at mapping time, or even confirmed when the mapping is uploaded18:18
henrynash_ayoung: later, i’;m up18:18
*** doug-fish has quit IRC18:18
jamielennoxalso where is that domain name immutable flag18:18
ayoungjamielennox, that is a global value18:19
dolphmjamielennox: agree, and i forgot about that flag18:19
notmorganok, please coninute this convo on the spec18:19
henrynash_so my concern here is about whether we NEED to have shadow users…what If I don’t want local direct assigments…and have multidatcentres….don;t I know have another bigs table to replicate?18:19
dolphmnotmorgan: ++18:19
*** toddjohn has joined #openstack-meeting18:19
samueldmqnotmorgan: ++18:19
*** shaohe_feng has quit IRC18:19
notmorganhenrynash_: yes. we do.18:19
*** BroNeed has joined #openstack-meeting18:19
samueldmqlet's focus on the current topic18:19
ayounghenrynash_, would that be on a per Idp basis?18:19
notmorganhenrynash_: this should not be optional18:19
BroNeedWhat is this place?18:19
henrynash_notmorgan: becasue....18:19
notmorganthe data doesn't move that fast, it simplifies out internal code paths AND security model18:20
*** shaohe_feng has joined #openstack-meeting18:20
notmorganand it prevents us from many many extra edge cases18:20
BroNeedAND you say?18:20
rderosenotmorgan: ++18:20
dstanekhenrynash_: replication shouldn't be terrible unless you are adding/removing users at lightning speed18:20
dolphmhenrynash_: so... your use case is that you have separate clouds that should not have replicated identity data?18:20
dolphmhenrynash_: why are you replicating in the first place?18:20
notmorganhave multiple code paths, security models, etc all means we're battling a lot of possible paths of maintenance and optimisation18:20
BroNeedmany many you say?18:20
henrynash_dolphm: I am assuming federation, but replication projects and assignments18:20
jamielennoxyea, i don't think shadow users should be optional18:21
BroNeedoptimization u say?18:21
*** prashantD_ has joined #openstack-meeting18:21
BroNeedshadow users you say?18:21
notmorganfungi, jeblair, mordred, might need a kick here in this channel (cc anyone who is op)18:21
jamielennoxthere are too many things that will hopefully rely upon it like direct role assignment18:21
*** ssalagame has joined #openstack-meeting18:21
shalehcan we find a way to prevent the need to replicate?18:21
ayoungshaleh, no,  I don't think so18:21
henrynash_so why do we need direct role assignment if we have this mapping faciity we sjust discussed?18:22
ayoungshaleh, actuallllly18:22
ayoungyes18:22
*** cdub has quit IRC18:22
notmorganfungi, jeblair, mordred: will ping if it becomes really important. (thnx)18:22
samueldmqnotmorgan: thanks18:22
BroNeedDo any of you know what are you are talkibg about or arw you just using fancy words with no meaning?18:22
ayounghenrynash_, so, what if we forced the id_mapping approach on shadow users18:22
dolphmBroNeed: are you here for an actual discussion, or are you just spamming the channel?18:22
*** john-davidge has quit IRC18:22
BroNeedYes18:22
BroNeedI asked what is this place18:22
rderosehenrynash_: mapping relies on direct role assignments18:22
henrynash_(don’t ecnourage it)18:22
ayoungdolphm, pretty sure it is a bot18:23
dolphmayoung: agree18:23
BroNeedLol no18:23
BroNeedI am no bot.18:23
dolphmBroNeed: please don't disrupt the meeting unless you have something to contribute18:23
BroNeedJust asking what this placw is18:23
*** lhcheng has quit IRC18:23
shaleh^topic18:23
BroNeedYes mam18:23
dstanekayoung: you think we can do away with the replication?18:23
ayoungdstanek, yep18:23
*** pvaneck has quit IRC18:24
ayoungif the userid is deterministic18:24
ayoungit will be the same in all places18:24
*** ChanServ sets mode: +b BroNeed!*@*18:24
*** BroNeed was kicked by ChanServ (Banned: spamming is off-topic)18:24
ayoungfor LDAP idMapping we do18:24
dolphmhenrynash_: i don't see the data being created by shadow users to be particularly burdensome for replication18:24
henrynash_redrose: if the mapping is going to create an assignment (whcih is what we just dsicused), why couldn’t it use teh epemeral user_id created by the mappoing18:24
shalehconsidering all the work Fernet puts into limiting replication, I'd rather not add more18:24
*** prashantD__ has quit IRC18:24
ayoungsha256{userid, domainid}18:24
ayoungwe'd make Federation use idp instead18:24
dolphmhenrynash_: as usual, there will be bursts of writes when new users arrive, but that's true today anyway18:24
ayoungsha256{userid, idpid}18:24
ayoungwith the userid value the value from the assertion18:24
jamielennoxuser id being deterministic doesn't get you things like role assignments that were created18:24
notmorganjamielennox: ++18:25
notmorganbut role assignments could be replicated without too much worry --18:25
jamielennoxnotmorgan: so could user ids18:25
notmorganjamielennox: sure.18:25
notmorganjamielennox: i'd argue you'd probably replicate it all.18:25
*** amotoki has joined #openstack-meeting18:26
notmorganbut i see this as non-optional, is my only point, not digging into replicate-or-not-to-replicate18:26
dolphmshaleh: it's also the difference between rather static data (users, roles, projects), and highly disposable data (tokens)18:26
ayoungjamielennox, but if there are explicit role assignments, those would have to be replicated anyway.  henrynash_ 's complaint is that his setup does not have direct role assignments in the normal case18:26
henrynash_i’d just seems really odd that we have federation, then we require keystone to replaciate around shadow versions of this same info18:26
dstaneki'm a firm -1 here because it just makes things too complicated.18:26
shalehdolphm: understood18:26
dstanekat what scale is user replication problematic?18:26
notmorgandstanek: -1 on optional?18:26
dstanekyes18:26
notmorgandstanek: or -1 on required?18:26
notmorgandstanek: :P18:26
dstanekit needs to be required18:26
lbragstadyou'd have to be creating thousands of users a second, no18:26
lbragstad?18:27
notmorganok cool.18:27
dstaneklbragstad: maybe?18:27
notmorganreplication of even a few thousand rows is not that much18:27
notmorganfwiw.18:27
shalehlbragstad: new group onboarding, M&A, etc.18:27
dstanekis this an actual problem that we can quantify and solve or is it theoretical right now?18:27
jamielennoxayoung: but therefore what you can have keystones without replicating data? what about projects etc?18:27
* notmorgan steps off the soapbox.18:27
* notmorgan shoves the soapbox back under the desk18:27
dolphmdstanek: ++18:28
gyeeyou can also configure selective replication right? doesn't have to be all tables18:28
samueldmqdstanek: good question18:28
ayoungjamielennox, it would work like this:18:28
notmorgangyee: you can.18:28
rderosehenrynash_: yeah, it's possible, but I think the goal is to eventually treat federated users like any other users and not have these special edge cases (ephemeral).18:28
*** paul-carlton1 has quit IRC18:28
notmorgansamueldmq: 30m in (fyi)18:28
topoldo we have use cases for all these fancy replication bells and whistles?18:28
gyeenotmorgan, then we don't need to do anything special on the keystone side18:29
ayoungdon't replicate shadow user, but replicate role assignment./  User goes from instance 1, where they have a shadow user record, to instance 2 where they do now.  Shadow user record is created, and mataches id in role assignment18:29
notmorgangyee: exactly18:29
samueldmqnotmorgan: thnaks, we're changing topics now18:29
notmorgantopol: replication is deployer choices and out of scope of keystone imo18:29
samueldmqso, we don't seem to have a 100% agreement on this right now, henrynash_ please post comments on the spec and continue discussion there18:29
samueldmqwe need to move on18:29
ayoungdolphm, do you have any strong objection to the userid generation scheme I proposed?18:29
henrynash_ayoung: assuming you don’t have something liek service users in your default domain, which you probably do18:29
shalehayoung: that sounds like what we all discussed happening in Tokyo18:29
*** shaohe_feng has quit IRC18:29
bknudsonwe're likely going to need to figure out a way to replicate users, projects, etc., so that we can share tokens between datacenters. database replication doesn't work when the code is at different levels.18:29
ayounghenrynash_, will still work18:29
jamielennoxyea, -1 on making this optional, you already replicate a lot of data to make this work, users is not a big deal and simplifies our code a lot18:30
samueldmqplease continue in dolphm's spec18:30
samueldmq#topic SAML2 Middleware18:30
*** openstack changes topic to "SAML2 Middleware (Meeting topic: keystone)"18:30
henrynash_ok, thx18:30
samueldmqdstanek: o/18:30
*** prashantD__ has joined #openstack-meeting18:30
*** amotoki has quit IRC18:30
gyeebknudson, don't share, trust :-)18:30
*** shaohe_feng has joined #openstack-meeting18:30
dstaneksamueldmq: o/18:30
dstanek#link https://github.com/dstanek/keystone-saml2-experiment/tree/testshib-hacking (experimental hacking)18:30
dstanekthis is something i've been working on and wanted to give an update and collect some input18:30
topolnotmorgan yes those bells and whistles were scaring me a little18:30
dstaneki need the IdPs that a Keystone SP can use to be highly dynamic and controlled by an API18:31
dstaneki want to limit Apache restarts18:31
lbragstad++18:31
dstaneki want to limit the need to use Keystone's API to manipulate thirdparty configuration18:31
dstaneki want centralized control over the IdP configuration (read: database not distributed XML files)18:31
dstanekso...i started working on middleware to replace mod_shib/shibboleth - that is mostly backed by pysaml218:31
*** e0ne has joined #openstack-meeting18:32
topoldstanek very cool!18:32
shalehdstanek: less dependence on apache too???18:32
ayoungdstanek, could you tackle this in mod_auth_mellon instead18:32
ayoungplease18:32
*** gokrokve has quit IRC18:32
dolphmayoung: in?18:32
gyeedstanek, we went over this awhile back18:32
ayoungthe world needs this. It is not a Keystone specific requirement18:32
gyeeI remember we hit a few critical issues18:32
dstanekright now i can almost do a round trip using testship (will be done by the end of the day)18:32
*** baoli_ has quit IRC18:32
ayoungdolphm, anything that needs SSO needs to be able to mananage the Idps18:33
gyee1) how to prevent replay attack18:33
dstaneki did lots of experiments with shib and mellon, but not a lot of good results18:33
*** xyang has joined #openstack-meeting18:33
dstanekayoung: i will provide for the world!18:33
dolphmgyee: a replay of what against what?18:33
*** reedip has joined #openstack-meeting18:33
samueldmqdstanek: this is a great idea18:33
ayoungdstanek, we have a team that works on that kind of stuff.18:33
gyeedolphm, submit the saml doc twice18:33
*** prashantD_ has quit IRC18:33
dstanekgyee: that's not terrible. you just need a list of open requests.18:33
gyeelike managing the relay state18:34
*** lpetrut has joined #openstack-meeting18:34
*** Ravikiran_K has quit IRC18:34
dstaneksamueldmq: not my idea :-) i'm just hacking on it18:34
ayoungits a python specific approach.  I have real concerns with doing crypto heavy operations in python18:34
ayoungbut, that is not the real issue18:34
*** Apoorva_ has quit IRC18:34
samueldmqdstanek: hacking on it in keystone is your great idea ;)18:34
dstanekgyee: right now my demo code does this with a process cache, but in a real impl i would have to use the database18:34
dolphmgyee: so after breaking the SSL connection between the client and keystone, you want to prevent a third party from sending that same request?18:34
jamielennoxgyee: i don't remember there being a nonce or anything in saml2? is there?18:35
ayoungthe real issue is that having SAML handled by a module for Apache that needs config file changes is too static18:35
*** Apoorva has joined #openstack-meeting18:35
*** stajkowski has joined #openstack-meeting18:35
dstanekdolphm: yes. because clients are stupid and may log saml or whatever18:35
*** reedip has quit IRC18:35
gyeethere's a relay state management in shibd18:35
jamielennoxgyee: there's a validity period on the assertion, but nothing that the server does specifically for replays18:35
gyeeit also includes trust originator18:35
*** pvaneck has joined #openstack-meeting18:35
*** yohoffman has joined #openstack-meeting18:35
gyeelike the entire request URL is part of the signature itself18:35
ayoungI don't want to get Keystone into the world of  general SAML support unless we are going to use SAML to replace tokens18:36
bknudsonis this a new library or does it live in keystone?18:36
gyeeI remember we were having trouble with it when fronted by a proxy18:36
bknudsonprobably has to live in keystone if it's got a db18:36
dolphmgyee: how does shib / mellon solve that problem?18:36
dstanekbknudson: i would like it to live in keystone since i think it would be generally useful18:36
gyeedolphm, it validates what's in the relay state against the caller18:37
ayoungthis is the wrong community for this dstanek .  SAML is only one of several Federation protocols.  We've had more requests for openicd lately than SAML18:37
gyeelike the request URL, time stamp, etc18:37
dstanekayoung: do you mean writing code to parse and interpret saml or writing code that uses a library to do that?18:37
samueldmqdstanek: is there a spec up for review so we can review/use for discussions ?18:37
gyeeif we implement relay state in middleware that would be awesomer18:37
ayoungdstanek, even the second part18:37
ayoungits not a keystone specific problem18:38
dstanekayoung: we already do this for k2k - this just brings it full circle18:38
ayoungdstanek, I know. and it was a mistake then18:38
bknudsonis restarting apache that big of a deal? you spin up a new instance and shut down the old one.18:38
rodrigodsk2k is crippled saml18:38
*** lhcheng has joined #openstack-meeting18:38
dolphmayoung: the keystone specific problem is managing one or more trusted IdP's per domain via the API as a domain admin without having to be the cloud operator, etc, right?18:38
dstaneksamueldmq: no, but there can be18:38
dolphmbknudson: as a domain admin, i don't have the ability to do that18:38
samueldmqdstanek: I think that would be useful18:39
jamielennoxalso k2k is an saml idp which is an easier problem18:39
dstaneksamueldmq: couldn't design it before digging in18:39
ayoungdolphm, even that is a general problem, we just solve it as an abstraction layer for the rest of openstack18:39
dstanekjamielennox: an SP is actually pretty easy too18:39
*** Wundrlnd has joined #openstack-meeting18:39
gyeejust use PKI tokens :-)18:39
ayoungwell...ok you mean domain as an Openstack specific object, so yes you are right18:39
samueldmqdstanek: got it18:39
dolphmayoung: yes, that's what i meant18:39
dstanekthe hardest thing is dealing with shibboleth18:39
*** shaohe_feng has quit IRC18:40
gyeeain't kidding18:40
*** bobh has joined #openstack-meeting18:40
ayoungdstanek, I am working on a POC with a different IdP right now18:40
rodrigodsdstanek, not worried about implementing saml but regarding the whole security of such authenticator involves18:40
ayoungI've worked with both Ipsilon and Keycloak18:40
rodrigodsgyee gave few examples18:40
ayoungand the mod_mellon part is being extracted by jdennis18:40
samueldmq#action dstanek to post a spec on SAML2 Middleware up to review18:40
*** shaohe_feng has joined #openstack-meeting18:40
gyeerodrigods, PKI token are S/MIME doc essentially18:40
dolphmayoung: extracted to where?18:40
WundrlndThis has got to be the gayest nerd network tranny shit I have ever stumbled across I am going back to Dalnet where the pussy is.18:41
gyeeS/MIME's being around since the beginning of time18:41
* notmorgan doesn't have a strong opinion on this front.18:41
dstanekbknudson: the other issue is that it's easy for me to crash shib and i wouldn't want domain admins to be able to do that18:41
ayoungthere is registration code for mod_mellon to talk to Ipsilon as part of the ipsilon proejct, and he's done a standa lone for keycloak.18:41
*** Wundrlnd has quit IRC18:41
ayoungI'll link18:41
*** coolsvap has quit IRC18:41
dstanekrodrigods: is it any worse than what we already do?18:41
*** nkinder has joined #openstack-meeting18:41
ayounghttps://github.com/jdennis/keycloak-httpd-client-install18:41
dstanekdoes anyone have an hardcore "this is stupid" or "i hate you" type of feedback?18:42
dstanekotherwise i'm just going to proceed18:42
ayoungnkinder, dstanek is proposing moving the SAML processing to a middleware inside of keystone18:42
gyeeno, middleware is a great idea!18:42
gyeeif we get it to cover the bases18:42
ayoungdstanek, I have a hard "please don't do it in keystone" feedback18:42
jamielennoxdstanek: so first thing is i don't see any management urls, but i assume they are an easy problem after getting the authenticator to work18:42
*** jdennis has joined #openstack-meeting18:42
rodrigodsthe problem is to know the whole base upfront18:42
ayoungI don't think you are  stupid and I don't hate you, dstanek18:42
dstaneki've started looking into shibboleth's dynamic federations, but it seems to be too complicated for actual use18:42
rderosedstanek: i think you should proceed, it can just be another option18:42
rodrigodsgyee, ^18:42
notmorganjust keep in mind python sucks at crypto work18:43
dolphmayoung: do you object to the domain-admin use case for managing federations, or to the implementation?18:43
samueldmqso ayoung and dstanek (and others) please keep in the discussion in -keystone ?18:43
jamielennoxdstanek: i've in the past said to implement it elsewhere and i know you've looked into it so if you really have to do it in middleware i'd prefer it to live upstream in keystone18:43
ayoungdolphm, implementation18:43
dstanekayoung: not moving...this is all new stuff for a SP18:43
notmorganwell, likely will get better if we get some JIT added and/or asyncio+uvloop18:43
samueldmqit should have a general agreement so dstanek can proceed with the spec/implementation18:43
samueldmqwe gotta move18:43
notmorganbut just keep that in mind.18:43
samueldmq#topic Performance testing patches up for review18:43
*** openstack changes topic to "Performance testing patches up for review (Meeting topic: keystone)"18:43
jamielennoxdstanek: but mostly i'd want to make sure this becomes something in contrib that people _can_ use, i don't think we should ever recommend it as the default18:43
samueldmqlbragstad: o/18:43
dolphmayoung: i'm not clear on how an alternative implementation would satisfy the domain-admin-federation-manager use case, then18:44
lbragstadso performance has been coming up ... a lt18:44
dstanekjamielennox: ++18:44
lbragstadlot*18:44
ayoungdolphm, I want a general solution to SSO.  I want to have mod_mellon do exactly what dstanek is proposing anyway18:44
dolphmayoung: or at least, i'm not clear on what that alternative should look like18:44
notmorgansamueldmq: can you timebox this at 10 min instead of 15 [for my last minute topic]18:44
lbragstadi wanted to try and get something written that would allow us to test performance the same way18:44
lbragstadthat way we can get recreateable results18:44
notmorganlbragstad: ++ and i like it18:44
lbragstadand hopefully tie it into reviews18:44
lbragstadwith something like leaving commit18:44
lbragstadcomment*18:44
samueldmqnotmorgan: sure, I will do that and leave your 5 mins at the end18:44
rodrigodslbragstad, nice18:44
samueldmqlbragstad: you have 10 mins :)18:45
lbragstadlike "recheck" but "check performance"18:45
gyeerodrigods, bases as in managing and validating relay states18:45
ayoungdolphm, so, accepting a new IdP is an operator level operation.  Lets assume we can make it far more managable than shibboleth does today.  jdennis 's tool is for that exact problem in keuycloak18:45
notmorganlbragstad: 3rd party CI can trigger on any event18:45
ayoungand is based on the ipsilon approach18:45
lbragstadso I start contributing what i have to one of my own repos https://github.com/lbragstad/keystone-performance18:45
*** xinwu has quit IRC18:45
ayoungthe two really should be merged into a single tool that knows about multiple Idps, but the amount of Idp specific logic is high right now18:45
lbragstad^ that will go through and set up keystone using openstack ansible18:45
shalehdstanek: even if it goes no where official, the code is worth exploring.18:45
ayoungso...that is something that can be done by ansible fairly simply18:45
notmorganayoung: we need to continue on, this convo will need to continue in -keystone or on a spec18:45
ayoungnotmorgan, ++18:46
notmorganayoung: sorry. just keeping things moving.18:46
shalehdstanek: maybe it gets folded into another project, maybe it becomes a project. Still of value.18:46
jamielennoxlbragstad: so is this 3rd party or going to be on infra resources?18:46
lbragstadthe performance tests are extremely basic but I wanted to throw it out there so that people can play wiht it18:46
samueldmqnotmorgan: ayoung ++18:46
jamielennoxlbragstad: also i think it's beneficial18:46
lbragstadjamielennox i might be able to get some bare metal resources18:46
notmorganjamielennox: it can't be in infra unless there is hardware dedicated to it.18:46
henrynash_lbragstad: it’s a GREAT start18:46
bknudsonlbragstad: this is going to be really useful18:46
henrynash_lbragstad: and we really neeed this18:46
notmorganjamielennox: it needs to be consistent hardware that isn't affected by bad neighbor/different provider18:46
bknudsonwe'll likely wind up implementing something like this for our cloud, too.18:47
samueldmqlbragstad: thanks for the initiative, and for sharing it18:47
jamielennoxnotmorgan: ++18:47
*** Sukhdev has joined #openstack-meeting18:47
gyeeare we talking about rally gate?18:47
notmorganjamielennox: or it needs to be run at least in consistent providers on consistent flavors18:47
lbragstadso please play wiht it, open bugs against the plays, etc..18:47
notmorgangyee: no.18:47
bknudsonand hopefully we can share the tests, although every deployment is going to be different18:47
*** vishnoianil has joined #openstack-meeting18:47
notmorgangyee: rally has failed to meet what lbragstad is proposing.18:47
jamielennoxnotmorgan: mostly i was just thinking it's a lot easier problem if we just consider it a 3rd party job18:47
lbragstadmy next step is to write something that would kick of infra per patch18:47
shalehlbragstad: thanks for sharing the work you have18:47
notmorganjamielennox: i would like this ot be 3rd party tbh18:47
rodrigodsit needs dedicated hardware18:48
lbragstadyep18:48
lbragstadit is18:48
notmorganjamielennox: i am happy to ask -infra about taking it on, but right now they aren't (afaik) in  aplace for supporting this18:48
lbragstadit's hosted on rackspace dedicated bare metal servers18:48
rodrigodsit needs to run lots of times, to get "real world" reports18:48
notmorganonce infra-cloud is in a place it might be a topic worth considering with them.18:48
amakarovlbragstad, why not to use rally for that? The only issue - it uses devstack18:48
lbragstadexactly18:49
jamielennoxnotmorgan: no, i'm thinking 3rd party is good, particularly if we have hardware in rax and rax people to fix it18:49
notmorganbut there are lots of questions about running real bare-metal resources that i wouldn't want to lump on them until thye have a clear plan/story for it18:49
notmorganjamielennox: ++18:49
bknudsonif we can get rally to help out then we should take that18:49
bknudsonbut as it is our needs are pretty simple.18:49
gyeetrouble with performance tests is really environment isolation and consistency18:49
bknudsonnot that hard to write a script to validate a token18:49
gyeesomething we can't do well with VMs18:49
notmorgani'm fine with rally being used. i wont support it being a "rally" job18:49
* topol trust me henrynash really needs this performance stuff :-)18:49
henrynash_topol: :-)18:49
notmorgani support it being "use appropriate technology" behind the scenes, regardless of what it is18:50
notmorganamakarov: ^18:50
jamielennoxlbragstad: have you got code somewhere for what will be run?18:50
samueldmqtopol: henrynash_ :)18:50
dolphmgyee: hence, lbragstad is going straight to dedicated bare metal18:50
*** shaohe_feng has quit IRC18:50
gyeedolphm, no argument here18:50
jamielennoxlbragstad: what scope do you expect? just token validate?18:50
bknudsonjamielennox: https://github.com/lbragstad/keystone-performance/blob/master/validate.py18:50
amakarovnotmorgan, why not?18:50
notmorganjamielennox: token issue, token validate18:50
*** ivar-laz_ has quit IRC18:50
notmorganamakarov: because it doesn't matter what tech is used.18:50
*** bobh has quit IRC18:50
notmorganamakarov: i will be very against calling it a "rally gate"18:50
notmorganamakarov: let the team decide what they'll use18:51
jamielennoxbknudson: doh - thanks18:51
*** adiantum has joined #openstack-meeting18:51
*** shaohe_feng has joined #openstack-meeting18:51
notmorganit can be rally.18:51
*** ivar-lazzaro has joined #openstack-meeting18:51
notmorganit can be something else18:51
amakarovnotmorgan, understood18:51
lbragstadjamielennox it does authenticate 1000 times and valiate 1000 times18:51
notmorganbut if you lock it in as rally, i'm -218:51
*** xinwu has joined #openstack-meeting18:51
samueldmqnotmorgan: ++18:51
*** xinwu has quit IRC18:51
lbragstadjamielennox https://github.com/lbragstad/keystone-performance18:51
notmorganamakarov: and rally very well might be the right tool :)18:51
*** mbound has quit IRC18:51
samueldmqlbragstad: nice, so basically make people aware of the performance tests18:51
samueldmqlbragstad: you done ?18:51
*** shaleh has quit IRC18:51
lbragstadsamueldmq yep18:51
samueldmqlbragstad: thanks18:52
notmorganlbragstad: make sure you get a proper 3rd party CI account18:52
bknudsonso one thing that's going to be tricky is dealing with larger config changes... e.g., switch from uuid to fernet for example18:52
lbragstadall, ping me if you have questions18:52
samueldmq#topic Open Discussion18:52
*** openstack changes topic to "Open Discussion (Meeting topic: keystone)"18:52
dolphmbknudson: ++18:52
jamielennoxlbragstad: and somewhere to push results to, for pretty graphs?18:52
samueldmqnotmorgan: o/18:52
notmorganok18:52
notmorganso18:52
notmorgangoing to harp on review numbers again18:52
dolphmbknudson: i think the configuration that we use for testing needs to be "opinionated" for exactly that reason18:52
dolphmbknudson: testing sqlite is not useful, for example18:52
notmorgan#link http://paste.openstack.org/show/508737/18:52
gyeeso I am a bit concerned about this patch https://review.openstack.org/#/c/309146/18:52
lbragstaddolphm so OSA is what I chose but I'm open to other opinions18:52
gyeeit will change the behavior of fernet tokens18:53
notmorganthere have been 59 business days or so since RC1 of mitaka18:53
*** shaleh has joined #openstack-meeting18:53
notmorganit is not unreasonable that all cores should be at 1-review-per-business day (newton)18:53
samueldmqplease let's focus on notmorgan's topic, just to keep moving :)18:53
notmorganpeople are doing better.18:53
notmorganbut still calling to action - review.18:53
notmorgani will be administratively abandoning old reviews with no movement very soon.18:54
notmorganbut please review.18:54
gyeesir yes sir18:54
notmorganeveryone should review. -1s, +1s, +0 all matters to us and helps18:54
topolyep. will do18:54
samueldmqnotmorgan: ++18:54
dolphm#goteam18:55
samueldmqcores and non-cores are more than welcome to review18:55
* dstanek hangs his head in shame18:55
*** reedip has joined #openstack-meeting18:55
* dolphm joins dstanek18:55
*** reedip has quit IRC18:55
notmorganI've been working with steve to keep an eye for potential new cores as well18:55
rodrigodsfor non-cores, review is the best way to learn18:55
shalehdstanek: can't code all day :-)18:55
dstanekshaleh: challenge accepted18:55
* topol topol cant believe gyee reviewed more than he did.... 18:55
notmorganalso if you CANT remain core, or don't want to, you can step down and be fast-tracked back in if you have time again18:55
dolphmshaleh: what is the alternate universe you speak of18:55
shalehdolphm: married life :-)18:55
gyeetopol, the day ain't over yet18:56
notmorganjust keep it in mind that we want you to be able to contribute18:56
notmorganand feel successful at it18:56
notmorganreviews, code, etc18:56
dstanekshaleh: "sorry honey, but i really need to code right now."18:56
*** jmckind has joined #openstack-meeting18:56
samueldmqnotmorgan: ++18:56
dolphmmemorize it!18:56
notmorganwhat ever makes it easiest for you to succeed.18:57
*** prometheanfire has joined #openstack-meeting18:57
samueldmq#action everyone to review/contribute code!18:57
*** olaph has joined #openstack-meeting18:57
notmorgancore, non-core, etc, that is what we (core team, PTL, etc) is for.18:57
notmorganheck even bug triage18:57
gyeedolphm, its MEMOIZE18:57
notmorgans/heck even/also18:57
*** asingh has quit IRC18:57
*** xyang has quit IRC18:58
samueldmqnotmorgan: keystone says: challenge accepted!18:58
notmorgani'm using stackalytics Newton cycle18:58
notmorganand http://www.timeanddate.com/date/workdays.html to figure out the number of "business days"18:58
amakarovgyee, memoize also innvolves "invalidate" and "expire" :)18:58
gyeethere will be a draw at the end of the cycle for a free trip to barcelona18:58
gyeedrawing18:58
*** xyang has joined #openstack-meeting18:58
notmorganusually it's not quantity over quality, but when the numbers are this low... quantity matters too :)18:58
rodrigodsbrazil has far less working days fwiw :)18:58
rodrigodslots of holidays18:59
samueldmqso, we're running out of time18:59
notmorganrodrigods: still 59 reviews since March 16th isn't unreasonable :P18:59
shalehrodrigods: even more time for review then :-)18:59
samueldmqthanks everyone, it was a pleasure to ru nthis meeting :)18:59
notmorganrodrigods: in newton18:59
*** hasharAway is now known as hashar18:59
*** mriedem1 has joined #openstack-meeting18:59
bknudsondon't forget to vote.18:59
notmorgan(across all keystone repos)18:59
topolgood job samuelmdq18:59
samueldmq#endmeeting18:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:59
* notmorgan is done18:59
openstackMeeting ended Tue Jun  7 18:59:33 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
shalehbknudson: ++18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-06-07-18.01.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-06-07-18.01.txt18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-06-07-18.01.log.html18:59
samueldmqthanks18:59
rderosesamueldmq: nice job :)18:59
*** ihrachys has joined #openstack-meeting18:59
*** shaleh has left #openstack-meeting18:59
prometheanfire:D18:59
samueldmqfungi: infra folks: floor is yours18:59
fungithanks!19:00
prometheanfireianw: you here for this?19:00
*** jamielennox has left #openstack-meeting19:00
fungiinfra team, resemble!19:00
ianwprometheanfire: yes19:00
Zara\o/19:00
yolandao/19:00
*** doug-fis_ has quit IRC19:00
*** shaohe_feng has quit IRC19:00
mmedvedeo/19:00
*** lhcheng has left #openstack-meeting19:00
pleia2o/19:00
jeblairhowdy19:00
SotKo/19:00
*** Shrews has joined #openstack-meeting19:00
notmorganfungi: hey i resemble that remark19:00
*** mriedem has quit IRC19:01
fungiexcellent!19:01
bkeroo/19:01
Shrewso/19:01
olapho/19:01
stajkowskio/19:01
*** doug-fish has joined #openstack-meeting19:01
*** doug-fish has quit IRC19:01
*** Rockyg has joined #openstack-meeting19:01
*** nadeem has joined #openstack-meeting19:01
*** henrynash_ has quit IRC19:01
docaedoo/19:01
hashar19:01
*** shaohe_feng has joined #openstack-meeting19:01
hashar(merely lurking)19:01
*** doug-fish has joined #openstack-meeting19:01
cbadero/19:02
*** piet_ has quit IRC19:02
*** prashantD_ has joined #openstack-meeting19:02
fungitoday's topics are brought to you by pleia2, mtreinish, pabelanger, Zara, and the letter 319:03
prometheanfireo/19:03
fungi#startmeeting infra19:03
openstackMeeting started Tue Jun  7 19:03:45 2016 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: infra)"19:03
openstackThe meeting name has been set to 'infra'19:03
anteayathe letter 3 again19:03
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:03
mtreinishfungi: ?19:03
anteayawhen does the number 3 get a turn19:04
fungianteaya: i'm unoriginal19:04
mtreinishoh, I did put something on the agenda last week19:04
mtreinishI forgot19:04
fungimtreinish: excellent, someone else with an even worse memory than mine! ;)19:04
fungi#topic Announcements19:04
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:04
fungi#info Tentative late-cycle joint Infra/QA get together to be held September 19-21 (CW38) in at SAP offices in Walldorf, DE19:04
*** jungleboyj has quit IRC19:04
fungicheck with mkoderer and oomichi for details19:04
fungi#link https://wiki.openstack.org/wiki/Sprints/QAInfraNewtonSprint19:04
fungialso we did a couple project renames last week. i screwed one of them up by turning puppet back on a few minutes early19:05
mordredo/19:05
*** sheel has quit IRC19:05
fungithere is now a dead "openstack-infra/ansible-puppet" repo with just a readme in it, in read-only mode. we can safely purge that from disk before the next gerrit reindex19:05
*** AJaeger has joined #openstack-meeting19:05
*** pabelanger has joined #openstack-meeting19:05
pabelangero/19:05
* AJaeger apolizies for beeing late19:06
*** amrith is now known as _amrith_19:06
* fungi hangs head in shame19:06
fungimoving on19:06
fungi#topic Actions from last meeting19:06
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:06
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-05-31-19.03.html19:06
*** prashantD__ has quit IRC19:06
fungipleia2 set up filtering to direct provider account contact address(es) into a high priority inbox19:06
fungii saw that happened!19:06
pleia2so, filtering!19:06
fungifiltering!!!19:06
pleia2I went ahead and filed a ton of old mail too19:06
* fungi us using up his exclamation mark quota for the month)19:06
*** singhj has joined #openstack-meeting19:06
zaroo/19:06
notmorganfungi: uhm. they have a quota for that? :(19:07
pleia2so it should be in the proper place, not everything is in filtering rules though since some companies send from multiple addresses and domains19:07
* bkero lets fungi borrow some of his exclamation mark quota. He's clearly making better use of them.19:07
pleia2I figure I'll log in and tweak over time, the work I did last week was a massive first pass over 25k messages19:07
*** galstrom is now known as galstrom_zzz19:07
*** sarob has quit IRC19:08
pleia2do we have imap or pop access to this?19:08
anteayapleia2: thank you for this19:08
*** galstrom_zzz is now known as galstrom19:08
fungisupposedly imap works19:08
pleia2I couldn't find docs for it through their help menus, so I wasn't sure19:08
fungii think it might be the same thing that i use to read my jeremy@openstack.org address, so sync up with me after the meeting and we'll see if similar parameters work19:09
pleia2but I think the next step is figuring out how we stay on top of this email, logging in all the time is not something I can really do, but I could drop it in my imap client where I monitor other addresses19:09
pleia2fungi: cool, thanks19:09
*** Leo_ has quit IRC19:09
fungiyeah, same, if it works over imap and there's a high=priority inbox then i'll just check it from mutt as continuously as my other addresses19:09
fungier, high-priority19:10
* pleia2 nods19:10
fungifungi start an ml thread revisiting current priority efforts list19:10
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2016-June/004374.html19:10
fungifollow up to that and i'll provide a specs update once we come to some stasis there19:10
*** Leom has joined #openstack-meeting19:10
fungihopefully should have somthing up for approval in next week's meeting19:10
Zalman{-}evening, people this is british server?19:10
pleia2anyone interested can see how I filtered and we can adjust accordingly19:10
*** shaohe_feng has quit IRC19:10
fungi#topic Specs approval19:10
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:10
fungi#info Approved spec "A Task Tracker for OpenStack"19:11
*** shaohe_feng has joined #openstack-meeting19:11
fungi#link http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html19:11
fungi(and there was much rejoicing)19:11
pleia2\o/19:11
anteaya#link small edit https://review.openstack.org/#/c/326680/19:11
anteayaand yay!19:11
Zara\o/19:12
fungianteaya: oh, lgtm. approving19:12
anteayathanks, it works locally19:12
*** reedip has joined #openstack-meeting19:12
fungishould merge shortly19:13
anteayathank you19:13
fungi#topic Priority Efforts19:13
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:13
fungii don't see any urgent updates there, but we've got some updates filtering in on the aforementioned ml thread19:14
fungialso rcarrillocruz mentioned that hpe is moving our infra-cloud hardware again in ~4-6 weeks to a less damp facility19:14
*** zeih has joined #openstack-meeting19:14
Zara:D19:14
pabelangerDid we decided if we wanted to try used the hardware today anyways?19:14
yolanda:(19:14
pabelanger/used/using19:15
pleia2I miss our weekly updates19:15
fungii'll leave it up to rcarrillocruz and anyone else currently wrangling the hardware to determine if that's feasible19:15
*** reedip has quit IRC19:15
fungipleia2: yep, as soon as we get the priority list pruned and updated i'd like to start doing them again, or at least collecting incremental updates19:15
*** reedip has joined #openstack-meeting19:15
fungior you just mean you miss the updates on infra-cloud?19:16
anteayajeblair also made a point that perhaps we could entertain the idea of another hardware provider19:16
*** reedip has quit IRC19:16
pabelangeranteaya: ++19:16
pleia2fungi: infra-cloud, the ones cody was doing19:16
jeblairyeah, at this point, if someone else offers hardware (or we still have folks interested waiting in the wings), i think that would be a good idea19:16
anteayas/another/a different19:16
fungiyeah, there is at least one company who has reached out to us about the logistics of providing hardware/colocation19:16
jeblairwe're 6 months behind on this, mostly due to hp logistical issues19:16
fungii can get people involved in a discussion with them as long as i get some volunteers to steer that19:17
pabelangerI'm happy to get more involved where ever needed19:17
* bkero willing to help out any way he can19:17
*** ihrachys has quit IRC19:18
fungiideally at least one person currently involved in the infra-cloud effort too, so that we can get some continuity on the effort19:18
yolandai can collaborate, and give advice, but cannot compromise on that at the moment19:18
*** ihrachys has joined #openstack-meeting19:18
fungithanks yolanda19:18
yolandai need to figure how much time could i dedicate19:18
*** yohoffman has quit IRC19:19
pabelangeryolanda: I'm free whenever you find the time19:19
fungialso no idea if rcarrillocruz is interested in helping with a separate provider, but he said he's missing the meeting today and will catch up afterward19:19
*** jrichli has joined #openstack-meeting19:19
fungiso should probably continue this discussion outside the meeting19:19
yolandapabelanger, we can schedule some time and i give you an overview19:19
*** jungleboyj has joined #openstack-meeting19:20
pabelangeryolanda: ack19:20
fungi#topic Timeline for first Xenial systems (pleia2)19:20
*** openstack changes topic to "Timeline for first Xenial systems (pleia2) (Meeting topic: infra)"19:20
*** zeih has quit IRC19:20
pleia2so, this came up because planet.o.o is a bit stuck with a broken package in trusty, the idea was floated to switch to pulling it from source19:20
fungilooks like there are a few drivers for having at least some preliminary use of xenial for our servers19:20
*** jrichli has left #openstack-meeting19:20
*** shaohe_feng has quit IRC19:21
pleia2and can't upgrade zanata until it's on xenial, and the i18n team is eager for the new features that the zanata folks put in for us19:21
*** lyrrad has joined #openstack-meeting19:21
*** shaohe_feng has joined #openstack-meeting19:21
pleia2so this topic is mostly to get a feel for our priority for moving to xenial on some systems19:21
*** liusheng has quit IRC19:22
*** timcline has quit IRC19:22
pleia2I'd rather not rewrite our planet module if it'll be fixed by an upgrade in a month, but if we aren't planning to go to xenial for 6 months, that's a very different story (and something I need to talk to the i18n folks about)19:22
fungimy recollection from the discussions befpre and at the summit was that we weren't going to push to upgrade all our trusty systems to xenial until next year, but that running xenial where it makes sense to do so is acceptable19:22
*** liusheng has joined #openstack-meeting19:22
*** merooney has quit IRC19:23
*** timcline has joined #openstack-meeting19:23
pleia2yeah, that makes sense, just trying to pin down when we should aim for the first xenial systems19:23
pabelangerWe still have some servers running precise, I'm trying to focus on upgrading them before moving into xenial.  But happy to review code19:23
fungithese all sound like cases where running xenial is at least no worse than trying to make things work on trusty19:23
fungiwe did also say we'd avoid deploying new xenial systems until we finished precise to trusty upgrades19:24
pleia2zanata could probably run on trusty if we grab java from a 3rd party repo, but that does not give me good feels :)19:24
fungiwe can likely knock out zuul and static pretty easily, but wiki is going to be a pretty involved upgrade due to its lack of configuration management19:24
*** mriedem has joined #openstack-meeting19:24
pleia2yeah, the wiki is hard19:24
*** carolbarrett has joined #openstack-meeting19:25
pabelangerwiki is last item on my list19:25
pabelangerI've been pusing it to the end on purpose because of the amount of work19:25
* pleia2 nods19:25
*** mriedem1 has quit IRC19:25
*** comay has joined #openstack-meeting19:26
pabelangerwith that said, if we want xenail first, I'm happy to skip wiki for the moment19:26
fungii was talking about it earlier today in #-infra, but we really need some clear cut plan on how to maintain it. i did a little research on whether we could run it from distro packages, and what the state is for the puppet modules in the forge, but ultimately i want whoever's going to be working on the uprgade to decide what's the most maintainable long term19:26
pabelangerIs the wiki long term now?19:26
funginot necessarily long term, but long enough term to get us a graceful exodus19:27
pleia2btw, mediawiki is being removed from debian and that's where ubuntu gets it from19:27
fungiwhich i think involves having it maintainable in the long term (regardless of whether we opt to actually maintain it indefinitely)19:27
fungipleia2: not "being removed" but removed more than a year ago19:27
pabelangerRight, I'm hoping 12 more months honestly of keeping wiki.o.o online19:27
*** timcline has quit IRC19:27
*** xyang has quit IRC19:28
fungipleia2: i also looked into rpms, and the packaging situation is even less fun there19:28
*** ihrachys has quit IRC19:28
pleia2aha19:28
fungieveryone these days seems to be installing from source19:28
*** baoli has joined #openstack-meeting19:28
pleia2yeah19:28
fungianyway, this is getting off onto a tangent19:28
pabelangermaybe we need to revisit moving away from mediawiki to something else? Not that I want to talk about it now19:29
pabelangerfungi: ++19:29
*** ihrachys has joined #openstack-meeting19:29
pleia2loosely speaking, do we think we can aim for having our first xenial systems available in a month?19:29
pleia2I can start working on fixes we need in puppet19:29
fungito tie that subtopic up, i'd love to have a very short spec describing a plan to get the wiki into configuration management and upgraded so that it can go onto the priority specs list19:29
fungithanks pleia2. any additional help there is appreciated19:29
pabelangerI'd like to stand up our xenial wheel mirror first, if possible.  Assuming rackspace has the image uploaded19:30
pleia2I'd like to have a new zanata server up for translations this cycle, which means having it ready for testing by august at the latest19:30
fungipleia2: yeah, that sounds reaosnable19:30
pleia2ok, great19:30
fungianybody object to having a xenial server or two in our corral in ~ a month?19:30
anteayaI do not object19:31
*** shaohe_feng has quit IRC19:31
anteayaand I agree with fungi's call for a spec for the wiki19:31
*** shaohe_feng has joined #openstack-meeting19:31
fungibeing able to meet the i18n team's needs, being able to get planet sanely off of precise, et cetera trump the risks of running a couple xenial servers "early" for me at least19:31
*** xyang has joined #openstack-meeting19:32
fungi#topic Setup a common message bus using mqtt (mtreinish)19:32
*** openstack changes topic to "Setup a common message bus using mqtt (mtreinish) (Meeting topic: infra)"19:32
*** reedip has joined #openstack-meeting19:32
fungithat topic you forgot to remember19:32
pleia2I can start drafting up the wiki spec (and pabelanger or anyone else is welcome to push changes to it as we go)19:32
fungithanks pleia2!19:32
pabelangerpleia2: thanks19:32
mtreinishfungi: well I did remember to put it on the wiki19:33
anteayamtreinish: yay!19:33
mtreinishthat counts for something :)19:33
fungimtreinish and i were discussing his gerrit to mqtt event translation and sdague's one-stream-to-rule-them-all vision19:33
*** nadya has joined #openstack-meeting19:34
fungithe idea here is that mtreinish and i would co-author a spec to add something like a firehose.openstack.org server with an mqtt view of everything in our infrastructure, adding gerrit's event stream as the first feature19:34
pleia2cool19:34
* mtreinish really likes that hostname19:34
fungisomething similar to the fedora community infrastructure's fedmsg, but not zeromq19:34
jeblair++ and ++19:35
anteayasounds good19:35
*** prashantD__ has joined #openstack-meeting19:35
*** reedip has quit IRC19:35
pleia2I don't know anything about mqtt and don't want to derail, but I will mention that the Fedora Infra team uses http://www.fedmsg.com/en/latest/overview/ very similiarly19:35
fungithis was just a quick sync up in the meeting to see if that's a completely insane idea and we should pack it in and pretend it never came up19:35
pleia2there's an instance of it running in debian infra as well19:35
*** obondarev has joined #openstack-meeting19:35
*** permalac has quit IRC19:36
fungiyeah, i expect that the mechanics of getting arbitrary system events into mqtt are pretty similar to zeromq, so we can probably borrow a lot from fedora infra and dsa for those19:37
jeblairi think it's a swell idea -- one thing i would like to caution though is that i think some of the things that we are using message buses for today we can and probably should use zuul for in zuulv319:37
fungijeblair: you mean as far as what nodepool is consuming from jenkins?19:37
notmorganjeblair: ++19:37
fungi(and also what nodepool is consuming from zuul as of this week)19:38
fungiwhat other message busses are we using?19:38
jeblairfungi: well, that specific case is not applicable in v3.  i was thinking more along the lines of some of the post-processing things we do might be better implemented as zuul jobs in v319:38
*** prashantD_ has quit IRC19:38
mtreinishjeblair: oh like the logstash and subunit processing?19:39
fungioh, sure, i would mostly see teh firehose as a third-party/personal point of integration19:39
mtreinishfungi: we do use zeromq for that path. Jenkins -> zmq -> gearman client -> gearman -> gearman worker19:40
jeblairyeah.  i don't have that all mapped out yet.  *maybe* it's best as an independent queue, or maybe it fits in to zuulv3.  mostly i mention that as something to keep in mind as we start thinking about how we can use it19:40
fungii'm unconvinced we should drive any internal infrastructure off of it, at least initially, and even then only if it makes sense to do so19:40
anteaya++ swell idea19:40
*** e0ne has quit IRC19:40
mtreinishfungi: yeah that was my thinking too, set it up for external use initially, but it might make sense eventually to start using it for internals too19:40
jeblairfungi: that seems like a good way to start -- get to know it before we start depending on it19:40
fungiso teh spec definitely wouldn't go into using it for anything other than experimentation19:41
*** shaohe_feng has quit IRC19:41
*** shaohe_feng has joined #openstack-meeting19:41
fungibut having it might help us drive some additional innovation from outside into the team19:41
*** zeih has joined #openstack-meeting19:42
fungias people see a consistent place to access some of the currently internalized events19:42
fungianyway, i think that more or less covers it. we still have a couple topics to go today...19:42
*** asettle has quit IRC19:42
fungi#topic zuul.o.o / static.o.o migration to ubuntu-trusty: Outage required (pabelanger)19:42
*** openstack changes topic to "zuul.o.o / static.o.o migration to ubuntu-trusty: Outage required (pabelanger) (Meeting topic: infra)"19:42
fungiso, wanting to work out a maintenance window for these?19:42
pabelangerYup19:43
pabelangerI think we need about 1-2 hours to be safe19:43
pabelangerI was thinking if we stopped gerrit, we should be safe to stop zuul and detach / attach volumes on static.o.o19:43
fungiyeah, i could _probably knock static.o.o out in 15 minutes if all goes smoothly, but wouldn't want to bank on that19:43
*** timcline has joined #openstack-meeting19:43
fungiso 2 hours seems like a safe estimate19:43
jeblairzuul should be pretty fast too.  very little state.19:44
fungimy schedule is wide open, and i'm happy to help with it19:44
fungiin zuul's favor, we also have zuul-dev successfully running on trusty now19:44
*** browne has left #openstack-meeting19:44
fungiso shouldn't run into unexpected puppet issues19:44
*** xyang has quit IRC19:44
rcarrillocruzheya19:44
jeblairand i think the only critical firewall involved is *on* the zuul host19:44
rcarrillocruzi'm around19:45
*** yassine has quit IRC19:45
*** timcline has quit IRC19:45
pabelangerYup, I think we can do it pretty quick19:45
anteayawhoever wants to drive this please suggest a date19:45
rcarrillocruzwootz, quite a bit of notifications19:45
*** timcline has joined #openstack-meeting19:45
pabelangerjust need to decide how much heads up to give the community19:45
pabelangertoo early / late to do it this friday?19:45
anteayafriday is fine for me19:45
fungii'm free this friday, but for a two-hour projected outage i'd be hesitant to announce it on such short notice19:46
anteayanothing of note this friday in the release schedule: http://releases.openstack.org/newton/schedule.html19:46
*** zeih has quit IRC19:46
pabelangerokay, happy to defer to fungi for the right day19:46
fungiyou beat me to linking it19:46
fungi#link http://releases.openstack.org/newton/schedule.html19:46
*** tpepper has joined #openstack-meeting19:46
anteayayay I beat fungi19:46
anteayathat never happens19:47
fungiif we do next week, that's the n2 milestone week19:47
anteayafungi: June 1719:47
anteayafungi: you are looking at July19:47
fungiindeed, i am19:47
fungile sigh19:47
*** longxiongqiu has joined #openstack-meeting19:48
jeblairlet's do it before then :)19:48
fungiso trove specs proposals deadline is the most exciting thing happening next week19:48
*** timburke has joined #openstack-meeting19:48
fungiyeah, i'm happy to help, and i'm available friday, june 1719:48
pabelangerokay, lets aim for that19:48
pabelangerI'll get something into pastebin to review19:49
*** nadya has quit IRC19:49
pabelangerthen send out the email to ML19:49
fungipabelanger: thanks!19:49
*** obondarev has quit IRC19:49
fungianything more to discuss on that?19:49
pabelangerI think we are good19:49
fungi#topic task-tracker migration-- load testing storyboard using storyboard-dev, and gerrit integration (Zara)19:50
*** openstack changes topic to "task-tracker migration-- load testing storyboard using storyboard-dev, and gerrit integration (Zara) (Meeting topic: infra)"19:50
pleia2exciting :)19:50
Zarahi! :) I squooshed two things together...19:50
fungiZara: i assume this is stemming from last week's question about maybe setting up the storyboard plugin on review-dev and pointing it at storyboard-dev?19:50
fungioh, or maybe not? ;)19:50
Zaraah, sorry, it was actually a bit different but it stemmed from there19:51
anteayafungi: that is the second part of this two part topic19:51
fungiyou have the floor!19:51
Zarathe first thing is more general: if we're expecting lots of new users, we should check storyboard works to scale...19:51
Zarawhat's the best way to do that?19:51
*** shaohe_feng has quit IRC19:51
*** obondarev has joined #openstack-meeting19:51
*** morgabra_ is now known as morgabra19:52
*** morgabra has joined #openstack-meeting19:52
fungiwe've done some pretty minimal load testing of services in the past19:52
*** cwolferh has quit IRC19:52
*** mbound has joined #openstack-meeting19:52
fungii think clarkb found a took to load-test etherpad for example and we tried out pointing it at etherpad-dev19:52
*** longxiongqiu has quit IRC19:52
*** shaohe_feng has joined #openstack-meeting19:52
*** reedip has joined #openstack-meeting19:53
fungithe openstackid devs did some load testing of authentication for their summit app pointed at openstackid-dev19:53
fungiet cetera19:53
*** cdent has joined #openstack-meeting19:53
fungiso it's generally been custom/ad-hoc whitebox solutions (based on some internal knowledge of the application and expected usage patterns)19:53
Zaraah, okay19:53
ZaraI think it also depends on the expected pace of migration19:54
Zarafor how heavy a load we need to have tested at any time19:54
fungii'm also perfectly happy to address nonobvious scaling challenges as we come across them rather than spend development rime prematurely optimizing for things we don't know will actually be an issue19:55
fungis/rime/time/19:55
anteayaokay that helps, thank you19:55
anteayathat was the prime dev concern when I asked are we ready for the masses19:56
*** merooney has joined #openstack-meeting19:56
*** reedip has quit IRC19:56
anteayaZara: are you ready to move to the second bit on the topic?19:56
fungistoryboard already has some pretty aggressive/challenging features on its roadmap, and so unnecessarily taxing the devs with scalability testing seems like an undue burden19:56
anteayafungi: thank you19:57
anteayaand yes agreed19:57
Zaraokay, I was the one who was worried about it, but I'm fine if other people are willing to share that down the line :)19:57
*** mbound has quit IRC19:57
funginote we're running out of meeting time if there's a part 219:57
* SotK too19:57
*** nadya has joined #openstack-meeting19:57
Zaraso the other thing was that I was tasked with gerrit integration, right now I have a big review backlog and so on, and it's unlikely to make fast progress while I'm on it19:58
fungi(2 minutes remaining)19:58
anteayaZara: well I think we are asking if someone can help with adding the storyboard gerrit plugin to the review-dev server19:58
anteayaat least that was what I was asking ofr19:58
anteayafor19:58
anteayaand also to squeeze it in we have a StoryBoard bug sprint coming up: https://wiki.openstack.org/wiki/VirtualSprints#StoryBoard_Bug_Sprint19:59
fungizaro seems like an obvious choice as he has knowledge of the puppet module, root access to the review-dev server and is the author of that gerrit plugin19:59
Zaraah, related, was going to say: if someone wants it right away, someone else needs to prod about it and push for that sort of thing19:59
fungibut i don't know what his availability is19:59
anteayaso hopefully we can onboard some new storyboard developers who are willing to help with bugs19:59
*** asettle has joined #openstack-meeting19:59
fungiokay, duly noted19:59
fungiand with that, we're at time19:59
anteayathank you20:00
fungithanks everyone!20:00
zaroi can help but will need to wait for a little bit20:00
fungi#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Jun  7 20:00:11 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-06-07-19.03.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-06-07-19.03.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-06-07-19.03.log.html20:00
ttxo/20:00
*** swifterdarrell has joined #openstack-meeting20:00
*** yolanda has left #openstack-meeting20:00
sdagueo/20:00
* fungi more or less ended on time this week20:00
thingeeo/20:00
dhellmanno/20:00
*** annegentle has joined #openstack-meeting20:00
*** AJaeger has left #openstack-meeting20:00
* dhellmann may drop off of this hotspot at some point20:00
*** pdardeau has joined #openstack-meeting20:00
ttxannegentle, dims, flaper87, johnthetubaguy, mestery, mtreinish, mordred, morgan, russellb : around ?20:00
mordredo/20:00
annegentleo/20:00
* mestery buckles in20:00
notmynamedhellmann: ok. probably nothing contentious to be discussed ;-)20:00
mordredalso may drop off this hotspot at any time20:01
* edleafe hides in the back20:01
mordredis on a train20:01
dimsoh dear! :)20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Jun  7 20:01:08 2016 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
*** prometheanfire has left #openstack-meeting20:01
*** olaph has left #openstack-meeting20:01
mtreinisho/20:01
johnthetubaguyo/20:01
ttxalright...20:01
ttxOur agenda for today is:20:01
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:01
ttx#topic Call out GPL style licenses in testing/validation.20:01
*** david-lyle has joined #openstack-meeting20:01
*** openstack changes topic to "Call out GPL style licenses in testing/validation. (Meeting topic: tc)"20:01
* Rockyg is petting a sweet cat that slinked in through the back20:01
ttx#link https://review.openstack.org/29314020:01
*** Swanson has joined #openstack-meeting20:01
ttxFeels like everyone is in agreement here, so unless someone yells, I'll just approve this one20:02
*** shaohe_feng has quit IRC20:02
ttxno yelling20:02
*** gmmaha has joined #openstack-meeting20:02
*** nadya has quit IRC20:02
*** Sukhdev has quit IRC20:02
ttxapproved then20:02
ttx#topic Remove Cue project team20:02
*** openstack changes topic to "Remove Cue project team (Meeting topic: tc)"20:02
ttx#link https://review.openstack.org/32441220:03
*** galstrom is now known as galstrom_zzz20:03
*** jmckind has quit IRC20:03
ttxThis one is about delivering on a promise some of us made of cleaning up the tent when a project just doesn't deliver on the expectations20:03
ttxEspecially when a project does not process reviews anymore, or doesn't release anymore, or doesn't addess vulnerabilities anymore, or doesn't participate to events anymore, or doesn't hold meetings / discuss on ML anymore20:03
ttxCue is a bit of a low-hanging fruit there, since they don't really have recent activity, missed the Mitaka release, missed the Austin Design Summit, and no recent meeting or ML discussion20:03
mtreinishttx: I'm just curious is there an activity requirement for projects written down anywhere?20:04
ttxSo I personally think they fell below the bar of activity that is expected of official OpenStack projects20:04
thingeemtreinish: no20:04
dhellmannI'm glad to see us taking these one at a time20:04
thingeecase by case20:04
*** sarob has joined #openstack-meeting20:04
*** rwsu has joined #openstack-meeting20:04
ttxmtreinish: actually there is20:04
mordredhas anyone pinged vipul about it?20:04
dhellmannthe release model tags specify release activity20:04
ttxbut there is no metric, we are just asking that a project is active before we can vet it20:04
mugsiemordred: I pinged min20:04
annegentlettx: yeah I was going to ask the same, is there a list or measure?20:04
mugsie(the new ptl)20:05
flaper87o/20:05
mordredmugsie: ah - cool.20:05
ttxmin was CCed on the review20:05
mtreinishttx: it'd be nice if we had something we could point to in the commit msg20:05
ttxI think it's a case of a single-vendor project where the single vendor lost most of its interest20:05
mesteryttx: Sounds about right20:06
mtreinishbecause from my pov not every project is going to be super active all the time20:06
*** glange has joined #openstack-meeting20:06
dtroyerttx ++  and a highlight of the dangers of low diversity20:06
sdaguediversity:danger20:06
mtreinishttx: but in this case I agree with the single vendor losing interest20:06
*** edtubill has quit IRC20:06
mtreinishI'm thinking more for the future20:06
thingeemtreinish: missing releases is pretty bad20:06
*** aerwin3 has quit IRC20:06
annegentleI think we have good input since Min answered, but did wonder about "who's next"20:06
ttxmtreinish: missing the release, the summit, the IRC meetings and no ML discussion is pretty much clear cut to me20:06
*** aerwin3 has joined #openstack-meeting20:07
sdagueyeh, it seems pretty straight forward20:07
ttxI mean, they can totally be back if they pick it up20:07
mesteryttx: Seems about right to me too20:07
*** shaohe_feng has joined #openstack-meeting20:07
thingeeannegentle: not our problem of who is next. it's retired and someone can revive.20:07
ttxbut fact is, they have not the level of activity that is expected of openstack projects at this point20:07
dhellmannthingee : we very well may end up with oslo libraries stable enough to not need a release in a given cycle, so it's not out of the question20:07
edleafeMaking it easier for projects to come in should also make it easier for them to go out20:07
ttxdhellmann: yes, in that case it's more of a combination of things20:08
dtroyeredleafe: ++20:08
ttxthe project also happens to be not mature20:08
mesteryedleafe: ++20:08
ttxedleafe: exactly20:08
mordrededleafe: ++20:08
thingeedhellmann: as it stands, cue is part of the release, and they failed at that. That's fine for future cases that maybe out of the process.20:08
dhellmannttx: right, that's why I don't think we want too many hard-and-fast rules20:08
sdaguedhellmann: but the whole oslo project isn't going to dry up20:08
ttxgreasing the door goes both ways20:08
sdaguedhellmann: agreed20:08
dimsttx +120:08
johnthetubaguydhellmann: stability is a good point, when we come to making the rules20:08
dhellmannthingee : sure, I support removing them, I was just pointing out that we can't make "you didn't release" a firm rule that automatically drops a project20:08
annegentledhellmann: ttx: ok so rules/lists/metrics won't really work20:08
sdagueI also think there is a difference, because oslo libs in some levels are like subtrees in a lot of other projects20:08
annegentlecase by case then20:08
*** merooney has quit IRC20:08
edleafeanother way to look at it: if they applied today for the big tent, would we feel that they measure up?20:09
sdaguefortunately we've got 13 elected representative humans that have human judgement20:09
*** adiantum has quit IRC20:09
dhellmannsdague : ++20:09
ttxannegentle: yes. My rule of thumb for the start is... having a tc member who cares enough to propose the removal20:09
dims++ sdague20:09
edleafesdague: yes!20:09
thingeedhellmann: I'm confused by your "we very well may end up..." ... makes it sounds like this is not happen, so it's not really relevant right now?20:09
mesterysdague: yes!20:09
sdagueI think coming up with an algorithm instead of just "representative humans" is the wrong thing to do20:09
ttxIt's not "you miss a release, you're out"20:10
dhellmannthingee : it is not sufficient for me to say that because a project did not release, they must be removed from openstack. I gave an example of where that would be OK.20:10
thingeedhellmann: that's not what we're saying20:10
ttxIt's just one symptom amongst others20:10
thingeedhellmann: that is just one of the things20:10
mtreinishttx: that's all I wanted to clarify. Because the commit msg could be read that way20:10
dhellmannok. that was the one I caught as it went past20:10
ttxmtreinish: oh, yes, there is no rule we are following here20:11
dimswe are not talking about archiving. just remove from governance. so easy +1 for removal20:11
dhellmannyes, in this case the project appears extremely inactive, as demonstrated by the many points raised. as long as we're all clear that no one of those points is sufficient on its own, I'm happy.20:11
*** cwolferh has joined #openstack-meeting20:11
*** baoli has quit IRC20:12
sdaguedhellmann: it's all still human judgement20:12
*** _amrith_ is now known as amrith20:12
dhellmannok, good20:12
ttxagreed20:12
sdagueI think that's our algorithm20:12
sdaguea TC vote20:12
*** shaohe_feng has quit IRC20:12
ttxjust a pile of symptoms and a gut call20:12
sdagueyes20:12
ttxThat case was arguably easy20:12
ttxwhich is why I posted it first20:12
thingeedims: you can bring something out of archive. Just like you can bring something out of retirement.20:12
*** baoli has joined #openstack-meeting20:12
ttxok, looks like we have majority there20:12
notmorganttx: can we swap the next two topics (before we swap)20:13
dimsthingee true20:13
fungialso, unlike int the beforetime, we can take a project out of openstack without having to rename its git repos20:13
*** toddjohn has quit IRC20:13
notmorganttx: the url entry should be less contentous/take less time.20:13
*** shaohe_feng has joined #openstack-meeting20:13
ttxnotmorgan: sure20:13
flaper87notmorgan: ++20:13
annegentleyeah sounds good to swap20:13
dimsfungi : was thinking about http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project steps20:14
*** reedip has joined #openstack-meeting20:14
ttxok, so, I'll approve it now20:14
*** jmckind has joined #openstack-meeting20:14
ttxapproved20:14
ttx#topic Adds a contributordocs: URL entry to projects.yaml20:15
*** openstack changes topic to "Adds a contributordocs: URL entry to projects.yaml (Meeting topic: tc)"20:15
ttx#link https://review.openstack.org/31639620:15
ttxThis is still in progress work, Anne do you have all you need to make progress ?20:15
*** reedip has quit IRC20:15
*** aerwin3 has quit IRC20:15
annegentleas I said in the review, it's a draft.20:15
notmorgani'm generally for this, needs a little cleanup though.20:15
mesteryyes20:15
notmorganbut it's def. going the right way20:15
mesteryOne tag removal in there20:15
mesterynotmorgan: ++20:15
annegentlemestery: yes nice catch20:15
*** aerwin3 has joined #openstack-meeting20:15
mesteryannegentle: nice work though!20:15
*** reedip has joined #openstack-meeting20:15
annegentleI'd like to figure out how to deal with projects with multiple repos with docs?20:15
mtreinishannegentle: yeah, that's what I was just gonna ask20:16
notmorganannegentle: make it a list?20:16
*** reedip has quit IRC20:16
annegentlewould it be better to put a docs: line for each repo?20:16
mtreinishbecause things like qa and infra have lots of very different projects20:16
notmorganannegentle: hm. probably per-repo20:16
annegentlesomeone tell me YAML solutions here :)20:16
dimsannegentle : where are we going to render/use this info?20:16
flaper87annegentle: haven't read the latest PS but, did you find a way to avoid adding the repos with `None` urls ?20:16
dhellmannannegentle : or per deliverable20:16
amrithannegentle, could it be as simple as a link to a page with that list of docs? is there value in having all the links in the infra project?20:16
notmorgandhellmann: ++20:16
flaper87that said, I'm certainly in favor of this20:16
notmorgandhellmann: yeah per deliverable would be my vote20:16
annegentleflaper87: I think I can leave the line blank instead of None, but I sorta used None to indicate "I'd expect something here"20:17
notmorganannegentle: you can, but None is fine as well.20:17
notmorgani like the explicits20:17
dhellmannannegentle : does the yaml parser turn "None" into a None value?20:17
johnthetubaguy+1 for adding None explicitly, its kinda nice20:17
annegentleamrith: not sufficient if I want to expand beyond contributor docs20:17
*** ihrachys has quit IRC20:17
annegentledhellmann: not sure, good question20:17
* dims envisions a pypi like interface for all this info 20:17
notmorgandhellmann: it should. if not we should make sure we're passing the right thing in20:17
dhellmannannegentle : because I wouldn't want the rendering code to have a special case for that20:17
*** aerwin3 has quit IRC20:17
*** aerwin3 has joined #openstack-meeting20:18
amrithannegentle, if that's the case should the link be at the project level or the release level?20:18
sdaguedhellmann: I'm nearly sure that it does20:18
notmorgani think "null" is correct20:18
notmorgannot "none"20:18
annegentleis there a way to say docs: and then what type? in YAML?20:18
notmorganhttp://yaml.org/type/null.html20:18
sdaguenotmorgan: yeh, that might be20:18
johnthetubaguynotmorgan: good point20:18
dhellmannsdague : possibly, but ... what notmorgan said20:18
annegentleamrith: you might be onto something there20:18
dhellmannwe can deal with that when we update the rendering code20:18
flaper87annegentle: cool20:18
annegentleamrith: release level perhaps20:18
*** ihrachys has joined #openstack-meeting20:19
amrithannegentle, maybe both?20:19
ttxannegentle: ok, so you will iterate on the review20:19
annegentleok I probably have enough to do another passthrough... for more reviews20:19
annegentleyeah20:19
notmorganannegentle: :)20:19
annegentlethanks20:19
ttxannegentle: sounds good20:19
amriththx annegentle20:19
mtreinishnotmorgan: heh, I like the definition there, "devoid of value"20:19
notmorganmtreinish: hehe20:19
ttxjust wanted to make sure you had all you needed to make progress20:19
ttxnext topic...20:19
ttx#topic Add golang as an approved language20:20
amrithlike the review of my book, "this book fills a much needed void".20:20
*** openstack changes topic to "Add golang as an approved language (Meeting topic: tc)"20:20
* dims dreads20:20
* notmorgan braces for impact.20:20
ttx#link https://review.openstack.org/31226720:20
ttxOK, so I'll say this upfront, I dislike all the options we are given here20:20
* edleafe gets the popcorn20:20
ttxLike Monty I tend to lose sleep over them over the past week20:20
* notmorgan steals edleafe's popcorn20:20
dhellmannttx: I think that's one thing we can all agree on.20:20
mordred++20:20
ttxLike there must be a solution that is perfect but I can't find it20:20
dimsttx : yep, don't like it at all20:20
annegentleI'll be honest, I feel backed in a corner.20:20
*** gordc has joined #openstack-meeting20:20
ttxMost TC members voiced their position on this one, I'll try to summarize20:20
notmorganso fwiw, i've changed my view somewhat.20:21
ttxFlavio raised that opening the floodgates to another language is not the right call at this time for OpenStack20:21
dougwigttx: any chance this can be tabled until the TC tackles defining openstack?20:21
flaper87o/20:21
ttxAs we are still struggling with driving more consistency and share more things between components of OpenStack20:21
annegentleTiming, urgency, emotional ties... rather than data-driven.20:21
ttxdougwig: we kind of already did20:21
ttxa long time ago20:21
notmorgandougwig: i would prefer to not take that on first if we're revisiting20:21
* Rockyg hands edleafe a pot of hot butter20:22
ttxAnd I tend to I agree with Flavio -- I'm still very much supporting the 2011 view that OpenStack is a thing, rather than a loose collection of things20:22
notmorgandougwig: this is about language first, scope is a separate convo20:22
edleafeRockyg: mmmmmm20:22
notmorganif it is being revisited20:22
ttxBut we are struggling to share more between projects, and I fear that adding Go would put the final nail in that coffin20:22
*** shaohe_feng has quit IRC20:22
ttxmestery advocated that we should just let the projects use the best tools.20:22
ttxHowever I think Flavio's option is still giving projects enough choices, including letting projects use dependencies written in other languages, maybe he can develop that in a minute20:22
ttxdims said the TC should vet which projects did enough due diligence to get to use Go and which didn't20:23
mesteryThe alternative is to say they are not openstack if they use a language like Go I guess20:23
ttxwhich on the surface sounds like a nice compromise option20:23
*** shaohe_feng has joined #openstack-meeting20:23
dimsttx : cross-project with guidance from TC20:23
flaper87yeah, I'm really worried about the community impact this will have and I lean towards the 2011 decision we made. More importantly, I'm in favor of taking a smaller step this time (or no step at all) and give us some extra time to process the big tent change20:23
ttxBut I really don't want that. I prefer to say "use a dependency" than be in the business of granting exceptions and telling others "no you're not tall enough to use Go"20:23
ttxmordred was very eloquent and I wouldn't dare summarize his views, maybe he can20:23
dimsttx ack20:23
mordredttx: no chance - that took me a long time to write20:23
flaper87mestery: not necessarily, some projects can use a dependency model as the one proposed 2 weeks ago but some projects won't be able to do that and, admitedly, the project might need to make other decisions there20:23
dhellmannyeah, I can't imagine how we could effectively police the "appropriate" use20:24
notmorgani am very very very very very very very against the TC saying "you can use go" individually20:24
flaper87mordred: lol20:24
thingeedhellmann: +120:24
notmynamethe TC has already supported other languages than python for valid technical reasons. and it seems everyone agrees with the technical justifications that have been given20:24
mordredttx: I hate both choices, I just think one is a little less bad than the other20:24
ttxnotmorgan: that we agree on20:24
flaper87notmorgan: yup, not the plan20:24
ttxmordred: it's also easier to revisit, although I'd hate that too20:24
* notmorgan summarizes mordred's email as "read the email for context"20:24
mesteryflaper87: Some not all, thus my comment was relevant :)20:24
mordrednotmorgan: ++20:24
ttxAny others I missed ?20:24
mugsieand we have in the past just let other languages slip in, and said nothing20:24
edleafeI'd still like to see an attempt to use gopy to create an extension for the "slow part" so that the majority of the code can remain in Python20:24
ttxI think thingee is also on flaper87 option20:24
flaper87mugsie: yup20:24
mesterymugsie: What? Blasphemy20:24
* ttx ctaches up with recent reviews20:25
flaper87mugsie: that was for mestery20:25
mesterylol :)20:25
dimsdhellmann : cross-project spec and debate at cross project meeting20:25
mugsieflaper87: tab+m?20:25
notmynameedleafe: all we've talked about now with swift specifically is a small part of the whole. we're not planning on rewriting everything in go20:25
*** adiantum has joined #openstack-meeting20:25
flaper87mugsie: guilty as charged20:25
notmorganas long as we clearly say this is a big tent issue (go is not part of the tent), but (as long as infra doesn't raise a flag, and they havent), you can use our CI.20:25
mesteryI like dtroyer's comment, it was spot on I think, and aligns with what dougwig mentioned too.20:25
edleafenotmyname: that was more for Designate's concerns20:26
notmorgani'm fine with it at this point, regardless of the direction taken.20:26
thingeeyes, I think if the TC provides the option for projects to have an outside requirement based on go that's not part of the big tent, that would be fine.20:26
sdaguemestery: then propose some removes if that is your primary concern20:26
* notmorgan feels that a decision needs to be made today fwiw on this.20:26
ttxmugsie made good points on more fragemntation at specific project level vs. more fragmentation at openstack-level20:26
flaper87thingee: ++20:26
notmorganthingee: and that as the add on point20:26
flaper87notmorgan: +! on making the decision today20:26
dhellmannthingee : we don't currently have any formal restrictions about the language of third-party dependencies, do we?20:26
mesterysdague: Fair point20:26
dimsthingee : i'd like people to do their work here, not go elsewhere..20:26
annegentlethe timing is what's troubling. Why didn't you come to the TC over a year ago to map out a plan notmyname ? Why are we in this position of a black-and-white decision?20:26
notmynamedoes "not in the tent" mean that it's not in the openstack/* namespace at all?20:26
thingeedhellmann: nope20:26
flaper87notmyname: nope20:26
mordrednotmyname: the openstack/ namespace does not convey meaning20:27
notmorgannotmyname: no, just not in governance20:27
devanandathingee: that sounds like we're saying "if you develop your libraries elsewhere, you can use what ever language you want, and you can use them in openstack projects"20:27
*** roxanaghe has quit IRC20:27
mugsieI also would ask, we are talking about devs who are cross -virtical project devs. - did we ever really have that many? (aprart from the period when stuuff was being brought out of nova)20:27
notmorgannotmyname: absolutely still possible to be in openstack/* namespace if they want to be :)20:27
dhellmanndevananda : as long as you can pip-install them20:27
thingeedims: no one said to go elsewhere. you're still part of the community. it's the project's choice if they can't work with the option given20:27
notmorganit is up to the project to make that choice.20:27
mugsienotmorgan: is it?20:27
mordreddhellmann: or apt/yum20:27
dtroyermordred: as much as I wish that were true, it is not20:27
devanandadhellmann: I can't "pip install mysql" - but we depend on mysql20:27
dhellmannmordred : or import from python, I guess I should say20:27
devanandamordred: right. that's better20:27
anteayamugsie: it is not the number it is the workload20:27
dhellmanndevananda : mysql is not a lib20:27
mordreddtroyer: it may imply meaning to people, but it does not convey chosen meaning20:27
notmorganmugsie: it is. infra has said they are willing to help make go part of the deal, like java can be, like javascript can be20:28
anteayamugsie: and those that do cross project have had an increaased workload20:28
edleafemysql is also not part of OpenStack20:28
flaper87mordred: +120:28
mugsieanteaya: the point raised in the review was loack of cross-virtical-project developers20:28
anteayaright20:28
dimsthingee : ttx : do we let code be in openstack/ git and use CI but just not in governance?20:28
ttx"not in the tent" just means "not under the TC rule"20:28
notmorganmugsie: so the code can use opoenstack infra and be in openstack/* namespace, just not be in governance as an official openstack deliverable (it can be a dep like mysql is)20:28
ttxwhich is kind of what you want here20:28
anteayaand the ones that are currently active have an increased workload20:28
mordreddims: yes. we have tons of things like that20:28
sdaguedims: yes20:28
*** Apoorva has quit IRC20:28
dimswhew ok20:28
mugsienotmorgan: yeah - I knew that, but the issue around community costs is still going to happen then20:29
thingeedims: projects not part of the governance can already do that20:29
cdenthaving lots of things that are not OpenStack™ in /openstack is bound to cause external folk a ton of confusion20:29
flaper87and some actually do already, IIRC20:29
ttxprojects can continue to use openstack infrastructure and prove us wrong20:29
notmorganmugsie: somewhat. it doesn't convey ATC, doesn't convey other benefits, doesn't convey VMT coverage, etc20:29
notmynamewhat you're asking is that the swift contributors, in order to move forward with the best technical solution, will work in 2 separate repos? one under the TC and one not, where one is dependent on the other20:29
cdents/a ton of/increasaed20:29
anteayaand if the workload decreased to a managable amount we might get more folks doing cross project work20:29
*** rama_y has joined #openstack-meeting20:29
*** saggi has joined #openstack-meeting20:29
dimsthingee : that softens the blow20:30
anteayacdent: it already is20:30
devanandanotmorgan: ah, thanks for the clarification. would it be correct to restate that as "develop it using shared openstack resources, but not under openstack governance" ?20:30
annegentleright on the dependency... I don't understand any technical reason not to keep having the separate golang solution for object portion? What changed notmyname other than ttx's request?20:30
dimsnot sure what practical difference it makes to infra/docs etc20:30
thingeecdent: I disagree, we have things not part of openstack that are dependencies for certain use cases.20:30
notmorgandevananda: yes, better phrasing20:30
cdentthingee: I'm just reporting what people tell me20:30
devanandanotmorgan: maybe I'm being obtuse, but what's the practical difference, then?20:31
notmorgannotmyname: i would almost argue that should be the case in either case.20:31
notmynameannegentle: that is what we're planning on. having a golang object server (and a few supporting daemons). but there's not a dividing line between that and the rest of the project20:31
thingeecdent: I'm just reporting what is happening today :) - I mean libvirt is fine for example20:31
edleafecdent: that was recognized when we got rid of stackforge20:31
ttxnotmyname: the trick is how to allow you to do that without breaking the rest of openstack with crazy Golang rewrites20:31
dhellmannnotmyname : we would also need to decide how that dependency is consumed. I'm not sure devstack would want to install it from source, for example. Maybe?20:31
*** jrichli has joined #openstack-meeting20:32
notmorgandevananda: it's a resource allocation thing, horizontal teams are not required to be part of it, and those resources are very constrained.20:32
notmorgandevananda: and a marketing thing.20:32
flaper87dhellmann: ++20:32
notmynameit's like going to any other project and picking some files from some subdirectory and asking those to be developed in a separate repo now20:32
annegentlenotmyname: is there a technical problem with the dividing line? (really trying to understand, this is not a judging stance)20:32
mugsieso, as a straw man, we could have a repo that docs the usage, and how to install a repo in openstack/ , and for features requires work in both repos, but the 2nd repo is not part of openstack20:32
*** galstrom_zzz is now known as galstrom20:32
flaper87dhellmann: notmyname but that's something we can work together on with the infra team and whatnot if needed20:32
mugsiewhat is the difference then20:32
dimsdhellmann : i dont know how doing this way in any way reduces burden on cross project teams...20:32
*** shaohe_feng has quit IRC20:32
notmynameannegentle: yes. I went into this in great detail in an email to tts and flaper87, but that's not currently a public document20:32
ttxannegentle: yes there is... notmyname explained it to me quite well. the way swift is designed makes it hard to split it along dependency lines20:32
jrollttx: I find your use of the word "breaking" there interesting, why does re-writing things in golang inherently break things? or do you mean break openstack into two communities, between the go bits and the python bits20:32
annegentlenotmyname: ok20:33
ttxwhich is why it's not a nideal solution at all20:33
flaper87annegentle: notmyname: happy to share the contents of that email20:33
johnthetubaguycdent: agreed the current state of /openstack is confusing, points to the deeper questions we still need to answer here20:33
mordredjroll: community20:33
notmynameflaper87: I would totally support that20:33
*** reedip has joined #openstack-meeting20:33
jrollmordred: noted, the wording threw me20:33
annegentleflaper87: notmyname: thanks that will help me understand20:33
*** cody-somerville has joined #openstack-meeting20:33
flaper87annegentle: notmyname: coolio, I'll probably just put everything on an etherpad20:33
devanandanotmorgan: I am struggling to see how the distiction of whether a golang-based project falls under TC guidance has any bearing on cross-project teams (aside from the TC)20:33
*** shaohe_feng has joined #openstack-meeting20:33
notmynameflaper87: annegentle: I can put it on the ML after the meeting20:33
*** eharney has quit IRC20:33
dimsdevananda : me too20:34
notmorgandevananda: docs team, VMT, etc20:34
ttxannegentle: it's a problem that is linked to the very integrated design in swift, other openstack projects are less likely to have the same problem20:34
*** obondarev has quit IRC20:34
jrolldevananda++20:34
devanandanotmorgan: docs, VMT, etc, already don't have to care about new projets20:34
jroll^20:34
devanandanotmorgan: so why would they care about this one?20:34
annegentleI basically still sense that the problem is complex, the solution proposed is too simplified, so we all can't agree.20:34
clarkbdevananda: dims we spend a significant amount of time hand holding every little piece of dev20:34
notmorgandevananda: but the non-governance repos can't ask for these resources20:34
dhellmanndevananda : not true. They don't have to do the work for them, but they have to support them with tooling and guidance.20:34
ttxannegentle: yes20:34
notmorgandevananda: in an official capacity that is20:34
dimsclarkb : saying, you can create new repos with go code and use CI/infra etc..does not reduce that burden20:35
anteayahaving to go to teams and re-iterate what took place in a different meeting or summit session that they didn't know about because they were doing their own work20:35
devanandadhellmann: I see. so the removal of the expectation that horizontal teams do (or do not) have to provide guidance to go-lang projects -- is that the sticking point?20:35
dhellmanndevananda : that resulted in "the install guide" being renamed and repurposed, for example, to make space for other guides20:35
clarkbdims: yes it does I dont have to debug your tests when they fail20:35
*** reedip has quit IRC20:35
anteayathere is a lot of repeating of events that goes along with cross project work20:35
johnthetubaguydevananda: dhellmann: well, you end up getting a parallel set of tooling for all the go folks I guess? regardless of who does it20:35
clarkbor teach you how to use sphinx etc20:35
mugsieclarkb: even for some big tent projects - they dont get that20:35
dimsclarkb : interesting distinction20:35
notmorgandevananda: that is part of the deal. also marketing from the foundation and ATC etc conveyance would be excluded20:35
devanandaclarkb: adding a dependency on another language, regardless of whether horizontal teams support that language, or whether the TC has oversight, still results in "me needing to debug it when it fails and affects my gate"20:35
clarkbmugsie: they totally so...20:35
clarkbI spend a large chunj of my time debugging your code20:36
devanandaclarkb: so adding golang _at all_ carries that shared debugging burden20:36
dhellmannjohnthetubaguy : possibly. expectations for something likes i18n might be lower if the project isn't official.20:36
notmorgandhellmann: ++20:36
johnthetubaguydevananda: true20:36
johnthetubaguyoops20:36
devanandaregardless of TC oversight of golang-based projects20:36
dimsclarkb : so we'll let folks use other languages instead of swift in new git repos?20:36
johnthetubaguydhellmann: true20:36
ttxdevananda: infra costs are mostly similar. It just makes it a lot harder to introduce new organizations to "openstack development", for example20:36
*** xyang1 has quit IRC20:36
*** prashantD_ has joined #openstack-meeting20:36
ttxor drive any sort of cross-project initiative20:36
dimsoops golang20:36
*** asettle has quit IRC20:36
devanandattx: ok, thanks. that is what I envision, but not what notmorgan was claiming above20:36
Guest43585why not have two separate object storage projects that implement the object storage API defined by the object storage program?20:37
*** Guest43585 is now known as scotticus20:37
clarkbdims: we already do... java, Go, php, even objective C I tink20:37
dhellmanndevananda : that's a good point. and projects may choose not to depend on unstable unofficial projects for that reason.20:37
devanandascotticus: that's not what was proposed, nor what we're discussing20:37
jbrycenotmorgan: from a practical perspective i would have a hard time feeling ok with excluding talking about something that is a better user experience developed by the same team that develops the rest of the project….20:37
*** claudiub has quit IRC20:37
* dhellmann has to drop off20:37
*** jungleboyj has quit IRC20:38
notmorganjbryce: there is a difference from the standpoint of "this is an openstack project" and "this is a dependency such as mysql"20:38
*** jmckind has quit IRC20:38
notmorganjbryce: my words are insufficient to cover the fidelity there20:38
notmorganjbryce: it may be the best experience to do this with this dependency20:38
notmynamenotmorgan: jbryce: but in this case, you're talking about a required dependency that's developed by the same group of people20:38
devanandanotmyname: * and on the same shared infrastructure :)20:38
notmorgannotmyname: i'm going to go out and say RDBMS is required.20:38
ttxwe are already building a solution out of things that are developed in openstack, or developed in openstack infra but by non-TC-driven teams, and stuff that is developed outside. The question here is where do we draw the line20:39
notmorgannotmyname: and in most cases that is mysql20:39
*** xyang has joined #openstack-meeting20:39
flaper87ttx: or developed by openstack people out side openstack and inside openstack that depend on openstack20:39
*** obondarev has joined #openstack-meeting20:39
*** prashantD__ has quit IRC20:39
flaper87that came out messy but you get my point20:39
mordredwe typically do not depend on external _source_ repositories. we depend on released binaries of things20:39
* flaper87 hopes20:39
clarkb(dont read my comments as anti new lang I enjoy the challenges, but generqlly think that alot of the cross project work is taken for granted when we complwtwly fix the random lang rwlated test thing that broke your tests and ypu didnt notice because we fixed)20:39
mordredso we do not install mysql from source to install openstack20:39
annegentlettx: to me the line is drawn based on priorities, and right now I don't want to prioritize in this language-contributor-centric way.20:39
dimsclarkb :) no worries20:40
mordredwe apt-get/yum install mysql20:40
notmynamebut in this case it's that you've got one group of people working on one thing, but forced to develop it in two separate repos20:40
mordredit's a dependency20:40
*** annemccormick has quit IRC20:40
annegentleclarkb: yes, that.20:40
jrollclarkb: <320:40
ttxnotmyname: yes, that is why I don't like this solution. I just hate it less than the other option20:40
devanandaclarkb: and thank you :)20:40
flaper87annegentle: that pretty much summarizes my comment and concern.20:40
*** xinwu has joined #openstack-meeting20:41
notmynamettx: the other option being golang is ok? (which everyone has agreed is probably the right answer, technically)20:41
*** xyang1 has joined #openstack-meeting20:41
edleafenotmyname: technical merits aren't the only (or most important) thing20:41
devanandattx: if i'm following, this will force openstack projects that want to develop some compoent(s) in golang to build, test, and publish those component(s) independently,so that they can be installed via package managers20:42
ttxnotmyname: the other option being to say that rewriting things in Go is ok across the board, and struggle to drive cross-project goals or specs incrementally more20:42
dimsttx : are we back where we are or do we need a resolution to say - "You can be in big tent only if the project is written in python"?20:42
flaper87the technical merits is not what we're weighting more here, fwiw20:42
dimswe are essentially saying that here20:42
ttxso it's about project-centric pain vs. cross-project pain. You can actually see that in the vote spread20:42
annegentledims: you already don't need that.20:42
edleafedims: or rather, you really need to demonstrate why you *can't* write it in Python20:42
scotticusdims: i feel like i have a solution for that :P20:42
jbrycein a pre-big-tent world, the drawing of the lines would seem more rational to me, but in a post-big-tent world where we’ve already created a lot of confusion externally, this seems like an arbitrary place to deny an official project team’s consensus request, discussed over 3 design summits, on mailing lists, back by data…20:42
thingeedims: I think that would probably be the result of this discussion ... a resolution of some sort20:42
scotticusor proposal.20:42
dimsannegentle : we don't say it explicitly, we should now that we have a decision here20:42
*** xyang has quit IRC20:42
devanandattx: if that's a correct summary, I would restate it as "non-python projects must be developed and released completely independently, and consumed by python projects only in their binary / released / distro'd forms"20:43
*** shaohe_feng has quit IRC20:43
annegentledims: it's that this proposal is written too black-and-white.20:43
dimsthingee ++20:43
mordreddevananda: I believe you stated that very clearly20:43
*** mickeys has quit IRC20:43
flaper87devananda: ++20:43
dimsannegentle : don't know how else it could have been written :(20:43
notmynameannegentle: how so? what shoudl change?20:43
*** shaohe_feng has joined #openstack-meeting20:43
jbrycebig tent was a much bigger move in terms of cross-project impact and we sort of ran headlong into that one. and i thought that was about a shift of “what is openstack” to “who is openstack”20:43
annegentledims: notmyname: More like the considerations upfront than the "contributors are in pain let's alleviate that"20:44
devanandajbryce: ++20:44
*** mickeys has joined #openstack-meeting20:44
ttxjbryce: yes, and "who is openstack" is defined by the practices that we share20:44
*** lblanchard has quit IRC20:44
flaper87ttx: ++20:44
annegentlenotmyname: though what I also would dive into is what was the order of javascript additions?20:44
dimsannegentle : don't know if it would have changed the outcome20:44
jrollblunt question: we've talked a lot about the community impact here; has anyone considered the impact if swift decides to no longer be part of openstack?20:44
*** ayoung has quit IRC20:44
ttxand I feel like this is extending it beyond our capacity to absorb it20:44
annegentlenotmyname: it's possible my history order is incorrect20:44
anteayattx: ++20:44
*** jprovazn has quit IRC20:45
ttxI don't like yes, I don't like no, and I don't like stalling. Someone help me20:45
*** toddjohn has joined #openstack-meeting20:45
scotticusif openstack is wanting to be a series of control planes, shouldn't it just be a collection of API contracts/definitions?20:45
johnthetubaguyttx: it doesn't help, but I am in the same camp right now20:46
mordredscotticus: no20:46
notmynameit's never been that scotticus20:46
mordredscotticus: that was decided a very long time ago20:46
edleafescotticus: no, that was decided a long time ago20:46
mordrededleafe: jinx20:46
edleafemordred: jinx20:46
dimseveryone abstain? (looking at @notmorgan)20:46
flaper87scotticus: tbh, I believe that's quite a loaded question that's not going to help with this discussion but no is the answer20:46
mordredhahaha20:46
notmorgandims: no i don't think adding it is going to work, and i cannot -1 rollcall the addition20:47
* flaper87 hands a cookie to edleafe and mordred20:47
notmynamettx: go to what the data says. we've got data points from swift and definite interest from other projects as well20:47
notmorgandims: i agree strongly with both notmyname and mordred20:47
jbrycei definitely don’t think this is an easy one at all. i know that several have said they don’t like the idea of opening up alternate languages on a case-by-case basis through a tc approval process, but in the situation where there isn’t a clear consensus for one side, maybe that is the right way to start20:47
ttxdims: stalling it would be an option, but I don't feel like it's much better for notmyname than saying no20:47
notmorgandims: and since i cannot and CANNOT make a case here right now, i will support the decision made.20:47
dimsagree20:47
jbrycethe swift team has set a pretty high bar for making that justification20:47
carolbarrettIf the desire is to be able to include add'l languages in the future - why not establish a team to go off and create a proposal for the TC to review/approve by some point in time?20:47
*** banix has quit IRC20:47
edleafejbryce: exactly. Demonstrate why you need Go or anything else20:47
dtroyerI think the TC getting a bit more involved in actually guiding projects is not a bad thing at all20:47
jbryceliterally over more than a year of time, testing, data gathering20:47
*** ihrachys has quit IRC20:48
ttxedleafe: to whom ?20:48
notmorgandtroyer: ++20:48
edleafettx: to the TC20:48
carolbarrettdtroyer ++20:48
edleafettx: that is a technical decision, no?20:48
notmynameedleafe: has swift not done that sufficiently yet?20:48
devanandanotmyname: what would the impact be if the golang parts of swift were released independently and consumed by the rest of swift as system libraries (eg, apt-get install my-faster-swfit-lib) ?20:48
amrithdtroyer ... ++20:48
jbryceand if we can’t feel good about a blanket deicision, maybe we are just not at a point to be able to make the blanket decision and we need to use the tc algorithm like sdague said20:48
*** mickeys has quit IRC20:48
annegentledevananda: apparently there's a document about that20:48
edleafenotmyname: For swift, yes. For Designate, no20:48
*** Apoorva has joined #openstack-meeting20:48
devanandaannegentle: oh?20:48
ttxedleafe: I really fear we'll be back into granting exceptions, and judging projects technical analysis20:48
dimsttx : we can let folks add proposals to cross-project specs and talk about it there and vote on the spec and let some amount of vetting happen20:48
annegentledevananda: I asked something similar and flaper87 and notmyname can send20:49
dimswill give a say to everyone in the process on a specific projects plans20:49
ttxlike swift is pretty clear-cut, I totally get why they need go. What about designate ?20:49
notmynamedevananda: it would be very disruptive for swift contributors. it's a very silly and arbitrary project division. we would likely do our best to keep them as unified as possible20:49
johnthetubaguyttx: maybe that how we don't stall and don't decide right now?20:49
edleafenotmyname: hence the dislike of making all Go (or anything else) accepted by default20:49
devanandanotmyname: ok, thanks20:49
dimsi agree that TC should not be the police. can we use cross project to do that?20:50
* jlvillal wonders if the 'repo' tool would help with multiple project development20:50
notmorgandims: doubtful.20:50
ttxSo... one option would be to give Swift an exception and let them use Go. That is pretty safe. But that makes them special again20:50
anteayadims: noone likes to be the police20:50
edleafettx: yes, but I don't see any way out of that. Unless we're willing to trade community for a bunch of loosely-associated tribes20:50
notmynamehonestly, my biggest challenge, if the TC says "split", as PTL would be to convince swift contributors to not ragequit and find something else to do20:50
flaper87dims: fwiw, I'd prefer the TC to do that in this case20:50
*** adisky has quit IRC20:50
notmorgannotmyname: fair data point20:50
thingeeno, I'm not for special case. I'm really unhappy with the previous special cases.20:50
dtroyerflaper87: ++20:50
flaper87ttx: I honestly would prefer to stay consistent in this case20:50
flaper87so no special case20:51
*** toddjohn has quit IRC20:51
notmynamethingee: I've never asked for this to be a special case for swift :-)20:51
dimsthat's all the ideas i had :)20:51
notmorgani'm at the point that i think (don't hate me) a special case is the only thing i can vote for/against clearly20:51
flaper87time check20:51
thingeeI don't really understand how stalling is going to bring some magic answer to this. It's a difficult decision, but the TC has weighed in on the issue. I think both options suck, but I don't really understand the point of decisions being made if we're not going to go by them.20:51
edleafenotmorgan: agree20:51
mordredthingee: ++20:51
notmorganstalling is not going to answer it20:52
johnthetubaguyso in a years time, we will know the impact it has had on swift20:52
devanandathingee: +120:52
ttxSo I'm open for someone (dims) to propose a mechanism by which we would be able to vet projects individually20:52
*** baoli has quit IRC20:52
dtroyerthingee: ++ please do something, and then follow though on it20:52
notmorganbascially a stall here is a -1 imo20:52
flaper87thingee: ++20:52
dimsttx : very cool. i am open to that20:52
johnthetubaguyits possible swift will build a group of folks that work well in both go and python20:52
*** baoli has joined #openstack-meeting20:52
johnthetubaguyor they might decide to move everything to go20:52
edleafedims: I'd love to help20:52
devanandajohnthetubaguy: it's already been in discussion for a long time, and the impact is becoming clear to that project20:52
ttxbut the current resolution can' tpass at this stage, unless a few people who voted -1 decide to change their vote20:52
dimsedleafe : ack20:52
flaper87dims: ttx until that happens, I think we should stick with what's been voted on20:52
ttxwe have a majority to deny this as it stands20:53
notmorganttx: so i think the answer is no to golang. by the nature of the votes.20:53
*** shaohe_feng has quit IRC20:53
amrithdims, I'm interested in that as well; am happy to help with that proposal.20:53
dimsamrith : ack20:53
thingeeok, so we stall because some member abstain and need more time?20:53
notmynameall the things you're proposing as future things for swift is exactly what's happened in the feature branch. which seemed entirely ok with everyone. and now we want to merge some golang code to master and this is what it's turned in to20:53
*** shaohe_feng has joined #openstack-meeting20:53
dimsnotmyname : i'll need your help as well20:53
*** jaypipes has quit IRC20:53
*** kylek3h has quit IRC20:54
dtroyerdims: me too20:54
notmynamedims: with what now? I missed somethign it seems20:54
dimsnotmyname : "<ttx>So I'm open for someone (dims) to propose a mechanism by which we would be able to vet projects individually"20:54
notmorgannotmyname: basically special case with a clear set of guidelines for anyone wanting it in the future20:54
ttxnotmyname: propose a mechanism for selective access to extra languages20:54
notmorgannotmyname: so it's "here is how you get approval for this"20:54
*** cody-somerville has quit IRC20:54
*** reedip has joined #openstack-meeting20:55
notmynameok20:55
thingeedims: I and other members have expressed we'd not like the TC to be part of that process.20:55
*** reedip has quit IRC20:55
jrollif we assert that allowing go will break the community, and then allow a select few projects to use it, won't that still break the community?20:55
notmynamedoes that imply that the TC is ok with swift's code repo having golang code?20:55
* jroll devil's advocate20:55
ttxsince it looks like we can't resolve ourselves to accept blank approval20:55
notmorganttx: so lets call it "no to golang in this proposal".20:55
devanandajroll: ++20:55
thingeedims: to which others expressed the community should vet20:55
mugsiejroll: ++20:55
dimsthingee : yep, i mentioned that already20:55
thingeewhich I also don't think is productive20:55
*** dprince has quit IRC20:55
annegentlenotmyname: revise not to "go or no go" but to a "here's what we expect from projects when they add a language"20:55
jrollfwiw, I'm on the 'allow' side of this line but don't get a vote20:55
jbrycethingee: i think at least one other tc member said he would like to be20:56
*** baoli has quit IRC20:56
devanandaas far as notmorgan's objection earlier to the TC getting back into the busiess of special casing projects, I agree - TC shouldn't do that20:56
edleafejroll: small cracks are much better than chasms20:56
dimsannegentle : agree20:56
thingeejbryce: I'd hate to repeat pre big tent unproductive discussions.20:56
devanandaedleafe: small cracks widen over time20:56
jrolledleafe: I disagree that it would be any worse allowing anyone to use go20:56
*** baoli has joined #openstack-meeting20:56
carolbarrettIf the TC won't take the role of making decisions about governance across the projects, then who should?20:56
*** jrichli has quit IRC20:56
carolbarrettI thought that was a key part of the TC charter20:56
jrolledleafe: or any "larger of a crack", using your analogy20:56
devanandacarolbarrett: the TC does make decisions across projects20:56
notmynameI seem to be seeing a lot of contradictory things being said. let's special-case. specical-case is bad. no golang. but here's how any new language should be ok20:56
sdaguejroll: as someone who maintains common infrastructure everyone has to use in the gate, it's always worse when people do things differently20:57
notmorganttx: so.20:57
devanandacarolbarrett: but blessing exceptions to its own rules? that's not what the TC is about20:57
notmorganif i am reading this:20:57
ttxnotmorgan: I'm lost20:57
notmorgan1) No to golang, blanket is what i am hearing20:57
notmorganplease correct me if i am wrong20:57
ttxyes, I think that's fair20:57
carolbarrettdevananda: sounds like a cross-project governance decision to me...20:57
jrollsdague: right, so why is allowing select people to do something different better than allowing anyone? if nothing else, allowing anyone will make that special thing less special20:57
jbrycethat’s where the votes on the review sit currently, yes20:57
notmorgan2) dims, notmyname, etc will come up with a guideline to cover access for other languages20:57
dims3 mins time check20:57
notmorgansomething we can judge the projects by20:58
sdaguejroll: I agree, I don't think it's better. And wouldn't really feel any different about it.20:58
mordrednotmorgan: and there are some people who have expressed interest in that, some who have express dislike, and others who have not said anything20:58
notmorgan3) Swift is not being told no to "golang"20:58
*** roxanaghe has joined #openstack-meeting20:58
jrollsdague: fair enough20:58
notmorganmordred: i dis like it a lot20:58
flaper87notmorgan: somehow, I'm afraid that guideline will endup in the TC voting on the same thing we're voting on right here20:58
mordrednotmorgan: right. I'm just annotating20:58
flaper87but I could be wrong, need to read it first20:58
notmorganmordred: ++20:58
ttxnotmorgan: hmm, expand on 3 ?20:58
mugsiewell, i think this is going to end in the current language policy20:58
notmorgan3) swift is being asked to rpopose the way we vette projects - and they'd be the first in the line for it20:58
mordrednotmorgan: like, 2 isn't "we've agreed it's a good idea" - more, 2) may be another avenue worth discussing pending details20:58
ttxbecause we are not really saying yes either ;/20:59
notmynamettx: I feel like this meeting should use executive privilege and keep going for a few minutes to get to a conclusion20:59
mesterynotmorgan: 3 seems to conflict with 120:59
mugsieuse python, want something else go to the TC20:59
notmorgannot being told to "go away and split off"20:59
notmorganexplicitly20:59
notmorganit was more of 2a.20:59
notmorgannot 320:59
*** priteau has quit IRC20:59
*** aysyd has quit IRC20:59
flaper87notmorgan: yeah20:59
notmorganthat was what i read from this meeting.20:59
*** asettle has joined #openstack-meeting20:59
ttxnotmyname: I'm fine with that yes20:59
ttxI think we need a few extra minutes20:59
ttxnext meeting if any could move to another room20:59
notmorgani was just summarizing what i saw in the meeting20:59
ttxalthough that makes me getting drunk to forget all this later away21:00
*** jichen has quit IRC21:00
flaper87notmorgan: sounds like a fair summary to me21:00
anteayattx: I don't see a conflict in the ical schedule21:00
*** xyang has joined #openstack-meeting21:00
flaper87ttx: I'm ahead of you on that ;)21:00
*** ihrachys has joined #openstack-meeting21:00
* flaper87 acts normal21:00
edleafettx: maybe we should all have a few drinks, and then continue :)21:00
johnthetubaguyyeah, I think that is a good summary, and its not self-consistent really, hence the issue21:00
dimswe need to find a reasonable way to vet proposals and make aware of people the deeper issues behind choices21:00
ttxSo, summary21:00
*** saggi has quit IRC21:00
*** baoli has quit IRC21:01
cdentSo, something I'd like to be more clear about: What does swift gain by being in OpenStack?21:01
*** mickeys has joined #openstack-meeting21:01
mordredI think 1 is the only thing that's clear - 2 and 3 are maybes as things to explore to mitigate the results of 121:01
*** baoli has joined #openstack-meeting21:01
mordredsince there are clearly people who are unhappy with 1 - and working to find ways to move forward are the next steps that we are likely to explore21:01
flaper87mordred: right, I believe #2 should be very specific. Something projects would apply for and that defines the process to get a vet21:01
notmorgancdent: i am going to say that is a convo outside the scope of this - please please do not bring that part back in here. Swift has decided they want to be part of openstack, i am willing to view that as face value worthy21:01
ttxWe have a framework for accepting extra languages (and this proposal was made under it) that grant blanket access to extra languages21:01
jbryceto me it sounds like people are generally uncomfortable with both of the blanket options currently on the table, but feel that it’s potentially more harmful to open the “flood gates” to an unlimited set of go proposals across all projects21:01
*** prashantD__ has joined #openstack-meeting21:02
* Rockyg hands mordrd a bottle of single malt21:02
ttxjbryce: yes21:02
flaper87Rockyg: yo, don't forget me !21:02
mordredjbryce: ++21:02
*** JRobinson__ has joined #openstack-meeting21:02
thingeejbryce: +121:02
ttxI think that there is a majority at the TC that is not comfortable with Go blanket access21:02
notmorganjbryce: yes.21:02
* Rockyg passes out glasses21:02
amrithheh heh ... Rockyg gives edleafe butter and mordred single malt :)21:02
edleafejbryce: more than that. When the next new popular language comes up, why say no to that one? And then the next?21:02
ttxThere MAY be room for more selective access, although a lot of us hate what that may mean21:02
* edleafe thinks Rockyg is typing in a pantry21:02
* dims carries the burden21:03
mordredttx: right. but it's possible that that is less bad to people generally21:03
ttxbut that eeds some work, basically a new framework for us to accept language additions21:03
* amrith carries dims21:03
mordreddepending on what magic dims and notmyname write up21:03
devanandajbryce: additionally, some members of the TC do not want the TC to be in the positin of judging which projects are 'worthy' of using golang21:03
ttxmordred: yeah, maybe, devil is in the details21:03
*** shaohe_feng has quit IRC21:03
ttxdevananda: but that still may be the less worse option htere21:03
mordredttx: right. I don't have a strong opinion on that yet, as I haven't spent much time mulling it, personally21:03
jbryceat the same time do most people acknowledge that hummingbird provides a technical improvement for swift?21:03
annegentlecdent: marketing events infra test docs automation debugging frameworks a community and more. but no commas ever. :)21:03
*** doug-fish has quit IRC21:03
dtroyerdevananda: which is too bad because I think that is its job…21:03
*** spotz is now known as spotz_zzz21:03
mordredjbryce: I do not think anyone disputes that21:04
ttxso as far as this patricular resolution is concerned, I think we need to deny it21:04
flaper87jbryce: mordred ++21:04
*** oshidoshi has joined #openstack-meeting21:04
edleafejbryce: I think that's the point: swift demonstrated clearly why it was necessary21:04
devanandadtroyer: we were in that position before the big-tent .. it's not great21:04
annegentlejbryce: that's not the heart of the belief set this change brings21:04
*** shaohe_feng has joined #openstack-meeting21:04
ttxjbryce: I'd agree to that.21:04
flaper87ttx: and wait for what dims and others will work on21:04
*** doug-fish has joined #openstack-meeting21:04
dtroyerdevananda: as implemented then, right.  I think we're worse off now21:04
ttxwhich is why I want to find a way for them to use it without killing the cross-project efforts while doing it21:04
*** ayoung has joined #openstack-meeting21:04
mordredjbryce: the vexxing part is balancing the tech and the non-tech results - since the two aren't directly comparable21:04
devanandadtroyer: constructively, I disagree21:04
*** hashar has quit IRC21:04
*** bswartz1 has joined #openstack-meeting21:05
*** doug-fish has quit IRC21:05
mordredjbryce: if it was all one or all the other, I think this would be much easier to talk about and discuss and whatnot21:05
*** doug-fish has joined #openstack-meeting21:05
notmorganhonestly, i'm willing to special case swift here. provided they work with dims et al on a forward proposal.21:05
* dhellmann returns 21:05
notmorganmordred: also +1000021:05
mordreddhellmann: welcome back!21:05
jbryceand also the swift project team sees a separation of the hummingbird object server implementation from openstack swift bits as a difficult ongoing softward lifecycle model to follow?21:05
*** prashantD_ has quit IRC21:05
notmynamejbryce: yes. absolutely21:05
fungiopenstack/liberasurecode also provides a technical improvement for swift, but is consumed as an unofficial repo. it might help to outline how hummingbird is in a different situation21:06
flaper87jbryce: yup, that was the feedback we got21:06
annegentlejbryce: notmyname to me it's unclear why that separation is untenable21:06
ttxjbryce: and also results in local fragmentation21:06
* mordred is now arrived in his trainstation - y'all enjoy, must AFK21:06
carolbarrettdevananda: Someone has to make decisions, it's a fact of life. The TC is elected to govern the projects. If a person isn't comfortable making decisions, then why would they want to be part of the TC?21:06
jbrycemordred: yeah i get that part. as i said to ttx and thingee earlier i’m torn myself because of it21:06
devanandacarolbarrett: it's not about making decisions or notmaking decisions21:06
anteayamordred: safe travels21:06
annegentlefungi: yes I wondered that as well21:06
*** rubasov has joined #openstack-meeting21:06
notmynamefungi: that's an external project, just like mysql or anything else. but we wanted it to move to openstack/* because frankly lawyers let employees contribute there isntead of some random bitbucket repo21:07
ttxdhellmann: summary is we'll deny this one, and some people will work on a new framework that lets us get the technical benefits without most of the community drawbacks, by rating more selective access21:07
notmynamefungi: and the original authors have about a hundred other thigns on their plate too21:07
funginotmyname: but the swift community is contributing to it?21:07
notmynamefungi: some21:07
notmynamefungi: just like we do to eventlet21:07
carolbarrettdevananda: would be interested to have a follow-up conversation to better understand your viewpoint21:07
fungiare swift team members its primary contributors now?21:07
devanandacarolbarrett: be happy to21:07
ttxs/rating/granting21:08
notmynamefungi: hard to say. the move is recent21:08
carolbarrettdevananda: Thanks21:08
*** merooney has joined #openstack-meeting21:08
*** scotticus has left #openstack-meeting21:08
ttxtimecheck again21:08
*** oshidoshi has quit IRC21:08
notmynamettx: that sounds like restarting this discussion and having it again with some different details21:08
ttxI don't think we'll get any further today21:08
notmorganttx: 8min over. we can continue for a few more.21:08
notmynamefor the record, I think rejecting this proposal is the wrong choice21:08
*** edtubill has joined #openstack-meeting21:09
*** torgomatic has joined #openstack-meeting21:09
ttxnoted21:09
annegentlenotmyname: recorded21:10
notmyname(wanted that on the record so in 5 years when meeting logs are brought up again, it'll be there) ;-)21:10
notmorgannotmyname: hehe21:10
*** xyang has quit IRC21:10
annegentlenotmyname: heh nice21:10
ttxnotmyname: and maybe prove you right21:10
dims:)21:10
*** ebalduf_ has quit IRC21:10
Rockygshould add something as a comment that a different proposal will appearsoon21:10
notmorganttx: if we need to wait 5 years... i'm going to be sad.21:10
ttxok, I'll comment on the review to call it, and close this meeting21:10
ttxunless anyonte has items for open discussion21:10
notmynameyes, one final thing please21:10
*** gordc has left #openstack-meeting21:10
ttx#topic Open discussion21:11
*** openstack changes topic to "Open discussion (Meeting topic: tc)"21:11
ttxnotmyname: go for it21:11
notmynameso fir now, it seems that the swift contribs will continue. and I'll work with dims. and this will be brought up again21:11
*** merooney has quit IRC21:11
*** reedip has joined #openstack-meeting21:11
notmorgannotmyname: that is how i understand it.21:11
notmynameno mandate from the TC that swift needs to split into differnet projects, one in and one out of openstack21:11
EmilienM(just a review request, if TC can approve https://review.openstack.org/#/c/323027/ -- it will help Puppet group to release Newton b1, thanks)21:11
ttxfor the record, I'm really losing sleep over this. Sometimes I wish I cared less21:11
ttxnotmyname: nothing of the sort21:12
devanandacarolbarrett: short version is: judging the "value" or "worthiness" of a project (and the team of developers behind it) is detrimental to community building, and created a lot competition between projects and negative pressure on the TC21:12
dhellmannttx: thanks for the summary, there was a lot of scrollback21:12
dimsnotmyname : no change in status quo21:12
*** edtubill has quit IRC21:12
ttxnotmyname: just no to the resolution as it stands21:12
notmynamethanks for the explicit clarification21:12
*** thorst has quit IRC21:12
dhellmannttx: new topic: I would like to find a way to merge changes to the projects.yaml file that only affect release tags faster, because the week review delay is holding up some project releases.21:13
Rockygnotmyname, so, limbo still....21:13
devanandacarolbarrett: so the TC adopted more objective guidelines for "being one of us" rather than subjective judgements of "being good enough to be one of us"21:13
notmynameRockyg: yeah21:13
*** yamahata has quit IRC21:13
*** thorst has joined #openstack-meeting21:13
carolbarrettdevananda: if we have a set of criteria, then everyone in the community knows the rules...21:13
notmorganEmilienM: proposal works for me btw.21:13
ttxok, thanks everyone, we need to close it.21:13
*** edtubill has joined #openstack-meeting21:13
annegentlethanks ttx21:13
jrollthanks ttx21:13
*** shaohe_feng has quit IRC21:13
anteayattx: thank you21:13
ttxNow let's bring me that bottle of Absinth21:13
annegentlethanks notmyname21:13
*** shaohe_feng has joined #openstack-meeting21:14
devanandacarolbarrett: exactly. I think that's what this discussion has been, in part, about21:14
ttx#endmeeting21:14
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:14
edleafethanks everyone21:14
openstackMeeting ended Tue Jun  7 21:14:02 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-06-07-20.01.html21:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-06-07-20.01.txt21:14
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-06-07-20.01.log.html21:14
RockygThanks!21:14
devanandattx: what's your preferred variety?21:14
amriththx ttx21:14
devanandaof absinthe :)21:14
*** bswartz1 has quit IRC21:14
ttxdevananda: the sort they serve in Prague will do21:14
* fungi assumes "the green kind"21:14
notmorganttx: heh.21:15
devanandahah21:15
fungiresulting in varying degrees of blindness when consumed21:15
*** gmmaha has left #openstack-meeting21:15
*** timburke has left #openstack-meeting21:15
*** reedip has quit IRC21:15
*** carolbarrett has quit IRC21:15
*** yamahata has joined #openstack-meeting21:15
*** merooney has joined #openstack-meeting21:16
*** toddjohn has joined #openstack-meeting21:16
*** toddjohn has quit IRC21:17
*** thorst has quit IRC21:17
*** toddjohn has joined #openstack-meeting21:17
*** lpetrut has quit IRC21:17
*** rossella_s has joined #openstack-meeting21:17
*** claudiub has joined #openstack-meeting21:17
*** rderose has quit IRC21:17
*** merooney has quit IRC21:17
*** HeOS has joined #openstack-meeting21:18
*** ihrachys has quit IRC21:18
*** Leom has quit IRC21:19
*** jmlowe has joined #openstack-meeting21:20
*** ihrachys has joined #openstack-meeting21:20
*** jmlowe has left #openstack-meeting21:21
*** Leo_ has joined #openstack-meeting21:21
*** cody-somerville has joined #openstack-meeting21:21
*** leeantho has quit IRC21:23
*** shaohe_feng has quit IRC21:24
*** Leo_ has quit IRC21:24
*** shaohe_feng has joined #openstack-meeting21:24
*** Leo_ has joined #openstack-meeting21:25
*** obondarev has quit IRC21:25
*** amotoki has joined #openstack-meeting21:27
*** amitgandhinz has quit IRC21:27
*** nmagnezi has quit IRC21:28
*** toddjohn has quit IRC21:28
*** toddjohn has joined #openstack-meeting21:29
*** zeih has joined #openstack-meeting21:30
*** toddjohn has quit IRC21:30
*** toddjohn has joined #openstack-meeting21:30
*** toddjohn has quit IRC21:30
*** ihrachys has quit IRC21:31
*** toddjohn has joined #openstack-meeting21:31
*** ihrachys has joined #openstack-meeting21:31
*** reedip has joined #openstack-meeting21:32
*** ijw has quit IRC21:32
*** ijw has joined #openstack-meeting21:32
*** amotoki has quit IRC21:33
*** prashantD has joined #openstack-meeting21:33
*** ijw has quit IRC21:33
*** rtheis has quit IRC21:34
*** shaohe_feng has quit IRC21:34
*** doug-fish has quit IRC21:34
*** azbiswas has joined #openstack-meeting21:34
*** shaohe_feng has joined #openstack-meeting21:35
*** zeih has quit IRC21:35
*** reedip has quit IRC21:35
*** prashantD__ has quit IRC21:35
*** tpepper has left #openstack-meeting21:36
*** mriedem has quit IRC21:36
*** toddjohn has quit IRC21:36
*** thorst has joined #openstack-meeting21:38
*** cody-somerville has quit IRC21:39
*** doug-fish has joined #openstack-meeting21:40
*** thorst has quit IRC21:42
*** Leo_ has quit IRC21:42
*** Leom has joined #openstack-meeting21:43
*** shaohe_feng has quit IRC21:44
*** doug-fis_ has joined #openstack-meeting21:46
*** merooney has joined #openstack-meeting21:46
*** shaohe_feng has joined #openstack-meeting21:47
*** ihrachys has quit IRC21:48
*** annegentle has quit IRC21:49
*** prashantD_ has joined #openstack-meeting21:49
*** doug-fish has quit IRC21:50
*** doug-fis_ has quit IRC21:51
*** roxanaghe has quit IRC21:52
*** reedip has joined #openstack-meeting21:53
*** prashantD has quit IRC21:53
*** cdent has quit IRC21:53
*** ayoung has quit IRC21:54
*** Sukhdev has joined #openstack-meeting21:54
*** shaohe_feng has quit IRC21:54
*** shaohe_feng has joined #openstack-meeting21:54
*** edtubill has quit IRC21:55
*** reedip has quit IRC21:55
*** cloudtrainme has joined #openstack-meeting21:56
*** Sukhdev has quit IRC21:57
*** edtubill has joined #openstack-meeting21:57
*** spotz_zzz is now known as spotz21:58
*** azbiswas has quit IRC21:58
*** cody-somerville has joined #openstack-meeting21:59
*** cody-somerville has quit IRC21:59
*** cody-somerville has joined #openstack-meeting21:59
*** ihrachys has joined #openstack-meeting21:59
*** nadeem has quit IRC22:00
*** rderose has joined #openstack-meeting22:01
*** karthikp_ has quit IRC22:01
*** Rockyg has quit IRC22:02
*** merooney has quit IRC22:02
*** edtubill has quit IRC22:03
*** asettle has quit IRC22:03
*** sdake_ has joined #openstack-meeting22:03
*** cody-somerville has quit IRC22:03
*** doug-fish has joined #openstack-meeting22:04
*** shaohe_feng has quit IRC22:05
*** Sukhdev has joined #openstack-meeting22:05
*** shaohe_feng has joined #openstack-meeting22:05
*** sdake has quit IRC22:06
*** sdake has joined #openstack-meeting22:06
*** henrynash_ has joined #openstack-meeting22:06
*** rderose has quit IRC22:08
*** weshay has quit IRC22:08
*** ayoung has joined #openstack-meeting22:08
*** doug-fish has quit IRC22:09
*** sdake_ has quit IRC22:10
*** rderose has joined #openstack-meeting22:10
*** ssalagame has quit IRC22:10
*** edtubill has joined #openstack-meeting22:11
*** reedip has joined #openstack-meeting22:11
*** Sukhdev has quit IRC22:12
*** toddjohn has joined #openstack-meeting22:12
*** Sukhdev has joined #openstack-meeting22:12
*** ssalagame has joined #openstack-meeting22:15
*** shaohe_feng has quit IRC22:15
*** shaohe_feng has joined #openstack-meeting22:15
*** reedip has quit IRC22:15
*** Sukhdev has quit IRC22:16
*** singhj has quit IRC22:16
*** Sukhdev has joined #openstack-meeting22:16
*** IlyaG has joined #openstack-meeting22:16
*** toddjohn has quit IRC22:18
*** ijw has joined #openstack-meeting22:19
*** ihrachys has quit IRC22:19
*** ihrachys has joined #openstack-meeting22:20
*** ijw has quit IRC22:21
*** Apoorva_ has joined #openstack-meeting22:21
*** IlyaG has quit IRC22:22
*** ijw_ has joined #openstack-meeting22:23
*** IlyaG has joined #openstack-meeting22:23
*** adiantum has quit IRC22:23
*** rderose has quit IRC22:24
*** salv-orl_ has joined #openstack-meeting22:24
*** Apoorva has quit IRC22:25
*** IlyaG has quit IRC22:25
*** shaohe_feng has quit IRC22:25
*** shaohe_feng has joined #openstack-meeting22:26
*** JRobinson__ is now known as JRobinson__afk22:26
*** Apoorva_ has quit IRC22:26
*** salv-orlando has quit IRC22:27
*** timcline has quit IRC22:27
*** ijw_ has quit IRC22:27
*** timcline has joined #openstack-meeting22:28
*** amitgandhinz has joined #openstack-meeting22:28
*** fawadkhaliq has joined #openstack-meeting22:28
*** Apoorva has joined #openstack-meeting22:29
*** ijw has joined #openstack-meeting22:29
*** mriedem has joined #openstack-meeting22:29
*** amotoki has joined #openstack-meeting22:30
*** Julien-zte has quit IRC22:30
*** Julien-zte has joined #openstack-meeting22:30
*** rbak has quit IRC22:31
*** rbak has joined #openstack-meeting22:31
*** reedip has joined #openstack-meeting22:31
*** bobh has joined #openstack-meeting22:31
*** timcline has quit IRC22:32
*** ihrachys has quit IRC22:32
*** reedip has quit IRC22:32
*** prashantD__ has joined #openstack-meeting22:33
*** ssalagame has quit IRC22:33
*** efried has quit IRC22:34
*** amotoki has quit IRC22:34
*** shaohe_feng has quit IRC22:35
*** shaohe_feng has joined #openstack-meeting22:36
*** tlaxkit has joined #openstack-meeting22:36
*** prashantD_ has quit IRC22:37
*** bobh has quit IRC22:37
*** ihrachys has joined #openstack-meeting22:38
*** ssalagame has joined #openstack-meeting22:39
*** amitgandhinz has quit IRC22:41
*** singhj has joined #openstack-meeting22:41
*** cdub has joined #openstack-meeting22:42
*** JRobinson__afk is now known as JRobinson__22:42
*** sarob has quit IRC22:42
*** cloudtrainme has quit IRC22:43
*** cloudtrainme has joined #openstack-meeting22:43
*** cloudtrainme has quit IRC22:43
*** sdake has quit IRC22:43
*** henrynash_ has quit IRC22:45
*** shaohe_feng has quit IRC22:46
*** singhj has quit IRC22:46
*** shaohe_feng has joined #openstack-meeting22:47
*** reedip has joined #openstack-meeting22:49
*** singhj has joined #openstack-meeting22:54
*** jckasper has quit IRC22:54
*** jckasper has joined #openstack-meeting22:55
*** reedip has quit IRC22:55
*** shaohe_feng has quit IRC22:56
*** cwolferh has quit IRC22:58
*** dimtruck is now known as zz_dimtruck22:59
*** shaohe_feng has joined #openstack-meeting22:59
*** jungleboyj has joined #openstack-meeting22:59
*** jckasper has quit IRC22:59
*** Leom has quit IRC23:01
*** cwolferh has joined #openstack-meeting23:02
*** absubram has quit IRC23:04
*** ihrachys has quit IRC23:05
*** Sukhdev has quit IRC23:05
*** Sukhdev has joined #openstack-meeting23:05
*** longxiongqiu has joined #openstack-meeting23:05
*** shaohe_feng has quit IRC23:06
*** galstrom is now known as galstrom_zzz23:06
*** baoli has quit IRC23:07
*** shaohe_feng has joined #openstack-meeting23:07
*** IanGovett has joined #openstack-meeting23:08
*** edtubill has quit IRC23:08
*** Sukhdev has quit IRC23:09
*** longxiongqiu has quit IRC23:10
*** reedip has joined #openstack-meeting23:12
*** sdake has joined #openstack-meeting23:12
*** roxanaghe has joined #openstack-meeting23:13
*** markvoelker has quit IRC23:13
*** rbak has quit IRC23:14
*** sacharya_ has joined #openstack-meeting23:15
*** sacharya has quit IRC23:15
*** reedip has quit IRC23:15
*** sdague has quit IRC23:16
*** shaohe_feng has quit IRC23:16
*** shaohe_feng has joined #openstack-meeting23:17
*** spotz is now known as spotz_zzz23:17
*** ihrachys has joined #openstack-meeting23:18
*** Sukhdev has joined #openstack-meeting23:19
*** xyang1 has quit IRC23:19
*** IlyaG has joined #openstack-meeting23:20
*** ijw has quit IRC23:21
*** henrynash_ has joined #openstack-meeting23:21
*** ijw has joined #openstack-meeting23:22
*** prashantD_ has joined #openstack-meeting23:22
*** prashantD__ has quit IRC23:25
*** sacharya_ has quit IRC23:25
*** ivar-laz_ has joined #openstack-meeting23:26
*** shaohe_feng has quit IRC23:27
*** shaohe_feng has joined #openstack-meeting23:28
*** IlyaG has quit IRC23:28
*** cwolferh has quit IRC23:29
*** ivar-lazzaro has quit IRC23:29
*** Sukhdev has quit IRC23:30
*** amotoki has joined #openstack-meeting23:30
*** Sukhdev has joined #openstack-meeting23:32
*** IlyaG has joined #openstack-meeting23:33
*** reedip has joined #openstack-meeting23:33
*** prashantD__ has joined #openstack-meeting23:34
*** tochi has joined #openstack-meeting23:34
*** azbiswas has joined #openstack-meeting23:34
*** amotoki has quit IRC23:35
*** reedip has quit IRC23:35
*** IlyaG has quit IRC23:35
*** IlyaG has joined #openstack-meeting23:35
*** Julien-zte has quit IRC23:36
*** ihrachys has quit IRC23:36
*** shaohe_feng has quit IRC23:37
*** prashantD_ has quit IRC23:37
*** shaohe_feng has joined #openstack-meeting23:37
*** fawadkhaliq has quit IRC23:37
*** IlyaG has quit IRC23:37
*** ihrachys has joined #openstack-meeting23:38
*** IanGovett has quit IRC23:38
*** adahms has joined #openstack-meeting23:38
*** amitgandhinz has joined #openstack-meeting23:39
*** IanGovett has joined #openstack-meeting23:40
*** Sukhdev has quit IRC23:40
*** Sukhdev has joined #openstack-meeting23:40
*** salv-orl_ has quit IRC23:43
*** cwolferh has joined #openstack-meeting23:43
*** salv-orlando has joined #openstack-meeting23:43
*** amitgandhinz has quit IRC23:44
*** garthb_ has quit IRC23:44
*** IanGovett has quit IRC23:45
*** henrynash_ has quit IRC23:45
*** sdake has quit IRC23:46
*** tlaxkit has quit IRC23:46
*** shaohe_feng has quit IRC23:47
*** shaohe_feng has joined #openstack-meeting23:48
*** renato_r_ has quit IRC23:51
*** reedip has joined #openstack-meeting23:52
*** fawadkhaliq has joined #openstack-meeting23:52
*** reedip has quit IRC23:55
*** thorst has joined #openstack-meeting23:56
*** fawadkhaliq has quit IRC23:56
*** cdub has quit IRC23:56
*** thorst has quit IRC23:56
*** thorst has joined #openstack-meeting23:57
*** shaohe_feng has quit IRC23:57
*** jungleboyj has quit IRC23:58
*** shaohe_feng has joined #openstack-meeting23:58

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