Tuesday, 2014-06-10

*** stevemar has joined #openstack-meeting00:02
*** shivharis has quit IRC00:03
*** moha_hunt has joined #openstack-meeting00:03
*** vjay3 has quit IRC00:05
*** VijayB has quit IRC00:05
*** jjmb has joined #openstack-meeting00:05
*** stevemar2 has joined #openstack-meeting00:06
*** natarajk has quit IRC00:06
*** bgorski has quit IRC00:06
*** colinmcnamara has joined #openstack-meeting00:07
*** vivek-ebay has quit IRC00:09
*** stevemar has quit IRC00:10
*** bgorski has joined #openstack-meeting00:10
*** zhiyan_ is now known as zhiyan00:10
*** reed has quit IRC00:11
*** fawadkhaliq has quit IRC00:12
*** VijayB_ has joined #openstack-meeting00:13
*** eankutse has joined #openstack-meeting00:16
*** samcdona has joined #openstack-meeting00:17
*** manishg has joined #openstack-meeting00:19
*** nedbat_ has quit IRC00:19
*** nedbat has joined #openstack-meeting00:20
*** colinmcnamara has quit IRC00:20
*** yingjun has joined #openstack-meeting00:21
*** manishg_ has joined #openstack-meeting00:21
*** weshay has joined #openstack-meeting00:22
*** vermarah__ has quit IRC00:22
*** vermarah_ has quit IRC00:22
*** vermarah has quit IRC00:22
*** manishg has quit IRC00:23
*** manishg_ is now known as manishg00:23
*** gokrokve has quit IRC00:24
*** eankutse has quit IRC00:26
*** matsuhashi has joined #openstack-meeting00:27
*** tomoe_ has quit IRC00:27
*** eguz has quit IRC00:28
*** yingjun has quit IRC00:29
*** yingjun has joined #openstack-meeting00:29
*** leeantho has quit IRC00:30
*** jaypipes has quit IRC00:32
*** ArxCruz_ has joined #openstack-meeting00:32
*** ArxCruz has quit IRC00:33
*** vjay3 has joined #openstack-meeting00:33
*** novas0x2a|laptop has quit IRC00:34
*** Kanzhe has quit IRC00:35
*** pdehaye has quit IRC00:36
*** chuckC has quit IRC00:37
*** marcoemorais has quit IRC00:38
*** marcoemorais has joined #openstack-meeting00:38
*** banix has joined #openstack-meeting00:41
*** vjay3 has quit IRC00:41
*** novas0x2a|laptop has joined #openstack-meeting00:43
*** dstanek_zzz is now known as dstanek00:44
*** yingjun has quit IRC00:44
*** bdpayne has quit IRC00:44
*** yingjun has joined #openstack-meeting00:44
*** whenry has joined #openstack-meeting00:44
*** hrybacki has quit IRC00:44
*** nedbat has quit IRC00:46
*** nedbat has joined #openstack-meeting00:46
*** cjellick has quit IRC00:47
*** cjellick has joined #openstack-meeting00:47
*** chuckC has joined #openstack-meeting00:50
*** nedbat has quit IRC00:50
*** cjellick has quit IRC00:51
*** yamahata has quit IRC00:52
*** dstanek is now known as dstanek_zzz00:54
*** paulbc has quit IRC00:54
*** nedbat has joined #openstack-meeting00:56
*** nedbat has quit IRC00:56
*** colinmcnamara has joined #openstack-meeting00:58
*** colinmcnamara has quit IRC01:00
*** Mandell has quit IRC01:00
*** vjay3 has joined #openstack-meeting01:00
*** Mandell has joined #openstack-meeting01:01
*** colinmcnamara has joined #openstack-meeting01:02
*** Mandell has quit IRC01:03
*** kayaliu_ has joined #openstack-meeting01:03
*** vjay3 has quit IRC01:06
*** Mandell has joined #openstack-meeting01:06
*** topol has joined #openstack-meeting01:07
*** kayaliu_ has quit IRC01:07
*** rm_work is now known as rm_work|away01:07
*** tkay has quit IRC01:08
*** kayaliu_ has joined #openstack-meeting01:09
*** arnaud has joined #openstack-meeting01:10
*** haomaiwang has joined #openstack-meeting01:10
*** mberlin has joined #openstack-meeting01:11
*** mberlin1 has quit IRC01:11
*** haomaiw__ has joined #openstack-meeting01:12
*** haomaiwang has quit IRC01:15
*** Mandell has quit IRC01:16
*** flaviof is now known as flaviof_zzz01:20
*** sweston has joined #openstack-meeting01:20
*** yaguang has joined #openstack-meeting01:20
*** ramashri has quit IRC01:22
*** fnaval has joined #openstack-meeting01:24
*** caleb_ has joined #openstack-meeting01:24
*** marcoemorais has quit IRC01:26
*** devlaps has quit IRC01:26
*** adalbas has joined #openstack-meeting01:27
*** adalbas has quit IRC01:27
*** vivek-ebay has joined #openstack-meeting01:27
*** marun has quit IRC01:28
*** shakayumi has joined #openstack-meeting01:30
*** shakayumi has quit IRC01:30
*** arnaud has quit IRC01:31
*** nedbat has joined #openstack-meeting01:31
*** nosnos has joined #openstack-meeting01:33
*** nati_uen_ has quit IRC01:36
*** yamahata has joined #openstack-meeting01:37
*** rickerc has quit IRC01:38
*** prad has quit IRC01:38
*** bgorski has quit IRC01:39
*** colinmcnamara has quit IRC01:40
*** shakayumi has joined #openstack-meeting01:41
*** shakayumi has quit IRC01:41
*** igordcard has quit IRC01:41
*** Daisy has joined #openstack-meeting01:41
*** xuhanp has joined #openstack-meeting01:42
*** dstanek_zzz is now known as dstanek01:44
*** neelashah has joined #openstack-meeting01:45
*** weshay has quit IRC01:47
*** kashyapk has joined #openstack-meeting01:49
*** saurabhs has left #openstack-meeting01:50
*** rickerc has joined #openstack-meeting01:53
*** rkukura has joined #openstack-meeting01:53
*** rkukura has left #openstack-meeting01:53
*** neelashah has quit IRC01:53
*** neelashah has joined #openstack-meeting01:54
*** dstanek is now known as dstanek_zzz01:54
*** hs634 has left #openstack-meeting01:54
*** kashyapk has quit IRC01:55
*** bgorski has joined #openstack-meeting01:55
*** gokrokve has joined #openstack-meeting01:56
*** hrybacki has joined #openstack-meeting02:01
*** sweston has quit IRC02:01
*** caleb_ has quit IRC02:02
*** caleb_ has joined #openstack-meeting02:03
*** kayaliu__ has joined #openstack-meeting02:03
*** kayaliu_ has quit IRC02:03
*** rickerc has quit IRC02:07
*** amcrn has quit IRC02:08
*** vpanizo has quit IRC02:08
*** vpanizo has joined #openstack-meeting02:09
*** sweston has joined #openstack-meeting02:09
*** rkukura has joined #openstack-meeting02:10
*** colinmcnamara has joined #openstack-meeting02:10
*** blogan has joined #openstack-meeting02:13
*** mlavalle has quit IRC02:13
*** sweston has quit IRC02:13
*** rickerc has joined #openstack-meeting02:13
*** vpanizo has quit IRC02:13
*** nkubota has joined #openstack-meeting02:15
*** gokrokve has quit IRC02:18
*** tomoe_ has joined #openstack-meeting02:19
*** reed has joined #openstack-meeting02:19
*** sankarshan is now known as sankarshan_away02:20
*** schwicht has quit IRC02:20
*** Daisy has quit IRC02:20
*** whenry has quit IRC02:22
*** nati_ueno has joined #openstack-meeting02:23
*** ramashri has joined #openstack-meeting02:24
*** novas0x2a|laptop has quit IRC02:25
*** reed has quit IRC02:25
*** zhikunliu has joined #openstack-meeting02:26
*** colinmcnamara has quit IRC02:26
*** sbalukoff has quit IRC02:27
*** epico has joined #openstack-meeting02:28
*** kayaliu__ has quit IRC02:30
*** VijayB_ has quit IRC02:31
*** manishg has quit IRC02:32
*** VijayB has joined #openstack-meeting02:32
*** colinmcnamara has joined #openstack-meeting02:33
*** dstanek_zzz is now known as dstanek02:33
*** arnaud has joined #openstack-meeting02:33
*** VijayB has quit IRC02:37
*** jjmb has quit IRC02:38
*** paragan has joined #openstack-meeting02:41
*** paragan has joined #openstack-meeting02:41
*** kayaliu__ has joined #openstack-meeting02:41
*** Michalik_ has joined #openstack-meeting02:41
*** jjmb has joined #openstack-meeting02:43
*** jjmb has quit IRC02:43
*** ramashri has quit IRC02:45
*** mspreitz has joined #openstack-meeting02:46
*** primeministerp has quit IRC02:46
*** Daisy has joined #openstack-meeting02:47
*** matiu has joined #openstack-meeting02:49
*** matiu has joined #openstack-meeting02:49
*** rwsu has quit IRC02:52
*** dstanek is now known as dstanek_zzz02:52
*** hrybacki has quit IRC02:56
*** nedbat has quit IRC02:59
*** tvoran has joined #openstack-meeting03:00
*** bgorski has quit IRC03:01
*** tvoran has quit IRC03:01
*** tvoran has joined #openstack-meeting03:01
*** colinmcnamara has quit IRC03:03
*** dstanek_zzz is now known as dstanek03:04
*** crc32 has quit IRC03:05
*** colinmcnamara has joined #openstack-meeting03:08
*** nati_ueno has quit IRC03:10
*** ramishra has joined #openstack-meeting03:10
*** david-lyle has joined #openstack-meeting03:11
*** lbragstad has quit IRC03:11
*** mtanino has quit IRC03:11
*** prad has joined #openstack-meeting03:12
*** vkmc has quit IRC03:15
*** Michalik_ has quit IRC03:17
*** zhiyan is now known as zhiyan_03:20
*** SridharG has joined #openstack-meeting03:20
*** sankarshan_away is now known as sankarshan03:24
*** bdpayne has joined #openstack-meeting03:25
*** zhiyan_ is now known as zhiyan03:26
*** colinmcnamara has quit IRC03:27
*** haomaiw__ has quit IRC03:27
*** haomaiwang has joined #openstack-meeting03:27
*** kayaliu__ has quit IRC03:29
*** kayaliu_ has joined #openstack-meeting03:29
*** caleb_ has quit IRC03:29
*** colinmcnamara has joined #openstack-meeting03:30
*** colinmcnamara has quit IRC03:31
*** tvoran_ has joined #openstack-meeting03:31
*** tvoran_ has quit IRC03:33
*** tvoran_ has joined #openstack-meeting03:34
*** SridharG has quit IRC03:35
*** tvoran has quit IRC03:35
*** colinmcnamara has joined #openstack-meeting03:35
*** jjmb has joined #openstack-meeting03:37
*** colinmcnamara has quit IRC03:39
*** gcb has joined #openstack-meeting03:41
*** arnaud has quit IRC03:42
*** nosnos has quit IRC03:43
*** vjay3 has joined #openstack-meeting03:45
*** vpanizo has joined #openstack-meeting03:48
*** dguitarbite has joined #openstack-meeting03:49
*** Longgeek has joined #openstack-meeting03:52
*** dims_ has quit IRC03:53
*** eghobo has joined #openstack-meeting03:55
*** eghobo has quit IRC03:55
*** eghobo has joined #openstack-meeting03:56
*** coolsvap|afk is now known as coolsvap03:57
*** Longgeek has quit IRC03:57
*** dguitarbite has quit IRC04:00
*** jamespage has quit IRC04:00
*** jamespage has joined #openstack-meeting04:00
*** jamespage has quit IRC04:00
*** jamespage has joined #openstack-meeting04:00
*** sweston has joined #openstack-meeting04:00
*** tvoran_ has quit IRC04:01
*** yamamoto_ has joined #openstack-meeting04:01
*** MarkAtwood has joined #openstack-meeting04:02
*** MarkAtwood has quit IRC04:02
*** whenry has joined #openstack-meeting04:06
*** cknight has joined #openstack-meeting04:13
*** Michalik_ has joined #openstack-meeting04:13
*** johnpur has joined #openstack-meeting04:13
*** novas0x2a|laptop has joined #openstack-meeting04:14
*** cknight has quit IRC04:14
*** neelashah has quit IRC04:16
*** johnpur has left #openstack-meeting04:16
*** ramishra has quit IRC04:17
*** Michalik_ has quit IRC04:18
*** fnaval has quit IRC04:18
*** shankar has joined #openstack-meeting04:19
*** ramishra has joined #openstack-meeting04:21
*** lcheng has joined #openstack-meeting04:21
*** ngoswami has joined #openstack-meeting04:22
*** kashyapk has joined #openstack-meeting04:22
*** nelsnels_ has quit IRC04:22
*** nosnos has joined #openstack-meeting04:24
*** gokrokve has joined #openstack-meeting04:25
*** tkay has joined #openstack-meeting04:25
*** kashyapk has quit IRC04:26
*** kashyapk has joined #openstack-meeting04:26
*** yisun has joined #openstack-meeting04:27
*** david-lyle has quit IRC04:33
*** marcoemorais has joined #openstack-meeting04:34
*** yingjun has quit IRC04:35
*** yingjun has joined #openstack-meeting04:36
*** eghobo has quit IRC04:36
*** yingjun has joined #openstack-meeting04:36
*** marcoemorais1 has joined #openstack-meeting04:36
*** gokrokve has quit IRC04:37
*** lbragstad has joined #openstack-meeting04:38
*** Mandell has joined #openstack-meeting04:38
*** marcoemorais has quit IRC04:39
*** whenry has quit IRC04:41
*** dims_ has joined #openstack-meeting04:46
*** banix has quit IRC04:46
*** kayaliu_ has quit IRC04:47
*** deepakcs has joined #openstack-meeting04:48
*** dstanek is now known as dstanek_zzz04:50
*** eghobo has joined #openstack-meeting04:50
*** Praveen has joined #openstack-meeting04:50
*** ngoswami has quit IRC04:50
*** dims_ has quit IRC04:50
*** elo2 has joined #openstack-meeting04:51
*** ildikov has quit IRC04:51
*** ArxCruz_ has quit IRC04:52
*** Daisy has quit IRC04:53
*** alonha has joined #openstack-meeting04:53
*** elo has quit IRC04:53
*** eghobo has quit IRC04:54
*** eghobo has joined #openstack-meeting04:54
*** Praveen has quit IRC04:54
*** whenry has joined #openstack-meeting04:57
*** topol has quit IRC04:57
*** gokrokve has joined #openstack-meeting04:58
*** gokrokve has quit IRC04:58
*** harlowja is now known as harlowja_away04:59
*** gongysh has joined #openstack-meeting04:59
*** hareeshpc has joined #openstack-meeting04:59
*** s3wong has joined #openstack-meeting04:59
yamahatahi05:00
swestonhi05:00
s3wonghello05:00
hareeshpcHi05:00
*** natarajk has joined #openstack-meeting05:00
alonhaHi05:00
gongyshhi05:00
natarajkhi05:00
yamahata#startmeeting servicevm-device-manager05:01
openstackMeeting started Tue Jun 10 05:01:05 2014 UTC and is due to finish in 60 minutes.  The chair is yamahata. Information about MeetBot at http://wiki.debian.org/MeetBot.05:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:01
*** openstack changes topic to " (Meeting topic: servicevm-device-manager)"05:01
openstackThe meeting name has been set to 'servicevm_device_manager'05:01
yamahata#topic Announcement05:01
*** openstack changes topic to "Announcement (Meeting topic: servicevm-device-manager)"05:01
*** tian has joined #openstack-meeting05:01
yamahatacreated irc channel on freenode #tacker05:01
*** shankar has quit IRC05:01
yamahatarequested repository on stackforge. it's under review05:01
*** nshaikh has joined #openstack-meeting05:02
yamahata#link https://review.openstack.org/#/c/97435/05:02
s3wongOK05:02
*** arnaud has joined #openstack-meeting05:02
hareeshpcok05:03
yamahata#topic nfv follow up05:03
*** openstack changes topic to "nfv follow up (Meeting topic: servicevm-device-manager)"05:03
*** zhikunliu has quit IRC05:04
*** OSM has joined #openstack-meeting05:04
yamahataAs BP for NFV support,  two Blueprints for vlan trunking and unfirewall-unaddress  are proposed by Ian.05:04
*** OSM is now known as songole05:04
yamahataRegarding vlan trunking, I think it's mostly same to vlan-aware-vm/l2-gateway. So we need to coordinate it.05:05
alonhaCan you point to the blueprints?05:05
yamahata#link https://review.openstack.org/#/c/97714/05:05
s3wongyamahata: I think mestery agrees with your -1 on the VLAN trunking bp05:06
yamahata#link https://review.openstack.org/#/c/94612/05:06
*** bobmel has joined #openstack-meeting05:06
s3wongit is redundant to what has been filed05:06
yamahata#link https://blueprints.launchpad.net/neutron/+spec/l2-gateway05:06
yamahatano neutron-spec for the last one05:06
yamahatas3wong: Yes.05:06
bobmelHi all! bob melander here. Sorry for being late.05:07
yamahataI pinged Eric, but haven't got any reply.05:07
yamahatabobmel: hello05:07
yisunbut no one is working on L2 GW05:07
s3wongyamahata: also, ijw filed another on having two interfaces to same network bp05:07
yamahatabobmel: It's early morning there?05:07
s3wongbobmel: changed your handle already? :-)05:07
swestonyamahata: late evening :-)05:07
bobmelyamahata: yes, early morning and I'm more of a evening guy :-)05:08
yisunDoes anyone know who is working on L2 GW?05:08
yamahataI'm willing to write l2gw or update vlan-ware-vlan spec.05:08
yamahataor anyone volunteer?05:08
s3wongyisun: I believe someone from Ericsson05:08
yisunBut what is the problem to let Eric to continue?05:08
yisunEric is from Ericsson05:08
yisunBut L2 GW I don’t think so05:09
bobmelyisun: Stephan baucke and Rasha Ben Ali, both ericsson05:09
yisunBut the owner of L2 GW is Rossella Sblendido05:09
yisunI’m reading the wrong one?05:09
bobmelok, aha, has it changed recently?05:10
*** garyduan has joined #openstack-meeting05:10
yamahatayisun: the issues is Eric is not responsive recently.05:10
yisunNo, it was like that a year ago05:10
bobmelStephan and Rasha also have some l2gw blueprint I beleive05:10
garyduanHi, sorry, I am late05:10
yamahatagaryduan: hi.05:10
yisunOk, little history about these vlan or L2 thing05:11
garyduanyamahata: hi05:11
yamahataI'm wondering how we can accelerate or make things progress.05:11
yisunIn the Hongkong summit, I was trying to consolidate the efforts, only ERIC responsed and worked on it05:11
yisunno one else make any progress since then other than Eric05:11
yamahataOkay, I'll update BP unless Eric does.05:11
yamahataThen we'll see how the spec review goes05:12
s3wongthe one rossella_s filed was a while back, so not sure if she is still going to work on it05:12
yamahatas3wong: can you ping him?05:12
yisunI really think she is from Midocura :-)05:12
s3wongsimilar to the port mirroring bp, the one implementing it doesn't need to be the one filing the bp05:12
yamahataher?05:12
s3wongyisun: she used to be, she is now at SUSE :-)05:12
s3wongyisun: she filed it when she was with Midokura05:13
yamahatas3wong: okay05:13
s3wongyamahata: yes, I can ping rossella_s to see if she is still interested in implementing it05:13
*** lbragstad has quit IRC05:13
yamahata#action yamahata update BP, see how review goes unless eric does.05:13
yamahata#action s3wong ping rossella_s05:13
*** gcb has quit IRC05:14
yisunYamahata, by the BP, you meant L2 GW?05:14
yamahataYes L2Gw.05:14
*** vpanizo has quit IRC05:14
*** Michalik_ has joined #openstack-meeting05:14
yisunOk05:14
yamahataIf rossella_s write it, it's great. otherwise I'll take it.05:14
yamahatathe next blueprint is unfirewall/unaddressed port05:15
yamahata#link https://review.openstack.org/9771505:15
*** ildikov has joined #openstack-meeting05:15
yamahataIt's also by Ian.05:15
*** lbragstad has joined #openstack-meeting05:15
yamahataThe proposal is, unfirewall == unaddressed.05:15
yamahataDo we want to separate them?05:16
yamahataI mean unfirewalled port with address and unfirewalled port without address.05:16
*** zhikunliu has joined #openstack-meeting05:17
yisunYamahata: why do you want to separate them?05:17
alonhaMaybe the more proper term is 'trusted port'?05:17
yamahatayisun: Yes, I though. I'm not sure if there is a use case.05:18
yamahataOnly unfirewalled port without address is okay?05:18
yisunGary: we have such a port, right?05:18
bobmelRouter ports would be one example05:19
garyduanit could be unfirewalled but with address05:19
yamahataFor router vm case, port needs IP address without firewall.05:19
*** Michalik_ has quit IRC05:19
s3wongyamahata: yisun: garyduan: this is port without security group, right?05:19
garyduanright05:19
yamahatas3wong: yes.05:19
yisuns3wong: it does not have IP either05:19
s3wongyamahata: we also need port that isn't attached to any subnet, thus port w/out IP05:20
yamahatas3wong: Does it mean unaddressed? Is the port associated to only network?05:20
yisunHere is one more case, that I don’t know which buck it fits05:20
yisunI have a redundant ports to back up each other05:21
yisunand both them have the same MAC and IP05:21
s3wongyamahata: IP address assigned to VM is from user specifying which network the port belongs to; if we want to create VM with a port that is not attached to any network, it seems reasonable that it has to be without any IP address05:22
gongyshfor router vm,  we need to remove anti spoof chain.05:22
s3wongyisun: sounds like a different bp05:23
s3wongneed to update that requirements on our list05:23
gongyshw3wong:  not attached to any network -> not attached to any subnets?05:23
yisuns3wong: could be05:24
yamahataThere are many requirements for port attributes. I'll create wiki page for it.05:24
yisunall: bascially, for the service VM, we may have to disable all firewall checks05:24
yamahataThen we can summarize use case and requirement. then break down to BPs05:24
yamahata#action yamahata create wiki page for port attributes05:24
yisunyamahata+105:24
s3wonggongysh: not attached to any network or subnet, in a serviceVM pool, ideally, we don't set the VM interface attachment and its IP address until we know which network we want to attach the port to05:24
s3wongyamahata: that is definitely a good idea05:25
yisuns3wong: in that case, we can create vnic and plugin network when we need05:25
bobmelyamahata: +105:25
garyduanthere is a case that one port can server multiple networks05:25
s3wongyisun: can we create VM without any port initially?05:25
yamahataAt least the consensus is Ian's proposal should be split/enhanced into some BPs.05:26
s3wonggaryduan: is it supported today?05:26
yisuns3wong, I think you need a vnic for mgt at least05:26
*** nkubota has quit IRC05:26
garyduans3wong: in neutron, no05:26
natarajkyisub: that's correct05:26
natarajkyou need atleast one for mgmt for service vm05:26
s3wongyisun: OK - that's cool, since yamahata is introducing mgmt interface concept, that could be the first interface for serviceVM05:27
yisunnatarajk: the is the basic requirement and any other interfaces can be create on daemon05:27
yisuns/the/this/05:27
bobmelnatarajk: yisun: unless you do management by RPC proxy05:27
yamahataI create wiki page05:28
yamahata#link https://wiki.openstack.org/wiki/ServiceVM/neutron-port-attributes05:28
yamahatajust blank yet.05:28
bobmelnatarajk: yisun: Then you may not have mgmt vnic05:28
yisunbobmel: why?05:28
yamahata#action anyone update wiki page with usecase/requirement05:28
*** kayaliu_ has joined #openstack-meeting05:28
natarajkbobmel: i meant we need atleast one for mgmt05:28
yisunnatarajk:+105:29
*** vpanizo has joined #openstack-meeting05:30
bobmelyisun: natarajk: I was referring to mgmt done as specified here: https://wiki.openstack.org/wiki/Oslo/blueprints/message-proxy-server05:30
s3wongbobmel: I think yisun and others are saying having a mgmt intf is a basic requirement for serviceVM05:30
yamahatabobmel: the blueprint needs to be updated according to the discussion at the summit05:31
yamahataThe first target is to build RPC over marconi.05:31
yisunbobmel: I need to read the bp, but shouldn’t we at least have an interface that we can send restful request?05:32
*** radek has joined #openstack-meeting05:32
yamahataI mean "enhancing neutron metadata agent and use notification over HTTP" section05:32
*** nkubota has joined #openstack-meeting05:33
bobmels3wong: Ok, that I agree with. Just need not necessarily be a network interface,05:33
garyduanAre we still talking neutron port attributes?05:33
*** vuil has joined #openstack-meeting05:34
*** vuil has quit IRC05:34
yamahataSeems no.05:34
yamahatathat's all from me as nfv follow up?05:34
s3wongyamahata: mgmt interface is NOT Neutron port, isn't it?05:35
yamahataanthing else?05:35
yamahatas3wong: mgmt interface can be non-neutron port.05:35
yamahatas3wong: But Neutron port can be mgmt port. That's the first goal.05:35
s3wonggaryduan: so what yamahata said above ^^^^^05:35
s3wonggaryduan: not necessarily about neutron port05:36
*** pradipta_away is now known as pradipta05:36
s3wongyamahata: thanks!05:36
yamahata#topic open discussion05:37
*** openstack changes topic to "open discussion (Meeting topic: servicevm-device-manager)"05:37
yamahataWhen tacker-spec repository is created, I'd like to start spec review of Rest api of device manager.05:38
garyduanyamahata: I was not able to attend last week's meeting05:38
yamahatagaryduan: no problem.05:38
garyduanyamahata: do we have these BP listed somewhere?05:38
*** gyee has quit IRC05:38
yamahata#link https://wiki.openstack.org/wiki/ServiceVM/neutron-and-other-project-items05:38
alonhaWhat is the differenc between this group and the new NFV one? Aren't both deal with the same problems?05:38
yamahatayou also want to see05:39
yamahata#link https://wiki.openstack.org/wiki/Meetings/NFV05:39
garyduanthanks05:39
s3wongalonha: at least at this point, the tacker team has not talked about things like how to saturate a 40G link05:39
alonhaSorry, what is tacker team?05:40
yamahataaloga: Maybe, we're understanding the difference. If BPs is covered by BP, it can be under NFV unbrella.05:40
s3wongalonha: sorry, the ServiceVM team :-)05:40
yamahatacovered by *NFV*05:40
*** tappel has joined #openstack-meeting05:41
yamahataaloga: serviceVM/device manager is not always covered by NFV.05:41
yamahataaloga: off course we'll work closely with NFV. Maybe subteam of NFV?05:41
garyduanIn general, I think we are not able to address all of the requirements. We need to identify several issues we must address first.05:41
*** rajeshr has joined #openstack-meeting05:41
alonhaSo, for now, two different groups?05:42
s3wonggaryduan: agreed, and based on last week's meeting, the general consensus is the serviceVM team will prioritize NFV use cases to address05:42
*** kayaliu_ has quit IRC05:42
s3wongalonha: at this point, the NFV subteam's mission is to gather requirements and file bps05:42
*** kayaliu_ has joined #openstack-meeting05:42
*** Michalik_ has joined #openstack-meeting05:43
alonhaok, thanks.05:43
s3wongalonha: OTOH, serviceVM team is here to get implementation / design done05:43
alonhagot it, thanks,05:43
yamahataanything else to discuss?05:44
yisunBTW— I got a new requirement today, not solid, but worth to share05:44
yisunWe are doing performance tuning on our service VM.05:45
yisunWe were trying to add some early random drop logic05:45
*** paulbc has joined #openstack-meeting05:45
yisunbut we can not find a good trigger for it. Since we have not clue on the hypervisro load05:45
yisunEven in the VM, our CPU usage is ok, but hypervisor may be already out of CPU.05:46
yisunSo, in order to issue something accurate, some hypervisor resource usage visibility may be helpful05:46
yamahatayisun: somthing like feeding some statistics of ceilometer to inside VM?05:46
yisunyamahata: there was one of thing I was thinking05:47
*** dims_ has joined #openstack-meeting05:47
*** Michalik_ has quit IRC05:47
yamahatasounds interesting05:47
s3wongyisun: yamahata: wonder if Ceilometer (used mostly for tenant) can cover hypervisor stats05:47
yisunyamahata: since this is only the first a few day that I’m looking into this, so it is not a solid idea yet, I will report back when I get more05:48
yamahatas3wong: At worst we can write a driver to gather such info05:48
yamahatas3wong: I guess there already is, though05:48
s3wongyamahata: OK05:48
*** Longgeek has joined #openstack-meeting05:49
garyduanI remember there was discussion at Neutron pod at Atlanta05:49
*** Longgeek has quit IRC05:49
garyduantalking about gathering traffic info by agent05:50
*** kashyapk has quit IRC05:50
*** eguz has joined #openstack-meeting05:50
*** eghobo has quit IRC05:50
*** Longgeek has joined #openstack-meeting05:50
*** kashyapk has joined #openstack-meeting05:50
*** alonha has left #openstack-meeting05:51
yamahatanothing more?05:51
*** Longgeek has quit IRC05:51
*** dstanek_zzz is now known as dstanek05:51
*** Longgeek has joined #openstack-meeting05:51
*** dims_ has quit IRC05:51
yamahataOkay let's review blueprint and update port attributes page05:51
s3wonggaryduan: so that is a fair requirements, you can put that into serviceVM wiki05:51
bobmelyamahata: I just added one about the sec group disable05:52
yamahatabobmel: thanks05:52
yamahatasee you next week or nfv meeting05:53
yamahata#endmeeting05:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:53
openstackMeeting ended Tue Jun 10 05:53:06 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-06-10-05.01.html05:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-06-10-05.01.txt05:53
openstackLog:            http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-06-10-05.01.log.html05:53
garyduans3wong: I agree on the requirement in general05:53
yamahatagaryduan: sorry, too eary to close05:53
garyduans3wong: but not necessarily the approach05:53
yamahataearly05:53
*** yingjun has quit IRC05:53
garyduanyamahata: that's fine.05:53
s3wonggaryduan: yep, week by week we get more requests, we will prioritize, but good to have a centralized place to write them down05:54
*** yingjun has joined #openstack-meeting05:54
yisuns3wong: do we have a target date that we will close the requirement collection and start to set priority?05:54
*** songole has quit IRC05:54
s3wongyisun: not yet :-)05:54
yisunsorry, I will not in the latest meeting, this is only a catch up question, just in case I missed it05:55
yamahatayisun: s3wong do we want to set?05:55
yisuns/will/was/05:55
s3wongyamahata: do we want to get things moving before project gets into incubation (because that will take some time)05:55
*** natarajk has quit IRC05:56
yisunyamahata: it really depends on how we to plan this.05:56
yisuns/to/want to/05:56
yamahatas3wong: yisun I see05:56
yamahataI thought it would be good to have some code working before applying incubation process05:57
s3wongyamahata: absolutely05:57
*** jtomasek has joined #openstack-meeting05:57
yamahataAnd have some experience with openstack CI05:57
s3wongyamahata: and also plan for maximizing benefits for community05:57
*** blogan has quit IRC05:58
s3wonganyway, let's add requirements on the wiki page06:00
yisun+106:00
s3wongmeeting time's up. see you guys next week :-)06:00
bobmelBye06:00
s3wongbye06:00
yisunbye06:00
garyduanbye06:00
swestonbye06:00
*** dstanek is now known as dstanek_zzz06:01
hareeshpcbye06:02
*** hareeshpc has left #openstack-meeting06:02
*** Longgeek has quit IRC06:04
*** Longgeek has joined #openstack-meeting06:04
*** Longgeek has quit IRC06:04
*** Longgeek has joined #openstack-meeting06:05
*** kayaliu_ has quit IRC06:06
*** Longgeek has quit IRC06:06
*** Longgeek_ has joined #openstack-meeting06:06
*** kashyapk has quit IRC06:08
*** arnaud has quit IRC06:08
*** ramishra has quit IRC06:08
*** Daisy has joined #openstack-meeting06:08
*** ramishra has joined #openstack-meeting06:08
*** kashyapk has joined #openstack-meeting06:08
*** _nadya_ has joined #openstack-meeting06:10
*** vivek-ebay has quit IRC06:11
*** radek has quit IRC06:13
*** bdpayne has quit IRC06:13
*** whenry has quit IRC06:13
*** cody-somerville has joined #openstack-meeting06:17
*** cody-somerville has quit IRC06:17
*** cody-somerville has joined #openstack-meeting06:17
*** dims_ has joined #openstack-meeting06:17
*** yisun has left #openstack-meeting06:17
*** akuznetsov has joined #openstack-meeting06:18
*** s3wong has quit IRC06:18
*** mkoderer has joined #openstack-meeting06:21
*** dims_ has quit IRC06:22
*** Macaveli has joined #openstack-meeting06:24
*** novas0x2a|laptop has quit IRC06:27
*** novas0x2a|laptop has joined #openstack-meeting06:28
*** Fdot has joined #openstack-meeting06:28
*** stevemar2 has quit IRC06:30
*** evgenyf has joined #openstack-meeting06:30
*** jtomasek has quit IRC06:31
*** bdpayne has joined #openstack-meeting06:33
*** bdpayne_ has joined #openstack-meeting06:35
*** yamamoto_ has quit IRC06:35
*** whenry has joined #openstack-meeting06:39
*** bdpayne has quit IRC06:39
*** xuhanp has quit IRC06:40
*** xuhanp has joined #openstack-meeting06:41
*** eguz has quit IRC06:41
*** Mandell has quit IRC06:42
*** Michalik_ has joined #openstack-meeting06:43
*** ngoswami has joined #openstack-meeting06:46
*** jtomasek has joined #openstack-meeting06:48
*** Michalik_ has quit IRC06:48
*** lbragstad has quit IRC06:49
*** luqas has joined #openstack-meeting06:50
*** lbragstad has joined #openstack-meeting06:50
*** afazekas is now known as __afazekas06:51
*** shankar has joined #openstack-meeting06:52
*** dguitarbite has joined #openstack-meeting06:52
*** cody-somerville has quit IRC06:55
*** salv-orlando has quit IRC06:58
*** mrunge has joined #openstack-meeting06:58
*** jcoufal has joined #openstack-meeting06:59
*** nosnos has quit IRC06:59
*** matsuhashi has quit IRC07:01
*** matsuhas_ has joined #openstack-meeting07:01
*** armax has quit IRC07:01
*** kashyapk has quit IRC07:03
*** kashyapk has joined #openstack-meeting07:03
*** paulbc has quit IRC07:03
*** whenry has quit IRC07:04
*** nosnos has joined #openstack-meeting07:05
*** flaper87|afk is now known as flaper8707:06
*** devlaps has joined #openstack-meeting07:07
*** yingjun has quit IRC07:07
*** yingjun has joined #openstack-meeting07:07
*** devlaps has quit IRC07:07
*** kashyapk has quit IRC07:08
*** cody-somerville has joined #openstack-meeting07:09
*** tkay has quit IRC07:10
*** dguitarbite has quit IRC07:12
*** ttrifonov_zZzz is now known as ttrifonov07:13
*** tkay has joined #openstack-meeting07:16
*** sushils_ has joined #openstack-meeting07:16
*** pdehaye has joined #openstack-meeting07:17
*** dims_ has joined #openstack-meeting07:17
*** dims_ has quit IRC07:22
*** bogdando has quit IRC07:23
*** tkay has quit IRC07:23
*** sushils_ has quit IRC07:24
*** bogdando has joined #openstack-meeting07:24
*** doron_afk has joined #openstack-meeting07:25
*** pdehaye has quit IRC07:25
*** bauzas has joined #openstack-meeting07:26
*** _nadya_ has quit IRC07:28
*** jackmccann has quit IRC07:30
*** andreaf has quit IRC07:31
*** phil__ has joined #openstack-meeting07:31
*** mwagner_lap has quit IRC07:34
*** mrunge has quit IRC07:35
*** kashyapk has joined #openstack-meeting07:36
*** mwagner_lap has joined #openstack-meeting07:36
*** Macaveli is now known as Macaveli|BRB07:38
*** ominakov has joined #openstack-meeting07:40
*** ArthurBerezin has joined #openstack-meeting07:41
*** jlibosva has joined #openstack-meeting07:42
*** Macaveli|BRB is now known as Macaveli07:44
*** Michalik_ has joined #openstack-meeting07:44
*** enykeev has joined #openstack-meeting07:45
*** tappel has quit IRC07:46
*** ArthurBerezin has left #openstack-meeting07:46
*** bobmel has quit IRC07:47
*** thomasbiege has joined #openstack-meeting07:47
*** Michalik_ has quit IRC07:48
*** ajo|mac has joined #openstack-meeting07:50
*** SridharG has joined #openstack-meeting07:51
*** sweston has quit IRC07:54
*** afazekas has joined #openstack-meeting07:55
*** kashyapk has quit IRC07:56
*** hashar has joined #openstack-meeting07:56
*** kashyapk has joined #openstack-meeting07:56
*** yingjun has quit IRC07:58
*** andreaf has joined #openstack-meeting07:58
*** dguitarbite has joined #openstack-meeting07:59
*** yingjun has joined #openstack-meeting07:59
*** ihrachyshka has joined #openstack-meeting07:59
*** nkubota has quit IRC08:00
*** nkubota has joined #openstack-meeting08:00
*** kashyapk has quit IRC08:01
*** vjay3 has quit IRC08:04
*** vrovachev has joined #openstack-meeting08:05
*** kashyapk has joined #openstack-meeting08:06
*** julienvey has joined #openstack-meeting08:07
*** bauzas has quit IRC08:07
*** gcb has joined #openstack-meeting08:08
*** vivek-ebay has joined #openstack-meeting08:12
*** IvanBerezovskiy has joined #openstack-meeting08:12
*** ramishra has quit IRC08:12
*** sweston has joined #openstack-meeting08:15
*** sbalukoff has joined #openstack-meeting08:15
*** vjay3 has joined #openstack-meeting08:15
*** ndipanov has joined #openstack-meeting08:17
*** derekh_ has joined #openstack-meeting08:17
*** dims_ has joined #openstack-meeting08:18
*** ygbo has joined #openstack-meeting08:19
*** ramishra has joined #openstack-meeting08:19
*** mrunge has joined #openstack-meeting08:19
*** vivek-ebay has quit IRC08:20
*** safchain has joined #openstack-meeting08:20
*** dims_ has quit IRC08:22
*** marcoemorais1 has quit IRC08:23
*** _nadya_ has joined #openstack-meeting08:25
*** ajo|mac has quit IRC08:31
*** ajo|mac has joined #openstack-meeting08:33
*** sweston has quit IRC08:35
*** nkubota has quit IRC08:36
*** matsuhas_ has quit IRC08:38
*** kashyapk has quit IRC08:38
*** kashyapk has joined #openstack-meeting08:39
*** bdpayne_ has quit IRC08:39
*** nosnos has quit IRC08:40
*** pelix has joined #openstack-meeting08:41
*** lbragstad has quit IRC08:43
*** nosnos has joined #openstack-meeting08:43
*** lbragstad has joined #openstack-meeting08:43
*** nosnos has quit IRC08:44
*** matsuhashi has joined #openstack-meeting08:44
*** Michalik_ has joined #openstack-meeting08:45
*** ramishra has quit IRC08:47
*** Michalik_ has quit IRC08:50
*** jhenner has joined #openstack-meeting08:50
*** jcoufal has quit IRC08:55
*** jcoufal has joined #openstack-meeting08:56
*** ArthurBerezin1 has joined #openstack-meeting08:58
*** thomasbiege1 has joined #openstack-meeting09:00
*** sweston has joined #openstack-meeting09:02
*** nosnos has joined #openstack-meeting09:03
*** yingjun has quit IRC09:03
*** yingjun has joined #openstack-meeting09:03
*** thomasbiege has quit IRC09:04
*** jgallard has joined #openstack-meeting09:05
*** ramishra has joined #openstack-meeting09:06
*** novas0x2a|laptop has quit IRC09:07
*** zhikunliu has quit IRC09:09
*** ihrachyshka has quit IRC09:10
*** idegtiarov has joined #openstack-meeting09:10
*** isviridov_ is now known as isviridov09:12
*** ArthurBerezin1 has quit IRC09:17
*** llu is now known as llu-away09:17
*** llu-away is now known as llu09:17
*** nedbat has joined #openstack-meeting09:17
*** pradipta is now known as pradipta_away09:18
*** zhiyan is now known as zhiyan_09:18
*** dims_ has joined #openstack-meeting09:19
*** tomoe_ has quit IRC09:19
*** luqas has quit IRC09:20
*** pradipta_away is now known as pradipta09:20
*** evgenyf has quit IRC09:21
*** pradipta is now known as pradipta_away09:21
*** Daisy has quit IRC09:23
*** mspreitz has quit IRC09:23
*** sweston has quit IRC09:24
*** dims_ has quit IRC09:25
*** ArthurBerezin has joined #openstack-meeting09:32
*** doron_afk is now known as doron09:33
*** paulbc has joined #openstack-meeting09:33
*** ArthurBerezin1 has joined #openstack-meeting09:35
*** nacim has joined #openstack-meeting09:35
*** ramishra has quit IRC09:36
*** KurtRao has joined #openstack-meeting09:36
*** xianghui has quit IRC09:37
*** ArthurBerezin has quit IRC09:37
*** belmoreira has joined #openstack-meeting09:42
*** weshay has joined #openstack-meeting09:43
*** yingjun has quit IRC09:45
*** Michalik_ has joined #openstack-meeting09:46
*** luqas has joined #openstack-meeting09:49
*** doron is now known as doron_afk09:49
*** kashyapk has quit IRC09:49
*** xianghui has joined #openstack-meeting09:50
*** paulbc has quit IRC09:50
*** kashyapk has joined #openstack-meeting09:50
*** Michalik_ has quit IRC09:51
*** xianghui has quit IRC09:51
*** sankarshan is now known as sankarshan_away09:52
*** xianghui has joined #openstack-meeting09:52
*** ihrachyshka has joined #openstack-meeting09:53
*** kashyapk has quit IRC09:54
*** vjay3 has quit IRC09:56
*** ArthurBerezin1 has left #openstack-meeting09:59
*** julienvey has quit IRC09:59
*** salv-orlando has joined #openstack-meeting10:00
*** gongysh has quit IRC10:03
*** gcb has quit IRC10:04
*** jgallard has quit IRC10:07
*** egallen has joined #openstack-meeting10:11
*** xuhanp has quit IRC10:14
*** MaxV has joined #openstack-meeting10:16
*** gcb has joined #openstack-meeting10:16
*** evgenyf has joined #openstack-meeting10:16
*** igordcard has joined #openstack-meeting10:16
*** doron_afk is now known as doron10:18
*** matiu has quit IRC10:21
*** dims_ has joined #openstack-meeting10:21
*** ngoswami has quit IRC10:22
*** ngoswami has joined #openstack-meeting10:22
*** mrunge has quit IRC10:24
*** egallen has quit IRC10:27
*** dims_ has quit IRC10:27
*** mrunge has joined #openstack-meeting10:29
*** hashar has quit IRC10:32
*** paragan has quit IRC10:33
*** kashyapk has joined #openstack-meeting10:34
*** matiu has joined #openstack-meeting10:35
*** xianghui has quit IRC10:38
*** MaxV has quit IRC10:41
*** ajo|mac has quit IRC10:43
*** jjmb has quit IRC10:45
*** Michalik_ has joined #openstack-meeting10:46
*** vjay3 has joined #openstack-meeting10:50
*** Michalik_ has quit IRC10:51
*** jjmb has joined #openstack-meeting10:54
*** ArthurBerezin has joined #openstack-meeting10:56
*** ArthurBerezin has left #openstack-meeting10:57
*** matiu has quit IRC10:57
*** ekarlso has quit IRC10:57
*** julienvey has joined #openstack-meeting10:59
*** enykeev has quit IRC11:00
*** mahesh__ has joined #openstack-meeting11:00
*** xianghui has joined #openstack-meeting11:02
*** mahesh__ has quit IRC11:03
*** matiu has joined #openstack-meeting11:03
*** matiu has quit IRC11:03
*** matiu has joined #openstack-meeting11:03
*** enykeev has joined #openstack-meeting11:04
*** coolsvap is now known as coolsvap|afk11:04
*** simonmcc has quit IRC11:04
*** bogdando has quit IRC11:04
*** bogdando has joined #openstack-meeting11:04
*** simonmcc has joined #openstack-meeting11:04
*** MaxV has joined #openstack-meeting11:05
*** epico has quit IRC11:05
*** bauzas has joined #openstack-meeting11:06
*** cyeoh has quit IRC11:06
*** doron is now known as doron_afk11:07
*** bauzas has quit IRC11:09
*** schwicht has joined #openstack-meeting11:10
*** cyeoh has joined #openstack-meeting11:10
*** ngoswami has quit IRC11:10
*** yaguang has quit IRC11:10
*** ngoswami has joined #openstack-meeting11:10
*** akuznetsov has quit IRC11:16
*** oomichi_ has joined #openstack-meeting11:16
*** akuznetsov has joined #openstack-meeting11:19
*** luqas has quit IRC11:22
*** dims_ has joined #openstack-meeting11:23
*** _nadya_ has quit IRC11:26
*** salv-orlando has quit IRC11:27
*** vpanizo has quit IRC11:28
*** vjay3 has quit IRC11:29
*** alexpilotti has joined #openstack-meeting11:29
*** salv-orlando has joined #openstack-meeting11:32
*** yamahata has quit IRC11:32
*** egallen has joined #openstack-meeting11:35
*** schwicht has quit IRC11:35
*** kashyapk has quit IRC11:36
*** kashyapk has joined #openstack-meeting11:37
*** miqui has quit IRC11:38
*** xianghui has quit IRC11:40
*** tomoe_ has joined #openstack-meeting11:41
*** rajeshr has quit IRC11:43
*** vjay3 has joined #openstack-meeting11:47
*** gcb has quit IRC11:47
*** jjmb has quit IRC11:47
*** Michalik_ has joined #openstack-meeting11:47
*** eankutse has joined #openstack-meeting11:47
*** nedbat has quit IRC11:48
*** eankutse has quit IRC11:49
*** eankutse has joined #openstack-meeting11:49
*** hashar has joined #openstack-meeting11:49
*** Michalik_ has quit IRC11:51
*** ArxCruz has joined #openstack-meeting11:52
*** Youcef_ has joined #openstack-meeting11:53
*** xianghui has joined #openstack-meeting11:53
*** Macaveli has quit IRC11:56
*** Youcef has quit IRC11:56
*** ttrifonov is now known as ttrifonov_zZzz11:56
*** ttrifonov_zZzz is now known as ttrifonov11:56
*** Macaveli has joined #openstack-meeting11:56
*** _nadya_ has joined #openstack-meeting11:57
*** paragan has joined #openstack-meeting12:00
*** nedbat has joined #openstack-meeting12:01
*** jhenner has quit IRC12:01
*** jhenner has joined #openstack-meeting12:02
*** nedbat has quit IRC12:03
*** adalbas has joined #openstack-meeting12:04
*** hrybacki has joined #openstack-meeting12:05
*** radez_g0n3 is now known as radez12:05
*** doron_afk is now known as doron12:08
*** afazekas has quit IRC12:09
*** aysyd has joined #openstack-meeting12:09
*** shakayumi has joined #openstack-meeting12:10
*** egallen has quit IRC12:12
*** matiu has quit IRC12:12
*** kashyapk has quit IRC12:13
*** yingjun has joined #openstack-meeting12:13
*** kashyapk has joined #openstack-meeting12:13
*** egallen has joined #openstack-meeting12:14
*** matiu has joined #openstack-meeting12:14
*** matiu has joined #openstack-meeting12:14
*** jhenner has quit IRC12:18
*** kashyapk has quit IRC12:19
*** vivek-ebay has joined #openstack-meeting12:19
*** jhenner has joined #openstack-meeting12:20
*** jdob has joined #openstack-meeting12:22
*** xuhanp has joined #openstack-meeting12:23
*** vivek-ebay has quit IRC12:24
*** afazekas has joined #openstack-meeting12:24
*** dkranz has joined #openstack-meeting12:24
*** Longgeek_ has quit IRC12:25
*** Longgeek has joined #openstack-meeting12:26
*** mwagner_lap has quit IRC12:26
*** hrybacki_ has joined #openstack-meeting12:26
*** moha_hunt has quit IRC12:27
*** kayaliu_ has joined #openstack-meeting12:27
*** dprince has joined #openstack-meeting12:28
*** dhellmann has quit IRC12:28
*** yaguang has joined #openstack-meeting12:29
*** shankar has quit IRC12:30
*** yaguang has quit IRC12:30
*** yaguang has joined #openstack-meeting12:30
*** moha_hunt has joined #openstack-meeting12:30
*** mrunge has quit IRC12:32
*** jang has quit IRC12:33
*** bknudson has quit IRC12:34
*** julienvey has quit IRC12:35
*** jang has joined #openstack-meeting12:36
*** deepakcs has quit IRC12:39
*** marekd_ has quit IRC12:40
*** pdmars has joined #openstack-meeting12:44
*** pdmars has quit IRC12:44
*** pdmars has joined #openstack-meeting12:45
*** lbragstad has quit IRC12:45
*** eankutse has quit IRC12:46
*** SridharG has quit IRC12:46
*** Michalik_ has joined #openstack-meeting12:48
*** luqas has joined #openstack-meeting12:48
*** SridharG has joined #openstack-meeting12:48
*** dkranz has quit IRC12:48
*** julienvey has joined #openstack-meeting12:49
*** boh_ricky has joined #openstack-meeting12:50
*** vivek-ebay has joined #openstack-meeting12:51
*** bknudson has joined #openstack-meeting12:52
*** japplewhite has joined #openstack-meeting12:52
*** HenryG has quit IRC12:53
*** alexpilotti_ has joined #openstack-meeting12:53
*** Michalik_ has quit IRC12:53
*** afazekas has quit IRC12:53
*** kashyapk has joined #openstack-meeting12:53
*** alexpilotti has quit IRC12:54
*** alexpilotti_ is now known as alexpilotti12:54
*** SridharGaddam has joined #openstack-meeting12:55
*** SridharG has quit IRC12:55
*** vivek-eb_ has joined #openstack-meeting12:57
*** mspreitz has joined #openstack-meeting12:57
*** changbl has quit IRC12:57
*** rbowen has joined #openstack-meeting12:57
*** dims_ has quit IRC12:59
*** baoli has joined #openstack-meeting12:59
*** vivek-ebay has quit IRC13:00
*** cknight has joined #openstack-meeting13:00
*** jhenner has quit IRC13:03
*** julienvey has quit IRC13:04
*** yamahata has joined #openstack-meeting13:05
*** julienvey has joined #openstack-meeting13:06
*** jecarey has quit IRC13:06
*** amotoki_ has joined #openstack-meeting13:06
*** julim has joined #openstack-meeting13:06
*** afazekas has joined #openstack-meeting13:07
*** erecio has quit IRC13:07
*** erecio has joined #openstack-meeting13:08
*** idegtiarov has quit IRC13:09
*** julienvey has quit IRC13:11
*** kayaliu_ has quit IRC13:11
*** kayaliu_ has joined #openstack-meeting13:12
*** vijendar has joined #openstack-meeting13:13
*** jhenner has joined #openstack-meeting13:17
*** lbragstad has joined #openstack-meeting13:17
*** jecarey has joined #openstack-meeting13:18
*** alexpilotti_ has joined #openstack-meeting13:21
*** alexpilotti has quit IRC13:22
*** alexpilotti_ is now known as alexpilotti13:22
*** bcrochet has quit IRC13:23
*** dstanek_zzz is now known as dstanek13:23
*** bcrochet has joined #openstack-meeting13:25
*** lbragstad1 has joined #openstack-meeting13:26
*** boh_ricky has quit IRC13:26
*** boh_ricky has joined #openstack-meeting13:27
*** tvoran has joined #openstack-meeting13:27
*** sushils_ has joined #openstack-meeting13:27
*** sushils_ has quit IRC13:27
*** doron is now known as doron_afk13:27
*** sushils_ has joined #openstack-meeting13:28
*** lbragstad has quit IRC13:28
*** lbragstad has joined #openstack-meeting13:29
*** lbragstad1 has quit IRC13:30
*** dims_ has joined #openstack-meeting13:30
*** gokrokve has joined #openstack-meeting13:31
*** banix has joined #openstack-meeting13:33
*** nedbat has joined #openstack-meeting13:34
*** devlaps1 has joined #openstack-meeting13:34
*** jgrimm has joined #openstack-meeting13:34
*** AndChat|27729 has joined #openstack-meeting13:34
*** AndChat|27729 has quit IRC13:35
*** jackib has joined #openstack-meeting13:35
*** salv-orlando has quit IRC13:35
*** julienvey has joined #openstack-meeting13:35
*** salv-orlando has joined #openstack-meeting13:36
*** dguitarbite has quit IRC13:37
*** toan-tran has joined #openstack-meeting13:38
*** boh_ricky has quit IRC13:38
*** jang has quit IRC13:39
*** matsuhashi has quit IRC13:39
*** julienvey has quit IRC13:40
*** kashyapk has quit IRC13:41
*** eharney has joined #openstack-meeting13:41
*** Longgeek has quit IRC13:42
*** yingjun has quit IRC13:42
*** Longgeek has joined #openstack-meeting13:42
*** julienvey has joined #openstack-meeting13:43
*** kevinconway has joined #openstack-meeting13:45
*** noslzzp has quit IRC13:46
*** lbragstad has quit IRC13:48
*** jackib has quit IRC13:48
*** lbragstad has joined #openstack-meeting13:48
*** Michalik_ has joined #openstack-meeting13:49
*** nosnos has quit IRC13:50
*** _nadya_ has quit IRC13:50
*** haleyb has quit IRC13:50
*** mtanino has joined #openstack-meeting13:50
*** egallen has quit IRC13:53
*** haleyb has joined #openstack-meeting13:54
*** Michalik_ has quit IRC13:54
*** Fdot_ has joined #openstack-meeting13:54
*** neelashah has joined #openstack-meeting13:55
*** aveiga has joined #openstack-meeting13:55
*** lbragstad1 has joined #openstack-meeting13:57
sc68calhello everyone, who's ready for some IPv6?13:57
* aveiga is always ready for IPv613:58
sc68cal:)13:58
*** lbragstad has quit IRC13:58
SridharGaddamhi13:58
*** thangp has joined #openstack-meeting13:58
*** Fdot has quit IRC13:59
*** SridharGaddam is now known as SridharG13:59
sc68cal#startmeeting neutron_ipv614:00
openstackMeeting started Tue Jun 10 14:00:02 2014 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_ipv6)"14:00
openstackThe meeting name has been set to 'neutron_ipv6'14:00
*** BrianB___ has joined #openstack-meeting14:00
baoliHi14:00
*** pcm_ has joined #openstack-meeting14:00
xuhanphi14:00
SridharGhello everyone..14:00
sc68cal#link https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_June_10th14:00
sc68cal#topic blueprints14:01
*** openstack changes topic to "blueprints (Meeting topic: neutron_ipv6)"14:01
sc68calDo we have any new blueprints to discuss?14:02
*** Shixiong has joined #openstack-meeting14:03
*** jcoufal has quit IRC14:03
sc68calIf not, we'll continue to code reviews14:04
xuhanpsc68cal, I saw Shixiong just joined, so shall we discuss the dnsmasq review?14:04
*** dane_leblanc has joined #openstack-meeting14:04
sc68calxuhanp: sure, that's a good idea14:05
aveigasilence indicates acceptance, sc68cal14:05
sc68cal#topic code review14:05
*** openstack changes topic to "code review (Meeting topic: neutron_ipv6)"14:05
aveigamight as well go to reviews14:05
Shixiongsure14:05
sc68calxuhanp: you wanted to take on part of the dnsmasq changes, that was part of Shixiong's large patch?14:06
xuhanpsure. depends how to divide it.14:07
sc68cal#link https://review.openstack.org/#/c/70649/14:07
xuhanpwe already tested the code. Most of it works, except the one pid problem. And I will file a bug for DHCP security rule to allow dhcpv6 from dnsmasq14:08
*** vivek-eb_ has quit IRC14:08
sc68calxuhanp: Cool. I saw you had a patch get accepted yesterday to allow DHCPv6 solicit through?14:08
sc68calerr - out of a guest14:08
*** balajiiyer has joined #openstack-meeting14:08
xuhanpyep.14:09
Shixiongxuhanp, I am still investigating that pid problem14:09
*** yingjun has joined #openstack-meeting14:09
*** balajiiyer has left #openstack-meeting14:09
xuhanpShixiong, we also did some investigation on that. Can share with you if you need.14:09
xuhanpI think we need to break your patch into smaller ones and submit for code review ASAP.14:09
xuhanpgive we are already at Juno-114:09
ShixiongThat will be awesome.14:10
ShixiongDo you want to have a meeting to talk about that, or you think email exchange should be fine?14:10
xuhanpI can talk with you after this meeting on openstack-neutron if that's OK14:10
*** KurtRao has quit IRC14:10
*** eankutse has joined #openstack-meeting14:10
*** KurtRao has joined #openstack-meeting14:11
sc68cal#link https://launchpad.net/neutron/+milestone/juno-1 J-1 milestone14:11
*** yingjun has quit IRC14:11
sc68cal#link https://launchpad.net/neutron/+milestone/juno-2 J-2 milestone14:11
*** maxdml has joined #openstack-meeting14:11
*** stevemar has joined #openstack-meeting14:11
sc68calWe've got a couple v6 BPs in both milestones14:11
aveigaj1 is one week14:11
sc68calless than that :(14:12
sc68calI believe this thursday14:12
aveiga6/1214:13
aveigaaccording to the link14:13
*** vjay3 has quit IRC14:13
sc68calxuhanp: Shixiong: baoli: Take a look at J-2 milestone, there's two IPv6 blueprints in for J-214:13
sc68cal#link https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-slaac14:14
sc68cal#link https://blueprints.launchpad.net/neutron/+spec/neutron-ipv6-radvd-ra14:14
baolisaw that.14:14
baolisc68scal, thanks for your review on my spec14:15
*** jdob has quit IRC14:15
sc68calbaoli: you're very kind to say so, since I -1'd it..14:15
*** jdob has joined #openstack-meeting14:15
sc68calDuring the main meeting yesterday we brought up the issue of the 1 attribute vs 2 attributes (see the los)14:16
sc68cal*logs14:16
*** oomichi_ has quit IRC14:16
baolisc68cal, is there a decision on that?14:16
*** lbragstad1 has quit IRC14:16
sc68calThere was only one dissenting opinion from the core team regarding 1 attr vs 2 attrs14:16
Shixiong@xuhanp, I will have a meeting until noon today EST time. Is it possible we can chat at different time on the pid issue?14:17
sc68calthis was in regards to getting the python-neutronclient change in14:17
*** _nadya_ has joined #openstack-meeting14:17
xuhanpShixiong, sure.14:17
sc68calbaoli: I *think* that for the most part the 2 attr is the way we're going to go14:18
ShixiongI prefer give you and Jian Li a call so we can talk, which is more efficient14:18
xuhanpShixiong, sure.14:18
xuhanpthat works too.14:18
baolisc68cal, what's the reason for my bp to be on the j2 list?14:18
sc68calbaoli: the radvd one?14:19
baolisc68cal, yes14:19
sc68calDo you think it can be done by J-2? or should we move it to j-3?14:19
*** dhellmann has joined #openstack-meeting14:20
*** flaviof_zzz is now known as flaviof14:20
xuhanpsc68cal, are we already decided to go to the "1" attribute one proposed by baoli? I saw your comment on that spec still objects it.14:20
*** sankarshan_away is now known as sankarshan14:21
baolisc68cal, it's going to be a different implementation than what's currently being worked on. So schedule wise is not the concern for now14:21
*** kebray has quit IRC14:21
sc68calxuhanp: No, we are still on the 2 attr track :)14:21
aveigabaoli: what's different about it?14:22
baoliaveiga, can you be more specific on your question?14:22
aveigait looks to me like that BP is for setting up radvd in the qrouter namespace to act as an RA daemon, and I fully support doing that14:22
Shixiongxuhanp, I just sent you an email to your gmail account with proposed date. Please let me know if it works for you.14:22
xuhanpShixiong, got it. will reply14:22
baoliaveiga, it's proposing one attribute in the subnet API.14:23
*** egallen has joined #openstack-meeting14:23
aveigahttps://blueprints.launchpad.net/neutron/+spec/neutron-ipv6-radvd-ra doesn't seem to propose any api changes14:23
*** trey_h has joined #openstack-meeting14:23
*** kayaliu_ has quit IRC14:23
sc68calAh. I see the confusion14:24
aveigaunless you meant a different BP14:24
*** kayaliu_ has joined #openstack-meeting14:24
*** isviridov is now known as isviridov|away14:24
sc68calYour Blueprint in LP talks about doing radvd and is a child of the two attributes BP14:24
sc68calbut your spec in gerrit that you link to that bp is about the single attribute14:24
*** sushils_ has quit IRC14:24
*** Michalik_ has joined #openstack-meeting14:25
*** mwagner_lap has joined #openstack-meeting14:25
baolisc68cal, sorry for the confusion. I probably should've started a new BP.14:25
aveiga+1 to that, because the LP version is something I'd love to see14:25
aveigait would actually make my idea for ipv6 floats incredibly easy14:26
baoliaveiga, does that mean that there will be implementation in openstack to support slaac?14:26
aveigaof course14:26
baolisorry, two implemenation in openstack to support slaac14:26
aveigasure, and why not? It should be a config/build option to pick dnsmasq vs radvd14:26
aveigabesides, I think we need unicast RA14:27
baoliaveiga, I agree with you that with the RA, a lot of other things may become easier.14:27
*** vjay3 has joined #openstack-meeting14:27
aveigaunicast RA lets me add a float by just sending a new subnet advertisement to a single host :)14:27
aveigaI'm writing a BP for this now, actually14:27
*** dkranz has joined #openstack-meeting14:28
sc68calYes, also if you have something slated for J-2, please make sure you have a spec in neutron-specs14:28
sc68calpeople are chomping at the bit to -1 and -2 stuff that does not have a spec in neutron-specs14:28
dane_leblancaveiga, if we're adding unicast RAs, that will impact the design spec I wrote for muliple prefixes per port14:29
aveigahow does that implement selective prefix allocation?14:29
*** mspreitz has quit IRC14:29
aveigaI'd think it would actually be easier with unicast14:29
sc68caldane_leblanc: do you have a link for that spec?14:30
dane_leblancI was assuming SLAAC woudl be automatic... and not selective per port14:30
dane_leblanchttps://review.openstack.org/#/c/98217/14:30
aveigaoh, misunderstanding14:30
aveigaslaac for the fixed would be multicast still14:30
*** hashar has quit IRC14:31
aveigawe would only unicast RAs for extra features, like floats or prefix delegation nodes14:31
dane_leblancaveiga, okay... was thinking differently about floating ips14:31
dane_leblancI was thinking floating IPs would only use DHCP.14:31
*** jdob_ has joined #openstack-meeting14:31
*** jdob has quit IRC14:31
aveigadane_leblanc: absolutely, buit the dhcpv6 solicit has to be initiated by RA still14:32
dane_leblancBut your idea is less restrictive on admin14:32
aveigayou either do this via unicasting RA's (easy) or filtering the multicasted RA to select hosts (harder, more state/config to track)14:32
sc68calbaoli: What should we do about your launchpad blueprint, and the spec?14:33
baolisc68cal, I would create a new BP and link that to my spec.14:33
*** rkukura has left #openstack-meeting14:33
dane_leblancaveiga, agreed, unicast RA's would be less complicated14:33
sc68calOK. So I assume that we should remove https://blueprints.launchpad.net/neutron/+spec/neutron-ipv6-radvd-ra from the J-2 milestone14:34
*** thomasbiege1 has quit IRC14:34
baolisc68cal, well I'd still like to see the new bps put in the j-214:34
*** cknight has left #openstack-meeting14:34
sc68calbaoli: you mean for the single attribute?14:34
aveigaI'd like to see the radvd BP created as a -spec14:35
*** thomasbiege has joined #openstack-meeting14:35
aveigaeither that or I'm going to file a bug against the dnsmasq implementation for not supporting unicast RA14:35
baolisc68cal, yes. it's for both single attr and radvd. Becasue I'm going to use radvd to implement it14:35
aveigabaoli: can we split that?14:35
aveigaone for the radvd implementation, and one for single that depends on radvd14:36
sc68calOK - so here's my concern. I already -1'd your spec for the single attribute saying that it'd kill momentum. Now we're removing a blueprint from J-2 for adding radvd, because you want to continue on this single attribute path14:36
baoliaveiga, one attr doesn't depend on radvd.14:36
baoliaveiga, it's the opposite14:36
aveigaradvd doesn't depend on an api attribute14:37
*** doron_afk is now known as doron14:37
*** jaypipes has joined #openstack-meeting14:37
*** kgriffs|afk is now known as kgriffs14:38
baolisc68cal, you seem to suggest in the review that use one attr in the CLI14:38
*** moha_hunt has quit IRC14:38
baoliSo if one attr simplify the API, which is more important, I don't know the reason why we have to stick with the two attr.14:39
aveigabaoli: the suggestion is that you could provide a method for using one attr in the cli if people feel that it's "too complicated" to use two14:39
*** jaypipes has quit IRC14:39
aveigaI am strongly against a signle api attribute, as I really need those knobs for finer grained configurations14:39
baoliaveiga, any specific case that two attr can do but one attr can not?14:40
*** jaypipes has joined #openstack-meeting14:40
*** elo2 has quit IRC14:40
sc68calLet's take this off line14:40
aveigaselectively toggling provider networks14:40
*** jgrimm has quit IRC14:40
sc68calbaoli: I asked you to send an e-mail to the mailing list about this last week, if I recall14:40
*** doron is now known as doron_afk14:40
*** jdob_ is now known as jdob14:40
baolisc68cal, sorry, did you ask me to send configuration on dual stack?14:41
*** jaypipes has quit IRC14:41
sc68calI'd have to check the logs to be certain14:41
baolisc68cal, didn't get a chance to do that. But the devstack patch commit message pretty much described how to do that.14:41
*** jaypipes has joined #openstack-meeting14:42
*** nelsnelson has joined #openstack-meeting14:42
*** AlanClark has joined #openstack-meeting14:42
*** yingjun has joined #openstack-meeting14:42
sc68calI don't believe everyone is aware of the devstack patch, so it's always useful to start a thread on the ML and link things14:42
baolihttps://review.openstack.org/#/c/87987/14:42
*** jeffrey4l has joined #openstack-meeting14:42
*** BrianB___ has quit IRC14:44
baolisc68cal, it will be on the review alias, if not on the developer alias14:44
*** trey_h has quit IRC14:44
*** jaypipes has quit IRC14:44
*** trey_h has joined #openstack-meeting14:45
*** yaguang has quit IRC14:45
baoliaveiga, there is one value from my spec: provider_slaac, which excplicitly indicates provider net14:45
*** BrianB___ has joined #openstack-meeting14:45
*** jgallard has joined #openstack-meeting14:45
*** thedodd has joined #openstack-meeting14:45
*** jaypipes has joined #openstack-meeting14:46
baoliaveiga, that should cover the use case you guys are working on.14:46
sc68calShixiong: xuhanp: So I think for now we have only one BP that is slated for j-214:46
sc68calhttps://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-slaac14:46
sc68calDo you need help creating a spec for it in neutron-specs?14:46
ShixiongMaybe this should be the one we focus on14:46
*** ominakov has quit IRC14:47
*** xianghui has quit IRC14:47
xuhanpShixiong, do you have plan to do that? I can certainly help if you need14:47
*** sushils_ has joined #openstack-meeting14:47
ShixiongI am not sure what I need to do...to be honest....14:47
Shixiong"creating a spec for it in neutron-specs"?14:47
*** yingjun has quit IRC14:47
xuhanpWe need to create a new code review in neutron-specs project14:48
sc68calI agree - plus I did some of the legwork for you, the patch for provider-nets slaac checks for constants.DHCPV6_STATELESS and does an eui64 address calculation, so I think the API is all set, we just need to do the dnsmasq piece14:48
*** jmontemayor has joined #openstack-meeting14:48
*** trey_h_ has joined #openstack-meeting14:48
*** trey_h_ has quit IRC14:48
sc68calhttps://review.openstack.org/#/c/86044/7/neutron/db/db_base_plugin_v2.py14:48
xuhanpsc68cal, yep. that one is based on dazhao's patch, right?14:48
*** jmontemayor has quit IRC14:48
xuhanpI have some memory on that one.14:49
*** sushils_ has quit IRC14:49
*** sushils__ has joined #openstack-meeting14:49
*** trey_h_ has joined #openstack-meeting14:49
xuhanpShixiong, I can help on the spec create if you are not familiar with that. and we can talk about how to speed up the dnsmasq code in our talk this week.14:49
xuhanpif we are OK with that.14:50
ShixiongYup, that will definitely help.14:50
*** jmontemayor has joined #openstack-meeting14:50
ShixiongThanks, Xuhan!14:50
xuhanpShixiong, welcome14:50
*** trey_h has quit IRC14:50
sc68calxuhanp: yup14:52
*** ominakov has joined #openstack-meeting14:54
*** reed has joined #openstack-meeting14:54
*** ominakov has quit IRC14:54
*** Macaveli has quit IRC14:55
sc68calDoes the ipv6-radvd-ra blueprint depend on the single attribute? I don't think it does14:55
sc68calso I'd like to sign someone up for the work, or else it's going to get moved out of J-214:55
baolisc68cal, it talks about RA support in neutron14:55
baoliand the supporting implementation will be using radvd14:55
sc68calyes, but it was a child of the two attribute blueprint14:55
sc68calin launchpad14:56
sc68calwhich meant that it was going to use the two attribute changes to the API14:56
*** afazekas has quit IRC14:56
sc68calI believe your neutron-spec review needed to link to a new blueprint in launchpad14:56
sc68calsince that was an API change14:56
*** isviridov|away is now known as isviridov14:56
sc68calI'm sorry I didn't catch it sooner14:56
baolisc68cal, i didn't realize until today. Thanks for that. So I'm going to create a new BP and link the spec to the new BP14:57
*** otherwiseguy has joined #openstack-meeting14:57
*** cjellick has joined #openstack-meeting14:57
*** cjellick has quit IRC14:57
*** cjellick has joined #openstack-meeting14:58
*** mspreitz has joined #openstack-meeting14:58
sc68calOK, then I'm going to ask cores to move the radvd blueprint out of J-2 unless we have someoneone who wants to work on it14:58
aveigait needs a -spec first14:59
sc68calindeed14:59
aveigaI guess I can work on the spec, but there's no way I'd be able to implement it14:59
*** gokrokve has quit IRC14:59
sc68calOK, well that's all we have time for15:00
sc68calsee everyone next week, let's start some threads on the ML15:00
*** Michalik_ has quit IRC15:00
sc68cal#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Tue Jun 10 15:00:29 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-06-10-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-06-10-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-06-10-14.00.log.html15:00
*** gokrokve has joined #openstack-meeting15:00
*** Shixiong has quit IRC15:00
n0ano#startmeeting gantt15:01
*** eankutse1 has joined #openstack-meeting15:01
openstackMeeting started Tue Jun 10 15:01:11 2014 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: gantt)"15:01
openstackThe meeting name has been set to 'gantt'15:01
*** aveiga has left #openstack-meeting15:01
* n0ano is hopefully using the right window this week :-)15:01
n0anoanyone here to talk about the scheduler?15:01
mspreitzyes15:01
*** PaulMurray has joined #openstack-meeting15:01
*** jcoufal has joined #openstack-meeting15:01
*** hashar has joined #openstack-meeting15:02
toan-tranyes15:02
*** tianst has joined #openstack-meeting15:02
*** idegtiarov has joined #openstack-meeting15:02
*** jcoufal has quit IRC15:02
*** giustoXricordarv has joined #openstack-meeting15:02
*** doron_afk is now known as doron15:03
*** eankutse has quit IRC15:03
n0anobauzas won't be here today (traveling) but I got a status from him15:03
*** johnpur has joined #openstack-meeting15:03
n0ano#topic code forklift15:03
*** openstack changes topic to "code forklift (Meeting topic: gantt)"15:03
*** jcoufal has joined #openstack-meeting15:03
*** Michalik_ has joined #openstack-meeting15:03
n0anohe had to address issues related to object model support and miss use of some DB fields but the patches for the scheduler-lib are here:15:04
*** johnpur has left #openstack-meeting15:04
n0anohttps://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/scheduler-lib,n,z15:04
*** xianghui has joined #openstack-meeting15:04
*** ihrachyshka has quit IRC15:04
n0ano#action all to review the scheduler-lib patches15:04
*** HenryG has joined #openstack-meeting15:04
n0anoI did find some people to work on the isolate scheduler DB access BP so we should get some action on that15:05
n0anoother than that, I think the forklift is basically work in progress15:05
n0anoif no questions on that...15:06
*** jtomasek has quit IRC15:06
n0ano#topic no-db scheduler15:06
*** openstack changes topic to "no-db scheduler (Meeting topic: gantt)"15:06
*** vkmc has joined #openstack-meeting15:06
*** vkmc has quit IRC15:06
*** vkmc has joined #openstack-meeting15:06
n0anoI noticed that yorik (doesn't appear to be online today) abandoned the patch for the no-db work15:07
n0anoI wanted to talk to him about that as I don't think we wanted to just give up on it15:07
toan-trann0ano: I hope that's not because of last week15:07
n0anotoan-tran, agreed15:07
*** vjay3 has quit IRC15:08
n0anoI'll ping him on email and see if I can get an explanation, hopefully he is just looking at different ways to implement things15:08
*** vjay4 has joined #openstack-meeting15:08
*** ildikov_ has joined #openstack-meeting15:08
n0anoanyway...15:08
n0ano#topic policy based scheduler15:08
*** marun has joined #openstack-meeting15:08
*** openstack changes topic to "policy based scheduler (Meeting topic: gantt)"15:08
n0anotoan-tran, I believe this is your issue15:08
toan-trann0ano: thanks15:09
*** ildikov has quit IRC15:09
toan-tranHere is the bp: https://blueprints.launchpad.net/nova/+spec/policy-based-scheduler15:09
toan-tranand its specs: https://review.openstack.org/#/c/97503/215:09
toan-tranthe idea is to be able to control scheduling decision process by policy15:10
toan-trancurrently what're we're doing is to put a list of Filters, Weighers and parameters into nova.conf15:10
toan-tranall of these Filters & Weighers will be applied to ALL requests from ALL clients on ALL hosts15:10
*** dane_leblanc has quit IRC15:11
toan-tranimagin if we need 2 policies:15:11
toan-tranLoadBalancing for overall infrastructure15:11
*** dane_leblanc has joined #openstack-meeting15:11
*** doron is now known as doron_afk15:12
toan-tranand Consolidation (regrouping hosts) in an aggregate15:12
toan-tranthat's simply impossible15:12
mspreitzI'm not sure I understand your use case15:12
toan-tranFYI, we have this usecase at Cloudwatt15:12
toan-tran:)15:12
mspreitzwhat do you mean by "overall infrastructure", how is that different from an aggregate?15:12
toan-tranit's Windows licence :)15:12
toan-tranMicrosoft charges Windows licence by physical hosts15:13
*** jpeeler has quit IRC15:13
mspreitzso placement matters15:13
toan-tranthus it's important that we can regroup Windows VM in minimal of hosts15:13
toan-tran==> Consolidation15:13
mspreitzI do not understand why you are framing this as an issue for all VMs.  Shouldn't it be a policy issue for the VMs with Windows licenses whose cost you want to minimize?15:14
PaulMurraytoan-tran do you stack windows?15:14
n0anotoan-tran, devil's advocate here, wouldn't that just be a slightly more complex weighting funcitno15:14
toan-tranhowever, we still need the global Load Balancing in all infrastructure, so that other VMs will be distributed evenly15:14
*** ominakov has joined #openstack-meeting15:14
toan-tranPaulMurray: yes15:14
*** zhangleiqiang has joined #openstack-meeting15:15
toan-tranmspreitz: it's one of the usecases15:15
PaulMurraytoan-tran, very familiar... :)15:15
PaulMurraytoan-tran, we do it with filter scheduler15:15
PaulMurraytoan-tran, whats the problem?15:15
toan-trann0ano: yes this usecase is feasible  with another wiegher15:15
*** jcoufal has quit IRC15:15
mspreitzThe big picture thing that confuses me is that the blueprint talks about making distinctions per client, but the solution is not so structured15:15
PaulMurraytoan-tran, not saying it cant be better...15:15
toan-tranthe thing is more general15:15
*** mberlin has quit IRC15:16
toan-tranwe have only ONE global policy for all requests , all users, all clusters of hosts15:16
toan-tranwhat we're proposing is a seperation between scheduling logic from its application domain15:16
toan-transcheduling logic = how do you want to schedule the requested resources15:17
*** mberlin has joined #openstack-meeting15:17
toan-tranapplication demain = where you want to execute this logic15:17
*** dprince has quit IRC15:17
toan-trananother example then : :)15:17
*** sarob has joined #openstack-meeting15:17
*** YorikSar has joined #openstack-meeting15:18
toan-tran2 users signs 2 different contracts15:18
*** markwash has joined #openstack-meeting15:18
toan-tranone with gold quality (high quality equipments) , another with trial (low quality equipments)15:18
*** belmoreira has quit IRC15:19
toan-tranwith Filter Scheduler, you probably create 2 flavors and put metadata on them and give users the rights to use it15:19
YorikSarn0ano: Sorry for being late. We can get back to no-db topic once we're finished with other topics.15:19
n0anoYorikSar, tnx, will do15:19
toan-tranthe problem is that :15:20
toan-tranit's not transparent to users: he has to explicitly choose the right flavor15:20
*** matiu has quit IRC15:20
*** elo has joined #openstack-meeting15:20
toan-tranimagine that the trial user is now satisfied with the trial and decide to go for gold contract15:20
toan-tranthen he has to change his entire application to call for the gold flavor15:21
*** vkmc has quit IRC15:21
mspreitzhuh?15:21
mspreitzHow much of a change is that really?15:21
n0anotoan-tran, he just has to change the flavor requested, that doesn't seem like such a big deal15:21
toan-tranmspreitz: well, it's not tranparent15:22
mspreitzThe contract quality is inherently visible to the cloud user15:22
mspreitzone way or another15:22
n0anotoan-tran, not sure it should be transparent, he's changing what he will be billed, he should be aware of that15:22
toan-tranmspreitz: but technically  it is not managed by client, but by cloud provider15:23
mspreitzWhat n0ano said15:23
toan-trann0ano: he will be billed by his contract,15:23
*** peoplemerge1 has joined #openstack-meeting15:24
toan-tranyes15:24
n0anoI would imaging that cloud provider has two host aggregates, one gold & one bronze, users can use flavor to select the price/performance the user wants15:24
*** atiwari has joined #openstack-meeting15:24
toan-tranbut he does not need to verify his flavors15:24
*** jcoufal has joined #openstack-meeting15:24
toan-trann0ano: we do, actually, have several aggrs with associated flavors for customers to choose15:25
mspreitzI am very confused.  This example is about the very kind of stuff that flavors are about15:25
mspreitzwell, that's a bit of an overstatement, but you get the idea15:25
toan-tranmspreitz: the problem is that right now customers have to select the right flavors15:25
*** xuhanp has quit IRC15:25
toan-tranand we want to leverage from customers15:26
mspreitzYes, flavors are based on considerations that are user visible15:26
toan-tranto manage the whole deployment process from cloud provider's end15:26
n0anotoan-tran, I think your policy based scheduling might have merit but we really don't see a good use case for it yet15:26
mspreitzFrom the user's point of view, flavors are nothing but an unwelcome pain.  They are there to make the providing easier.15:26
*** annegentle_ has joined #openstack-meeting15:26
toan-tranmspreitz: exactly15:27
mspreitzOK, let me try to buck him up15:27
mspreitzI can imagine use cases15:27
mspreitztoan-tran may not remember my history here, but I came in with similar issues15:27
toan-tranmspreitz: go ahead15:27
mspreitzIn fact, my group worked an example in 2012 where we deployed VMs running IBM software whose license cost also depends on placement15:27
*** jgrimm has joined #openstack-meeting15:28
mspreitzwe put a policy statement on those VMs that created a preference for co-location.15:28
mspreitzA somewhat precise preference, in terms of licensing.15:28
mspreitzIn the same example we also had some anti-colocation constraints for reliability15:28
*** changbl has joined #openstack-meeting15:29
*** kayaliu_ has quit IRC15:29
*** vkmc has joined #openstack-meeting15:29
mspreitzAnd used logic that threw in some preference for minimzing network usage.15:29
*** tianst has quit IRC15:29
mspreitzA reasonable thing if you are deploying, say, a three tier web application.15:29
mspreitzBut we took a little different tack...15:29
mspreitzWe let there be policy statements in the input, attached precisely to groups of VMs and between them.15:30
*** jeffrey4l has quit IRC15:30
*** nshaikh has quit IRC15:30
mspreitzour solution transformed the input to a constrained optimization problem and solved that to get the placement.15:30
mspreitzYou may know that some others guys from Cisco and VMware are advocating this approach15:30
mspreitzas well15:31
toan-tranSolverScheduler you mean15:31
mspreitzyes15:31
*** gyee has joined #openstack-meeting15:31
toan-tranI have done some analysis on that: https://docs.google.com/document/d/1RfP7jRsw1mXMjd7in72ARjK0fTrsQv1bqolOriIQB2Y/edit?usp=drive_web15:32
*** thedodd has quit IRC15:32
toan-tranSolverScheduler needs a bunch of contraints as input15:32
toan-tranand PolicyBasedScheduler can get these constraints15:32
toan-tranactually the constraint will be what the policy rules dictate15:33
mspreitzYes, I saw that analysis, and was not as alarmed by it as by the remarks in the blueprint15:33
n0anotime check, I want to talk about no-db and have an open, do we have an end goal for this discussion?15:33
mspreitzIf your intent is what you outline in that analysis, I may be able to live with it15:33
mspreitzn0ano: i'm happy to stop here and do some more reading and thinking15:34
toan-tranmspreitz: oh, I have intention to develop it into a more ambitious than that :)15:34
toan-tranthe first step is to have an policy based scheduling engine15:34
*** thedodd has joined #openstack-meeting15:34
toan-tranthen (much much) later it can incorprate with Tetris & Congress15:34
n0anotoan-tran, but first you have to get by the objections to the current BP :-)15:35
toan-transo that we can have a scheduling engin inside Gantt to be able to controlscheduling from intial placement to life-cycle15:35
toan-trann0ano: that's right :D15:35
*** fnaval has joined #openstack-meeting15:35
toan-tranI tries my best to present something simple in nova first15:36
n0anotoan-tran, note, you have to refresh your BP, it's about to get dropped right now15:36
toan-trann0ano: what do you mean?15:36
*** idegtiarov has quit IRC15:36
n0anolast message - code review expired after 1 week of no activity after a negative review, it can be restored using the `Restore Change` button under the Patch Set on the web interface15:37
*** kayaliu_ has joined #openstack-meeting15:37
toan-trann0ano: ok :)15:37
n0anoanyway, moving on...15:37
n0ano#topic no-db scheduler15:37
*** openstack changes topic to "no-db scheduler (Meeting topic: gantt)"15:37
n0anoYorikSar, you still here?15:38
YorikSarn0ano: Yep15:38
n0anoI see you abandoned the current patch, I hope that just means you thinking how to do it and not giving up15:38
YorikSarI've written my reasons in the comment to change request in the spec repo15:38
*** Longgeek has quit IRC15:39
mspreitzlink?15:39
YorikSarNope, I think it's just a premature optimization that shouldn't be implemented right away.15:39
YorikSar#link https://review.openstack.org/9212815:39
YorikSarThere are other options that hasn't been considered.15:39
*** edmund has joined #openstack-meeting15:39
n0anogood, I agree, just so that we don't give up completely15:40
YorikSarAnd there's nothing to write in "Problem statement" section.15:40
*** jpeeler has joined #openstack-meeting15:40
YorikSarSo I guess this effort might be revived once Gantt faces performance issues related to DB, but for now it should be left alone.15:40
n0anoI thought this all started with the performance issues with a Bluehost 10,000 node system, I would think those performance issues reamain15:41
n0anos/reamain/remain15:41
*** Leonr has joined #openstack-meeting15:41
YorikSarThere have been a lot of work done under aegis of no-db-scheduler blueprint (even before it has been created).15:41
*** sushils__ has quit IRC15:41
*** nkubota has joined #openstack-meeting15:41
YorikSarThey should be verified. One hug performance bottleneck has been eliminated - separate key-value table for host states.15:42
YorikSar*huge15:42
n0anothat required a join operation, right?15:42
YorikSarYes15:42
*** nacim has quit IRC15:43
YorikSarAnd all cool documents-reports has been written before that has been done.15:43
mspreitzAnd it has been experimentally verified that those joins cost less than the stuff that was eliminated?15:43
YorikSarmspreitz: Yes...15:43
*** sushils_ has joined #openstack-meeting15:44
YorikSarI'm talking about changes that happened last summer iirc15:44
mspreitzthanks15:44
*** BrianB___ has quit IRC15:44
*** changbl has quit IRC15:44
*** Michalik_ has quit IRC15:45
n0anoso, to summarize, this is really a performance optimization issue and we want to make sure we are addressing the right problem15:45
YorikSarSo now I suggest to focus on more pressing issues like separating Gantt and polishing its API and come back to performance once it becomes a problem.15:45
n0anoYorikSar, +115:46
YorikSarn0ano: Yes15:46
*** eankutse1 has quit IRC15:46
*** eankutse has joined #openstack-meeting15:46
n0anoOK, sounds like a plan15:46
toan-tranYorikSar: I think the problem is always there, but I agree that we can address no db once Gantt is materalized15:46
YorikSartoan-tran: It's speculated that it should become a real problem at 10k+ nodes.15:47
YorikSartoan-tran: So I wouldn't say it's there. It might be.15:47
n0anomoving on...15:48
YorikSartoan-tran: I mean it definitelly was there, but in current state of Nova it might be already gone.15:48
n0ano#topic opens15:48
*** openstack changes topic to "opens (Meeting topic: gantt)"15:48
n0anobased upon last weeks discussion I've created a BP to optimize the status reporting from compute nodes15:49
n0ano#link https://review.openstack.org/#/c/97903/15:49
*** egallen has quit IRC15:49
n0anobasic idea is, rather that update the DB every minute, only update the DB when the status changes15:49
mspreitzsome folks were talking about status that changes every time, like CPU utilization.  So I am confused.15:49
*** Michalik_ has joined #openstack-meeting15:49
n0anocpu utilization is not currently reported so that will be a future issue15:50
mspreitzsame for memory?15:50
toan-tranmspreitz: cpu utilization is utilisation-aware15:50
mspreitz?15:50
toan-trannot on this period update15:50
mspreitztoan-tran: what do you mean by "cpu utilization is utilisation-aware" ?15:51
n0anomspreitz, interesting point, turns out I think there's a bug in the current memory reporting, it doesn't report used memory...15:51
n0anoit only reports memory used by instances15:51
toan-tranmspreitz: period update does not update cpu utilisation if i'm not wrong15:51
mspreitzWell, actually, I think we should focus first on allocated memory rather than used memory15:51
n0anotoan-tran, +115:51
*** egallen has joined #openstack-meeting15:51
PaulMurrayn0ano, the discussion I remember talked about calculating regularly but only updating if it changed15:51
n0anoPaulMurray, that's what I do with the current reporting mechanism15:52
*** elo has quit IRC15:52
mspreitzby which I think I may mean what n0ano said: focus on how much memory is dedicated to instances15:52
PaulMurrayn0ano, so does this change that reporting?15:52
n0anomspreitz, but that's not a true indication of `node` resources, if many other processes are using memory you might not want to schedule onto that node15:53
*** Fdot_ has quit IRC15:53
*** paulbc has joined #openstack-meeting15:53
mspreitzyeah, if you really want a compute node doing other things too, then you have to account for them15:54
*** sushils_ has quit IRC15:54
*** doron_afk has quit IRC15:54
n0anowhich it is currently not doing, I'll raise that issue on the mailing list and see what peope think15:54
mspreitzand you have to account for broken compute-node business too (e.g., half-deleted VMs)15:54
*** nedbat_ has joined #openstack-meeting15:54
n0anoyou could argue both ways (we only care about instance usage vs. node usage), I don't know what people really want15:55
PaulMurrayn0ano, actually we want to know what is left available15:55
PaulMurrayn0ano, imo15:55
n0anowhich is not what is currently being reported15:55
mspreitzWhat I would really like is to count memory allocated to instances + all other memory usage, compare with memory capacity15:55
n0anomspreitz, +115:56
mspreitzBut let me revise that after a second's reconsideration...15:56
toan-tranmspreitz: I'm not sure if the current period update count on allocated mem to instances15:57
mspreitzif the non-instance usage is arbitrarily dynamic, you could get into over-use15:57
n0anothat is my preference but I see it rather simplistic, report free memory (no matter what the occupied memory is used for)15:57
n0anomspreitz, ?15:57
*** IvanBerezovskiy has left #openstack-meeting15:57
mspreitzSuppose you allocate all available memory now, and then some non-instance process wants even more?15:57
n0anolinux handles that15:58
PaulMurraymspreitz, some hypervisors use memory in addition to the instance allocation15:58
n0anoPaulMurray, all the more reason to report true memory usage15:58
mspreitzYou really want allocations such that the users can be relied on to not exceed them.  We rarely want to actually use the host's virtual memory, we want to stay in physical memory15:58
*** paulmo has joined #openstack-meeting15:58
*** nedbat has quit IRC15:58
*** markwash has quit IRC15:58
PaulMurrayn0ano, yes, agreed15:59
mspreitzI am presuming that the overheads due to being a compute node can be reasonably characterized15:59
*** julim has quit IRC15:59
n0anowe're running out of time, I suggest everyone comment on my BP and respond to the email thread that I start16:00
n0anoso, top of the hour, tnx everyone and we'll talk again next week16:00
*** Leon has joined #openstack-meeting16:00
n0ano#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
*** phil__ has quit IRC16:00
openstackMeeting ended Tue Jun 10 16:00:47 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-10-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-06-10-15.01.txt16:00
*** nlahouti__ has joined #openstack-meeting16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-06-10-15.01.log.html16:00
*** Leon is now known as Guest2645216:01
*** nlahouti__ has quit IRC16:01
*** terryw has joined #openstack-meeting16:01
*** coolsvap|afk is now known as coolsvap16:01
*** MaxV has quit IRC16:01
*** otherwiseguy has quit IRC16:01
*** egallen has quit IRC16:02
*** julim has joined #openstack-meeting16:02
*** peoplemerge1 has quit IRC16:03
*** Leonr has quit IRC16:03
*** pballand has joined #openstack-meeting16:03
*** pballand has quit IRC16:03
*** emagana has quit IRC16:04
*** egallen has joined #openstack-meeting16:04
*** paulbc has left #openstack-meeting16:04
*** hemna has joined #openstack-meeting16:04
*** luis_ has joined #openstack-meeting16:05
*** vjay4 has quit IRC16:05
*** otherwiseguy has joined #openstack-meeting16:06
*** kayaliu_ has quit IRC16:06
*** alexpilotti_ has joined #openstack-meeting16:07
*** jgrimm has quit IRC16:07
*** markwash has joined #openstack-meeting16:07
*** marcoemorais has joined #openstack-meeting16:08
*** ramishra has joined #openstack-meeting16:09
*** emagana has joined #openstack-meeting16:10
*** terryw has quit IRC16:10
*** annegentle_ has quit IRC16:10
*** luis_ has quit IRC16:11
*** alexpilotti_ has quit IRC16:12
*** spzala has joined #openstack-meeting16:12
*** evgenyf has quit IRC16:13
*** annegent_ has joined #openstack-meeting16:14
*** cath6184 has joined #openstack-meeting16:14
*** julienvey has quit IRC16:14
*** zhangleiqiang has quit IRC16:16
*** paulmo has left #openstack-meeting16:16
*** jackib has joined #openstack-meeting16:16
*** shakayumi is now known as shakayumi_afk16:17
*** shakayumi_afk has quit IRC16:19
*** jaypipes has quit IRC16:20
*** Michalik_ has quit IRC16:20
*** jgallard has quit IRC16:22
*** SridarK has quit IRC16:24
*** jackib has quit IRC16:25
*** bgorski has joined #openstack-meeting16:25
*** thomasbiege1 has joined #openstack-meeting16:25
*** luqas has quit IRC16:25
*** dprince has joined #openstack-meeting16:26
*** thomasbiege has quit IRC16:26
*** marcoemorais has quit IRC16:27
*** marcoemorais has joined #openstack-meeting16:27
*** denis_makogon_ has joined #openstack-meeting16:27
*** marcoemorais has quit IRC16:28
*** marcoemorais has joined #openstack-meeting16:29
*** marcoemorais has quit IRC16:29
*** richm has joined #openstack-meeting16:29
*** ihrachyshka has joined #openstack-meeting16:29
*** marcoemorais has joined #openstack-meeting16:29
*** jgrimm has joined #openstack-meeting16:29
*** thomasbiege has joined #openstack-meeting16:30
*** thomasbiege1 has quit IRC16:30
*** thomasbiege has quit IRC16:31
*** toan-tran has quit IRC16:33
*** jaypipes has joined #openstack-meeting16:33
*** annegent_ is now known as annegentle_16:34
*** mdml has joined #openstack-meeting16:34
*** vuil has joined #openstack-meeting16:35
*** xianghui has quit IRC16:35
*** markmcclain has joined #openstack-meeting16:36
*** maxdml has quit IRC16:37
*** igordcard has quit IRC16:39
*** isviridov is now known as isviridov|away16:40
*** gokrokve_ has joined #openstack-meeting16:40
*** vivek-ebay has joined #openstack-meeting16:40
*** emaganap has joined #openstack-meeting16:41
*** emagana has quit IRC16:43
*** gokrokve has quit IRC16:43
*** luis_ has joined #openstack-meeting16:45
*** ramashri has joined #openstack-meeting16:46
*** mwagner_lap has quit IRC16:48
*** caleb_ has joined #openstack-meeting16:48
*** mtanino has quit IRC16:49
*** dkranz has quit IRC16:49
*** Michalik_ has joined #openstack-meeting16:49
*** k4n0 has joined #openstack-meeting16:50
*** s3wong has joined #openstack-meeting16:50
*** changbl has joined #openstack-meeting16:50
*** yogeshmehra has joined #openstack-meeting16:51
*** thinrichs has joined #openstack-meeting16:51
*** hashar has quit IRC16:54
*** jcoufal has quit IRC16:55
*** pcm_ has left #openstack-meeting16:55
*** emaganap has quit IRC16:56
*** _nadya__ has joined #openstack-meeting16:56
*** luis_ has quit IRC16:57
*** emagana has joined #openstack-meeting16:57
*** trey_h_ has quit IRC16:57
boris-42#startmeeting rally16:59
openstackMeeting started Tue Jun 10 16:59:27 2014 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot.16:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:59
*** openstack changes topic to " (Meeting topic: rally)"16:59
openstackThe meeting name has been set to 'rally'16:59
boris-42msdubov ping16:59
coolsvaphello16:59
boris-42coolsvap Hi there16:59
boris-42hughsaunders ping16:59
k4n0o/16:59
msdubovboris-42 Hi!16:59
*** denis_makogon_ is now known as denis_makogon17:00
*** _nadya_ has quit IRC17:00
*** tkay has joined #openstack-meeting17:00
*** amaretskiy has joined #openstack-meeting17:01
*** klindgren_ has joined #openstack-meeting17:01
*** kun_huang has joined #openstack-meeting17:01
*** rediskin has joined #openstack-meeting17:02
boris-42kun_huang rediskin  klindgren_ glad to see u17:02
*** olkonami has joined #openstack-meeting17:02
boris-42#topic rally docs17:02
*** openstack changes topic to "rally docs (Meeting topic: rally)"17:02
kun_huangboris-42 :)17:02
boris-42msdubov share with others what is the current state of it17:02
*** julim has quit IRC17:03
*** cath6184 has quit IRC17:03
msdubovboris-42 So I'm currently transcribing the docs to the .rst format, to push it to readthedocs17:03
msdubovI'll publish a corresponding patch today or tomorrow17:04
*** weshay has quit IRC17:04
msdubovFurther work is to extend the docs with new texts17:04
*** weshay has joined #openstack-meeting17:04
*** egallen has quit IRC17:04
msdubovAnd also restructure the docstrings in code17:04
msdubovSo that we can easily implement the "rally info" command17:04
msdubovBasically that's the plan17:05
*** blogan has joined #openstack-meeting17:05
msdubovHope somebody will help me with that ;)17:05
*** rockyg has joined #openstack-meeting17:05
*** thomasbiege has joined #openstack-meeting17:05
kun_huangboris-42 msdubov I'm glad to do that; actually I need join you back17:06
boris-42kun_huang yep we are missing you imho17:07
boris-42#topic rally info17:08
*** openstack changes topic to "rally info (Meeting topic: rally)"17:08
boris-42As there is a lot of new members17:08
*** harlowja_away is now known as harlowja17:08
boris-42could you explain idea of it msdubov ?17:08
boris-42and share with others that document17:08
msdubovboris-42 Yep, sure, wait a bit17:08
msdubovSo first the idea:17:09
*** jackib has joined #openstack-meeting17:09
msdubovThe 'rally info' command should serve as a helping system built-in in the CLI17:09
msdubovFor example you can write "rally info contexts" and get the overall description of what the contexts in Rally are for17:10
msdubovOr "rally info NovaServers.boot_server" => Info about that specific benchmark scenario17:10
msdubovAnd that info should be retrieved automatically from the docstrings (at least the most of it)17:11
msdubovHere is the link: https://docs.google.com/a/mirantis.com/document/d/1m4HqrbWOfcvi-LKjehJZTeYX1p-TzXeUvfIHhyU9nOI/edit#heading=h.zh97w9nib53417:11
msdubovThe doc contains an overview of what the "rally info" will look like17:11
hughsaundershey17:11
boris-42klindgren_ k4n0 coolsvap ^ anybody interested ?17:11
msdubovAnd also in p.5, there is a work plan17:11
boris-42hughsaunders hey hey=)17:12
coolsvapboris-42: I am already working on one of the CLI, I can have work with msdubov17:12
coolsvapreading the doc17:12
boris-42coolsvap yep that will be great17:13
*** ngoswami has quit IRC17:13
*** VijayB has joined #openstack-meeting17:13
kun_huangmsdubov good cmd; are there some first commits?17:13
*** VijayB has quit IRC17:14
*** VijayB has joined #openstack-meeting17:14
*** colinmcnamara has joined #openstack-meeting17:14
*** VijayB has quit IRC17:14
msdubovkun_huang, No commits for the "rally info" command but there is currently some work on improving the docstrings (e.g. that patch with rst docs mentioned above)17:14
*** derekh_ has quit IRC17:15
*** VijayB_ has joined #openstack-meeting17:15
*** egallen has joined #openstack-meeting17:15
*** egallen has quit IRC17:16
coolsvapmsdubov: okay17:17
*** paragan has quit IRC17:17
*** VijayB has joined #openstack-meeting17:17
*** vrovachev has quit IRC17:17
boris-42#topic Functional testing17:18
*** openstack changes topic to "Functional testing (Meeting topic: rally)"17:18
boris-42rediskin pls provide in verbose mode what you are doing17:19
*** jgrimm has quit IRC17:19
*** HenryG has quit IRC17:19
rediskinhere is blueprint https://blueprints.launchpad.net/rally/+spec/tests-integrated17:19
*** balajiiyer has joined #openstack-meeting17:19
*** VijayB_ has quit IRC17:19
rediskinone helper function and one test is done :)17:20
*** mspreitz has quit IRC17:20
rediskinhttps://review.openstack.org/8573817:20
*** HenryG has joined #openstack-meeting17:20
*** jackib has quit IRC17:20
*** otherwiseguy has quit IRC17:20
* boris-42 ^ that was super verbose mode of rediskin lol=)17:20
rediskinas you can see in work items, next step is command's output format17:20
*** VijayB has quit IRC17:21
rediskintest results you can see in jenkins's comment for every patch (curreenlty last line)17:22
*** fnaval has quit IRC17:22
*** fnaval has joined #openstack-meeting17:22
boris-42Okay lemme add some info for non related to this stuff17:22
rediskinhttp://logs.openstack.org/55/89555/11/check/check-rally-cli/bb84bd4/console.html17:23
boris-421) There is special job that is run against every patch in rally17:23
boris-42You already saw it17:23
boris-42it's called check-rally-cli17:23
boris-42if you click on it you'll get ^ that one from rediskin link result17:23
boris-42rediskin made a special mini framework for that17:24
* boris-42 rediskin and it's located here https://github.com/stackforge/rally/blob/master/tests_ci/test_cli.py17:24
boris-42That job actually run devstack that install openstack & rally17:24
boris-42and then run all these tests17:24
boris-42from DeploymentTestCase17:25
boris-42and other17:25
boris-42what we need now is to test all CLI commands that we have and check that they works17:25
boris-42But we have some small issue17:25
*** markmcclain has quit IRC17:25
boris-42They draw "tables" and it's hard to parse them17:25
boris-42so rediskin said that probably we should add to all commands JSON format as well17:25
boris-42and then we can test all17:26
hughsaunders+117:26
rediskinrally deployment list --output json17:26
boris-42+ it's nice feature (if somebody is going to integrate somewhere rally)17:26
*** caleb_ has quit IRC17:26
boris-42rediskin or --out_format ison17:26
*** fnaval has quit IRC17:27
boris-42or --rest json lol17:27
hughsaunderswhat do thethe rporjects use for this? as i think they have started supporting alternative output formats17:27
boris-42hughsaunders not sure they they support alternative outputs17:27
hughsaundersoh, dear terrible touch screen typing!17:27
*** nedbat has joined #openstack-meeting17:27
rediskinopenstack.common.cliutils used in rally17:28
*** emaganap has joined #openstack-meeting17:28
*** dims_ has quit IRC17:28
rediskinthere is no support for other formats, only prettytable17:28
boris-42hughsaunders actually it's implementation related17:28
*** emaganap has quit IRC17:29
*** markmcclain has joined #openstack-meeting17:29
*** xwizard has joined #openstack-meeting17:29
boris-42hughsaunders so I think that we should just implement it17:29
*** malini2 has joined #openstack-meeting17:29
hughsaundersin common?17:30
rediskinmaybe we can make own print_list function and contribute it to upstream17:30
*** nedbat_ has quit IRC17:30
*** carl_baldwin has joined #openstack-meeting17:30
*** xwizard is now known as tnurlygayanov_17:30
hughsaundersI must have been confused, cant find an option for alternative formatting in other openstack projects17:31
*** emagana has quit IRC17:31
*** emagana has joined #openstack-meeting17:31
hughsaundersbut however its implemented, great idea17:31
boris-42hughsaunders sometimes commands prints as well hints17:32
boris-42hughsaunders and other formatting stuff17:32
*** balajiiyer has left #openstack-meeting17:32
boris-42hughsaunders so it's not just about printing tables back in JSON17:32
boris-42hughsaunders it's just a different output at all17:32
boris-42rediskin ^17:32
hughsaundersboris-42: so how would a user split the hints from the json output?17:33
rediskinsome unix command have oprtion for "batch-mode"17:33
hughsaundersor would hints be surpressed when json is output?17:33
boris-42hughsaunders read my messages17:34
*** japplewhite has left #openstack-meeting17:34
hughsaundersboris-42: so you17:34
boris-42[21:32:01] <boris-42> hughsaunders sometimes commands prints as well hints17:34
boris-42[21:32:06] <boris-42> hughsaunders and other formatting stuff17:34
rediskine.g top:  -b  :Batch-mode operation17:34
rediskin            Starts top in 'Batch' mode, which could be useful for sending output from top to other programs or to a file...17:34
boris-42[21:32:14]  balajiiyer (~Adium@72.32.115.231) left the channel.17:34
boris-42[21:32:25] <boris-42> hughsaunders so it's not just about printing tables back in JSON17:34
boris-42[21:32:32] <boris-42> hughsaunders it's just a different output at all17:34
boris-42hughsaunders rediskin  nope guys17:34
boris-42hughsaunders rediskin it's just different output at all17:34
hughsaundersboris-42: so no hints/comments when json is output?17:35
boris-42hughsaunders rediskin rally detailed for example will print just list17:35
hughsaundersthat makes sense as then it will be easy to parse17:35
boris-42hughsaunders in this list every element is aggregated data17:35
boris-42{"atomic_table": {}, "scenario_output": xxx, ….}17:35
*** Michalik_ has quit IRC17:36
*** dane_leblanc has quit IRC17:36
*** denis_makogon has quit IRC17:37
*** VijayB_ has joined #openstack-meeting17:37
*** amotoki_ has quit IRC17:37
*** dane_leblanc has joined #openstack-meeting17:38
hughsaundersahh, so multiple tables may be encoded into a single json output17:38
boris-42hughsaunders nope17:38
boris-42hughsaunders let's avoid mess17:38
boris-42hughsaunders Pretty user oriented output is one task17:39
*** ivar-lazzaro has joined #openstack-meeting17:39
boris-42hughsaunders ugly formal json output is another17:39
boris-42hughsaunders one should be easy for humans another for machines17:39
hughsaundersok17:40
*** markwash_ has joined #openstack-meeting17:41
*** dims_ has joined #openstack-meeting17:42
*** thedodd has quit IRC17:42
*** markwash has quit IRC17:43
*** markwash_ is now known as markwash17:43
boris-42hughsaunders cause otherwise we will get something that is hard to use for both humans & machines17:43
boris-42hughsaunders + mess in code=)17:43
boris-42hughsaunders with non trivial logic=)17:43
*** Mandell has joined #openstack-meeting17:44
*** colinmcnamara has quit IRC17:44
*** eankutse1 has joined #openstack-meeting17:44
*** _nadya__ has quit IRC17:45
*** dshurtle has joined #openstack-meeting17:45
boris-42#topic free discussion17:46
*** openstack changes topic to "free discussion (Meeting topic: rally)"17:46
boris-42hughsaunders msdubov marcoemorais rediskin k4n0 kun_huang coolsvap amaretskiy anything to discuss?17:46
*** zdiN0bot has joined #openstack-meeting17:47
rockygo/17:47
boris-42rockyg hi there17:47
boris-42rockyg wanna discuss rally?)17:47
*** eankutse has quit IRC17:47
rockygHi!  refstack is having a f2f in SF tomorrow.  I was hoping we could get a rally person in the mix.  Maybe demo rally?17:47
amaretskiynothing specific to discuss from me, I'm going to discuss my patches with boris-4217:48
kun_huangboris-42 nope, I'm reading functional testing discuss17:48
*** luis_ has joined #openstack-meeting17:48
boris-42SF?)17:48
boris-42rockyg ^17:48
rockygI think you guys have the UI donw and maybe your UI could have differnt endpoints?  Rally, test server, refstack?17:48
rockygSan Feancisco.17:49
boris-42rockyg oh unfortunately I am now in Moscow...17:49
rockyg^Francisco17:49
boris-42rockyg and we don't have anybody in US that is related to rally =(17:49
*** Haneef has joined #openstack-meeting17:49
rockygAnyone out in SF bay area?17:49
boris-42rockyg =(17:49
rockygDang.17:49
boris-42rockyg I was there17:49
boris-42rockyg recently (about 3 weeks ago)17:49
rockygMaybe we could do an irc or joinme for a bit?17:50
boris-42rockyg maybe Hangout call?17:50
boris-42rockyg I think google hangout is good enough for such things17:50
coolsvapi think hangout is an option17:50
rockygYeah, that would work.  I'm not sure on times, though because our f2f is 1300-1800 UTC-0717:50
coolsvapi m waiting on it17:50
*** sballe_ has quit IRC17:50
rockygCool coolsvap17:51
boris-42rockyg so I can wake up in 4:30 a.m.17:51
*** zns has joined #openstack-meeting17:51
hughsaundersboris-42: dedication!17:51
rockygI really want to get some synergy going here and it seems rally UI is likely pretty solid and most advanced of all out there.17:51
*** akuznetsov has quit IRC17:51
boris-42rockyg pls could you provide your email17:52
rockygWhat is that utc, boris-42?17:52
boris-42hughsaunders +417:52
*** haomaiwang has quit IRC17:52
boris-42rockyg utc +417:52
*** zdiN0bot has left #openstack-meeting17:52
boris-42rockyg so if we make it in 5 a.m. it will be about 6 p.m. in SF17:53
rockygmy email is rockyg@gmail.com  and rochelle.grober@huawei.com, but gmail is better for tomorrow.17:53
*** ildikov_ has quit IRC17:53
boris-42rockyg works for you?17:53
boris-42hughsaunders wanna some late meeting?)17:53
boris-42coolsvap are you going to take a part in this stuff?17:53
*** Michalik_ has joined #openstack-meeting17:53
coolsvapboris-42: yes17:53
boris-42coolsvap email then17:54
rockygI'll get others on board for it.  I think a late running meeting is fine.  Might get a little pushback, but I can be pushy back;-)17:54
coolsvapcoolsvap@gmail.com17:54
hughsaundersboris-42: i may be able to join also17:54
*** ildikov_ has joined #openstack-meeting17:54
*** caleb_ has joined #openstack-meeting17:54
*** ivar-lazzaro1 has joined #openstack-meeting17:54
boris-42hughsaunders sorry for such a crazy time17:54
boris-42hughsaunders I just changed my schedule tied to work till late=)17:55
rockygthat would be cool.  a refstack/Rally mini summit17:55
*** rm_work|away is now known as rm_work17:55
boris-42rockyg yep17:55
kun_huangrockyg boris-42 what's the accurate time of that refstack meeting?17:56
boris-42hughsaunders rockyg kun_huang  we need to make some party in Moscow17:56
*** e0ne has joined #openstack-meeting17:56
hughsaundersboris-42: no promises but add me to the hangout and i'll join if i can17:56
boris-42coolsvap ^17:56
hughsaundersboris-42: if mirantis is paying ;-)17:56
boris-42hughsaunders hehe=)17:56
rockygparty in Moscow!  Maybe after Paris?17:56
boris-42rockyg maybe before?17:57
*** ihrachyshka has quit IRC17:57
rockygGotta get my passport in order!17:57
boris-42rockyg need to talk with Mirantis=)17:57
boris-42rockyg about party lol17:57
kun_huangboris-42 rockyg both okay for me. I haven't gone to Europe17:57
coolsvaprockyg: add me for hangout17:57
rockyg<chucckle>17:57
*** ivar-lazzaro has quit IRC17:58
boris-42kun_huang wanna as well hangout ?17:58
rockygOK.  Anyone who wants in, post email here so I can refer back to minutes.17:58
boris-42rockyg coolsvap  everybody get invites?17:58
kun_huangrockyg okay17:58
hughsaundersrockyg: hugh@wherenow.org17:58
boris-42rockyg I already made invite17:58
boris-42lol17:58
hughsaundersboris-42: just got it..17:59
*** e0ne has quit IRC17:59
rockygKewl!  add davidlenwell and zehicle if you can.17:59
*** AndChat|641136 has joined #openstack-meeting17:59
boris-42rockyg go to rally chat17:59
boris-42rockyg openstack-rally17:59
*** kristysiu has joined #openstack-meeting17:59
boris-42so glad to see you guys all17:59
rockyggoing now.17:59
boris-42#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Tue Jun 10 17:59:45 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-06-10-16.59.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-06-10-16.59.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-06-10-16.59.log.html17:59
*** rodrigods has joined #openstack-meeting18:00
*** olkonami has left #openstack-meeting18:00
*** raildo has joined #openstack-meeting18:00
stevemaro/18:00
kristysiuhi18:00
bknudsonhi18:00
morganfainbergdolphm, ayoung, bknudson, dstanek, jamielennox, morganfainberg, stevemar, gyee, henrynash, topol, marekd, lbragstad, joesavak, shardy, fabiog, fmarco76, nkinder, lloydm, shrekuma, ksavich18:00
ayoungYou made it?18:01
*** jlibosva has quit IRC18:01
morganfainbergmeeting time! https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:01
stevemarahoy18:01
morganfainbergayoung, just got back this second18:01
*** AndChat|641136 is now known as e0ne18:01
*** amaretskiy has left #openstack-meeting18:01
*** eankutse1 has quit IRC18:01
morganfainbergayoung, literally sat down.18:01
morganfainbergseems like we're light on people today... anyway...18:01
*** henrynash has joined #openstack-meeting18:01
gyee\o18:01
henrynashhi18:01
morganfainberghere we go.18:01
morganfainberg#startmeeting keystone18:01
openstackMeeting started Tue Jun 10 18:01:59 2014 UTC and is due to finish in 60 minutes.  The chair is morganfainberg. 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
morganfainberg#topic Juno1 Milestone18:02
*** openstack changes topic to "Juno1 Milestone (Meeting topic: keystone)"18:02
*** rwsu has joined #openstack-meeting18:02
*** DavidHu has joined #openstack-meeting18:02
morganfainberg#link https://launchpad.net/keystone/+milestone/juno-118:02
*** emagana has quit IRC18:02
dstaneko/18:02
morganfainbergAny changes that aren't gating by EOD today will be pushed toj218:02
morganfainbergwe have 2 changes that need eyes (afaik)18:03
*** e0ne has quit IRC18:03
morganfainberg#link https://review.openstack.org/#/c/99075/18:03
*** emagana has joined #openstack-meeting18:03
*** jaypipes has quit IRC18:03
morganfainberg#link https://review.openstack.org/#/c/74214/18:03
gyeegating is pretty risky these days :)18:03
stevemari'll take a look at those today18:03
dstaneki will too18:03
morganfainberggyee, thats why today is the goal, gives us 2 days?18:03
ayounglast one is pretty solid18:03
*** colinmcnamara has joined #openstack-meeting18:04
ayoungrecommend we get it in and let people beat on it18:04
*** belmoreira has joined #openstack-meeting18:04
morganfainberglets get the spec for that one in as well18:04
*** jamielennox has joined #openstack-meeting18:04
*** rossk has joined #openstack-meeting18:04
stevemarayoung, ++ I think thats the best course of action18:04
morganfainbergbut we'll hold that topic until later in the meeting (we have a whole section on it!)18:04
morganfainbergok moving on, we have a bunch to cover today18:05
morganfainberg#topic Hackathon Information18:05
*** openstack changes topic to "Hackathon Information (Meeting topic: keystone)"18:05
*** akuznetsov has joined #openstack-meeting18:05
morganfainberg#link http://dolphm.com/openstack-keystone-hackathon-for-juno18:05
henrynashfor mine, teh only changes I will push in later today are moving the ID creation from controller to manager (few real lines of code to change, just lots of tetsing mechanical changes)18:05
*** mrodden has joined #openstack-meeting18:05
henrynashsorry, topic has moved on18:05
morganfainberghenrynash, ah.18:05
morganfainberg#link https://docs.google.com/forms/d/1TlJ2u1ucxpia0SkWbkRo-_5DmVfXEQG7GKYVLc9abfc/viewform?usp=send_form18:05
morganfainbergi think everyone has filled out the form18:06
*** bobt has joined #openstack-meeting18:06
*** ildikov_ has quit IRC18:06
*** changbl has quit IRC18:06
morganfainbergno new info... just fill out the form if you haven't and you're going18:06
morganfainbergsee everyone in July in San Antonio18:06
stevemarshould be fun18:07
morganfainberghenrynash, we can talk about the differences in spec vs what is in the review shortly18:07
henrynashok18:07
morganfainberg#topic Spec Approval Requirements18:07
*** openstack changes topic to "Spec Approval Requirements (Meeting topic: keystone)"18:07
morganfainbergdolphm isn't here, so we don't get his view on it.18:07
*** emagana has quit IRC18:08
ayoungmorganfainberg, I'd say it needs to be  viewed by the team, with not major objections, and then at least two people go through a spec in depth18:08
*** jmontemayor has quit IRC18:08
ayoungso anyone on the team can  -2  if it is really wrong18:08
*** emagana has joined #openstack-meeting18:08
ayoungbut we need a way to say "I've looked at it and nothing scares me"18:08
ayoungwhich is why Iwas thinking "vote in the weekly meeting"18:09
morganfainbergayoung, a general thumbs up/thumbs down in the meeting and then a really in depth 2x+2 seems reasonable to me18:09
gyeedeal18:10
bknudsonlet's try it18:10
*** jmontemayor has joined #openstack-meeting18:10
morganfainbergwe should also corner dolphm later today for his input, but i think it lines up.18:10
dstaneksounds reasonable to me18:10
morganfainbergcool.18:10
morganfainbergno complaints?18:10
*** jmontemayor has quit IRC18:11
morganfainbergok now moving onto the bulk of the meeting, the thumbs up/thumbs down for specifications18:11
*** luis_ has quit IRC18:11
morganfainberg#topic Keystone Spec Approvals18:11
*** marekd has joined #openstack-meeting18:11
*** openstack changes topic to "Keystone Spec Approvals (Meeting topic: keystone)"18:11
morganfainbergayoung, o/ this is all yours18:11
*** mrunge has joined #openstack-meeting18:11
ayoungOK..hoqdo we do votes here...18:11
morganfainberglead us through it18:11
*** Michalik_ has quit IRC18:11
*** jmontemayor has joined #openstack-meeting18:12
morganfainbergstartvote i think.18:12
ayoungFirst one up is18:12
*** jmontemayor has quit IRC18:12
ayoungService Token Composite Authorization18:12
morganfainberg#link https://review.openstack.org/9631518:13
*** jmontemayor has joined #openstack-meeting18:13
ayoungThanks18:13
ayoung#startvote18:13
openstackOnly the meeting chair may start a vote.18:13
ayounghmmm18:13
gyeeheh18:13
morganfainbergbefore we vote, any questions on the topic?18:13
dstanekfail!18:13
bknudsonI haven't looked at it, but it looks doable to me.18:13
morganfainbergQuick intro: this is providing a service-token (e.g. glance service user) to the auth-token middleware18:13
bknudsonfrom scanning through it now18:13
morganfainbergthen policy can act upon either the x-auth-token or x-service-token18:14
gyeeno major objection here18:14
bknudsonI think we discussed this on irc18:14
morganfainbergbknudson, we did and at the summit18:14
ayoungmorganfainberg, what is policy.json going to look like for these?18:14
jamielennoxmorganfainberg: i haven't gone through the spec in detail but it looks like what i remember from summit18:14
jamielennox(so +1)18:14
morganfainbergayoung, TBD, but i think it will be %(service_user_id) or %(service_roles) vs %(role)18:15
dstanekwhat's the 'different manner'?18:15
*** mrunge has quit IRC18:15
ayoungmorganfainberg, since you are chair, I think you have to #startvote18:15
ayounghttp://ci.openstack.org/meetbot.html#voting18:15
morganfainbergayoung, yeah sec18:15
bknudsonhow about update the commit message to say it was discussed at meeting on 2014-06-10 and approved?18:16
morganfainberg#startvote Service Token Composite Authorization, do we like the general approach? Yes, no18:16
openstackBegin voting on: Service Token Composite Authorization, do we like the general approach? Valid vote options are Yes, no.18:16
openstackVote using '#vote OPTION'. Only your last vote counts.18:16
bknudson#vote Yes18:16
*** thinrichs has quit IRC18:16
gyee#vote hell yeah18:16
openstackgyee: hell yeah is not a valid option. Valid options are Yes, no.18:16
ayoung#vote Yes18:16
jamielennox#vote yes18:16
morganfainberg#vote yes18:16
henrynash#vote yes18:16
gyee#vote Yes18:16
stevemar#vote yes18:16
dstanek#vote yes18:17
morganfainbergbknudson, i like the idea link to the summary showing approval.18:17
*** coolsvap is now known as coolsvap|afk18:17
*** bdpayne has joined #openstack-meeting18:17
morganfainbergeveryone voted?18:17
stevemareveryone but dolphm18:17
*** rockyg has left #openstack-meeting18:17
morganfainbergo18:17
morganfainberg#endvote18:17
openstackVoted on "Service Token Composite Authorization, do we like the general approach?" Results are18:17
bknudsontoo late dolphm, already decided18:17
openstackYes (8): gyee, dstanek, ayoung, morganfainberg, bknudson, jamielennox, henrynash, stevemar18:17
ayoungOK next up18:18
jamielennoxi'll be interested to see how this one works in practice, i'm not sure how easy it'll be to craft policy that works with and without subject tokens18:18
ayoungtoken versions independent from API versions18:18
*** __afazekas is now known as afazekas18:18
morganfainberg#link https://review.openstack.org/9846418:18
morganfainbergthis might actually be better suited for K18:18
morganfainbergthis would be what leads to the id-only tokens18:19
ayoungSo...18:19
bknudsonwell, we're never going to change identity version again anyways18:19
ayoungdo we really want to do this just for Tokens?18:19
morganfainbergit basically amkes token versions independant of the API version18:19
morganfainbergbknudson, agree18:19
*** _nadya_ has joined #openstack-meeting18:19
stevemar98464 -> seems no one has reviewed it but lance18:19
morganfainbergayoung, what would be the other options? for all objects (e.g. users, domains, etc)?18:19
bknudson"microversioning"18:19
*** k4n0 has left #openstack-meeting18:19
ayoungI mean,  each of the various entities, or at least top level modules could benefit from this approach18:19
ayoungwhy token more than, say, user?18:19
ayounger identity18:20
morganfainbergayoung, i think because we have a real need for limiting token size.18:20
morganfainbergayoung, vs a nice-to-have18:20
jamielennoxmorganfainberg: this is being done as a querystring?18:20
morganfainbergayoung, would be my only (not so strong) argument18:20
morganfainbergjamielennox, that was the original idea18:20
morganfainbergdefault token version in config (or in the case of V2, the API controller)18:21
morganfainbergoverridable with a query string18:21
dstaneki haven't read the spec...does it was what will vary based on the version?18:21
ayoungaccepts header?18:21
jamielennoxmorganfainberg: i'm not sure that really makes sense, you would end up in a situation like /v3/auth/tokens?format=v218:22
bknudsony, let's figure out a way to do the microversioning18:22
bknudsonand let's not do it with a query parameter18:22
bknudsonuse accepts header18:22
ayoungOK,  I'm going to suggest we table this one until it gets more review18:22
morganfainbergbknudson, ++ ok lets table this one and move towards micro-versioning.18:22
ayoungnext up18:22
bknudsonsounds like don't plan to do it for J anyways18:22
*** eankutse has joined #openstack-meeting18:22
ayoungapi-validation blueprint18:22
morganfainberg#link https://review.openstack.org/9595718:23
bknudsonhmm, don't see ldbragst18:23
bknudsonlet me walk over18:23
ayoungWhile we are waiting18:23
ayoungplease don;t have the name of the spec review begin with "add spec..."18:23
*** rediskin has left #openstack-meeting18:23
ayoungIts like, duh18:23
ayoungor as they say here18:24
ayoungder18:24
*** manishg has joined #openstack-meeting18:24
bknudsonnot in. I guess we've got a meeting scheduled over this one18:24
bknudsonwell, I like the proposal18:25
morganfainbergdo we defer it then?18:25
morganfainbergcan vote anyway18:25
*** harlowja is now known as harlowja_away18:25
ayoung I'm still OK with this one.  I'd like to see bknudson 's comments addressed, but the general approach is strong18:25
bknudsonthis is one of the things on our security checklist for our products18:25
*** dims_ has quit IRC18:25
bknudsononly concern is breaking backwards compat18:25
morganfainberg#startvote api-validation specification. Yes, No18:25
openstackUnable to parse vote topic and options.18:25
*** caleb_ has quit IRC18:25
dstanekapproach is good...i'm curious to see what this looks like with a fully fleshed out implementation18:25
bknudson#vote Yes18:26
dstanek#vote yes18:26
ayoungtry that again morganfainberg18:26
marekd#vote yes18:26
morganfainberg#startvote Do we accept the proposal for api-validation? Yes, No18:26
openstackBegin voting on: Do we accept the proposal for api-validation? Valid vote options are Yes, No.18:26
openstackVote using '#vote OPTION'. Only your last vote counts.18:26
ayoung#vote yes18:26
marekd#vote yes18:26
bknudson#vote yes18:26
dstanek#vote yes18:26
morganfainberg#yote yes18:26
jamielennox#vote yes18:26
stevemar#vote yes18:26
*** gokrokve_ has quit IRC18:26
henrynash#vote yes18:26
morganfainberglooks like everyone18:27
stevemari was happy with this one a few iterations ago18:27
morganfainberg#endvote18:27
openstackVoted on "Do we accept the proposal for api-validation?" Results are18:27
openstackYes (7): dstanek, ayoung, bknudson, marekd, jamielennox, henrynash, stevemar18:27
gyeeI am not comfortable voting on this one as I haven't gone through the details18:27
*** eankutse has quit IRC18:27
morganfainberggyee, ah, sorry missed you18:27
* morganfainberg grumbles and learns to count18:27
bknudsonare we voting on the details or on the general approach?18:27
morganfainberggeneral approach18:27
ayoungnext up was Cross Backend Unique Identifiers for User and Group Entities but I don't see it18:27
ayoungdid it merge?18:27
bknudsonI don't like the ugly error message, but other than that think it's a good idea18:27
morganfainbergdetails are for the review18:27
bknudsonuniuque IDs merged18:27
bknudsonfirst spec!18:28
morganfainberghenrynash, any updates on the spec vs what is up for the review?18:28
morganfainbergbefore we move on?18:28
ayounggyee, OK...-1 the spec and up it to +1 or 2 when you are comforatable18:28
gyeeayoung, thanks, I'll definitely review it today18:29
henrynashmorganfainberg: no, the only differences from the version posted right now and the spec are listed in limiations18:29
morganfainbergok18:29
henrynashof the commit message18:29
ayoungcan we use bugs for spec bugs?18:29
*** eankutse has joined #openstack-meeting18:29
*** jecarey has quit IRC18:29
ayoungLike :spec for X says foo but should say bar.18:29
morganfainbergayoung, i'd just propose the change to the spec.18:29
ayoungmorganfainberg, fair enough18:29
*** safchain has quit IRC18:29
morganfainbergunless the spec is fully implemented, then bugs are probably the right approach18:29
ayoungnext up18:29
ayoungr V3 extension advertisement18:30
*** eankutse has quit IRC18:30
bknudsonhey!18:30
ayoung#link https://review.openstack.org/9597318:30
bknudsonany qs?18:30
morganfainberg#link https://review.openstack.org/9597318:30
*** eankutse has joined #openstack-meeting18:30
stevemar++++18:30
morganfainbergi'm happy with it as is.18:30
stevemarvery happy with it as is18:30
bknudsongot a request from dolphm to have the router intercept the GET / request18:30
gyeethis is a no-brainer18:30
bknudsonso that's the approach proposed18:30
*** gduan has joined #openstack-meeting18:30
morganfainbergbknudson, yeah that works.18:30
bknudsonrather than having the controller register18:30
ayoungbknudson, ":.. code-block:: javascript"18:30
*** jecarey has joined #openstack-meeting18:31
morganfainberg#startvote Accept V3 Extension Advertisement spec? yes, no18:31
openstackBegin voting on: Accept V3 Extension Advertisement spec? Valid vote options are yes, no.18:31
openstackVote using '#vote OPTION'. Only your last vote counts.18:31
jamielennoxbknudson: you don't intend to advertise these from GET / just /v3?18:31
bknudsonlike is done with admin & public18:31
ayoung#vote yes18:31
bknudsonjamielennox: right, just GET /v3.18:31
morganfainberg#vote yes18:31
henrynash#vote yes18:31
dstanek#vote yes18:31
gyee#vote yes18:31
stevemar#vote yes18:31
jamielennox#vote yes18:31
*** garyduan has quit IRC18:31
stevemarayoung, calling it javascript might just be a limitation of sphinx18:32
morganfainbergmarekd, you want to weigh in?18:32
marekdhaven't read it - don't wait :/18:32
bknudsonjamielennox: it would be tricky to have it work with GET / since the controllers don't get to see those.18:32
morganfainbergmarekd, ok18:32
morganfainberg#endvote18:32
openstackVoted on "Accept V3 Extension Advertisement spec?" Results are18:32
openstackyes (7): gyee, dstanek, ayoung, morganfainberg, jamielennox, henrynash, stevemar18:32
jamielennoxbknudson: there has been the assumption until now that the information provided at /v3 is a subset of what is provided at /, it means if i hit the version control at / i don't have to do /v318:32
ayoungWeb Authentication for SAML federated Keystone18:32
morganfainberg#link https://review.openstack.org/9686718:32
*** ildikov has joined #openstack-meeting18:33
marekdppl have some concerns here...18:33
stevemarlots of questions on this one still18:33
bknudsonjamielennox: maybe there's a way to do it that I haven't thought of18:33
marekdstevemar: ++18:33
ayoungThis one I would say is not quite full baked yet18:33
*** jecarey_ has joined #openstack-meeting18:33
*** jgrimm has joined #openstack-meeting18:33
morganfainbergshould we table this one then?18:33
jamielennoxbknudson: i'm not saying the assumption is correct but its going to be a bit of a pain to do both18:33
*** egallen has joined #openstack-meeting18:33
*** beagles has quit IRC18:33
ayoung Its on the right track, but I think it might actually require some input from Horizon folks18:33
morganfainbergayoung, after this mind commenting on the specs that we table saying as much?18:33
ayoung++18:34
stevemaryeah, so far no input from any horizon folks18:34
morganfainbergreasonable to ask horizon to weigh in on this18:34
*** emagana has quit IRC18:34
marekdand what about addind a 'static webpage' tied directly to Keystone?18:34
ayoungTable?18:34
morganfainberg#action ayoung to comment on tabled specification reviews (why and what was decided)18:34
ayoungNext up non-persistent-tokens18:34
*** kgriffs is now known as kgriffs|afk18:35
morganfainberg#link https://review.openstack.org/9597618:35
jamielennoxtable, at the very least it should be an extension18:35
*** nati_ueno has joined #openstack-meeting18:35
bknudsonI looked over this one and no real issues with it. Could use more details but I think it's workable18:35
morganfainbergjamielennox, ++18:35
ayoungbknudson, I assume your comments are detail oriented, not show stoppers?18:35
ayoungany of them worth noting?18:35
bknudsonthere was a question about whether it's discoverable or not18:36
morganfainberga lot of the work on this one is scaffolding so we can make the token presistence redundant18:36
ayoungbknudson, I would say "no"18:36
bknudsonalso it might be a good idea to split out the token object from persistent tokens18:36
ayoungat least, I see no reason to make it discoverabl18:36
morganfainbergbknudson, that is the data model bit.18:36
ayoungthe keystone server can validate using PKI18:36
*** fnaval has joined #openstack-meeting18:36
morganfainbergbknudson, it should be more explicit then.18:36
*** emagana has joined #openstack-meeting18:37
morganfainbergany questions on the persistence of tokens spec?18:37
*** jecarey has quit IRC18:37
morganfainbergerm non-persistence?18:37
ayoungNote that this depends on widespread consumtion of revocation evetns18:37
ayoungevents18:37
*** giustoXricordarv has quit IRC18:37
*** beagles has joined #openstack-meeting18:37
ayoungwhich is still WIP18:37
ayoungbut I don't think there is any question to the validity of the approach18:38
bknudsonis there a spec for remaining revocation events work?18:38
ayoungbknudson, let me check18:38
gyeemorganfainberg, you may want the security folks to chime in on that one18:38
*** giustoXricordarv has joined #openstack-meeting18:38
ayoungnot a new spec, but an old BP I think18:38
*** mdml has quit IRC18:38
morganfainberggyee, ++ i'll add securityimpact18:38
bknudsonok, I thought at this point we require specs.18:38
morganfainbergbknudson, we do18:39
ayounghttps://blueprints.launchpad.net/python-keystoneclient/+spec/revocation-event-api18:39
dstaneki haven't thought about this one enough to vote on it18:39
ayoungbut that does not indicate Auth Token middleware...I'll work up a spec for the Auth Token work.18:39
*** ArthurBerezin has joined #openstack-meeting18:39
morganfainbergok18:39
morganfainbergwell lets quick vote, i'll add a 3rd option going forward, table18:39
morganfainberg#startvote Accept Non-Persistence of tokens Spec? Yes, No, Table18:40
openstackBegin voting on: Accept Non-Persistence of tokens Spec? Valid vote options are Yes, No, Table.18:40
openstackVote using '#vote OPTION'. Only your last vote counts.18:40
bknudson#vote table18:40
ayoung#vote yes18:40
dstanek#vote table18:40
* morganfainberg abstains.18:40
gyee#vote table18:40
jamielennox#vote i love the approach but i think it's too soon18:40
openstackjamielennox: i love the approach but i think it's too soon is not a valid option. Valid options are Yes, No, Table.18:40
jamielennox:(18:40
jamielennox#vote table18:40
marekd#vote table18:41
henrynash#vote yes18:41
ayoungAre we really not happy with the spec?18:41
*** ArthurBerezin has left #openstack-meeting18:41
ayoungIt has dependencies, but the approach is right18:41
morganfainbergayoung, i think we need the revocations evtents spec18:41
morganfainbergbefore we can accept this one18:41
ayoungwhy?18:41
gyeeayoung, I am not sure if we fully flush out the implications yet18:41
morganfainbergw/o the dependencies, we can't implement this completely18:41
*** gduan has quit IRC18:41
*** garyduan has joined #openstack-meeting18:42
ayoungWe need Auth token middleware to accept them, but the logic cor that is well established18:42
ayoungcor -> for18:42
ayoungthe API spec is up for review18:42
ayoungand the events are part of the server18:42
jamielennoxalso morganfainberg is lining up a lot of work for himself18:42
ayoungso, no, I don't think we *need* it, but it can't hurt to have it laid out18:42
morganfainbergayoung, sure, i think if that spec was accepted then this one could be. lets revisit next week if its an issue i'll gut the persistence part and make it only the scaffolding work.18:42
ayoung++18:43
morganfainberg#endvote18:43
openstackVoted on "Accept Non-Persistence of tokens Spec?" Results are18:43
openstackTable (5): bknudson, dstanek, gyee, marekd, jamielennox18:43
openstackYes (2): henrynash, ayoung18:43
*** igordcard has joined #openstack-meeting18:43
*** Mandell has quit IRC18:43
ayoung audit support for federation18:43
morganfainbergtabled till next week, might require reduction in scope for J18:43
morganfainberg#link https://review.openstack.org/9758118:43
bknudsonhave not looked at this one18:43
stevemarit's got a few issues with it18:43
morganfainbergi think this one is fairly straightforward18:44
*** nedbat has quit IRC18:44
morganfainbergbut the issues are all in details not approach18:44
stevemari think i might upload a new version soon if topol doesn't get around to it18:44
gyeeyeah, this one seem like a no-brainer18:44
*** nedbat has joined #openstack-meeting18:44
bknudsonI assume it's using and extending the current auditing18:44
morganfainbergbknudson, yes18:44
stevemarbknudson, yep18:44
bknudsonrather than starting something new18:44
ayoungI would like to see some sort of test listener18:44
*** ilyashak_ has joined #openstack-meeting18:44
morganfainbergbknudson, jsut expanding to federation work.18:44
*** jprovazn has joined #openstack-meeting18:44
ayoungsomething that a Keystone admin could run to confirm that the events are being emitted18:44
stevemaras it stands only events that call auth controller are logged18:45
morganfainbergi think we can vote on this one, remember the vote is general approach18:45
bknudsonwe've got a request to enable notifications by default18:45
*** ilyashak_ has quit IRC18:45
stevemarsomething that seems worth doing18:45
ayoungAnd the red blocks from whitespace burn my eyes18:45
morganfainbergbknudson, right.18:45
stevemarayoung, i'll upload a new version today :)18:45
morganfainberg#startvote Audit Notifications for Federation? Yes, No, Table18:45
openstackBegin voting on: Audit Notifications for Federation? Valid vote options are Yes, No, Table.18:45
dstanekI don't see a lot of info in the proposed changes section18:45
openstackVote using '#vote OPTION'. Only your last vote counts.18:45
bknudson#vote yes18:45
*** ilyashak_ has joined #openstack-meeting18:45
stevemar#vote yes18:45
morganfainberg#vote yes18:45
ayoung#vote yes18:45
marekd#vote yes18:45
gyee#vote yes18:45
henrynash#vote table18:45
*** nedbat_ has joined #openstack-meeting18:46
*** ilyashak_ has quit IRC18:46
*** thedodd has joined #openstack-meeting18:46
morganfainbergdstanek, i think it's a small amount of changes18:46
*** gokrokve has joined #openstack-meeting18:46
henrynash#vote yes18:46
morganfainbergdstanek, it's really about adding a decorator i think.18:46
*** nedbat_ has quit IRC18:46
dstanek#vote no - i have no idea what's actually changing :-(18:46
openstackdstanek: no - i have no idea what's actually changing :-( is not a valid option. Valid options are Yes, No, Table.18:46
dstanek#vote table18:46
*** nedbat_ has joined #openstack-meeting18:46
morganfainbergdstanek, try again :P18:46
morganfainberganyone want to switch to table?18:47
jamielennox#vote yes18:47
dstaneki'd love to know more before voting18:47
morganfainberggoing in 318:47
morganfainberg#endvote18:47
openstackVoted on "Audit Notifications for Federation?" Results are18:47
openstackTable (1): dstanek18:47
openstackYes (8): gyee, ayoung, morganfainberg, bknudson, marekd, jamielennox, henrynash, stevemar18:47
gyeedstanek, no peer pressure here :)18:47
jamielennoxdstanek: but i agree, given that i know we want to do auditing i don't learn much from the spec18:47
morganfainbergi think this yes is contigent on using the same notifiers as we currently use18:47
ayoungdstanek, -1 the review and comment on what you want to see, please18:47
bknudsonhenrynash voted for all 318:47
dstanekayoung: of course18:47
henrynashbknudson: well, I dint vote no18:48
morganfainbergok, next up?18:48
ayoungNext up JSON Home18:48
*** annegentle_ has quit IRC18:48
ayoung#link https://review.openstack.org/#/c/97359/18:48
bknudsonif the spec turns out to be a disaster hopefully the Yes vote here isn't binding18:48
morganfainbergi'll be honest i haven't looked at it18:48
morganfainbergbknudson, nah yes isn't binding18:48
bknudsonbtw, I just wrote this up because it's interesting18:48
*** pelix has quit IRC18:48
ayoungbknudson, Yes means "I have no serious objections"18:48
*** sushils_ has joined #openstack-meeting18:48
*** erecio has quit IRC18:48
bknudsonwasn't planning to even work on it unless I had some time.18:49
*** rellerreller has joined #openstack-meeting18:49
*** Mandell has joined #openstack-meeting18:49
*** erecio has joined #openstack-meeting18:49
bknudsonalso, someone might say do this rather than the v3 extension advertisement18:49
*** rellerreller has left #openstack-meeting18:49
morganfainberg#startvote JSON Home Spec? Yes, No, Table18:49
openstackBegin voting on: JSON Home Spec? Valid vote options are Yes, No, Table.18:49
ayoungOooh18:49
openstackVote using '#vote OPTION'. Only your last vote counts.18:49
dstaneki think this is great18:49
dstanek#vote yes18:49
*** nedbat has quit IRC18:49
*** balajiiyer has joined #openstack-meeting18:49
* morganfainberg has to abstain because i haven't read it in depth18:49
morganfainbergor at all18:49
gyeeso JSON home will eventually deprecate the current scheme?18:50
ayoungmorganfainberg, then vote table18:50
morganfainberg#vote table18:50
jamielennoxbknudson: did you find any libraries that could deal with jsonhome?18:50
bknudsongyee: there is really no current scheme18:50
bknudsonjamielennox: I didn't look for a library18:50
gyeebknudson, current version discovery I mean18:50
bknudsongyee: right, it would cover current version discovery18:51
jamielennoxbknudson: it's not all that well defined but there is definetly a current scheme and it's at least similar across most openstack services18:51
bknudsonso hopefully we'd deprecate the current way18:51
ayoung#vote table18:51
*** SridharG has quit IRC18:51
ayoungLets get the library and some more eyes on this before we say OK18:51
*** akuznetsov has quit IRC18:51
jamielennox#vote table18:51
bknudsonjamielennox: there was a project that was using it... marconi maybe18:51
*** yingjun has joined #openstack-meeting18:52
henrynash#vote yes18:52
jamielennoxbknudson: yea, marconi was what i was thinking - but honestly i think if i was TC an incubation requirement would be to use a similar format to everyone else18:52
*** hashar has joined #openstack-meeting18:52
gyeebknudson, did we discuss this at one of the cross-project sessions?18:52
jamielennox(whatever that is)18:52
bknudsonthey'll both work18:52
bknudsongyee: I don't think it was discussed, there's been some mailing list discussion18:52
gyee#vote yes18:53
gyeeanything for consistency18:53
morganfainberganyone else?18:53
gyeenext up, pagination!18:53
morganfainbergin 318:53
*** akuznetsov has joined #openstack-meeting18:53
morganfainberg#endvote18:53
openstackVoted on "JSON Home Spec?" Results are18:53
openstackTable (3): ayoung, morganfainberg, jamielennox18:53
openstackYes (3): henrynash, gyee, dstanek18:53
bknudsona tie!18:53
morganfainbergEven keel18:53
dstaneki'm getting better at this voting thing18:54
morganfainbergdstanek, hehe18:54
*** Mandell has quit IRC18:54
*** olaph has joined #openstack-meeting18:54
morganfainberglets look into a library, with a library i'm a yes18:54
ayoungLets try to revisit this one next week.18:54
morganfainbergayoung, ++18:54
ayoungNext up Session tokens18:54
ayoungOIK...little bit of background18:54
*** giustoXricordarv has quit IRC18:54
ayoungHorizon does unspeakable things with tokens18:54
ayoungwell, everyone does, byut horizon particularly18:55
ayoungHorizon really needs sessions, not tokens, to maintain a cache of the userid and password18:55
ayoungif we do a session, the rules would be different than they are for tokens:18:55
bknudsonhorizon must have sessions18:55
bknudsonit's part of django18:55
ayoungbknudson, yeah, but not in its connection with Keystone18:55
ayoungso18:55
morganfainbergbknudson, right now they use the keystone token (effectively) as the session18:55
ayoungHorizon doesn't hold on to password18:56
morganfainbergbknudson, and store that in ... the session object18:56
ayoungit uses a keystone token, and passes one scoped token to keystone to get another scoped differently18:56
ayoungthis is kida wrong18:56
*** markmcclain has quit IRC18:56
ayoungleast privilege says "got from unscoped to scoped only"18:56
*** Michalik_ has joined #openstack-meeting18:56
ayoungbut also, if we shorted the token lifespan any shorter, we are going to be kicking people out of horizon even when they are actively using it18:57
jamielennox#link https://review.openstack.org/#/c/96648/18:57
ayounga session should last about 10 minutes18:57
morganfainberg(configurable)18:57
morganfainbergand can be extended18:57
ayoungyes18:57
*** yingjun has quit IRC18:57
*** nati_ueno has quit IRC18:57
ayoungif the user actively contacts the server, the session shsoulkd be extended18:57
bknudsonI don't see how a session token is going to work with pki... the doc has the expiration time18:57
morganfainberg2 minutes.18:58
ayoungbknudson, it has to be done via keystone18:58
*** e0ne has joined #openstack-meeting18:58
ayounghandthe old session back, get a new one, or some comparable mechanism18:58
dstanekwhat can you do with a session token? just exchange it for a scoped token?18:58
bknudsonit's only unscoped?18:58
*** yogeshmehra has quit IRC18:58
ayoungcorrect18:58
ayoungto both of you18:58
morganfainberg#startvote Session Tokens Spec? yes, no, table18:58
openstackBegin voting on: Session Tokens Spec? Valid vote options are yes, no, table.18:58
openstackVote using '#vote OPTION'. Only your last vote counts.18:58
morganfainbergkeep talking just gettnig the vote going.18:59
*** marun is now known as marun_afk18:59
morganfainbergpersonally, i like the idea and would love to see it18:59
*** gduan has joined #openstack-meeting18:59
morganfainbergand the general principle is sound18:59
morganfainbergimo18:59
morganfainberg#vote yes18:59
* ayoung abstains18:59
gyee#vote table18:59
bknudson#vote table19:00
*** garyduan has quit IRC19:00
bknudsonHaven't looked at it.19:00
bknudsonalso, we're out of time19:00
morganfainbergwe're at the end, feel free to table and we can circle back19:00
gyeelike non-persistence one, we need more in-depth study on the impact as it fundamentally changed how Horizon operates19:00
*** colinmcnamara has quit IRC19:00
ayoungclose out the vote before we close the meeting, please19:00
morganfainbergok lets circle back on this one.19:00
jamielennoxi want more information19:00
morganfainberg#endvote19:00
openstackVoted on "Session Tokens Spec?" Results are19:00
openstacktable (2): gyee, bknudson19:00
openstackyes (1): morganfainberg19:00
morganfainberg#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Jun 10 19:00:56 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-10-18.01.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-06-10-18.01.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-06-10-18.01.log.html19:01
fungiinfra team assemble!19:01
fungipinging (for listed agenda items) mordred reed rdopiera ianw anteaya19:01
reedo/19:01
*** lcostantino has joined #openstack-meeting19:01
*** Macaveli has joined #openstack-meeting19:01
*** jamielennox has left #openstack-meeting19:01
*** luis_ has joined #openstack-meeting19:01
krotschecko/19:01
ianwo/ (but the agenda item is from last week)19:01
*** bobt has quit IRC19:01
pleia2o/19:01
fungiianw: okay, i can skip that if you have no updates19:01
anteayao/19:02
clarkbo/19:02
reedgotta kill firefox every day at least once... something's off19:02
zaroo/19:02
ianwfungi: nothing for the meeting, thanks19:02
fungiSergeyLukjanov: around?19:02
SergeyLukjanovyup19:02
mordredo/19:02
*** bknudson has quit IRC19:02
SergeyLukjanovo/19:02
fungii think we have quorum19:02
fungi#startmeeting infra19:02
openstackMeeting started Tue Jun 10 19:02:40 2014 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
jesusauruso/19:02
SergeyLukjanovfungi, ++19:02
*** pcrews_ has joined #openstack-meeting19:02
SergeyLukjanovand I think I have a big latency ;)19:03
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:03
fungi#topic Actions from last meeting19:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:03
*** harlowja_away is now known as harlowja19:03
*** garyduan has joined #openstack-meeting19:03
anteayaI like the quick topics19:03
fungi#link http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-06-03-19.02.html19:03
*** gduan has quit IRC19:03
fungithere were none19:03
fungi(that was quick)19:03
anteaya:D19:04
*** thedodd has quit IRC19:04
*** mugsie has joined #openstack-meeting19:04
fungi#topic Manage-projects status (fungi, mordred)19:04
*** openstack changes topic to "Manage-projects status (fungi, mordred) (Meeting topic: infra)"19:04
fungimordred fixed a new bug today19:04
mordredfungi: I pushed a patch to fix the current issue19:04
fungi#link https://review.openstack.org/9913619:04
mordredit was a fun one19:04
mordredeveryone should marvel at its wonder19:04
fungii haven't gone back to see if the recently added projects are updated yet19:04
clarkbhuh how did that sneak in19:05
*** Mandell has joined #openstack-meeting19:05
mordredclarkb: it came in during the exception error cleanup19:05
clarkbah19:05
*** thedodd has joined #openstack-meeting19:05
mordredand it's one of those places where the backwards logic makes your head spin19:05
* anteaya marvels19:05
clarkbmordred: go bourne?19:05
mordredclarkb: :)19:06
fungialso there's still an open review to add some extra race safety around acl creation... no idea if it's actually needed any longer19:06
fungi#link https://review.openstack.org/9468419:06
fungianything else to cover on this before i move to the next topic?19:06
*** luis_ has quit IRC19:07
clarkbfungi: I think we can be defensive and mrege that change19:07
fungi#topic Review proposal to move Activity Board fully under openstack-infra (reed)19:07
*** openstack changes topic to "Review proposal to move Activity Board fully under openstack-infra (reed) (Meeting topic: infra)"19:07
clarkbI will rereview19:07
*** sarob has quit IRC19:07
fungithx19:07
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2014-June/001292.html19:07
*** emaganap has joined #openstack-meeting19:07
*** aburaschi has joined #openstack-meeting19:08
fungireed: apologies for not following up yet. it's been a crazy week. i think mordred replied a couple times on that thread though19:08
*** jang has joined #openstack-meeting19:08
mordredI have. I think we're making progress in the thread19:08
reed#info the gist of it is that we're going to need assistance in order to achieve that. Bitergia is not self-sufficient and being an external provider it may become quite expensive.19:08
mordredI think we can make the puppet without problems, I read through their docs19:08
mordredbut I think we may need slightly more detailed install instructions from them19:08
*** rdopieralski has joined #openstack-meeting19:09
rdopieralskihi19:09
reedmordred: i think so too, the basic install shouldn't be too complicated19:09
mordredthe stackalytics install instructions I referenced are a great example of about the level of detail we need19:09
reedI'll have them provide those19:09
fungirdopieralski: welcome... you haven't missed your topic yet, so just hang in there19:09
*** nati_ueno has joined #openstack-meeting19:09
mordredreed: it took me about an hour to puppet stackalytics, so I dont' think it'll take long to do activity board19:09
rdopieralskifungi: thank you19:10
*** erecio has quit IRC19:10
reedthere are other 'puppetification' jobs we need to do, too, askbot for example19:10
clarkbmordred: cool19:10
*** dims_ has joined #openstack-meeting19:10
clarkbreed: ugh19:10
*** emagana has quit IRC19:10
clarkbreed: as long as I don't have to do it <_<19:10
mordredclarkb: askbot might not be as bad anymore since we've got postgres in puppet at this point19:10
mordredalthough it woudl be eversonice if it would run on mysql so we could use rax cloud dbs19:10
*** erecio has joined #openstack-meeting19:11
reedclarkb, and this time we have the head developer on board :)19:11
clarkbI mean yes we could just postgres it19:11
mordred++19:11
reedEvgeny agreed that it would be a good idea to do it19:11
mordredlet's get activity done first19:11
clarkb++19:11
*** marcoemorais has quit IRC19:11
*** marcoemorais has joined #openstack-meeting19:11
reedyes, I agree, activity first because it's 1) easier and 2) askbot requires a bit more thoughts on a more resilient architecture, too19:12
fungimordred: i'm still a little twitchy about rackspace's trove service since it's query socket is accessible from all tenants in the same region... we might want to hold off putting more stuff in it until we get a better comfort level for that19:12
*** marcoemorais has quit IRC19:12
*** marcoemorais has joined #openstack-meeting19:12
*** emagana has joined #openstack-meeting19:12
mordredfungi: we can get iccha1 to fix that now!19:13
reed#task reed to ask Bitergia to provide detailed instructions to run the grimoire suite19:13
fungi(though it sounds like neutron is needed to be able to address it)19:13
*** Michalik_ has quit IRC19:13
mordredfungi: several things are needed I believe, but yeah19:13
reednext topic?19:13
mordredfungi: we could always move to just running our own galera cluster in which all of our dbs lay with ssl cert-based auth ...19:14
* mordred shuts up19:14
fungi#topic Review proposal towards a better integration of gerrit and openstack people db (reed)19:14
*** openstack changes topic to "Review proposal towards a better integration of gerrit and openstack people db (reed) (Meeting topic: infra)"19:14
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2014-June/001297.html19:14
fungianother awesome e-mail i'm sorry i haven't replied to yet. it's flagged for attention still :/19:14
reedso, this one is detailed in a blog post by me, etherpad and blueprint19:14
reedno problem19:14
reedthe TL;DR version:19:15
reedwe're going to build a directory of people involved in openstack19:15
*** emaganap has quit IRC19:15
*** yogeshmehra has joined #openstack-meeting19:15
reedbuilt on top of the current 'members' database, and exposing OpenID services19:16
morganfainbergyeah.19:16
anteayaplease no pictures19:16
morganfainbergthat was a topic from the summit19:16
reedthe database will not be of Foundation members19:16
morganfainbergthis is the replacement for LP SSO right?19:16
*** balajiiyer has left #openstack-meeting19:16
reednot only, at least, multiple roles are envisioned19:16
fungimorganfainberg: right, and more19:16
morganfainbergwell one of the roles.19:16
reedmorganfainberg, yes, also19:16
morganfainbergyep19:16
morganfainbergas i said at the summit, count me on this front. ahppy to help19:17
mordredwoot19:17
clarkbone concern on my end is we need to make sure doing something other than openid is feasible19:17
reedRight now we have members==developers, speakers, voters to talks and a few other smaller roles19:17
*** _nadya_ has quit IRC19:17
anteayaclarkb: ++19:17
morganfainbergunfortunately ubuntu running freeipa (longer view) wont... really occur, though fedora if could [again if we wanted to move away from the peopledb info]19:17
reedclarkb, why? until now I have insisted on openid because my understanding is that gerrit won't do anything but openid19:18
morganfainbergs/if/it19:18
anteayasince gerrit is changing its auth strategy19:18
morganfainbergclarkb, what auth strategies do we need?19:18
clarkbreed: gerrit is potentialyl removing openid19:18
mordredreed: gerrit will also do ldap - and yes, upstream gerrit is starting to want to make openid go away19:18
* reed yells at the cloud19:18
clarkbmordred and zaro have pinged them and it looks like we may get an openid plugin19:18
mordredmorganfainberg: I thought freeipa on ubuntu was coming?19:18
clarkbbut I wasn't super convinced given spearce's stance19:18
mordredclarkb: awesome19:18
morganfainbergok LDAP is easy19:18
morganfainbergmordred, it's... slow19:18
reedldap is crap19:19
morganfainbergmordred, i'm still trying to lean on people to get resources19:19
*** Michalik_ has joined #openstack-meeting19:19
clarkbI think starting with openid is great19:19
mordredreed: well, let's not go to the "is crap" place just yet19:19
clarkbwe have openid today and will have it tomorrow19:19
mordredclarkb: ++19:19
morganfainbergmordred, but it's hard to get commitment on it.19:19
reedanyway, this is largely independent from the crap we have to deal with :)19:19
clarkbjust keep in mind that openid may not be the only thing we need to do19:19
mordredreed: yes19:19
*** Michalik_ has quit IRC19:19
fungigerrit will actually do other things besides openid now and has for a while (for example ldap)19:19
morganfainbergmordred, it might be if we do FreeIPA we run fedora for those boxen until ubutnu is stable+happy19:19
reedcurrently the OpenID service is just a php app built on top of a couple of database tables19:19
morganfainbergit's coming, just might be longer than this dev cycle19:20
mordredI think clarkb's point is excellent - in making the db, we should keep in mind we might want to put more than one access method on top of it19:20
*** Michalik_ has joined #openstack-meeting19:20
mordredmorganfainberg: well ... our biggest problem is the fedora lifecycle - but we can come back to that19:20
fungibut yes, i agree that openid is a good initial target and then we just need to make sure it's not designed to make it harder than necessary to hook in other protocols later as needed19:20
reednow, the reason for this topic in the agenda is that I'd like to make sure that we design the tables and the database to keep into account all of the things that gerrit needs19:20
morganfainbergreed, there was some desire to not use the people db info directly, some data that shouldn't be used?19:20
morganfainbergi think i remember19:20
*** VijayB_ has quit IRC19:21
reedmorganfainberg, not sure I follow... do you remember something more?19:21
mordredreed, morganfainberg: I believe they were talking about wanting to be able to split the db into people db and then also some of the info that the foundation might need that the project might not want access to19:21
morganfainbergreed, there was extra data in the people db there was concern about exposing19:21
mordredthat ^^19:21
reedright ...19:21
reedthe DB itself won't be publicly available, ever, there are personal data in there that we're not allowed to share19:21
mordredbecause ultimately we want to be able to operate the people db in infra, but we don't want to have secrets in there that it would be inappropriate for infra to be privy to19:22
morganfainbergmordred, ++19:22
fungiyeah, separation of concerns... not just dumping it all together19:22
*** amotoki has quit IRC19:22
reedright now running the people DB in infra is not an option19:22
fungiagreed19:22
morganfainbergit might make sense to separate concerns and sync the important infra-safe info to the new db somehow?19:22
morganfainbergto begin with.19:22
morganfainbergor is that biting off too much/boiling the ocean19:22
*** VijayB has joined #openstack-meeting19:23
reedmorganfainberg, boiling :)19:23
fungifrom what i understand more refactoring of the current database is needed to separate out authentication and basic account info from foundation membership stuff19:23
*** gyee has quit IRC19:23
reedfungi, exactly19:23
morganfainbergreed, fair enough. lets use what we have and then work on a split.19:23
*** VijayB has quit IRC19:23
*** vivek-ebay has quit IRC19:24
fungithe idea i think is that we get a toehold by running the openid service connecting to the current database with some constraints on the db server end and then try to get a new authentication/accounts db separate from it running in parallel19:24
reednew database will need to have all the details for gerrit to authorize commits, and contain also status about each person: is that person a developer? a speaker? something else?19:24
fungithe migration could be piecemeal if we do it carefully19:24
morganfainbergfungi, ++19:24
morganfainbergreed, i'd like to circle back on that and see about something like FreeIPA (if possible) when we split vs. just-another-SQL-back-end19:24
reedthis is also an attempt at simplyfing *a lot* the onboarding of new developers19:24
clarkbis the intent to keep the existing HTTP request to db get back 200 for signed CLA?19:25
clarkber keep that process?19:25
clarkbin that case gerrit doesn't need to know anything really19:25
fungiclarkb: i think we should be able to replace that19:25
clarkbfungi: how?19:25
reedclarkb, not if we can make it better19:25
clarkbI think I am missing that important piece19:25
* mordred is too19:25
mordredfungi: can you splain?19:25
clarkbif we do have this magical pony19:25
clarkbhow do we interact with it? because that will help determine the size and shape of this thing19:26
mordred++19:26
fungiclarkb: leave the cla signing in but drop the contactstore connection. instead the openid data should be sufficient to (hopefully) marry to group membership api calls now that those exist and now that all clas in current gerrit are group-based not tracked in separate tables19:26
reedwe want to get to a place where openstackid.org shows profile pages for each person involved in openstack19:26
*** kristysiu has quit IRC19:26
*** afazekas has quit IRC19:26
mordredfungi: you're suggesting that the openid thing simply doesn't auth if the person doesn't have the CLA?19:27
reedperson creates an account, goes to groups.openstack.org, checks things there...19:27
*** sarob has joined #openstack-meeting19:27
fungimordred: no, not at all suggesting that19:27
reedmaybe later signs the CLA, commits code, maybe later becomes a member of the foundation, a speaker... etc19:27
reedall with one identity managed by us19:27
*** sweston has joined #openstack-meeting19:27
clarkbfungi: so we would be going back to syncing against an openid service?19:28
morganfainbergreed, so o.o properties would be SSO to this system19:28
mordredok. I get all that. I have two questions that I would like asnwered19:28
fungimordred: suggesting that the reason we did the contactstore thing was twofold... to make sure the contributor was a foundation member first and to track the correlation to their gerrit account (the latter of which was never done entirely properly anyway)19:28
clarkbfungi: just with API calls isntead of direct DB manipulation?19:28
*** ramishra has quit IRC19:28
fungibut for anyone to sign the cla in gerrit, they have to log into gerrit, which now means they have an openid account in our openid provider19:28
reedmorganfainberg, SSO would be cool but until now, all the design choices depend on what gerrit provides... openid I was told and openid I had implemented19:28
morganfainbergreed, sure.19:28
mordredfungi: ah. ok19:28
fungiclarkb: syncing? not needed this way as far as i know19:29
clarkbfungi: I see so we would purely rely on the data provided by openid19:29
mordredfungi: so how does the foundation get information that a user has signed the CLA?19:29
reedmordred: right nkow the foundation doesn't know that19:29
fungigerrit handles cla signing and enforcement. it auto-adds users to per-cla gerrit groups now. there is also an api call to enumerate group members in gerrit19:29
mordredok19:29
clarkbso we would sync the other direction and that is where the APIs come into play19:30
*** sweston has quit IRC19:30
fungiyep19:30
reedmordred: in fact, the foundation needs to query gerrit directly to find the list of ATCs19:30
*** novas0x2a|laptop has joined #openstack-meeting19:30
mordredseems fine to me19:30
fungithe foundation can, when and as often as it wants, query gerrit to find out who's signed the cla19:30
mordredI like it19:30
clarkbya I think that should work fine19:30
fungivia a rest api now even19:30
*** Sukhdev has joined #openstack-meeting19:31
fungiso between having openid authentication info and the cla lookups, the foundation can correlate whatever they need19:31
mordred++19:31
fungiwhere gerrit is concerned19:31
*** amcrn has joined #openstack-meeting19:31
clarkbso the data would be whatever gerrit thinks it should know about at https://review.openstack.org/#/settings/ and https://review.openstack.org/#/settings/contact19:32
anteayamuch better relationship19:32
reedindeed, instead of counting on email lookups that sometimes fail with obscure error messages19:32
fungiclarkb: so the outstanding question which someone hopefully finds time to look into soon is how much gerrit will import from openid. i know it does e-mail address and username...19:33
*** pdmars_ has joined #openstack-meeting19:33
fungii suspect it does not do group membership updates from openid, but hopefully we don't need that19:33
reedthe process to onboard a new developer will be extremely linear, no back and forth between 3 accounts19:33
mordredgroup memberships is an openid extension19:33
reedfungi, gerrit may not need to know about that...19:34
mordredgerrit does not consume it - launchpad provided it but we had to do that db sync script hell to get group info19:34
fungiyeah, and one i'm assuming gerrit doesn't make use of19:34
*** malini2 has quit IRC19:34
clarkbwhich should be fine19:34
morganfainbergsounds like a question for zaro19:34
fungiright, that 'splains why we didn't make use of it for gerrit19:34
reedare you talking about groups as in 'programs'?19:34
fungireed: agreed19:34
morganfainbergbut, i don't think gerrit does consume that19:34
clarkbit keeps gerrit group membership in gerrit rather than cores needing to use $thingoverthere to manage the groups19:34
mordredyup19:34
*** jtomasek has joined #openstack-meeting19:34
fungireed: no, meaning if we wanted to control things like acls via group membership managed from the openid end rather than directly in gerrit, but probably not necessary or even desirable anyway19:35
reedlet's be clear: when I talk about 'groups' in the openid (let's call it this way at the moment) is more similar to 'affiliation'19:35
*** ramashri has quit IRC19:35
mordredlike, "Monty works for HP"19:35
clarkbya I don't think it is desireable19:35
mordrednot "Monty is Infra Cre"19:35
fungiright, so not a concern19:35
mordreds/re/ore/19:35
mordred++19:35
*** pdmars has quit IRC19:35
zaromorganfainberg: sorry i don't know, would need to dig.19:36
mordredit will be data that things like stackalytics and activity board could mine19:36
*** dshurtle has quit IRC19:36
reedmordred: right, we want to have the manager of a team specify who works for him/her on the 'People Directory'19:36
* reed notes that this thing needs a name19:36
morganfainbergzaro, no worries. sounds like it's a non-issue19:36
*** jmontemayor has quit IRC19:36
anteayareally?19:36
anteayawe want work organization trees?19:36
anteayaor openstack organization trees?19:36
fungianteaya: for tracking the corporate cla19:36
anteayaoh19:36
reedanteaya, yes, for a couple of reasons19:36
mordredreed: biggest thing I think we need there so that the reporting thigns can do the right thing...19:37
reedCCLA is one, reporting is another19:37
fungibut also for member company contribution metrics in aggregate19:37
mordredreed: is making sure we're keeping data-warehouse style data ranges for affiliations19:37
reedmordred: next step will be to have an API service on top of this database19:37
anteayak19:37
reedan API that stackalytics, git-dm, bitergia and the world can query19:38
reedwe'll have to sit down and design that19:38
morganfainbergreed, so, the READ part of CRUD19:38
anteayaI like that someone can change call signs and it makes no nevermind to the rest of us19:38
*** nealph has quit IRC19:38
reedmorganfainberg, indeed19:39
reedso, how do we proceed?19:39
fungianteaya: yes, but large companies donating funds and people to the effort want to be able to show the "money people" what they're accomplishing with that19:39
reedthe blueprint and spec need feedback19:39
anteayafungi: true, they do19:39
anteayadid the inital spec commit merge yet?19:39
morganfainbergreed, have links for those handy? (i can look up if not)19:39
fungianteaya: i should have put that on the agenda. inserting it as a quick topic now19:40
anteayathanks19:40
reedmorganfainberg, from the email: http://lists.openstack.org/pipermail/openstack-infra/2014-June/001297.html19:40
morganfainbergreed, tyvm19:40
*** Sukhdev has quit IRC19:40
*** bknudson has joined #openstack-meeting19:40
*** emagana has quit IRC19:41
*** emagana has joined #openstack-meeting19:41
*** sarob has quit IRC19:42
*** emagana has quit IRC19:42
fungiokay, so anything else on that? we've got about 15 minutes left19:42
fungiwas definitely good to get an update and call to action there19:42
reedfungi, I'm good, as long as I get comments on the blueprint :)19:42
*** emagana has joined #openstack-meeting19:43
fungiyes, i will make a note to provide some feedback, please everyone with interest do the same19:43
fungi#topic Infra specs (fungi)19:43
*** openstack changes topic to "Infra specs (fungi) (Meeting topic: infra)"19:43
fungi#link https://review.openstack.org/9444019:43
fungiplease let's get this put to bed. there are now numerous specs changes waiting on it19:43
anteayayes19:43
anteayado merge19:43
*** vivek-ebay has joined #openstack-meeting19:44
anteayathen we can look at other specs19:44
fungimordred: clarkb: jhesketh: please weigh in on that19:44
clarkbfungi: I mean I weighed in, it won't work :P19:44
*** zdiN0bot has joined #openstack-meeting19:44
clarkbfungi: should we just go ahead and address comments and shove it through?19:44
SergeyLukjanov++ for merging19:44
SergeyLukjanov:)19:44
morganfainbergas somethng keystone just went through, have you decided what the spec approval process is? standard +2/+2/+A?19:44
morganfainbergjust so there isn't a question when it comes time to approve specs.19:45
fungiclarkb: i think so, if the comments are blockers19:45
clarkbfungi: not being able to build the resulting document seems like a blocker to me but I didn't -1 because you can still review specs without it19:45
mordredclarkb: the doc doesn't build?19:45
fungiyeah, we're not yet publishing them other than as drafts anyway, so i wasn't too worried about it, but it's trivial to fix19:45
clarkbmordred: see my comment, it won't find docs under subdirs like implemented/19:46
anteaya+1 address comments and shove it though19:46
fungi#link https://review.openstack.org/#/c/94440/3/doc/source/index.rst19:46
fungifor clark's concern19:46
mordredclarkb: lemme pull it then - I hacked on the heat one to fix its doc build19:46
*** nedbat_ has quit IRC19:46
mordredoh - or your thing19:46
fungianyway, didn't want to take up too much time with this topic, just wanted to make sure to get it on everyone's radar19:46
mordredyeah. I'll go look at it.19:46
clarkbmordred: are you volunteering to fix the issues real quick?19:47
*** nedbat has joined #openstack-meeting19:47
anteayafix and merge is my stance19:47
clarkbI don't think there is anything contentious just details needed to make it work properly19:47
mordredclarkb: I'm volunteering to think about it19:47
mordred:)19:47
clarkb:) ok19:47
*** nedbat has quit IRC19:47
fungi#topic Request for comments on the horizon split plan (rdopiera)19:47
*** openstack changes topic to "Request for comments on the horizon split plan (rdopiera) (Meeting topic: infra)"19:47
fungi#link https://etherpad.openstack.org/p/horizon-split-plan19:47
*** nedbat has joined #openstack-meeting19:47
*** thedodd has quit IRC19:47
mordredI, for one, welcome our new split horizon overlords19:47
morganfainbergmordred, ++19:48
fungithis seems to have been fleshed out a lot more now19:48
anteayardopieralski: my comment is the same one I made on https://review.openstack.org/#/c/95716/19:48
fungii tried to keep up with the related threads on the -dev ml but probably missed some of the issues19:48
rdopieralskianteaya: yes, I will make a new group for that19:48
*** jmontemayor has joined #openstack-meeting19:48
mordred"    in horizon, add django_horizon to requirements.txt, as -e path-to-the-repo"19:48
rdopieralskianteaya: thank you19:48
anteayardopieralski: I agree with markmc that expecting core to admin 16 repos in stackforge is odd19:48
mordredplease no19:48
anteayardopieralski: k, thanks19:48
*** noslzzp has joined #openstack-meeting19:49
mordredthat needs to be as a refernce to the master tarball on tarballs.o.o19:49
rdopieralskimordred: great, thank you19:49
mordred(updated etherpad)19:49
rdopieralskiawesome19:49
fungiwhat needs to be discussed here, other than making sure we're all aware this is coming? (i know the new name for the split-out half hasn't been settled yet at least)19:49
mordredseems straightforward to me19:50
anteayapoll is open: http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_ea99af9511f3f255&akey=e4c064fca36f8d2619:50
*** thedodd has joined #openstack-meeting19:50
clarkbanteaya: were those names vetted first?19:50
*** kun_huang has quit IRC19:50
clarkbwe seem to have a really hard time doing that19:50
mordredyeah. that was my question19:50
*** luis_ has joined #openstack-meeting19:50
anteayardopieralski's email has the process19:50
rdopieralskifungi: I mostly wanted you to look at it and catch any obvious blunders, like you just did19:50
fungiclarkb: i asked, sounds like the top several will get sent to the foundation for vetting19:50
pleia2one landed on the -infra list, but it was moderated so I was able to reject it19:50
pleia2(one == a ballot)19:51
*** caleb_ has joined #openstack-meeting19:51
*** trey_h has joined #openstack-meeting19:51
fungiclarkb: mordred: vetting 18 would be a bit of a waste of time19:51
clarkbfungi: right but a human can use the googles before hand19:51
rdopieralskiI would also want, if possible, to ask someone of you to volunteer in helping with it19:51
clarkbfungi: which would have caught every other rename we have had to do19:51
mordredplease let schwartzchild win19:51
rdopieralskiduring the freeze itself19:51
anteayahttp://lists.openstack.org/pipermail/openstack-dev/2014-June/037185.html19:51
*** Macaveli has quit IRC19:51
fungiclarkb: true. the degree to which anyone has is unknown19:51
*** e0ne has quit IRC19:51
fungito me anyway19:51
rdopieralskibut we don't have a date for that yet, so it may be too early19:51
fungirdopieralski: yeah, once we know when you'll be ready, it'll be easier to rally the troops on it19:52
anteayardopieralski: helping with what? with the vetting of names?19:52
morganfainbergmordred, there is a t missing in the poll option compared to what you typed. "schwarzchild" vs "schwartzchild"19:52
clarkbhttps://www.paloaltonetworks.com/products/technologies/panorama.html19:52
rdopieralskianteaya: nah, with the actual split19:52
anteayardopieralski: oh the split19:52
morganfainbergis that supposed to be schwartzchild instead?19:52
rdopieralskimorganfainberg: possibly19:53
clarkba quick googling should be able to exclude blatant problems...19:53
rdopieralskiI just copied it from the etherpad :P19:53
morganfainbergrdopieralski, probably a typo ... it looks... off19:53
*** eglynn has joined #openstack-meeting19:53
* morganfainberg shrugs19:53
*** eglynn is now known as eglynn-afk19:53
fungimorganfainberg: no, http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CB8QFjAA&url=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FSchwarzschild_radius&ei=SWKXU-bYMrCisATqtoGwDQ&usg=AFQjCNFL3m870AJgoy-enNcbYecDseUeew&sig2=VLmoF4rk51OcChUoTZUynw19:54
fungier19:54
fungihttp://en.wikipedia.org/wiki/Schwarzschild_radius19:54
morganfainbergfungi, oh ok.19:54
morganfainbergworks for me19:54
fungi(a nod to the event _horizon_)19:54
morganfainbergyep yep19:54
anteayacan I get a few minutes, I just need folks to agree I am doing the right thing with templates19:54
fungiat least that's my assumption19:54
fungianteaya: yep19:54
fungirdopieralski: anything else?19:54
rdopieralskifungi: that's all, thank you19:55
fungi#topic Review Third Party wiki templates - seed pages (anteaya)19:55
*** openstack changes topic to "Review Third Party wiki templates - seed pages (anteaya) (Meeting topic: infra)"19:55
anteayathanks19:55
fungiyou have the floor ;)19:55
mordredmorganfainberg: :)19:55
anteayaso we have been progressing through third party templates19:55
anteayaand i have some to look at19:55
anteaya#link https://wiki.openstack.org/wiki/ThirdPartySystems/IBMPowerKVMCI19:55
*** marun_afk is now known as marun19:55
anteaya#link https://wiki.openstack.org/wiki/ThirdPartySystems/OpenStack-Neutron19:56
anteayaplease share your feedback19:56
anteayaare we happy yet? do we want them all to use this format?19:56
anteayaanything missing?19:56
fungianteaya: well, the example demonstrates that intent and focus may be redundant concepts19:56
*** raildo has left #openstack-meeting19:56
fungibut beyond that, fine with me19:56
anteayaokay, which should we keep, intent?19:57
anteayaand thanks19:57
anteayaor do we like focus better?19:57
clarkbit might be more readable as a more normal wiki page but then you will probably have drift19:57
reedanteaya, how hard is it to make the line "3rd party system: IBM PowerKVM CI" more prominent?19:57
*** marcoemorais has quit IRC19:57
fungii'm also marginally unsure how we want to translate openstack programs to the per-project acls we talked about setting up (all projects in the listed program, or only some projects in a program allow any third-party voting?)19:57
anteayareed: I can work for that, what do you want, larger font? more space around it?19:58
ianw"current status" seems like something that will get out of date and not always reflect reality19:58
*** marcoemorais has joined #openstack-meeting19:58
reedwhere are these templates going to be shown? on individual pages or as a 'sidebox' embedded in other pages?19:58
anteayafungi: yes, that does present an issue needing discussion19:58
reednot clear to me the scope of this effort to be able to comment... but since I love templates :)19:58
clarkbfungi: I think we go with all projects19:58
clarkbfungi: its too complicated otherwise19:58
fungiianw: i think the hope is that it gets updated by the owners of that account when it breaks, as an indicator to everyone that they know it's broken19:59
*** devlaps1 has quit IRC19:59
fungiclarkb: yeah, agreed. all projects in a given program get an acl stanza allowing that vote19:59
clarkbso you have compute-ci network-ci et al as groups owned by nova-ptl neutron-ptl19:59
fungianteaya: did you need to hit your other topic too? 30 seconds19:59
anteayaline 11 #link https://etherpad.openstack.org/p/automated-gerrit-account-naming-format19:59
*** malini1 has joined #openstack-meeting19:59
fungi#topic Formatting Automated Gerrit Account Names (anteaya)20:00
*** openstack changes topic to "Formatting Automated Gerrit Account Names (anteaya) (Meeting topic: infra)"20:00
reedanteaya, that first line with a larger font, like an h3 level or something similar would be better... right now the pages as they are displayed now are not very clear to me (but I may be the wrong audience)20:00
anteayacan we live with that as an automated gerrit naming format?20:00
fungi#link https://etherpad.openstack.org/p/automated-gerrit-account-naming-format20:00
anteayareed: you are the right audience, will look at that20:00
*** devlaps has joined #openstack-meeting20:00
*** markmc has joined #openstack-meeting20:00
*** caleb_ has quit IRC20:00
*** rdopieralski has quit IRC20:00
anteayalines 11-16 is the proposed format20:00
*** sushils_ has quit IRC20:00
*** jaypipes has joined #openstack-meeting20:00
fungianteaya: seems fine to me20:00
fungialso we're running over20:00
anteayado we need more discussion or can i publish?20:00
*** vinod has joined #openstack-meeting20:00
anteayakk20:01
anteayadone20:01
clarkbI don't want to change usernames20:01
clarkbbut we can talk over there ->20:01
anteayaclarkb: just asking about format guidelines atm20:01
fungiclarkb: i think we had decided we only change new usernames, not existing ones20:01
fungiand we change existing and new display names20:01
markmc"time now, folks. time now"20:01
fungianyway, ttx is going to get mad at me20:01
fungi#endmeeting20:01
ttxnot at all20:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:01
*** sushils_ has joined #openstack-meeting20:01
openstackMeeting ended Tue Jun 10 20:01:44 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-06-10-19.02.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-06-10-19.02.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-06-10-19.02.log.html20:01
ttxAnyone around for the TC meeting ?20:01
markmchey20:01
dhellmanno/20:01
vishyo/20:01
* jaypipes gets Internet just in the nick of time...20:02
reedttx is mad already20:02
Kiallo/20:02
mikalMorning20:02
* fungi standing in for jeblair20:02
anteayao/20:02
devanandao/20:02
jaypipeso/20:02
* morganfainberg lurks.20:02
russellbo/20:02
mugsieo/20:02
annegentlehoo hoo20:02
*** iron1 has quit IRC20:02
vinodo/20:02
mordredo/20:02
mordredo/20:02
*** markmcclain has joined #openstack-meeting20:02
ttxmarkmcclain, sdague : around ?20:02
markmcclaino/20:03
ttxAlmost everyone today!20:03
markwasho/20:03
ttx#startmeeting tc20:03
openstackMeeting started Tue Jun 10 20:03:07 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
ttxHere is our agenda for today:20:03
*** openstack changes topic to " (Meeting topic: tc)"20:03
openstackThe meeting name has been set to 'tc'20:03
*** tsimmons has joined #openstack-meeting20:03
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:03
ttx#topic Glance Program Mission Statement and the Catalog20:03
*** openstack changes topic to "Glance Program Mission Statement and the Catalog (Meeting topic: tc)"20:03
ttxmarkwash: o/20:03
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2014-June/036767.html20:03
markwashhi hi20:03
ttxOverdue original mission is proposed at:20:03
ttx#link https://review.openstack.org/9800120:03
ttxI think we should approve that one now and then discuss the real proposed change:20:03
ttx#link https://review.openstack.org/9800220:04
*** vkmc has quit IRC20:04
ttxUnless there is strong objection on the 98001 "original" wording20:04
annegentleheh I wasn't gonna nitpick 98001 but I like the serial comma in 98002's list20:04
* devananda adds +1 to the first review20:04
annegentlebut I can wait for the second20:04
*** VijayB has joined #openstack-meeting20:05
markwashannegentle: ugh I missed that! I love the oxford comma20:05
ttx7 YES, I can approve now unless someone objects20:05
russellb<3 oxford comma20:05
mikalI like cheese20:05
fungii've commented a vote in favor on jeblair's behalf, since it lgtm20:05
markwash(commas matter. "Let's eat, grampa!")20:05
ttxOk let's approve it20:06
dhellmannmmm, delicious20:06
annegentlemarkwash: mikal: snort20:06
*** changbl has joined #openstack-meeting20:06
mordredyummy salty human flesh...20:06
*** jaycaz has joined #openstack-meeting20:06
ttxThat should facilitate discussion on 9800220:06
sdaguettx here now20:06
*** Haneef has quit IRC20:06
ttxok, 98001 merged20:06
*** VijayB has quit IRC20:06
ttxNow on to 9800220:06
*** betsy has joined #openstack-meeting20:06
ttxmarkwash: could you provide examples of other artifact types that would make sense for storage into the new Glance ?20:07
* devananda notes the lengthy discussions on rev2 of 98002, starts catching up20:07
markwashso part of it is breaking up the idea of image so that it is more usable and interoperable for example20:07
markmcyes, maybe start with concrete example of why the mission needs expanding20:07
* dhellmann went a little too far stripping out implementation details in his proposed revision20:07
markwashso instead of just "image"20:07
markwashwe could have an artifact for disk images and artifacts for the full arrangement of device mappings20:07
markwashanother popular example is pretty much anything that can go in a heat template20:08
zanebheat and murano templates are another obvious one20:08
gokrokveSolum LP20:08
markwashand the examples that seemed to push this to the fore were murano packages and something something solum20:08
mikalmarkwash: why be an artifact store at all?20:08
markwash:-)20:08
ttxmarkwash: ok20:08
mikalmarkwash: couldn't you just be a catalog of artifacts stored elsewhere?20:08
dhellmannwhy do those things need to go in glance, though? why shouldn't they go in the heat database?20:08
ttxmikal: it's what it is actually20:08
*** vkmc has joined #openstack-meeting20:08
markwashmikal: actually that's what we want to be20:08
dhellmannah, ok, we should take out "store" then :-)20:09
markwashmikal except glance has to own stuff in order to guarantee integrity20:09
zanebdhellmann: because we don't want to implement a catalog service in heat20:09
mikalmarkwash: sure20:09
russellba registry of things, their type, and location, right?20:09
markwashso if we can't own it without storing it, we'll store it20:09
fungishould glance become the heat database? ;)20:09
devanandamarkwash: so the artefacts may be stored, essentially, anywhere - and glance would just provide the browsability?20:09
mikalSo... does that mean that a key store is just a special case of glance now?20:09
jaypipesglance stores the archetypes, other projects store the artifacts themselves?20:09
russellbmikal: i think keys are one exception20:09
mikalrussellb: why?20:09
devanandarussellb: why?20:09
markwashagain, we *own* it so we will continue to store everything we have to in order to completely control access20:09
russellbmikal: since we said keys justify special handling (around security, compliance)20:09
russellbthat's why we allowed a special program for key handling20:10
dhellmannzaneb: why do you need a catalog service to store templates? we don't need one to store most of the rest of the stuff we store? (serious question about the difference)20:10
zanebdhellmann: basically for the same reason we need one for images20:10
devanandawhat makes a pub key different from a heat template different from an image -- from the perspective of publishing & browsing opaque content?20:10
*** fnaval has quit IRC20:10
markmcdhellmann, to allow users to browse available templates20:10
devanandarussellb: don't snapshots have similar security requriements?20:11
russellbsecurity compliance rules around storing key material20:11
mikalrussellb: I am ok with that, as long as there's a good reason20:11
zanebthey're a pain to store outside the cloud and still be able to access from Heat20:11
*** pcrews_ has left #openstack-meeting20:11
*** fnaval has joined #openstack-meeting20:11
markwashmikal: we don't do fancy crypto so we shouldn't store keys20:11
markwashits not that we couldn't20:11
zanebyou could just use swift20:11
russellbdevananda: haven't heard that requirement20:11
markwashits just that no one would choose to use glance for keys :-)20:11
*** nati_ueno has quit IRC20:11
markmczaneb, but you wouldn't have browsing20:11
zanebbut glance provides a lot of nice things (e.g. artifacts are immutable)20:11
russellbright, and typing20:11
dhellmannis immutability a strong enough feature to be mentioned in the mission, preventing any type of artifact from being mutable without TC approval later?20:12
russellband i guess some additional access controls20:12
markmctyping facilitates browsing20:12
* markmc getting silly now20:12
russellb:)20:12
jaypipesdhellmann: I think that's a good question.20:12
ttxI think it makes sense to use a more generic name than "images" since we are about to use glance to store more than just disk images20:12
* markwash is not sure he can follow the pace of all this :-)20:12
markmcimmutability is there for browsing experience too?20:12
zanebrussellb: yeah, typing is essential for Murano, at least20:13
jaypipesdhellmann: is mutability a requirement for being a versioned archetype? I think it is.20:13
dhellmannmarkwash: what I read in draft 3 was a lot of features of glance, but not the *reason* for having those features20:13
markwashimmutability is just part the expected user experience of a repository20:13
jaypipesdhellmann: sorry, meant *immutability* :)20:13
*** eankutse has quit IRC20:13
markwashthink sonatype nexus for an example of another "repository" as I mean it today20:13
fungijaypipes: i think strict versioning at least enables immutability20:13
ttxdhellmann: agree reason could be provided in the commit message20:13
zanebI actually don't like the wording w.r.t immutability20:13
jaypipesfungi: agreed.20:13
*** jecarey has joined #openstack-meeting20:14
jaypipesand frankly, the prospect of having a service that provides these schemas/archetypes in a consistent, versioned manner is really appealing to me.20:14
dhellmannttx: no, I mean the mission is supposed to describe what is being built in terms of what benefit it brings, not in terms of a product manager's view of features20:14
zanebthe repository should be versioned and you should only be able to reference fixed versions20:14
devanandamarkwash: if glance may be configured as a broker that does not store objects locally, how does it guarantee immutability?20:14
zanebnot 100% sure that 'immutable' is the right way to describe that20:14
fungi"what problems this solves in an openstack environment"?20:14
*** jecarey_ has quit IRC20:14
dhellmannzaneb: those are product requirements, not a program mission description20:14
jaypipesI envision things like images, block device mappings, even things like capabilities that are currently randomly plopped into nova's compute node and flavor extra_specs stuff,20:14
markwashdevananda: we strive to own the account things are stored under elsewhere20:14
dhellmann"a service to store and find application-specific BLOBs" is a mission20:15
*** crobertsrh has joined #openstack-meeting20:15
*** crobertsrh has left #openstack-meeting20:15
mordreddhellmann: ++20:15
*** crobertsrh has joined #openstack-meeting20:15
ttxdhellmann: glance first consumer are other openstack services though, and I think taht's covered in "artifacts consumable by OpenStack services in a unified manner" wording20:15
*** denis_makogon has joined #openstack-meeting20:15
zanebdhellmann: swift does that. glance is something more specific20:15
dhellmannttx: ok, I was being brief for irc20:15
dhellmannzaneb: does swift have search?20:15
devanandazaneb: that's my confusion20:15
*** fnaval has quit IRC20:16
dhellmannzaneb: are swift objects application-specific? maybe "strongly typed" instead?20:16
mordredit's an artifact registry20:16
mikaldhellmann: it has search for prefix in a container20:16
markmcwow, BLOB is actually an acronym20:16
mordredthat you can stick something in swift is irrelvant20:16
mordredmarkmc: yup. Binary Large OBject20:16
dhellmannmarkmc: yeah20:16
mordredyou can also just have  LOB20:16
*** olaph has left #openstack-meeting20:16
fungimarkmc: if it's in the jargon file, it's *got* to be true20:16
fungigospel20:16
markwashkeeping in mind that we actualy use swift for storage in many deployments. . we're focusing on the value add over-top of swift20:16
mordredmarkwash: ++20:16
markmcfungi, wikipedia too20:16
markwashwhich includes rich type-specific metadata20:16
dhellmannmarkwash: +120:17
markmcmetadata is a feature, why is it useful? browsing?20:17
gokrokveReferences is one of the key features of the artifact repository20:17
zanebdhellmann: I think you'll end up with a different product if your mission doesn't include the fact that artifacts are versioned20:17
dhellmannmarkwash: is that what "documents" means in the current draft? I wasn't sure what the distinction between documents and BLOB was20:17
ttxOK, looks like we'll have to timebox this20:17
markwashdhellmann: yes20:17
jaypipesmarkmc: technically, when Jim Starkey invented the term back in the 70s, Blob was not an acronym.. he just meant to reference a thing without structure.20:17
devanandaa service which brokers access to application-specific data objects which, once stored, are versioned.20:17
markwashmetadata is such a terrible word20:17
dhellmannmarkwash: ok, thanks for clarifying20:17
gokrokveIt should be able to download a bulk of artifacts tied by references20:17
markwashthe goal is to take as much semantic user metadata and make it actually schematic document data20:17
* jaypipes goes back into pedantry cave.20:18
mordredjaypipes: new rule, anyone who mentions starkey loses ;)20:18
jaypipesmordred: :)20:18
markwashsince user-metadata is not very discoverable, understandable, portable, etc20:18
devanandamordred: lol20:18
annegentlejaypipes: pedant!20:18
ttxLet's try to iterate on the review itself. If it stalls we can raise a ML thread20:18
sdagueok, so here's where I like doing mission statements in folksy language. :)20:18
ttxBUT20:18
*** vkmc has quit IRC20:18
markmc"document" doesn't resonate with me as data which is attributes describing the BLOB20:18
markwashmarkmc: fair20:18
ttxI kinda like that we are expanding Glance role to cover not just disk images but other BLOBs of the same type of usage20:18
dhellmannmarkmc: +120:19
ttxOne potential issue we need to check is the change in the "official name" from "OpenStack Image Service" to "OpenStack Artifact Repository"20:19
markwashactually I struggled to get that term, I don't know what the right one is, just metadata is so so overloaded :-)20:19
*** nati_ueno has joined #openstack-meeting20:19
ttxPersonally I think the new name makes way more sense, but I feel like we need to warn more than just the developers about it20:19
ttx(once we converge onto a new mission/name)20:19
jaypipesmarkwash: schema? archetype?20:19
markmcyeah, I think there's consensus here on the general idea20:19
markmcjust nitpicking now, really20:19
russellbyeah, definitely like the general idea20:19
mordred++20:19
russellbwording is hard20:19
markmccollaborative editing20:19
mordredgeneral idea rocks20:19
mordredwords suck20:19
zanebmarkwash: I'm also curious about the Graffiti blueprint, and how that ties in with this mission20:19
ttxOK, and gerrit helps with that20:19
ttxLets' move on to next topi, shall we20:19
ttx+c20:20
mordredzaneb: I think that's to expand on the metadata side of the coin20:20
markwashso, my feeling on Graffiti is that it helps us with the user-metadata we will keep20:20
russellbhow many sides does the coin have20:20
markwashand the fact that it helps other openstack projects too is just gravy20:20
*** Michalik_ has quit IRC20:20
mordredrussellb: 100000000000000020:20
dhellmannrussellb: that depends on the coin's type, right?20:20
mordreddhellmann: I need some coin metadata20:20
russellb:)20:20
dhellmannmordred: ask markwash20:20
russellbok, i think we can move to the next topic20:20
markmcok, moving on from glance ...20:20
devanandattx: ++20:20
markmcto more glance?20:20
ttx#agreed let's iterate on wording on the gerrit review20:20
zanebmarkwash: ok, I just want to make sure the Glance team has freedom of action in that area without coming back to the TC20:21
markwashzaneb: good point20:21
ttx#topic Glance Functional API and Cross-project API Consistency20:21
*** openstack changes topic to "Glance Functional API and Cross-project API Consistency (Meeting topic: tc)"20:21
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2014-May/036416.html20:21
markwashlets be sure of that in the notes on the vote if we can20:21
ttxSo this is more of an advice question, touching API convergence20:21
markwashoh yeah this one20:21
markwashmostly some folks elected you guys to appoint an api consistency committee20:21
* ttx with type passed in payload, or actions/action20:21
markwashdid you do that?20:21
markwashshould we talk to them?20:21
russellbi like the way you propose better than nova's way20:22
ttxerr20:22
markmc#link http://lists.openstack.org/pipermail/openstack-dev/2014-June/thread.html#3670120:22
ttx /action with type passed in payload, or /actions/action20:22
markmcdamn threads crossing month boundaries20:22
dhellmannyeah, I forget who mentioned logging but between that and making request routing easier I like the action in the url, too20:22
sdaguerussellb: agreed, the proposed glance way for actions is much nice20:22
sdaguenicer20:22
russellbanyone disagree?20:22
sdaguedhellmann: that was me :)20:23
markmcI just wish we were gradually converging on API consistency20:23
ttxso I don't think we should block them from implementing it at all :)20:23
dhellmannsdague: that was a good point20:23
markmcthat consensus meant all projects would adopt this pattern in future20:23
markmcrather than another project to iterate further on this20:23
annegentlettx: I'm in agreement, I'd like to see one project do the work and others follow and it doesn't always have to be nova as pattern-setter20:23
russellbmarkmc: yes, agreed... how can we communicate this widely?20:23
sdaguedhellmann: I stare at logs a lot... the action urls are painful today20:23
markmcrussellb, dunno20:23
russellbshould it be something we document as a best practice recommended by this group?20:23
russellband then blog about it in our new TC update series?  :)20:24
dhellmannshould we start an API style guide in the wiki? or an all-projects spec repo?20:24
anteayacyeoh had a summit session on apis20:24
* markmc had a document called "ReST standards" before; geddit?20:24
markwashthere were volunteers for this in a summit session20:24
markwashyou could just delegate20:24
ttxrussellb: at one point in history we wanted to have some API czar, but that died quickly20:24
markmc(for another project)20:24
anteayajaypipes you said you would do a thing out of that session20:24
sdagueright, didn't we discuss an all-projects spec repo20:24
sdagueand even ttx agreed on it :)20:24
russellbthis is all i know of ... https://wiki.openstack.org/wiki/APIChangeGuidelines20:24
dhellmannmarkwash: by "we" I meant "openstack" rather than "the tc"20:24
*** afazekas has joined #openstack-meeting20:24
russellband it's not really about API design at all20:24
markwashdhellmann: ah kk20:24
markmcwe've had some etherpads from design summit sessions too20:25
russellbttx: a nice idea if the right person stepped up and was motivated20:25
markmcbut they were proposals I guess20:25
devanandadhellmann: api style guide could be helpful, but shouldn't be too rigid or may get abused/ignored, depending on how things go20:25
* markmc put links in https://etherpad.openstack.org/p/juno-cross-project-consistency-across-rest-apis20:25
dhellmanndevananda: sure20:25
ttxOK, so agreement on letting Glance go in that direction, and wish we had clearer guidelines set to encourage future convergence ?20:26
sdaguettx: +120:26
anteayaI can cobble together the cyeoh's session notes and do a ml post so it gets a tc agenda item20:26
markmcclain+120:26
fungisounds reasonable20:26
devananda+120:26
markmcwe would fully support anyone wanting to take on the task of document style guidelines20:26
ttx#agreed Glance can definitely go in that direction for API20:26
dhellmannmarkwash: how about if you *start* a style guide?20:26
dhellmannmarkwash: see what I did there?20:26
markwashif I start it, it will never be finished20:26
markwashor started20:26
dhellmannhaha20:26
markwash:-)20:26
devanandatossing this out there as possibly helpful for folks20:26
ttx#info TC would like to have "good API design" guidelines to encourage convergence, looking for volunteers to document and propose that20:26
devanandahttps://restful-api-design.readthedocs.org/en/latest/methods.html20:27
annegentleI can ask Diane Fleming if she's interested in picking up an API style guide but we'd need to define what you want.20:27
dhellmannmarkwash: seriously, you could just start with this one issue20:27
annegentleshe'd have the most cross-project knowledge from all the API doc work20:27
markwashdhellmann: I'll give it some thought but I'm in too dangerous a location to commit to anything right now20:27
dhellmannmarkwash: ok20:27
* markmc throws http://fedoraproject.org/wiki/Cloud_APIs_REST_Style_Guide out there as an example20:28
ttxok, moving on to next topic ?20:28
markwashmoar glance!20:28
annegentlehonestly this looks like something Diane could do, would you like it?20:28
ttx#link http://fedoraproject.org/wiki/Cloud_APIs_REST_Style_Guide20:28
ttxannegentle: if she wants to propose something, i don't think we should prevent her20:29
annegentlettx: got it20:29
ttxbut she should expect the "convergence guideliens" to be nitpicked over to death20:29
ttxso albestos suit recommended20:29
annegentleheh20:29
jaypipesdang it, I really wish I had the time to respond to that Glance functional API thread :(20:29
annegentleflame-proof but cancer-causing. Check20:30
jaypipestoo many darn emails.20:30
russellbor some asbestos-replacement that won't ruin your lungs20:30
ttxjaypipes is the closest we have in the TC to an APi integrist20:30
fungihe is also flameproof, from what i hear20:30
markwashI'm a bit afraid that some rest purism might argue against our approach20:30
markmcttx, integrist needs translation - I only learned it from nijaba in atlanta :)20:31
*** SlickNik has joined #openstack-meeting20:31
ttxoh.20:31
ttxfrenchism probably20:31
markmcmarkwash, rest purism? never!20:31
ttxok, moving on20:31
ttx#topic Integrated projects and new requirements: Gap analysis for Glance20:31
*** openstack changes topic to "Integrated projects and new requirements: Gap analysis for Glance (Meeting topic: tc)"20:31
ttxmOAR Glance20:32
ttxmarkwash: hi!20:32
* markwash just made it in time20:32
ttx#link https://etherpad.openstack.org/p/glance-integration-gaps20:32
* russellb glances over the etherpad20:32
markwashthe formatting there is probably not so good20:32
ttxI figured we should expedite this one, since we have markwash around20:32
markwashbottom line is that I couldn't really find much of a problem, except pace of bug triage and docs maybe20:32
*** arunkant has quit IRC20:33
*** shadower has quit IRC20:33
*** kmartin has quit IRC20:33
*** AaronGr has quit IRC20:33
*** nijaba has quit IRC20:33
*** pfalleno1 has quit IRC20:33
*** enikanorov_ has quit IRC20:33
*** jrist has quit IRC20:33
*** esmute has quit IRC20:33
*** jwang_ has quit IRC20:33
*** ogelbukh has quit IRC20:33
*** ryanpetrello has quit IRC20:33
*** cschwede_ has quit IRC20:33
*** scottda has quit IRC20:33
russellbi have no complaints20:33
russellbnice work :)20:33
sdaguemarkwash: so I know for a fact the tempest tests for glance don't actually try to store real binary data, because I got bit by it :)20:33
*** Sukhdev has joined #openstack-meeting20:33
*** esmute has joined #openstack-meeting20:33
*** pfallenop has joined #openstack-meeting20:33
*** shadower has joined #openstack-meeting20:33
*** jwang_ has joined #openstack-meeting20:33
vishyits ok REST fails when using lists + acls20:33
*** shadower has quit IRC20:33
*** shadower has joined #openstack-meeting20:33
*** scottda has joined #openstack-meeting20:33
*** jrist has joined #openstack-meeting20:33
*** kmartin has joined #openstack-meeting20:33
ttxmarkwash: you might want to refine your https://launchpad.net/~glance-coresec/+members -- looks like an old list of glance-core people20:33
*** kmartin has quit IRC20:33
*** kmartin has joined #openstack-meeting20:33
markwashsdague: eek20:33
*** arunkant has joined #openstack-meeting20:33
*** ryanpetrello has joined #openstack-meeting20:33
*** AaronGr has joined #openstack-meeting20:33
sdagueAnd I'm pretty sure much of the v2 api is not covered20:33
markwashglance core has been a bit of an alumni association, yes20:33
russellbwould be nice to get nova updated to using latest glance API20:34
russellbcould use help there20:34
sdaguemarkwash: yeh, mtreinish wrote all the glance tests a year ago when they largely didn't exist20:34
*** nijaba has joined #openstack-meeting20:34
*** nijaba has quit IRC20:34
*** nijaba has joined #openstack-meeting20:34
sdaguebut there are definitely holes20:34
*** ogelbukh has joined #openstack-meeting20:34
annegentlemarkwash: my input on docs would be that API docs also include the reference listings at http://developer.openstack.org/api-ref-image-v2.html and http://developer.openstack.org/api-ref-image-v1.html20:34
ttxmordred: could you add markwash as admin to https://launchpad.net/~glance-coresec/+members ?20:34
markwashttx: OH! core-sec20:35
ttxmordred: and maybe remove yourself (you retain access through openstack-admins)20:35
*** cschwede has joined #openstack-meeting20:35
fungior i can take care of it if mordred is busy mordreding20:36
annegentlemarkwash: bit of docs analytics trivia20:36
markwashannegentle: I personally have had a perilous time trying to keep our docs in mind. its like there's no cubby space for that in my brain somehow20:36
*** navid has joined #openstack-meeting20:36
ttxfungi: we have to elevate ourselves to admin, while he is admin already. But yes, you can do it :)20:36
annegentlemarkwash: one of the most visited pages on the docs site is http://docs.openstack.org/image-guide/content/ch_converting.html20:36
annegentlemarkwash: sounds like your brain needs a mudroom for docs20:36
markwashindeed20:37
annegentlemarkwash: but it's also the most exited page20:37
*** dhellman_ has joined #openstack-meeting20:37
*** thuc has joined #openstack-meeting20:37
*** s3wong_ has joined #openstack-meeting20:37
*** sarob has joined #openstack-meeting20:38
mordredttx: on it20:38
sdaguemarkwash: I haven't looked recently, but I did have concerns about the review patterns in glance core. Where largely nothing would get looked at for 4 - 6 weeks, then mass approvals near a milestone20:38
ttxmarkwash: I don't see any gaps. Only suggestions for improevments (like moar coverage)20:38
markwashsdague: yes, honestly we're struggling in that capacity :-(20:39
sdaguethat pattern in glance was actually one of the key reasons we implemented clean check20:39
jaypipesrussellb: I've been working towards glance v2 api support in nova.20:39
fungittx: markwash: mordred: updated glance-coresec20:39
russellbjaypipes: awesome20:39
mordredfungi: oh - you got it. great20:39
sdaguebecause lots of glance patches with really old test results would get sent into the queue20:39
jaypipesrussellb: all the blueprints are marked low priority and retargeted to j-220:39
markwashI've been very time conflicted and haven't figured out the right way to motivate folks20:39
*** plomakin_ has joined #openstack-meeting20:39
fungittx: markwash: mordred: admins are now brian waldon and mark washenberger20:39
*** Mandell has quit IRC20:39
sdaguemarkwash: so I guess that raises an interesting question. Is the core review team healthy enough to take on more mission?20:39
ttxmarkwash: so now you can clean up https://launchpad.net/~glance-coresec/+members, ideally so that it's only 2-4 active core20:40
ttx(interested in security issues)20:40
markwashprobably want to remove bcwaldon fungi20:40
fungimarkwash: will do20:40
markmcclainsdague: was wondering the same thing20:40
*** eglynn-afk is now known as eglynn20:40
fungimarkwash: done20:40
mikaljaypipes: they will have been retargetted because we're so close to j-1 now20:40
jaypipessdague: I believe the core review team would expand given the new mission...or at least, the opportunity to add some new folks would exist.20:40
markwashsdague: actually i think the extra interest from murano and graffiti folks is something we could catalyze into better review practices20:40
jaypipesmikal: oh, I know. wasn't complaining. just as an FYI20:40
markwashb/c the problem is that glance's old mission is kind of stale and uninteresting20:40
*** fnaval has joined #openstack-meeting20:40
markwashso it doesn't really draw people into the project as much20:41
ttx#info recommendation: more coverage (API v2, binary content...)20:41
ttx#info recommendation: saner review pattern20:41
markwashmurano, graffiti, solumn, heat, etc.20:41
markwashs/solumn/solum/ of course20:41
devanandamarkwash: being stable isn't a bad thing ... :)20:41
*** dhellmann_ has joined #openstack-meeting20:41
sdaguemarkwash: ok. I think it's something we should checkpoint on though. Because I do get concerned with integrated projects that only review in bursts20:41
markwashsdague: +120:41
sdaguedevananda: um... you should have seen some of those patches. :)20:42
*** rromans_ has joined #openstack-meeting20:42
markwashcheckpointing is great b/c honestly we need help and you guys can point us in the right direction20:42
ttxsdague: I expect the new mission will inject new blood, fwiw20:42
*** zns has quit IRC20:42
sdaguettx: yep, that's fair. I just want to raise it as a concern.20:42
*** belmoreira has quit IRC20:42
ttxconcern noted20:42
sdagueso we can be mindful of it20:42
ttxanything else ?20:42
ttxDo we agree tat there is no gap, only a set of recommendations ?20:43
dhellman_I thought testing was a gap?20:43
ttx#info recommendation: fix glance-coresec to only include 2-4 active core members interested in security issues20:43
*** sarob has quit IRC20:43
markwashis there an api coverage report generated from tempest?20:43
sdaguemarkwash: I haven't dug into it deeply20:43
navidHi20:44
ttxdhellman_: A gap would mean, we'd reject Glance in integration if it were proposed now. Do you think testing coverage is a gap ?20:44
ttxA gap means we want to have a gap coverage plan in place ASAP20:44
sdaguettx: the lack of testing a binary image is probably a gap :)20:44
sdaguebut I'll let markwash pound that out in a week, and it should be fine20:44
ttxOK20:44
dhellmann_ttx: what sdague said :-)20:44
navidsince you are discussing tests. is there a solid document about unit tests in keystone20:44
markwashascii is a subset of binary20:44
markwashbam20:44
*** HenryG has quit IRC20:45
fungiheh20:45
ttx#info gap: intgeration tests -- lack of testing a binary image20:45
anteayanavid: this is a meeting, try #openstack-dev20:45
sdaguemarkwash: :)20:45
ttxOK, anything else ?20:45
fungii suppose the pedants can say high-bit rather than binary20:45
*** devlaps1 has joined #openstack-meeting20:45
markwashfungi: you got me20:45
*** kgriffs|afk is now known as kgriffs20:46
ttxmarkwash: so you should come up with a plan to address the identified gap, ideally within the Juno cycle20:46
ttxshould be short :)20:46
markwashI'll see if the plan can be a gerrit review20:46
ttxYou can file the plan in a doc like https://wiki.openstack.org/wiki/Governance/TechnicalCommittee/Ceilometer_Gap_Coverage20:46
ttxjust ping me when you have it up20:47
markwashkk20:47
ttxlet's move on20:47
ttx#topic Defcore status update20:47
*** openstack changes topic to "Defcore status update (Meeting topic: tc)"20:47
mikalOh hai20:47
markwash(thanks everybody!)20:47
ttxno zehicle today, maybe mikal can expose how last meetings went ?20:47
ttxmarkwash: Thanks for everything20:48
*** luis_ has quit IRC20:48
*** dhellmann_ has quit IRC20:48
mikalSo... I'm meant to have drafted by now a request for PTLs and TC to help nominate designated sections for their projects20:48
mikalIts started, but stalled20:48
mikalI'll pick that up again this week, so expect something soon20:48
*** dhellmann_ has joined #openstack-meeting20:48
ttxmikal: and mordred was supposed to file a scoring proposal as a governance change20:48
mordredyes. I'm behidn. sorry20:48
*** VijayB_ has joined #openstack-meeting20:48
*** mrunge has joined #openstack-meeting20:48
*** gyee has joined #openstack-meeting20:49
ttxmikal: is tat still needed ?20:49
mikalttx: cool20:49
ttx+h?20:49
mikalttx: the designated sections thing? I was only asked to do it last week, so I guess that defcore believes it is still needed20:49
*** zdiN0bot has quit IRC20:49
ttx(I think it is, just checking)20:49
*** sballe has joined #openstack-meeting20:49
mikalI was going to draft it in the form of a TC resolution requesting PTLs to provide a response for the TC to rubber stamp / route20:49
*** VijayB_ has quit IRC20:49
mikalBased on the principles we agreed to a while ago20:50
*** vermarah has joined #openstack-meeting20:50
*** vermarah__ has joined #openstack-meeting20:50
*** vermarah_ has joined #openstack-meeting20:50
ttxmikal: do you think we need a resolution for that ?20:50
*** hs634 has joined #openstack-meeting20:50
mikalttx: probably not, but it seemed the easiest way to get something into the repo20:50
mikalttx: just a really light weight "please consider these principles and then send a gerrit review adding a section for your project below"20:51
mikalttx: if you have a different process, I'm all ears20:51
*** gyee has quit IRC20:51
ttxmikal: was thinking an email with cc:openstack-tc should be sufficient, but i'm fine with the resolution route20:51
*** thuc has quit IRC20:51
*** klindgren_ has left #openstack-meeting20:51
ttxit will just take more time20:51
*** vkmc has joined #openstack-meeting20:51
mikalYeah, I liked that just because it ties everything together with a documented history20:52
ttxmikal: your call, really.20:52
ttxmikal: anything else ?20:52
*** thuc has joined #openstack-meeting20:52
mikalWell, let me finish writing it first and then people can comment on the process20:52
*** VijayB has joined #openstack-meeting20:52
ttxQuestions on defcore ?20:53
ttx#topic Governance changes in review20:53
*** openstack changes topic to "Governance changes in review (Meeting topic: tc)"20:53
*** gyee has joined #openstack-meeting20:53
ttx* Propose Designate for Incubation (https://review.openstack.org/97609)20:53
KiallHeya20:53
*** rodrigods_ has joined #openstack-meeting20:54
*** lsmola__ has joined #openstack-meeting20:54
*** devlaps has quit IRC20:54
*** malini1 has quit IRC20:54
*** nedbat has quit IRC20:54
*** bknudson has quit IRC20:54
*** amcrn has quit IRC20:54
*** manishg has quit IRC20:54
*** blogan has quit IRC20:54
*** s3wong has quit IRC20:54
*** hemna has quit IRC20:54
*** Guest26452 has quit IRC20:54
*** dhellmann has quit IRC20:54
*** hrybacki_ has quit IRC20:54
*** Youcef_ has quit IRC20:54
*** bogdando has quit IRC20:54
*** masayukig has quit IRC20:54
*** rromans has quit IRC20:54
*** rodrigods has quit IRC20:54
*** DuncanT- has quit IRC20:54
*** elo1 has quit IRC20:54
*** coolsvap|afk has quit IRC20:54
*** plomakin has quit IRC20:54
*** lsmola_ has quit IRC20:54
*** hugokuo has quit IRC20:54
*** dhellmann_ is now known as dhellmann20:54
ttx-1s from mikal and markmc still standing20:54
* mikal looks again20:54
russellbappears to be general support, just for some requests to add/change wording20:54
Kiallmarkmc just proposed we reword one of the sections, we're happy to. mugsie was preparing an alternative20:54
*** VijayB has quit IRC20:54
mikalOh yeah20:54
markmccool20:54
Kialland I believe we have addressed mikal's concers20:55
*** hemna has joined #openstack-meeting20:55
mugsieyeah - what we have now is "Enable operators to provide scalable, on demand self service access for customers to authoritative DNS services."20:55
mikalI just wanted the nova proxy work20:55
mikalKiall: I don't see a new patchset?20:55
markmcclainhave we solved the issue of where to house the application?20:55
Kiallmikal: Oh - We've included that in the wiki page20:55
*** julienvey has joined #openstack-meeting20:55
Kiallan action item seems inappropriate for merging into the repo?20:55
mugsiemikal: https://wiki.openstack.org/wiki/Designate/Incubation_Application#Why_a_new_project.3F20:55
*** kaitlin has joined #openstack-meeting20:55
mikalOh, I see20:55
ttxmarkmcclain: orthogonal discussion ?20:55
Kiallmarkmcclain: no, not that I saw.20:56
Kiallttx: ++20:56
*** kaitlin has left #openstack-meeting20:56
dhellman_markmcclain: do you mean which program?20:56
*** nati_ueno has quit IRC20:56
Kiallmarkmc: does mugsie's alternative wording make sense for you?20:56
ttxmordred: asked you a question there: "@Monty: Obviously the application should not live in the projects.yaml. Would you have the application details in the commit message ? Or in some new file under the "resolutions" directory ? Or in a file in a new "applications" directory ?"20:56
*** dhellmann has quit IRC20:56
*** bogdando has joined #openstack-meeting20:56
*** dhellman_ is now known as dhellmann20:56
markmcKiall, sounds a lot better, yes20:56
*** thuc has quit IRC20:56
ttxOK, let's iterate one more time and get it approved soon20:57
markmcbut then again ... "scalable, on deman" ... true of all OpenStack20:57
*** s3wong_ is now known as s3wong20:57
Kiallmarkmc: Okay, we're happy to make that change - but don't want to change the document mid voting without telling people ;)20:57
ttx* Adds a resolution addressing expected election behaviour (https://review.openstack.org/98675)20:57
anteayao/20:57
*** yingjun has joined #openstack-meeting20:57
markmcclainttx: yes orthogonal but in the comments of this review20:57
ttxNot as much time to discuss that as I'd like to20:57
ttxLet's comment on te Gerrit review20:57
anteayacomments so far range from none of the tc can be included in the process to all of the tc must be included20:57
mikalanteaya: yeah, do both of those20:58
anteayaso patchset 2 will be a challenge for me20:58
anteayayou got it20:58
anteayaadditional comments welcome20:58
mugsieanteaya: if you have any questions about what I meant in my comments, ping me20:58
eglynnanteaya: ... well to be fair, it was more that it must be spelled out which it is20:58
ttxyeah, I think everyone agrees with the general intent, but the escalation process in case of violation may still need a bit of refinement20:58
*** nedbat has joined #openstack-meeting20:58
anteayawhich needs to take into account our voting process20:58
anteayathe timing around it and how it currently works20:59
eglynn... and who does the investigating20:59
*** enikanorov_ has joined #openstack-meeting20:59
eglynn... and the finding of guilt, and deciding the penalty20:59
anteayawho has time to do the investigating20:59
*** ArxCruz has quit IRC20:59
anteayanot guilt, violation21:00
ttxOK, let's continue on the review. I know a lot of people haven't reviewed it yet ( includeing me)21:00
anteayadifferent words21:00
ttx* Add translation support requirement (https://review.openstack.org/97872)21:00
*** baoli has quit IRC21:00
ttxsame here, needs a bit more reviews21:00
ttx#topic Housekeeping items21:00
*** openstack changes topic to "Housekeeping items (Meeting topic: tc)"21:00
ttx* Sync infra projects list (https://review.openstack.org/98239)21:00
ttxThat one I shall approve after meeting, unless someone complains NOW21:00
ttx#topic Open discussion21:01
*** openstack changes topic to "Open discussion (Meeting topic: tc)"21:01
ttxFamous last words, anyone ?21:01
russellbwe talked about blogging our activities, i'll take a stab at covering this week21:01
anteayayay21:01
*** rbowen has quit IRC21:01
dhellmannthanks, russellb!21:01
mikalrussellb: thanks21:01
ttxrussellb: still working out the details of the o.o/blog accounts21:01
jaypipesrussellb: ty21:01
russellbttx: will just post to mine for now21:02
zanebrussellb: ++21:02
russellbtomorrow morning21:02
ttxrussellb: ok21:02
ttxMaybe we should just post to personal blogs nd keep some common title21:02
*** richm has left #openstack-meeting21:02
ttx#endmeeting21:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:02
openstackMeeting ended Tue Jun 10 21:02:57 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-06-10-20.03.html21:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-06-10-20.03.txt21:03
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-06-10-20.03.log.html21:03
*** pdmars_ has quit IRC21:03
markmcclainif it ends up on planet than we're good21:03
ttxdhellmann, dolphm, notmyname, eglynn, markwash, jgriffith, mikal, zaneb, david-lyle, kmestery, SlickNik, SergeyLukjanov: around ?21:03
devanandadhellmann: on 97872, this seems to settle the discussion of "should we translate log messages". Is that the intent?21:03
SergeyLukjanovo/21:03
mesteryo/21:03
markwasho/21:03
dolphmo/21:03
SlickNiko/21:03
dhellmanno/21:03
mikalHi!21:03
zanebhere, but might have to disappear in ~ half an hour21:03
* fungi standing in for jeblair21:03
jgriffitho/21:03
notmynamehere21:03
* mrunge for david-lyle21:03
*** vinod has left #openstack-meeting21:03
ttxzaneb: hopefully we'll be done by then :)21:03
ttx#startmeeting project21:03
openstackMeeting started Tue Jun 10 21:03:56 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:03
*** openstack changes topic to " (Meeting topic: project)"21:03
openstackThe meeting name has been set to 'project'21:04
ttxAgenda for today is available at:21:04
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:04
eglynno/21:04
ttx#topic News from the 1:1 sync points21:04
*** openstack changes topic to "News from the 1:1 sync points (Meeting topic: project)"21:04
ttx#link http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-06-10-08.41.html21:04
ttx#topic Other program news21:05
*** openstack changes topic to "Other program news (Meeting topic: project)"21:05
ttxInfra, QA, Docs... anything you'd like to mention ?21:05
*** nati_ueno has joined #openstack-meeting21:05
ttxmtreinish, fungi ?21:05
*** tsimmons has left #openstack-meeting21:05
ttxannegentle (if still around) ?21:05
fungittx: nothing new from infra. be kind, test your patches ;)21:05
*** manishg has joined #openstack-meeting21:05
ttxfungi: the gate fire seems to be mostly under control now ?21:05
fungithe gate's not nearly as far behind as last week21:06
fungiright21:06
*** yingjun has quit IRC21:06
mtreinishttx: nothing from me today, was heads down trying to debug the gate last week21:06
fungilooking at ~3-4 hour delays in approval to merge at the moment21:06
ttxStill a lot to process for juno-121:06
ttxwhich brings us to the next topic21:06
*** mwagner_lap has joined #openstack-meeting21:06
*** hashar has quit IRC21:06
dhellmann3-4 hours is pretty good for a weekday21:06
ttx#topic Juno-1 tagging21:06
*** openstack changes topic to "Juno-1 tagging (Meeting topic: project)"21:06
ttx#info juno-1 needs to be tagged between now and Thursday21:06
eglynnare we going to explicit wait for gate drainage?21:07
ttxBy the end of the day the j-1 plans should reflect what is already approved and in-flight21:07
eglynn*explicitly21:07
ttxeglynn: hmm, not sure I understand your question21:07
ttxWe should generally shoot for tagging tomorrow, rather than stretch it to Thursday21:07
eglynnttx: ... I mean, wait for the verification queue of approved patches to drain21:07
mikalttx: I was intending to produce a git sha interactively with you tonight my time, tomorrow morning your time. Is that ok with you?21:08
eglynnttx: ... or just go with whatever has landed by EoD tmrw21:08
*** manishg is now known as 92AABDT0N21:08
ttxeglynn: ideally we should tag when what was approved today gets merged21:08
eglynnjust mainly wondering about gate-lag21:08
*** marcoemorais has quit IRC21:09
eglynnttx: k, that sounds reasonable21:09
ttxbut we can also have exceptions, if like a blueprint completion is a few hours away in the queue21:09
*** marcoemorais has joined #openstack-meeting21:09
*** aburaschi has quit IRC21:09
*** Mandell has joined #openstack-meeting21:09
ttxso when you have everything you want in juno-1, just let me know a SHA I can use for the juno-1 tag21:09
ttxand i'll make it happen21:09
ttxIt's fine if stuff is deferred, juno-1 is just a point in time21:10
ttxit should reflect what we amnaged to squeeze in by that date21:10
*** rockyg has joined #openstack-meeting21:10
ttxQuestions on juno-1 ?21:10
SergeyLukjanovttx, will we have proposed branches this time?21:10
ttxmikal: I have to run an errand tomorrow morning21:11
*** malini1 has joined #openstack-meeting21:11
*** bknudson has joined #openstack-meeting21:11
*** amcrn has joined #openstack-meeting21:11
*** manishg has joined #openstack-meeting21:11
*** blogan has joined #openstack-meeting21:11
*** Guest26452 has joined #openstack-meeting21:11
*** hrybacki_ has joined #openstack-meeting21:11
*** Youcef_ has joined #openstack-meeting21:11
*** masayukig has joined #openstack-meeting21:11
*** DuncanT- has joined #openstack-meeting21:11
*** coolsvap|afk has joined #openstack-meeting21:11
*** hugokuo has joined #openstack-meeting21:11
*** dickson.freenode.net changes topic to "Governance changes in review (Meeting topic: tc)"21:11
ttxSergeyLukjanov: no21:11
mikalttx: ok, I can just send you an email then21:11
SergeyLukjanovttx, ok21:11
ttxSergeyLukjanov: we tag directly on master, new process21:11
*** malini1 has quit IRC21:11
*** Mandell has quit IRC21:11
*** VijayB has joined #openstack-meeting21:11
ttxmikal: you can also say "tag when change N merges"21:12
mikalttx: ok21:12
fungittx: give me or someone in infra a heads up before you push the first tag on master just so we can be on top of triage if it goes bad21:12
ttxas long as you tell me what to do if it gets booted out of the gate queue (block or release)21:12
fungithough in reality i can't think of reasons it should21:12
ttxfungi: ok, will wait until you're up21:12
*** tnurlygayanov_ has quit IRC21:12
*** sweston has joined #openstack-meeting21:12
*** yuan has quit IRC21:13
ttxI have a tag for Glance already21:13
ttxerr, a SHA for glance21:13
*** manishg has quit IRC21:13
markwashgo glance!21:13
ttxfungi: we could try to push the tag for it just after meeting ?21:13
*** yuan has joined #openstack-meeting21:13
* markwash contributes21:13
fungittx: sure21:14
ttxOther questions ?21:14
*** mugsie has left #openstack-meeting21:14
ttx#topic Enable Autokick BP adjustment script21:14
* dolphm is envious of real PTLs like markwash21:14
*** openstack changes topic to "Enable Autokick BP adjustment script (Meeting topic: project)"21:14
*** Mandell has joined #openstack-meeting21:14
ttxI finalized a new version of the script that adjusts milestone and series goal in Launchpad21:14
*** ItSANgo has quit IRC21:14
*** yogeshmehra has quit IRC21:14
ttxFor projects using -specs it will also automatically clear the "milestone target" field if it's set on an unprioritized blueprint21:14
ttxThe goal being to use the milestone target as a blessed list21:14
ttxrather than duplicate the entry point for people wanting to submit features (spec in Gerrit + BP in Launchpad)21:15
ttxI've run it for most projects during the 1:1 sync today, and plan to run it on cron every 2/3 hours starting tomorrow21:15
ttxAny final objection ?21:15
*** nati_ueno has quit IRC21:15
ttxnotmyname: I did not enable the script for swift, since you don't have a juno milestone yet21:15
zanebttx: consider putting "this is an automated message" in the comment it leaves21:15
mesteryNone here, thanks for setting this up ttx!21:15
*** leeantho has joined #openstack-meeting21:16
dolphmmestery: ++21:16
notmynamettx: ack21:16
ttxzaneb: I just like to get the angry people complaining about it21:16
*** VijayB has quit IRC21:16
fungisounds pretty awesome21:16
*** elo has joined #openstack-meeting21:16
ttx#agreed autokick script to run under cron from now on21:16
ttxNB: I promised a script that would facilitate creating a BP to track an accepted spec, still working on it21:16
ttxIt's delayed due to launchpad not supporting creating BPs from the API, so I have to play tricks around it21:16
zanebttx: I'm more worried about people who think they have brought your wrath down on themselves ;)21:16
ttxStay tuned -- in the mean time just manually file them, like you always did :)21:16
eglynnis the wiki updated to describe the user visible aspects of the new process?21:17
*** dprince has quit IRC21:17
ttx#action ttx to add "this is an automated message" to the whiteboard warning21:17
eglynn... i.e. that the filing of a BP in LP will now be a drivers/PTL action *after* the corresponding action has landed21:17
ttxeglynn: unfortunately, not. It's on my TODO list, hope to do it tomorrow21:17
eglynnttx: cool, thanks!21:17
eglynn... corresponding *spec has landed21:18
*** jaycaz has quit IRC21:18
ttx#topic Sahara-dashboard to Horizon merge progress21:18
*** jaycaz has joined #openstack-meeting21:18
*** openstack changes topic to "Sahara-dashboard to Horizon merge progress (Meeting topic: project)"21:18
ttxSergeyLukjanov: floor is yours21:18
*** rodrigods_ has quit IRC21:18
SergeyLukjanovttx, thanks21:18
*** nedbat has quit IRC21:19
SergeyLukjanovso, the current progress is near to 021:19
*** edmund1 has joined #openstack-meeting21:19
*** nedbat has joined #openstack-meeting21:19
SergeyLukjanovmostly all patches are under review21:19
SergeyLukjanovbut there is a lack of reviews to make them all landed in juno21:19
eglynnSergeyLukjanov: are the patches getting reviewer traction?21:19
eglynnk21:20
SergeyLukjanovI presume crobertsrh is here, he is doing this work from sahara side21:20
crobertsrhYes, I am here.21:20
*** edmund has quit IRC21:20
ttxmrunge is here for Horizon21:20
eglynnI think david-lyle is on vacation21:20
SergeyLukjanovcrobertsrh, cool, any details?21:20
mrungeyes, correct21:20
*** markmc has quit IRC21:20
crobertsrhReviewer traction has increased a bit today, but we haven't seen much action from the cores yet.21:20
mrungeit seems like most Horizon cores are quite busy with other stuff21:21
mrungeand we have an insane queue of patches to review in horizon21:21
mrungethat the sad status21:21
*** patelna has joined #openstack-meeting21:22
mrungethat's ^21:22
SergeyLukjanovheh, I understand21:22
*** jprovazn has quit IRC21:22
* fungi thinks we all know what that's like21:22
SergeyLukjanovwe've agreed on design summit that if we'll not be able to merge sahara-dashboard into horizon in j2 timeframe21:23
* jgriffith sighhs21:23
SergeyLukjanovthan we'll need to rollback to the separate repo for juno release21:23
*** moha_hunt has joined #openstack-meeting21:23
*** nedbat has quit IRC21:23
*** nedbat has joined #openstack-meeting21:23
*** vivek-ebay has quit IRC21:23
SergeyLukjanovmrunge, do you have any suggestions for improving the review process?21:24
lchengcrobertsrh: is it possible to have a recorded demo of sahara to help reviewers visualize how it should look (I'm not sure how easy it is to setup sahara in devstack)21:24
*** tbarron has quit IRC21:24
*** banix has quit IRC21:24
SergeyLukjanovdocs for running / testing horizon with sahara were requested initially and AFAIK crobertsrh shared them21:24
crobertsrhlcheng:  There are a couple of videos on youtube.  I will try to find them for you.21:24
SergeyLukjanovlcheng, I have a screencast recorded for icehouse release somewhere, I'll find it and share21:25
lchengcrobertsrh: awesome, just add the links on the BP21:25
lchengSergeyLukjanov: thanks!21:25
SergeyLukjanovttx, are you ok with rollback plan?21:26
SergeyLukjanovmrunge, thanks for +2ing sahara patch ;)21:26
*** jaypipes has quit IRC21:26
crobertsrhmrunge, that made my day :)21:27
mrungeSergeyLukjanov, crobertsrh that's just one +221:27
ttxI think it's very important to expose the integrated functionality in horizon21:27
mrungeand you just dropped off 8k lines of code21:27
crobertsrhI'm easy to please21:28
ttxit's a major new feature of Juno Horizon21:28
eglynnare those 8 KLOCs nicely split up?21:28
*** malini1 has joined #openstack-meeting21:28
*** changbl has quit IRC21:28
crobertsrh9 or 10 patch sets.  Generally 1 new panel per patch21:28
eglynn... or just a few monolithic patches?21:28
eglynnk21:28
ttxif it's not landed by j-2 then yes, probably better to ship it separately21:28
fungi~1000 loc per patch is still pretty huge21:28
*** thangp has quit IRC21:28
ttxbut we should try our best to have it in by then21:28
mrungeI still think, we should be able to merge21:28
*** changbl has joined #openstack-meeting21:29
mrungegiven, that reviewers will do their duties21:29
*** jaypipes has joined #openstack-meeting21:29
SergeyLukjanovmrunge, ttx, yup, I still think that we'll be able to do it too21:29
ttxSergeyLukjanov, mrunge: we should watch progress there from time to time, don't hesitate to raise it again at future meetings21:29
eglynn... so is the train of patches to be gated on a -2'd sentinel patch?21:29
*** adalbas has quit IRC21:29
*** vivek-ebay has joined #openstack-meeting21:29
eglynn... so that either all or none land by juno-2?21:29
mrungerollback?21:29
eglynn(... in the style of the recent swift approach)21:30
mrungethere were a bunch of minors until now21:30
* zaneb disappears21:30
mikalYou could try the approach we're planning for the nova ironic driver21:30
ttxeglynn: I think the current thinking is to roll them back. They are guarded by a feature switch IIUC21:30
mikalBuild a chain of patches, with the first one having a -221:30
eglynnhttp://openstack.10931.n7.nabble.com/Swift-storage-policies-merge-plan-td41512.html21:30
SergeyLukjanovttx, ack, I'm monitoring the progress21:30
mikalOnce all the rest of the chain is approved, remove that first -221:30
mikalThey merge as a block21:31
eglynn^^^ that's the swift approach I mentioned21:31
mikalOh nice21:31
mikalI thought we'd invented it21:31
mikal:P21:31
fungiyeah, infra has done that a few times in the past for similar situations as well21:31
*** rockyg has left #openstack-meeting21:31
fungii think it's convergent evolution21:31
*** pdmars has joined #openstack-meeting21:31
*** amcrn has quit IRC21:31
eglynn"convergent evolution" ... /me likee :)21:32
SergeyLukjanovmrunge, could horizon split affect sahara merge to horizon?21:32
*** flaper87 is now known as flaper87|afk21:32
*** jtomasek has quit IRC21:32
*** patelna has quit IRC21:32
mrungeSergeyLukjanov, in theory: no21:32
notmynamewe're actually going to try to end up with one merge commit to gate. to avoid weeks-to-months in the gate to land the chain21:32
*** kevinconway has quit IRC21:32
*** jtomasek has joined #openstack-meeting21:32
eglynnseems like a neat idea, whoever invented it21:32
*** vivek-ebay has quit IRC21:33
*** vivek-ebay has joined #openstack-meeting21:33
fungiyeah, it's worth noting we've seen gerrit's jgit behave badly on dependent patch series >~4-5 changes. it will just arbitrarily claim it ran into merge conflicts. i think there's an upstream bug reported but not sure of the status21:33
mrungeSergeyLukjanov, you're just putting code to openstack_dashboard, not to horizon dir. that shouldn't be affected at all by horizon split21:33
SergeyLukjanovmrunge, that's cool21:33
ttxok, anything more on atht topic ? We should revisit it every 2 or 3 meetings to make sure we are all in sync21:34
ttxSergeyLukjanov: I'll let you put it back on the agenda regularly ;)21:34
*** nati_ueno has joined #openstack-meeting21:35
ttx#topic Open discussion21:35
*** openstack changes topic to "Open discussion (Meeting topic: project)"21:35
SergeyLukjanovttx, ok, thx21:35
mrungeSergeyLukjanov, probably you guys should show up on the Horizon weekly meetings as well21:35
mesterySo, I wanted to discuss the "ssh timeout" issue here.21:35
mesteryhttps://bugs.launchpad.net/neutron/+bug/132365821:35
uvirtbotLaunchpad bug 1323658 in nova "SSH EOFError - Public network connectivity check failed" [Undecided,New]21:35
SergeyLukjanovmrunge, crobertsrh is attending them AFAIK21:35
*** zaneb has quit IRC21:35
mesteryI put some comments in the bug, but it looks like in the cases I've examined, the guest VM never comes back from a resize/restart.21:35
mesteryWas hoping to get some nova eyes on that bug. :)21:35
crobertsrhYes, I attend them21:35
ttxmikal: ^?21:36
crobertsrhI'll try to be more vocal21:36
mikalWhat version of libvirt are we running in the gate now?21:36
sdaguemikal: just be aware that if you drop a ton of patches all at once into the gate - you do a mini dos attack21:36
*** pdmars has quit IRC21:36
mesteryMyself, armax and salv-orlando spent a lot of time debugging that over the past week and a half to get to this point. :)21:36
mikalmestery: I think you might need to start an openstack-dev thread about that if you haven't already21:36
*** jdob has quit IRC21:36
mikalmestery: I don't have an answer off the top of my head21:37
mesterymikal: Will do, I'll start that after the meeting.21:37
sdagueoh, we should get mriedem in here21:37
mesterymikal: OK, thanks!21:37
mikalmestery: although we've seen some weird behaviour with snapshots in our ancient version of libvirt21:37
*** jaypipes has quit IRC21:37
sdaguethe sneaking suspicion at this point is it's floating ip related21:37
mikalmestery: I wonder if this is similar21:37
mesterymikal: I was suspecting an older version of libvirt possibly as well.21:37
*** neelashah has quit IRC21:37
sdagueand it times with when ceilometer landed a floating ip polling patch21:37
sdaguewhich causes tracebacks in n-api21:38
mesteryThe logs all show neutron has set everyting up.21:38
mesterywhen I added a console dump of the guest when the failurie is hit, there is no console output in the return value. :)21:38
*** sarob has joined #openstack-meeting21:38
ttxmestery: if we can't blame neutron anymore for all weird issues...21:38
mesteryttx: :P21:38
*** sweston has quit IRC21:40
ttxmestery: we won't get to a solution in the meeting, so yes, raising a ML thread about it should help getting nova eyes on it. This is a major offender so hopefully it should get people attention21:40
ttxAnything else, anyone ?21:41
mesteryttx: Doing it now in fact. Thanks!21:41
jgriffithttx: your script works wonderfully!21:41
* ttx quicklooks the gate21:41
ttxjgriffith: as in people blame me instead of you ?21:41
jgriffithttx: now if it can just hit people over the head with a virtual hammer when they retarget something after it's run21:41
jgriffithttx: haha!21:41
jgriffithttx: another advantage I hadn't thought of21:42
fungijgriffith: you need to come at them with a clue-by-four21:42
jgriffithfungi: LOL21:42
notmynamettx o/21:42
jgriffithfungi: I should be careful, lest I'm hit with one myself21:42
*** sarob has quit IRC21:43
ttxeglynn: is hbase-events-feature completed by the merging of https://review.openstack.org/#/c/91408/ ?21:43
ttxnotmyname: shoot21:43
eglynnttx: yes, it sure is21:43
ttxok will mark it implemented21:43
notmynameas we've been using a feature branch in swift, I'd like to propose a summit session on using feature branches as a common thing (as opposed to squashed branches as one patch). something to discuss in paris21:44
notmynameerr...to rephrase, we've used one feature branch. it has advantages and disadvantages21:44
*** henrynash has quit IRC21:44
ttxnotmyname: ok, hopefully we'll remember that by then :)21:44
* eglynn wonders why the LP auto-update didn't kick in when the patch landed ...21:44
notmynamettx: I'll remind you. we'll have one for the erasure code work anyway21:44
*** elo has quit IRC21:45
ttxeglynn: I don't think we have such a thing21:45
*** ItSANgo has joined #openstack-meeting21:45
*** ItSANgo_ has joined #openstack-meeting21:45
*** elo has joined #openstack-meeting21:45
eglynnttx: ... a-ha, /me was thinking of LP bugs21:46
*** vijendar has quit IRC21:46
ttxok, looks like we don't have anything else to discuss21:46
ttxat least for today21:46
ttxso...21:47
ttx#endmeeting21:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:47
openstackMeeting ended Tue Jun 10 21:47:09 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2014/project.2014-06-10-21.03.html21:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2014/project.2014-06-10-21.03.txt21:47
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2014/project.2014-06-10-21.03.log.html21:47
eglynngood night all!21:47
ttxThanks everyone21:47
mesteryThanks ttx!21:47
mikal:)21:47
*** jecarey has quit IRC21:47
*** eglynn has quit IRC21:48
SergeyLukjanovttx, thx!21:49
*** crobertsrh is now known as _crobertsrh21:49
*** _crobertsrh has left #openstack-meeting21:50
*** ramashri has joined #openstack-meeting21:50
*** lcostantino has quit IRC21:51
*** elo has quit IRC21:51
*** elo1 has joined #openstack-meeting21:52
*** dims__ has joined #openstack-meeting21:52
*** thuc has joined #openstack-meeting21:52
*** elo has joined #openstack-meeting21:53
*** hrybacki has quit IRC21:53
*** sushils_ has quit IRC21:53
*** dims_ has quit IRC21:54
*** dhellmann has quit IRC21:55
*** ramashri_ has joined #openstack-meeting21:55
*** ramashri has quit IRC21:55
*** dhellmann has joined #openstack-meeting21:55
*** nedbat has quit IRC21:56
*** mrunge has quit IRC21:56
*** hrybacki_ has quit IRC21:57
*** elo1 has quit IRC21:58
*** kebray has joined #openstack-meeting21:59
*** elo1 has joined #openstack-meeting21:59
*** bauzas has joined #openstack-meeting21:59
*** changbl has quit IRC22:00
*** thuc has quit IRC22:01
*** elo1 has quit IRC22:02
*** vpanizo has joined #openstack-meeting22:03
*** nedbat has joined #openstack-meeting22:04
*** egallen has quit IRC22:05
*** nedbat has quit IRC22:05
*** elo1 has joined #openstack-meeting22:06
*** marcoemorais has quit IRC22:08
*** elo has quit IRC22:10
*** nati_ueno has quit IRC22:14
*** AlanClark has quit IRC22:15
*** thuc has joined #openstack-meeting22:17
*** rossk has quit IRC22:18
*** thuc_ has joined #openstack-meeting22:19
*** denis_makogon has quit IRC22:19
*** kayaliu_ has joined #openstack-meeting22:19
*** jtomasek has quit IRC22:20
*** bknudson has quit IRC22:22
*** thuc has quit IRC22:22
*** VijayB_ has joined #openstack-meeting22:23
*** MaxV has joined #openstack-meeting22:23
*** VijayB_ has quit IRC22:24
*** betsy has quit IRC22:27
*** MaxV has quit IRC22:28
*** Sukhdev has quit IRC22:29
*** Sukhdev has joined #openstack-meeting22:29
*** MaxV has joined #openstack-meeting22:29
*** MaxV has quit IRC22:29
*** VijayB has joined #openstack-meeting22:29
*** VijayB has quit IRC22:30
*** moha_hunt has quit IRC22:31
*** hemna has quit IRC22:31
*** mspreitz has joined #openstack-meeting22:32
*** nati_ueno has joined #openstack-meeting22:32
*** zns has joined #openstack-meeting22:33
*** gduan has joined #openstack-meeting22:34
*** garyduan has quit IRC22:34
*** ivar-lazzaro1 has quit IRC22:36
*** ttrifonov is now known as ttrifonov_zZzz22:37
*** hemna has joined #openstack-meeting22:38
*** zns_ has joined #openstack-meeting22:38
*** zns has quit IRC22:38
*** sarob has joined #openstack-meeting22:38
*** vkmc_ has joined #openstack-meeting22:39
*** sarob has quit IRC22:42
*** vkmc has quit IRC22:43
*** thedodd has quit IRC22:43
*** VijayB has joined #openstack-meeting22:44
*** bauzas has quit IRC22:44
*** thuc has joined #openstack-meeting22:45
*** thuc_ has quit IRC22:45
*** zns has joined #openstack-meeting22:46
*** ArxCruz has joined #openstack-meeting22:46
*** Guest26452 has quit IRC22:48
*** zns_ has quit IRC22:49
*** igordcard has quit IRC22:50
*** marekd is now known as marekd|away22:59
*** elo has joined #openstack-meeting22:59
*** mspreitz has quit IRC22:59
*** KurtRao has quit IRC23:00
*** KurtRao has joined #openstack-meeting23:00
*** fnaval has quit IRC23:00
*** elo has quit IRC23:01
*** VijayB has quit IRC23:01
*** fnaval has joined #openstack-meeting23:01
*** vivek-ebay has quit IRC23:01
*** VijayB has joined #openstack-meeting23:01
*** thuc has quit IRC23:03
*** thuc has joined #openstack-meeting23:03
*** bogdando has quit IRC23:04
*** radez is now known as radez_g0n323:04
*** dane_leblanc has quit IRC23:05
*** fnaval has quit IRC23:05
*** jaycaz has quit IRC23:06
*** VijayB has quit IRC23:06
*** jaycaz has joined #openstack-meeting23:06
*** dims__ has quit IRC23:06
*** bogdando has joined #openstack-meeting23:07
*** julienvey has quit IRC23:07
*** jaycaz has quit IRC23:08
*** zns has quit IRC23:08
*** dims__ has joined #openstack-meeting23:08
*** dane_leblanc has joined #openstack-meeting23:09
*** nati_ueno has quit IRC23:10
*** edmund1 has quit IRC23:12
*** zns has joined #openstack-meeting23:13
*** dstanek is now known as dstanek_zzz23:13
*** vivek-ebay has joined #openstack-meeting23:15
*** atiwari has quit IRC23:16
*** zaneb has joined #openstack-meeting23:17
*** zns has quit IRC23:18
*** gokrokve has quit IRC23:19
*** reed_ has joined #openstack-meeting23:21
*** tvoran has quit IRC23:21
*** reed has quit IRC23:22
*** emagana has quit IRC23:22
*** kayaliu_ has quit IRC23:24
*** reed_ has quit IRC23:27
*** hrybacki has joined #openstack-meeting23:27
*** bdpayne has quit IRC23:33
*** bdpayne has joined #openstack-meeting23:34
*** Mandell has quit IRC23:34
*** kgriffs is now known as kgriffs|afk23:35
*** zaneb has quit IRC23:37
*** Mandell has joined #openstack-meeting23:38
*** sarob has joined #openstack-meeting23:38
*** jmontemayor has quit IRC23:39
*** thuc has quit IRC23:39
*** reed_ has joined #openstack-meeting23:39
*** cvbock has quit IRC23:39
*** thuc has joined #openstack-meeting23:39
*** kun_huang has joined #openstack-meeting23:41
*** ArxCruz has quit IRC23:41
*** sarob has quit IRC23:43
*** vkmc_ has quit IRC23:43
*** thuc has quit IRC23:43
*** oda-g has joined #openstack-meeting23:44
*** jwang_ has quit IRC23:46
*** yamahata has quit IRC23:46
*** tomoe__ has joined #openstack-meeting23:47
*** thuc has joined #openstack-meeting23:48
*** lcheng has quit IRC23:49
*** tomoe_ has quit IRC23:50
*** tomoe__ has quit IRC23:51
*** tomoe_ has joined #openstack-meeting23:51
*** jwang_ has joined #openstack-meeting23:52
*** gokrokve has joined #openstack-meeting23:52
*** bogdando has quit IRC23:54
*** malini1 has left #openstack-meeting23:54
*** vermarah__ has quit IRC23:56
*** vermarah has quit IRC23:56
*** vermarah_ has quit IRC23:56
*** bogdando has joined #openstack-meeting23:57
*** kun_huang has quit IRC23:57
*** thuc has quit IRC23:57
*** vuil has quit IRC23:58
*** thuc has joined #openstack-meeting23:58
*** jwang_ has quit IRC23:58
*** cjellick has quit IRC23:59
*** cjellick has joined #openstack-meeting23:59

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