Tuesday, 2014-06-24

*** haomaiw__ has quit IRC00:02
*** stephen-ma has quit IRC00:02
*** kenhui has joined #openstack-meeting00:02
*** vermarah has quit IRC00:04
*** vermarah_ has quit IRC00:04
*** jmontemayor has quit IRC00:04
*** eankutse has quit IRC00:06
*** fawadkhaliq has quit IRC00:07
*** eankutse has joined #openstack-meeting00:09
*** xianghui has joined #openstack-meeting00:09
*** eankutse has quit IRC00:09
*** yisun has quit IRC00:09
*** rmoe has quit IRC00:09
*** crandquist has quit IRC00:09
*** vivek-ebay has quit IRC00:10
*** annegent_ has quit IRC00:10
*** ddieterly has joined #openstack-meeting00:11
*** ddieterly has quit IRC00:12
*** ddieterly has joined #openstack-meeting00:12
*** yamahata has quit IRC00:13
*** Penick has quit IRC00:14
*** lcheng has quit IRC00:14
*** fawadkhaliq has joined #openstack-meeting00:15
*** jackib has quit IRC00:16
*** ddieterly has quit IRC00:17
*** kenhui has quit IRC00:17
*** gokrokve has quit IRC00:17
*** padkrish has quit IRC00:18
*** sankarshan is now known as sankarshan_away00:18
*** jamiem has joined #openstack-meeting00:21
*** matsuhashi has joined #openstack-meeting00:21
*** achanda has quit IRC00:22
*** markmcclain1 has quit IRC00:22
*** nati_ueno has joined #openstack-meeting00:23
*** leeantho has quit IRC00:23
*** rmoe has joined #openstack-meeting00:24
*** achanda has joined #openstack-meeting00:24
*** _nadya_ has quit IRC00:25
*** eghobo has quit IRC00:26
*** ajo|mac_ has quit IRC00:27
*** bdpayne_ has quit IRC00:28
*** marcoemorais has quit IRC00:31
*** carl_baldwin has quit IRC00:32
*** Mandell has quit IRC00:35
*** sweston_ has quit IRC00:36
*** markmcclain has joined #openstack-meeting00:36
*** kayaliu_ has joined #openstack-meeting00:36
*** cjellick has quit IRC00:38
*** mtanino has joined #openstack-meeting00:41
*** sweston_ has joined #openstack-meeting00:42
*** kayaliu_ has quit IRC00:43
*** kayaliu_ has joined #openstack-meeting00:43
*** markmcclain has quit IRC00:43
*** caleb_ has joined #openstack-meeting00:45
*** mattgriffin has joined #openstack-meeting00:45
*** yamamoto has joined #openstack-meeting00:46
*** Mandell has joined #openstack-meeting00:47
*** otter768 has joined #openstack-meeting00:48
*** yingjun has joined #openstack-meeting00:53
*** hrybacki has quit IRC00:54
*** Leonr has quit IRC00:55
*** Rajeev has quit IRC00:55
*** sweston_ has quit IRC00:57
*** dkehn has joined #openstack-meeting00:57
*** yamahata has joined #openstack-meeting00:58
*** haomaiwa_ has joined #openstack-meeting00:59
*** topol has joined #openstack-meeting01:01
*** chuckC has quit IRC01:02
*** Mandell has quit IRC01:04
*** annegent_ has joined #openstack-meeting01:05
*** eghobo has joined #openstack-meeting01:05
*** eghobo has quit IRC01:05
*** eghobo has joined #openstack-meeting01:05
*** beagles is now known as brent01:06
*** sarob has quit IRC01:06
*** ildikov has quit IRC01:06
*** brent is now known as beagles01:06
*** sarob has joined #openstack-meeting01:06
*** bdperkin has quit IRC01:07
*** morganfainberg has quit IRC01:07
*** morganfainberg_Z is now known as morganfainberg01:07
*** ddieterly has joined #openstack-meeting01:08
*** nelsnelson has quit IRC01:09
*** mxu has quit IRC01:09
*** bdpayne has joined #openstack-meeting01:09
*** annegent_ has quit IRC01:10
*** caleb_ has quit IRC01:10
*** crandquist has joined #openstack-meeting01:10
*** yaguang has joined #openstack-meeting01:11
*** sarob has quit IRC01:11
*** ArthurBerezin has joined #openstack-meeting01:11
*** bdperkin has joined #openstack-meeting01:15
*** crandquist has quit IRC01:15
*** fnaval has joined #openstack-meeting01:16
*** mattgriffin has quit IRC01:17
*** ArthurBerezin has left #openstack-meeting01:19
*** lbragstad has joined #openstack-meeting01:20
*** stevemar has joined #openstack-meeting01:22
*** crc32 has quit IRC01:23
*** shakamunyi has joined #openstack-meeting01:24
*** shakamunyi has quit IRC01:24
*** shakamunyi has joined #openstack-meeting01:25
*** mtanino has quit IRC01:28
*** haomaiwa_ has quit IRC01:31
*** jamiem has quit IRC01:34
*** ramashri has quit IRC01:37
*** amcrn has quit IRC01:38
*** Sukhdev has quit IRC01:41
*** songole has quit IRC01:41
*** mberlin1 has joined #openstack-meeting01:42
*** vkmc has joined #openstack-meeting01:43
*** mberlin has quit IRC01:43
*** chuckC has joined #openstack-meeting01:43
*** kenhui has joined #openstack-meeting01:43
*** nosnos has joined #openstack-meeting01:44
*** eguz has joined #openstack-meeting01:46
*** mattoliverau has quit IRC01:48
*** caleb_ has joined #openstack-meeting01:49
*** salv-orlando has quit IRC01:49
*** eghobo has quit IRC01:50
*** eguz has quit IRC01:51
*** baojg has joined #openstack-meeting01:52
*** kenhui has quit IRC01:52
*** mattoliverau has joined #openstack-meeting01:53
*** nati_ueno has quit IRC01:53
*** yingjun has quit IRC01:59
*** yingjun has joined #openstack-meeting01:59
*** Michalik_ has joined #openstack-meeting02:01
*** yingjun has quit IRC02:01
*** xianghui^ has joined #openstack-meeting02:06
*** jackib has joined #openstack-meeting02:08
*** neelashah has joined #openstack-meeting02:09
*** xianghui has quit IRC02:10
*** crandquist has joined #openstack-meeting02:10
*** neelashah1 has joined #openstack-meeting02:12
*** neelashah has quit IRC02:12
*** novas0x2a|laptop has quit IRC02:12
*** baojg has quit IRC02:12
*** VijayB has joined #openstack-meeting02:13
*** esker has joined #openstack-meeting02:14
*** epico has joined #openstack-meeting02:14
*** annegent_ has joined #openstack-meeting02:15
*** crandquist has quit IRC02:15
*** ddieterly has quit IRC02:15
*** Michalik_ has quit IRC02:16
*** nkubota has joined #openstack-meeting02:16
*** sweston_ has joined #openstack-meeting02:16
*** VijayB_ has quit IRC02:17
*** sweston_ has quit IRC02:17
*** VijayB has quit IRC02:18
*** kenhui has joined #openstack-meeting02:18
*** sweston_ has joined #openstack-meeting02:18
*** balajiiyer has joined #openstack-meeting02:18
*** vijendar1 has joined #openstack-meeting02:18
*** vijendar has quit IRC02:21
*** sbalukoff has quit IRC02:21
*** kayaliu__ has joined #openstack-meeting02:25
*** fnaval has quit IRC02:26
*** kayaliu_ has quit IRC02:26
*** amcrn has joined #openstack-meeting02:27
*** epico has quit IRC02:30
*** adalbas has quit IRC02:30
*** mestery has quit IRC02:31
*** mestery has joined #openstack-meeting02:31
*** epico has joined #openstack-meeting02:32
*** baojg has joined #openstack-meeting02:32
*** fnaval has joined #openstack-meeting02:33
*** banix has joined #openstack-meeting02:34
*** sarob has joined #openstack-meeting02:35
*** amcrn has quit IRC02:38
*** kenhui has quit IRC02:40
*** yfujioka has joined #openstack-meeting02:42
*** crandquist has joined #openstack-meeting02:44
*** paragan has joined #openstack-meeting02:45
*** fnaval has quit IRC02:45
*** sweston_ has quit IRC02:48
*** baojg has quit IRC02:48
*** crandquist has quit IRC02:49
*** carl_baldwin has joined #openstack-meeting02:49
*** ddieterly has joined #openstack-meeting02:49
*** Michalik_ has joined #openstack-meeting02:52
*** mestery_ has joined #openstack-meeting02:52
*** nosnos has quit IRC02:54
*** ddieterly has quit IRC02:54
*** nosnos has joined #openstack-meeting02:54
*** mestery has quit IRC02:55
*** kayaliu_ has joined #openstack-meeting02:57
*** kayaliu__ has quit IRC02:57
*** nosnos has quit IRC02:59
*** nosnos has joined #openstack-meeting03:05
*** ramashri has joined #openstack-meeting03:07
*** amcrn has joined #openstack-meeting03:07
*** Michalik_ has quit IRC03:10
*** akuznetsov has joined #openstack-meeting03:11
*** ddieterly has joined #openstack-meeting03:11
*** ramashri has quit IRC03:11
*** jackib has quit IRC03:13
*** dims__ has quit IRC03:13
*** ramashri has joined #openstack-meeting03:14
*** crandquist has joined #openstack-meeting03:15
*** ddieterly has quit IRC03:16
*** matsuhashi has quit IRC03:18
*** matsuhashi has joined #openstack-meeting03:19
*** zhiyan_ is now known as zhiyan03:19
*** sbalukoff has joined #openstack-meeting03:20
*** vkmc has quit IRC03:20
*** hrybacki has joined #openstack-meeting03:20
*** sarob has quit IRC03:22
*** sarob has joined #openstack-meeting03:23
*** matsuhashi has quit IRC03:24
*** fawadkhaliq has quit IRC03:24
*** sarob_ has joined #openstack-meeting03:26
*** baojg has joined #openstack-meeting03:27
*** sarob has quit IRC03:27
*** ramishra has joined #openstack-meeting03:27
*** Michalik_ has joined #openstack-meeting03:28
*** kenhui has joined #openstack-meeting03:29
*** sankarshan_away is now known as sankarshan03:30
*** esker has quit IRC03:32
*** Mandell has joined #openstack-meeting03:34
*** kenhui has quit IRC03:34
*** nosnos has quit IRC03:34
*** nosnos has joined #openstack-meeting03:35
*** fawadkhaliq has joined #openstack-meeting03:35
*** ramishra_ has joined #openstack-meeting03:37
*** eghobo has joined #openstack-meeting03:38
*** ramishra has quit IRC03:38
*** nosnos has quit IRC03:39
*** dims__ has joined #openstack-meeting03:39
*** mattgriffin has joined #openstack-meeting03:40
*** fawadkhaliq has quit IRC03:40
*** lbragstad has quit IRC03:41
*** dims__ has quit IRC03:41
*** shankar has joined #openstack-meeting03:44
*** ivar-lazzaro has quit IRC03:46
*** annegent_ has quit IRC03:47
*** annegent_ has joined #openstack-meeting03:50
*** yaguang has quit IRC03:51
*** annegent_ has quit IRC03:51
*** dpaterson has quit IRC03:53
*** lbragstad has joined #openstack-meeting03:54
*** sarob_ has quit IRC03:54
*** sarob has joined #openstack-meeting03:55
*** banix has quit IRC03:56
*** hrybacki has quit IRC03:57
*** baojg has quit IRC03:59
*** sarob has quit IRC03:59
*** jamespage has quit IRC04:00
*** yamamoto has quit IRC04:00
*** jamespage has joined #openstack-meeting04:00
*** yamamoto has joined #openstack-meeting04:01
*** banix has joined #openstack-meeting04:01
*** GheRivero has quit IRC04:04
*** davidlenwell_ has joined #openstack-meeting04:04
*** GheRivero has joined #openstack-meeting04:04
*** davidlenwell has quit IRC04:05
*** otter768 has quit IRC04:06
*** liusheng is now known as liusheng-leave04:07
*** liusheng-leave is now known as liusheng-afk04:07
*** matsuhashi has joined #openstack-meeting04:10
*** tkay has quit IRC04:11
*** ddieterly has joined #openstack-meeting04:11
*** banix has quit IRC04:13
*** kayaliu_ has quit IRC04:13
*** kayaliu_ has joined #openstack-meeting04:14
*** SridharG has joined #openstack-meeting04:15
*** ddieterly has quit IRC04:16
*** nosnos has joined #openstack-meeting04:19
*** pballand has joined #openstack-meeting04:19
*** ramashri has quit IRC04:21
*** neelashah1 has quit IRC04:21
*** nshaikh has joined #openstack-meeting04:21
*** ildikov has joined #openstack-meeting04:22
*** yaguang has joined #openstack-meeting04:23
*** baojg has joined #openstack-meeting04:24
*** sarob has joined #openstack-meeting04:25
*** yfried_ has quit IRC04:27
*** radez is now known as radez_g0n304:29
*** ngoswami has joined #openstack-meeting04:30
*** sarob has quit IRC04:30
*** ildikov has quit IRC04:32
*** kayaliu_ has quit IRC04:33
*** Michalik_ has quit IRC04:33
*** kayaliu_ has joined #openstack-meeting04:33
*** kayaliu_ has quit IRC04:33
*** kayaliu_ has joined #openstack-meeting04:33
*** Michalik_ has joined #openstack-meeting04:35
*** nshaikh has quit IRC04:38
*** otherwiseguy has quit IRC04:38
*** yamamoto has quit IRC04:39
*** mattgriffin has quit IRC04:39
*** morganfainberg_L has joined #openstack-meeting04:41
*** dims has joined #openstack-meeting04:42
*** gyee has quit IRC04:42
*** yamamoto has joined #openstack-meeting04:42
*** kopparam has joined #openstack-meeting04:42
*** crandquist has quit IRC04:43
*** gokrokve has joined #openstack-meeting04:44
*** shakamunyi has quit IRC04:45
*** nshaikh has joined #openstack-meeting04:46
*** dims has quit IRC04:47
*** natarajk has joined #openstack-meeting04:47
*** natarajk has left #openstack-meeting04:49
*** natarajk has joined #openstack-meeting04:49
*** _nadya_ has joined #openstack-meeting04:50
*** mlavalle has quit IRC04:50
*** hemanthravi has joined #openstack-meeting04:51
*** zz_blogan is now known as blogan04:51
*** pballand has quit IRC04:52
*** _nadya__ has joined #openstack-meeting04:52
*** _nadya_ has quit IRC04:52
*** imsurit has joined #openstack-meeting04:52
*** ngoswami has quit IRC04:52
*** s3wong has joined #openstack-meeting04:55
*** kopparam_ has joined #openstack-meeting04:57
*** nati_ueno has joined #openstack-meeting04:58
*** gongysh has joined #openstack-meeting04:58
*** kopparam has quit IRC04:58
*** pballand has joined #openstack-meeting04:59
yamahatahello05:00
gongyshhi05:00
natarajkhi05:00
*** kenhui has joined #openstack-meeting05:00
*** fawadkhaliq has joined #openstack-meeting05:00
s3wonghello05:00
*** eghobo has quit IRC05:00
*** eghobo has joined #openstack-meeting05:01
yamahataIs there Bob, Balaji?05:01
yamahatagive them minutes05:01
yamahata#startmeeting servicevm-device-manager05:02
openstackMeeting started Tue Jun 24 05:02:06 2014 UTC and is due to finish in 60 minutes.  The chair is yamahata. Information about MeetBot at http://wiki.debian.org/MeetBot.05:02
*** bmelande has joined #openstack-meeting05:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:02
*** openstack changes topic to " (Meeting topic: servicevm-device-manager)"05:02
openstackThe meeting name has been set to 'servicevm_device_manager'05:02
yamahata#link https://wiki.openstack.org/wiki/Meetings/ServiceVM agenda05:02
yamahata#topic announce05:02
*** openstack changes topic to "announce (Meeting topic: servicevm-device-manager)"05:02
yamahatathe repo on stackforge isn't created yet. It's too slow05:03
yamahataSo I create temporal repo until the creation on stackforge05:03
yamahata#link https://github.com/yamahata/tacker-specs for specs05:03
yamahata#link https://github.com/yamahata/tacker05:03
yamahata#link https://github.com/yamahata/python-tackerclient client05:04
yamahatathe main server is still WIP, but I think it's fine for api review05:04
*** kenhui has quit IRC05:04
s3wongyamahata: nice!05:04
yamahataOnce the repo is created, we can move to stackforge05:05
*** armax has quit IRC05:05
yamahatadoes anyone have anything to announce?05:05
natarajkBrocade's DNRM code is available in github now05:05
natarajk  https://github.com/Karthik-Natarajan05:06
natarajkIt can be used in tacker project05:06
gongyshDNRM?05:06
yamahatanatarajk: cool. Now we have 4 independent implementations. We should consolidate somehow05:06
yamahata#link https://github.com/Karthik-Natarajan brocade DNRM05:07
natarajkDynamic Network Resource Management (DNRM)05:07
*** caleb_ has quit IRC05:07
*** xuhanp has joined #openstack-meeting05:07
yamahatanatarajk: do you have any documentation? API documentation?05:07
natarajkI'll add the design docs as well05:07
*** lbragstad has quit IRC05:07
bmelandeCisco implementation with CSr1kv as first VM appliance is here: https://github.com/CiscoSystems/neutron/tree/csr1kv_for_routing_juno05:08
gongyshyamhata: what is the url for reviewing of the code and BP spec?05:08
yamahataI saw the quite old one, https://wiki.openstack.org/w/images/7/71/Dnrm-blueprint-001.pdf it doesn't seem to match the implementation05:08
*** haleyb has quit IRC05:08
yamahata#link  https://wiki.openstack.org/w/images/7/71/Dnrm-blueprint-001.pdf dnrm spec seems too old05:08
*** _nadya__ has quit IRC05:08
s3wongyamahata: with these implementation, what is the plan to consolidate or integrate (in case they are all addressing different aspects of serviceVM)?05:09
natarajkThe supervisor service will maintain a pool of VMs05:09
*** gokrokve_ has joined #openstack-meeting05:09
natarajkIf some parts can be reused, we are happy to help05:09
yamahataI think the plan is implement l3_plugin that talks with servicevm project as PoC.05:09
s3wongyamahata: but what is the scope of serviceVM in tacker?05:10
yamahataThen we can validate that routerVM(cisco, brocade) can be consolidated to tacker.05:10
yamahatas3wong: yes.05:10
yamahataAnd we can also confirm tacker API is enought (at least) rounterVMs.05:11
*** gokrokve has quit IRC05:11
*** ddieterly has joined #openstack-meeting05:11
*** achanda has quit IRC05:11
yamahataAt first cisco/brocade router implementation may/can differ, eventually we should consolidate the implementations somehow.05:12
*** Mandell has quit IRC05:12
yamahataI'm willing to implemente l3 service pluging for PoC.05:12
yamahataCisco and Brocade can work on their implementation in parallel.05:12
s3wongyamahata: so we can try to put L3 plugin to integrate with serviceVM project, then see if Cisco and Brocade router VM implementation can be integrated?05:12
yamahatas3wong: that's what I have in mind. any opinions?05:13
natarajkThat's fine.05:13
bmelandeyamahata: Are you talking about the l3 plugin in Neutron tree?05:13
yamahatabmelande: yes.05:13
yamahataL3 plugin in Neutron that talks to tacker to spin up/down VM05:14
natarajkyamahata: Are the tacker API's ready for review ?05:14
gongyshyamahata:  why not l3 agent?05:14
yamahatanatarajk: not ready for code review. ready for API review.05:14
bmelandeyamahata: Ok. One thing though. I think that plugin needs to be properly modularized.05:14
yamahatagongysh: including l3-agent05:15
bmelandeyamahata: It is not at the moment.05:15
yamahatabmelande: Do you mean l3pluging needs to be refactored for modularity?05:15
*** ddieterly has quit IRC05:16
yamahatal3pluging l3-plugin05:16
bmelandeyamahata: Yes, it really needs that IMHO.05:16
yamahatabmelande: I have same feeling.05:16
s3wongbmelande: is that part of serviceVM project though?05:16
*** haleyb has joined #openstack-meeting05:17
bmelandeyamahata, s3wong: No it is not part of service VM. Just that if we target to add to the existing l3 plugin, it will get even worse.05:17
yamahatas3wong: bmelande Without actual service, servicevm project won't have any value. I think servicevm project needs real example05:18
s3wongyamahata: agreed05:18
*** carl_baldwin has quit IRC05:18
*** ivar-lazzaro has joined #openstack-meeting05:18
*** achanda has joined #openstack-meeting05:19
bmelandeyamahata: That I agree with too. Just wanted to mention that aspect. We don't need to go deeper into that issue here/now.05:19
yamahataSo we have 5 tasks now05:20
yamahata#action natarajk write DNRM API documentation05:20
bmelandeyamahata: I wonder about the service instance etc. Is that stuff really needed in service VM?05:20
yamahata#action tacker api review05:20
*** balajiiyer has left #openstack-meeting05:21
yamahatabmelande: I'll drop it because we haven't reached consensus.05:21
yamahatabmelande: Just template and hosting device05:21
bmelandeyamahata: ok05:21
yamahatathe code is there, but I'll remove it.05:22
yamahata#action yamahata start 3-plugin poc code/blueprint05:22
yamahata#action someone l3-plugin refactoring blueprint/spec/code05:22
yamahataIs there any announcement?05:23
s3wongyamahata: you were saying 5 tasks? you listed 4, what is the last one?05:24
yamahatas3wong: ouch, 4. I can't count numbers.05:24
gongyshyamahata: how to review tacker api? is there gerrit review URL set up?05:24
s3wongyamahata: OK :-)05:24
yamahata#link https://github.com/yamahata/tacker-specs/blob/master/specs/juno/api.rst  api spec05:25
*** VijayB has joined #openstack-meeting05:25
yamahataI'll remove service resource.05:25
yamahataDoes github support commenting or something?05:25
bmelandeyamahata: will the REST API implementation be based on some particular framework?05:25
*** kayaliu_ has quit IRC05:26
yamahataIf no, I'll move it to google-doc.05:26
*** tkay has joined #openstack-meeting05:26
gongyshI don't think github support comment05:26
*** sarob has joined #openstack-meeting05:26
yamahatabmelande: What do you mean by 'some particular framework'?05:26
natarajkyamahata: google-doc is better05:26
*** topol has quit IRC05:26
yamahata#action yamahata move api document google-doc and announce it05:26
*** haomaiwa_ has joined #openstack-meeting05:26
s3wongyamahata: yes, putting it in .rst format but not on gerrit basically negates the reason why it was in .rst in the first place :-)05:27
yamahataNow it's 5 tasks. :-)05:27
*** ildikov has joined #openstack-meeting05:28
yamahatabmelande: I plan to implement tacker based on neutron one. Do you have any preference?05:29
*** pballand has quit IRC05:29
*** Demitar_ has joined #openstack-meeting05:29
bmelandeyamahata: That's fine with me. Just asked given that there's been discussions to migrate Neutron to pecan.05:29
*** amitpp has joined #openstack-meeting05:29
*** SridharG has quit IRC05:30
yamahatabmelande: Yes, that's my concern. Any idea?05:30
yamahataI just use neutron because it is there. No other special reason05:30
bmelandeyamahata: Yes that makes sense to get going fastest.05:31
natarajkyamahata: i think markmcclain was planning to migrate to pecan05:31
natarajkwe can check with him05:31
*** sarob has quit IRC05:31
yamahatayes fastest way for working code. later we can fix it.05:31
yamahata#topic api discussion05:32
*** openstack changes topic to "api discussion (Meeting topic: servicevm-device-manager)"05:32
yamahatawe already discussing on api05:32
*** Demitar has quit IRC05:32
yamahataDo we have anything else on servicevm api/implementation?05:33
*** Demitar_ has quit IRC05:33
*** shakamunyi has joined #openstack-meeting05:33
yamahataOkay let't move on05:33
natarajkyamahata: i wanted to bring up with cross-tenant port attachement issue in nova05:33
natarajkdoes anyone have a solution for it ?05:34
yamahatanatarajk: do you have any links?05:34
natarajki don't have any links. I sent you a e-mail last week on that issue05:35
bmelandenatarajk: There was a recent reveiw out for change to policy05:35
natarajkbmelande: link please05:35
*** coolsvap|afk is now known as coolsvap05:35
*** SridharG has joined #openstack-meeting05:35
bmelandenatarajk: searchign for it...05:36
*** VijayB has quit IRC05:36
bmelandeone sec...05:36
s3wongSpeaking of that, I almost forgot. Last week at the LBaaS mid-cycle, there was some work done on creating a new "advanced service" role (in addition to admin and tenant)05:37
s3wongthe review is here: #link https://review.openstack.org/#/c/10128105:37
bmelandeHere is the review I was mentioneing:https://review.openstack.org/#/c/10128105:37
bmelandes3wong: you were faster. :-)05:37
s3wongbmelande: that's the one :-)05:37
natarajks3wong: thanks05:38
*** shakamunyi has quit IRC05:38
s3wongbmelande: turns out we were talking about the same thing :-)05:38
yamahatacool.05:39
bmelandes3wong: indeed. :-)05:40
*** baojg has quit IRC05:40
yamahata#topic neutron review05:40
*** openstack changes topic to "neutron review (Meeting topic: servicevm-device-manager)"05:40
yamahatawe already covered one05:40
yamahataWe have three specs floating.05:41
*** rwsu has quit IRC05:41
*** tkay has left #openstack-meeting05:41
yamahatal2-gateway/vlan-aware-vm, portsecurity extension and unaddressed port05:41
*** baojg has joined #openstack-meeting05:42
yamahatal2-gateway and unaddressed port needs more review to make progress05:42
s3wongyamahata: aren't those reviews marked as NFV ones?05:42
yamahatas3wong: yes, they are marked as NFV ones.05:42
*** dims has joined #openstack-meeting05:43
bmelandeyamahata: you can add the 101281 to that list.05:43
yamahatabmelande:  Sure. Can you please add it to the wiki page?05:43
bmelandeyamahata: ok05:43
s3wongbmelande: that one is sent out by mestery, don't you dare to give him a -1 :-)05:43
yamahata#action bmelande add 101281 to code review tracking list05:43
*** _nadya_ has joined #openstack-meeting05:44
bmelandes3wong: Yes, let's not go near that one. :-)05:44
natarajkwe can some +1s :)05:44
natarajkwe can give05:45
natarajksome +1s05:45
s3wongnatarajk: :-)05:45
yamahataanything else for review?05:46
yamahata#topic open discussion05:46
*** openstack changes topic to "open discussion (Meeting topic: servicevm-device-manager)"05:46
*** ArthurBerezin has joined #openstack-meeting05:47
s3wongyamahata: the 2 interfaces to same network one is picking up traction as well05:47
yamahatas3wong: agree. link?05:47
s3wong#link https://review.openstack.org/9771605:47
*** dims has quit IRC05:47
yamahata#action s3wong add 97716 to review tracking page05:48
yamahata#action everyone review specs/codes05:48
yamahatas3wong: thanks for the link05:48
yamahatanatarajk: I had a quick look at the code, the concept looks quite different from servicevm. Could you please explain a bit here?05:49
yamahataespecially what does resource mean and it's action.05:49
natarajkyamahata: every VM is a resource05:49
natarajkResource manager will maintain the pool of VMs05:49
*** _nadya_ has quit IRC05:50
natarajkl3 plugin will talk to the resource manager service to get the list of VMs05:50
natarajkscheduler will allocate the VM satisfying the policy05:50
*** morganfainberg_L has quit IRC05:51
yamahatanatarajk: I see.05:51
*** vivek-ebay has joined #openstack-meeting05:51
*** ivar-lazzaro has quit IRC05:51
natarajki'll also send out the design doc for DNRM05:51
yamahatanatarajk: Yes, please. Then we can make discuss on it.05:52
natarajkhttps://docs.google.com/document/d/1_A2UJDGngzkicY3Zx95TgXg5Fu6wn5ZL_Gx2zJt4m18/edit?pli=105:52
natarajkCan you access it ?05:52
yamahatanatarajk: I also looked at neutron and code. But they have only master branch. It is difficult to get diff from plain neutron/nova05:52
s3wongnatarajk: the doc is a Mirantis doc?05:52
*** kopparam_ has quit IRC05:53
yamahatanatarajk: I'm seeing mirantis doc05:53
natarajkBrocade used Mirantis consultants05:53
*** sweston_ has joined #openstack-meeting05:53
yamahatanatarajk: can you please add the link to the wiki page?05:53
s3wongnatarajk: from your description, it is a service VM pool manager?05:53
natarajkYamahata: Yes, that's correct05:54
yamahata#action natarajk add dnrm page to the wiki05:54
*** ihrachyshka has joined #openstack-meeting05:54
bmelandenatarajk: The scheduler is not part of resource manager, right?05:54
natarajkyamahata: Correct. It's part of Neutron05:54
*** Michalik_ has quit IRC05:55
natarajkyamahata: But we had a very simple scheduler to start with05:55
*** ihrachyshka has quit IRC05:55
*** sirushti has joined #openstack-meeting05:56
*** sirushti has left #openstack-meeting05:56
*** kopparam has joined #openstack-meeting05:56
yamahatanatarajk: thanks for explanation.05:57
yamahataanything else to discuss?05:57
natarajkyamahata: Welcome. DNRM's Neutron/Nova code is based on havana. Resource manager can be reused now05:57
*** vivek-ebay has quit IRC05:57
yamahataOkay let's meet next week. (or on nfv meeting)05:58
yamahata#endmeeting05:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:58
openstackMeeting ended Tue Jun 24 05:58:26 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:58
s3wongcool, finished 2 minutes early!05:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-06-24-05.02.html05:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-06-24-05.02.txt05:58
openstackLog:            http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-06-24-05.02.log.html05:58
s3wongThanks, guys!05:58
yamahatathanks05:58
bmelandeyamahata, natarajk: Cisco also has a device resource manager, along with scheduler05:58
*** sirushti has joined #openstack-meeting05:59
s3wongbmelande: is that part of your device manager?05:59
*** sirushti has left #openstack-meeting05:59
yamahatabmelande: Do you mean https://review.openstack.org/92004 ?05:59
bmelandeThe scheduler is separate from device manager05:59
*** haomaiwa_ has quit IRC06:00
bmelandeYou can find an illustration of the relationssghips in this BP:06:00
bmelandehttps://review.openstack.org/#/c/91071/06:00
bmelandeSorry, wrong link06:01
bmelandeHere is the correct one: https://review.openstack.org/#/c/91645/06:01
*** Longgeek has joined #openstack-meeting06:01
*** yisun_ has joined #openstack-meeting06:02
*** Longgeek has quit IRC06:02
bmelandeyamahata: The 92004 is the router scheduler that is able to scheduler neutron routers to l3 agents (for namespace-based Neutron routers) or to service VMs06:03
*** Longgeek has joined #openstack-meeting06:03
yamahatabmelande: I see. I'll re-review your specs/codes.06:04
*** fawadkhaliq has quit IRC06:04
bmelandeyamahata: The juno code branch I linked to is in sync with the device manager BP06:04
bmelandeyamahata: and scheduler BPs06:05
*** comay has quit IRC06:06
*** doron_afk has joined #openstack-meeting06:06
*** ArthurBerezin has left #openstack-meeting06:06
*** gokrokve_ has quit IRC06:08
*** brucer_ has quit IRC06:10
*** liusheng-afk is now known as liusheng06:10
*** ddieterly has joined #openstack-meeting06:11
*** evgenyf has joined #openstack-meeting06:12
*** kayaliu_ has joined #openstack-meeting06:13
*** mrmartin has joined #openstack-meeting06:14
*** mrmartin has quit IRC06:15
*** sweston_ has quit IRC06:15
*** ddieterly has quit IRC06:16
*** ddieterly has joined #openstack-meeting06:16
*** bmelande has quit IRC06:19
*** lcheng has joined #openstack-meeting06:20
*** harlowja is now known as harlowja_away06:20
*** ddieterly has quit IRC06:21
*** natarajk has quit IRC06:23
*** coolsvap is now known as coolsvap|afk06:24
*** kayaliu_ has quit IRC06:25
*** stevemar has quit IRC06:25
*** kayaliu_ has joined #openstack-meeting06:25
*** sarob has joined #openstack-meeting06:26
*** mrunge has joined #openstack-meeting06:28
*** Michalik_ has joined #openstack-meeting06:28
*** coolsvap|afk is now known as coolsvap06:28
*** s3wong has quit IRC06:29
*** sarob has quit IRC06:31
*** markwash has joined #openstack-meeting06:33
*** Michalik_ has quit IRC06:33
*** shakamunyi has joined #openstack-meeting06:34
*** slong has quit IRC06:34
*** shakamunyi has quit IRC06:38
*** lcheng has quit IRC06:39
*** blogan is now known as zz_blogan06:41
*** dims has joined #openstack-meeting06:43
*** Macaveli has joined #openstack-meeting06:44
*** ramishra_ has quit IRC06:44
*** ramishra has joined #openstack-meeting06:46
*** dims has quit IRC06:48
*** Fdot has joined #openstack-meeting06:49
*** bauzas has joined #openstack-meeting06:54
*** bauzas has quit IRC06:56
*** bauzas has joined #openstack-meeting06:56
*** sarob has joined #openstack-meeting06:56
*** eguz has joined #openstack-meeting06:59
*** sarob has quit IRC07:01
*** nshaikh has quit IRC07:01
*** bdpayne has quit IRC07:02
*** amcrn has quit IRC07:02
*** yfujioka has quit IRC07:03
*** eghobo has quit IRC07:03
*** marekd|away is now known as marekd07:04
*** yamamoto has quit IRC07:05
*** eguz has quit IRC07:05
*** ivar-lazzaro has joined #openstack-meeting07:08
*** imsurit has quit IRC07:10
*** mrmartin has joined #openstack-meeting07:11
*** ArthurBerezin has joined #openstack-meeting07:13
*** nati_ueno has quit IRC07:15
*** ttrifonov_zZzz is now known as ttrifonov07:16
*** julienvey has joined #openstack-meeting07:16
*** afazekas is now known as __afazekas07:17
*** gokrokve has joined #openstack-meeting07:19
*** ArthurBerezin has left #openstack-meeting07:19
*** jcoufal has joined #openstack-meeting07:21
*** tnurlygayanov has quit IRC07:22
*** asettle has quit IRC07:23
*** moha_hunt has joined #openstack-meeting07:23
*** tnurlygayanov has joined #openstack-meeting07:23
*** gokrokve has quit IRC07:23
*** asettle has joined #openstack-meeting07:24
*** kopparam has quit IRC07:25
*** salv-orlando has joined #openstack-meeting07:26
*** sarob has joined #openstack-meeting07:26
*** gongysh has quit IRC07:27
*** gongysh has joined #openstack-meeting07:28
*** sarob_ has joined #openstack-meeting07:28
*** bgorski has joined #openstack-meeting07:28
*** SridharG has quit IRC07:29
*** rm_work has quit IRC07:29
*** Michalik_ has joined #openstack-meeting07:29
*** SridharG has joined #openstack-meeting07:29
*** sarob has quit IRC07:31
*** ilyashakhat has quit IRC07:31
*** beekneemech has joined #openstack-meeting07:32
*** bnemec has quit IRC07:32
*** rm_work has joined #openstack-meeting07:32
*** ilyashakhat has joined #openstack-meeting07:33
*** sarob_ has quit IRC07:33
*** Michalik_ has quit IRC07:34
*** hashar has joined #openstack-meeting07:34
*** kayaliu_ has quit IRC07:34
*** shakamunyi has joined #openstack-meeting07:34
*** mrmartin has quit IRC07:38
*** shakamunyi has quit IRC07:39
*** andreaf has joined #openstack-meeting07:39
*** achanda has quit IRC07:40
*** mrda is now known as mrda-away07:40
*** yamamoto has joined #openstack-meeting07:41
*** nacim has joined #openstack-meeting07:41
*** shankar has quit IRC07:43
*** dims_ has joined #openstack-meeting07:44
*** ihrachyshka has joined #openstack-meeting07:45
*** jtomasek has joined #openstack-meeting07:45
*** afazekas has joined #openstack-meeting07:46
*** dims_ has quit IRC07:49
*** kayaliu_ has joined #openstack-meeting07:51
*** kopparam has joined #openstack-meeting07:56
*** belmoreira has joined #openstack-meeting07:58
*** otherwiseguy has joined #openstack-meeting08:01
*** ygbo has joined #openstack-meeting08:02
*** safchain has joined #openstack-meeting08:04
*** otherwiseguy has quit IRC08:05
*** phil__ has joined #openstack-meeting08:06
*** nacim has quit IRC08:09
*** amitpp has quit IRC08:12
*** Mandell has joined #openstack-meeting08:13
*** kopparam has quit IRC08:15
*** kopparam has joined #openstack-meeting08:15
*** Mandell has quit IRC08:18
*** kopparam has quit IRC08:20
*** kopparam has joined #openstack-meeting08:22
*** nacim has joined #openstack-meeting08:24
*** lcheng has joined #openstack-meeting08:26
*** sarob has joined #openstack-meeting08:26
*** nacim has quit IRC08:28
*** ivar-lazzaro has quit IRC08:29
*** bogdando has quit IRC08:29
*** Michalik_ has joined #openstack-meeting08:30
*** ramishra has quit IRC08:30
*** sarob has quit IRC08:31
*** ramishra has joined #openstack-meeting08:32
*** vjay2 has joined #openstack-meeting08:32
*** bogdando has joined #openstack-meeting08:32
*** nshaikh has joined #openstack-meeting08:33
*** jcoufal has quit IRC08:33
*** jcoufal has joined #openstack-meeting08:34
*** MaxV has joined #openstack-meeting08:34
*** Michalik_ has quit IRC08:34
*** shakamunyi has joined #openstack-meeting08:35
*** tylerdurden has joined #openstack-meeting08:37
*** shakamunyi has quit IRC08:37
*** jlibosva has joined #openstack-meeting08:37
*** ominakov has joined #openstack-meeting08:38
*** dguitarbite has quit IRC08:38
*** ramishra has quit IRC08:38
*** nacim has joined #openstack-meeting08:41
*** Mandell has joined #openstack-meeting08:42
*** tylerdurden has quit IRC08:42
*** isviridov|away is now known as isviridov08:45
*** dims_ has joined #openstack-meeting08:45
*** Mandell has quit IRC08:46
*** ygbo has quit IRC08:46
*** ygbo has joined #openstack-meeting08:46
*** salv-orlando_ has joined #openstack-meeting08:47
*** salv-orlando_ has quit IRC08:48
*** salv-orlando_ has joined #openstack-meeting08:48
*** salv-orlando has quit IRC08:49
*** salv-orlando_ is now known as salv-orlando08:49
*** Mandell has joined #openstack-meeting08:49
*** dims_ has quit IRC08:50
*** shankar has joined #openstack-meeting08:52
*** _nadya_ has joined #openstack-meeting08:52
*** Mandell has quit IRC08:54
*** hashar has quit IRC08:55
*** _nadya_ has quit IRC08:57
*** _nadya_ has joined #openstack-meeting09:00
*** ArthurBerezin1 has joined #openstack-meeting09:03
*** kopparam has quit IRC09:03
*** ArthurBerezin1 has left #openstack-meeting09:04
*** Mandell has joined #openstack-meeting09:04
*** kopparam has joined #openstack-meeting09:07
*** Mandell has quit IRC09:09
*** ihrachyshka has quit IRC09:10
*** xuhanp has quit IRC09:10
*** xuhanp has joined #openstack-meeting09:11
*** Mandell has joined #openstack-meeting09:11
*** dguitarbite has joined #openstack-meeting09:13
*** Mandell has quit IRC09:15
*** Mandell has joined #openstack-meeting09:16
*** pelix has joined #openstack-meeting09:16
*** ArthurBerezin has joined #openstack-meeting09:20
*** evgenyf has quit IRC09:20
*** Mandell has quit IRC09:20
*** sankarshan is now known as sankarshan_away09:21
*** ramishra has joined #openstack-meeting09:23
*** ArthurBerezin has quit IRC09:24
*** kayaliu_ has quit IRC09:26
*** kayaliu_ has joined #openstack-meeting09:26
*** sarob has joined #openstack-meeting09:26
*** ramishra has quit IRC09:28
*** zhiyan is now known as zhiyan_09:28
*** baojg_ has joined #openstack-meeting09:29
*** baojg has quit IRC09:30
*** Mandell has joined #openstack-meeting09:30
*** sushils_ has joined #openstack-meeting09:30
*** Michalik_ has joined #openstack-meeting09:31
*** sarob has quit IRC09:31
*** kopparam has quit IRC09:33
*** Mandell has quit IRC09:34
*** Michalik_ has quit IRC09:35
*** enikanorov_ has quit IRC09:37
*** shakamunyi has joined #openstack-meeting09:38
*** enikanorov_ has joined #openstack-meeting09:38
*** ArthurBerezin has joined #openstack-meeting09:38
*** liusheng has quit IRC09:40
*** liusheng has joined #openstack-meeting09:40
*** amitpp has joined #openstack-meeting09:41
*** shakamunyi has quit IRC09:42
*** ArthurBerezin has left #openstack-meeting09:44
*** evgenyf has joined #openstack-meeting09:44
*** Longgeek has quit IRC09:45
*** Longgeek has joined #openstack-meeting09:45
*** dims_ has joined #openstack-meeting09:46
*** SridharG has quit IRC09:46
*** Longgeek has quit IRC09:46
*** Longgeek has joined #openstack-meeting09:47
*** dims_ has quit IRC09:51
*** SridharG has joined #openstack-meeting09:51
*** rajeshr has joined #openstack-meeting09:51
*** Longgeek has quit IRC09:52
*** Longgeek has joined #openstack-meeting09:53
*** xuhanp has quit IRC09:57
*** lcheng has quit IRC10:04
*** dguitarbite has quit IRC10:05
*** Mandell has joined #openstack-meeting10:06
*** ihrachyshka has joined #openstack-meeting10:06
*** Mandell has quit IRC10:10
*** Mandell has joined #openstack-meeting10:14
*** kopparam has joined #openstack-meeting10:14
*** sankarshan_away is now known as sankarshan10:16
*** asselin has quit IRC10:17
*** nosnos has quit IRC10:19
*** Mandell has quit IRC10:19
*** nosnos has joined #openstack-meeting10:19
*** matsuhashi has quit IRC10:23
*** matsuhashi has joined #openstack-meeting10:24
*** nosnos has quit IRC10:24
*** amitpp has quit IRC10:24
*** HenryG has quit IRC10:25
*** sarob has joined #openstack-meeting10:26
*** matsuhashi has quit IRC10:28
*** alexpilotti has joined #openstack-meeting10:28
*** sarob has quit IRC10:31
*** Michalik_ has joined #openstack-meeting10:31
*** paragan has quit IRC10:34
*** Mandell has joined #openstack-meeting10:35
*** Michalik_ has quit IRC10:36
*** shakamunyi has joined #openstack-meeting10:38
*** Mandell has quit IRC10:39
*** Mandell has joined #openstack-meeting10:39
*** ihrachyshka has quit IRC10:41
*** shakamunyi has quit IRC10:43
*** yaguang has quit IRC10:44
*** Mandell has quit IRC10:44
*** kayaliu_ has quit IRC10:46
*** dims_ has joined #openstack-meeting10:46
*** kayaliu_ has joined #openstack-meeting10:47
*** Mandell has joined #openstack-meeting10:47
*** salv-orlando has quit IRC10:48
*** sorantis has joined #openstack-meeting10:48
*** lcheng has joined #openstack-meeting10:51
*** Mandell has quit IRC10:51
*** gongysh has quit IRC10:53
*** ngoswami has joined #openstack-meeting10:54
*** haomaiwa_ has joined #openstack-meeting10:54
*** Mandell has joined #openstack-meeting10:54
*** epico has quit IRC10:57
*** Mandell has quit IRC10:59
*** kayaliu_ has quit IRC11:02
*** ArthurBerezin1 has joined #openstack-meeting11:03
*** Longgeek has quit IRC11:03
*** enykeev has quit IRC11:05
*** aloga has quit IRC11:05
*** lcheng has quit IRC11:06
*** aloga has joined #openstack-meeting11:06
*** lcheng has joined #openstack-meeting11:07
*** alexpilotti has quit IRC11:09
*** oanufriev has joined #openstack-meeting11:13
*** SridharG has quit IRC11:15
*** Longgeek has joined #openstack-meeting11:18
*** yamahata has quit IRC11:18
*** MaxV has quit IRC11:19
*** _nadya_ has quit IRC11:20
*** lcheng has quit IRC11:22
*** sorantis has quit IRC11:22
*** lcheng has joined #openstack-meeting11:23
*** ArthurBerezin1 has left #openstack-meeting11:26
*** sarob has joined #openstack-meeting11:26
*** coolsvap is now known as coolsvap|afk11:27
*** jprovazn has joined #openstack-meeting11:31
*** BrianB__ has quit IRC11:31
*** sarob has quit IRC11:31
*** Michalik_ has joined #openstack-meeting11:32
*** MaxV has joined #openstack-meeting11:35
*** rajeshr has quit IRC11:36
*** Michalik_ has quit IRC11:37
*** Longgeek has quit IRC11:38
*** Longgeek has joined #openstack-meeting11:38
*** haomaiwa_ has quit IRC11:38
*** shakamunyi has joined #openstack-meeting11:39
*** Longgeek_ has joined #openstack-meeting11:39
*** salv-orlando has joined #openstack-meeting11:39
*** vkmc has joined #openstack-meeting11:43
*** vkmc has quit IRC11:43
*** vkmc has joined #openstack-meeting11:43
*** Longgeek has quit IRC11:43
*** shakamunyi has quit IRC11:44
*** banix has joined #openstack-meeting11:45
*** banix_ has joined #openstack-meeting11:45
*** kopparam has quit IRC11:46
*** kopparam has joined #openstack-meeting11:47
*** vjay2 has quit IRC11:49
*** ddieterly has joined #openstack-meeting11:50
*** kopparam has quit IRC11:51
*** nkubota has quit IRC11:53
*** igordcard has joined #openstack-meeting11:53
*** jackib has joined #openstack-meeting11:55
*** vjay2 has joined #openstack-meeting11:55
*** markvoelker1 has joined #openstack-meeting11:56
*** weshay has joined #openstack-meeting11:57
*** banix has quit IRC11:58
*** banix_ is now known as banix11:58
*** ramishra has joined #openstack-meeting11:59
*** jdob has joined #openstack-meeting12:01
*** vjay2 has quit IRC12:02
*** dkranz has joined #openstack-meeting12:03
*** nacim has quit IRC12:05
*** shankar has quit IRC12:10
*** jamiem has joined #openstack-meeting12:13
*** ArthurBerezin has joined #openstack-meeting12:14
*** banix has quit IRC12:15
*** yamamoto has quit IRC12:16
*** baojg_ has quit IRC12:16
*** ddieterly has quit IRC12:16
*** baojg has joined #openstack-meeting12:16
*** baojg has quit IRC12:17
*** kopparam has joined #openstack-meeting12:17
*** baojg has joined #openstack-meeting12:17
*** dprince has joined #openstack-meeting12:19
*** shakamunyi has joined #openstack-meeting12:20
*** nacim has joined #openstack-meeting12:21
*** tylerdurden has joined #openstack-meeting12:22
*** kopparam has quit IRC12:22
*** stevemar has joined #openstack-meeting12:22
*** baojg has quit IRC12:22
*** xuhanp has joined #openstack-meeting12:23
*** dguitarbite has joined #openstack-meeting12:24
*** yaguang has joined #openstack-meeting12:25
*** xuhanp has quit IRC12:25
*** shakamunyi has quit IRC12:25
*** doron_afk is now known as doron12:25
*** kopparam has joined #openstack-meeting12:26
*** sarob has joined #openstack-meeting12:26
*** tylerdurden has quit IRC12:26
*** xuhanp has joined #openstack-meeting12:28
*** jamiem has quit IRC12:30
*** sarob has quit IRC12:31
*** yaguang has quit IRC12:31
*** adalbas has joined #openstack-meeting12:32
*** jamiem has joined #openstack-meeting12:32
*** Michalik_ has joined #openstack-meeting12:33
*** jackib has quit IRC12:33
*** edmund1 has joined #openstack-meeting12:36
*** jackib has joined #openstack-meeting12:36
*** Michalik_ has quit IRC12:37
*** jamiem has quit IRC12:38
*** jaypipes has quit IRC12:41
*** jaypipes has joined #openstack-meeting12:43
*** yaguang has joined #openstack-meeting12:44
*** mwagner_lap has quit IRC12:45
*** changbl has quit IRC12:45
*** hrybacki has joined #openstack-meeting12:49
*** baoli has joined #openstack-meeting12:52
*** balajiiyer has joined #openstack-meeting12:53
*** flaper87|afk is now known as flaper8712:54
*** vjay2 has joined #openstack-meeting12:54
*** banix has joined #openstack-meeting12:56
*** balajiiyer has quit IRC12:56
*** oomichi has quit IRC12:57
*** julim has joined #openstack-meeting12:59
*** ddieterly has joined #openstack-meeting12:59
*** doron is now known as doron_afk13:01
*** hemanthravi has quit IRC13:03
*** yaguang has quit IRC13:03
*** Michalik_ has joined #openstack-meeting13:05
*** baojg has joined #openstack-meeting13:06
*** gholt has quit IRC13:07
*** bauzas has quit IRC13:09
*** zhangleiqiang has joined #openstack-meeting13:09
*** gholt has joined #openstack-meeting13:09
*** nacim has quit IRC13:11
*** cerndev has joined #openstack-meeting13:12
*** andreaf has quit IRC13:13
*** dims_ has quit IRC13:13
*** dims_ has joined #openstack-meeting13:14
*** SridharG has joined #openstack-meeting13:14
*** bklei has joined #openstack-meeting13:15
*** temujin has joined #openstack-meeting13:15
*** neelashah has joined #openstack-meeting13:15
cerndevhi13:16
*** cerndev is now known as sajeesh13:16
*** bknudson has joined #openstack-meeting13:17
sajeeshtesting13:17
*** yaguang has joined #openstack-meeting13:18
*** hemanthravi has joined #openstack-meeting13:19
*** kopparam has quit IRC13:21
*** nelsnelson has joined #openstack-meeting13:21
*** Longgeek has joined #openstack-meeting13:21
*** Longgeek_ has quit IRC13:22
*** shakamunyi has joined #openstack-meeting13:22
*** radez_g0n3 is now known as radez13:23
*** bauzas has joined #openstack-meeting13:26
*** sarob has joined #openstack-meeting13:26
*** mattgriffin has joined #openstack-meeting13:27
*** shakamunyi has quit IRC13:27
*** nacim has joined #openstack-meeting13:28
*** annegent_ has joined #openstack-meeting13:30
*** sarob has quit IRC13:31
*** tbarron has joined #openstack-meeting13:33
*** SridharG has quit IRC13:33
*** ArthurBerezin has left #openstack-meeting13:35
*** vjay2 has quit IRC13:35
*** lbragstad has joined #openstack-meeting13:37
*** ramishra has quit IRC13:38
*** vjay2 has joined #openstack-meeting13:38
*** banix has quit IRC13:39
*** ramishra has joined #openstack-meeting13:39
*** ramishra has quit IRC13:39
*** ramishra has joined #openstack-meeting13:39
*** balajiiyer has joined #openstack-meeting13:39
*** jecarey has quit IRC13:41
*** mestery_ is now known as mestery13:42
*** pdmars has joined #openstack-meeting13:43
*** _nadya_ has joined #openstack-meeting13:45
*** pdmars has quit IRC13:45
*** pdmars has joined #openstack-meeting13:45
*** SridharG has joined #openstack-meeting13:46
*** vivek-ebay has joined #openstack-meeting13:47
*** jasondotstar has joined #openstack-meeting13:47
*** kevinconway has joined #openstack-meeting13:49
*** yaguang has quit IRC13:50
*** carlp has joined #openstack-meeting13:51
*** hashar has joined #openstack-meeting13:52
*** kevinconway has quit IRC13:53
*** thangp has joined #openstack-meeting13:54
*** Shixiong has joined #openstack-meeting13:55
*** jackmccann has quit IRC13:56
sc68calHello everyone13:59
*** shakamunyi has joined #openstack-meeting13:59
*** aveiga has joined #openstack-meeting13:59
*** shakamunyi has quit IRC13:59
xuhanphello13:59
*** whenry has joined #openstack-meeting13:59
carlpsc68cal: morning13:59
aveigao/13:59
sc68cal#startmeeting neutron_ipv613:59
openstackMeeting started Tue Jun 24 13:59:48 2014 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.13:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:59
*** openstack changes topic to " (Meeting topic: neutron_ipv6)"13:59
openstackThe meeting name has been set to 'neutron_ipv6'13:59
sc68cal#topic blueprints14:00
*** openstack changes topic to "blueprints (Meeting topic: neutron_ipv6)"14:00
*** esker has joined #openstack-meeting14:00
*** annegent_ has quit IRC14:01
*** gokrokve has joined #openstack-meeting14:01
*** BrianB__ has joined #openstack-meeting14:01
*** armax has joined #openstack-meeting14:01
*** dane_leblanc has joined #openstack-meeting14:01
sc68calHere's what's scheduled for J-214:01
sc68calhttps://launchpad.net/neutron/+milestone/juno-214:01
*** flaper87 is now known as flaper87|afk14:01
*** eankutse has joined #openstack-meeting14:02
*** eankutse has quit IRC14:02
*** hrybacki has left #openstack-meeting14:02
*** rbak has joined #openstack-meeting14:02
*** eankutse has joined #openstack-meeting14:02
*** yaguang has joined #openstack-meeting14:02
sc68calIt looks like we need to have that updated, to reflect what we are currently working on14:03
*** bklei has quit IRC14:03
*** paragan has joined #openstack-meeting14:03
*** paragan has quit IRC14:03
*** paragan has joined #openstack-meeting14:03
*** topol has joined #openstack-meeting14:04
*** HenryG has joined #openstack-meeting14:04
*** beekneemech is now known as bnemec14:04
HenryGSorry I am late14:05
*** salv-orlando has quit IRC14:05
sc68calDo we have any new blueprints to discuss?14:05
BrianB__It's missing a few BP14:05
xuhanpsc68cal, I've update the SLAAC spec to stateful/stateless14:05
xuhanphttps://review.openstack.org/#/c/99595/14:05
xuhanpit still has Mark's -2 on it.14:06
*** yamamoto has joined #openstack-meeting14:07
xuhanpAnd I am not sure if we should set this stateful/stateless spec be dependent on the RADVD spec14:07
*** yamamoto has quit IRC14:07
sc68calxuhanp: it may be worth abandoning that review and creating another14:07
xuhanpsc68cal, that may work :-)14:08
sc68calsince that review was originally targeted to slaac/slaac and the -2 from mark is significant, since they wanted us to not have dnsmasq advertise routes14:08
sc68caland work on radvd instead14:08
*** Shixiong_ has joined #openstack-meeting14:08
sc68calthat may be useful for historical purposes14:08
aveigaxuhanp: dnsmasq shouldn't be dependant on radvd14:09
xuhanpsc68cal, ok that makes sense. I've already got some comments. will see what I can do.14:09
sc68calBrianB__: do you know which BPs are missing?14:09
aveigajust make the dependancy "assuming an RA is present" since provider nets can do RAs too14:09
xuhanpaveiga, that's what I thought.14:09
*** matiu has quit IRC14:10
xuhanpaveiga, ok. will modify that.14:10
*** tsekiyama has joined #openstack-meeting14:11
dane_leblancsc68cal: I don't see RADVD and the multi prefix in the J2 blueprint list14:11
aveigadane_leblanc: the RADVD is still pending +214:11
sc68calhmm yeah https://blueprints.launchpad.net/neutron/+spec/neutron-ipv6-radvd-ra has no series goal14:12
*** ajo|mac has joined #openstack-meeting14:12
*** kenhui has joined #openstack-meeting14:12
*** mwagner_lap has joined #openstack-meeting14:12
*** edmund1 has quit IRC14:12
sc68cal#action sc68cal get https://blueprints.launchpad.net/neutron/+spec/neutron-ipv6-radvd-ra set to the correct Juno milestone14:13
*** shakamunyi has joined #openstack-meeting14:13
*** vivek-ebay has quit IRC14:13
*** nkubota has joined #openstack-meeting14:14
sc68calOK - do we have anything else to discuss in the blueprint topic14:15
dane_leblancHave you had a chance to review my comments for multiple prefix BP?14:16
BrianB__sc68cal, sorry could not find the link I was ref to radvd and http://wikicentral.cisco.com/display/OPENSTACK/Blueprint+ideas14:16
*** markwash has quit IRC14:17
BrianB__https://review.openstack.org/9821714:17
sc68callooks like that wikicentral times out for me14:17
BrianB__sorry c&p error14:18
*** Longgeek has quit IRC14:18
sc68caldane_leblanc: I'll take a look at your comments14:18
*** Longgeek has joined #openstack-meeting14:19
xuhanpI will review that spec too.14:19
sc68calat this point it looks like there is either bugs in sphinx or something because the references come out a little broken, but I've seen a couple specs like that14:19
dane_leblancsc68cal: Thanks, that BP is stalled with -114:19
sc68calHenryG: how is https://review.openstack.org/#/c/101306/ going14:21
*** trey_h has joined #openstack-meeting14:21
HenryGLooks like just nits remaining14:22
xuhanpI just gave a -1 today. Sorry about that late comment14:22
HenryGI will address them and ask for approval14:22
HenryGxuhanp: np14:22
sc68caldane_leblanc: I think once we get the radvd implementation underway we'll be able to give more bandwidth to other reviews, like your multi prefix bp14:23
*** jackib has quit IRC14:23
*** esker has quit IRC14:24
*** esker has joined #openstack-meeting14:24
sc68cal#topic code review14:24
*** openstack changes topic to "code review (Meeting topic: neutron_ipv6)"14:24
*** otherwiseguy has joined #openstack-meeting14:25
sc68calAny reviews that need eyeballs?14:25
*** alexpilotti has joined #openstack-meeting14:25
xuhanpsc68cal, I can use some reviews on https://review.openstack.org/#/c/101433/14:25
sc68calI try and keep a list current for the main meeting - to get cores focused on specific reviews - https://wiki.openstack.org/wiki/Network/Meetings#IPv6_.28sc68cal.2914:26
*** david-lyle has joined #openstack-meeting14:26
sc68calxuhanp: cool I'll add that to the list14:26
*** sarob has joined #openstack-meeting14:26
xuhanpand this one:  https://review.openstack.org/#/c/80932/14:26
xuhanpI think it's listed as the dependency of the RADVD implementation14:27
*** SridharG has quit IRC14:27
sc68calxuhanp: agree14:28
*** sankarshan is now known as sankarshan_away14:28
Shixiong_xuhanp, do you need me to review those two code submissions?14:28
Shixiong_101433, and 80932?14:29
xuhanpShixiong_, sure. these are two Ipv6 related bugs14:29
xuhanpthanks14:29
Shixiong_ok, will do14:29
sc68calcool - any others that I need to bring to core's attention?14:31
*** dkranz has quit IRC14:31
*** sarob has quit IRC14:31
sc68cal#topic bugs14:32
*** openstack changes topic to "bugs (Meeting topic: neutron_ipv6)"14:32
sc68calhttps://bugs.launchpad.net/neutron/+bugs?field.tag=ipv614:32
sc68calIf you've reported a bug and don't see it in that list, please add the ipv6 tag to it :)14:33
*** reed has joined #openstack-meeting14:34
*** otherwiseguy has quit IRC14:35
sc68calany other bugs to discuss? otherwise we'll do open discussion14:35
*** crandquist has joined #openstack-meeting14:36
*** fnaval has joined #openstack-meeting14:36
sc68cal#topic open discussion14:36
*** openstack changes topic to "open discussion (Meeting topic: neutron_ipv6)"14:36
*** fnaval has quit IRC14:36
*** fnaval has joined #openstack-meeting14:36
*** andreaf has joined #openstack-meeting14:37
*** SridharG has joined #openstack-meeting14:37
*** craigbr has joined #openstack-meeting14:40
sc68calIf there's nothing else, I'll give everyone back 20 minutes. I'm always in #openstack-neutron if you need me14:40
*** ominakov has quit IRC14:41
sc68calSee everyone next week!14:41
sc68cal#endmeeting14:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:41
openstackMeeting ended Tue Jun 24 14:41:34 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-06-24-13.59.html14:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-06-24-13.59.txt14:41
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-06-24-13.59.log.html14:41
*** garyh has joined #openstack-meeting14:42
*** Macaveli has quit IRC14:43
*** jamiem has joined #openstack-meeting14:44
*** aveiga has left #openstack-meeting14:44
*** markmcclain has joined #openstack-meeting14:45
*** eharney has joined #openstack-meeting14:45
*** trey_h has quit IRC14:45
*** topol has quit IRC14:45
*** ivasev has joined #openstack-meeting14:45
*** jprovazn is now known as jprovazn_afk14:46
*** trey_h has joined #openstack-meeting14:46
*** dkranz has joined #openstack-meeting14:46
*** markmcclain1 has joined #openstack-meeting14:47
*** Michalik_ has quit IRC14:47
*** jackib has joined #openstack-meeting14:49
*** markmcclain has quit IRC14:50
*** Shixiong_ has quit IRC14:50
*** nacim has quit IRC14:51
*** nshaikh has left #openstack-meeting14:52
*** mtanino has joined #openstack-meeting14:52
*** baoli_ has joined #openstack-meeting14:53
*** baoli_ has quit IRC14:53
*** baoli_ has joined #openstack-meeting14:53
*** Michalik_ has joined #openstack-meeting14:54
*** imsurit has joined #openstack-meeting14:54
*** baoli has quit IRC14:55
*** banix has joined #openstack-meeting14:55
*** yingjun has joined #openstack-meeting14:55
*** achanda has joined #openstack-meeting14:55
*** miqui_ has joined #openstack-meeting14:57
*** miqui has quit IRC14:58
*** morganfainberg_L has joined #openstack-meeting14:58
*** caleb_ has joined #openstack-meeting14:58
*** carl_baldwin has joined #openstack-meeting14:59
*** elambert has joined #openstack-meeting14:59
*** nati_ueno has joined #openstack-meeting15:00
*** martines_ has joined #openstack-meeting15:00
*** Demitar has joined #openstack-meeting15:00
n0ano#startmeeting gantt15:00
openstackMeeting started Tue Jun 24 15:00:44 2014 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: gantt)"15:00
openstackThe meeting name has been set to 'gantt'15:00
n0anoanyone here to talk about the scheduler?15:00
bauzas\o15:00
*** chuckC has quit IRC15:01
bauzassounds like the crowds are silent :)15:01
*** marun has joined #openstack-meeting15:01
*** ajo|mac has quit IRC15:02
n0anolisten to the crickets :-)15:02
*** cjellick has joined #openstack-meeting15:02
*** yaguang has quit IRC15:02
bauzaswell, it's the Summer, so that's possible :)15:02
n0anowell, we can make it quick15:02
*** tosky has joined #openstack-meeting15:02
n0ano#topic code forklift15:02
*** openstack changes topic to "code forklift (Meeting topic: gantt)"15:02
*** tosky has left #openstack-meeting15:03
bauzassoooooo15:03
bauzaslong debates this week with johnthetubaguy :)15:03
n0anoI see that john garbutt doesn't like one of your patches, is that one crucial15:03
bauzaswell, which one do you refer ?15:03
n0anohttps://review.openstack.org/#/c/97232/15:03
bauzasah, this one15:04
bauzas(I know now all of them by the numbers ;) )15:04
*** SridharG has quit IRC15:04
n0anoit's shorter :-)15:04
bauzasso, indeed, the problem is about how we care until Gantt is out15:04
*** alexpilotti has quit IRC15:04
*** PaulMurray has joined #openstack-meeting15:04
bauzasI finally agreed with John15:04
n0anoif we can do the split and then do 97232 then I don't have a problem waiting for it also, my prime goal is just doing the split15:05
bauzasindeed15:05
bauzaswe will still have many things to do15:05
n0anoI looked at 82778 and didn't see anything wrong (probably a weakness in my pyhthon foo)15:06
bauzasso, let's unscope 97232 from the pre-split tasks15:06
n0ano+115:06
bauzasyey, the real debate is about 8277815:06
bauzaseverything was fine until last week...15:06
*** achanda has quit IRC15:06
bauzasthe idea is to update the stats without returning nothing15:07
bauzasthat's cool15:07
bauzasbut...15:07
* johnthetubaguy waves15:07
bauzas(teaser)15:07
bauzasso, everything is setup in resourcetracker and updated to the scheduler15:07
bauzasnothing is needed to be returned to RT15:07
bauzasnothing but...15:08
bauzasI discovered a section of PCI code asking explicitely for the compute node id15:08
*** neelashah has quit IRC15:08
bauzaswhich is not returned back when creating15:08
*** tbarron has quit IRC15:08
bauzasso that's blocking the creation of computenode in TR15:08
bauzasRT15:08
n0anoyeah, things can get very intertwined15:09
bauzasI did the PCI code review and there is no clear benefit of keeping the cn id15:09
*** tbarron has joined #openstack-meeting15:09
bauzasthat's basically for raising an exception and saying which CN is failing15:09
*** Michalik_ has quit IRC15:09
bauzasso, yjiang5 agreed on removing that cn id from PCI15:09
bauzasbut until that, compute node creations has to be done on the RT side15:10
n0anoso now you're dependent upon the change to the PCI code, right?15:10
bauzasnope15:10
bauzasbecause that's life, and we have to figure out another way15:10
johnthetubaguyn0ano: I think we can leave compute node in nova basically15:10
johnthetubaguyn0ano: and gantt just has its own copy15:11
*** ewindisch has quit IRC15:11
*** alexpilotti has joined #openstack-meeting15:11
*** jcoufal has quit IRC15:11
bauzasthat was most of the previous talk I had with johnthetubaguy, about keeping compute node in Nova :)15:11
johnthetubaguyn0ano: so PCI stuff still goes in there tables (till they fix that)15:11
bauzasso n0ano your thoughts are welcome here :)15:11
*** miqui_ is now known as miqui15:11
johnthetubaguyyeah, would be good to agree a direction here15:11
*** dkranz has quit IRC15:12
johnthetubaguyI am pro leaving compute node in nova, and just not populating the stats there when we switch to gantt15:12
n0anoa little concerned about 2 copies of compute node (one in nova, one in gantt) but, if we're careful, it's probably OK15:12
johnthetubaguythat way we don't have to wait for PCI, they can do that at there own speed15:12
*** ewindisch has joined #openstack-meeting15:12
n0ano+1 (not being depenent upon PCI changes is good)15:13
johnthetubaguyn0ano: yeah, it just means we wrip it out of Nova later, and gantt needs a separate database and schema anyways15:13
bauzas+1 too15:13
n0anoI'm hearing violent agreement15:13
*** shakamunyi has quit IRC15:13
bauzasyey, but the debate is not there :)15:13
*** daneleblanc has joined #openstack-meeting15:14
bauzasnow we agree to workaround the current situation (RT has to know the CN ID)15:14
PaulMurraybauzas, what does it take for PCI stuff to be done first15:14
bauzaswhat's the best option ?15:14
bauzasPaulMurray: good question, a quick code review showed me little effort here15:14
*** gokrokve has quit IRC15:14
*** yfried_ has joined #openstack-meeting15:14
PaulMurraybauzas, so why not do it?15:14
bauzasPaulMurray: but I'm possibly missing a crucial thing15:14
PaulMurraybauzas, I think you said it was for information in the exceptions?15:15
PaulMurraybauzas, or at least logging15:15
n0anoPaulMurray, I've been waiting 2 weeks for a simple change, things can take a long time to get done15:15
bauzasPaulMurray: because PCI code is very sensitive, I have no way to correctly test it :)15:15
johnthetubaguyyeah, its not worth doing PCI code15:15
PaulMurrayn0ano, no s***15:15
johnthetubaguybauzas: I got confused where we are debating to be honest15:16
bauzasPaulMurray: and I unfortunately discovered that PCI testing is a bit unsufficient because Jenkins was still happy with my change even if I was not giving back the id.... :)15:16
n0anothe more stuff we are responsible for, the better15:16
johnthetubaguybauzas: yes, no PCI passthrough testing in the gate right now15:16
johnthetubaguyn0ano: turns out we get PCI stats for scheduling OK, its just some internal account stuff that not scheduling related that happens to use ComputeNode that would stay in nova15:17
bauzasok, everyone happy with leaving compute nodes in RT ?15:17
*** dane_leblanc has quit IRC15:17
PaulMurraybauzas, no, but understand it may be better than waiting on pci15:17
johnthetubaguyPaulMurray: what your worry with compute node in RT15:18
n0anojohnthetubaguy, as I said, a little icky (2 copies) but probably OK, something to fix as soon as possible once gantt is split out15:18
bauzasPaulMurray: the alternative was to give back the id when creating the node in Scheduler client code15:18
*** sweston_ has joined #openstack-meeting15:18
johnthetubaguyn0ano: its just a slightly empty nova structure, the gnatt one will have to be different in shape regardless15:18
PaulMurraybauzas, johnthetubaguy its only about making things cleaner for me15:19
johnthetubaguyn0ano: there should be no data in two places, except the name15:19
bauzasI made various code proposals about the split in different patchsets15:19
johnthetubaguyPaulMurray: right, I see it as delete the ComputeNode independently of the scheduler split15:19
bauzaspeople can compare and appreciate which one is better15:19
*** sarob has joined #openstack-meeting15:19
*** Demitar has quit IRC15:19
*** ramishra has quit IRC15:19
bauzasI'm still having a -1 from Jenkins on the last patchset, but probably a short miss15:20
bauzasor some tests to fix15:20
PaulMurraybauzas, is the latest the one to review?15:20
bauzasone sec, checking15:20
PaulMurraybauzas, you made 3 revisions since I started to look15:20
*** yisun_ has quit IRC15:21
johnthetubaguyso, for the record, I am kinda pushing for this sort of approach: https://review.openstack.org/#/c/101858/15:21
*** Demitar has joined #openstack-meeting15:21
n0anobauzas, you do have a -1, I missed that (I `hate` color encodings)15:21
bauzasok, lemme give you details15:21
johnthetubaguybasically, just move self.conductor_api.compute_node_update into the scheduler client15:21
*** belmoreira has quit IRC15:22
*** sarob has quit IRC15:22
bauzaspatchset #26 is everything done in Scheduler, compute nodes owned by sched client15:22
johnthetubaguyso we drop a gantt client that would take the same stats and store them somewhere else, if you don't want nova-scheduler15:22
bauzasnah, nevermind15:22
bauzasso15:22
*** sarob has joined #openstack-meeting15:22
johnthetubaguyits a tricky line to draw, thats agreed here15:23
*** vjay2 has quit IRC15:23
bauzasso, patchset #26 is everything done in sched client15:23
n0anojohnthetubaguy, +2 (plus the devil is in the details)15:23
bauzaspatchset #27 is john's proposal about keeping creation in RT15:23
bauzaspatchset #30 is a CRUD interface15:23
bauzas(everything done in sched client)15:24
*** dkranz has joined #openstack-meeting15:24
johnthetubaguyyup, https://review.openstack.org/#/c/101858 (which because #27) is just updating the stats in the client, and leaving the compute node in the RT15:24
bauzaspatchset #31 is john's idea, but a little rewritten15:24
PaulMurraybauzas, I'm wondering if this should be marked work in progress15:24
*** Michalik_ has joined #openstack-meeting15:25
bauzasPaulMurray: I can, at least until Jenkins is happy15:25
bauzasPaulMurray: but situation is changing everyday because of the confusion15:25
*** topol has joined #openstack-meeting15:25
*** sajeesh has quit IRC15:25
bauzasyesterday, it was OK for reviewing15:25
PaulMurraybauzas, its the latter I was thinking about15:25
bauzasok, putting WIP now15:25
*** neelashah has joined #openstack-meeting15:26
PaulMurraybauzas, although I know people don't review WIP#15:26
johnthetubaguybauzas: my patch had some fixed up unit tests you might want to borrow15:26
PaulMurraybauzas, but I will :)15:26
bauzaswell, I think we need to agree on the approach15:26
johnthetubaguybauzas: what have we not agreed on at this point?15:27
bauzaseveryone's happy with keeping cn creation in RT and cn update in scheduler client ?15:27
*** sarob has quit IRC15:27
n0anobauzas, +1 (that's my understanding)15:27
bauzasjohnthetubaguy: I was feeling a little confusion over here15:27
bauzasPaulMurray ?15:27
*** rbowen has quit IRC15:27
PaulMurraybauzas, not sure15:27
*** rbowen has joined #openstack-meeting15:27
PaulMurraybauzas, I think I am probably not deep enough into the problems here15:28
bauzasPaulMurray: could you then review all the patchsets I mentioned and leave a comment directly in Gerrit ?15:28
johnthetubaguyso just be mess things up a bit, I don't think we keep ComputeNode in RT, I think we remove that separately to this client work15:28
PaulMurraybauzas, yes, I was half way through looking but got confused over what I should be looking at15:28
bauzasthis blueprint is awfully time-consuming, and I just want to make sure we all agree on what needs to be done15:28
*** jecarey has joined #openstack-meeting15:29
bauzasthe last 2 weeks were about doing back and forthes on that patch, just want to make sure everybody will like the direction :)15:29
*** ramishra has joined #openstack-meeting15:30
PaulMurraybauzas, by "create compute node" do yo mean the conductor call to create it in db or do you mean the compute_node data structure?15:30
bauzasRT will still issue the call to conductor create, and the DB model will stay in Nova :)15:30
*** Demitar has quit IRC15:31
PaulMurraybauzas, I would prefer to see the db create and update in client library, but as I said15:31
bauzasbut in the proposal, the sched client is doing the update call15:31
PaulMurraybauzas, I not sure I yunderstand the difficulties15:31
bauzasto the conductor15:31
*** coolsvap|afk is now known as coolsvap15:31
*** hashar is now known as hasharMeeting15:31
bauzaswell, there is no difficulty in having sched client owning the creation15:31
bauzasyou can look at patchset #2615:32
bauzasthat was the case15:32
*** caleb_ has quit IRC15:32
bauzaswe just need to return the id when the creation is done15:32
*** changbl has joined #openstack-meeting15:32
johnthetubaguyPaulMurray: let me find you a quick link, its this...15:32
*** leeantho has joined #openstack-meeting15:32
johnthetubaguyPaulMurray: https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/models.py#L137815:32
PaulMurrayn0ano, as a process point, is it ok dwelling on this in this meeting?15:33
johnthetubaguyPCI device stats are stored with a foreignkey into compute node table15:33
n0anoPaulMurray, sure, this is the only agenda item for today15:33
johnthetubaguyits not scheduler info, its resource tracker only state, so needs to stay in Nova15:33
bauzasPaulMurray: https://review.openstack.org/#/c/82778/26/nova/scheduler/client.py here is the proposal having sched client owning conductor calls15:33
*** marun has quit IRC15:33
johnthetubaguyPaulMurray: if the scheduler client owns the compute node, it ends up passing back the id, so that the compute node id is known to the PCI tracer15:34
*** zz_blogan is now known as blogan15:34
*** haomaiwa_ has joined #openstack-meeting15:34
*** kenhui has quit IRC15:35
*** crandquist has quit IRC15:35
johnthetubaguyPaulMurray: so when you replace the nova scheduler client, the gantt client would have to still access the nova db, which is not allowed, so we need to first change the PCI stats, then we also end up pass back in id that should be interal to gantt, and its all very confusing15:35
n0anoas I understand it, this is all a little convoluted in order to make the current PCI code happy15:35
*** kenhui has joined #openstack-meeting15:35
bauzasjohnthetubaguy: I'm just wondering if we can imagine such scenario :15:35
johnthetubaguyn0ano: yeah, further I think it doesn't work when you add in the gantt client, until you change the nova DB structures for the PCI devices15:35
*** oanufriev has quit IRC15:36
bauzas1. merge the client to place all creation/update calls and return the id with a FIXME comment15:36
*** oanufriev has joined #openstack-meeting15:36
bauzas2. do the PCI work of removing that FK15:36
johnthetubaguyupdates only seems to work both ways though, although it leaves the old DB structures in Nova, till it deletes them, which we have to do anyway due to the different deprecation cycles15:36
n0anojohnthetubaguy, well, one good thing is jiang is in my group so I can probably get his attention to make PCI changes :-)15:36
bauzas3. provide a Gantt client15:36
*** flaper87|afk is now known as flaper8715:36
johnthetubaguyn0ano: right, but its a bit chain of changes that may never get into trunk15:37
bauzasanyway,we're far from proposing a Gantt client now so there is high probability to have the PCI fix before the use of a Gantt client in Nova15:37
*** marun has joined #openstack-meeting15:37
n0anojohnthetubaguy, which is why we work around the PCI code for now and worry about fixing it later15:38
PaulMurrayn0ano, the reason I didn't get the ComputeNode object done in RT a while back was difficulties with PCI15:38
*** vermarah_ has joined #openstack-meeting15:38
*** vermarah has joined #openstack-meeting15:38
PaulMurrayn0ano, that's why I am sympathetic to the "PCI avoidance route"15:38
*** ArthurBerezin has joined #openstack-meeting15:38
johnthetubaguyn0ano: yeah, thats my preference15:38
PaulMurrayn0ano, sooner or later we need to clean up the PCI code15:38
n0anounfortunate that all roads lead back to the PCI code, oh well15:38
*** boh_ricky has joined #openstack-meeting15:39
bauzasand there is high visibility because of the SRIOV efforts15:39
*** gokrokve has joined #openstack-meeting15:39
n0anoI don't have a problem with PCI & SR/IOV, it's just the implementation that needs to be cleaned up15:39
PaulMurrayn0ano, there was a suggestion (possibly from jiang) to make PCI a resource plugin for extensible RT15:39
bauzasn0ano: +115:40
*** gyee has joined #openstack-meeting15:40
PaulMurrayn0ano, we could try to make an effort to sort it out if that ever comes about15:40
*** SridharG has joined #openstack-meeting15:40
n0anomid-cycle meetup coming soon, we should raise that issue then (both jiang & I will be there)15:41
PaulMurrayn0ano, me too15:41
bauzasI won't be able to be there :(15:41
*** daneleblanc has quit IRC15:41
n0anobauzas, NP, I'll do your proxy :-)15:41
*** fnaval has quit IRC15:41
bauzasmy wife had the unsupportable thing to expect to release my 2.0 baby by these dates15:42
johnthetubaguyI will be at the mid-cylce15:42
johnthetubaguyjust not really sure what we are disagreeing about here15:42
n0anobauzas, congratulations, that's a good excuse15:42
n0anojohnthetubaguy, seems like the current PCI implementation is impacting two different areas, that's an indication that somethings wrong15:43
*** MaxV has quit IRC15:43
bauzasanyway, that's also a matter of timeline15:43
bauzasI would prefer this code to be merged before Juno-215:43
*** HenryG has quit IRC15:43
johnthetubaguyn0ano: yes, but we seem to have a solution to that now, but maybe I am missing something15:43
*** MaxV has joined #openstack-meeting15:43
bauzasbasically, the refactor is very simple, but we care about how we should do it15:43
n0anojohnthetubaguy, a work around for us but we would still like the PCI code to change later15:44
johnthetubaguyn0ano: oh very true, I think the SRIOV stuff gets most of that into a better place, but there are other bits of work15:45
n0anoas I keep saying, the devil is in the details15:45
bauzasmaybe I'm wrong, but if we talk about workarounds, why returning an id can't be a possible approach ?15:45
n0anobauzas, would that require changes to the PCI code?15:46
PaulMurraybauzas, the db interface passes back the whole data structure with the id filled in15:46
johnthetubaguybauzas: what id are you returning, is the problem? and why, the key into the DB should the (compute host, compute node) tripple that gets returned from select destinations15:46
bauzasn0ano: nope15:46
PaulMurraybauzas, could do same?15:46
johnthetubaguyPaulMurray: I just don't see what the scheduler should have to return the values you just sent it, given the values are out of date when you send them, but you know the better values yourself15:47
johnthetubaguy^ oops, why the scheduler, not what15:47
bauzasjohnthetubaguy: if we say that https://review.openstack.org/#/c/82778/26/nova/scheduler/client.py is returning the compute_node['id'], that's a workaround15:47
PaulMurrayjohnthetubaguy, yes, fair enough15:48
johnthetubaguybauzas: but what would the gantt client do when you drop it in there?15:48
*** MaxV has quit IRC15:48
johnthetubaguybauzas: it is writing into a different database, so the id will not help the PCI stats that still talks to the Nova db15:48
bauzasbut we agreed to ask PCI guys to do the removal ?15:48
*** asselin has joined #openstack-meeting15:48
PaulMurraybauzas, isn't the PCI stats part of the compute node information that would go to the scheduler?15:49
bauzasas I said, in terms of planning, this is far sooner to remove the FK in PCI table that having Nova making use of a Gantt client15:49
*** MaxV has joined #openstack-meeting15:49
johnthetubaguybauzas: its a bit trickier on the PCI side, it might make sense to keep it15:49
*** ramishra has quit IRC15:49
bauzasjohnthetubaguy: well, yjiang5 said he was ok to remove it15:49
johnthetubaguybauzas: can we go back to the question around the id, what would you return, and how does it help the PCI stats?15:50
*** ramishra has joined #openstack-meeting15:50
*** rmoe has quit IRC15:50
*** atiwari has joined #openstack-meeting15:50
johnthetubaguybauzas: it should go into the persistent resource tracker BP, so its more of a move, but lets not get distracted by PCI details15:50
bauzasjohnthetubaguy: https://review.openstack.org/#/c/82778/26/nova/scheduler/client.py L65 I would return values['id']15:50
johnthetubaguybauzas: but its from the gantt db, not the nova db, so doesn't help the PCI stats15:51
johnthetubaguythat id doesn't exist in the nova db15:51
johnthetubaguy(when using the gantt client)15:51
*** sushils_ has quit IRC15:51
* johnthetubaguy so wishes he could draw a picture15:52
*** chuckC has joined #openstack-meeting15:52
* bauzas would love to see all of you in person :)15:53
PaulMurraymaybe we need our own meet up15:53
*** eghobo has joined #openstack-meeting15:53
johnthetubaguyhttps://awwapp.com/draw.html#0dca39e515:53
*** eghobo has quit IRC15:53
bauzasI'm saying that once we will a gantt client15:53
n0anoPaulMurray, unfortunately, the july in Oregon and nov and Pars are the only near term options15:54
*** ramishra has quit IRC15:54
n0anos/and Pars/in Paris15:54
johnthetubaguybauzas: thats what I am trying to say, the id is from the wrong database: https://awwapp.com/draw.html#0dca39e515:54
*** eghobo has joined #openstack-meeting15:55
bauzaswe would possibly move the conductor calls back in RT in the _update() method and make use of the client, if necessary15:55
*** jtomasek has quit IRC15:55
johnthetubaguybauzas: you can't access the nova DB directly from compute nodes, security reasons, so we need the conductor for that15:55
*** zhangleiqiang has quit IRC15:56
*** hartsocks has joined #openstack-meeting15:56
johnthetubaguythe scheduler might need its own conductor, but thats a different story15:56
*** paragan has quit IRC15:56
bauzasjohnthetubaguy: I would so love to show you my thoughts in the code directly...15:56
johnthetubaguy(I have a gantt API plan in my head that doesn't involve REST...)15:56
*** phil__ has quit IRC15:56
johnthetubaguybauzas: which bit?15:56
*** markmcclain1 has quit IRC15:57
*** hemna_ has joined #openstack-meeting15:58
bauzasjohnthetubaguy: https://review.openstack.org/#/c/82778/26/nova/compute/resource_tracker.py15:58
bauzasjohnthetubaguy: consider this one the trunk with gantt in use15:58
*** yamahata has joined #openstack-meeting15:59
*** marekd is now known as marekd|away15:59
n0anounfortunately, I have another meeting and we're running out of time, I'll have to send you guys over to #openstack-nova15:59
johnthetubaguybauzas: so thats basically the gantt client I am imagining, but it talks to the scheduler "conductor", but right now that would break PCI if it were the nova client as well15:59
*** ArthurBerezin has left #openstack-meeting16:00
bauzaslet's move to #openstack-nova :)16:00
*** Fdot has quit IRC16:00
n0anoso, I'll thank everyone, looking forward to an updated patch, and we'll talk again next week16:00
johnthetubaguybauzas: +116:00
bauzasn0ano: thanks a lot :)16:00
*** vivek-ebay has joined #openstack-meeting16:00
n0ano#endmeeting16:00
PaulMurraybye n0ano16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Tue Jun 24 16:00:25 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-06-24-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-06-24-15.00.txt16:00
n0anobye all16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-06-24-15.00.log.html16:00
*** annegent_ has joined #openstack-meeting16:00
*** xuhanp has quit IRC16:00
*** evgenyf has quit IRC16:00
*** eghobo has quit IRC16:01
*** annegent_ has quit IRC16:01
*** ramishra has joined #openstack-meeting16:01
*** eghobo has joined #openstack-meeting16:01
*** annegent_ has joined #openstack-meeting16:01
*** caleb_ has joined #openstack-meeting16:01
*** sweston_ has quit IRC16:02
*** PaulMurray has left #openstack-meeting16:02
*** prad_ has joined #openstack-meeting16:03
*** temujin has quit IRC16:03
*** vivek-ebay has quit IRC16:03
*** vivek-ebay has joined #openstack-meeting16:04
*** MaxV has quit IRC16:05
*** fnaval has joined #openstack-meeting16:06
*** crandquist has joined #openstack-meeting16:06
*** rmoe has joined #openstack-meeting16:06
*** marcoemorais has joined #openstack-meeting16:08
*** sweston_ has joined #openstack-meeting16:08
*** Leonr has joined #openstack-meeting16:09
*** crandquist has quit IRC16:11
*** yingjun has quit IRC16:11
*** yingjun has joined #openstack-meeting16:12
*** Michalik_ has quit IRC16:16
*** yingjun has quit IRC16:16
*** Demitar has joined #openstack-meeting16:16
*** kenhui has quit IRC16:17
*** nati_ueno has quit IRC16:17
*** andreaf has quit IRC16:18
*** andreaf has joined #openstack-meeting16:19
*** markwash has joined #openstack-meeting16:20
*** beagles is now known as brent16:21
*** brent is now known as beagles16:22
*** gokrokve_ has joined #openstack-meeting16:22
*** afazekas has quit IRC16:24
*** gokrokve has quit IRC16:25
*** ramashri has joined #openstack-meeting16:25
*** salv-orlando has joined #openstack-meeting16:26
*** flaper87 is now known as flaper87|afk16:26
*** Demitar has quit IRC16:26
*** comay has joined #openstack-meeting16:27
*** sankarshan_away is now known as sankarshan16:29
*** otherwiseguy has joined #openstack-meeting16:30
*** vivek-ebay has quit IRC16:31
*** gokrokve_ has quit IRC16:32
*** yjiang5 is now known as yjiang5_away16:33
*** hemanthravi has quit IRC16:35
*** pberis has quit IRC16:35
*** salv-orlando_ has joined #openstack-meeting16:36
*** yfried_ has quit IRC16:36
*** yfried_ has joined #openstack-meeting16:37
*** salv-orlando has quit IRC16:37
*** salv-orlando_ is now known as salv-orlando16:37
*** tkay has joined #openstack-meeting16:39
*** __afazekas is now known as afazekas16:41
*** jcoufal has joined #openstack-meeting16:41
*** natarajk has joined #openstack-meeting16:41
*** noslzzp has quit IRC16:42
*** isviridov is now known as isviridov|away16:43
*** moha_hunt has quit IRC16:43
*** jjmb has quit IRC16:43
*** noslzzp has joined #openstack-meeting16:43
*** pballand has joined #openstack-meeting16:44
*** sarob has joined #openstack-meeting16:45
*** balajiiyer has quit IRC16:48
*** meteorfox has joined #openstack-meeting16:48
*** ramishra has quit IRC16:49
*** ramashri has quit IRC16:49
*** bdpayne has joined #openstack-meeting16:49
*** balajiiyer has joined #openstack-meeting16:49
*** beagles is now known as brent16:50
*** thinrichs has joined #openstack-meeting16:50
*** yjiang5_away is now known as yjiang516:51
*** brent is now known as beagles16:52
*** hasharMeeting has quit IRC16:52
*** whenry has quit IRC16:54
*** pelix has quit IRC16:54
*** ajo|mac has joined #openstack-meeting16:54
*** harlowja_away is now known as harlowja16:55
*** baoli has joined #openstack-meeting16:56
*** ramishra has joined #openstack-meeting16:56
*** baoli has quit IRC16:56
*** baoli has joined #openstack-meeting16:57
*** baoli_ has quit IRC16:57
*** SumitNaiksatam has quit IRC16:57
*** shakamunyi has joined #openstack-meeting16:59
*** shakamunyi has quit IRC16:59
*** Demitar has joined #openstack-meeting16:59
*** Michalik_ has joined #openstack-meeting16:59
*** bklei has joined #openstack-meeting16:59
boris-42#startmeeting Rally17:00
openstackMeeting started Tue Jun 24 17:00:03 2014 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: Rally)"17:00
openstackThe meeting name has been set to 'rally'17:00
*** shakamunyi has joined #openstack-meeting17:00
*** rbowen has quit IRC17:00
boris-42msdubov hughsaunders marcoemorais ping17:00
*** caleb_ has quit IRC17:00
*** rbowen has joined #openstack-meeting17:00
*** olkonami has joined #openstack-meeting17:00
*** whenry has joined #openstack-meeting17:00
*** lcheng has quit IRC17:01
marcoemoraisboris-42: heya17:01
meteorfoxboris-42: hi17:01
*** tzabal has joined #openstack-meeting17:01
coolsvapheya17:01
*** k4n0 has joined #openstack-meeting17:01
*** jtaleric has joined #openstack-meeting17:01
k4n0I am here for rally meeting17:01
k4n0o/17:02
boris-42=)17:02
* jtaleric lurking 17:02
*** mrunge has quit IRC17:02
boris-42Hi all17:02
*** balajiiyer has left #openstack-meeting17:02
oanufrievhi17:02
tzabalhi17:02
boris-42let's just wait a couple of minutes17:03
olkonamihi17:03
*** BrianB__ has quit IRC17:04
*** msdubov_ has joined #openstack-meeting17:04
*** ajo|mac has quit IRC17:04
*** ivar-lazzaro has joined #openstack-meeting17:04
boris-42so let's start=)17:04
*** lcheng has joined #openstack-meeting17:05
boris-42#topic we should do something with our unit test coverage17:05
*** openstack changes topic to "we should do something with our unit test coverage (Meeting topic: Rally)"17:05
boris-42Okay recently (today) I added new job in Jenkins17:05
boris-42that will create cover report on every patch17:05
boris-42job is called rally-coverage17:06
*** ramashri has joined #openstack-meeting17:06
*** redixin has joined #openstack-meeting17:06
boris-42and if you click on it you'll see pretty html report17:06
boris-42(red lines means that code is not covered by unit tests)17:06
redixinsorry i late -_-17:06
boris-42We should have 100% coverage17:06
boris-42Any questions?17:06
k4n0boris-42, 100% should be enforced on gates17:06
boris-42k4n0 99^17:07
boris-42k4n0 +1 for that to have some kind of 98% as a lower border for coverage17:07
boris-42k4n0 otherwise just -117:07
k4n0+117:07
boris-42but first of all we need to cover everything tests=)17:07
*** Demitar has quit IRC17:08
boris-42okay next topic17:08
k4n0We can split up modules and start writing tests , maybe do this on a google doc or something17:08
boris-42k4n0 probably we should make some kind of blueprint17:08
boris-42k4n0 and workitems17:08
boris-42?17:08
redixin+1 for blueprint17:08
k4n0boris-42, blueprint is also good, ill make one after meeting17:09
boris-42k4n0 thanks17:09
boris-42so we will be able to split work17:09
boris-42and work together17:09
boris-42okay next topic17:09
k4n0ok17:09
boris-42#topic osprofiler17:09
*** openstack changes topic to "osprofiler (Meeting topic: Rally)"17:09
k4n0#action make blueprint for unit test coverage17:09
boris-42Okay guys I made a last changes in API17:10
*** gokrokve has joined #openstack-meeting17:10
boris-42and cover it 100% by unit tests17:10
*** jsavak has joined #openstack-meeting17:10
boris-42Going to launch devstack with it17:10
boris-42and if there is no issues I will cut release17:10
boris-42Any questions?)17:10
*** VijayB has joined #openstack-meeting17:11
boris-42https://github.com/stackforge/osprofiler this is library if somebody doesn't know =)17:11
boris-42Okay moving to next topc17:11
*** bdpayne has quit IRC17:11
boris-42#topic Rally SLA17:12
*** openstack changes topic to "Rally SLA (Meeting topic: Rally)"17:12
boris-42redixin plsss be more verbose17:12
boris-42=)17:12
k4n0what is Rally SLA ?17:12
boris-42redixin and tell us what is it and status17:12
*** bklei has left #openstack-meeting17:12
*** SumitNaiksatam has joined #openstack-meeting17:12
*** rockyg has joined #openstack-meeting17:12
redixinrally sla is just one more section in the task config file17:13
redixinit is possible to specify criterios17:13
redixinlike maximum error rate17:13
redixinor time limits17:13
*** haneef_ has joined #openstack-meeting17:13
k4n0that is great17:13
redixintask is going as usual, but there is special command to check if task was successful or not17:14
*** DuncanT- is now known as DuncanT17:14
redixinaccording to criterios17:14
*** jtaleric is now known as rook17:14
*** rook is now known as jtaleric17:14
redixinhere is the patch https://review.openstack.org/#/c/98158/17:14
boris-42redixin btw we will need to add it to HTML17:14
boris-42redixin somehow (e.g. does it pass or not criteria) and details17:15
boris-42redixin I'll think about it17:15
redixinyes, we can add one more table to html results17:15
redixinand one more table to task detailed outpu17:15
boris-42redixin yep17:15
*** iyozhikov is now known as IgorYozhikov17:16
*** IgorYozhikov is now known as iyozhikov17:16
boris-42So as well our jobs check-rally-dsvm-rally and check-rally-dsvm-neutron-rally17:16
boris-42will be able to check more carefully17:16
boris-42benchmarks17:16
*** haomaiwa_ has quit IRC17:16
boris-42e.g. we can setup for most of them that there is no failures17:17
boris-42so we won't need to go and take a look every time on all tasks17:17
boris-42any questions?17:17
*** eharney_ has joined #openstack-meeting17:17
*** eharney has quit IRC17:18
*** eharney_ is now known as eharney17:18
*** penguinRaider has joined #openstack-meeting17:20
boris-42#topic stress runner17:20
*** openstack changes topic to "stress runner (Meeting topic: Rally)"17:20
boris-42olkonami pls could you introduce us?17:21
*** jtaleric is now known as rook17:21
olkonamiit is runner which increase concurrency stepwise17:22
*** jseutter has joined #openstack-meeting17:22
olkonamihttps://review.openstack.org/#/c/94806/17:22
boris-42olkonami is it ready?17:22
olkonamiboris-42: not yet17:23
*** sushils has joined #openstack-meeting17:24
boris-42olkonami ok any questions about it?17:24
k4n0olkonami, when does it stop increasing concurrency?17:24
k4n0olkonami, i mean if lots of api errors start coming up due to increased load, does it still keep increasing concurrency?17:25
*** rwsu has joined #openstack-meeting17:25
*** nealph has quit IRC17:26
olkonamik4n0: we have max_failure_rate parameter for that, if it is exceeded, it will stop increasing17:26
k4n0olkonami, ok so that is max failure for atomic action ?17:26
k4n0olkonami, I will check the patch in detail, we  can move on for now :)17:27
*** sirushti has joined #openstack-meeting17:27
olkonamik4n0, sorry, don't understand question17:28
boris-42k4n0 nope for atomic action17:28
boris-42k4n0 for whole iteration17:28
k4n0boris-42, got it17:28
boris-42k4n0 so it will run with some constant load17:28
boris-42k4n0 for some period17:28
*** sirushti has left #openstack-meeting17:28
boris-42k4n0 before increasing load it will check17:28
boris-42k4n0 that success / all is > then some parameter17:29
k4n0boris-42, cool , got it17:29
boris-42#topic RPS runner (or refactored periodic)17:29
*** openstack changes topic to "RPS runner (or refactored periodic) (Meeting topic: Rally)"17:29
boris-42oanufriev hey could you share updates ?17:29
olkonamialso now parameter for regular stop incrasing is named "growth_count", do someone have better proposes?17:29
redixinstart, step, stop17:30
oanufrievsorry, i can share them in 1.5 haur. Thereis a bug in unit test that causes memory leak17:30
*** bdpayne has joined #openstack-meeting17:30
oanufrievif it's about code17:31
oanufrievand about works17:31
*** doron_afk has quit IRC17:31
*** amcrn has joined #openstack-meeting17:32
oanufrievperiodic runner has been redesigned to check rps parameter instead period17:32
oanufrievso now it should be understanded as N runs per second17:33
*** ildikov has quit IRC17:34
oanufrievalso i made extensible pool of multiprocessing.Process instances instead of using fixed lenght list of pools17:34
*** shakamunyi has quit IRC17:34
*** redixin has quit IRC17:34
oanufrievthat was made to decrease memory usage and related failures17:34
oanufrievquestions17:35
oanufriev?17:35
*** rediskin has joined #openstack-meeting17:36
boris-42oanufriev when can we see any patches related to this?17:36
oanufrievin 1.5 hour at gerrit ^)17:36
oanufrievin 1.5 hour at gerrit :)17:36
boris-42oanufriev great17:37
boris-42any questions from anybody?17:37
boris-42marcoemorais hughsaunders rediskin k4n0 olkonami ?17:37
rediskinnope17:37
k4n0nope17:37
*** akuznetsov has quit IRC17:37
*** vivek-ebay has joined #openstack-meeting17:37
*** caleb_ has joined #openstack-meeting17:38
*** samcdona has quit IRC17:38
olkonamino patchs - no questions :)17:38
*** achanda has joined #openstack-meeting17:38
boris-42lol=)17:39
boris-42#topic rally & tempest17:39
*** openstack changes topic to "rally & tempest (Meeting topic: Rally)"17:39
boris-42k4n0 any news?)17:39
*** sarob has quit IRC17:39
k4n0no updates, I am working on fixing review comments on latest patch17:39
k4n0I am generating html from json stored in DB17:39
k4n0json is coming from tempest subunit logs17:40
*** jprovazn_afk has quit IRC17:40
*** sarob has joined #openstack-meeting17:40
*** andreaf has quit IRC17:40
*** vjay2 has joined #openstack-meeting17:40
*** Mandell has joined #openstack-meeting17:40
k4n0Now i need to refactor the code such that we have a command like this "rally verify result -type html -out file.html "17:40
*** ramishra has quit IRC17:40
k4n0https://review.openstack.org/10191717:41
*** ramashri has quit IRC17:42
*** msdubov_ has quit IRC17:43
boris-42k4n0 ok great17:44
boris-42#topic Open Discussion17:44
*** openstack changes topic to "Open Discussion (Meeting topic: Rally)"17:44
boris-42Anybody would like to discuss anything?17:44
*** _nadya_ has quit IRC17:45
boris-42hey hey hey?)17:46
k4n0nothing from my end. I am not feeling well today17:46
k4n0I have to get my wisdom tooth removed tomorrow :)17:46
boris-42=)17:46
boris-42k4n0 tomorrow?17:46
boris-42k4n0 or yestardsy?)17:47
k4n0tomorrow afternoon17:47
*** fawadkhaliq has joined #openstack-meeting17:47
olkonamik4n0, get well soon!17:48
k4n0thanks17:48
boris-42k4n0 oh17:48
*** sarob has quit IRC17:49
boris-42k4n0 have the same experience on previous friday=)17:49
boris-42I would like to try to avid such stuff in future=)17:49
*** mrunge has joined #openstack-meeting17:49
k4n0boris-42, you also removed wisdom tooth?17:49
boris-42k4n0 yep17:50
boris-42k4n0 4 days ago17:50
k4n0boris-42, haha, conincidence17:50
k4n0boris-42, anyways, lets talk after meeting :)17:50
boris-42k4n0 okay17:50
boris-42I think we can end this meeting17:50
*** sankarshan is now known as sankarshan_away17:50
boris-42thank you all guys=)17:51
oanufrievboris-42 that's why you so angry =)17:51
boris-42oanufriev yep =)17:51
k4n0thanks all17:51
k4n0oanufriev, haha17:51
boris-42#endmeeting17:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:51
openstackMeeting ended Tue Jun 24 17:51:33 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-06-24-17.00.html17:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-06-24-17.00.txt17:51
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-06-24-17.00.log.html17:51
*** tzabal has left #openstack-meeting17:51
*** olkonami has left #openstack-meeting17:53
*** sarob has joined #openstack-meeting17:53
*** k4n0 has quit IRC17:53
*** Michalik_ has quit IRC17:54
*** Penick has joined #openstack-meeting17:54
*** rgrober has joined #openstack-meeting17:54
*** leonchio_ has joined #openstack-meeting17:55
*** thinrichs has quit IRC17:56
*** pballand has quit IRC17:56
*** jcoufal has quit IRC17:56
*** yjiang5 is now known as yjiang5_away17:57
*** rockyg has quit IRC17:57
*** thinrichs has joined #openstack-meeting17:57
*** kwss has joined #openstack-meeting17:58
*** vivek-ebay has quit IRC17:59
*** henrynash has joined #openstack-meeting17:59
*** ivar-lazzaro has quit IRC17:59
dolphmayoung, bknudson, dstanek, jamielennox, morganfainberg, stevemar, gyee, henrynash, topol, marekd, lbragstad, joesavak, shardy, fabiog, fmarco76, nkinder, lloydm, shrekuma, ksavich: https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:00
lbragstaddolphm: hey18:00
henrynashhi18:00
bknudsonhi18:00
morganfainberg_Lallo18:01
*** rgrober has quit IRC18:01
dolphmi was about to say the meeting agenda is empty today18:01
morganfainberg_Ldolphm: added middleware to meeting notes just now18:01
dolphmand then morganfainberg_L went and ruined the party18:01
morganfainberg_L>.>18:01
henrynash(Henry is on a dodgy connection while on vacation is liable to go radio-silent at the drop of a hat)18:01
*** johnthetubaguy is now known as zz_johnthetubagu18:01
*** vivek-ebay has joined #openstack-meeting18:01
dolphmhenrynash: you should be radio silent already!18:01
morganfainberg_Lhenrynash: vacation and still on IRC?18:01
dolphmraise InvalidVacation('IRC')18:01
*** dstanek has joined #openstack-meeting18:02
ayoungyo18:02
morganfainberg_Ldolphm:++18:02
henrynashok, ok, I just love you guys too much...18:02
stevemaro/ o/18:02
dstaneko/18:02
*** Michalik_ has joined #openstack-meeting18:02
dolphm#startmeeting keystone18:02
openstackMeeting started Tue Jun 24 18:02:21 2014 UTC and is due to finish in 60 minutes.  The chair is dolphm. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: keystone)"18:02
openstackThe meeting name has been set to 'keystone'18:02
topolo/18:02
dolphmnothing new on the hackathon front, so:18:02
dolphm#topic Keystone Middleware Repo Created!18:02
gyee\o18:02
*** openstack changes topic to "Keystone Middleware Repo Created! (Meeting topic: keystone)"18:02
dolphmmorganfainberg_L: o/18:02
morganfainberg_LMiddleware Repo is in!18:02
ayoungnow the real work begins18:02
morganfainberg_Lall new middleware code changes should go against keystonemiddleware18:02
stevemaryay another thing to track in gerrit18:03
bknudsonso at some point it gets released18:03
dolphmmorganfainberg_L: do we have patches to move everything over?18:03
bknudsonany reason it can't be released today?18:03
ayoungwe need to deprecate keystoneclient.middleware.*18:03
morganfainberg_Lbknudson: i want to make sure we're not missing anything before we release18:03
*** bobt has joined #openstack-meeting18:03
morganfainberg_Lbknudson: but other than that no18:03
bknudsonpersonally I'd rather changes were covered by tempest before merging anything new18:03
ayoungadd to devstack18:03
*** atiwari has quit IRC18:03
morganfainberg_Ldolphm: everything should be moved over, history was preserved18:03
morganfainberg_Layoung: yes, i am going to be proposing that fix today18:04
ayoung++18:04
bknudsonI think devstack will install it once it's in requirements.txt18:04
morganfainberg_Lbknudson: tempest and stable bitrot jobs are included18:04
dolphmmorganfainberg_L: i was including that ^ in the notion of "move everything over"18:04
morganfainberg_Lbknudson: no, it needs to be sources frmo the repo, like django_openstack_auth18:04
*** harlowja has quit IRC18:04
morganfainberg_Ldolphm: ++18:04
morganfainberg_Lthe initial release will be 1.0.018:04
dolphmswapping imports in other projects as well18:04
morganfainberg_Lwe're calling this "stable" :)18:04
dolphmmorganfainberg_L: ++18:04
morganfainberg_LLP project has been created, pypi target as well18:05
morganfainberg_Ldolphm holds the keys to release (same as ksc)18:05
*** kgriffs has joined #openstack-meeting18:05
bknudsononce it's released we'd change other projects to use it?18:05
*** kgriffs has left #openstack-meeting18:05
dolphmmorganfainberg_L: let me know when to push buttons18:05
*** ramashri has joined #openstack-meeting18:05
morganfainberg_Lbknudson: we can do an alpha release and do some initial work on that18:05
bknudsony, i'd expect an alpha release18:05
dolphm#action Everyone: add openstack/keystonemiddleware to your watched projects in gerrit18:06
*** fnaval has quit IRC18:06
morganfainberg_Lbknudson: basically, everyone do a once over, make sure it looks right, i'm working on the devstack front18:06
morganfainberg_Lif there are no issues we can release an alpha (and get it in global reqs) soon18:06
morganfainberg_L#action We need tests for ec2_token middleware18:06
bknudsonhttp://git.openstack.org/cgit/openstack/keystonemiddleware/tree/18:07
bknudsonhehe18:07
morganfainberg_Lthere weren't any afaict18:07
*** samcdona has joined #openstack-meeting18:07
morganfainberg_Lso i didn't port any18:07
* ayoung takes a note that we are going to need a new RPM18:07
*** harlowja has joined #openstack-meeting18:07
*** harlowja has quit IRC18:07
morganfainberg_Li verified before the repo was created docs build worked, pep8, and py27 worked18:07
*** Demitar has joined #openstack-meeting18:08
dolphmmorganfainberg_L: proposed a change to openstack/governance https://review.openstack.org/#/c/102305/18:08
morganfainberg_Lonce we release we can deprecate all the other middlewares. I'll be retargeting bugs in LP for ksc against middleware this week.18:08
morganfainberg_Ldolphm: ++ :)18:08
*** markwash has quit IRC18:08
*** padkrish has joined #openstack-meeting18:08
*** shakamunyi has joined #openstack-meeting18:09
morganfainberg_Luh.. thats it from me :)18:09
*** lcheng has quit IRC18:09
topolso we can stop watching keystoneclient?18:10
dolphmmorganfainberg_L: danke!18:10
ayoungtopol, you can18:10
dolphmtopol: hell no18:10
ayoungheh18:10
bknudsonkeystoneclient still has the python API18:10
*** crandquist has joined #openstack-meeting18:10
stevemartopol, nope, just the middleware is being separated, still has all the library and API stuff18:10
morganfainberg_Ldolphm: i'll send a nice email to -dev mailing list today as well.18:10
dolphmwe'll have to alert packagers as well18:10
stevemarmorganfainberg, ++18:10
morganfainberg_Ldolphm: sould i x-post to main openstack list?18:11
topolso on the keystone info page someone will update so newbies can find all the repos and what is in what?18:11
dolphmmorganfainberg_L: i'd send a different note in that direction, honestly18:11
morganfainberg_Ldolphm: ok18:11
morganfainberg_Ldolphm: maybe we should wait to send there until we release18:11
dolphmmorganfainberg_L: want to etherpad both? i could contribute a bit18:11
morganfainberg_Ldolphm: ++ will do18:11
dolphmmorganfainberg_L: ++18:11
bknudsondoes keystonemiddleware have its own launchpad? (and where do bugs get reported?)18:11
topolcause we have blossomed a little :-)18:11
morganfainberg_Lbknudson: yes it does18:11
ayoung#action topol to update keystone info page18:12
dolphm#action dolphm to move bugs to https://launchpad.net/keystonemiddleware18:12
bknudsonhttps://launchpad.net/keystonemiddleware18:12
morganfainberg_Ldolphm: let me know if you want help moving bugs around18:12
topolayoung, cool. folks give me authority to do that?18:12
bknudsonno bugs in keystonemiddleware now18:12
bknudsonnice18:12
topolyep its empty18:12
topolI checked18:12
dolphmtopol: you can grant yourself that authority i believe...18:13
topolk18:13
dolphmanyone have a link to the keystone bug team thing? i can't remember what it's called18:13
topolI'll handle18:13
ayoung#action ayoung to set all keystoneclient middleware bugs to "also affects keystonemiddleware"18:13
morganfainberg_Lkeystonedrivers?18:13
lbragstad#link https://launchpad.net/~keystone-drivers18:13
stevemartopol, https://wiki.openstack.org/wiki/Keystone might want to add the keystone-specs too :D18:13
dolphmmorganfainberg_L: no, there's a public group18:13
morganfainberg_Ldolphm: oooh18:13
topolstevemar ++++18:13
morganfainberg_Ldolphm: uh18:13
*** dims_ has quit IRC18:13
*** jlibosva has quit IRC18:14
*** ajo|mac has joined #openstack-meeting18:14
dolphmi have no idea where to find it...18:14
*** dims_ has joined #openstack-meeting18:14
dolphmooh18:14
ayoungCurrent middleware bugs https://bugs.launchpad.net/python-keystoneclient/?field.searchtext=middleware&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&18:14
ayoungfield.has_no_package=18:14
*** bgorski has quit IRC18:14
dolphmanyone can join this group https://launchpad.net/~keystone-bugs18:14
ayounglet me try that again18:14
ayounghttps://bugs.launchpad.net/python-keystoneclient/?field.searchtext=middleware&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=18:14
morganfainberg_Lthe keystonedrivers group (core) should have access to update the middleware lp page as needed (Same as ksc)18:14
*** lcheng has joined #openstack-meeting18:14
morganfainberg_Ldolphm: please 2x check i don't need to "fix" anything in the lp page for middleware18:15
*** ngoswami has quit IRC18:15
morganfainberg_Li think i got it all so you/other cores can fix as needed18:15
*** Michalik_ has quit IRC18:15
dolphmmorganfainberg_L: it all looks right to me18:15
morganfainberg_Li also created 1.0.0 milestone pre-emptively18:15
*** _nadya_ has joined #openstack-meeting18:15
*** belmoreira has joined #openstack-meeting18:15
ayoungis it going to be a problem that it is keystonemiddleware and not python-keystonemiddleware?18:16
morganfainberg_Layoung: no18:16
ayoungat least, that is what launchpad calls it18:16
*** rook has left #openstack-meeting18:16
dolphmmorganfainberg_L: you actually made a 1.0.0 series... which should be a 1.x.x series18:16
morganfainberg_Ldolphm: ah lets fix that then18:16
ayoungmorganfainberg_L, than can we renamte python-keystoneclient to keystoneclient?18:16
dolphmmorganfainberg_L: done18:16
*** Michalik_ has joined #openstack-meeting18:16
ayoungNot asking to18:16
dolphmmorganfainberg_L: you can then create a 1.0.0 milestone within that series18:16
ayoungasking if it would be possible, or18:16
morganfainberg_Ldolphm: hm, looks like i can't remove a series?18:16
morganfainberg_Loh you fixed:P18:17
ayoungif something requires the python- prefix?18:17
morganfainberg_Lhaha18:17
dolphmmorganfainberg_L: maybe because i just renamed it18:17
*** otherwiseguy has quit IRC18:17
ayoungI though it was a package thing18:17
morganfainberg_Layoung: nah, otherwise keystone would need it as well18:17
*** ArthurBerezin has joined #openstack-meeting18:17
ayoungmorganfainberg_L, I guess we'll find out18:17
* gyee planning on checking in java middleware in that repo as it longer prefix with python-18:17
bknudsonayoung: someone might write a .NET client and call it .NET-keystoneclient18:18
topolkeystone client will eventually be depracted via openstack client correct?18:18
bknudsonunix folks would never see it18:18
morganfainberg_Ltopol:  the CLI18:18
morganfainberg_Ltopol:  not the library part18:18
gyeetopol, that's the rumor18:18
dolphmi know someone has implemented c++ middleware for keystone18:18
bknudsonwell, maybe the openstacksdk will make it useless18:18
ayoung2 bugs now18:18
topolbut the library is now going into middleware or am I confused as usal/18:19
morganfainberg_Lin theory, we could have non-python middleware in that repo eventually.18:19
dolphmand rackspace has a java version http://openrepose.org/18:19
bknudsonthen we also have the cms code in python-keystoneclient18:19
dolphmbknudson: i think we need a python-keystonelib package for cms...18:19
ayoungwe are not targetting python 2.6 for middleware, correct?18:19
morganfainberg_Layoung: middleware is the same as ksc18:20
morganfainberg_Layoung: we haven't dropped 2.6, therefore we can't drop it here18:20
ayoungmorganfainberg_L, OK18:20
dolphmthere was a summit session on 2.6 - does anyone know the outcome?18:20
morganfainberg_Ldolphm: suse was the one up in the air still18:20
dstanekdolphm: on dropping 2.6? i heard that we can't because of a linux distro18:21
morganfainberg_Ldolphm: everyone else was ok with dropping 2.6, long term 2.6 support will last until we EOL the last of the releases that had 2.6 support18:21
dolphmi don't see a summit etherpad on the topic18:21
ayoungI think that RH has pulled the requirement18:21
ayoungwe have "collections" now which lets us run python >2.6 for openstack18:21
dolphmso where is suse at on support?18:21
*** pfallenop has quit IRC18:21
*** ArthurBerezin has left #openstack-meeting18:21
morganfainberg_Ldolphm: my guess is K will be where we drop 2.618:21
dstanekdolphm: https://etherpad.openstack.org/p/juno-cross-project-future-of-python18:22
dolphmdropping 2.6 support would be a huge advantage for the gate18:22
morganfainberg_Ldolphm: gate will still need to support 2.6 for EOL purposes18:22
dolphmdstanek: thanks!18:22
dstanekyes, they said that they'll have a very long time before they get rid of the gate support18:22
dolphmmorganfainberg_L: only on stable/ though, right?18:22
*** atiwari has joined #openstack-meeting18:23
morganfainberg_Lright18:23
morganfainberg_Lmiddleware likely will need to remain 2.6 compat until we drop the last 2.6 capable release to EOL18:23
morganfainberg_L(likely Juno will still be 2.6 compat)18:23
dolphmwell, then nothing to get excited about for now18:23
dolphm#topic open discussion18:23
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:23
ayoungmorganfainberg_L, but that would be the old packages18:24
ayoungnot keystonemiddleware18:24
*** yfried_ has quit IRC18:24
ayoungjust python-keystoneclient18:24
morganfainberg_Layoung: if juno is 2.6 compatible, middlware will need to keep it since we'll be adopting the new packaging this cycle18:24
ayoungmorganfainberg_L, we are going to need to keep the existing packageset for older releases18:24
morganfainberg_Layoung: yep. clients will be in the same boat18:25
ayoungOK, so we'll get 2.6 as a req that way18:25
dstanekdolphm: publish your secret reviewday support when you have a chance - i'd love to start trying it out18:25
*** fnaval has joined #openstack-meeting18:25
dolphmdstanek: lol ++18:25
*** jmontemayor has joined #openstack-meeting18:26
*** harlowja has joined #openstack-meeting18:26
*** harlowja has quit IRC18:26
bknudsonany specs we think are ready to go in?18:26
bknudsonif we don't get any specs in then this is going to be a pretty small release18:26
*** armax_ has joined #openstack-meeting18:26
stevemari'd like to appeal to folks to review https://review.openstack.org/#/c/100023/ -> 'federating multiple keystone', it's getting kind of ugly and complicated18:26
*** harlowja has joined #openstack-meeting18:26
*** harlowja has quit IRC18:26
morganfainberg_Ldolphm: https://etherpad.openstack.org/p/dev_keystonemiddleware_anouncement18:27
*** _nadya_ has quit IRC18:27
stevemarmorganfainberg, your etherpad is rather empty18:27
*** harlowja has joined #openstack-meeting18:27
*** harlowja has quit IRC18:27
morganfainberg_Lstevemar: shush18:27
kwssstevemar, I'd like to ask a question about that18:27
morganfainberg_L:P18:27
*** _nadya_ has joined #openstack-meeting18:27
stevemarkwss ! go ahead18:27
*** armax has quit IRC18:28
*** armax_ is now known as armax18:28
kwssWill keystone to keystone federation use the same mapping / attribute trust mechanisms as saml2 etc.?18:28
dstanekstevemar: yes, i want to go over that again today - started looking yesterday after jsavak pushed18:28
bknudsongood question18:28
*** vjay2 has quit IRC18:28
*** caleb_ has quit IRC18:28
morganfainberg_Lkwss: very good question18:28
*** harlowja has joined #openstack-meeting18:28
*** harlowja has quit IRC18:28
gyeeI don't see why not18:29
dolphmstevemar: ugly and complicated sounds like you have work to do before appealing to reviewers :P18:29
dstanekkwss: i think it should18:29
*** harlowja has joined #openstack-meeting18:29
*** harlowja has quit IRC18:29
kwssme too18:29
dstaneki don't see the difference between k2k and federation18:29
gyeedstanek, exactly18:29
*** harlowja has joined #openstack-meeting18:29
*** harlowja has quit IRC18:29
stevemardolphm, actually, i wanted you to weigh in on it, its growing too big, there are too many use cases being proposed18:29
*** jmontemayor has quit IRC18:30
dolphmstevemar: that's the danger with federation it seems - need to narrow the use case that we pursue to ONE, and ensure that we're making room to support the rest later18:30
dolphmayoung: wow, thanks for moving bugs over18:32
*** sarob has quit IRC18:32
kwssI think that all protocols should use the same common mechanisms18:33
bknudsonkwss & others: https://review.openstack.org/#/c/100279/ -- this spec looks like a good to me!18:33
morganfainberg_Layoung: i think session tokens are important if we can shore that spec up.18:33
*** ajo|mac has quit IRC18:33
ayoungmorganfainberg_L, wilco18:33
morganfainberg_Lbknudson: that one looks close.18:33
dstanekstevemar: all of the use cases i have seen are very similar18:33
*** tris has joined #openstack-meeting18:33
morganfainberg_Lbknudson: at the very least like a decent idea with a lot of thought put into it18:33
stevemarkwss, so both keystone instances should be running something like mod_shib to talk to each other?18:33
bknudsonmorganfainberg_L: I think it exposes that we've got a security issue in idps18:33
morganfainberg_Lbknudson: we do.18:33
bknudsonmorganfainberg_L: more like an issue of trusting too much18:33
*** brich1 has joined #openstack-meeting18:33
*** jecarey has quit IRC18:33
morganfainberg_Lbknudson: ++18:33
stevemarbknudson, only when using regex ?18:33
bknudsonstevemar: y, the regex18:33
morganfainberg_Lbknudson: if we can narrow that down to be more restrictive it would def. be good18:33
*** jmontemayor_ has joined #openstack-meeting18:33
*** marcoemorais has quit IRC18:33
kwssstevemar, the actual communication between the two servers is a separate issue, I meant the same mechanisms are handling mapping / authorization18:33
ayoungdolphm, yeah...pretty easy once I got rolling18:33
*** marcoemorais has joined #openstack-meeting18:34
ayoungsome of those will end up falling squarely on one side or the other18:34
*** harlowja has joined #openstack-meeting18:34
*** harlowja has quit IRC18:34
dolphmayoung: ++ i'm copying statuses over on the ones you're marking as affecting keystonemiddleware18:34
*** sarob has joined #openstack-meeting18:34
stevemarkwss, if we can re-use them, then sure18:34
ayoungdolphm, it does mean that all reafactorings from auth_token middleware to keystoneclient will start with adding code to the client, and then a second review to remove from the middleware18:34
ayoungdolphm, ++18:34
bknudsonayoung: I think there's no more changes to keystoneclient middleware except for security fixes18:35
*** henrynash has quit IRC18:35
morganfainberg_Lbknudson: ++18:35
*** ramashri has quit IRC18:35
dolphmbknudson: we can't just do an import from keystonemiddleware ?18:36
*** ramashri has joined #openstack-meeting18:36
stevemarkwss, you mean the mapping engine, and leveraging groups and roles?18:36
ayoungbknudson, right.  I'm talking about the keystonemiddleware version.  Now that the middleware is split from the client, and since we still have more refactoring to do, we will have to split reviews over both repos18:36
bknudsondolphm: no, circular dependency!18:36
morganfainberg_Layoung:  yes.18:36
kwssstevemar, what I'd like to see is a flow which is separated into protocol dependent i.e keystone to keystone communication and protocol independent (mapping etc.) operations18:36
morganfainberg_Layoung: and changes to client need a release before they can really be consumed by the middleware18:37
stevemarkwss, i'd love to see that too! but I can't seem to get passed the darn use cases right now18:37
topoltoo many use cases :-(18:37
dolphmbknudson: that's why i'd like to have keystonelib18:37
kwssstevemar, yea and hopefully trusted attribute filter too18:37
stevemarkwss, topol too many voices (in my head and in the review)18:37
morganfainberg_Ldolphm: i'd be happy to do the same work to split the stuff out if we can identify what we want split18:38
topolstevemar +++ what do you recommend18:38
morganfainberg_Ldolphm: it's not hard (just timeconsuming)18:38
kwssstevemar, what can I do to help?18:38
dolphmmorganfainberg_L: off the top of my head, i'm only aware of keystoneclient.common.cms18:38
morganfainberg_Ldolphm: session?18:38
*** harlowja has joined #openstack-meeting18:39
*** harlowja has quit IRC18:39
stevemarkwss, in line comments in the review, and if you have time, can we chat after?18:39
dstanekstevemar: i'm sorta interested in the higher level usecase - be able to federate keystones just like anything else18:39
dolphmmorganfainberg_L: hmmmmmmm18:39
ayoungmorganfainberg_L, ooh. that is going to be painful.  middleware will only test against a released version of the client18:39
morganfainberg_Layoung: yep18:39
kwssstevemar, sure to both, I'll point David at the review too18:39
dstanekstevemar: we seem to be making this too complicated18:39
morganfainberg_Layoung: though i can work aroudn that in devstack with a little magic18:39
morganfainberg_Layoung: i'll be putting those reviews up today.18:40
stevemardstanek, that was my comment about ugly and complex18:40
*** harlowja has joined #openstack-meeting18:40
*** harlowja has quit IRC18:40
stevemarthough craig has a good point about the terminology, we're not being consistent right now18:40
morganfainberg_Ldolphm: if sesson and cms were not in ksc (and then auth plugins?) then we could avoid a lot of circular deps18:41
topolcould we cut federation down to 2 primary use cases?18:41
dstanekstevemar: what is the timeline to get this approved? it seems like a good discusson for the hackathon18:41
topoland stay focused?18:41
morganfainberg_Ldolphm: though i'd really want to talk to jamielennox before we try to split that stuff out18:41
dolphmtopol: that would be nice :)18:41
dolphmmorganfainberg_L: ++18:41
dolphmmorganfainberg_L: if the use case for cms is agreeable, i can create a spec for just that, and we can go case by case?18:42
morganfainberg_Ldolphm: but it would likely make other clients consuming session and auth plugins waaaay easier18:42
*** ivar-lazzaro has joined #openstack-meeting18:42
stevemartopol, i think that is a good idea18:42
bknudsonmy opinion was that we should remove the keystonemiddleware dependency from keystoneclient and do the imports18:42
bknudsonit's essentially optional18:42
*** harlowja has joined #openstack-meeting18:42
stevemari'm a fan of the bursting one18:42
dolphmbknudson: ? long term or immediately?18:42
stevemardstanek, i was really hoping to have this approved or near approved for the hackathon18:42
dstanektopol: agreed, but i think all of the uses cases should be captured and then we can generalize that in the spec say exactly which ones will be focused on18:42
morganfainberg_Lbknudson: so if middleware is available import?18:43
stevemardstanek, ++18:43
bknudsondolphm: I think we'd need to give it some small amount of time18:43
topolwe always have another release, another hackathon in SAT, unless dolphm runs out of good restaurants to take us too18:43
dolphmbknudson: sure18:43
morganfainberg_Lbknudson: and remove the middleware in ksc completely?18:43
bknudsonmorganfainberg_L: no need to check if it's available... paste isn't going to start with it.18:43
dstanektopol: we need to start having them at a beach18:43
morganfainberg_Lbknudson: ok i'm confused.18:43
*** bdpayne_ has joined #openstack-meeting18:43
morganfainberg_Lbknudson: explain it like i'm 5 :P (ugh, i feel fogged today)18:44
topoldstanek, shame.  we come to SAT to get things done, not see you in your speedo :-)18:44
bknudsonmorganfainberg_L: no, ksc still does the imports18:44
stevemartopol, nice visual18:44
bknudsonmorganfainberg_L: the middleware is only used if you put it in your paste pipeline18:44
morganfainberg_Lright18:44
bknudsonit's not used if you're just making use of the client18:44
morganfainberg_Lso keystoneclient.middleware imports keystonemiddleware?18:44
bknudsonso regular apps aren't going to fail if they don't have the middleware around18:44
morganfainberg_Lbut there isn't a dep to install keystonemiddleware explicitly18:45
morganfainberg_L?18:45
dolphmdstanek: hawaii?18:45
bknudsonmorganfainberg_L: right. no middleware in ksc requirements18:45
ayoungI think that might be going too far18:45
topolI can get myself approved for hawaii but probably not everyone else :-(18:45
ayoungwe need to package up  keystonemiddleware anyway18:46
*** bdpayne has quit IRC18:46
dolphmit's the easiest way to include both the US and australia18:46
dstanekdolphm: sounds great!18:46
dolphmi mean, it's only logical18:46
*** novas0x2a|laptop has joined #openstack-meeting18:46
ayoungand doing that implies a bunch of changes beyond the paste change18:46
lbragstadI +1 that logic18:46
*** ivar-lazzaro has quit IRC18:46
morganfainberg_Lbknudson: that would break some EOL releases with new keystoneclient releases though18:46
morganfainberg_Lbknudson: that was my only real concern. and grizzly is widely used18:46
* topol face palm trying to get hawaii approvals...18:46
ayoungyeah18:46
stevemari see how it is, henrynash and I aren't even included18:46
ayoungtoo much to break18:46
dstanektopol: don't worry i'll have my speedo in SAT - i'll wear it for casual Friday18:46
morganfainberg_Lbknudson: it's why the spec opted for sec-maintenance for the middleware in ksc18:47
bknudsonmorganfainberg_L: y, it wouldn't affect us since we don't package that way18:47
topoldstanek, I'll have to skip lunch to be safe then :-)18:47
morganfainberg_Lbut people do use newer clients with older services18:47
* dolphm hackathon update: for everyon's own safety, do not show up on friday18:47
morganfainberg_Ldolphm: ?18:47
bknudsonfri the week before?18:48
topoljoke18:48
morganfainberg_Loh oh18:48
bknudsonis there a gun show?18:48
morganfainberg_Ldamn it18:48
dstaneklol18:48
ayoungOk,  any thoughts on this:  is there anyway to to endpoint binding of tokens without endpoints knowing their own ids?18:48
lbragstadlol18:48
dolphmmorganfainberg_L: dstanek's gun show featuring speedos18:48
* morganfainberg_L facepalms18:48
*** HenryG has joined #openstack-meeting18:48
morganfainberg_Li uh...18:48
bknudsonI assume we're allowed to open carry there?18:48
morganfainberg_Lno18:48
lbragstadsuns out guns out?18:48
dolphmbknudson: conceal only in texas18:48
*** ajo|mac has joined #openstack-meeting18:49
gyeeayoung, sure, each endpoint have their own unique cert/private key18:49
ayounggyee, nope18:49
gyeejust encrypt the toke for that endpoint only18:49
ayoungthat doesn't work for multi18:49
ayoungso token is for 3 endpoints only18:49
ayoungthat only works for one specific endpoint18:49
gyeeyou issue the token for that endpoint only18:49
gyeeso encrypting it with the endpoint's public key18:50
ayounggyee, that is a lot of infrastrucutre18:50
gyeeayoung, but arn't we pushing PKI already?18:50
ayoungand it seems like a misuse of crypto.  THere is nothing wrong with othser services seeing the token contents18:50
morganfainberg_Lbknudson: largely speaking, you can use 0.9.0 keystoneclient (and middleware) as far back as you want as long as you configure it correctly18:51
gyeewhy, if that token is only good for that particular endpoint18:51
topollbragstad... its in the constitution son18:51
ayounggyee, and, really, that is just replace "endpoint id" with "endpoint keypair"18:51
dolphmit also lets endpoints share keys, which seems totally reasonable18:52
bknudsonmorganfainberg_L: y, and you need to start installing all the new deps for 0.9.0... good luck!18:52
gyeedolphm, sure, PKI is made for that stuff18:52
ayoungdolphm, shared keys does not seem reasonable to me18:52
*** julienvey has quit IRC18:52
ayoungyou'd have to share a private key18:52
morganfainberg_Lbknudson: hm. how far have the deps changed (conflicted) since say... grizzly release (assuming no one uses folsom)18:52
ayoungwhich is generally frowned upon18:52
gyeemultiple instances of an endpoint?18:52
dolphmayoung: if i deploy two services on the same node, i'm might not care that they share private keys, etc18:53
dolphmayoung: or like glance api and glance registry, for example18:53
gyeesure multiple instances of an endpoint have to share the same keys18:53
ayoungmy thought, though, is that if we need to give each endpoint an identity of some sort, then maybe we use that identity for fetching policy after all18:53
ayoungI really don't want to build that infrastructure unless it is well justified18:53
ayoungI don't think it is yet18:54
*** lsell has joined #openstack-meeting18:54
gyeeendpoints should have an identity anyway18:54
ayounggyee, why not the service users18:54
ayoungthat seems to make more sense18:54
*** crandquist has quit IRC18:54
*** hashar has joined #openstack-meeting18:54
ayoungbut we can't bind a token to a service user18:54
gyeethey can use the service identity sure18:54
ayoungactually, we totally could18:54
gyeebut an identity can have multiple keys18:54
bknudsonmorganfainberg_L: our issue is that we need to go through legal to get new packages approved18:54
ayoungtoken { "service_user":"keystone"}  means only the keystone service user should treat the token as valid18:55
gyeeendpoint-scope and service-scope, killing two birds with one stone18:55
dolphmwhy can't all users just have keys?18:55
ayoungbut we'd need that information when we issued the token.  And there is no link in keystone between the service users and the endpoiints yet18:55
gyeeapologize to the animal lovers18:55
*** lsell has left #openstack-meeting18:55
ayoungwe don't need PKI for this18:56
dolphmand then all everything barbican everywhere18:56
*** julienvey has joined #openstack-meeting18:56
*** krtaylor has quit IRC18:56
ayoungwe just need to identify who can use the token18:56
morganfainberg_Lbknudson: aren't you going to have to do that anyway even with what you're proposing?18:56
*** nibalizer has joined #openstack-meeting18:56
*** achanda has quit IRC18:56
gyeedude, we are using PKI tokens already!18:56
gyeemake it count18:56
bknudsonmorganfainberg_L: well, we handle new releases, but old releases use old client. we're not affected18:56
ayounggyee, we have one service that requires tokens,  not everywhere18:56
ayounglets not build things just to build them18:57
gyeeayoung, I mean the framework is already there18:57
ayoungpeople get lynched that way18:57
gyeejust make use of it18:57
ayoungno, it really is not18:57
ayoungI mean, I like PKI as an option18:57
ayoungjust not a hard requirement, for the endpoint to validate to keystone18:57
*** hrybacki has joined #openstack-meeting18:57
gyeeI think PKI is a great option for this stuff18:57
*** jdob has quit IRC18:57
ayounggyee, option, yes18:57
ayoungrequirement, not18:57
morganfainberg_Lstill don't see how that really affects things here. i'm thinking from the standpoint of a couple companies i know that use latest *client* + grizzly services and breaking their deployment with the next ksc relese would be ugly18:57
ayoungand, it is beside the point18:58
*** jdob has joined #openstack-meeting18:58
ayoung the issue is not PKI or no PKI18:58
*** baoli_ has joined #openstack-meeting18:58
*** mugsie has joined #openstack-meeting18:58
gyeeI though you ask how to make the stuff work18:58
bknudsonmorganfainberg_L: they can't install keystonemiddleware?18:58
*** ianw has joined #openstack-meeting18:58
*** baoli_ has quit IRC18:58
ayoungthe issue is "do we use the endpoint id for policy fetch"  and "do we use the endpoint id for token binding"18:58
ayoungif not, then what do we do18:58
morganfainberg_Lthey can, but i am not seeing a compelling argument to break them?18:58
* dolphm 1 min18:59
*** baoli_ has joined #openstack-meeting18:59
*** jtomasek has joined #openstack-meeting18:59
ayoungand I think the policy fetch is leaning toward "use the service users context"18:59
morganfainberg_Lbknudson: i might be missing the point of ripping it out in a hurry18:59
*** julienvey has quit IRC18:59
morganfainberg_Lthats all18:59
*** jcoufal has joined #openstack-meeting18:59
morganfainberg_Ltalk morein -keystoen after meeting18:59
gyeeayoung, service account should be fine, services owns the endpoints anyway18:59
bknudsonmorganfainberg_L: we can take as long as we think is prudent19:00
dolphm#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Jun 24 19:00:24 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-06-24-18.02.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-06-24-18.02.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-06-24-18.02.log.html19:00
*** dstanek has left #openstack-meeting19:00
*** brich1 has quit IRC19:00
anteayao/19:00
jeblairinfra folks around?19:00
SergeyLukjanovo/19:00
*** baoli has quit IRC19:00
*** krtaylor has joined #openstack-meeting19:01
*** kwss has quit IRC19:01
*** morganfainberg_L has quit IRC19:01
fungiheyo19:01
jeblairmaybe there will not be a quorum and i can eat lunch without getting crumbs in my keyboard...19:01
*** morganfainberg_L has joined #openstack-meeting19:01
krotscheckEh? wha?19:01
clarkbo/19:01
krtayloro/19:01
*** morganfainberg_L has quit IRC19:02
*** morganfainberg_L has joined #openstack-meeting19:02
ianwo/19:02
jeblairoh well, here we go then ;)19:02
*** yamahata__ has joined #openstack-meeting19:02
nibalizero/19:02
jeblair#startmeeting infra19:02
openstackMeeting started Tue Jun 24 19:02:34 2014 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:02
jeblairagenda ^ (full)19:02
*** padkrish has quit IRC19:02
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-06-17-19.01.html19:02
jeblairlast meeting ^19:03
*** yamahata_ has quit IRC19:03
jeblair#topic  Actions from last meeting19:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:03
ttxo/19:03
jeblairjeblair and clarkb if feeling better to upgrade jenkins timeout plugin starting june 1819:03
*** vivek-ebay has quit IRC19:03
clarkbI completed that yesterday19:03
jeblairand then some19:03
jesusauruso/19:03
*** sarob has quit IRC19:03
*** Michali__ has joined #openstack-meeting19:03
bcrocheto/19:03
*** Michalik_ has quit IRC19:03
jeblairzaro: so your change that depends on that should be able to proceed19:04
clarkbzaro: can you make a point of bugging me to merge the puppet chagnes asssociated iwth that?19:04
*** sarob has joined #openstack-meeting19:04
jeblairand clarkb is also proceeding with the trusty upgrade19:04
clarkbwe need to merge the changes that update the plugin versiosn in puppet and the job updates to use the new version of the plugin19:04
jeblairon a related note, there are pending changes to remove the last of envinject usage, then we can yank that plugin as well19:04
jeblair#topic  F20 jobs (ianw 24/6)19:05
*** openstack changes topic to "F20 jobs (ianw 24/6) (Meeting topic: infra)"19:05
jeblairianw: you have the floor!19:05
ianwhi, not sure if anyone noticed, but redhatci was very unstable19:05
ianwturns out it was all due to a RHOS issue https://bugzilla.redhat.com/show_bug.cgi?id=111206819:05
uvirtbotianw: Error: Could not parse XML returned by bugzilla.redhat.com: HTTP Error 404: Not Found19:05
ianwredhatci is also a good dog-fooding thing for us19:06
ianwbut hopefully i can turn that back on soon19:06
ianwto the f20 jobs, the blocker is the nodepool allocation issue19:06
ianwi've gotten https://review.openstack.org/#/c/101110/ (Track last allocations to ensure forward-progress) into shape for review19:07
*** sarob_ has joined #openstack-meeting19:07
clarkbcool /me adds that to review list19:07
ianwprobably jeblair is the main person, but if there are any big issues with the approach, i'd like to know19:07
SergeyLukjanovme too19:07
*** vinod1 has joined #openstack-meeting19:08
jeblairinterestingly enough, we basically haven't had any nodepool contention for the past week, until this morning19:08
*** _nadya_ has quit IRC19:08
*** hrybacki has left #openstack-meeting19:08
*** sarob has quit IRC19:09
jeblairnow there are a lot of nodes in the delete state; we should check on that19:09
*** ramashri has quit IRC19:09
*** jdob has quit IRC19:09
jeblairianw: thanks for working on that; i think we'll probably just follow up in the review at this point19:09
*** jdob has joined #openstack-meeting19:09
*** moha_hunt has joined #openstack-meeting19:09
jeblairunless there are any other aspects we should discuss now19:09
jeblair?19:10
ianwok, sounds good.  that's it for me19:10
jeblair#topic  Request for comments on the horizon split plan (rdopiera)19:10
*** openstack changes topic to "Request for comments on the horizon split plan (rdopiera) (Meeting topic: infra)"19:10
jeblairis this old?19:10
anteayaI think so?19:10
anteayaI could never find out for sure19:10
anteayaand I don't know who has the next itme19:10
jeblairyes, this one is old19:11
jeblair#topic  Designate repository renames (stackforge -> openstack)19:11
*** openstack changes topic to "Designate repository renames (stackforge -> openstack) (Meeting topic: infra)"19:11
*** ildikov has joined #openstack-meeting19:11
KiallHeya :)19:11
jeblairdesignate is incubated now19:11
*** jang1 has joined #openstack-meeting19:12
jeblairso we should move it to openstack/19:12
*** bobt has quit IRC19:12
*** mrunge has quit IRC19:12
fungii'm pretty well open to work on a project rename batch any time between now and darmstadt19:12
KiallSo - I had a Q or 2 related to renaming the projects.. First was scheduling the rename, and the second was what can we expect to explode (e.g. I've seen some if org == 'openstack':'s in the code..)19:12
KiallThe second is probably more of a non-meeting time Q, but worth a quick mention :)19:13
jeblairKiall: when we do that, all the changes will move over, but devs will need to update their git remotes -- that's the main point of disruption19:13
jeblairKiall: we usually do renames on friday afternoons or weekends -- any time/date that's particularly good or bad for you?19:13
*** vivek-ebay has joined #openstack-meeting19:13
jeblairKiall: (it's a 15 minute downtime for all of gerrit, so that's the primary scheduling motivator)19:14
KiallIdeally, I'd like to be around, so the US morning on a weekend seems reasonable19:14
*** padkrish has joined #openstack-meeting19:14
Kiall(US morning so it's not 3am or something for me!)19:14
zaroo/19:15
KiallRe date, the sooner the better IMO.19:15
*** dims_ has quit IRC19:15
fungiif it needs to be before the north-american west-coasters are awake, i'm happy to take point on it (well, i'm happy to regardless)19:16
*** dims_ has joined #openstack-meeting19:16
*** ayoung has quit IRC19:16
*** vivek-ebay has quit IRC19:16
*** lsell has joined #openstack-meeting19:16
*** vivek-ebay has joined #openstack-meeting19:16
Kiallfungi: west coast before midday works for me, I live in Ireland, but work with the Seattle office.. So I'm used to that ;)19:16
clarkbthis next weekend is hard for me19:16
clarkbI am doing thing19:16
jeblairi can do saturday at 1600 utc... fungi if you want to volunteer for ealier i'm not going to object ;)19:17
jeblairactually, if clarkb isn't around anyway, i can go ahead and commit to 150019:17
fungii'm fine with 1600utc if it means more of us around to fix whatever i accidentally break ;)19:17
*** fawadkhaliq has quit IRC19:17
fungior 150019:17
KiallThat sounds good to me19:17
Kiall(either 15 or 1600 UTC)19:17
clarkbI can do weekend after easy enough though19:17
clarkbwill nurse post 4th hangover19:18
clarkband be lazy >_>19:18
* SergeyLukjanov can help with renaming patches and side effects q.19:18
fungiheh19:18
jeblairyeah, i don't really want to do this wknd after19:18
jeblairSergeyLukjanov: cool19:18
jeblair#agreed rename designate (and bash8) saturday 1500 UTC19:18
*** Michali__ has quit IRC19:18
jeblairi'll send an announcement19:18
KiallGreat - Thanks guys :)19:18
clarkbwfm19:18
jeblairKiall: np, thank you!19:18
fungilooked like we also had murano projects to move to the attic?19:18
SergeyLukjanovok19:18
SergeyLukjanovfungi, yup19:19
fungithough i guess we could wait until we get to those on the agenda19:19
SergeyLukjanovI think ruhe could talk about it19:19
ruheo/19:19
jeblair#topic  Deprecate deprecated Murano projects (move to attic or completely remove?) [ruhe]19:19
*** openstack changes topic to "Deprecate deprecated Murano projects (move to attic or completely remove?) [ruhe] (Meeting topic: infra)"19:19
*** vinod1 has left #openstack-meeting19:19
jeblairsince we're here...19:19
SergeyLukjanovheh, agenda wiki page is still loading for me :(19:19
anteayayup19:19
*** jackib has quit IRC19:19
ruhejeblair: thanks19:19
ruheseveral murano repositories were deprecated after we merged functionality into stackforge/murano. they have nothing but a readme file with a deprecation notice.19:19
*** flaper87|afk is now known as flaper8719:20
fungiand the answer is... move to attic since we don't delete projects ;)19:20
ruhei see two options: 1) remove them completely (and preserve history somewhere in github), 2) move them to attic, but afaik current attic is only for projects from openstack group (not for stackforge projects)19:20
*** imsurit has quit IRC19:20
ruhefungi: is attic for all projects, or just those from openstack group?19:20
fungioh, i see. this comes back to the need for a stackforge-attic19:20
SergeyLukjanovwe could make a stackforge-attic too IMO19:20
jeblairor 3) just set them to read-only and leave in stackforge19:20
SergeyLukjanovwe have some dead projects in stackforge19:21
ruhejeblair: sometimes they confuse newcomers, that's why we wanted to get rid of them19:21
jeblairthe main reason to have an openstack attic is so that when people look at the "openstack" org in github, they only see real live openstack projects...19:21
fungithat also seems like a fine option (i was in favor of doing that for openstack deprecated projects too, fwiw)19:21
SergeyLukjanovjeblair, it's an option too, but it could be a bit frustrating for newcomers19:21
jeblairi'm not sure the same thing is true for stackforge?  it seems like ruhe and SergeyLukjanov think so :)19:21
*** Sukhdev has joined #openstack-meeting19:22
fungiwell, if the project had a final commit which removed all files except for a readme with a deprecation "we have moved" notice, i don't think that should be too frustrating for newcomers19:22
jeblairanyone else with opinions?19:22
anteayaI have no opinion, the only stackforge project I have interacted with is gertty19:22
SergeyLukjanovjeblair, I see stackforge like our one more our org19:22
SergeyLukjanovand IMO it's good to keep it clean19:22
SergeyLukjanovjeblair, but I'm agreed that it's not so important as keeping clean github.com/openstack19:23
anteayaso I don't know how stackforge contributors think19:23
ruhethere is also MRaaS, which seems to be dead. and might confuse people about MRaaS vs Sahara19:23
jeblairokay, i won't try to argue that we keep it "dirty", so i guess we can move them to the attic19:24
jeblairthe stackforge-attic19:24
jeblairwhich i just made on github19:24
*** ajo|mac has quit IRC19:24
SergeyLukjanov:)19:24
jeblairruhe: are those projects ready to move now?19:25
ruhejeblair: yes19:25
*** hemna__ has joined #openstack-meeting19:25
jeblairokay, so we can move them on saturday then with the other renames19:25
fungisounds good19:25
SergeyLukjanovjeblair, would we like to collect list of completely dead projects on stackforge?19:25
SergeyLukjanovlike mraas19:25
clarkbSergeyLukjanov: that is probably not a bad idea19:25
fungiSergeyLukjanov: that might be hard to identify without input from their core review teams19:26
clarkbif for no other reason to get an idea of how prevalent it is19:26
fungibut is possibly worth pursuing19:26
Kiallfungi: maybe 6 months no commits or something?19:26
Kiall(or pick a number...)19:26
ruhejeblair: cool. i can create needed patches (in cases if they're needed) using SergeyLukjanov's help, since i have him in the same room :)19:26
*** bdpayne_ has quit IRC19:26
fungiKiall: i don't want to rule out the possibility that a project can be "finished" and not have any reported bugs/fixes or new features needed19:26
jeblairKiall: we'll exclude any projects that don't get commits from 6 months and have Donald Knuth as a core reviewer. ;)19:26
fungihah19:27
SergeyLukjanov:)19:27
Kialllol19:27
*** bdpayne has joined #openstack-meeting19:27
KiallWell, 6 months might be a list, rather than shortlist :)19:27
*** SumitNaiksatam has quit IRC19:27
jeblair#topic  What server for devstack.org documentation? (anteaya)19:27
fungi6 months of inactivity might make for a good list of core review teams to follow up with at least19:27
*** openstack changes topic to "What server for devstack.org documentation? (anteaya) (Meeting topic: infra)"19:27
anteayahi19:27
jeblairfungi: ++19:28
anteayadtroyer has the docs in devstack now19:28
anteaya#link https://review.openstack.org/#/c/101668/19:28
jeblairoh neat19:28
anteayamerged yesterday19:28
anteayaso now we just need a job to publish them somewhere19:28
SergeyLukjanovI'll review the list of stackforge projects to find persons who we'd like to contact about removing repos from stackforge19:28
anteayaunfortunately our meeting is a hard time for dtroyer to make19:29
anteayaso we need something like puppet to run build_docs19:29
jeblairanteaya: has the domain been moved yet?19:29
anteayaand publish19:29
anteayadtroyer says he wants the server first19:29
*** jergerber has joined #openstack-meeting19:29
anteayaand I know you want the domain name first19:29
jeblairer19:29
*** sarob_ has quit IRC19:29
anteayaand I have seen no action on the domain name19:29
jeblairi think the domain should be _transferred_ first19:29
anteayaso I don't know what to do19:29
anteayayeah, I know that19:29
jeblaircontinuing to point to gh-pages19:29
anteayaahd dean can't come to infra meetings19:30
anteayaso I do't know what to do next19:30
jeblairthen we can publish the docs, then point the domain at the new location19:30
*** sarob has joined #openstack-meeting19:30
anteayaright19:30
anteaya_I_ know that19:30
anteayabut I can't seem to convince dtroyer19:30
anteayaso what to do next?19:30
jeblairbecause, honestly, that's the hard part of this -- that's the part that people have said they wanted to do for like a year, but nothings happening19:31
anteayaright19:31
anteayaI have an email out, I have seen no action19:31
anteayaI talked to dtroyer19:31
anteayahe wants the server first19:31
*** harlowja has quit IRC19:31
*** marcoemorais has quit IRC19:31
jeblairit's not his domain name19:31
anteayahe says don't worry about the domain name19:31
jeblairit's jesse andrews19:31
anteayatrue, it isn't19:31
anteayacorrect19:31
*** marcoemorais has joined #openstack-meeting19:32
anteayajeblair: can you talk to dtroyer?19:32
*** marcoemorais has quit IRC19:32
jeblairanteaya: sure?19:32
anteayaI have asked him to come to infra meetings, he can't come19:32
anteayathanks19:32
*** marcoemorais has joined #openstack-meeting19:32
fungiis the plan a rackspace cloudsites server for now? if so, i think we may not be able to add one for devstack.org until the domain is hosted on rackspace's nameservers? (unless we pick some other name and set up an alias later)19:32
jeblairfungi: i'm not sure it's even worth making a detailed plan until the domain is transferred, but yeah, we could do cloud sites, or something on static.o.o19:33
anteayaright now we just need a server with apache to server static html files19:33
*** sarob_ has joined #openstack-meeting19:33
anteayahe didn't mention needing cloudsites19:33
*** jasondotstar has quit IRC19:33
fungiotherwise "server first" is a little irrelevant, since it would be a different "server"19:33
*** rockyg has joined #openstack-meeting19:33
anteayamostly he wants a script to run the build_docs job19:33
anteayawhich I do think puppet can fire19:34
jeblairi think our options are: transfer ownership of the domain, then move the site.  or deprecate the domain and host the docs at docs.o.o/devstack19:34
jeblairanteaya: jenkins will run it19:34
annegent_o/19:34
anteayagreat19:34
fungii'm more in favor of the latter anyway (and have devstack.org just serve as a redirect)19:34
annegent_I'd rather not increase the scope of docs further all the time19:34
jeblairfungi: yeah, that still needs to be foundation owned though19:34
funginot necessarily docs.o.o/devstack specifically, but somewhere on an existing site19:34
clarkbannegent_: I don't think it is a scope incrase.19:34
*** dhellman_ has joined #openstack-meeting19:35
*** sarob has quit IRC19:35
clarkbannegent_: it would just host the docs for that project like we host docs for all other projects19:35
reedi have asked Jesse and Soo multiple times, in real life, too... I will ask more19:35
reeds/more/again19:35
jeblairanteaya: annegent_ sorry, i meant http://docs.openstack.org/developer/devstack19:35
jeblairannegent_: so yeah, not intending to increase scope19:35
annegent_clarkb: jeblair: I guess I'm ok with /developer/devstack19:35
*** achanda has joined #openstack-meeting19:35
fungiannegent_: something similar to the developer reference content we currently publish for the python clients, presumably19:35
anteayareed: dtroyer said he had asked jesse and jesse had said yes19:35
anteayareed: I don't get the feeling there needs to be more asking19:36
clarkbfungi: ya19:36
anteayajust the domain transfer needs to happen19:36
reedanteaya, when did dtroyer ask last time?19:36
lselli can chime in on the domain transfer -- jesse said yes, but we still need credentials and he's gone quiet19:36
lsellit's quick to do, but he's been unresponsive for about a month now19:36
anteayareed: couple weeks before summit19:36
anteayareed: permissions are in place afaik19:37
reedexactly, and in order to transfer the domain you need to be quick and responsive at the right time19:37
jeblairlsell: weird :( thanks19:37
anteayareed: looks like lsell is on it19:37
*** harlowja has joined #openstack-meeting19:37
reedanteaya, I and her both are19:37
anteayaokay19:37
lsellwe just need the auth code, stefano has sent him about five emails19:37
anteayawell keep us informed on your progress19:37
lsellbut yes, any help appreciated19:37
*** jackib has joined #openstack-meeting19:37
anteayalsell: ah, I didn't know that19:38
*** pballand has joined #openstack-meeting19:38
anteayahmmmm, anyone live close to him? perhaps he needs another beer?19:38
anteayaanyway that is all from me19:38
anteayaand ttx has two items19:38
jeblairthanks19:38
ttxi do!19:38
jeblair#topic  Support for proposed/* pre-release branches instead of milestone-proposed [ttx]19:38
*** openstack changes topic to "Support for proposed/* pre-release branches instead of milestone-proposed [ttx] (Meeting topic: infra)"19:38
*** harlowja_ has joined #openstack-meeting19:39
ttxso I looked up my old patch for this, and I'm not even sure it's needed19:39
ttxCurrent plan is to use proposed/juno pre-release19:39
ttxthat would generate nova-proposed-juno.tar.gz, which doesn't look any weirder than milestone-proposed.tar.gz19:40
ttxso unless you have process adherence to milestone-proposed.tar.gz, I'm not sure we need to rename tarballs to match old name19:40
jeblairttx: agreed, the new name should be fine19:40
ttxthere will be leftovers tarballs, but we can leave with that19:41
ttxso i'm not sure where to look for other needed changes19:41
fungiand probably the biggest to-do items from infra on this are all-projects and individual acl updates, changes to logic in zuul's layout and devstack-gate/grenade setup...19:41
*** caleb_ has joined #openstack-meeting19:41
jeblairwe could probably delete those milestone-proposed tarballs as a special case19:41
ttxI suspect somewhere deep in there is the magic that makes stable/* work together with stable/* when available19:41
anteayahow would the acl files change? anything with milestone would be pre-release?19:41
jeblairsince they are potentially confusing (and would have been overwritten if we did not change schemes)19:41
*** noslzzp has quit IRC19:41
nibalizeropenstack:19:42
nibalizererp19:42
ttxand we need to teach that to look for proposed/* just in case stable/* doesn't exist19:42
*** harlowja has quit IRC19:42
jeblairttx: it's actually magical enough that i don't think it needs updating19:42
fungianteaya: right now we have a lot of acl references to refs/heads/milestone-proposed which would probably need to be switched to refs/heads/proposed/*19:42
anteayaah19:42
anteayathat makes sense19:42
anteayathen the grand renaming of the gerrit groups19:42
ttxfungi: yep, that's the only change I found so far19:42
anteayaonce folks catch on19:42
ttxjeblair: that would truly be magic. I don't believe it.19:43
fungii'm not so picky that i care about .*-milestone groups being renamed19:43
*** sarob_ has quit IRC19:43
fungibut perhaps others disagree19:43
anteayakk19:44
anteayagood19:44
*** VijayB has quit IRC19:44
jeblairwe do still have milestones, after all :)19:44
ttxjeblair: also was wondering how we could test that, do you have a test project with pre-release / release jobs enabled ?19:44
ttxthat said, worst case scenario we'll have the same issues as with milestone-proposed19:45
jeblairttx: no, but we could probably use the sandbox repo; though i'm inclined to say let's just try to have people on-deck to re-run jobs if there are problems the first time we do this19:45
ttx#info needs to switch ACLs from refs/heads/milestone-proposed to refs/heads/proposed/*19:45
clarkb++ on deck sounds good19:46
ttxOK I'll update the release scripts so that they use proposed/* on pre-release19:46
jeblairttx: anything else on this topic?19:46
ttxjeblair: nope, looks simpler than I thought19:47
fungii can probably wrap the milestone-proposed to proposed/* acl changes into my normalization script series just so we catch any stragger open reviews ion a subsequent pass19:47
*** shakamunyi has quit IRC19:47
jeblair#topic  Is merge_tags.sh broken ? [ttx]19:47
*** openstack changes topic to "Is merge_tags.sh broken ? [ttx] (Meeting topic: infra)"19:47
fungis/stragger/straggler/19:47
ttxjeblair: you'll have to explain to me the magic that will make us degrade to using proposed/* in testing, though19:47
ttxso the second part of my patch was to teach proposed/* to merge_tags.sh19:48
ttxbut looking into it I realized that it must fail most of the time19:48
ttxin particular it fails on stable/* tags19:48
ttxbut silently (reports SUCCESS)19:48
*** kenhui has joined #openstack-meeting19:48
ttxit also failed on all 2014.1 tags19:49
fungittx: it was fixed prior to https://jenkins.openstack.org/job/swift-merge-release-tags/3/console19:49
ttxwith errors around CLA19:49
*** VijayB_ has joined #openstack-meeting19:49
*** jcoufal has quit IRC19:49
ttxfungi: OK, couldn't find reference to fix19:49
clarkbya the CLA thing should be sorted out19:49
clarkbttx: it was fixed int he context of translation proposals iirc19:49
ttxok, so it should work on release19:49
* fungi checks for a more recent example as proof19:50
*** hockeynu_ has joined #openstack-meeting19:50
ttxDoes it make sense to fix it for stable/* ?19:50
ttxIt's a release job, not a pre-release job, right19:50
*** fawadkhaliq has joined #openstack-meeting19:50
*** flaper87 is now known as flaper87|afk19:50
*** markmc has joined #openstack-meeting19:50
clarkbyes should be a release job19:50
jeblairconfirmed19:51
ttxOk, so I'll teach it proposed/*19:51
fungihere's a fun silent failure...19:51
ttxdoes it make sense to merge tags on stable releases ?19:51
fungi#link https://jenkins.openstack.org/job/cinder-merge-release-tags/2/console19:51
ttxfungi: yeah right :)19:51
fungi"error: malformed object name origin/milestone-proposed"19:51
ttxstable releases are tagged on stable/foo19:51
*** salv-orlando has quit IRC19:51
ttxfungi: it's when milestone-proposed doesn't exist anymore19:51
ttxso I don't think there is anything that should be merged back19:52
*** otherwiseguy has joined #openstack-meeting19:52
*** salv-orlando has joined #openstack-meeting19:53
ttxsince I'm not 100% sure I got why we were doing merge_tags.sh in the first place, I figured I should ask before I "fix" it there19:53
clarkbttx: the reason merge tags exists is so that the pbr versions works when you go to the next version19:53
*** baojg has quit IRC19:53
*** vivek-ebay has quit IRC19:53
*** VijayB_ has quit IRC19:53
*** eglynn has joined #openstack-meeting19:53
clarkbsince it is git tag based you have ot make sure the tags end up in your history19:53
*** shakamunyi has joined #openstack-meeting19:53
fungiin the history of your current branch, specifically19:53
ttxclarkb: so we shouldn't merge tags back to master for stable/foo release tags, right ?19:54
*** _nadya_ has joined #openstack-meeting19:54
jeblairttx: that sounds reasonable to me19:54
ttxgood thing it fails, after all.19:54
clarkbttx: you should for the first stable release but probably not for subsequent ones19:54
fungipresumably not, no. also pbr versioning is different for the projects which have a stable branch model, such that the old tag names are irrelevant anyway, right?19:54
ttxclarkb: so we should merge tags back from proposed/foo to master, but not from stable/foo19:55
jeblairttx: we may want to follow up with mordred on this19:55
clarkbttx: that sounds right19:55
*** jtomasek has quit IRC19:55
fungibecause we configure the package to have metadata about the next version being worked toward, and pbr uses that to determine what to set the current version to19:55
*** hockeynu_ has quit IRC19:55
clarkbbut we should get mordred's input19:55
ttxok, i'll fix merge_tags.sh and make sure mordred reviews it19:55
ttxthat's all I had -- thanks for making the time19:56
jeblairttx: cool, thanks19:56
jeblair#topic  Open discussion19:56
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:56
jeblair#link https://wiki.openstack.org/wiki/Qa_Infra_Meetup_201419:56
jeblairthere's a qa/infra joint meetup/sprinty thing happening in a few weeks19:56
*** otherwiseguy has quit IRC19:56
clarkbI have a couple changes up to ease the pain of the trusty transition for a couple projects19:56
fungiand swift is a hybrid between library serial release model and server stable branching, so it makes use of the pbr tag-based postversioning i assume19:56
jeblairyou should come unless you're having a family reunion19:56
clarkbgetting quick review on that would be great and make our users happy :)19:56
*** otherwiseguy has joined #openstack-meeting19:56
clarkbI will be there :)19:57
fungiis most everyone staying at the maritim?19:57
fungii need to go ahead and book my lodging this week19:57
anteayaclarkb: topic name for patch series?19:57
anteayaI19:57
anteayam staying in frankfurt19:57
clarkbanteaya: there is no patch series because they are independent. I will post links in -infra19:57
anteayabut I think I am the only one19:57
clarkbI am staying at maritim in darmstadt19:57
anteayaclarkb: cool or an etherpad19:57
mroddendid anyone need anything else from me re: the bash8 rename?19:57
mroddeni saw it will be done on sat.19:57
jeblairanteaya: i suspect mordred will -- starwood and all19:57
anteayajeblair: he is leaning darmstadt19:57
notmynamefungi: FWIW, it was recently (circa atlanta summit) pointed out that swift's versioning via pbr isn't actually what anyone wants. we'll be updating it to be more like other server projects during juno (still semver, but not using the pbr+tags like client libs)19:58
fungimrodden: yeah, you'll want to be around if possible to make sure your stuff is working and approve the .gitreview update patch for it19:58
anteayaso I went ahead and booked without hearing from him19:58
jeblairanteaya: now i'm just confused! :)19:58
funginotmyname: oh, right, i remember being in that session now ;)19:58
anteayajeblair: yeah, me too19:58
*** Michalik_ has joined #openstack-meeting19:58
*** zehicle_at_dell has joined #openstack-meeting19:58
*** Penick has quit IRC19:58
mroddenfungi: be around on sat.?19:59
anteaya1500 utc19:59
jeblairoh, i added some potential sprint topics to the wiki page; feel free to add more19:59
*** natarajk has quit IRC19:59
clarkbcool /me checks if zuul is on there :)19:59
fungimrodden: or just be ready to deal with it on monday when you get around to it, assuming it's a low-volume sort of project19:59
*** markwash has joined #openstack-meeting19:59
anteayaI might have to add infra-manual if the first commit doesn't merge before then19:59
jeblairanteaya: nicely done!19:59
anteayaha ha ha20:00
mroddenfungi: np i can be around on sat. at 1500 UTC i think, just wanted to clarify20:00
anteayaoh I think we are done20:00
*** balajiiyer has joined #openstack-meeting20:00
jeblairthanks everyone!20:00
*** balajiiyer has left #openstack-meeting20:00
jeblair#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Jun 24 20:00:43 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-06-24-19.02.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-06-24-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-06-24-19.02.log.html20:00
ttxOK... Anyone here for the TC meeting ?20:01
devanandao/20:01
russellbo/20:01
jeblairo/20:01
markwasho/20:01
*** armax has quit IRC20:01
markmchey20:01
*** nibalizer has left #openstack-meeting20:01
sdagueo/20:01
*** leonchio_ has quit IRC20:01
mikalAhoy20:01
ttxannegentle, mordred, markmcclain, jaypipes, dhellmann : around ?20:01
*** natarajk has joined #openstack-meeting20:01
annegent_here20:01
*** Sukhdev has quit IRC20:01
dhellmanno/20:01
ttxvishy is proxied by markwash20:01
ttxOK, looks like we can have a meeting20:01
ttx#startmeeting tc20:02
openstackMeeting started Tue Jun 24 20:02:01 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
jeblairannegent_: ping20:02
*** openstack changes topic to " (Meeting topic: tc)"20:02
openstackThe meeting name has been set to 'tc'20:02
ttxAgenda for today:20:02
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:02
ttxmarkwash: you're available now ?20:02
markwashI'm here!20:02
markwash:-)20:02
ttx#topic Glance gap coverage plan20:02
*** openstack changes topic to "Glance gap coverage plan (Meeting topic: tc)"20:02
annegent_jeblair: pong20:02
ttxTwo weeks ago a single gap was raised against Glance in the integrated requirements gap analysis:20:02
zehicle_at_dello/20:02
ttx- Lack of testing a binary image in integration tests20:02
ttxmarkwash posted the following plan to address it:20:03
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee/Glance_Gap_Coverage20:03
ttxPretty simple, looks good to me20:03
markwashyeah, we targeted j-2 and feel good about it20:03
*** Penick has joined #openstack-meeting20:03
markwashtried to get it done this past week but couldn't quite find the immediate manpower20:03
ttxUnless someone has an issue with it, I'll add it to the TC wikipage for tracking20:03
dhellmannseems good to me20:04
*** marcoemorais has quit IRC20:04
*** spzala has joined #openstack-meeting20:04
ttxand we'll haunt markwash back about this targeting in a few weeks time20:04
ttxwhen we review gap coverage progress post-j220:04
sdaguewfm20:04
*** hemna__ has quit IRC20:04
ttx#action ttx to add Glance gap coverage plan to TechCommittee wiki page for tracking20:04
*** sarob has joined #openstack-meeting20:04
*** marcoemorais has joined #openstack-meeting20:04
ttx#topic Other governance changes in review20:04
*** openstack changes topic to "Other governance changes in review (Meeting topic: tc)"20:04
ttx* Modify Images mission to fit Artifact Repository (https://review.openstack.org/98002)20:05
markwashthanks dhellman for the wording20:05
dhellmannmarkwash: glad I could help :-)20:05
ttxThis one is Glance territory too20:05
*** marcoemorais has quit IRC20:05
ttxA new wording was proposed, hopefully it will please enough people.20:05
*** penguinRaider has quit IRC20:05
ttxThe marketing folks approached me about the change from "image service" to "artifact repository"20:05
*** caleb_ has quit IRC20:05
*** caleb_` has joined #openstack-meeting20:05
*** caleb_` has quit IRC20:05
markwashI have a call with them tomorrow20:05
*** zdiN0bot has joined #openstack-meeting20:05
*** marcoemorais has joined #openstack-meeting20:05
ttxthey want to have a chance to discuss that name and weigh in on the review before this is finally approved20:05
ttxNobody suggested something better yet, though20:06
ttxbut that name leaks into the "official naming" so I think that request is fair20:06
annegent_it means docs changes too20:06
*** marcoemorais has quit IRC20:06
*** caleb_ has joined #openstack-meeting20:06
markwashI would also like a little time for some other glance folks to respond to the latest patch, if that's okay20:06
annegent_we use Image Service currently20:06
*** marcoemorais has joined #openstack-meeting20:06
ttxso yes, I'll stall this until at least next meeting20:06
*** vkmc has quit IRC20:07
annegent_ttx: markwash: can I get in on that call?20:07
*** pballand has quit IRC20:07
* annegent_ is not a marketer20:07
ttxannegent_: i'm not on that call, but maybe markwash can include you20:07
*** _nadya_ has quit IRC20:07
markwashannegent_: I'll ask to have you included20:07
annegent_thanks markwash20:07
lsellyes20:08
ttx* Add translation support requirement (https://review.openstack.org/97872)20:08
ttxRequirements changes need consensus, as they reflect the base set of requirements we all agree on20:08
ttxI'm not sure this one is ready to gather that consensus20:08
ttxLooks like policy could mature a bit and the technical result could be tested20:08
dhellmannThe i18n team has been trying for 2 summits to move ahead on this.20:08
dhellmannI'd like to at least be able to go back to them with specific instructions about what they need to do.20:09
ttxdhellman_: that's fair20:09
dhellmannwe have a lot of the tooling in place already20:09
*** jog0 has joined #openstack-meeting20:09
dhellmannincluding the CI jobs20:09
ttxdhellman_: personally I think of two things20:09
dhellmannand a few projects are accepting changes20:09
ttx(1) we need to somehow test that what we do is usable20:09
*** mrmartin has joined #openstack-meeting20:09
ttxbecause I know of at least two releases where it wasn't the case20:09
dhellmannok20:09
sdaguedhellmann: where are the CI jobs? I guess that's something I'm not aware of.20:10
ttxbecause there is no automated test around that20:10
dhellmannsdague: jobs to extract the messages, not to run tests20:10
jeblairheh, literally "continuous integration" :)20:10
jeblairunlike most of the jobs we run20:10
sdagueok, fair :)20:10
dhellmannunit tests exist, so what other tests do we want? a full d-g job with an alternate translation?20:10
sdaguebut that's not the jobs we know we need20:10
jeblairsdague: ++20:10
sdaguedhellmann: yeh20:10
ttx(2) I would like to clarify end-user facing vs. operator-facing messages. The plan was to enable two separate translation domains to be able to prioritize one over the other20:10
dhellmanndo we have the resources to run a d-g job with translations? we're already talking about combining some gate jobs20:11
ttxmarkmc: do we have support for multiple translations domains now ?20:11
* ttx lost track of that20:11
markmcttx, dhellman has written some nice docs clarifying some of this in the last week20:11
sdaguedhellmann: even nightlies are fine20:11
dhellmannttx: we now have several domains, one for API and other user messages and a bunch of others for different log levels for operators20:11
annegent_dhellmann: ttx: and documentation20:11
sdaguehonestly, I'm totally happy to have the i18n jobs be nightlies, but we do need to actually see if that works for reals20:12
jeblairttx: yeah, if that's something we want to do, we should standardize that (2 domains) at the tc level20:12
dhellmanndocs are waiting for the requirements issue to clear up so they can merge: https://review.openstack.org/#/c/96961/20:12
ttxthe current wording places end-user-facing and operators-facing on the same level though.20:12
markmcttx, http://docs-draft.openstack.org/61/96961/7/check/gate-oslo.i18n-docs/c4074a7/doc/build/html/guidelines.html#log-translation20:12
markmcdocs haven't been merged yet20:12
dhellmannttx, jeblair : there are 5 different domains20:12
dhellmannthat's what the translators wanted20:12
jeblairdhellmann: user + 4 logs?20:13
dhellmannthey actually wanted 6, but we agreed not to translate debug messages20:13
dhellmannyes20:13
dhellmannhttps://review.openstack.org/#/c/96961/7/doc/source/guidelines.rst20:13
ttxdhellmann: ok, so it looks like we could iterate on the current proposal20:13
markmcI think this is progressing well, but we do need the policy to link to these guidelines20:13
markmcand then there's the testing issue20:13
ttxi'll get my feedback in20:13
dhellmannok, I think we can land the doc changes ^^ this week, and I can update the policy20:13
dhellmannI'll tell the i18n team they need to find someone to work on the test job before we can approve the policy20:14
dhellmannwas that the only objection?20:14
ttxit felt like we were farther away from a solution, reading the comments20:14
* dhellmann thought so too20:14
*** padkrish has quit IRC20:14
*** balajiiyer has joined #openstack-meeting20:14
jeblairi'm optimistic20:14
dhellmann#action dhellmann talk to i18n team about finding someone to create a test job with translations20:15
annegent_dhellmann: we have a doc gate test for translation job on japanese20:15
annegent_dhellmann: if it helps20:15
dhellmannannegent_: yes, that may help as an example20:15
ttxOK, let's iterate a bit more on this, if it's not blocked20:15
*** jog0 is now known as jogo_20:15
dhellmannno,  it sounds like they have more work to do, and that's fine now that we know what it is20:15
ttxnext topic...20:15
devanandadhellmann: with those doc changes, I think my concern is addressed.20:15
dhellmanndevananda: ok, thanks20:16
ttxnice doc20:16
ttx#topic Defcore20:16
*** openstack changes topic to "Defcore (Meeting topic: tc)"20:16
ttxWe have two resolutions covering the recent requests for technical input from Defcore:20:16
ttx* Resolution requesting designated sections from projects (https://review.openstack.org/100675)20:16
ttxStill missing input from Swift, Glance, keystone, Horizon, Neutron and Cinder20:17
mikalSo we talked about this one last week20:17
mikalttx: well, not really20:17
ttxI informed all those PTLs during the 1:1 sync points today20:17
markwashdoes anyone here have the link to the original etherpad?20:17
mikalMy proposal was that we merge this, and then take patches from those projects on top20:17
*** zdiN0bot has left #openstack-meeting20:17
ttxmikal: ah. hmm20:17
zehicle_at_dell#link https://etherpad.openstack.org/p/openstack-designated-sections20:17
markwashty20:17
*** fnaval has quit IRC20:17
mikalttx: hence the TODOs20:18
ttxmikal: the trick is we'd merge (i.e. approve) a partial thing20:18
dhellmannI like that. I think I would have preferred to have the nova stuff in a separate patch, but there's probably not much to discuss about the header of the resolution itself.20:18
ttxmikal: I thought people would just propose further changesets20:18
mikaldhellmann: I wanted an example to help PTLs work out what to write20:18
*** fnaval has joined #openstack-meeting20:18
jeblairttx, mikal: was there a -dev list thread for these?20:18
dhellmannmikal: I thought that's probably what you were doing.20:18
russellbfurther changesets might get frustrating, fragmenting discussion20:18
mikalttx: well, I wanted to allow the TC to discuss each project indivisually20:18
mikali.e. if we dig into a thing on neutron, we should not block say glance20:18
dhellmannthey can submit patches on top of this patch, too, it doesn't have to merge first20:18
ttxmikal: right, I just fear that will push us past "end of month"20:19
dhellmannmikal: +120:19
mikalttx: well, it means we can do them in parallel20:19
eglynnzehicle_at_dell: is backporting test coverage to tempest:stable/havana an option at this stage for a project that's not currently included in these designated sections?20:19
mikalBut I agree that I've sat on this too long20:19
ttxjeblair: no specific thread on that specific request, no20:19
zehicle_at_delleglynn, it's not required20:20
ttxjeblair: it's been documented through all the defcore posts20:20
zehicle_at_dellwe agreed with the Tempest team that we could test Havana using trunk branchless20:20
ttxalso input was already provided in an etherpad before20:20
zehicle_at_dellsince Havana is advisory, it's OK20:20
markmcwe could add a designated sections template and ask each project to complete it20:20
markmcdon't need all projects in one file20:20
ttxmarkmc: +120:21
eglynnzehicle_at_dell: ok, interesting ... I though branchless tempest only applied to stable/icehouse not before20:21
*** esel has joined #openstack-meeting20:21
sdaguezehicle_at_dell: branchless tempest doesn't work on havana20:21
mikalmarkmc: that's true, I hadn't thought of that20:21
sdagueit's icehouse and forward20:21
mikalWe could for example build a little directory tree or something20:21
dhellmannmarkmc: we could add that to the programs.yaml file, too20:21
eglynnzehicle_at_dell: i.e. wot sdague said20:21
zehicle_at_delleglynn, we're testing the stable APIs.  It's a pretty good test of the ones we are most interested in20:21
sdaguethere were too many API breaks between havana and icehouse20:21
ttxmikal: maybe make a directory under resolutions20:21
* dhellmann still needs to work on turning programs.yaml into html20:21
mikaleglynn: well, except it will change over time and the historical values matter20:21
mikalWould people like me to refactor this into a directory and see what it looks like?20:22
zehicle_at_dellsdague, it they are breaks in "core" APIs then we want to know that20:22
ttxmikal: +120:22
dhellmann+120:22
mikalI could do that now and we could circle back in a few minutes20:22
*** craigbr has quit IRC20:22
*** fifieldt_ has joined #openstack-meeting20:22
ttxmikal: also redirect people to doing their own change, because I told them all to changeset your original change20:22
*** fnaval has quit IRC20:22
ttxmikal: so you can add a note on the commit message to redirect them20:22
sdaguezehicle_at_dell: well, it's more complicated, because of the way tempest used to coevolve with projects, the APIs could slip over time20:22
jeblairmikal: do i understand correctly that your nova change means a public cloud can run nova with a proprietary compute driver, scheduler, and database, and declare that they are running "OpenStack"?20:22
russellbjeblair: correct.20:23
zehicle_at_dellsdague, it really makes it easier if we focus on the forward direction of Tempest instead of trying to make it work for a release that we're not really enforcing20:23
mikaljeblair: OMG, can we decouple that for just a moment?20:23
mikalI'm happy to discuss it, but I want to unblock the process first20:23
russellbjeblair: well, potentially.20:23
*** pballand has joined #openstack-meeting20:23
sdagueand we looked at what it would take to get havana in line, and it really was more work than anyone was willing to sign up for20:23
ttxjeblair: well, they would need to run a few other openstack pieces :)20:23
sdaguezehicle_at_dell: agreed20:23
zehicle_at_dellsdague, happy to discuss it more.  would want to involve davidlenwell_20:23
sdaguethat's why our focus is icehouse forward20:23
*** mwagner_lap has quit IRC20:23
*** dprince has quit IRC20:23
jeblairmikal: okay sure -- i thought we were good on the process.  :)20:23
*** SlickNik has joined #openstack-meeting20:24
*** craigbr has joined #openstack-meeting20:24
sdagueplus it gets rid of backport burden20:24
ttxjeblair: also I don't think they would run "openstack". They would maybe run "an openstack compatible cloud" or "an openstack interoperable cloud"20:24
mikaljeblair: well, except I have to do this refacotr20:24
ttxtrademarks to be defined20:24
jeblairmikal: it's the first time we're seeing this whole thing converge and i'm just sanity checking my understanding20:24
jeblairmikal: carry on!20:24
markmcttx, nope, this would be an OpenStack cloud20:25
* ttx wants to decouple "openstack" the thing we work on from the trademark programs20:25
zehicle_at_dellttx, the specific trademarks are "powered" and "compatible" as defined by the Foundation20:25
zehicle_at_dellbut compatible does not mean quite what you may thing - it's not about APIs20:25
ttxzehicle: right20:25
markmcttx, OpenStack Compatible (if such a TM existed) would be where you're not running the designated sections20:25
*** fifieldt has quit IRC20:25
ttxmarkmc: so.. "OpenStack powered" ?20:25
markmcttx, yeah20:26
*** radez is now known as radez_g0n320:26
zehicle_at_dellmarkc, we'd have to use a different name but the API only mark is still a ways off.  We've deliberately NOT done that20:26
markmczehicle_at_dell, that's why I said "(if such a TM existed)"20:26
zehicle_at_dellmarkc, and it's not clear that we will at this time20:26
markmcand it's markmc not markc20:26
*** jergerber has quit IRC20:26
zehicle_at_dellmarkc, I understand.  the trick is that there IS a compatible mark.20:26
*** eguz has joined #openstack-meeting20:26
dhellmannmikal: these all look like reasonable plugin spots in nova. I assume there are designated sections that call all of these things listed as exceptions?20:27
*** MaxV has joined #openstack-meeting20:27
ttxmarkmc: I still think we should prefix whatever technical input we produce for Defcore with clear warnings that we do not encourage substituting pieces of openstack code20:27
*** fnaval has joined #openstack-meeting20:27
mikaldhellmann: well, all of those things have well defined plug in layers, and existing out of tree extensions (to the best of my knowledge)20:28
*** davidlenwell_ is now known as davidlenwell20:28
dhellmannmikal: like, you say "scheduler driver" but that implies the scheduler service is still considered designated?20:28
*** eguz has quit IRC20:28
ttxbecause I want to just designate areas of code that are desogned to be extensible20:28
markmcttx, as in, that would be the TC's consensus input to the board's TM policy decision making ?20:28
jeblairttx: i think that may be in conflict with the actual content of that change20:28
mikaldhellmann: agreed. You run the service, but you can plug in your own algorithm20:28
*** eguz has joined #openstack-meeting20:28
dhellmanncool20:28
*** fawadkhaliq has quit IRC20:28
mikalIs https://review.openstack.org/#/c/100675/4 closer?20:28
dhellmannthat seems like exactly what we want to be doing when we specify designated sections -- specifying the bits we think should and should not be replaceable20:28
russellbttx: i don't know why we'd list anything if we felt you shouldn't actually replace code20:29
mikaldhellmann: noting that we have already passed a set of guidelines which basically say that20:29
ttxjeblair: on one side, we the TC are the ultimate technical representation, and we are asked to provide a technical input, which is basically which parts of the code allow plugins20:29
mikali.e. we're being consistent over time which is a nice feeling20:29
jeblairmikal: you have extra content in 'instructions.rst'20:29
mikaljeblair: doh20:29
dhellmannmikal: you probably want a file in the resolutions/ dir to point to all of those little files so they render properly. I can help you with that offline.20:29
ttxjeblair: on the other, we are the representation of the contributors of the project, and as mordred said last week, we should not encourage building proprietary products on top of openstack20:29
russellbttx: we can't pretend to be ignorant to the purpose of why we're providing this list ...20:29
mikaldhellmann: ta20:30
mikaldhellmann: perhaps instructions.rst should be up a dir level?20:30
*** fawadkhaliq has joined #openstack-meeting20:30
mikaldhellmann: and include the sub files?20:30
*** marcoemorais has quit IRC20:30
mikaljeblair: fix uploaded20:30
ttxrussellb: the alternative would be what ? To refuse to produce that information, so that they have to make their own idea ?20:30
dhellmannmikal: that would work, maybe using a toctree20:30
mikaldhellmann: got an example I can copy?20:30
ttxI prefer to provide a conservative version20:30
*** eghobo has quit IRC20:30
*** marcoemorais has joined #openstack-meeting20:31
jeblairttx: i lean toward very conservative.20:31
ttxat least we cna make sure that it follows technical lines20:31
dhellmannmikal: let me whip one up20:31
russellbttx: to say that what we support is getting involved and contributing to the project, and that what we deliver is OpenStack, not intended to be replaced by outside code, even if technically possible20:31
mikaldhellmann: thanks man20:31
* zehicle_at_dell would like to have a follow-up from last week to review the process and clearify how designated sections and capabilities become core20:31
ttxjeblair: we approved guidelines before -- do you still agree with them ?20:31
mikaldhellmann: Or just upload a new version of that review with it done...20:31
*** marcoemorais has quit IRC20:31
mikaldhellmann: we don't need too much process for that20:31
ttxjeblair: http://git.openstack.org/cgit/openstack/governance/tree/resolutions/20140402-defcore-designated-sections-guidelines.rst20:32
*** marcoemorais has joined #openstack-meeting20:32
*** ajo|mac has joined #openstack-meeting20:32
dhellmannmikal: ok, doing that now20:32
mikaldhellmann: :)20:32
ttxIf we follow those guidelines we previously approved, we can provide a technical answer20:33
markmcttx, the important point IMHO is that we should not be in a position where it looks like the TC is the ones pushing a TM policy that allows drivers to be replaced with proprietary alternatives20:33
russellbmarkmc: +10020:33
ttxmarkmc: that I agree on20:33
markmcttx, we can provide technical input (perhaps policy opinions too), but ultimately the board is the one making this policy decision20:34
ttxwe need to be able to provide that etchnical info without endorsing the policy that might be driven from it20:34
devanandamarkmc: ++20:34
jeblairttx: i abstained from that vote.  i'm still trying to understand the ramifications of this; thus my question earlier.20:34
mikalmarkmc: do you feel we're doing that now though?20:34
mikalmarkmc: we're effectively just listing the areas we think plugins are ok20:34
russellbi feel we're being roped in as accomplices by generating this list, yes.20:34
russellband the more i think about it, the less I like this whole thing.20:34
jeblairttx: i will vote on the actual resolutions, however.20:35
markmcmikal, I've seen language in the etherpads that suggests we have full control over this aspect of the TM policy20:35
devanandaOTOH, we should not be in a position where we prevent folks from making necessary customizations for their environment (eg, changing scheduler filters, or adding hardware drivers, etc)20:35
mikalPicking on the nova example, I think that horse has bolted for all these examples20:35
dhellmannmikal: updated20:35
*** blogan is now known as zz_blogan20:35
dhellmannmikal: oops, should update the instructions, too20:36
jeblairdevananda: i'm not sure we have the power to prevent that sort of thing.  what we may have the power to prevent is people doing that sort of thing and calling their work ours.20:36
mikaldhellmann: yeah, just noticed that20:36
zehicle_at_dellrussellb, "roped in" - we're trying to have Board & TC collaboration FWIW20:36
*** denis_makogon_ has joined #openstack-meeting20:36
dhellmannmikal: fixed20:37
russellbzehicle_at_dell: *nod* and that much is appreciated20:37
mikaldhellmann: am I fixing or you?20:37
mikalOk, cool20:37
sdaguemarkmc: is your statement just in reference to the TM? because the projects being apache licensed do kind of explicitly allow for proprietary mix.20:37
sdague(note: mostly playing devil's advocate there, because I want people upstream as much as possible)20:37
markmcsdague, yeah, it's just about the TM20:37
ttxhmm20:37
markmcsdague, we can value people's freedom to mix with proprietary20:37
*** therve has joined #openstack-meeting20:37
ttxso I think we should have a lot of discussions about this this week20:37
sdaguemarkmc: ok, sure, I agree with that20:37
ttxthis meeting won't be enough20:37
markmcsdague, we don't have to value it so much that they should be able to call it OpenStack20:37
*** denis_makogon_ is now known as denis_makogon20:37
*** dkranz has quit IRC20:38
*** mugsie has left #openstack-meeting20:38
russellbmarkmc: indeed20:38
jeblairttx: agreed20:38
markmcsdague, OTOH, I do like the idea of an OpenStack Compatible Cloud TM20:38
*** adalbas has quit IRC20:39
* zehicle_at_dell repeats that a single topic meeting on this may be helpful to resolve concerns and help collaboration. I don't want to hijack TC meetings with concerns over the broader process20:39
mikalOk, so...20:39
devanandazehicle_at_dell: ++ to separate meeting20:39
mikaldhellmann and I now have https://review.openstack.org/#/c/100675 ready for people to take another look please20:39
russellbwe've spent a ton of a lot of meetings on this20:39
*** bdpayne has quit IRC20:39
sdaguemarkmc: sure. Though I think we've got a lot of internal technical work to make that meaningful. /me stares at how optional the nova api is, for instance.20:39
russellbcould at least move to the ML after this to keep it moving20:40
zehicle_at_dellrussellb, yes and likely many more to come.  there's a lot at stake and we're taking it slow20:40
ttxzehicle: right, I'd like to see if i can find a middle path first20:40
markmcsdague, we can value people with products that are compatible with OpenStack; but we likely value them less than OpenStack products20:40
ttxbut then we can certainly do a single-topic meeting20:40
ttxcould even be a TC meeting dedicated to the issue20:40
devanandait seems like this derails the TC every time it comes up -- which should tell us something about the topic20:40
ttxyes, we need to clarify our positions20:40
* zehicle_at_dell is in the Bay area this week. happy to also meet 1x1 with people if they'd like. 20:41
ttxok, so I'll be in touch via IRC with various members soon20:41
*** sirushti has joined #openstack-meeting20:41
ttxand will consider dedicating a full meeting to that issue, maybe next week20:41
russellbthanks, ttx.20:41
zehicle_at_dellttx, please let me know so I can include DefCore members20:41
dhellmannzehicle_at_dell: I would actually prefer that you not meet 1:1 with anyone. Having separate in person meetings that we can't all attend is in part why some of us are confused.20:41
*** sirushti has left #openstack-meeting20:42
ttxzehicle: you can already warn them, that would be 20:00 UTC on Tuesday20:42
*** sarob has quit IRC20:42
zehicle_at_delldhellmanm, hmmm. not sure I agree20:42
*** caleb_ has quit IRC20:42
ttxThe other review is:20:42
*** sarob has joined #openstack-meeting20:43
ttx* Propose scores for DefCore capabilities (https://review.openstack.org/100721) (https://review.openstack.org/100722)20:43
ttxI think it's in the same bag though.20:43
dhellmannzehicle_at_dell: the DefCore team has produced a lot of written stuff that I personally have had trouble wading through because I don't have the context from the meetings.20:43
ttx#topic Election behavior guidelines20:43
*** openstack changes topic to "Election behavior guidelines (Meeting topic: tc)"20:43
ttxWe have two competing proposals now:20:43
ttx* Adds a resolution addressing expected election behaviour (https://review.openstack.org/98675)20:43
ttx* A resolution on standards of behavior during elections (https://review.openstack.org/100445)20:43
dhellmannzehicle_at_dell: that's not a knock on your work, just a thing I've been struggling with as I review the output20:43
ttxBoth describe expected behavior from candidates in a way that will reach the intended goal IMHO20:43
markmcttx, heh, which is which :)20:44
ttxThey differ in the way they suggest issues are to be handled:20:44
*** sarob_ has joined #openstack-meeting20:44
ttxFirst one describe a process to report issues privately, which then may escalate to the Community Code of Conduct violation process20:44
ttxSecond one suggests to report issues publicly and let voters be influenced (or not) by the publicly reported issue20:44
ttxPersonally I prefer the first one because (1) not everybody is comfortable with reporting issues publicly20:44
ttxand (2) I fear that without independent investigation imaginary claims would have the same impact as real issues in the public forum20:44
ttxBUT it's worth noting that whichever we choose to explicitly promote, both options are always present:20:44
zehicle_at_delldhellmann, that's why we create summaries.  don't know how to have a transparent process with less clutter.  the 1x1 helps me have better back and forth with people who have strong opinions20:45
jeblairttx: i agree, and i believe the second one does not address the actual problems we've seen20:45
ttx- you can always report a CoC violation20:45
*** padkrish has joined #openstack-meeting20:45
ttx- you can always publicly shame behavior in an attempt to influence voters20:45
ttxA third proposal would be to not promote any specific way issues are to be handled.20:45
ttxand just adopt Anita's draft line 1-21 or Eoghan's draft lines 1-12 + 30-4220:45
mikalThe third way sounds like a cop out to me20:45
jeblairi'd like to find out what people think the reporting mechanism should be, and fix up the first one.20:45
sdagueso I'd be fine with the private reporting, though I do like the pledge in the 2nd one20:45
annegent_to me, the reporting mechanism should be the same as a violation of code of conduct20:45
* anteaya would like to know what people think will happen if someone loses foundation membership20:45
sdaguebecause I actually think that, by itself, is a powerful deterant20:46
annegent_easier to explain and remember20:46
jeblairsdague: i don't like the pledge -- i think forced pledges are insincere and we've seen no objectionable behavior from actual candidates20:46
dhellmannas was pointed out, the pledge wouldn't have solved the issue we had last cycle because the candidate wasn't acting "badly"20:46
ttxanteaya: can't vote, can't be elected to TC (can still be PTL I think)20:46
jeblairsdague: i think that fundamentally, it's the communication that's the deterrent, and that's what we should do20:46
*** marekd|away is now known as marekd20:46
anteayatxx can't get summit passes20:46
dhellmannand we essentially have the "no clear reporting guidelines" now, and so we have this issue that no one wants to talk about publicly20:46
ttxhmm no, can't be elected PTl either20:47
anteayaso what is wrong with losing voting previledges and summit passes?20:47
*** sarob has quit IRC20:47
anteayaand not being able to stand for election20:47
ttxanteaya: tat we can easily fix20:47
ttx(the pass)20:47
*** penguinRaider has joined #openstack-meeting20:47
anteayaright20:47
annegent_I'm also a bit concerned about the pledge and any legal ramifications for poor wording or definitions that aren't crisply legal20:47
anteayaso all the lose is the right to vote and lead20:47
anteayaI dont' think that is excessive for violations of fair elections20:47
annegent_what if the candidate herself is not the bad actor? Has that already been discussed?20:47
jeblairand to be fair, i think anteaya's inclusion of language about the existing CoC is helpful -- it already exists, says what it says and has penalties; nothing about this can or should change that.20:48
*** nati_ueno has joined #openstack-meeting20:48
jeblairwe could not mention it, but that won't change that it exists20:48
ttxjeblair: right, that's my point about the choice not being that much relevant anyway, both options exist already20:48
*** bdpayne has joined #openstack-meeting20:48
jeblairttx: yeah20:49
markmcrather than focus on punishment, maybe it should be on correcting our culture20:49
anteayamostly this gives me the right to investigate, if someone makes a report, and says who I report to20:49
markmce.g. in the cases in the last cycle, it might have been enough to talk about the concrete issues without naming names20:49
ttxjeblair: which is why a 3rd proposal where you just reaffirm the behavior and link to the CoC would be sufficient20:49
*** caleb_ has joined #openstack-meeting20:50
markmcI'm not sure the people involved realized they were necessarily doing anything terribly wrong20:50
ttxmarkmc: i'm not sure eglynn's proposal achieves "correcting our culture" better, though20:50
markmcthat's what needs correcting20:50
markmcttx, it talks about culture, and reinforcing it20:50
anteayareally?20:50
ttxI fear that public shaming is not the solution we shoud encourage either20:50
markmcttx, "talk about the concrete issues without naming names"20:51
anteayayou think people in opensource dint' know that circualteing private emails was not a good idea20:51
markmci.e. not quite publich shaming, but at least publicly discuss the behavior20:51
anteayaand using the voters list for the emails?20:51
jeblair(or private campaign events)20:51
anteayaI don't buy they didn't know20:51
markmcanteaya, I was a recipient of that email, saw how the recipients responded to it and felt the sender's apology was sincere20:51
markmcanteaya, people can get carried away with their enthusiasm20:52
anteayaokay well you know more than I20:52
anteayabecause I never saw it20:52
mikalSo, I think it might be harder than we realize to draw the line by the way20:52
anteayabecaue noone filed a report20:52
markmcanteaya, that's what concerns me about all of this - it lacks empathy for people making genuine mistakes20:52
annegent_anteaya: besides, legally, if I RSVP to a Summit party, how do I know I haven't opted in to being on a mailing?20:52
mikalSo... Is a summit party "hosted" by a person intending to run for election inappropriate for example?20:52
anteayamarkmc: so as a receiptent do you think this was a genuine mistake?20:52
annegent_markmc: yes, me too20:52
*** sweston_ has quit IRC20:52
markwashis it really the job of the resolution to show empathy?20:52
markmcanteaya, very much so, yes20:52
anteayaand do you think if I read the email, I would reach the same conclusion?20:52
markmcanteaya, poorly judged, I'd say20:52
*** pballand has quit IRC20:53
anteayado you think I would conclude the same as you20:53
markmcanteaya, where the sender realized the error when it was pointed out20:53
annegent_markwash: not empathy but fairness and rights20:53
markmcrussellb, would you agree ?20:53
*** aimon_ has joined #openstack-meeting20:53
russellbi think the apology was sincere, yes20:53
russellbso yes, agreed20:53
dhellmannmikal: good question, and I'd like to think if there was some formal way to raise the issue an attendee who was uncomfortable would at least have a way to get an answer.20:53
markmcit wasn't acceptable behavior, that's not the point20:53
*** padkrish has quit IRC20:53
anteayaso the email and using teh voters list was one incident20:53
jeblairmarkmc: i think the existing proposal in 1 is quite fair -- it does not rely on the election inspector to make significant judgements -- it does rely on the ED to do so, but he or she is already empowered by the bylaws and coc to do exactly that20:53
russellbvery poorly judged mistake, with a sincere apology after it was calledo ut20:53
anteayathe other was the private meeting20:53
annegent_dhellmann: but we have a reporting structure already20:54
russellbi don't know if it was a single incident or not, but markmc were on the same one20:54
*** vivek-ebay has joined #openstack-meeting20:54
russellbmarkmc and I*20:54
dhellmannannegent_: do we? what is it?20:54
ttxI could go with a new version of eglynn's proposal that would at least mention that the CCoC covers election behavior, and does not go into such great lengths to encourage public shaming20:54
anteayaannegent_: yes, I too would like to know20:54
jeblairmarkmc: i feel like we could drop the second part of the first proposal and we would have a lot more agreement, however, i'm not sure it would actually change any of the facts20:54
dhellmann annegent_ : I thought anteaya said she didn't receive any complaints?20:54
anteayasince i didn't and noone else did20:54
annegent_dhellmann: http://www.openstack.org/legal/code-of-conduct/ << possibly we need a tc resolution for our elections that enhances this, but this document is well tested and clear20:54
anteayawhom I consulted while this was going on20:54
ttxor with a new version of Anita's that would not feel like empathy  is not an option20:54
anteayaannegent_: yes, that is what my proposal references20:55
annegent_dhellmann: but anyone could report the violation, does it have to go through election officials?20:55
anteayaI had many questions during this situation20:55
eglynnttx: I could draft something of that ilk, keeping the original "ethos" of the proposal20:55
ttxannegent_: technically, not20:55
anteayaand zero reports20:55
annegent_ttx: so you're asking for another proposal?20:55
dhellmannannegent_: I don't know. Maybe you're right and we just need to clarify the answer to that question20:55
*** sankarshan_away has quit IRC20:55
jeblairttx: i'd be okay with just the first part of anteaya's but i feel like we'd be dropping the ball on trying to clarify a policy and not actually clarifying how to deal with violations20:55
anteayajeblair: +20:55
anteayawe need to know how this is resolved20:56
annegent_to me, we either are drafting a separate code of conduct for tc / ptl candidates or asking those candidates and the electorate to follow the existing CoC20:56
ttxannegent_: I think we can't choose between the two because we want both (and will have both anyway)20:56
annegent_there may be a third option20:56
anteayaotherwise we end up feeling it isn't even after it is20:56
sdagueI do think the empathy piece is important. As we grow in community size, we don't know each other like we used to, and if we don't give the benefit of the doubt I'm concerned where that takes us20:56
ttxannegent_: since nothing will prevent people from filing CCoC violations and/or publicshame people on -dev20:56
anteayatake the shanley thing, which reached a resolution, but people thought it didnt'20:56
markwashbut empathy has other vehicles than the resolution, too20:57
anteayaand still have the perception that it didn't20:57
ttxchoosing one feels like we promote one behavior over the other20:57
dhellmannsdague: +120:57
jeblairsdague: what do you think the reporting mechanism should be?20:57
*** kenhui has quit IRC20:57
anteayaI'm really surprised at suggestions that conducting an investigation implies I will lack empathy20:57
*** fawadkhaliq has quit IRC20:57
anteayaI just want to find the facts20:57
*** sankarshan_away has joined #openstack-meeting20:57
anteayanot dwell in gossip20:57
*** VijayB has joined #openstack-meeting20:58
dhellmannttx: I don't know that I could point to any example of public shaming in open source that had a good outcome.20:58
annegent_anteaya: it's not you specifically, it's whether it makes sense to make the election official apart from the foundation20:58
mikalanteaya: I agree. There is no harm in the election officials investigating concerns.20:58
*** jdob has quit IRC20:58
anteayamikal: thank you20:58
anteayathat is all I am asking for20:58
anteayathe abiltiy to investigate20:58
annegent_and to me, the election officials serve an important role of knowing the CoC and reporting mechanisms but that they shouldn't be separate from the rest of the membership20:58
anteayaif the mistake was genuine20:58
anteayathat comes out in the facts20:59
markmcanteaya, would you (as the election official) be comfortable summarizing complaints with names redacted?20:59
*** topol has quit IRC20:59
markmcanteaya, publicly20:59
annegent_I'd rather the foundation do the investigations and that I know who to report to rather than spreading out the reporting further20:59
anteayamarkmc: if that is the structure that is decided upon, yes20:59
*** vivek-ebay has quit IRC20:59
*** lcheng has quit IRC20:59
markmcthat could be a part of the process20:59
markmcnot necessarily the whole thing20:59
anteayathough my preference would be to report to at least one other body before doing so20:59
markmcjust an idea20:59
jbrycethis last time around, i heard concerns after the election was already closed and a comment from those people that they weren’t sure how to report beforehand20:59
ttxdhellmann: I agree... which is why i don't really like eglynn's proposal saying "openly draw attention to cases where the actual behavior of candidates is questionable"20:59
*** fawadkhaliq has joined #openstack-meeting20:59
*** baoli has joined #openstack-meeting21:00
mikalannegent_: I think what anteaya is saying is that she's effectively the person delegated by the foundation to run the election, and therefore should be the first point of contact for election issues.21:00
jbryceso if anything, i think that some guidance on whom to contact is needed. whicever path is chosen21:00
anteayamikal: I'm delegated byt the tc21:00
ttxjbryce: +121:00
devanandajbryce: +121:00
mikalannegent_: this might be because for example we might need to stop and re-run the election, which would require the election official's involvement21:00
anteayamikal: the elections follow the tc charter, I report to the tc21:00
jbrycewhether that’s list, tc delegate, foundation officer…i think right now people just don’t know21:00
markmcanteaya, nicely clarified :)21:00
* anteaya nods21:00
mikalanteaya: sure, but that's the TC acting on behalf of the foundation, right?21:00
ttxok, time is running out21:00
ttxmikal: no21:01
dhellmannanteaya: so it sounds like you already know your reporting structure for issues, but people don't know they can report them to you21:01
anteayamikal: yes21:01
eglynnany closer to a decision point, folks?21:01
jeblairwell, the tc is chartered by the foundation bylaws, so there's a relationship there21:01
mikalLOL21:01
anteayadhellmann: yes21:01
anteayadhellmann: that is how I felt21:01
*** ramashri has joined #openstack-meeting21:01
anteayaI tried to get people to file a report21:01
ttxjeblair: yes, partly21:01
anteayathey wouldn't21:01
anteayabecause they didn't kow how it worked21:02
*** caleb_ has quit IRC21:02
ttxok... next steps?21:02
annegent_I'm okay with documenting the reporting... I'm struggling with documenting what behavior to report.21:02
sdagueanteaya: ok, so with that context, I think it's fine to clarify the reporting21:02
*** baoli has quit IRC21:02
anteayasdague: great thanks21:02
*** baoli_ has quit IRC21:02
*** nati_ueno has quit IRC21:02
anteayapick whatever body you want21:02
anteayathat is whom I will report to21:02
*** nati_ueno has joined #openstack-meeting21:02
ttxwe have until the next elections to pick the right thing :)21:02
dhellmannannegent_: is there harm in leaving the behavior open-ended, and applying judgement to the reports?21:02
devanandaI would think folks will continue to hesitate to report a preceived issue when they do not know what that report will lead to21:02
ttxand this meeting is over21:03
mikalSigh21:03
annegent_dhellmann: it's less risky from a legal standpoint, to me21:03
devanandabut knowing who to report to is, at least, something :)21:03
mikalI feel like sometimes IRC is the wrong format for these contentious issues21:03
devanandamikal: ++21:03
annegent_mikal: truth21:03
*** sweston_ has joined #openstack-meeting21:03
dhellmannmikal: +121:03
ttx#endmeeting21:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:03
anteayamikal: your living room for the next?21:03
mikalI want to lock you all in a room and not let you out until we reach a concensus21:03
openstackMeeting ended Tue Jun 24 21:03:45 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-06-24-20.02.html21:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-06-24-20.02.txt21:03
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-06-24-20.02.log.html21:03
annegent_lol21:03
anteayamikal: I'm bringing my cat21:04
mikalanteaya: heh, sure!21:04
ttxmikal: it would probably help a lot.21:04
mikalanteaya: and cats are welcome21:04
jogo_zehicle_at_dell:  DefCore question http://lists.openstack.org/pipermail/foundation/2014-June/001697.html21:04
jbrycemikal: but who do you escalate to if someone else has the key to the lock??21:04
*** termie has quit IRC21:04
mikalttx: in all seriousness, I'm starting to think we need a TC midcycle meetup21:04
mikalttx: I feel some of these issues will never be resolved this way21:04
ttxisn't that called OSCON?21:04
mikalttx: which sucks because they're important21:04
ttxoh wait21:04
ttxdhellmann, dolphm, notmyname, eglynn, markwash, jgriffith, mikal, zaneb, david-lyle, kmestery, SlickNik, SergeyLukjanov: around ?21:04
russellbmaybe if OSCON tickets weren't 18 thousand dollars or whatever21:04
dhellmanno/21:05
mikalttx: well, we haven't been explicit about that, so I for example am not approved to go to OSCON21:05
mesteryo/21:05
eglynno/21:05
dolphmo/21:05
david-lyleo/21:05
notmynamehere21:05
SlickNiko/21:05
markwasho/21:05
ttx#startmeeting project21:05
dhellmannmikal, ttx : yeah, I didn't even know I was supposed to ask21:05
openstackMeeting started Tue Jun 24 21:05:17 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:05
mikalI am not here. I am in a cloud of annoyed.21:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:05
jgriffitho/21:05
*** openstack changes topic to " (Meeting topic: project)"21:05
openstackThe meeting name has been set to 'project'21:05
ttxSorry for the lateness21:05
*** HenryG has quit IRC21:05
*** mrmartin has quit IRC21:05
mikalOk fine, I'm here21:05
ttxdamn TC cahir can't keep meeting on rails21:05
*** caleb_ has joined #openstack-meeting21:05
*** terriyu has joined #openstack-meeting21:05
ttxchair*21:05
SlickNiklol21:05
ttxAgenda for today is available at:21:05
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:05
mikalttx: yeah, _that_guy_21:05
ttx#topic News from the 1:1 sync points21:05
*** openstack changes topic to "News from the 1:1 sync points (Meeting topic: project)"21:06
ttxSee log at:21:06
ttx#link http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-06-24-08.01.html21:06
therveo/21:06
*** lsell has left #openstack-meeting21:06
ttxJuno-2 plans look relatively good, thanks to autokick.py invaluable contribution to clarity21:06
mikalttx: I feel like we should tell people to hold off on proposing dedicated sections for their things until the TC is finished arguing21:06
ttxmikal: we can parallelize21:06
ttx#topic Other program news21:07
*** openstack changes topic to "Other program news (Meeting topic: project)"21:07
ttxInfra, QA, Docs... anything you'd like to mention ?21:07
mtreinishttx: we started running some tempest jobs on trusty today21:07
mtreinishseems to be working well so far21:08
eglynnmtreinish: as an experiment?21:08
*** balajiiyer has quit IRC21:08
mesterymtreinish: Yay!21:08
eglynnmtreinish: ... or in anger?21:08
ttxmikal: we just need to have 1:1 discussions over those topics over the week, not just all at once in a one-hour slot21:08
SlickNikmtreinish: nice!21:08
*** igordcard has quit IRC21:08
*** julim has quit IRC21:08
mtreinisheglynn: as the first step in migrating over. I think they're in the check queue21:08
eglynnmtreinish: "in anger" == voting?21:08
eglynnmtreinish: cool21:08
mtreinishclarkb has been doing all the work21:08
mtreinisheglynn: yeah they're voting21:08
eglynnclarkb: kudos!21:08
* eglynn looks forward to the happy day when ceilo gates against mongodb :)21:09
*** kgriffs has joined #openstack-meeting21:09
clarkbeglynn: well it does gate against mongodb on cetnos6 right?21:09
clarkbeglynn: also pecan is guinea pigging for you and will run ceilometer tests on trusty21:09
eglynnclarkb: not py27 or tempest21:09
eglynnclarkb: but yeah, jut py26 units21:10
eglynn*just21:10
*** radix has quit IRC21:10
clarkbthat should happen real soon now then we can expand to the rest of ceilometer21:10
eglynnclarkb: excellent! :)21:10
*** jwang_ has quit IRC21:10
*** jwang_ has joined #openstack-meeting21:10
ttxok, anything else ?21:11
mtreinishnothing from me21:11
ttx#topic Common spec proposal/approval deadlines21:11
*** openstack changes topic to "Common spec proposal/approval deadlines (Meeting topic: project)"21:11
ttxAs was predicted, -specs review represents a lot of work21:11
dhellmannI'm anticipating markmc releasing a new version of oslo.messaging soon, so heads-up on that21:11
ttxnova wins with a specs backlog of 15421:12
ttxI still think design up-front will ultimately result in less wasted effort21:12
ttxBut as we get closer to feature freeze (juno-3) there will be a point in time where stuff under spec review can't possibly make it into Juno21:12
ttxAnd reviewing specs after that point will be a distraction from Juno work21:12
mikalWe're going to try a specs review day tomorrow to see if that helps21:12
ttxSo we discussed today the idea of a Juno spec proposal deadline21:12
ttxIt would come a few weeks before a Juno spec approval deadline21:12
mikalttx: did you see my email to openstack-dev with nova's proposed dates for such a thing?21:12
ttxwhich would come before the Feature proposal Freeze (the deadline for proposing implementation code for review)21:13
ttxmikal: yes21:13
ttxwhich in itself comes before Feature freeze (September 4)21:13
*** vivek-ebay has joined #openstack-meeting21:13
ttxThe question is, which projects are interested in following that, and is there convergence on dates (or is each project using different dates)21:13
thervettx, Sounds like a lot of process...21:13
ttxPersonally I think SpecApprovalDeadline (SAD) should be at least 3 weeks before FPF, so before July 3121:13
ttxAnd SpecProposalDeadline (SPD) at least two weeks before that, so before July 1721:13
ttxmikal proposed for Nova: July 3 for SPD, July 10 for SAD21:13
*** radix has joined #openstack-meeting21:13
ttxtherve: it might not make sense for smaller projects21:13
mikalWe had a bit of a balancing act21:13
*** eankutse has quit IRC21:13
*** dims__ has joined #openstack-meeting21:13
ttxmikal: One week between the two might not be long enough to give them a chance21:14
mikalWe wanted to have those earlier, but have left it too late21:14
eglynnI was think July 11th as SAD for ceilo, so similar21:14
ttxmikal: Also you could use the meetup for a quick approval round21:14
ttxtherve: I like the SAD acronym though21:14
mikalYeah, we can use the exceptions process to handle some of the fail here21:14
mesteryI'm good with the same dates as mikal has selected.21:14
mikalAnd learn from the experience21:14
mesterymikal: +121:14
markwashmikal: +121:14
mikalThe only contentious point seems to be when we open K specs21:14
thervettx, Smelling a great slogan :)21:14
mikalWhich is somethign I'm a little uncomfortable with dictating too closesly given I might not be the K PTL21:15
ttxmestery: do you think one week between proposal and approval will let you review/approve stuff proposed before SPD?21:15
mesteryFor K specs, the neutron drivers team is going to start putting -2 on specs we know won't land in Juno.21:15
mesteryttx: It's a bit tight, but I like the shorter gap, it forces the issue in some cases.21:15
dhellmannFor oslo, we're going to hold off on setting firm deadlines and judge submissions when they come. We aren't seeing a lot of specs now, and if something good comes in we might just approve it for K. We try to be in sync, but tend to run ahead of the other projects to allow syncing or adoption, so if we cut things off too early we're going to have huge bits of unused time in the schedule.21:15
*** hrybacki has joined #openstack-meeting21:15
mikalmestery: for ones previously approved, or those in flight, or both?21:15
ttxso maybe it only makes sense for neutron and nova21:16
mesterymikal: In flight which are proposed but not approved, and new submissions after the SAD.21:16
jgriffithmikal: honestly my policy on that is when K opens up21:16
ttxthey are the only ones with a huge backlog21:16
therveThe spec deadline makes for a short calendar. That's like half of the year where you can't land specs21:16
dolphmmestery: like, -2 pending re-proposal against a k* directory?21:16
mesterydolphm: Correct.21:16
*** rbowen has quit IRC21:16
*** dims_ has quit IRC21:16
mikaltherve: well, for nova its about not distracting cores from reviewing patches at certain points in the cycle21:16
mikalWe want to set the expectation that we're busy elsewhere21:16
mesteryAt the start of K, we'll wipe the specs repo clean and start fresh, at least that was my thinking. Things which were not approved need to be re-proposed.21:17
*** sarob_ has quit IRC21:17
eglynnwhy the -2 if there's a separate k* directory in the specs repo?21:17
mikalmestery: we talked about that too, we're also going to unmerge approved things which never had code proposed21:17
jgriffithmestery: _121:17
dolphmmestery: as long as things can land in the K dir during juno development, that sounds totally reasonable ++21:17
jgriffitherr.. +121:17
*** Michalik_ has quit IRC21:17
*** sarob has joined #openstack-meeting21:17
thervemikal, I understand. It'd be nice to be able to say "your spec looks good, but you can only propose the patch in release+1"21:17
thervewhich blueprints allowed21:17
jgriffithdolphm: I think trying to plan out to K right now is sort of a waste of my time21:17
mesteryeglynn: That's another way of doing it, but I'd like to hold off on adding hte K directory as long as possible, I tend to agree with mikal's reasoning on the distraction thing.21:17
jgriffithin terms of a spec at least21:17
eglynnmestery: fair enough21:18
*** Michalik_ has joined #openstack-meeting21:18
mikalPeople can always be writing their rst file in their homedir for a week or two21:18
mikalI don't think its a super big deal21:18
mesterymikal: Agreed21:18
*** lcheng has joined #openstack-meeting21:18
dolphmtherve: s/propose/have considered for merging/21:18
ttxjgriffith: what's cinder take on this ? You're hit with a lot of specs too21:18
dolphmtherve: or seriously consider as a release blocker21:19
jgriffithttx: I liked the two weeks out from submission freeze21:19
jgriffithttx: and like I said, I'm inclined to ignore anything K related until midway through J321:19
*** changbl has quit IRC21:19
*** cgoncalves has quit IRC21:19
thervedolphm, I guess my question is if we could distinguish specs merged into master with specs approved21:19
therveMaybe that defeats the purpose21:19
jgriffithttx: I alredy know there will be exceptions21:19
*** julienvey has joined #openstack-meeting21:20
jgriffithso I'd rather plan on it and make it "harder" after mid July21:20
jgriffiththerve: merged are approved... I'm confused?21:20
jgriffiththerve: you want a long term db to look at?21:20
eglynnjgriffith: merged in juno dir == approved, or?21:21
jgriffitheglynn: that just puts us backin the mess of LP IMO21:21
thervejgriffith, Yeah that's my point, we used to have more states with blueprints.21:21
jgriffiththe beauty of the specs for me is tracking and organization as well as detail21:21
ttxOK, so it looks like only a few projects would use that21:21
jgriffiththerve: and I think that was *bad*21:21
ttxI hear nova and neutron21:21
eglynnjgriffith: fair point, though the overhead of proposing/landing a specs patch sets the bar significantly higher?21:21
jgriffiththerve: chaos... look at al the "zombie" BP's out there21:22
jgriffitheglynn: true21:22
eglynn(as opposed to a drive-by filing on LP)21:22
thervejgriffith, Well nova spec backlog doesn't look great to me :)21:22
ttxso i propose each project announces its own date and deadlines21:22
*** eguz has quit IRC21:22
*** sarob has quit IRC21:22
jgriffitheglynn: but I'm not convinced with rapid pace of change etc it's worth my time to deal with things that are 3+ months out21:22
mesteryttx: +121:22
eglynnttx: subsidiarity, me likee! :)21:22
jgriffithttx: sigh21:22
mikaltherve: I think its great21:22
ttxand we'll look at it at the end of the cycle and see if we try to make it converged next time or not21:22
jgriffithttx: probably the right answer21:22
eglynnjgriffith: that's fair21:23
thervettx, °121:23
mikaltherve: we're being more honest about how much we think we can get done21:23
jgriffithbut means I'll be taking some flack again :)21:23
mikaltherve: and we're designing things before we argue in code reviews for the implementation or roll it back21:23
ttxjgriffith: blame nova for it ?21:23
mikaltherve: _and_ we're finally letting operators have a say21:23
jgriffithttx: my new motto ;)21:23
mikalI don't think its slower at all21:23
*** amcrn has quit IRC21:23
thervemikal, Fair enough. Heat clearly doesn't have that problem, so it's hard to imagine being in your shoes21:23
mikalIt just feels that way because we're setting people's expectations better21:23
*** cgoncalves has joined #openstack-meeting21:23
jgriffitheglynn: yeah.. part of this is I want to se how specs works out for a full ccle21:23
jgriffithcycle21:23
*** aimon_ has quit IRC21:24
ttxI don't think it's slower. We are building a longer pipeline, so it takes time before things are aligned to it properly21:24
dolphmttx: as long as we keep all the dates in a single wiki page / etherpad or something, so projects that want to settle on a single date can do so? if projects have a reason to deviate, that seems fair... but less than ideal21:24
jgriffithttx: +121:24
ttxbut then I'd expect things will flow better IN the new pipeline21:24
eglynnjgriffith: yep, exactly, it's a learning process for all21:24
jgriffiththe good thing I'm seeing is that specs actually lead to implemented code21:24
ttxwith less wated effort overall21:24
ttxwasted*21:24
*** sarob has joined #openstack-meeting21:24
jgriffithas opposed to willy-nilly bp's that never get acted on21:24
ttxdolphm: hmm, would you be interested in it ?21:25
jgriffiththerve: eglynn actually... that's an interesting point maybe21:25
jgriffiththerve: eglynn still submit a bp.... submit spec during window21:25
eglynnthe devs have to start to see the pay-off from the process as well /methinks21:25
ttxI can document them all in the juno release schedule21:25
jgriffithspec controls targetting so I'm happy that way21:25
*** sweston_ has quit IRC21:25
eglynn(before they *fully* buy into it)21:25
*** trey_h_ has joined #openstack-meeting21:25
ttxif you keep me in the lop21:25
ttxloop*21:26
*** thangp has quit IRC21:26
jgriffithttx: "lop" isn't that the sound I hear when my head falls off21:26
ttxno, that's "bop"21:26
jgriffithha21:26
dolphmttx: interested in deviating?21:26
ttxdolphm: no, interested in SPD/SAD in the first place21:27
*** ajo|mac has quit IRC21:27
dolphmttx: oh, yes.21:27
ttxoh ok. It felt like it was a nova-neutron discussion here21:27
eglynnso I thinking part of the documentation of this process should emphasize the *direct* benefits to devs21:27
ttx+cinder although I have difficulty to parse "I liked the two weeks out from submission freeze"21:27
*** nealph has joined #openstack-meeting21:28
*** trey_h has quit IRC21:28
eglynnotherwise it appears as a Kafkaesque maze to some ;)21:28
*** ajo|mac has joined #openstack-meeting21:28
ttxeglynn: ok, will document them all21:28
* ttx needs to docuemtn RequirementsFreeze anyway21:28
eglynnttx: thank you sir!21:28
ttxso i'll go on a wiki rampage21:28
ttxonce they are all documented i'll ML thread the thing21:28
* mestery gest out of ttx's way.21:28
eglynnLOL :)21:28
eglynnexcellent!21:29
ttx#action ttx to document SPD/SAD as optyional steps21:29
jgriffithttx: sorry... to clarify freeze spec submit/approve 1-2 weeks out from feature freeze21:29
ttx#action ttx to then start a ML thread about proposed dates and potential convergence21:29
*** Sukhdev has joined #openstack-meeting21:29
ttx#action ttx to document resultig dates to the Juno release schedule page21:29
jgriffithto ease confusion I'm going to "blame" nova and do whatever mikal does :)21:29
ttxsounds like a plan21:30
ttxfamous last words on this topic ?21:30
dolphmactually, we talked about a SAD for each *milestone* for keystone21:30
mikalLOL21:30
mesterydolphm: That's a lot of SADness. :)21:31
*** fawadkhaliq has quit IRC21:31
ttxmestery: you said it21:31
ttx#topic sahara-to-horizon merge21:31
*** openstack changes topic to "sahara-to-horizon merge (Meeting topic: project)"21:31
ttxSergeyLukjanov: around?21:31
dolphmyeah, but making the pipeline longer means that i'm starting to think we should have shorter milestones, to facilitate smaller changes21:31
ttxdavid-lyle: around?21:31
david-lyleyup21:31
annegent_there needs to be a blame mikal song like blame canada21:31
SergeyLukjanovttx, yup, I'm here21:31
* ttx sets up the boxing cage21:31
eglynnSAD is already taken as a TLA == "seasonal affective disorder" ;)21:31
* mestery makes some popcorn.21:31
ttxeglynn: awesome.21:31
mikalHeh21:32
dolphm#link https://blueprints.launchpad.net/sahara/+spec/merge-sahara-dashboard-to-horizon21:32
ttxSergeyLukjanov: i'll let you introduce the topic21:32
*** sweston_ has joined #openstack-meeting21:32
SergeyLukjanovttx, okay21:32
*** eghobo has joined #openstack-meeting21:32
SergeyLukjanovso, the topic is to merge sahara-dashboard to the horizon21:32
SergeyLukjanovI believe we have a bp for horizon too21:33
*** marcoemorais has quit IRC21:33
* ttx resists a Launchpad blame21:33
SergeyLukjanov#link https://blueprints.launchpad.net/horizon/+spec/merge-sahara-dashboard21:33
*** marcoemorais has joined #openstack-meeting21:34
ttxSergeyLukjanov: is that the list of proposed patches ? https://review.openstack.org/#/q/topic:bp/merge-sahara-dashboard,n,z21:34
SergeyLukjanovso, the current state is that all (or 90%) needed patches are under reviewf21:34
SergeyLukjanovttx, yup, I think it's a complete list21:35
ttxWas there progress on this since the last episode ? Like more patches posted, or some patches merged ?21:35
SergeyLukjanovhttps://review.openstack.org/#/q/horizon+comment:%22Sahara%22,n,z works good too21:35
*** julienvey has quit IRC21:35
SergeyLukjanovttx, one patch merged IIRC - client bindings21:35
*** julienvey has joined #openstack-meeting21:36
*** eghobo has quit IRC21:36
*** harlowja_ has quit IRC21:36
*** eghobo has joined #openstack-meeting21:36
*** harlowja has joined #openstack-meeting21:36
ttxdavid-lyle: so the main issue on your side is the size of the patch ?21:36
*** amcrn has joined #openstack-meeting21:36
david-lylettx: getting core focus on it21:36
annegent_I want to raise a slight concern about how to document21:36
annegent_horizon is core, sahara is not21:36
SergeyLukjanovthere were a number of reviews for other patches and comments are resolved now, but the size of patches is very big, so, needs more iterations21:37
david-lyleI think that has been addressed21:37
ttxdavid-lyle: ok21:37
ttxannegent_: "core" ?21:37
annegent_ttx: the docs mission scope is only for core21:37
david-lylesahara is integrated21:37
annegent_ttx: we try to get to integrated but don't promise21:37
david-lyleah21:37
ttxannegent_: what definition of "core" are you using for that ?21:38
*** hrybacki has quit IRC21:38
annegent_just saying it makes for a bit of doc difficulty across "how do I install OpenStack"21:38
*** pberis has joined #openstack-meeting21:38
annegent_ttx: the one in effect when we made our mission statement in july 201321:38
*** shakamunyi has quit IRC21:38
*** SridharG has quit IRC21:38
*** enikanorov_ has quit IRC21:38
annegent_it's a known difficulty; just noting it here for others to note as a concern21:38
*** enikanorov_ has joined #openstack-meeting21:38
ttxannegent_: hmm, not sure what that would include :)21:38
*** padkrish has joined #openstack-meeting21:38
*** rediskin has left #openstack-meeting21:38
ttxanyway, I see your point21:39
*** markvoelker1 has quit IRC21:39
thervedavid-lyle, Sorry if I say something dumb, but would it be possible for horizon to have integration points (plugins) so that sahara is in horizon the service but not horizon the code base?21:39
ttxhow does that influence the discussion here ?21:39
*** shakamunyi has joined #openstack-meeting21:39
ttxintegrated projects must be.. well.... integrated21:39
*** shakamunyi has quit IRC21:39
jogo_Heat is not core either21:39
annegent_they can be integrated but we're not promising docs21:39
ttxso sahara dashboard must be in horizon21:40
eglynntherve: yeah out-of-tree dashboards, that's what I was thinking also21:40
annegent_and by we I mean the doc team itself -- the horizon and sahara team are welcome to figure it out21:40
*** shakamunyi has joined #openstack-meeting21:40
david-lyletherve, we have a plugin mechanism and that's how the sahara dashboard was created, but if it's not in Horizon it becomes more difficult to maintain in the long run21:40
*** shakamunyi has quit IRC21:40
ttxeglynn: that already exists, there is a sahara-dashboard21:40
therveThat problem is meant to happen again, with solum for example21:40
SergeyLukjanovtherve, it's already done as sahara-dashboard project and we're moving now it into the horizon21:40
annegent_jogo_: sure but we (docs team) are working with them on integration in the user guide this cycle, it's just a few cycles later than their first integrated release21:40
*** hrybacki has joined #openstack-meeting21:40
ttxit's supposed to be integrated within horizon now that sahara is integrated21:41
eglynnttx: I guess the question is, why doesn't that suffice?21:41
eglynnttx: (... to meet the integartion requirements?)21:41
ttxeglynn: because horizon ships with dashboard integration for all the other integrated buts21:41
ttxbits*21:41
thervedavid-lyle, SergeyLukjanov: Okay. I feel that if we could keep things smaller we should, but I understand maintenance would be easier this way21:41
ttxso it's a "first cycle requirement" to get your dashboard plugin into horizon mainline21:42
ttxit neevr was an issue before21:42
jogo_annegent_: ahh so core first21:42
david-lyleThere shouldn't be a reason we can't merge Sahara, it just takes time to integrate an 8k loc dashboard even if already existant21:42
annegent_jogo_: right21:42
*** vkmc has joined #openstack-meeting21:43
*** vkmc has quit IRC21:43
*** vkmc has joined #openstack-meeting21:43
ttxSergeyLukjanov: you feel like it's not going fast enough for a merge in Juno ?21:43
annegent_ttx: david-lyle: any reason sahara can't be in a separate repo with separate reviewers under the Dashboard program?21:43
*** shakamunyi has joined #openstack-meeting21:43
annegent_I might not understand the technical limits21:43
eglynnk, so it seems that evolving the dashboard for incubating proects *within* horizon somehow would avoid the need for a mega-merge post-integration?21:43
therveannegent_, From what we're talking, it's mostly a maintenance problem21:43
ttxannegent_: all the other integrated bits are in horizon repo, so why would we specialcase sahara ?21:43
eglynnincubating *projects21:43
david-lyleannegent_: we could take that approach, integration testing becomes more involved21:43
annegent_ttx: because it's the biggest so far?21:44
SergeyLukjanovttx, it's difficult to say now - all patches are on review, but /me and david-lyle think that it could be done in time for juno21:44
*** hrybacki has quit IRC21:44
*** aimon has joined #openstack-meeting21:44
dhellmannyeah, making changes to the APIs the dashboards use is harder if they're in separate repos, because you have to figure out how to stage the changes and make all of them continue to work instead of doing it all in one patch21:44
SergeyLukjanovttx, there is already a huge work done on adjusting some parts for the whole chain of changes21:44
annegent_dhellmann: ouch yeah then21:44
david-lylewe could do that with all service panels, but as soon as they become interdependent we get into troubled waters21:44
*** belmoreira has quit IRC21:44
devanandathis discussion sounds similar to ironic's nova virt driver "prepare to merge during incubation" discussion.21:44
devanandaalso worth noting that horizon will face the same intergration for an ironic dashboard soon21:45
eglynnbig-bang merge of pre-existing out-of-tree dashboard post-integration inevitably leads to a 8 KLOC set of patches festering on gerrit21:45
ttxSergeyLukjanov: OK, not sure we can do to help you guys sort it out. Anything you need from us?21:45
eglynnwhat if horizon had an incubation sandbox?21:45
*** hrybacki has joined #openstack-meeting21:45
thervedhellmann, I guess one question would be if horizon shouldn't provide stable APIs for allowing custom integration21:46
david-lylewe've pulled in the tuskar-ui repo because of the scope and size of that21:46
dhellmannyeah, the policy in oslo has shifted to taking the first version of something like that as-is and then interating21:46
ttxeglynn: it's a bit of the same problem with nova ironic driver21:46
eglynnin-tree, then post-intregation could be just a matter of promoting out of a contrib area21:46
SergeyLukjanovttx, I think nope, I've added this point to agenda as we agreed with you to raise this topic every several weeks to monitor status21:46
eglynnttx: fair point21:46
ttxyou basically want to review in the original repo and just merge it all21:46
dhellmanntherve: I'd love it if they did, since I want to add some dashboards for Dreamhost, but if they don't now we can't block sahara on that21:46
david-lyleso Horizon program has horizon and tuskar-ui repos21:46
devanandattx: review code in antoher repo has not worked for the nova.virt.ironic driver at all21:46
devanandattx: for that that's worth21:46
therveeglynn, We somewhat do that in Heat for resources21:46
*** esker has quit IRC21:46
eglynntherve: interesting ... does the approach work?21:47
ttxdevananda: yes, "you want" wasn't meant as a recommendation :)21:47
*** esker has joined #openstack-meeting21:47
ttxSergeyLukjanov: ok21:47
therveeglynn, I think so? We run the tests as part of everything else, but don't install the contrib resources by default. Obviously the amount of code is smaller.21:47
*** kgriffs is now known as kgriffs|afk21:47
ttxSergeyLukjanov: From a release management perspective, i can only reiterate that having dashboard functionality for integrated projects is high on the release priority list21:48
eglynntherve: smaller and also perhaps most "testable"?21:48
therveeglynn, Possibly yeah21:48
ttxSergeyLukjanov: so yes, we can follow up regularly21:48
SergeyLukjanovttx, ack21:48
david-lylettx: I think Horizon will be able to integrate the dashboard in J-221:48
*** changbl has joined #openstack-meeting21:48
ttxdavid-lyle: I thin k that's a good target. We have some room for overflowing to early J3 that way21:49
SergeyLukjanovdavid-lyle, it'll be awesome - we'll have some time to implement dashboard features21:49
*** jogo_ has quit IRC21:49
SergeyLukjanovttx, ++21:49
ttx#topic Open discussion21:49
*** openstack changes topic to "Open discussion (Meeting topic: project)"21:49
ttxWe can continue discussing better options to integrate 8K lines of code in one shot, or discuss anything else21:50
lifelessgulp21:50
ttxwell, not one shot :)21:50
ttxbut it's true that it will bite us again21:50
* dhellmann puts down his shot of whiskey21:50
david-lyleideally what I think would help is better inclusion of the Horizon team as part of UI development in incubated projects, the problem of course being resource constraint, pay me now or pay me later I suppose21:51
eglynnany opinions on the usefulness or otherwise of the PTL webinars?21:51
SergeyLukjanovttx, yeah, it'll happens again ~ each cycle21:51
*** yjiang5_away is now known as yjiang521:51
*** esker has quit IRC21:51
* eglynn was disappointed not a single question from the floor at the cinder/ceilo webinar earlier today21:51
ttxdavid-lyle: sahara had dashboards already developed -- did that actually help or hurt ? I can see that development goes faster but review goes slower ?21:52
dhellmanneglynn: how many people were listening live? I haven't done mine yet.21:52
mikaleglynn: do we have numbers on if people actually attend them?21:52
*** armax has joined #openstack-meeting21:52
ttxeglynn: dunno, that will be my first. Not sure what to expect21:52
eglynndhellmann: dunno, I wasn't on the meetingburner (just phone + slides on a tablet)21:52
eglynnmikal: apparently more traffic on the youtube recording after the fact21:53
david-lylettx: it certainly helps, but now horizon core is looking at this thing cold and not watching it come together. quick ramp up and try to make sure it's consistent with the rest of Horizon21:53
*** rockyg has quit IRC21:53
mesteryeglynn: How long did you get to present? I21:53
eglynnmikal: ... otherwise relatively small attendence (10s as opposed to 100s)21:53
mesteryeglynn: I'm up Thursday :)21:53
*** nati_ueno has quit IRC21:53
david-lyleso far it looks like it was done well, but I haven't gotten to the end yet21:53
*** caleb_ has quit IRC21:53
david-lyledon't ruin it for me21:53
SergeyLukjanovttx, david-lyle, for example, in sahara, we've started dev. of both server side and dashboard in one day and the first version of dashboard has been released right after the first working version of server side21:53
eglynnmestery: 20 mins, I went overtime tho'21:53
mesteryeglynn: :)21:53
*** caleb_ has joined #openstack-meeting21:53
*** nati_ueno has joined #openstack-meeting21:54
david-lylettx: there's now way we would have been able to reproduce in Juno the same degree of API coverage starting from scratch21:54
*** hrybacki_ has joined #openstack-meeting21:54
ttxdavid-lyle: yeah. Ican see benefits to both approaches21:55
*** hrybacki has quit IRC21:55
ttxAnything else, anyone ?21:55
devanandadavid-lyle: given this context, any thoughts or suggestions w.r.t. tuskar / ironic UI integration next cycle?21:55
*** mrda-away is now known as mrda21:56
*** eharney has quit IRC21:56
david-lyledevananda: getting Horizon core looking at the patches now or designs at least would aid the adoption process21:56
*** annegent_ has quit IRC21:57
devanandadavid-lyle: ack21:57
*** neelashah has quit IRC21:58
*** amcrn has quit IRC21:58
*** amcrn_ has joined #openstack-meeting21:58
*** caleb_ has quit IRC21:58
ttxok, looks like that clsoes it21:59
ttx#endmeeting21:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:59
openstackMeeting ended Tue Jun 24 21:59:04 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2014/project.2014-06-24-21.05.html21:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2014/project.2014-06-24-21.05.txt21:59
ttxthanks everyone!21:59
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2014/project.2014-06-24-21.05.log.html21:59
*** shakamunyi has quit IRC21:59
therveThanks!21:59
mesteryThanks ttx!21:59
eglynngood night folks!21:59
*** shakamunyi has joined #openstack-meeting22:00
SergeyLukjanovttx, thx22:00
*** jtomasek has joined #openstack-meeting22:00
*** baoli has joined #openstack-meeting22:00
*** dhellman_ has quit IRC22:00
*** SlickNik has left #openstack-meeting22:02
*** denis_makogon has quit IRC22:02
*** aimon has quit IRC22:03
*** jsavak has quit IRC22:03
*** jpeeler has quit IRC22:04
*** craigbr has quit IRC22:07
*** jtomasek has quit IRC22:07
*** Michalik_ has quit IRC22:07
*** caleb_ has joined #openstack-meeting22:08
*** kayaliu_ has joined #openstack-meeting22:09
*** caleb_ has quit IRC22:10
*** tbarron has quit IRC22:10
*** pberis has quit IRC22:11
*** jaypipes has quit IRC22:11
*** miqui has quit IRC22:11
*** pballand has joined #openstack-meeting22:12
*** paulmo_ has joined #openstack-meeting22:12
*** nijaba has quit IRC22:13
*** pdmars has quit IRC22:13
*** nijaba has joined #openstack-meeting22:15
*** nijaba has quit IRC22:15
*** nijaba has joined #openstack-meeting22:15
*** marekd is now known as marekd|away22:15
*** ivasev has quit IRC22:16
*** paulmo_ has left #openstack-meeting22:18
*** bknudson has quit IRC22:18
*** shakamunyi has quit IRC22:20
*** zz_blogan is now known as blogan22:23
*** Michalik_ has joined #openstack-meeting22:25
*** kayaliu_ has quit IRC22:25
*** kayaliu_ has joined #openstack-meeting22:26
*** HenryG has joined #openstack-meeting22:27
*** markmc has quit IRC22:28
*** shakamunyi has joined #openstack-meeting22:29
*** nelsnelson has quit IRC22:30
*** noslzzp has joined #openstack-meeting22:31
*** vijendar1 has quit IRC22:31
*** Longgeek has quit IRC22:32
*** eglynn has quit IRC22:32
*** penguinRaider has quit IRC22:33
*** sushils has quit IRC22:34
*** craigbr has joined #openstack-meeting22:34
*** MaxV_ has joined #openstack-meeting22:34
*** MaxV has quit IRC22:34
*** yamahata has quit IRC22:35
*** IngoH has joined #openstack-meeting22:36
*** Demitar has quit IRC22:36
*** sushils has joined #openstack-meeting22:36
*** nijaba_ has joined #openstack-meeting22:36
*** nijaba has quit IRC22:36
*** IngoH has quit IRC22:36
*** ajo|mac has quit IRC22:37
*** lcheng has quit IRC22:41
*** nijaba_ has quit IRC22:45
*** esel has quit IRC22:46
*** boris-42 has quit IRC22:46
*** MaxV_ has quit IRC22:47
*** yamahata has joined #openstack-meeting22:48
*** eghobo has quit IRC22:50
*** Penick has quit IRC22:51
*** nijaba has joined #openstack-meeting22:51
*** jmontemayor_ has quit IRC22:52
*** caleb_ has joined #openstack-meeting22:52
*** msdubov has quit IRC22:52
*** marcoemorais has quit IRC22:53
*** marcoemorais has joined #openstack-meeting22:53
*** marcoemorais has quit IRC22:54
*** marcoemorais has joined #openstack-meeting22:54
*** caleb_ has quit IRC22:55
*** marcoemorais1 has joined #openstack-meeting22:55
*** rbowen has joined #openstack-meeting22:56
*** marcoemorais2 has joined #openstack-meeting22:56
*** marcoemorais2 has quit IRC22:56
*** fnaval has quit IRC22:56
*** hashar has quit IRC22:56
*** marcoemorais2 has joined #openstack-meeting22:56
*** Penick has joined #openstack-meeting22:58
*** nijaba has quit IRC22:58
*** marcoemorais has quit IRC22:59
*** marcoemorais1 has quit IRC22:59
*** caleb_ has joined #openstack-meeting23:00
*** caleb_ has quit IRC23:00
*** caleb_ has joined #openstack-meeting23:00
*** rbak has quit IRC23:01
*** Leonr has quit IRC23:01
*** lbragstad has quit IRC23:01
*** boris-42 has joined #openstack-meeting23:02
*** caleb_ has quit IRC23:02
*** msdubov has joined #openstack-meeting23:02
*** atiwari has quit IRC23:03
*** julienvey has quit IRC23:04
*** chuckC has quit IRC23:04
*** rbowen has quit IRC23:04
*** changbl has quit IRC23:05
*** pballand has quit IRC23:06
*** meteorfox has quit IRC23:07
*** _nadya_ has joined #openstack-meeting23:08
*** yamahata has quit IRC23:08
*** otherwiseguy has quit IRC23:09
*** ddieterly has quit IRC23:09
*** Penick has quit IRC23:11
*** _nadya_ has quit IRC23:12
*** esker has joined #openstack-meeting23:13
*** moha_hunt has quit IRC23:14
*** banix has quit IRC23:15
*** mattgriffin has quit IRC23:16
*** arnaud__ has joined #openstack-meeting23:17
*** hockeynu_ has joined #openstack-meeting23:18
*** Penick has joined #openstack-meeting23:18
*** kayaliu_ has quit IRC23:23
*** bdpayne_ has joined #openstack-meeting23:23
*** eghobo has joined #openstack-meeting23:24
*** mwagner_lap has joined #openstack-meeting23:25
*** eghobo has quit IRC23:25
*** eghobo has joined #openstack-meeting23:25
*** bdpayne has quit IRC23:26
*** hockeynu_ has quit IRC23:26
*** markwash has quit IRC23:26
*** Sukhdev has quit IRC23:29
*** brucer has joined #openstack-meeting23:29
*** chuckC has joined #openstack-meeting23:35
*** sushils has quit IRC23:38
*** bauzas has quit IRC23:39
*** lsell has joined #openstack-meeting23:40
*** sushils has joined #openstack-meeting23:40
*** david-lyle has quit IRC23:41
*** david-lyle has joined #openstack-meeting23:42
*** jaypipes has joined #openstack-meeting23:43
*** lbragstad has joined #openstack-meeting23:43
*** elambert has quit IRC23:44
*** oomichi has joined #openstack-meeting23:45
*** marcoemorais2 has quit IRC23:45
*** Penick has quit IRC23:45
*** marcoemorais has joined #openstack-meeting23:45
*** amalagon has quit IRC23:45
*** Michalik_ has quit IRC23:45
*** marcoemorais has quit IRC23:46
*** Michalik_ has joined #openstack-meeting23:46
*** marcoemorais has joined #openstack-meeting23:46
*** david-lyle has quit IRC23:46
*** gokrokve has quit IRC23:47
*** otter768 has joined #openstack-meeting23:50
*** marcoemorais has quit IRC23:52
*** Penick has joined #openstack-meeting23:52
*** marcoemorais has joined #openstack-meeting23:52
*** tris has quit IRC23:52
*** tris has joined #openstack-meeting23:55
*** yamahata has joined #openstack-meeting23:57
*** harlowja_ has joined #openstack-meeting23:58
*** safchain has quit IRC23:58
*** yingjun has joined #openstack-meeting23:58
*** baoli has quit IRC23:59
*** baoli has joined #openstack-meeting23:59

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