Tuesday, 2013-05-14

*** kebray has quit IRC00:00
*** dakang has quit IRC00:01
*** gyee has joined #openstack-meeting00:01
nati_uenopcm_: hi00:01
pcm_nati_ueno: hi00:02
nati_uenoOnly two guys?00:03
*** markmcclain has joined #openstack-meeting00:03
*** Swami has joined #openstack-meeting00:03
*** sacharya has joined #openstack-meeting00:03
nati_uenoSwami: hi could you update https://docs.google.com/a/ntti3.com/presentation/d/1J7k1eI13-3pQVwp5XgZDWPfzUvuSqczRdK0lEZKQOKk/edit#slide=id.gd3a78cf4_146 ?00:04
nati_uenofor your progress on the tasks00:04
nati_uenomarkmcclain: hi00:04
*** dakang has joined #openstack-meeting00:05
SwamiHi Mark, based on the blueprint and our discussions I have updated the Wiki with the API and CLI commands00:05
*** salv-orlando has quit IRC00:06
nati_uenoOk let's start meeting00:06
nati_ueno#startmeeting quantum_vpnaas00:06
openstackMeeting started Tue May 14 00:06:33 2013 UTC.  The chair is nati_ueno. Information about MeetBot at http://wiki.debian.org/MeetBot.00:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.00:06
*** openstack changes topic to " (Meeting topic: quantum_vpnaas)"00:06
nati_uenoah no00:06
openstackThe meeting name has been set to 'quantum_vpnaas'00:06
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"00:06
openstackMeeting ended Tue May 14 00:06:42 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)00:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/quantum_vpnaas/2013/quantum_vpnaas.2013-05-14-00.06.html00:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/quantum_vpnaas/2013/quantum_vpnaas.2013-05-14-00.06.txt00:06
openstackLog:            http://eavesdrop.openstack.org/meetings/quantum_vpnaas/2013/quantum_vpnaas.2013-05-14-00.06.log.html00:06
nati_ueno#startmeeting openstack_networking_vpn00:06
openstackMeeting started Tue May 14 00:06:56 2013 UTC.  The chair is nati_ueno. Information about MeetBot at http://wiki.debian.org/MeetBot.00:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.00:06
*** openstack changes topic to " (Meeting topic: openstack_networking_vpn)"00:06
openstackThe meeting name has been set to 'openstack_networking_vpn'00:07
nati_ueno#topic local_subnet vs local_cidr00:07
*** openstack changes topic to "local_subnet vs local_cidr (Meeting topic: openstack_networking_vpn)"00:07
nati_uenoso one minor point on api discussion is local_subnet vs local_cidr00:07
nati_uenoopenstack networking guys tend to +1 for local_cidr because subnet is already used in more general meanings00:08
nati_uenovpn guys tend to +1 for local_subnet because it is familiar with existing configrations00:08
nati_uenomarkmcclain: how do you think?00:09
markmcclainmy preference is for local_cidrs00:10
nati_uenome too00:10
markmcclainI know it is different from other implementations00:10
SwamiI am ok with local_cidrs00:10
nati_uenopcm_ : how do you think?00:10
pcm_nati_ueno: no real preference. StrongSwan seems to use left and right for local/remote. Not sure if that muddies it more.00:11
nati_uenopcm_: gotcha00:11
pcm_with subnet00:11
pcm_leftsubnet rightsubnet00:11
*** tomoe_ has quit IRC00:12
nati_uenoit is driver specific so it looks no problem00:12
SwamiBut as far we document in the help string, we can map it in the implementation00:12
*** tomoe_ has joined #openstack-meeting00:12
nati_uenoOK so let's go with local_cidr but may be we should discuss this again when Qin@VMware join the meeting.00:13
nati_uenoOK next topic00:13
markmcclainthe one question I do have to local subnets00:13
markmcclainthere should be a 1:1 for the cidr list and a tenants subnet correct?00:13
markmcclainso would it make more sense to accept a list of subnet ids?00:14
nati_uenoNo we should support small area of the subnet00:14
nati_uenoor aggregate of the subnets00:14
SwamiYes that was our proposal, peer_cidrs and local_cidrs will be a list of cidrs00:14
nati_uenolet's say if Subnet cidr is, we can also specify on vpn00:14
nati_uenoSwami: right00:15
nati_uenomarkmcclain: is this makes sence?00:15
markmcclainnati_ueno: I don't understand that use case00:15
nati_uenomarkmcclain: so sometimes, we want to expose only limited ips for vpn side00:16
nati_uenoor aggregate many tiny subnets for performance reason00:16
markmcclainaggregating a list of existing cidrs is easy00:16
*** tomoe_ has quit IRC00:17
Swamiyes we can aggregate and provide a single cidr that will accept all the subnets in the tenants network00:17
nati_uenoso let's numbering the usecase 1) sub area of subnet 2) aggregate multiple subnets00:18
nati_uenomarkmcclain: 1) don't make sense for you?  and 2) makes sense for you00:18
markmcclainAutomating #2 reduces the chance of errors00:19
nati_uenoOK for 1). may I ask why it doesn't make sense?00:19
nati_uenohow we Automating #2 ?00:21
markmcclainhave to think a bit more00:22
nati_uenomarkmcclain: gotcha.00:23
markmcclainbut it just seems odd that we're requiring a tenant to enter data00:23
markmcclainmultiple times00:23
nati_uenomarkmcclain: I agree for that point. may be client can accept subnet_id and translate it to the cidr00:24
Swamiin that case can we document and say enter the aggregate cidr for the peer and local subnets00:24
markmcclainnati_ueno: that approach supports the case of making local_cidrs a list of subnet_ids00:25
nati_uenomarkmcclain: we should think about cli namings00:26
*** BobBall has joined #openstack-meeting00:26
nati_uenomarkmcclain: but my intension is specifying subnet_id in local_cidrs on CLI00:26
*** IlyaE has quit IRC00:27
nati_uenoor may be we can hire local_subnet and accept both of subnet_id and cidrs00:27
markmcclainSwami: a vpnserviceconnection has a 1:1 with a VPNConneciton00:27
markmcclainthe VPNService can only have 1 subnet, so we'd be agg'ing only 1 subnet00:27
markmcclainnati_ueno: specifying a cidr on the CLI is ambigous00:28
SwamiYes that is true00:28
markmcclaina tenant can create two networks with the same cidr00:28
markmcclainwhich subnet would you match?00:28
nati_uenomarkmcclain: it don't matter, because we connect vpn to the router00:29
nati_uenomarkmcclain: And we can't plug overwrapping subnets for one router00:29
*** emagana has quit IRC00:29
markmcclainright but for referential integrity.. we need to know which subnet they want associated00:29
markmcclainotherwise the logic in the router becomes more complex00:30
nati_uenowhat's referential integrity?00:30
*** dolphm has joined #openstack-meeting00:30
markmcclainat the db layer how the models relate to each other00:30
*** stevebaker has quit IRC00:31
nati_uenoso some usecase requires different range of subnet's cidr.00:31
nati_uenoso we can't mapping it 1to100:31
nati_uenoI agree if we chooose subnet_id00:32
nati_uenowhen the subnet deleted, we can also update vpn config automatically00:32
nati_uenoit is clean00:32
*** markpeek has joined #openstack-meeting00:32
nati_uenohowever it limits the scope00:32
nati_uenoAnd also even if VPNService can only have 1 subnet, the associated router will be nexthops for multiple local subnets (cidrs)00:35
*** stevebaker has joined #openstack-meeting00:35
nati_uenoso using cidrs is simple way to support usecases ( #1 #2)00:35
*** bdpayne has quit IRC00:36
*** dhellmann is now known as dhellmann-away00:36
markmcclainthey'll work because the data is denormalized… but long term this might cause more problems00:37
markmcclainwe move forward with cidrs for now, but might make sense to revisit this00:37
*** openstack has joined #openstack-meeting00:41
*** ChanServ sets mode: +o openstack00:41
*** iccha_ has quit IRC00:41
nati_uenomarkmcclain: Thanks. Could you target the bp above?00:41
markmcclainnati_ueno: done00:42
nati_uenomarkmcclain: Thanks!00:42
nati_uenook next.  check default value for lifetime value (Swami)00:42
nati_uenoSwami: did you checked this one?00:42
Swaminachi: updated the document for the default Kilobytes.00:42
nati_uenoSwami: Thanks!00:42
nati_ueno Implement Data Model (Swami will push code to the gerrit)00:43
nati_uenoSwami: May I ask when you can push?00:43
Swaminachi: Yes I have to do some clean up and once done, I will push it to the gerrit for review00:43
nati_uenoSwami: in this week or next week?00:43
SwamiNachi: By the end of this week, it should be in gerrit, but it may not have the unit-tests covered.00:43
nati_uenoSwami: it is OK for now because it is WIP00:44
Swamigot it.00:44
nati_uenoso 5/20 is OK?00:44
SwamiYes let us target for 5/20.00:44
nati_uenoSwami: Thanks!00:44
nati_uenoImplement Driver (Nachi & PCM )00:45
nati_uenopcm_: do you have any progress?00:45
*** sandywalsh has quit IRC00:45
pcm_Just looked at StrongSwan docs. See they have example for net2net, psk. Assuming that is what we want to do first off right?00:45
pcm_They have example net http://www.strongswan.org/uml/testresults/ikev2/net2net-psk/00:46
SwamiI pcm if you need any pointers to Strongswan or sample configuration, let me know and I can provide it.00:46
*** RajeshMohan has quit IRC00:46
pcm_Swami: Can always use more info. Feel free to email me info.00:46
SwamiLook for IKEv1 examples for the first test case00:46
nati_uenoSwami: Thanks!00:47
pcm_I was going to try to set this up in VBOX.00:47
nati_uenoOK let's target driver for 5/31 since this one depends CRUD model00:47
pcm_Have four VMs, trying to figure out how to do the I/Fs.00:47
*** stevemar has joined #openstack-meeting00:47
nati_uenopcm_: gotcha00:47
nati_uenopcm_: 5/31 is OK for you also?00:47
pcm_nachi_ueno: Let me know if it makes sense to do a sample in VBOX for config.00:48
nati_uenopcm_: it sounds make sence00:48
pcm_nachi_ueno: Not sure, as I don't know how much there is to do (never have done a driver for OS). Will defer to your assesment.00:49
nati_uenopcm_: gotcha. if strongswan works, it is not difficult to write driver. it just RPC & and conf generation00:49
markmcclainDo we have a spec interface for the driver?00:49
nati_uenomarkmcclain: not yet. I'll propose it00:50
nati_uenoOK next00:50
nati_uenoCLI (python-quantum client) work (Swami will push code to the gerrit)00:51
nati_uenoSwami: this is 5/20 also?00:51
nati_uenoSwami: Thanks!!00:51
nati_ueno Write openstack network api document wiki (Sachin) <-- let's ask this next time00:51
nati_uenoDevstack support00:51
nati_uenoAny task takers?00:51
nati_uenook I'll take this for now00:51
markmcclainnati_ueno: it's hard to write devstack support until00:52
pcm_I can ask if someone on our team wants to help, if you'd like.00:52
markmcclainthere are rudimenatry steps to install the needed components00:52
nati_uenomarkmcclain: yeah, I agree. It will be may be late July00:52
nati_uenopcm_: thanks!00:52
nati_uenoOK if anyone interested in Horizon and Tempest, please let me know00:53
markmcclainfor LBaaS we kept a wiki with the installation instructions and then the devstack support became an afternoon project00:53
*** gyee has quit IRC00:53
*** jog0 has quit IRC00:53
nati_uenomarkmcclain: That's nice idea00:53
nati_uenomarkmcclain: Let's have installation instructions for VPN00:54
markmcclainit also helps the reviewers test00:54
nati_uenomarkmcclain: gotcha00:54
nati_uenomarkmcclain: I'll link the wiki when I submit strong swan driver00:54
markmcclainsounds good00:54
nati_uenoOK any other topics?00:55
pcm_nati_ueno: Offline maybe we can talk about VBOX emulation of the test setup I have.00:56
nati_uenopcm_: Gotcha. Are you in Bay Area? if so F2F is more efficient for this kind of task :)00:56
pcm_nati_ueno: Nope. East Coast :(00:57
pcm_Boston area00:57
nati_uenoOK let's talk on online. my skype is nati.ueno same for google+00:57
nati_uenoNext meeting is 5/16 Thursday at 5pm (PST) ( VMWare guy will join)00:58
pcm_Can do a phone call or WebEx possibly.00:58
pcm_oh ok.00:58
nati_uenopcm_: yes00:58
nati_uenopcm_: webex & phone call is OK too00:58
nati_uenomarkmcclain: the time is OK for you?00:58
markmcclainI'm a maybe for Thurs (it conflicts with the Atlanta OpenStack Meetup)00:59
markmcclainif the wifi is good.. I'll do both00:59
nati_uenoWhat's the time of Atlanta OpenStack Meetup>00:59
nati_uenoMay be we can change the time00:59
markmcclainthe meetup is 7pm eastern01:00
*** dolphm has joined #openstack-meeting01:00
nati_uenoOk let's schedule in the mail01:00
nati_uenoThank for your joining meeting!01:00
pcm_nati_ueno: FYI My skype is pc_michali01:00
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"01:00
openstackMeeting ended Tue May 14 01:00:58 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)01:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_networking_vpn/2013/openstack_networking_vpn.2013-05-14-00.06.html01:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_networking_vpn/2013/openstack_networking_vpn.2013-05-14-00.06.txt01:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_networking_vpn/2013/openstack_networking_vpn.2013-05-14-00.06.log.html01:01
nati_uenopcm_: Thanks!01:01
markmcclainhave a good evening01:01
*** markmcclain has quit IRC01:01
*** Swami has quit IRC01:02
*** zhuadl has joined #openstack-meeting01:02
*** dolphm has quit IRC01:05
*** alexpilotti has quit IRC01:06
*** markpeek has quit IRC01:09
*** danwent has quit IRC01:11
*** zhuadl has quit IRC01:11
*** dolphm has joined #openstack-meeting01:13
*** RajeshMohan has joined #openstack-meeting01:13
*** dolphm has quit IRC01:23
*** sandywalsh has joined #openstack-meeting01:23
*** stevebaker has quit IRC01:26
*** RajeshMohan has quit IRC01:28
*** RajeshMohan has joined #openstack-meeting01:29
*** stevebaker has joined #openstack-meeting01:32
*** terryg_ has quit IRC01:34
*** RajeshMohan has quit IRC01:36
*** RajeshMohan has joined #openstack-meeting01:37
*** anniec has quit IRC01:43
*** nati_ueno has quit IRC01:45
*** enikanorov has quit IRC01:46
*** yaguang has joined #openstack-meeting01:46
*** haleyb_ has left #openstack-meeting01:47
*** enikanorov has joined #openstack-meeting01:47
*** bmpbike has joined #openstack-meeting01:53
*** jbjohnso_ has quit IRC01:54
*** stevemar has quit IRC01:55
*** soulxu1304 has quit IRC02:00
*** tomoe_ has joined #openstack-meeting02:03
*** nati_ueno has joined #openstack-meeting02:06
*** lloydde has joined #openstack-meeting02:07
*** alexxu has joined #openstack-meeting02:10
*** bdperkin is now known as bdperkin_gone02:19
*** stevemar has joined #openstack-meeting02:22
*** stevemar has quit IRC02:24
*** stevemar has joined #openstack-meeting02:24
*** lloydde has quit IRC02:25
*** pcm_ has quit IRC02:29
*** zhuadl has joined #openstack-meeting02:35
*** amyt has joined #openstack-meeting02:36
*** amyt has joined #openstack-meeting02:37
*** vkmc has quit IRC02:42
*** dperaza has quit IRC02:44
*** HenryG_ has quit IRC02:48
*** markpeek has joined #openstack-meeting02:51
*** dakang has quit IRC03:02
*** bmpbike has quit IRC03:03
*** dcramer_ has quit IRC03:05
*** rkukura has left #openstack-meeting03:07
*** SergeyLukjanov has joined #openstack-meeting03:11
*** RajeshMohan has quit IRC03:15
*** RajeshMohan has joined #openstack-meeting03:16
*** dakang has joined #openstack-meeting03:25
*** dakang has quit IRC03:27
*** bdpayne has joined #openstack-meeting03:30
*** nati_ueno has quit IRC03:31
*** anniec has joined #openstack-meeting03:32
*** ladquin is now known as ladquin_ZzzZ03:34
*** dakang has joined #openstack-meeting03:35
*** novas0x2a|laptop has quit IRC03:35
*** lloydde has joined #openstack-meeting03:35
*** stevemar has quit IRC03:38
*** lloydde has quit IRC03:41
*** anniec_ has joined #openstack-meeting03:51
*** maoy has quit IRC03:53
*** Changbin has quit IRC03:53
*** anniec has quit IRC03:53
*** anniec_ is now known as anniec03:53
*** dakang has quit IRC03:58
*** anniec has quit IRC04:00
*** Mandell has joined #openstack-meeting04:02
*** zhuadl has quit IRC04:06
*** lloydde has joined #openstack-meeting04:08
*** emagana has joined #openstack-meeting04:11
*** SergeyLukjanov has quit IRC04:13
*** fifieldt has joined #openstack-meeting04:13
*** RajeshMohan has quit IRC04:17
*** RajeshMohan has joined #openstack-meeting04:18
*** dcramer_ has joined #openstack-meeting04:18
*** dakang has joined #openstack-meeting04:21
*** sacharya has quit IRC04:21
*** koolhead17 has joined #openstack-meeting04:25
*** koolhead17 has joined #openstack-meeting04:25
*** eharney has quit IRC04:26
*** danwent has joined #openstack-meeting04:27
*** dcramer_ has quit IRC04:32
*** lloydde has quit IRC04:33
*** koolhead17 has quit IRC04:33
*** SergeyLukjanov has joined #openstack-meeting04:41
*** boris-42 has joined #openstack-meeting04:41
*** dakang has quit IRC04:41
*** koolhead17 has joined #openstack-meeting04:46
*** nati_ueno has joined #openstack-meeting04:46
*** bdpayne has quit IRC04:47
*** lloydde has joined #openstack-meeting04:53
*** SergeyLukjanov has quit IRC04:54
*** emagana has quit IRC04:55
*** emagana_ has joined #openstack-meeting04:55
*** IlyaE has joined #openstack-meeting04:57
*** nati_ueno has quit IRC05:11
*** shri has joined #openstack-meeting05:12
*** shri has left #openstack-meeting05:12
*** bdpayne has joined #openstack-meeting05:14
*** egallen has quit IRC05:16
*** SergeyLukjanov has joined #openstack-meeting05:16
*** danwent has quit IRC05:18
*** nati_ueno has joined #openstack-meeting05:19
*** boris-42 has quit IRC05:31
*** cdub_ has quit IRC05:33
*** _ozstacker_ has quit IRC05:33
*** _ozstacker_ has joined #openstack-meeting05:34
*** Mandell has quit IRC05:44
*** emagana_ has quit IRC05:45
*** emagana has joined #openstack-meeting05:48
*** markpeek has quit IRC05:51
*** bdpayne has quit IRC05:52
*** SergeyLukjanov has quit IRC05:52
*** psedlak has joined #openstack-meeting05:53
*** reed has quit IRC05:55
*** resker has quit IRC06:03
*** esker has joined #openstack-meeting06:04
*** brucer has joined #openstack-meeting06:06
*** garyk has joined #openstack-meeting06:07
*** lukego has joined #openstack-meeting06:08
*** esker has quit IRC06:09
*** lloydde has quit IRC06:09
*** egallen has joined #openstack-meeting06:11
*** Mandell has joined #openstack-meeting06:11
*** lloydde has joined #openstack-meeting06:11
*** SumitNaiksatam has left #openstack-meeting06:15
*** emagana has quit IRC06:16
*** ogelbukh4 is now known as ogelbukh06:16
*** gitanshi has joined #openstack-meeting06:20
*** koolhead17 has quit IRC06:25
*** egallen has quit IRC06:27
*** boris-42 has joined #openstack-meeting06:29
*** IlyaE has quit IRC06:30
*** afazekas has joined #openstack-meeting06:31
*** afazekas_ has joined #openstack-meeting06:38
*** afazekas has quit IRC06:38
*** jcoufal has joined #openstack-meeting06:39
*** SergeyLukjanov has joined #openstack-meeting06:39
*** jcoufal has quit IRC06:39
*** jcoufal has joined #openstack-meeting06:40
*** lloydde has quit IRC06:41
*** flaper87 has joined #openstack-meeting06:41
*** lloydde has joined #openstack-meeting06:41
*** ttrifonov is now known as ttrifonov_zZzz06:43
*** boris-42 has quit IRC06:44
*** ttrifonov_zZzz is now known as ttrifonov06:44
*** lloydde has quit IRC06:46
*** boris-42 has joined #openstack-meeting06:48
*** alexxu has quit IRC06:50
*** pnavarro has joined #openstack-meeting06:55
*** mrunge has joined #openstack-meeting07:01
*** egallen has joined #openstack-meeting07:06
*** esker has joined #openstack-meeting07:07
*** lloydde has joined #openstack-meeting07:11
*** egallen has quit IRC07:12
*** lloydde has quit IRC07:21
*** smoser has quit IRC07:21
*** esker has quit IRC07:29
*** smoser has joined #openstack-meeting07:30
*** brucer has quit IRC07:31
*** pnavarro has joined #openstack-meeting07:32
*** pnavarro has quit IRC07:40
*** jtomasek has joined #openstack-meeting07:41
*** RajeshMohan has quit IRC07:44
*** RajeshMohan has joined #openstack-meeting07:44
*** zhuadl has joined #openstack-meeting07:49
*** Adri2000_ is now known as Adri200007:54
*** esker has joined #openstack-meeting07:55
*** salv-orlando has joined #openstack-meeting07:55
*** johnthetubaguy has joined #openstack-meeting07:56
*** lloydde has joined #openstack-meeting08:12
*** fifieldt has quit IRC08:16
*** lloydde has quit IRC08:17
*** zhuadl has quit IRC08:20
*** esker has quit IRC08:22
*** Mandell has quit IRC08:25
*** mkollaro has joined #openstack-meeting08:27
*** mkollaro has quit IRC08:32
*** mkollaro has joined #openstack-meeting08:33
*** pnavarro has joined #openstack-meeting08:34
*** enikanorov_ has joined #openstack-meeting08:37
*** ndipanov has quit IRC08:39
*** huats_ has joined #openstack-meeting08:42
*** huats_ has quit IRC08:42
*** huats_ has joined #openstack-meeting08:42
*** cody-somerville_ has joined #openstack-meeting08:44
*** enikanorov-w_ has joined #openstack-meeting08:46
*** esker has joined #openstack-meeting08:47
*** enikanorov has quit IRC08:49
*** cody-somerville has quit IRC08:49
*** huats has quit IRC08:49
*** enikanorov-w has quit IRC08:49
*** jhenner has joined #openstack-meeting08:59
*** sushils has joined #openstack-meeting09:04
*** alexpilotti has joined #openstack-meeting09:08
*** ndipanov has joined #openstack-meeting09:09
*** mkollaro has quit IRC09:10
*** egallen has joined #openstack-meeting09:11
*** lloydde has joined #openstack-meeting09:12
*** alexpilotti has quit IRC09:15
*** lloydde has quit IRC09:17
*** esker has quit IRC09:17
*** rwsu-away has quit IRC09:20
*** pnavarro has quit IRC09:20
*** tomoe_ has quit IRC09:21
*** mkollaro has joined #openstack-meeting09:24
*** asalkeld has quit IRC09:24
*** pnavarro has joined #openstack-meeting09:24
*** amotoki has quit IRC09:34
*** nati_ueno has quit IRC09:37
*** esker has joined #openstack-meeting09:46
*** garyk has quit IRC09:56
*** SergeyLukjanov has quit IRC09:58
*** pcm_ has joined #openstack-meeting10:02
*** esker has quit IRC10:09
*** garyk has joined #openstack-meeting10:12
*** lloydde has joined #openstack-meeting10:13
*** egallen has quit IRC10:14
*** lloydde has quit IRC10:18
*** esker has joined #openstack-meeting10:37
*** pcm_ has quit IRC10:44
*** pnavarro has quit IRC10:46
*** SergeyLukjanov has joined #openstack-meeting10:52
*** esker has quit IRC11:00
*** schwicht has joined #openstack-meeting11:01
*** pnavarro has joined #openstack-meeting11:01
*** esker has joined #openstack-meeting11:10
*** jang has joined #openstack-meeting11:10
*** lloydde has joined #openstack-meeting11:13
*** esker has quit IRC11:16
*** resker has joined #openstack-meeting11:18
*** lloydde has quit IRC11:18
*** resker has quit IRC11:23
*** pnavarro has quit IRC11:24
*** SergeyLukjanov has quit IRC11:25
*** SergeyLukjanov has joined #openstack-meeting11:25
*** alexpilotti has joined #openstack-meeting11:29
*** asalkeld has joined #openstack-meeting11:30
*** brucer has joined #openstack-meeting11:33
*** marun has quit IRC11:35
*** vkmc has joined #openstack-meeting11:38
*** vkmc has joined #openstack-meeting11:38
*** egallen has joined #openstack-meeting11:41
*** sandywalsh has quit IRC11:47
*** pcm_ has joined #openstack-meeting11:48
*** dolphm has joined #openstack-meeting11:56
*** maoy has joined #openstack-meeting11:58
*** maoy has quit IRC11:59
*** sandywalsh has joined #openstack-meeting12:01
*** sgordon__ has joined #openstack-meeting12:01
*** mrunge has quit IRC12:04
*** sgordon__ has quit IRC12:07
*** gitanshi_ has joined #openstack-meeting12:12
*** ameade_ has joined #openstack-meeting12:13
*** iccha_ has joined #openstack-meeting12:13
*** lloydde has joined #openstack-meeting12:14
*** gitanshi has quit IRC12:16
*** iccha has quit IRC12:16
*** shang has quit IRC12:16
*** torgomatic has quit IRC12:16
*** timello_ has quit IRC12:16
*** jpeeler has quit IRC12:16
*** ameade has quit IRC12:16
*** torgomatic has joined #openstack-meeting12:17
*** rnirmal has joined #openstack-meeting12:18
*** lloydde has quit IRC12:19
*** ladquin_ZzzZ is now known as ladquin12:20
*** timello_ has joined #openstack-meeting12:20
*** rnirmal has quit IRC12:20
*** rnirmal has joined #openstack-meeting12:21
*** jpeeler has joined #openstack-meeting12:21
*** rnirmal has quit IRC12:21
*** rnirmal has joined #openstack-meeting12:21
*** Yada has quit IRC12:22
*** tomoe_ has joined #openstack-meeting12:24
*** lukego has quit IRC12:24
*** adalbas has joined #openstack-meeting12:24
*** shang has joined #openstack-meeting12:25
*** lukego has joined #openstack-meeting12:25
*** dolphm has quit IRC12:27
*** tomoe_ has quit IRC12:29
*** egallen has quit IRC12:30
*** enikanorov-w has joined #openstack-meeting12:38
*** dolphm has joined #openstack-meeting12:39
*** ayoung has quit IRC12:39
*** NickChase has joined #openstack-meeting12:41
*** NickChase is now known as nickchase12:42
*** SergeyLukjanov has quit IRC12:43
*** schwicht has quit IRC12:47
*** enikanorov-w_ has quit IRC12:47
*** schwicht has joined #openstack-meeting12:48
*** dprince has joined #openstack-meeting12:48
*** yaguang has quit IRC12:53
*** sacharya has joined #openstack-meeting12:53
*** sld has joined #openstack-meeting12:53
*** dakang has joined #openstack-meeting12:55
*** amyt_ has joined #openstack-meeting12:56
*** nachi_ has quit IRC12:56
*** stevebaker has quit IRC12:56
*** stevebaker has joined #openstack-meeting12:57
*** nachi_ has joined #openstack-meeting12:57
*** pnavarro has joined #openstack-meeting12:57
*** amyt has quit IRC12:57
*** jimbaker` has quit IRC12:57
*** amyt_ is now known as amyt12:57
*** jimbaker has joined #openstack-meeting12:58
*** jimbaker has joined #openstack-meeting12:58
*** HenryG has joined #openstack-meeting12:59
*** writerDi_ has joined #openstack-meeting12:59
*** writer___ has joined #openstack-meeting13:00
annegentleanyone here for the Doc team meeting?13:01
annegentleraise your hand! o/13:01
* ladquin is13:01
annegentlehey ladquin!13:01
*** dakang has left #openstack-meeting13:01
ladquinhey annegentle!13:01
* annegentle sees if she remembers the meeting commands13:01
writer___my nickname keeps getting shorter - ha ha13:01
nickchasegood morning13:01
annegentle#startmeeting docwebteam13:02
openstackMeeting started Tue May 14 13:02:00 2013 UTC.  The chair is annegentle. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
* nickchase raises hand13:02
*** openstack changes topic to " (Meeting topic: docwebteam)"13:02
openstackThe meeting name has been set to 'docwebteam'13:02
annegentlewriter___: hee hee. Fill in the blank?13:02
ladquinmorning / evening /afternoon all13:02
*** sgordon has joined #openstack-meeting13:02
* sld raises hand.13:02
annegentlehey nickchase welcome!13:02
annegentlehi sld (short nick)13:02
nickchaseThanks anne13:02
annegentleOkay, the agenda is at https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting13:02
*** writer___ is now known as dianefleming13:02
annegentle#topic Previous action items13:03
*** openstack changes topic to "Previous action items (Meeting topic: docwebteam)"13:03
annegentlelast meeting's notes are at http://eavesdrop.openstack.org/meetings/docwebteam/2013/docwebteam.2013-04-09-13.00.html13:03
*** writerDi_ has quit IRC13:03
annegentleI had an action to add more info about 1.7.2 to the HowTo wiki page13:03
dianeflemingAren't we at 1.8.0 now?13:03
annegentleI added info about the Maven plugin, but we're already at 1.8.0 so I don't think I should document a specific version13:04
annegentledianefleming: yup13:04
*** SergeyLukjanov has joined #openstack-meeting13:04
annegentleSo, I added a section about the Maven plugin and edited a section and PDF, and so on.13:04
dianeflemingdoesn't david c keep release notes for each version? could we link to that?13:04
ladquinwere all poms migrated?13:04
annegentleAnd fixed a link to the release notes13:04
*** jasondotstar has joined #openstack-meeting13:04
annegentleladquin: yes, to 1.7.2, now we should move to 1.8.013:04
ladquinoh, ok, good13:05
annegentleladquin: though 1.8.0 is not as critical13:05
annegentleThe only other ACTION was to release Grizzly docs. DONE and Done and done.13:05
annegentle#topic Grizzly release13:05
*** openstack changes topic to "Grizzly release (Meeting topic: docwebteam)"13:05
*** matiu has quit IRC13:05
annegentleDoes anyone have any input/feedback/gripes about the Grizzly release (docs specifically?)13:05
annegentlehow did the DocImpact work for you? etc.13:06
sldI have some problems with inconsistencies in some areas (config and cli options, etc.), but that is already being worked on, as you know.13:06
dianeflemingI have some confusion about what to do with DocImpact bugs -13:07
annegentlesld: always need more consistency work13:07
annegentledianefleming: sure13:07
dianeflemingdo we have an official process?13:07
*** dhellmann-away is now known as dhellmann13:07
annegentledianefleming: yep, here: https://wiki.openstack.org/wiki/Documentation/HowTo#Using_the_DocImpact_Flag_in_a_Commit_Message13:07
annegentleI thought grizzly was a bear of a release. Ha. Kidding.13:08
dianeflemingIs there a way we could automate the creation of doc bugs from dev bugs? Once someone flags a bug as DocImpact, could a doc bug be autogenerated?13:08
dianeflemingthat would save a step13:08
sldlol annegentle13:08
annegentledianefleming: man that would be great. I bet the Launchpad API has something?13:09
ladquinhahah :P13:09
dianeflemingyeah, because the current process is extra work -13:09
annegentledianefleming: yeah it's very manual13:09
annegentledianefleming: and Tom (fifieldt) does it all more or less13:09
sldI can look at the doc bug autogeneration with tom...  ;-)13:10
annegentleI'll take an action item to ask ttx or the -infra team if they have ideas13:10
annegentlesld: that would be great too!13:10
annegentle#action: annegentle to ask ttx and -infra folks about DocImpact automation13:10
nickchaseThere is definitely an API to create a bug, so hopefully they should be able to do that.13:10
dianefleminganother issue I have is, once a new release is cut, I am not sure which bugs should be backported to earlier release13:10
annegentleIt would also be nice to stop cluttering up our mailing list with DocImpact13:10
ladquin+1 to that13:11
annegentledianefleming: right now, nearly all patches should be backported because nothing affects "only havanah" right now13:11
*** sacharya has quit IRC13:11
annegentledianefleming: at least, not that I've seen yet.13:11
dianeflemingis there a way to have a bug target more than one release?13:11
dianeflemingwell, some docs aren't release-specific - how do we handle those?13:12
*** alexpilotti has quit IRC13:12
annegentledianefleming: not that I know of, it means 2 patches in a single bug. The "Fix Released" automation doesn't care what branch a patch is on13:12
dianeflemingor the doc spans a few releases13:12
dianeflemingi guess what i'm saying is, is there a way to indicate in the bug that it applies to multiple releases? so that we know to backport it?13:12
annegentledianefleming: ok, then I suppose I mostly care about ones that are asked on the comments13:12
annegentledianefleming: no, not that I know of... we used review comments to request backports previously13:13
annegentledianefleming: and it's a judgement call13:13
slddianefleming: might be able to do that where you click on "also affects distribution" or "also affects project" on the bug page itself.13:13
*** dripton has joined #openstack-meeting13:13
*** stevemar has joined #openstack-meeting13:13
dianeflemingokay -13:13
annegentleokay, I'll move along13:14
annegentle#topic Doc titles consistency work13:14
*** openstack changes topic to "Doc titles consistency work (Meeting topic: docwebteam)"13:14
*** lloydde has joined #openstack-meeting13:14
annegentledianefleming has a series of patches to get consistency in the titles across the docs13:14
annegentlethis has been a huge job13:14
annegentlewell, huge, er, tedious?13:15
dianeflemingha - a little of both13:15
dianeflemingit took awhile to figure a few things out - the actual work is just tedious13:15
dianeflemingbut i'm almost done13:15
annegentleyeah. The bugs have the title changes, such as https://bugs.launchpad.net/openstack-manuals/+bug/117838813:15
uvirtbot`Launchpad bug 1178388 in openstack-manuals "openstack-manuals - update book titles for consistency: DEVELOPER GUIDES (specs)" [Medium,Fix released]13:15
annegentle#info Titles changing for consistency, review the patches13:16
annegentle#link https://bugs.launchpad.net/openstack-manuals/+bug/117838813:16
*** jecarey has joined #openstack-meeting13:16
dianeflemingyes, that bug links to a bunch of changes - each one needs to be reviewed separately, since they are all in different projects13:16
annegentle#link https://review.openstack.org/#/dashboard/244813:16
annegentleyeah I think that link ^^ shows a lot of them together13:17
*** koolhead17 has joined #openstack-meeting13:17
*** koolhead17 has joined #openstack-meeting13:17
annegentleany questions on the title consistencies?13:17
*** deagle has quit IRC13:17
annegentlehonestly the install guides were the toughest, https://bugs.launchpad.net/openstack-manuals/+bug/117707513:17
uvirtbot`Launchpad bug 1177075 in openstack-manuals "openstack-manuals - update book titles for consistency: INSTALLATION GUIDES" [Medium,Fix released]13:17
annegentleI'm still working on a patch that makes basic and advanced more clear13:18
*** deagle has joined #openstack-meeting13:18
annegentlethough install needs the deepest detanglement13:18
* koolhead17 joined late13:18
dianeflemingyes -13:18
annegentlehey koolhead1713:18
sldI can possibly help with the install docs, since I do a lot of that. ;-)13:18
annegentlesld: that would be awesome. I have a call this week with Cisco writers as well to help out13:19
koolhead17sld, would love to see you13:19
koolhead17hey annashen13:19
annegentlesld: it's tough to know how to coordinate, honestly, but we have to try'13:19
*** lloydde has quit IRC13:19
annegentlesld: let's meet this week, k?13:19
annegentle#action annegentle to set up meeting with sld to talk about install docs13:19
sldsounds good.13:19
annegentle#topic API site navigation and versions13:19
*** openstack changes topic to "API site navigation and versions (Meeting topic: docwebteam)"13:19
annegentleGreat feedback on the new navigation for the API reference page -- and the version numbers are helpful too.13:20
annegentleNice work!!13:20
ladquinnavigation is awesome13:20
annegentledianefleming rocked it13:20
dianeflemingthanks!! and thanks to david cramer13:21
annegentle#info API reference page has version numbers and navigation13:21
annegentle#link http://api.openstack.org/api-ref.html13:21
annegentleyes, thanks to dwramer too13:21
annegentleer. He's usually dwcramer? Anywho.13:21
ladquinyes :)13:21
sldawesome page... GJ....just bookmarked it.13:21
annegentleThe mailing list feedback was positive and Gabriel Hurley likes it.13:21
dianefleminggabriel has good taste13:22
annegentledianefleming also uncovered a bug with the way the api-specs.html page was getting overwritten.13:22
annegentleOkay, on to configuration reference info! Reference info abounds.13:22
annegentle#topic Auto-generated configuration reference tables13:22
*** openstack changes topic to "Auto-generated configuration reference tables (Meeting topic: docwebteam)"13:22
annegentleThere are several patches with newly-created configuration tables such as https://review.openstack.org/#/c/28903/13:23
annegentleBasically sld and Tom have been busy automators!13:23
annegentleChime in on the mailing list (or here is fine too) if you have questions or input13:23
annegentleI still want a walkthrough on where the strings come from so that I can patch the help strings.13:23
annegentleTom said he can do that, or maybe sld you and I can walk through it when we meet13:24
annegentleThe mappings (groupings) are set with https://github.com/fifieldt/autogenerate-config-docs/tree/master/flagmappings13:24
annegentleThat's what gives you each table13:24
annegentleAfter we have a good sense that the tables are complete, we'll incorporate them into references13:25
sldwell, those are partly done manually still, but a good part of it is automated...13:25
annegentlesld: yeah, the .flagmappings are maintained by hand13:25
*** lbragstad has joined #openstack-meeting13:25
annegentleone thing I wondered was, should the auto-gen code live in Oslo?13:25
annegentleis it worthwhile to ask Mark if that's a good location for it?13:25
annegentleor, does it belong in the docs repo13:26
sldi'm thinking the docs repo would be better ... at least when it is done.. since the goal is to update documentation with it.13:26
annegentle#info Automated configuration information will be pulled from each project13:26
annegentlesld: yep, makes sense then13:26
annegentleAnother thought is that we'll have to ensure translations can get picked up as well13:27
annegentlefor example, I saw that glance has .po files with the help text in them already13:27
annegentle(descriptions only would be candidate for translation, of course)13:27
annegentleI'll post to the mailing list with any other thoughts I come up with13:28
annegentlewhich naturally leads to the next topic...13:28
*** dperaza has joined #openstack-meeting13:28
annegentle# Restructure of docs13:28
annegentle#topic Restructure of docs13:28
*** openstack changes topic to "Restructure of docs (Meeting topic: docwebteam)"13:28
annegentleI mean :)13:28
annegentle#link https://blueprints.launchpad.net/openstack-manuals/+spec/restructure-documentation13:28
annegentleSo we have a blueprint13:29
annegentle#link https://wiki.openstack.org/wiki/Blueprint-restructure-documentation13:29
annegentleand we have a few people working on parts of it that I wanted to let people know about.13:29
annegentle1. dianefleming is working on User Guide, API Reference13:29
dianeflemingand api specifications (formerly known as api dev guides)13:30
annegentle2. sld and fifieldt are working on the definitive list of config options13:30
annegentledianefleming: yep13:30
*** alexpilotti has joined #openstack-meeting13:30
annegentlebut that also points out, I don't think the spec for the blueprint covers everything, Tom put it together as a starting point, and we need many many more details13:31
*** mrodden has joined #openstack-meeting13:31
annegentle3. I'm meeting with a few people this week about install13:31
dianeflemingi agree - i'd like to update it with some details - is that okay? or do I need to clear it with someone?13:31
*** sacharya has joined #openstack-meeting13:31
sldgo for it.13:31
sldi plan to do the same.13:31
annegentle3. nickchase is doing a content analysis of the "Admin Manuals"13:31
annegentledianefleming: yes, go for it, let's make that wiki page the place for our notes13:31
dianeflemingawesome - thx13:32
annegentleer that should have been 4. for nickchase :)13:32
annegentleThe Operations Guide is undergoing an O'Reilly review to hopefully publish through their channels, we're in the planning phase for that.13:32
koolhead17annashen, w00000t13:32
annegentleAnd I spoke to an architect yesterday who would like to work on the architecture half of that document as well.13:32
koolhead17annegentle, w00t13:32
koolhead17awesome news13:33
annegentleBut - it does mean we can only link to content in the Operations Guide (not xi:include it)13:33
annegentlekoolhead17: early stages, don't tweet it, it's not a done deal.13:33
*** amyt has quit IRC13:33
annegentleIt's not a secret either, just not fully baked.13:33
*** eharney has joined #openstack-meeting13:33
*** eharney has quit IRC13:33
*** eharney has joined #openstack-meeting13:33
*** SergeyLukjanov has quit IRC13:34
koolhead17annegentle, its just awesome!! :)13:34
annegentleSo, with all that knowledge, let's keep doing the What goes where? exercises to refactor!13:34
annegentleI don't really have anyone who wants to wrangle the "Developing OpenStack" content, but that's okay.13:34
sldwhat does that entail?13:35
annegentlemy priorities would be the install/config, user guide, etc.13:35
dianefleming"developing OpenStack"  - that's the Python book, right?13:35
*** sacharya has quit IRC13:35
annegentlesld: The "Developing OpenStack" content is all in RST in the separate project repos. Publishes to http://docs.openstack.org/developer/13:35
koolhead17annegentle, are we writing OS bible?13:35
annegentlebut has no overarching organization13:35
annegentlekoolhead17: heh13:35
annegentledianefleming: I don't know if it'll ever be a "book"13:36
*** SergeyLukjanov has joined #openstack-meeting13:36
dianeflemingyeah - i think it needs a good edit -13:36
annegentleboy howdy, yeah it does13:37
dianeflemingsome of the code doesn't work  - i can take that specific book on to test it13:37
dianeflemingand edit it13:37
*** ayurchen has quit IRC13:37
annegentleit's a ton of files across a bunch of repos, but might be a good cleanup effort.13:37
annegentleit is spring afterall, time for clean up :)13:37
dianeflemingyou can give me that developer stuff -13:37
dianeflemingthe python book and the RST stuff13:37
sldI can consolidate it all....13:37
sldok, n/m ... too late ;)13:38
annegentleI like it when two people want a task :)13:38
*** ayurchen has joined #openstack-meeting13:38
annegentlethe three of us could meet outside of this meeting to see what it would entaile13:38
dianeflemingha haha - i guess i haven't had my coffee yet13:38
annegentlethough really, the devs like to keep it their own, ya know? I've done patches that don't get accepted, etc.13:39
annegentleso I'd rather prioritize in "our" realm?13:39
dianefleminglet's you and I talk about it and see how to proceed?13:39
sldyea = keep things in this area.13:39
annegentleok, any questions on refactor?13:39
* koolhead17 loves title "OpenStack Bible"13:39
annegentle#topic open discussion13:39
*** openstack changes topic to "open discussion (Meeting topic: docwebteam)"13:39
annegentleWe didn't talk about translation this week but I think the work is still going on.13:40
dianeflemingay yi yi13:40
annegentleand we have a Japanese translator asking good Qs on the list.13:40
annegentleI'm going on a field trip to a local farm today so I'll be away for most of the "day" but back online later.13:41
annegentleThird graders are fun. Need coffee. :)13:42
ladquinquick comment about bug 117834313:42
uvirtbot`Launchpad bug 1178343 in openstack-manuals "Folsom doc links are difficult to guess (and get to through link nav)" [High,Confirmed] https://launchpad.net/bugs/117834313:42
ladquinSorry I didn't update this patch, but wanted to maybe take advantage of the meeting time to ask you:13:42
*** Yada has joined #openstack-meeting13:42
annegentleladquin: oh yeah13:42
ladquin I agree with Lorin's comments on consistency, but also one reason I like this layout is because it makes it very visibly clear you're not browsing a trunk doc page, but.. maybe that's just me.13:42
annegentleladquin: oh I see. Yeah the visual difference makes you know "we're not in Kansas anymore"13:42
ladquinIf you all prefer the current layout, I'll amend the patch now13:42
ladquinha, exactly13:43
annegentleladquin: I was thinking that a long, comprehensive listing, also indicates you're on a "special" one off page?13:43
annegentleladquin: by the time you like all the admin guides and isntall guides it'll look different :)13:44
annegentleladquin: but I was just happy you patched it!13:44
ladquinannegentle, like the one for trunk? (is it long?)13:44
ladquinso... shall I just use the current layout?13:45
annegentleladquin: there isn't a page like this yet... with all folsom books linked from it13:45
annegentleladquin: so you'd basically take the /run/ and /install/ pages and concatenate them13:45
*** ayurchen has quit IRC13:45
annegentleladquin: yeah I think so...13:45
ladquinok, will amend the patch and you can all review it13:45
annegentleladquin: thanks a bunch13:46
annegentleOk, I need to scurry to get on the bus to the farm. :)13:46
annegentleThanks all for attending, and talk more soon!13:47
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"13:47
openstackMeeting ended Tue May 14 13:47:09 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docwebteam/2013/docwebteam.2013-05-14-13.02.html13:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docwebteam/2013/docwebteam.2013-05-14-13.02.txt13:47
openstackLog:            http://eavesdrop.openstack.org/meetings/docwebteam/2013/docwebteam.2013-05-14-13.02.log.html13:47
ladquinthank you13:47
*** sld has left #openstack-meeting13:47
*** dianefleming has left #openstack-meeting13:48
*** ayoung has joined #openstack-meeting13:48
*** dcramer_ has joined #openstack-meeting13:51
*** markpeek has joined #openstack-meeting13:51
*** sgordon has left #openstack-meeting13:51
*** markmcclain has joined #openstack-meeting13:51
*** mrodden has quit IRC13:52
*** ladquin is now known as ladquin_brb13:55
*** rwsu has joined #openstack-meeting13:56
*** amyt has joined #openstack-meeting13:56
*** ayurchen has joined #openstack-meeting13:59
*** alexpilotti has quit IRC14:02
*** bdperkin_gone is now known as bdperkin14:03
*** SergeyLukjanov has quit IRC14:05
*** maoy has joined #openstack-meeting14:10
*** esker has joined #openstack-meeting14:11
*** mrunge has joined #openstack-meeting14:13
*** lloydde has joined #openstack-meeting14:15
*** lloydde has quit IRC14:20
*** jlucci has joined #openstack-meeting14:22
*** dripton_ has joined #openstack-meeting14:25
*** ameade has joined #openstack-meeting14:25
*** esker has quit IRC14:26
*** esker has joined #openstack-meeting14:27
*** esker has quit IRC14:30
*** johnthetubaguy1 has joined #openstack-meeting14:30
*** andreaf has joined #openstack-meeting14:31
*** ladquin_brb is now known as ladquin14:31
*** danwent has joined #openstack-meeting14:32
*** n0ano has joined #openstack-meeting14:32
*** jcoufal has quit IRC14:32
*** fesp has joined #openstack-meeting14:32
*** nachi__ has joined #openstack-meeting14:34
*** cp16net_ has joined #openstack-meeting14:35
*** markmcclain has quit IRC14:35
*** dripton has quit IRC14:35
*** lukego has quit IRC14:35
*** ameade_ has quit IRC14:35
*** enikanorov_ has quit IRC14:35
*** johnthetubaguy has quit IRC14:35
*** flaper87 has quit IRC14:35
*** afrittoli has quit IRC14:35
*** cdub has quit IRC14:35
*** jrcookli has quit IRC14:35
*** ogelbukh has quit IRC14:35
*** cp16net has quit IRC14:35
*** cp16net_ is now known as cp16net14:35
*** cdub has joined #openstack-meeting14:36
*** enikanorov has joined #openstack-meeting14:36
*** jrcookli has joined #openstack-meeting14:36
*** woodspa has joined #openstack-meeting14:36
*** hub_cap has joined #openstack-meeting14:37
*** jeblair_ has joined #openstack-meeting14:37
*** nikhil_ has joined #openstack-meeting14:37
*** Brainspa1kle has joined #openstack-meeting14:38
*** nikhil_ is now known as Guest2561214:38
*** crank_ has joined #openstack-meeting14:38
*** westmaas_ has joined #openstack-meeting14:40
*** maurosr- has joined #openstack-meeting14:41
*** bdperkin_ has joined #openstack-meeting14:41
*** westmaas_ has joined #openstack-meeting14:41
*** hub_cap_ has quit IRC14:42
*** jeblair has quit IRC14:42
*** nikhil has quit IRC14:42
*** carlp has quit IRC14:42
*** crank has quit IRC14:42
*** maurosr has quit IRC14:42
*** westmaas has quit IRC14:42
*** nachi has quit IRC14:42
*** sdake has quit IRC14:42
*** Brainspackle has quit IRC14:42
*** bdperkin has quit IRC14:42
*** bdperkin_ is now known as bdperkin14:42
*** westmaas_ is now known as westmaas14:42
*** crank_ is now known as crank14:42
*** koolhead17 is now known as koolhead17|afk14:45
*** sdake has joined #openstack-meeting14:48
*** sdake has joined #openstack-meeting14:48
*** jtomasek has quit IRC14:48
*** markmcclain has joined #openstack-meeting14:49
*** carlp has joined #openstack-meeting14:49
*** jhenner has quit IRC14:51
*** cdub has quit IRC14:55
*** jgallard has joined #openstack-meeting14:55
*** cdub has joined #openstack-meeting14:55
*** cp16net is now known as cp16net|away14:55
*** SergeyLukjanov has joined #openstack-meeting14:56
*** kebray has joined #openstack-meeting14:56
*** reed_ has joined #openstack-meeting14:57
*** Mandell has joined #openstack-meeting14:57
*** esker has joined #openstack-meeting14:58
*** cp16net|away is now known as cp16net14:59
*** armax has joined #openstack-meeting14:59
*** s_ has joined #openstack-meeting14:59
*** johnthetubaguy1 is now known as johnthetubaguy14:59
*** rerngvit has joined #openstack-meeting14:59
*** sushils has quit IRC15:00
n0ano#startmeeting scheduler15:00
openstackMeeting started Tue May 14 15:00:29 2013 UTC.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: scheduler)"15:00
openstackThe meeting name has been set to 'scheduler'15:00
rerngvithello all15:00
n0anoShow of hands, anyone here for the scheduler meeting?15:00
*** IlyaE has joined #openstack-meeting15:01
*** hartsocks has joined #openstack-meeting15:01
n0anoHmmm, rerngvit so far it looks like it's just you & I :-)15:01
rerngvitoh seems to be a busy day for everyone else15:02
*** cody-somerville_ is now known as cody-somerville15:02
n0anoI moved this weekend and only got internet back about 30 min ago15:02
rerngvitoh lucky you.15:02
n0anoyou better smile when you say that :-)15:03
rerngvitI did now15:03
rerngvitok more people, cool15:03
n0anoI only have half my machines up and I'll be routing cables for a week.15:03
rerngvithalf of your machines? Are you running a data center at home? :)15:04
n0anoAs I remember, we left off at `the future of the scheudler' and seemed to cover that pretty well15:04
*** sushils has joined #openstack-meeting15:04
rerngvityeah, we were going through the list15:04
n0anowe only have ntework bandwidth aware scheduling & ensembles to do a first pass over15:04
n0anounfortunately, I don't think the people involved in those two areas are here to day yet.15:04
rerngvitwhat should we do then?15:05
jgallardperhaps we can wait few minutes more?15:05
rerngvitok agree.15:05
n0anowell, if there's not burning issues, I'm willing to wait a few and then defer to next week.15:05
n0anoMy internet should be better so I can send out a proper meeting notice then also15:06
jgallardsounds good to me15:06
*** sacharya has joined #openstack-meeting15:07
rerngvitsound good to me as well15:07
alaskiI'm here, but distracted with other things15:07
n0anoOK, if there's no objections let's close for today (I'll take the blame for not sending out a notice) and we'll try to do better next week.15:08
jgallardn0ano, ok for me15:08
*** jeblair_ is now known as jeblair15:09
rerngvitok, but you should not take any blame, we made a schedule :)15:09
jgallardyes, no blame at all :)15:09
alaskiworks for me.  I just want to mention that I just posted https://review.openstack.org/#/c/29091/ as an indication of where I'm thinking the scheduler can be called from when it's a queryable entity.15:09
alaskistill WIP15:09
n0anoalaski, aah, the silent partner, OK let's try again next week, we should do better.15:10
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"15:10
openstackMeeting ended Tue May 14 15:10:23 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:10
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-05-14-15.00.html15:10
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-05-14-15.00.txt15:10
openstackLog:            http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-05-14-15.00.log.html15:10
*** openstack has joined #openstack-meeting15:47
*** hobana.freenode.net sets mode: +ns 15:47
*** hobana.freenode.net sets mode: -o openstack15:49
-hobana.freenode.net- *** Notice -- TS for #openstack-meeting changed from 1368546424 to 128266156415:49
*** hobana.freenode.net sets mode: +ct-s 15:49
*** dperaza has joined #openstack-meeting15:49
*** bdpayne has joined #openstack-meeting15:49
*** emagana has joined #openstack-meeting15:49
*** jang has joined #openstack-meeting15:49
*** mattray has joined #openstack-meeting15:49
*** yamahata__ has joined #openstack-meeting15:49
*** bdperkin has joined #openstack-meeting15:49
*** torgomatic has joined #openstack-meeting15:49
*** jrcookli_ has joined #openstack-meeting15:49
*** flaper87 has joined #openstack-meeting15:49
*** jcoufal has joined #openstack-meeting15:49
*** NobodyCam_ has joined #openstack-meeting15:49
*** dhellmann has joined #openstack-meeting15:49
*** asalkeld_ has joined #openstack-meeting15:49
*** dprince_ has joined #openstack-meeting15:49
*** jtomasek has joined #openstack-meeting15:49
*** sacharya has joined #openstack-meeting15:49
*** sushils has joined #openstack-meeting15:49
*** IlyaE has joined #openstack-meeting15:49
*** s_ has joined #openstack-meeting15:49
*** armax has joined #openstack-meeting15:49
*** kebray has joined #openstack-meeting15:49
*** SergeyLukjanov has joined #openstack-meeting15:49
*** cdub has joined #openstack-meeting15:49
*** carlp has joined #openstack-meeting15:49
*** sdake has joined #openstack-meeting15:49
*** westmaas has joined #openstack-meeting15:49
*** maurosr- has joined #openstack-meeting15:49
*** crank has joined #openstack-meeting15:49
*** Brainspa1kle has joined #openstack-meeting15:49
*** Guest25612 has joined #openstack-meeting15:49
*** jeblair has joined #openstack-meeting15:49
*** hub_cap has joined #openstack-meeting15:49
*** woodspa has joined #openstack-meeting15:49
*** enikanorov has joined #openstack-meeting15:49
*** cp16net has joined #openstack-meeting15:49
*** nachi__ has joined #openstack-meeting15:49
*** danwent has joined #openstack-meeting15:49
*** andreaf has joined #openstack-meeting15:49
*** johnthetubaguy has joined #openstack-meeting15:49
*** ameade has joined #openstack-meeting15:49
*** dripton has joined #openstack-meeting15:49
*** jlucci has joined #openstack-meeting15:49
*** maoy has joined #openstack-meeting15:49
*** ayurchen has joined #openstack-meeting15:49
*** amyt has joined #openstack-meeting15:49
*** rwsu has joined #openstack-meeting15:49
*** markpeek has joined #openstack-meeting15:49
*** ayoung has joined #openstack-meeting15:49
*** Yada has joined #openstack-meeting15:49
*** eharney has joined #openstack-meeting15:49
*** lbragstad has joined #openstack-meeting15:49
*** deagle has joined #openstack-meeting15:49
*** koolhead17|afk has joined #openstack-meeting15:49
*** jecarey has joined #openstack-meeting15:49
*** stevemar has joined #openstack-meeting15:49
*** jasondotstar has joined #openstack-meeting15:49
*** HenryG has joined #openstack-meeting15:49
*** jimbaker has joined #openstack-meeting15:49
*** pnavarro has joined #openstack-meeting15:49
*** nachi_ has joined #openstack-meeting15:49
*** stevebaker has joined #openstack-meeting15:49
*** schwicht has joined #openstack-meeting15:49
*** nickchase has joined #openstack-meeting15:49
*** dolphm has joined #openstack-meeting15:49
*** enikanorov-w has joined #openstack-meeting15:49
*** shang has joined #openstack-meeting15:49
*** adalbas has joined #openstack-meeting15:49
*** rnirmal has joined #openstack-meeting15:49
*** jpeeler has joined #openstack-meeting15:49
*** timello_ has joined #openstack-meeting15:49
*** iccha_ has joined #openstack-meeting15:49
*** sandywalsh has joined #openstack-meeting15:49
*** pcm_ has joined #openstack-meeting15:49
*** vkmc has joined #openstack-meeting15:49
*** brucer has joined #openstack-meeting15:49
*** garyk has joined #openstack-meeting15:49
*** mkollaro has joined #openstack-meeting15:49
*** ndipanov has joined #openstack-meeting15:49
*** cody-somerville has joined #openstack-meeting15:49
*** huats_ has joined #openstack-meeting15:49
*** salv-orlando has joined #openstack-meeting15:49
*** RajeshMohan has joined #openstack-meeting15:49
*** smoser has joined #openstack-meeting15:49
*** afazekas has joined #openstack-meeting15:49
*** psedlak has joined #openstack-meeting15:49
*** _ozstacker_ has joined #openstack-meeting15:49
*** BobBall has joined #openstack-meeting15:49
*** benonsoftware has joined #openstack-meeting15:49
*** gongysh has joined #openstack-meeting15:49
*** otherwiseguy has joined #openstack-meeting15:49
*** yuanz has joined #openstack-meeting15:49
*** ashwini has joined #openstack-meeting15:49
*** kmartin has joined #openstack-meeting15:49
*** samc_ has joined #openstack-meeting15:49
*** vipul has joined #openstack-meeting15:49
*** esmute has joined #openstack-meeting15:49
*** mikal has joined #openstack-meeting15:49
*** arosen has joined #openstack-meeting15:49
*** mdenny has joined #openstack-meeting15:49
*** zaro has joined #openstack-meeting15:49
*** SpamapS has joined #openstack-meeting15:49
*** asadoughi2 has joined #openstack-meeting15:49
*** bradjones has joined #openstack-meeting15:49
*** zigo has joined #openstack-meeting15:49
*** dragondm has joined #openstack-meeting15:49
*** jgriffith has joined #openstack-meeting15:49
*** adam_g has joined #openstack-meeting15:49
*** ladquin has joined #openstack-meeting15:49
*** davidhadas has joined #openstack-meeting15:49
*** DuncanT has joined #openstack-meeting15:49
*** frankm_ has joined #openstack-meeting15:49
*** sileht has joined #openstack-meeting15:49
*** juice has joined #openstack-meeting15:49
*** tr3buchet has joined #openstack-meeting15:49
*** lifeless has joined #openstack-meeting15:49
*** dkehn has joined #openstack-meeting15:49
*** chmouel has joined #openstack-meeting15:49
*** martine_ has joined #openstack-meeting15:49
*** dosaboy has joined #openstack-meeting15:49
*** jaypipes has joined #openstack-meeting15:49
*** alaski has joined #openstack-meeting15:49
*** markvoelker has joined #openstack-meeting15:49
*** hyakuhei_ has joined #openstack-meeting15:49
*** spn has joined #openstack-meeting15:49
*** zul has joined #openstack-meeting15:49
*** noslzzp has joined #openstack-meeting15:49
*** dansmith has joined #openstack-meeting15:49
*** blamar has joined #openstack-meeting15:49
*** toanster has joined #openstack-meeting15:49
*** sivel_ has joined #openstack-meeting15:49
*** swifterdarrell has joined #openstack-meeting15:49
*** kiall has joined #openstack-meeting15:49
*** devananda has joined #openstack-meeting15:49
*** al-maisan has joined #openstack-meeting15:49
*** jcooley has joined #openstack-meeting15:49
*** niska has joined #openstack-meeting15:49
*** termie has joined #openstack-meeting15:49
*** shengjie_ has joined #openstack-meeting15:49
*** med_ has joined #openstack-meeting15:49
*** ijw has joined #openstack-meeting15:49
*** mestery has joined #openstack-meeting15:49
*** jdurgin has joined #openstack-meeting15:49
*** rosmaita_ has joined #openstack-meeting15:49
*** creiht has joined #openstack-meeting15:49
*** guitarzan has joined #openstack-meeting15:49
*** russellb has joined #openstack-meeting15:49
*** fungi has joined #openstack-meeting15:49
*** clarkb has joined #openstack-meeting15:49
*** soren has joined #openstack-meeting15:49
*** Guest78415 has joined #openstack-meeting15:49
*** cyeoh_ has joined #openstack-meeting15:49
*** morganfainberg has joined #openstack-meeting15:49
*** dabo- has joined #openstack-meeting15:49
*** echohead_ has joined #openstack-meeting15:49
*** EntropyWorks has joined #openstack-meeting15:49
*** nijaba has joined #openstack-meeting15:49
*** ekarlso- has joined #openstack-meeting15:49
*** dendrobates has joined #openstack-meeting15:49
*** jamespage has joined #openstack-meeting15:49
*** sdague has joined #openstack-meeting15:49
*** sirushti has joined #openstack-meeting15:49
*** zynzel has joined #openstack-meeting15:49
*** Adri2000 has joined #openstack-meeting15:49
*** pleia2 has joined #openstack-meeting15:49
*** EmilienM has joined #openstack-meeting15:49
*** beagles has joined #openstack-meeting15:49
*** saschpe_ has joined #openstack-meeting15:49
*** ttx has joined #openstack-meeting15:49
*** oubiwann has joined #openstack-meeting15:49
*** dtroyer has joined #openstack-meeting15:49
*** Daviey has joined #openstack-meeting15:49
*** davidkranz has joined #openstack-meeting15:49
*** nsavin has joined #openstack-meeting15:49
*** notmyname has joined #openstack-meeting15:49
*** beyounn has joined #openstack-meeting15:49
*** tris has joined #openstack-meeting15:49
*** bgmccollum_ has joined #openstack-meeting15:49
*** belliott has joined #openstack-meeting15:49
*** evilroots has joined #openstack-meeting15:49
*** anteaya has joined #openstack-meeting15:49
*** briancline has joined #openstack-meeting15:49
*** annegentle has joined #openstack-meeting15:49
*** fsargent has joined #openstack-meeting15:49
*** primeministerp has joined #openstack-meeting15:49
*** kpepple_ has joined #openstack-meeting15:49
*** vishy has joined #openstack-meeting15:49
*** pvo has joined #openstack-meeting15:49
*** troytoma` has joined #openstack-meeting15:49
*** redthrux has joined #openstack-meeting15:49
*** rmk has joined #openstack-meeting15:49
*** anderstj has joined #openstack-meeting15:49
*** netapp has joined #openstack-meeting15:49
*** anniecheng has joined #openstack-meeting15:49
*** ctracey has joined #openstack-meeting15:49
*** yongli has joined #openstack-meeting15:49
*** akshayms has joined #openstack-meeting15:49
*** comstud has joined #openstack-meeting15:49
*** _cerberus_ has joined #openstack-meeting15:49
*** llu has joined #openstack-meeting15:49
*** uvirtbot` has joined #openstack-meeting15:49
*** kashyap has joined #openstack-meeting15:49
*** joearnold has joined #openstack-meeting15:49
*** hemnafk has joined #openstack-meeting15:49
*** radez_g0n3 has joined #openstack-meeting15:49
*** edleafe has joined #openstack-meeting15:49
*** obondarev has joined #openstack-meeting15:49
*** Kharec has joined #openstack-meeting15:49
*** branen has joined #openstack-meeting15:49
*** done__ has joined #openstack-meeting15:49
*** jd__ has joined #openstack-meeting15:49
*** harlowja has joined #openstack-meeting15:49
*** lcheng has joined #openstack-meeting15:49
*** alpha_ori has joined #openstack-meeting15:49
*** christophk has joined #openstack-meeting15:49
*** bcwaldon has joined #openstack-meeting15:49
*** annashen has joined #openstack-meeting15:49
*** mordred has joined #openstack-meeting15:49
*** jesusaurus has joined #openstack-meeting15:49
*** cburgess has joined #openstack-meeting15:49
*** ttrifonov has joined #openstack-meeting15:49
*** hobana.freenode.net changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"15:49
*** n0ano_ has joined #openstack-meeting15:50
*** asadoughi2 is now known as asadoughi15:51
*** psedlak has quit IRC15:52
*** esker has joined #openstack-meeting15:52
*** alexpilotti has joined #openstack-meeting15:53
*** lcestari has joined #openstack-meeting15:55
*** gokrokve_ has joined #openstack-meeting15:57
*** garyk has quit IRC15:58
*** emagana has quit IRC15:59
*** lcheng2 has joined #openstack-meeting15:59
*** yaguang has joined #openstack-meeting16:00
*** afazekas has quit IRC16:01
*** luis_fdez has joined #openstack-meeting16:06
*** kebray has quit IRC16:09
*** n0ano__ has joined #openstack-meeting16:09
gokrokve_Hi. Are we going to have a Hyper-V meeting?16:10
*** psedlak has joined #openstack-meeting16:10
*** n0ano_ has quit IRC16:10
*** hanney has joined #openstack-meeting16:10
*** danwent has quit IRC16:13
*** gongysh has quit IRC16:13
*** gyee has joined #openstack-meeting16:15
*** colinmcnamara has joined #openstack-meeting16:16
*** maurosr- is now known as maurosr16:20
*** afazekas has joined #openstack-meeting16:25
*** flaper87 has quit IRC16:26
*** esker has quit IRC16:29
*** kebray has joined #openstack-meeting16:29
*** dontalton has joined #openstack-meeting16:29
*** lloydde has joined #openstack-meeting16:32
*** asgreene has joined #openstack-meeting16:33
*** MarkAtwood has joined #openstack-meeting16:35
*** dolphm has quit IRC16:42
*** jang1 has joined #openstack-meeting16:43
*** dolphm has joined #openstack-meeting16:43
*** ogelbukh has joined #openstack-meeting16:43
*** jtomasek has quit IRC16:48
*** gokrokve_ has quit IRC16:49
*** done__ has left #openstack-meeting16:50
*** shengjie_ has quit IRC16:52
*** dolphm has quit IRC16:53
*** krtaylor has joined #openstack-meeting16:54
*** psedlak has quit IRC16:55
*** neelashah1 has joined #openstack-meeting16:56
*** marun has joined #openstack-meeting16:58
*** markwash has joined #openstack-meeting17:02
*** krtaylor has quit IRC17:07
*** Mandell has joined #openstack-meeting17:08
*** kirankv has joined #openstack-meeting17:09
*** koolhead17|afk has quit IRC17:09
*** mrunge has joined #openstack-meeting17:10
*** gokrokve has joined #openstack-meeting17:11
*** ladquin is now known as ladquin_afk17:13
*** kirankv has quit IRC17:14
*** markmcclain has joined #openstack-meeting17:15
*** kirankv has joined #openstack-meeting17:15
*** pabelanger has joined #openstack-meeting17:16
*** emagana has joined #openstack-meeting17:16
*** cp16net is now known as cp16net|away17:17
*** boris-42 has joined #openstack-meeting17:19
*** gokrokve has quit IRC17:19
*** luis_fdez has quit IRC17:20
*** kirankv has left #openstack-meeting17:21
*** litong has joined #openstack-meeting17:21
*** sivel_ is now known as sivel17:21
*** koolhead17|afk has joined #openstack-meeting17:22
*** markmcclain has quit IRC17:23
*** dolphm has joined #openstack-meeting17:24
*** mrunge has quit IRC17:26
*** nati_ueno has joined #openstack-meeting17:26
*** HenryG has quit IRC17:27
*** afazekas has quit IRC17:29
*** henrynash has joined #openstack-meeting17:29
*** n0ano__ has quit IRC17:30
*** dolphm has quit IRC17:33
*** pcm_ has quit IRC17:34
*** pcm__ has joined #openstack-meeting17:35
*** pleia2 has quit IRC17:42
*** pleia2 has joined #openstack-meeting17:42
*** hanney has quit IRC17:43
*** cp16net|away is now known as cp16net17:44
*** SergeyLukjanov has quit IRC17:44
*** epim has joined #openstack-meeting17:46
*** IlyaE has quit IRC17:49
*** rkanade has joined #openstack-meeting17:49
*** dcramer_ has joined #openstack-meeting17:51
*** dolphm has joined #openstack-meeting17:52
*** bknudson has joined #openstack-meeting17:55
*** atiwari has joined #openstack-meeting17:57
*** fabio has joined #openstack-meeting17:59
ayoung#topic https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting#Agenda_for_next_meeting17:59
henrynashhi all18:00
rkanadeHi all18:00
dolphmgyee: o/18:00
henrynashwho is that guy "all"…he's popular18:00
stevemarhello all18:00
rkanadei am Rohan Kanade :018:01
dolphmrkanade: welcome18:01
dolphm#startmeeting keystone18:01
openstackMeeting started Tue May 14 18:01:19 2013 UTC.  The chair is dolphm. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
openstackThe meeting name has been set to 'keystone'18:01
ayoung#link https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting#Agenda_for_next_meeting18:01
dolphmthe agenda is giant today18:01
*** Mandell has quit IRC18:01
bknudsonlet's just talk about ldap.18:01
dolphmand sort of a mess18:01
ayoungdolphm, yeah, that is my doing.  I girue I would make people aware of those isues, not expecting them to be resolved18:01
ayoungno, we can't just talk about LDAP18:02
dolphmsure we can ;)18:02
dolphmbut first18:02
rkanadeCan we get some feedback on https://review.openstack.org/#/c/2551718:02
gyeewow, dolphm, I forgot to add the pluggable token management to the agenda18:02
ayoungthere is a lot going on, and we need core to be engaged across the board18:02
dolphm#topic Havana milestone 118:02
gyeeI posted the code yesterday18:02
dolphm#link https://launchpad.net/keystone/+milestone/havana-118:02
dolphm#link https://wiki.openstack.org/wiki/Havana_Release_Schedule18:02
*** esker has joined #openstack-meeting18:02
dolphmjust an announcement/reminder- havana-m1 is about two weeks out, if you don't think a bp will make it, or are working on a bp should be targeted to m1, let me know18:03
*** afazekas has joined #openstack-meeting18:03
ayoungdolphm, so the anony binding is the riks issue there, since it isn't started18:03
bknudsonand I think topolino is on vacation?18:03
dolphmi believe the milestone will be forked on may 28th18:03
stevemarbknudson: yep, he is18:03
dolphm#topic High priority issues?18:03
*** afazekas has quit IRC18:04
dolphmanything not on the agenda already?18:04
ayoungbknudson, the actual impl is pretty small, can someone else from IBM pick it up?18:04
dolphmayoung: noted18:04
*** SergeyLukjanov has joined #openstack-meeting18:04
*** afazekas has joined #openstack-meeting18:04
bknudsontopol is the one with the minions. cat's away kind of thing.18:04
dolphmand no topol present18:04
ayoungand sahdev is gone, too18:04
dolphmi also remember it being a very simple bp18:04
bknudsonit should be like 10 lines of code.18:04
ayoungdolphm, for anonymous,  yeah, the one thing I asked is that instead of deducing anonymous, he make it an explicit enumeration value...I can take that one18:05
bknudsonI hate to promise to do something and then find I'm too busy, but I think I could pick it up.18:05
ayoungbknudson, do you have LDAP exp?18:05
bknudsonayoung: I've got some LDAP exp. Worked on IBM's server for a few years.18:05
*** anniec has joined #openstack-meeting18:05
ayoungif you take it, I can help you.18:05
dolphmbknudson: ayoung: first one to code review wins18:05
bknudsonok, I'll put it on my list.18:05
gyeewhich one?18:05
bknudsonI seem to be better about creating work than finishing it.18:06
dolphmbp keystone-ldap-anonymous-binding18:06
gyeeyeah, should be easy18:06
ayoungtoken flush is under review.  the one thing that might mitigate is if we get some agreement on the revoked token table18:07
dolphmbknudson: it'd be tough to beat ayoung's stream of consciousness blueprinting ;)18:07
ayoung#link https://review.openstack.org/#/c/28859/18:07
bknudsonI tend to report bugs.18:07
dolphm#topic High priority code reviews18:07
dolphmbknudson: nothing wrong with that!18:07
gyeedolphm, pluggable token management18:07
dolphm#link https://review.openstack.org/#/c/29021/18:08
dolphmgyee: ^18:08
*** maoy has quit IRC18:08
gyeeyeah, 1 KLOC worth of shit18:08
ayoungrkanade, I'll look after the meeting, promise18:08
*** maoy has joined #openstack-meeting18:09
ayoung#action ayoung to review  https://review.openstack.org/#/c/29021/ right after meeting18:09
rkanadethanks adam :)18:09
henrynashgyee: excellent progress on this…I'll go through it in detail18:09
ayoungthere it is in the notes!18:09
dolphmobviously code reviews for/blocking bp's have highest priority, so besides gyee's that also includes:18:09
dolphm#link https://review.openstack.org/#/c/28133/18:09
bknudsonwe've got competing fixes for the atomic problem... jay pipes had one too, I think.18:09
dolphm#link https://review.openstack.org/#/c/27881/18:09
dolphmbknudson: have links to those?18:09
rkanadeJay pipes review for atomic issue doesnt work18:09
dolphmrkanade: link to review?18:10
bknudson#link https://review.openstack.org/#/c/27507/18:10
rkanadementioned the issue on that review18:10
bknudsonjay pipes is abandoned.18:10
gyeecode review Tuesday, keep'em coming :)18:10
ayoungrkanade, aside from "user create needs to be atomic"  what bug is this really fixing?18:10
dolphmbknudson: not intentionally though18:10
*** dwaite has joined #openstack-meeting18:11
ayoungdon't have to answer here, but update the bug report with an actualy "this is causing problem blah..."18:11
rkanadeit is fixing other 4 apis too 1. update_user_project 2. delete_domain 3. delete_project 4. delete_user18:11
dolphmwhat is update_user_project?18:12
ayoungbecause, while I am sympathetic, LDAP is not going to play well.  And I don't think it is smart to treat sql as a more equal backend18:12
rkanadeit is an api call, it needs to be atomic18:12
dolphmayoung: +118:12
rkanadeall these are api calls which need to be atomic18:12
ayoungrkanade, understand, I am propsing that we split identity into 3 parts18:12
ayoungand so domains, users, and projects/roles might all be in 3 separate backends18:13
*** markmcclain has joined #openstack-meeting18:13
ayoungso, kiss your integrity constriants goodbye18:13
henrynashayoung: +118:13
*** maoy_ has joined #openstack-meeting18:13
*** maoy has quit IRC18:13
*** maoy_ is now known as maoy18:13
rkanade3 sql backend instances ?18:13
ayounggyee, if you quote me, I want full attribution18:13
ayoungrkanade, nope18:13
ayoungrkanade, I would see domains in a flat file, idenitity in LDAP, and projects in SQL18:14
ayoungbeing them most common impl  down the road18:14
rkanadeSo no sql backend for identity ?18:14
asgreenewhy split up into multiple stores before the single store models work?18:14
henrynashayoung: that's essentially what the bp: https://blueprints.launchpad.net/keystone/+spec/auth-domain-architecture18:14
ayoungrkanade, it will be there, but don't expect the calls to be atomic across domains, idenityt, and projects18:15
henrynashayoung: except that I don't necessarily agree that domains will be a flat file18:15
*** Mandell has joined #openstack-meeting18:15
*** vkmc has quit IRC18:15
rkanadeok, but that wont fix the atomicity issue right ?18:15
ayounghenrynash, sure18:15
ayoungrkanade, so long as it is atomic within a single backend, I am OK with it...but I roles assignments are going to be separate from users18:16
ayoung update_user_project can't be atomic18:16
rkanadei see18:16
ayoungdelete_user  probabny not either18:16
*** arosen has quit IRC18:16
ayoungdelete_domain  will span 3 backends18:16
henrynashasgreene: it's an issue of whether identity needs to be defined and tested…ie. where authentication and authorisation needs to take place….and it may well be in non-openstack systems18:16
*** afazekas has quit IRC18:16
bknudsonatomicity will still be problem, but the fix won't be "put it in a single db transaction"18:16
rkanadeok, i can fix issue for single backend for now , is the session code in the review alright?18:17
ayounghenrynash, to your point, domains will have multiple backends.  I just like the flat file cuz I'm a control freak18:17
ayoungand not a "flat" file, but kindof textured and bumpy and json like18:17
henrynashbknudson: agreed…we need to make a s/w resilient and expectant to find integrity issues18:17
rkanade@bknudson : can you provide some alternative ?18:17
dolphmbknudson: +118:17
*** arosen has joined #openstack-meeting18:17
henrynashayoung: :-)18:17
dolphmayoung: sounds like yaml18:18
*** eharney has quit IRC18:18
bknudsonrkanade: I don't think there's an obvious fix for it.18:18
*** vkmc has joined #openstack-meeting18:18
dolphmbknudson: +118:18
ayoungdolphm, btw, I'll communicate with jamielennox tonight, and we should have an updated token flush for tomorrow18:18
dolphmayoung: awesome, thanks18:18
dolphmayoung: i'm looking forward to that18:18
rkanadeany specific reason why db transactions arent ok?18:18
ayoungdolphm, maybe. Guess it is time to learn "yet another..."18:18
gyeeyay, token flush!18:19
ayoungrkanade, they are fine, just they can't span multiple backends18:19
ayoungrkanade, lets talk after this, and I can help you scope in the patch, ok?18:19
rkanadeok sure18:19
*** markmcclain has quit IRC18:19
ayoungdolphm, I'd like to target "split crednetials" for H118:19
ayoung#link https://review.openstack.org/#/c/28372/18:20
dolphmis there a bp?18:20
gyeespeaking of credentials, when are we migrating ec2_credential table over to credential?18:20
ayoungshould be fairly close.18:20
gyeeno reason to keep both18:20
ayoungdolphm, it is linked to a larger BP, but not one that would be completed for H1, so nevermind18:20
dolphmgyee: +118:20
ayounggyee, +118:21
ayounggyee, that might also help out with some of the issues we have with the ec2 middleware18:21
dolphmayoung: like what?18:21
gyeedolphm, ayoung, should I file a bp and get it done?18:21
dolphm#link https://review.openstack.org/#/c/27563/18:22
henrynashdolphm: how about: https://blueprints.launchpad.net/keystone/+spec/inherited-domain-roles18:22
dolphmgyee: that'd be great18:22
henrynashdolphm: I could get that done for H118:22
ayoungdolphm, thanks18:22
ayoungyeah waht are we doing about domains?18:22
ayounger, regions18:23
henrynashdolphm: although we haven't actually approved it18:23
dolphmhenrynash: let me know when you have an implementation, and if it looks like we can merge in h1, we'll bump it up?18:23
henrynashdolphm: ok18:23
gyeedolphm, what's the deal with this? https://review.openstack.org/#/c/27563/18:23
ayoungaside from termie are we all agreed that jaypipes bp is correct?18:23
dolphmhenrynash: direction is approved, just no spec or anything to approve the bp design18:23
ayoung#link https://blueprints.launchpad.net/keystone/+spec/first-class-regions18:23
gyeeI hate to agree with termie, but I think he's onto something18:24
dolphmhenrynash: spec == code review*18:24
* jaypipes had pretty much just given up on it all.18:24
*** n0ano has joined #openstack-meeting18:24
ayounghe did write up a doc spec18:24
henrynashdolphm: ;-)18:24
gyeeI like a general approach for endpoint lookups18:24
gyeean endpoint is just a url and a bunch a attributes18:24
ayoungis the "regions" abstraction general enough to cover all of the use cases we have?18:24
ayoungnamely:  what endpoints to link to a project, and so on?18:25
gyeewe should be able to construct any kind of filters18:25
*** markmcclain has joined #openstack-meeting18:25
dolphmayoung: it sounded like it was general enough for the discussions we had in the regions session18:25
gyeejust like LDAP filters18:25
dolphmjaypipes: since there's no impact on existing api's, i'm wondering if this should be an OS-REGION extension on top of v318:25
ayoungdolphm, yep, that was my take.18:25
ayoungdolphm, the one issue that has come up (and I think it covers) is for things that are not necessarily keystone concepts, like cells.18:26
dolphmjaypipes: and limit the implementation impact to it's own middleware18:26
*** jcoufal has quit IRC18:26
jaypipesdolphm: I don't see why it would be an extension... the concept is already in the existing API -- it's just not a first-class citizen.18:26
dolphmayoung: i don't think it's intended to overlap with cells, afaik18:26
dolphmayoung: just everyone's various interpretations of "regions" and availability zones18:27
ayoungdolphm, so, it was not intended to, but *could* it was the question18:27
jaypipesayoung: cells are private to an implementation -- i.e. they are not discoverable,.18:27
dolphmjaypipes: termie will certainly be much more agreeable if it's a discrete extension18:27
jaypipesayoung: in other words, a user can't ask that a resource be spun up in a cell.18:27
ayoungif we say that Regions is the abstraction for grouping resources, and ,if you ever need to expose something new, such as cells (in the future) I think there is a clear mapping18:27
ayoungjaypipes, not today. But what about tomorrow?18:28
jaypipesdolphm: extension of the service catalog or extension of the API in general?18:28
dolphmayoung: tenants/projects are the abstraction for grouping resources18:28
ayoungdolphm, but not by locale18:28
dolphmjaypipes: of the api in general18:28
jaypipesayoung: I'll pay you for that hamburger then.18:28
ayoungdolphm, I hear you, this is nova stuff, and not our abstractions18:28
ayoungjaypipes, you misunderstand18:28
ayoungI am saying that "yes, this abstraction is powerful enough"18:28
jaypipesdolphm: I'm fine putting it in an extension if that's what folks want, sure.18:29
ayoungso we *should* go with regions as designed.  I don't think that was clear.18:29
ayoungjaypipes, it can't be an extension18:29
jaypipesayoung: ah, gotcha18:29
ayoungit needs to be part of the service catalog18:29
dolphmayoung: ?18:29
*** n0ano has quit IRC18:29
jaypipeslol, when you guys figure that out, lemme know and I will code it up. ;)18:29
ayoungdolphm, regions are going to be how we group things in the service catalog18:29
ayoungjaypipes, this is when I go to bat for you and say "lets cook this"18:30
dolphmayoung: sure, but that doesn't mean it needs to be in the catalog controller/driver18:30
ayoungdolphm, OK,  I can see it as a separate back end...maybe, if I squint18:30
dolphmayoung: then it should be just as easy to see it as an extension with it's own backend (please continue squinting)18:30
fabioMaybe there should be a Group concept like the one for users18:31
gyeeayoung, with the pluggable token management backend, you can have you own catalog if you want18:31
gyeejust saying18:31
dolphmayoung: there's a bunch of other reviews on the meeting agenda, any others your want to mention?18:31
ayoungdolphm, ok, so a related issue is: splitting migration back ends18:31
ayoungkeeping it in the scoped o jaypipes work18:31
ayoungsay he needs a DB backend18:31
*** novas0x2a|laptop has joined #openstack-meeting18:31
ayoungwe shouldn't be oputting that in with the rest of the common sql code18:31
*** david-lyle has joined #openstack-meeting18:32
dolphmcurrently db_sync will stand up tables for any/all extensions, i don't see an immediate reason to change that, although it'd be ncie18:32
ayoungso we need to make it the first backend that has its own revision repo...18:32
dolphmit's not a blocker18:32
ayoungdolphm, extensions should not be in core, otherwise, "extensions" means nothing18:32
ayoungbut we already have the mech18:32
gyeeayoung, I think "extensions" is more significant to the API then impl18:33
ayoungdolphm, I think we need to be able to enumerate through the "active extensions" from the config file, and call db_syn on each one18:33
ayounggyee, I'll link, one sec18:33
bknudson#link https://wiki.openstack.org/wiki/Keystone/sql-migrate-extensions18:33
ayoung#link https://github.com/openstack/keystone/blob/master/keystone/cli.py#L5118:34
ayoungso we call db_sync for each backend, even though they are all common code18:34
ayoungbut we have no way for doing it for an 3rd party extension18:34
bknudsonayoung: so we'd need some way for extension to register db_sync.18:34
ayoungbknudson, right...so how about18:34
ayoungextensions = regions, oauth....18:35
ayoungand then we pull that out of the config file and enumerate?18:35
bknudsonextensions is a config option? it's not just they add middleware?18:35
*** antonym has joined #openstack-meeting18:36
ayoungbknudson, it is done like that for now^^18:36
dolphmayoung: i'm just saying that's massive scope creep for this, considering we're way past that18:36
ayoungbut not everything that is registered that way would end up getting a db_sync18:36
dolphmayoung: nice to have yes, but not a blocker for this18:36
ayoungdolphm, no, this is fixing something we've messed up18:36
ayoungdolphm, oauth is going to have the same thing18:36
dolphmayoung: right, but it's already broken18:37
ayoungit also would have been cleaner for trusts...I'm truying to learn from mistakes of the past18:37
ayoungso for all extensions, we need this18:37
ayoungwe are making the rule "do it in an extension first"18:37
ayoungso this is out side of the bargain18:37
ayoungdolphm, I can code it up...I'll take this, and jaypipes can consume it18:37
gyeeit going to be messy, if I remove an extension from the pipeline, do I run db_sync to downgrade?18:38
dolphmayoung: sure, but it's not fair to block his implementation if he gets there first18:38
ayounggyee, you don't have to, but you can18:38
dolphmgyee: +118:38
gyeeI think this is going to be extremely messy18:38
dolphmdb_sync <backend-name> ?18:38
dolphmgyee: +118:38
ayounggyee, there is actually already a mechanism in place for it, we just don't use it18:38
ayoungsee the BP18:39
gyeehow the deployers need to have knowledge of the backend18:39
ayoungjust needs a unique repo patch18:39
bknudsonis the repository path in the extension?18:39
ayounggyee, no, they need to register it as an extension.  we can have the rgions extension enabled by default if we decided18:39
ayoungbknudson, sort of18:39
*** n0ano has joined #openstack-meeting18:39
ayoungbknudson, it is in the DB table18:39
ayoungand the migrations themselves are then in the extension18:40
dolphmwe don't even support multiple sql backends, much less this18:40
bknudsonayoung: yes, that's what I was asking.18:40
ayoungdolphm, we do  support this already, for the most part18:40
*** markwash has quit IRC18:40
ayoungwe just have only one migrtation scheme, in common18:40
ayoungbut in the db:18:40
ayoungselect * from migrate_version;18:40
ayoungkeystone      | /opt/stack/keystone/keystone/common/sql/migrate_repo |      2218:40
dolphmayoung: post a demo of two backends using separate sql connection strings, and an API call that consumes both18:41
*** n0ano has quit IRC18:41
*** n0ano has joined #openstack-meeting18:41
ayoungdolphm, this would be in a single backend.  smaller use case18:41
dolphm(since this was on the agenda)18:41
dolphm#topic splitting migration back ends18:41
ayoungdolphm, anyway, enough people have the context, I'll work with the people writing extensions to make it happen18:42
*** markwash has joined #openstack-meeting18:42
dolphmayoung: alright18:42
dolphm#topic IPv6 and eventlet18:42
dolphmbknudson: ?18:42
rkanade It is very late here in India,  please give your comments on the review itself https://review.openstack.org/#/c/25517 . Thanks :) , cya all .18:43
*** Yada has quit IRC18:43
dolphmrkanade: o/18:43
ayounggnighht rkanade18:43
bknudsondolphm: I added this just to mention the bug report...18:43
*** rkanade has left #openstack-meeting18:43
bknudson#link https://bugs.launchpad.net/keystone/+bug/117873218:43
uvirtbot`Launchpad bug 1178732 in keystone "Eventlet dnspython monkey-patching problems" [Undecided,New]18:43
ayoungso we are back on an even keel with IPv6 and eventlet for gating, right?18:43
dolphmthere's also:18:43
dolphm#link https://bugs.launchpad.net/keystone/+bug/117620418:43
uvirtbot`Launchpad bug 1176204 in keystone "keystone ipv6 tests fail" [Undecided,Fix committed]18:43
bknudsonI think what I'll go with is moving the wsgi.Server code to its own part18:43
dolphmbknudson: ayoung: what's the current status of all this?18:43
ayoungso jamielennox is working on something that might help, too18:44
bknudsonWhere we are now is that the tox.ini sets the env var for eventlet18:44
bknudsonThis is another change that we should be able to get rid of.18:44
ayoungjamielennox had posted code for reveiw, but it was too huge...18:44
ayoungit is now abandoned and he is reworking into smaller patches18:44
ayoungone goal, the main one, is to remove eventlet from the server test code, and use webtest18:45
ayounglet me find the link18:45
*** jaybuff has joined #openstack-meeting18:45
ayoung#link https://review.openstack.org/#/c/28387/18:45
*** markmcclain has quit IRC18:45
ayounghe has split the v2 and v3 tests out, but the main thing, the webtest one, is still being reworked18:46
bknudsonthe major problem was the tests, so changing to webtest would make it easier18:46
bknudsonbut I assume the keystone-all server still uses eventlet?18:46
ayoung#link https://blueprints.launchpad.net/keystone/+spec/extract-eventlet18:46
ayoung#link https://review.openstack.org/#/c/29049/18:46
dolphminteresting approach18:46
bknudsondo we use eventlet when run under apache?18:47
dolphmbknudson: i would assume so based on this patch18:47
dolphmbknudson: no18:47
ayoungbknudson, as much as possible, no18:47
ayoungmost of the eventlet patching was moved into the startup code, and apache start up bypasses that18:47
dolphmnginx as well18:48
bknudsonthen I'm not sure what the blueprint is talking about with apache/nginx?18:48
ayoungbknudson, trying to make sure we are testing what would actually be run in them, for one thing18:48
*** eharney has joined #openstack-meeting18:48
*** eharney has joined #openstack-meeting18:48
*** lcheng2 has quit IRC18:49
bknudsonso is the blueprint about changing keystone-all to not use eventlet, too?18:49
ayoungbknudson, no, the blueprint is to make the final changes to make the tests and client and middleware don't require it18:49
dolphmtargetted bp to m218:49
ayoungdolphm, thanks18:50
bknudsonok, well, maybe I'll get my change in before that.18:50
bknudsonI don't think it conflicts.18:50
*** markmcclain has joined #openstack-meeting18:51
ayoungdolphm, so the test re-org is a *nice to have* not a need-to-have18:51
ayoungbut it comes from jamielennox trying to separate out the eventlet code in the testing, and getting frustrated with the organic nature of the code18:51
ayoungI think the v3 one looks good, suspect that the v2 one is probably right, as well18:51
ayounganyway, instead of it coming by fiat, everyone should look and provide feed back, with an eye to keeping the tests as maintainable as possible18:52
ayoungdolphm, can we talk Token table revocations list now?18:52
dolphmayoung: is that on the agenda somewhere?18:53
ayoungdolphm, yep18:53
ayoungdolphm, right under "Atomic API "18:53
dolphmwas hoping to get to notifications (but bknudson also disappeared)18:53
dolphmbknudson: er, maybe not18:53
dolphmbknudson: maybe my client was acting weird18:54
dolphmayoung: i thought we talked about atomic stuff18:54
dolphmayoung: pm me18:54
ayoungdolphm, so Token revocation is a real bug, and is stonewalled18:54
dolphm#topic Notifications18:54
dwaiteis there a BP for revocations?18:54
ayoungdwaite, see the agenda, links to the reviews, and bps off of them18:55
bknudsonwe were wondering if you dolphm could use some help on the notifications, to speed it up18:55
ayoungdolphm, just need people to keep that process moving. termie objects, but I think we can't meet his ideals on this one\18:55
bknudsonI've got a guy on my team here ( lbragstad ) who could help out18:55
dolphmbknudson: what kind of help?18:55
bknudsondolphm: implement it.18:55
*** david-lyle has quit IRC18:55
dolphmi'd love to, but not sure if i can hit m118:56
dolphmbknudson: oh wait, i misread that18:56
bknudsondolphm: I think it's scheduled for m3, with his help could probably move up to m2.18:56
dolphmbknudson: you want him to implement it?18:56
bknudsondolphm: yes, have him implement it.18:56
dolphmbknudson: i don't have any issue with that18:56
bknudsondolphm: great!18:56
dolphmbknudson: i've only put a little thought into how i would implement, but haven't written any code18:57
lbragstaddolphm: awesome thanks!18:57
bknudsonthat was it for notifications.18:57
ayoungnotifications are an argument to split project fro identity, too.18:57
dolphmbknudson: why i had notifications targetted to m3- it's not api-impacting, so that's just the latest it could possibly merge; i'd like it to depend on oslo.notify, which is still in progress18:57
*** fabio has quit IRC18:58
dolphmlbragstad: get caught up on oslo.notify!18:58
dolphmi haven't seen any blockers in those discussions for us18:58
*** sushils has quit IRC18:58
lbragstaddolphm: yep, I was working with a core from oslo on that for a while yesterday18:58
dolphmlbragstad: keep me posted18:58
ayoungdolphm, last thing I'd like to hit is: gate support for MySQL and Postgres Unit tests18:59
lbragstadI guess the only question I had was if notify doesn't have a maintainer, does that effect us18:59
dolphm#topic gate support for MySQL and Postgres Unit tests18:59
*** asgreene has quit IRC18:59
dolphmerr eff18:59
dolphm1 minute18:59
ayoungwe can run the unit tests against the real DBS, we should be running that in the gate.  Agreed?18:59
ayoung#link https://review.openstack.org/#/c/27878/18:59
ayounghenrynash, gyee ?18:59
dolphm"unit" tests, no lol18:59
gyeeayoung, on it18:59
openstackMeeting ended Tue May 14 19:00:15 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
henrynashayoung: agreed…let me know how I can help19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-05-14-18.01.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-05-14-18.01.txt19:00
dolphmswitching to -dev19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-05-14-18.01.log.html19:00
*** bknudson has left #openstack-meeting19:00
*** olaph_ has joined #openstack-meeting19:00
*** reed_ has joined #openstack-meeting19:01
* fungi whistles innocently19:01
*** reed_ is now known as reed19:01
*** atiwari has quit IRC19:02
* olaph_ wolfwistles at fungi19:02
jeblair#startmeeting infra19:02
openstackMeeting started Tue May 14 19:02:51 2013 UTC.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** nachi__ has quit IRC19:02
openstackThe meeting name has been set to 'infra'19:02
jeblairpabelanger, mordred: ping19:03
fungipublic service reminder: when mass-deleting servers from the cli, make quadruply sure to use the right pattern19:03
fungitriple-checking is clearly insufficient (for me at least)19:03
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:04
jeblair#action actions from last meeting19:04
jeblair#topic actions from last meeting19:04
*** dwaite has left #openstack-meeting19:05
clarkbI have put up a bug day schedule on our wiki page19:05
clarkb#link https://wiki.openstack.org/wiki/InfraTeam#Bugs19:05
fungimetbot is in here...19:05
fungihowever, meetbot is missing his cloak19:06
clarkbeach bugday is the tuesday after a milestone and starts at 1600UTC so that we can go through them before this meeting19:06
*** jkyle has joined #openstack-meeting19:06
fungii think he came back in on a netsplit while services was still absent or something. want me to bounce the process?19:07
jeblairah, so it may just not be able to set the topic19:07
jeblairfungi: nah, we'll just live without the topic changes for now19:07
jeblairand assume the logging commands are working19:07
* fungi checks that19:07
pleia2my hope is that these bug days will become less needed and shorter as we get better at using the tracking day to day19:08
clarkbI have also got hpcloud az3 in the devstack-gate rotation using the new account. I will do az2 and az1 next over the course of today assuming things rotate out quick enough19:08
clarkbpleia2: ++19:08
fungimeetbot seems to be logging to eavesdrop okay19:08
jeblairfungi: is our foundation meeting at 1600 utc?19:09
fungijeblair: possibly. looking19:09
fungioh, right normally yes19:10
clarkbwe can shift the time as necessary. I threw something out there so that we can have this discussion :)19:10
fungiwe meet tuesdays at 1600 utc (foundation staff)19:10
clarkbfungi: is 1700 to early then?19:10
jeblairmaybe we could do it at 1700?  that still gives us 2 hours19:10
*** nati_ueno has quit IRC19:10
clarkbthat works for me. I will update the wiki19:10
fungiclarkb: 1700 is fine by me19:11
clarkbwe can continue post this meeting if we really need to but as pleia2 says hopefully we get good at it and that isn't necessary :)19:11
*** nati_ueno has joined #openstack-meeting19:11
jeblairclarkb: testr?19:11
jeblair"clarkb to ping markmc and sdague about move to testr"19:12
clarkbI filed https://bugs.launchpad.net/python-keystoneclient/+bug/1177924 to track testr adoption across the projects that haven't switched19:12
uvirtbot`Launchpad bug 1177924 in python-keystoneclient "Use testr instead of nose as the unittest runner." [Undecided,In progress]19:12
clarkbhad a quick chat with sdague and realized he probably isn't the best person to drive this. ttx mentioned getting it targeted to a milestone so I have been trying to ping people involved with those projects to drum up support19:13
clarkbwhich has started the ball rolling19:13
jeblairclarkb: cool; it looks like there are reviews listed too19:14
clarkbyup. I have resurrected mordred's python-keystoneclient change and asalkeld_ is doing ceilometer19:14
clarkboh and sbaker is doing heatclient19:14
*** IlyaE has joined #openstack-meeting19:15
jeblairclarkb: anything else re testr?19:16
clarkbI don't think so. basically going to continue arguing for it so that we can get interest and effort19:16
jeblair"fungi open a bug about replacing mirror26 and assign it to himself"19:16
clarkband support as necessary19:16
fungibug opened, worked and closed19:16
fungimirror26 now runs centos and the old oneiric one is gone19:17
jeblairi deleted lists and eavesdrop19:17
jeblairi also moved paste and planet to new servers19:17
jeblairmordred did inform the tc of current testing plans19:17
jeblairi saw him do it19:17
jeblairmordred: any yelling?19:17
clarkbI don't remember any19:18
jeblairfungi open bug about spinning up new precise slaves, then do it19:18
jeblairthat happened.19:18
clarkbhe did it twice ;)19:18
jeblairtwice, even, for good measure19:18
fungicollateral damage aside19:18
fungiall done19:18
fungiand the right quantal slaves are deleted now19:18
jeblair"clarkb to get hpcloud az3 sorted out"19:18
*** shri has joined #openstack-meeting19:18
*** shri has left #openstack-meeting19:19
fungi(not the quantal slaves which were named precise[0-9]+)19:19
clarkbthat seems to be mostly sorted. trying to pay attention to test results to make sure az3 isn't failing devstack gate tests for weird reasons19:19
jeblairclarkb: cool.  probably good to double check the runtime too19:19
jeblair"fungi add change to disable nova py26 tests for folsom"19:19
fungithat was done when the remaining jobs were changed over to centos6 node labels19:20
jeblairannegentle: ping19:20
fungiand that bug is wrapped up and closed out now as well19:20
*** ayoung has quit IRC19:21
jeblaircool.  i think there was some overlap with agenda items and items from last meeting19:21
*** lloydde has quit IRC19:21
jeblairso i think we're nominally ready to skip to the docs topics19:21
jeblairthough i think clarkb wanted annegentle here for those...19:21
clarkbyeah particularly the for the one about publishing old docs19:21
*** olaph__ has joined #openstack-meeting19:22
clarkbbasically do we want to publish the docs based on the eol tags? or just not bother?19:22
jeblairclarkb: do we have a quorum for the maven topic?19:22
clarkbjeblair: I think so19:22
jeblairclarkb: yeah, good question for annegentle.  :)19:22
jeblair#topic clouddocs-maven-plugin internalization19:23
jeblair#link https://bugs.launchpad.net/openstack-ci/+bug/108281219:23
uvirtbot`Launchpad bug 1082812 in openstack-ci "Move rackspace/clouddocs-maven-plugin to openstack-dev/clouddocs-maven-plugin" [High,Triaged]19:23
clarkbso I am a horrible person and forget names, but do we want to make clouddocs-maven-plugin a stackforge project and have them drive most of the things or put it under the openstack-infra umbrella and make things go?19:24
*** gyee has quit IRC19:24
*** sandywalsh has quit IRC19:24
*** olaph_ has quit IRC19:24
jeblairclarkb: openstack-infra i think.19:24
jeblairclarkb: is it a problem that https://github.com/rackspace/clouddocs-maven-plugin does not exist?19:24
clarkbjeblair: yes, I think that means it is currently a private repo19:25
mordredjeblair: sorry - got distracted - no yelling, they were fine with it19:25
jeblairi think it moved to https://github.com/rackerlabs/clouddocs-maven-plugin19:25
jeblairDavid Cramer authored a commit a day ago19:25
jeblairclarkb: i think it was david cramer we talked to.  :)19:25
clarkbok, in that case I can whip up a change to slurp it in and have dwcramer give us the go ahead19:26
fungidcramer_ seems to be in here... the same?19:26
clarkbthe other piece to that is publishing it to maven nexus, zaro made that sound easy so I am not too worried about it19:26
jeblairclarkb: my notes said that the release process would be:19:26
jeblair  generate two commits (remove snapshot, inc+add snapshot) to pom.xml19:26
jeblair  then tag the correct one after merging19:26
jeblair(inc == increment version number)19:26
zaroclarkb: theoretically19:26
clarkbyup then the tagging will kick off a maven nexus publish build19:27
*** jlucci has quit IRC19:27
*** olaph_ has joined #openstack-meeting19:27
clarkb(it is worth noting that this release dance is one of the reasons Gerrit is trying Buck)19:27
*** jlucci has joined #openstack-meeting19:27
jeblairand all of this is probably very similar to what we should need to do for the gearman plugin19:27
jeblairclarkb: eot?19:28
mordredyes. teaching jenkins/gerrit about mvn release process - or teaching mvn about gerrit process is the game19:28
*** gokrokve has joined #openstack-meeting19:28
jeblair#topic What can infra do to enable remote participation at the next Design Summit?19:29
jeblairreed: ping19:29
reedI can't play that game19:29
reedwe have basically two issues for the next summit:19:29
*** olaph__ has quit IRC19:29
reed -  we have never found a good technical solution for remote participation at the design sessions19:30
*** neelashah1 has quit IRC19:30
reed -  we only practiced IRC for meetings as a community19:30
reedI think we should have a way for the community to practice how to hold discussions across different places19:31
reedbefore I start the conversation online where I know people will suggest we use google hangout, i'd like to explore what the infra team can do19:31
*** neelashah has joined #openstack-meeting19:32
reedthe main alternatives I see to hangout/skype are XMPP+jingle if we want video and mumble/murmur19:32
clarkbis the problem we are trying to solve general realtime collaboration or realtime collaboration specific to the summit because I think they are different19:32
clarkb*different problems19:32
fungithinking about the summit design sessions, what goes on is mostly a three-way combination of voice discussion, slideshow presentations and etherpad note taking19:32
reedclarkb, the issue is specific to summit19:33
clarkbin the general case you can assume everyone is using the same set of tools, but in design sessions half of your attendance will be in one place and the other half will use the tools19:33
reedand to user group meetings, if you want19:33
fungietherpad is already remotely joinable, so we basically need something to bridge the gap for voice and slideshows i think19:33
jeblairfungi: i don't think slideshows are that important.  they should be discouraged for design summit sessions anyway.19:34
clarkbwe could demand no slide decks to solve half that problem :)19:34
clarkbjeblair: jinx19:34
mordredjeblair: ++19:34
fungijeblair: granted, i agree with you on that19:34
reedfungi,  faces would be a nice addition19:34
russellbor post slides somewhere you can download them ...19:34
reedslides can also be done in html :)19:34
russellbso it's the voice and video part.19:35
russellbasterisk can do it19:35
ttxrussellb: you have a highlight on... XMPP ?19:35
reedrussellb, SIP?19:35
russellbreed: SIP and XMPP at the same time, if you'd like19:35
clarkbdoes that place unreasonable requirements on the network at the conference center? they never seem to handle things well19:36
reedconsider we'll be in Hong Kong, so networking can be challenging, too :)19:36
jeblairhow about focusing on just audio -- i'm a little concerned about bandwidth and network reliability...19:36
clarkbjeblair: ++19:36
*** sandywalsh has joined #openstack-meeting19:36
russellbany voice+video (*especially* video) solution is going to be bandwidth hungry19:36
*** lcheng2 has joined #openstack-meeting19:36
reedclarkb, god only knows what will happen there... but we can make them pay super-serious attention to that19:36
russellbjust audio is even easier19:36
fungiwithout faces, i think we still need something which will pop up a subtitle indicating who's talking19:36
ttxone-way audio with IRC feedback is what Ubuntu used to use at UDS19:36
clarkbI am not familiar with asterisk but mumble does rooms like irc channels19:36
*** sandywalsh_ has joined #openstack-meeting19:37
*** rerngvit has joined #openstack-meeting19:37
*** rerngvit has quit IRC19:37
ttxwith a projection of an IRC channel all the time, difficult to ignore19:37
jeblairttx: that seemed very reliable19:37
*** dprince_ has quit IRC19:37
ttxcritical participants can be hooked in in two-way voice, if necessary19:37
fungihaving been on my share of two-way conference calls, it gets unmanageable once you have 10 or more people trying to keep from talking over top of one another, without a moderator to voice and devoice them19:37
russellbi like that.19:38
reedthe main drawback of that is that I can't see how we can have that system tested/deployed before the Summit19:38
reedI explain:19:38
ttxI mean, the session moderator knows if he has a ccritical participant and can hook him in19:38
ttxeveryone else can have one-way audio + IRC19:38
*** alexpilotti has quit IRC19:38
reedmy idea is to ask user groups to test the remote system we put in place so we get to HK with practice and knowledge19:38
jeblairttx: +119:38
russellbjust need decent audio equipment so that it's actually usable ...19:38
fungithat sounds reasonable to me19:38
ttxwe could even abandon the idea of lurkers on one-way audio + IRC and just support critical participants in a ad-hoc manner19:39
reedI don't see how IRC+audio streaming can be made enough for user group Atlanta to chime in the meeting in Chicago, for example19:39
fungirussellb: we had "decent" audio equipment in san diego (not awesome, but usable). the techs who wired the rooms did a less than perfect job though19:39
jeblairreed: i think we could still test that in the manner you are discussing19:39
ttxfrankly, you know when you've a critical person missing from the discussion.19:40
reedjeblair, I think we need video, too19:40
russellbfungi: was that when we had the webex things?19:40
fungirussellb: yes, webex itself is crap though, in my opinion19:40
russellbneeding video, but being concerned about conference internet, is going to be a bit concerning19:40
jeblairreed: the thing we can't test is how the network in hong kong is going to perform, which is why i think focusing on resilient low-bandwith protocols is our best way to prepare for that.19:40
*** sandywalsh has quit IRC19:40
ttxso I think having decent phones in each room that a small set of people, invited by the PTL, can call in...19:40
ttxis all we need from a technical perspective19:41
reedrussellb, we will take care of the infrastructure later, once we have the specs ready... it's a matter of writing down the contracts19:41
*** afazekas has joined #openstack-meeting19:41
ttxone-way audio + IRC is a plus19:41
*** olaph__ has joined #openstack-meeting19:41
russellbjust a phone is a bit of a pain, not everyone will be able to hear it, and the people on the phone wont' hear the whole room19:41
*** timello_ has quit IRC19:41
jeblairreed: wasn't there already a spec for the network?  i seem to remember some bandwidth number is the proposal responses from the venue19:42
russellbnot much better than someone's laptop19:42
ttxPersonally I don't mind if we lose the US lurkers. We'll have the APAC ones in the rooms to replace them.19:42
reedjeblair, the bandwidth was never an issue afaik19:42
*** timello has joined #openstack-meeting19:42
russellbproblem is the lurkers complain when they can't hear something19:42
reedAFAIK we never had issues at the summit with streaming videos19:42
ttxrussellb: that's why, personally, I would get rid of the intermediary setup19:42
ttxrussellb: have a solution for critical participants if we need them19:43
reedthe problems users saw at this summit were for few failed hardware and some closed ports19:43
ttxrussellb: but not try and fail at something that pretends to enable remote participation19:43
*** olaph_ has quit IRC19:44
fungiin san diego, i had to investigate and restart webex on average twice a day, and i was only responsible for one room19:44
*** lloydde has joined #openstack-meeting19:44
reedis there a system that we can put in place that supports chat, audio and video and, if networking fails, drop video?19:44
jeblairttx: so that's a big first question we need to answer: do we want to enable general streaming for everyone, or focus just on the critical participants (invite only)?19:45
clarkbI think chat is IRC and should remain IRC as we already have a ton of tooling around it and it is familiar19:45
reedfungi, what was the cause of that? networking or webex failures?19:45
ttxjeblair: yes19:45
fungireed: networking and hardware failures19:45
fungireed: my room had the laptop that kept locking up too19:46
reedso we need something that can basically run as a daemon19:46
ttxjeblair: I think we can do a good job at handling critical participation... not convinced we can build a good story for general remote participation... and doing a bad one is worse than not doing it19:46
reedheadless preferrably19:46
jeblairttx: indeed, things will go wrong, so we should keep it as simple as we can19:46
reedttx: for critical participation we're investigating the possibility to pay for their travel19:47
fungiso the critical-participants-only solution seems to be in line with the atc-only physical access to the rooms. open remote participation is likely to draw non-participant lurkers19:47
*** shardy has joined #openstack-meeting19:47
ttxreed: it's a bit difficult though. some people don't know they are critical until the session is up19:47
fungimuch in the same way that discouraging non-atc participants helped a bunch in portland19:47
ttxflying them on short notice is kinda expensive19:47
reedttx, got it, make sense19:48
ttxin all cases you'll have critical people that won't show up19:48
ttxeven when it's in the US we have that scenario19:48
reedso what you're suggesting is to ...19:49
*** koolhead17|afk has quit IRC19:49
ttxso having a conference phone and bridges set up in the rooms might be all we need19:49
reedproceed like we did in Portland? nothing  globally, and ad-hoc per room?19:49
fungidedicated conference bridge number per room, with a conference room phone19:49
ttxthat ^19:49
clarkband dedicated irc channels and etherpads per session19:50
jeblairreed: which isn't ad-hoc at all.  i definitely think we should spend some time setting this up and making sure it works.19:50
clarkbor per room. eg somewhere people can find the info if mordred doesn't do it ahead of time19:50
*** thingee has joined #openstack-meeting19:50
reedjeblair, not very sexy, but we can throw it out there19:50
jeblairreed: i love things that work, regardless of how sexy they are.19:51
fungii'd rather have functional than sexy19:51
fungior what jeblair said19:51
ttxclarkb: re: dedicated irc channels -- that's a bit useless as we ignore them19:51
reedyou guys19:51
clarkbttx: yeah I am just thinking that a lot of the sessions don't have a remote meet point until they start19:52
jeblairttx: if we projected them like UDS19:52
clarkbttx: so we need someway of making sure that the important participants know what things are ahead of time19:52
ttxclarkb: it's actually harder to ignore the etherpad, and the chat there19:52
jeblairalternatively, we could encourage the use of the etherpad chat19:52
russellbyeah, projecting them would make it work, i think19:52
clarkbirc or etherpad etc19:52
reedwe'll need a webpage to summarize it all19:52
ttxsure. We can have a box to project the etherpad in each room19:52
reedthe agenda will have to contain the IRC channel and the phone number for the room19:52
ttxreed: hmm. If too many people join the bridge it will be useless for the critical people19:53
russellbetherpad chat is ok too though, really ... everyone is looking at etherpad already anyway, and it's archived with the notes19:53
ttxI'd rather have the moderator invite critical people in19:53
fungiwe'd still need a little more cultural pressure to not ignore them. i saw a tendency in some design sessions to not pay attention to the etherpad chat window even though it was on the projector19:53
reedI still think that we won't find a way to test this system with the user groups, it's not useful for that use case19:53
russellbyou can set up a bridge to be listen-only by default unless you have a code to be a talker19:53
*** alexpilotti has joined #openstack-meeting19:53
jeblairrussellb: should we attempt to use ip telephony or pots?19:53
ttxrussellb: ah, interesting19:54
russellbeither ... ip should be fine, but depends on reliability of your network19:54
ttxrussellb: it's just that... I suspect we would set up the phone only in sessions where we know someone is missing19:54
russellb(of course)19:54
jeblairttx: if we're doing this with asterisk, we might be able to scale out listening to a large number of listeners, and allow them to listen in-browser, etc.19:54
*** n0ano has quit IRC19:55
russellbalso ip would be way cheaper.19:55
jeblair(so lurkers aren't using up telephone resources)19:55
reedok, sounds good19:55
ttxjeblair: that means setting up the phone call at every session19:55
ttx..or you would just keep it running ?19:55
reedhow do you suggest we test this?19:56
* ttx remembers reed running between rooms to check that the Webex stuff was still up19:56
clarkbwe could try running this meeting with the system one day19:56
fungii think it would just be a conference phone dialed into the bridge number for that room as the call moderator, with written instructions on how to redial if it's disconnected19:56
reednot exactly the way I intended...19:56
*** alexpilotti has quit IRC19:56
reedso to summarise19:57
reedyou're suggestion Asterisk server/SIP and phones in each room19:57
*** mattray has quit IRC19:57
jeblairrussellb: would you be willing to help?19:58
jeblairi intend to ask pabelanger too when he's around.  :)19:58
*** samalba has joined #openstack-meeting19:58
funginow that's half a dozen international calls from hong kong to wherever our bridge number is, connected 8 hours a day for 5 days, more or less. not sure what the expense winds up looking like for that19:58
reedI'm still not convinced this is the best way to proceed19:58
russellbfungi: via IP though, free19:58
jeblairfungi: that does make trying to use SIP compelling.19:58
reedbut I do note the convenience of good old telephones19:58
fungiunless we do voip over the conference network yes19:58
russellband ... need to check regulatory issues19:59
russellbsome countries block voip :(19:59
fungii note the stability of good old telephones vs voip across the world from a conference19:59
jeblairwe should probably found out how much pots calls would cost from the facility20:00
ttxrussellb: but this is Hong-Kong... oh wait.20:00
fungivoip participants make sense, but for the conference room an actual phone line per room would likely be less finicky20:00
jeblairokay, we're at time...20:00
reedI think we can keep discussing this next week, I'll start a thread on the list, probably20:00
jeblairttx: is there a meeting in here now?20:00
ttxjeblair: no.20:00
reedthe TC...20:00
*** pcm__ has quit IRC20:00
ttxyou can overrun... a bit.20:01
russellbcanceled today20:01
ttxNo TC meeting this week20:01
*** david-lyle has joined #openstack-meeting20:01
fungiwant me to bounce the bot real quick between meetings? i can do it after we wrap this one up i guess20:01
jeblairreed: yeah, let's do that; we'll resume next week20:01
reedyeah, I think we wont' go too far anyway and we have time :)20:01
jeblairreed: and try to get people who are willing to help here20:01
*** olaph__ has quit IRC20:01
reedyep, will do20:01
*** olaph_ has joined #openstack-meeting20:01
reedthanks everybody20:02
jeblairi'm certainly willing to arrive at the summit early and help set up20:02
fungias am i20:02
reedok, gotta go20:02
jeblairok, thanks20:02
*** stevebaker has quit IRC20:02
jeblairthanks everyone, see you next week20:02
openstackMeeting ended Tue May 14 20:03:02 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-05-14-19.02.html20:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-05-14-19.02.txt20:03
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-05-14-19.02.log.html20:03
jeblairfungi: bounce away20:03
* fungi will go ahead and get meetbot sane now20:03
*** openstack has joined #openstack-meeting20:03
*** ChanServ sets mode: +o openstack20:03
jeblair#startmeeting test20:03
openstackMeeting started Tue May 14 20:03:46 2013 UTC.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: test)"20:03
openstackThe meeting name has been set to 'test'20:03
jeblairfungi: lgtm20:03
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:04
olaph_oooh, sign me up for the get-there-early-crew20:04
openstackMeeting ended Tue May 14 20:04:01 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:04
openstackMinutes:        http://eavesdrop.openstack.org/meetings/test/2013/test.2013-05-14-20.03.html20:04
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/test/2013/test.2013-05-14-20.03.txt20:04
openstackLog:            http://eavesdrop.openstack.org/meetings/test/2013/test.2013-05-14-20.03.log.html20:04
fungiolaph_: when the time comes, i expect reed will put out a call for volunteers anyway. hard to miss20:04
*** jcoufal has joined #openstack-meeting20:08
*** n0ano has joined #openstack-meeting20:09
*** ayoung has joined #openstack-meeting20:09
*** markmcclain has quit IRC20:09
*** markmcclain has joined #openstack-meeting20:11
*** jaybuff has left #openstack-meeting20:12
*** markpeek has quit IRC20:13
*** maoy has quit IRC20:15
*** maoy has joined #openstack-meeting20:15
*** n0ano has quit IRC20:15
*** lcheng2 has quit IRC20:17
*** boris-42 has quit IRC20:19
*** maoy has quit IRC20:19
*** jbresnah has joined #openstack-meeting20:20
*** dcramer_ has quit IRC20:21
*** stevebaker has joined #openstack-meeting20:22
*** jlucci has quit IRC20:24
*** SergeyLukjanov has quit IRC20:26
*** SlickNik has joined #openstack-meeting20:28
*** flaper87 has joined #openstack-meeting20:29
*** pnavarro has quit IRC20:30
*** pnavarro has joined #openstack-meeting20:30
*** datsun180b has joined #openstack-meeting20:32
*** pnavarro has quit IRC20:32
*** pnavarro has joined #openstack-meeting20:32
*** olaph__ has joined #openstack-meeting20:33
*** IlyaE has quit IRC20:34
*** saurabhs has joined #openstack-meeting20:34
*** gyee has joined #openstack-meeting20:35
*** neelashah has quit IRC20:35
*** IlyaE has joined #openstack-meeting20:36
*** olaph_ has quit IRC20:37
*** armax has left #openstack-meeting20:38
*** ayurchen has quit IRC20:42
*** gokrokve has quit IRC20:42
*** ayurchen has joined #openstack-meeting20:43
*** afazekas has quit IRC20:46
*** tzumainn has joined #openstack-meeting20:47
*** nati_ueno has quit IRC20:48
*** carl_ has joined #openstack-meeting20:51
*** gabrielhurley has joined #openstack-meeting20:52
*** nati_ueno has joined #openstack-meeting20:52
*** markmc has joined #openstack-meeting20:54
*** sarob has joined #openstack-meeting20:57
*** sarob_ has joined #openstack-meeting20:59
ttxnotmyname, jd__, markwash, jgriffith: around ?21:00
*** sarob has quit IRC21:00
ttxok, let's get started, jgriffith will join us21:00
ttx#startmeeting project21:00
openstackMeeting started Tue May 14 21:00:46 2013 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: project)"21:00
openstackThe meeting name has been set to 'project'21:00
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:00
*** olaph_ has joined #openstack-meeting21:01
ttxUsual stuff. Two weeks left in havana-1, will look into the havana-1 plans with an eye on postponing stuff21:01
ttx#topic General stuff21:01
*** openstack changes topic to "General stuff (Meeting topic: project)"21:01
*** zyluo_ has joined #openstack-meeting21:01
ttx2013.1.1 was released last week21:01
ttxannegentle, jeblair/mordred, sdague/davidkranz: Anything from Docs/Infra/QA teams ?21:01
ttxAnything anyone wants to raise that affects all projects ?21:02
ttxjeblair: is that a yes ?21:02
ttxor just a hello ?21:02
jeblairwe're talking about remote summit participation in the infra team meetings, so stop by next week if you want to contribute21:02
ttxthat was a yes.21:03
ttxanything else ?21:03
*** olaph__ has quit IRC21:03
*** harlowja has quit IRC21:04
*** harlowja_ has joined #openstack-meeting21:04
ttxthere is a discussion about copyright headers on legal-discuss that you may want to intervene in.21:04
*** sarob_ has quit IRC21:04
ttxok, let's go per-project now21:04
ttx#topic Oslo status21:04
*** openstack changes topic to "Oslo status (Meeting topic: project)"21:04
ttxmarkmc: hi!21:04
*** HeidiBretz has joined #openstack-meeting21:04
ttx#link https://launchpad.net/oslo/+milestone/havana-121:04
*** sarob has joined #openstack-meeting21:04
ttxsignificant progress since... this morning.21:04
markmcI'd say correlation-id and object-serialization are very likely to make it21:05
markmcthe others, it's hard to say21:05
ttxtrusted-messaging is marked as depending on keystone/key-distribution-server, which is a bit... not in havana plans yet21:05
*** danwent has joined #openstack-meeting21:05
markmcgood chance, but couldn't guarantee any of them21:05
ttxhow much is that actually blocked by it ?21:05
markmcyeah, I should talk to simo about that21:05
markmcwe could land the code in oslo without that21:05
*** flwang has joined #openstack-meeting21:05
markmcbut whether that would achieve anything useful ...21:05
markmcso, good point21:06
ttxyou can remove the dep if it's not a hard dep, and replace it by a mention in the blueprint description21:06
ttxQuestions about Oslo ?21:06
markmcoh, wiki page21:06
ttxwiki page ?21:06
markmcI basically re-wrote it21:06
markmchopefully that answers most of the questions I was hearing at the summit21:07
markmcthere are some details about making hacking and pbr part of oslo that monty and I will work out21:07
ttxcool, will review it21:07
markmcoh, another thought21:07
markmcnothing in havana is yet using oslo.config from havana21:08
markmcthey're all till using 2013.1 or whatever21:08
markmcanother thing I should fix21:08
markmcthat's me21:08
ttx#topic Keystone status21:09
*** openstack changes topic to "Keystone status (Meeting topic: project)"21:09
ttxdolphm: o/21:09
ttx#link https://launchpad.net/keystone/+milestone/havana-121:09
ttxdolphm: keystone-ldap-anonymous-binding isn't started yet, do you still think it will make it ?21:09
dolphmyes, it should be a very simple implementation21:09
ttxLooking at the more general havana plan... any idea who plans to work on store-quota-data and pluggable-remote-user ?21:10
dolphmstore-quota-data, i'd have to go back and look at the summit etherpad21:10
dolphmpluggable-remote-user, either myself or possibly gyee21:10
*** emagana has quit IRC21:10
dolphmgyee is on a pluggable spree21:10
ttxdolphm: ok, fill  them out if you already know21:11
dolphmi'll talk to him21:11
ttxkeeping you busy with security fixes during this milestone21:11
*** pabelanger has quit IRC21:11
ttxAnything more about Keystone ?21:11
dolphmotherwise, i think it's fairly realistic to see an m2-targetted blueprint or two completed in time for m121:11
ttxthat would be great.21:11
dolphmi did want to mention that the bug in our release notes concerns read-only LDAP uses cases in havana has slipped to 2013.1.221:12
*** alexpilotti has joined #openstack-meeting21:12
dolphmthat's it from me21:12
ttxdolphm: could you quickfix the release notes ?21:12
dolphmttx: they're up to date: "Read-only LDAP deployments using the bundled identity driver still requires a default domain to be created in LDAP (fix in progress for 2013.1.2)."21:13
ttxoh, ok. Known bug.21:13
ttx#topic Ceilometer status21:13
*** openstack changes topic to "Ceilometer status (Meeting topic: project)"21:13
ttxjd__: o/21:13
ttx#link https://launchpad.net/ceilometer/+milestone/havana-121:13
ttxGood progress...21:13
jd__thank you! :)21:14
ttxAll on track ?21:14
*** olaph_ has quit IRC21:14
jd__so far so good, I've pinged Toni about his blueprint because I'm worried21:14
jd__I've the feeling his patchset is going to be big and will have some rework21:14
jd__we didn't see anything for weeks21:14
jd__so I might postpone it for havana-2 if no progress, anyway that's no blocker21:15
ttxI won't say "not a big deal if it slips" because you have so many in the pipe...21:15
ttxLooking into the general plan at https://blueprints.launchpad.net/ceilometer/havana now21:15
jd__ttx: well, at least it doesn't block anything else :)21:15
ttxThere is still a bit of milestone targeting needing to be done21:15
ttxjd__: right :)21:15
ttxA few of those untargeted blueprints are actually started: hbase-metadata-query, alarm-api, add-event-table...21:15
jd__yeah, I'm having a hard time pushing people to assign bp and milestone21:15
*** lbragstad has quit IRC21:16
ttxonce it's assigned, it's just a matter of asking the assignee when he thinks, roughly, it will land21:16
jd__yup, I'll do that :)21:17
*** jang1 has quit IRC21:17
ttxYour plan is pretty ambitious already at 45 blueprints.21:17
ttxNote that it's better to postpone stuff early rather than communicate false hopes to people :)21:17
ttxQuestions on Ceilometer ?21:18
jd__ttx: fair enough :)21:18
ttx#topic Swift status21:18
*** openstack changes topic to "Swift status (Meeting topic: project)"21:18
ttxnotmyname: o/21:18
ttx#link https://launchpad.net/swift/+milestone/1.8.121:19
ttxnotmyname: About https://blueprints.launchpad.net/swift/+spec/proxy-affinity-writes, should it be considered "Started" ?21:19
ttxSaw code in WIP at https://review.openstack.org/#/c/27431/21:19
*** dcramer_ has joined #openstack-meeting21:19
notmynameya, I saw that too21:19
notmynamebut I hadn't had a chance to review it yet21:19
notmynamebasically 1.8.1 will be the completion of the global cluster features21:20
ttxnotmyname: if work is started we can update status21:20
notmynameand I was just looking at the separate replication patches21:20
ttxproxy-affinity-writes is not directly linked to global cluster ?21:20
notmynameyes, if work has started, we can update the status. the author didn't reference the blueprint, and I hadn't had a chance to see if it actually matches, so I hadn't updated anything yet21:21
notmynameyes, it's related21:21
ttxnotmyname: Will update status for you. anything you wanted to raise ?21:21
notmynamecan I update the status after I have a change to look at the code?21:21
*** jasondotstar has quit IRC21:22
notmynamethe other thing to mention is swift api work21:22
ttxnotmyname: sure, I'll revert my status change then21:22
*** alexpilotti has quit IRC21:22
notmynamework is continuing on https://wiki.openstack.org/Swift/API to define the functionality that wil be defined as swift api v1.021:22
ttxAnything more on Swift ?21:23
notmynamework will be continuing to define this and then move on to next versions of the api21:23
notmynamethat's all from me21:24
ttx#topic Glance status21:24
*** openstack changes topic to "Glance status (Meeting topic: project)"21:24
ttxmarkwash: o/21:24
ttx#link https://launchpad.net/glance/+milestone/havana-121:24
markwasha very few recent changes there21:24
*** lcheng2 has joined #openstack-meeting21:24
ttxGood progress... api-v2-property-protection isn't started yet ?21:25
markwashfolks are now getting together to plan out the nitty gritty details21:25
markwashI'm sure that one will slip21:25
markwashI'll get another opinion about h2 vs h3 from them next monday21:25
ttxmarkwash: let's move it to h2 already21:26
ttxwill do21:26
ttxLooking into the general havana plan now @ https://blueprints.launchpad.net/glance/havana21:26
markwashmultiple image locations seems stalled out as well21:26
ttxStill a lot of stuff without a milestone target set... should we consider those all targeted to havana-3 ?21:26
markwashnot for all of them, unfortunately21:27
markwashI'll make sure that page looks pretty by thursday during the glance meeting21:27
markwash#action markwash target all the blueprints21:27
ttxre: not all of them -- yes, support-for-multipart-form-data-contenttype and hypervisor-templates-as-glance-images are already started...21:27
ttxso probably not that far from completion21:28
ttxAnything more on Glance ?21:28
markwashthose are sort of dark horses, though21:28
markwashso I don't know about their velocity yet21:28
markwashnothing more from me21:28
ttxdark horses. I like that.21:28
*** neelashah has joined #openstack-meeting21:28
ttxmarkwash: thx!21:28
ttx#topic Quantum status21:28
*** openstack changes topic to "Quantum status (Meeting topic: project)"21:28
ttxmarkmcclain: hi!21:28
ttx#link https://launchpad.net/quantum/+milestone/havana-121:28
ttxcatching up with recent changes :)21:29
*** mattray has joined #openstack-meeting21:30
markmcclainyeah.. had a few folks try to sneak two bps into h121:30
*** lbragstad has joined #openstack-meeting21:30
*** martine_ has quit IRC21:30
ttxportbinding-ex-db looks implemented to me ?21:30
ttxor is there more to it ?21:31
ttxSame question for https://blueprints.launchpad.net/quantum/+spec/api-core-for-services (targeted to havana-2)21:31
markmcclainthere's another review associated with it that is not linked21:31
ttxgood then21:31
markmcclainapi-core will have 2 reviews21:31
markmcclainonly 1 has been submitted21:32
ttxGood progress overall... except remove-use-of-quantum which is still pending the choice of the new name :)21:32
ttxLooking into the general havana plan now: https://blueprints.launchpad.net/quantum/havana21:32
markmcclainrussellb: do you have a pronunciation :)21:32
russellbmarkmcclain: it's like the-artist-formerly-known-as-prince, you couldn't pronounce that symbol either21:32
ttxmarkmcclain: You might want to add https://blueprints.launchpad.net/quantum/+spec/quantum-vpnaas-ipsec-ssl, since it's a dependency of vpnaas-python-apis21:33
ttxLooks like you're almost done with https://blueprints.launchpad.net/quantum/havana/+setgoals21:33
markmcclainI will.. they just agreed yesterday exactly what was in it21:33
ttxAnything else on Quantum ?21:33
markmcclainnot from me21:33
ttxdo we have jgriffith ?21:34
ttxwe do have jgriffith21:34
ttx#topic Cinder status21:34
*** openstack changes topic to "Cinder status (Meeting topic: project)"21:34
ttx#link https://launchpad.net/cinder/+milestone/havana-121:34
*** henrynash has quit IRC21:35
jgriffithI'll be moving state machine to H221:35
ttxlooks like this is all a bit late, anything you'd like to defer now ?21:35
jgriffiththat one and I need to contact xing Yang regarding her FC support21:35
ttxFeeling confident for the "started" ones ?21:35
jgriffithso far yes21:36
jgriffithMost are coming along nicely21:36
jgriffitha few should land before the end of the week21:36
ttxok, beware of the review queue toward the end of the milestone21:36
ttxLooking into the general havana plan @ https://blueprints.launchpad.net/cinder/havana21:36
ttxhttps://blueprints.launchpad.net/cinder/+spec/volume-migration should have a priority set21:37
jgriffithon it21:37
jgriffithI actually would like to work with Avishay and break that one up a bit21:37
ttxotherwise looking pretty good21:37
jgriffithIt's a bit too general as it is right now for my liking21:37
jgriffithI'll try and catch him tonight and sort that21:37
ttxyes, those kind tend to never be completed21:37
ttxAnything more about Cinder ?21:38
jgriffithor they're not what anybody wants :)21:38
jgriffithNope, that's it for me21:38
*** rnirmal has quit IRC21:38
ttx#topic Nova status21:38
*** openstack changes topic to "Nova status (Meeting topic: project)"21:38
ttxrussellb: o/21:38
ttx#link https://launchpad.net/nova/+milestone/havana-121:38
ttxGetting a bit late, still feeling optimistic ?21:38
russellbfor all of this?  no :-)21:38
russellbi've starting pushing some things back today21:39
russellbwill continue to do so over the next week as i'm able to catch up with people21:39
ttxuse-db-time and remove-instance-fault-table are targeted but not started yet21:39
russellbuse-db-time is quick and easy21:39
russellbthe other probably won't make it, but figured i'd give it a few days in case code magically appears21:39
*** henrynash has joined #openstack-meeting21:40
ttxotherwise you got them all triaged, as of 5 minutes ago21:40
ttxhttps://blueprints.launchpad.net/nova/havana/+setgoals has a new one :)21:40
russellbhaha, yeah.21:40
russellbas of about 1 minute ago21:41
*** emagana has joined #openstack-meeting21:41
* russellb fixes it up21:41
russellbgood now21:41
ttxlive-migration-to-conductor (High) depends on query-scheduler (Medium) -- which one should be adjusted ?21:41
russellbquery-scheduler should go to high, then21:42
ttxok will do21:42
*** johnthetubaguy has quit IRC21:42
ttxAny question on Nova ?21:42
*** lcestari has quit IRC21:42
russellbquestion from me21:42
russellbdo we have a page i can point people on blueprint process?21:42
russellbi spend a lot of time telling people which fields to set, etc., to get it on my radar21:43
ttxI'd say https://wiki.openstack.org/wiki/Release_Cycle, and https://wiki.openstack.org/wiki/Blueprints21:43
russellbok will check those out, thanks21:43
ttxThey may need some updates, but that's the reference doc21:43
*** stevemar has quit IRC21:44
russellbk, will review / propose updates as needed21:44
ttx#topic Heat status21:44
*** openstack changes topic to "Heat status (Meeting topic: project)"21:44
ttxshardy: hi!21:44
ttx#link https://launchpad.net/heat/+milestone/havana-121:44
*** jecarey has quit IRC21:44
*** olaph_ has joined #openstack-meeting21:44
ttxrussellb: there is also https://wiki.openstack.org/wiki/PTLguide but that's more for PTL and drivers.21:44
*** olaph_ has left #openstack-meeting21:45
ttxshardy: havana-1 looks in good progress21:45
*** zyluo_ has quit IRC21:45
shardyttx: I think we're in good shape for h1, apart from a few of the networking bugs may slip21:45
ttxLooking into the general havana plan @ https://blueprints.launchpad.net/heat/havana now21:45
shardyneed to speak to stevebaker and jpeeler to confirm21:45
ttxCould still use a bit more target milestones... but I see progress :)21:46
shardyttx: Yes, I've started putting things I think will get done, or which I'd like to see done for h221:46
ttxa number of those untargeted blueprints are already started, like watch-ceilometer or function-plugins21:46
ttxso their assignee should have an idea of when he will complete them21:47
shardybut a lot of promised contributions are being slow to materialize, so I'm still playing wait-and-see on some of the bigger stuff expected later in the cycle21:47
ttxshardy: it's not a big deal to keep low prio stuff untargeted21:47
ttxA bit more embarassing for High prio stuff21:47
shardyttx: I'll speak to asalkeld and zaneb to get updates on when those will land21:48
ttxsince High means, you really want it in the release21:48
ttxshardy: That's all I had for you. anything you wanted to mention ?21:48
shardyone question21:48
shardyyou asked for havana roadmap emails to the list last week21:49
ttxyep, those would be nice21:49
shardywhich list - do you want user-focussed ones to the openstack list?21:49
shardyor xpost to both?21:49
reedxpost is evil21:49
ttxxpost is evil. Post to openstack-dev only. I saw russellb pushed one to his blog, that's fine too21:49
shardywasn't sure how to pitch it so wanted to clarify21:50
shardyOk, thanks21:50
ttxI'm pretty sure reed will pick those up and mention them in the newsletter21:50
reedi should stop xposting myself :)21:50
*** sacharya has quit IRC21:50
ttxso they will get attention, without the drawbacks of cross-posting21:50
ttxQuestions about Heat ?21:50
russellbttx: yeah, was hoping newsletter would get it21:50
reedif it's on planet there are highest chances it will make it to the newsletter21:51
ttx#topic Horizon status21:51
*** openstack changes topic to "Horizon status (Meeting topic: project)"21:51
ttxgabrielhurley: hey21:51
ttx#link https://launchpad.net/horizon/+milestone/havana-121:51
ttxProgress is a bit slow...21:51
gabrielhurleyit's kinda borderline21:51
gabrielhurleythings are moving along21:51
gabrielhurleythe keystone stuff has been significantly slowed by getting some reviews through on keystoneclient21:52
gabrielhurleybut I still have confidence in those21:52
gabrielhurleyI'm not ready to bump any *quite* yet21:53
ttxadmin-group-crud is not started... is it simple enough to be completed in the two remaining weeks ?21:53
gabrielhurleybut I am gonna be tightening in on people this week21:53
gabrielhurleyyeah, it is21:53
*** neelashah has quit IRC21:53
ttxQuestions on Horizon ?21:53
gabrielhurleyby-and-large none of these will be showstoppers if they *do* slip, though21:53
*** egallen has joined #openstack-meeting21:53
ttxgabrielhurley: right, you got the essential under control21:54
ttxgabrielhurley: anything else you wanted to mention ?21:54
*** thingee has left #openstack-meeting21:54
ttxok then21:54
ttx#topic Incubated projects21:54
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:54
ttxhub_cap, devananda: welcome!21:54
ttxAny question ?21:54
*** vkmc_ has joined #openstack-meeting21:55
*** lbragstad has quit IRC21:55
*** jpich has joined #openstack-meeting21:55
devanandanope. just following along and learning :)21:56
ttxdevananda: first step is getting that repo set up :)21:56
devanandayep... not a lot of real activity yet as a result21:56
ttxdevananda: do you have seed code ready to fill it ?21:57
devanandai'v e got a review up for that, just waiting on jeblair21:57
devanandaand yes21:57
devanandaworking on some skeleton docs and will be posting BPs soon21:57
*** schwicht has quit IRC21:57
devanandaso that once there is a repo, folks can begin claiming parts of it and working in parallel21:57
ttxreddwarf still needs to move, but i guess it can wait for the name vet first21:57
ttxdevananda: hopefully should be all set today21:58
ttxok, if you have no question, I guess I can close the meeting21:58
ttxanything else, anyone ?21:58
*** mrunge has joined #openstack-meeting21:58
*** jcoufal has quit IRC21:59
*** schwicht has joined #openstack-meeting21:59
ttxok then22:00
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:00
openstackMeeting ended Tue May 14 22:00:10 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2013/project.2013-05-14-21.00.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-05-14-21.00.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-05-14-21.00.log.html22:00
*** datsun180b has quit IRC22:00
hub_capheh thx for the welocme ttx sry for the lateness ;)22:00
*** sushils has joined #openstack-meeting22:01
gabrielhurleyokay, horizon time22:02
gabrielhurley#startmeeting horizon22:02
openstackMeeting started Tue May 14 22:02:06 2013 UTC.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.22:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:02
*** openstack changes topic to " (Meeting topic: horizon)"22:02
openstackThe meeting name has been set to 'horizon'22:02
gabrielhurleyHi folks!22:02
mrungehey gabriel22:02
gabrielhurley#topic overview22:02
*** openstack changes topic to "overview (Meeting topic: horizon)"22:02
gabrielhurleyWe've got two weeks left to get blueprints into H1, so this is crunch time. The more we can do this week the better.22:03
*** leandrorosa has joined #openstack-meeting22:03
gabrielhurleyThank you to everyone who's been reviewing lately, it's been a big help22:03
gabrielhurleyBasically, anything that's not up for code review by this time next week is probably going to get deferred to H2, just FYI.22:04
gabrielhurleyOverall things are looking decent, though, so I still have confidence in what we can do in H122:04
gabrielhurleylet's dive into specifics of the blueprints22:04
gabrielhurley#topic blueprints22:04
*** openstack changes topic to "blueprints (Meeting topic: horizon)"22:04
gabrielhurleyThe two "essential" BPs are committed, so that's great.22:05
*** schwicht has quit IRC22:05
gabrielhurleyKeystone BPs are the next big chunk22:05
gabrielhurleyI noticed that https://review.openstack.org/#/c/21942/ is currently abandoned22:05
gabrielhurleylcheng, david-lyle: care to update us?22:05
*** sarob has quit IRC22:05
david-lylegyee is going to pick it up22:05
gabrielhurleyany ETA?22:06
*** sarob has joined #openstack-meeting22:06
david-lylestarting early this week22:06
gabrielhurleyis that actually blocking work on the domain, group, etc. CRUD or just a nice-to-have for those?22:06
gabrielhurleyseems like it's only strictly a blocker for the login w/ domain22:06
david-lylenot blocking22:07
david-lylejust blocking anything with a v3 token22:07
*** schwicht has joined #openstack-meeting22:07
gabrielhurleyso are you still feeling confident on the various keystone v2 blueprints for h1?22:07
david-lyleso we can work against the v3 API using a v2 token22:07
dolphmgabrielhurley: +1 that's all accurate22:08
david-lylefor basic CRUD yes, not sure the total scope that will be in the initial commits22:08
gabrielhurleydavid-lyle: sounds good. we can always improve over time.22:08
*** markmc has quit IRC22:08
*** markmcclain has quit IRC22:08
david-lyleyeah, at least we'll have something to build on22:08
gabrielhurleyanything myself or dolphm can do to make things smoother?22:09
gabrielhurley(since keystone v3 accounts for about 1/3 of the H1 milestone... ;-) )22:09
*** jecarey has joined #openstack-meeting22:09
david-lyleno, I think we're set, we do have questions regarding domain scoping22:09
dolphmdomain scoped tokens?22:10
david-lylelcheng put it in the blueprint with screenshots22:10
gabrielhurleywhich blueprint?22:10
david-lyleno scoping operations to a domain in the UI22:10
*** sarob has quit IRC22:10
*** lcheng2 has quit IRC22:10
*** lcheng2 has joined #openstack-meeting22:11
david-lyleif you are admin and looking at a domain it doesn't necessarily make sense to then go look at other panels and see all22:12
*** huats_ is now known as huats22:12
gabrielhurleydavid-lyle: my initial thought is that for the case of an uber-admin with cross-domain privileges some sort of "active context" is probably a good idea, as per the suggestions in the whiteboard22:12
david-lyleso setting a domain scope to filter those panels makes domain adminstration a lot easier22:12
gabrielhurleyokay, other blueprints22:13
gabrielhurleystevebaker: are you around to talk about the Heat UI at all?22:13
*** harlowja has joined #openstack-meeting22:14
gabrielhurleyanyhow, I messaged Steve about that BP this morning, I'm sure he'll get back to me about it. It may slip to H2, but we'll see.22:14
gabrielhurleyah, h!22:15
* stevebaker reads22:15
gabrielhurleybasically just asking what the state of it is and what we can do to help22:15
gabrielhurleyI'd love to let people start trying out Heat in Horizon as early in the cycle as possible (which'll bump adoption for y'all too)22:16
stevebakerI've been distracted by heat tempest stuff, but will get back onto horizon heat next. Current task is writing a test for the stack create workflow22:16
*** harlowja_ has quit IRC22:16
stevebakerwhich I'll need some help with.22:16
gabrielhurleyyeah, I recall that there were two pieces that needed doing from the summit: the tests, and the "post the template and get back a form" workflow bit.22:17
*** HeidiBretz has quit IRC22:17
stevebakerat least I'll be able to submit to gerrit once this test is done22:17
gabrielhurleyIf that second part is still unresolved then perhaps you could post the current state of your code for collaboration and we can collectively get that doe22:17
gabrielhurleysounds great22:17
*** egallen has quit IRC22:17
gabrielhurleykeep us posted :-)22:17
stevebakerok, cool22:18
gabrielhurleyI don't see amotoki here... can anyone speak to the Quantum Security Groups blueprint?22:18
gabrielhurleyI haven't had any updates there in a couple weeks.22:18
david-lyleeric peterson contacted him about that22:19
*** sushils has quit IRC22:19
gabrielhurleygood to know22:19
david-lylehe's not made any progress lately22:19
gabrielhurleythis is the one I actually think is most likely to slip to h222:19
gabrielhurleyit's not a simple problem due to the differences in quantum and nova22:19
david-lylehe did provide a link to his work in progress but it dates back to sometime in grizzly22:19
gabrielhurley(per-port vs. per-server)22:19
david-lylemy guess is a slip, but I can't speak for amotoki22:20
gabrielhurleyI'll check in with him myself, but don't be surprised if this one is deferred22:20
gabrielhurleythanks for the update though22:20
gabrielhurleyTatiana Mazur indicated confidence in landing the DRY templates BP in H1, so I'd guess we'll see a review in the next week or so.22:20
gabrielhurleyI believe that leaves the rest of the BPs as currently in code review (and most of those look pretty good as far as I could see today)22:21
lcheng2gabrielhurley: when you get the chance, can you perform an initial review https://github.com/gabrielhurley/django_openstack_auth/pull/4122:21
*** sushils has joined #openstack-meeting22:22
gabrielhurleylcheng2: I actually have looked at it and don't see any major issues, but don't wanna commit anything based on non-final code in keystoneclient22:22
gabrielhurley#topic bugs22:22
*** openstack changes topic to "bugs (Meeting topic: horizon)"22:22
*** marun_ has joined #openstack-meeting22:23
gabrielhurleyThere's one bug I wanna call attention to22:23
*** topol has joined #openstack-meeting22:23
gabrielhurleyand maybe other folks here can help sort out where we need to go with it22:23
uvirtbot`Launchpad bug 1179526 in horizon "source_lang in Horizon repo is overwritten by Transifex" [High,Confirmed]22:23
gabrielhurleymy understanding is we've basically got the source language codes crossed between Horizon and Transifex and that's causing a lot of woes22:23
*** vkmc_ has quit IRC22:24
*** egallen has joined #openstack-meeting22:24
*** ladquin_afk is now known as ladquin22:24
*** marun has quit IRC22:24
*** marun_ is now known as marun22:24
gabrielhurleygoing further, it sounds like we probably need to scrap the source language on Transifex and align it to the correct source language in Horizon22:25
gabrielhurleydoing that may screw up the existing translations, so what we need to do (I think) is back up the actual current translations and be prepared to re-add them to transifex if the whole thing goes haywire22:25
gabrielhurleyanyone got any input here?22:25
mrungeno, sadly not.22:26
gabrielhurleyheh. okay.22:26
gabrielhurleywell, I'll post my thoughts on the ticket22:27
jpichNo, might be worthwhile talking with those mysterious contacts we have in Transifex to see if they have any input on handling this22:27
gabrielhurleyjpich: also a good idea22:27
gabrielhurleyokay then22:27
gabrielhurley#topic open discussion22:27
*** openstack changes topic to "open discussion (Meeting topic: horizon)"22:27
gabrielhurleyThat's all I have22:27
gabrielhurleyother folks?22:27
*** mkollaro has quit IRC22:28
david-lyleI have high level multi-region support implemented and would like to review, but I need openstack-auth changes22:28
david-lyleI know it's not H1, but our environment needs it22:29
gabrielhurleydavid-lyle: I saw that one too. I think I misread the description the first time.22:29
gabrielhurleyI'll take another look at it22:29
david-lyleok, thanks! https://github.com/gabrielhurley/django_openstack_auth/pull/4222:30
gabrielhurleyWhen we get that squared away we need to do some better differentiation between regions in a single service catalog vs. different auth endpoints (which is what Horizon's "regions" setting controls now)22:30
*** anniec has quit IRC22:31
*** litong has quit IRC22:31
gabrielhurleyI assume that'll happen in the Horizon review that accompanies the openstack-auth PR, though22:31
*** pcm_ has joined #openstack-meeting22:31
*** pcm_ has quit IRC22:31
david-lyleyes, I'm not sure providing the current region picker is of much value22:31
*** pcm_ has joined #openstack-meeting22:32
david-lyleas a login is required when switching22:32
*** dcramer_ has quit IRC22:32
gabrielhurleyIt's actually super-useful for dev against multiple environments, and it originally came out of a use case at rackspace, I think.22:32
gabrielhurleybut I'm not sure it's used very often these days22:32
david-lylewe use it, but essentially the same number of clicks would log you out and select a different region22:33
david-lyleI'm don't mind it, but I think it can be confusing22:33
gabrielhurleyfair enough22:34
gabrielhurleywe can discuss more later22:34
gabrielhurleyanybody else got other topics before I wrap things up here?22:35
*** stevebaker has quit IRC22:35
*** stevebaker_ has joined #openstack-meeting22:35
*** stevebaker_ is now known as stevebaker22:35
*** echohead_ is now known as echohead22:35
gabrielhurleythanks for the input, y'all22:36
gabrielhurleykeep up the hard work22:36
gabrielhurleysame time next week!22:36
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:36
openstackMeeting ended Tue May 14 22:36:39 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-05-14-22.02.html22:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-05-14-22.02.txt22:36
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-05-14-22.02.log.html22:36
*** bradjones is now known as bradjones|away22:37
david-lylethanks Gabriel22:37
*** jpich has quit IRC22:38
*** mrunge has quit IRC22:41
*** Adri2000 has quit IRC22:44
*** jaypipes has quit IRC22:44
*** markpeek has joined #openstack-meeting22:44
*** gabrielhurley has quit IRC22:44
*** dcramer_ has joined #openstack-meeting22:48
*** sarob has joined #openstack-meeting22:48
*** carl_ has left #openstack-meeting22:49
*** Adri2000 has joined #openstack-meeting22:51
*** mattray has quit IRC22:51
*** Swami has joined #openstack-meeting22:53
*** Swami has quit IRC22:54
*** anniec has joined #openstack-meeting22:54
*** Swami has joined #openstack-meeting22:56
*** Swami has quit IRC22:56
*** epim has quit IRC22:59
*** HeidiBretz has joined #openstack-meeting23:01
*** leandrorosa has quit IRC23:04
*** epim has joined #openstack-meeting23:04
*** dolphm has quit IRC23:05
*** kebray has quit IRC23:07
*** sarob_ has joined #openstack-meeting23:08
*** dcramer_ has quit IRC23:09
*** brucer has quit IRC23:11
*** sarob has quit IRC23:12
*** sarob_ has quit IRC23:13
*** markwash_ has joined #openstack-meeting23:13
*** gongysh has joined #openstack-meeting23:15
*** markwash has quit IRC23:16
*** markwash_ is now known as markwash23:16
*** sgordon__ has joined #openstack-meeting23:16
*** HeidiBretz has quit IRC23:22
*** sacharya has joined #openstack-meeting23:22
*** epim has quit IRC23:29
*** saurabhs has quit IRC23:31
*** HeidiBretz has joined #openstack-meeting23:32
*** anniec has quit IRC23:32
*** sushils has quit IRC23:34
*** kebray has joined #openstack-meeting23:35
*** amyt has quit IRC23:36
*** sushils has joined #openstack-meeting23:39
*** lloydde has quit IRC23:42
*** HeidiBretz has quit IRC23:44
*** schwicht has quit IRC23:45
*** sacharya has quit IRC23:47
*** colinmcnamara has quit IRC23:48
*** asalkeld_ has quit IRC23:49
*** asalkeld has joined #openstack-meeting23:49
*** salv-orlando has quit IRC23:52
*** schwicht has joined #openstack-meeting23:54

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