Tuesday, 2016-05-24

*** zhurong has joined #openstack-meeting00:00
*** shaohe_feng has quit IRC00:00
*** jhesketh_ is now known as jhesketh00:02
*** alexpilotti has quit IRC00:02
*** shaohe_feng has joined #openstack-meeting00:03
*** zhurong has quit IRC00:05
*** thinrichs has joined #openstack-meeting00:06
*** spzala has joined #openstack-meeting00:07
*** mtanino has joined #openstack-meeting00:08
*** timcline has joined #openstack-meeting00:09
*** gyee has quit IRC00:10
*** shaohe_feng has quit IRC00:11
*** roxanagh_ has joined #openstack-meeting00:11
*** shaohe_feng has joined #openstack-meeting00:12
*** salv-orl_ has quit IRC00:13
*** toddjohn has quit IRC00:14
*** timcline has quit IRC00:14
*** spzala has quit IRC00:14
*** roxanagh_ has quit IRC00:16
*** rderose has joined #openstack-meeting00:17
*** gatekeep has joined #openstack-meeting00:19
*** devananda has joined #openstack-meeting00:19
*** cwolferh has joined #openstack-meeting00:19
*** mrda has joined #openstack-meeting00:19
*** samueldmq has joined #openstack-meeting00:19
*** rcarrillocruz has joined #openstack-meeting00:19
*** d0ugal has joined #openstack-meeting00:19
*** bkero has joined #openstack-meeting00:19
*** vdrok has joined #openstack-meeting00:19
*** patrickeast has joined #openstack-meeting00:20
*** aranjan has quit IRC00:20
*** bryan_att has joined #openstack-meeting00:20
*** aranjan has joined #openstack-meeting00:20
*** jamesdenton has quit IRC00:21
*** shaohe_feng has quit IRC00:21
*** ildikov has joined #openstack-meeting00:21
*** shaohe_feng has joined #openstack-meeting00:21
*** aranjan has quit IRC00:21
*** CaptTofu has joined #openstack-meeting00:22
*** aranjan has joined #openstack-meeting00:22
*** aranjan_ has joined #openstack-meeting00:23
*** aranjan has quit IRC00:23
*** aranjan_ has quit IRC00:23
*** aranjan has joined #openstack-meeting00:24
*** aranjan has quit IRC00:24
*** bobh has quit IRC00:25
*** aranjan has joined #openstack-meeting00:25
*** mickeys has quit IRC00:25
*** r-mibu has quit IRC00:25
*** r-mibu has joined #openstack-meeting00:26
*** mickeys has joined #openstack-meeting00:28
*** aranjan has quit IRC00:29
*** sarob has quit IRC00:30
*** shaohe_feng has quit IRC00:31
*** shaohe_feng has joined #openstack-meeting00:32
*** baoli has quit IRC00:32
*** mickeys has quit IRC00:33
*** baoli has joined #openstack-meeting00:33
*** Sukhdev has quit IRC00:33
*** baoli has quit IRC00:33
*** baoli has joined #openstack-meeting00:34
*** dimtruck is now known as zz_dimtruck00:34
*** mickeys has joined #openstack-meeting00:35
*** mickeys has quit IRC00:35
*** mickeys has joined #openstack-meeting00:35
*** Julien-zte has joined #openstack-meeting00:38
*** bobh has joined #openstack-meeting00:38
*** shaohe_feng has quit IRC00:41
*** shaohe_feng has joined #openstack-meeting00:42
*** hoangcx has joined #openstack-meeting00:42
*** sheel has joined #openstack-meeting00:43
*** hoangcx has left #openstack-meeting00:43
*** fitoduarte has quit IRC00:46
*** thinrichs has left #openstack-meeting00:49
*** zz_dimtruck is now known as dimtruck00:49
*** vishwanathj has quit IRC00:50
*** Qiming has joined #openstack-meeting00:52
*** shaohe_feng has quit IRC00:52
*** mickeys has quit IRC00:52
*** ssalagame has quit IRC00:54
*** rfolco has quit IRC00:54
*** Sukhdev has joined #openstack-meeting00:54
*** shaohe_feng has joined #openstack-meeting00:54
*** ssalagame has joined #openstack-meeting00:54
*** mickeys has joined #openstack-meeting00:55
*** mbound has joined #openstack-meeting00:55
*** adahms has quit IRC00:55
*** sams-gleb has joined #openstack-meeting00:56
*** rfolco has joined #openstack-meeting00:56
*** ekcs has quit IRC00:58
*** mickeys has quit IRC00:59
*** mbound has quit IRC00:59
*** wznoinsk has joined #openstack-meeting00:59
*** xingchao has joined #openstack-meeting01:00
*** gongysh has quit IRC01:02
*** shaohe_feng has quit IRC01:02
*** shaohe_feng has joined #openstack-meeting01:02
*** sams-gleb has quit IRC01:03
*** spotz_ is now known as spotz_zzz01:04
*** mtanino has quit IRC01:05
*** toddjohn has joined #openstack-meeting01:08
*** rderose has quit IRC01:10
*** timcline has joined #openstack-meeting01:10
*** zhurong has joined #openstack-meeting01:11
*** shashank_hegde has quit IRC01:11
*** shaohe_feng has quit IRC01:12
*** sridhar_ram1 has quit IRC01:12
*** shaohe_feng has joined #openstack-meeting01:13
*** karthikp_ has quit IRC01:14
*** donghao has joined #openstack-meeting01:14
*** timcline has quit IRC01:15
*** karthikp_ has joined #openstack-meeting01:16
*** cody-somerville has joined #openstack-meeting01:17
*** cody-somerville has quit IRC01:17
*** cody-somerville has joined #openstack-meeting01:17
*** anteaya has quit IRC01:18
*** SumitNaiksatam has joined #openstack-meeting01:18
*** SumitNaiksatam has left #openstack-meeting01:19
*** spzala has joined #openstack-meeting01:19
*** llu has joined #openstack-meeting01:19
*** dmacpher-afk is now known as dmacpher01:21
*** cody-somerville_ has joined #openstack-meeting01:21
*** toddjohn has quit IRC01:22
*** toddjohn has joined #openstack-meeting01:22
*** shaohe_feng has quit IRC01:22
*** cody-somerville has quit IRC01:23
*** shaohe_feng has joined #openstack-meeting01:23
*** zhangshuai has joined #openstack-meeting01:24
*** ssalagame has quit IRC01:25
*** RuiChen has joined #openstack-meeting01:26
*** toddjohn has quit IRC01:28
*** Julien-zte has quit IRC01:28
*** mtanino has joined #openstack-meeting01:30
*** pzchen has joined #openstack-meeting01:31
*** shaohe_feng has quit IRC01:33
*** zhhuabj_ has quit IRC01:34
*** asselin has joined #openstack-meeting01:34
*** shaohe_feng has joined #openstack-meeting01:34
*** Apoorva has quit IRC01:34
*** mtanino has quit IRC01:35
*** cody-somerville_ has quit IRC01:35
*** rderose has joined #openstack-meeting01:36
*** cdelatte has quit IRC01:37
*** asselin has quit IRC01:38
*** manikanta_ has joined #openstack-meeting01:40
*** Sukhdev has quit IRC01:40
*** yamahata has quit IRC01:42
*** karthikp_ has quit IRC01:43
*** manikanta_ has quit IRC01:43
*** shaohe_feng has quit IRC01:43
*** tfukushima has joined #openstack-meeting01:43
*** shaohe_feng has joined #openstack-meeting01:44
*** zhhuabj_ has joined #openstack-meeting01:46
*** ivar-laz_ has joined #openstack-meeting01:46
*** cody-somerville_ has joined #openstack-meeting01:46
*** gongysh has joined #openstack-meeting01:46
*** eric_lopez has quit IRC01:48
*** jamesmcarthur has joined #openstack-meeting01:49
*** ivar-lazzaro has quit IRC01:49
*** liamji has joined #openstack-meeting01:49
*** ivar-laz_ has quit IRC01:50
*** gongysh has quit IRC01:51
*** amitgandhinz has joined #openstack-meeting01:52
*** spzala has quit IRC01:52
*** s3wong has quit IRC01:53
*** pzchen has quit IRC01:53
*** shaohe_feng has quit IRC01:53
*** shaohe_feng has joined #openstack-meeting01:54
*** pzchen has joined #openstack-meeting01:54
*** karthikp_ has joined #openstack-meeting01:55
*** cody-somerville_ is now known as cody-somerville01:56
*** cody-somerville has joined #openstack-meeting01:57
*** amitgandhinz has quit IRC01:58
*** bobh has quit IRC01:59
*** jamesmcarthur has quit IRC01:59
*** karthikp_ has quit IRC01:59
*** sams-gleb has joined #openstack-meeting02:00
*** IlyaG has quit IRC02:00
*** shaohe_feng has quit IRC02:03
*** shaohe_feng has joined #openstack-meeting02:04
*** jamesmcarthur has joined #openstack-meeting02:06
*** fnaval_ has quit IRC02:08
*** sams-gleb has quit IRC02:08
*** timcline has joined #openstack-meeting02:11
*** yamahata has joined #openstack-meeting02:11
*** samP_ has joined #openstack-meeting02:13
*** shaohe_feng has quit IRC02:14
*** jamesmcarthur has quit IRC02:14
*** unicell1 has quit IRC02:14
*** thorst_ has quit IRC02:14
*** thorst_ has joined #openstack-meeting02:15
*** penick has quit IRC02:15
*** timcline has quit IRC02:16
*** fnaval has joined #openstack-meeting02:17
*** shaohe_feng has joined #openstack-meeting02:17
*** nelsnels_ has joined #openstack-meeting02:17
*** qwebirc31154 has joined #openstack-meeting02:17
*** samP_ has quit IRC02:18
*** nelsnelson has quit IRC02:18
*** Qiming has quit IRC02:18
qwebirc31154startmeeting higgins02:18
*** qwebirc31154 has left #openstack-meeting02:18
*** Qiming has joined #openstack-meeting02:19
*** sacharya has joined #openstack-meeting02:19
*** qwebirc91159 has joined #openstack-meeting02:20
*** fnaval_ has joined #openstack-meeting02:20
*** jckasper has quit IRC02:21
*** fnaval has quit IRC02:21
*** jckasper has joined #openstack-meeting02:21
*** markvoelker has quit IRC02:21
*** ljxiash has joined #openstack-meeting02:21
*** jamesmcarthur has joined #openstack-meeting02:22
*** jckasper has quit IRC02:22
*** jckasper has joined #openstack-meeting02:22
*** MaxPC has joined #openstack-meeting02:22
*** thorst_ has quit IRC02:23
*** shaohe_feng has quit IRC02:24
*** toddjohn has joined #openstack-meeting02:24
*** shaohe_feng has joined #openstack-meeting02:25
*** samP_ has joined #openstack-meeting02:25
*** qwebirc91159 has quit IRC02:25
*** cyli_ has joined #openstack-meeting02:26
*** spzala has joined #openstack-meeting02:26
*** spzala has quit IRC02:26
*** spzala has joined #openstack-meeting02:27
*** licy has joined #openstack-meeting02:27
*** dmorita_ has quit IRC02:28
*** samP_ has left #openstack-meeting02:28
*** samP_ has joined #openstack-meeting02:29
*** toddjohn has quit IRC02:29
*** samP_ has left #openstack-meeting02:29
*** Qiming has quit IRC02:30
*** ljxiash has quit IRC02:30
*** samP_ has joined #openstack-meeting02:31
*** cyli_ has quit IRC02:31
*** ljxiash has joined #openstack-meeting02:31
*** spzala has quit IRC02:31
licyHELP02:32
*** shaohe_feng has quit IRC02:34
*** jamesmcarthur has quit IRC02:34
*** shaohe_feng has joined #openstack-meeting02:34
*** samP_ has left #openstack-meeting02:35
*** samP_ has joined #openstack-meeting02:35
*** pgreg has joined #openstack-meeting02:35
*** ljxiash has quit IRC02:35
*** pgreg has quit IRC02:36
*** qwebirc20589 has joined #openstack-meeting02:36
*** pgreg has joined #openstack-meeting02:37
*** salv-orlando has joined #openstack-meeting02:38
*** qwebirc20589 has quit IRC02:38
*** jamesmcarthur has joined #openstack-meeting02:39
*** xingchao has quit IRC02:41
*** bobh has joined #openstack-meeting02:41
*** licy has left #openstack-meeting02:41
*** jamesmcarthur has quit IRC02:42
*** qwebirc87082 has joined #openstack-meeting02:43
*** salv-orlando has quit IRC02:43
*** qwebirc87082 has left #openstack-meeting02:43
*** ljxiash has joined #openstack-meeting02:43
*** cyli_ has joined #openstack-meeting02:44
*** shaohe_feng has quit IRC02:44
*** shaohe_feng has joined #openstack-meeting02:45
*** Qiming has joined #openstack-meeting02:46
*** xingchao has joined #openstack-meeting02:47
*** enriquetaso has quit IRC02:48
*** jckasper has quit IRC02:48
*** dmorita has joined #openstack-meeting02:48
*** cyli_ has quit IRC02:48
*** jckasper has joined #openstack-meeting02:49
*** chuanyun_li has joined #openstack-meeting02:49
*** jckasper has quit IRC02:50
*** jckasper has joined #openstack-meeting02:50
*** karthikp_ has joined #openstack-meeting02:51
*** xingchao has quit IRC02:52
*** eric_lopez has joined #openstack-meeting02:52
*** dmorita has quit IRC02:53
*** amitgandhinz has joined #openstack-meeting02:54
*** sudipto has joined #openstack-meeting02:54
*** shaohe_feng has quit IRC02:55
*** shaohe_feng has joined #openstack-meeting02:55
*** bobh has quit IRC02:55
*** jamesmcarthur has joined #openstack-meeting02:55
*** aimon has quit IRC02:56
*** karthikp_ has quit IRC02:56
*** hongbin has joined #openstack-meeting02:56
*** epico has joined #openstack-meeting02:56
*** Qiming has quit IRC02:56
*** shu-mutou has joined #openstack-meeting02:57
*** chuanyun_li has quit IRC02:58
*** mkrai has joined #openstack-meeting02:58
*** haiwei_ has joined #openstack-meeting02:59
*** yuanying has joined #openstack-meeting02:59
*** amitgandhinz has quit IRC02:59
*** enriquetaso has joined #openstack-meeting02:59
*** jamesmcarthur has quit IRC02:59
hongbin#startmeeting higgins03:00
*** MaxPC has quit IRC03:00
openstackMeeting started Tue May 24 03:00:05 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-05-24_0300_UTC Today's agenda03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: higgins)"03:00
*** WangJian has joined #openstack-meeting03:00
*** Vivek___ has joined #openstack-meeting03:00
yuanyinghi03:00
*** karthikp_ has joined #openstack-meeting03:00
haiwei_hi03:00
hongbinhey03:00
shu-mutouo/03:00
sheelhi03:01
mkraio/03:01
Vivek___o/03:01
*** Sukhdev has joined #openstack-meeting03:01
*** Namrata has joined #openstack-meeting03:01
hongbinpause a few seconds for other attendees03:01
*** karthikp_ has quit IRC03:02
*** spzala has joined #openstack-meeting03:02
sudiptoo/03:02
*** shashank_hegde has joined #openstack-meeting03:02
*** jamesmcarthur has joined #openstack-meeting03:03
hongbinThanks for joining the meeting yuanying haiwei_ shu-mutou sheel mkrai Vivek___ sudipto03:03
hongbin#topic Introductions (For attendees not present on the first meeting)03:03
*** openstack changes topic to "Introductions (For attendees not present on the first meeting) (Meeting topic: higgins)"03:03
NamrataO/03:03
hongbinNamrata: hey03:03
WangJianhi03:04
hongbinAnyone want to introduce themselves?03:04
*** yanyanhu has joined #openstack-meeting03:04
*** timcline has joined #openstack-meeting03:04
yanyanhuhi, sorry, I'm late03:05
hongbinyantarou: NP03:05
*** shaohe_feng has quit IRC03:05
*** namrata_ has joined #openstack-meeting03:05
*** baoli has quit IRC03:05
hongbinI didn't see Vivek___ sudipto WangJian  at the first meeting03:05
sudiptoHi, I am contributor to nova atm (and glance) and i am also looking at hyper/kubernetes as my area of interest.03:05
*** sams-gleb has joined #openstack-meeting03:05
WangJianI am from China, and I working in Huawei. Very glad to work with you guys03:06
hongbinWelcome sudipto WangJian03:06
*** shaohe_feng has joined #openstack-meeting03:06
haiwei_welcome03:06
sudiptoworking for Linux Technology Center/IBM India.03:06
*** sajeesh has quit IRC03:06
sudiptothanks hongbin03:06
Vivek___Hi Hongbin, I was there but i was bit late in that meeting.03:06
hongbinVivek___: Oh, sorray about that03:06
*** Namrata has quit IRC03:07
hongbinAnyone else want to introduce themselves?03:07
*** Qiming has joined #openstack-meeting03:07
Vivek___Hi, I am Vivek Jain an individual contributor based in  India.03:07
hongbinVivek___: Welcome to the Higgins team03:07
mkraiWelcome everyone!03:07
hongbin#topic Announcements03:07
*** openstack changes topic to "Announcements (Meeting topic: higgins)"03:07
*** spzala has quit IRC03:08
hongbinThis is the second Higgins team meeting. We will hold a team meeting at this time every weeks.03:08
sheel👍03:08
hongbinHope this is a good time for everyone03:08
*** erlon_ has joined #openstack-meeting03:08
hongbin#topic Review Action Items03:08
*** openstack changes topic to "Review Action Items (Meeting topic: higgins)"03:08
hongbin1. hongbin fill FAQ to explain the relationship between Magnum and Higgins (DONE)03:08
hongbin#link https://wiki.openstack.org/wiki/Higgins#Frequently_Asked_Questions03:08
*** timcline has quit IRC03:09
mkraiThanks hongbin for this one. It is really helpful03:09
*** yamamot__ has joined #openstack-meeting03:09
mkrai+103:09
hongbinmy pleasure03:09
sheelawesome..03:09
hongbinPlease feel free to edit the answers if you have anything to add to revise03:09
hongbinOr feel free to discuss with me if you have any inputs03:10
*** rfolco has quit IRC03:10
hongbin2. hongbin schedule a weekly meeting for Higgins (DONE)03:10
hongbin#link https://review.openstack.org/#/c/318335/ meeting at every Tuesday 0300UTC03:10
*** klkumar has joined #openstack-meeting03:10
hongbinAs announced, we will have a weekly team meeting03:10
hongbinThis conclude the review action items03:11
hongbinAny comment for that?03:11
hongbin#topic Drive consensus on project scope03:11
*** openstack changes topic to "Drive consensus on project scope (Meeting topic: higgins)"03:11
hongbin#link https://etherpad.openstack.org/p/container-management-service etherpad for collaborating on project requirements03:11
hongbinAt the first meeting, we discussed a little about the project scope.03:11
hongbinWe had everyone write down their preference in the etherpad above.03:11
hongbinRight now, we need to decide based on the proposed requirements.03:12
hongbinFirst, I will pause a few minutes for everyone review the etherpad for recap.03:12
hongbinAt the bottom of the etherpad, there is a decision session. We are going to discuss each bullet in that session.03:12
*** sams-gleb has quit IRC03:13
*** flwang has joined #openstack-meeting03:13
flwango/03:13
hongbinflwang: hey03:13
flwanghongbin: hey hongbin03:13
hongbinflwang: we are reviewing the etherpad03:13
flwangsorry for the late03:14
hongbinflwang: NP03:14
hongbinflwang: #link https://etherpad.openstack.org/p/container-management-service03:14
flwanghongbin: oh, the original one03:14
*** jamesmcarthur has quit IRC03:14
hongbinyes03:14
*** jamesmcarthur has joined #openstack-meeting03:15
*** roxanagh_ has joined #openstack-meeting03:15
*** shaohe_feng has quit IRC03:15
hongbinIf everyone finish the reading, we are going to debate the descision03:15
*** Julien-zte has joined #openstack-meeting03:16
*** shaohe_feng has joined #openstack-meeting03:16
*** cody-somerville has quit IRC03:16
yanyanhuI'm done03:16
mkraiMe too03:17
sheelyep03:17
yuanyingok03:17
WangJiandone03:17
Qimingo/03:17
hongbinOK. Let's discuss the first item03:17
hongbin1. Container Abstraction03:17
hongbinQiming: hey03:17
hongbinIn the proposed project scope, there are several proposed container technologies03:18
hongbinFirst, there are container runtimes, i.e. docker, clear container03:19
Qimingyes, different layers / approaches for abstraction03:19
hongbinSecond, there are COEs, i.e. kubernetes, docker swarm, apache mesos03:19
*** jckasper has quit IRC03:19
hongbinWe need to decide which one to integrate03:19
*** zhhuabj_ has quit IRC03:19
hongbinAt least, decide which one to start with03:19
mkraiDocker, rocket and clearcontainer03:19
hongbinOpinions?03:19
mkraiDocker will be our first phase implementation.03:20
yanyanhuIMHO, docker should be the first one03:20
QimingI'd vote for basic container abstraction03:20
*** roxanagh_ has quit IRC03:20
mkraiI have already posted a patch for docker03:20
Qimingleave the proxying for other COEs a future decision03:20
mkrai+1 for docker03:20
yanyanhuagree03:20
mkraiYes Qiming agree03:20
hongbinIt looks everyone agree to start with docker03:20
hongbinAny opposing point of view?03:20
*** jamesmcarthur has quit IRC03:20
*** jckasper has joined #openstack-meeting03:21
*** thorst_ has joined #openstack-meeting03:21
sudipto+1 for docker03:21
haiwei_agree03:21
hongbin#agreed pick docker as the first integrated container runtime03:21
WangJiandocker +103:21
*** fnaval has joined #openstack-meeting03:21
flwang+103:21
shu-mutou+1 for docker03:21
flwangwe should use #vote03:21
hongbinFor the second item, container management03:21
hongbinflwang: oh, yes we can03:21
*** dneary has quit IRC03:21
Vivek___+103:22
hongbineveryone want to vote?03:22
Qiming+1 for docker, but I'd propose we do it by separating the interface and the mechanism (driver)03:22
*** markvoelker has joined #openstack-meeting03:22
namrata_+103:22
sudiptoQiming, +103:22
*** manikanta_ has joined #openstack-meeting03:22
mkraiI guess it is clear03:22
hongbinflwang: It looks everyone agree on docker, a vote is not necessary03:22
mkraiso vote is not needed03:22
flwanghongbin: hah, ok03:22
hongbinOK. Go to the second item03:23
yanyanhumaybe we can use vote for next topic  :)03:23
*** pzchen has quit IRC03:23
hongbinThere are four proposed items03:23
hongbin1. Basic container operations (i.e. CRUD)03:23
hongbin2. Advanced operations03:23
hongbin3. Scheduling containers03:24
hongbin4. Nested containers (containers on Nova instances) VS non-nested containers (containers on compute hosts)03:24
*** chuanyunli has joined #openstack-meeting03:24
hongbinAt the fist meeting, we agreed on #103:24
mkraiYes03:24
*** fnaval_ has quit IRC03:24
hongbinSo, I guess we don't need to debate it further?03:24
flwanghongbin: yes :)03:24
mkraiCorrect03:24
yanyanhuthink so03:24
haiwei_yes03:24
hongbinHow about #203:24
sudiptohongbin, i read through the first meeting logs, i was wondering - will there be focus on isolated/clear containers as well?03:25
yanyanhuI suggest we leave it to upper layer services03:25
hongbinShould Higgins support advanced operations (i.e. keep container alive)03:25
*** zhhuabj_ has joined #openstack-meeting03:25
mkraiSure we will be supporting advance features in future but I guess it is not the right time to discuss03:25
mkraisudipto, Yes we are planning to03:25
hongbinsudipto: I believe there will be a focus (personal opinion)03:25
haiwei_agree mkrai03:25
yuanying+1 mkrai03:25
yanyanhuat least in current stage, we should focus on primitive support03:25
*** shaohe_feng has quit IRC03:25
*** toddjohn has joined #openstack-meeting03:26
mkraiYes hongbin we should support03:26
*** shaohe_feng has joined #openstack-meeting03:26
sudiptohongbin, some of the workflow for hyper type containers actually use qemu - which kind of overlaps with nova's code. However, that is probably a topic for discussion later.03:26
hongbinsudipto: ack03:27
hongbinI guess everyone don't want to support advanced operations?03:27
*** markvoelker has quit IRC03:27
*** roxanagh_ has joined #openstack-meeting03:27
yanyanhuyes, at least not now :)03:27
haiwei_no now03:27
hongbinThen, I am going to cross it out of the list03:27
*** jamesmcarthur has joined #openstack-meeting03:27
sheelhongbin: should be supproted but in future after basic setup ready03:27
QimingI'd vote for keeping the scope limited for now, for several reasons: 1. personally, I'd like to view  Higgins a 'container' flavor of nova, just like Ironic, a 'bare-metal' flavor of nova, leaving upper layer orchestration to other projects; 2. lessons learned from the past, when you put something there public, you will NEVER get a chance to deprecate it ...03:27
mkraihongbin, I think you can mark it for later03:27
*** thorst_ has quit IRC03:28
hongbin#agreed Higgins won't consider support advanced container operation at short time03:28
hongbinQiming: +103:28
hongbin#3 support scheduling for containers03:28
hongbinI think this is a must?03:28
mkraiYes a must03:28
yanyanhuyea03:29
mkraiAnd how we are going to do it in first phase?03:29
haiwei_should we consider No4 first?03:29
hongbinI think we can implement a very simple scheduler to start03:29
*** sdake_ has quit IRC03:29
sudiptohongbin, mkrai when we start supporting scheduling for containers - what happens when we get to the COEs (i believe at that time, we would want to be a passthrough?)03:29
hongbinFor example, randomly picking a host03:29
Qimingwe got to decide where to launch a container, but we should copy the interface design from nova03:30
hongbinsudipto: We can decide it later, once we want to support COEs. I guess we can pass through03:30
mkraiYes sudipto03:30
hongbinQiming: Yes, copying nova scheduler is an option03:30
Qiminga simple, naive scheduler is okay for the near future, but in the long run, we are not supposed to reinvent a scheduler03:30
mkraiAnd I think it will be better03:31
hongbinQiming: nova is going to split out their scheduler into a separated project03:31
sheelQiming: +103:31
Qimingyes, so I said 'copy the interface design', not the code03:31
hongbinQiming: I see03:31
*** toddjohn has quit IRC03:32
mkraiYes because our use case may vary03:32
flwangand inintially, we just need to support a roundrobin and add more scheduler driver later03:32
sudiptohongbin, mkrai - while designing the scheduler - i am bit concerned about the metrics that would be used here. Unlike nova, we should start with a pluggable architecture there - that is - there could be various sources of metrics generation and not dependence on another higgins component IMHO.03:32
Qimingflwang, +103:32
janonymous_Hi03:33
haiwei_flwang +103:33
hongbinsudipto: Yes, we could discuss the scheduler implementation details later03:33
sheelflwang:  right03:33
sudiptohongbin, sure.03:33
flwangwe don't really need a fancy scheduler for now, which could be done later after we figure out what's the metrics we really care about03:33
mkraiIt is a huge topic03:33
hongbinRight now, we just need to decide what to do, not necessary how to do it03:33
sudiptohongbin, mkrai sure.03:34
flwangi'm thinking higgins cases maybe different from nova's03:34
hongbin#4 Support nested VM (VS none-nested VM)03:34
*** jamesmcarthur has quit IRC03:34
*** xingchao has joined #openstack-meeting03:34
flwangkeep it simple03:35
*** iyamahat has quit IRC03:35
hongbinShould we start with nested VM use case, or non-nested VM use case, or both?03:35
mkraiNon nested03:35
sudiptomkrai, +103:35
Vivek___+103:35
Qimingso the todo could be: 1. an scheduler interface design (copy from nova). 2. a dummy scheduler plugin doing things like round-robin03:35
yanyanhumaybe we should abstract the host from the beginning?03:35
yuanyingnested VM means, user managed  VM ?03:35
hongbinQiming: +103:35
*** unicell has joined #openstack-meeting03:35
hongbinyuanying: Nested VM means running containers in VMs03:35
hongbinyuanying: like what Magnum is doing03:36
*** arvinc_ has joined #openstack-meeting03:36
yanyanhucontainers -> abstracted host -> VM/Baremetal?03:36
*** shaohe_feng has quit IRC03:36
Qimingyanyanhu, +103:36
*** shaohe_feng has joined #openstack-meeting03:36
mkraiyanyanhu, And compute hosts also03:36
hongbinyanyanhu: we have a topic later to discuss host management03:36
yanyanhuhongbin, ok03:36
hongbinI guess everyone agree to start with non-nested VM use case03:36
hongbinAny opposing point of view?03:37
haiwei_agree03:37
WangJianagree03:37
janonymous_+103:37
mkrai+103:37
yanyanhu+103:37
shu-mutou+103:37
hongbin#agreed support non-nested container use case as a start03:37
Vivek___+103:37
sheelagree03:37
namrata_+103:37
*** JRobinson__ is now known as JRobinson__afk03:37
hongbin#3 container composition03:37
hongbinShould we support docker-compose like feature03:38
hongbinopinions?03:38
*** zhangshuai_ has joined #openstack-meeting03:38
yuanyingI read this document, https://coreos.com/rkt/docs/latest/running-lkvm-stage1.html03:38
Qimingem ... sounds like a Heat job03:38
yanyanhu+103:38
*** _alastor__ has quit IRC03:38
flwanghongbin: i vote yes03:39
yuanyingThis document suppose how to use hyper/clear container technology03:39
flwangthink it's a common simple tool for developer03:39
*** xingchao has quit IRC03:39
Qimingyes, it is simple03:39
Qimingbut maybe too simple to meet user requirements03:39
mkraiyes we should03:39
*** Douhet has quit IRC03:39
Qimingsuppose you want to make some changes to the containers deployed03:39
mkraiyuanying, Yes rocket supports clear container03:39
yanyanhuI guess user can use heat to achieve this goal03:39
sudiptoQiming, +1 -03:40
Qiminghow would you do that? change the yml file and run 'docker-compose' again?03:40
yanyanhuso we may need to consider its relationship with heat template03:40
mkraithe same way docker does it?03:40
mkraiWhy heat here? yanyanhu03:40
*** tochi has quit IRC03:40
*** manikanta_ has quit IRC03:41
Qiminga structured definition or a delcarative language helps simplify the initial deployment, but it is not a great tool for daily operations03:41
yanyanhumkrai, because heat is orchestration service, so deployment is part of its scope03:41
yanyanhuso there should be overlap here I think03:41
*** banix has quit IRC03:41
*** Douhet has joined #openstack-meeting03:41
hongbinIt looks there are two opposing point of view03:42
*** zhangshuai has quit IRC03:42
hongbin1. It belongs to higgins03:42
mkraiyanyanhu, you mean deployment of containers?03:42
hongbin2. It belongs to Heat03:42
haiwei_yanyanhu, you mean Heat can do the things what docker-compose does?03:42
*** yuval has joined #openstack-meeting03:42
yanyanhumkrai, could be03:42
yanyanhuand also the app/service upon container03:42
*** yuval has left #openstack-meeting03:42
hongbinOK. I guess it is better to table this one03:42
hongbinWe can discuss it in the ML instead03:43
yanyanhuuser can use heat template to describe this kind of deployment if they will I think03:43
Qimingyes, hongbin, we don't need to rush to a conclusion here03:43
hongbinQiming: ack03:43
hongbinNext one03:43
hongbinConainer host management03:44
QimingI'm also thinking of other use cases, where users want to model things in TOSCA03:44
yanyanhumkrai,  maybe my misunderstanding, but I hope we can have a more thorough discussion for this topic :)03:44
*** baoli has joined #openstack-meeting03:44
mkraiYes sure. ML is needed03:44
hongbin#action Hongbin start a ML to discuss the container composition topic03:44
*** karthikp_ has joined #openstack-meeting03:44
*** jamesmcarthur has joined #openstack-meeting03:44
hongbinOK. Docker host management03:44
Qimingthe key of the docker-compose proposal is about ease-of-use, ease-of-management, that is something we should keep in mind as well03:45
hongbinyanyanhu: you had a comment for host management before?03:46
yanyanhuyes, about the abstraction layer03:46
*** shaohe_feng has quit IRC03:46
yanyanhuto hide the type of host from scheduler03:46
*** roxanagh_ has quit IRC03:46
hongbinlike how nova does?03:46
*** zhangshuai_ has quit IRC03:47
yanyanhuyes03:47
hongbinack03:47
*** zhangshuai_ has joined #openstack-meeting03:47
*** shaohe_feng has joined #openstack-meeting03:47
Qiming'host' management is a must, IMO, but we should be careful when exposing a user API03:47
hongbinYes03:47
WangJianwill it include what docker machine does?03:47
Qimingem.. interesting03:48
hongbinI guess it is different03:48
hongbindocker machine is for provision a machine (per my understanding)03:48
mkraiHeat will be our first choice when supporting nested vms?03:48
hongbinnova compute agent is for managing the hosts03:48
*** iyamahat has joined #openstack-meeting03:48
hongbinmkrai: not sure from me03:49
*** karthikp_ has quit IRC03:49
hongbinI agree with Qiming that host management is a must, otherwise, the scheduler is not going to work03:49
QimingI see, if we are never gonna support containers on VMs, host management is not that interesting, it becomes completely a nova thing03:50
mkraiWe will support it Qiming03:50
WangJian+1 Qiming03:50
*** jckasper has quit IRC03:51
yanyanhuagree03:51
sudiptoQiming, hongbin by host management are we referring to Ironic sort of a thing or compute driver sort of a thing?03:51
WangJianI think we can support docker machine later03:51
Qimingif we will support containers on abstract hosts (VMs or baremetals), higgins has to know the nature of the 'host', what/where are they03:51
Qimingsudipto, it is more of a compute driver thing, IMO03:51
hongbinHowever, we decided to start with non-nested use case03:52
hongbinThat means we don't need to worry the containers on VMs/Ironic right now03:52
Qimingstarting from baremetal sounds good03:52
yanyanhuhongbin, there can be an abstraction layer and bare metal can be the first kind of "physical" host03:52
*** chuanyunli has quit IRC03:52
*** dimtruck is now known as zz_dimtruck03:52
sudiptoQiming, precisely. hence my earlier comment on the metrics gathering stuff. I don't think this can be based on nova - simply because nova does it based on the hypervisor.03:52
*** yamahata has quit IRC03:53
hongbinyanyanhu: ack03:53
haiwei_my concern is who will control the host, in other words, where does the 'host' come from? It should come from Nova? or not03:53
sheelwe are left with 6 more minutes03:54
Qimingagreed, sudipto, just want to remind folks ... let's keep the design open03:54
*** iyamahat has quit IRC03:54
yuanyinghaiwei_: We will not use nova to manage03:54
yuanyinghost03:54
haiwei_then use what?03:54
*** jamesmcarthur has quit IRC03:54
mkraihongbin, get this to ML?03:54
yuanyinghost will be set up by operator's hand03:55
hongbin#action hongbin start a ML to discuss container host management03:55
hongbin#topic Open Discussion03:55
*** openstack changes topic to "Open Discussion (Meeting topic: higgins)"03:55
*** _alastor__ has joined #openstack-meeting03:55
*** amitgandhinz has joined #openstack-meeting03:55
*** moiz has joined #openstack-meeting03:55
sheelproject name -do we need change?03:55
*** roxanagh_ has joined #openstack-meeting03:55
*** david-lyle_ has joined #openstack-meeting03:55
hongbinsheel: you have a better name?03:55
mkraiWe need more contributors :)03:56
*** qwebirc4678 has joined #openstack-meeting03:56
sheelhongbin: I was looking into start casts of magnum pi03:56
sudiptoWe haven't talked Image management at all, wondering if we intend to use a proxy to docker registry or something.03:56
sheel;)03:56
*** shaohe_feng has quit IRC03:56
mkraiThat is still in todo sudipto03:56
hongbinsudipto: we can cover that in the next meeting03:56
yanyanhusudipto, I'm not clear about the detail, but I guess we can follow the way that nova-docker is using?03:57
*** david-lyle has quit IRC03:57
*** shashank_hegde has quit IRC03:57
hongbinI think nova-docker is using glance03:57
yanyanhuyes03:57
*** shaohe_feng has joined #openstack-meeting03:57
sudiptomkrai, hongbin - next meeting sounds reasonable. yanyanhu - yeah that would mean docker tar files in glance.03:57
hongbinTHe feedback is not so good, because glance don't support layers of images03:57
Qimingthen, go glance, ;)03:57
*** zhangshuai_ has quit IRC03:58
yanyanhuhongbin, that is a problem...03:58
hongbinFor glance, the docker images don't have layers anymore03:58
Qimingso .. no longer docker push, docker pull, ;)03:58
sudiptohongbin, yeah - there's a new project called Glare. I will have some update on this in the next meeting.03:58
mkraiThanks sudipto03:58
hongbinsudipto: ack03:59
Qimingif Higgins is focused on providing container lifecycle/runtime management, we can ignore the 'push/pull' requirement03:59
hongbinmaybe03:59
hongbinOK. time is up03:59
mkraiThanks everyone!03:59
sudiptoAlrite, thanks everyone!03:59
hongbinEveryone. Thanks for joining the meeting03:59
*** jamesmcarthur has joined #openstack-meeting03:59
Qimingbye03:59
sheelThank you guys03:59
*** amitgandhinz has quit IRC04:00
yanyanhuthanks04:00
namrata_Thanks ..bye04:00
Vivek___Thanks04:00
WangJianthx, bye04:00
*** xingchao has joined #openstack-meeting04:00
haiwei_thanks04:00
hongbinHope to see you all in the next meeting04:00
shu-mutouthx, bye04:00
*** tochi has joined #openstack-meeting04:00
hongbin#endmeeting04:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"04:00
openstackMeeting ended Tue May 24 04:00:13 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:00
*** WangJian has left #openstack-meeting04:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/higgins/2016/higgins.2016-05-24-03.00.html04:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/higgins/2016/higgins.2016-05-24-03.00.txt04:00
openstackLog:            http://eavesdrop.openstack.org/meetings/higgins/2016/higgins.2016-05-24-03.00.log.html04:00
*** qwebirc4678 has quit IRC04:00
*** hongbin has quit IRC04:00
*** Julien-zte has quit IRC04:01
*** zhangshuai_ has joined #openstack-meeting04:02
*** shashank_hegde has joined #openstack-meeting04:03
*** spzala has joined #openstack-meeting04:04
*** xingchao has quit IRC04:04
*** timcline has joined #openstack-meeting04:05
*** iyamahat has joined #openstack-meeting04:06
*** shaohe_feng has quit IRC04:06
*** links has joined #openstack-meeting04:07
*** zhhuabj_ has quit IRC04:07
*** shaohe_feng has joined #openstack-meeting04:07
*** fnaval_ has joined #openstack-meeting04:07
*** salv-orlando has joined #openstack-meeting04:08
*** timcline has quit IRC04:09
*** sams-gleb has joined #openstack-meeting04:10
*** fnaval has quit IRC04:10
*** spzala has quit IRC04:10
*** adahms has joined #openstack-meeting04:11
*** rderose has quit IRC04:13
*** rderose has joined #openstack-meeting04:13
*** jamesmcarthur has quit IRC04:13
*** aranjan has joined #openstack-meeting04:15
*** shaohe_feng has quit IRC04:17
*** ijw has quit IRC04:17
*** rderose has quit IRC04:17
*** shaohe_feng has joined #openstack-meeting04:17
*** salv-orlando has quit IRC04:17
*** sdake has joined #openstack-meeting04:17
*** sdake has quit IRC04:18
*** sams-gleb has quit IRC04:18
*** zhhuabj_ has joined #openstack-meeting04:20
*** yamamot__ has quit IRC04:21
*** markvoelker has joined #openstack-meeting04:23
*** zhangshuai_ has quit IRC04:24
*** zhangshuai_ has joined #openstack-meeting04:24
*** spotz_zzz is now known as spotz04:25
*** thorst_ has joined #openstack-meeting04:26
*** sgotliv has joined #openstack-meeting04:26
*** shaohe_feng has quit IRC04:27
*** markvoelker has quit IRC04:28
*** shaohe_feng has joined #openstack-meeting04:30
*** Vivek___ has quit IRC04:30
*** absubram has joined #openstack-meeting04:31
*** absubram_ has joined #openstack-meeting04:32
*** thorst_ has quit IRC04:33
*** jamesmcarthur has joined #openstack-meeting04:33
*** zhangshuai_ has quit IRC04:35
*** absubram has quit IRC04:36
*** absubram_ is now known as absubram04:36
*** Poornima has joined #openstack-meeting04:36
*** shaohe_feng has quit IRC04:37
*** shaohe_feng has joined #openstack-meeting04:38
*** sudipto has quit IRC04:39
*** jamesmcarthur has quit IRC04:41
*** armax has quit IRC04:41
*** ljxiash has quit IRC04:42
*** ljxiash has joined #openstack-meeting04:42
*** roxanagh_ has quit IRC04:43
*** tfukushima has quit IRC04:43
*** sridharg has joined #openstack-meeting04:43
*** asselin has joined #openstack-meeting04:46
*** ljxiash has quit IRC04:47
*** shaohe_feng has quit IRC04:47
*** jamesmcarthur has joined #openstack-meeting04:50
*** shaohe_feng has joined #openstack-meeting04:51
*** amitgandhinz has joined #openstack-meeting04:56
*** rbartal has joined #openstack-meeting04:57
*** eric_lopez has quit IRC04:57
*** shaohe_feng has quit IRC04:58
*** shaohe_feng has joined #openstack-meeting04:58
*** eric_lopez has joined #openstack-meeting04:59
*** cody-somerville has joined #openstack-meeting05:01
*** xingchao has joined #openstack-meeting05:01
*** amitgandhinz has quit IRC05:01
*** namrata_ has quit IRC05:01
*** spzala has joined #openstack-meeting05:02
*** jamesmcarthur has quit IRC05:02
*** manikanta_ has joined #openstack-meeting05:04
*** yamamoto has joined #openstack-meeting05:04
*** jamesmcarthur has joined #openstack-meeting05:05
*** timcline has joined #openstack-meeting05:06
*** spzala has quit IRC05:06
*** hparekh has left #openstack-meeting05:07
*** arvinc_ has quit IRC05:07
*** shaohe_feng has quit IRC05:08
*** enriquetaso has quit IRC05:08
*** shaohe_feng has joined #openstack-meeting05:09
*** timcline has quit IRC05:10
*** JRobinson__afk is now known as JRobinson__05:11
*** yanyanhu has left #openstack-meeting05:12
*** karthikp_ has joined #openstack-meeting05:12
*** jaypipes has quit IRC05:13
*** xingchao has quit IRC05:13
*** dmellado has quit IRC05:13
*** karthikp_ has quit IRC05:13
*** jamesmcarthur has quit IRC05:14
*** links has quit IRC05:14
*** samP_ has quit IRC05:14
*** jamesmcarthur has joined #openstack-meeting05:14
*** yamamoto has quit IRC05:14
*** samP_ has joined #openstack-meeting05:15
*** trozet has quit IRC05:15
*** sams-gleb has joined #openstack-meeting05:15
*** ntpttr has quit IRC05:15
*** yamamoto has joined #openstack-meeting05:16
*** dansmith has quit IRC05:16
*** albertom has quit IRC05:16
*** baoli has quit IRC05:16
*** ntpttr has joined #openstack-meeting05:16
*** lcastell has quit IRC05:17
*** dmellado has joined #openstack-meeting05:17
*** albertom has joined #openstack-meeting05:17
*** lcastell has joined #openstack-meeting05:17
*** links has joined #openstack-meeting05:17
*** trozet has joined #openstack-meeting05:18
*** dansmith has joined #openstack-meeting05:18
*** dansmith is now known as Guest7113205:18
*** shaohe_feng has quit IRC05:18
*** shaohe_feng has joined #openstack-meeting05:19
*** tfukushima has joined #openstack-meeting05:20
*** sacharya_ has joined #openstack-meeting05:21
*** tfukushima has quit IRC05:21
*** dmorita has joined #openstack-meeting05:23
*** sacharya has quit IRC05:23
*** sams-gleb has quit IRC05:23
*** links has quit IRC05:24
*** markvoelker has joined #openstack-meeting05:24
*** jamesmcarthur has quit IRC05:24
*** roxanagh_ has joined #openstack-meeting05:25
*** sacharya has joined #openstack-meeting05:26
*** sudipto has joined #openstack-meeting05:26
*** dmorita has quit IRC05:27
*** jamesmcarthur has joined #openstack-meeting05:28
*** sacharya_ has quit IRC05:28
*** shaohe_feng has quit IRC05:28
*** toddjohn has joined #openstack-meeting05:29
*** markvoelker has quit IRC05:29
*** shaohe_feng has joined #openstack-meeting05:29
*** roxanagh_ has quit IRC05:29
*** thorst_ has joined #openstack-meeting05:30
*** aranjan has quit IRC05:31
*** cschwede has quit IRC05:32
*** jamesmcarthur has quit IRC05:32
*** jamesmcarthur has joined #openstack-meeting05:33
*** toddjohn has quit IRC05:34
*** iceyao has joined #openstack-meeting05:34
*** adahms has quit IRC05:35
*** aranjan_ has joined #openstack-meeting05:35
*** yujunz has joined #openstack-meeting05:35
*** cody-somerville has quit IRC05:36
*** jamesmcarthur has quit IRC05:37
*** cschwede has joined #openstack-meeting05:37
*** thorst_ has quit IRC05:38
*** iceyao has quit IRC05:39
*** shaohe_feng has quit IRC05:39
*** iceyao has joined #openstack-meeting05:39
*** shaohe_feng has joined #openstack-meeting05:39
*** adiantum has joined #openstack-meeting05:39
*** haiwei_ has quit IRC05:42
loquacitieshi everyone, docs install guide meeting starts here in 15 mins :)05:42
*** Sukhdev_ has joined #openstack-meeting05:45
*** Niham has joined #openstack-meeting05:46
*** Niham has quit IRC05:46
*** Sukhdev has quit IRC05:46
*** yujunz has quit IRC05:49
*** shaohe_feng has quit IRC05:49
*** shaohe_feng has joined #openstack-meeting05:50
*** jckasper has joined #openstack-meeting05:51
*** lpetrut has joined #openstack-meeting05:53
*** jprovazn has joined #openstack-meeting05:54
*** katomo has joined #openstack-meeting05:55
*** Niham has joined #openstack-meeting05:55
*** jckasper has quit IRC05:55
*** erlon_ has quit IRC05:56
*** amotoki has joined #openstack-meeting05:56
*** ljxiash has joined #openstack-meeting05:56
*** amitgandhinz has joined #openstack-meeting05:57
loquacitieshi, who do we have here for the install guide meeting?05:58
loquacitiesi'll kick off the bot in a couple of mins05:59
katomoo/05:59
loquacitieshiya katomo05:59
*** shaohe_feng has quit IRC05:59
loquacitiesmight just be you and me :(05:59
*** Fdaisuke has quit IRC06:00
katomo:(06:00
*** shaohe_feng has joined #openstack-meeting06:00
*** thorst_ has joined #openstack-meeting06:00
loquacitiesright, well, let's kick off anyway, even if it's just the two of us06:01
loquacitiesthere's still plenty to talk about06:01
katomoI'd like to see folks from dev teams06:01
loquacitiesyeah, me too06:01
katomoyeah06:01
loquacities#startmeeting docinstallteam06:01
openstackMeeting started Tue May 24 06:01: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:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.06:01
*** openstack changes topic to " (Meeting topic: docinstallteam)"06:01
openstackThe meeting name has been set to 'docinstallteam'06:01
loquacities#topic omg no one came to the meeting06:01
*** openstack changes topic to "omg no one came to the meeting (Meeting topic: docinstallteam)"06:01
loquacitiesok, how do we get devs to the meeting?06:02
*** amitgandhinz has quit IRC06:02
*** hoangcx has joined #openstack-meeting06:02
katomohmmm...06:02
loquacitiesi could send a personal email to CPLs?06:02
katomogood idea06:02
loquacitiesi'm sure i've mentioned in the newsletter heaps, so maybe keep doing that06:02
loquacities#action Lana to email CPLs about install guide meeting attendance06:03
loquacities#undo06:03
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0xa510190>06:03
*** Fdaisuke has joined #openstack-meeting06:03
loquacities#action loquacities to email CPLs about install guide meeting attendance06:03
*** ijw has joined #openstack-meeting06:03
*** links has joined #openstack-meeting06:03
loquacitiesok, well, i guess that's a good start06:04
loquacitiesmoving on06:04
loquacities#topic proposals06:04
*** openstack changes topic to "proposals (Meeting topic: docinstallteam)"06:04
loquacities#link https://review.openstack.org/#/c/314020/ - Zigo's proposal for having debconf build as a conditional, instead of a seperate book. What do we think about this?06:04
*** fnaval has joined #openstack-meeting06:04
loquacities#link https://review.openstack.org/#/c/316325/ - Kato's proposal for having the debconf book build separately, but relying on install guide content. What do we think about this?06:04
loquacitiespersonally, i think your proposal has more merit at this stage, katomo06:05
katomoI'd like to use my #316325 patch.06:05
loquacities+106:05
katomoyep06:05
loquacitiesi've already +2d it, we need someone to +2A06:05
loquacitiesi think we can probably ask JRobinson__ to do that06:05
*** JRobinson__ is now known as JRobinson__afk06:06
loquacitiesheh, i'll ping him later ;)06:06
katomo:)06:06
*** fnaval_ has quit IRC06:06
loquacities#topic specs06:06
*** openstack changes topic to "specs (Meeting topic: docinstallteam)"06:06
loquacities#link https://review.openstack.org/#/c/310588/ - Needs approval/merge06:06
loquacities#link https://review.openstack.org/#/c/301284/ - Well and truly merged, need to start work06:07
*** timcline has joined #openstack-meeting06:07
loquacitiesi think we've addressed all the concerns on 310588 now06:07
*** rcernin has joined #openstack-meeting06:07
katomo #310588 is just +A'd !06:07
loquacitiesoh! joe did it :)06:07
*** nadya has joined #openstack-meeting06:08
loquacitiessweet06:08
loquacitiesso, now we need to just start work on the action items for both specs06:08
loquacitiesi might need to send an email about that, so that's it not you and me doing everything06:08
*** hoangcx has left #openstack-meeting06:08
katomohehe06:08
loquacitiesand, finally ...06:09
loquacities#topic bikeshedding06:09
*** openstack changes topic to "bikeshedding (Meeting topic: docinstallteam)"06:09
*** thorst_ has quit IRC06:09
loquacities#info what to call the New and Improved(TM) Install Guide?06:09
loquacitiesi'm thinking something like "OpenStack Installation Tutorial"06:09
*** shaohe_feng has quit IRC06:09
katomohm06:09
loquacitiesbut maybe we should create a google poll or something?06:10
loquacitiespeople can vote and submit their ideas?06:10
*** shaohe_feng has joined #openstack-meeting06:10
katomoyeah, good idea06:10
*** tfukushima has joined #openstack-meeting06:10
loquacitiesok, i'll sort that out06:10
loquacities#action loquacities to create poll on naming06:10
loquacities#topic open discussion06:10
*** openstack changes topic to "open discussion (Meeting topic: docinstallteam)"06:10
loquacitiesanything else?06:10
katomonothing from me06:11
loquacitiescool06:11
loquacitiesthanks for hanging around :)06:11
loquacitiesi'll try and spruik the meeting a little more for next time06:11
katomothanks, loquacities06:11
loquacities#endmeeting06:11
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:11
*** sdake has joined #openstack-meeting06:11
openstackMeeting ended Tue May 24 06:11:26 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:11
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-05-24-06.01.html06:11
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-05-24-06.01.txt06:11
openstackLog:            http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-05-24-06.01.log.html06:11
*** timcline has quit IRC06:11
*** katomo has quit IRC06:11
*** sverma has joined #openstack-meeting06:11
*** sridharg has quit IRC06:13
*** nikhil has quit IRC06:14
*** xgerman has quit IRC06:14
*** scottda has quit IRC06:14
*** morgabra has quit IRC06:15
*** serverascode has quit IRC06:15
*** marios has quit IRC06:15
*** sneti_ has quit IRC06:15
*** meteorfox has quit IRC06:15
*** DuncanT has quit IRC06:15
*** scottda has joined #openstack-meeting06:16
*** CaptTofu has quit IRC06:16
*** hazmat has quit IRC06:16
*** mrhillsman has quit IRC06:16
*** nikhil has joined #openstack-meeting06:16
*** MarkAtwood has quit IRC06:16
*** betherly has quit IRC06:16
*** xgerman has joined #openstack-meeting06:17
*** marios has joined #openstack-meeting06:17
*** serverascode has joined #openstack-meeting06:17
*** larainema has quit IRC06:17
*** meteorfox has joined #openstack-meeting06:17
*** vishnoianil has quit IRC06:17
*** homerp has quit IRC06:18
*** lekha-away has quit IRC06:18
*** simonmcc has quit IRC06:18
*** edwarnicke has quit IRC06:18
*** DuncanT has joined #openstack-meeting06:18
*** hazmat has joined #openstack-meeting06:19
*** betherly has joined #openstack-meeting06:19
*** MarkAtwood has joined #openstack-meeting06:19
*** fwdit has joined #openstack-meeting06:19
*** madorn has quit IRC06:19
*** sballe_ has quit IRC06:19
*** lekha-away has joined #openstack-meeting06:19
*** shaohe_feng has quit IRC06:20
*** larainema has joined #openstack-meeting06:20
*** edwarnicke has joined #openstack-meeting06:20
*** isq has quit IRC06:20
*** shaohe_feng has joined #openstack-meeting06:20
*** dolphm has quit IRC06:21
*** sams-gleb has joined #openstack-meeting06:21
*** CaptTofu has joined #openstack-meeting06:21
*** sballe_ has joined #openstack-meeting06:21
*** paul-carlton2 has joined #openstack-meeting06:21
*** sparkycollier has quit IRC06:21
*** coolsvap has quit IRC06:21
*** fmccrthy has quit IRC06:21
*** macsz has quit IRC06:21
*** med_ has quit IRC06:21
*** simonmcc has joined #openstack-meeting06:21
*** isq has joined #openstack-meeting06:21
*** fmccrthy has joined #openstack-meeting06:22
*** serverascode has quit IRC06:22
*** woodster_ has quit IRC06:22
*** ogelbukh has quit IRC06:22
*** huangtianhua has joined #openstack-meeting06:23
*** macsz has joined #openstack-meeting06:23
*** dolphm has joined #openstack-meeting06:23
*** morgabra has joined #openstack-meeting06:23
*** homerp has joined #openstack-meeting06:24
*** markvoelker has joined #openstack-meeting06:25
*** ogelbukh has joined #openstack-meeting06:25
*** med_ has joined #openstack-meeting06:25
*** med_ has quit IRC06:25
*** med_ has joined #openstack-meeting06:25
*** sdake has quit IRC06:25
*** nadya has quit IRC06:25
*** sparkycollier has joined #openstack-meeting06:26
*** woodster_ has joined #openstack-meeting06:26
*** tiantian has quit IRC06:26
*** coolsvap has joined #openstack-meeting06:26
*** ashtokolov has quit IRC06:26
*** samueldmq has quit IRC06:27
*** samueldmq has joined #openstack-meeting06:27
*** harlowja has quit IRC06:28
*** saisriki- has quit IRC06:28
*** sams-gleb has quit IRC06:28
*** saisrikiran has joined #openstack-meeting06:28
*** vishnoianil has joined #openstack-meeting06:29
*** markvoelker has quit IRC06:29
*** ashtokolov has joined #openstack-meeting06:29
*** shaohe_feng has quit IRC06:30
*** serverascode has joined #openstack-meeting06:32
*** shaohe_feng has joined #openstack-meeting06:33
*** cebruns has quit IRC06:33
*** cebruns has joined #openstack-meeting06:35
*** sdake has joined #openstack-meeting06:37
*** salv-orlando has joined #openstack-meeting06:37
*** shaohe_feng has quit IRC06:40
*** shaohe_feng has joined #openstack-meeting06:41
*** pzchen has joined #openstack-meeting06:42
*** mrhillsman has joined #openstack-meeting06:43
*** yuval has joined #openstack-meeting06:44
*** earlephilhower has quit IRC06:46
*** Sukhdev_ has quit IRC06:46
*** sridharg has joined #openstack-meeting06:46
*** madorn has joined #openstack-meeting06:48
*** numans has joined #openstack-meeting06:49
*** unicell has quit IRC06:50
*** shaohe_feng has quit IRC06:50
*** shaohe_feng has joined #openstack-meeting06:51
*** unicell has joined #openstack-meeting06:51
*** toanster has joined #openstack-meeting06:52
*** toan has quit IRC06:52
*** sdake has quit IRC06:53
*** sneti_ has joined #openstack-meeting06:55
*** amitgandhinz has joined #openstack-meeting06:57
*** lpetrut has quit IRC06:58
*** shaohe_feng has quit IRC07:01
*** sams-gleb has joined #openstack-meeting07:01
*** shaohe_feng has joined #openstack-meeting07:01
*** amitgandhinz has quit IRC07:02
*** spzala has joined #openstack-meeting07:02
*** tesseract has joined #openstack-meeting07:04
*** ijw has quit IRC07:05
*** thorst_ has joined #openstack-meeting07:06
*** spzala has quit IRC07:07
*** timcline has joined #openstack-meeting07:07
*** tesseract has quit IRC07:08
*** mkrai has left #openstack-meeting07:08
*** manikanta_ has quit IRC07:09
*** yamahata has joined #openstack-meeting07:10
*** jtomasek has quit IRC07:10
*** shaohe_feng has quit IRC07:11
*** shaohe_feng has joined #openstack-meeting07:12
*** timcline has quit IRC07:12
*** sacharya has quit IRC07:13
*** jprovazn has quit IRC07:13
*** jprovazn has joined #openstack-meeting07:13
*** thorst_ has quit IRC07:13
*** rossella_s has joined #openstack-meeting07:16
*** moizarif has joined #openstack-meeting07:17
*** rwsu has joined #openstack-meeting07:19
*** jschwarz has joined #openstack-meeting07:20
*** moiz has quit IRC07:20
*** shaohe_feng has quit IRC07:21
*** shaohe_feng has joined #openstack-meeting07:21
*** matrohon has joined #openstack-meeting07:22
*** rwsu has quit IRC07:22
*** rwsu has joined #openstack-meeting07:22
*** Ravikiran_K has joined #openstack-meeting07:25
*** markvoelker has joined #openstack-meeting07:26
*** nkrinner has joined #openstack-meeting07:28
*** jlanoux has joined #openstack-meeting07:29
*** shaohe_feng has quit IRC07:31
*** markvoelker has quit IRC07:32
*** rossella_s has quit IRC07:32
*** shaohe_feng has joined #openstack-meeting07:32
*** henrynash has joined #openstack-meeting07:32
*** rossella_s has joined #openstack-meeting07:33
*** spotz is now known as spotz_zzz07:34
*** sgotliv_ has joined #openstack-meeting07:35
*** sgotliv has quit IRC07:37
*** ihrachys has joined #openstack-meeting07:37
*** sgotliv__ has joined #openstack-meeting07:40
*** manikanta_tadi has joined #openstack-meeting07:40
*** zeih has joined #openstack-meeting07:41
*** shaohe_feng has quit IRC07:42
*** sgotliv_ has quit IRC07:42
*** shaohe_feng has joined #openstack-meeting07:42
*** sgotliv_ has joined #openstack-meeting07:43
*** aranjan_ has quit IRC07:43
*** sgotliv__ has quit IRC07:45
*** paul-carlton2 has quit IRC07:46
*** Niham has quit IRC07:47
*** woodster_ has quit IRC07:48
*** sgotliv_ has quit IRC07:48
*** lpetrut has joined #openstack-meeting07:48
*** hashar has joined #openstack-meeting07:49
*** sgotliv has joined #openstack-meeting07:50
*** shaohe_feng has quit IRC07:52
*** sgotliv_ has joined #openstack-meeting07:53
*** shaohe_feng has joined #openstack-meeting07:53
*** zeih has quit IRC07:54
*** sgotliv has quit IRC07:55
*** zeih has joined #openstack-meeting07:56
*** beisner has quit IRC07:56
*** Fdaisuke has quit IRC07:57
*** sgotliv_ has quit IRC07:58
*** sgotliv_ has joined #openstack-meeting07:58
*** amitgandhinz has joined #openstack-meeting07:58
*** vuntz_ is now known as vuntz07:59
*** Fdaisuke has joined #openstack-meeting07:59
*** paul-carlton2 has joined #openstack-meeting07:59
*** zhurong_ has joined #openstack-meeting08:00
*** shaohe_feng has quit IRC08:02
*** amitgandhinz has quit IRC08:03
*** shaohe_feng has joined #openstack-meeting08:03
*** toscalix has joined #openstack-meeting08:03
*** mbound has joined #openstack-meeting08:04
*** spzala has joined #openstack-meeting08:04
*** zhurong has quit IRC08:04
*** mbound has quit IRC08:05
*** mbound has joined #openstack-meeting08:06
*** JRobinson__afk is now known as JRobinson__08:07
*** beisner has joined #openstack-meeting08:08
*** shashank_hegde has quit IRC08:08
*** spzala has quit IRC08:08
*** timcline has joined #openstack-meeting08:08
*** zhurong_ has quit IRC08:09
*** zeih has quit IRC08:10
*** zhurong has joined #openstack-meeting08:11
*** thorst_ has joined #openstack-meeting08:11
*** timcline has quit IRC08:12
*** shaohe_feng has quit IRC08:12
*** shaohe_feng has joined #openstack-meeting08:13
*** sacharya has joined #openstack-meeting08:13
*** belmoreira has joined #openstack-meeting08:15
*** lpetrut has quit IRC08:17
*** sacharya has quit IRC08:18
*** thorst_ has quit IRC08:18
*** ygbo has joined #openstack-meeting08:19
*** e0ne has joined #openstack-meeting08:20
*** zeih has joined #openstack-meeting08:22
*** shaohe_feng has quit IRC08:23
*** shaohe_feng has joined #openstack-meeting08:23
*** asettle has joined #openstack-meeting08:24
*** salv-orlando has quit IRC08:25
*** odyssey4me_ is now known as odyssey4me08:26
*** afazekas_ is now known as afazekas08:27
*** markvoelker has joined #openstack-meeting08:28
*** yassine has joined #openstack-meeting08:29
*** paul-carlton2 has quit IRC08:29
*** yassine is now known as Guest6630408:29
*** singhj has joined #openstack-meeting08:30
*** e0ne has quit IRC08:31
*** zhurong has quit IRC08:31
*** hichihara has joined #openstack-meeting08:32
*** e0ne has joined #openstack-meeting08:32
*** rubasov has quit IRC08:32
*** zhurong has joined #openstack-meeting08:32
*** markvoelker has quit IRC08:32
*** shaohe_feng has quit IRC08:33
*** zhhuabj_ has quit IRC08:33
*** shaohe_feng has joined #openstack-meeting08:34
*** fzdarsky has joined #openstack-meeting08:34
*** pnavarro has joined #openstack-meeting08:34
*** Guest66304 is now known as yassou08:35
*** singhj has quit IRC08:35
*** mickeys has joined #openstack-meeting08:37
*** HeOS has joined #openstack-meeting08:38
*** zeih has quit IRC08:38
*** ig0r_ has joined #openstack-meeting08:40
*** paul-carlton2 has joined #openstack-meeting08:41
*** mickeys has quit IRC08:41
*** shaohe_feng has quit IRC08:43
*** shaohe_feng has joined #openstack-meeting08:44
*** Niham has joined #openstack-meeting08:45
*** Niham has quit IRC08:45
*** zhhuabj_ has joined #openstack-meeting08:47
*** pzchen has quit IRC08:51
*** pzchen has joined #openstack-meeting08:51
*** Niham has joined #openstack-meeting08:53
*** pzchen has quit IRC08:53
*** Niham has quit IRC08:53
*** shaohe_feng has quit IRC08:53
*** shaohe_feng has joined #openstack-meeting08:54
*** shu-mutou is now known as shu-mutou-AFK08:58
*** wznoinsk has quit IRC08:59
*** amitgandhinz has joined #openstack-meeting08:59
*** wznoinsk has joined #openstack-meeting08:59
*** Niham has joined #openstack-meeting08:59
*** Niham has quit IRC09:00
*** electrofelix has joined #openstack-meeting09:00
*** Niham has joined #openstack-meeting09:01
*** Niham has quit IRC09:02
*** Niham has joined #openstack-meeting09:03
*** amitgandhinz has quit IRC09:03
*** shaohe_feng has quit IRC09:04
*** shaohe_feng has joined #openstack-meeting09:05
*** lpetrut has joined #openstack-meeting09:07
*** acoles_ is now known as acoles09:07
*** timcline has joined #openstack-meeting09:09
*** aranjan has joined #openstack-meeting09:11
*** lpetrut1 has joined #openstack-meeting09:12
*** lpetrut has quit IRC09:13
*** lpetrut1 is now known as lpetrut09:13
*** timcline has quit IRC09:13
*** shaohe_feng has quit IRC09:14
*** aranjan has quit IRC09:14
*** aranjan has joined #openstack-meeting09:14
*** shaohe_feng has joined #openstack-meeting09:15
*** tochi has quit IRC09:15
*** thorst_ has joined #openstack-meeting09:16
*** ociuhandu has joined #openstack-meeting09:17
*** claudiub has joined #openstack-meeting09:18
*** aranjan has quit IRC09:19
*** sdake has joined #openstack-meeting09:20
*** ociuhandu has quit IRC09:20
*** moiz has joined #openstack-meeting09:23
*** manikanta_tadi has quit IRC09:23
*** thorst_ has quit IRC09:24
*** asdfljfkdnkfn has joined #openstack-meeting09:24
*** shaohe_feng has quit IRC09:24
*** asdfljfkdnkfn has quit IRC09:24
*** shaohe_feng has joined #openstack-meeting09:25
*** ljxiash has quit IRC09:27
*** moizarif has quit IRC09:27
*** ljxiash has joined #openstack-meeting09:27
*** nadya has joined #openstack-meeting09:27
*** ljxiash has quit IRC09:27
*** ljxiash has joined #openstack-meeting09:27
*** JRobinson__ has quit IRC09:28
*** zigo_ is now known as zigo09:28
*** jtomasek_ has joined #openstack-meeting09:33
*** gmann_ has joined #openstack-meeting09:34
*** shaohe_feng has quit IRC09:34
*** donghao has quit IRC09:35
*** shaohe_feng has joined #openstack-meeting09:35
*** haukebruno has joined #openstack-meeting09:36
*** manikanta_tadi has joined #openstack-meeting09:36
*** Poornima has quit IRC09:37
*** Poornima has joined #openstack-meeting09:38
*** gcb has quit IRC09:40
*** gcb has joined #openstack-meeting09:41
*** anilvenkata has joined #openstack-meeting09:41
*** liusheng has quit IRC09:41
*** liusheng has joined #openstack-meeting09:42
*** shaohe_feng has quit IRC09:45
*** shaohe_feng has joined #openstack-meeting09:46
*** sgotliv has joined #openstack-meeting09:46
*** sgotliv_ has quit IRC09:47
*** sgotliv_ has joined #openstack-meeting09:51
*** sgotliv has quit IRC09:52
*** Poornima has quit IRC09:52
*** jckasper has joined #openstack-meeting09:53
*** yassou has quit IRC09:54
*** fnaval has quit IRC09:54
*** shaohe_feng has quit IRC09:55
*** sambetts|afk is now known as sambetts09:55
*** voyageur has joined #openstack-meeting09:55
*** shaohe_feng has joined #openstack-meeting09:56
*** jckasper has quit IRC09:57
*** moizarif has joined #openstack-meeting09:58
*** moiz has quit IRC09:59
*** iceyao_ has joined #openstack-meeting09:59
*** amitgandhinz has joined #openstack-meeting10:00
*** iceyao_ has quit IRC10:00
*** iceyao__ has joined #openstack-meeting10:00
*** iceyao__ has quit IRC10:00
*** iceyao_ has joined #openstack-meeting10:01
*** sdake has quit IRC10:01
*** iceyao__ has joined #openstack-meeting10:02
*** iceyao_ has quit IRC10:02
*** iceyao has quit IRC10:02
*** hoangcx_ has joined #openstack-meeting10:02
*** bcafarel has joined #openstack-meeting10:03
*** Poornima has joined #openstack-meeting10:04
*** amitgandhinz has quit IRC10:04
*** spzala has joined #openstack-meeting10:05
*** shaohe_feng has quit IRC10:05
*** sudipto has quit IRC10:06
*** sudipto has joined #openstack-meeting10:06
*** shaohe_feng has joined #openstack-meeting10:06
*** zhurong has quit IRC10:06
*** zhhuabj_ has quit IRC10:07
*** iyamahat has quit IRC10:08
*** spzala has quit IRC10:10
*** timcline has joined #openstack-meeting10:10
*** MaxPC has joined #openstack-meeting10:11
*** ljxiash has quit IRC10:12
*** ljxiash has joined #openstack-meeting10:12
*** yamahata has quit IRC10:13
*** e0ne has quit IRC10:13
*** e0ne has joined #openstack-meeting10:14
*** timcline has quit IRC10:14
*** sacharya has joined #openstack-meeting10:15
*** aranjan has joined #openstack-meeting10:15
*** shaohe_feng has quit IRC10:15
*** shaohe_feng has joined #openstack-meeting10:16
*** zeih has joined #openstack-meeting10:17
*** ljxiash has quit IRC10:17
*** sacharya has quit IRC10:19
*** aranjan has quit IRC10:20
*** hoangcx_ has left #openstack-meeting10:21
*** thorst_ has joined #openstack-meeting10:21
*** zeih has quit IRC10:21
*** zhhuabj_ has joined #openstack-meeting10:25
*** shaohe_feng has quit IRC10:26
*** shaohe_feng has joined #openstack-meeting10:27
*** thorst_ has quit IRC10:28
*** nadya has quit IRC10:28
*** bvandenh has joined #openstack-meeting10:28
*** markvoelker has joined #openstack-meeting10:29
*** jlanoux has quit IRC10:30
*** jlanoux has joined #openstack-meeting10:31
*** asselin has quit IRC10:31
*** markvoelker has quit IRC10:34
*** toscalix has quit IRC10:35
*** shaohe_feng has quit IRC10:36
*** toscalix_ has joined #openstack-meeting10:36
*** shaohe_feng has joined #openstack-meeting10:37
*** toscalix_ has quit IRC10:40
*** e0ne_ has joined #openstack-meeting10:41
*** toscalix has joined #openstack-meeting10:41
*** e0ne has quit IRC10:42
*** jlanoux has quit IRC10:42
*** jlanoux has joined #openstack-meeting10:43
*** toscalix has quit IRC10:46
*** shaohe_feng has quit IRC10:46
*** shaohe_feng has joined #openstack-meeting10:47
*** pgreg_ has joined #openstack-meeting10:48
*** ljxiash has joined #openstack-meeting10:50
*** Niham has quit IRC10:50
*** pgreg has quit IRC10:51
*** ljxiash has quit IRC10:52
*** ljxiash has joined #openstack-meeting10:52
*** sudipto has quit IRC10:53
*** toscalix has joined #openstack-meeting10:54
*** shaohe_feng has quit IRC10:56
*** dmowrer has joined #openstack-meeting10:57
*** shaohe_feng has joined #openstack-meeting10:57
*** lazy_prince has quit IRC10:59
*** janonymous_ has quit IRC11:00
*** lazy_prince has joined #openstack-meeting11:00
*** reedip has quit IRC11:00
*** amitgandhinz has joined #openstack-meeting11:00
*** julen has joined #openstack-meeting11:01
*** sudipto has joined #openstack-meeting11:01
*** dprince has joined #openstack-meeting11:02
*** cdelatte has joined #openstack-meeting11:03
*** dcwangmit01 has quit IRC11:04
*** amitgandhinz has quit IRC11:05
*** spzala has joined #openstack-meeting11:06
*** Qiming has quit IRC11:06
*** shaohe_feng has quit IRC11:07
*** masahito has quit IRC11:07
*** shaohe_feng has joined #openstack-meeting11:08
*** Ravikiran_K has quit IRC11:08
*** spzala has quit IRC11:10
*** timcline has joined #openstack-meeting11:10
*** reedip has joined #openstack-meeting11:11
*** epico has quit IRC11:12
*** rtheis has joined #openstack-meeting11:12
*** janonymous_ has joined #openstack-meeting11:13
*** salv-orlando has joined #openstack-meeting11:15
*** timcline has quit IRC11:15
*** aranjan has joined #openstack-meeting11:16
*** tellesnobrega has quit IRC11:17
*** shaohe_feng has quit IRC11:17
*** sdake has joined #openstack-meeting11:17
*** BobBall has left #openstack-meeting11:17
*** spotz_zzz is now known as spotz11:19
*** salv-orlando has quit IRC11:19
*** shaohe_feng has joined #openstack-meeting11:19
*** aranjan has quit IRC11:21
*** iceyao__ has quit IRC11:23
*** nadya has joined #openstack-meeting11:25
*** sdague has joined #openstack-meeting11:25
*** thorst_ has joined #openstack-meeting11:26
*** shaohe_feng has quit IRC11:27
*** ociuhandu has joined #openstack-meeting11:28
*** tfukushima has quit IRC11:28
*** shaohe_feng has joined #openstack-meeting11:28
*** gmann_ has quit IRC11:30
*** markvoelker has joined #openstack-meeting11:30
*** thorst_ has quit IRC11:31
*** rodrigods has quit IRC11:31
*** rodrigods has joined #openstack-meeting11:31
*** tlbr_ has quit IRC11:31
*** vgridnev has quit IRC11:33
*** phil_h has joined #openstack-meeting11:34
*** ig0r_ has quit IRC11:34
*** markvoelker has quit IRC11:35
*** vgridnev has joined #openstack-meeting11:35
*** shaohe_feng has quit IRC11:37
*** shaohe_feng has joined #openstack-meeting11:38
*** asettle has quit IRC11:39
*** asettle has joined #openstack-meeting11:39
*** vgridnev has quit IRC11:40
*** vgridnev has joined #openstack-meeting11:40
*** sudipto has quit IRC11:42
*** hichihara has quit IRC11:43
*** thorst_ has joined #openstack-meeting11:43
*** julim has joined #openstack-meeting11:45
*** salv-orlando has joined #openstack-meeting11:46
*** spotz is now known as spotz_zzz11:47
*** shaohe_feng has quit IRC11:48
*** shaohe_feng has joined #openstack-meeting11:48
*** sdake has quit IRC11:49
*** zhurong has joined #openstack-meeting11:51
*** pgreg_ has quit IRC11:51
*** yassine has joined #openstack-meeting11:52
*** yassine is now known as Guest966511:52
*** cdub has joined #openstack-meeting11:52
*** askb has joined #openstack-meeting11:53
*** rfolco has joined #openstack-meeting11:54
*** ig0r_ has joined #openstack-meeting11:57
*** Qiming has joined #openstack-meeting11:58
*** shaohe_feng has quit IRC11:58
*** shaohe_feng has joined #openstack-meeting11:59
*** tlbr has joined #openstack-meeting12:00
*** amitgandhinz has joined #openstack-meeting12:01
*** jckasper has joined #openstack-meeting12:02
*** markvoelker has joined #openstack-meeting12:02
*** jckasper has quit IRC12:03
*** jaypipes has joined #openstack-meeting12:03
*** yamamoto has quit IRC12:04
*** amitgandhinz has quit IRC12:06
*** spzala has joined #openstack-meeting12:07
*** asettle has quit IRC12:08
*** sams-gleb has quit IRC12:08
*** shaohe_feng has quit IRC12:08
*** sams-gleb has joined #openstack-meeting12:09
*** bobh has joined #openstack-meeting12:09
*** shaohe_feng has joined #openstack-meeting12:09
*** liamji has quit IRC12:10
*** hashar is now known as hasharAw12:10
*** spzala has quit IRC12:11
*** timcline has joined #openstack-meeting12:11
*** timcline has quit IRC12:15
*** asettle has joined #openstack-meeting12:15
*** Qiming has quit IRC12:15
*** Ravikiran_K has joined #openstack-meeting12:16
*** sams-gleb has quit IRC12:17
*** asettle has quit IRC12:17
*** Qiming has joined #openstack-meeting12:17
*** aranjan has joined #openstack-meeting12:17
*** asettle has joined #openstack-meeting12:17
*** shaohe_feng has quit IRC12:18
*** tfukushima has joined #openstack-meeting12:19
*** shaohe_feng has joined #openstack-meeting12:19
*** ayoung has quit IRC12:19
*** cdub has quit IRC12:20
*** aranjan has quit IRC12:21
*** sams-gleb has joined #openstack-meeting12:23
*** adrianofr has joined #openstack-meeting12:27
*** bobh has quit IRC12:28
*** bvandenh has quit IRC12:28
*** shaohe_feng has quit IRC12:29
*** shaohe_feng has joined #openstack-meeting12:29
*** maeca1 has joined #openstack-meeting12:30
*** cdub has joined #openstack-meeting12:31
*** beisner has quit IRC12:32
*** dneary has joined #openstack-meeting12:33
*** moizarif has quit IRC12:34
*** samP_ has quit IRC12:34
*** salv-orlando has quit IRC12:35
*** dprince has quit IRC12:38
*** jckasper has joined #openstack-meeting12:38
*** dneary has quit IRC12:39
*** shaohe_feng has quit IRC12:39
*** shaohe_feng has joined #openstack-meeting12:40
*** bvandenh has joined #openstack-meeting12:42
*** aysyd has joined #openstack-meeting12:42
*** dneary has joined #openstack-meeting12:42
*** cdub has quit IRC12:43
*** shaohe_feng has quit IRC12:49
*** yanyanhu has joined #openstack-meeting12:49
*** yassine has joined #openstack-meeting12:50
*** yassine is now known as Guest7386012:50
*** shaohe_feng has joined #openstack-meeting12:50
*** asselin has joined #openstack-meeting12:50
*** Guest9665 has quit IRC12:52
*** Guest73860 is now known as yassou12:53
*** beisner has joined #openstack-meeting12:53
*** kylek3h has joined #openstack-meeting12:54
*** baoli has joined #openstack-meeting12:55
*** sheel has quit IRC12:55
*** baoli_ has joined #openstack-meeting12:56
*** rubasov has joined #openstack-meeting12:56
*** david-lyle has joined #openstack-meeting12:57
*** aliadil has joined #openstack-meeting12:58
*** john-dav_ has joined #openstack-meeting12:59
*** shaohe_feng has quit IRC12:59
*** john-dav_ is now known as john-davidge13:00
Qiming#startmeeing senlin13:00
*** baoli has quit IRC13:00
yanyanhuhello13:01
*** Qiming has quit IRC13:01
*** david-lyle_ has quit IRC13:01
yanyanhuQiming, typo in command13:01
*** Qiming has joined #openstack-meeting13:01
Qiming#startmeeting senlin13:02
openstackMeeting started Tue May 24 13:02:06 2016 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
*** openstack changes topic to " (Meeting topic: senlin)"13:02
openstackThe meeting name has been set to 'senlin'13:02
*** elynn has joined #openstack-meeting13:02
Qiminghad to try again13:02
elynno/13:02
*** amitgandhinz has joined #openstack-meeting13:02
Qimingseems some networking problem13:02
Qiminghi, elynn13:02
yanyanhuhi13:02
Qiminghi13:02
elynnsorry a little late13:02
Qimingnot at all13:02
*** xuhaiwei_ has joined #openstack-meeting13:02
*** shaohe_feng has joined #openstack-meeting13:02
QimingI don't have outstanding issues for discussion today13:03
Qimingif you have some, please update the meeting agenda13:03
*** zhurong has quit IRC13:03
Qiming#link https://wiki.openstack.org/wiki/Meetings/SenlinAgenda13:03
Qiming#topic newton work items13:03
*** openstack changes topic to "newton work items (Meeting topic: senlin)"13:03
Qimingtesting13:04
elynnonly event show and api show are needed.13:04
Qimingyou mean the other API tests are all done?13:05
elynnI think13:05
yanyanhupatches have been proposed for these two cases. And elynn has started working on negative cases13:05
elynnExcept for negative tests13:05
*** pradk has joined #openstack-meeting13:05
Qiminggreat13:05
*** mjturek1 has left #openstack-meeting13:05
elynnSaw your comment on event show13:05
elynnpatch13:06
Qiminghave tests in tree can help us ensure that the api changes are reflected into the tempest test cases soon, if any13:06
*** bvandenh has quit IRC13:06
elynnhttps://review.openstack.org/#/c/320227/1/senlin/tests/tempest/api/events/test_event_show.py13:06
Qimingyes, don't think cls.event is necessary13:06
*** alyson_ has joined #openstack-meeting13:07
elynnIf put these lines in to test_show_event()13:07
*** zhurong has joined #openstack-meeting13:07
*** amitgandhinz has quit IRC13:07
elynnIn this test will contain 2 API access13:07
*** spzala has joined #openstack-meeting13:07
Qimingemm, right13:08
elynnone for event list and one for event show. just for remind.13:08
Qiminganother workaround is to set limit=1 when doing listing13:08
*** aranjan has joined #openstack-meeting13:09
*** sdake has joined #openstack-meeting13:09
elynnhmm, that's a good idea13:09
Qimingthe reason is that we only allow specifying event_id for event_show13:09
*** xyang1 has joined #openstack-meeting13:09
Qiminggate patch is still pending review, right?13:09
elynnYes...13:09
elynnI rebase it today, to get it on top~13:10
*** shaohe_feng has quit IRC13:10
yanyanhulooks like a lot of patches are pending13:10
yanyanhufor lack of workflow13:10
Qimingem, may be time to ping the reviewers13:10
elynnBut still no progress.13:10
*** shaohe_feng has joined #openstack-meeting13:10
Qimingit's been there for a while now13:10
elynnOkay13:10
Qimingand we'd better turn it on13:10
elynnI will reach them after meeting.13:11
Qimingthx13:11
QimingRally test ?13:11
yanyanhuhttps://review.openstack.org/31845313:11
yanyanhualso pending there13:11
*** toddjohn has joined #openstack-meeting13:11
*** salv-orlando has joined #openstack-meeting13:11
yanyanhuthis patch tries to add senlin support to rally-gate13:11
yanyanhuafter that, any changes related to senlin in rally project can be verified13:11
*** lixinhui_ has joined #openstack-meeting13:12
*** timcline has joined #openstack-meeting13:12
*** spzala has quit IRC13:12
Qimingthe other one has been hanging for over 40 days13:12
*** bvandenh has joined #openstack-meeting13:12
yanyanhuit has been updated :)13:12
yanyanhuhttps://review.openstack.org/30152213:12
yanyanhuand ready for review now13:12
elynnWhich channel should I use to find the right guy to review? Qiming13:13
Qimingalso need to ping the rally team13:13
*** sdake has quit IRC13:13
yanyanhuyep13:13
Qimingopenstack-infra I think13:13
*** designbybeck has joined #openstack-meeting13:13
elynnThx13:14
yanyanhuI guess the first step is merging the patch to add gate job13:14
Qimingyes13:14
yanyanhuthen more plugins can be added13:14
Qimingand we can manage those plugins by ourselves13:14
yanyanhuyes, in senlin repo13:15
Qimingokay13:15
Qiming#action yanyan and elynn to push infra and rally gate reviews13:15
Qiminghealth management13:16
Qimingdon't think I have got any feed back on the etherpad13:16
*** timcline has quit IRC13:16
*** bobh has joined #openstack-meeting13:16
lixinhui_this topic is indeed complicated13:16
QimingI have started working on adding event listener to health manager13:16
*** eharney has quit IRC13:17
yanyanhusaw that patch you proposed13:17
Qiminghi, lixinhui_13:17
lixinhui_I saw your patch13:17
lixinhui_hi, Qiming13:17
lixinhui_fencing agent works now13:17
Qimingthe patch is about reorg the functions so that an event listener can be squeezed in13:17
lixinhui_just can not keep long run13:17
yanyanhuyes, it looks good13:17
Qimingfencing agent will crash?13:18
lixinhui_just stop response13:18
Qimingfencing agent should be just about some scripts13:18
*** klkumar has quit IRC13:18
lixinhui_have to reload it13:18
lixinhui_do not sure what will do?13:19
lixinhui_will we install the agent into Senlin profile13:19
lixinhui_?13:19
Qiminghaven't touch that thing for 2 years now13:19
lixinhui_me never :)13:19
Qimingcould be a new type of drivers I think13:19
lixinhui_?13:20
Qimingit will always be some model specific IPMI calls or something alike13:20
lixinhui_do you mean with some software intalling functions13:20
*** shaohe_feng has quit IRC13:20
*** shaohe_feng has joined #openstack-meeting13:21
lixinhui_what can be primary categories of model13:21
*** hichihara has joined #openstack-meeting13:21
QimingI was looking at openipmi13:21
xuhaiwei_do you want to do something keeping pinging the vms?13:21
Qimingthere are many other vendor specific interfaces I think13:21
Qimingxuhaiwei_, hi13:22
xuhaiwei_ping the vms to check if it is alive?13:22
xuhaiwei_yes, Qiming13:22
*** _amrith_ is now known as amrith13:23
lixinhui_no, that is detection part13:23
Qimingxuhaiwei_, it is doable, but cannot be sure: 1) the VMs have not blocked ICMP traffic, 2) cannot be sure the VM is dead if ping fails13:23
Qimingxinhui and I were talking about fencing13:23
Qimingthe term is called STONITH -- Shoot The Other Node In The Head13:23
xuhaiwei_oh, it seems tacker has a feature of pinging vms13:24
xuhaiwei_not very sure what you are talking about13:24
Qimingping is one way, but event if a ping fails, you cannot declare that VM is dead13:24
lixinhui_xuhaiwei_ are you investigating Taker these days?13:24
xuhaiwei_yes, lixinhui_, just installed it, don't know much about tacker13:25
lixinhui_s/Taker/tacker13:25
QimingI think he is investigating the integration of tacker and senlin?13:25
xuhaiwei_yes, Qiming13:25
Qiminggreat, I should help them, if they allow us to do that13:26
xuhaiwei_In fact I am investigating nfv need for tacker more13:26
Qimingokay13:26
*** vhoward has joined #openstack-meeting13:26
xuhaiwei_about auto-scaling feature in tacker, they seems not interested in senlin13:26
lixinhui_will NEC provide any SDN controller?13:26
Qimingtwo features needed from tacker side is HA and AutoScaling13:26
lixinhui_as backend of tacker?13:26
*** zz_dimtruck is now known as dimtruck13:27
*** ayoung has joined #openstack-meeting13:27
xuhaiwei_no definite task from my boss currently lixinhui_13:27
Qimingxuhaiwei_, they are not familiar with senlin13:27
QimingI left some comments to their specs13:27
lixinhui_where are the specs13:27
xuhaiwei_yes, I am not familiar with tacker too, need to investigate it and see if we can propose senile to them13:28
xuhaiwei_I saw your comments13:28
Qimingif they want to retry what we have failed, that is fine13:28
xuhaiwei_the current Heat PTL is reviewing tacker much now?13:28
Qimingin an open community, you cannot force others to do something they don't believe13:28
*** jamesmcarthur has joined #openstack-meeting13:28
Qimingxuhaiwei_, I don't think so13:29
xuhaiwei_at least he is a heat core13:29
Qimingit is a heat core from huawei13:29
xuhaiwei_I can't remember his name13:29
xuhaiwei_ok13:29
Qimingkind of misleading the tacker team ... sigh13:30
Qiminganyway13:30
Qimingdocumentation13:30
*** eharney has joined #openstack-meeting13:30
*** shaohe_feng has quit IRC13:30
Qimingresumed my work on adding tutorials13:30
Qimingneed to add a simple guide on how to achieve auto-scaling with and without heat13:31
Qimingand some simple tutorial on exercising the policies13:31
*** jprovazn has quit IRC13:31
QimingAPI documentation was cleansed13:31
Qimingit was a tedious work ...13:31
Qimingevery single parameter has to be reviewed several times13:32
Qiminghope it is done this time13:32
*** jprovazn has joined #openstack-meeting13:32
Qimingcontainer support13:32
Qimingxuhaiwei_, reviewed your patch13:32
xuhaiwei_thanks13:33
QimingI think we are touching some implementation details in the review13:33
Qimingfor example, a container cluster should memorize the 'hosting nodes' for each container13:33
xuhaiwei_since we got an agreement on adding a new property 'host' to Node api, I will start to implement it soon13:33
Qimingyes, that is true, we can decide where to put this data later13:33
Qimingit can be a policy data, can be a cluster data13:34
*** ildikov has quit IRC13:34
Qimingbut we don't have to worry about it13:34
*** ildikov has joined #openstack-meeting13:34
Qimingem...13:34
xuhaiwei_ok, I was not sure whether we needed to add a similar property to Cluster api13:35
xuhaiwei_it seems not now13:35
QimingI'm more worried about the placement policy implementation13:35
*** jprovazn has quit IRC13:35
Qimingxuhaiwei_, that can be driven by requests13:35
Qimingspeaking of extending the node-create api so that the 'host' can be specified, that would be useful13:36
*** jprovazn has joined #openstack-meeting13:36
*** Poornima has quit IRC13:36
QimingI was also thinking about adding a --profile parameter to the cluster-scale-out call, so that new nodes added can use a different profile13:36
*** fesp has joined #openstack-meeting13:36
Qimingit is for the use case of rolling upgrade13:37
xuhaiwei_the placement policy implementation depends on the existing nodes, but the current nodes are not a definite thing13:37
*** lblanchard has joined #openstack-meeting13:37
*** lblanchard has joined #openstack-meeting13:37
Qimingwhat do you mean by "not a definite thing"?13:37
xuhaiwei_I mean the vm cluster which will host the container cluster is not definite13:38
*** efried has joined #openstack-meeting13:38
Qimingthen we have the policy to handle that13:38
xuhaiwei_in placement policy we need to get the vm nodes information first13:38
Qimingyes13:38
Qimingeach time you do a placement decision, you will get all the nodes13:39
Qimingamong which, there could be some nodes newly added13:39
xuhaiwei_yes13:39
Qimingthose are things you will keep in mind when developing the policy, they are not blockers, right?13:40
*** fesp has quit IRC13:40
*** shaohe_feng_ has joined #openstack-meeting13:40
*** noslzzp has quit IRC13:40
*** noslzzp has joined #openstack-meeting13:40
xuhaiwei_a little complicated but not very difficult I think13:40
Qimingright13:40
*** shaohe_feng has joined #openstack-meeting13:41
Qimingokay, looking forward to your patches13:41
Qimingengine improvement13:41
*** shaohe_feng_ has quit IRC13:41
xuhaiwei_ok13:41
Qimingbatch control is done, removing line 34 now13:41
*** regXboi has joined #openstack-meeting13:42
Qimingas for line 33, NODE_CREATE, NODE_DELETE, I'm thinking of translating NODE_CREATE to CLUSTER_SCALE_OUT if cluster parameter is specified13:42
*** manikanta_tadi has quit IRC13:42
Qimingin that way, all cluster policies that can handle CLUSTER_SCALE_OUT action will automatically apply on the NODE_CREATE request13:43
*** jamesmcarthur has quit IRC13:43
Qimingjust a rough idea, haven't got time to think through yet13:43
lixinhui_sounds reasonable13:44
Qiminga brutal way is to remove --cluster from node-create call13:44
Qimingbut this is really a big hole we have to fix asap13:44
*** iceyao has joined #openstack-meeting13:45
Qimingor else, node-create calls can skip all policy checks ...13:45
*** amitgandhinz has joined #openstack-meeting13:45
Qimingplease find me on IRC if you have any suggestions on this13:45
Qimingreceiver of zaqar, no one is onto yet I believe13:46
*** amitgandhinz has quit IRC13:46
Qimingnotifications13:46
*** amitgandhinz has joined #openstack-meeting13:46
Qimingem, I read the versioned notification api spec in nova13:46
Qimingno matter we will do the same thing or not, that spec is a good writeup13:47
Qimingso, I have added a starting point for versioned objects13:47
*** phil_ has joined #openstack-meeting13:47
*** phil_ is now known as Guest386913:48
Qimingas I have noted in the commit message: oslo.versionedobjects will help serve two use cases -- live upgrade of senlin service; versioned notification13:48
xuhaiwei_a versioned notification api?13:48
Qimingyes, notification should be versioned13:48
Qimingwe need to control what senlin is saying to other services when it speaks13:48
xuhaiwei_control what?13:49
Qimingall contents should be predictable13:49
xuhaiwei_ohh13:49
Qimingsay, if senlin wants to post a message into zaqar or oslo.notification when a cluster is scaled out13:49
*** cdub has joined #openstack-meeting13:49
*** merooney has joined #openstack-meeting13:49
Qimingthere needs a spec for the message payload13:49
Qimingso the receiver can always expect that there will be a 'nodes' key which is a list of new nodes added, ...13:50
Qimingwe cannot assume that we will never change the content13:51
*** shaohe_feng has quit IRC13:51
Qimingso at the very beginning, we will do version control for this13:51
*** shaohe_feng has joined #openstack-meeting13:51
*** claudiub has quit IRC13:51
Qimingthanks god, we are a new service, we don't have to do a lot backward compatibility things13:51
*** klkumar has joined #openstack-meeting13:51
*** iyamahat has joined #openstack-meeting13:51
*** hoangcx has joined #openstack-meeting13:52
Qimingwe learned a lot from lessons in other services13:52
*** dasm has joined #openstack-meeting13:52
*** yamahata has joined #openstack-meeting13:52
xuhaiwei_yes13:52
Qiminganyone can jump in to that thread if interested13:52
Qimingwe may need to revised the db schema for this purpose13:53
Qimingadd a new multi-string option: "event_backend"13:53
Qimingthen the same event api can be used to save records into db or post messages to queue or BOTH ...13:54
*** jamesmca_ has joined #openstack-meeting13:54
*** anteaya has joined #openstack-meeting13:54
Qiming#topic open discussion13:54
*** openstack changes topic to "open discussion (Meeting topic: senlin)"13:54
lixinhui_https://review.openstack.org/#/c/318577/1/specs/newton/manual-and-auto-scaling.rst13:54
*** fnaval has joined #openstack-meeting13:54
*** liamji has joined #openstack-meeting13:55
lixinhui_is the link referred to the mentioned tacker AS discussion?13:55
Qimingthat is one of them13:56
elynnMaybe we can propose a spec based on senlin?13:56
Qimingalso this one: https://review.openstack.org/#/c/306562/13:56
Qimingelynn, we want to help13:56
*** cdub has quit IRC13:57
*** twm2016 has joined #openstack-meeting13:57
Qimingbut someone else should sign on get the job done13:57
*** diana_clarke has left #openstack-meeting13:58
*** Julien-zte has joined #openstack-meeting13:58
*** hynekm has joined #openstack-meeting13:58
*** MarkBaker has quit IRC13:58
*** rbak has joined #openstack-meeting13:58
*** boden has joined #openstack-meeting13:59
Qiminganything else?13:59
Qimingtime is up13:59
xuhaiwei_no13:59
lixinhui_no13:59
*** jaugustine has joined #openstack-meeting13:59
*** MarkBaker has joined #openstack-meeting13:59
Qimingthanks guys, already very late, good night13:59
Qiming#endmeeting13:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:59
openstackMeeting ended Tue May 24 13:59:48 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-05-24-13.02.html13:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-05-24-13.02.txt13:59
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-05-24-13.02.log.html13:59
*** jamesmca_ has quit IRC13:59
* dasm is ready for Neutron Team Meeting! FTW!14:00
mesteryo/14:00
*** slaweq has joined #openstack-meeting14:00
*** amuller has joined #openstack-meeting14:00
johndperkinshi14:01
amullerhiya14:01
*** janzian has joined #openstack-meeting14:01
akamyshnikovahi14:01
haleybhi14:01
ihrachys#startmeeting networking14:01
openstackMeeting started Tue May 24 14:01:11 2016 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: networking)"14:01
openstackThe meeting name has been set to 'networking'14:01
ihrachyshello my friends!14:01
njohnstono/14:01
HenryGo/14:01
slaweqhello14:01
yamahatahello14:01
*** shaohe_feng has quit IRC14:01
hoangcxhi14:01
ihrachysit's nice to see you all! :)14:01
amotokihi14:01
* ihrachys waves14:01
bodenhowdy  o/14:01
*** jlibosva has joined #openstack-meeting14:01
regXboio/ o\ o/14:01
*** jamesmca_ has joined #openstack-meeting14:01
ihrachysok, let's get it started14:02
twm2016o/14:02
*** shaohe_feng has joined #openstack-meeting14:02
ajo_o/14:02
ihrachys#link https://wiki.openstack.org/wiki/Network/Meetings Agenda14:02
*** HoloIRCUser has joined #openstack-meeting14:02
*** sbelous_ has joined #openstack-meeting14:02
bcafarelhi14:02
ihrachys#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:02
HoloIRCUserHi14:02
ihrachysas you should be aware of, newton-1 is already approaching14:02
*** HoloIRCUser is now known as reesip14:02
ihrachysit's actually happening in next week or two14:03
ihrachys#link http://releases.openstack.org/newton/schedule.html Release schedule14:03
*** hichihar_ has joined #openstack-meeting14:03
*** asingh has joined #openstack-meeting14:03
ihrachysto keep us focused on delivering what's scheduled, if not in N-1 then at least in N-final, please keep in mind the following...14:03
*** pc_m has joined #openstack-meeting14:04
yanyanhuQiming, xuhaiwei_ , host of node?14:04
yanyanhuif node is a VM managed by nova, how enduser could know the information about nova-compute nodes14:04
*** sudipto has joined #openstack-meeting14:04
xuhaiwei_hi yanyanhu14:04
ihrachysyanyanhu: please use another channel, we run a meeting. thanks.14:04
ihrachyswe have the review dashboard contributed by rossella_s14:04
ihrachys#link http://status.openstack.org/reviews/14:04
ihrachysnote the link at the top in "Gerrit Dashboard links" section14:05
*** bvandenh has quit IRC14:05
rossella_sthanks for mentioning this ihrachys14:05
*** xuhaiwei_ has quit IRC14:05
ihrachysit requires to be logged in, and it's personal (f.e. it hides your own patches, or patches that you voted)14:05
*** yamamoto has joined #openstack-meeting14:05
dasmrossella_s: thanks14:06
*** xenogear has joined #openstack-meeting14:06
ihrachysplease make sure that 1) we give priority to patches on that dashboard; 2) if you see a critical patch that is not there, please make sure the gerrit topic is correct (belonging to a bug or blueprint that is targeted for Newton)14:06
*** reesip has quit IRC14:06
ihrachysthat will hopefully help us not to loose focus.14:06
*** HoloIRCUser has joined #openstack-meeting14:06
ihrachysmore general announcements to come...14:06
ihrachys1. we have a mentoring program running, and people ask for help:14:06
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2016-May/095667.html14:07
ihrachysas per the email, it should not require too much time on your behalf, so please consider joining the good effort14:07
*** lixinhui_ has left #openstack-meeting14:07
*** cdub has joined #openstack-meeting14:07
* njohnston volunteered, heaven help his mentee14:07
rossella_snjohnston, thanks for that!14:07
ihrachysand another thing to mention, amuller was looking for more volunteers to get tempest tests for neutron to a better shape:14:07
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2016-May/094997.html14:08
dasmihrachys: i'm one of the mentors. can tell that it indeed doesn't require a lot of time.14:08
amullerThank you Ihar :)14:08
ihrachysI know tests are boring, but please consider doing what's right ;)14:08
rossella_sregarding mentoring people interested can ping me...I have been a mentor for a while for the outreachy program :)14:08
rossella_sihrachys ++14:08
*** bvandenh has joined #openstack-meeting14:09
*** fnaval has quit IRC14:09
ihrachysalso worth noting is the fact that the next Monday is a holiday in US.14:09
*** woodster_ has joined #openstack-meeting14:09
ihrachysso I am wondering what you think about when we will have the next one14:09
*** dslevin has joined #openstack-meeting14:10
ihrachyswe can keep it on Monday, and US folks will join on best effort, or we may skip it.14:10
dasmihrachys: second option seems to be good solution14:10
ihrachyseveryone in agreement with that ^?14:11
amotokiit depends on our PTL14:11
ihrachysor you are just sleepy :P14:11
*** Guest71132 is now known as dansmith14:11
ajo_if there's something important we can always reach out via email, but let's leave last call to our PTL may be?14:11
*** shaohe_feng has quit IRC14:11
ihrachysamotoki: the PTL suggested to reach out to you guys hence I am asking14:11
hichihar_N-1 closes limit14:12
*** dansmith is now known as Guest2162114:12
amullerWhy not have it a week from now?14:12
hichihar_N-1 is next week?14:12
amullerSo have it on this slot next week as a one time thing14:12
dasmamuller: tuesday?14:12
amulleryes14:12
ihrachysajo_: we will definitely render unto Caesar14:12
*** henrynash has quit IRC14:12
*** shaohe_feng has joined #openstack-meeting14:12
rossella_samuller, +114:12
ihrachysamuller: I suspect the slot will be used.14:12
dasmamuller: makes sense...14:12
ajo_amuller +1 : we can fall back to #openstack-neutron if the slot here is busy14:12
ihrachysbut we can run it in our channel14:12
*** absubram has quit IRC14:13
*** timcline has joined #openstack-meeting14:13
*** penick has joined #openstack-meeting14:13
* dasm is wondering what kind of mess we will have with next meetings :D14:13
ajo_lol14:13
amullerihrachys: indeed the slot is taken in this room next week14:13
yanyanhufor heat stack, host's definition is more confusing...14:13
*** hichihara has quit IRC14:13
yanyanhu#endmeeting14:14
*** moiz has joined #openstack-meeting14:14
*** Guest21621 is now known as dansmith14:14
ajo_yanyanhu, I believe you're talking on the wrong channel14:14
amotokiyanyanhu: wrong channel :(14:14
amullerihrachys: I never understood why IRC channels are a problem considering they're limitless, we can just have it on the main channel14:14
*** spzala has joined #openstack-meeting14:14
*** cody-somerville has joined #openstack-meeting14:14
*** cody-somerville has quit IRC14:14
*** cody-somerville has joined #openstack-meeting14:14
*** brad_behle has joined #openstack-meeting14:14
ihrachyssomeone is eager to end our meeting! :(14:14
dasmxD14:14
ajo_:')14:14
hichihar_;)14:14
*** yanyanhu has quit IRC14:14
ihrachysamuller: they say it's to avoid too much clash and allow people to join more of those held.14:14
*** dane_leblanc has joined #openstack-meeting14:14
*** spzala has quit IRC14:14
*** jamesmca_ has quit IRC14:14
dasmamuller: i've seen couple of meetings in regular channel. maybe it is good solution for next week?14:15
*** jckasper has quit IRC14:15
*** jckasper has joined #openstack-meeting14:15
*** julim has quit IRC14:15
dasmwith info on ML about temporary chnge14:15
dasm*change14:15
amotokituesday 22UTC looks open14:15
*** spotz_zzz is now known as spotz14:15
ihrachysok, let me update the PTL with ideas popping up here, and deliver it to armax. he will make a final call.14:15
dasm++14:16
hichihar_+114:16
njohnston+114:16
ihrachysfinal thing... armax naively said he will go to vacation the first two weeks of June14:16
*** merooney has quit IRC14:16
ihrachysso keep in mind he may be not that responsive as usual14:16
ihrachysmeaning, time to wait goes as far as 30 mins!14:17
*** bvandenh has quit IRC14:17
*** timcline has quit IRC14:17
ihrachysok, that's it on announcement front14:17
ihrachys#topic Gate14:17
*** openstack changes topic to "Gate (Meeting topic: networking)"14:17
*** jckasper_ has joined #openstack-meeting14:17
ihrachysas you probably know, a rare patch goes without a recheck these days due to functional test failures14:18
ihrachys#link https://bugs.launchpad.net/neutron/+bug/156766814:18
openstackLaunchpad bug 1567668 in neutron "Functional job sometimes hits global 2 hour limit and fails" [High,In progress] - Assigned to Jakub Libosvar (libosvar)14:18
*** ajmiller_ has joined #openstack-meeting14:18
ajo_armax, you can get rid of us for a couple of weeks, but it won't be forever!... lol. Enjoy your vacation :)14:18
*** sheel has joined #openstack-meeting14:18
ihrachysjlibosva: you were looking into it. is it still cloudy there?14:18
*** jckaspe__ has joined #openstack-meeting14:18
*** spzala has joined #openstack-meeting14:18
*** sridharg has quit IRC14:18
dasmit seems to be one of the patches: https://review.openstack.org/#/c/317369/14:18
jlibosvaI tried to come up with a workaround - anyone feel free to comment: https://review.openstack.org/#/c/317369/14:18
* ihrachys targeted the bug to n-114:19
jlibosvawhile running debugging patch with rechecks to gather yet more info of what's going on there14:19
*** bcafarel has quit IRC14:19
ihrachysok, let's continue in gerrit on that one. I feel you are in good hands with kevinbenton and otherwiseguy on the patch.14:20
ihrachyswe have more gate failure bugs reported14:20
ihrachys#link https://bugs.launchpad.net/neutron/+bugs?field.tag=gate-failure14:20
jlibosvaI consulted the workaround with otherwiseguy on impacts of that patch. Basically not blocking on select() passed more than 10 times in a row14:20
*** jckasper_ has quit IRC14:20
ihrachysjlibosva: great. what's the usual failure rate?14:20
*** phil_h has quit IRC14:20
jlibosvaihrachys: IIRC according graphite it's 40-50%14:20
*** penick has quit IRC14:21
ihrachysok, seems promising14:21
ihrachysso, back to the list of gate failure bugs I mentioned above14:21
ihrachyswe have some bugs that currently have no assignees there14:21
*** shaohe_feng has quit IRC14:21
ihrachysf.e. https://bugs.launchpad.net/neutron/+bug/1584920 or https://bugs.launchpad.net/neutron/+bug/158492314:22
openstackLaunchpad bug 1584920 in neutron "ExternalGatewayForFloatingIPNotFound exception raised in gate-tempest-dsvm-neutron-full" [High,New]14:22
openstackLaunchpad bug 1584923 in neutron "test_port_security_macspoofing_port fails with IndexError: list index out of range" [High,New]14:22
ihrachysit would be cool to see someone taking care of those orphans14:22
*** shaohe_feng has joined #openstack-meeting14:22
ihrachysany volunteers?14:22
dasmwill try to do this: https://bugs.launchpad.net/neutron/+bug/158492314:23
openstackLaunchpad bug 1584923 in neutron "test_port_security_macspoofing_port fails with IndexError: list index out of range" [High,New] - Assigned to Darek Smigiel (smigiel-dariusz)14:23
*** HoloIRCUser has quit IRC14:23
ihrachysdasm: ok, please assign it to yourself if you will work on it.14:23
dasmihrachys: done14:23
*** elynn has left #openstack-meeting14:23
yamamotodasm: i think https://review.openstack.org/#/c/251423/ also fixes that bug14:23
ihrachysoh you did. thanks.14:23
*** fwdit has quit IRC14:23
*** aranjan has quit IRC14:23
*** dneary_ has joined #openstack-meeting14:24
dasmyamamoto: oh. thanks. i'll look into this14:24
*** rossella_s has quit IRC14:24
jckasper14:24
*** sacharya has joined #openstack-meeting14:24
*** jckasper has quit IRC14:24
ihrachysyamamoto: hm. is it a dup?14:24
*** rossella_s has joined #openstack-meeting14:24
dasmihrachys: seems to be14:24
*** jamesmcarthur has joined #openstack-meeting14:24
*** sacharya has quit IRC14:24
yamamotoi haven't looked 1584923 but i guess so14:24
ihrachysdasm: ok. let's check it and mark appropriately if that's the case.14:24
dasmihrachys: yamamoto. will check14:25
ihrachysanyone to take care of  https://bugs.launchpad.net/neutron/+bug/1584920 ?14:25
openstackLaunchpad bug 1584920 in neutron "ExternalGatewayForFloatingIPNotFound exception raised in gate-tempest-dsvm-neutron-full" [High,New]14:25
*** merooney has joined #openstack-meeting14:26
ihrachysok, we'll find someone. or not.14:26
carl_baldwinI'll work on finding someone.14:26
*** jckaspe__ has quit IRC14:26
carl_baldwinOr, take it later this week.14:26
ihrachysthanks Carl!14:26
ihrachysthat's the spirit :)14:27
*** lixinhui_ has joined #openstack-meeting14:27
*** hongbin has joined #openstack-meeting14:27
dasmcarl_baldwin: round robin? )14:27
dasm:)14:27
*** hongbin has left #openstack-meeting14:27
ihrachysok, let's hope we have the most burning gate issues taken care of. let's move on.14:27
ihrachys#topic Bugs14:27
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:27
ihrachyshichihar_: you were the latest deputy. do you have anything significant to report?14:28
ihrachyswere docs sufficient for you to run with the role?14:28
hichihar_ihrachys: Nothing. It was a quiet last week although it seems this week was exciting... :P14:28
*** rhagarty has joined #openstack-meeting14:28
*** lixinhui_ has quit IRC14:28
carl_baldwinI can confirm that, I've already go a backlog of new bugs I'm working through.14:29
ihrachysok, let's make sure no bugs don't fall thru the cracks and we pass the role to the next deputy with some overlap14:29
carl_baldwin:)14:29
carl_baldwinThat's me!14:29
*** Mr__T has left #openstack-meeting14:29
* ihrachys bows to the mightly ubiquitous Carl14:30
ihrachys*mighty14:30
ihrachys#topic Docs14:30
ajo_I've signed up for the next slot, after migthy  carl_baldwin and kevinbenton14:30
*** openstack changes topic to "Docs (Meeting topic: networking)"14:30
ihrachysI don't see Sam-I-Am here14:30
*** slaweq has quit IRC14:30
ihrachysanyone want to update on docs front?14:30
*** ajmiller has quit IRC14:31
*** jamesmcarthur has quit IRC14:31
*** dneary has quit IRC14:31
*** asingh has quit IRC14:31
ihrachysok, I guess we skip it14:31
ihrachys#topic Open Discussion14:32
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"14:32
ihrachysthe agenda on demand agenda is empty14:32
*** shaohe_feng has quit IRC14:32
hichihar_Client?14:32
ihrachysso if anyone has a thing to raise, please do14:32
ihrachyshichihar_: what's about it?14:32
ajo_#link https://review.openstack.org/#/c/320439/14:32
*** slaweq has joined #openstack-meeting14:32
*** shaohe_feng has joined #openstack-meeting14:32
*** sridharg has joined #openstack-meeting14:32
hichihar_I thought we have client section in meeting.14:32
ajo_if anybody has time and interest, I have put for review an spec related to flow management in the l2-agent ovs extensions14:32
hichihar_It may be my misunderstand.14:33
ihrachyshichihar_: not in the official agenda but we can discuss it now. do you have anything on your mind worth attention of the whole team?14:33
dasmihrachys: hichihar_ is right. last time we had transition to osc and keystonev314:33
*** HoloIRCUser2 has joined #openstack-meeting14:33
*** jckasper has joined #openstack-meeting14:33
*** banix has joined #openstack-meeting14:34
*** HoloIRCUser2 has joined #openstack-meeting14:34
hichihar_I don't have idea about client but client folks?14:34
ihrachysdasm: if we think it's worth a stable topic in the agenda, let's edit the wiki page to make sure it's covered: https://wiki.openstack.org/wiki/Network/Meetings14:34
*** john-davidge_ has joined #openstack-meeting14:34
dasmihrachys: will do.14:34
amotokiwe have a lot of time remaining. let's discuss ajo_'s and move other later.14:34
*** Julien-z_ has joined #openstack-meeting14:34
amotokii forgot to add the client topic to the agenda.14:34
*** e0ne has joined #openstack-meeting14:34
ihrachysok, let's do the ajo_'s topic14:35
ihrachysajo_: do you plan for more details on the matter, or that's it, and we will see more when we come to implementation?14:35
ajo_it doesn't need a lot of discussion here probably, but I just wanted to raise awareness14:35
*** e0ne_ has quit IRC14:35
ajo_ihrachys, I didn't want to drill down into the implementation details if not necessary, we can discuss that over code if the high level is clear14:35
*** phil_h has joined #openstack-meeting14:36
ajo_may be we can define more clearly how the API interface itself will change to allow this, for example14:36
ihrachysI see. one thing worth mentioning there is how we are going to test it performance wise. introducing lots of redirections and tables may not be easy on the switch (?)14:36
*** Julien-zte has quit IRC14:37
*** aliadil has quit IRC14:37
*** amitgandhinz has quit IRC14:37
*** askb has quit IRC14:37
ajo_ihrachys, well, you will have the same amount of redirections if you have the same extensions happening14:37
ajo_ihrachys,  the only thing is that you will have the non interoperability14:37
ajo_ihrachys, ovs firewall has already lots of table jumps, and it's still faster than iptables fw14:37
*** amitgandhinz has joined #openstack-meeting14:37
ihrachysI see. anyway, I guess it does not required a discussion here and can be postponed to gerrit.14:38
ajo_ihrachys, ack, btw, the fixed parts that I'm proposing in the pipeline, are mostly taken from ovs firewall itself14:38
ajo_all of them, in fact :)14:38
ihrachysanything more to cover? amotoki, wanna do the client update?14:38
amotokire client, we are reviewing the initial OSC plugin support: https://review.openstack.org/#/c/309587/ it seems close to merge.14:38
amotokionce it is merged, we will enable OSC plugin gate in the openstack client side.14:39
amotokiin addition, I am preparing a devref on command namespaces in neutron osc plugin.14:39
*** marios_ has joined #openstack-meeting14:40
amotokiwe see dynamic-routing folks are active to implement osc plugin commands. we will support them.14:40
*** jaypipes has quit IRC14:40
*** hasharAw is now known as hashar14:40
amotokithat's the update. in the summit, we agree that we have the osc transition status in our meeting.14:41
*** brad_behle_ has joined #openstack-meeting14:41
*** ssalagame has joined #openstack-meeting14:41
ihrachysamotoki: good progress14:41
amotokiI will add a topic to the meeting agenda after the meeting.14:41
ihrachysamotoki: yeah, please update the agenda, I missed that point.14:41
ihrachysthanks14:41
dasmso maybe i'll give status about keystone v3.14:41
ihrachysdasm: please do14:42
dasmfirst patch for neutronclient was sent yesterday: https://review.openstack.org/#/c/320090/14:42
*** ssalagame has quit IRC14:42
*** shaohe_feng has quit IRC14:42
dasmi noticed errors on nova, because made wrong assumption. will update it today14:42
*** cody-somerville has quit IRC14:42
*** moiz has quit IRC14:42
*** anteaya has quit IRC14:42
*** noslzzp has quit IRC14:42
*** lblanchard has quit IRC14:42
*** toddjohn has quit IRC14:42
*** zhurong has quit IRC14:42
*** david-lyle has quit IRC14:42
*** beisner has quit IRC14:42
*** aysyd has quit IRC14:42
*** wznoinsk has quit IRC14:42
*** cebruns has quit IRC14:42
*** homerp has quit IRC14:42
*** marios has quit IRC14:42
*** Douhet has quit IRC14:42
*** cwolferh has quit IRC14:42
*** Swanson has quit IRC14:42
*** markmcclain has quit IRC14:42
*** hugokuo has quit IRC14:42
*** Yingxin has quit IRC14:42
*** brad_behle has quit IRC14:42
*** designbybeck has quit IRC14:42
*** john-davidge has quit IRC14:42
*** yuval has quit IRC14:42
*** dolphm has quit IRC14:42
*** rbartal has quit IRC14:42
*** nelsnels_ has quit IRC14:42
*** bkero has quit IRC14:42
*** neiljerram has quit IRC14:42
*** rmk has quit IRC14:42
HoloIRCUser2amotoki: post this, would lbaas etc. be enabled as plugin?14:42
*** brad_behle_ is now known as brad_behle14:42
dasmthat's all for now in keystone v3 topic14:43
*** shaohe_feng has joined #openstack-meeting14:43
amotokiHoloIRCUser2: yes. all commands related to advanced services will go to the OSC plugin way.14:43
ihrachysthanks dasm for the update.14:43
*** ajmiller_ has quit IRC14:43
HoloIRCUser2amotoki: okay, great....14:43
* ihrachys notes we experience netsplit14:44
ihrachysok, I guess that's all we have for today.14:44
ihrachyskeep up the good work folks!14:45
*** bcafarel has joined #openstack-meeting14:45
ihrachys#endmeeting14:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:45
openstackMeeting ended Tue May 24 14:45:05 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-05-24-14.01.html14:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-05-24-14.01.txt14:45
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-05-24-14.01.log.html14:45
*** _d34dh0r53_ is now known as d34dh0r5314:45
*** twm2016 has left #openstack-meeting14:45
yamamotobye14:45
hichihar_bye14:45
* ihrachys is glad openstack bot is on my side of the split14:45
ihrachysciao14:45
*** regXboi has quit IRC14:46
*** sbelous_ has left #openstack-meeting14:46
*** janzian has left #openstack-meeting14:46
*** boden has left #openstack-meeting14:46
*** pc_m has left #openstack-meeting14:46
dasmo/14:47
*** jlibosva has quit IRC14:47
*** rcernin has quit IRC14:47
*** mlavalle has joined #openstack-meeting14:49
*** anilvenkata has quit IRC14:49
*** mlavalle has left #openstack-meeting14:49
*** sdake has joined #openstack-meeting14:49
*** edtubill has joined #openstack-meeting14:49
*** hichihar_ has quit IRC14:49
*** jckasper_ has joined #openstack-meeting14:51
*** dneary_ is now known as dneary14:52
*** jckasper has quit IRC14:52
*** shaohe_feng has quit IRC14:52
*** jckasper_ has quit IRC14:52
*** jckasper has joined #openstack-meeting14:53
*** asingh has joined #openstack-meeting14:53
*** hynekm has left #openstack-meeting14:54
*** hoangcx has quit IRC14:54
*** jaypipes has joined #openstack-meeting14:55
*** weshay has joined #openstack-meeting14:55
*** shaohe_feng has joined #openstack-meeting14:55
*** jamesmcarthur has joined #openstack-meeting14:56
*** links has quit IRC14:57
*** Leo_ has joined #openstack-meeting14:57
*** asettle has quit IRC14:58
*** trandles has joined #openstack-meeting14:58
*** asettle has joined #openstack-meeting14:58
*** rcernin has joined #openstack-meeting14:59
*** HoloIRCUser3 has joined #openstack-meeting14:59
*** jamesmcarthur has quit IRC14:59
carl_baldwinHi.  Turns out I can't make the meeting today.  I will send something to the mailing list.14:59
xiaohhuiok14:59
*** mlavalle has joined #openstack-meeting15:00
*** julim has joined #openstack-meeting15:00
HoloIRCUser3Hi15:01
blogancarl_baldwin: :(15:01
*** marios_ has quit IRC15:01
*** jdurgin1 has joined #openstack-meeting15:01
HoloIRCUser3And to think I joined the meeting this time ....15:01
*** marios_ has joined #openstack-meeting15:01
*** ssalagame has joined #openstack-meeting15:01
mlavalle#startmeeting Routed Networks15:02
openstackMeeting started Tue May 24 15:02:02 2016 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** sajeesh has joined #openstack-meeting15:02
*** openstack changes topic to " (Meeting topic: Routed Networks)"15:02
openstackThe meeting name has been set to 'routed_networks'15:02
*** absubram has joined #openstack-meeting15:02
*** HoloIRCUser2 has quit IRC15:02
xiaohhuiSo we will still have the meeting, right?15:02
HoloIRCUser3M sorry my nick isn't changing15:02
*** shaohe_feng has quit IRC15:02
mlavalleCarl had an unexpected meeting15:03
*** shaohe_feng has joined #openstack-meeting15:03
xiaohhuiLet's have the sync up15:03
mlavallexiaohhui, blogan: carl_baldwin has an unexpected meeting. He won't be able to make it to this one15:03
*** amitgandhinz has quit IRC15:03
bloganmlavalle: alrighty15:04
*** RuiChen has quit IRC15:04
mlavallexiaohhui, blogan: we can definetely have the meeting today ourselves15:04
*** amitgandhinz has joined #openstack-meeting15:04
xiaohhuiok15:04
HoloIRCUser3Count me in as well mlavalle (it's reedip here)15:04
*** Qiming has quit IRC15:04
jschwarz\o/15:05
mlavallexiaohhui, blogan: Carl is going to send a message to the ML, proposing to do an email update15:05
bloganHoloIRCUser3: interesting name reedip15:05
HoloIRCUser3Its from an App on the fone15:06
*** e0ne has quit IRC15:06
xiaohhuireedip: are you still working on this patch https://review.openstack.org/30464715:06
mlavallexiaohhui, blogan, HoloIRCUser3, jschwarz: but we can go on here....15:06
*** jamesmcarthur has joined #openstack-meeting15:06
HoloIRCUser3Stupid app doesn't let me change the NICK15:06
mlavalle#topic Announcements15:06
*** openstack changes topic to "Announcements (Meeting topic: Routed Networks)"15:06
*** merooney has quit IRC15:06
bloganmlavalle: ok lets do it15:06
bloganHoloIRCUser3: sounds like a limited app :)15:06
mlavalleKeep in mind that Newton-1 is a little more than a week ago15:06
HoloIRCUser3xiaohhui : I will start from tomorrow... I shifted from Japan to India in between the Austin Summit so my whole work was haywired15:07
mlavalleAny other announcements from the team?15:07
mlavalleIf not, let's move on...15:08
mlavalle#topic Progress Reports15:08
*** openstack changes topic to "Progress Reports (Meeting topic: Routed Networks)"15:08
mlavalleAs I said earlier, carl_baldwin is going to send his progress report to the ML. So, let's start with DHCP15:09
mlavalleblogan: you are up15:09
*** merooney has joined #openstack-meeting15:09
*** trandles has left #openstack-meeting15:10
bloganso I've per the ML thread I reworked the scheduling a bit back to where I initially had it15:10
bloganhttps://review.openstack.org/#/c/311931/15:10
*** yamamoto has quit IRC15:11
bloganit's still a wip and its not pretty and it still needs tests but i ddidn't want to write tests until the direction is solidified15:11
*** sridharg has quit IRC15:11
*** xiaohhui has quit IRC15:11
*** dneary has quit IRC15:12
*** sgotliv_ has quit IRC15:12
bloganthe not pretty part is because we need to bind a dchp agent to a segment ONLY when segment's exist, otherwise we need to do it by the network.  however, the base scheduler and base resource filter's interface don't expect that15:12
bloganso that interface doesn't work in this case, and if i change that interface it'll probably break out of tree schedulers like bgp15:13
*** shaohe_feng has quit IRC15:13
bloganits a very hairy problem15:13
*** timcline has joined #openstack-meeting15:13
*** merooney has quit IRC15:13
mlavalleblogan: do you need any help?15:14
bloganin the meantime ive been working on the agent side of things, to make it segment aware, and that is definitely shaping up to be a large effort15:14
bloganmlavalle: just help in the sense of needing some ideas on how to solve that particular issue15:14
*** dneary has joined #openstack-meeting15:14
*** jamesmcarthur has quit IRC15:14
mlavalleblogan: post ideas in the reviw?15:15
mlavallereview^^^15:15
bloganmlavalle: yeah, that'd be good15:15
*** jrist has quit IRC15:15
*** xiaohhui has joined #openstack-meeting15:15
mlavalleblogan: I will take a look later today15:16
bloganill comment where the ugliness is15:16
bloganon the review15:16
*** brad_behle has left #openstack-meeting15:16
jschwarzwill also take a look at it tomorrow15:16
*** amrith is now known as _amrith_15:17
*** yamamoto has joined #openstack-meeting15:17
mlavalleanything else blogan?15:18
*** timcline has quit IRC15:18
*** e0ne has joined #openstack-meeting15:18
*** rderose has joined #openstack-meeting15:18
bloganmlavalle: nope that's it for now, just want to reiterate the agent side of it will be more work than I expected nad probably any of us expected :)15:19
mlavalleblogan: will you need help with that piece?15:19
*** dmorita has joined #openstack-meeting15:20
*** amuller is now known as amuller_afk15:20
bloganmlavalle: I can probably break the tasks up into chunks so that other's can take them if they want, otherwise i can chip away at it15:21
*** sudipto has quit IRC15:21
mlavalleok15:21
mlavallelet's move on15:21
bloganthanks mlavalle15:21
mlavalle#topic Host Segments mappping15:21
*** openstack changes topic to "Host Segments mappping (Meeting topic: Routed Networks)"15:21
mlavalleON this subject we made great progress last wekk15:22
mlavallelast week^^^15:22
*** henrynash has joined #openstack-meeting15:22
*** jlanoux has quit IRC15:22
xiaohhuigreat!15:22
mlavallehttps://review.openstack.org/#/c/285548/ got +2ed by carl_baldwin and +1ed by xiaohhui . Thanks for all the help with reviews15:23
*** shaohe_feng has joined #openstack-meeting15:23
*** yamamoto has quit IRC15:24
mlavalleafter xiaohhui rechecked it last night, some test cases in neutron.tests.unit.agent.test_securitygroups_rpc started failing15:24
xiaohhuiI think it has been fixed15:24
xiaohhuijust a rebase can resolve it15:24
*** asettle has quit IRC15:25
mlavallexiaohhui: great, thanks for saving me some research time. I was so frustrated a few minutes ago :-)15:25
bloganhopefully there aren't conflicts15:25
*** xenogear has quit IRC15:25
*** dmorita has quit IRC15:25
mlavalleso moving on...15:25
mlavalle#topic Enable Create / Delete of Segments on Existing Network in ML215:26
*** openstack changes topic to "Enable Create / Delete of Segments on Existing Network in ML2 (Meeting topic: Routed Networks)"15:26
mlavallexiaohhui: this is you, right?15:26
xiaohhuiyeah15:26
xiaohhuiThe code is ready for review15:26
xiaohhuihttps://review.openstack.org/#/c/31735815:26
xiaohhuiI hope you guys can reiview it15:27
*** sridharg has joined #openstack-meeting15:27
mlavalleyeah will take a look today also15:27
mlavallethanks for pushing this forward.... anything else on this topic?15:27
*** comay has quit IRC15:28
xiaohhuiI think there is nothing else15:28
mlavallesince xiaohhui has the mike already...15:28
mlavalle#topic OVN plugin15:28
*** openstack changes topic to "OVN plugin (Meeting topic: Routed Networks)"15:28
xiaohhuiThe patch from richard has been merged. https://review.openstack.org/#/c/312705/15:29
xiaohhui(Convert core plugin to ML2 mechanism driver)15:29
xiaohhuiBut the ovn part is still no progress, I think it would be better to move on, once the ml2 code has settled.15:30
mlavallexiaohhui: ok15:30
xiaohhuiMaybe we can update the host / segment mapping for ovn, once your patch has been merged.15:30
*** tonytan4ever has joined #openstack-meeting15:31
xiaohhuiThere is a wip patch for it, I will re-evaluate it this week. https://review.openstack.org/#/c/302623/15:31
mlavallexiaohhui: yeah, I expect that to merge any time soon.... especially after your big help of a few minutes ago ;-)15:31
xiaohhui:)15:32
*** galstrom_zzz is now known as galstrom15:32
mlavallemoving on then ...15:32
xiaohhuiNothing else for OVN from me.15:32
*** nadya has quit IRC15:33
mlavalle#topic Integration with Nova Scheduler15:33
*** openstack changes topic to "Integration with Nova Scheduler (Meeting topic: Routed Networks)"15:33
mlavalleON this front, I had a conversation with cdent earlier today15:33
*** shaohe_feng has quit IRC15:33
mlavalleHe is implementing the code for generic resource pools in Nova15:34
*** shaohe_feng has joined #openstack-meeting15:34
*** salv-orlando has quit IRC15:34
mlavalleThere are several patches for this. The top of the stack is here: https://review.openstack.org/#/c/293104/15:34
mlavalleI intend to follow this work closely and help with reviews where I can15:35
*** jschwarz has quit IRC15:35
mlavalleAlso johnthetubaguy has pushed revisions to https://review.openstack.org/#/c/31300115:35
*** cdelatte has quit IRC15:35
mlavalleMaybe he cares to comment about it?15:35
*** links has joined #openstack-meeting15:36
mlavalleThis is the refactoring of 'allocate_for_instance' in Nova compute that allocates network resources for instances15:36
*** comay has joined #openstack-meeting15:36
*** julim has quit IRC15:37
*** adiantum has quit IRC15:37
mlavalleit is being refactored, some pieces to the conductor, pre-scheduling, so segments data con be used in the scheduling decision15:37
*** puiterwijk has joined #openstack-meeting15:37
*** enriquetaso has joined #openstack-meeting15:37
mlavalleIn any case I intend to review that spec and help where I can15:37
mlavalleFinally, I attended yesterday's Nova Scheduler meeting and reminded people to post reviews for the Routed Networks spec for Nova: https://review.openstack.org/#/c/263898/15:38
bloganill review too, more for my own learning though :)15:38
*** ihrachys has quit IRC15:39
mlavalleSeveral of them said they are going to review it: johnthetubaguy, bauzas, edleafe15:39
mlavallethat's it for this week on this topic15:39
*** julim has joined #openstack-meeting15:39
*** leeantho has joined #openstack-meeting15:40
*** singhj has joined #openstack-meeting15:40
*** fnaval has joined #openstack-meeting15:40
*** aliadil has joined #openstack-meeting15:40
*** claudiub|2 has joined #openstack-meeting15:40
*** designbybeck has joined #openstack-meeting15:40
*** dolphm has joined #openstack-meeting15:40
*** rbartal has joined #openstack-meeting15:40
*** nelsnels_ has joined #openstack-meeting15:40
*** bkero has joined #openstack-meeting15:40
*** neiljerram has joined #openstack-meeting15:40
*** rmk has joined #openstack-meeting15:40
*** wilhelm.freenode.net changes topic to "newton work items (Meeting topic: senlin)"15:40
mlavalle#topic L2 Adjacency Extension15:40
*** openstack changes topic to "L2 Adjacency Extension (Meeting topic: Routed Networks)"15:40
*** aliadil has quit IRC15:40
*** aliadil has joined #openstack-meeting15:40
mlavalleHoloIRCUser3: are you still woking on https://review.openstack.org/#/c/304647/?15:40
*** adisky has joined #openstack-meeting15:41
*** salv-orlando has joined #openstack-meeting15:41
HoloIRCUser3Mlavalle:yeah, will restart it tomorrow15:41
HoloIRCUser3Sorry for the delay15:42
mlavalleto begin with, it needs a rebase :-)15:42
HoloIRCUser3I shifted from Japan to India15:42
HoloIRCUser3So things have been a bit messy for now15:42
mlavalleahhh. How do you like being back in the Mother Land?15:42
*** jamesmcarthur has joined #openstack-meeting15:42
HoloIRCUser3Not different... having stayed almost a year in Japan makes me feel both are pretty good places to live and love...15:43
*** adiantum has joined #openstack-meeting15:43
mlavalle:-)15:43
HoloIRCUser3:) thanks for asking though...15:43
mlavalleany thing else on this topic?15:43
*** shaohe_feng has quit IRC15:43
*** ljxiash has quit IRC15:44
mlavalleif not, let's move on...15:44
HoloIRCUser3Not from my end for now... wll be back in the meeting tomorrow...15:44
mlavalle#topic Client15:44
*** openstack changes topic to "Client (Meeting topic: Routed Networks)"15:44
*** aliadil has quit IRC15:45
mlavallertheis: anything to report on client for Routed Networks?15:45
*** synegy34 has joined #openstack-meeting15:45
xiaohhuirichard mentioned to me yesterday that he may be not able to attend this meeting.15:45
rtheisback from the dentist just in time15:45
rtheiswe have SDK patch merged for network segments15:45
*** shaohe_feng has joined #openstack-meeting15:45
*** delattec has joined #openstack-meeting15:45
*** sudipto_ has joined #openstack-meeting15:45
*** ajmiller_ has joined #openstack-meeting15:45
*** moiz has joined #openstack-meeting15:45
*** anteaya has joined #openstack-meeting15:45
*** noslzzp has joined #openstack-meeting15:45
*** lblanchard has joined #openstack-meeting15:45
*** toddjohn has joined #openstack-meeting15:45
*** david-lyle has joined #openstack-meeting15:45
*** beisner has joined #openstack-meeting15:45
*** aysyd has joined #openstack-meeting15:45
*** wznoinsk has joined #openstack-meeting15:45
*** cebruns has joined #openstack-meeting15:45
*** homerp has joined #openstack-meeting15:45
*** Douhet has joined #openstack-meeting15:45
*** cwolferh has joined #openstack-meeting15:45
*** Swanson has joined #openstack-meeting15:45
*** markmcclain has joined #openstack-meeting15:45
*** hugokuo has joined #openstack-meeting15:45
*** Yingxin has joined #openstack-meeting15:45
*** wilhelm.freenode.net changes topic to "Announcements (Meeting topic: networking)"15:45
*** ajmiller_ has quit IRC15:45
*** ajmiller_ has joined #openstack-meeting15:45
mlavallertheis: lol.... you are not in pain right?15:45
*** shaohe_feng has quit IRC15:45
*** shaohe_feng has joined #openstack-meeting15:45
rtheismlavalle: no pain, just a cleaning today15:46
HoloIRCUser3rtheis: lucky u... I connected via the fone while driving( now home)15:46
*** tfukushima has quit IRC15:46
*** jrist has joined #openstack-meeting15:46
*** hashar is now known as hasharAway15:46
rtheisI am going to rebase the CLI patch set and then it should be ready15:46
*** beisner has quit IRC15:46
* mlavalle stalled enough, so rtheis could make his report on time15:47
*** brucet_ has joined #openstack-meeting15:47
*** jrist has quit IRC15:47
rtheisnothing else from me  on client15:47
mlavallertheis: thanks for the status report15:48
rtheisyw15:48
*** jrist has joined #openstack-meeting15:48
mlavallemoving on...15:48
*** gatekeep has quit IRC15:48
*** brucet has joined #openstack-meeting15:48
mlavalle#topic Open Agenda15:48
*** openstack changes topic to "Open Agenda (Meeting topic: Routed Networks)"15:48
*** beisner has joined #openstack-meeting15:48
mlavalledid I miss anyone?15:48
*** KanagarajM has joined #openstack-meeting15:48
*** lblanchard has quit IRC15:48
*** marios_ has quit IRC15:48
*** penick has joined #openstack-meeting15:49
*** marios has joined #openstack-meeting15:49
*** KanagarajM has left #openstack-meeting15:49
mlavalleany other topics to bring to the team?15:49
*** lblanchard has joined #openstack-meeting15:49
*** yamamoto has joined #openstack-meeting15:49
*** marios is now known as Guest9795415:49
*** jamesmca_ has joined #openstack-meeting15:49
mlavalleIn that case, we will return 10 minutes to everybody's agenda15:50
mlavalleThanks for attending and for your reports !15:50
mlavalle#endmeeting15:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:50
openstackMeeting ended Tue May 24 15:50:43 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/routed_networks/2016/routed_networks.2016-05-24-15.02.html15:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/routed_networks/2016/routed_networks.2016-05-24-15.02.txt15:50
openstackLog:            http://eavesdrop.openstack.org/meetings/routed_networks/2016/routed_networks.2016-05-24-15.02.log.html15:50
*** Guest97954 is now known as marios15:50
*** belmoreira has quit IRC15:51
*** jamesmcarthur has quit IRC15:51
*** jdurgin1 has quit IRC15:52
*** mlavalle has left #openstack-meeting15:53
*** gyee has joined #openstack-meeting15:53
*** AndChat|105216 has joined #openstack-meeting15:53
*** brucet_ has quit IRC15:54
*** shaohe_feng has quit IRC15:54
*** sridharg has quit IRC15:54
*** jamesmca_ has quit IRC15:54
*** shaohe_feng has joined #openstack-meeting15:54
*** Swami has joined #openstack-meeting15:55
*** numans has quit IRC15:55
*** morgabra has quit IRC15:55
*** morgabra has joined #openstack-meeting15:55
*** AndChat-105216 has joined #openstack-meeting15:55
*** AndChat|105216 has quit IRC15:55
*** KanagarajM has joined #openstack-meeting15:56
*** dneary has quit IRC15:56
*** brucet has quit IRC15:56
*** HoloIRCUser3 has quit IRC15:56
*** timcline has joined #openstack-meeting15:56
*** timcline has quit IRC15:56
*** paul-carlton2 has quit IRC15:56
*** timcline has joined #openstack-meeting15:57
*** yamamoto has quit IRC15:57
*** jrist has quit IRC15:57
*** delattec has quit IRC15:57
*** sudipto_ has quit IRC15:57
*** ajmiller_ has quit IRC15:57
*** moiz has quit IRC15:57
*** anteaya has quit IRC15:57
*** noslzzp has quit IRC15:57
*** toddjohn has quit IRC15:57
*** david-lyle has quit IRC15:57
*** aysyd has quit IRC15:57
*** wznoinsk has quit IRC15:57
*** cebruns has quit IRC15:57
*** homerp has quit IRC15:57
*** Douhet has quit IRC15:57
*** cwolferh has quit IRC15:57
*** Swanson has quit IRC15:57
*** markmcclain has quit IRC15:57
*** hugokuo has quit IRC15:57
*** Yingxin has quit IRC15:57
*** armax has joined #openstack-meeting15:57
*** cody-somerville has joined #openstack-meeting15:57
*** weshay has quit IRC15:58
*** AndChat-105216 has quit IRC15:59
*** jamesmcarthur has joined #openstack-meeting15:59
*** manikanta_tadi has joined #openstack-meeting16:00
*** cody-somerville has quit IRC16:00
*** matrohon has quit IRC16:02
*** toddjohn has joined #openstack-meeting16:02
*** twm2016 has joined #openstack-meeting16:02
*** shaohe_feng has quit IRC16:04
*** shaohe_feng has joined #openstack-meeting16:05
*** jlanoux has joined #openstack-meeting16:06
*** jrist has joined #openstack-meeting16:06
*** delattec has joined #openstack-meeting16:06
*** sudipto_ has joined #openstack-meeting16:06
*** ajmiller_ has joined #openstack-meeting16:06
*** moiz has joined #openstack-meeting16:06
*** noslzzp has joined #openstack-meeting16:06
*** david-lyle has joined #openstack-meeting16:06
*** aysyd has joined #openstack-meeting16:06
*** wznoinsk has joined #openstack-meeting16:06
*** cebruns has joined #openstack-meeting16:06
*** homerp has joined #openstack-meeting16:06
*** Douhet has joined #openstack-meeting16:06
*** cwolferh has joined #openstack-meeting16:06
*** Swanson has joined #openstack-meeting16:06
*** markmcclain has joined #openstack-meeting16:06
*** hugokuo has joined #openstack-meeting16:06
*** Yingxin has joined #openstack-meeting16:06
*** amuller_afk has left #openstack-meeting16:07
*** anteaya has joined #openstack-meeting16:07
*** jamesmcarthur has quit IRC16:08
*** yamamoto has joined #openstack-meeting16:08
*** lezbar has joined #openstack-meeting16:09
*** paul-carlton2 has joined #openstack-meeting16:12
*** kmartin has quit IRC16:12
*** shaohe_feng has quit IRC16:14
*** e0ne has quit IRC16:14
*** Guest3869 has quit IRC16:14
*** Julien-z_ has quit IRC16:14
*** dslevin has quit IRC16:15
*** slaweq has quit IRC16:15
*** lakshmiS has joined #openstack-meeting16:15
*** shaohe_feng has joined #openstack-meeting16:15
*** HeOS has quit IRC16:16
*** jtomasek_ has quit IRC16:16
*** slaweq has joined #openstack-meeting16:16
*** twm2016 has left #openstack-meeting16:16
*** nkrinner is now known as nkrinner_afk16:16
*** jamesmcarthur has joined #openstack-meeting16:17
*** sacharya has joined #openstack-meeting16:18
*** Brucet has joined #openstack-meeting16:18
*** sudipto_ has quit IRC16:19
*** lakshmiS has quit IRC16:19
*** adiantum has quit IRC16:20
*** fzdarsky is now known as fzdarsky|afk16:20
*** sridhar_ram_ has joined #openstack-meeting16:21
*** yamamoto has quit IRC16:21
*** yamamoto has joined #openstack-meeting16:22
*** dslevin has joined #openstack-meeting16:22
*** dslevin has quit IRC16:22
*** iyamahat has quit IRC16:22
*** yamahata has quit IRC16:22
*** kebray has joined #openstack-meeting16:23
*** dslevin has joined #openstack-meeting16:23
*** lakshmiS has joined #openstack-meeting16:23
*** ig0r_ has quit IRC16:24
*** unicell has quit IRC16:24
*** shaohe_feng has quit IRC16:24
*** sams-gleb has quit IRC16:25
*** shaohe_feng has joined #openstack-meeting16:25
*** sams-gleb has joined #openstack-meeting16:26
*** MarkBaker has quit IRC16:26
*** jamesmcarthur has quit IRC16:29
*** yassou has quit IRC16:29
*** jamesmcarthur has joined #openstack-meeting16:29
*** bcafarel has quit IRC16:31
*** asettle has joined #openstack-meeting16:32
*** slaweq has left #openstack-meeting16:33
*** jamesmcarthur has quit IRC16:33
*** maeca1 has quit IRC16:34
*** sams-gleb has quit IRC16:34
*** jttgtest has joined #openstack-meeting16:34
*** alex_xu has quit IRC16:35
*** shaohe_feng has quit IRC16:35
*** sdake_ has joined #openstack-meeting16:35
*** shaohe_feng has joined #openstack-meeting16:35
*** jttgtest has left #openstack-meeting16:35
*** dmacpher is now known as dmacpher-afk16:36
*** IlyaG has joined #openstack-meeting16:36
*** shashank_hegde has joined #openstack-meeting16:37
*** sdake has quit IRC16:38
*** IlyaG has quit IRC16:38
*** alex_xu has joined #openstack-meeting16:38
*** jamesmcarthur has joined #openstack-meeting16:40
*** klkumar has quit IRC16:40
*** delatte has joined #openstack-meeting16:43
*** toscalix has quit IRC16:43
*** Brucet has quit IRC16:44
*** Swami has quit IRC16:45
*** mickeys has joined #openstack-meeting16:45
*** shaohe_feng has quit IRC16:45
*** delattec has quit IRC16:46
*** shaohe_feng has joined #openstack-meeting16:46
*** iyamahat has joined #openstack-meeting16:46
*** Leo_ has quit IRC16:48
*** yamahata has joined #openstack-meeting16:49
*** jamesmcarthur has quit IRC16:49
*** liamji has quit IRC16:50
*** asettle has quit IRC16:50
*** ygbo has quit IRC16:51
*** harlowja has joined #openstack-meeting16:51
*** rbartal has quit IRC16:52
*** mbound has quit IRC16:54
*** Apoorva has joined #openstack-meeting16:55
*** tonytan4ever has quit IRC16:55
*** shaohe_feng has quit IRC16:55
*** ivar-lazzaro has joined #openstack-meeting16:56
*** azbiswas has joined #openstack-meeting16:56
*** banix has quit IRC16:57
*** eric_lopez has quit IRC16:58
*** shaohe_feng has joined #openstack-meeting16:58
*** banix has joined #openstack-meeting16:58
*** roxanaghe_ has joined #openstack-meeting16:58
*** dmorita has joined #openstack-meeting16:59
*** e0ne has joined #openstack-meeting16:59
*** jamesmcarthur has joined #openstack-meeting17:01
*** SumitNaiksatam has joined #openstack-meeting17:01
*** zhurong has joined #openstack-meeting17:01
*** kaisers has quit IRC17:01
*** roxanaghe has quit IRC17:01
*** rbak has quit IRC17:02
*** KanagarajM has quit IRC17:02
*** kaisers has joined #openstack-meeting17:02
*** brucet has joined #openstack-meeting17:04
*** dmorita has quit IRC17:04
*** eric_lopez has joined #openstack-meeting17:05
*** shaohe_feng has quit IRC17:05
*** shaohe_feng has joined #openstack-meeting17:06
*** sverma has quit IRC17:08
*** brucet has quit IRC17:08
*** jamesmcarthur has quit IRC17:08
*** azbiswas_ has joined #openstack-meeting17:10
*** sambetts is now known as sambetts|afk17:11
*** roxanaghe__ has joined #openstack-meeting17:11
*** azbiswas has quit IRC17:12
*** e0ne has quit IRC17:12
*** pnavarro has quit IRC17:12
*** aranjan has joined #openstack-meeting17:14
*** fitoduarte has joined #openstack-meeting17:14
*** rbak has joined #openstack-meeting17:15
*** jamesmcarthur has joined #openstack-meeting17:15
*** roxanaghe_ has quit IRC17:15
*** rbak has quit IRC17:15
*** shaohe_feng has quit IRC17:16
*** shaohe_feng has joined #openstack-meeting17:16
*** lpetrut has quit IRC17:17
*** rbak has joined #openstack-meeting17:17
*** jlanoux has quit IRC17:17
*** azbiswas has joined #openstack-meeting17:18
*** singhj has quit IRC17:18
*** unicell has joined #openstack-meeting17:20
*** unicell has quit IRC17:20
*** unicell has joined #openstack-meeting17:20
*** cody-somerville has joined #openstack-meeting17:20
*** azbiswas_ has quit IRC17:21
*** aranjan has quit IRC17:22
*** ayoung has quit IRC17:22
*** Leo_ has joined #openstack-meeting17:22
*** aranjan has joined #openstack-meeting17:22
*** Leo_ has quit IRC17:23
*** merooney has joined #openstack-meeting17:23
*** shashank_hegde has quit IRC17:23
*** aranjan has quit IRC17:23
*** ayoung has joined #openstack-meeting17:23
*** aranjan has joined #openstack-meeting17:24
*** Leo_ has joined #openstack-meeting17:24
*** jckasper has quit IRC17:26
*** shaohe_feng has quit IRC17:26
*** jckasper has joined #openstack-meeting17:26
*** azbiswas has quit IRC17:26
*** jckasper has quit IRC17:27
*** shaohe_feng has joined #openstack-meeting17:27
*** jamesmcarthur has quit IRC17:28
*** e0ne has joined #openstack-meeting17:30
*** jckasper has joined #openstack-meeting17:31
*** sams-gleb has joined #openstack-meeting17:31
*** jamesmcarthur has joined #openstack-meeting17:32
*** cody-somerville has quit IRC17:32
*** rbak has quit IRC17:34
*** Ravikiran_K has quit IRC17:34
*** ayoung has quit IRC17:35
*** ayoung has joined #openstack-meeting17:36
*** haukebruno has quit IRC17:36
*** rbak has joined #openstack-meeting17:36
*** shaohe_feng has quit IRC17:36
*** dmorita has joined #openstack-meeting17:37
*** shaohe_feng has joined #openstack-meeting17:37
*** nadya has joined #openstack-meeting17:39
*** sams-gleb has quit IRC17:40
*** baoli_ has quit IRC17:40
*** numans has joined #openstack-meeting17:42
*** paul-carlton2 has quit IRC17:44
*** acoles is now known as acoles_17:45
*** dmowrer has quit IRC17:46
*** shaohe_feng has quit IRC17:46
*** shashank_hegde has joined #openstack-meeting17:47
*** shaohe_feng has joined #openstack-meeting17:47
*** Swami has joined #openstack-meeting17:48
*** dslevin has quit IRC17:48
*** Leo_ has quit IRC17:50
*** yamamoto has quit IRC17:52
*** yamamoto has joined #openstack-meeting17:53
*** Sukhdev has joined #openstack-meeting17:54
*** dcwangmit01 has joined #openstack-meeting17:54
*** mbound has joined #openstack-meeting17:54
*** jamesmcarthur has quit IRC17:55
*** gagehugo has joined #openstack-meeting17:55
*** shaohe_feng has quit IRC17:57
*** banix has quit IRC17:57
*** lhcheng has joined #openstack-meeting17:57
*** john-davidge_ has quit IRC17:57
*** dneary has joined #openstack-meeting17:58
notmorganajayaa, 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, xek17:58
rodrigodso/17:58
amakarovo/17:58
*** pvaneck has joined #openstack-meeting17:58
lhchengo/17:58
lbragstado/17:58
roxanaghe__\o17:58
crinkleo/17:59
*** adiantum has joined #openstack-meeting17:59
*** mbound has quit IRC17:59
*** shaohe_feng has joined #openstack-meeting18:00
*** jamielennox has joined #openstack-meeting18:00
raildo\o18:00
knikollao/18:00
*** karthikp_ has joined #openstack-meeting18:00
notmorgani.. don't think we have quorum of cores.18:00
gyee\o18:00
jamielennoxnotmorgan: you stated it?18:00
*** zhurong has quit IRC18:00
notmorganjamielennox: not yet, was waiting for folks to show up18:00
*** adisky has quit IRC18:00
bknudsonhi18:00
gagehugoyo18:00
jaugustineo/18:00
henrynashhi18:01
notmorgani think we have enough now.18:01
jamielennox#startmeeting keystone18:01
*** sajeesh has quit IRC18:01
openstackMeeting started Tue May 24 18:01:12 2016 UTC and is due to finish in 60 minutes.  The chair is jamielennox. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:01
jamielennox:)18:01
dstanekahoy18:01
jamielennox#link https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:01
hogepodgeo/18:01
*** rha has joined #openstack-meeting18:01
rderoseo/18:02
gagehugo /o/18:02
jaugustine\o\18:02
jaugustinehaha18:02
jamielennoxok, as most people are probably aware of by now, stevemar recently had a baby boy and is on leave for the next couple of weeks18:02
lbragstadwhoop whoop!18:02
lbragstadwhen does he start reviewing code?18:02
henrynashrattle rattle18:02
notmorganlbragstad: hehe18:02
henrynashwho says he isn’t18:03
jamielennoxin reality this means he'll proabably be around, but in the mean time the cores will generally be able to sort out most things for him18:03
breton_o/18:03
topolo/18:03
jamielennoxanything particular come find me or notmorgan18:03
jamielennoxand of course - congrats stevemar18:03
dstanekjamielennox: ++18:03
amakarov+118:03
topol+++18:04
gagehugo+118:04
notmorganjamielennox: lets start w/ the etherpad thing18:04
*** banix has joined #openstack-meeting18:04
notmorganjamielennox: then we can continue w/ spec freeze etc.18:04
*** pabelanger has joined #openstack-meeting18:04
jamielennox#topic Meeting Agenda Moving to Etherpad?18:04
*** openstack changes topic to "Meeting Agenda Moving to Etherpad? (Meeting topic: keystone)"18:04
jamielennoxnotmorgan: ok then18:04
notmorganTalked with steve and a few others18:04
*** merooney has quit IRC18:04
notmorganpeople cannot edit the wiki because no new accounts are allowed18:05
notmorganas a trial i created an etherpad18:05
notmorgan#link https://etherpad.openstack.org/p/keystone-weekly-meeting18:05
raildonotmorgan: ++ for etherpad18:05
notmorganinstead of the wiki we can use the etherpad for meetings. any issues/concerns/love the ideas?18:05
gyeeall love here18:05
dstanekworks for me18:05
lbragstadi'm indifferent - either works for me18:05
rodrigodsjust put the etherpad URL in the wiki18:05
notmorganrodrigods: that is the plan.18:06
topolworks18:06
bknudsonmakes sense since editing the wiki is a pain18:06
lbragstadyes18:06
knikolla++ for etherpad, with link in wiki18:06
breton_i wonder how good it will work in a year18:06
henrynashworks for me (already edited it!)18:06
*** karthikp_ has quit IRC18:06
jamielennoxyea, i'm not too worried either way - works if we can't et people accessing the wiki18:06
notmorganok lets start going from the etherpad then18:06
notmorgani've added the spec freeze bit to it18:06
notmorganand i'l update the wiki to reference more prominently after this meeting18:06
jamielennox#action notmorgan fix the wiki keystonemeeting links to point to the new meeting etherpad18:07
*** shaohe_feng has quit IRC18:07
jamielennoxhmm, no meetbot confirmations - hope i didn't screw this up18:07
notmorganyou don't get them on #link or action18:07
*** karthikp_ has joined #openstack-meeting18:07
jamielennoxah18:08
*** shaohe_feng has joined #openstack-meeting18:08
jamielennox#topic Spec proposal freeze is next week, couple of weeks longer for spec freeze.18:08
*** openstack changes topic to "Spec proposal freeze is next week, couple of weeks longer for spec freeze. (Meeting topic: keystone)"18:08
*** mbound has joined #openstack-meeting18:08
jamielennoxnext week is spec proposal freeze18:08
*** sarob has joined #openstack-meeting18:08
jamielennoxfor anyone unfamiliar this means that any specs you want to land in newton have to be at least proposed by then18:08
jamielennoxwe then have a few weeks before specs have to be actually approved to land in newton18:09
*** karthik__ has joined #openstack-meeting18:09
jamielennoxso if you're thinking of still proposing something get a wriggle on18:09
breton_is next week 30-5?18:09
*** cody-somerville has joined #openstack-meeting18:09
*** _sarob has joined #openstack-meeting18:09
notmorganbreton_: yes18:09
*** karthikp_ has quit IRC18:09
*** merooney has joined #openstack-meeting18:09
* topol wriggle? I need an Australian dictionary18:09
henrynash“get a wriggle on”18:09
jamielennoxnotmorgan: i assume it's the end of the week?18:09
notmorganjamielennox: yes by end of the week is usually what we aim for18:10
breton_so, will it be unfrozen in 30-5? or frozen on the 30th?18:10
notmorganbreton_: after the week18:10
notmorganso after friday18:10
notmorganerm.. wait no.18:10
lbragstadit will be frozen after the 5th, right?18:10
notmorganthe spec proposal freeze happens after friday18:10
notmorganth... 4th?18:10
notmorgan3rd.18:10
breton_3rd18:11
*** sdake_ is now known as sdake18:11
jamielennoxafter may 3rd is my understanding18:11
notmorganyes18:11
notmorganso a week from this coming friday is your deadline18:11
*** dmowrer has joined #openstack-meeting18:11
*** yohoffman has joined #openstack-meeting18:11
jamielennox#topic Keystone Core Sec Updates18:12
*** openstack changes topic to "Keystone Core Sec Updates (Meeting topic: keystone)"18:12
*** numans has quit IRC18:12
* notmorgan has a lot of topics.18:12
dstanekif you're going to be cutting it that close you may want to get moving on it18:12
notmorgan#link https://launchpad.net/~keystone-coresec18:12
notmorganthe keystone core sec team is too large18:12
*** yamamoto_ has joined #openstack-meeting18:12
*** aranjan has quit IRC18:12
*** david-lyle_ has joined #openstack-meeting18:12
notmorganand has a lot of folks not actively participating18:12
notmorgani am going to trim this down.18:12
breton_what is coresec?18:12
breton_oh, ok.18:13
*** ivar-laz_ has joined #openstack-meeting18:13
notmorganbreton_: folks who evaluate embargoed bugs18:13
*** aranjan has joined #openstack-meeting18:13
notmorgansecurity vulnerabilities18:13
lbragstadI don't think i'm on that list18:13
*** Apoorva_ has joined #openstack-meeting18:13
dstaneknotmorgan: i'm on there, but only occasionally comment - so you can trim me if you need to18:13
notmorganso, anyone can be on this (does not need to be a core reviewer)18:13
gyeenotmorgan, I would like to stay on it18:13
notmorganbut if you're not interested and are on the list please speak up.18:13
rodrigodshmm interesting18:13
notmorganor if you aren't on the list and are interested...18:13
dstaneki feel bad taking up someone's spot if i can't contribute back enough18:13
notmorganspeak up18:13
*** sarob has quit IRC18:14
notmorgani'll conferr with people after the meeting18:14
*** ajmiller__ has joined #openstack-meeting18:14
notmorganso think about it18:14
*** wznoinsk_ has joined #openstack-meeting18:14
dstanekit would be nice to somehow still be able to see what's happening though :-(18:14
lbragstadis there a limit to how many people we can have?18:14
notmorganideally we should be ~5 people18:14
notmorganany one can be looped in to view a security bug18:14
lbragstadnotmorgan because it's security related?18:14
*** karthik__ has quit IRC18:14
rderosenotmorgan: I'd be interested18:14
notmorganthis is just the front line group who evaluates IF a bug is really a bvlunerability18:14
*** shashank_hegde_ has joined #openstack-meeting18:15
*** moizarif has joined #openstack-meeting18:15
notmorganthink about it, i'll work out who will be on the team after the meeting :)18:15
*** shashank_hegde has quit IRC18:15
*** aysyd has quit IRC18:15
*** cwolferh has quit IRC18:15
*** shashank_hegde_ is now known as shashank_hegde18:15
*** cebruns has quit IRC18:15
*** jrist has quit IRC18:15
notmorgani can guarantee that stevemar will be staying on that list [as ptl]18:15
*** cwolferh has joined #openstack-meeting18:15
*** noslzzp_ has joined #openstack-meeting18:15
notmorganok thats all on that topic.18:15
*** jrist has joined #openstack-meeting18:15
*** fzdarsky|afk is now known as fzdarsky|lunch18:16
*** fzdarsky|lunch is now known as fzdarsky18:16
*** ivar-laz_ has quit IRC18:16
jamielennox#topic Reviews!18:16
*** cebruns has joined #openstack-meeting18:16
*** openstack changes topic to "Reviews! (Meeting topic: keystone)"18:16
notmorganok18:16
notmorganso.18:16
*** ivar-laz_ has joined #openstack-meeting18:16
breton_lets do them?18:16
notmorganin newton we have been lacking reviews and have a lot of open patches18:16
*** yamamoto has quit IRC18:16
*** ivar-lazzaro has quit IRC18:16
*** Apoorva has quit IRC18:16
*** ajmiller_ has quit IRC18:16
*** moiz has quit IRC18:16
*** noslzzp has quit IRC18:16
*** david-lyle has quit IRC18:16
*** wznoinsk has quit IRC18:16
*** Douhet has quit IRC18:16
notmorgansome can be abandoned, some need rebasing18:16
bknudsonhttp://russellbryant.net/openstack-stats/keystone-reviewers-90.txt18:16
henrynashok, guilty as charged. C- for Henry18:16
*** electrofelix has quit IRC18:16
notmorganbut in short... we have been lacking reviews18:16
notmorganhttp://stackalytics.com/?module=keystone-group18:16
notmorgan#link http://stackalytics.com/?module=keystone-group18:16
notmorganthat is specific to newton code18:17
notmorganruss' only covers avg reviews.18:17
*** Douhet has joined #openstack-meeting18:17
*** ijw has joined #openstack-meeting18:17
notmorganthis is a call to action for everyone18:17
notmorganplease review.18:17
*** aranjan has quit IRC18:17
notmorgancores, non-cores, new folks, etc18:17
bknudsonI haven't been able to review so much lately due to changes in the job... hoping to get back to it sometime.18:17
henrynashwill do18:17
*** shaohe_feng has quit IRC18:17
*** ijw has quit IRC18:17
notmorganquestion things in the patch if you don't understand (-1s for things that look wrong, but no score with questions help too)18:17
notmorganin short. review.18:17
*** ijw has joined #openstack-meeting18:17
gyeegetting back on the review horse18:18
*** shaohe_feng has joined #openstack-meeting18:18
knikollai’ll start reviewing more, whatever my +1 is worth.18:18
bknudsonmy reviews seem to mostly be ignored lately anyways18:18
* rodrigods have some patches that would love reviews18:18
notmorganwe are actively keeping an eye on folks who are reviewing, get the code base, etc for new cores fwiw18:18
breton_that's because i am on vacation18:18
breton_that's why there are no reviews.18:18
stevemarknikolla: it's worth more than you think -- a good review is a good review, regardless who does it18:18
dstaneki'm guilty of being low in review count - been tied up with capstone, but that's changing in a day or two18:18
notmorganbut everyting does need reviews, a +1 means a lot, a -1 with questions/concerns means a lot18:18
breton_i'll be back and we'll be good again, relax.18:18
notmorgana +0 with questions means a lot18:18
notmorganEVEN if a core already +2'd18:19
raildoI'll review more on this release :)18:19
lbragstadnotmorgan ++18:19
jamielennox /kick stevemar18:19
dstanekknikolla: ideally you find stuff and it gets fixed before a core comes around and -1's it18:19
notmorganplease review. we lean on everyones to make the code base good.18:19
*** vishnoianil has quit IRC18:19
notmorganand every review matters.18:19
bknudsonthe comments along with the review are worth more than the vote. Try out the change and say what you did18:19
knikollaunderstood, i’ve been mostly commenting with +018:19
bknudsoncheck the coverage report and say if everything is covered18:19
notmorganif you have a concern you don't want to say publically, you can talk to a core.. or me directly18:19
*** jamesmcarthur has joined #openstack-meeting18:20
jamielennoxthe problem with a lot of +0 is they go unnoticed18:20
notmorgani'll happily help guide if you're unsure about how to review.18:20
notmorganjamielennox: we need to fix that.18:20
topolI will put more focus on reviewing as well18:20
topolmessage heard!18:20
jamielennoxi often miss +0 for ages because it doesn't show up as a change in the review list18:20
gyeeNo Review Left Behind Act18:20
notmorgancores - please do not ignore +0s. submitters, be sure to look for the +018:20
jamielennoxjust as an aside18:20
amakarovjamielennox, ++18:20
notmorganwith questions.18:20
jamielennoxnotmorgan: ok?18:21
notmorganand if a +0 is being ignored, raise it up to someone :) don't hesitate to point it out if it seems like it is relevant or change the vote to -1 after conferring with a core18:21
*** salv-orlando has quit IRC18:21
notmorganjamielennox: yep :)18:21
bknudsonsubmitters should realize that pretty much nothing is going to get merged this release due to lack of reviews.18:21
rodrigodsi usually +1 when i have doubts18:21
notmorgan(or just change it to -1 if you feel it is important enough)18:21
notmorganor a +118:21
rodrigodsjust for the person be able to see18:21
dstanekbknudson: yes. so they should be reviewing too!18:21
notmorganbknudson: exactlyu18:22
* notmorgan has one more short topic.18:22
jamielennox#topic Good News Everbody!18:22
*** openstack changes topic to "Good News Everbody! (Meeting topic: keystone)"18:22
notmorganso. i've proxied for steve (and talked with him)18:22
notmorganand conferred with the cores.18:22
notmorganPlease welcome rodrigods as the newest member of the core team.18:22
henrynashwoot woot!18:23
bknudsoncongrats to rodrigods18:23
lbragstadrodrigods congrats!18:23
rodrigodso/18:23
raildoYAY congrats rodrigods!18:23
gyeerodrigods, congrats!18:23
amakarovrodrigods, congratulations!18:23
raildo:D18:23
*** nadya has quit IRC18:23
knikollarodrigods: congrats!18:23
*** ig0r_ has joined #openstack-meeting18:23
notmorgani will send an email out after the meeting and get you added to the gerrit group.18:23
jamielennoxwell done rodrigods18:23
rodrigodswill i be able to +A all my code?18:23
rodrigods:)18:23
notmorganrodrigods: lol.18:23
rodrigodsthank you all18:23
bknudsonthanks for all your work on keystone.18:23
henrynashrodigods: instant demotion18:23
raildolol18:23
rderoserodrigods: congrats!!!18:23
jamielennoxshortest core stint award goes to18:23
*** Leom has joined #openstack-meeting18:23
notmorgani want to reiterate that rodrigods has shown understanding of the code base and quality reviews and code.18:23
gagehugograts!18:23
gyees/demo/demoli/18:23
*** rossella_s has quit IRC18:24
notmorganwe are continuing to look for other reviewers/contributors to include in the core group.18:24
rodrigodsthanks! and also for the mentoring since i've joined the openstack community18:24
*** jamesmcarthur has quit IRC18:24
*** shaleh has joined #openstack-meeting18:24
notmorgan#action notmorgan to send email and add rodrigods to core group after meeting18:24
*** rossella_s has joined #openstack-meeting18:24
dstanekrodrigods: congrats18:24
jamielennoxrodrigods: thanks for sticking in there and everything you've done18:24
topolCONGRATULATIONS rodrigods! Very well deserved!18:25
*** earlephilhower has joined #openstack-meeting18:25
rodrigodsreally glad to be part of the core team, will try to work harder18:25
dolphmrodrigods: /salute18:26
notmorganrodrigods: you now have +2/+A rights on the keystone repositories.18:26
rodrigodsawesome :)18:26
jamielennox#topic Creating new versions of keystone component drivers (e.g. V8, V9 etc.)18:26
*** openstack changes topic to "Creating new versions of keystone component drivers (e.g. V8, V9 etc.) (Meeting topic: keystone)"18:26
henrynashok18:26
*** kmartin has joined #openstack-meeting18:26
jamielennoxgo go henrynash!18:26
*** neiljerram has quit IRC18:27
bknudsonthe suspense...18:27
henrynashso todate, every time we create a new version of a driver, we archive off an example driver (e.g. SQL) so that we can test we haev not broken teh old interface18:27
*** shaohe_feng has quit IRC18:27
henrynashsome have suggest this is a poor way of doing it....18:27
henrynash…but so far I don’t have any otehr ideas18:28
bknudsonI guess the old driver is in git already18:28
bknudsonso maybe check out an old keystone?18:28
*** shaohe_feng has joined #openstack-meeting18:28
gyeemicroversioned keystone drivers :-)18:29
henrynashbknudson: so we usual want to substitute an individual driver18:29
bknudsony, check out only that driver.18:29
bknudsoncheck out keystone to a new directory and pull out the driver.18:29
knikollacheck out only that specific driver from git18:29
*** rcernin has quit IRC18:29
henrynashwe used to so this for client testing, I think…but we moved away form it18:29
bknudsonor maybe you can just check out a file.18:29
bknudsonthat was in a different repo18:30
jamielennoxdo we expect people to subclass the driver class directly or duck type it?18:30
*** ivar-laz_ has quit IRC18:30
bknudsonyou could do git checkout stable/master -- keystone/identity/backend/sql.py18:30
henrynashno18:30
henrynash(to jamie)18:30
bknudsonthey have to subclass since it's abc.18:30
bknudsonthis is why abc is a bad idea in python18:30
dstanekthe issue is that we don't want to carry an extra copy of the backend?18:30
henrynashwe only support the interface, we don’t promise they can subclass our driver and we’ll maintin the code otehyc an continue to subclass18:30
amakarovhenrynash, is there a problem description somewhere?18:31
henrynashjust ayiojng objecting in: https://review.openstack.org/#/c/305315/18:31
bknudsonI don't mind keeping a copy in the tests, so not sure what the complaints are.18:31
dstanekbknudson: ++18:31
dstaneki dont18:31
henrynashthis is teh current example: we just need to copy the driver so we can test18:31
*** karthikp_ has joined #openstack-meeting18:32
henrynashayoung: you about?18:32
shalehso where is ayoung to provide an alternative since he complained?18:32
bknudsonit's not 400 lines that we have to maintain18:32
dstanek like having to rely on checking out individual files18:32
amakarovhenrynash, can we make subsequent interfaces inherited?18:32
henrynashok, so I’ll follow up with ayoung and ask him to calrify his concern and propose an alternative if he feels striongly about it18:32
amakarovthis will save a lot of copying18:33
bknudsonthe copy is so that we can test with an old implementation18:33
bknudsonthe interface is already inherited18:33
henrynashbknudson: ++18:33
jamielennoxi think we need to maintain those tests, and we need to maintain the symbols so that anyone who subclassed it doesn't get broken immediately18:33
dstanekamakarov: it's the copying of the backend18:34
amakarovbknudson, I'm about "class IdentityDriverV9(IdentityDriverV8)"18:34
*** ivar-lazzaro has joined #openstack-meeting18:34
*** singhj has joined #openstack-meeting18:35
bknudsonno, we decided to do an adapter18:35
amakarovbknudson, well, then we need all the code18:35
*** karthikp_ has quit IRC18:35
henrynashamakarov: we wanted to make sure the new driver & interface was as clean as possible…pushing the ugliness into the adaptor18:35
*** mbound has quit IRC18:35
henrynashjamielennox: ok, think we ar done on this one18:36
jamielennox#topic Microversioning of the Identity API18:36
*** openstack changes topic to "Microversioning of the Identity API (Meeting topic: keystone)"18:36
*** karthikp_ has joined #openstack-meeting18:36
henrynashdamn. me again18:36
*** sams-gleb has joined #openstack-meeting18:37
henrynashok, so we have at least one hcnage that requires break api18:37
henrynash(hierarchial naming)...18:37
henrynash…and the push back from several was that we should really do microversioning now for teh Idenityt API18:37
henrynashso this is now proposed: https://review.openstack.org/#/c/315180/18:37
*** shaohe_feng has quit IRC18:38
henrynashthis is basically teh same approach nova uses, adapted for keystone18:38
notmorgan this is an API breaking change - the options are:18:38
notmorgan1) Microversions (like nova)18:38
notmorgan2) Don't break the API and not change this18:38
notmorgan3) API V418:38
notmorganin order of my preference [assuming this is something we want]18:39
*** shaohe_feng has joined #openstack-meeting18:39
henrynashI re-wrote the origional spec published by ayoung to docuemtn all teh use cases etc and make this a compelte sepc (rather than just refer to the nova spec)18:39
raildoAPI v4, please no :(18:39
jamielennoxso regards the hierarchical naming (main cause for this) - is that something we can solve with an api version change? it seems like a modelling problem18:39
bknudsonconsidering how hard it is to get other projects to even use current features I'd vote for don't break the api.18:39
gyeev4 is least disruptive18:39
notmorganhenrynash: why do we need this relaxed naming?18:39
ayoungI'm here18:40
*** ivar-lazzaro has quit IRC18:40
notmorganis there a real use case we're missing that uniqueness per domain is unacceptable?18:40
notmorgansince domains are not hierarchical18:40
bknudsoncan we put the new stuff on a different path (make it a different resource)?18:40
* samueldmq reads up18:40
amakarovjamielennox, policy enforcement for ex.18:40
*** karthikp_ has quit IRC18:40
amakarovjamielennox, we can do it in keystone for RBAC318:40
notmorganbknudson: the issue is projects would leak through into the old api...or you'd need a new api to see the project?18:40
henrynashnotmorgan: so I think there are two things here: we can argue whether we can get away with naming uniquenss or not…..but I think it is better we agree to our approach of hwo we modify the API when we need to….and I’m sure we will need to18:41
*** karthikp_ has joined #openstack-meeting18:41
dstanekbknudson: that's what i would vote for. new/different API resources18:41
jamielennoxbknudson: also it's really an /auth request18:41
ayoungI don't see why relaxing a rule is breaking the contract, but I'm not going to fight this fight.  If microversions buy us things elsewhere, and this is a good place to introduce them,lets do it18:41
raildonotmorgan: project name is unique in a domain, we can't have a parent and a subproject with the same name18:41
bknudsonhow can we prevent leaking to the old api in any case?18:41
notmorganraildo: i don't see that as a problem18:41
*** dmowrer has quit IRC18:41
jamielennoxit's not just a parent problem18:42
raildonotmorgan: we can have something like, coke->dev and pepsi->dev18:42
notmorganraildo: so make coke_domain and pepsi_domain18:42
jamielennoxan accounting project and a engineering project both want to create ProjectX18:42
jamielennoxthat name is only unique via the path18:42
henrynashso on the specific naming issue, I think it is untennable that as hiearchies grow, that all leaves/nodes have to be unique18:42
notmorganjamielennox: and i'm going to argue that accounting should be a domain and engineering should be.18:42
raildonotmorgan: yes, but this doesn't work for reseller, since we can create subprojects acting as domains18:42
raildocant*18:43
*** dmowrer has joined #openstack-meeting18:43
notmorganraildo: again, i'm back to domains.18:43
dstanekhenrynash: so what part of the API is being broken? just getting error codes (4xx) where we used to get success (2xx)?18:43
notmorganeverything still works with a new domain.18:43
notmorganinc. "reseller" concepts.18:44
henrynashnotmorgan, jamielennox: I guess I am more interested in whether we think we must be able to break teh API in teh future, and if so, how shoudl we do it....18:44
notmorganadd a domain to the account.18:44
notmorganhenrynash: microversions or V418:44
*** sverma has joined #openstack-meeting18:44
*** merooney has quit IRC18:44
notmorganhenrynash: and i'm fine with either18:44
*** sams-gleb has quit IRC18:44
gyeeauth is part of defcore, so we have to be mindful about interop18:44
jamielennoxhenrynash: given that other projects are adopting microversions, i'd say we would do that - but i would like to be left with absolutely no other choice18:44
ayounglets not V418:44
notmorganthough microversions seems to be the pattern for openstack18:44
ayoungmicro changes are microversions.  A big version jump is just going to be ignored18:45
jamielennoxyea, particularly around the auth apis18:45
henrynashdtsanek: teh specific problem is that before thsi proposed change, teh proejct scope of “test” would work, but mioght now aftewards, since “test” is not unqiue and /“dev/test” would be requied18:45
notmorganif we did a big api version jump, we'd need to extract auth to /auth18:45
notmorgannot /<version>/auth18:45
*** ntata| has quit IRC18:45
jamielennoxnotmorgan: ++ to that anyway18:45
ayoungI'm not sure we are not just making busywork for ourselves, but if this is the cautious approach, it probably is the better way to go18:45
notmorganthat whole tie auth to the CRUD api is what caused us so much headache in api verion adoption18:45
notmorgananyway18:46
notmorganayoung: it is the conservative approach18:46
notmorganand keystone frankly needs to err to the conservative side18:46
knikollanotmorgan: ++18:46
henrynashnotmorgan: I have to agree with you18:46
*** ivar-lazzaro has joined #openstack-meeting18:46
*** iceyao has quit IRC18:46
jamielennoxi'm also wondering if we have a real world request for this yet or are looking at upcoming pain points?18:47
*** karthikp_ has quit IRC18:47
jamielennoxgiven the adoption of hierarchies so far..18:47
henrynashjamielennox: so mine is the only one I knwo of so far….although if we do the work and never incremenent teh microversion number, nothing breaks anywya18:47
*** hasharAway is now known as hashar18:47
bknudsonnova used microversions for all sorts of fixes18:48
*** links has quit IRC18:48
*** lpetrut has joined #openstack-meeting18:48
ayoungjamielennox, we have requests18:48
notmorgani'll argue that almost everything that is desired with reseller could be done with domains.18:48
bknudsonuseful ones like better validation of user input18:48
*** shaohe_feng has quit IRC18:48
notmorganon the topic of hierarchies.18:48
henrynashbknudson: agreed, and I plan to copy their approach18:48
notmorganbknudson: ++18:48
ayoungHMT is limited by other projects, but we want to keep it that way, and stay ahead of the demand18:48
dstaneknotmorgan: ++18:48
*** shaohe_feng has joined #openstack-meeting18:49
ayoungwe had a customer ask about it.  Horizon support needs to come up18:49
knikollaalso with microchanges we might be able to have better adoption of our newer apis18:49
*** sverma has quit IRC18:49
*** aranjan has joined #openstack-meeting18:49
jamielennox2-3 more minutes so we can leave time for the last topic18:49
bknudsonwe've seen that better adoption only comes when we spend our time in the other projects18:49
*** ivar-lazzaro has quit IRC18:49
henrynashok, so review the spec….and we’ll go from there18:50
jamielennoxbknudson: ++ no one else does auth work18:50
jamielennoxhenrynash: my view would be microversions is the answer, but only when we're really sure what we want to solve with it18:50
*** dimtruck is now known as zz_dimtruck18:50
jamielennoxso i'd prefer to discuss the hierarchical naming problem18:50
rodrigodsit can be useful for other stuff18:50
rodrigodsnot only HMT18:50
rodrigodsHMT was the trigger, but...18:50
knikollajamielennox: the use cases will come once it’s there18:51
*** asettle has joined #openstack-meeting18:51
dstaneki think that in a way microversions are an API/architecture smell18:51
dstanekmaybe a necessary one?18:51
*** asettle has quit IRC18:51
*** asettle has joined #openstack-meeting18:51
jamielennoxrodrigods: it can, but we've kept our api stable for a while now18:51
jamielennoxdstanek: ++18:51
ayoungdstanek, part of the issue is that Keystone is not really a micros service18:51
bknudsonif we could design things perfectly from the beginning we wouldn't need it, but we're not perfect.18:51
ayoungits more of just a service, not a macro one.  THat would be nova18:51
rodrigodsbknudson, ++18:51
dstanekeven in nova i'd argue that it's not great architecture18:52
ayoungnova is a macros service18:52
ayoungits like 15 things18:52
ayoungKeysteon is about 518:52
jamielennoxok, review spec18:52
bknudsonI'm surprised every time someone says openstack servers are microservices.18:52
henrynashjamielennox: so the spec that is up: (there are two alternatives): https://review.openstack.org/#/c/310048/ and https://review.openstack.org/#/c/315180/18:52
dstanekbknudson: or it we understood hypertext18:52
ayoungauth, id &  federation, assignment, resource, policy,18:52
jamielennox#topic Multiple datacenters18:52
*** openstack changes topic to "Multiple datacenters (Meeting topic: keystone)"18:52
ayoungeach could and should be separate if we were serious about microservies18:52
*** matrohon has joined #openstack-meeting18:52
ayoungAh18:53
jamielennoxamakarov: was hoping to give you a bit more time there, sorry18:53
ayoungjamielennox, beyond Fernet?18:53
*** e0ne has quit IRC18:53
agrebennikovare you guys going to wrap up and skip this topic?18:53
dstanekayoung: microservices is really abot team size. so if the same team manages all the microservices then splitting won't matter18:53
ayoungwe should get a best practice written up about Fernet key rotation18:53
jamielennoxamakarov: or i can leave it for next week and put you in first instead?18:53
amakarovjamielennox, I think 5 min is anough for now18:54
amakarovagrebennikov is here18:54
amakarovAnd the case is described in etherpad18:54
agrebennikovso I tried to explain in details what I need18:54
agrebennikovand this is actually a very common request from the customer18:54
shalehlink to pad?18:55
amakarovI believe last time we agreed that admin CAN specify project IDs, right?18:55
jamielennoxso to my mind if you are replicating role ids, project ids and user ids in all regions then you are pretty much replicating the database anyway18:55
amakarovhttps://etherpad.openstack.org/p/keystone-weekly-meeting18:55
*** toddjohn has quit IRC18:55
agrebennikovjamielennox, no, this is not quite correct18:55
agrebennikovdb replication means if you broke it in one place - it gets broken in all others18:56
agrebennikovand we actually had this issue in production cloud18:56
shalehwhy is DB replication an issue since there will be few writes?18:56
*** cody-somerville has quit IRC18:56
agrebennikovthat is why the customer decided to get rid of this18:56
*** prometheanfire has joined #openstack-meeting18:56
shalehwithout writing UUID there is little to break in Keystone DB now18:57
agrebennikovshaleh, because nobody wants to deal with additional instance of db specifically for keystone18:57
jamielennoxhave you tried the read-only database conenctions for this? because if that doesn't work for this case i'm in big trouble :)18:57
dstanekagrebennikov: so the alternative is to manually do replication?18:57
agrebennikovwhich has to have different peers than all other dbs18:57
*** markvoelker_ has joined #openstack-meeting18:57
gyeeagrebennikov, I hear ya, LDAP is already replicated18:58
agrebennikovldap only provides users18:58
shalehdstanek: a push model on the occasional new user / role / project change would not be too bad. But this is still an additional DB instance18:58
lbragstadayoung we have something similar to what you're suggesting in the fenret FAQ18:58
gyeeand groups18:58
shalehso I do not see the request18:58
*** shaohe_feng has quit IRC18:58
*** redbo has joined #openstack-meeting18:58
ayoungagrebennikov, is this essentially "we need to be able to say what the projet Id is" but also for roles and assignments?18:59
ayounglbragstad, cool.  Link?18:59
lbragstadayoung that document seems like the right place for a fernet best practices18:59
*** markvoelker has quit IRC18:59
lbragstadayoung yeah18:59
dstanekshaleh: i would not want keystone to be responsible for that. dbs are built to do this18:59
shalehif every region has their own DB, however you want to sync it is your issue. Otherwise, read only calls back to "home" should work.18:59
jamielennoxyea, i feel this will grown form project_ids to needing to specify all ids18:59
jamielennoxalso we've one minute18:59
shalehdstanek: I am not saying Keytone would drive it18:59
*** merooney has joined #openstack-meeting18:59
lbragstadayoung http://docs.openstack.org/admin-guide/keystone_fernet_token_faq.html18:59
dstanekshaleh: any code even :-)18:59
jamielennoxagrebennikov, amakarov: sorry i should have pushed it till next week and given you more time18:59
jamielennoxplease continue the discussion in #openstack-keystone for now19:00
agrebennikovayoung, yes please. roles and projects19:00
shalehamakarov: write more, show the problems.19:00
amakarovagrebennikov, till next week then ^^19:00
*** markvoelker has joined #openstack-meeting19:00
jamielennox#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue May 24 19:00:33 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-05-24-18.01.html19:00
*** shaleh has left #openstack-meeting19:00
amakarovjamielennox, I'll email os-dev19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-05-24-18.01.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-05-24-18.01.log.html19:00
agrebennikovshaleh, do you need 5 pages? ;)19:00
ayoungagrebennikov, I think it is a reasonable request.  We've had enough people ask for it19:00
fungiinfra team, assemble!19:00
SotKo/19:00
nibalizero/19:00
ayoungit should not be the norm19:00
pleia2/go/19:00
fungitoday's topics are brought to you by waynr, notmorgan, puiterwijk, and the letter 319:00
prometheanfireyo19:00
pleia2hah19:00
pleia2o/19:01
notmorgano/19:01
crinkleo/19:01
*** shaohe_feng has joined #openstack-meeting19:01
puiterwijkHi. Thanks, fungi, for the ping19:01
*** martines has quit IRC19:01
prometheanfirethough I'm not on the team :P19:01
*** rockyg has joined #openstack-meeting19:01
pabelangero/19:01
fungiprometheanfire: everyone's on the team19:01
ianwo/19:01
fungiwe're a very inclusive bunch19:01
bkeroo/19:01
*** tonytan4ever has joined #openstack-meeting19:01
prometheanfirefungi: damn, was hoping it was notmyproblem19:02
fungiwe19:02
fungi're everyone's problem19:02
fungijeblair: clarkb: around?19:02
*** markvoelker_ has quit IRC19:02
*** merooney has quit IRC19:02
prometheanfireianw: want to talk about the dib changes here?19:02
fungiyolanda's not in channel at the moment19:02
prometheanfirethat's what I'm here for19:02
*** rha has left #openstack-meeting19:02
fungiand mordred's on vacation still this week i think19:03
fungijhesketh may still be asleep19:03
*** rbowen has quit IRC19:03
fungiwell, let's get going19:03
fungi#startmeeting infra19:03
openstackMeeting started Tue May 24 19:03:29 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
anteayaI like the letter 319:03
openstackThe meeting name has been set to 'infra'19:03
zaroo/19:03
*** rbowen has joined #openstack-meeting19:03
anteayaeven better than the number 319:03
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:03
*** glange has joined #openstack-meeting19:03
fungi#topic Announcements19:03
*** cody-somerville has joined #openstack-meeting19:03
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:03
fungi#info REMINDER: Gerrit downtime on Friday 2016-06-03 at 20:00 UTC19:03
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2016-May/004322.html19:04
*** merooney has joined #openstack-meeting19:04
jeblairfungi: o/19:04
pleia2we still need a change for the openstack-infra/ansible-puppet -> openstack-infra/ansible-role-puppet rename19:04
fungialso worth noting, we're in an ad hoc sprint upgrading a bunch of our servers from ubuntu 12.04 to 14.04 this week19:04
pleia2not sure who is responsible for that19:04
fungi#link https://wiki.openstack.org/wiki/VirtualSprints#Infra_Trusty_Upgrade19:04
*** cody-somerville has quit IRC19:04
*** cody-somerville has joined #openstack-meeting19:05
fungipleia2: mordred added that one to the list, but he may have hoped one of us would fill in the blanks19:05
* pleia2 nods19:05
fungiwe can punt on it if there's no change come maintenance time19:05
*** karthikp_ has joined #openstack-meeting19:05
fungi#topic Actions from last meeting19:05
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:05
jeblairfungi: yes!19:05
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-05-17-19.01.html19:05
fungijeblair investigate mail filtering by recipient options for infra-root@o.o inbox19:05
fungiwhat's the option?19:05
jeblairturns out the web thingy has decent mail filtering19:06
fungioh, as we hoped but dared not expect19:06
jeblairso we can filter by recipient address19:06
* anteaya loves when jeblair uses the technical terms19:06
pleia2that's helpful19:06
fungithat makes imap a bit easier19:06
jeblairand filter messages into folders19:06
*** banix has quit IRC19:06
*** jamesmcarthur has joined #openstack-meeting19:07
jeblairso we can continue to use a single storage account, which will make the foundation happy that they don't have to pay for more than one19:07
fungiso we should probably plan to filter recipients for cloud provider accounts into a specific inbox we can all subscribe to19:07
pleia2wfm19:07
jeblairand we can just check various folders19:07
fungisounds great19:07
jeblairwe can continue to add aliases if we want, or of course, start filtering by from address or other things19:07
fungiany volunteers for implementing the filtering?19:08
fungiand letting us know which inbox(es) is/are high priority?19:08
pleia2if it can wait until next week, it's probably a good sister's couch task for me to take while I'm east coasting19:08
jeblairthe filtering is easily created/modified through the usual webmail interface (so no admin perms needed)  (adding aliases requires an admin, of which there are few)19:08
*** shaohe_feng has quit IRC19:08
fungipleia2: i think there's not a huge rush on it19:08
*** yohoffman has left #openstack-meeting19:09
jeblair++19:09
*** karthik__ has joined #openstack-meeting19:09
*** vishnoianil has joined #openstack-meeting19:09
pleia2ok, I'll start taking care of it next wednesday19:09
fungi#action pleia2 set up filtering to direct provider account contact address(es) into a high priority inbox19:09
fungithanks jeblair, pleia2!19:09
fungi#topic Specs approval19:09
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:09
*** karthikp_ has quit IRC19:10
funginone new this week19:10
fungittx had another update to the task tracker spec19:10
anteayasome good reading there19:10
fungi#link https://review.openstack.org/31418519:11
*** karthikp_ has joined #openstack-meeting19:11
fungialso docaedo added one for running a less-technical-user-friendly irc front-end19:11
*** shaohe_feng has joined #openstack-meeting19:11
fungi#link https://review.openstack.org/31950619:11
docaedoI did!19:11
bkerodocaedo++19:11
pleia2cool19:11
*** karthik__ has quit IRC19:11
fungiand nibalizer wrote the one about server boot automation he promised at the summit19:12
fungi#link https://review.openstack.org/31094819:12
anteayayay promises kept19:12
*** karthikp_ has quit IRC19:13
fungi#topic Priority Efforts19:13
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:13
fungino updates this week, but i plan to start a thread on the ml to discuss updates to the current priority efforts list19:13
fungi#action fungi start an ml thread revisiting current priority efforts list19:13
fungi#topic Jenkins Job Builder v2 API (waynr)19:13
*** openstack changes topic to "Jenkins Job Builder v2 API (waynr) (Meeting topic: infra)"19:13
fungi#link https://specs.openstack.org/openstack-infra/infra-specs/specs/jenkins-job-builder_2.0.0-api-changes.html19:13
*** martines has joined #openstack-meeting19:14
fungioh, he's not in channel19:14
*** moizarif has quit IRC19:14
*** moiz has joined #openstack-meeting19:14
*** zz_dimtruck is now known as dimtruck19:15
fungii'll parrot him from the agenda until he shows up...19:15
*** waynr has joined #openstack-meeting19:15
fungi<waynr> Jenkins Job Builder v2 API has been rebased on to JJB master branch and is ready for review19:15
*** sheel has quit IRC19:15
waynrthanks pleia2 fungi for the reminder19:15
fungioh, hey! you can take over introducing your topic now ;)19:15
waynrand apologies for the tardiness...i am so scatterbrained today :)19:15
waynrokay, so basically I understand that JJB and the v2 API efforts in particular are not a high priority for openstack-infra19:16
*** rderose_ has joined #openstack-meeting19:16
*** phil_h has quit IRC19:16
fungifacilitating your work is still a high priority for me, so let me know what sorts of things you need (branch deletions, tags pushed) and i'm happy to do it19:17
waynrbut wanted to bring it up here anyway to make sure I am doing everything I can to make it high visibility since it can be difficult for me also to sustain attention on a project like this for long periods of time (it's also not a huge priority for my team at work, it's mostly my pet/side project)19:17
waynryeah, the "feature/2.0.0" branch is no longer necessary I think19:18
fungii'm probably misunderstanding what went on in that feature branch, if you haven't merged it back to master yet19:18
waynrI think we came to the conclusion about a month ago that it would be too difficult to maintain two active branches of development so the 2.x series is what we want to move forward with as the main line of development19:19
*** shaohe_feng has quit IRC19:19
*** rderose has quit IRC19:19
fungiso do you have changes which landed on that branch that you need merged into master before you continue work in the master branch toward the 2.0 release?19:19
waynrnope, nothing was ever merged into the feature/2.0.0 branch19:20
waynrI rebased everything that was targeting it onto master branch over the weekend19:20
fungioh, got it. so you just have changes proposed against master that haven't landed19:20
waynryeah, exactly19:20
*** asettle has quit IRC19:20
*** sdake has quit IRC19:21
waynrso yeah, deleting that feature branch is the next step (I can update the 2.0.0 api spec if necessary to avoid possible confusion about what branch these changes are targeting)19:21
fungi#info Deleted openstack-infra/jenkins-job-builder feature/2.0.x branch which was previously at 245f643522da0236254bb14f055df5cbb571938f19:21
*** sdake has joined #openstack-meeting19:21
waynragain, another reason for me to bring up the 2.0.0 API work here is just to increase visibility (maybe someone who sees this discussion will be interested enough to help review :)19:22
fungifrom an openstack infra/ci perspective, as long as those changes aren't modifying the xml output by jjb i think we don't have much of a stake in the order in which you merge things. i'd leave that determination to the jjb core reviewers (zaro, electrofelix, zxiiro)19:22
*** megm has quit IRC19:23
waynri might throw this up onto the open discussion section of the meeting periodically if y'all think this is a good way to achieve that visibility goal (otherwise, I am open to alternatives)19:23
*** shaohe_feng has joined #openstack-meeting19:23
waynrthe answer might just be for me to keep pestering the other jjb cores19:23
fungiif the xml comparison ci job indicates a difference, please give me or one of our other admins some heads up and an opportunity to review the results19:23
*** jprovazn has quit IRC19:23
waynroh sure19:24
waynrI'm pretty sure that won't happen though19:24
jeblairwe'll probably pin jjb<2.0 for the zuul2.5 ansible launcher, since it uses internal api stuff19:24
*** jprovazn has joined #openstack-meeting19:24
jeblairsince our needs there are fairly static, that way we don't impact ability for jjb2 to proceed19:24
fungiyep, as a result i'm mostly happy to give the jjb team autonomy over what's going on there19:24
jeblair(and we can look at unpinning later when it settles)19:25
waynrjeblair: I'd be interested in seeing what parts of the API zuul2.5 is using19:25
*** megm has joined #openstack-meeting19:25
waynrI wonder if it is just jenkins_jobs.cmd.execute(args)19:25
jeblairwaynr: i'll point them out to you in channel after meeting; i did have to do a couple things i didn't like, maybe could positively influence jjb219:26
waynr(which is what my JJB 1.x wrapper project does)19:26
fungii think it's more for getting at the internal data structures representing job config data?19:26
waynroh... in that case I think you'll like some of the API changes I am making!19:26
fungibut yeah, no need to dive into that under this meeting topic19:26
fungianything else for this? zaro/zxiiro, did you have any input for waynr?19:27
*** baoli has joined #openstack-meeting19:27
zaroi'm fine with strategy proposed19:27
zxiirosounds reasonable to me19:28
waynrso the final thing was just protocol as far as merging changes in a large series such as this...is it fine to merge earlier commits once they are approved even if there is remaining 2.0.0 api work left to do?19:28
*** adiantum has quit IRC19:28
waynrzaro zxiiro the reason I ask this is that if for example someone wanted to get a high priority feature released they wouldn't be able to get it until the first 2.0 release19:29
*** kmartin has quit IRC19:29
waynr(once we've begun merging changes from the jjb-2.0.0-api topic, that is)19:29
*** shaohe_feng has quit IRC19:29
fungii'll defer to zaro and zxiiro on that as well. the usual concerns are that if you disappear without finishing it then there could be a half-implemented transition worth of technical debt to support or try and unwind again19:29
*** shaohe_feng has joined #openstack-meeting19:29
zaroyeah, i'm not sure there's a beter alternative though.19:30
*** sdake has quit IRC19:30
*** sdake has joined #openstack-meeting19:31
fungiright, every patch series has this inherent risk to varying degrees anyway19:31
fungiso it's more a question of comfort level of the reviewers19:31
*** cody-somerville has quit IRC19:31
*** cody-somerville has joined #openstack-meeting19:31
fungiokay, sounds like a bit of agreement around this. thanks waynr, zaro, zxiiro!19:32
waynrcool19:32
zarowaynr: you should probably get feedback from electrofelix though19:32
waynrthanks again fungi, anteaya for reminding me about the meeting!19:32
*** gagehugo has left #openstack-meeting19:32
anteayawaynr: and pleia219:33
waynrzaro: I'll make sure to ping him with a link to this meeting19:33
zxiirocool. I think electrofelix mentioned we can get high priority patches in a stable release branch too once we start merging 2.x stuff19:33
waynrand pleia219:33
waynranteaya: thanks for the correction!19:33
anteaya:)19:33
fungi#topic OpenID implementation (notmorgan, puiterwijk)19:33
*** openstack changes topic to "OpenID implementation (notmorgan, puiterwijk) (Meeting topic: infra)"19:33
notmorgano/19:33
puiterwijkI'm here still :)19:33
notmorganso. simply put this came up in an internal Red Hat meeting.19:33
notmorganlooking for a general idea for the timeline of moving openstackid to ipsilon19:34
notmorgan(desired timeline)19:34
*** torgomatic has joined #openstack-meeting19:34
notmorganand identifying what was needed, if anything, on the ipsilon side before we could do it.19:34
jeblairsmarcet is away for the next 2 weeks i believe19:34
notmorganaiui ipsilon now supports OIDC as well.19:34
puiterwijknotmorgan: correct. We merged that patch last week, and have submitted certification results (all pass)19:35
*** xyang1 has quit IRC19:35
fungii'm not sure we ever got complete consensus that we would necessarily replace openstackid with ipsilon, though we mighth start using ipsilon for things other than the www.openstack.org site if the foundation developers aren't keen on moving their site off openstackid19:35
puiterwijkSo in the next release, which should be end this week, it will be included19:35
pleia2fungi: ++19:35
jeblairas the driver for the current openstackid, i think it would be good to involve smarcet in discussions19:35
notmorganjeblair: ++19:36
jeblairbut perhaps we can continue to lay foundations while he's away19:36
notmorganfungi: or however we want to do it.19:36
fungiso while it would be preferable to make sure ipsilon can be used to achieve the same things the www site needs from openstackid, i wouldn't want to completely predicate our implementation on them agreeing to stop using openstackid there19:36
notmorganthe only concern i have if we don't replace openstackid.org is we may need a new domain for cookie isolation etc19:37
notmorgannot a huge hurdle19:37
*** mickeys has quit IRC19:37
*** e0ne has joined #openstack-meeting19:38
fungiwe have idp.openstackid.org as jeblair's early poc. seems like an okay one to keep using (unless the worry is that a compromise on the current openstackid.org server could be leveraged to steal authentication secrets from ipsilon sessions)19:38
*** vhoward has quit IRC19:38
notmorgani do want to point out that merging ids later (from a standpoint of registeted IDP) is more of a headache than not.19:38
notmorganfungi: that is a concern, but i think we're in a boat where that level of compromise is going to get ugly no matter what19:38
notmorganidp.openstackid.org is sufficient imo19:38
*** baoli has quit IRC19:39
notmorganpuiterwijk: feel free to disagree with me if you think otherwise :)19:39
pleia2it would be nice to see zanata move over to ipsilon, they're using them together upstream (in fedora) so that would give us a tested, known pairing there19:39
*** adiantum has joined #openstack-meeting19:39
*** shaohe_feng has quit IRC19:39
puiterwijknotmorgan: that sounds about right to me. Moving is a concern, and the cookies shouldn't be too much worse I'd say19:39
*** ig0r_ has quit IRC19:39
*** dimtruck is now known as zz_dimtruck19:40
fungidid we figure out whether we're able to (or even want to) use the same url pattern as openstackid uses for identifiers?19:40
notmorganfungi: not sure about that.19:40
puiterwijkfungi: as long as you setup the httpd redirects, Ipsilon can handle pretty much any url scheme you want19:40
puiterwijkWhat are you using now?19:40
fungifor example it gives https://openstackid.org/jeremy.stanley for my openid right now19:40
jeblairfungi: i configured it to use the openstackid scheme for identifiers19:40
jeblairi don't know that we agreed that was *desirable* but i believe it's *possible* :)19:41
notmorgani do want to say that if we lean on idp.openstackid.org for non-o.o sites, i would advocate moving o.o over to idp.oid.o if we decide to use ipsilon (we can use some httpd things for redirects...but in general)19:41
*** merooney has quit IRC19:41
fungii worry that tying the id to a human hane is problematic because humans change their names on occasion (i've brought that up with the openstackid devs more than once)19:41
notmorganrather than try and merge everything down to the bare-word domain19:41
*** sams-gleb has joined #openstack-meeting19:41
notmorgani would vote for "username" not "human name"19:41
fungis/hane/name/19:42
notmorganas well.19:42
puiterwijkfungi: right. That's why in Fedora we decided to use username as the non-changing ID which is used as identity.19:42
notmorganit's why almost every IDP does that.19:42
*** matrohon has quit IRC19:42
*** salv-orlando has joined #openstack-meeting19:42
puiterwijkWe use http://puiterwijk.id.fedoraproject.org/ (unfortunately, we started out without https, and switching later is a massive pain)19:42
*** shaohe_feng has joined #openstack-meeting19:42
jeblairi initially did that so that we could minimize the complexity of changing things that use openstackid to using ipsilon, as well as eventually moving ipsilon from idp.o.o to o.o19:42
fungii like that. we have some systems which consider username unchangeable once set (e.g., gerrit) so tying them together feels natural19:42
notmorganfungi: ++19:42
*** zqfan has quit IRC19:43
notmorganand i'd be more willing to argue/helpfolks make that change once.19:43
puiterwijkFor a better example: https://puiterwijk.id.gnome.org/ :)19:43
jeblairhowever, we can still accomplish those things with more complexity (like, using a script and a database dump to make the mappings)19:43
notmorganover trying to deal with usernames.19:43
notmorganerm humannames19:43
notmorganso it sounds like come back in a couple weeks and work on the db backend driver bits.19:43
notmorgan?19:43
notmorganand start working on details like username vs humanname19:44
puiterwijkIs anything wrong with the db backend driver? (sqlalchemy)19:44
puiterwijkOh, or did you mean auth db backend?19:44
notmorganpuiterwijk: as long as it's configurable, no issues19:44
fungii think jeblair already wrote a fairly basic backend db driver to grok the silverstripe user db used by the www site (same db that openstackid.org is looking at)19:44
notmorganpuiterwijk: auth db where the user data is.19:44
notmorgansilverstr... what fungi said19:44
jeblairfungi: yes i did, that's written19:44
*** phil_h has joined #openstack-meeting19:44
puiterwijknotmorgan: ah, I see :)19:44
notmorganok cool.19:44
notmorganpuiterwijk: as long as sql-a can be told to use non-sqlite dbs, we're good (for sessions etc)19:45
puiterwijknotmorgan: yep. I would actually not suggest sqlite for production. We fully support anything that's supported by sqlalchemy19:45
fungiit may need some extending to handle the authorization/group details there (from an oidc/oauth perspective)19:45
*** carolbarrett has joined #openstack-meeting19:45
jeblairi ran into some minor speedbumps setting up ipsilon; i think a good thing to work on now might be standing up a server with just the test backend (don't worry about silverstripe yet) and shake out the installation/config bits19:46
jeblair(in our environment)19:46
jeblairi have some very basic puppet standing by as well19:46
*** tonytan4ever has quit IRC19:46
fungisounds like there was also some work done recently to make sure it's more solid on debian-based distros, and there was talk of finding someone willing to make official debian packages for it?19:46
jeblairso perhaps i should get that into a new puppet module, and then stand up a server19:46
puiterwijkjeblair: for puppet, you might want to use ipsilon-db2conf. That will generate you a configuration file if you prefer to use that over web administration19:47
jeblairpuiterwijk: oh cool19:47
*** merooney has joined #openstack-meeting19:47
puiterwijkfungi: yeah, I've been testing various parts on Debian, and am now adding test skipping to the test suite so I can actually run the suite on Debian19:47
puiterwijk(there's a few modules that will unfortunately not work on Debian anytime soon like SSSD, but the rest should work just fine)19:47
*** gyee has quit IRC19:47
notmorgannot super worried about SSSD not working19:47
notmorgantbh19:48
puiterwijkAnd yeah, if anyone's interested in helping packaging for Debian, feel free to get in touch.19:48
*** ociuhandu has quit IRC19:48
puiterwijknotmorgan: yeah, didn't think so. But that's one of the reasons you can't run the test suite right now, because there's no easy way to skip those tests on Debian :)19:48
fungialso, if there's interest, we may have people willing to help get sdist/wheel working so you can publsh releases to pypi too19:48
*** mugsie|mobile has joined #openstack-meeting19:48
puiterwijkfungi: sounds good. If there's anyone interested in doing that, feel free to bring them in touch with me19:48
puiterwijknotmorgan: after I get the test skipping et al in, I plan to add Debian to the list of OS's that need to pass for every patchset to be merged.19:49
*** timcline has quit IRC19:49
fungipuiterwijk: also you may want to create an account on pypi.python.org and register https://pypi.python.org/pypi/ipsilon so that it doesn't get snapped up by a squatter or something19:49
*** ifat_afek has joined #openstack-meeting19:49
*** zz_dimtruck is now known as dimtruck19:49
puiterwijkI have an account, and that's a good idea19:49
*** sams-gleb has quit IRC19:49
*** shaohe_feng has quit IRC19:49
*** moiz has quit IRC19:49
* notmorgan steals it fast :P19:50
notmorgandef go register it.19:50
*** shaohe_feng has joined #openstack-meeting19:50
puiterwijkJust did.19:50
puiterwijkThanks for the hint19:51
fungiokay, anything else we want to cover for now, that doesn't need to wait for smarcet to be back around?19:51
*** merooney has quit IRC19:52
fungithanks notmorgan and puiterwijk!19:52
fungi#topic Open discussion19:52
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:52
* notmorgan goes back to lurker mode for a few minutes.19:53
fungianybody do anything fun for victoria day/patriots day, or planning something interesting for memorial day?19:53
pleia2fyi, I'm taking a long memorial day weekend, so I'll be away this Thursday - Tuesday, then working east coast time Wed-Friday19:53
fungii've been informed i won't be around monday, so that i can get some projects done on the house19:53
anteayaI went for a nice walk yesterday19:53
pleia2visiting family and moose and eating lobster rolls in Maine :)19:53
anteayawas beautiful19:53
anteayapleia2: nice19:54
jeblairfungi: i think i will be joining you, in spirit at least.19:54
anteayafungi: lucky you19:54
ianwpromethanfire raised some issues with our project-config dib elements which resulted in https://etherpad.openstack.org/p/gentoo-ci19:54
*** rustlebee has quit IRC19:54
*** rustlebee has joined #openstack-meeting19:54
*** rustlebee is now known as russellb19:54
prometheanfirehttps://review.openstack.org/#/c/319030/ https://review.openstack.org/#/c/318994/19:54
ianwso there is some work to do, but i think we can overhaul things to fix up the dependencies there19:54
prometheanfirethose are the two reviews that came from that etherpad so far19:54
anteayapleia2: I understand moose rolls are quite tasty19:55
fungibswartz: also pointed out that the ubuntu-core trusty base images dib's ubuntu element (but not the ubuntu-minimal element we use for nodepool) are no longer being provided by canonical19:55
fungis/://19:55
pleia2anteaya: oh dear, we'll be visiting one (some?) at an animal care facility, no eating :)19:55
pleia2(this is like the kangaroos all over again!)19:55
fungiso i guess anybody using that dib element is in a bad way now19:56
jeblairthe ansible environment variable situation is "whack".  i'm nearing the bottom of that; when i get there, i think we'll be ready for zuulv2.519:56
*** jamesmcarthur has quit IRC19:56
anteayapleia2: ah visiting the moose, eating lobster rolls, now I get it19:56
pleia2anteaya: yes, eat the sea bugs, visit the fluffy animals19:56
prometheanfirefungi: no, the dep tree is really just a collector19:56
prometheanfirenot a true graph19:56
*** singhj has quit IRC19:56
anteayapleia2: enjoy the fluffy animals :)19:56
ianwfungi: yeah, i've wondered if we really have the bandwidth to support the !minimal paths19:56
prometheanfireso it's fine, just slightly counterintuitive19:56
pabelangerjeblair: excellent19:56
*** annegentle has joined #openstack-meeting19:56
*** jamesmcarthur has joined #openstack-meeting19:56
anteayajeblair: all these technical terms today19:57
anteayaI can't keep up19:57
pabelangerjeblair: I'll try and finish off the zuul-worker DIB element this week.  Need to do a few updates to some puppet bits19:57
*** amakarov is now known as amakarov_away19:57
zarofungi: most likely route to force online reindex is with admin-console plugin.19:57
ianwfungi: yeah, deps run in different phases ... but it would sure be nice for testing if caching the repos was a separate thing.  currently it gets  pulled in before we run puppet19:57
jeblairpabelanger: cool; it's not a blocker but will be nice to have when we're ready for the jenkinsectomy19:58
fungizaro: that sounds like a good way forward to me then. thanks for researching19:58
*** asettle has joined #openstack-meeting19:59
fungiokay, anything else? we're at 45 seconds remaining19:59
*** cdent has joined #openstack-meeting19:59
fungi(last call!)19:59
pleia2thanks for chairing, fungi19:59
prometheanfirehave a nice weekend19:59
fungiyou're welcome!19:59
fungi...and we're out of time--thanks everyone!19:59
fungi#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue May 24 20:00:01 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-05-24-19.03.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-05-24-19.03.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-05-24-19.03.log.html20:00
fungithe stage is yours, ttx20:00
*** shaohe_feng has quit IRC20:00
flaper87o/20:00
annegentleo/20:00
mesteryo/20:00
dhellmanno/20:00
ttxo/20:00
prometheanfirewhich one is this one?20:00
* dougwig is lurking.20:00
*** gordc has joined #openstack-meeting20:00
* rockyg is snoozing in the back20:00
dimso/20:00
ttxjohnthetubaguy, mtreinish, thingee, mordred, morgan, russellb, sdague : around ?20:00
sdagueo/20:00
* edleafe finds a dark spot on the side20:00
thingeeo/20:00
fungiprometheanfire: technical committee20:00
* mugsie|mobile lurks20:01
johnthetubaguyo/20:01
*** leeantho has quit IRC20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue May 24 20:01:06 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
prometheanfireoh, this should be fun20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
openstackThe meeting name has been set to 'tc'20:01
mtreinisho/20:01
russellbo/20:01
*** shaohe_feng has joined #openstack-meeting20:01
* flaper87 bows20:01
* prometheanfire lurks20:01
ttxHi everyone!20:01
ttxWe have accumulated a sane backlog... Our agenda for today:20:01
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:01
ttx#topic Clarify language about expectations for cycle-with-intermediary releases20:01
*** openstack changes topic to "Clarify language about expectations for cycle-with-intermediary releases (Meeting topic: tc)"20:01
ttx#link https://review.openstack.org/31831920:01
*** nadeem has joined #openstack-meeting20:02
ttxThis one is just a language clarification. Saw no objection, just got enough votes20:02
ttxSo will approve now unless someone screams20:02
*** sdake_ has joined #openstack-meeting20:02
dimsttx : sounds good20:02
* notmorgan screams for ice cream?20:02
ttx#topic Adds a docs:devdocs tag to indicate if project publishes devdocs20:02
*** openstack changes topic to "Adds a docs:devdocs tag to indicate if project publishes devdocs (Meeting topic: tc)"20:02
* flaper87 wants icecream20:02
*** asingh has quit IRC20:02
ttx#link https://review.openstack.org/31639620:03
ttxThis one is slightly more contentious. Anne proposes a tag to describe which projects have developer docs20:03
thingeecan we avoid discussing the maturity level in this topic please.20:03
ttxI think that's a valid piece of information for users, but I also think it's accurately communicated through:20:03
ttxhttp://docs.openstack.org/developer/openstack-projects.html20:03
ttxthingee: I think we can20:03
mesterythingee: ++20:03
ttxSo.. I'm unconvinced of the benefit of maintaining this in two places20:03
annegentlettx my only concern with  using openstack-projects.html is it's a manual process to keep that updated20:03
russellbcan it be applied per repo?20:03
*** Leom has quit IRC20:04
*** sgotliv_ has joined #openstack-meeting20:04
sdaguettx: we maintain diversity tags in 2 places ?20:04
russellbaren't those docs usually a per repo thing?20:04
*** swiftfan has joined #openstack-meeting20:04
ttxannegentle: it's also a manual process to update the tags ?20:04
thingeerussellb: tags today allow that, so yes?20:04
annegentlerussellb not in my findings unfortunately20:04
sdaguehow is this different than that?20:04
russellbthingee: ack20:04
*** Apoorva_ has quit IRC20:04
dhellmannsdague : where do we do that?20:04
ttxsdague: I don't understand20:05
mtreinishannegentle: just curious could we use the script in the existing place?20:05
annegentlettx oh I don't see it as super manual when I can run a script.20:05
sdaguewe created a tag for diversity based on data you can find elsewhere20:05
*** ociuhandu has joined #openstack-meeting20:05
*** sdake has quit IRC20:05
annegentlemy idea is to start with this tag, then expand to different docs:20:05
annegentletags to indicate which projects are more complete in their20:05
*** pabelanger has left #openstack-meeting20:05
annegentledoc coverage.20:05
ttxWe have a page that lists dev docs. Anne proposes that we build tags that say "yes, there is a devdoc entry for the project on that page". I'm not sure what added value that brings to the user20:05
annegentlederp paste20:05
*** lhcheng has left #openstack-meeting20:05
*** phil_h has quit IRC20:05
*** jaugustine has quit IRC20:05
annegentleI'd like to have a starting point, and what we tell early projects now is "at least write contrib docs"20:06
dhellmannsdague : ah, yeah. I think I made the same argument against that tag, too. This case is even "worse" in the sense that it's a binary flag. At least for diversity it's a summary of the data collected elsewhere.20:06
sdaguettx: it seems like value from the project overview perspective.20:06
*** asingh has joined #openstack-meeting20:06
flaper87and I believe it's different from the diversity tag20:06
annegentlethen we can add more doc tags for what else is written/maintained20:06
thingeethis would assumes the user is someone interested in the development processes of a project.20:06
annegentleI could skip to a "docs:drift" tag instead, which would measure the time diff between when RST files were last updated versus code files20:06
johnthetubaguyannegentle: so if we autogenerated the info into the generated html, would that do the same thing?20:07
annegentlethingee yeah, it's an audience-centric view. Not the greatest approach.20:07
ttxIn the case of the diversity, you have to interpret a pie chart into a boolean, not just copy a boolean into another boolean20:07
sdaguethe whole point of tags was to provide one stop shop for information about a project that is useful to consumers20:07
*** baoli has joined #openstack-meeting20:07
mtreinishjohnthetubaguy: yeah, that's what I was wondering20:07
sdaguettx: but you still need to know where to find that other thing20:07
sdagueyou are assuming a lot of pre knowledge20:07
thingeeas oppose to today where we have a tag recognizing installation docs and the user is someone who is deploying something20:07
thingeeops tag actually20:07
annegentlemtreinish johnthetubaguy maybe? so take openstack-projects.html and do something?20:07
fungiworth noting, contributor documentation is often expected by contributors to be found in the git repo for the project they just cloned or are browsing, so also having it published in a rendered form on docs.openstack.org seems sort of secondary20:07
johnthetubaguyaggregating data is useful, when exploring projects20:08
ttxsdague: you mean, we need to assume people look for documentation by clicking on a linkk saying "Documentation" on almost every openstack website ?20:08
annegentlefungi that's true, and a fair point.20:08
notmorgani just want to say i don't have a strong view here.20:08
fungifor example, most of our projects have a CONTRIBUTING.rst in the top-level directory, few of them actually publish that anywhere in a rendered form20:08
notmorgani will support the direction annegentle would like to see it go.20:08
sdaguehonestly, I feel like replicating information that can be done nearly automatically has very low cost, and at least some benefit20:08
notmorgansine i think she has a solid understanding of the needs on this front.20:08
rockyguh, as a "user", I'll go wherever I might find an answer, so the tag would be useful20:09
annegentleI think mtreinish might be onto something, where we "quality check" the completeness of openstack-projects.html.20:09
ttxI'm just trying to avoid extra bureaucracy and stale data. If Anne thinks she can maintain the tag alright, why not20:09
johnthetubaguysdague: thinking a similar thing, honestly20:09
notmorganttx: that is 100% fair20:09
johnthetubaguyI mean skip the tag, and just add something into the rendered html?20:09
thingeeI don't see a strong benefit of being able to see this information at a glance besides knowing the doc coverage as annegentle mentioned. If it can be maintained easily, i don't see harm in in it. I also don't have a strong opinion.20:09
dimsthe link to the doc for a project is more valuable than the tag itself..20:09
flaper87I'm honestly more concerned about what other tags we're considering for the docs group than this one per se.20:09
mesterydims: ++20:09
annegentlejohnthetubaguy honestly I'm not in love with "devdocs" tag because it's not that meaningful to end users20:09
dhellmannjohnthetubaguy : yeah, I suggested adding URLs instead of a tag20:10
ttxalso as a data point, the existence of an install doc is maintained as an ops tag20:10
dimsdhellmann : ++20:10
annegentleI wanted to get this up there as a POC to see if we could automate docs tags...20:10
sdagueadding urls would also be fine with me20:10
johnthetubaguydhellmann: I missed that, that would work20:10
rockygdhellmann, ++20:10
*** shaohe_feng has quit IRC20:10
*** tonytan4ever has joined #openstack-meeting20:10
*** asingh has quit IRC20:11
ttxI'd say that adding urls feels like less useless duplication, at least one can get to the doc from there20:11
annegentledhellmann I like that idea because looking now, people tend to point to a wiki page, blech.20:11
johnthetubaguygiven nova vs compute, for dev and api docs, its handy to have a lookup20:11
dhellmannurls work for this tag, but will be a bit complicated for "is covered by an install guide" since there may be several20:11
dimsannegentle : agree20:11
mesteryI like dhellmann's idea of the urls to be honest20:11
flaper87So, URLs and we're good ?20:11
sdaguedhellmann: maybe, there is typically a base entry point20:11
flaper87:D20:11
annegentleall: and for the next trick, how to figure out which projects are lacking API docs?20:11
russellburls ++20:11
ttxdhellmann: so adding to the deliverable grammar rather than use a tag ?20:11
sdagueannegentle: and I agree, api doc url is also good here20:11
johnthetubaguyannegentle: a URL?20:11
dhellmannttx; right, I propose a data model in a comment on anne's patch20:12
annegentlejohnthetubaguy well, it also gets to "are you publishing to a known URL pattern or not?"20:12
ttxdhellmann: this still creates a maintenance cost and a risk of stale data, but I can see it was having higher value, so that compensates20:12
ttxs/was/as20:13
dhellmannttx: yeah, staleness is going to be a bit of a concern either way20:13
*** shaohe_feng has joined #openstack-meeting20:13
annegentleI'd still like ideas for discovering which projects are off-pattern... ideas?20:13
ttxok, so let's express that in the review and morve formward ?20:13
flaper87++20:13
annegentleyes please add to review20:13
*** Sukhdev has quit IRC20:13
*** adiantum has quit IRC20:13
ttxannegentle: you can easily check which project is missing the extra devdoc yaml entry20:13
ttxeven easier than checking presence of tag20:13
annegentlettx yep that pattern will help immensely, is it ok to then spread to other doc types? Please comment on review.20:14
dhellmannannegentle : if we specify base URLs in code, and slugs in the YAML, then all of the functional URLs will have to follow the pattern.20:14
*** lpetrut has quit IRC20:14
sdaguethis data really shouldn't get very stale. If people are randomly moving docs urls all over the place, that's a way different problem20:14
dimsdhellmann : love it20:14
annegentlesdague they are for api-ref for sure already20:14
ttxyou can have a doc: entry at the same level as tag entries, and then list URLs to various types of docs20:14
sdagueannegentle: in a one time move20:14
annegentlesdague by not publishing the same way20:14
annegentlettx ok put an example in the review, thanks!20:14
*** asettle has quit IRC20:14
annegentleI'll take on which doc urls in a revision20:15
johnthetubaguyannegentle: sdague: as an aside, I guess we need to fix that with redirects or something, but thats a difference conversation20:15
dhellmannannegentle : see my comment from May 2320:15
ttxdoc: - devdoc:<URL> - install:<URL> etc20:15
*** dmorita has quit IRC20:15
ttxOK, I think we can iterate on the review and offline20:15
annegentlejohnthetubaguy we do redirects a lot now, but yes, that would be ideal20:15
dhellmanns/devdoc/contribdoc/20:15
annegentledhellmann cool20:15
annegentlettx yep! Thanks20:15
ttxI propose we move on to next topic20:15
flaper87++20:16
ttx#topic Trim tc-approved-release tag to just base IaaS projects - initial discussion20:16
*** openstack changes topic to "Trim tc-approved-release tag to just base IaaS projects - initial discussion (Meeting topic: tc)"20:16
*** jamesmcarthur has quit IRC20:16
ttx#link https://review.openstack.org/31469120:16
ttxLet's timebox the initial discussion on this one to 20  minutes to give room to make progress on the golang discussion20:16
ttxOnly Doug and I have been posting comments on this one so far (as TC members)20:16
notmorgani don't understand the intentioin here. it seems superfluous to do?20:16
mtreinishttx: well and me :)20:16
ttxProposal is to limit tc-approved-release to "Base IaaS" projects, removing heat, horizon, ironic, sahara, ceilometer and trove20:16
ttxmtreinish: obviously :)20:16
thingeeI think this is some other kind of tag. Also this will be difficult to determine.20:16
dhellmannnotmorgan: not just superfluous, but against the established process20:17
ttxIn my comment I noted the proposal is a bit incompatible with how we said we'd use 'tc-approved-release' when it was first created20:17
notmorgandhellmann: fair enough20:17
ttxi.e. it was not meant to describe "Base IaaS" projects, it was only meant to fulfill our obligations under the Foundation bylaws20:17
ttxwith changes to the list being Board-driven rather than TC-driven20:17
thingeeAnd I'm curious on the value. Was that explained somewhere?20:17
ttxOf course we could change that, but I think in that case we should update the tag description as well20:17
mugsie|mobileOr a new tag?20:17
notmorgandhellmann: i voted and concur with your vote.20:17
dhellmannyeah, this tag was defined very carefully to avoid having to keep having this discussion at all20:17
mtreinishttx: right, but as long as the borad process is being used to determine technical things like interop requirements I think we should take a more active role in determining what is included there20:18
thingeeso new tag ... if there's value20:18
notmorganthingee: i said as much in my review.20:18
dimsthingee  mugsie|mobile ++20:18
ttxthingee: yes20:18
dougwigthis tag has some overlap with computer:starter-kit idea, imo.20:18
*** fzdarsky is now known as fzdarsky|afk20:18
dhellmannmtreinish : if there are issues with projects on the list, we should address those one at a time.20:18
mtreinishI can respin it as a new tag, thats easy enough to20:18
*** kmartin has joined #openstack-meeting20:18
dougwig /this tag/this change/20:18
*** phil_h has joined #openstack-meeting20:18
dimsmtreinish : sounds like the right thing to do20:18
thingeesigmavirus24: yea what about compute:starter-kit as dougwig suggested20:18
ttxI can see the cost of that tag (endless discussions on what is "Base IaaS" and not sure what value it brings to end users of openstack20:19
mesterydougwig: Good point20:19
sigmavirus24huh?20:19
dhellmannmtreinish : like http://governance.openstack.org/reference/tags/starter-kit_compute.html ?20:19
notmorganttx: starterkit seems to cover this anyway20:19
sigmavirus24How did I get pulled into this?20:19
flaper87thingee: you meant dougwig20:19
flaper87:D20:19
flaper87sigmavirus24: typo20:19
notmorgansigmavirus24: typo?20:19
sigmavirus24ah20:19
thingeesigmavirus24: http://governance.openstack.org/reference/tags/starter-kit_compute.html20:19
dims:)20:19
jrollmtreinish: so 'base' here means 'covered by defcore'?20:19
* notmorgan makes it a point to bring sigmavirus24 into every convo now20:19
mesterynotmorgan: lol20:19
johnthetubaguyif we don't want to talk about the tag, should we not either delete it, or added to everything?20:19
* sigmavirus24 shakes head20:19
mugsie|mobileWhy should only base iaas be covered by defcore?20:20
notmorganjohnthetubaguy: it is mostly historical. it was a baseline to start with, long term it should be something we can drop20:20
dhellmannjohnthetubaguy : the tag is an implementation of our duties under the bylaws w.r.t. the defcore committee20:20
mtreinishsure, compute starter kit is similar, but the problem is for the purpose of actually enforcing interop the tc isn't actually asserting those projects. Its saying anything which was in the intergrated release pre big tent can be used20:20
notmorganjust not yet20:20
thingeesigmavirus24: oh heh, for some reason I thought I read last night you starting this, sorry20:20
ttxnotmorgan: starterkit has value ("what should I start with"). Not sure "What are the 'Base IaaS' projects" is a question users have and we need to provide an answer for20:20
sigmavirus24thingee: no worries :D20:20
dhellmannso we need the tag, unless we come up with another way to do that, but we have the tag so we don't need another way to do it20:20
*** shaohe_feng has quit IRC20:20
*** Leom has joined #openstack-meeting20:20
notmorganttx: right, starterkit i see as the intention of this change.20:20
dhellmannthe name of the tag was, as described in its definition, selected specifically because that's what the bylaws call this list20:20
mtreinishif defcore is the only trademark thing which as a community we're also using to enforce interop I fele like we should be a bit more targetted in what we say should be used there20:20
notmorganttx: in spirit if not in the letter20:20
thingeenotmorgan, dhellmann +120:21
ttxnotmorgan: except it's larger than starter-kit20:21
*** pdardeau has joined #openstack-meeting20:21
notmorganttx: hence my view it's the spirit of the change20:21
dims"has-interop-tests"?20:21
notmorganeven though it's a narrower tag (starterkit)20:21
johnthetubaguymtreinish: it does feel wrong to side step our obligations around maintaining the tag20:21
sdaguetags are cheap, so lets not overload existing things20:21
dhellmannmtreinish : if we end up with 2 interop processes, we're going to have different versions of interoperability20:21
mugsie|mobilemtreinish: why? Should we not aim to have trove etc checked for interop?20:21
*** shaohe_feng has joined #openstack-meeting20:21
*** ayoung has quit IRC20:21
* dims nods with mugsie|mobile 's question20:22
mugsie|mobile(Or Designate, but I would argue we should be base iaas)20:22
ttxI kind of see what mtreininsh wants though...; there are things in tc-approved-release we'd likely never ever want in the "OpenStack-powered compute" trademark program20:22
dhellmannttx: it's not our job to define trademark programs20:22
notmorganso, lets invert this.20:22
ttxdhellmann: right20:22
dhellmannthat's the board's job20:22
johnthetubaguyso tested for interop and in the OpenStack-powered compute are not the same thing right?20:22
thingeedhellmann: +120:22
notmorganif defcore wants to propose the "trademark" tag20:22
dhellmannand they're doing that by creating different programs as needed20:22
flaper87dhellmann: ++20:22
notmorganlet them.20:22
dimsdhellmann : we need something to reflect which ones we cover under trademark programs?20:22
notmorganand i'll support it20:22
notmorgani don't want the TC to define it20:22
ttxdhellmann: also compute is not the only trademark they might want to create20:22
* markvoelker notes that it is possible to create other Components than what is in DefCore today, and give them their own interop/Powered badges20:22
mtreinishdhellmann: it's not, but we also use it to say this is what we mean to be interoperable (with defcore) which feels like a technical thing20:22
ttxmarkvoelker: ++20:23
notmorgandefcore/board.20:23
johnthetubaguynotmorgan: hence my suggestion of adding the tag to every project, if thats what we want to do20:23
*** Apoorva has joined #openstack-meeting20:23
dhellmanndims : yes, the tc-approved-release is our list of projects we consider reasonable for defcore to be looking at -- the ones we've agreed for them to look at20:23
flaper87markvoelker: ++20:23
*** timcline has joined #openstack-meeting20:23
notmorganjohnthetubaguy: i'd rather let this tag die long term. it's very historical20:23
dimsmarkvoelker ++20:23
flaper87we can have a tag for what projects are interoperable, as it's been mentioned already20:23
johnthetubaguynotmorgan: I am OK deleteting it20:23
dhellmannwe can't have a membership change in the TC having big changes in that list, because it takes a while for defcore to move20:23
johnthetubaguymarkvoelker: totally +1 that20:23
sdagueright, tc-approved-release is what the TC has said the board can consider for interop20:23
ttxnotmorgan: unfortunately the bylaws change very slowly20:23
notmorganttx: yes i know.20:23
cdentIt sounds like people are wanting to abdicate technical responsibility (for interoperability) to defcore, which seems contrary to what I would hope a _technical_ committee is for.20:23
dhellmannnotmorgan : no, no, it's not historical -- the current membership is historical but the tag is definitely something we have to keep up with20:24
sdaguecdent: well, it's more subtle than that20:24
mugsie|mobilecdent: ++20:24
flaper87cdent: I don't think that's the intention20:24
notmorgancdent: we have unfortunately already delegated that long ago20:24
*** dmowrer has quit IRC20:24
dhellmanncdent : not abdicate, collaborate20:24
notmorgancdent: but the intention here is not to have the TC dictate what is defcore sprecifc20:24
cdentsdague: I know it is more subtle than that, but it does _sound_ that way.20:24
*** singhj has joined #openstack-meeting20:24
sdaguebecause the board owns the mission of the commercial competition space. So they really should be the one to come up with commercial certifications they feel best fit in the marketplace20:25
notmorgancdent: but have defcore propose from their side as well getting collaboration20:25
dhellmannthe tc has input into defcore through this tag and through statements about future technical direction (see my pending proposals for examples)20:25
*** dmowrer has joined #openstack-meeting20:25
dhellmannand of course anyone can go to defcore meetings and argue points there20:25
hogepodgecdent: defcore is a board process which seeks direction from tc20:25
sdagueand the TC has the ability to say, via tc-approved-release, this is the menu of things we're ok with you building from20:25
notmorganbut the board and defcore comittee owns the trademark stuff. I just can't see us defining the tag w/o directed input from the board and defcore20:25
dhellmannthat process is open, and done through code review20:25
ttxcdent: the weapon you can enforce interoperability with is trademark programs -- and that's the board prerogative20:25
sdagueand we've generally agreed at this point the menu is bigger than defcore needs, and that's fine20:25
sdaguebecause nothing on the menu is rediculous20:25
notmorganso i'd rather have the proposal inverted if we're using it in this way20:25
dhellmannsdague : right, we never want this list to be too much smaller than what defcore needs/wants20:26
dimsso we should not take things out of that menu20:26
notmorganwe work with defcore to determien what the tag is. anyway i think i've said enough.20:26
ttxcdent: they get to define what the OpenStack[tm] can be applied to20:26
sdagueand if the board feels there is another cert they want to spur competition / market on, they can ask the tc to put more on the menu20:26
*** noslzzp_ has quit IRC20:26
dhellmannnotmorgan : all of that work was already done, that's how the tag was created in teh first place20:26
notmorgandhellmann: right20:26
*** sridhar_ram has joined #openstack-meeting20:26
*** factor has quit IRC20:26
flaper87dhellmann: ++20:26
notmorgandhellmann: so nothing to change imo20:26
dhellmannsdague : right, that's what we said when we created the tag20:26
rockyg++20:26
dhellmannI feel like there's just some history here that folks don't remember/know/understand.20:27
sdaguewe can decide that stuff should come off the menu. That's fine, that's a very specific different thing.20:27
edleafedhellmann: ++20:27
mesterydhellmann: ++20:27
dhellmannsdague: yes, but we should do that deliberatively and one project at a time20:27
sdaguebut I don't think we want to conflate that with what's actually being interop tested20:27
dimsdhellmann : agree20:27
dhellmannand with "reasons" beyond "cleaning up"20:27
notmynamedhellmann: seems like a good summary of a lot of openstack discussions ;-)20:27
sdaguebecause it always was supposed to be larger20:27
ttxI should probably unearth links to the orginal discussion for context20:27
dhellmannnotmyname : so true20:27
dimssdague : so we need a tag that reflects what's being defcore-tested20:27
sdaguedims: that would be fine20:28
dimsat this moment20:28
hogepodgesdague: dims: defcore is a very small subset of openstack, "core", and we could communicate that better.20:28
dhellmanndims : well, that gets us back into redefining things that are defined elsewhere. DefCore has that info, and there's a trademark site that lists the current rules.20:28
*** asettle has joined #openstack-meeting20:28
annegentlemtreinish so is that the need, to indicate whats tested?20:28
sdaguehogepodge: right, given the amount of confusion, I think a tag would actually be quite useful20:28
dimsdhellmann : yep, so we don't need to do that here20:28
hogepodgesdague: +120:28
ttxIt's not completely crazy to have a tag that reflects current defcore projects. Not sure that's a question that people actually have, but I can see it clarifying things20:28
sdaguebecause I bet most of the TC doesn't know what the list is :)20:28
*** asettle has quit IRC20:28
sdagueeven though they could look it up20:29
dimshaha20:29
rockygdhellmann, dims ++20:29
rockygDefined in DefCore repo.20:29
dimsone google search away :)20:29
mtreinishannegentle: well I was more trying to define a set of what the tc thinks is base set of projects for interop20:29
*** baoli has quit IRC20:29
hogepodgettx: sdague: especially since compute will capture keystone, cinder, nova, glance, neutron. it's confusing20:29
dhellmannsdague : how about a link from http://governance.openstack.org/reference/tags/tc-approved-release.html to that info?20:29
dimsmtreinish : what yardstick would you use to measure that?20:29
mugsie|mobileand again,  why should that list only be iaas?20:29
*** baoli has joined #openstack-meeting20:29
annegentlemtreinish that was originally the starter kit20:29
*** dmowrer has quit IRC20:30
sdagueannegentle: it's not20:30
mesteryannegentle: I didn't think the starter kit was for interop20:30
hogepodgebut, a defcore tag should say 'defcore' to prevent even more confusion20:30
sdaguemestery: ++20:30
mtreinishannegentle: maybe, but if so I feel there is a disconnect in the messaging then20:30
annegentlesdague mestery ok, right, it was for computing20:30
mesteryyes20:30
annegentlemtreinish nope I'm wrong :)20:30
sdagueright, lets not conflate things20:30
*** shaohe_feng has quit IRC20:30
johnthetubaguymestery: are you suggesting the menu is too big for defcore right now, or something different?20:30
sdaguebecause there are a few different slices here, which have very close member sets, but they are for different reasons20:31
flaper87so, the time is almost up for this topic. Can we summarize the discussion and write down the main take-aways ?20:31
*** rderose_ has quit IRC20:31
sdagueand that was the whole problem with the "integrated release"20:31
mesteryjohnthetubaguy: I'm not suggesting anything, I was just saying the "compute:starter" tag was not indicating interop20:31
dhellmannright20:31
*** jprovazn has quit IRC20:31
dimsmestery : ack20:31
johnthetubaguymestery: sorry, I used the wrong name, that was for mtreinish20:31
mesteryjohnthetubaguy: heh, no worries :)20:31
anteayaso many m's20:32
mtreinishjohnthetubaguy: I think it is, like horizon isn't likely ever gonna be an interop requirement20:32
sdaguemtreinish / hogepodge so how about a whole new tag here?20:32
*** fdegir has joined #openstack-meeting20:32
johnthetubaguymestery: my typing skills at 9pm are even worse than normal!20:32
dhellmannI'd be OK with a tag reflecting what defcore is using. I don't think we need a tag "suggesting" an interop set of any sort.20:32
*** sridhar_ram1 has joined #openstack-meeting20:32
sdaguemtreinish: well, I think I agree with dhellmann that we should do deletes from that 1 at a time.20:32
mtreinishjohnthetubaguy: and I think a base interop set shouldn't be things that consume other openstack apis (but maybe that's just my opinion)20:32
flaper87johnthetubaguy: try it at 10pm :P20:32
notmorganjohnthetubaguy: the old "m<tab>" trap20:32
notmorganjohnthetubaguy: i am very familiar with it.20:32
mtreinishsdague: sure, I can do it as that20:32
mugsie|mobilemtreinish: but why does it have to be iaas?20:32
mugsie|mobileflaper87: I feel your pain20:33
mtreinishmugsie|mobile: well what kinda of openstack cloud doesn't use iaas as a base?20:33
johnthetubaguyflaper87: we should compare hours after evening meal or something, heh20:33
ttxOK, I think there is general agreement that whatever this tag is trying to convey, tc-approved-release is probably not the right place for it20:33
*** sridhar_ram has quit IRC20:33
flaper87ok, I guess we'll iterate again over the new patchset with the new tag20:33
mesteryttx: ++20:33
thingeettx: +120:33
dhellmannmtreinish : I think you're trying to pull the TC into an area that's the board's responsibility.20:33
*** shaohe_feng has joined #openstack-meeting20:33
johnthetubaguymtreinish: sdague: yeah, I am +1 the one by one removal, FWIW20:33
mtreinishI'm fine with working it as a new tag20:33
dougwigmtreinish: can you really get a large group of people to define IaaS the same way?20:33
ttxThere might be room for another tag (or not) but let's wait until that is proposed ?20:34
hogepodgesdague: yes, defcore has meaning and a tag to capture that is useful20:34
mtreinishdhellmann: interop is very much a TC thing20:34
johnthetubaguyand a new tag for the new thing sounds like a nice idea too20:34
sdaguehogepodge: ++20:34
dhellmannmtreinish : defining sets of things though?20:34
sdagueok, so mtreinish has 2 todos, right?20:34
flaper87We should wait for mtreinish's new PS and comment there.20:34
ttxWe are approaching our timebox20:34
johnthetubaguyso interop is a TC thing, trademarks is a board thing, right?20:34
* jroll wonders what world bare metal machines aren't IaaS :P20:34
sdaguenew tag, plus propose any appropriate deletes?20:34
mugsie|mobilejroll ++20:34
thingeejroll: heh20:34
hogepodgemtreinish: I'd like for projects outside of defcore to define what interop means to them too, again, guidance20:34
sdagueand we move on those in gerrit20:34
dhellmannwhere "appropriate deletes" includes detailed reasons beyond cleaning things up20:34
edleafejroll: ++20:34
*** baoli has quit IRC20:34
mtreinishjroll: I was thinking only from the api side, not the functionality20:34
sdaguedhellmann: absolutely20:34
jroll(I get the removal motivation here, but "not IaaS" heh)20:35
jrollmtreinish: yeah, fair20:35
johnthetubaguydhellmann: +120:35
dimsmtreinish : +120:35
*** baoli has joined #openstack-meeting20:35
mtreinishjroll: in the ironic case it goes through nova for the most part :)20:35
*** julim has quit IRC20:35
sdaguejroll: yeh, ironic is super weird in not having a user API from an interop perspective20:35
ttxOK, let's move on to next topic20:36
sdaguewhich isn't that it's not an important project, it's just that by rule it can't be defcore, which doesn't do admin apis20:36
jrollsdague: right, I get that it's an interop thing, and I'd agree for now, but we should be clear about that rather than saying "IaaS"20:36
thingeettx: +1 move on20:36
sdaguejroll: agree20:36
*** asingh has joined #openstack-meeting20:36
ttxplease follow-up on that review20:36
ttx#topic Add golang as an approved language - benefits vs. costs, and the scope clarification option20:36
*** openstack changes topic to "Add golang as an approved language - benefits vs. costs, and the scope clarification option (Meeting topic: tc)"20:36
ttx#link https://review.openstack.org/31226720:37
* edleafe gets popcorn20:37
ttxLast week I tried to reframe the choices we actually had on this one, since I think we can't really say "no" to golang in official OpenStack projects as they stand20:37
flaper87edleafe: share20:37
ttxSo I presented two alternatives: "yes" and "no and do things in other languages as OpenStack dependencies"20:37
thingeecurrent thread http://lists.openstack.org/pipermail/openstack-dev/2016-May/thread.html#9545220:37
* edleafe hands flaper87 a handful20:37
ttxThat said, nobody on the thread did really support my "official scope drives official languages" theory -- and then the discussion on that thread went sideways20:37
* rockyg opens one eye and reaches for edleafe's popcorn20:37
ttxFinally, a "yes but everything that can be done in Python should still be done in Python" option emerged recently20:37
*** dane_leblanc has quit IRC20:37
dhellmannttx: I like the distinction, but that thread got off track so fast I didn't follow up20:38
notmorganso i think adrian otto summed up my vew perfectly: http://lists.openstack.org/pipermail/openstack-dev/2016-May/095827.html20:38
*** jamesmcarthur has joined #openstack-meeting20:38
ttxSo I'd like to take a temperature read (not a vote) to clarify current TC members positions on this before we continue the discussion20:38
mesterydhellmann: ++ to that20:38
ttxTC members, please order the following options in descending order of preference20:38
ttx#1: Yes to golang, without restrictions20:38
annegentleI enjoyed the trip in the five years ago time machine20:38
dhellmannttx: it is extremely unlikely that if we approve the use of golang we could avoid having projects start rewriting things20:38
*** rderose_ has joined #openstack-meeting20:38
ttx#2: Yes to golang, with clear description on where it is appropriate to use it (i.e. when Python can't be used)20:38
*** jamesmcarthur has quit IRC20:38
ttx#3: Components requiring golang should really be developed as OpenStack dependencies, no need to expand the language set now20:38
edleafeannegentle: yeah, I remember the discussion, but missed that meeting20:39
ttx#4: Some other solution: remaining options don't work for me20:39
ttxAt this stage I think I'm 3,2,1,420:39
notmorgan#2, #1, #320:39
dimsttx : i would like to add some guidance on projects that want to pick up go and tell them beware of these things before you go down this road20:39
thingee3, 2, 1, 420:39
flaper87#3 #2 #120:39
notmorganand very strongly prefer #2 to #320:39
dougwigdhellmann: are some of those rewrites good things, or is it all bad?20:39
dims#2 #1 #3 #420:39
mtreinish3,2,1,420:39
annegentleMy preference: 3, 2, 120:40
dhellmanndougwig : the comments I saw made no distinction and were effectively "I'll rewrite everything because I can"20:40
johnthetubaguy2,3,4,120:40
* notmorgan doesn't see 4 as an option.20:40
dhellmann3, 2, 4, 120:40
sdague3,2,1,4 I think, though 2 & 3 are kind of close for me20:40
*** dane_leblanc has joined #openstack-meeting20:40
ttxnotmorgan: #4 is "none of the above"20:40
* dhellmann waits for ttx to apply condorcet rules in his head20:40
mestery#2 #3 #120:40
mtreinishnotmorgan: well #4 is the cause of and solution to all of life's problem20:40
flaper87dhellmann: lol20:40
notmorganttx: hence i don't see it as an option ;)20:40
johnthetubaguy2 and 3 are a very close call for me too, honestly20:40
dimsmtreinish : that's #41 :)20:40
ttxdhellmann: I didn't really expect 3 to be so popular given the silence on that thread20:41
fungidougwig: there's at least one project who suggested they wanted to rewrite a component in go because someone had already done a poc in it so reusing that would be less work than trying to optimize the python code in place20:41
* flaper87 hands johnthetubaguy a coin20:41
*** singhj has quit IRC20:41
*** shaohe_feng has quit IRC20:41
dhellmannttx: every time I started to reply there were another 10 messages to read...20:41
mugsie|mobilefungi: that is a bit of an over simplification20:41
mtreinishdims: nah, it's actually beer :) (it's a simpsons quote)20:41
dims:)20:41
flaper87dhellmann: it took me a good piece of today to catch up20:41
ttxdhellmann: untrue! that thread was pretty calm20:41
sdaguettx: or it's just hard to build up the emotional energy for it20:41
*** shaohe_feng has joined #openstack-meeting20:41
dougwigdhellmann: fungi: wow, i would expect programmer standard laziness to not ditch oslo et al without a good reason.20:42
dhellmannttx: maybe I should be checking email more often20:42
annegentledoes the diff between 3 and 2 then require defining dependency borders?20:42
fungimugsie|mobile: best summary i have, though i'm sure there's more to it for that case20:42
ttxannegentle: #2 is simple, it's just yes with some words added20:42
mugsie|mobileThere is20:42
mtreinishdhellmann: heh, yeah I was in a similar situation on that thread20:42
annegentlethat is, does the difference get into the plugin boundaries also?20:42
notmorganttx: basically (i'll quote adrian): "Openstack projects shall use Python as the preferred programming language. Golang may be used as an alternative if the project leadership decides it is justified."20:42
dhellmanndougwig : I think NIH is trumping laziness in those cases20:42
notmorgansomething like that ^ annegentle20:42
ttxannegentle: #3 is more tricky. We need to explain what "everything where python is not sufficient should really be an openstack dependency" actually means in specific cases20:42
*** factor has joined #openstack-meeting20:42
annegentlenotmorgan the problem with aotto's language though is "what's project leadership" defined as20:43
dougwigdhellmann: won't those types produce lousy python anyway? i'm not sure that's better.20:43
mugsie|mobiledhellmann: not so, in some of them we do not need any olso.* libs20:43
thingeeannegentle: bingo20:43
annegentlettx okay, yeah, that's what I thought.20:43
flaper87annegentle: <320:43
notmorganannegentle: i prefer a change to "demonstrobly needed"20:43
notmorganaka how swift justified it20:43
ttxannegentle: in some cases it's simple (think gnocchi). In others it's complex (think Swift)20:43
annegentlenotmorgan and then that five year history lesson was nice in talking about autonomy20:43
notmorganthat was good.20:43
dimsnotmorgan : demonstrate to who? TC?20:43
dhellmannmugsie|mobile : you're not doing configuration?20:43
jrollnotmorgan: which comes down to #1, right? "project leadership" implies no TC interaction there20:43
dimsthat's why i prefer #220:43
notmorganjroll: it is defining loose bounds20:43
thingeenotmorgan: we're already seeing other projects' leadership jumping on this now.20:44
notmorganjroll: a social and community project20:44
sdaguedhellmann: or logging20:44
notmorgans/project/contract20:44
edleafejroll: exactly. It's open season at that point20:44
ttxdims: I think we can recognize a good technical rationale when we see one. The one posted for Swift explaining that they exhausted their options to solve their issue with Python was pretty compelling20:44
notmorganit's about phrasing.20:44
*** dmowrer has joined #openstack-meeting20:44
notmorganbut that is why i said #2 then #120:44
dimsttx : i mean do projects have to come to TC for a decision?20:44
notmorgandims: please no.20:44
dimsexactly notmorgan20:44
jrollso it's #1 then20:45
mesteryjroll: seems like it20:45
*** gyee has joined #openstack-meeting20:45
jroll(to be clear, I'm personally okay with that)20:45
notmorganjroll: shrug, i disagree, but it's close enough i can't argue further.20:45
dougwigso you want to prevent the SME's that have solid reasons due to the people problems around handling the abusers?20:45
thingeettx: others would argue as we've seen in notmyname's original thread that they've exhausted their options as well, even though some people in the community disagree. This is why I think special casing won't work.20:45
mesterydougwig: I want no such thing.20:45
dhellmannthingee : yeah, there's no way to special case this20:46
notmorganthingee: i believe the teardown was mostly of designate less of swift.20:46
thingeesaying you're going to have the community as oppose to the TC special case these as well is already showing a divide in agreement20:46
dougwig(for the record, i'm not planning to write anything in go.)20:46
notmorganthingee: of the cases that were "exaughsted"20:46
flaper87thingee: ++20:46
ttxso #3 is more popular than #2. But most people aren't ready to fight the emotional battle that #3 means (including figuring out how a #3 would look like)20:46
annegentleI'll be honest, it feels a little like we're giving up on the cross project discipline needed to make OpenStack operable. So if we're resigned to "welp, projects are gonna do what projects gonna do" then #2.20:46
annegentle(that took me a while to type, heh)20:46
thingeenotmorgan: again, how to define when something has been exhausted ... there's already a split in the community from notmyname's original thread.20:46
ttxannegentle: yeah, I can see how #2 is much more.. comfortable20:46
dhellmannannegentle : that's disappointing, but seems true20:46
thingeedetermine*20:46
*** sams-gleb has joined #openstack-meeting20:47
flaper87ttx: I'm ready20:47
anteayaannegentle: I agree with you20:47
notmorgani strongly prefer #2 and #1 to #320:47
anteayaannegentle: I think your observation is accurate and disappointing20:47
mesterynotmorgan: ME too20:47
annegentlenotmorgan what's special casing again?20:47
dtroyer_zzannegentle: yes, because there is a set of questions that many are actively avoiding and #3 hits them head on20:47
thingeeannegentle: swift can, but others can't, for now20:47
dhellmannnotmorgan : how would you define where it's appropriate?20:47
annegentlenotmorgan "only this project is coolkids?"20:47
notmorganannegentle: i'm for a simple phrasing that directs where it should be used, so sure #120:47
ttxso #3 is preferred to #2 but the people who prefer #2 feel more strongly about it20:47
edleafedtroyer_zz: avoidance and/or exhaustion20:48
*** singhj has joined #openstack-meeting20:48
notmorganannegentle: very simple phrasing. the expectation is you will demonstrate it as swift came to the table.20:48
notmorganbut if that means i really mean option #1, then sure, option 120:48
thingeeIf you're concerned about community divide, I think either decision is going to result in that... so we shouldn't use that argument.20:48
jrollnotmorgan: well, the question is who you must demonstrate it to20:48
edleafettx: so what happens when someone doesn't think the "clear description" applies to their case?20:48
jrollnotmorgan: if that is "project leadership" e.g. "ironic core team", I think that means #1. I think #2 means "TC"20:49
mesteryedleafe: Which will happen almost immediatly20:49
edleafes/someone/some project20:49
*** e0ne has quit IRC20:49
ttxSo here is what I propose20:49
notmorgani'd also be ok with saying "and not to replace the wsgi/API layer"20:49
ttxmorgan can champion option #220:49
notmorganttx: sounds to me i'm championing #120:49
notmorganbased on the folks here.20:49
johnthetubaguyjroll: that wasn't my read really, #2 was just there are some guidelines, I thought?20:49
mesterynotmorgan: I think it does too20:49
* dims champion's #2 :)20:49
ttxSomeone (I'll do it if nobody else has the energy for it) can champion option #320:49
sdaguenotmorgan: honestly, I would be much more comfortable with a project that was fully go than half and half20:49
* edleafe would champion #3 if he were on the TC20:50
mugsie|mobileWell, are we not already in #2 if projects have to get TC approval?20:50
notmorganbut lets be fair, i am at the point of "can we stop with this convo, we already have javascript, some java, bash, python, etc"20:50
mugsie|mobileAs the current policy allows for TC allowed exceptions20:50
notmorganand i'm willing to go with "hey infra, is this going to be a problem specifically with our resources and do you have a solid reason not to support go"20:50
thingeemugsie|mobile: that's a question of who would police this. thread has said TC to community.20:50
notmorganfrom that standpoint20:50
annegentlettx I'm not totally sure what tasks it would take to get to #320:50
*** e0ne has joined #openstack-meeting20:50
bswartzwe have java?20:50
dhellmannnotmorgan : and docs, and release, and i18n, and...20:50
notmorganbswartz: some. not a lot.20:51
anteayanotmorgan: I don't think the decision is infra's20:51
sdaguebecause the boundary and skills are very different at that point. I think assuming that you are going to get a bunch of folks that are good at reviewing 2 langs in one tree is odd.20:51
* bswartz blinks20:51
ttxannegentle: right, up to the champion to come up with a description of what his world would look like20:51
anteayainfra's job is to support the decisions the tc makes, not make them20:51
mtreinishsdague: ++20:51
edleafeanteaya: but infra's feedback is majorly important20:51
dimsdhellmann : i spent a few days looking at kubernetes repo20:51
*** shaohe_feng has quit IRC20:51
notmorgananteaya: i am asking if itwould cause an issue with resources.20:51
annegentle#3 is pretty sweeping technically isn't it ttx ?20:51
jrolljohnthetubaguy: I guess I'm trying to understand where morgan is at, but if #2 is "follow these guidelines" it's roughly equivalent to #1 to me (because the real concerns are fragmenting community and such, and I don't think usage boundaries will help that)20:51
notmorgananteaya: after that, i'm willing to accept it.20:51
anteayaedleafe: yes it is, but infra is in the business of how, not what20:51
sdaguettx: I guess that's a #520:51
ttxI thought the temperature read would bury #3, but since it's not buried, we need to investigate how feasiable it would be20:51
*** shaohe_feng has joined #openstack-meeting20:51
anteayanotmorgan: that is a different question, and a fair one for infra20:51
sdague#1 except the whole project has to be in one language20:52
*** dmorita has joined #openstack-meeting20:52
ttxsdague: oh boy, a new one20:52
notmorgananteaya: if there is a real concern aka, we don't have resources, we can't do it because golang is doesn't produce the same results in CI and we need to solve that first"20:52
dimssdague : i can buy that20:52
notmorgananteaya: then we have a hit list that needs to be addressed first20:52
ttxsdague: not sure what that one brings ?20:52
johnthetubaguyjroll: ah, gotcha20:52
bswartzsdague: that's a good idea but it kills horizon doesn't it?20:52
sdagueit brings a much more defined boundary20:52
fungibswartz: "have" java in the sense that there are java-based projects using our infrastructure, running jobs there and publishing/releasing from there20:52
ttxsdague: avoid dual-language core reviewers ?20:52
*** csomerville has joined #openstack-meeting20:52
*** cody-somerville has quit IRC20:52
dougwigif #3, what about all the data plane projects that are currently in python? shouldn't the ideological divide apply there?20:52
notmorgananteaya: and that is what i feel infra has said that it isn't an issue.20:53
*** eharney has quit IRC20:53
anteayanotmorgan: right and as far as I know, notmyname has been working on an etherpad to address these questions20:53
dtroyer_zzbswartz: that particular point keeps getting lost...20:53
dimssdague : do we then say, new project cannot do what swift does?20:53
sdaguein the same way we assume projects interop over REST to each other, we assume that is a language neutral boundary we're all good with20:53
flaper87dougwig: data plane is really the wrong distinction20:53
anteayanotmorgan: it will be work, infra has not said the work is insurmountable, not that I have seen20:53
notmorgananteaya: right and that is where i place my blockers outside of that... i'm for adding/accepting it.20:53
sdaguebecause otherwise we're going to get all these odd internal cross language protocols that are different in every instance20:53
*** JRobinson__ has joined #openstack-meeting20:53
* jroll wonders how the oslo team feels given there could eventually be a flood of oslo libs written in go20:54
dougwigflaper87: ok then, how about !control plane?20:54
*** sams-gleb has quit IRC20:54
anteayanotmorgan: that is fine, as long as we are clear that infra is not left being responsible for more that it is willing to be20:54
dhellmannsdague : does that mean these projects wouldn't emit notifications on the message bus?20:54
edleafesdague: you'll also have two sets of cores for a project20:54
flaper87dougwig: still wrong, you're kicking out glance, basically.20:54
sdaguedhellmann: they'd need an oslo.messaging20:54
notmorgananteaya: nope, i am asking for technical reasons based on our CI and infra that would be the reasons to hold off accepting20:54
*** dimtruck is now known as zz_dimtruck20:54
sdagueand config, log20:54
notmorgananteaya: not "is this a good idea"20:54
notmorgananteaya: we're on the same page.20:54
dougwigflaper87: yeah, i'm highlighting that it's an odd distinction we're drawing.20:54
*** rwsu has quit IRC20:55
*** waynr has left #openstack-meeting20:55
jrollsdague: ++ curious how oslo team feels here20:55
notmorganfor the record. if we make a decision that is kicking a project out, i am against it categorically20:55
anteayanotmorgan: seems we are, yes20:55
notmorganbased upon this topic.20:55
* flaper87 is trying to understand what #5 looks like20:55
*** lpabon has joined #openstack-meeting20:55
dimsharlowja : around?20:55
thingeefive mins left20:55
ttxLast question, I know who feels strongly against #3, who feels strongly against #2 ?20:55
annegentlepartially my sense is that #3 is where reality is sitting for swift, they have the ability to "plugin" and operate some golang code. Maybe I'm wrong though.20:55
*** mbound has joined #openstack-meeting20:55
gordclucky for swift, they don't use oslo. (unless that's changed)20:55
dhellmannjroll : I hope no one is expecting the Oslo team to write those things. Some might, but I don't really know how many are interested.20:55
notmorgani worry #3 leads to dropping swift20:55
notmorganthat is my strongest concern there.20:56
annegentlegordc oh yeah and it's a total pain to scrape their config opt20:56
jrollannegentle: they'd essentially need to move all of swift out of openstack, or ship that piece outside of openstack as a replacement to an in-openstack thing20:56
jrolldhellmann: ++20:56
edleafenotmorgan: but isn't hummingbird more of a plugin for swift?20:56
ttxnotmorgan: would you have some time in the coming week so that we can study this more closely ?20:56
sdaguedhellmann: no, I would expect that to be part of the cost of bringing in a new language environment20:56
notmorganttx: maybe.20:56
mesteryjroll: Right, notmyname said as much last week at the meeting I believe20:56
dimsttx : i'd oppose #320:56
johnthetubaguyI thought the go bit of swift plugged into the python API bit?20:56
jrolledleafe: no, it's a replacement of one "binary" required to run swift20:56
dtroyer_zzsdague: +++20:56
jrollAIUI20:56
edleafenotmorgan: in the same sense as a C library in Python20:56
harlowjadims whats up20:56
ttxdims: noted. Wondering if anyone strongly opposes #220:57
johnthetubaguyjroll: hmm, I thought I checked that last week, and I was told the opposite20:57
thingeettx: I'm against #2 so far ... just because I haven't heard a good "description" of this special casing would happen.20:57
*** ifat_afek has quit IRC20:57
thingeeor who would police it20:57
ttxthingee: noted20:57
dougwigwhy would we keep the python backend for swift in openstack, if the recommended backend by that team is the go version?  just because it's python?20:57
johnthetubaguyjroll: but that was my initial assumption20:57
jrolljohnthetubaguy: I could be wrong, but I'm curious how they're plugging go into python if so20:57
harlowjai don't mind learning go, as long as there are people to help in supporting it (aka, oslo not == go dumping ground, lol)20:57
mesteryRight, the distinction between #1 and #2 is the line we draw, and that will be hard to do20:57
johnthetubaguyjroll: +120:57
*** jamesmcarthur has joined #openstack-meeting20:57
flaper87thingee: ++20:57
sdagueI mostly think the details of #2 are hard to get right20:57
thingeesdague: yes20:58
flaper87sdague: could you summarize #5 in the review ?20:58
notmynamejroll: johnthetubaguy: happy to go over it, but not going to happen in the last 2 minutes20:58
dimsmestery : ttx : #1 is open season, so we can skip that20:58
ttxsdague: #3 is not easier,might even be impossible20:58
johnthetubaguyso I was seeing #2 as a set of guidelines20:58
jrolljohnthetubaguy: sounds like it's the object server rewritten, notmyname correct?20:58
gordcsdague: agreed, same for #3.20:58
redboIt's not an API binding, hummingbird is a web server.20:58
harlowjago already uses the equivalent of oslo.config anyway via flags (The precursor to oslo.config anyway); so there u go :-P20:58
notmorganedleafe: possibly, i worry if you say hummingbird is a plugin, you now have a thing where swift is recommended "don't use the python impl"20:58
flaper87ttx: time check20:58
ttxflaper87: moving to Open discussion onw20:58
ttxnow20:58
johnthetubaguyif #2 means its policed by some central group, I am against it20:58
johnthetubaguyat least I think I am20:58
dimsjohnthetubaguy : #2 is guidlines we publish20:58
dimsIMHO20:59
johnthetubaguydims: right, thats fine20:59
* edleafe admires johnthetubaguy's certainty!20:59
notmorganjohnthetubaguy: i'd just opt out of gating things at that point.20:59
ttxI identified stakeholders for the next step, and will be in touch, trying to make progress with a resolution on this20:59
ttx#topic Open discussion20:59
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:59
ttxLast minute comments on anything else ?20:59
johnthetubaguyedleafe: well, I mean in the context of defining #220:59
notmynameI'm not a fan of the whole "2 gladiators fighting it out for their respective armies" thing (ie champions for some viewpoint that then represent that view to everyone)20:59
ttxnotmyname: oh, that's not what I meant21:00
notmorganuh21:00
notmorgani have last mingute thing21:00
notmorgansec21:00
dimsnotmyname : i think i signed up to propose a change to the review to reflect #2 :)21:00
*** jamesmcarthur has quit IRC21:00
notmorgangothicmindfood wanted to communicate that for the leadership thing, she will be sending an email out to the atendees in the next couple days21:00
notmorganlook for it21:00
edleafejohnthetubaguy: :)21:00
*** mbound has quit IRC21:00
notmynamedims: ack :-)21:00
notmorganwe have a full (20 person) session scheduled.21:00
annegentlecool notmorgan21:00
*** asettle has joined #openstack-meeting21:00
ttxnotmyname: I'm trying to see who cares enough to spend some time on refining what their solution would look like.21:01
notmorganso 24-48hrs there should be an email to the individuals not to the ML21:01
jrollwoot21:01
anteayattx: that was how I interpreted it21:01
* notmorgan is going to lean on notmyname for help on this championing21:01
thingeetime21:01
*** dmorita has quit IRC21:01
notmynamettx: ok21:01
notmorgannotmyname: you're getting volunteered ;)21:01
notmorganhehe21:01
ttxnotmyname: I'll be in touch with you so that you can explain to me the various reasons why #3 is just plain impossible.21:01
*** shaohe_feng has quit IRC21:01
notmynamettx: ok :-)21:01
ttx(like, technically)21:01
*** rcernin has joined #openstack-meeting21:02
ttxalright time is up21:02
*** shaohe_feng has joined #openstack-meeting21:02
ttx#endmeeting21:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:02
openstackMeeting ended Tue May 24 21:02:23 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:02
ttxThanks everyone21:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-05-24-20.01.html21:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-05-24-20.01.txt21:02
*** gordc has left #openstack-meeting21:02
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-05-24-20.01.log.html21:02
*** redbo has left #openstack-meeting21:02
*** sridhar_ram1 has quit IRC21:02
dimsttx : thanks for herding us cats as usual :)21:03
*** _amrith_ is now known as amrith21:03
*** rfolco has quit IRC21:03
*** cdent has left #openstack-meeting21:04
*** sridhar_ram has joined #openstack-meeting21:04
ttxdims: it doesn't get easier with time, or maybe I'm getting old21:04
*** mugsie|mobile has quit IRC21:04
*** mugsie|mobile has joined #openstack-meeting21:04
*** pdardeau has left #openstack-meeting21:04
dims:)21:04
*** Sukhdev has joined #openstack-meeting21:04
*** dmorita has joined #openstack-meeting21:05
*** karthikp_ has joined #openstack-meeting21:05
*** ayoung has joined #openstack-meeting21:05
*** jaypipes has quit IRC21:05
rockygttx, nah, everyone else's fingers are just typing faster21:06
*** jdurgin has quit IRC21:07
*** jdurgin has joined #openstack-meeting21:08
*** mugsie|mobile has quit IRC21:08
*** karthikp_ has quit IRC21:09
*** cloudtrainme has joined #openstack-meeting21:11
*** rwsu has joined #openstack-meeting21:11
*** shaohe_feng has quit IRC21:11
*** rockyg has quit IRC21:12
*** shaohe_feng has joined #openstack-meeting21:12
*** MaxPC has quit IRC21:16
*** lpabon has quit IRC21:18
*** ekcs has joined #openstack-meeting21:18
*** lblanchard has quit IRC21:19
*** amrith is now known as _amrith_21:20
*** vishwanathj has joined #openstack-meeting21:20
*** zz_dimtruck is now known as dimtruck21:21
*** shaohe_feng has quit IRC21:22
*** shaohe_feng has joined #openstack-meeting21:22
*** yamahata has quit IRC21:24
*** torgomatic has left #openstack-meeting21:25
*** baoli has quit IRC21:25
*** baoli has joined #openstack-meeting21:26
*** hashar has quit IRC21:27
*** dimtruck is now known as zz_dimtruck21:29
*** e0ne has quit IRC21:30
*** MaxPC has joined #openstack-meeting21:31
*** lakshmiS has quit IRC21:32
*** shaohe_feng has quit IRC21:32
*** shaohe_feng has joined #openstack-meeting21:33
*** csomerville has quit IRC21:33
*** MaxPC has quit IRC21:34
*** annegentle has quit IRC21:34
*** sdake has joined #openstack-meeting21:34
*** edtubill has quit IRC21:34
*** sgotliv_ has quit IRC21:35
*** julen has quit IRC21:35
*** thorst_ has quit IRC21:37
*** thorst_ has joined #openstack-meeting21:38
*** sdake_ has quit IRC21:38
*** cloudtrainme has quit IRC21:41
*** dneary has quit IRC21:42
*** rtheis has quit IRC21:42
*** shaohe_feng has quit IRC21:42
*** thorst_ has quit IRC21:43
*** shaohe_feng has joined #openstack-meeting21:43
*** henrynash has quit IRC21:43
*** rcernin has quit IRC21:43
*** thorst_ has joined #openstack-meeting21:44
*** karthikp_ has joined #openstack-meeting21:45
*** stevebak` is now known as stevebaker21:46
*** penick_ has joined #openstack-meeting21:46
*** penick has quit IRC21:46
*** penick_ is now known as penick21:46
*** s3wong has joined #openstack-meeting21:48
*** thorst_ has quit IRC21:48
*** thorst_ has joined #openstack-meeting21:50
*** karthikp_ has quit IRC21:50
*** Sukhdev has quit IRC21:50
*** annegentle has joined #openstack-meeting21:50
*** sams-gleb has joined #openstack-meeting21:51
*** shaohe_feng has quit IRC21:52
*** Sukhdev has joined #openstack-meeting21:53
*** dane_leblanc has quit IRC21:53
*** shaohe_feng has joined #openstack-meeting21:53
*** thorst_ has quit IRC21:54
*** baoli has quit IRC21:59
*** baoli has joined #openstack-meeting21:59
*** sams-gleb has quit IRC21:59
*** prometheanfire has left #openstack-meeting22:00
*** penick has joined #openstack-meeting22:01
*** penick has quit IRC22:02
*** shaohe_feng has quit IRC22:03
*** aranjan has quit IRC22:03
*** shaohe_feng has joined #openstack-meeting22:03
*** aranjan has joined #openstack-meeting22:04
*** aranjan has quit IRC22:05
*** aranjan has joined #openstack-meeting22:05
*** timcline has quit IRC22:06
*** penick has joined #openstack-meeting22:07
*** dneary has joined #openstack-meeting22:07
*** asettle has quit IRC22:08
*** darrenc is now known as darrenc_afk22:09
*** sdake has quit IRC22:09
*** cody-somerville has joined #openstack-meeting22:09
*** cody-somerville has quit IRC22:09
*** cody-somerville has joined #openstack-meeting22:09
*** mickeys has joined #openstack-meeting22:09
*** albertom has quit IRC22:10
*** shaohe_feng has quit IRC22:13
*** shaohe_feng has joined #openstack-meeting22:14
*** mickeys has quit IRC22:14
*** thorst_ has joined #openstack-meeting22:15
*** darrenc_afk is now known as darrenc22:16
*** jamesdenton has joined #openstack-meeting22:17
*** sdake has joined #openstack-meeting22:19
*** galstrom is now known as galstrom_zzz22:19
*** albertom has joined #openstack-meeting22:19
*** thorst_ has quit IRC22:19
*** shashank_hegde has quit IRC22:19
*** spzala has quit IRC22:22
*** claudiub has joined #openstack-meeting22:22
*** cdub has quit IRC22:22
*** spzala has joined #openstack-meeting22:22
*** singhj has quit IRC22:23
*** cody-somerville has quit IRC22:23
*** shaohe_feng has quit IRC22:23
*** albertom has quit IRC22:24
*** rossella_s has quit IRC22:24
*** nadeem has quit IRC22:24
*** rossella_s has joined #openstack-meeting22:24
*** sridhar_ram has left #openstack-meeting22:25
*** claudiub|2 has quit IRC22:26
*** shaohe_feng has joined #openstack-meeting22:26
*** dmowrer has quit IRC22:26
*** spotz is now known as spotz_zzz22:26
*** spzala has quit IRC22:27
*** dmowrer has joined #openstack-meeting22:27
*** carolbarrett has quit IRC22:27
*** shashank_hegde has joined #openstack-meeting22:27
*** annegentle has quit IRC22:29
*** dmowrer has quit IRC22:31
*** albertom has joined #openstack-meeting22:31
*** cody-somerville has joined #openstack-meeting22:32
*** shaohe_feng has quit IRC22:33
*** shaohe_feng has joined #openstack-meeting22:34
*** mickeys has joined #openstack-meeting22:35
*** claudiub|2 has joined #openstack-meeting22:36
*** amitgandhinz has quit IRC22:37
*** albertom has quit IRC22:40
*** claudiub has quit IRC22:40
*** SotK has quit IRC22:41
*** rbak has quit IRC22:43
*** singhj has joined #openstack-meeting22:43
*** SotK has joined #openstack-meeting22:43
*** Sukhdev has quit IRC22:43
*** spzala has joined #openstack-meeting22:43
*** shaohe_feng has quit IRC22:44
*** shashank_hegde has quit IRC22:44
*** shaohe_feng has joined #openstack-meeting22:45
*** jckasper has quit IRC22:46
*** singhj has quit IRC22:48
*** shaohe_feng has quit IRC22:54
*** shaohe_feng has joined #openstack-meeting22:55
*** baoli has quit IRC22:55
*** sams-gleb has joined #openstack-meeting22:56
*** yamahata has joined #openstack-meeting22:58
*** absubram has quit IRC22:58
*** Julien-zte has joined #openstack-meeting23:00
*** KrishR has quit IRC23:01
*** vishwanathj has quit IRC23:03
*** shaohe_feng has quit IRC23:04
*** sams-gleb has quit IRC23:05
*** Leom has quit IRC23:05
*** leeantho has joined #openstack-meeting23:05
*** leeantho has quit IRC23:05
*** aranjan_ has joined #openstack-meeting23:05
*** aranjan_ has quit IRC23:05
*** aranjan has quit IRC23:05
*** adiantum has joined #openstack-meeting23:05
*** leeantho has joined #openstack-meeting23:06
*** aranjan has joined #openstack-meeting23:06
*** amakarov_away has quit IRC23:07
*** shaohe_feng has joined #openstack-meeting23:07
*** amakarov_away has joined #openstack-meeting23:07
*** sdague has quit IRC23:09
*** adiantum has quit IRC23:10
*** mickeys has quit IRC23:11
*** markvoelker has quit IRC23:11
*** mickeys has joined #openstack-meeting23:11
*** david-lyle_ is now known as david-lyle23:12
*** shaohe_feng has quit IRC23:14
*** mickeys has quit IRC23:15
*** adahms has joined #openstack-meeting23:16
*** cody-somerville has quit IRC23:17
*** shaohe_feng has joined #openstack-meeting23:18
*** Sukhdev has joined #openstack-meeting23:21
*** shashank_hegde has joined #openstack-meeting23:21
*** asingh has quit IRC23:23
*** mickeys has joined #openstack-meeting23:24
*** mickeys has quit IRC23:24
*** shaohe_feng has quit IRC23:25
*** mickeys has joined #openstack-meeting23:25
*** roxanaghe__ has quit IRC23:25
*** banix has joined #openstack-meeting23:25
*** shaohe_feng has joined #openstack-meeting23:26
*** aranjan has quit IRC23:30
*** jamesmcarthur has joined #openstack-meeting23:30
*** Swami has quit IRC23:31
*** aranjan has joined #openstack-meeting23:31
*** albertom has joined #openstack-meeting23:31
*** aranjan has quit IRC23:31
*** leeantho has quit IRC23:32
*** aranjan has joined #openstack-meeting23:32
*** rderose_ has quit IRC23:32
*** jamesdenton has quit IRC23:33
*** annegentle has joined #openstack-meeting23:35
*** shaohe_feng has quit IRC23:35
*** jamesmcarthur has quit IRC23:35
*** shaohe_feng has joined #openstack-meeting23:36
*** aranjan has quit IRC23:36
*** Qiming has joined #openstack-meeting23:37
*** Julien-zte has quit IRC23:38
*** zqfan has joined #openstack-meeting23:38
*** mickeys has quit IRC23:39
*** Sukhdev has quit IRC23:39
*** jamesmcarthur has joined #openstack-meeting23:40
*** tochi has joined #openstack-meeting23:41
*** shashank_hegde has quit IRC23:42
*** thorst_ has joined #openstack-meeting23:45
*** shaohe_feng has quit IRC23:45
*** jamesmcarthur has quit IRC23:45
*** shaohe_feng has joined #openstack-meeting23:46
*** aranjan has joined #openstack-meeting23:46
*** asingh has joined #openstack-meeting23:46
*** s3wong has quit IRC23:47
*** thorst__ has joined #openstack-meeting23:47
*** yamahata has quit IRC23:48
*** mickeys has joined #openstack-meeting23:48
*** dmacpher-afk has quit IRC23:48
*** Sukhdev has joined #openstack-meeting23:49
*** iyamahat has quit IRC23:49
*** shashank_hegde has joined #openstack-meeting23:49
*** asingh has quit IRC23:50
*** thorst_ has quit IRC23:52
*** adrianofr has quit IRC23:52
*** bobh has quit IRC23:53
*** iyamahat has joined #openstack-meeting23:54
*** manikanta_ has joined #openstack-meeting23:54
*** SumitNaiksatam has quit IRC23:54
*** sdake has quit IRC23:55
*** thorst__ is now known as thorst_23:55
*** shaohe_feng has quit IRC23:55
*** shaohe_feng has joined #openstack-meeting23:56

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